Incorrect information

"Users running canvas apps when a security group is associated with the environment of the app must be members of the security group to be able to run the canvas app, regardless of whether the app has been shared with them. Otherwise, users will see this error message: "You can't open apps in this environment. You are not a member of the environment's security group." If your Power Platform admin has set governance details for your organization, you will see a governance contact that you may reach out to for security group membership."
A customer must fill out an Office Form to have a change made to the EnforceDataverseUserAccessMonitoringMode to make this behavior work as documented.

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

ID: 9aafd67e-8013-565e-6566-9773136c4405
Version Independent ID: 1db48adc-6512-7978-4656-2cf081b5cdb7
Content: Control user access to environments: security groups and licenses - Power Platform
Content Source: power-platform/admin/control-user-access.md
Service: power-platform
Sub-service: admin
GitHub Login: @paulliew
Microsoft Alias: paulliew

Thanks for your comment, @russrimm. This issue has been assigned to the doc author for review.


Firebase Analytics different method names?

https://github.com/flutter/flutter/issues/37600

Closing this due to the tag spam from other issues. If this is still an issue then it'll most likely be covered under #2582


GraphiQL onEditQuery is called without query argument after TypeScript migration

I'm updating our installation of graphiql to 1.0.0-alpha.1, and thanks to the new TypeScript types (🎉) I was was really quickly made aware that the type signature of the function passed to GraphiQL as the onEditQuery prop has changed:

This breaks our usage of graphiql-explorer. (see example setup  which uses onEditQuery https://github.com/OneGraph/graphiql-explorer-example/blob/master/src/App.js#L189)
It looks like this change was made in the recent TypeScript migration.
I understand that this prop is likely going to be deprecated in the new API per #1165, but it looks to me like this change was unintentional (onEditQuery is unchanged in the README, and per https://github.com/graphql/graphiql/pull/1242#issue-364380842 that this should have minimal production changes).

this might be a good candidate for a hotfix to backport

or wait, so this is only an issue in alpha, as 0.17.5 was before the typescript migration

@acao right! I had the issue in 1.0.0-alpha.1/3, so no need to backport

great! thanks for this, we can get another alpha out here shortly. I'll close this once it's been released. glad the new typescript types are working out for you :smile:

pre-release is out, find 1.0.0-alpha.4 :)

use latest alpha btw! @cshaver lemme know if you have any issues


Add support for aws.iam.ManagedPolicies.AWSXRayDaemonWriteAccess

Fixes: #1062

Thanks so much for this @michael-golden :)


Cannot Remote Desktop Client

I have an issue with remote desktop client in together LAN wifi in lastest version : 1.4.0

Please follow the bug reporting guidelines: https://github.com/quasar/Quasar/issues/new?template=bug_report.md


No threads to run command

I am exceedingly excited to try to use your debugger pluging but have been running into a few problems. I was hoping you could point me in the right direction here. Any attempt to use the lldb adapter results in an exception. I cannot get the terminal to launch with the platform module and when I switch to the terminus plugin I run into the following exception without fail:
OS: Windows
{
"log_info": true,
"ui_scale": 10,
"font_face": "Inconsolata",
"external_terminal": "terminus"
}
Just to be sure I was on head I pulled your plugin from source:
Branch ST3 head as of today 1/3/2021
commit 85387c9334688974817361c473ce0f98ce3fd489 (HEAD -> st3, tag: st3-0.2.10, origin/st3)
Author: David<EMAIL_ADDRESS>Date:   Fri Nov 13 01:43:07 2020 -0800
fixes issues with latest release of lldb adapter and fixes #74

I am getting the following when I click the play button in a debug session:
I have a simple application that does a printf inside main and I am trying to break on the first line.
NOTE the TRYING TO START THINGS is my little addition to the package to understand where things were going off the rails with the platform terminal.
======================================================
updating settings callback view
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
updating settings callback view
updating settings callback view
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
updating settings callback view
updating settings callback view
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
updating settings callback view
updating settings callback view
Settings were udpdated: reloading configuations
Settings were udpdated: reloading configuations
Starting process: ['node', 'C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger/debug_adapters/lldb_util/entry.js', 'C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\data\debug_adapters\vscode-lldb/extension/adapter/codelldb']
<<  {"type": "request", "command": "initialize", "seq": 1, "arguments": {"locale": "en-us", "adapterID": "python", "clientID": "sublime", "clientName": "Sublime Text", "columnsStartAt1": true, "supportsRunInTerminalRequest": true, "linesStartAt1": true, "supportsVariableType": true, "supportsVariablePaging": false, "pathFormat": "path"}}

{"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"exceptionBreakpointFilters":[{"default":true,"filter":"cpp_throw","label":"C++: on throw"},{"default":false,"filter":"cpp_catch","label":"C++: on catch"}],"supportTerminateDebuggee":true,"supportsCancelRequest":true,"supportsCompletionsRequest":true,"supportsConditionalBreakpoints":true,"supportsConfigurationDoneRequest":true,"supportsDataBreakpoints":true,"supportsDelayedStackTraceLoading":true,"supportsEvaluateForHovers":true,"supportsFunctionBreakpoints":true,"supportsGotoTargetsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsLogPoints":true,"supportsReadMemoryRequest":true,"supportsRestartFrame":true,"supportsSetVariable":true}}
<<  {"type": "request", "command": "launch", "seq": 2, "arguments": {"type": "lldb", "request": "launch", "args": ["-arg1", "-arg2"], "name": "Dbg", "program": "C:\Users\ihdav\repos\cpptest/src/a.exe"}}
{"type":"event","seq":1,"event":"initialized"}
{"type":"request","seq":2,"command":"runInTerminal","arguments":{"args":["C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\data\debug_adapters\vscode-lldb\extension\adapter\codelldb.exe","terminal-agent","--port=61512"],"cwd":"","kind":"integrated","title":"Dbg"}}
Starting process: ['C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\data\debug_adapters\vscode-lldb\extension\adapter\codelldb.exe', 'terminal-agent', '--port=61512']
TRYING TO START THINGS
<<  {"type": "response", "message": null, "seq": 3, "request_seq": 2, "success": true, "command": "runInTerminal"}
<<  {"type": "request", "command": "setDataBreakpoints", "seq": 4, "arguments": {"breakpoints": []}}
<<  {"type": "request", "command": "setExceptionBreakpoints", "seq": 5, "arguments": {"filters": ["cpp_throw"]}}
<<  {"type": "request", "command": "setBreakpoints", "seq": 6, "arguments": {"source": {"path": "C:\Users\ihdav\repos\cpptest\src\main.cpp"}, "breakpoints": [{"line": 6}]}}
<<  {"type": "request", "command": "setFunctionBreakpoints", "seq": 7, "arguments": {"breakpoints": []}}
{"type":"response","request_seq":4,"success":true,"command":"setDataBreakpoints","body":{"breakpoints":[]}}
{"type":"response","request_seq":5,"success":true,"command":"setExceptionBreakpoints"}
{"type":"response","request_seq":6,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"id":2,"message":"Locations: 0","verified":false}]}}
{"type":"response","request_seq":7,"success":true,"command":"setFunctionBreakpoints","body":{"breakpoints":[]}}
<<  {"type": "request", "command": "configurationDone", "seq": 8, "arguments": null}
{"type":"event","seq":3,"event":"output","body":{"output":"Launching: C:\Users\ihdav\repos\cpptest\src\a.exe -arg1 -arg2\n"}}
{"type":"event","seq":4,"event":"output","body":{"output":"Launched process 16192\n"}}
{"type":"response","request_seq":2,"success":true,"command":"launch"}
{"type":"response","request_seq":8,"success":true,"command":"configurationDone"}
{"type":"event","seq":5,"event":"continued","body":{"allThreadsContinued":true,"threadId":0}}
Traceback (most recent call last):
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\core\sublime_event_loop.py", line 13, in call
self.callback(*self.args)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\dap\client.py", line 332, in _on_continued
self._continued(threadId, body.get('allThreadsContinued', True))
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\dap\client.py", line 339, in _continued
self.events.on_continued_event(event)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\debugger\debugger_session.py", line 466, in on_continued_event
self.callstack.on_continued_event(self.client, event)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\debugger\debugger_session.py", line 652, in on_continued_event
self.on_selected_thread(None)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\core\event.py", line 37, in call
self.post(*data)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\core\event.py", line 41, in post
h.callback(*data)
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\debugger\debugger_session.py", line 63, in
self.callstack.on_selected_thread.add(lambda thread: self._refresh_state())
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\debugger\debugger_session.py", line 222, in _refresh_state
thread = self.callstack.command_thread()
File "C:\Users\ihdav\AppData\Roaming\Sublime Text\Packages\Debugger\modules\debugger\debugger_session.py", line 577, in command_thread
raise core.Error("No threads to run command")
Debugger.modules.core.error.Error: No threads to run command
==============================================================

Re-open if you still are running into issues here


Merging synchronous stream with self doesn't work right

This should print out 2, 3, and <end>, but only 2 and <end> get printed.
var Bacon = require('baconjs');

var s = Bacon.once(2);
s.merge(s.map(3).delay(1)).log();

Changing it to be var s = Bacon.once(2).delay(1); or merging against a different stream like s.merge(Bacon.once(2).map(3).delay(1)).log(); both work fine.
Bacon 0.7.41 from NPM

Known issue, sorry :( See #367


Hide Empty Groups

Gibberbot currently displays groups which have zero online members. With large, diverse, extensively-grouped contact lists, this makes for a cluttered display, especially when few contacts are online. It should be possible to choose to hide these groups, so that only groups with online members are displayed.

We don't show groups anymore!


[YUNIKORN-2956] Fix layout break on Queues v2 page

What is this PR for?
Queues v2 page layout not expected fit content in panel when media screen height small.
It will overflow the panel block.
What type of PR is it?

[x] - Bug Fix

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2956
Screenshots (if appropriate)

Before
After

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 35.71%. Comparing base (d714335) to head (85f7b36).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #220   +/-   ##
=======================================
  Coverage   35.71%   35.71%
=======================================
  Files           2        2
  Lines          56       56
=======================================
  Hits           20       20
  Misses         33       33
  Partials        3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Grand Rick Patch 5

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

There seem to be no changes in this Pull Request so I will be closing it.  Please raise a new one with your desired changes - you may wish to have a look at our Editing Guide in Docs: https://linkfree.eddiehub.io/docs/how-to-guides/editing


Add & clean deprecated

Related: #877

Codecov Report

Merging #895 (fcade91) into master (8301b6c) will increase coverage by 0.57%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #895      +/-   ##
==========================================
+ Coverage   78.84%   79.41%   +0.57%
==========================================
  Files         106      105       -1
  Lines       10879    10758     -121
==========================================
- Hits         8578     8544      -34
+ Misses       2301     2214      -87

Impacted Files
Coverage Δ

authority/src/lib.rs
78.94% <ø> (+0.28%)
:arrow_up:

authority/src/tests.rs
100.00% <ø> (ø)

oracle/rpc/src/lib.rs
0.00% <ø> (ø)

tokens/rpc/src/lib.rs
0.00% <ø> (ø)

utilities/src/lib.rs
100.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Hover breaks if button disabled

If button is disabled and radium styles contain styling for hover attribute it will apply that styling on hover but will not remove it after hover away:
<button type='button' disabled={true} style={styles.button}>I'm button</button>

let styles = {
  button: {
    backgroundColor: 'blue',
    ':hover': {
      backgroundColor: 'red'
    }
  }
}

In this example button will be rendered as blue initially, but on hover, it will become red as expected. But the problem arises when you hover away, although it would be expected to have a button go back to original blue color, it will actually stay red forever.
Additional: Even after this bug gets fixed it makes it difficult for the user to style button on hover if it can possibly be disabled. So we have to leave ':hover' styling as an empty object and then use Readium.getState to know when button is hovered and then apply our own styling in case button is hovered but not disabled. This was very easy with CSS ':hover:disabled', but with Radium it has to be additionally complicated:
<button type='button'
             disabled={this.props.disabled}
             key='button'
             style={[styles.button, Radium.getState(this.state, 'button', 'hover') && !this.props.disabled &&
                         styles.buttonHovered]}>
  I'm button
</button>

let styles = {
  button: {
    backgroundColor: 'blue',
    ':hover': {}
  },
  buttonHovered: {
    backgroundColor: 'red'
  }
}

EDIT: Referenced here https://github.com/FormidableLabs/radium/issues/686
If that pull request with :disabled props gets merged this issue can also be closed.

Thanks @niksajanjic! Going to close this issue in favor of #686. Will work on landing that PR to resolve this.


Fix vetting locations and email templates

Note that the concept of a VettingLocation will have to go in the near future, as RaLocations and RegistrationAuthorityCredentials are clearly distinguishable concepts that do not need to be unified in this manner.

:+1:


Adding a simple config makes the proxy host offline

I'll keep this plain and simple.
I added a simple proxy host with the following advanced config;
server {
       listen 81;
       listen [::]:81;

       server_name example.example.com;

       root /var/www/example;
       index index.html;

       location / {
               try_files $uri $uri/ =404;
       }
}

And when I saved the config, the proxy host status just says offline.

Even if I remove the server {} part it just gives me a 404 error.

Do you mean the advanced config/Custom Nginx Configuration as set in the web gui?
That custom config will just drop in above the location tag on the actual nginx config file. NPM does the rest, so you wouldn't put in any of the other stuff. The only part you could specify is:
       root /var/www/example;         index index.html;
Or are you creating a completely new .conf file and dropping it in the proxy_host directory?

@wolviex
Hello, I was looking at the wrong config, however, I had to remove server {} and it fixed that config (for some reason).
Now, the real config is as follows (it's a bit lengthy)
server {
    server_name guardsman.astrohweston.xyz;

    root /opt/guardsman-web/public;
    index index.html index.htm index.php;
    charset utf-8;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
        expires 1y;
        add_header Cache-Control "public, no-transform";
        add_header Accept-Encoding "gzip, compress, br";
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log  /var/log/nginx/guardsman.log error;

    location /api/* {
        expires -1;
        add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
    }

    location /openapi.json {
        expires -1;
        add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
    }

    location /statistics.json {
        expires -1;
        add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
    }

    #GZIP
    # Enable gzip compression.
    gzip on;

    # Compression level (1-9).
    # 5 is a perfect compromise between size and CPU usage, offering about
    # 75% reduction for most ASCII files (almost identical to level 9).
    gzip_comp_level    5;

    # Don't compress anything that's already small and unlikely to shrink much
    # if at all (the default is 20 bytes, which is bad as that usually leads to
    # larger files after gzipping).
    gzip_min_length    256;

    # Compress data even for clients that are connecting to us via proxies,
    # identified by the "Via" header (required for CloudFront).
    gzip_proxied       any;

    # Tell proxies to cache both the gzipped and regular version of a resource
    # whenever the client's Accept-Encoding capabilities header varies;
    # Avoids the issue where a non-gzip capable client (which is extremely rare
    # today) would display gibberish if their proxy gave them the gzipped version.
    gzip_vary          on;

    # Compress all output labeled with one of the following MIME-types.
    gzip_types
      application/atom+xml
      application/javascript
      application/json
      application/ld+json
      application/manifest+json
      application/rss+xml
      application/vnd.geo+json
      application/vnd.ms-fontobject
      application/x-font-ttf
      application/x-web-app-manifest+json
      application/xhtml+xml
      application/xml
      font/opentype
      image/bmp
      image/svg+xml
      image/x-icon
      text/cache-manifest
      text/css
      text/plain
      text/vcard
      text/vnd.rim.location.xloc
      text/vtt
      text/x-component
      text/x-cross-domain-policy;
    # text/html is always compressed by gzip module

    # allow larger file uploads and longer script runtimes
    client_max_body_size 100m;
    client_body_timeout 120s;

    sendfile off;

    location /api/docs {
        proxy_pass http://<IP_ADDRESS>:9001;
    }

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param PHP_VALUE "upload_max_filesize = 100M \n post_max_size=100M";
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param HTTP_PROXY "";
        fastcgi_intercept_errors off;
        fastcgi_buffer_size 16k;
        fastcgi_buffers 4 16k;
        fastcgi_connect_timeout 300;
        fastcgi_send_timeout 300;
        fastcgi_read_timeout 300;
    }

    location ~ /\.ht {
        deny all;
    }
}

The above config file has been edited so it doesn't require an SSL cert. I'm assuming I can add when I'm making a proxy host?
In any case, even when I add this, it just says that it's offline. Again, I removed the server {} part of the config, and it showed it online. However, when I opened the website, it have me a 502 error. I then added an SSL certificate in the proxy manager, and it still would not work and would just give me a 502 error. From what I've gathered from a normal Nginx instance, I wouldn't need to run any of the files in order to get my site up.
But now, I don't know so I'd really appreciate any help that can be given, thank you!

My configuration is pointing towards port 80, which was in the config file but I removed it and just added it to the proxy host instead.

If you're manually editing the nginx configuration files then this isn't an NPM question, this is an nginx question. Nginx Docs
The fact that you're specifying a root with index suggests that this is not a proxy host, it only has proxy subdirectories.
What part of this are you creating with NginxProxyManager?

Hey, can you ellaborate what you mean by what part?
Thank you!

What part of this configuration are you creating with Nginx Proxy Manager, in the WebUI?
What Docker Image are you using here?


mudlet package: Unknown module(s) in QT: uitools multimedia

Issue description
while working on lua support, I tried updating mudlet but I have this issue (which also happens on master) @wyvie any idea ?
Info: creating stash file /build/Mudlet-Mudlet-3.0.0-delta/src/.qmake.stash
Project MESSAGE: mudlet will be installed to /nix/store/zn5k5aw6frf0x8bg66xcjaryjiqy2bkx-mudlet-3.0.0-delta/bin...
Project MESSAGE: Lua files will be installed to /nix/store/zn5k5aw6frf0x8bg66xcjaryjiqy2bkx-mudlet-3.0.0-delta/share/mudlet/lua...
Project MESSAGE: Geyser lua files will be installed to /nix/store/zn5k5aw6frf0x8bg66xcjaryjiqy2bkx-mudlet-3.0.0-delta/share/mudlet/lua/geyser...
Project ERROR: Unknown module(s) in QT: uitools multimedia
note: keeping build directory '/tmp/nix-build-mudlet-3.0.0-delta.drv-0'

Steps to reproduce
nix-build -A mudlet <master>
Technical details
sandboxed mode on 453a60ed9556f4cbbd1d3868419abd0a6c35992b

Adding qttools and qtmultimedia to buildInputs (and the arguments) should fix that.

lost interest in that one


KAFKA-13495: add reason to JoinGroupRequest

As part of KIP-800, this patch aims to add a reason to why a consumer is joining a group and log it in the broker.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@dajac @showuon i reverted to using reason: Option[String] for handleJoinGroup(). KafkaApi always pass in a reason which could be null so we would see "null" as the reason instead of "not provided".

@dajac gentle reminder to take another pass

@jeffkbkim , KafkaApisTest is still failed some tests. Please take a look. Thanks.
https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-11566/6/#showFailuresLink


Need help for the maintenance of this project?

Hey @ronvanderheijden ,
Your package is exactly what I needed and I'm using (a fork of) it in production now.
So first of all, thanks for the hard work.
I've noticed you are not maintaining it anymore (I'm not sure you even noticed the 4 PRs I opened :) )
In the case you are seeing this message, do you need help in maintaining it? I'm considering forking it but I would really like to avoid that as much as possible as fragmenting the packages is never a good idea. If you need some help to review the PRs, I'm volunteering to help maintain the package! Let me know!

I hope the owner responds back to us, as I am using this package in an abstracted manner to develop OAuth 2.1 + OpenID Connect for our microservices at my startup, @myanmarcyberyouths, and my product, https://breezemm.com.

Hey guys!
I am glad you like the package, but maintaining it is currently not possible for me. I can look at PRs now and then, but I don't have the time right now to work on new features/bugfixes
@moufmouf , your help as a volunteer/co-maintainer is very welcome! I will give you some permissions to do that, but I would like to be a part of the review process.
Thanks again for your kind words. Let's make the packages up-to-date and better together!

Thanks a lot! I don't know why, I only noticed your message now.
I'll make my best ;)
We still have #17 and #18 to merge. Shall I wait for your comments or proceed forward?


How to use li with list type none ?

I have following lines:
docx.ul do
li 'Text1'
li 'Text2'
end
I don't want list items to be marked with any bullets, numbers or letters.

If you want all unordered list to have this appearance, the best choice is to alter the default list styles applied to the document using the list_style directive.  You can get an overview in the README.  If you'd like to see the default values used by the document as a reference, you can do so here.  I believe the format value you want is 'none', but you can research the OOXML tags used by the renderer by googling ooxml and the tag in question.
If you only want this appearance for a single list, it might actually be easier to implement your unstyled list as a borderless table.  (Tables are also covered in the README.)


[MQ - build reliability]: Nightly smoke tests runs are failing

The JavaScript smoke tests pipeline has been failing for quite some time - the last time it passed was on August 5th.
https://dev.azure.com/azure-sdk/internal/_build?definitionId=740&_a=summary
The failures are consistent and seem to involve samples from form-recognizer and service-bus:
##[error]Test Failed - Package: ai-form-recognizer - Sample File:recognizeBusinessCard.js
exception: TypeError: Cannot read property 'value' of undefined
##[error]Test Failed - Package: service-bus - Sample File:usingAadAuth.js
exception: ServiceBusError: ENOTFOUND: getaddrinfo ENOTFOUND .servicebus.windows.net
CC: @benbp, who has worked on the smoke test pipeline in the past.

@richardpark-msft the test matrix includes gov/china clouds, which are still not yet in a working state. However, the last succeeding run for the public cloud smoke tests was 10/28: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=595160&view=results

Looking into this a bit more we've got some problems but I think we can solve at least a few of them right off the bat:

Our test-resources.yaml wasn't creating the sample queues we need for samples to run. Which would have been obvious if...
...we were running real samples. Our portion of the smoke tests that was failing was because we were only running the usingAadAuth.js and it didn't do any actual usage of the client until recently. So it never worked either, we just didn't realize that.

My work right now is to see if I can drag in some more realistic samples, fix the .yml for service bus. It's not going to be perfect but we'll have something useful at the end. :)


The Substrate release stream which is followed is not documented

https://github.com/threefoldtech/tfchain/blob/development/docs/development/upgrade_deps.md


Partial sync on mobile client - android

KBFS gives me 250GB of encrypted storage, which is absolutely awesome and a great secure alternative for storing my project files and personal records, with the possibility of having the most important documents always with me.
However, while on the desktop I can customize the paths synced (keybase fs enable ...), there's just no way I can do it on the mobile app. This makes the offline feature basically unusable on the mobile as there's no way I could store 250 (or even simply 10) GB of data on my mobile, and thus I can't sync any files (as it's all-or-nothing). What I would like to be able to do is something like #15044, but for mobile. Is it possible?

We don't yet have a GUI design for supporting partial syncs on mobile; once we do, we'll implement it, but I can't promise any timeline on that.
In the meantime, for stuff you want synced on mobile, you could in theory make a new team (or subteam) for yourself, sync that team's folder, and put the important stuff in there.

thank you @strib, I'll follow your suggestion and make a personal team then


[Suggestion] Mutually exclusive

A pretty cool and useful feature would be to have it be possible to have CE's be mutually exclusive with both other CE's and normal enchantments. This could either be hard coded or configurable I feel that the latter would be the more appreciated version.

Could you explain more to me?

Like where you can't have silk touch and fortune on a pickaxe.


fix(multi): extract path from the first subtxn

This is a hack, not a proper fix. We'd need to
rework how we handle paths (right now only path is
expected to be associated with a request) to actually
be able to expose more paths.
Signed-off-by: Raul Gutierrez S<EMAIL_ADDRESS>

LGTM, ship it!


plot_model gives different results using theano and tensorflow

Hi, when I was using plot_model to view the keras model structure, theano and tensorflow backend gave different results. I wonder if this is normal? Thanks.

Hi!
When creating an issue, it's very helpful for the people reading to have the code. Could you please provide it? If you can reproduce the issue with a minimum amount of code, it would also accelerate the reviewing process.
Thank you.


Add Twitter to URL matches

Twitter also mutes video when the tab is switched.

@buttercookie42 Would you like to review this?

@nils-werner: Can you confirm that this is still necessary? I've tried a few Twitter videos (e.g. this) and background playback worked fine for me.
Embedded Youtube videos (via an iframe) should work anyway and apart from that in practice the mobile Twitter page opens the full Youtube page anyway instead of playing the video in its embedded form.

@butterookie42 I've just tried it in firefox mobile. Background playback is working on twitter.

Okay, in that case please re-open if Twitter ever changes its behaviour again.


Move the tests on RSoulatIOHK/cardano-c-cbmc to C from CPP

in /lib/tests/ all the tests are written in CPP. I want to move them to C so that I can use CBMC later to improve assurance.

Hi @RSoulatIOHK, we chose gtest for unit testing since it is really versatile and makes writing tests really fast. But if there is more value in having the tests in C (I.E so they can be made into CBMC proofs), we could change our workflow for this, we do have 1100 tests currently (we aim for 100% code coverage since we use the tests + valgrind to hunt for memory leaks) and I estimate we will have several times more tests since we are barely at 50% of the project progress, so back porting all of those tests could take some time 😅. I wonder if the CMBC tests could be added orthogonally to the unit tests suite. Anyways, let me know if there is something we can do to help with this effort, we are always looking into ways to increase the reliability and assurance of the library

Hi @AngelCastilloB . Thanks for your feedback. I raised an issue on my fork so that it can be in our backlog of ideas in GitHub projects, I did not expect someone from the original team to work on that 😄 it could be orthogonal for sure, I hope I can find some time to set CBMC on this :)


Server Rack Metadata Retrieval and Persistence on Azure Environment

In order to move Pinot to cloud, cloud VM rack metadata awareness is needed for maintenance purpose and disaster recovery. In Azure use cases, fault domain (FD) metadata is needed in the Pinot ecosystem during update or fault events.
In this issue we will focus on retrieving and persisting FD and VM instance information of Azure VM for Pinot servers so that later on we can use this mapping to fit in existing Server Pool Based Instance Assignment or Replica-Group Instance Assignment based strategy for high data availability purpose.

So in this case, we need to set server instances metadata and use it for segment assignment.
I feel the complication is that we need to handle rack metadata change which involves the segment assignment reblance.

@xulinjintu wondering whether your changes can be used for AWS as I am interested to use it there. Also once the segment is tagged with failure domain zone information how the segment replicas are handled to spread across different zones?

@xulinjintu Also I was trying to compare the Azure to AWS and wondering whether it is possible to add (if not already added)  following information for Azure
a) Region
b) Availability Zone
c) Availability Set
d) Fault Domain (Already included)
This will enable AWS also to use this implementation directly and potentially works for GCP. Because AWS High Availability  is driven by Availability Zones and Regions . This in-turn also helps Azure as well because then you can cover any failures from a particular Availability zone which is highly important for a proper HA design.

So in this case, we need to set server instances metadata and use it for segment assignment.
I feel the complication is that we need to handle rack metadata change which involves the segment assignment reblance.

@fx19880617 This is the first step, instance assignment strategy will be addressed in another issue.

@pabrahamusa This can definitely be extended to AWS, the additional work would be implementing AWS metadata retrieval processors. Special configs for AWS might be needed.
Regarding those properties we retrieve, I wonder if fault domain is unique across different regions. Availability zone is essentially a combination of FD and UD. Since update domains are subsets of fault domains, I wonder if we only need to FD to achieve HA.

@xulinjintu  Adding just FD should work if FD is unique per AZ.  However do you think it will be better to add  Availability Sets , FD and UD  to provide more granular control and flexibility on replicas?  For HA, Muti AZ is only needed where Single points of failure (SPOF) are eliminated with an N+1 or 2N redundancy configuration. Where Muti Region design can bring other complexities like replication lag so we could potentially ignore Region all together.  Please note that In AWS instead of Availability Sets,FD and UD it is just AZ (Availability Zone).

@pabrahamusa , @fx19880617 , the idea here is to make it cloud neutral. The goal is to assign instances in such a way that each instance for a table is in an "island". The definition of an "island" is cloud-specific. The requirement is that the provider gives a guarantee that should there be some planned outage, no two "island"s will be taken down at the same time. For Azure, this happens to be called Fault Domain. For a data center providing native hardware, this turns out to be "rack". If there are APIs to recognize the "island" to which an instance belongs (or, APIs to ask for N instances in N -- or even M  different islands), then we can potentially use those APIs to arrive at an optimal instance assignment for a table.
The approach followed is that we mark in a single place in zookeeper (at cluster level) the "ID" of the provider (e.g. "Azure" or "XYZ"). We then have specific paths in ZK where the characteristics, the API, perhaps the name of the plugin to be loaded, etc. are specified for the "ID" in question.
If the ID is not specified, an installation will not see any modifications to Znodes or any new znodes. @xulinjintu  is driving the design for this, so please provide input in the design document.
cc: @kishoreg

Instance pool concept can be used as the availability set. Please read: https://docs.pinot.apache.org/operators/operating-pinot/instance-assignment#pool-based-instance-assignment for more context

Please refer to the PR #6842 for Failure Domain Retrieval Logic for Server Instances.


Support wild cards for barback transformers

For Angular transformers, there's a scenario where they need to extract expressions from all HTML files within a directory. Currently in order to do this, the transformer needs to have some listing of all the files to be included. It would be ideal if the user could just provide some form of directory or regular expression of paths.
This seems like something which would be needed for an image sprite builder as well to avoid requiring every individual image be listed.

This issue has been moved to dart-lang/barback#29.


First Draft of the 2020 ANS Winter submission

This is the first rough draft.  I have some changes I know I need to make/ specific sections I need more help in than others:

I think the introduction may be too long, but I also think it doesn't quite get the motivation and background across.  I think it would help to go back to it after the rest of the paper goes through the first revisions and rewrite it.
in the theory section, I have left a comment to myself to create a figure to show the axial fuel-shuffling I describe in the report.  I have an image from a previous meeting, but it's more than one page long, so I need to make something that shows it in one figure.
I need to flesh out the results section, but I'm not sure what is appropriate to include here, since the page limit is 4 pages.  I was considering a table giving the mass fractions of the isotopes we really care about - uranium, plutonium, xenon, iodine, for start.  If this should be included, should it be in the appendix instead?
Conclusion needs work, though I also think I should re-write it last, with the introduction.
not sure of proper way to acknowledge the group and the NRC for my fellowship, is there a template?  I saw other papers in our group referencing the specific project number for their fellowship, where would I find this?
Is there anyone else I should include in the acknowledgements?
is there anything in the author information I've missed, and should I add Memo and Roberto as authors?
I need to go back through and add more in text citations
some odd formatting i still haven't found the source of

for the future, if it's a document, it's helpful to include the built pdf in the pr facilitate review

2020-richter-ans-winter-report.pdf
I think this might be more mature in a few weeks. Maybe the deadline will be extended or maybe ICAPP or PHYSOR will be accepting new papers for 2021...

(but, good start!!)


Forward/backward shortcut

Hi,
A common used shortcut for moving backwards and forwards between pages is not implemented.
Forward: alt + →
Backwards: alt + ←
This is for example used in Chrome, Firefox and Nautilus. It would be great if this could be implemented.
OS:
Arch Linux
GPMDP Version:
4.5.0-2

This was actually working on Mac, but with cmd + -> / cmd + <-.
On the latest version, it unfortunately has been broken.

+1
Also the "<-" button dissapeared from the search input. No possibility to navigate through the UI :(

Thought my mouse broke, but yeah, it definitely seems like forward and back are broken :[

Duplicate, fixed in master

Still not fixed. The XF86Back and XF86Forward (A.K.A. alt + left array and alt + right arrow) still not working. I mapped this to my mousepad gesture and it's working in almost every application, expect the gpmdp.


[Plugin Request] Smooth transition between two frames for switching color schemes

This could be done with widgets by creating a screenshot and easing out its opacity which is what gnome is actually doing, but instead of a screenshot it gets the rendered rectangle from the compositor, so I feel like it would be better to have this as a feature at the compositor level, because in my experience its kind of expensive and slow for GTK to render a fullscreen image and it doesn't feel as smooth
So my request is for a plugin that would expose a dispatcher that would ease in the next frame.
https://github.com/hyprwm/hyprland-plugins/assets/104676705/a87c6c1f-0610-4423-b74b-67f80ce7269a

sounds trivial

Hi, I actually made something fairly similar recently.
I am working on a tool, Ricer, that aims to make ricing all apps as seamless as possible.
I wanted to have something similar to a transition you described above so I made a simple Python script that takes a screenshot and then fades it out.
I plan to add more transitions, similar to swww, as soon as I have some free time.
Shifter
(Most of the delay seen in the video is caused by the glava taking a really long time to start, you can edit my fish function linked in the shifter repo so it waits less to start the fade)


Ellekit Support

Basic pr to add Ellekit Support, still testing

https://github.com/asdfzxcvbn/pyzule/issues/44#issuecomment-2183351063


Prevent error Argument #2 ($array) must be of type array

This PR will fix the following error when checking model macros:
Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array,
 null given in vendor/larastan/larastan/src/Methods/MacroMethodsClassReflectionExtension.php:135

This PR won't have any breaking changes.
The return value of $refProperty->getValue() can be null.

So with this change, it will be ignored if $refProperty->getValue() is null.

Thanks for this, can you please give an example of code that caused this to fail? Writing a test for this would be good too

Hi,
Cannot merge this without a test. Please try to add a test case.


Allow to use custom fetch implementation, axios example

Codecov Report

Merging #53 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   99.59%   99.59%   +<.01%
==========================================
  Files          16       16
  Lines         244      245       +1
  Branches       45       46       +1
==========================================
+ Hits          243      244       +1
  Misses          1        1

Impacted Files
Coverage Δ

src/client/client.ts
100% <100%> (ø)
: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 08c6d93...6c9a27e. Read the comment docs.


primesieve 6.2 fails two tests on 32bit architectures

According to Debian Package Auto-Building for the latest packaging for primesieve 6.2, here, primesieve 6.2 fails two tests on the i386 architecture (and other 32bit arch): the involved tests are: floorPow2 and ilog2 .

Hi Jerome,

The ilog2.cpp test has been fixed by commit https://github.com/kimwalisch/primesieve/commit/a1d3a3b812360a52712990500542552f6d49cbf1
The floorPower2.cpp test has been fixed by commit https://github.com/kimwalisch/primesieve/commit/6c74531408cab6d2f19f4bd0f71e3df69c328c85

The other bugs which are all related to:
libprimesieve.so.8.2.0: undefined reference to `__atomic_fetch_add_8'

are not primesieve bugs, these are caused by CPU architectures that currently don't fully support C++11 threading. The build status  shows that for each such failure the CPU architecture is out of date. I cannot fix these failures.

Thanks for the numerical fixes.
Otherwise, I am not sure what to understand by out of date CPU architecture: I guess it is more correct to say that the compiler doest not fully support C++-11 on some architectures. Of course we cannot fix the compiler (or the architectures). Given that, is there any work around that can be applied only on these exotic architecture ?

I guess it is more correct to say that the compiler doest not fully support C++-11 on some architectures.

Yes, that is more accurate.

Given that, is there any work around that can be applied only on these exotic architecture ?

Yes, I guess it is possible. This issue seems to be a known Debian bug. Apparently the atomic features are not in libpthread.so on some Debian CPU architectures  but in libatomic.so.
Hence a possible fix would be to add libatomic as a link dependency of libprimesieve and static_libprimesieve in CMakeLists.txt:
- target_link_libraries(libprimesieve Threads::Threads)
+ target_link_libraries(libprimesieve Threads::Threads atomic)

- target_link_libraries(static_libprimesieve Threads::Threads)
+ target_link_libraries(static_libprimesieve Threads::Threads atomic)

However I cannot test if this really fixes the issue. I found one other open source project that fixed the same issue this way.

Ok. Can you make conditional/optional in CMakeLists.txt ?
And then release a micro version in such a way I can easily repack and test ?

Ok. Can you make conditional/optional in CMakeLists.txt ?
And then release a micro version in such a way I can easily repack and test ?

Yes, but it will take a few hours because I need to test this myself a little (I am worried libatomic might not exist on some systems (e.g. Windows) and CMakeLists.txt must handle this correctly).

I understand. Take you time. It would be nice if you can test it on Debian derived box.
For Debian, I will trigger it only where it is required.

I have now merged the fix for the libatomic linker error. I have tested the fix on Debian, Ubuntu, Red Hat, macOS and Windows. CMakeLists.txt now correctly finds libatomic and adds it as a link dependency to libprimesieve(but only if this is really needed).
I am not 100% sure if it works though as I don't have access to any of the Debian architectures where the primesieve-6.2 build failed.
I have released primesieve-6.3-rc1 for testing.

Thanks for your prompt fix. I will have a look on next Friday.

I have just tested primesieve-6.3-rc1 on an armel box: the built and the tests work.
When do you plan to release the version 6.3 ?

If v6.3-rc1 works for you I will release primesieve-6.3 tomorrow, v6.3 will
contain no code changes compared to v6.3-rc1.
Regards,
Kim
On Nov 17, 2017 9:36 PM, "Jérôme Benoit"<EMAIL_ADDRESS>wrote:

I have just tested primesieve-6.3-rc1 on an armel box: the built and the
tests work.
When do you plan to release the version 6.3 ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kimwalisch/primesieve/issues/45#issuecomment-345358700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcMW8VvEvwRMcFe1sUuCJXt8WBoLuMpks5s3e45gaJpZM4Qav8w
.

Hi Jérôme,
I have released primesieve-6.3 on GitHub:
https://github.com/kimwalisch/primesieve/releases
Kim
On Fri, Nov 17, 2017 at 10:31 PM, Kim Walisch<EMAIL_ADDRESS>wrote:

If v6.3-rc1 works for you I will release primesieve-6.3 tomorrow, v6.3
will contain no code changes compared to v6.3-rc1.
Regards,
Kim
On Nov 17, 2017 9:36 PM, "Jérôme Benoit"<EMAIL_ADDRESS>wrote:

I have just tested primesieve-6.3-rc1 on an armel box: the built and the
tests work.
When do you plan to release the version 6.3 ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kimwalisch/primesieve/issues/45#issuecomment-345358700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcMW8VvEvwRMcFe1sUuCJXt8WBoLuMpks5s3e45gaJpZM4Qav8w
.

So I have begun to package. It appears that the check in CMakeLists.txt see whether or not the atomic material comes from the compiler itself or from the adhoc libatomic library. I will dig the issue next week-end. Sorry for the delay.

It appears that the check in CMakeLists.txt see whether or not the atomic
material comes from the compiler itself or from the adhoc libatomic library.

Yes, while searching for the error using Google I found that the LLVM
compiler had the same issue: https://reviews.llvm.org/D10453 (also bug
explained here:
https://answers.launchpad.net/gcc-arm-embedded/+question/616213). And as
LLVM also uses cmake as its build system I cloud see how they fixed the
issue and implement something similar. As far as I understand this issue
exists on CPU architectures that do not have the required atomic
instructions to support C++11 atomics, in this case using C++11 atomics
requires linking against libatomic. Hence in CMakeLists.txt I first check
whether C++11 atomic compiles without libatomic, if it does not compile I
add libtoamic to the linker flags.
Kim
On Sat, Nov 18, 2017 at 4:06 PM, Jérôme Benoit<EMAIL_ADDRESS>wrote:

So I have begun to package. It appears that the check in CMakeLists.txt
see whether or not the atomic material comes from the compiler itself or
from the adhoc libatomic library. I will dig the issue next week-end. Sorry
for the delay.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kimwalisch/primesieve/issues/45#issuecomment-345448009,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcMW6vpVcbuA06y192Ao34ZLWoKL5UFks5s3vJ2gaJpZM4Qav8w
.

Yes but as libatomic is installed and it is meant to be transparent at build time, the test is lure.
Having said that, I have noticed that some tests are lasting extremely long on armel. So, you might consider to avoid atomic feature when it is not engraved in the CPU.

Having said that, I have noticed that some tests are lasting extremely long on armel.

How how long did it take to complete primesieve's test suite on armel?
What are the 2 slowest tests on armel?

My goal with primesieve's test suite has been that it should complete in about 30 seconds on a recent x86 CPU. Unfortunately this also means that if the test suite is run on a very old or low power embedded CPU running the test suite might take much longer. E.g. For the hppa CPU (which I guess is at least 15 years old) primesieve-6.2 took 2430 seconds to complete its test suite.
Looking at the build time and test time of the gmp C multiprecision library for the hppa CPU I see that it even took 1h 17m. So other libraries are having the same issue.
This is not an easy fix because I cannot simply reduce the tests by a factor of 100 just to reduce the test suite runtime on some ancient CPUs...

So, you might consider to avoid atomic feature when it is not engraved in the CPU.

I am quite sure that the long test run times are not related to the use of atomic instructions. Atomics are obviously only used when using multi-threading but e.g. for the hppa architecture many long running tests: generate_primes2, next_prime2, prev_prime1, generate_n_primes1 are single-threaded tests. Also atomics are used extremely sparsely in primesieve so that even if the CPU does not support hardware atomics this will not affect primesieve's run-time.

I will record the time next time. BTW, it can be an issue for automates at building time; we will see.
Otherwise, do you have any idea how to harden the test ?

do you have any idea how to harden the test?

Sorry, but I don't understand what you mean?

The current test does not work. If libatomic is installed, the test set have_atomic to true.

My understanding is that have_atomic is set to true only if the compiler is able to compile std::atomic without linking against libatomic. In this case libatomic is not needed.
If however have_atomic is false than we need to link against libatomic.
I have tested this on i386 and x64 and there it worked fine.

it does not work on armel .

Ok, can you print the cmake (and make) output here so that I can see what went wrong?

it does not work on armel.

I have been able to reproduce the bug on my old 32-bit PowerPC Mac. The issue is that these old CPU architectures do have 32-bit atomic instructions but not 64-bit atomic instructions. Hence my have_atomic test which used std::atomic<int> passed fine but then primesieve failed to compile because it uses std::atomic<int64_t>.
Hence I have now modified the test in CMakeLists.txt to use std::atomic<int64_t> and now the test correctly fails on my 32-bit PowerPC Mac.
check_cxx_source_compiles("
    #include <atomic>
    #include <stdint.h>
    int main() {
        std::atomic<int64_t> x;
        x = 1;
        x--;
        return (int) x;
    }"
    have_atomic)

Can you please retest using the latest code from the master branch?

Sorry for my late reply. It works on armel. I am on way to test on other architectures.

Sorry for my late reply. It works on armel. I am on way to test on other architectures.

Thanks, once you have tested it successfully on other architectures I will bump the version number again and release 6.4. I misunderstood you last week, I thought it was working without any issues that's why I released 6.3 last week, otherwise I would have fixed this issue first before releasing version 6.3.

The suggested test works at least on the mipsel, mips, and armel architectures (which architect officially supported by Debian).
The time for the test are:
armel: 1175.13 s
mips: 707.6 s
mipsel: 417.96 s
Concerning realising, you did misunderstand my claim, but I rather overestimated my own test; I am sorry for that.
Given that, I do not think it is necessary to make a new release: let apply a patch and see if it works well on all architectures (officially or not supported by Debian).

Given that, I do not think it is necessary to make a new release: let apply a patch and see if it works well on all architectures (officially or not supported by Debian).

OK, I like this solution better.

It rocks ! In about 5 days, it should reach testing. Thank you very much for your patience.


axios.post() requests do not send headers and payload as expected

The Axios .post() function is not working as I expected it to.
Sitting on the serverside Java debugger I have grabbed the MimeHeader's sent to the server by Axios and also by (ubuntu) cURL.
The java server-side class is org.apache.catalina.connector.CoyoteAdapter.
The debugger is in the service(Request, Response) method (version tomcat-embed-core-8.5.6.jar, line: 308).
I issued 3 'login' requests and compared the results.

cURL, which works as expected
AXIOS, using textual field names in the .post call
AXIOS, using named fields in the .post call
Neither of the 2 Axios calls sends the request as I expect it should do.

Here is the CURL:
curl -X POST -vu webui:webuisecret http://localhost:8081/merchant/oauth/token -k -H "Accept: application/json" -d "password=merchant1&username=merchant1&grant_type=password&scope=read%20write&client_secret=webuisecret&client_id=webui"
and here are captured the

=== MimeHeaders ===
host = localhost:8081
authorization = Basic d2VidWk6d2VidWlzZWNyZXQ=
user-agent = curl/7.47.0
accept = application/json
content-length = 118
content-type = application/x-www-form-urlencoded

All good so far.
[AXIOS - TEXT NAMES]
Then I sent the request with this Axios JS code:

 onLogin( credentials ) {
    axios.post(
            Config.appUrl + 'oauth/token', {
            headers: {
                'accept': 'application/json',
                'accept-language': 'en_US',
                'content-type': 'application/x-www-form-urlencoded'
            }, auth: {
                username: Config.clientId,
                password: Config.clientSecret
            }, body: {
                'password': credentials.password,
                'username': credentials.username,
                'grant_type': 'password',
                'scope': 'read write',
                'client_secret': Config.clientSecret,
                'client_id': Config.clientId
            }
        }, Config )

The server responds with an error : "provider.endpoint.TokenEndpoint  : Handling error: InvalidRequestException, Missing grant type".
From this, it sounds like the body is not being properly submitted (hence deciding to look at the headers and payload on the server).
Here is what we see on the server:

=== MimeHeaders ===
host = localhost:8081
user-agent = Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
accept = application/json, text/plain, /
accept-language = en-US,en;q=0.5
accept-encoding = gzip, deflate
content-type = application/json;charset=utf-8
referer = http://localhost:8081/merchant/
content-length = 321
cookie = JSESSIONID=69AA1724151AAE81659FDEC49354AA85
authorization = Basic d2VidWk6d2VidWlzZWNyZXQ=
connection = keep-alive

The requested Basic Auth does seem to be successfully applied with Axios.
However:

Headers are not honoured (content-type, for example, should be application/x-www-form-urlencoded, not application/json;charset=utf-8)
Content seems to be of completely different length

[AXIOS - FIELD NAMES]
And, I get the same result if I use the field name equivalents for the headers{accept} and body {*} segments:

 onLogin( credentials ) {
    axios.post(
        Config.appUrl + 'oauth/token', {
            headers: {
                accept: 'application/json',
                'accept-language': 'en_US',
                'content-type': 'application/x-www-form-urlencoded'
            }, auth: {
                username: Config.clientId,
                password: Config.clientSecret
            }, body: {
                password: credentials.password,
                username: credentials.username,
                grant_type: 'password',
                scope: 'read write',
                client_secret: Config.clientSecret,
                client_id: Config.clientId
            }
        }, Config )

Results in:

=== MimeHeaders ===
host = localhost:8081
user-agent = Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
accept = application/json, text/plain, /
accept-language = en-US,en;q=0.5
accept-encoding = gzip, deflate
content-type = application/json;charset=utf-8
referer = http://localhost:8081/merchant/
content-length = 321
cookie = JSESSIONID=69AA1724151AAE81659FDEC49354AA85
authorization = Basic d2VidWk6d2VidWlzZWNyZXQ=
connection = keep-alive

Here is my package.json content:

"devDependencies": {
"babel-core": "^6.21.0",
"babel-loader": "^6.2.10",
"babel-preset-es2015": "^6.18.0",
"babel-preset-react": "^6.16.0",
"eslint": "^3.13.1",
"eslint-config-airbnb": "^14.0.0",
"eslint-plugin-import": "^2.2.0",
"eslint-plugin-jsx-a11y": "^3.0.2",
"eslint-plugin-react": "^6.9.0",
"file-loader": "^0.9.0",
"react-hot-loader": "^1.3.1",
"react-router": "^3.0.2",
"webpack": "^1.14.0",
"webpack-dev-server": "^1.16.2"
},
"dependencies": {
"alt": "^0.17.4",
"axios": "^0.7.0",
"history": "^1.12.5",
"jsuri": "^1.3.1",
"rest": "^1.3.1",
"react-mixin": "^3.0.1",
"react": "^15.4.2",
"react-dom": "^15.4.2"
}

Can somebody please help me to identify what is wrong with my .post() request ?

You aren't configuring the request correctly. The body option doesn't exist in axios. You should use data instead. And the first option for post is the data itself, not the axios config.
You can see an example request with content type application/x-www-form-urlencoded in the README: https://github.com/mzabriskie/axios#using-applicationx-www-form-urlencoded-format

SignIn = () => {
    console.log('login clicked')
    let data = JSON.stringify({
        password: this.state.password,
        username: this.state.email
    })

    axios.post('url', data, {
        headers: {
            'Content-Type': 'application/json',
        }
    }
    )
}

Hi guys, I opened a ticket that I believe that it might be related to this issue.
#1149
Thank you.

I discovered that for this particular scenario (calling oauth/token endpoint) axios seems to be case sensitive for the content-type header key. 'Content-Type' works fine but 'content-type' results in a missing grant-type. I am running 0.18.0.  Right now I am slammed with work - otherwise I would step into the debugger to see what is going on. Maybe the folks who are very knowledgeable with the internals of axios can either confirm or reject my statement.
I do want to state that I use axios extensively in my work - kudos the the author.

I am using axios like so:
 axios
      .post(`${serviceRoot}/sendMail`, data)
      .then(function(response) {
        console.log(response)
        resolve(response)
      })

but there is no payload:

The service works fine when posting with postman like tool:

It looks like you only have two points left to make it work :
one : the http method should be set to POST instead of GET since you want to send something.
two : you can then add the http header (like what you did with the authorization header) Content-Type: 'application/json`
On the back-end don't forget to use some kind of body parser utility package like this one : body-parser and set it up with your app.
I suppose your server is using express, here is how you will do it with express :
const express = require('express');
const app = express();
const bodyParser = require('body-parser')
const jsonParser = bodyParser.json();

app.use(jsonParser); // use it globally
app.get('your_route', jsonParser, otherMiddleware, (req, res) => ...); // use it for specific routes

/* ... rest of your code */


Plant Relocator fails to cut trees properly

Note: I have Fast Leaves Decay

1.11.2 right?

Yes, sorry.


Error on enroll,   wait for default project creation

On enroll
Project created. Waiting until it's operative.........thread 'tokio-runtime-worker' panicked at 'Project should have identity set', implementations/rust/ockam/ockam_command/src/enroll/auth0.rs:327:14
https://github.com/build-trust/ockam/blob/a5ac07e3c6185346eee1c85df64d2cf166cee871/implementations/rust/ockam/ockam_command/src/enroll/auth0.rs#L327
(it is waiting for the project' route to be there,  but the default_project is not updated)

Fixed here: https://github.com/build-trust/ockam/pull/3300


Undocumented Flag Handling in SIDC Symbols

@dceejay
Before submitting a new PR, I wanted to clarify a behavior I recently encountered:
After spending some time trying to understand why flag-xx was being appended to my SIDC symbols, I discovered the following code snippet:
javascript Copy code if (data.SIDC.length > 12) {     var cc = data.SIDC.substr(12, 2).toLowerCase();     opts.country = cc.toUpperCase();     opts.staffComments = emojify(":flag-" + cc + ":") + " " + (opts?.staffComments || "");     data.flag = emojify(":flag-" + cc + ":"); }
This code assumes that the SIDC string has an additional flag identifier beyond the standard length. However, this behavior is undocumented and not compliant with milsymbol.js, which supports MIL-STD-2525D (and possibly assumes compliance with MIL-STD-2525C). Introducing this undocumented feature creates inconsistencies.
Furthermore, since the payload.flag option already exists, why not use it directly to set the flag instead of deriving it from the SIDC string in this ad hoc manner?
Additionally, as per the emoji list used (emojilist), the emojify(":flag-xx:") will only return the same two characters instead of an actual flag emoji. Therefore, the benefit of constructing an emoji string in this way is unclear. If it doesn't yield the intended flag symbol, why introduce this complexity?
Suggested Actions:
Either remove this undocumented SIDC flag handling or document it explicitly, ensuring it aligns with the MIL-STD-2525D standard.
Consider leveraging the existing payload.flag for this functionality instead of adding assumptions based on SIDC strings.
Simplify or clarify the emoji construction if it doesn't achieve the desired visual representation.
Would appreciate any feedback or thoughts on how to address this discrepancy.
B.T.W - Is there any way for less formal contributors discussion?

The 2525C standard defines a 15 char string  of which
"g. Positions 13 and 14, country code, identifies the country with which a symbol is associated. Country code identifiers are listed in ISO 3166-1." - so it could be there - it's not an assumption/ad-hoc.
The fact that most uses only use 12 chars (eg milsymbol.js) - is fine - but hey - if the info is there occasionally we can try to show it.
Milsymbol.js also has optional fields for other things like targetNumber but doesn't display that either...
msg.payload.flag should create a flag symbol in the popup info panel if valid - which is best we can do for non-SIDC icons
Email works if you prefer -  dceejay (A-T) gmail.com

Closed by fixes.


Determine experiment #3 hypothesis

Is your feature request related to a problem? Please describe.
Experiment 3 needs a hypothesis to discover the limitations of JanGAN. I.e. how few letters can we give it before the accuracy begins to break down?
Describe the solution you'd like
A group discussion and/or brainstorm

It'll probably be sensible to send a hypothesis proposal to Giorgio when done.


Fix quirk_applied check only working for v1 quirks

https://github.com/zigpy/zigpy/pull/1450 must have broken this check to no longer be True for v2 quirks, since CustomDeviceV2 no longer extends CustomDevice, only BaseCustomDevice.  This PR checks for the base class now.
(Noticed this whilst working on https://github.com/zigpy/zha/pull/231)

I believe this also needs some fixes in zigpy.

I believe this also needs some fixes in zigpy.

What is needed there?

Separate from this PR, but:

https://github.com/zigpy/zigpy/pull/1485


Broken arrows

I am going to use this nice Gantt for a solution, and I have a question: why so many broken lines (see screenshot below)? Wouldn't it be easier to just go straight?

I was thinking maybe something like this:

Thanks!

Hi @PathToSharePoint,
I will check how it looks like.

Arrow visual fix has been published with new release

I checked out the live demo, looks great!


Planner 1580 add frontend service

Add front end with the ability to:

Load submitted problems and view best solutions
Add new problems (tenants)
Switch between different tenants and view their best solutions

To run the ui:

run spring boot app from the root directory:
-- ./mvnw spring-boot:run
run frontend app in a different terminal:
-- cd spring-boot-task-assigning-frontend
-- npm start

Sorry for holding the review off; I might be able to get to it tomorrow or early next week.

@rsynek thanks for the review! There are no plans currently for an optaweb-task-assignment, and the UI is just for testing and experimental purposes for using SolverManager, that's why there are no tests.


BUG: Poor user experience if the user chooses “don’t ask me again” when denying permission or locations - DHM-S-1-7

Behaviour if user denies permissions on location is much better than in V0.5.12, but still not perfect.
[DHM-S1-7] Poor user experience if the user chooses “don’t ask me again” when denying permission – user just gets repeated notifications that the app needs to access location info, but gets no guidance how to get out of this situation (they need to go deep into the settings menu & explicitly adjust the permissions).
Pretty minor issue, and not obvious how to do better.
However I can see a user misreading the location access request, and then getting into this state & not knowing how to get out - so worth considering if we want to give the best possible UX for all possible users.

Can we check on each start and then warn the user if it is still unset?

This is still an issue in the released 1.0 app, but I do not feel it is a critical issue.
I expect the android and iOS flow/permissions (and solutions) may be slightly different.   [I don't even know if there is a way for us to detect that the user isn't pushing the "deny" button, but instead the OS is auto-denying the permission request.]
I don't necessarily want to say we won't fix this, but this could be a thorny issue that can't be fixed, and it only rears up if the user both denies location permissions, AND clicks the "do not re-ask" when doing so.

Closing this issue out as we have taken it into consideration and documented the feedback on this page in Jira.


Component: Filter

New component request:
Filter group
consisting of a sub components, eg. filter accordion and different filter types

Handled in another Issue: https://github.com/Infineon/infineon-design-system-stencil/issues/1209


[RFC] Require "scalar" variables to be 0-dim

The current definition in Variable.backward of a "scalar" variable is an array containing 1 element.  This may cause unexpected behavior that only occurs when batch_size=1.  The PR proposes to fix the definition to being a 0-dimensional array.

Jenkins, test this please

All tests passed. LGTM


android-studio: 2<IP_ADDRESS> -> 2<IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for android-studio is: Official IDE for Android (stable channel)
meta.homepage for android-studio is: https://developer.android.com/studio/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2<IP_ADDRESS> with grep in /nix/store/s8zm2mssip2slvilsb0pzax1q95q2jy8-android-studio-stable-2<IP_ADDRESS>
found 2<IP_ADDRESS> in filename of file in /nix/store/s8zm2mssip2slvilsb0pzax1q95q2jy8-android-studio-stable-2<IP_ADDRESS>

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

android-studio
androidStudioPackages.stable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s8zm2mssip2slvilsb0pzax1q95q2jy8-android-studio-stable-2<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/d780bd9c7079d7301cde744ceefe32953f33235c#android-studio

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s8zm2mssip2slvilsb0pzax1q95q2jy8-android-studio-stable-2<IP_ADDRESS>
ls -la /nix/store/s8zm2mssip2slvilsb0pzax1q95q2jy8-android-studio-stable-2<IP_ADDRESS>/bin

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

1 package built:

android-studio

Maintainer pings
cc @alapshin @johnrtitor @numinit for testing.

Result of nixpkgs-review pr 328548 run on x86_64-linux 1

1 package built:

android-studio (androidStudioPackages.stable)


Automatically add .pyi files to manifest

When using the setuptools.grpc tools, the user needs to specify recursive-include py *.pyi in the MANIFEST.in file, otherwise setuptools[scm] doesn't seem to realize that the files should be included (not sure why it does realize the .py files should).
It is supposed to be a way to include them automatically if the sub-command build_py reports the new *.pyi files:

https://setuptools.pypa.io/en/latest/userguide/extension.html#supporting-sdists-and-editable-installs-in-build-sub-commands

This is probably also needed to support editable installs.

This is much less pressing now because we are generating a MANIFEST.in with the cookiecutter templates.


Trailing back-slash in String argument value leads to incorrect parsing

Hi,
as subject.
Given a -p String parameter:
ReadText.Demo.exe head -p "c:\trailing - back - slash"
It gets parsed as:
c:\trailing - back - slash"
The trailing back-slash causes the value of the parameter to hold the double-quote value, while the back-slash is lost.
This seems to happen only when the traling back-slash is immediately followed by the double-quote.
Thanks

That's the magic of .Net.

If a double quotation mark follows an odd number of backslashes, including just one, each preceding pair is replaced with one backslash and the remaining backslash is removed; however, in this case the double quotation mark is not removed

The quick fix: put a double-slash at the end of your path instead of a single one. Since .Net does some pre-processing of arguments to get your string[] args parameter to Main(), CommandLine can't do anything about it unless it performs the parsing on the full string.
That has some trade-offs since System.Environment.CommandLine isn't as obvious as passing in an argument array (which most C# programmers are familiar with)

It could be worth considering parsing System.Environment.CommandLine then, which preserves the correct arguments.

I feel like some documentation regarding this would be beneficial... basically that the recommended approach is to utilize the System.Environment.CommandLine instead of string[] args from Main.

@ericnewton76 Env.CommandLine is not a drop-in replacement for args, since it is just a single string (similar to ProcessStartInfo.Arguments). Splitting the line on spaces would work except when there is quoted text, in which case we'd have to implement the parsing logic within the parser itself (I don't believe there is an equivalent to Python's shlex.split in .Net).
This would probably take the form of a new overload for ParseArguments that accepts a single string.

It goes down to the Windows API, CommandLineToArgvW. There's a lot of material about this weird behavior, like https://blogs.msdn.microsoft.com/oldnewthing/20100917-00/?p=12833/
Funniy thing, it seems that DOS bat files behave differently. Wondering if they use a different API or if cmd reimplemented command line parsing.
i.e.
@echo %1
@echo %2
sample.cmd "this works\fine" "hello"
"this works\fine"
"hello"

Yep, one argument against it is that the current behavior is standard, if quirky. Those familiar with Windows command line who know about escaping slashes may expect your tool to behave the same way.

Right, that's a valid point. I tried other command line libraries and they all rely on the same behavior. Probably we can live with it :)


turning an object into an array

Description
Good afternoon. I can make mistakes in actions. But when I do initialization through curly brackets,  I get an array instead of the expected object.
Reproduction steps
For examle
using json = nlohmann::json;

int main()
{
  std::string str = "{ \"uuu\": 123 }";
  json j = json::parse(str);
  json a {  j  }; // a is array of objects ["{ \"uuu\": 123 }"]
  json b {  a  }; // b is array of array of objects [["{ \"uuu\": 123 }"]]
}

Expected vs. actual results
I would like to see the same object
Minimal code example
No response
Error messages
No response
Compiler and operating system
g++
Library version
last
Validation

[ ] The bug also occurs if the latest version from the develop branch is used.
[ ] I can successfully compile and run the unit tests.

Duplicate if #2583


WPF MVVM, after switching from the login-view to the main-view only the login-elements can be found.

My WPF MVVM application shows a login-view after startup. After entering a password, you can click the login button. If logging in is successful, the main-view will be shown. With WinAppDriver I'm able to:

Start the application
Find the password control
Enter a password
Find the login-button
Click the login-button.

At this point the main-view is shown. The problem is this: when I search for elements that are on this main-view I can not find them. The only elements I can find are elelements that are on the login-view.

Are you able to find the elements with inspect.exe

Yes I am. I use the ClassName to find the elements. With the command session.FindElements(By.ClassName("Button")) I only find the buttons of the login-view. With inspect.exe I can find the two buttons on the main-view, furthermore inspect.exe shows that they do have ClassName=Button.

Try using desktop session.

Using a desktop session works. I'll try to re-write the tests. Thanks.

Great, You are welcome.


Menu

Menu page - The previous menus created are not being formated correctly(Showing up one after another instead on in a serial order).

Resolved this issue!


feat(tql): add initial implementation for cte support

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Support CTE queries for TQL
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb/issues/1915

@etolbakov  Hi, still working on this PR?

hello, sorry I've stopped working on that

hello, sorry I've stopped working on that

All right. I closed this PR. Feel free to open it again when you want. Thanks.


Fix shutdown for continuous build tests

Now the continuous build tests don't use the daemon, so normally the daemon process does not exit. So it makes no sense on waiting for the exit.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Cleanup naming of methods and variables

This PR goes some way to cleaning up the plug-in code, renaming "NAM" methods/variables to "Model" and a few other things. see #267

PR updated

how about it @sdatkinson? I think it will make the code a lot nicer. :-)
will keep on having to redo this PR if it sits around whilst other changes get merged


Easy way to copy URLs from chat

I don't seem to be able to copy a URL from a chat session easily.
As a Mac user, I am used to being able to control-click (or something - my muscle memory won't reveal to my conscious self with confidence which gesture exactly is the one which usually works) to copy the URL under the cursor to the clipboard.
Unfortunately, this doesn't seem to work in the Keybase client - when I control-click on a URL, I get a "copy" tooltip which however only copies the text exactly under the cursor. To capture a URL, I have to select it by painting over it, which is somewhat tedious and error-prone especially with small fonts.
I realize this request may impose cross-platform challenges if the conventional gestures differ between platforms.

This seems to be a duplicate of #10569.

Definitely the same conclusions, though that one is about Linux.

@tripleee Does this Copy URL command not appear in the context menu for you? I've a friend running Keybase in macOS and this appears when he "right-clicks" on a URL.


[Enhancement] Action label for "Show Message" should be "Show Alert"

Summary
on the property pane action, the label says "Show Message" where as the actual function behind it is "showAlert()"
Motivation
I think this has to be consistent to reduce cognitive load for the user.
Additional Context

Hi, can I take on this issue?

@MartinTuroci Thanks for showing interest. Unfortunately, we are not yet decided to go with this change.
Please do check other issues which are tagged as Hacktoberfest. We are happy to assign those to you.

We are thinking of changing the function showAlert() to showMessage() since the alert in the browser is having a different UI. The challenge in that would be to write migrations so that the existing applications wouldn't be breaking. We won't be taking that path since a lot of users are using showAlert in their production workflows.
Another approach is to introduce whole new function named showMessage() and deprecate the function showAlert(). But, this deprecation infrastructure is not in place yet.
So, we will work on this issue only when a generic solution to deprecation and communication of the deprecation are in place.

This is a one line change, will add this to my PR


Refresh in ER Diagram reverts all changes without asking

System information:

Operating system (distribution) and version Win10
DBeaver version 21.1.0

Steps to reproduce, if exist:

Make some changes in ER diagram (Drag new tables, change their positioning, create/delete connections)
Change view style in context menu or press F5

Expected: Pop-up window appears asking if you want to revert changes.
Actual: All changes are reverted without asking.

Fixed.

Verified


Fix typo in moduleNameMapper docs

Sorry for this, it was left from my previous PR. Thank you!

Codecov Report

Merging #9501 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #9501   +/-   ##
======================================
  Coverage      65%     65%
======================================
  Files         283     283
  Lines       12144   12144
  Branches     3008    3008
======================================
  Hits         7894    7894
  Misses       3607    3607
  Partials      643     643

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 fdd700f...9ab2e0a. Read the comment docs.


Bad certificate error

Kubernetes Version: 1.8.4
I'm attempting to give this a try in a testing cluster I've spun up with kops 1.8.0. I think I'm quite close, but it looks like I've got a certificate problem somewhere. When attempting to do the following, I get a few errors:
kubectl --kubeconfig=/path/to/my/kubeconfig --token="$(heptio-authenticator-aws token -i mycluster.local)" get nodes
The first is immediate on my local workstation:
error: You must be logged in to the server (Unauthorized)
The second is from the container itself:
time="2017-12-05T20:14:47Z" level=info msg="http: TLS handshake error from <IP_ADDRESS>:41980: remote error: tls: bad certificate" http=error
I'm assuming I have the wrong certificate configured somewhere, but from the docs it is not clear where that might be. Does the authenticator need to use the cluster certificates (in this case generated by kops) or are the certs it generates on its own correct?

Any Update on the issue?
We too are facing the same problem only thing that is different for us is that after all the kops rolling update if we restart the docker container named

I have seen that after doing kops rolling update restarting the docker pod 'k8s_kube-apiserver-*' in Master worked for me rather than kubelet service. And we could automate this by adding a file asset

content: |
sudo docker ps | grep k8s_kube-apiserver_kube-apiserver | awk {'print $1'} | xargs sudo docker restart
name: restart-api.sh
path: /srv/kubernetes/restart-api.sh
roles:
- Master

And then executing it. Dont know if its right thing to do or not

@KaustubhKhati @Raffo @baniol I'm trying to better understand the issue you are running into. Are you saying that when using kops 1.8 and adding the webhook if the backend that it's suppose to connect to isn't alive it fails?
Or how can I best reproduce this?

Also, did anyone have a chance to run through #45 to verify if that solved their problems?

@christopherhein I try to explain what happen to me:

I create an entirely new kops cluster (kops 1.9 with kubernetes 1.9.3, private+public subnets, cni mode and weave, just to add more info about the setup) with the configuration exactly as explained in https://github.com/heptio/authenticator/pull/45
I wait for the cluster to be healthy
I apply the daemonset + configmap for the authenticator
I get unauthorized. I see the error like in the first message: time="2017-12-05T20:14:47Z" level=info msg="http: TLS handshake error from <IP_ADDRESS>:41980: remote error: tls: bad certificate" http=error
To solve it, I ssh into the master node, do a docker stop of the apiserver container and do a systemctl restart kubelet.
From there on everything works.

I haven't looked too much myself in trying to understand the full root cause of the issue, but it is definitely more than just annoying. Strange enough, I didn't have this issue with the a heptio quickstarter cluster.

I'm doing the same equivalent steps, nothing significantly different:
My hook:
hooks:
  - name: kops-hook-authenticator-config.service
    before:
      - kubelet.service
    roles: [Master]
    manifest: |
      [Unit]
      Description=Download Heptio AWS Authenticator configs from S3
      [Service]
      Type=oneshot
      ExecStart=/bin/mkdir -p /srv/kubernetes/heptio-authenticator-aws
      ExecStart=/usr/bin/docker run --net=host --rm -v /srv/kubernetes/heptio-authenticator-aws:/srv/kubernetes/heptio-authenticator-aws quay.io/coreos/awscli@sha256:7b893bfb22ac582587798b011024f40871cd7424b9026595fd99c2b69492791d aws s3 cp --recursive s3://bucket/cluster/addons/authenticator /srv/kubernetes/heptio-authenticator-aws/

I will perform additional tests after the weekend to understand better the interactions.

@Raffo any update?

@Raffo @christopherhein  In my case i am applying the heptio-authenticator-daemonset  first and copying the cert files to S3 bucket after that I am doing KOPS edit cluster followed by Rolling Update. This flow works for me without giving the bad certificate issue.

@KaustubhKhati I think that works because you are essentially restarting the API server when you do the rolling update, right?

@Raffo Yes

Ok, but this is also different from the previously provided instructions that do not have a rolling update listed.

Cool, so we should be covered, agreed? can we close this?

@christopherhein Well, in the list of commands in this issue, you have kops update, AFAIK this does not restart the API server node, which is saying to me that we didn't find the mistery :-D I'm still okay to close this and re-open it if I find a more reliable way to verify it, unfortunately I have very little time to invest to test this.

The cohesive list to get the authenticator working for a kops cluster (or any cluster) should go as follows - https://github.com/heptio/authenticator#kops-usage which includes #3 that says "If the cluster already exists, roll the cluster with kops rolling-update cluster ${CLUSTER_NAME} in order to recreate the master nodes."

I've gone through all the kops steps, including the rolling update, and I'm still having this issue.

Now that kops has this in as a feature this should be an automated config. Closing. Please open if you are still running into issues.
/close


update proxy of master to upgrade-near-8.2

What problem does this PR solve?
Issue Number: ref #4982, close https://github.com/pingcap/tiflash/issues/9147
Problem Summary:
update proxy to upgrade-near-8.2
Proxy PR:
Including:\nSubmodule contrib/tiflash-proxy 7dc50b4eb0..0d76d66782:

adapt to upgrade-near-8.2
Merge remote-tracking branch 'tikv/master' into upgrade-near-8.2
Add approvers (#373)
Strengthen configuration change approval (#371)
Add log for current ReadIndex mechanism (#370)
Add some tests for replica read (#369)

What is changed and how it works?

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/retest

/unhold

/test


add vignette

as discussed, let's move it outside of MASH folder and remove mash_pipeline.ipynb @grennfp


Handle Safari's private mode

When using localStorage / sessionStorage on Safari (iOS or OS X) running in private mode the following error is thrown:
QuotaExceededError: Dom exception 22: An attempt was made to add something to storage that exceeded the quota

This happens because the quota is set to 0.
See: http://stackoverflow.com/questions/21159301/quotaexceedederror-dom-exception-22-an-attempt-was-made-to-add-something-to-st
I think we should fall back to storing the session in memory?
Maybe have an easy way to communicate to the package user that this happened?

Using memory won't work on reload, that's why we use storage.
Got same problem in a different project. To avoid the bug we will need to put a try/catch around the use of storage.
The thing is if we cannot write on the storage, users will have to relog on every refresh.
(It's call private mode for a reason after all.)
Highly recommend SPA.
If you know an alternative (without using cookies) to keep the session alive let me know.
In the meantime I will make sure it doesn't crash at least.

(Sending a msg to Safari team about this issue would help too btw)

I totally understand why we normally use localStorage, but now my app breaks when a user forgets about this. By having a fallback I can display a notification and leave the choice to my user.
SPA? Single page app?
I'm afraid I don't know of a better solution, even sessionStorage doesn't work, which would have been a better fallback.
I can't imagine the Safari team doesn't know, seeing that Stack overflow topic.
I'm not sure about the error. It really breaks the functionality of superlogin-client? In this case we would simply be clarifying an existing issue. Getting a clear error is probably also easier for the developer, otherwise its something he/she has to manually check for and write a clear message for. Then again, if no library does this it does sound like a bad idea.

Been very long time the issue exist on Safari. Hope they will fix it soon.
But more people complaining to them the better.
At least for your project to avoid getting stuck you could add the following in your code:
if (typeof localStorage === 'object') {
    try {
        localStorage.setItem('localStorageTest', 'test');
        localStorage.removeItem('localStorageTest');
    } catch (e) {
        Storage.prototype.setItem = function() {};
    }
}

It should avoid any crash from localStorage (within superlogin-client included) and your app should start.
But as I mention, on reload of the page we will have no way to know if there was a previous session active.
This is a really specific case though (Safari + Private Mode), so let's make sure it doesn't break first. Then see if there is a solution to keep the session alive.

(I indent to pick this up, but I'm currently still swamped by other higher priority issues I have to fix first)

I made a memory storage for now. At least it won't crash.
See v0.5.1

Thanks for picking this up!
The relevant commit: https://github.com/micky2be/superlogin-client/commit/4084e8923bb0a47c87723cb14f2b59c91ac8c2b6#diff-1fdf421c05c1140f6d71444ea2b27638R57
I tested this and found a small issue where I created a pull request for.

damn, I need to test my code correctly
Thanks

With that latest release this issue seems fixed.


Network policy blocks traffic that should be allowed

On a kind cluster with calico install, using this network policy, I expect pod x/a to be able to reach pod y/b over any port on TCP.  x/a is able to reach y/b on port 80 over TCP. However, x/a is not able to reach y/b on ports over TCP (79, 81, 82, etc.).
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-all-80
  namespace: x
spec:
  egress:
  - ports:
    - {}
    - port: 80
    to:
    - namespaceSelector:
        matchLabels:
          ns: "y"
      podSelector:
        matchLabels:
          pod: b
  - ports:
    - port: 53
      protocol: UDP
  podSelector:
    matchLabels:
      pod: a
  policyTypes:
  - Egress

I also see analogous behavior with the ingress analogue network policy.
  Going down the leftmost column is the Source pod, going across the topmost row is the Destination pod.
+--------+-----+-----+-----+-----+
| TCP/79 | X/A | X/B | Y/A | Y/B |
| TCP/80 |     |     |     |     |
| TCP/81 |     |     |     |     |
| TCP/82 |     |     |     |     |
+--------+-----+-----+-----+-----+
| x/a    | X   | X   | X   | .   |
|        | X   | X   | X   | .   |
|        | X   | X   | X   | .   |
|        | X   | X   | X   | .   |
+--------+-----+-----+-----+-----+
| x/b    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+
| y/a    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+
| y/b    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+

Current Behavior

Measured connectivity (note the x/a->y/b entries):
+--------+-----+-----+-----+-----+
| TCP/79 | X/A | X/B | Y/A | Y/B |
| TCP/80 |     |     |     |     |
| TCP/81 |     |     |     |     |
| TCP/82 |     |     |     |     |
+--------+-----+-----+-----+-----+
| x/a    | X   | X   | X   | X   |
|        | X   | X   | X   | .   |
|        | X   | X   | X   | X   |
|        | X   | X   | X   | X   |
+--------+-----+-----+-----+-----+
| x/b    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+
| y/a    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+
| y/b    | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
|        | .   | .   | .   | .   |
+--------+-----+-----+-----+-----+

Possible Solution

Could this come down to network policy parsing?
The docs on NetworkPolicyPort say that the {} NetworkPolicyPort should allow all ports on TCP:
type NetworkPolicyPort struct {
	// The protocol (TCP, UDP, or SCTP) which traffic must match. If not specified, this
	// field defaults to TCP.
	// +optional
	Protocol *v1.Protocol `json:"protocol,omitempty" protobuf:"bytes,1,opt,name=protocol,casttype=k8s.io/api/core/v1.Protocol"`

	// The port on the given protocol. This can either be a numerical or named port on
	// a pod. If this field is not provided, this matches all port names and numbers.
	// +optional
	Port *intstr.IntOrString `json:"port,omitempty" protobuf:"bytes,2,opt,name=port"`
}

And kube seems to parse the network policy the same way:
$ kubectl get netpol -n x allow-all-80 -o yaml
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-all-80
  namespace: x
spec:
  egress:
  - ports:
    - protocol: TCP
    - port: 80
      protocol: TCP
    to:
    - namespaceSelector:
        matchLabels:
          ns: "y"
      podSelector:
        matchLabels:
          pod: b
  - ports:
    - port: 53
      protocol: UDP
  podSelector:
    matchLabels:
      pod: a
  policyTypes:
  - Egress

Steps to Reproduce (for bugs)

Create conf.yaml
 kind: Cluster
 apiVersion: kind.x-k8s.io/v1alpha4
 networking:
   disableDefaultCNI: true
   podSubnet: <IP_ADDRESS>/16
 nodes:
   - role: control-plane
   - role: worker
   - role: worker

Create kind cluster with calico
 #!/usr/bin/env bash

 set -o errexit -o nounset -o pipefail
 set -xv

 CLUSTER_NAME=${CLUSTER_NAME:-netpol-calico}

 kind create cluster --name "$CLUSTER_NAME" --config conf.yaml
 until kubectl cluster-info;  do
     echo "$(date)waiting for cluster..."
     sleep 2
 done

 kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
 kubectl -n kube-system set env daemonset/calico-node FELIX_IGNORELOOSERPF=true
 kubectl -n kube-system set env daemonset/calico-node FELIX_XDPENABLED=false

using cyclonus, with netpol.yaml containing the policy above:
 go run cmd/cyclonus/main.go probe --all-available --policy-path netpol.yaml --server-pod a,b --server-namespace x,y --server-port 79,80,81,82

Context

I'm working on the kube e2e network policy tests.

Your Environment

Calico version: 3.17.2
Orchestrator version (e.g. kubernetes, mesos, rkt): kind 0.9.0; kindest/node:v1.19.1
Operating System and version: uname -a: Linux a 4.19.121-linuxkit #1 SMP Tue Dec 1 17:50:32 UTC 2020 x86_64 Linux
Link to your project (optional):

thanks @mattfenwick -- @fasaxc @caseydavenport   , any thoughts on this?.... been evolving our test suite to auto generate basically every possible scenario and evaluate it

Looks like a mismatch here: https://github.com/projectcalico/libcalico-go/blob/b29066676c7438a22f7185c00e644354f3c84576/lib/backend/k8s/conversion/conversion.go#L562
If the port struct has no port in it, we skip the whole port struct rather than treating as "all ports" for the given protocol.

I'm happy to put together a PR to address this if that helps you @fasaxc , lmk!

@mattfenwick Be my guest; should be fairly straightforward and that code is easily unit tested by passing it a canned NetworkPolicy and verifying what you get out.  Now we know what the issue is, I'd probably start with a test to repro the scenario in UT; then fix it :-)

/assign

Thanks for the pointer @fasaxc ! 😄   Finally got around to this and put up a PR, not sure I got it 100% right but it's progress at least!!

Merged your changes @mattfenwick ; after a few hours the pin updates should flow through and then you'll be able to test with calico/node:master


Plan editor does not see 'share' link in actions menu

If you share a plan and make the person an Editor, they do not see the 'Share' option when they click on the list of available Actions on their My Dashboard page. They do however have access to the Share tab when they click to edit the plan.
We should update the logic so that its consistent for both. @sjDCC and @stephaniesimms which is the correct behavior? Should someone with editor access be able to access the Share tab?

Editor privileges include the ability to comment and make changes. They cannot invite others/share the plan. So they shouldn't see the "Share" option in the Actions menu for a plan where they only have Editor access. And they should not be able to perform any of the actions on the Share tab. If it's easy to update the logic it would be better to hide the Share tab altogether @briri - yes.

Ok. thanks for the clarification @stephaniesimms.

almost working as expected @briri - Read only and Reviewer roles are okay. But as an Editor I shouldn't see the Share action or have access to that tab either (see screenshot below). Editors and Read Only privileges should be the same with regard to sharing.

Permissions and views all look good to me now. Closing out