Only use sometimes when rules are required

Fixes: https://github.com/tastyigniter/TastyIgniter/issues/778

Not sure if this works but using the nullable (not present) rule instead works and more cleaner... We could then add new component properties to make fields required or not.

I was working on the principle that if they were shown they are required?

On 5 Jun 2021, at 07:46, Sam Poyigi @.***> wrote:
Not sure if this works but using the nullable (not present) rule instead works and more cleaner... We could then add new component properties to make fields required or not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tastyigniter/ti-ext-cart/pull/57#issuecomment-855194377, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMVOYMGKBR5WB4LC5TAL3TRHB3DANCNFSM46CV6FWA.

No problem - updated.

On 8 Jun 2021, at 21:21, Sam Poyigi @.***> wrote:
Right, I mean we don't need the if check, simply replacing sometimes rule with nullable will cover cases where the fields are hidden.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tastyigniter/ti-ext-cart/pull/57#issuecomment-857097826, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMVO5BHGCGBPS7LH4OBQDTRZ3T7ANCNFSM46CV6FWA.


Wrong theme object for CssBaseline style overrides when using styled-components

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
CSB
Steps:

open  CSB
see console

Current behavior 😯
No response
Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Here is a working solution: https://codesandbox.io/s/styled-components-forked-n5k1ri?file=/src/demo.js I hope this helps.

@mnajdova I expect theme object

But instead i have
styles: Fn
defaultTheme: Object
theme: Object

Ah, I see the confusion now. The signature between emotion & styled-components is different. We normalized it in the GlobalStyles components, but we haven't done it in the style overrides. We should update the documentation for the CSS baseline, for example this should be updated: https://mui.com/material-ui/react-css-baseline/#scrollbars
You should treat the value you receive in the styleOverrides as props, and extract the theme out of it.


Ft csvPatch

Fixes # VORTEX-6247:Reordering CSV columns
Proposed Changes
Bug caused by duplicates of the Index and Color columns which must always exist.

When user has these fields automatically re-name on import to prevent memory confusion.
Retains user color & potential custom indexing.
---Could be modified to override our Index + Color with user; but may not neccessarily make sense to do so.

Ill leave it up to matt to approve this when its ready since you guys have been working on it


Laptop

Anything relating with the laptop isn't done. The only reason why I created a PR was so it would be merged to master and then everyone would alter the layout since almost every DOM element is position: absolute; I wrote about the layout shift in the group chat but basically, someone deleted the code that was needed for 3D and now everything has to be shifted back to where it was so the 3D can work properly. I still have to fix things like actually moving the laptop, animations, and anything else related to it

https://user-images.githubusercontent.com/77304345/200839155-29ead16b-cfac-4104-819b-2d33a591e7c9.mov


Controller codes not as per the style guide

I have some files which are not indented, or missing some conventions as per the rubocop style guide. Not that the code is not working, but some experienced people who are seeing them for the first time may see it as a bad taste. May I submit PR, by fixing some of those I could? Let me know your opinions, thanks

Vamsi

Please create pull request, so the team members can see what you are trying to do!

I would say yes, however be gentle. More PRs is better than one giant PR.

Please feel free to open pull requests 👍


Merge Files.Backend and Files.Shared into Files.Core

Description
Backend is a backend-code of Files.App and Shared provide common code for multiple projects.
Concerned code
None
Gains

A better readability.

Requirements
No response
Comments
No response

@d2dyno1

Merging with #4180


HSEARCH-4183 SearchResult.took() returns incorrect, very large value with the Lucene backend

https://hibernate.atlassian.net/browse/HSEARCH-4183

Merged, thanks!

Do we need to backport it?


Add more features to README

Automatic beautiful structured logging of any Go struct etc.

Automatic error stack logging with the xerrors package.

Will also add more examples that show off these features.


i2c always reads input as 0xff

EDIT: PROBLEM FOUND
line 118 of wire.cpp checks if i2c_read(...) returns zero, and discards the data if it does not.
i2c_read(...) in Dev2C.h, does not return zero on a successful read. It will return the result of read(...) in AZ3166WiFiUdp.cpp, which returns the result of recvfrom(...) in UDPSocket.h, which returns the number of bytes sent from the buffer.
Modifying Wire.cpp so that it reads in the data regardless of what i2c_read returns removes the issue, though some sort of replacement error handling should probably be added.
END EDIT
I'm using an IoT devkit to read temperature from an MLX90614 sensor, using the kitronik edge connector to link the two. Pins 19 and 20 on the kitronik are being used as SCL and SDA, and I'm using the Adafruit MLX90614 library to read from the sensor. I've been using a Saleae logic analizer to examine the signals being sent between the two.
When I try to read it, the devkit sends the correct signals to the sensor, which sends back replies that correctly represent the current temperature. However, the devkit reports that the signals it is receiving are always 0xff, regardless of what the sensor is sending. So when it reads in two bites representing the temperature, it always reads 0xffff, which on the sensor in question corresponds to 1037.55 degrees celcius. The actual values that the saleae reports from the sensor, (e.g. 0xA7, 0x3A), when processed, convert to an accurate temperature of 27.15, so the sensor appears to be working correctly.

I've checked this with a backup MLX90614 sensor and received the same result. I've also checked it with and without using a pair of 10kOhm resistors to pull up the sda and scl lines by connecting them to the 3v rail of a breadboard, and received the same results.
edit: I thought there was an issue with the voltage, it looks like I was just reading it incorrectly, the voltage appears to be fine.
When I checked the voltage reaching the sensor, it appears to only be 2.1 volts, below the sensor's  required minimum of 2.6 volts, despite being hooked up to the 3v VDD pin. The devkit is being powered by a USB connection to a macbook pro. I was initially powering an Atlas serial port expander as well, but the behavior and low voltage persists even when the MLX90614 sensor is the only device being powered.
edit:
I'm testing out code in this repository: https://github.com/douglas-johnston/testing-i2c-on-AZ3166
The original code  I used to check the input from the sensor:
#include <Wire.h>
#include <Adafruit_MLX90614.h>
Adafruit_MLX90614 mlx = Adafruit_MLX90614();
//this emulates the function of the Adafruit_MLX90614 "readAmbientTempC()" function, but displays the bytes received from the sensor.
float read16() {
uint16_t ret;
Wire.beginTransmission(0x5A); // start transmission to device
Wire.write(0x07); // sends register address to read from
Wire.endTransmission(false); // end transmission
Wire.requestFrom(0x5A, (uint8_t)3);// send data n-bytes read
ret = Wire.read(); // receive DATA
ret |= Wire.read() << 8; // receive DATA
uint8_t pec = Wire.read(); //crc check, not used
Serial.println(ret, HEX); //prints the two bytes the arduino recieves
float processed = (ret * 0.02) - 273.15; //converts recieved data into celcius
return processed;
}
void setup() {
Serial.begin(115200);
mlx.begin();
Serial.println(read16());
Serial.print("Ambient = "); Serial.print(mlx.readAmbientTempC());
Serial.print("*C\tObject = "); Serial.print(mlx.readObjectTempC()); Serial.println("*C");
}
void loop() {
}

Hi, can you repro your problem with our new version of sdk?

Hello, were you able to solve the problem?


Are both export and backup necessary?

I don't understand why both export and backup are necessary. From what I understand, the use cases for doing either of them are transferring keys to a different yubikey, generating other subkeys, modifying existing subkeys (e.g. their expiration). All of these should be possible after importing the previously exported master and/or subkeys. Why would a backup of the whole .gnupg directory be necessary then?

Not necessary but: It's always good to use multiple ways when creating backups.  (And ideally also test them.¹)
¹ Setting the expiration date on the sub keys to 1 year as suggested in https://github.com/drduh/YubiKey-Guide#sub-keys, forces you to “test” at least one of them once a year.

Backup isn't necessary and there may even be benefit in skipping it - it all depends on your use case and threat model. The guide recommends doing both to strike a balance of usability and is perhaps overly conservative when it comes to recovery planning.


samples: Add samples for sum and avg aggregations

This PR contains the samples for SUM and AVG aggregations.
blocked on #1067

@bourgeoisor, can you PTAL?

Nit good to have: newline at end of all the files

will follow up in a separate PR, thanks!


[KOGITO-1023] consolidate kogito-bom and kogito-runtimes repos

Also please delete kogito-bom stage from Jenkinsfile:
https://github.com/kiegroup/kogito-cloud/blob/6ad6afe989c8d4bddd2c1016007ed63851442c3b/Jenkinsfile#L21-L30


quotation mark in a comment line

spec closes the definition of a function/macro body even when a quotation mark appears in a comment line.
The following code fragment appears in standard.mac. This is a valid syntax and only # $* is treated as a comment.
def user_setdial '# $*'

On the other hand, the following code causes a syntax error because a quotation mark in a comment line is marked as the end of the function definition but a curly brace is not closed there.
def myfunc(k, x) '{
    # use Hooke's law
    return k * x
}'

The current version of the extension simply ignores all characters after a comment sign (#) until the end of line. This behavior is different from what spec does. Though I feel spec's behavior is confusing for most users, the extension needs to follow how the spec interpreter does.

The syntax parser of the extension, which is written in Peggy, was modified so as to handle a quotation mark in a comment line properly in v1.8.2.
I think it is difficult for syntax highlighting to support this rule, owing to the limitation of TexMate grammar syntax.
For the present, I will not (and can not) make the syntax highlighting feature support the rule.
In future I might implement it using the semantic syntax highlighting feature.


I can't upload specific type such as .stl

i how to upload specific type such as .stl, my code doesn't work why? What about acceptedFileTypes? ( note, just i can't upload it on mac )
<FilePond
acceptedFileTypes={['model/*']}
labelIdle={gettext('Üst çene stl tarama dosyasını alana sürükleyin ya da tıklayarak seçim yapınız ')}
server={
    {
        url: '/api/v1/case/impression/upload/' + t.props.match.params.id + '/?name=upperjawstl',
        process: {
            method: "POST",
            headers: {
                Authorization: `Token ${localStorage.getItem('token')}`,
                'X-CSRFToken': $.cookie('csrftoken'),
            },
        }
    }
} />
}

have you registered the file validate type plugin?

Closed because no response for 4 days.


[SampleApp] Launching default app template on iPad with iOS7.0 renders incorrectly

I adjusted the app generated by react-native init <myproject> to be Universal instead of iPhone; and the resulting app renders strangely on an iOS7.0 iPad Mini.

Some initial observations:

the welcome text is not shown at all; if I put the fontSize property in comment, the Text becomes visible, but layout still isn't correct
the text is centered correctly horizontally, but the justifyContent seems to have no effect at all

Details:

iPad Retina Mini
iOS: 7.0.4
react-native: 0.5.0-rc and 0.4.4

@thomasvm can you confirm this is still happening on the latest react-native?
Tested in simulator for iPad and iPad Retina and it all seemed to render correctly, but I don't know about retina mini on a real device.

@brentvatne

This issue is way old, closing for now, if it turns out to be an issue just ping me and I will reopen!


Breaking: rename VissibleName to VisibleName

I think this is a typo but I might be wrong?
If it is, this change should be ok but it will definitely be a breaking change if someone is using this attribute

nevermind. I should have read this first https://github.com/splitbrain/ReMarkableAPI/wiki/Storage

nevermind. I should have read this first https://github.com/splitbrain/ReMarkableAPI/wiki/Storage


Logs for "Automate update Translator cid" are not readable

For example: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/10950266371/job/30405179010
The log is too big it is almost impossible to see the compilation / testing results in a reasonable time. The verbosity of the workflow needs to be reduced. Also it should clearly print what translator commits have been verified and what was the result (exact error message) for each commit.

It is working in progress.

In review

The attached PR meets the target, check comments:
https://github.com/intel/intel-xpu-backend-for-triton/pull/2319#issuecomment-2401704522


Node resizing bug after restoring a flow

Describe the Bug
At first, on custom nodes, when you modify the label in the node, its size adapts and the edge with the other nodes adapt. However, if we do the same thing on the nodes of a restored flow, the size of the nodes adapts but the edge lose the true position of the handle.
I even used the updateNodeInternals function before saving, but the result is the same.
FYI, I tested with default nodes and it generates the same bug.
i'm saving like this:
const onSave = useCallback(() => {         if (rfInstance) {             const flow = rfInstance.toObject();             flow.nodes.forEach(node => {                 updateNodeInternals(node.id);             });             localStorage.setItem('flow', JSON.stringify({                 ...flow,             }))         }     }, [rfInstance]);
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

create two custom nodes and link them with an edge
save the flow
restore the flow
update (first) node label with big text

Expected behavior
Th node handles should adapt its handle positon
Screenshots or Videos
Before saving:

After restoring:

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

This should be fixed in v10.3.9. Can you confirm @Hillal-azem ?

Please re-open if the issue still occurs.


⚠ Bofrost.at has degraded performance

In e77b01c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2264 ms

Resolved: Bofrost.at performance has improved in af32e00 after 9 minutes.


Update to latest rand_core version

Using<EMAIL_ADDRESS>fails to compile since the versions differ.

I have released version 0.4.1 upgrading rand_core to 0.5 (0.4.0 contained a small formatting mistake).
I had to increase the minor version because the minimum supported Rust version has changed from 1.31.0 to 1.32.0.
I believe this should be solved now. Please feel free to reopen otherwise.


Issue with minting function on stETH

I went through the instructions step by step my first problem was the pictures Every picture I tried to open took me to a page that said "Sorry this is not the page you are looking for", the second problem I had was with stETH I minted my SepoliaETH but no stETH was deposited to the wallet as referenced in the following photos. I tried three times

Noted. I believe this has been resolved. Thanks.

yes I think it was resolved thank you for your help


release: Update KServe and dependencies to v0.11.1

Motivation
Update KServe and CRDs in preparation for v0.11.1 release
Modifications

Update go.mod dependencies
Update CRDs under config/crd/bases

Thanks @rafvasq


Update peer dependencies to support react / react-dom >= 15.0.0

This will get rid of the nag message for npm v3 users and will allow npm v2 users on React 15 to continue using react-tooltip.

Thanks :+1:

NP!


V0.7.2 release

patch release to allow 0.7.* series to build on nightly again

Closing -- just intended to use PR to check CI


Can't connect to ip address <IP_ADDRESS>:88

I'm stucked at
Step 2: Join the above network, and navigate to the static IP and port we set in config.json (http://<IP_ADDRESS>:88), you will
I can't connect it from my pc, but I can open it on rpi. How do I fix this?
Also how do I implement this functionality in an electronjs app, can you give some tips?

Sorry this took so long to respond to, I have been swamped at work lately.  It seems like the DHCP server is not working?  Can you post the logs from the rpi side of things?
I meant to debug this - are you on a Pi3?

Yes I'm on pi3 model b. I'm a beginner on linux. Do you want the logs from only the terminal or is there a dump file anywhere else I should look for?

I want to use this to setup my Rpi 3B as an wifi AP, is the problem with installing this on a Rpi 3B resolved?

So I just ran this on my Pi3 and I was able to complete the loop and have the wifi connect to my home wifi.
Can you try the following:
0. In your config file - under "access_point" add a property "force_reconfigure" and set it to "true"
1. Stop the service if you enabled it and `cd` into the project directory
2. Manually run this command `sudo npm start`
3. You should see something like this:

><EMAIL_ADDRESS>start /home/pi/work/raspberry-wifi-conf
> node server.js

Wifi is not enabled, Enabling AP for self-configure

Force reconfigure enabled - reset AP
... dhcp server restarted!
ifdown wlan0 successful...
ifup wlan0 successful...
... hostapd restarted!
... AP Enable Success!

HTTP server running...

At this point using a different wifi device (I use my android phone), connect to the rpi-wifi-ap wifi access point.
If the above works, you should be able to access <IP_ADDRESS>:88 on a chrome browser.
Please let me know which step fails.  If for you get the "HTTP server running" message but the access point does not show up, let me know (I might have seen that issue once or twice when bringing this up).  Typically restarting the app fixes this hiccup - would love more data on this.


Docs: Idempotency docs say only Middy v3.x is supported

What were you searching in the docs?
I was reading the whole Powertools for AWS Lambda (Typescript) docs.
Is this related to an existing documentation section?
https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/idempotency/#makehandleridempotent-middy-middleware
How can we improve?
Immediately below the heading "MakeHandlerIdempotent Middy middleware" there is a "A note about Middy" which says that only v3.x is support. Other parts of the documentation say v4.x

Got a suggestion in mind?
Change v3.x to v4.x
Acknowledgment

[X] I understand the final update might be different from my proposed suggestion, or refused.

Hey @buggy , thanks for dropping the issue that we have missed during the upgrade to v2. Dropping the fix asap.

Found additional inconsistencies:

https://github.com/aws-powertools/powertools-lambda-typescript/blob/bf0aa4b5dbe04c1187b413cd7e0cba33852ad81f/docs/index.md?plain=1#L267
https://github.com/aws-powertools/powertools-lambda-typescript/blob/bf0aa4b5dbe04c1187b413cd7e0cba33852ad81f/docs/core/metrics.md?plain=1#L203


GPC tweaks. Properly deal with extension conflicts.

Reviewer: @jdorweiler
CC: @pdol @kdzwinel
Description:
Two changes here:

Set GPC to default on
Don't overwrite GPC signal if already set by UA or other extension. See https://github.com/EFForg/privacybadger/pull/2722 and https://github.com/globalprivacycontrol/gpc-spec/issues/11#issuecomment-736772505 for background.

Steps to test this PR:

Install extension in Firefox and Chrome
Verify that GPC setting is on, navigator.globalPrivacyControl is set to true on websites, and the Sec-GPC: 1 header is attached to requests.
Turn GPC setting off. Verify that navigator.globalPrivacyControl is set to false on websites, and the Sec-GPC: 1 header is not attached to requests.
Install other extension that sets GPC, such as Privacy Badger. Probably should test the next few steps twice: once with DDG installed first and Privacy Badger installed second; once with Privacy Badger installed first and DDG installed second.
Confirm that navigator.globalPrivacyControl is set to true on websites, and the Sec-GPC: 1 header is attached to requests when GPC is on in Privacy Badger and off in DDG.
Confirm that navigator.globalPrivacyControl is set to true on websites, and the Sec-GPC: 1 header is attached to requests when GPC is off in Privacy Badger and on in DDG.
Confirm that navigator.globalPrivacyControl is set to false on websites, and the Sec-GPC: 1 header is not attached to requests when GPC is off in both extensions. Also check console logs to make sure no errors are thrown.
Confirm that navigator.globalPrivacyControl is set to true on websites, and the Sec-GPC: 1 header is attached to requests when GPC is on in both extensions. Also check console logs to make sure no errors are thrown.

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

👍


Add logging

As the sources are available online additional logging beyond what is currently logging should not be necessary, closing as wont fix


chore(main): release 0.1.1

:robot: I have created a release beep boop
0.1.1 (2024-10-10)
Bug Fixes

Add beta warning to the connect modal. (#58) (5152b1d)
Add ZMK links to the about modal. (#56) (3c319b5)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.1.1
:sunflower:


map: interpret POI taps on Android

x-ref for issue on exact coordinates: https://github.com/react-native-maps/react-native-maps/issues/2496

Fixes https://github.com/NWACus/avy/issues/77
Fixes

Fixes https://github.com/NWACus/avy/issues/604

before
after

https://github.com/NWACus/avy/assets/7328370/3c077712-aa13-47ae-ac8b-191f0607a601
https://github.com/NWACus/avy/assets/7328370/d6d21a3f-74f8-4820-b995-f90a433a49e8


Open to exposing Status (firing, resolved) in AlertTemplateData?

Proposal
We use an annotation called Description that allows engineers to provide guidance on what to do when an alert fires (or resolves). We'd like to allow our engineers to customize the instructions provided in message depending on the state of alert (if resolved, then do something else) which would require access to the state of the rule.
Would this be something accepted by the community and I suspect it might not be immediately straightforward in Eval() given alert state is determined elsewhere.

Once the alert is resolved, the annotations should no longer be evaluated, so it seems impossible for me.

Once the alert is resolved, the annotations should no longer be evaluated, so it seems impossible for me.

Oh duh, that makes sense. Thanks for the quick reply!


Support single event sites

Some events will have a website set up for a single event and then not be used again.

This now works by setting a "primary event" in configuration


TODO

diagnostics: MQTT discovery publications should expose an availability topic which is set appropriately depending on server response.  I think this can be done in a way where all the entities share the same availability topic.  Note that topic strings should be done in mqtt.js and not index.js -- DONE (but see comment below on "DIAGNOSTICS AVAILABILITY"

Examine the feasibility of exposing certain commands as switches via MQTT discovery.  (The only problem is that onstar2mqtt doesn't know the current state of a switch, so it will almost always be published as "unknown.")  (Q: is there a way to configure a switch as a button instead of a toggle??)  -- DONE

runtime configurable polling interval.  This will allow changing the interval (which would be exposed via https://www.home-assistant.io/integrations/number.mqtt/)  Changing the timeout would require calling clearInterval() and then setting it once again.  (also consider using setTimeout/clearTimeout instead of set/clearInterval.)

For #1 (diagnostics availability):
mqtt.js has a "getAvailabilityTopic()" and the mqtt discovery configs actually are publishing that as "availability_topic : this.getAvailabilityTopic()".  However, it might as well not exist:  in the main loop, as part of the initialization, that topic is published with a payload of "true", and it's never changed.   It should be trivial for the code that handles diagnostic parsing to publish this as 'true' when it gets valid diagnostic data, and publish it as false when it gets an error.
This is significant when the vehicle stops responding to diagnostic queries (after 5-6 requests?)  The question is: what kind of JSON is returned from the server when this "vehicle not responding" happens?  Does it look like a diagnostic packet or is it generic?  If the former, the code for setting availability could be contained in the "if (diag) {" block.  Otherwise, things become more complex...

As an alternative to publishing any "availability_topic" whatsoever, there's also "expire_after" config option.  This is documented as "if set, it defines the number of seconds after the sensor's state expires, if it's not updated.  After expiry, the sensor's state becomes unavailable."  The problem with this is that I don't know how it reacts when the sensor is updated, but with the exact same value as it had previously.  Does that count as an update?  see: https://www.home-assistant.io/integrations/sensor.mqtt/

For # 2, see: https://www.home-assistant.io/integrations/button.mqtt/

DIAGNOSTICS AVAILABILITY
The code for this is done and working, but using it suggests it might not be desirable for everyone.
Which is worse:  seeing a value that's old, or seeing no value at all?  When an entity in HA is marked unavailable, the dashboards don't show that value!
If this value is made configurable, it might be easiest for the code detecting the toggle to just delete the map containing the configuration topics/payloads, and let that be regenerated.  I'd still want the diagAvailable topic to be updated, but just remove that topic from the list of diagnostic required availability topics.


Cannot use import statement outside a module

I used this component in my react website and it is working fine. I am migrating my site to next however, while using this component it gives the following error:

Steps to reproduce:

Install the library with yarn add react-github-btn
Stop the server with Control + C
Run the server again and visit the page that is consuming github buttons

The strange thing is, it works with the following steps:

Run the server with yarn dev
Install the library with yarn add react-github-btn
Use it normally and it works

The moment I restart the server same error pops up again ;(
While searching about the error on stackoverflow I found that people suggesting to add type -> module in the package.json file however it does not resolve this issue. In this case I get internal server error.
Here is the video for reference:
https://user-images.githubusercontent.com/2767152/110960363-7b1ce880-8370-11eb-905d-c3ead7288ab7.mov

You need to use next-transpile-modules to transpile ES module inside node_modules.

@ntkme thanks.
If you can add some explanation it will be awesome :)
For anyone who is experiencing the similar issue follow the steps:

Install the next-transpile-modules with command yarn add next-transpile-modules
In your project's root directory, next to package.json add a new file with name (next.config.js [docs])(https://nextjs.org/docs/api-reference/next.config.js/introduction)
Paste the following code and save the file:

const withTM = require("next-transpile-modules")(["react-github-btn"]);
module.exports = withTM();

Restart your server


Nuxt and TypeScript compatibility issues

Following up on the #29 issue that is now closed.
There seems to be an issue with style-resources-module and TypeScript support.
I have a minimal, reproducible template:
vue init scaleleap/nuxt-typescript-template style-resources-module-ts-error
cd style-resources-module-ts-error
npm i
npm run dev

Errors out with:
 ERROR  Failed to compile with 1 errors                                                                        friendly-errors 13:02:30

 ERROR  in ./pages/index.vue?vue&type=style&index=0&lang=scss&                                                 friendly-errors 13:02:30

Module build failed (from ./node_modules/sass-loader/lib/loader.js):                                           friendly-errors 13:02:30

  background-color: $body-bg;
                   ^
      Undefined variable: "$body-bg".
      in /private/tmp/your-project-name/pages/index.vue (line 14, column 21)
                                                                                friendly-errors 13:02:30
 @ ./node_modules/vue-style-loader??ref--9-oneOf-1-0!./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--9-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--9-oneOf-1-3!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=style&index=0&lang=scss& 4:14-369 14:3-18:5 15:22-377
 @ ./pages/index.vue?vue&type=style&index=0&lang=scss&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js

Template source: https://github.com/ScaleLeap/nuxt-typescript-template

Thank you for your attention.

Moved broken example to a branch, so I can use master: https://github.com/ScaleLeap/nuxt-typescript-template/tree/style-resources-breakage
Not sure how to use a branch with vue init otherwise I'd edit my original post.

When will this be fixed? I tried this module out already in March, and deemed it unusable with TypeScript + Nuxt project because of this bug...
With Vue 3 approaching, having TypeScript supported should get more priority.

Is this fixed with v1?

Hmm still not fixed. Is there any work around maybe?

@manniL I can confirm this is still a bug with version 1.0.0

Not an ideal solution but the way I am currently running this is via official nuxt typescript runtime.

@lukas-martys
I'm running it with nuxt-ts too but I am getting the error nevertheless. Does it indeed work for you?
@manniL
Any way around it yet?

Just adding my two cents; adding @nuxt/typescript-runtime and using nuxt-ts like @lukas-martys said works for me. I also tried a fresh install of my node modules and removed package-lock.

@lukas-martys  @kn0wn
That workaround doesn't seem to be working for me. I have a minimal reproducible example here. Can you spot anything?
Steps to repro:

Created app with npx create-nuxt-app my-app, all defaults except the following

Choose a programming language: Typescript
Choose the runtime for TypeScript @nuxt/typescript-runtime

Install sass: yarn add --dev sass-loader node-sass
Create _variables.scss in assets with $brand-primary variable
Add config to nuxt.config.js:styleResources: {
    scss: ['./assets/_variables.scss']
  },

Use variable in a component (in my case pages/index.vue)
Try to run app by calling npm run dev which in turn calls nuxt-ts and get error SassError: Undefined variable: "$brand-primary".

Check for adding '@nuxtjs/style-resources' in modules section in the nuxt.config.js file. It works for me.

A lot has changed in Nuxt since this was reported and also the repro repos are dead so please report new issue with reproduction steps if this is still a problem.


License

Without a public license file, the code here is pretty much read only.  People don't technically have the right to run the software.  I don't believe that is your intent.  Can you let us know under which license you are releasing your mod under so that the community can act accordingly?

@piisawheel I have to make sure that the Developers working on the mod are still on agreement with what type of License, I have not listed one cause the mod was being rewritten

https://github.com/BedrockLegends-Mods/WoodenUtilities/commit/fad04abb488a72f7f24264bebf932447db2fbf0c


Add missing erase(first, last) function to ordered_map

Fixes #3108

Coverage remained the same at 100.0% when pulling 6cdc1c2f112ce17d88784ed9a8ff3fa2542d63fc on issue3108_erase_in_ordered_map into 7440786b813534b567f6f6b87afb2aa19f97cc89 on develop.

There is an assertion that only hits on MSVC builds:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.16.27023\include\vector(199) : Assertion failed: vector iterators incompatible

As I do not work on Windows, I cannot debug into this problem to get a stack trace. Any help is greatly appreciated!

>	test-ordered_map.exe!std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>>::_Compat(const std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>> & _Right) Line 190	C++
 	test-ordered_map.exe!std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>>::operator==(const std::_Vector_const_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>> & _Right) Line 154	C++
 	test-ordered_map.exe!doctest::detail::Expression_lhs<std::_Vector_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>> &>::operator==<std::_Vector_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>>>(std::_Vector_iterator<std::_Vector_val<std::_Simple_types<std::pair<std::string const ,std::string>>>> && rhs) Line 1238	C++
 	test-ordered_map.exe!_DOCTEST_ANON_FUNC_2() Line 248	C++
 	test-ordered_map.exe!doctest::Context::run() Line 6487	C++
 	test-ordered_map.exe!main(int argc, char * * argv) Line 6571	C++

Here's the call-stack

VS seems to be in line with cppreference, at least.
See https://en.cppreference.com/w/cpp/container/vector/pop_back: Iterators and references to the last element, as well as the end() iterator, are invalidated.
The Container::resize at the end of ordered_map::erase is equivalent to a N pop_back()s, and that the last one of those invalidates your 'first'.

Seems like if the range being removed is at the end, that requires resetting the first iterator to be end() before returning.

I added auto offset = std::distance(Container::begin(), first); at the beginning of the function and returned return Container::begin() + offset; at the end. That fixes it as well.

Thanks for the help! I will update the PR later on. Very interesting to see that only MSVC debug mode detected this issue!

Thanks for the help! I will update the PR later on. Very interesting to see that only MSVC debug mode detected this issue!

I think that this is solely because of the extra debugging information that MSVC debug adds.  The first iterator at the end of the operation should be exactly the same value as you get by begin() + count when the iterators are just pointers into the vector, which they are most of the time.  There is no observable difference between the old and new code without that extra debugging, but the new code is more correct.

Thanks for the help! I will update the PR later on. Very interesting to see that only MSVC debug mode detected this issue!

I think that this is solely because of the extra debugging information that MSVC debug adds. The first iterator at the end of the operation should be exactly the same value as you get by begin() + count when the iterators are just pointers into the vector, which they are most of the time. There is no observable difference between the old and new code without that extra debugging, but the new code is more correct.

Yes, I'm aware that this is really pedantic - that's why I would have expected UBSAN or ASAN to detect this.
Anyway - thanks @ltjax and @gregmarr for the help!


add property schema for kubectlmage

This PR:

adds/changes/removes etc

Testing
Description on how {APP-NAME} can be tested.

[ ] fresh install works
[ ] upgrade from previous version works

Other testing
Description of features to additionally test for {APP-NAME} installations.

[ ] check reconciliation of existing resources after upgrading
[ ] X still works after upgrade
[ ] Y is installed correctly

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.
[ ] Update Lastpass values if required.

Waiting for a @giantswarm/team-rocket review before merging.

Yolo


exclude logo.webp from the dist folder

as much as everyone loves the logo, I think people shouldn't download it with npm (+ 25kb). They should come to the repo to admire it.

Hey there! Thanks for the issue, me and my team will solve it!

fixed in 4ccbd30a0bd54223fba876544032bacb166e58a9


Add doctrine dbal tracing support that is optional to enable

This is the tracing support for dbal. This also took me half a day figuring out how to make it optional to use and enable. The problem is that there is no clear way to enable tracing because there actually is no hook.
I cheated the system by replacing the symfony DbalLogger that is often used to log queries to monolog. So enabling this will actually disable that functionality. If someone else has an better idea feel free to help out I've been hitting my head on making this work better for 6 hours straight now and could not find any better way.
To use Dbal tracing you will have to enable the following options:
doctrine:
    dbal:
        logging: true

sentry:
    register_dbal_listener: true

Good luck!

The only neat way we could fix the Class Doctrine\DBAL\Logging\SQLLogger not found.. Is to install the suggested dependencies for the test. This way we can also unit test the DbalListener.

The only neat way we could fix the Class Doctrine\DBAL\Logging\SQLLogger not found.. Is to install the suggested dependencies for the test. This way we can also unit test the DbalListener.

install the suggested dependencies for the test

This is the way 👍

I cheated the system by replacing the symfony DbalLogger that is often used to log queries to monolog

As far as I know, the Symfony Profiler works the same way by adding a custom SQL logger, which is the public-facing API nearest to where the actual query is really executed. During the past few days I also explored to hook into more low-level points like the driver or the entity manager itself so that we can get more precise tracing of different parts of Doctrine, but for an initial implementation of this feature what you did is more than enough imho

install the suggested dependencies for the test

This is the way 👍

I cheated the system by replacing the symfony DbalLogger that is often used to log queries to monolog

As far as I know, the Symfony Profiler works the same way by adding a custom SQL logger, which is the public-facing API nearest to where the actual query is really executed. During the past few days I also explored to hook into more low-level points like the driver or the entity manager itself so that we can get more precise tracing of different parts of Doctrine, but for an initial implementation of this feature what you did is more than enough imho

@ste93cry You can indeed wrap the whole driver with composition for more complex tracing en good example of this I found in the following opentracing bundle:
https://github.com/auxmoney/OpentracingBundle-Doctrine-DBAL

@ste93cry You can indeed wrap the whole driver with composition for more complex tracing en good example of this I found in the following opentracing bundle:
https://github.com/auxmoney/OpentracingBundle-Doctrine-DBAL

@ste93cry I added tests, I feel that this one is GTG

@ste93cry I added tests, I feel that this one is GTG

I applied the changes you requested.

I applied the changes you requested.

Before I forget as usual, can you please also add a CHANGELOG entry with a reference to this PR?

Before I forget as usual, can you please also add a CHANGELOG entry with a reference to this PR?

@ste93cry @Jean85 Okay, I'm going to be very honest here. I'm a freelance developer and doing this in my free time. I've been trough 2 review passes already and am burned out. Contributing is not easy and I've now spend 40 of my hours researching making PR's and applying review comments. I'm not getting paid for this.
I might come back later for this, after I recharged...

@ste93cry @Jean85 Okay, I'm going to be very honest here. I'm a freelance developer and doing this in my free time. I've been trough 2 review passes already and am burned out. Contributing is not easy and I've now spend 40 of my hours researching making PR's and applying review comments. I'm not getting paid for this.
I might come back later for this, after I recharged...

First of all, I wanna thank you for the help you gave us until now

I'm a freelance developer and doing this in my free time

As you know, Sentry is a company, however most of the contributors of this package like you do this in their free time without getting paid. Myself is not getting paid for this, I do it both to contribute back to the community and because I like the product and I feel that working on it is satisfying. Even though, and I know this, often I leave a lot of comments which someone (or a lot of people) may find uninteresting and/or unuseful, I strongly want to keep the code standard and quality of this package the highest I can and this means usually going through many review and changes. Some of these changes are indeed opinionable personal preference and I will try to make my best in the future to improve on this and instead make them myself to not bother people.

If you have the time to apply the last touches, please do so :).

Sure, once I will have a bit of free time during these days I will happily do it :+1:

First of all, I wanna thank you for the help you gave us until now

I'm a freelance developer and doing this in my free time

As you know, Sentry is a company, however most of the contributors of this package like you do this in their free time without getting paid. Myself is not getting paid for this, I do it both to contribute back to the community and because I like the product and I feel that working on it is satisfying. Even though, and I know this, often I leave a lot of comments which someone (or a lot of people) may find uninteresting and/or unuseful, I strongly want to keep the code standard and quality of this package the highest I can and this means usually going through many review and changes. Some of these changes are indeed opinionable personal preference and I will try to make my best in the future to improve on this and instead make them myself to not bother people.

If you have the time to apply the last touches, please do so :).

Sure, once I will have a bit of free time during these days I will happily do it :+1:

@ste93cry thank you for your understanding answer. Could you and @Jean85 make time to check if all the open comments now are all you want changed?
If so I will make one last commit that applies them.

@ste93cry thank you for your understanding answer. Could you and @Jean85 make time to check if all the open comments now are all you want changed?
If so I will make one last commit that applies them.

I cannot promise that these changes will be the last, even though I think that after them we should be ok. As I replied above, if you don't have the time to work on this anymore I will anyway step up and end the work because it's indeed something we want to merge and that in the good and in the bad I strongly believe that is a good starting point

I cannot promise that these changes will be the last, even though I think that after them we should be ok. As I replied above, if you don't have the time to work on this anymore I will anyway step up and end the work because it's indeed something we want to merge and that in the good and in the bad I strongly believe that is a good starting point

I can't believe I finally got the build green! PR should be ready now for the review, I tried it by using a SQLite in-memory database and it worked quite well, although there are probably many things that can be improved. @rjd22 it would be awersome if you could take a look and try it 😃

Where would you add it? The only place I see that makes sense is the documentation on the official website

I would put the default values with a comment here: https://github.com/getsentry/sentry-symfony#configuration-of-the-sdk

Are we sure we want to do that? The direction I would like to take as already done for Monolog is moving all documentation besides the install instruction to https://github.com/getsentry/sentry-docs to avoid having to maintain in one place only the docs, so I would like to avoid adding more things in the README

I'm :+1: on moving that stuff to the docs if we leave a clear reference to it. Obviously it should end up in a different PR.

@Jean85 @ste93cry thank you for all the work! It's great to see this one merged. Maybe it would be best to look over the main one after this one and finish with the twig tracing:
https://github.com/getsentry/sentry-symfony/pull/423

Hi @rjd22 Could some documentation of this option be added in the Readme ?
I don't understand what it does.


Link in Readme is dead

The pending solution lives here.

Well, it does not anymore; the link is dead.

Should be fixed on github, but I cannot change it on the package website. Thanks for letting me know!


Cannot add unique index for _to in edge collection

I'm on arango 3.4.7 and I wanted to add an unique index on _to. For some reason it seems to start indexing but nothing happens. No error nothing. I tried it in the regular html backend of arango.
Maybe its related to #5643?

@konsultaner: Indexing a larger collection may take some time.
The web UI of ArangoDB will only show the index once it has been fully created. If index creation fails it should however display an error message eventually, but that may be easy to overlook when continuing working on other things in the web UI.
In order to check if there is any issue with creating that index, can you try starting the index creation from the arangosh instead? The command for creating an index should be something like
db.<collection>.ensureIndex({ fields: ["_to"], ... });

(if the index is just on _to - other index properties will need to be added, such as type (mandatory), unique (optional), sparse (optional).

I tried it again and it worked. I have no Idea why it did not work the first time. Sorry, I might have done something wrong..


Govc session persistance

Description of changes:
Persist govc sessions to known tmp dir mounted in container
This should allow our cli to reuse the same vsphere session per command execution. It should help with concurrent session problems
We should add a mechanism to destroy the session at the end of each cli execution, to avoid leaving orphan sessions. If not, these will stay active until they expire. I'll follow up with a fix for this in the next PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

closing this in favor of reusing containers with #705


Configurable task execution role

Configurable task execution role
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html

Thanks. This is good, I'm just wondering whether this setting should be global or per-cluster. To work backwards from customer requirements, in your use-case, for what scenario did you need this setting for?

You need to define an IAM execution role if you want logs https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_cloudwatch_logs.html#cwl_iam_policy (you need a role + policy allowing writing to Cloudwatch Logs) or want to use images hosted on ECR https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_Console_Repositories.html (role + policy pulling from ECR)
Both sound more like a per-cluster then per pod requirement and therefor I think configuring them per cluster is fine.


Fix 2.1 branch

Sorry, missed a few things there

/retest

/test build-containers

/test test-infra_build-containers

/test test-infra_build-containers

/test test-infra_build-containers


Add clipping plane to example

Overview
Adds clipping plane to example scene to demonstrate fixed axis
Changes

Fixes: #5803

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run


BoltGraphClient serializes object parameters ignoring JsonContractResolver -> implement Neo4jIgnoreAttribute

As mentioned in #126

we can`t exclude complex properties as usual with [JsonIgnore] because then they would not be serialized to our ASP.net Redis session cache, where we need them. So we derived our own ContractResolver interpreting the self-created attribute “[Neo4jIgnore]” instead of [JsonIgnore] to exclude complex properties ONLY from the Neo4j serialization. This works fine with http/https. But the BoltGraphClient seems to ignore this and throws exceptions ("Property values can only be of primitive types or arrays"). The bug does not occur if I use [JsonIgnore] – but as mentioned, that breaks our Redis caching.

@cskardon
I have looked into your code and found that the BoltGraphClient serializes object parameters in Neo4jDriverExtensions with your own method SerializeObject - so any custom JsonContractResolver will never apply here.
Our problem could easily by solved by adding an attribute Neo4jIgnoreAttribute to your project and extend the SerializeObject method with an additional condition || pi.IsDefined(typeof(Neo4jIgnoreAttribute) for that:
        {
            return type.GetProperties(BindingFlags.Instance | BindingFlags.Public)
                .Where(pi => !(pi.GetIndexParameters().Any() || pi.IsDefined(typeof(JsonIgnoreAttribute)) || pi.IsDefined(typeof(Neo4jIgnoreAttribute))))
                .ToDictionary(pi => pi.Name, pi => Serialize(pi.GetValue(value), converters, gc, pi.CustomAttributes));
        }

So users could decide if they want to [JsonIgnore] properties in every serialization or just [Neo4jIgnore] only for Neo4jClient.
Should be implemented also for non-Bolt usage so that [Neo4jIgnore] will work in both.
I will create a pull request with those changes.
Use can reproduce or test it with this example class and cypher
        public class Actor
        {
            public string Name { get; set; }
        }
        public class Movie
        {
            public string Title { get; set; }
            [Neo4jIgnore]
            public Actor MainActor { get; set; }
        }

                var q2 = graphClient.Cypher
                    .Match("(m:Movie {Title:'Ocean`s Eleven'})")
                    .Set("m += {paramMovie}")
                    .WithParam("paramMovie", movie)
                    .Return(m => m.As<Movie>());

                var result = q2.Results.SingleOrDefault();

Here is the PR: https://github.com/Readify/Neo4jClient/pull/337

Closing this as the PR was put into 4.x

Closing this as the PR was put into 4.x


Show log ends up in SBOX_FATAL_MEMORY_EXCEEDED

Bug description
So basically I have multiple containers running, every container works fine to show its logs and stuff.
However I have one container, that is running a .NET Core 3.1 application and when I try to view its logs, the web UI breaks and chrome shows me this error code: SBOX_FATAL_MEMORY_EXCEEDED
Portainer Logs
I´ve had the portainer log open while i was trying to get the logs from my container this is happening on, but there are no logs appearing in the portainer log.
Anyone an idea what that could be?

Edit: Forgot to mention, when I try to get the logs of the container using docker logs -f <container_name> i get the console output of my .NET Core Application just fine... It seems portainer just has an issue with something. Not sure

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
Thnks for posting this, is it possible to share the .net application , so that
we could reproduce. pl let us know if the environment is portainer 2.0 and
docker 19.03 or above. is it on docker swarm or standalone

Hi, unfortunately it is not possible to share the .net application as it requires several access tokens and credentials since it connects to different external services.
I am using Portainer 2.0 yes, the latest portainer-ce docker image and  Docker standalone 20.10.1 on an Ubuntu VPS

I found the issue and I guess that is not portainers fault.
I had a infinite loop in which I updated the Console Title without delay.

I found the issue and I guess that is not portainers fault.
I had a infinite loop in which I updated the Console Title without delay.

@johmarjac just to confirm with you to see if we need to investigate this: did the infinite loop created a massive amount of logs? Where you looking at the logs of a container in a Docker endpoint inside Portainer or a Kubernetes endpoint?
Thanks.

@johmarjac just to confirm with you to see if we need to investigate this: did the infinite loop created a massive amount of logs? Where you looking at the logs of a container in a Docker endpoint inside Portainer or a Kubernetes endpoint?
Thanks.

No the infinite loop did only set the Console Title of the .NET Core App Console Application that was running.
while(true)
{
    Console.Title = $"PacketCount: {list.Count}";
}

Basically this, but not logging anything.
And it was in a Docker endpoint inside portainer yes. I ddidnt use Kubernetes.

No the infinite loop did only set the Console Title of the .NET Core App Console Application that was running.
while(true)
{
    Console.Title = $"PacketCount: {list.Count}";
}

Basically this, but not logging anything.
And it was in a Docker endpoint inside portainer yes. I ddidnt use Kubernetes.

I'm trying to understand why Portainer would not display any logs but the Docker CLI would work. Did you had a massive amount of logs inside this container? I'm guessing the container being stuck in an infinite loop could cause some intensive resource usage or making the container busy and unable to give a proper logs response but I'm curious why the CLI actually works.

I'm trying to understand why Portainer would not display any logs but the Docker CLI would work. Did you had a massive amount of logs inside this container? I'm guessing the container being stuck in an infinite loop could cause some intensive resource usage or making the container busy and unable to give a proper logs response but I'm curious why the CLI actually works.

Well the CLI itself felt super unresponsive as well, took ages to come up but did come up and took ages to abort using Ctrl + C.
But yet again, no massive amount of logs, just the Console Title being set in an infinite loop.

Well the CLI itself felt super unresponsive as well, took ages to come up but did come up and took ages to abort using Ctrl + C.
But yet again, no massive amount of logs, just the Console Title being set in an infinite loop.

Ok, yes, it seems that is it related to the fact that the container was stuck in an infinite loop. We should probably handle this properly instead of crashing the browser.

Ok, yes, it seems that is it related to the fact that the container was stuck in an infinite loop. We should probably handle this properly instead of crashing the browser.

@deviantony I prepared a small image reproducing this error.
docker pull johmarjac/inflooptest:latest
In portainer you need to run with interactive shell -ti otherwise the error didnt appear nor the application did not run I actually was not sure.

@deviantony I prepared a small image reproducing this error.
docker pull johmarjac/inflooptest:latest
In portainer you need to run with interactive shell -ti otherwise the error didnt appear nor the application did not run I actually was not sure.

Great, @PortainerSupport have a look and see if you can reproduce.

Great, @PortainerSupport have a look and see if you can reproduce.

Ticket update by Bala Natarajan<EMAIL_ADDRESS>we have deployed the same .net app thru UI choose interactive tty (ti).after
deployment n clicked logs UI wasnt responsive, then refresh the page, its back
to normal. its docker 20.10 with swarm enabled
docker logs/events comamnd isnt responding too

Ticket update by Bala Natarajan<EMAIL_ADDRESS>we have deployed the same .net app thru UI choose interactive tty (ti).after
deployment n clicked logs UI wasnt responsive, then refresh the page, its back
to normal. its docker 20.10 with swarm enabled
docker logs/events comamnd isnt responding too

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
johmarjac wasn't found at github.com.
hello   Office 365      johmarjac
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:08:21 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: Show log ends up in SBOX_FATAL_MEMORY_EXCEEDED #QUE00000269
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser t18si18845019pjq.51 - gsmtp
DSN generated by:       MEAPR01MB4277.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:08:21 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:08:26 AM      v2app8.mail.happyfox.com MW3PR06CA0006.namprd06.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    5 sec
3       1/18/2021
4:08:29 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    3 sec
4       1/18/2021
4:08:29 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB4277.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=lfreBAlS7Cs98LmyFTqZE1mCMoNhonMBOgSHHIkfH9nW4XIB9WPKTf9T6VM62f7ywOiFnNyFtPZGzR+lpxE0GFZxg9eD16ItOMFraocbB4DpZLB+lpBUTjPXpsaOeGA9LhcacItvRMmjNmRbbnNMq0UGTs7lB2e2gBKt46owGpWGlwIELPqK9g70JEjrrs5lGW5WWEvPtwShlTeu4wwTI3JJnIh38dCPPcDbGHYxYVrMyKec0j5V2yiEveskfYCsDKtNrj3v+8LvAZ7QltggvoSXW3zvecf+f126CGgU3MAwEWYGRmF8pHgeqSer2/HSYAnjFj4voCzrjTj6EkXEAg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=2QhcpZUB3PUkHU5wBxeFTkQ5tMBAhz2/lv7iunMrL10=;
b=U2HuXrCE1WNZRviTi7gNFlznr2ZEk0wzURzieSa7+uk34KSvEAYvEh/7PykuqGr4NtD0xx9BP1YuvmdCtSUyMtaRvWV8okU1i6L4Wi4G197IdTk1Lp59wvZfOFqBzPXXvWP28zEUns5T6oXBQvn0/XsUQlrMT6Y/UoKG9YC6/CEFMvqWyNmYufCU6DXkBHbRBgetzIZlrVixxVYokIElDWUlqueYvhH3fpeSUiang/1d/sCvphK9QG+mvwiXcTuT2fRCIcjXe9CormekK00vSjpqmuY5XdmpHDsDUAzXP34KPH2hh1kv0Ni3gdCRSSNTi76pJUFjmh46OMBYCk0QKw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=2QhcpZUB3PUkHU5wBxeFTkQ5tMBAhz2/lv7iunMrL10=;
b=iKS7Az+L49AmwT9Hs62w5raIrapyAmYD/JvvpPgyYhw/Ha5yjPnT1iOP8MJLSmsh9TmdOnwgpyLmyGuTVNZDnrmDuGIReJ2StVGFY25x1cvPELt/AwdY+0dmWQOlrcHgE80gxqwBK5ayrIWcTESRW/4Tb51chAI+dLEyQ4uYRpo=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by MEAPR01MB4277.ausprd01.prod.outlook.com (2603:10c6:220:3d::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12; Mon, 18 Jan
2021 04:08:29 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:08:29 +0000
Content-Type: multipart/mixed; boundary="===============9132007747519924453=="
Subject: Re: Show log ends up in SBOX_FATAL_MEMORY_EXCEEDED #QUE00000269
From: "Bala Natarajan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:08:21 -0000
Reply-To: "Bala Natarajan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW3PR06CA0006.namprd06.prod.outlook.com
(2603:10b6:303:2a::11) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW3PR06CA0006.namprd06.prod.outlook.com (2603:10b6:303:2a::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12 via Frontend Transport; Mon, 18 Jan 2021 04:08:26 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id 497B31E3358        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:08:21 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: de5762c4-ea9a-4435-8459-08d8bb66b510
X-MS-TrafficTypeDiagnostic: MEAPR01MB4277:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6430;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
sb0JiHH89NKUvAh/iDojAOTqOgZoCl+axjTctHiawRDck54OMVb/Txej/21Q1S7FIbunr/c61BbvfKLmx6kKAgZn1IBioCHOxF/IsvdoDTUMcsF6T11q4Q5QGfuOt7HLwDgD6QjzRtlN9grTY5ZZAcE0aiH6i+qplyZc33bEylqZFPPt3ePOaHc3/UdptPx2PDH1LJy9NsvEHfr9BNfi4ixUsuUNzIKrpdChbgEsj/6PxHym2DqBu26gVkZLrHDS4osX1x2otHWd7t33gCk3ZzIAz+2RCMN4FkQxIVd8/PEGxNXazX4k5DyZar97DoXbKxu7e9LbqSyjBOng7yRLne9pbtgZYwMw6UxhuWjOyT7Bs91Lpgld8Jt8gM4/+tKGmMMhZTNPIJmqE/9sdYEAyA==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(376002)(366004)(346002)(396003)(39830400003)(136003)(26005)(103116003)(478600001)(5660300002)(55236004)(86362001)(66476007)(66556008)(66576008)(316002)(66946007)(186003)(36756003)(6266002)(7126003)(3450700001)(83380400001)(9686003)(8676002)(8936002)(52116002)(33964004)(6916009)(2906002);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?zHfIIFcp+gnOQY8S0dPqtsew/BmQMJlNeUow3y+7dpyOiVVIaVQ5YU8NnoRx?=
=?us-ascii?Q?ZavW5pruY9Vynql9oWc4vKeaa/CG7s1EAT0c1t0jfHA/LIb7dY4Q48Nz9BAi?=
=?us-ascii?Q?FkpKw6HQZIUh3R8xVVyVfXbEoBj1z135eVVs1lmx6chMUIiIzdXKtAzeUQ0M?=
=?us-ascii?Q?rixo9UPnSrIAlEvtl/jj2ZaHOVElLzzII5r5OczYK05hPs6L9BN9SdkM3cc8?=
=?us-ascii?Q?a32dN8xavoNS45p3fSXSO/Bp+HlulBJaAHvM/I9LLH22JjzrPXu/gIXf57XE?=
=?us-ascii?Q?HU0FhhOLrr6NZII6jKPiDQHiy/cvT/04kdAiFENJJlN6aCKHBVsrEMBuV96l?=
=?us-ascii?Q?9XDU+i0AOhbMgczQrvj7Q6F0Tz3+QijTaFUR8io8RXQMMGH0djEq/XLnPRsV?=
=?us-ascii?Q?5r93oMJ+C2/+yjP0ASASeP/KL7P/hFfpML+pfjT40b/EE+p3J2Nu4uGkOQo3?=
=?us-ascii?Q?4pv8VohbPIpAme6AOYQWvhwydjTlRlb3Ar/1Rjo/5xVorXuSY7yyc+glOS/N?=
=?us-ascii?Q?bYxnN30SQRC5r3trWvgNXpEm2wRz2vvWFv/MqBqhNCBnNfU/A5Hl3e3IGY43?=
=?us-ascii?Q?m7HstEaq1Jtr//uc4i2ikMGFsf5+ksYW9FXK4U8ktN4uKvvWIezceEVy9d7g?=
=?us-ascii?Q?Q5r420LIVmdisWR4R1U0z8r9b61A+P79dpxLo2Iq4XChgwC2fMkBX7xdZlkd?=
=?us-ascii?Q?wEI+ZT+o1TI3x0SJ8Aarf9ZiGo11+G8fbFILPXEqVUzLLwjZmOhmKc4U3aSm?=
=?us-ascii?Q?cyt4gDjMaz1qc8QQKc15xZ+ioXm/58mA9+4iCVgYQUp92ub1qf9BChA0MQtC?=
=?us-ascii?Q?a3UC0FCeXmvwPOG9336aHkYOMuRoirrMgFp+V7AO9KxKsKTHD/6trhTnXfxE?=
=?us-ascii?Q?373A5miXnV6UiR8XGBF0l/XxSB1xYZq1BQ9hDmmxua/AreEylLeBeTofrD8M?=
=?us-ascii?Q?kM3wcdE8U5WwYWge0TFxptzKbnv2BdPwzUmnFzXP5sAtoWaVpxAz42XTlYGM?=
=?us-ascii?Q?6PYO?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: de5762c4-ea9a-4435-8459-08d8bb66b510
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:08:29.0930
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: EkTxLy8Lxv100NQvUdhG4Jjwp9/X1NU0lI4Q9nM6G146z8yyPmJwN4gejecRnrjHtrrtMRNwtzzgBqsZ17BWsA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MEAPR01MB4277
New reply for the ticket #QUE00000269
we have deployed the same .net app thru UI choose interactive tty (ti).after
deployment n clicked logs UI wasnt responsive, then refresh the page, its back
to normal. its docker 20.10 with swarm enabled
docker logs/events comamnd isnt responding too

Bala Natarajan
Reply to this email to submit an update.

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
johmarjac wasn't found at github.com.
hello   Office 365      johmarjac
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:08:21 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: Show log ends up in SBOX_FATAL_MEMORY_EXCEEDED #QUE00000269
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser t18si18845019pjq.51 - gsmtp
DSN generated by:       MEAPR01MB4277.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:08:21 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:08:26 AM      v2app8.mail.happyfox.com MW3PR06CA0006.namprd06.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    5 sec
3       1/18/2021
4:08:29 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    3 sec
4       1/18/2021
4:08:29 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB4277.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=lfreBAlS7Cs98LmyFTqZE1mCMoNhonMBOgSHHIkfH9nW4XIB9WPKTf9T6VM62f7ywOiFnNyFtPZGzR+lpxE0GFZxg9eD16ItOMFraocbB4DpZLB+lpBUTjPXpsaOeGA9LhcacItvRMmjNmRbbnNMq0UGTs7lB2e2gBKt46owGpWGlwIELPqK9g70JEjrrs5lGW5WWEvPtwShlTeu4wwTI3JJnIh38dCPPcDbGHYxYVrMyKec0j5V2yiEveskfYCsDKtNrj3v+8LvAZ7QltggvoSXW3zvecf+f126CGgU3MAwEWYGRmF8pHgeqSer2/HSYAnjFj4voCzrjTj6EkXEAg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=2QhcpZUB3PUkHU5wBxeFTkQ5tMBAhz2/lv7iunMrL10=;
b=U2HuXrCE1WNZRviTi7gNFlznr2ZEk0wzURzieSa7+uk34KSvEAYvEh/7PykuqGr4NtD0xx9BP1YuvmdCtSUyMtaRvWV8okU1i6L4Wi4G197IdTk1Lp59wvZfOFqBzPXXvWP28zEUns5T6oXBQvn0/XsUQlrMT6Y/UoKG9YC6/CEFMvqWyNmYufCU6DXkBHbRBgetzIZlrVixxVYokIElDWUlqueYvhH3fpeSUiang/1d/sCvphK9QG+mvwiXcTuT2fRCIcjXe9CormekK00vSjpqmuY5XdmpHDsDUAzXP34KPH2hh1kv0Ni3gdCRSSNTi76pJUFjmh46OMBYCk0QKw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=2QhcpZUB3PUkHU5wBxeFTkQ5tMBAhz2/lv7iunMrL10=;
b=iKS7Az+L49AmwT9Hs62w5raIrapyAmYD/JvvpPgyYhw/Ha5yjPnT1iOP8MJLSmsh9TmdOnwgpyLmyGuTVNZDnrmDuGIReJ2StVGFY25x1cvPELt/AwdY+0dmWQOlrcHgE80gxqwBK5ayrIWcTESRW/4Tb51chAI+dLEyQ4uYRpo=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by MEAPR01MB4277.ausprd01.prod.outlook.com (2603:10c6:220:3d::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12; Mon, 18 Jan
2021 04:08:29 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:08:29 +0000
Content-Type: multipart/mixed; boundary="===============9132007747519924453=="
Subject: Re: Show log ends up in SBOX_FATAL_MEMORY_EXCEEDED #QUE00000269
From: "Bala Natarajan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:08:21 -0000
Reply-To: "Bala Natarajan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW3PR06CA0006.namprd06.prod.outlook.com
(2603:10b6:303:2a::11) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW3PR06CA0006.namprd06.prod.outlook.com (2603:10b6:303:2a::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12 via Frontend Transport; Mon, 18 Jan 2021 04:08:26 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id 497B31E3358        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:08:21 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: de5762c4-ea9a-4435-8459-08d8bb66b510
X-MS-TrafficTypeDiagnostic: MEAPR01MB4277:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6430;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
sb0JiHH89NKUvAh/iDojAOTqOgZoCl+axjTctHiawRDck54OMVb/Txej/21Q1S7FIbunr/c61BbvfKLmx6kKAgZn1IBioCHOxF/IsvdoDTUMcsF6T11q4Q5QGfuOt7HLwDgD6QjzRtlN9grTY5ZZAcE0aiH6i+qplyZc33bEylqZFPPt3ePOaHc3/UdptPx2PDH1LJy9NsvEHfr9BNfi4ixUsuUNzIKrpdChbgEsj/6PxHym2DqBu26gVkZLrHDS4osX1x2otHWd7t33gCk3ZzIAz+2RCMN4FkQxIVd8/PEGxNXazX4k5DyZar97DoXbKxu7e9LbqSyjBOng7yRLne9pbtgZYwMw6UxhuWjOyT7Bs91Lpgld8Jt8gM4/+tKGmMMhZTNPIJmqE/9sdYEAyA==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(376002)(366004)(346002)(396003)(39830400003)(136003)(26005)(103116003)(478600001)(5660300002)(55236004)(86362001)(66476007)(66556008)(66576008)(316002)(66946007)(186003)(36756003)(6266002)(7126003)(3450700001)(83380400001)(9686003)(8676002)(8936002)(52116002)(33964004)(6916009)(2906002);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?zHfIIFcp+gnOQY8S0dPqtsew/BmQMJlNeUow3y+7dpyOiVVIaVQ5YU8NnoRx?=
=?us-ascii?Q?ZavW5pruY9Vynql9oWc4vKeaa/CG7s1EAT0c1t0jfHA/LIb7dY4Q48Nz9BAi?=
=?us-ascii?Q?FkpKw6HQZIUh3R8xVVyVfXbEoBj1z135eVVs1lmx6chMUIiIzdXKtAzeUQ0M?=
=?us-ascii?Q?rixo9UPnSrIAlEvtl/jj2ZaHOVElLzzII5r5OczYK05hPs6L9BN9SdkM3cc8?=
=?us-ascii?Q?a32dN8xavoNS45p3fSXSO/Bp+HlulBJaAHvM/I9LLH22JjzrPXu/gIXf57XE?=
=?us-ascii?Q?HU0FhhOLrr6NZII6jKPiDQHiy/cvT/04kdAiFENJJlN6aCKHBVsrEMBuV96l?=
=?us-ascii?Q?9XDU+i0AOhbMgczQrvj7Q6F0Tz3+QijTaFUR8io8RXQMMGH0djEq/XLnPRsV?=
=?us-ascii?Q?5r93oMJ+C2/+yjP0ASASeP/KL7P/hFfpML+pfjT40b/EE+p3J2Nu4uGkOQo3?=
=?us-ascii?Q?4pv8VohbPIpAme6AOYQWvhwydjTlRlb3Ar/1Rjo/5xVorXuSY7yyc+glOS/N?=
=?us-ascii?Q?bYxnN30SQRC5r3trWvgNXpEm2wRz2vvWFv/MqBqhNCBnNfU/A5Hl3e3IGY43?=
=?us-ascii?Q?m7HstEaq1Jtr//uc4i2ikMGFsf5+ksYW9FXK4U8ktN4uKvvWIezceEVy9d7g?=
=?us-ascii?Q?Q5r420LIVmdisWR4R1U0z8r9b61A+P79dpxLo2Iq4XChgwC2fMkBX7xdZlkd?=
=?us-ascii?Q?wEI+ZT+o1TI3x0SJ8Aarf9ZiGo11+G8fbFILPXEqVUzLLwjZmOhmKc4U3aSm?=
=?us-ascii?Q?cyt4gDjMaz1qc8QQKc15xZ+ioXm/58mA9+4iCVgYQUp92ub1qf9BChA0MQtC?=
=?us-ascii?Q?a3UC0FCeXmvwPOG9336aHkYOMuRoirrMgFp+V7AO9KxKsKTHD/6trhTnXfxE?=
=?us-ascii?Q?373A5miXnV6UiR8XGBF0l/XxSB1xYZq1BQ9hDmmxua/AreEylLeBeTofrD8M?=
=?us-ascii?Q?kM3wcdE8U5WwYWge0TFxptzKbnv2BdPwzUmnFzXP5sAtoWaVpxAz42XTlYGM?=
=?us-ascii?Q?6PYO?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: de5762c4-ea9a-4435-8459-08d8bb66b510
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:08:29.0930
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: EkTxLy8Lxv100NQvUdhG4Jjwp9/X1NU0lI4Q9nM6G146z8yyPmJwN4gejecRnrjHtrrtMRNwtzzgBqsZ17BWsA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MEAPR01MB4277
New reply for the ticket #QUE00000269
we have deployed the same .net app thru UI choose interactive tty (ti).after
deployment n clicked logs UI wasnt responsive, then refresh the page, its back
to normal. its docker 20.10 with swarm enabled
docker logs/events comamnd isnt responding too

Bala Natarajan
Reply to this email to submit an update.

I'll close this issue and reference it in https://github.com/portainer/portainer/issues/3749


Add basic pkg-config info

Hi @gquintard,
Thank you for the patch! I was missing the patch level information on the version. I've made a little modification to display it. Everything is now merged!
Here:
https://github.com/SpiderLabs/ModSecurity/blob/a3980bbea16d0a68fbb01fb2cf9320b48ed1a7f8/modsecurity.pc.in#L8
And here:
https://github.com/SpiderLabs/ModSecurity/blob/a3980bbea16d0a68fbb01fb2cf9320b48ed1a7f8/configure.ac#L25-L26
https://github.com/SpiderLabs/ModSecurity/blob/a3980bbea16d0a68fbb01fb2cf9320b48ed1a7f8/configure.ac#L207-L208

Thanks!

Revisiting that one, shouldn't
Cflags: -I@includedir@/@PACKAGE@

just be
Cflags: -I@includedir@/

?
in the first case you include modsecurity/modsecurity.h, in the second one modsecurity.h. The former seems more right to me.


[SPARK-33071][SPARK-33536][SQL][FOLLOW-UP] Rename deniedMetadataKeys to nonInheritableMetadataKeys in Alias

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/30488. This PR proposes to rename Alias.deniedMetadataKeys to Alias.nonInheritableMetadataKeys to make it less confusing.
Why are the changes needed?
To make it easier to maintain and read.
Does this PR introduce any user-facing change?
No. This is rather a code cleanup.
How was this patch tested?
Ran the unittests written in the previous PR manually. Jenkins and GitHub Actions in this PR should also test them.

cc @cloud-fan and @Ngone51 can you take a look please?

Had a short offline discussion with @cloud-fan. Let me just rename the variables to make to address my own concern with a minimized fix.

Test build #132475 has started for PR 30682 at commit 402b5cf.

Test build #132479 has started for PR 30682 at commit 40c580e.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37077/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37081/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37081/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37081/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37077/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37077/

Merged to master and branch-3.1.

Thanks @cloud-fan and @Ngone51

Test build #132479 has finished for PR 30682 at commit 40c580e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132479/

Test build #132475 has finished for PR 30682 at commit 402b5cf.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132475/


Streamlit

merging the streamlit branch back to main. Project is considered 95% complete. Items remaining to implement are auto-population of tables for boundary conditions, mannings roughness, and levees.


gcc failed to build on 10.13

Please always follow these steps:

[x] Confirmed this is a problem with brew installing one, specific formula (not cask) and not every time you run brew? If it's a general brew problem please file this issue at https://github.com/Homebrew/brew/issues/new. If it's a brew cask problem please file this issue at https://github.com/Homebrew/caskroom/homebrew-cask/new
[X] Ran brew update and retried your prior step?
[X] Ran brew doctor, fixed all issues and retried your prior step?
[X] Ran brew gist-logs <formula> (where <formula> is the name of the formula that failed) and included the output link?
[ ] If brew gist-logs didn't work: ran brew config and brew doctor and included their output with your issue?

Please note we will close your issue without comment if you delete or do not fill out the issue checklist and provide ALL the requested information.
To help us debug your issue please explain:

What you were trying to do (and why)
What happened (include command output)
What you expected to happen
Step-by-step reproduction instructions (by running brew install commands)

New Formulae
To get a new formula into Homebrew please file a Pull Request.

https://gist.github.com/shatteringlass/21fb3c03bf39931fa7be9d698413282f
c/c-ing @fxcoudert as demanded :)

Please note we may immediately close your issue without comment if you do not fill out the issue template and provide the requested information.

I don't know if this was automatically closed, but it's unfortunate that gist-logs --new-issuedoesn't open a new issue with the required template in the body. anyway, manually fixed, hope you can reopen this.

I think this is an upstream issue. I have reported it to GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
Can you test if building without the --with-jit --with-nls options changes anything?

I tried building without options. Here is the related gist-logs:
https://gist.github.com/4b14d36a6bcc4656471e46a08e792bad https://gist.github.com/4b14d36a6bcc4656471e46a08e792bad

Il giorno 10 ago 2017, alle ore 15:21, FX Coudert<EMAIL_ADDRESS>ha scritto:
I think this is an upstream issue. I have reported it to GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
Can you test if building without the --with-jit --with-nls options changes anything?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Homebrew/brew/issues/3035#issuecomment-321548962, or mute the thread https://github.com/notifications/unsubscribe-auth/AFOjWECjAHIVPOYGohkiB5El_BHRBo9eks5sWwPfgaJpZM4Oykip.

I am going to close this issue here. The problem has been reported, I can reproduce it myself but only intermittently. It seems related to makefile parallelisation.

@shatteringlass one more question: does your High Sierra machine use the HFS or the APFS filesystem?

FWIW, no trouble here on 10.13 with the merge of gcc 7.2.0 today. I declined the update to APFS for now though so I'm still on old trusty HFS+.
==> Summary
🍺  /usr/local/Cellar/gcc/7.2.0: 1,487 files, 284.3MB, built in 37 minutes 36 seconds


small patch , rip duplicate full release

QOL: Gem Cannon now also Exhausts Gems from cards in Stasis, and gems in sockets now actually do go to the Exhaust pile.
QOL: Character Boss' Cards' beta art is now independantly togglable(Should cover most cards, report if any isn't functional).
QOL: Branch no longer consumes your Vigor if you choose to get block from it.
QOL: Miscellaneous text and visual fix.
BALANCE: Neow's Hermit ability nerfed from adding 2 random curses to adding a single Decay.
BALANCE: Nibble and Lick damage buffed: 1→4.
BALANCE: Unupgraded Prismatic Spray damage buffed: 2→3 for more initial pickability.
BALANCE: Upgraded Prismatic Barrier Block nerfed: 4→3 to counter the goodness of multi-dexterirty utilizability a bit.
BALANCE: Chrono-Boost buffed: (1 Strength) , 1 Strength per 12 cards played → (2 Strength) , 2 Strength per 12 cards played.
BUGFIX: Deflecting Bracer no longer functions when you're in Defensive Mode.
BUGFIX: Bottled Anomaly & Bottled Black Hole & Blank Card now functions like how the players would expect for Unknown cards.
BUGFIX Split: Specialist is now seeded.
BUGFIX: Fixes taking damage from the second tackle duplicated by Duplicated Form when you have Protective Gear.
BUGFIX: Fixed a rare bug where the game crashes if you play a Strike&Defend from characters other than the Bronze Automaton, which gained Encode in a previous Back to Basics event. (Fixing by only allowing adding Encoding to Automaton's Strikes and Defends)
BUGFIX: Fear No Evil now functions against Character Bosses.
BUGFIX: Ghost Lash & Specters Wail's Afterlife damage effect is now modified correctly by modifiers (like Vulnerable, Weak, Strength, Vigor).
BUGFIX: Fixed Character Bosses' energy panel popping up during an event before the fight starts (captive hero colosseum event).
BUGFIX: Fixed Act 3 Defect generating a Lightning Orb by Storm+Defragment with extra damage than it's supposed to.
BUGFIX: Fixed Woman in Blue's Intangible potion not functional to Non-attack damage.

@Mwallx Currently this PR has a lot of conflicts, can you resolve these on your end?  I'm likely to get some things wrong if I try it myself with this many.  Not sure if a PR was merged in the wrong order or what happened here.

I've made mine compatible with the main stream, didnt realize there are more with ez's, should be easy to be done in 1hour.

I've made mine compatible with the main stream, didnt realize there are more with ez's, should be easy to be done in 1hour.


Fix compilation error

While fixing and refactoring the code, the Arduino car system was accidentally given an extra brace, so it no longer compiles.

Working on this using the branch compilation-fix (which is the branch in the above-referenced merge request).

Completed in above-referenced pull request.


Looking way to directly modify an entry from the server itself, specifically a unique id counter.

I am looking way to directly modify an entry from the server itself, specifically a unique id counter.  I am guessing that all should be done with requests, but I am wondering if I can update several distinct key values directly.  A few variables I want to keep in the bd.json itself to keep synchronization.  FE, { "variables": { "uid_counter": 0 } } as the db.json and then in the server be able to let new_uid = ++variables.uid_counter  from some callback triggered by the server.  For example generating a new record / entry.  Maybe an example or api documentation with a little more detail or which code files to examine to figure these things out.  The examples in the readme are great for just getting things working but I can't find any detailed documentation for the specific features and how to use them.

I am guessing it's something to do with https://github.com/typicode/lowdb, but still figuring it out.  pointers appreciated.  Am I going in the right direction.  lowdb looks simple enough but how to tap that directly inside jsonserver?


For types annotated with ApiControllerAttribute, consider making complex type parameters FromBody by default

As part of producing, more opinionated APIs via ApiControllerAttribute we can assume any complex type parameter in your action without binding information is interpreted as FromBody. This will reduce the amount of typing \ clutter in user code:
[ApiController]
public class OrdersController
{
   // ...
   [HttpPost]
   public IActionResult Create(Book book); // Assumes FromBody

   [HttpPut]
   public IActionResult Update([FromQuery] Book book); // Opt out
}

We could add a switch to ApiControllerOptions to disable this behavior globally.

The proposal here is to do:

Complex types are [FromBody] by default
Parameters that match the route are [FromRoute] by default
Any other parameters are [FromQuery] by default

We think this is the most reasonable possible convention we could have and guides you towards good practices.

No one has raised a significant objection to this so we're going to start working on it 👍


Possible to run 2 instances at same time?

Is it possible to run 2 instances of this for example if you have 2 or more bitmex accounts?

Yes, you can achieve this by either (off the top of my head)
a) Use two different browsers (e.g. Firefox and Chrome). This is probably the best solution, since API keys will be remembered.
b) Use one browser, but open another instance in incognito mode. This has the inconvenience of API keys not being remembered for the incognito instance after you close it.

How do I get a second instance to run in a separate browser? Im on windows. I am opening 2 command prompts and running npm run startup. When I do this in the second command prompt I just get an error.

You only need to run one instance of the server (npm run startup). It can handle multiple keys at a time.
After you have started the server instance, open a second browser and go to the URL http://localhost:3006, type in your second API key and you should be good to go :)


3/10/2020 Publish

Docs Build status updates of commit 331a5d8:
:clock10: Full build: the average full build time is 34 min(s) 31 sec(s), this is based on the last 12 build(s) for this repository.
:warning: This is a FULL build due to a recent Docs Build service upgrade, normally no action is required on your part. In the result you find subsequent builds still performing full builds, please contact your repository admin to manually perform a full build on the 'live' branch. For more detailed info, please click here.

Docs Build status updates of commit 331a5d8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/speech-service.md
:warning:Warning
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)
Details

docs-ref-services/service-bus.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

docs-ref-services/speech-service.md

[Warning] Uid(microsoft-cognitiveservices-speech-sdk) has already been defined in docs-ref-services/speech-service.md.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How to execute code

How can I implement the training quantum circuit, what are the places that need to be modified in the code, thank you

你好能加好友交流一下嘛

vx：real_hg

Hi. Sorry about the late response. I've been busy lately. I will update more detailed Readme file later.
If you want to train quantum circuits, you can run  result.py  with desired parameters (unitary Ansatz, encoding methods etc.). It will benchmark the training result and save it as result.txt  in result folder.

Thank you, by the way, I would like to ask the reason and limitation that only binary classification can be used in the paper, and multi-classification cannot be performed.
Thanks!

Tak Hur @.***> 於 2022年3月22日 上午1:40 寫道：

Hi. Sorry about the late response. I've been busy lately. I will update more detailed Readme file later.
If you want to train quantum circuits, you can run result.py with desired parameters (unitary Ansatz, encoding methods etc.). It will benchmark the training result and save it as result.txt in result folder.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

--
------ By mail1.ncnu.edu.tw https://www.ncnu.edu.tw
------------------------------------!!!方便快速的電子郵件仍無法免除延遲或遺失,
重要或具時效之訊息請勿以電子郵件為唯一傳達方式!!!
請尊重智慧財產權! 請勿開啟不明來源郵件!
請使用公務信箱收發公務所需資訊,  以免資訊外洩!
--
------ By mail1.ncnu.edu.tw https://www.ncnu.edu.tw
------------------------------------!!!方便快速的電子郵件仍無法免除延遲或遺失,
重要或具時效之訊息請勿以電子郵件為唯一傳達方式!!!
請尊重智慧財產權! 請勿開啟不明來源郵件!
請使用公務信箱收發公務所需資訊,  以免資訊外洩!

Yes. Multi-classifier can be generated by repeating binary classification. Or maybe you can construct more direct multi-classifier from parameterised quantum circuit, but we haven't tried implementing it.
The purpose of this work was to compare various parameters (unitary ansatz, data encoding etc). So we used the simplest model, which is binary classification.

Thanks!
I have another question, the convolutional filters L in the figure, if I want to adjust L to 2, where should I modify it in the code?

No worries!
Yes, the number of layers L can't be easily modified, unlike other tunable parameters.
Unfortunately, you will have to do this manually. If you look at QCNN.py, you can see the details of QCNN structure. You can increase the L by simply repeating the layers (which is by default set to 1). You need to use different weights (parameters) for the added layers, so you will have to multiply the total_params by L in Training.py