Crash on Startup

After upgrading from version 2.8 to 3, Mapbox Studio would not start. I un-install, re-install the ultimate version several times, restart the computer but nothing will do. I also try to run the soft with Admin privileges without success.
I have been reading post relative to the .mapbox-studio folder and app.db but in my case, the folder does not even exist.
When I try to launch the app, the first loading screen briefly appears and fade out (I remember having the same issue when trying to lauch a previous 64 bits version on my 32 bits machine).
I am running Windows 7 32 bits.

Hi everyone
I had same problem this morning when upgrading from 2.8 to 3.0. I use windows 8.1 64 bits.
I'm going to try the following solution.
Regards

Which following solution?

Sorry
This
https://github.com/mapbox/mapbox-studio-classic/issues/1384
But didn't work.
Obviously dll were version related and didn't function on Mp 3.0.

The workaround described in #1384 is not valid for 0.3.0!
Please remove all files, that were extracted from the zip linked there.

Try the following steps instead:

look into %USERPROFILE%\.mapbox-studio (<- paste this into the address bar of file explorer)
if there is an app.db.compacted, delete it
check via Task Manager that there are no running processes of

node.exe or
mapbox-studio.exe

if there are, kill them
open a command prompt:  (Windows key + r, type cmd, press ENTER)

type: cd C:\Program Files\mapbox-studio\resources\app
type: vendor\node index.js

Is there an error message or Mapbox Studio @ http://localhost:3000/?

If there is an error message, please post it here.
If it shows Mapbox Studio @ http://localhost:3000/ open your browser at http://localhost:3000/

check if Mapbox Studio Classic works in your browser
when you are done testing, go back to the console, press Ctrl+C to stop Mapbox Studio!!
check if Mapbox Studio now works via the Application shortcut.

Thanks Berg.
This worked it.
I have a personal Mapbox account and also working in a Client's account.
I have followed your instructions -the last ones ;-)- and Mapbox runned ok but I had 'connection not allowed' message when tried to connect. See below images.
Then I came back to web Mapbox studio and reset my password and succesfully connected with Mapbox Studio desktop with my account. After this I close and restarted and connected with my client's provided user credentials.
Now all is working fine, for now,
I remember taht last session -threee days ago- that I had problems to uploads style to my client's Mapbox web, so I continued working in a local folder. Now I have uploaded without problems.
This is only my opinion, but seems that version change and 'possiblly' working with 2 Mapbox accounts during it crashes the new installation.
Thanks for your solutions.
And thanks again.
Ferran

Sorry to re-open but I cannot follow the workaround as I do not have the .mapbox-studio created after a fresh install...
About the command line, vendor\node index.js give a node.exe system error saying "api-ms-win-crt-runtime-l1-1-0.dll is missing" try to re-install the programme to solve this issue."

@inclanfunk ah, so fresh install means you cloned from Github?
Then you need to install the Visual C++ Redistributable for Visual Studio 2015.

Nope I download it from there:
https://www.mapbox.com/mapbox-studio-classic/#win32

@inclanfunk That is really strange, I just downloaded, installed and verified that the 32bit installer version works for me.
Could you check, if api-ms-win-crt-runtime-l1-1-0.dll is in
C:\Program Files\mapbox-studio\resources\app\vendor

and in
C:\Program Files (x86)\mapbox-studio\resources\app\node_modules\mapnik\lib\binding\node-v11-win32-ia32

Hey, I have the same problem than @inclanfunk
@BergWerkGIS The file you have descibed is not there (with hyphens), It is with underlines:
api_ms_win_crt_runtime_l1_1_0
what to do next? :)
Thanks

Now I have renamed that file, but now the next error message does not find the win-core-timezone file.
shall I rename them all changing underlines to hyphens?

@peterbodo y, renaming all file in both directories would be necessary.
It is probably easier to install [Visual C++ Redistributable for Visual Studio 2015], which should solve this, too.

@BergWerkGIS
Thanks, I could not download Visual C++, It just did not start downloading. For any case I have renamed the files in Program Files, but I do not have a Program Files (x86) Folder at all.
I have tried to run. Now it works for 5-6 secs, before it disappears.
I have tried in CMD as well
C:\Program Files\mapbox-studio\resources\app>vendor\node index.js
module.js:356
Module._extensions[extension](this, filename);
^
Error: The specified module could not be found.
C:\Program Files\mapbox-studio\resources\app\node_modules\mapnik\lib\binding\nod
e-v11-win32-ia32\mapnik.node
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (C:\Program Files\mapbox-studio\resources\app\node_mod
ules\mapnik\lib\mapnik.js:31:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
C:\Program Files\mapbox-studio\resources\app>

@peterbodo sorry, typo: the second path was also meant to be C:\Program Files.
Could you you look again in
C:\Program Files\mapbox-studio\resources\app\node_modules\mapnik\lib\binding\node-v11-win32-ia32

and rename there, too?

@BergWerkGIS
yep thanks.
Are these exactly the same files?
Can I just copy them?

@BergWerkGIS
and it works now. Thx!

Please confirm if it works renaming all the files of both folder or just
the api-ms-win-crt-runtime-l1-1-0.dll
Thanks

@inclanfunk
Rename them all!
I mean the api ms win files

And can I copy the renamed one from *C:\Program
Files\mapbox-studio\resources*app\vendor to C:\Program
Files\mapbox-studio\resources\app\node_modules\mapnik\lib\binding\node-v11-win32-ia32
? Thanks

@peterbodo @inclanfunk
I've republished the 0.3.1 release.
Download again from https://www.mapbox.com/mapbox-studio-classic/ and reinstall.
Then it should work without renaming.

Still not working.
Install without trouble, launch... start to load... 3 second later close by
itself.
Any ideas? Thanks.

@inclanfunk could you again try the steps outlined above?
Im especially interested in the output after vendor\node index.js.

Sure...
On vendor\node index.js command, the result is:
events.js:72
throw er; // Unhandled 'error' event
^
Error: OK, read

Oh, that's a vague error message.

I just checked with two more W7 machines and Mapbox Studio Classic worked on them.
The only things to try I can think of at the moment are (repeating vendor\node index.js test for each):

delete .mapbox-studio folder, %USERPROFILE%\.mapbox-studio <- paste this into the address bar of file explorer to easily find it
install  Visual C++ Redistributable for Visual Studio 2015

Or try to get access to a 64bit machine.
If you want to process a lot of data with Mabox Studio Classic 32bit you could run into out-of-memory problems later on.

I've setup another fresh and vanilla W7 32bit VM and tested the 0.3.1 release: it worked.

Howdy
I'm new to MapBox running Windows 7 at 64bits. Downloaded and installed the latest version 0.3.1 yesterday. Same problem as above: program opens, loading circle spins then the window vanishes.
I have worked through the above troubleshooting to no avail:
-searched %USERPROFILE%.mapbox-studio and deleted app.db.compacted
-checked Task Manager for running .exe
-then ran the cdm and recieved this error

Suggestions?
Also I had the same problem as above I could not get the Visual C++ Redistributable for Visual Studio 2015 files to DL

@pdwelker your error means Mabox Studio Classic cannot write to app.db.
These are the possible reasons:

node.exe/mapbox-studio.exe processes are still running and blocking the file
a left over app.db.compacted is still there
somehow the permissions to %USERPROFILE%\.mapbox-studio are screwed

Since you've already looked into 1. and 2. I suggest you

verify 1. again
delete %USERPROFILE%\.mapbox-studio completely. Make sure that it is really gone (press F5 to refresh), as Explorer sometimes doesn't report an error, even if it was not able to remove a directory completely
run vendor\node index again

Any errors?

I just checked with the Microsoft download for Visual C++ Redistributable for Visual Studio 2015 and it worked for me.
Here are some alternative direct download links: x64 x86

@BergWerkGIS after deleting the entire .mapbox-studio folder completely and re-running the vendor\node index, I received the http://localhost:3000/ in the command prompt.
Mapbox opened and connected in the browser on the second attempt. After this I stopped (ctl+c) mapbox in the command prompt. When clicking on the shortcut Mapbox now opens successfully! It works! Thank you!
One more question: What is the http://localhost:3000/ version of Mapbox? Is it just a browser version of  Mapbox Studio?

@pdwelker Great, that it works now.
Mapbox Studio Classic is always the same (localhost).
The shortcut starts a bundled browser displaying localhost:3000, so that you don't have to go to the command line, start it there and then manually open your own browser.

After running node index, I get the following error:
module.js:340
throw err:
Error: Cannot find module 'C:\Users%USERPROFILE%\mapbox-studio_032\resources\app\vendor\index'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:935:3
Any help?

@dosstx

'C:\Users\%USERPROFILE%\mapbox-studio_032\resources\app\vendor\index'

Looks at bit unusual to me, could you describe in more detail how you installed Mapbox Studio Classic?

Did you use the installer from here https://www.mapbox.com/mapbox-studio-classic ?
Or did you install from source?

What were your exact steps? (so I can try to reproduce)

@BergWerkGIS I am in a closed environment connecting to Mapbox Atlas server. I can get Studio to open up but can't load any basemaps. During the "Connect to your mapbox account to get started" screen I have the Atlas server set to my employer's API path. Are there logs I can check to see why it's not successfully connecting to the Atlas server?

nevermind. Got it working. Changed API path to another one.

@dosstx Great that it works now. Thanks for letting me know (just wanted to look into this).


Add additional annotations

Is there any possibility to add additional annotations to the test? Playwright itself offers for example the option to us test.info().annotations.push(...) to add some more, but it does not appear in the Azure test results.
There are some interesting fields:

Would it be possible to access them somehow? For example to add the actual used browser version or something like that?

Look at the reporter config testRunConfig section

@alexneo2003 I know this section, but as it is located in the configuration-file I do not have access to the exact browser version used in the specific run. Inside the testfile I am able to do something like
    test.beforeEach(async ({ loginPage, homepage, browser }) => {
        console.log(`${browser.browserType().name} ${browser.version()}`);
    });

what in this case gives me a firefox 127.0. But how am I able to print this version to every test run?

Inside testRunConfig you have parameter Configuration - it can be related with browser as Test Case configuration.
That information what you show on your screenshot are placed on higher level than test scope.

So then maybe my interpretation of the fields was wrong. Is there any possibility to note the used browser-versions to a specific test run of a specific test id with a specific configuration? At least the configuration does not know if the CI/CD-Pipeline is using a newer version of the browser...

sorry but no, I'm don't know how do it


problems with claim move and wallets

GD. I have claimed MOVE but before this I did not understand what wallet address is necessary to use. I used Razor address but where was only testnets at that moment. So now I worrying will I have mainnet on Razor wallet and  how my Move will appear there? Can you help please?

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WR240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hello @Ksju7
Sorry about your experience.
But, you must take immediate action to safely secure your wallet.
Please write us back using our “Chat icon” located on our Movementlabs-Help Center
You may include a link to this issue in the message content.
The issue here will be looked into and you will get assisted instantly.
Thanks!


Support Pro*COBOL listing

That's how [errors look] like in the listing [...]:
  1496             PERFORM CHANGE-VAL.
  1497        *
Error at line 1498, column 12 in file /tmp/MYPRG.pco
  1498             EXEC SQL
  1498  ...........1
  1498  PCB-S-00576, PLS-390: undefined column 'CNT' in INSERT statement
Error at line 1498, column 12 in file /tmp/MYPRG.pco
  1498             EXEC SQL
  1498  ...........1
  1498  PCB-S-00576, PLS-0: SQL Statement ignored
  1499                 INSERT INTO VAL (
  1500                   V1
  1501                 , V2
  1502                 , V3
  1503                 , V4
  1504                 , CNT
  1505                 , V5
  1506                 , v6
  1507                 , V7
  1508                 , V8
  1509                 , TUSER
  1510                 , TCHK
  1511                 , TMODTIME
  1512                 , UPDPID
  1513                 )
  1514                 VALUES (
  1515                   :VAL1
  1516                 , :VAL2
  1517                 , :VAL3
  1518                 , :VAL4
  1519                 , :VALCNT
  1520                 , :VAL5
  1521                 , :VAL6
  1522                 , :VAL7
  1523                 , :VAL8
  1524                 , :VALUSER
  1525                 , :VALCHK
  1526                 , TO_CHAR(SYSTIMESTAMP,'yyyy-mm-dd-hh24:mi:ssxff6')
  1527                 , :VALID               )
  1528             END-EXEC.
  1529        *
  1530             IF SQLCODE NOT = 0
  1531                MOVE SQLCODE TO DB-STAT
  1532                MOVE 8 TO INT-STAT
  1533                GO TO SEC-END.
  1534        *

[...] it would be cool if "COBOL_LISTFILE" could also highlight [... Pro*COBOL generated listings correctly]
Originally posted by @GitMensch in https://github.com/spgennard/vscode_cobol/issue_comments/708932180

As a comparison and test, this is how the header look different between MF Visual COBOL generated listings and Pro*COBOL generated listings:

* Micro Focus COBOL                  V4.0 revision 000 09-Oct-20 10:00 Page   1
* /tmp/PROG.cob
* Options: int("PROG.int") verbose ANIM DIRECTIVES"/tmp/demo.dir"
*          NOBOUND DIRECTIVES/tmp/demo_project.dir" XREF
*          LIST(/tmp/list/PROG.clis)
     1 IDENTIFICATION DIVISION.
     2 PROGRAM-ID.    PROG.
     4*------------------------------------------------------------*
     5* PROG     Sample program

* Micro Focus COBOL                  V4.0 revision 000 09-Oct-20 10:00 Page   2
* /tmp/PROG.cob
     6/
     7 DATA DIVISION.
     8 WORKING-STORAGE SECTION.

and that's the Pro*COBOL one:
Pro*COBOL: Release <IP_ADDRESS>.0 - Production on Thu Oct 15 08:14:37 2020
Version <IP_ADDRESS>.0

Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.

Open file: /tmp/MYPRG.pco
     1         IDENTIFICATION DIVISION.
     2         PROGRAM-ID.    MYPRG.
     4        *-----------------------------------------------------------*
     5        * MYPRG    I-O sample program.
     6        /
     7         DATA DIVISION.
     8         WORKING-STORAGE SECTION.

So to highlight that via COBOL_LISTFILE it looks that mainly the additional offset 8 for the actual start (2 space padding + initial 6 columns from COBOL which are suppressed in the MF listing) needs to be taken care of and additional the header and diagnostics which are the only lines that don't start with a space).
I haven't checked yet how diagnostic messages look in the MF listing (guess they will look beautiful) for the Pro*COBOL diagnostics see the thread start.
Note: Pro*COBOL also places a header on each "n" lines (strangely without a "page" counter) and before each "part" (like the precompiler options and the statistics) and also places the line feed character there as MF does (MF seems to use a separate line for that while Pro*COBOL goes on in the same line and does not start the document with a line feed, but does not insert a page for the line breaking comment) - here's the end of the test listing for additional reference:
Pro*COBOL: Release <IP_ADDRESS>.0 - Production on Thu Oct 15 08:14:37 2020
Version <IP_ADDRESS>.0

Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.

                              Precompiler Options
-------------------------------------------------------------------------------
Option Name    Current Value        Where set
-------------------------------------------------------------------------------
asacc             no                default
assume_sqlcode    no                default
auto_connect      no                default
charset_picn      nchar_charset     default
charset_picx      db_charset        default
close_on_commit   yes               mode
common_parser     no                default
config            default config    default
cwh_sql99         yes               default
date_format       local             default
db2_array         no                default
dbms              native            default
declare_section   yes               mode
define            BIT64             /opt/oracle/product/cli18/precomp/admin/pcbc
                  *none*            /opt/oracle/product/cli18/precomp/admin/pcbc
dynamic           ansi              mode
end_of_fetch      100               mode
errors            yes               default
file_id           0                 default
fips              no                default
format            ansi              default
hold_cursor       no                default
host              cobol             default
implicit_svpt     no                default
iname             /tmp/test/MYPRG.cocommand line
include           *none*            default
ireclen           132               command line
litdelim          quote             default
lname             /tmp/list/MYPRG.licommand line
lreclen           132               default
ltype             long              default
maxliteral        256               default
maxopencursors    10                default
max_row_insert    0                 default
memforprefetch    0                 default
mode              ansi              command line
nested            yes               default
nls_local         no                default
oname             /obs/sbl/tmp/CP_PRcommand line271.cob
oraca             no                default
oreclen           132               command line
outline           no                default
outlnprefix       *none*            default
pagelen           66                default
picn_endian       big               default
picx              charf             default
plan_baseline     no                default
plan_enabled      yes               default
plan_fixed        yes               default
plan_prefix       none              default
plan_run          no                default
prefetch          1                 default
release_cursor    no                default
runoutline        no                default
select_error      yes               default
sqlcheck          semantics         command line
stmt_cache        0                 default
threads           no                default
trim_password     no                default
type_code         ansi              mode
unsafe_null       no                default
userid            /@ora4tst         command line
varchar           no                default
xref              yes               default
Pro*COBOL: Release <IP_ADDRESS>.0 - Production on Thu Oct 15 08:14:37 2020
Version <IP_ADDRESS>.0

Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.

Statistics
----------

Return code: 1
Number of messages at severity I: 0
Number of messages at severity W: 0
Number of messages at severity E: 20
Number of messages at severity F: 0
Number of input lines: 2229
Number of host variables declared: 28
Number of cursor names: 16
Number of statement names: 0
Maximum memory (bytes) used: 1439332


Fix clone k8s

Fix e2e test dependency on building k8s

These two should not be tightly-coupled.  e.g. for RPM testing, the
packages will be built/installed, then e2e tests will run.  Having k8s
secondarily built/installed will seriously screw with rpm-building and
testing.

Signed-off-by: Chris Evich<EMAIL_ADDRESS>

/test ami

We need that to support different branches, where is that failing for you? @mrunalp ptal

@cevich What problem are we trying to solve here? It is the way it is because we want to cache kube build for faster bug fixes into 1.0 branch but still allow newer fixes to go into master at the expense of building kube in e2e.
What we would really really like is a way to tag the ami on the basis of target branch.

We need that to support different branches, where is that failing for you.

Aye, I hopefully moved this task in such a way that should still work...

What problem are we trying to solve here?

Mmm, I mentioned y'all in the commit that introduced this.

It is the way it is because we want to cache kube build for faster bug fixes into 1.0 branch

Ahh okay, maybe then we should just set force: true on the git task?

Mmm, I mentioned y'all in the commit that introduced this.

ofc I can't find it now...oh here it is: https://github.com/kubernetes-incubator/cri-o/commit/4dce8e12a0ca0770df3bfb1ae42c106912669365
I'm affraid I ran into this by accident, so no idea if it'll reproduce again...it may be due to some clash between AMI-state?.  I think @mrunalp is right, we need some better ami/cache tagging magic 😖  Would you mind prioritizing that on my trello card?
...okay I'll pick this up again next week..for now, just FYI in case y'all reproduce this anywhere else.

We can close this then, anyone can search the github repo ;)

@runcom oh no, this is an actual problem that needs fixing.The playbook must only make necessary changes, no matter what combination of tags is used.  Remember, declarative not imperative.
The problem is cloning of the k8s repo task happens twice.  Hence the second one will fail any time after k8s(?) is built (which changes the cloned repo).  Tasks should not be duplicated in this way, it's asking for trouble.

@runcom  uggg, I cannot re-open this PR and it's necessary and it passed all the tests.
@rhatdan please help.  Things are steaming forward way too fast, without actually considering the big picture or others experience / input.  I feel disinclined to participate in a community where both my contributions and good-intentions are ignored.  it's not playing nice in the sandbox 😞

Reopening. I am a bit confused as tests are passing on PRs going in to master despite the two clones. What we want to do is keep the clone in ami but override that in master in a safe manner.

Alright, nothing is broken right now, so hold on merging this till we actually see and understand that something IS broken somewhere in the flow. As it doesn't seem, I don't want to risk in the following week.

/test ami

It seems from the comments test ami was broken but I can't see where it's actually failing in the CI. When we merged my PR everything was working just fine with slash test ami.

Reopening. I am a bit confused as tests are passing  on PRs going in to master despite the two clones.
What we want to do is  keep the clone in ami but override that in master in a safe manner.

Thanks @mrunalp and also for the 'desired goal' info.  Yes, safety is my goal as well...hence this PR 😀  -  I've stumbled across trouble once, and maybe it's reproducible.  Do you know off-hand, about how long the kube build takes?  Are we talking about saving 30-seconds or 10-minutes?

Alright, nothing is broken right now, so hold on  merging this till we actually see and understand that
something IS  broken somewhere in the flow. As it doesn't seem, I don't want to risk  in the following week.

Yes @runcom , hence " I'll pick this up again next week..for now, just FYI in case y'all reproduce this anywhere else." (and the source of my frustration).
All,
Just Generally speaking...doing the same thing twice (the same way) in one playbook run is a asking for insanity.  Remember that these tasks (given same input) are suppose to not make any changes that aren't required (hence the failure).
That said, do we ever care about preserving the cached build of kube?  If not, then a really simple solution here is to add the --force option.  With that on the second run, we've changed the inputs, so any differing results are to be expected.
it also means I don't need to investigate the actual cause (because we don't care about what the repo-change was, as it's being force-clobbered).
What y'all think?

BTW: I think that No handlers could be found for logger "dnf" is caused by a missing package (memory is a little fuzzy-though).

    "changed": false,
    "failed": true,
    "item": "libguestfs-tools"
}

MSG:
---
async task did not complete within the requested time

Probably a networking-related issue...and a reminder that someone should take some time to prune that list of RPMs.  I doubt we really actually need libguestfs-tools (eh?)

...answering some of my own questions...I have a theory of how it broke for me...

we want to cache kube build for faster bug fixes into 1.0 branch...

There's a cache-state "non-sequitur" produced by @runcom 's change.  The include-file doesn't only build kube.  It also installs (and changes other aspects of the system).  Therefor, any future changes in a later run, which omits some aspect of those changes, will also fail to invalidate the cache.
For example:

AMI caches "kube-past" installation and configuration, along with /etc/critical/snafu - which causes some horrible bug.
An unrelated CI run for some random PR, clones "kube-future" with a fix for that bug:  Don't install /etc/critical/snafu.
Random PR author jumps off 16th story, because he/she can't figure out how a supposedly fixed bug seemingly re-appeared.
Just before the engineer-splatters, they remember to look at the JFM playbook, but sadly...it's too late.  All they can do is curse Ansible 😀

Short of being able to tag the AMI cache for a specific branch (seems more and more critical).  I think maybe there's a simple short-term fix here:

Separate the "building" from the "installing and configuring".
Only cache the "building" part.
For the test-time run, --force clone "future-kube", retaining identical cached output but not changes to the system.
Build future-kube (gets speed boost), then do the install/configure part.

Does that sound good?
Anyone know off-hand what make target I need to use to avoid installing?

...answering some of my own questions...I have a theory of how it broke for me...

I'd love to see where it broke for you, was it in the CI or your own VM? I haven't seen any failure in the CI so far actually.

I'd love to see where it broke for you, was it in the CI or your own VM? I haven't seen any failure in the CI so far actually.

@runcom Follow the link in this comment: https://github.com/kubernetes-incubator/cri-o/commit/4dce8e12a0ca0770df3bfb1ae42c106912669365#commitcomment-25387341
Though if my theory is correct, it will be very hard to reproduce this in k8s or any other build+install+configure include.  It's going to depend on way more variables than we should be worrying about.  In any case, separating the clone+build tasks from the install+configure tasks should prevent any possibility of hitting this problem, specially tagged AMI's or otherwise.
(Did I mention that I don't like using cache for CI?) 😀

@runcom @mrunalp That last commit is completely speculative, dotted with FIXME's and TODOs.  It's just a brute-force (I'm the dumb brute in this case) attempt to see if it's possible to separate the build, from the install tasks.
Though my feeble attempt may simply implode, the overall-idea should be sound:  Cache the artifacts from building.  Later, force-clone and re-build only any changed artifacts before testing.  This should allow us to avoid any cached-vs-reality inconsistencies (because a repo. changed out of sync with cache-generation).
Does this make any sense at all?
I guess maybe a fall-back is, do the same thing, but only for the kube tasks (instead of everything).
Oh, also, would it make sense to also cache a CRI-O build using this technique?

(woops, forgot to do the pre-test re-building tasks)

(/me presses enter, then runs away...fast!)
/test all

okay, wow, that's surprising...both slash-test-ami's have successfully past all the speculative build/install changes and are now running the integration tests...
/me looks away in case it implodes

@runcom @mrunalp Could I have some help investigating why the ami_fedora e2e tests failed?
It's certainly related to changes I made in DO NOT MERGE: TEST SEPARATION OF BUILD VS INSTALL.  I marked all the ones I suspect with a #TODO in the code.  Hopefully one will stand out to you like a sore thumb 😬 (and be easy to fix).
Esp. This one and this related one.


Terminal rewards

Merge Terminal rewards into main. Merge after #86
[x] Pytests passing
[x] Linter applied.

Thanks, @DanielHettegger!
I do not see any issue with the implementation. 💯
Let's perhaps include the final modifications applied to #86.
Also, I would not merge this branch into "main" before running some simulations (heuristics & MARL). From a few preliminary rollouts, I see the terminal cost is still very high.

Thanks Pablo! Should we tune the final rewards somehow before merging or is it okay like this?

We can leave it as is IMO.
In any case, we can always modify the values from the config later on. :)


Bugfix: Don't access debugNeedsLayout in profile or release modes. (#164)

Bugfix: Don't access debugNeedsLayout in profile or release modes. (#164)

CC @venkatd

Merging because @salihgueler is OOO.


Add Undertow 2.1.7.final+ worker thread pool metrics.

Fix Undertow 2.1.7.final+ worker thread pool metrics.

[ ] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

I found undertow worker thread pool monitoring is not supported in skywalking-showcase songs service which use spring-boot-starter-undertow:2.5.6.
However spring-boot-starter-undertow:2.5.6 is in our java-agent test matrix.
After research, I located the problem of undertow undertow-worker-thread-pool-scenario, it just change test version of  spring-boot-starter-undertow,
but forgot to upgrade the version of spring-boot-dependencies, which actualy control the version of xnio(the impl of undertow worker threadpool).
So currently, undertow only tested and supported in xnio version 3.3.8.final. In showcase songs service, we use xnio 3.8.x.final, this explains why no threadpool metrics reported.
In this PR, I add 3.8.x as supported version and fix undertow undertow-worker-thread-pool-scenario to make sure it fully tested.

springboot
undertow
xnio

2.1.9.RELEASE
2.0.26.final
3.3.8.final

2.2.13.RELEASE
2.0.33.final
3.3.8.final

2.3.12.RELEASE
2.1.7.final
3.8.0.final

2.4.13
2.2.12.final
3.8.4.final

2.5.9
2.2.14.final
3.8.4.final

2.6.3
2.2.14.final
3.8.4.final

TaskPool is a inner class in org.xnio package, I try add a new class with same package name to access TaskPool but failed, so I change back to reflect way.
java.lang.IllegalAccessError: tried to access class org.xnio.XnioWorker$TaskPool from class org.xnio.XnioWorkerTaskPoolAccessor


[docs] More documentation for lit substitutions

Add explanations for lit substitutions marked as "FIXME" in the testing
documentation.

Place all %target-* substitutions in the same section of the
documentation.
Remove substitutions that are no longer available or in use, such as
%llvm-opt and %leaks-runner.
Use uniform spacing between all substitutions bullet points.

(The following isn't part of the commit messages in this pull request.)
Note that %clang-importer-sdk is still undocumented. I'm still not sure what that substitution does, so I didn't document this in this pull request.

@modocache Thank you!  Looks good, just a few comments from me.  Please fix and I'll merge.

Thanks for the review, @gribozavr! I amended your suggested changes to the commit.

@modocache Thanks!


Openvpn screwed things up?

ZNC was working beautifully on my vps until I installed Openvpn at the same droplet. Now it is giving me  took too long to respond error on browser and (Connection timed out) in hexchat. Any idea what might have caused this?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40400626-openvpn-screwed-things-up?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Post the relevant part of znc -D and your znc version and bindhost can also be helpful.
The support channel would be #znc at freenode.

Looks like Openvpn is misconfigured. Without any details about your configuration it's hard to say anything in particular.

Thanks for the replies, Openvpn is working so I was just wondering if there is a known issue that causes one to not work with the other. I will go hit up the znc channel in freenode. thanks again.

Solved my problem, somehow the vpn setup removed the rule that allows the port, added it back using:
sudo ufw allow
sudo ufw reload
works again,


Server-side authentication

I'm excited to finally see the version 1.0.0 ready for action. It looks really cool so thank you all for all the efforts!
Maybe this is the right time to ask about the server-side authentication concepts when using react-router? I've been struggling on this for months and none of the solutions feel like the right way to do it. If the matching process would be synchronous I would use the react-cookie package as here https://github.com/rackt/react-router/issues/1629. The main question is how to initialize the router environment before the match function so i could manipulate with session/cookies inside onEnter and so the match function will allow/restrict based on that (putting this into location.state?). This part is straight forward when doing it only on the client side but on the server side I feels like I would need to pass data/request into the match function or smth.
Would someone be so kind and show the how-to on this? Thanks!

I will try to put more examples and guides probably tomorrow, I'm AFK today. But we definitely will have much more examples :smile:

Thanks @knowbody!

@knowbody Any success on that?

been a bit busy lately, I put them tonight! Promise :pray:

Hehe, thanks man :).

Any progress on this issue? I need to do the same thing. Users are pre authenticated and credentials are passes as request headers.

I think this is heavily dependent on how you do data modeling.
In general the approach you want to take is to just populate the relevant store with information from the cookies (i.e. make this part of the code potentially not be strictly isomorphic).
I'm not sure how helpful it'd be to add a minimal example, when in practice our users most likely would be using Redux or another Flux framework with a potentially different API.
Perhaps this is better suited for a more full-fledged example, e.g. one that shows isoversal rendering with Redux? @gaearon thoughts?

I do use redux. I templated my application from
https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/server.js
Should i dispatch a redux action to login the user right after the store is created in server.js above?
Thanks!

I have no idea what's idiomatic for Redux, sorry.

Well, you managed to help me anyway :)
I check for my headers, if they are present i dispatch a pre-authenticated-user action to my store that changes state as if the user has logged in. react-routes then checks for logged in users in onEnter. It's all  working...
Great :)
/Magnus


Add NVENC Video Encode and Decode GPU

[ ] Add NVENC Video Encode and Decode GPU #5

This comment appears when your computation resources cannot catch up the fast decode speed. I think that what I wrote is confusing. I will change it.

The new branch will support GPU encoding as default option (you can change it in the config.py if you don't want). Moreover, based on my test, GPU encoding help the program accelerate quite a lot. If you have a little bit extra GPU memory (~extra 1.5 GB is needed for 480P input (before Supre-Resolution)) unusued, I recommend you to use this default encoding way.

The new branch will support GPU encoding as default option (you can change it in the config.py if you don't want). Moreover, based on my test, GPU encoding help the program accelerate quite a lot. If you have a little bit extra GPU memory (~extra 1.5 GB is needed for 480P input (before Supre-Resolution)) unusued, I recommend you to use this default encoding way.

For GPU decoding, I don't have too much idea how to use moviepy to achieve this purpose. Also, I feel that when using hardware decode, we usually need to first transfer data from CPU memory to GPU. When the GPU decode them, they need to transfer back to CPU, which creates unneeded data transfer costs. If I use GPU decode, I also need to consider moving all CPU codes to CUDA-based. However, this will be a giant engineering task. Meanwhile, I need to think about how to redesign the whole struture to fully utilize the benefits of GPU decoding. Therefore, currently, I think that I need more time to consider GPU decoding.

Why is CUDA used for encoding? It is better to use the NVENC core video. Why is the CPU loaded at 100%? Will video decoding be added?

For Windows task manager, I always feel that their utilization of GPU reports is inaccurate. What I used for encoding is actually the Nvidia Hardware encoder (-c:v hevc_nvenc) built in FFMPEG (access it through moviepy package). I think that the NVENC is actually used but the Windows task manager cannot show the information accurately.


Fix chat message indicator size and "Message Seen" icon

What

Update icons from 20px -> 12px

(Note: SVGs themselves are 12px x 12px but plus padding inside the Icons is 16px which is why this PR has size 16 icons)

Update MessageSeen to be the non-filled version

Why
Per figma designs: https://www.figma.com/file/72qJ03EOQExf12g5JTdWjQ/Web-UI-Library---POR?node-id=3263%3A19683

How Tested

Why is there a change in the size of PIP stream?

Why is there a change in the size of PIP stream?

You happened to review just as I merged from main, but before the update-snapshots had run on top of that merge haha, should be gone once that finishes


Adding neptune as a command line observer is ignored

I'm trying to optionally add Neptune as an observer based on a command-line option, but adding it inside a function ends up not logging anything and issuing an error that no observers have been added to this run>
Config is setup as:
@ex.config
def Config():
     with_neptune=True
     neptune_project = 'test/test'

@ex.automain
def main(with_neptune: bool, neptune_project: str):
    if with_neptune:
        from neptunecontrib.monitoring.sacred import NeptuneObserver
        ex.observers.append(NeptuneObserver(project_name=neptune_project))

Resulting message in the logs is this, and no experiment shows up in Neptune:
WARNING - sim_1 - No observers have been added to this run

You have to add the observer before the main function, otherwise it wouldn't be able to log when the experiment started. Moving your if with_neptune: ... block into the config scope should work.


implemented fully auto april tag

Before issuing a pull request, please see the contributing page.

don't need this


VM and image definition generation mismatch

Hello, team.  I wanted to call out that when using the "az vm create" provided on this page, Ignite (November) 2023 onwards "az vm/vmss create" command will deploy Gen2-Trusted Launch VM by default.  The command provided on this page to create the image definition, though, "az sig image-definition create" will default to a generation 1 VM.  So, when the user finally runs the command "az sig image-version create" to create the image version, they'll get the error below.
(Conflict) The resource with id '/subscriptions/REDACTED/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM' has a different Hypervisor generation ['V2'] than the parent gallery image Hypervisor generation ['V1'].
Code: Conflict
We'll probably want to adjust the commands so that they all deploy and capture the same generation VM.

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

ID: 0ea3eb30-7cb6-46b9-cd12-8a1d108d707d
Version Independent ID: 2e610d00-db26-a002-6190-113221b273c1
Content: Tutorial - Use a custom VM image in a scale set with Azure CLI - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/tutorial-use-custom-image-cli.md
Service: virtual-machine-scale-sets
Sub-service: shared-image-gallery
GitHub Login: @cynthn
Microsoft Alias: cynthn

@ju-shim @mattmcinnes

@mbiver
Thanks for your feedback! We will investigate and update as appropriate.

Hello, we made these updates as a team right before Ignite - checking with them all now before we update the tutorial in question. Thank you.

Thanks for your contribution to our documentation
We are moving to a new user feedback system. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


[HTTP 200][ERR 104] nonce must be higher than<PHONE_NUMBER>2042

Hi,
Not sure why this would be an issue however I am getting the following error.

[HTTP 200][ERR 104] Cannot perform request - nonce must be higher than<PHONE_NUMBER>2042

Changing the following line to * 10000 fixes the issue:
https://github.com/joowani/quadriga/blob/ba1591eead956923c500c92d10804088650c07b8/quadriga/rest_client.py#L118
Cheers

Hi @maxim25,
Ok that's good to know. I will add the fix to the new release I'm working on.
Thanks!


chore: use tagged literals in tests

https://github.com/KaTeX/KaTeX/pull/3902 looks abandoned, so I've decided to try to finish it.
What is the previous behavior before this PR?
expect("\\mathinner{\\langle{\\psi}\\rangle}").toParse();
What is the new behavior after this PR?
expect`\mathinner{\langle{\psi}\rangle}`.toParse();

Fixes https://github.com/KaTeX/KaTeX/issues/1717

@edemaine could you please review and start CI job? Tests are passing locally.

I have fixed 2 issues with double backslashes and reverted every test that includes \u or backtick. While backtick test passes,  the string that expect resolves to has changed. Some test with \u, like An under-accent parser work fine with backticks and single backslash, but I'm not sure why  and I better move it to separate PR after I figure it out.

I found where we handle tagged literals:
https://github.com/KaTeX/KaTeX/blob/bedce93260cc413abb7730a5693dc27222297178/test/helpers.js#L17-L20
This gets called e.g. in getBuilt. So I think the correct test is:
const r = x => x != null && x.hasOwnProperty('raw') ? x.raw[0] : x;
r`\url`

which correctly generates "\\url". So I think all the \u tests can in fact be restored to use backticks. Sorry for the runaround!
Maybe you can update these comments too:
https://github.com/KaTeX/KaTeX/blob/bedce93260cc413abb7730a5693dc27222297178/test/katex-spec.js#L2919
https://github.com/KaTeX/KaTeX/blob/bedce93260cc413abb7730a5693dc27222297178/docs/api.md#L16
I think what is still problematic is ${ (because of interpolations, and \$ won't fix it) and ` that isn't preceded by a backslash (again \` would produce something different than `). But otherwise things template strings should be OK: \u and \x do not seem to pose any issue when using String.raw (or r as in our tests).
In the future, can you add commits instead of rebasing? Otherwise I can't really review the new changes. We squash commit when accepting the PR, so the commit history doesn't matter except for review.


Alert Combiner Improvement: Reduce Forta API calls

@christian-forta I noticed that the alert combiner might be unnecessarily calling the Forta API for certain bot ID and alert ID combination, and I think we can reduce the current 1,666 calls down to 98 calls. This reduction I think can speed up the bot.
IIUC, in this code here on Line 105
for bot_id in BOT_IDS: # 49 bot ids
    for alert_id in ALERT_ID_STAGE_MAPPING.keys(): # 34 alert id keys
        bot_alerts = forta_explorer.alerts_by_bot(bot_id, alert_id, start_date, end_date) # call to Forta API

This is making 49 x 34 = 1,666 network calls. I'm assuming most bots will produce at most 2 different alertIds, so I think we can potentially reduce this down to 49 * 2 = 98 calls. This would be a 94% reduction.
We can reduce this by changing the data structure a bit by creating a mapping of bot ids as keys and a list of associated alert ids as the value.
for bot_id, alert_ids in BOT_IDS_ALERT_IDS_MAPPING.items():
    for alert_id in alert_ids: # 1 - 3 alert ids
        bot_alerts = forta_explorer.alerts_by_bot(bot_id, alert_id, start_date, end_date) # call to Forta API

Assuming I understand the logic, I think this could be an easy win?

This was resolved


Add a strict option to ignore html errors

And clean up a bunch of whitespace, I guess?

Seems this project is dead then?


[Extensibility Bug] Codeunit "Catalog Item Management" Event OnAfterCreateNewItem

Issue #19834 is not closed
how this code can change Item? -> the Dimension is a Gobal Dimension:
table Default Dimension
trigger OnInsert()
 var
     IsHandled: Boolean;
 begin
     IsHandled := false;
     OnBeforeOnInsert(Rec, DimMgt, IsHandled);
     if IsHandled then
         exit;

     GLSetup.Get();
     if "Dimension Code" = GLSetup."Global Dimension 1 Code" then
         UpdateGlobalDimCode(1, "Table ID", "No.", "Dimension Value Code");
     if "Dimension Code" = GLSetup."Global Dimension 2 Code" then
         UpdateGlobalDimCode(2, "Table ID", "No.", "Dimension Value Code");
     DimMgt.DefaultDimOnInsert(Rec);
     UpdateParentId();
     UpdateParentType();
 end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 47995.


Identifying a bot's message in @app.event("message")

How can I reliably identify a bot message? I want to prevent the bot from responding to itself. Some methods that I currently use:

Look for "bot_id" in event
Save the timestamp whenever the bot sends a message, and ignore message events with the exact timestamp.
Check the user_id in event (not preferred as it is different for each workspace installation).

Second question. Why does the bot not receive its own messages in the internal workspace but receives it in the external workspace?
Follow up question to second question: If the current 2 token for 2 workspace setup is not appropriate, how should I change the configuration? It is a single server meant for multiple workspaces.
Reproducible in:
The slack_bolt version
slack-bolt==1.18.0
slack-sdk==3.21.3
Python runtime version
Python 3.9.12
Steps to reproduce:
(Share the commands to run, source code, and project settings (e.g., setup.py))

Setup app in socket mode.
Install to organization workspace, run server using organization workspace bot token.
Activate public distribution and install to external workspace. Respond to messages using organization workspace/external workspace bot token through "https://slack.com/api/chat.postMessage".

Truncated Logs in organization workspace:
received:
{"token": ..., "ts":<PHONE_NUMBER>.549739, 'event': {'client_msg_id':, 'type': 'message', 'text': 'test', 'user': ,...}}
post response:
{'ok': True, ... 'ts': '1691679444.825769, 'message': {'bot_id': , 'type': 'message', 'text': "response", 'user': , ...}}
Truncated Logs in external workspace:
received:
{"token": ..., "ts":<PHONE_NUMBER>.243649, 'event': {'client_msg_id':, 'type': 'message', 'text': 'test', 'user': ,...}}
post response:
{'ok': True, ... 'ts': '1691679662.924329, 'message': {'bot_id': , 'type': 'message', 'text': "response", 'user': , ...}}
received:
{"token": ..., "ts":<PHONE_NUMBER>.924329, 'event': {'bot_id':, 'type': 'message', 'text': 'response', 'user': ,...}}

Hi @YuPeiHenry, sorry for our slow response here.

How can I reliably identify a bot message?

You can check if subtype: bot_message exists in the payload. Also, as you mentioned checking if bot_id exists is a good way to go.

Second question. Why does the bot not receive its own messages in the internal workspace but receives it in the external workspace?

An app receives the same message event only once if the app is connected to several workspaces. As long as the message is identical in a Slack Connect channel, your app receives an event from any of the connected workspaces. If you want to know the list of workspaces / authorized users associatd with an event, you can perform apps.event.authorizations.list API with an app-level token and an event_context string data. You will see both the "internal" and "external" workspaces in the response.
I hope this helps.

Thanks @seratch , I have no further questions.


[AMBARI-25250] Blueprint processor should support multiple ZooKeeper nodes for Livy

What changes were proposed in this pull request?
Add multi-node host group replacement for livy.server.recovery.state-store.url so that the full ZK quorum is substituted instead of a random ZK node.
https://issues.apache.org/jira/browse/AMBARI-25250
How was this patch tested?
Adjusted unit test.
Deployed cluster via blueprint with multiple ZK nodes and the property set to %HOSTGROUP::zk%:2181.  Verified that livy.server.recovery.state-store.url in the cluster config contains all ZK nodes.
Deployed cluster via blueprint without setting the related properties (defaults to filesystem-based recovery).  Verified that livy.server.recovery.state-store.url is not changed by the blueprint logic.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5146/
Test FAILed.
Test FAILured.


HDDS-2769. security/SecurityWithRanger.md

What changes were proposed in this pull request?
translation to https://hadoop.apache.org/ozone/docs/0.5.0-beta/security/secuitywithranger.html
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2769
How was this patch tested?
hugo server

LGTM.  + 1.  Thanks @iamabug .


stop propagation only after MvcEvent::EVENT_DISPATCH_ERROR

because only one listener would be triggered
should fix https://github.com/ZF-Commons/zfc-rbac/issues/357

Coverage increased (+0.08%) to 92.9% when pulling bb292776d7d6f254f2b4ace2c6ddf087c79de524 on svycka:hotfix/issue-357 into<PHONE_NUMBER>fe50c06ef596848c5813ed4a739ac3 on ZF-Commons:master.

Can you add a test-case for this, please?

Write a test that fails without this patch and succeeds with this patch.

@svycka do we need still these conditions in tests:
         if (method_exists($eventManager, 'triggerEvent')) {
             $eventManager->expects($this->once())
                          ->method('triggerEvent')
                          ->with($event);
         } else {
             $eventManager->expects($this->once())
                          ->method('trigger')
                          ->with(MvcEvent::EVENT_DISPATCH_ERROR);
         }

?

@webimpress correct, this could also be updated.

Coverage increased (+0.1%) to 92.943% when pulling 0d093924b47bca56164de28692630be11f47b1d9 on svycka:hotfix/issue-357 into<PHONE_NUMBER>fe50c06ef596848c5813ed4a739ac3 on ZF-Commons:master.

@prolic anything else?

Coverage increased (+0.1%) to 92.943% when pulling a3afdac4a2dcdd4bf8eb169275499c9266d4344b on svycka:hotfix/issue-357 into<PHONE_NUMBER>fe50c06ef596848c5813ed4a739ac3 on ZF-Commons:master.

Coverage increased (+0.1%) to 92.943% when pulling a3afdac4a2dcdd4bf8eb169275499c9266d4344b on svycka:hotfix/issue-357 into<PHONE_NUMBER>fe50c06ef596848c5813ed4a739ac3 on ZF-Commons:master.

Thx


Feature request: that 'Local to Field' refactoring class in rope be exposed via the "Python Refactor"

Requesting that 'Local to Field' refactoring class in rope be exposed via the "Python Refactor" commands in the plugin.
Being able to select a local variable and convert it into a class field with a single shortcut would be a very useful feature.
Have already raised #3825 with a starting implementation.

@DonJayamanne I spoke too soon it's already a known issue : https://github.com/python-rope/rope/issues/254

@DonJayamanne it fails quite spectacularly within the rope library. I wonder what happens to some of the existing refactorings like extractMethod and extractVariable

Closing in favour of adding appropriate support in the language server.


Correction for raw affiliation Family physician practising in Woodstock, Ont, and Regional Academic Director (Oxford) at Western University.

Correction needed for raw affiliation Family physician practising in Woodstock, Ont, and Regional Academic Director (Oxford) at Western University.
raw_affiliation_name: Family physician practising in Woodstock, Ont, and Regional Academic Director (Oxford) at Western University.
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4376276902
contact: 1853564dac7b1204dfb19cf49e2a863b:a4b457d2f87c5719 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Octo not a FC

Octo isn't a fantasy console itself, but rather a suite of development tools (a high-level language, IDE, and debugging utilities) for CHIP-8, which is a fantasy console, supposedly the first to be called so.
My suggestion is to replace the Octo link with CHIP-8, linking to its Wikipedia article or perhaps Awesome CHIP-8.

We had a similar conversation #66, CHIP-8 is listed as a link. Considering CHIP-8 doesn't offer an official release, I prefer to mention it as is, and keep the more approachable implementation (Octo) on the list.

Hm, yes, there's definitely something to be said for not confusing people who are used to single-implementation fantasy consoles. And Octo is the only web CHIP-8 implementation I'm aware of.
That said, I think displaying the link as "Octo" is misleading at best. Perhaps the link text could be changed to "CHIP-8" but the link to Octo could remain?

Perhaps something like Octo (CHIP-8) or CHIP-8 (Octo) would do the trick

Using Octo (CHIP-8) now, it's better for any upcoming CHIP-8 compatibles/derivatives in future.


Copy URL

Add these options to Item View page

print
copy url
share (fb / tw)

Included in item view


unsupported application protocols ([edgedb-binary])

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Read the docs https://docs.edgedb.com/database/reference/protocol#sockets https://docs.edgedb.com/changelog/1_0_b3#tls and thinked it works with ALPN
try to use the edgedb cli tool with the edgeDB Container behind the traefik proxy
edgeDB Default PORT(5656)
$ edgedb --dsn edgedb://DOMAIN
What did you see instead?
edgedb error: ClientConnectionFailedError: received fatal alert: NoApplicationProtocol
Tested too if EdgeDB container is working with https got a website over https://DOMAIN/ui just have a problem with the cli tool
What version of Traefik are you using?
Version:      3.0.0
Codename:     beaufort
Go version:   go1.22.2
Built:        2024-04-29T14:25:59Z
OS/Arch:      linux/amd64
What is your environment & configuration?
services:
  traefik:
    image: traefik:v3.0.0
    container_name: traefik
    ports:
      - 80:80
      - 443:443
      # -- (Optional) Enable Dashboard, don't do in production
      - 8090:8080
      # -- Custom entrypoints
      - 5656:5656
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./traefik/traefik.yaml:/etc/traefik/traefik.yaml:ro
      - ./traefik/conf/:/etc/traefik/conf/
      - ./traefik/certs/:/etc/traefik/certs/
      - ./traefik/logs:/var/log/traefik/
    # -- (Optional) When using Cloudflare as Cert Resolver
    environment:
      - CF_DNS_API_TOKEN=API_KEY
      - "traefik.docker.network=traefik-network"
    labels:
      - "traefik.enable=true"
      - "traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto=https"
    # -- (Optional) When using a custom network
    networks:
      - traefik-network
    restart: unless-stopped

networks:
  traefik-network:
    external: true

EdgeDB Docker-Config
version: "3"

services:
  edgedb:
    image: edgedb/edgedb
    container_name: EdgeDB
    volumes:
      - "./dbschema:/dbschema"
      - "./data:/var/lib/edgedb/data"
    environment:
      EDGEDB_SERVER_INSTANCE_NAME: EdgeDB
      EDGEDB_SERVER_TLS_CERT_MODE: generate_self_signed
      EDGEDB_CLIENT_TLS_SECURITY: insecure
      EDGEDB_SERVER_ADMIN_UI: enabled
      EDGEDB_SERVER_USER: admin
      EDGEDB_SERVER_PASSWORD: test
      UID: 100
      GID: 100
    labels:
      - "traefik.enable=true"
      - "traefik.docker.network=traefik-network"

      - "traefik.http.routers.edgedb.entrypoints=websecure"
      - "traefik.http.routers.edgedb.rule=Host(`DOMAIN`)"
      - "traefik.http.routers.edgedb.tls=true"
      - "traefik.http.routers.edgedb.tls.certresolver=production"
      - "traefik.http.routers.edgedb.service=edgedb"
      - "traefik.http.services.edgedb.loadbalancer.server.port=5656"
      - "traefik.http.services.edgedb.loadbalancer.server.scheme=https"

      - "traefik.tcp.routers.edgedb.entrypoints=edgedb"
      - "traefik.tcp.routers.edgedb.rule=HostSNI(`DOMAIN`)"
      - "traefik.tcp.routers.edgedb.service=edgedb"
      - "traefik.tcp.routers.edgedb.tls=true"
      - "traefik.tcp.routers.edgedb.tls.certresolver=production"
      - "traefik.tcp.services.edgedb.loadbalancer.server.port=5656"
    networks:
      traefik-network:

networks:
  traefik-network:
    external: true

traefik.yaml
global:
  checkNewVersion: false
  sendAnonymousUsage: false

# -- (Optional) Change Log Level and Format here...
#     - loglevels [DEBUG, INFO, WARNING, ERROR, CRITICAL]
#     - format [common, json, logfmt]
log:
  level: DEBUG
  format: common
  filePath: /var/log/traefik/traefik.log

# -- (Optional) Enable Accesslog and change Format here...
#     - format [common, json, logfmt]
#accesslog:
#  format: common
#  filePath: /var/log/traefik/access.log

# -- (Optional) Enable API and Dashboard here, don't do in production
api:
  dashboard: true
  insecure: true

# -- Change EntryPoints here...
entryPoints:
  web:
    address: :80
    # -- (Optional) Redirect all HTTP to HTTPS
    http:
      redirections:
        entryPoint:
          to: websecure
          scheme: https
  websecure:
    address: :443
    proxyProtocol:
      trustedIPs:
        - <IP_ADDRESS>/16
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/18
        - <IP_ADDRESS>/18
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/17
        - <IP_ADDRESS>/15
        - <IP_ADDRESS>/13
        - <IP_ADDRESS>/14
        - <IP_ADDRESS>/13
        - <IP_ADDRESS>/22
    forwardedHeaders:
      trustedIPs:
        - <IP_ADDRESS>/16
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/18
        - <IP_ADDRESS>/18
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/20
        - <IP_ADDRESS>/22
        - <IP_ADDRESS>/17
        - <IP_ADDRESS>/15
        - <IP_ADDRESS>/13
        - <IP_ADDRESS>/14
        - <IP_ADDRESS>/13
        - <IP_ADDRESS>/22
  metrics:
    address: :8082

  # -- (Optional) Add custom Entrypoint
  edgedb:
    address: :5656
  # custom:
  #   address: :8080

# -- Configure your CertificateResolver here...
certificatesResolvers:
#   staging:
#     acme:
#       email<EMAIL_ADDRESS>#       storage: /etc/traefik/certs/acme.json
#       caServer: "https://acme-staging-v02.api.letsencrypt.org/directory"
#       -- (Optional) Remove this section, when using DNS Challenge
#       httpChallenge:
#         entryPoint: web
#       -- (Optional) Configure DNS Challenge
#       dnsChallenge:
#         provider: your-resolver (e.g. cloudflare)
#         resolvers:
#           - "<IP_ADDRESS>:53"
#           - "<IP_ADDRESS>:53"
  production:
    acme:
      email: E-MAIL
      storage: /etc/traefik/certs/acme.json
      caServer: "https://acme-v02.api.letsencrypt.org/directory"
      # -- (Optional) Remove this section, when using DNS Challenge
      #httpChallenge:
      #  entryPoint: web
      # -- (Optional) Configure DNS Challenge
      dnsChallenge:
        provider: cloudflare
        resolvers:
          - "<IP_ADDRESS>:53"
          - "<IP_ADDRESS>:53"

metrics:
  prometheus:
    entryPoint: metrics
    addRoutersLabels: true
    addEntryPointsLabels: true
    addServicesLabels: true
    headerLabels:
      label: requests_total

# -- (Optional) Disable TLS Cert verification check
serversTransport:
  insecureSkipVerify: true

providers:
  docker:
    exposedByDefault: false
  file:
    directory: /etc/traefik/conf
    watch: true

tls:
  options:
    default:
      alpnProtocols:
        - edgedb-binary
        - http/1.1
        - h2
        - acme-tls/1

If applicable, please paste the log output in DEBUG level
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:100 > Traefik version 3.0.0 built on 2024-04-29T14:25:59Z version=3.0.0
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/cmd/traefik/traefik.go:107 > Static configuration loaded [json] staticConfiguration={"api":{"dashboard":true,"insecure":true},"certificatesResolvers":{"production":{"acme":{"caServer":"https://acme-v02.api.letsencrypt.org/directory","certificatesDuration":2160,"dnsChallenge":{"provider":"cloudflare","resolvers":["<IP_ADDRESS>:53","<IP_ADDRESS>:53"]},"email":"CENSORED_EMAIL","keyType":"RSA4096","storage":"/etc/traefik/certs/acme.json"}}},"entryPoints":{"edgedb":{"address":":5656","forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"metrics":{"address":":8082","forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"traefik":{"address":":8080","forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"web":{"address":":80","forwardedHeaders":{},"http":{"redirections":{"entryPoint":{"permanent":true,"priority":9223372036854775806,"scheme":"https","to":"websecure"}}},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"websecure":{"address":":443","forwardedHeaders":{"trustedIPs":["<IP_ADDRESS>/16","<IP_ADDRESS>/20","<IP_ADDRESS>/22","<IP_ADDRESS>/22","<IP_ADDRESS>/22","<IP_ADDRESS>/18","<IP_ADDRESS>/18","<IP_ADDRESS>/20","<IP_ADDRESS>/20","<IP_ADDRESS>/22","<IP_ADDRESS>/17","<IP_ADDRESS>/15","<IP_ADDRESS>/13","<IP_ADDRESS>/14","<IP_ADDRESS>/13","<IP_ADDRESS>/22"]},"http":{},"http2":{"maxConcurrentStreams":250},"proxyProtocol":{"trustedIPs":["<IP_ADDRESS>/16","<IP_ADDRESS>/20","<IP_ADDRESS>/22","<IP_ADDRESS>/22","<IP_ADDRESS>/22","<IP_ADDRESS>/18","<IP_ADDRESS>/18","<IP_ADDRESS>/20","<IP_ADDRESS>/20","<IP_ADDRESS>/22","<IP_ADDRESS>/17","<IP_ADDRESS>/15","<IP_ADDRESS>/13","<IP_ADDRESS>/14","<IP_ADDRESS>/13","<IP_ADDRESS>/22"]},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}}},"global":{},"log":{"filePath":"/var/log/traefik/traefik.log","format":"common","level":"DEBUG"},"metrics":{"prometheus":{"addEntryPointsLabels":true,"addRoutersLabels":true,"addServicesLabels":true,"buckets":[0.1,0.3,1.2,5],"entryPoint":"metrics","headerLabels":{"label":"requests_total"}}},"providers":{"docker":{"defaultRule":"Host({{ normalize .Name }})","endpoint":"unix:///var/run/docker.sock","watch":true},"file":{"directory":"/etc/traefik/conf","watch":true},"providersThrottleDuration":"2s"},"serversTransport":{"insecureSkipVerify":true,"maxIdleConnsPerHost":200},"tcpServersTransport":{"dialKeepAlive":"15s","dialTimeout":"30s"}}
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:605 >
Stats collection is disabled.
Help us improve Traefik by turning this feature on :)
More details on: https://doc.traefik.io/traefik/contributing/data-collection/
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/cmd/traefik/traefik.go:490 > Configured Prometheus metrics metricsProviderName=prometheus
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:458 > Enabling ProxyProtocol for trusted IPs [<IP_ADDRESS>/16 <IP_ADDRESS>/20 <IP_ADDRESS>/22 <IP_ADDRESS>/22 <IP_ADDRESS>/22 <IP_ADDRESS>/18 <IP_ADDRESS>/18 <IP_ADDRESS>/20 <IP_ADDRESS>/20 <IP_ADDRESS>/22 <IP_ADDRESS>/17 <IP_ADDRESS>/15 <IP_ADDRESS>/13 <IP_ADDRESS>/14 <IP_ADDRESS>/13 <IP_ADDRESS>/22] entryPointName=websecure
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:73 > Starting provider aggregator aggregator.ProviderAggregator
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:220 > Starting TCP Server entryPointName=traefik
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:220 > Starting TCP Server entryPointName=websecure
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:220 > Starting TCP Server entryPointName=edgedb
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:220 > Starting TCP Server entryPointName=web
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *file.Provider
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *file.Provider provider configuration config={"directory":"/etc/traefik/conf","watch":true}
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:220 > Starting TCP Server entryPointName=metrics
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/file/file.go:122 > add watcher on: /etc/traefik/conf
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/file/file.go:122 > add watcher on: /etc/traefik/conf/headers.yml
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *traefik.Provider
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *docker.Provider
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *acme.ChallengeTLSALPN
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *acme.ChallengeTLSALPN provider configuration config={}
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *docker.Provider provider configuration config={"defaultRule":"Host({{ normalize .Name }})","endpoint":"unix:///var/run/docker.sock","watch":true}
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *traefik.Provider provider configuration config={}
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *acme.Provider
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > acme.Provider provider configuration config={"HTTPChallengeProvider":{},"ResolverName":"production","TLSChallengeProvider":{},"caServer":"https://acme-v02.api.letsencrypt.org/directory","certificatesDuration":2160,"dnsChallenge":{"provider":"cloudflare","resolvers":["<IP_ADDRESS>:53","<IP_ADDRESS>:53"]},"email":"CENSORED_EMAIL","keyType":"RSA4096","storage":"/etc/traefik/certs/acme.json","store":{}}
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:213 > Attempt to renew certificates "720h0m0s" before expiry and check every "24h0m0s" acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme
2024-05-05T21:32:31Z INF github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:795 > Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"middlewares":{"authentik":{"forwardAuth":{"address":"http://authentik-server:9000/outpost.goauthentik.io/auth/traefik","authResponseHeaders":["X-authentik-username","X-authentik-groups","X-authentik-email","X-authentik-name","X-authentik-uid","X-authentik-jwt","X-authentik-meta-jwks","X-authentik-meta-outpost","X-authentik-meta-provider","X-authentik-meta-app","X-authentik-meta-version"],"trustForwardHeader":true}}},"routers":{"plex":{"entryPoints":["websecure"],"rule":"Host(plex.CENSORED_DOMAIN)","service":"plex","tls":{"certResolver":"production"}},"syncthing":{"entryPoints":["websecure"],"middlewares":["authentik@file"],"rule":"Host(syncthing.CENSORED_DOMAIN)","service":"syncthing","tls":{"certResolver":"production"}},"synology":{"entryPoints":["websecure"],"rule":"Host(synology.CENSORED_DOMAIN)","service":"synology","tls":{"certResolver":"production"}},"vm":{"entryPoints":["websecure"],"rule":"Host(vm.CENSORED_DOMAIN)","service":"vm","tls":{"certResolver":"production"}}},"services":{"plex":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://CENSORED_IP:32400/"}]}},"syncthing":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://CENSORED_IP:8384"}]}},"synology":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://CENSORED_IP:5001/"}]}},"vm":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://CENSORED_IP:5001/vm"}]}}}},"tcp":{},"tls":{},"udp":{}} providerName=file
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"middlewares":{"dashboard_redirect":{"redirectRegex":{"permanent":true,"regex":"^(http:\/\/(\[[\w:.]+\]|[\w\._-]+)(:\d+)?)\/$","replacement":"${1}/dashboard/"}},"dashboard_stripprefix":{"stripPrefix":{"prefixes":["/dashboard/","/dashboard"]}},"redirect-web-to-websecure":{"redirectScheme":{"permanent":true,"port":"443","scheme":"https"}}},"routers":{"api":{"entryPoints":["traefik"],"priority":9223372036854775806,"rule":"PathPrefix(/api)","service":"api@internal"},"dashboard":{"entryPoints":["traefik"],"middlewares":["dashboard_redirect@internal","dashboard_stripprefix@internal"],"priority":9223372036854775805,"rule":"PathPrefix(/)","service":"dashboard@internal"},"prometheus":{"entryPoints":["metrics"],"priority":9223372036854775807,"rule":"PathPrefix(/metrics)","service":"prometheus@internal"},"web-to-websecure":{"entryPoints":["web"],"middlewares":["redirect-web-to-websecure"],"priority":9223372036854775806,"rule":"HostRegexp(^.+$)","service":"noop@internal"}},"serversTransports":{"default":{"insecureSkipVerify":true,"maxIdleConnsPerHost":200}},"services":{"api":{},"dashboard":{},"noop":{},"prometheus":{}}},"tcp":{"serversTransports":{"default":{"dialKeepAlive":"15s","dialTimeout":"30s"}}},"tls":{},"udp":{}} providerName=internal
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{},"tcp":{},"tls":{},"udp":{}} providerName=production.acme
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/pdocker.go:89 > Provider connection established with docker 20.10.23 (API 1.41) providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=mariadb-monitoring-and-backup-efc6655c0b879c4df2bb5ffeeb1adbe8e37aaf88addbc0cc9cc588ebad66a830 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=borgbackup-monitoring-and-backup-7ffbb799621def904bd7eb3fffbe9fe26a68483e8a0771fa14605e5a1dce522f providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=gotenberg-paperless-ngx-0b0b37409ca3ad0587f7f3d2a86cddc6a596dfa78ca55bc2844725031e34aaf3 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=broker-paperless-ngx-ccb4257f1dc282f7b6cc85cb0ea7e16219b4f975e2a5c230a359eeaf61146ab9 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=protonmail-bridge-paperless-ngx-9fe31c20c58d758966aaaf8e93fe98519edf682b2dab707a3088985e3ae0f1fa providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=tika-paperless-ngx-e3015bf1a4bc4e630839f12bb66ef153ecb488465cf02718c7635f2adbac9c27 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=worker-authentik-0e45844324972821bd1f41991b1f9066c5acb788f24c97a92b322d1250282a35 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=influxdb-monitoring-and-backup-697d7817891d6169b0d94022e2d6ae05beb75310e0d1a284264abcde78754100 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=gickup-monitoring-and-backup-5537ab57fd29df9d7fab2303c0b39eb1bbadace02a6ee1e236fe395d3d1a39eb providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=redis-authentik-7a1bdeaeafbac0f02297ad27f0a80750018dcfd739967276bb7537c236a41de1 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=postgresql-authentik-556efdbe20475f6171cc846104451a6e8c1e1e4104cb2b8317f4d8dd1cfb6523 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=mosquitto-monitoring-and-backup-696b0007081c19418d14afee3c6ceaa16e2cbc96ca2cd99964515733e1ee15c3 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/docker/config.go:184 > Filtering disabled container container=Unifi-Controller-d6f2af34f8cd0b49d0ec78d5b39969fc7938bbbb93fd2c3f9c09631ebd8f1075 providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"routers":{"authentik":{"entryPoints":["websecure"],"rule":"Host(authentik.CENSORED_DOMAIN)","service":"authentik","tls":{"certResolver":"production"}},"battlesnake":{"entryPoints":["websecure"],"rule":"Host(battlesnake.CENSORED_DOMAIN)","service":"battlesnake","tls":{"certResolver":"production"}},"edgedb":{"entryPoints":["websecure"],"rule":"Host(edgedb.CENSORED_DOMAIN)","service":"edgedb","tls":{"certResolver":"production"}},"gitea":{"entryPoints":["websecure"],"rule":"Host(git.CENSORED_DOMAIN)","service":"gitea","tls":{"certResolver":"production"}},"grafana":{"entryPoints":["websecure"],"rule":"Host(grafana.CENSORED_DOMAIN)","service":"grafana-monitoring-and-backup","tls":{"certResolver":"production"}},"homeassistant":{"entryPoints":["websecure"],"rule":"Host(homeassistant.CENSORED_DOMAIN)","service":"homeassistant","tls":{"certResolver":"production"}},"nodered":{"entryPoints":["websecure"],"rule":"Host(nodered.CENSORED_DOMAIN)","service":"nodered","tls":{"certResolver":"production"}},"ntfy":{"entryPoints":["websecure"],"rule":"Host(ntfy.CENSORED_DOMAIN)","service":"ntfy","tls":{"certResolver":"production"}},"paperless":{"entryPoints":["websecure"],"middlewares":["authentik@file"],"rule":"Host(paperless.CENSORED_DOMAIN)","service":"paperless","tls":{"certResolver":"production"}},"picoshare":{"entryPoints":["websecure"],"middlewares":["authentik@file"],"rule":"Host(i.CENSORED_DOMAIN)","service":"picoshare","tls":{"certResolver":"production"}},"portainer":{"entryPoints":["websecure"],"rule":"Host(portainer.CENSORED_DOMAIN)","service":"portainer","tls":{"certResolver":"production"}},"prometheus":{"entryPoints":["websecure"],"middlewares":["authentik@file"],"rule":"Host(prometheus.CENSORED_DOMAIN)","service":"prometheus","tls":{"certResolver":"production"}},"teleport-http":{"entryPoints":["web"],"rule":"Host(teleport.CENSORED_DOMAIN) || HostRegexp({subhost:[a-zA-Z0-9-]+}.teleport.CENSORED_DOMAIN)","service":"teleport"},"teleport-https":{"entryPoints":["websecure"],"rule":"Host(teleport.CENSORED_DOMAIN) || HostRegexp({subhost:[a-zA-Z0-9-]+}.teleport.CENSORED_DOMAIN)","service":"teleport","tls":{"certResolver":"production","domains":[{"main":"teleport.CENSORED_DOMAIN","sans":[".teleport.CENSORED_DOMAIN"]}]}},"uptime":{"entryPoints":["websecure"],"middlewares":["authentik@file"],"rule":"Host(uptime.CENSORED_DOMAIN)","service":"uptime","tls":{"certResolver":"production"}},"web":{"entryPoints":["websecure"],"rule":"Host(CENSORED_DOMAIN)","service":"web-traefik","tls":{"certResolver":"production"}}},"services":{"authentik":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:9000"}]}},"battlesnake":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:8000"}]}},"edgedb":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://<IP_ADDRESS>:5656"}]}},"gitea":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:3000"}]}},"grafana-monitoring-and-backup":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:3000"}]}},"homeassistant":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:8123"}]}},"nodered":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:1880"}]}},"ntfy":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:49152"}]}},"paperless":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:8000"}]}},"picoshare":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:80"}]}},"portainer":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:9000"}]}},"prometheus":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:9090"}]}},"teleport":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"https://<IP_ADDRESS>:3080"}]}},"uptime":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:3001"}]}},"web-traefik":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:80"}]}}}},"tcp":{"routers":{"edgedb":{"entryPoints":["edgedb"],"rule":"HostSNI(edgedb.CENSORED_DOMAIN)","service":"edgedb","tls":{"certResolver":"production","passthrough":false}}},"services":{"edgedb":{"loadBalancer":{"servers":[{"address":"<IP_ADDRESS>:5656"}]}}}},"tls":{},"udp":{}} providerName=docker
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for synology.CENSORED_DOMAIN with TLS options default entryPointName=websecure
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for syncthing.CENSORED_DOMAIN with TLS options default entryPointName=websecure
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for vm.CENSORED_DOMAIN with TLS options default entryPointName=websecure
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for plex.CENSORED_DOMAIN with TLS options default entryPointName=websecure
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/tls/certificate.go:131 > Adding certificate for domain(s) CENSORED_DOMAIN
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [synology.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=synology@file rule=Host(synology.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [syncthing.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=syncthing@file rule=Host(syncthing.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:851 > Looking for provided certificate(s) to validate ["synology.CENSORED_DOMAIN"]... ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=synology@file rule=Host(synology.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [vm.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=vm@file rule=Host(vm.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:851 > Looking for provided certificate(s) to validate ["syncthing.CENSORED_DOMAIN"]... ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=syncthing@file rule=Host(syncthing.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/tls/certificate.go:131 > Adding certificate for domain(s) *.CENSORED_DOMAIN,CENSORED_DOMAIN
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:851 > Looking for provided certificate(s) to validate ["vm.CENSORED_DOMAIN"]... ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=vm@file rule=Host(vm.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [plex.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=plex@file rule=Host(plex.CENSORED_DOMAIN)
2024-05-05T21:32:31Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:851 > Looking for provided certificate(s) to validate ["plex.CENSORED_DOMAIN"]... ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=plex@file rule=Host(plex.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:895 > No ACME certificate generation required for domains ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["synology.CENSORED_DOMAIN"] providerName=production.acme routerName=synology@file rule=Host(synology.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:895 > No ACME certificate generation required for domains ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["syncthing.CENSORED_DOMAIN"] providerName=production.acme routerName=syncthing@file rule=Host(syncthing.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:895 > No ACME certificate generation required for domains ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["vm.CENSORED_DOMAIN"] providerName=production.acme routerName=vm@file rule=Host(vm.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:895 > No ACME certificate generation required for domains ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["plex.CENSORED_DOMAIN"] providerName=production.acme routerName=plex@file rule=Host(plex.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for edgedb.CENSORED_DOMAIN with TLS options default entryPointName=websecure
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/server/service/tcp/service.go:95 > Creating TCP server entryPointName=edgedb routerName=edgedb@docker serviceName=edgedb@docker
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:400 > Adding TLS route for "HostSNI(edgedb.CENSORED_DOMAIN)" entryPointName=edgedb routerName=edgedb@docker
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [edgedb.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=edgedb@docker rule=HostSNI(edgedb.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:851 > Looking for provided certificate(s) to validate ["edgedb.CENSORED_DOMAIN"]... ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=edgedb@docker rule=HostSNI(edgedb.CENSORED_DOMAIN)
2024-05-05T21:32:33Z DBG github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:384 > Trying to challenge certificate for domain [edgedb.CENSORED_DOMAIN] found in HostSNI rule ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=production.acme routerName=edgedb@docker rule=Host(edgedb.CENSORED_DOMAIN)
2024-05-05T21:32:34Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:34Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 7879a10142195a55
2024-05-05T21:32:34Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: f820ddc51d8c6408
2024-05-05T21:32:34Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:34Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:35Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:35Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:36Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:36Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:36Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: a173f240f26c7781
2024-05-05T21:32:36Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: a173f240f26c7781
2024-05-05T21:32:50Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:50Z DBG github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:196 > Service selected by WRR: 08094eb2651d80a0
2024-05-05T21:32:56Z DBG github.com/traefik/traefik/v3/pkg/tcp/proxy.go:41 > Handling TCP connection address=<IP_ADDRESS>:5656 remoteAddr=<IP_ADDRESS>:43881
2024-05-05T21:32:56Z ERR github.com/traefik/traefik/v3/pkg/tcp/proxy.go:75 > Error while handling TCP connection error="readfrom tcp <IP_ADDRESS>:48538-><IP_ADDRESS>:5656: tls: client requested unsupported application protocols ([edgedb-binary])"
2024-05-05T21:32:56Z DBG github.com/traefik/traefik/v3/pkg/tcp/proxy.go:104 > Error while terminating TCP connection error="tls: CloseWrite called before handshake complete"

Hey @daniel156161.
Thanks for reaching out.
From our point of view, it's a feature proposal, but we’re unsure about the use case and the traction it will receive. We are going to leave the status as kind/proposal to give the community time to let us know if they would like this idea.
We will reevaluate as people respond.
Conversation is time-boxed to 6 months.

EdgeDB sounds like an edge case ;-)
When using TCP without TLS with a proprietary protocol, you can try to use .router.rule=HostSNI(`*`). If it uses a custom port anyway, that should just work for a single target service.
Note that this disables differentiation between domains for Traefik, so if you want to use different environments, you would need to use different IPs or ports.

I would definitely appreciate getting EdgeDB to work with Traefik.

Me too, having the binary edgedb protocol work would be wonderful, without having to use the slower http backend.

Hello,
This proposal was opened more than 6 months ago with almost no traction.
We won't add it to the Roadmap yet and we prefer to close it.
We'll re-open it later if necessary.


Display only "Begin Upload" button if any files are chosen

It would be great if the "Begin Upload" button only is visible, when there are any files chosen.

Also implemented. :D


dPaste went poof

As of 5 Sep 2022 at 08:46am MDT. FossHost Boston node went off the internet, unreachable, gone, therefore dpaste also went offline.
As of right now, it is still unknown what causes it.
The latest update was at Sep 5 11:29 am.

"ISP console doesn't report any issues; we'll update here when we have any root-cause/ETR" - Corwin.  Sep 5 11:29 am.
"boston aarch nodes are rebooting." - kryptonian. Sep 6 3:03 am.
"Issue seems to be related to IPv6 routing." - kryptonian. Sep 6 5:21 am.
"We are opening a ticket with the DC to get RCA assistance." - Corwin. Sep 6 9:34 am.
I will update this issue page regarding what happens next or if there is a new update from FossHost.

Resolved as of today.


[1.2-stable] Update Project Templates in the VSIX for ARM64

Numerous build issues in new blank applications and allows creation of Appx in Arm64 VS
Issues with double-building due to casing differences and uses the VC++ recommendation (C# doesn't care).
update vsix versions by bpulliam · Pull Request #3100 · microsoft/WindowsAppSDK (github.com)
Normalize ARM64 platform in project templates by evelynwu-msft · Pull Request #3101 · microsoft/WindowsAppSDK (github.com)

Internal link

/azp run

/azp run

/azp run TransportPackage-Foundation-PR


add custom runner for Cori pipeline

We can't use the runner cori-login to run Cori pipeline since its used for production, we should register a new runner with a new user account. This new user account will be used to serve buildtest regression test.
Once runner is registered we can run pipeline automatically for time being we will run pipeline manually.

this was fix in #589 using cori20-siddiq90 runner that runs via user siddiq90 see https://gitlab.nersc.gov/nersc/consulting/buildtest/-/pipelines/5588

this was fix in #589 using cori20-siddiq90 runner that runs via user siddiq90 see https://gitlab.nersc.gov/nersc/consulting/buildtest/-/pipelines/5588


Rename astrodb_scripts to astrodb_utils

Since we changed the name of the astrodb_utils package, the imports needed to be changed.

Yes to everything except update_regimes/. Those are one-off scripts and don't need to be updated.


State docs fixes

What Problem/Issue is it trying to solve?
Fixes in GitHub .md files for upcoming web docs.
Change List

Relative links for images replaced with https://raw.githubusercontent.com/.
⚠ Coverage badges links also changed to raw file links.
Relative links in the state docs replaced with global links.
$ heading in rx-state.md changed to $ (state observable). Otherwise, it's not working as anchor link :)

Merged changes to docs


Initial travis file

cc: @czue @esoergel

and so the travis sludge begins...

:eyes:

what's the end game here? travis deploys to a server?

:angel: build failures, bat:man: !  Does travis run tests on every commit for this repo or is it just 'cause they were pushed individually?

haha! yeah they were pushed individually. i think the end game here is to have our entire deploy_stack run on travis so we know if it works. then we can test certain things about the setup as well. the playbook returns 0 or 1 so it makes a good script for travis testing. was inspired by this blog post and @millerdev's pain in getting up and running with ansible.

:white_check_mark: for now just syntax checking. hopefully we can test more roles in the future. just don't want everyone's branch to show an :x: while i take my time figuring this out

@benrudolph Huge fan of this

Merging so I can get my PR to pass, assuming you will open a new PR for more changes on this branch

would be amazing if we got this fully working. might find ourselves wrestling with travis's runtime restrictions.

amaze:crystal_ball:s


Clear stale branches?

It looks as though the only two branches currently in use are master and gh-pages. It might be helpful to clean up the others. I was a bit confused by the presence of the gui branch, which saw activity as recently as two months ago. But my understanding is that the frontend code is now being kept in gh-pages?
Perhaps I'll wait a few days to see if people raise objections, and if not, I'll delete the older branches. (They can always be restored.)

you're right, the gui branch is obsolete, I think I meant it to be what gh-pages is now. Anyway, deleted it already. :)
projects.0.0.9 is an archived version - I think - of the projects with an old schema. I'll have a look later.

I'm going to delete the projects_0.0.9 branch. In case someone wants to restore it, the latest commit was 415f2a308b51917edcb35ebc57e27e4a9e6c3964.