ampy.pyboard.PyboardError: failed to access COM5

C:\Users\79966\Anaconda3\python.exe C:\Users\79966.PyCharm2019.1\config\plugins\intellij-micropython/scripts/microupload.py -C C:/Users/79966/PycharmProjects/untitled2 -v COM5 C:/Users/79966/PycharmProjects/untitled2/main.py
Connecting to COM5
Traceback (most recent call last):
File "C:\Users\79966.PyCharm2019.1\config\plugins\intellij-micropython/scripts/microupload.py", line 138, in
main(sys.argv[1:])
File "C:\Users\79966.PyCharm2019.1\config\plugins\intellij-micropython/scripts/microupload.py", line 56, in main
board = Pyboard(port)
File "C:\Users\79966\Anaconda3\lib\site-packages\ampy\pyboard.py", line 147, in init
raise PyboardError('failed to access ' + device)
ampy.pyboard.PyboardError: failed to access COM5

Hi,
I have a same problem, same error. with anaconda3

FLASH : problem
REPL : ok
thank you

Sorry for my late reply. Does the "Detect" button work in the MicroPython settings next to the "Device path" on your screenshot? Does it determine the same COM device path that you specify manually? I suppose that your Windows assigned a different COM number to your device. Sorry I don't have a Windows machine available at this moment, so I cannot reproduce this issue.

Closing this issue as obsolete. Please feel free to comment it if the problem persists.


fix: error rather than panicking if unable to send response in Axum integration

Because of the awkward setup of spawning into a pinned thread, the Axum integration tries to send its response through a channel (due to the weird Send/Sync workaround currently in place) and unwraps awaiting the receiver
https://github.com/leptos-rs/leptos/blob/0ff1e279a2774730ab01f28d2c794217de35a19d/integrations/axum/src/lib.rs#L332
Panicking here (or anywhere in these handlers) is a bad idea, and can cause difficult-to-reproduce issues.
I'm wondering if replacing all these with something like this might be a good idea.

Sure, I don't think it hurts. I've yet to see someone hit these, but a better experience is good if the do


Tutorial Page appstudio-devspace-fiori-create.md Issue. PROD

Tutorial issue found: https://github.com/sap-tutorials/Tutorials/blob/master/tutorials/appstudio-devspace-fiori-create/appstudio-devspace-fiori-create.md contains invalid tags. Even though your tutorial was created, the invalid tags listed below were disregarded. Please double-check the following tags:

products>sap-btp-cloud-foundry-environment

Affected server: PROD

Hi @MichaelCzcz ,
Which tag should be used instead?
Regards - Raz

The tag as such is correct, but the name space "products" is not. It has been replaced by "software-product" many months ago.

Pushed to production and create PR.


Advisory Board: First member's label disappears on narrow views

BUG
Current Behavior
As you resize the window, the first item in each gallery loses its figure__body.
https://cl.ly/3N233H0D0l37
Seems to be something with the overflow rule and where that element gets pushed to.
Desired Behavior
All names/labels should stay visible for all viewport sizes
Steps to Replicate
Replicated easily on Chrome; haven't checked other pages with similar galleries.
Why This Matters
Because people have names, even in small windows
OS/Browser (optional)
Def latest Chrome / OS X
Relevant Screenshots + Links
https://cl.ly/3N233H0D0l37

cc @DFurnes


Test multiple name auctions going in parallel

[x] verify that only the highest bid can close each day
[x] verify that a new bid on highest bid postpones closing of the highest bid by 24 hours
[ ] verify that no bids close if there isn't one
[x] verify balances of bidders are properly billed and refunded when outbid
[x] verify suffix can create *.suffix accounts

See existing test at end of eosio_system_tests.cpp

Fixed by #3206


Parses "cloves" ingredient incorrectly

Parses "1 tsp cloves" as an amount "1 tsp clove" with no ingredient. Should be "cloves" as an ingredient.

This one has caused a lot of problems, and I thought I'd solved it but clearly not. Training a model from the latest develop branch seems to do the right thing now, so it will be fixed in the next release. I'll write some tests to make sure it doesn't get missed again.

0e4246732f add some tests to check that the various uses of "cloves" are parsed correctly.
cf65f1687d adds a new model that passes these tests.
This is still in the develop branch for now, but I'll close this issue as completed.


Add a wiki: Dominion Strategy

Link to origin wiki:

https://dominionstrategy.miraheze.org/
https://dominioncg.fandom.com/
https://dominionstrategy.fandom.com/

Link to destination (independent) wiki:

https://wiki.dominionstrategy.com

Hello! My name is Matt. I'm the server admin of the Dominion Strategy Wiki. Our wiki is the home for information on Dominion, the deckbuilding board game by Donald X Vaccarino.
We have had problems with clones of our content showing up on the three sites above. The sites above are in various states of disrepair. The content on those sites has been stolen from our wiki without permission, so I'd like to get a redirect up to lead people back to the source of the most up-to-date content.
Our wiki is independently funded by sponsors on Patreon and we put in a lot of work to keep our content available, well-structured, and accurate. Thank you for running Indie Wiki Buddy!

Thank you for the submission! As of v3.11.0 (available for Chrome, soon to be available on Firefox), IWB redirects from dominioncg.fandom.com to wiki.dominionstrategy.com. We don't currently support redirecting from Miraheze, but I do see that the Miraheze wiki has gone private so hopefully it's defunct and a redirect is no longer needed.
I also didn't add dominionstrategy.fandom.com since that wiki seems to have been cleared out, but I notice there is still some activity there, so I'll go ahead and add that as an additional redirect origin in the next update.


Future of service worker tooling

I know that there's a decent number of folks who follow the issues here, so I wanted to provide a link to some of the team's thinking about the next-generation of service worker libraries: https://github.com/GoogleChrome/sw-helpers/issues/61
We don't have any current plans to end support for sw-toolbox (or sw-precache, for that matter), and we know there are a significant number of web applications that depend on its continued functionality.
But that issue outlines our general thinking about a rearchitecture of the libraries, along with some snippets of code, and is what we expect much of our new development efforts to focus on.

Would you be open to me adding a short, but consistent message on both sw-precache and sw-toolbox calling out that we're working on the next version of the libraries over in sw-helpers?
Fwiw, React don't currently do this in their main repo for Fiber support (https://github.com/facebook/react/) but given we're moving work to another repo there may be value in doing so.


BFCP RFC4583

Hey thanks for this. This all looks sensible to me, but is there any chance you could add a test sdp with some bfcp parameters? Not a fan of having untested syntax :slightly_smiling_face:

added test.

Released in<EMAIL_ADDRESS>


Update Simple Edge Discovery flows

Clarified the first scenario and added and additional scenario for Simple Edge Discovery

@crissancas thanks, changes made and committed to this PR - please can you review?

Thanks Kevin!

Re-opened as it was closed without merge - @crissancas please can you merge to main? Thanks!

Sorry Kev! My mistake, I didn't realize.


hype EthTurin with QV

Bounty
Deora sponsors EthTurin. explain what we do + QV + track.
Scope

content related to QV and EthTurin.
announce the talk with Giovani.
why use QV for hackathons?

Deliverables

twitter posts
talk with Giovani (how qv helps governance)

Gain for the project
Roles
bounty gardener: name / share
bounty worker: name / share
bounty reviewer: name / share

post content, possible themes:

what is qv?
how is it helpful?

mention in talk:

give basic voting instructions, how the app works

[ ] ask ethTurin for conversion from referrer

first tweet posted:
https://twitter.com/deora_earth/status/1252253242559467520

second tweet posted:
https://twitter.com/deora_earth/status/1252631509992902656


MERAKI_DEBUG environment variable doesn't work

upstream: https://github.com/cisco-open/terraform-provider-meraki/issues/131

fixed in upstream version


Misc bug fixes

Fixes #56 - Omit preceeding "0" for minutes and hours (unless description is time of day).  For example:
"Every 05 5 minutes, at 03:00 PM, Monday through Friday".
Fixes #49 - Properly handle step values with ranges; this handles expressions like 2/3, 4/3.
Fixes #46 - Properly handle expressions that contain both DOW AND DOM parts.

Removal of multiPartRangeFormat parameter of GetSegmentDescription together with the ComaMinX0ThroughX1 resource that was introduced in #61 breaks range tests for the Romanian language.


Add Json Content Type when create a request with body

By default when you add a body to a request, a header with Content-Type and application/json is added too.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Non overlapping controls

@msDestiny14
Hi! This is the PR for https://forum.babylonjs.com/t/non-overlapping-gui-linked-controls/24610
PG to test: https://playground.babylonjs.com/#BMW0VQ

Will be going over this soon carefully. Might do some testing locally myself as well. :)

Will be going over this soon carefully. Might do some testing locally myself as well. :)

I didn't touch any existing functionality so should be OK. Keeping my fingers crossed... 🤞

I approve. My only request if you can open an additional PR @RolandCsibrei for the documentation.
Feel free to at it to the GUI section and include a playground demo with it working. (Your current demo in the description is outdated since you updated the function names)
You can add me to the documentation PR. :)

Yep 😊
On Tue, Nov 2, 2021, 8:19 PM Pamela W @.***> wrote:

I approve. My only request if you can open an additional PR @RolandCsibrei
https://github.com/RolandCsibrei for the documentation.
Feel free to at it to the GUI section and include a playground demo with
it working. (Your current demo in the description is outdated since you
updated the function names)
You can add me to the documentation PR. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Babylon.js/pull/11365#issuecomment-958095468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYKGHLRGCIPQSGFQ46LFZ3UKBBUZANCNFSM5HCSLHHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Fix typos on the Connection page

Just fix a few typos and broken links on the Connection page.

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

@alex2304 Thank you for signing the Contributor License Agreement!

Thank you!


Update 01_quickstart.md

Switched to the official spaceflights since the required changes in Kedro are merged.
Description
Updated documentation.
PR Checklist

[ ] Tests added
[ ] Changelog updated

Tests are failing due to missing coverage reporter token. This happens always when PR is submitted from fork. We should fix the actions workflow to skip this step in such case.


Kserve deployment certificate issue - tls: failed to verify certificate: x509: certificate signed by unknown authority\nError from server (InternalError)

/kind bug
What steps did you take and what happened:
[I am trying to deploy kserve on bare metal Kubernetes v1.26.12 cluster, but getting certificate validity related issues. ]
Error log:
"/opt/test/kserve/kserve_manifest/kserve_manifest.yaml"], "delta": "0:00:00.675632", "end": "2024-04-27 05:27:25.793010", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2024-04-27 05:27:25.117378", "stderr": "Warning: Detected changes to resource inferenceservices.serving.kserve.io which is currently being deleted.\nError from server (InternalError): error when creating "/opt/test/kserve/kserve_manifest/kserve_manifest.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nError from server (InternalError): error when creating "/opt/test/kserve/kserve_manifest/kserve_manifest.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s\": tls: failed to verify certificate: x509: certificate signed by unknown authority", "stderr_lines": ["Warning: Detected changes to resource inferenceservices.serving.kserve.io which is currently being deleted.", "Error from server (InternalError): error when creating "/opt/test/kserve/kserve_manifest/kserve_manifest.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s\": tls: failed to verify certificate: x509: certificate signed by unknown authority", "Error from server (InternalError): error when creating "/opt/test/kserve/kserve_manifest/kserve_manifest.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s\": tls: failed to verify certificate: x509: certificate signed by unknown authority"], "stdout": "namespace/kserve created
: failed calling webhook \ "webhook.cert-manager. io" :
failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:442/mutate?timeout=IOs\" :
t Is: failed to verify certificate: 1509: certificate has expired or is not
yet valid: current time is before 2024-04-26 T from server (Internal Error): error when creating
Internal error occurred: failed callin
g webhook \ "webhook.cert-manager. :
What did you expect to happen:
No certificate issue, also the issue is intermittent, not reproduced every time. But once it's reproduced, we are not able to proceed.
What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

certificate-manager: v1.13.0
Istio Version: 1.17.0
Knative Version: 1.11.0
KServe Version:0.11.0
Kubeflow version: NA
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm] : bare metal
Minikube/Kind version: Kubespray - Kubernetes v 1.26.12
Kubernetes version: (use kubectl version):  1.26.12
OS (e.g. from /etc/os-release): rhel 8.8/Ubuntu 22.04

It is a clean installation. There is no other cert manager operator. Only the one we deployed as part of kserve deployment.
Currently we reprovisioned the system and issue is not reproduced, once issue is reproduced will provide more detail on it.
On a high level it seems a time sync issue since logs complaining about certificate validity has not started.
Do you have any high-level direction to investigate for the issue?
Also, we mostly observe this issue in rhel and not seen in ubuntu.

Thanks for the feedback.
@Jooho as you've worked with certs in the past, do you have any thoughts to add on this?

we observe  this issue on :
os：Centos 7.6
内核：3.10.0-1160.el7.x86_64
k8s集群：v1.26.9
deploy kserve from the Kubeflow Manifests v1.8.0
the err logs like :
Revision "sklearn-iris-predictor-00001" failed with message: Unable to fetch image "harbor.devops.win/kserve/sklearnserver:v0.11.1": failed to resolve image to digest: Get "https://harbor.devops.win/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority.


fix ArticleType's attachmentUrl when attachmentHash does not exist

The bug was introduced in #284 .
Querying ArticleType's attachmentUrl will trigger Cannot read properties of undefined (reading 'split') error.

The root cause is that for non-image articles, attachmentHash is null. However, we send null to MediaManager to generate URL for attachmentUrl field.
This PR:

Returns null for attachmentUrl if attachmentHash is null
Introduces a test case that will fail if this PR is not implemented

Coverage increased (+0.02%) to 87.549% when pulling e4fc699c8ed2c6c9421af6b95069e58ab0adcbea on fix-url-resolver into 6540c6cbb03e0166a125820344a6e8da5e744d61 on master.


Add pod label to specify builder-base image URI used for CI runtime

Setting a ci-build-image label with the builder-base image as value to be later consumed for setting an env var CI_BUILD_IMAGE (aws/eks-distro-prow-jobs#301)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/close


--skip is ignored in forge script

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
19d69f277de96f621d930cdb767a9693c55ae8e1
What command(s) is the bug in?
forge script
Operating System
Linux
Describe the bug
It seems that --skip works with forge build to skip compilation, but it does not work with forge script.
> forge build --skip "*"
[⠊] Compiling...
No files changed, compilation skipped

> forge script scripts/foundry/Deploy.s.sol:Deploy --skip "*"
[⠆] Compiling...
[⠊] Compiling 282 files with 0.8.24
...

I tried multiple combinations (e.g. --skip "*", --skip "*.sol", --skip "src" --skip "scripts").
I have a Docker container in which I run multiple forge scripts. What I want to achieve is: Run forge build when building the container, then run the script (without building again) when I run the container.

Running forge build without --skip flag will compile all contracts in project, and then forge script will just read cached script artifact, solving your usecase.
--skip flag on forge script doesn't really work, but currently forge script on its own is already smart enough to detect and compile only targeted script contract

Thanks for your reply! Unfortunately that's not my experience, currently forge script seems to always recompile all my contracts, do you know what might be the reason?
Here's the output when I run these commands on the host machine (not in Docker):
> forge --version
forge 0.2.0 (26e6e57 2024-04-28T00:19:12.405804000Z)

> forge build
[⠊] Compiling...
[⠒] Compiling 297 files with 0.8.24
[⠆] Solc 0.8.24 finished in 17.78s
Compiler run successful!

> forge script scripts/foundry/TomlTest.s.sol:TomlTest
[⠊] Compiling...
[⠘] Compiling 282 files with 0.8.24
[⠊] Solc 0.8.24 finished in 16.44s
Compiler run successful!
Traces:
...

Possibly the same issue as #7379.

Turns out it was a configuration issue, didn't realize I had force = true in foundry.toml.


Update kodi.rb

update to version 15.1

Thank you for the contribution. It was merged directly as fd3263dc1b14fd9ac6b322481ce47d134897b79c to keep commit history cleaner. Your contribution is still credited to you.


How to configure an argument

So I have the schema something like:
public class List
{
  public Guid Id {get; set;}
  public string Number {get; set;}
  //other props
}

The schema generated uses Id as an argument:
list ( id ID! ) List
I want to remove id and use Number  instead as argument. How can I achieve that?

I hope some of these links help explain things. This one describes why the id field is created.
You can turn that off - for all list fields - with the SchemaBuilderOptions
services.AddGraphQLSchema<DemoContext>(options =>
{
    options.AutoCreateFieldWithIdArguments = false;
});

However if you want to just change that one field. I hope this link will help. Basically you replace the field.
services.AddGraphQLSchema<DemoContext>(options =>
{
    options.PreBuildSchemaFromContext = schema =>
    {
        // Customise schema
        schema.Query().ReplaceField(
            "list", // field name
            new { number = ArgumentHelper.Required<string>() }, // define field arguments
            (ctx, args) => ctx.List.Where(l => l.Number == args.number).FirstOrDefault(), // resolve expression
            "Return a list element by number" // description
         );
    };
});

@lukemurray
Thanks this helps.


feat: ⚡ Ukraine relief feed

feat:⚡ first implementation of the ukraine feed

Closes #43

@xat It's not super clean because I could not tailored the request only in graphQL, to get only the tokens array based on the factors I used (supply >1, verified, Shares > 50% for the relief contract). The js part might surely be better but I think it's a good starting point

@xat @AliaK77
So what do we do? I just rebased it


Failed to build Qt 5.9.2 in parallel(make -jN && N > 1)

Your Windows build number:  (Type ver at a Windows Command Prompt)
Windows build number: 10.0.16299.19 and ubuntu 16.04

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)
Build qt 5.9.2 from source.
configure command:
current dir /somewhere/qt5-build
qt5 src dir /somewhere/qt5

../qt5/configure -opensource -confirm-license  -release -make libs -make examples -optimized-qmake -platform linux-g++-64 -no-qml-debug -no-directfb -no-kms -qt-xcb -qt-zlib -qt-libjpeg -qt-libpng -qt-harfbuzz -qt-xkbcommon -qt-freetype -qt-pcre -no-icu -prefix /home/jc_yang/non-specified -skip 3d -skip activeqt -skip androidextras -skip canvas3d -skip charts -skip connectivity -skip datavis3d -skip declarative -skip doc -skip enginio -skip gamepad -skip graphicaleffects -skip imageformats -skip location -skip macextras -skip multimedia -skip networkauth -skip purchasing -skip quickcontrols -skip quickcontrols2 -skip remoteobjects -skip script -skip scxml -skip sensors -skip serialbus -skip serialport -skip speech -skip translations -skip virtualkeyboard -skip wayland -skip webchannel -skip webengine -skip websockets -skip webview -skip x11extras -skip xmlpatterns
after successful config,
run make -j16 or make -j8 to start build

What's wrong / what should be happening instead:
I expect build to be success. but it failed with weird error condition.
below is excerpt of the build failure output:
"In file included from /usr/include/limits.h:25:0,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/limits.h:168,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/syslimits.h:7,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/limits.h:34,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zconf.h:422,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zlib.h:34,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zutil.h:31,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/crc32.c:31:
/usr/include/features.h:367:25: fatal error: .moc/sys/cdefs.h: Invalid argument
compilation terminated.
In file included from /usr/include/features.h:391:0,
from /usr/include/limits.h:25,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/limits.h:168,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/syslimits.h:7,
from /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed/limits.h:34,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zconf.h:422,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zlib.h:34,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/compress.c:9:
/usr/include/x86_64-linux-gnu/gnu/stubs.h:10:27: fatal error: .moc/gnu/stubs-64.h: Invalid argument
Makefile:17491: recipe for target '.obj/crc32.o' failed
In file included from /usr/include/stdio.h:27:0,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/gzguts.h:39,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/gzwrite.c:6:
/usr/include/features.h:391:23: fatal error: .moc/gnu/stubs.h: Invalid argument
compilation terminated.
make[3]: *** [.obj/crc32.o] Error 1
compilation terminated.
make[3]: *** Waiting for unfinished jobs....
Makefile:17442: recipe for target '.obj/compress.o' failed
make[3]: *** [.obj/compress.o] Error 1
Makefile:17732: recipe for target '.obj/gzwrite.o' failed
make[3]: *** [.obj/gzwrite.o] Error 1
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:219:0,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zconf.h:448,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zlib.h:34,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zutil.h:31,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/adler32.c:8:
/usr/include/x86_64-linux-gnu/sys/select.h:45:23: fatal error: .moc/bits/time.h: Invalid argument
compilation terminated.
Makefile:17395: recipe for target '.obj/adler32.o' failed
make[3]: *** [.obj/adler32.o] Error 1
In file included from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/zutil.h:38:0,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/deflate.h:16,
from /mnt/d/third_party_libs/qt5/qtbase/src/3rdparty/zlib/src/trees.c:37:
/usr/include/stdlib.h:42:30: fatal error: .moc/bits/waitstatus.h: Invalid argument
compilation terminated.
Makefile:17986: recipe for target '.obj/trees.o' failed
make[3]: *** [.obj/trees.o] Error 1
make[3]: Leaving directory '/mnt/d/third_party_libs/qt-host-build/qtbase/src/corelib'
Makefile:224: recipe for target 'sub-corelib-make_first' failed
make[2]: *** [sub-corelib-make_first] Error 2
make[2]: Leaving directory '/mnt/d/third_party_libs/qt-host-build/qtbase/src'
Makefile:48: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory '/mnt/d/third_party_libs/qt-host-build/qtbase'
Makefile:48: recipe for target 'module-qtbase-make_first' failed
make: *** [module-qtbase-make_first] Error 2"

make -j1 or just plainly make do run successfully. Just parallel build failed pretty fast.

I met the same issue while building another big project, and used strace to trace g++'s sys calls, here are some logs:
[pid 23421] open("bla_bla_bla/config.h", O_RDONLY|O_NOCTTY) = 4 [pid 23421] fstat(4, {st_mode=S_IFREG|0777, st_size=11046, ...}) = 0 [pid 23421] read(4, "/* +----------------------------"..., 11046) = 11046 [pid 23421] close(4)                    = 0 // some useless logs... [pid 23421] open("bla_bla_bal/base.h", O_RDONLY) = 4 [pid 23421] fstat(4, {st_mode=S_IFREG|0777, st_size=3690, ...}) = 0 [pid 23421] read(4, "/* +----------------------------"..., 4096) = 3690 [pid 23421] read(4, "", 4096)           = 0 [pid 23421] write(2, "In file included from "..., 294In file included from bla_bla_bla/common.h:16:0,                  from bla_bla_bla/bla_bla_bla.cpp:12: bla_bla_bla/base.h:43:26: fatal error: bla_bla_bla/version.h: Invalid argument
This log has been modified manually to remove my company's secrets
please take a look at the fstat and read calls:
The first pair of calls are normal, you can see they have same number on size parameters.
The second pair of calls are the point causing this problem, the file size if 3690bytes, but trying to invoke syscall read with 4096 bytes.

I met the same issue when I compile my project with "-jN" that is compiled well on another computer. Then I compile without "-jN", it's ok. Strangely, after the success, I compile the project with "-jN" again, and it works well.
So ,you can make  without "-jN".

16299 so probably #2448 and friends. Try the workaround and see if that helps. Or upgrade to 17035 if you can, and let us know if the problem persists.

If 16299.64 contains the fix for #2448 then I can confirm they are not the same bug.
I've just upgraded to .64 and the the same error still exist.

No, 17035 as it says in #2448....

@therealkenc this workaround works perfect for me. thank you so much for the reply.


Apply the PrettyContextBuilder to ControllerBroker.

Relates to issue #1393

Dependent on https://github.com/kubernetes-incubator/service-catalog/pull/1408


Support wildcard certificates with ACMEv2

On January 27 letsencrypt will make star certificates fully available via the ACME v2 protocol.
Are you planning on adding support for this?

Please see https://github.com/zenhack/simp_le/issues/101#issuecomment-372773310 for updates on the upstream issue, since the v2 endpoint has finally been released to production.

@almereyda as told in my first message on this issue and on the simp_le issue you mentioned, wilcard certificates requires dns-01 challenge support, which is absent from simp_le (and there are no plans to add it).

I am curious. Can't simp_le be replaced with another components that could handle dns-01 challenge? If not, what are our options? Can't we hack the configuration a bit on our end to support it?

It could, letsencrypt-nginx-proxy-companion is pretty much "just" bash automation around simp_le and nginx-proxy, there is nothing preventing someone from re-writting it to use another ACME client and provide additional features. As usual with small open source projects the only real issues are the amount of work necessary and the time it takes.
I've been thinking for a while about doing a fork of this project using certbot instead of simp_le but it's pretty far from a drop-in replacement as the two behave in very different ways. I lack the time to do more than experiment a bit with the idea once in a while.
As for other options, the most serious is probably switching to a bigger project like https://github.com/containous/traefik
To be honest I have my doubts about the long term viability of the nginx-proxy / docker-gen solution as it's now extremely hard to get contributions merged to those projects (mostly due to the fact that their creator is very busy working at influxdb, I guess. That's understandable).

@buchdag thank you for your reply.

The simp_le issue mentions that they are planning to support the DNS-01
challenge soon'ish.
On 15 March 2018 at 10:51, Dragnucs<EMAIL_ADDRESS>wrote:

@buchdag https://github.com/buchdag thank you for your reply.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/319#issuecomment-373319869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABka_GISKEcuTX9F-FpUc2P_lNQPU3rIks5tejmzgaJpZM4RmAk2
.

Errr no it does not.
We (zenhack and I) said on that issue that ACME v2 support is planned (we said nothing about when, and it might turn out to be harder than expected) and that dns-01 is out of scope.
Again dns-01 challenge is required to obtain a wildcard certificate through the Let's Encrypt ACME v2 endpoint, but they are not one and the same thing: implementing ACME v2 does not imply implementing dns-01 challenge at all.

@buchdag Thanks for your contribution!!! Traefik works really fine with it!!! I am doing some tests around it and it seems pretty stable as well. Since I have a couple servers running this repo It will take a couple months to release something usefull, but thank in advance!

I’m sorry, I didn’t mean to say that. I’m not a native English speaker so..
haha
I’ll try to dig into the code and see if I can add a hint to the error when
I have free time :)
Sorry again for what I said, and thanks to everyone for the contribution to
the awesome project!
On Wed, Apr 25, 2018 at 2:23 PM Nicolas Duchon<EMAIL_ADDRESS>wrote:

@BirkhoffLee https://github.com/BirkhoffLee "expect this to work"
"useless error" ... nice tone there.
BTW the "useless error" actually comes from simp_le, not from this
container's code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/319#issuecomment-384173713,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHxUf9jjsuyAqnU95EOfvJuJM1sQCOPEks5tsBZ9gaJpZM4RmAk2
.

My bad, I did not realize you were a non native english speaker. 😅
You're right with the fact that some warnings about unsupported features (as of now) like ACME V2 endpoints and wildcard certificates should be added. I'll try to add this to dev this week.

Thanks 😄
On Wed, Apr 25, 2018 at 2:50 PM Nicolas Duchon<EMAIL_ADDRESS>wrote:

My bad, I did not realize you were a non native english speaker. 😅
You're right with the fact that some warnings about unsupported features
(as of now) like ACME V2 endpoints and wildcard certificates should be
added. I'll try to add this to dev this week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/319#issuecomment-384178784,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHxUf2i0qWuzak52cgRseaj98kZ9vYikks5tsByhgaJpZM4RmAk2
.

hi team, how long we can support ACME v2 feature?

@buchdag actually traefik use lego as LE lib

While wildcard is not implemented, there's any workaround to minor work effort on setting up a wildcard configuration on nginx all the other benefits of this image? e.g. Can I manually generate a wildcard certificate ant let know "letsencrypt-nginx-proxy-companion" to use these custom certificates instead of try to create/renew new ones?
I tried to have my custom certificates on certificates path but they are still replaced by the single domain certificate that "letsencrypt-nginx-proxy-companion" generates. I can in a ugly way limit the permissions to read only for my custom certificates but still, the let's encrypt api will be called if I need to restart the docker which may enter in a out of limit requests to letsencrypt.
Meanwhile, it would be great if this will be implemented shortly or if I really need to consider other solution :(
Thanks in advance.

letsencrypt-nginx-proxy-companion does not "use" certificates. It handle their creation, renewal, and some symlink work so that nginx-proxy can pick them up.
The application you want to use your externally obtained certificates with is nginx-proxy and that amount to following their existing doc and doing a naming or symlinking job similar to what the companion do.

I understand your point and makes sense. Though, I'm not able to have a mixed configuration with domains that are under letsencrypt-nginx-proxy-companion management and domains that are not, having in mind that jwilder/nginx-proxy is the same and using the same certs dir for all domains. What's happening is that letsencrypt-nginx-proxy-companion is removing my custom certificates since it considers that they are unsed.
log:
letsencrypt-nginx-proxy-companion    | Symlinked domains: yyy.com xxx.com
letsencrypt-nginx-proxy-companion    | Enabled domains: xxx.com
letsencrypt-nginx-proxy-companion    | Disabled domains: yyy.com
letsencrypt-nginx-proxy-companion    | Some domains are disabled. Check them to remove unused symlinks.
letsencrypt-nginx-proxy-companion    |
letsencrypt-nginx-proxy-companion    | Checking domain yyy.com:
letsencrypt-nginx-proxy-companion    | Checking yyy.com.crt - removing.
letsencrypt-nginx-proxy-companion    | Checking yyy.com.key - removing.
letsencrypt-nginx-proxy-companion    | Checking yyy.com.dhparam.pem
letsencrypt-nginx-proxy-companion    | Checking yyy.com.chain.pem - removing.
letsencrypt-nginx-proxy-companion    | Unused domains checking is finished.

docker-compose.yml:
services:
  letsencrypt_nginx_proxy_companion:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-nginx-proxy-companion
    volumes_from:
      - load_balancer
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock:ro"
      - "${LETSENCRYPT_CERTS_PATH}:/etc/nginx/certs:rw"
    environment:
      - NGINX_DOCKER_GEN_CONTAINER=load_balancer
  load_balancer:
    image: jwilder/nginx-proxy
    container_name: load_balancer
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./docker/load-balancer/nginx-proxy-vhost.d:/etc/nginx/vhost.d
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - /usr/share/nginx/html
      - "${LETSENCRYPT_CERTS_PATH:/etc/nginx/certs:ro"
    labels:
      com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    environment:
      - ENABLE_IPV6=true
    restart: always
  website:
    container_name: website
    image:  ${IMAGE_WEBSITE}
    ports:
      - 5555:80
    environment:
      - VIRTUAL_HOST=xxx.com
      - LETSENCRYPT_HOST=xxx.com
      -<EMAIL_ADDRESS>  custom_certificates_website:
    container_name: custom-certificates-website
    image:  ${IMAGE_CUSTOM_CERTIFICATES_WEBSITE}
    ports:
      - 5556:80
    environment:
      - VIRTUAL_HOST=yyy.com,*.yyy.com

Ok that's a bug, it should not happen. Do you mind opening a separate issue so we can work toward fixing it ?

FWIW: I forked this a while back to use acme.sh instead of simp_le explicitly so I could do dns-01 validation via AWS Route53.  I haven't tried using wildcard certs with my fork, but if someone really wanted to they could try: https://github.com/speshak/docker-letsencrypt-nginx-proxy-companion/tree/acme.sh

In between, I found this - I hope it will help someone:
https://github.com/adferrand/docker-letsencrypt-dns

Is there any development on the problem ?

Support for wildcard certificates will come eventually but isn't planned anytime soon.

More accurately, the plan so far is:

switch to an ACME v2 compatible version of  simp_le before the november deadline
then switch from simp_le to acme.sh in the months following that
when the acme.sh based version is stable enough, start working on DNS-01 challenge and wildcard certificate support

I really hope that I'll be able to get to the last point in the next ~4 months but I really can't predict when I'll have free time and how much.

Does this mean all of you who want www.example.com and example.com to work use both here:
VIRTUAL_HOST=example.com,www.example.com
LETSENCRYPT_HOST=example.com,www.example.com
?

Does this mean all of you who want www.example.com and example.com to work use both here:
VIRTUAL_HOST=example.com,www.example.com
LETSENCRYPT_HOST=example.com,www.example.com
?

Well yes, but since I guess example.com and www.example.com will point to the same thing a CNAME record in your DNS settings is the more elegant way to solve this.

A pre-release with ACME v2 support is available as tag v1.12-rc.1. I can't guarantee this is fully production ready yet.
This is just part of the upcoming switch to ACME v2 protocol prior to the November 1st deadline I alluded to in my previous message, it does not bring support for wildcard certificates.
I had way less free time than expected since the end of July, so things are going rather slowly 😒

Just like to say that I've just tested the tag v1.12-rc.1 and according the logs, it generated the certificate with no hiccup whatsoever. So far so good.
Congratulations on this amazing tool to automate production environments!

Confirm that v1.12-rc.1 works with ACME v2 . I needed to upgrade:
While it was possible 2 days ago to create certificates with ACME v1, today I was not able to create any new certificate with ACME v1 - maybe duedate is not really beginning of november?

See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430/3

We will be beginning brown-outs for new ACME v1 registrations for the production environment for the following dates of this year:
October 10th to October 11th
October 16th to October 18th
October 31st onward
We will be permanently disabling new ACME v1 registrations in the production environment on October 31st.

I can confirm that as of today ACMEv1 was not supported for me anymore:
ACME server returned an error: urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

ACME v2 support has been merged to master in #590
latest is now compatible with ACME v2  and tagged version v1.12 is now available.
stable should be updated to v1.12 by the end of the month.

Hi, I am discovering this project. I see why the issue has been reopened but I also see there is a v1.12 solution for it. Is this finally solved? Thanks for sharing!

This is just part of the upcoming switch to ACME v2 protocol prior to the November 1st deadline I alluded to in my previous message, it does not bring support for wildcard certificates.

Now following suite with the release of v2 through #510 and #719, it appears even more possible to use dns-01 ACME v2 challenges with the companion.
In https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/issues/510#issuecomment-747608623 @pini-gh communicated the existence of a fork --- that happens to find itself at https://github.com/pini-gh/docker-letsencrypt-nginx-proxy-companion in opposition to the link provided there --- that implements the requested change here. See the comparison in https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/compare/v2.0.1...pini-gh:dns-01-challenge
Would this deem a suitable moment to issue a Pull Request from this PoC and test and extend it against the maintainer's expectations?

@almereyda as usual I'd really like to give users a roadmap and stick to it, but you saw how well it went the last time I tried that.
Things I can say for now:

yes, now that #510 / #719 are done, dns-01 challenges support will be worked on
there is some CI/CD and code refactoring work that I want to do before that
also, improvements on logging and debugging
I'll certainly start with @pini-gh fork and work with him on this if he wants to and has time to spare
it will probably be way harder to create a working integration test for this feature than the feature itself

Hello, any news regarding DNS challenge support?

Is there a way to customize executed acme.sh when I want to do wildcard with dns-01 challenge, I'll use if-else per domain to append TOKEN and change to dns-01 challenge

Hi, what about #916, any plans to merge it?

Bumping this issue since not a single comment has been posted in response to the PR #916 which seems to implement wildcard certificates.
Is it planned to be merged ? Or is this feature simply not planned to be implemented by the acme-companion devs for other reasons ?

@Miladiir @Hexalyse the PR #916 is unfortunately too much specific to cloudfare (because it's checking for the existence of CF_Token environment variable).
I have created a PR (#1022) for adding generic support for DNS challenges which is fully working for "non-wildcard" domains with minor changes to the code base and being not specific to any provider.
Based on what I have read in the #916 , the PR #1022 may not require a lot of additional work in order to support wildcards domains, because wildcard certs are issued based on DNS challenge : I think it only require to update the functions.sh as it's done in #916, but to be confirmed by @buchdag

Are there any updates on this? This feature is gonna help us a lot

If anyone is looking for a working alternative, here's an example of how to combine nginx-proxy with adferrand/dnsrobocert: Script to deploy certificates generated with DNSroboCert to jwilder's nginx-proxy. It's working very well, feel free to use it in any way that you see fit.

For anyone searching for wildcard certificate support in nginx-proxy:
I've created a docker image which is based on go-acme/lego and works perfectly well with nginx-proxy.
It supports all of their DNS providers and auto updates the certificates using cron before they get invalid.

I've created a docker image which is based on go-acme/lego and works perfectly well with nginx-proxy.

I confirm, thanks a lot for this image! The documentation being extra slim, I share my docker-compose.yml file here, with ovh api and wildcard certificate generation. if you have another registar/dns provider, you can check the proper environment variables here : https://go-acme.github.io/lego/dns/
version: "2.4"

services:
  nginx-proxy:
    image: nginxproxy/nginx-proxy:alpine
    container_name: nginx-proxy
    restart: always
    ports:
      - "80:80/tcp"
      - "443:443/tcp"
    volumes:
      - certs:/etc/nginx/certs:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      proxy-network:

  lego-acme:
    image: cilenco/lego-cron-wrapper
    container_name: lego-acme
    command: >
      --accept-tos<EMAIL_ADDRESS>--dns ovh
      --domains=*.example.com
    environment:
      - RUN_ARGUMENTS=--run-hook=/app/deploy
      - RENEW_ARGUMENTS=--renew-hook=/app/deploy
      - OVH_APPLICATION_KEY=<appkey>
      - OVH_APPLICATION_SECRET=<appsec>
      - OVH_CONSUMER_KEY=<conskey>
      - OVH_ENDPOINT=ovh-eu
    volumes:
      - certs:/app/certificates
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./deploy.sh:/app/deploy
    networks:
      - proxy-network-internal

  website:
    image: httpd:alpine
    container_name: website
    restart: always
    volumes:
      - ./website:/usr/local/apache2/htdocs/:ro
      - ./httpd.conf:/usr/local/apache2/conf/httpd.conf:ro
    environment:
      - VIRTUAL_HOST=example.example.com
    networks:
      - proxy-network

volumes:
  certs:

networks:
  proxy-network-internal:
    external: true
  proxy-network:
    external: true

Please note that the LETSENCRYPT_HOST disappear.

This took way, way longer than I intended, but support for DNS-01 challenge and wildcard certificates is coming, see #1137


error in creating app

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Closing as duplicate of #6698, #6696, and #6695


Add support for virtualHost for S3

Description
Add support for virtualHost for S3
Signed-off-by: Gregory Dymarek<EMAIL_ADDRESS>Issues Resolved
https://github.com/chef-cookbooks/aws/issues/390
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Thanks @gregd72002


[ipsec] Retry logic for failed/deleted SAS

Problem:
I just got a chance to do a screenshare with one of our open source users who reported IPSec problems. Debugging his setup, the tunnel between two of his servers had some problems. The packets from one end were reaching the other server, but the response was not reaching. Due to this after 5 retries, the SA got deleted.
Solution:
We should have a new goroutine in IPSec which is monitoring the status of all the SAs and expect them to be in "ESTABILISHED" state. If they are not and deleted, currently there is no logic to retry/reinitiate the SA but we should re-initiate the connection.

Thanks for digging this up. We are also experiencing this issue.

Fixed in ipsec:0.2.0 with image rancher/net:v0.13.2, targeted for v1.6.11 release.

Was able to reproduce the issue using rancher/net:v0.13.1 where when  connection between 2 hosts was lost and then restored after few minutes , ipsec connection between the 2 host never get re-established.
Steps that were followed to simulate the issue:
Drop connection between 2 hosts using iptable rules
iptables -I FORWARD -d <hostip> -p udp -m udp --dport 500 -j DROP
iptables -I FORWARD -d <hostip> -p udp -m udp --dport 4500 -j DROP
After 5 retransmit errors , ipsec connection between the 2 hosts gets dropped
swanctl --list-sas | grep <hostip> would be return no rows
Restore  connections between 2 hosts by deleting the rules that were created to drop connections.
Even after connection is restored , connection between containers from these hosts continues to be broken. ipsec connection between the 2 hosts does not get re-established. swanctl --list-sas | grep <hostip> would be return no rows.
When the same tests were done using rancher/net:v0.13.2  (using rancher/server:v1.6-development) , once the connection was restored between hosts , connection between containers from these hosts is restored in the next few seconds.
Even when connectivity between the hosts are down , ipsec connection between the 2 hosts get re-established in few seconds after they get dropped due to retransmission errors.

I have recently run into the same issue as well after upgrading to v1.6.10

@ibrokethecloud the issue has been fixed in v1.6.11 release.

same issue in v1.6.14
2/8/2018 1:43:35 AMRefer to router sidekick for logs
2/8/2018 5:50:01 PMRefer to router sidekick for logs
2/8/2018 5:50:01 PMmkfifo: cannot create fifo 'f': File exists

mkfifo: cannot create fifo 'f': File exists is not a message which should cause problems, if you experience issues, please file a new issue with the behavior and the used versions.

root@hs228151:~# docker ps
CONTAINER ID        IMAGE                             COMMAND                  CREATED
e99f1eb1b9f7        rancher/storage-nfs:v0.8.5        "start.sh storage ..."   14 hours ago
56f05f2eede7        rancher/net:v0.13.7               "/rancher-entrypoi..."   14 hours ago
6a832fce5247        rancher/net:v0.13.7               "/rancher-entrypoi..."   14 hours ago
1f3bf6a1c032        rancher/dns:v0.15.3               "/rancher-entrypoi..."   14 hours ago
2d90eb1d9279        rancher/net:holder                "/.r/r /rancher-en..."   14 hours ago
6480fb27e13f        rancher/metadata:v0.9.5           "/rancher-entrypoi..."   14 hours ago
5c0be9b1d93c        rancher/healthcheck:v0.3.3        "/.r/r /rancher-en..."   14 hours ago
e6014b14d3ff        rancher/network-manager:v0.7.19   "/rancher-entrypoi..."   14 hours ago
54b3a5b61acb        rancher/net:v0.13.7               "/rancher-entrypoi..."   14 hours ago
745ad5ce707f        rancher/agent:v1.2.9              "/run.sh run"            14 hours ago
0d3c02051280        rancher/server:stable             "/usr/bin/entry /u..."   14 hours ago
root@hs228151:~# docker logs -f  2d90eb1d9279
Refer to router sidekick for logs
^C
root@hs228151:~# docker exec -it 2d90eb1d9279 /bin/bash
root@2d90eb1d9279:/# sh -c echo Refer to router sidekick for logs; mkfifo f; exec cat f
mkfifo: cannot create fifo 'f': File exists
same issue in v1.6.14  rancher/net:v0.13.7

mkfifo: cannot create fifo 'f': File exists

This is not an error! This message can be ignored.


ubsan/memsan fix.

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Bug Fix

When getting data from ColumnArray https://github.com/yandex/ClickHouse/blob/master/dbms/src/Columns/ColumnArray.cpp#L144
we can get an invalid pointer when current array is empty. (due to left padding of podarray, it should be some global readonly address)
Theoretically we'd like to get the same pointer value in https://github.com/yandex/ClickHouse/blob/master/dbms/src/Columns/ColumnArray.cpp#L151 . However, since we have a dedicated ZeroValueStorage in hash table. The pointer of zero lengthed arrays becomes nil after placing into the agg states hash table, which leads to UBSan and MemSan failure.

This bug can be reproduced using the following query
SELECT groupUniqArray(v)
FROM
(
    SELECT
        1 AS id,
        [2] AS v
    UNION ALL
    SELECT
        1 AS id,
        [] AS v
)
GROUP BY id

clickhouse build command is
cmake -DSANITIZE=memory -DCMAKE_C_COMPILER="clang-8" -DCMAKE_CXX_COMPILER="clang++-8" -DCMAKE_CXX_FLAGS="-stdlib=libc++" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_CXX_FLAGS="-O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls" -DCMAKE_C_FLAGS="-O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls" -D ENABLE_HDFS=0 -D ENABLE_CAPNP=0 -D ENABLE_RDKAFKA=0 -D ENABLE_ICU=0 -D ENABLE_POCO_MONGODB=0 -D ENABLE_POCO_NETSSL=0 -D ENABLE_POCO_ODBC=0 -D ENABLE_ODBC=0 -D ENABLE_MYSQL=0 -D ENABLE_EMBEDDED_COMPILER=0 -D USE_INTERNAL_CAPNP_LIBRARY=0 -D USE_SIMDJSON=0 -DENABLE_READLINE=0 -DENABLE_ORC=0 -DENABLE_PARQUET=0 -DUSE_CAPNP=0 -DUSE_INTERNAL_ORC_LIBRARY=0 -DUSE_ORC=0 -DENABLE_SSL=0 ..
``

Actuall we can also make all StringRef zero value storages pointing to a global empty string.

Great, thanks for investigating!
Your test case reproduces the error for me, we probably should add id to the tests. It has a shorter form using the new Values table function: select groupUniqArray(v) from values('id int, v Array(int)', (1, [2]), (1, [])) group by id.
So, is the core cause that we compare uninitialized end to uninitialized pos here?
https://github.com/yandex/ClickHouse/blob/master/dbms/src/Columns/ColumnArray.cpp#L166
I think it would be good to achieve that the pos is always well-defined, by pointing it to a global empty string as you suggest. Or maybe even making it nullptr in such cases? That is, require that if StringRef.size == 0, then StringRef.data == nullptr.

I guess it's because ZeroValueStorage is not initialized. https://github.com/yandex/ClickHouse/blob/master/dbms/src/Common/HashTable/HashTable.h#L223
. I'm not sure how memsan reasons about this failure, but I remember the ubsan error is due to the invalid pos = 0xffffffffffffffff  and pos + field_size overflows.

Looking at emplaceIfZero, I don't see where the constructor is called for zero value Cell at all. Is this correct?
Before, there was an explicit initialization of zero StringRef in GroupUniqArray:
https://github.com/yandex/ClickHouse/pull/6729/files#diff-9281c6b3757a84abfb5643adf2bb48d2L251
but I removed it in the key holder PR -- don't remember why.
Anyway, it looks like it was a hack, and we should just properly call the constructor for zero Cell, the same way we do for all other Cells in emplaceNonZeroImpl.

yeah, initializing it properly also fixes the bug.

I'd prefer to call the Cell constructor in emplaceIfZero, because it would be only initialized on demand, and also would properly initialize complex cells like ClearableHashTableCell, which is not initialized to all zeros but has a version field.

@akuzm you just caught me in the middle :) . That commit was supposed to run a CI test but I soon realize it's too slow so I did locally...

I cannot reproduce the thread san build failure locally using
docker run -it --rm --net=host -v /ci/tsandebs:/package_folder  yandex/clickhouse-stateless-test

Is it some flaky test?

Is it some flaky test?

The logs are truncated, looks like some CI failure.

Ok, how can I trigger a retest without force push new stuff?

The thread sanitizer CI failure looks unrelated. The performance test didn't finish, but it shouldn't be influenced because we didn't change much. Will merge as is.


feat: New Tree chart

SUMMARY

Adds new Echart's Tree chart from
Check pr https://github.com/apache-superset/superset-ui/pull/1018
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

lint issues in zrender module


Merge contributions Paul

Please check if I removed all temporary copies of your work

You sure you want to merge all of the domains aswell??

Did not think of that, but it should be fine because the origins are mentioned


Mean Q calculations different from paper (or incorrect?)

Hi,
The code around calculating the mean Q value that is written to results.csv (ie the code starting around line 410 of rl_glue_ale_agent.py) has a couple of issues I think.  The main one is that it outputs the mean Q values across all actions instead of the mean of the max action Q values like the Deep Mind paper does. I believe from the look of the code that the intention was to output the mean of the max action Q values.
The other, related, issue is that the mean is calculated across only 100 phis instead of across 100 batches of 32 phis like the code seems to want to do. The code asks for
self.holdout_data = self.data_set.random_batch(holdout_size * self.batch_size)[0]

and that returns something of shape (3200, 4, 80, 80), but then it iterates with:
for i in range(holdout_size):
    holdout_sum += np.mean(self.network.q_vals(self.holdout_data[i, ...]))

pressumably assuming that random_batch indexed each batch separately and that q_vals takes a batch at a time, but random_batch just numbers each phi set separately instead and q_vals only takes one example. eg looking at the shape of self.holdout_data[0, ...] it gives (4, 80, 80). network.q_vals then returns something of shape (18,) (ie one for each action).
I believe the following code should work
        for i in range(holdout_size * self.batch_size):
            holdout_sum += np.max(
                self.network.q_vals(self.holdout_data[i, ...]))

        self._update_results_file(epoch, self.episode_counter,
                                  holdout_sum / (holdout_size * self.batch_size))

(Thank you very much for releasing this, by the way. I am still struggling through the theano parts in cnn_q_learner.py. It does my head in. Do you think it'd be worth switching to the cuDNN theano wrapper instead of the cuda_convnet now that that's been released?)

Unfortunately, I could'nt get any improvement from the suggested change after 15 epochs?
The numbers in results.csv are all roughly the same as the first epoch, and if I play the .pkl file from the 15th epoch it looks like its got Alzheimer's?
(Just out of curiosity, I wonder what your views on adding Monte Carlo Tree search to selecting training data are? It seems to significantly improve performance, there's a few well documented implementations. Its interesting too.
Deep Learning for Real-Time Atari Game Play Using Offline Monte-Carlo Tree Search Planning

The changes don't touch the learning code. They just change what is recorded to results.csv.
(15 epochs is not enough to see much, at least for breakout. At 60 epochs it should be pretty clear though)

Hi, sorry! Yes, I understand that script a bit better now.
I'm trying the changes now with Pong, that should be quick? I just wonder if you have a working ROM of Othello? Or a game to do quick tests with?
One last thing, is there a simple way of restarting the training of a saved network? It takes 36 hrs to run 100 epochs of Breakout and it got upto a per episode average of around 60.
I tried to restart the training, by replacing the environment and agent process start up lines p3 and p4 in ale_run.py with,
p3 = subprocess.Popen(['./rl_glue_ale_experiment.py', '--epoch_length', '50000'], env=my_env)
p4 = subprocess.Popen(['./rl_glue_ale_agent.py', "--nn_file",                        "/home/ajay/PythonProjects/deep_q_rl/_01-02-14-20_0p0001_0p9/network_file_100.pkl"], env=my_env)
Which loads the network and restarts the training fine, but its still not managed to get above the 60 level? Is this to be expected? Is it because the history of the dataset class is empty when the experiment is started again?
Output of Results.csv
epoch	num_episodes 	total_reward	reward_per_episode
1	10	439	43.9
2	10	445	44.5
3	10	459	45.9
4	9	421	46.7777777778
5	9	406	45.1111111111
6	10	420	42
7	10	400	40
8	9	462	51.3333333333
9	9	423	47
10	9	440	48.8888888889
11	10	438	43.8
12	10	396	39.6
13	9	380	42.2222222222
14	10	397	39.7
15	9	431	47.8888888889
16	8	459	57.375
17	10	418	41.8
18	11	346	31.4545454545
19	11	342	31.0909090909
20	11	401	36.4545454545
21	8	460	57.5
22	12	294	24.5
23	9	477	53

@alito Thanks for pointing this out.  I've addressed it in master by changing
self.holdout_data = self.data_set.random_batch(holdout_size * self.batch_size)[0]

to
self.holdout_data = self.data_set.random_batch(holdout_size)[0]

and increasing holdout size to 3200.  I think this is a bit clearer because the batch size doesn't really have anything to do with this calculation.

@AjayTalati I don't remember where I found my ROM files, but if you google around you should be able to find any game you are interested in without too much difficulty.
It looks like your approach to resuming learning is correct.  It may be that performance doesn't improve because the network has reached a local maxima.


Implement wlr output management v1

This first lets PixmanRegion32 and Box be instantiated using pointers to objects that already exist, rather than creating new instances of these structs when instantiating the class.
The the third commit adds handlers for the various structs and methods in wlroots'
wlr_output_management_v1.h. This lets compositors create output managers
and process client requests to change the output layout and
configuration of each output. The output layout and output interfaces
have been extended somewhat to allow for the interaction between these
and the output manager objects.

I was going to submit another PR but some of the new changes depend on some from the old PR so I've just merged the newer commits into this PR, hope you don't mind.


Configure gdbpath in settings.json

Is there a way to configure "gdbpath" in settings.json and not just the launch.json for the project?
launch.json could overwrite the default specified in settings.json when defined on a project basis.

no this isn't possible because of the way how debug extensions work in vscode. Only way to change it permanently is by adding your gdb path to your actual system PATH variable


Store user data in duk_context

Hello,
I'm maintainer of the CivetWeb web server.
I am currently trying to add server side JavaScript support by integrating Duktape (https://github.com/civetweb/civetweb/issues/194). CivetWeb already has Lua support, and I want to integrate Duktape in a similar way.
One key feature I used in the Lua integration is upvalues pushed by C functions, but I did not find any equivalent in Duktape yet. I would have multiple instances of the interpreter in the same process and need to attach some user data to C functions to identify the instance.
E.g.: for Lua, I do something like this in C:
1) push a function name
2) push values required to identify the instance within the C function (upvalues)
3) push a function pointer
4) bind these things together, so the C function can be called in the scripting language

In the implementation of the C function, I can access the values pushed in step 3.
In duktape I found duk_push_c_function + duk_put_prop_string - they seems to do 1+2+4, but not 3.
So, is there a way to add upvalues?
Is there a way to add some global user data to the duk_context - e.g. duk_set_user_data(context, void * data) done after duk_create_heap_default, and a corresponding duk_get_user_data(context) to call inside a C function called from the script?
If not, I think I could implement such a function on my own.
Are you interested in patches (pull requests), in case I need to make some?

This guide section may be useful: http://duktape.org/guide.html#programming.9
Once you have pushed the C function on the value stack, you can add ordinary properties to the function object pushed to identify the particular instance. In the C function you can then access the properties like:
duk_push_current_function(ctx);
duk_get_prop_string(ctx, -1, "myFunctionIdentifier");

Another much more level mechanism is the "magic" value of a function; it's a plain integer associated with the Ecmascript function instance which you can then access in the C function (duk_get_current_magic()).
As for the global user data, Duktape has three different "stashes": heap, global, thread. The stash objects are accessible from C code but not ordinary Ecmascript code, and can be used to store various auxiliary values.
So, you could store a void pointer into the global stash (or heap stash, if that's more appropriate; one heap may have multiple global object environments), e.g. as:
duk_push_global_stash(ctx);
duk_push_pointer(ctx, (void *) myPointer);
duk_put_prop_string(ctx, -2, "myUserData");

and then read it back later similarly as a property read.

Thank you for your quick reply.
The function "magic" seems to be only int16_t, but I need to store a pointer. I would prefer not to use an extra lookup table if possible.
Now, I used this code:
	duk_push_global_stash(ctx);
	duk_push_pointer(ctx, (void *)conn);
	duk_put_prop_string(ctx, -2, civetweb_conn_id);

after creating the interpreter state, and to get the value again in a C function
	duk_push_global_stash(ctx);
	duk_get_prop_string(ctx, -1, civetweb_conn_id);
	conn = (struct mg_connection *)duk_to_pointer(ctx, -1);

This seems to do what I need.
I'm doing this quite often - is it efficient this way?
If possible, I would like to store more C functions together with some values (numbers, strings, ...) in a table. I suppose this can be done with a sequence like duk_push_global_object, duk_push_object, then duk_push_c_function + duk_put_prop_string for all functions, duk_push_string + duk_put_prop_string for all strings, and so on, then finally duk_put_prop_string to give the global instance of the table/object a name.
Is it possible to add some "hidden" values to a table/object too? (values only accessible in C, not in the scripts). Is pointer added by a duk_push_pointer + duk_put_prop_string in the object accessible from the script somehow?

If you don't want it accessible to script, you have to use an invalid UTF-8 string for the property name (starting with a \xff byte).  put_prop_string() is the same thing as doing obj[str] in script, so if you start it with a FF byte it won't be accessible through normal means.

A bit more detail on what @fatcerberus said: http://duktape.org/guide.html#internalproperties
These internal properties will merge with ES6 "symbols" down the road. Right now these internal properties cannot be accessed by standard Ecmascript code but it's possible to craft a string using a buffer to gain access - so they're protected from accidental access but not intentional access. This will change later on for better sandboxing.

@bel2125 If you need to store a pointer, then probably easiest is to use an internal property on the Ecmascript function object (pushed by duk_push_c_function()) as I described.
As for performance, the cost is the same as a property lookup anywhere else - not terribly fast or terribly slow.

Thanks, it works according to your hints.


Can't get the networked version of scream working

When I first download scream, I assumed that the IVSHMEM version would be faster (because there wouldn't be any networking involved) and it worked perfectly, but as I later found out the normal version has noticeably less latency. When I tried to switch back though, I couldn't get it to work. Here's what I tried:

Removing the IVSHMEM entry from regedit
Completely reinstalling driver with restarting VM multiple times in between

The guest is a windows 10 VM running in qemu, it's using a virtio networking interface.
The host in running linux mint 19.2 and I'm using the included pulseaudio receiver.
I can reach the guest from the host and also the host from the guest via a ping command.
What happens:
The receiver starts (no output, doesn't crash) but I can't hear any output. It does open a sound output though on the host.
Let me know if you need more information about this issue.

If you are using multicast, Windows might be sending it over the wrong interface.
Does it work with unicast? Any firewall on the Linux side?

I haven't tried it with unicast as I read somewher that it is much worse quality (Can try it later though) I disabled the firewall on both linux and windows.

With which options do you run the receiver? (Also you need to use the networked receiver - just making sure :) ). You might want to specify the interface with -i option.
You can also do a tcpdump on the interface pointing to the guest, like so:
tcpdump -pni vethX port 4010
where "vethX" is the name of the interface pointing to the guest. When sound plays, you should see a stream of UDP packets.

I'm attempting to use the networked version as well (as IVSHMEM didn't work for me either,) and I am receiving no UDP packets.

I use this command to start the receiver:
./scream-pulse  -i virbr0
Here's a tcp dump:
https://pastebin.com/EL3wSsbd
command : user@comp:~$ sudo tcpdump -pni virbr0 port 4010 > Downloads/tcpdumb.txt
If I understand correctly, there is data coming through but some reason the player doesnt play it.

Yeah that is sound coming in all right. Next step is to check if the receiver gets and plays it.
Run the receiver in strace (as root), like:
strace ./scream-pulse -i virbr0
You might have to install strace.
Once you start playing sound, the output should show hectic activity.
If that happens, and you still don't hear a thing, maybe the stream is at volume zero, or you have another local problem.

Here's the output of the strace: https://pastebin.com/Bsda4jA6
I see a lot of not found errors, but I don't see any 'hectic' activity. Could it be that apparmor is blocking the utility?

Something is wrong with the receiver then right?

Yeah some firewalling (or apparmor) could be the issue. The receiver does not get the packets that show up on the wire.

Here are some tips for troubleshooting in a Windows only environment (I used Windows 10).
Download a packet sniffer, an easy to use one would be this: https://www.nirsoft.net/utils/smsniff.html
Or Microsoft Network Monitor (not as easy to use): https://www.microsoft.com/en-us/download/details.aspx?id=4865
Start the packet sniffer on both machines and play sound. First, check the machine that is broadcasting the sound. You should see an UDP broadcast stream to "<IP_ADDRESS>:4010" with lots of activity, several hundred kb/s. Then, check the machine that shall receive the sound. You should see the same. If not, temporarily disable any Software Firewall and see if that makes it work.
The sending machine needs to allow outgoing UDP traffic on port 4010, but the Windows firewall allows all outgoing traffic by default, so this should work right away.
On the receiving machine, all incoming traffic is blocked by default, so you need to create an inbound rule to allow UDP traffic on port 4010 for the playback software. The ScreamReader software that is included with Scream should automatically request such a rule when you first start it. Check your firewall settings whether such a rule exists.
To play back the stream, VLC player did not work well for me. It refused to play the multicast stream, only the single cast worked, and it was extremely choppy. The ScreamReader software worked great.

I think I'm having the same issue. I'm running a similar setup, with a Windows 10 VM in QEMU, and I initially used IVSHMEM assuming it would be better. I've since discovered that it has horrendous latency, and am trying to switch to the networked version. I can't get it to work. There's no audio from the receiver. I've removed the UseIVSHMEM registry entry, tried reinstalling Scream on Windows, tried messing with unicast IPs and ports, I just can't get it to work.
I'm running Fedora Silverblue 31, which doesn't have AppArmor. Instead, it has SELinux, but my SELinux Troubleshooter tool doesn't detect any issues with Scream.

A couple of years ago I remember having troubles making the network version work. The IVSHMEM version wasn't a thing then.
At the beginning I wasn't seeing packets from the VM all the time, because I was using 2 different network cards, one for the public internet and one for host-guest communication. Windows was picking one card at random at boot. The solution was to set the host-guest network card with a lower priority. Later unicast was implemented, that's another way to fix this.
The second issue I was having was the linux firewall. With the network card priority fixed I was seeing all the incoming packets but I couldn't make it work for the life of me.
I disabled UFW and messed a lot with iptables for nothing.
In the end I discovered that on a recent update ubuntu installed and activated firewalld.
A simple systemctl stop firewalld and scream started working.
Moral of the story is that if you see packets with tcpdump but the app doesn't receive them then you should really check the firewall.

I am also having the same issue. Works through ivshmem but latency is too high for comfortable gaming. The only reason I fell back to using ivshmem was actually this exact issue described here to begin with.
I can see the UDP multicast on wireshark but scream can't read it.

Well, I finally switched to arch, and the problem is fixed for me. Sadly I don't know what fixed it.

Alright, I give up. I've tried to get this working for about 5 hours now.
The Windows VM is setup to use unicast <IP_ADDRESS>:4010. I'm getting packets through the bridge just fine (virbr1). The Scream command is: ./scream -u -i virbr1 -p 4010 -o pulse and using it with -P makes no difference. I can see audio being played in the Windows VM and there's a Scream output device in Pulse. I also get Switched format to sample rate 48000, sample size 32 and 2 channels. once some audio is playing so it seems Scream is getting something. I've checked the audio levels, everything is fine - just no audio. Any ideas?

@bcHelix if you get the "switched format" message than you are receiving the audio packets. The format is in the header of each packet.
Can you try -o alsa instead of -o pulse to see if it makes any difference?

Same result with -o alsa. I verified everything was good in alsamixer.

Sadly I can't comment on the issue, because I switched to arch, and it works fine for me now. It was probably something to do with a firewall or something.

@bcHelix can you try with -o raw > out.raw instead of -o pulse and then send me the out.raw file?

./scream -u -i virbr1 -p 4010 -o raw > ~/out.raw produces a zero-byte file unfortunatly. I can still see tcpdump giving me (.153 is the VM):
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on virbr1, link-type EN10MB (Ethernet), capture size 262144 bytes
09:30:43.574420 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575264 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575349 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575408 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575454 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575501 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575554 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
09:30:43.575763 IP <IP_ADDRESS>.4010 > <IP_ADDRESS>.4010: UDP, length 1157
...
I had a hunch Apparmor was doing something here, but I checked the log for any apparmor DENIED messages and didn't see any.

@bcHelix just to be clear, you see the "Switched format" message when you try with raw?
Do you have any firewall enabled? I don't know what's your distro, try sudo systemctl status firewalld.service, sudo systemctl status firewall.service or sudo ufw status. If one is enabled disable it for testing.
Does sysctl net.ipv4.conf.all.route_localnet  return 1 or 0 ? If 0 set it to 1 with systemctl -w net.ipv4.conf.all.route_localnet=1 or edit /etc/sysctl.conf
If you manage your VM with virsh add trustGuestRxFilters='yes' to your network card like this:
    <interface type='network' trustGuestRxFilters='yes'>
      <mac address='52:54:00:d1:24:8e'/>
      <source network='private'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </interface>

If you are using virtio ensure you have a private network between your host and guest like the one above. Macvtap doesn't allow for direct host-to-guest communication unless you have a switch that support hairpinning.

I'm using Devuan (non-systemD Debian fork), and I have an NFT firewall up. I did a nft flush ruleset and I immediatly got sound. Very stange as NFT should not be restricting any traffic on the bridge. I'll have to take a closer look at the rules. I did make the trustGuestRxFilters='yes' and sysctl -w net.ipv4.conf.all.route_localnet=1 so it could also be that they had something to do with it.
Thanks very much for your help @martinellimarco!

Hi, I'm currently experiencing a similar issue, as detailed above I've set trustGuestRxFilters='yes' and done systemctl -w net.ipv4.conf.all.route_localnet=1, but I still don't seem to be able to get any audio output.
I tried the tcpdump step using sudo tcpdump -pni virbr0 port 4010, and it clearly has output there - what could the issue be?
To clarify though I also set UnicastIPv4 to <IP_ADDRESS> and UnicastPort to 4010 to make sure (though I think the problem is on the receiving end).
In the Linux client I'm using ./scream -u -i virbr0 to hopefully get the output additionally.

It's been quite a while since I looked into this however have you guys suffering with latency on the shared memory approach considered/heard of the IVSHMEM version with a bell? I remember using that for the last few years and that had all the latency issues taken care of.

I had this issue on Fedora 36 and fixed it. Here was my solution:
Edit the file /usr/lib/firewalld/zones
Remove the line that says <reject/> :
<rule priority='32767'>
  <reject/>
</rule>

Run sudo systemctl restart firewalld


docs: add high-level connector overview

Adds a high-level overview of the different components and containers of the complete connector.

Internally approved.


fix: Only delegate to DataFusion cast when we know that it is compatible with Spark

Which issue does this PR close?

N/A
Rationale for this change

We have a catchall block in cast.rs that delegates to DataFusion for any cast that we don't have a specific match arm for. This is dangerous because it means we sometimes inadvertently delegate to DataFusion for casts where DataFusion is not compatible with Spark, which can lead to data corruption and hard-to-debug issues such as https://github.com/apache/datafusion-comet/pull/383#issuecomment-2127417428
What changes are included in this PR?

This PR introduces specific checks so that we only delegate to DataFusion for specific casts and changes the catchall to return an error.
I also improved handling of dictionary-encoded string arrays so that these are unpacked early on and this would have prevented the issue in https://github.com/apache/datafusion-comet/pull/383#issuecomment-2127417428
How are these changes tested?

Existing tests

This is ready for review now @viirya @parthchandra @kazuyukitanimura @huaxingao


Running the same container in AKS instead of WebApp

@sarah-widder
How about creating the same deployment in AKS, should a separate solution be created for that or can this repo be extended to include an AKS deployment as well? This should be not difficult to implement, given there's already a dockerfile ready with all the dependencies.
I'm not completely sure about the authentication layer though, need to look closer.

For now I've disabled the authentication, just to test whether it works
here:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/frontend/src/pages/chat/Chat.tsx
amended lines 35-44 like that:
    const getUserInfoList = async () => {
        const userInfoList = await getUserInfo();
        // if (userInfoList.length === 0 && window.location.hostname !== "<IP_ADDRESS>") {
        //     setShowAuthMessage(true);
        // }
        // else {
        //     setShowAuthMessage(false);
        // }
        setShowAuthMessage(false);
    }

Now the authentication prompt doesn't appear, however the chat isn't working still due to name resolution error. It is the same error in both WebApp (which I deploy from the azure portal by clicking "Deploy to WebApp") and when I'm running it in kubernetes.
The error:
Error communicating with OpenAI: HTTPSConnectionPool(host='my-cognitive-account-chatgpt4.openai.azure.com', port=443): Max retries exceeded with url: //openai/deployments/gpt-4_0314/chat/completions?api-version=2023-03-15-preview (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f28c71e7950>: Failed to resolve 'my-cognitive-account-chatgpt4.openai.azure.com' ([Errno -2] Name does not resolve)"))

Can you suggest why am I getting that? My OpenAI account is located in FranceCentral region (because this is where GPT-4 is available), the edpoint is: https://francecentral.api.cognitive.microsoft.com
AZURE_OPENAI_RESOURCE: "my-cognitive-account-chatgpt4" -- the name of OpenAI (cognitive services account of type OpenAI)
AZURE_OPENAI_MODEL: "gpt-4_0314" -- deployment name
AZURE_OPENAI_MODEL_NAME: "gpt-4" -- model name
But how does it know where this resource is deployed, which subscription and which resource group?

aahh the problem is that I was missing a custom domain, thus my endpoint didn't look like customdomain.openai.azure.com

Now just need to be able to setup the same authentication mechanism (azure AD), as was done in WebApp, for my application running in AKS.
@pamelafox can you help with that perhaps?

Ok, i've solved the authentication problem, by following these steps (a great article by the way): https://kristhecodingunicorn.com/post/k8s_nginx_oauth/#configure-nginx-ingress-controller
and yeah, i really enjoy talking to myself here... :)

@ealasgarov Sorry, we're playing whack-a-mole on OpenAI repository issue trackers right now. Here's a write-up of how I enabled AAD for this repo, if it helps:
For sample-app-aoai-chatGPT, I automated the process of creating an app registration and protecting the app service with that app with a combination of hooks and Bicep.
The hooks are declared here:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/azure.yaml
For the pre provision hook, auth_init.sh calls auth_init.py:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/scripts/auth_init.py
That script makes REST API calls to https://graph.microsoft.com/v1.0/applications in order to create a new app registration. It then sets AUTH_APP_ID, AUTH_CLIENT_ID, and AUTH_CLIENT_SECRET.
For the provisioning step, AUTH_CLIENT_ID and AUTH_CLIENT_SECRET are passed in main.parameters.json:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/infra/main.parameters.json
Those parameters get passed into the appservice module here:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/5b311a9f74797b771dad2b515126f9ec91a3dabe/infra/main.bicep#L96
That appservice.bicep module adds the identity provider here:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/5b311a9f74797b771dad2b515126f9ec91a3dabe/infra/core/host/appservice.bicep#L103
For the post provision hook, auth_update.sh calls auth_update.py:
https://github.com/microsoft/sample-app-aoai-chatGPT/blob/main/scripts/auth_update.py
That code makes a REST API to update the redirect URIs for the registered application to include the deployed URL endpoint.
This all works great locally! However, it doesn't work on CI/CD as the pipeline principal doesn't have the permission needed to create an application registration.

Thanks for the reply Pamela, much appreciated!
I guess I've now sorted everything out and things seem to work, including azure authentication, except for one problem - each time after the first successful answer, I'm getting this error when asking a 2nd question:
Error
Requests to the Creates a completion for the chat message Operation under Azure OpenAI API version 2023-03-15-preview have exceeded token rate limit of your current OpenAI S0 pricing tier. Please retry after 7 seconds. Please go here: https://aka.ms/oai/quotaincrease if you would like to further increase the default rate limit.

I cannot replicate this on OpenAI studio Playground with the same deployment/model, there I can ask 10 questions one after another and everything works fine. Not sure why is that... But I will the open a separate issue for that one.

imo it would be great to just pass the following environment variables if possible:
AUTH_TENANT_ID
AUTH_CLIENT_ID
AUTH_CLIENT_SECRET

what do you guys think?

@ealasgarov  I am having issue still on this, can you share your ingress files and deployment files please if possible


If Untitled Document.md is the title, set it to the first markdown title (if available) if code is pasted

see https://github.com/joemccann/dillinger/issues/645

This issue can be closed now.


PWN-6501 - Username cut update

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-6501
Description of Work

Username cut update
NO-TICKET - Added debug screen for name service

Screenshots (Optional)

Screenshot #1
Screenshot #2
Screenshot #3

[Paste Pic 1]
[Paste Pic 2]
[Paste Pic 3]


prod logging crash

i found some big issues on production with all trace, info, warn and error logging .
it seems that when i use info, warn and error onto the same log file,
it seems to crashes on production when multiple connection received.
it crashes with assets pipeline is closed (forgot what was the actual error)
when i separate all the files, it works smoothly.
what is causing the problem?

i found the issue comes from csrf plugin i was using.
but is there a way to log error when it crashes?

im suspecting my crash was due to gorp sql connection idle timed out.
im currently testing it by setting
db.SetMaxIdleConns(0)
db.SetConnMaxLifetime(time.Minute) //1minute
but what is the recommended way to debug this type of issues on production?
the error seems very generic and does not show any crash?
but previous ive had similar issue with csrf plugin, with similar error.
anyway to log the full stack errors by revel?

It does sound like you are missing some part of the error. Are you seeing this message in the log file? Is there anything printed to stderr? If a template function panics you will get a misleading error I think, do you have any custom template functions?

Hi,
I found the crash was due to gorp using db/mysql connection idle issue. No
custom template function yet.
On 11 May 2016 10:27 pm, "notzippy"<EMAIL_ADDRESS>wrote:

It does sound like you are missing some part of the error. Are you seeing
this message in the log file? Is there anything printed to stderr? If a
template function panics you will get a misleading error I think, do you
have any custom template functions?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/revel/revel/issues/1049#issuecomment-218475992

So did this cause a panic? Do you get a clear error when in development mode?

it did not happen on my machine cox im using it within 1 user,
but on production, it crashes with
Error running: signal: broken pipe
does this count as panic?
i dont have any panic handler

maybe u can duplicate the issue if u initialize gorp mysql driver
and then refresh the page, then shutdown mysql, and then refresh the page again
makesure the page has mysql queries

am closing this for now.. If bug persists please repoen


The state of the repository at publication

This repository is changing constantly in response to questions and feedback from others; however, I think it's worth documenting (somewhere) the commit at the time of publication is: e43ffc43c2d1844a91e2570b1cb570cc27a6262d
You can browse the files of this repository and all its code/data/etc in this "original state" via
https://github.com/c2-d2/pr_mort_official/tree/e43ffc43c2d1844a91e2570b1cb570cc27a6262d

You can create a tag or even a release for that. Then people could easy load the version corresponding to the time of publication using something like git checkout paper.

https://github.community/t5/How-to-use-Git-and-GitHub/Create-releases-for-old-commits/td-p/6466

Thanks for pointing that out, @karel-brinda — will do.

I've made a tag of the paper version and you can find it under the releases tab. It is called paper so the command in comment https://github.com/c2-d2/pr_mort_official/issues/8#issuecomment-397420559 should work as shown. @nish-kishore we should add a reference to the release page somewhere on the main README?


New version: Cthulhu v2.2.0

Registering package: Cthulhu
Repository: https://github.com/JuliaDebug/Cthulhu.jl
Created by: @timholy
Version: v2.2.0
Commit: f3aa8ef242f282b580391f2ba376160369b7e6b1
Reviewed by: @timholy
Reference: https://github.com/JuliaDebug/Cthulhu.jl/commit/f3aa8ef242f282b580391f2ba376160369b7e6b1#commitcomment-54567587

Failure is because Cthulhu 2 only supports Julia 1.7+.


[WIP] JAMES-3680 Disable authentication on un-encrypted channels

Jira: https://issues.apache.org/jira/browse/JAMES-3680
https://github.com/linagora/james-project/issues/4441

Test Result (1 failure )

    org.apache.james.imapserver.netty.IMAPServerTest$AuthenticationRequireSSL.loginShouldFailWhenRequireSSLAndUnEncryptedChannel

What is the value default of plainAuthEnabled? (The ticket wrote TRUE, but before that plainAuthDisallowed default is TRUE )

I drop logics related to auth.plainAuthEnabled in this PR.
It will be adapted in another https://github.com/apache/james-project/pull/791

rebase master & resolve conflict


API

filter through API for data
randomized character
from one API
randomized Burgers from
food API

https://www.bobsburgersapi.com/