Add CMORizer for CT2019

This PR adds a CMORizer for the variable co2s for CT2019.

Tasks

[x] Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Make sure your code is composed of functions of no more than 50 lines and uses meaningful names for variables
[x] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[x] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
[x] Please use yamllint to check that your YAML files do not contain mistakes
[x] (Only if really necessary) Add any additional dependencies needed for the diagnostic script to setup.py, esmvaltool/install/R/r_requirements.txt or esmvaltool/install/Julia/julia_requirements.txt (depending on the language of your script) and also to meta.yaml for conda dependencies (includes Python and others, but not R/Julia)
[x] If new dependencies are introduced, check that the license is compatible with Apache2.0

New data reformatting script

[x] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[x] Add the new dataset to the table in the documentation
[x] Tag @mattiarighi in this pull request, so that the new dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.

Closes #1603.

There might be some issues regarding the definition of the variable, I close this for now an reopen it when the issues are resolved!

Solved the issue in ESMValGroup/ESMValCore#594, there are no changes for this CMORizer necessary. Ready for review!

Good idea to have download on-the-fly!

Is the codacy issue about FTP critical? @bouweandela

@schlunma there are some conflicts after #1545. You also need to add a bibtex file for your reference.

Is the codacy issue about FTP critical? @bouweandela

I tried to use a secure connection via FTP_TLS and pysftp, but in both cases the error messages suggest that the server does not support that:
paramiko.ssh_exception.SSHException: No hostkey for host aftp.cmdl.noaa.gov found.


update IM OperandRequest in OperandConfig template

Update IM OperandRequest in OperandConfig:

adding two operands: ibm-mongodb-operator and ibm-commonui-operator
removing ibm-cert-manager-operator, ibm-management-ingress-operator and ibm-ingress-nginx-operator

Test and verify in a build, it will update IAM internal OperandRequest correctly to remove discontinued services

issue: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/57518
Test Steps

Install CS4.0, and create IM OperandRequest ibm-iam-request with ibm-cert-manager-operator, ibm-management-ingress-operatorandibm-ingress-nginx-operator` included.
Update IM Opreq in  Opcon template like

operandRequest:
    requests:
        - operands:
              - name: ibm-mongodb-operator
              - name: ibm-commonui-operator
          registry: common-service

restart ODLM pod, will see above three operators removed from IM OperandRequest


Incomprehensibly large .logs

Describe the bug
So I've been cleaning my files, and noticed that my MultiMC instances weigh a ton.
It's not a problem with the modpack itself, but i have no idea which specific mod might cause the logs to be massive.
I had to download Vim to open the massive files even.
Expected behavior
The logs not to weigh in excess of megabytes
Observed/actual behavior
They did. Every microsecond or so ( there are like thousands logs every second) a problem with OpenGL is logged
evidence1.txt
ev2.txt
.
Steps To Reproduce
sry i have no idea where else to put the evidence
Modpack version
Sry but not modpack
Launcher
MultiMC
Install method
Using with additional mods/something else (please write below)
Additional context
simply, the more i played the bigger the files got. after like 20 mins there is a 600 mb latest.log
they get compressed to a thousand fold size decrease tho

Please send me the logs to pastebin or equivalent.

Sorry, I didn't notice you already sent logs. The issue is very likely caused by the shaders you are using. Here are my suggestions:

Make sure you are using the latest version of FO, which has the latest Iris - that may already fix it
If you want shaders, I suggest you to pick some from here: https://github.com/IrisShaders/Iris/blob/trunk/docs/supportedshaders.md
Try running it without shaders as well
Update your graphics drivers if possible

Have you an overlay like overwolf? Remove it, they have issues with Minecraft


00 01 dev and cf

Requirements for Contributing a Bug Fix

Fill out the template below. Any pull request that does not include enough
information to be reviewed in a timely manner may be closed at the maintainers'
discretion.

Identify the Bug

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Release Notes

Reopening pull request for first two branches that now pass markdown linting


Stateless hierarchy builder

Closes https://github.com/iTwin/presentation/issues/6.
The PR contains:

The proof of concept for a stateless Models Tree hierarchy builder.
Substantial load tests' rewrite for testing native and stateless implementations.
Some dependency updates

Did you start with rxjs v6 or used v7 from beginning? Do you know if there are any significant benefits in v7 and we should bump version in @itwin/components-react too?

I don't think there was a specific reason I chose 7 over 6 besides it being the latest version. Some online material suggests there're significant performance and memory footprint improvements - not sure that warrants an upgrade in @itwin/components-react.


Tech Talk 6.0 React Website

Tech Talk is a monthly event organized by softamplify technologies where a particular technology is presented by an expert, followed by a Q&A or Workshop.

You did well.
I have created a branch for you and merged with your branch
Good luck.


Generalize _xgroupBy to _xreduceBy

reduceBy, indexBy, countBy can now act as transducers; Bonus: groupBy no longer clones each step of the way in transducer-mode

lgtm; had to remind myself of the difference between _hasMethod and _checkForMethod
:cow2:

I don't see hasMethod anywhere FWIW.

hasMethod expired in https://github.com/ramda/ramda/pull/1400

@CrossEye  @davidchambers

:herb:


Sticky Scroll doesn't show wrapped text when Word Wrap is enabled

Type: Bug

Open a file with a function whose header is longer than the horizonal width of your vscode screen. Position the vertical scroll such that the function header is in the middle of the screen.
Toggle Word Wrap. The horizontal scroll bar should disappear, and the entire function header should be visible with part of the text wrapped to the following "line" (but not with a line number).
Toggle Sticky Scroll.
Scroll down into the function beyond the function header. Since sticky scroll is enabled, the header remains at the top of the screen. However, the wrapped text resulting from 'Word Wrap' is not displayed. So only part of the function header is actually 'stuck' at the top of the screen, not the full header.

VS Code version: Code 1.73.1<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T03:54:53.913Z)
OS version: Linux x64 5.17.11-051711-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12700 (20 x 3590)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
15.36GB (5.99GB free)

Process Argv
--unity-launch --crash-reporter-id 55a2c726-f3bc-456b-a46e-a516d8fee2b5

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
wayland

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
2e4cg342:30602488
3d0df643:30613357
89544117:30613380
fim-prod:30623723

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


RTL

i think that we have some issue for rtl direction

We don't have any issue, if you have an issue, you say whats your issue, and RTL is not done by me.


HNC: find a new way to test unpropagatable objects

Since #1489, HNC has been able to propagate cluster-admin rolebindings and therefore the test for #328, #605 and #771 have broken. We need to find another way to stop HNC from propagating these objects, possibly by having some special-purpose test webhook or something.

Another possible way to do it:

Create a Role in the parent and forbid it from being propagated
Create a RoleBinding in the parent

Usually, RBs cannot be created with the Roles they refer to existing first, so this should cause an error.

/good-first-issue

Replaced by https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/13
/close


existing tabs in vertical/horizontal splits should be reused

Issue Type: Bug
I usually have 3 vertical splits with multiple open file tabs in each.
When clicking on a class reference in vertical split 1, if that class is already opened in split 2 I expect it to gain focus in that split rather than open a new tab in a current split (1).
This is true not only when clicking on a class reference, but for all other actions like:

open command platter, type class name, if I already have it open in a split it should gain focus in that split (or come to focus).
when using "Find all references" and clicking on the overlay
clicking on the file in the explorer
I'm sure there are more entry points that I'm missing.


Run PTY tests in CI

The suite of tests dedicated to testing PTY winsize is now failing with the following error:
failed to copy from pty to stdout; handled EIO

Would be nice to figure this one out so we don't have a mismatch between CI and local testing.

Oh, I remember now. I wrote https://github.com/stateful/runme/pull/168#issuecomment-1457025344 but I think the root cause of the failed test was different. This error is handled and there is a description why it might happen:
// Linux kernel returns EIO when attempting to read from
// a master pseudo-terminal which no longer has an open slave.
// See https://github.com/creack/pty/issues/21.
if errors.Is(err, syscall.EIO) {
	c.logger.Debug("failed to copy from pty to stdout; handled EIO")
	return
}

@adambabik
Hmm, gotcha. The failed ci is here if you wanna check it out, but the logs seem overall fine.
Needs further investigation I guess. Debugging CI is complicated :(

The log is a bit tricky to follow up because the tests are run in parallel but I think this is a group:
2023-03-06T15:29:55.241Z	DEBUG	runner/service.go:301	sending data	{"_id": "cg30dso3digqu3rk1or0", "lenStdout": 46, "lenStderr": 0}
2023-03-06T15:29:55.242Z	DEBUG	runner/command.go:268	failed to copy from pty to stdout; handled EIO
2023-03-06T15:29:55.242Z	INFO	runner/service.go:317	command finished	{"_id": "cg30dso3digqu3rk1or0", "exitCode": 2}

The command finished with the exit code 2 but it had some output. Unfortunately, due to the test using require.EqualValues(t, 0, result.ExitCode) you didn't have a chance to see what the output is as it is checked in the next line. I recommend switching to:
assert.EqualValues(t, 0, result.ExitCode)
assert.EqualValues(t, "24\r\n80\r\n", string(result.Stdout))

Overall, you can consider a few things:

In the Execute method where cfg := &commandConfig{ ... } is instantiated, pass Logger:      logger instead of Logger:      r.logger so that the command struct logs also contain _id.
On a branch, you can temporarily modify the line which execute tests (run: SHELL=/bin/bash TZ=UTC go test ./...) in .github/workflows/ci.yml to run only a single test with the -run option.

Figured this out. Basically, the tput command requires to know the terminal name, which is usually stored in $TERM. CI doesn't do that though, so I just provided the variable -T linux. See #170

Figured this out.

Was an error message in stdout?

Was an error message in stdout?

Yep. Gets sent by tput command.


Streaming grpc call sporadically experiencing a "google.protobuf.message.DecodeError" that manifests as an empty response rather than an exception on the client

What version of gRPC and what language are you using?
1.59.0
What operating system (Linux, Windows,...) and version?
Linux (python:3.10-slim Docker image)
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.10
What did you do?
We have a streaming grpc call that looks like this:
  rpc ExternalSensorExecution (ExternalSensorExecutionRequest) returns (stream StreamingChunkEvent) {}

message StreamingChunkEvent {
  int32 sequence_number = 1;
  string serialized_chunk = 2;
}

This grpc call always either streams at least one StreamingChunkEvent or raises an Exception on the server.
We are sporadically seeing the following error in the client logs when making this gRPC call:
_common - Exception deserializing message!
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/grpc/_common.py", line 89, in _transform
    return transformer(message)
google.protobuf.message.DecodeError: Error parsing message

When this happens, rather than receiving an Exception on the client, the client receives an empty list back from the rpc call (as though the iterator raised a StopIteration early) so we don't have a way to reliably detect the error.
Unfortunately we don't yet have a reliable way to reproduce this, but we are seeing it across multiple customers using this gRPC call (some much more than others, which implies that certain responses are more likely to trigger the DecodeError).
There are two mysteries here for us:

Why protobuf is failing to parse a relatively simple response that is just an int and a string (the string is limited to 4MB in size)
Why the resulting Exception isn't surfaced to the client

What did you expect to see?
Either no protobuf error, or at least an Exception on the client
What did you see instead?
An error message in the logs that is swallowed instead of raising an Exception on the client
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?

Sorry to hear this issue. Unfortunately It's hard to say what's wrong based on current information, we'll need some sort of reproduction case to further debug this.

@XuanWang-Amos appreciate that its hard to give guidance here without a way to reproduce. Is there any logging that we can add on our side that might help give more information about what's going on?

Hi @gibsondan have you solved this issue? I am running into the same issue, with a grpc call (not streaming).

I resolved this by moving the call to no longer be streaming.


No longer count heartbeat instruction as own heartbeat

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

This PR is no longer applicable. We have excluded this is the cause of the connection issues, and the change makes no difference. The optimisation included in the HeartbeatMonitor can stay.
However, we have made changes to the HeartbeatMonitor structure and logging. This is included in PR #211


cmsRun logs are represented as byte literal

Impact of the bug
Log files (at least cmsRun logs)
Describe the bug
Logs like cmsRun1-stdout.log (e.g. https://cms-unified.web.cern.ch/cms-unified/joblogs/pdmvserv_RVCMSSW_14_0_0ZpToEE_m6000_14TeV__STD_2026D98_PU_240226_210724_9408/50660/RecoGlobalPU_2026D98PU/00b82ad5-0748-468a-942f-7b237ed79bec-10-1-logArchive/job/WMTaskSpace/cmsRun1/cmsRun1-stdout.log) seem to contain now
b"Setting up Frontier log level\nBeginning CMSSW wrapper script\n ...

The newlines represented as two characters \n instead of a real newline is particularly annoying.
How to reproduce it
N/A
Expected behavior
Log file formatted as
Setting up Frontier log level
Beginning CMSSW wrapper script
...

Additional context and error message
N/A

This has been resolved through https://github.com/dmwm/WMCore/pull/11933
Which actually closed another ticket that was duplicating the issue reported in here. Thanks for opening this up though, Matti.

Thanks!


CSSWG: fix FPWD boilerplate

See https://www.w3.org/TR/2021/WD-css-cascade-5-20210119/#status for an example.

Why is this closed? I'm not aware of an update to the Pubrules, and the previous version was not correct per Pubrules.
See https://www.w3.org/TR/2022/WD-vc-data-integrity-20221110/#sotd for a recent FPWD publication.

Ah, sorry, the files it edited were moved to the bikeshed-boilerplate project over a year ago, so I figured it must have been fixed over there.

I see. Thank you.


Detect broken anchor links

🚀 Feature
We can detect broken links now, but another thing that can break easily is anchor links. As we currently auto-generate ids based on heading text, rewriting a heading can break linking, and it's not easy to notice it.
We need a way to check anchor links at build time too, fail fast, and report errors

That would be amazing! We were thinking about adding this to our documentation setup (I was initially looking into something like remark-validate-links).

If anyone else is desperately waiting on this feature, I was able to get broken link detection set up in CI for my Docusaurus website using remark-validate-links and a GitHub action.

Here's my GitHub action YAML file (line 34-35 are the relevant lines)
Here's my lint.sh file (very tiny, you could also skip this step by launching a NPM/yarn script in package.json from the GitHub action directly, but I wanted to keep it separate)
Here's my remark config (line 16 is the relevant line, I also do a whole bunch of other checks)

Thanks @Zamiell that's useful to know how you made this work :)
We'll probably build something more "integrated" on top of the existing broken links checker (which only runs at built time), but having a remark linter could also be helpful to "pre-check" the links.

+1 for this feature,
Also slightly related (I can create a new ticket if you think it's adequate)
If your file is called docs index.md and the link points to docs Index.md it will work in OSX but it will fail in the linux CI 😕
I've tried to implement some workaround modifying this function and should not be very complicated. I think it would be great if docusaurus warned about this situation!
Thx for the nice work you do 🙏

Thanks for reporting @xiaogaozi
Note as part fo the MDX 2 migration (https://github.com/facebook/docusaurus/pull/8288), {#headingId} is not a valid syntax anymore, and Titus suggests we use {/*#headingId*/} instead.
It should also be possible to escape ids: \{#headingId}
Make sure to adapt once we upgrade to MDX 2

@slorber Actually I use markdownUtils.parseMarkdownHeadingId() to parse heading, so maybe I just need upgrade @docusaurus/utils package once Docusaurus upgrade to MDX 2?

Thanks to all the folks who contributed to this issue, I managed to implement the broken anchor links detection for both npm start and npm run build in the docs.knapsackpro.com repo.

Packages
npm install --save-dev concurrently
npm install --save-dev remark-cli
npm install --save-dev remark-validate-links

package.json
{
  "scripts": {
    "...": "...",
    "remark": "remark",
    "remark:once": "npm run remark -- --quiet --frail --use remark-validate-links docs/",
    "remark:watch": "npm run remark -- --quiet --frail --use remark-validate-links --watch docs/"
    "start": "concurrently \"npm run remark:watch\" \"npm run typecheck:watch\" \"docusaurus start\"",
    "build": "npm run remark:once && npm run typecheck && docusaurus build",
}

Links
For Remark to do its job, you need to use relative file paths in markdown files, which is what Docusaurus recommends anyways (see File paths and URL paths and Markdown links).
Here's an example commit where we changed url paths to relative file paths.

As a user, I've looked at "how can I make sure the links in the docs are OK?" problem today, some findings:

I obviously expect that it's the documentation generator's job to check the links, but it looks like at this point I need to work-around this.

Using remark here feels like a fundamentally wrong approach --- documentation generator generates HTML, which is the ground truth. The right approach is to check the links in HTML --- that is guaranteed to be correct, and moreover is polymorphic in the input markup.

Turns out my local setup with remark actually did miss a couple of broken links exactly because what remark thinks the resulting HTML would be is different from the actual HTML

Luckily, there's this nice no-nonsense tools for checking links in the resulting HTML: https://github.com/untitaker/hyperlink
$ npx @untitaker/hyperlink build --check-anchors

Was exactly how I found some broken links missing by remark.


fixes wrong order of fields when binding the variables.

Fixing #19 the order of the fields to match the variable order when bound.

Thanks!


tsc: "Cannot read properties of undefined (reading 'parent')"

🔎 Search Terms
tsc "Cannot read properties of undefined (reading 'parent')" crash
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABAQQBQEpEG8BQjEQIDOUiJAhlAKaIC8iYIANkwNw56JNWkAe7+GMESoK1RAEJa9Ri0y58+ANq8AunTJRKVAYgC+HfITBE43AHRM4Ac1S907Aziq8ADnABOpACZVg5ZlJkdiA
💻 Code
function A() {
  const state = null;

  let x;
  if (state !== null) {
    [x] = state;
  }

  console.log(x);
}

export default A;

🙁 Actual behavior
tsc crashes in some cases when using array destructing without const, let or var in JavaScript files (with compilerOptions.allowJs set to true in tsconfig.json).
The issue only occurs when compilerOptions.strict is set to true.
In the specified playground link, I think the error message (thrown in the JavaScript console) differs in browsers other than Safari, but the result is the same (TypeScript crashes).
🙂 Expected behavior
TypeScript should not crash.
Additional information about the issue
There is already a similar issue #57582 which was fixed by #57586, but the proposed fix does not work for this issue.
I don't have much knowledge of the TypeScript codebase but I think it might be possible to fix the issue with a similar approach like in #57586:
In getIteratedTypeOrElementType, reportTypeNotIterableError should only be called if errorNode has a value, e.g.:

This particular repro case was already fixed by https://github.com/microsoft/TypeScript/pull/57586

Ah I see, I thought this was already released with v5.4.5.


[Bug]: LightBot Dotnet sample error

Language
C#
Version
latest
Description
We encountered the following errors while running the .NET sample of Lightbot. The errors persist and keep repeating even when I choose 'Continue' in the debugger.

Message=
Source=
StackTrace:
at c (https://staticsint.teams.cdn.office.net/teams-modular-packages/hashed-assets/precompiled-web-worker-inner~i-7640a2a365c05855.worker.js:1:2978927)
at https://staticsint.teams.cdn.office.net/teams-modular-packages/hashed-assets/precompiled-web-worker-inner~b-7c46793c292c6494.worker.js:1:1106146
Reproduction Steps
1.The issue occurs after pressing F5 or selecting the Debug option.

Can you share repro steps? It looks like the debugging is breaking at Javascript code.

Hi @singhk97 ,
Repro steps ,

open the solution file on visual studio.
setup dev tunnel and Provide "Prepare app dependencies" through Teams toolkit.
click in debug or press F5 , it will lead to the error

Please find the below video
https://github.com/user-attachments/assets/a42ae317-5280-490b-9781-71d6f26799a4

closing as the issue seems to be related to developer project debugger setup and not the SDK itself.


true Required?

[EDIT by @guardrex to fix the character encoding]
Is it possible that <MonoLinkerI18NAssemblies>all</MonoLinkerI18NAssemblies> is not taking into account when the linker is disabled? For development builds this seems to be the default since 3.2.0 Preview 2.
This is working for me:
<PropertyGroup>
  <BlazorWebAssemblyEnableLinking>true</BlazorWebAssemblyEnableLinking>
  <MonoLinkerI18NAssemblies>all</MonoLinkerI18NAssemblies>
</PropertyGroup>

See also https://github.com/dotnet/AspNetCore.Docs/issues/15679

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

ID: 861a95e9-b329-6408-3127-9806c50a00dc
Version Independent ID: f1bb4fd6-29cd-4e11-e912-9c86b351bc31
Content: Configure the Linker for ASP.NET Core Blazor
Content Source: aspnetcore/host-and-deploy/blazor/configure-linker.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @catlan ... stand-by ... these issues are usually triaged on Fridays.

Cc @SteveSandersonMS


Amend Windows Reproducible Ant Check To Be Less Strict

Fixes #4062
Update the ant validation logic in the windows reproducible build script to allow any minor version of the correct major version. Both are defined in the script header, 1.10.{X} will be treated as allowed, rather than pinning to the exact version in the SBOM.

Tested OK locally.


Tests that snapshot error output, including error class

To make sure something like https://github.com/prisma/prisma/pull/8965 can not accidentally regress or happen again.

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


Print and PDF

print-friendly
pdf generation support

We still need to link in the PDF, and sort out icons

This is still a WIP


Update the DAODAO <> DAOstar integration

Goal is to (1) integrate query to DAODAO's indexer to daostar.org explorer frontend, AND/OR (2) deploy an update to the DAODAO factory so that it emits the right events for future DAOs (or figure out some other workaround) so that future DAODAO DAOs and daoURIs are indexed in our explorer.
Background:

Isaac and Josh recently updated the registration & indexing pattern for daoURI. We also redeployed the registration factory contracts across most chains. In particular, we noticed that many frameworks, e.g. Aragon and Snapshot X, had deployed DAOs with daoURI embedded in the contract itself, but we didn't have an indexing approach to capture all these DAOs.
DAODAO, daoURI has been configured for a while, it exists on DAODAO DAOs (though usage may not be much).
Noah has an indexer that is very complete, that has all the daoURIs.

In today's call with Noah and Jake from DAODAO, we agreed the simplest thing would be to ask for a query to incorporate into our explorer frontend to Noah's indexer, which he maintains for all DAODAO DAOs. @ipatka will send the basic structure of the request we want to Noah in the TG chat.
There's also some work that needs to happen on DAODAO's end, i.e. a lot of the daoURIs for current DAOs on DAODAO may be empty, so in the future they may want to update the default reference membersURI, proposalsURI, governanceURI, contractsURI, issuersURI, etc. so that each DAO is serving non-empty information by default.

Josh pinged Noah and Jake with a broad schema request, waiting on reply.

Noah Saso, [Aug 23, 2023 at 12:39:29 PM]:
curl -v https://search.daodao.zone/indexes/INDEX/documents\?limit=10000 -H 'Content-Type: application/json' -H 'Authorization: Bearer 29547412f05b2a4a52fe8b1f000f03206c9e650f66900a945370ff4ee616f659'
replace INDEX with daos for Juno DAOs, osmosis_daos for Osmosis DAOS, or stargaze_daos for Stargaze DAOs
output looks something like this:
{
"contractAddress": "juno10h0hc64jv006rr8qy0zhlu4jsxct8qwa0vtaleayh0ujz0zynf2s2r7v8q",
"codeId": 2454,
"block": {
"height": "9559797",
"timeUnixMs": "1691898715175"
},
"value": {
"admin": "juno10h0hc64jv006rr8qy0zhlu4jsxct8qwa0vtaleayh0ujz0zynf2s2r7v8q",
"config": {
"name": "DAO DAO",
"dao_uri": "https://daodao.zone/dao/juno10h0hc64jv006rr8qy0zhlu4jsxct8qwa0vtaleayh0ujz0zynf2s2r7v8q",
"image_url": "ipfs://bafkreiefe4icv32rsn5l43p776d5rd4yk6expmiita5jt5tqqugc65mbua",
"description": "A DAO that builds DAOs.",
"automatically_add_cw20s": false,
"automatically_add_cw721s": false
},
"version": {
"version": "2.1.0",
"contract": "crates.io:dao-core"
},
"proposal_modules": [
{
"prefix": "A",
"status": "enabled",
"address": "juno1hk37s260qdcxtv0qz3fzgr9cft7z2vt8shk2p96jxp3fxv0zvj6s47muex",
"info": {
"version": "2.1.0",
"contract": "crates.io:dao-proposal-single"
}
},
{
"prefix": "C",
"status": "enabled",
"address": "juno16t9xlgeg6vf08t550lsutdc30a39d95alt3yar50kkgdyt38ckvqrpxx6r",
"info": {
"version": "2.1.0",
"contract": "crates.io:dao-proposal-multiple"
}
},
{
"prefix": "B",
"status": "disabled",
"address": "juno13hfmp0tck77nwd6uu28t3envzpa6qmhuwlt6q5e4txkj6m5sf2wsmjwvmt",
"info": {
"version": "2.0.2",
"contract": "crates.io:dao-migrator"
}
}
],
"voting_module": "juno18mgqtspuydkn9kx4khp7652x3dmg9teryj845dz99tfp5jar6y5q4fks0z",
"active_proposal_module_count": 2,
"total_proposal_module_count": 3,
"votingModuleInfo": {
"version": "2.1.0",
"contract": "crates.io:dao-voting-cw20-staked"
},
"createdAt": "2022-08-11T20:17:10.234Z",
"adminInfo": null,
"proposalCount": 11,
"polytoneProxies": {}
}
}
Homepage:
https://daodao.zone/dao/CONTRACT
Info for one DAO:
https://indexer.daodao.zone/CHAIN/contract/CONTRACT/daoCore/dumpState
is one of these the DAO URI? ^
and CHAIN is one of:

juno-1
osmosis-1
stargaze-1

@Rashmi-278 If you can start querying the thing above that would be great; added you to the TG chat with DAODAO.

Note from Telegram chat,
We would be including the empty DAO URI strings too as it would help announce that a given contract self-identifies as a DAO

From today's conversation: Rashmi is working on improving this / converting their data format into the version we need for our frontend. Effectively, instead of fetching the data from the DAOs' own daoURIs, we are fetching it from the DAODAO's proprietary API.
Just a note that I would like to keep this issue open until we are fetching data from the DAOs themselves in the canonical way.

We also talked about the need to paginate to deal with the 1000s of DAOs coming from DAODAO.

Hooray to getting 1000s of DAOs!

No progress this week.

Any progress on this, Rashmi?

No updates yet.

No updates.

DAODAO integration is working on localhost!
Small issues: what is mainnet vs. ethereum? Why are these different?
It should "juno" not "junos".

Actively being worked on here, https://github.com/metagov/daostar/pull/185 Juno and Osmosis are ready
Preview here: https://deploy-preview-185--whimsical-cuchufli-3a5565.netlify.app/explore
PR is ready to merge to display Juno and Osmosis Regsistration Instances
Facing some issues with displaying Stargaze registration instances,
Working on debugging the issue and pagination
Discuss:
How to paginate?
Our options are,

Pagination
Instead of loading all items at once, implement pagination. Load a certain number of items (e.g., 100) initially, and then load more as the user navigates through pages.
Infinite Scrolling
As an alternative to traditional pagination, you can use infinite scrolling, where more items are loaded automatically or on demand as the user scrolls down.
Load on Demand
Implement a feature to load additional items on demand. For example, you could have a "Load More" button at the end of the list or use a scroll event to trigger the loading of more items.

Great progress!

Stargaze DAOs aren't being displayed as none of them have a DAO Name
curl -v "https://search.daodao.zone/indexes/stargaze_daos/documents?limit=5" ^      -H "Content-Type: application/json" ^      -H "Authorization: Bearer 29547412f05b2a4a52fe8b1f000f03206c9e650f66900a945370ff4ee616f659"
Response:
{   "results": [     {       "contractAddress": "stars1yq8vkp8e9w0f8vmzqchzvhzdpgw4f3xare67s7uh6nps4d58z2gqph2sde",       "codeId": 0     },     {       "contractAddress": "stars1yrlwe5fwumrprjhx8edwp5s666gzzdw88cflpg86q53jftnnp7zswqsx3j",       "codeId": 0     },     {       "contractAddress": "stars1yrf6t5rjuk7un6saunvv43map9v692h5ge6vanv4tekjwsxfmfyqgnse56",       "codeId": 0     },     {       "contractAddress": "stars1yzjz9pkufaqam43ydxdh55v0jk36ur6yjpaq0ay5dvug59c0hy9qgevxdr",       "codeId": 0     },     {       "contractAddress": "stars1yqz6z3xssn0alf3862jj2z8quj2wttu8kggu29wjkcpct7ktsqgq9h52vc",       "codeId": 0     }   ],   "offset": 0,   "limit": 5,   "total": 204 }

Closing this as this integration is completed.

Refer PR https://github.com/metagov/daostar/pull/185


[Bug]: Cloud controller manager crashes

Description
Cloud controller always crashes, it sometimes works again after deleting pod
Cloud controller manager

Kube.tf file
locals {
  # You have the choice of setting your Hetzner API token here or define the TF_VAR_hcloud_token env
  # within your shell, such as such: export TF_VAR_hcloud_token=xxxxxxxxxxx
  # If you choose to define it in the shell, this can be left as is.

  # Your Hetzner token can be found in your Project > Security > API Token (Read & Write is required).
  hcloud_token = "xxxxx"
}

module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token

  # Then fill or edit the below values. Only the first values starting with a * are obligatory; the rest can remain with their default values, or you
  # could adapt them to your needs.

  # * For local dev, path to the git repo
  # source = "../../kube-hetzner/"
  # If you want to use the latest master branch
  # source = "github.com/kube-hetzner/terraform-hcloud-kube-hetzner"
  # For normal use, this is the path to the terraform registry
  source = "kube-hetzner/kube-hetzner/hcloud"

  # You can optionally specify a version number
  # version = "1.2.0"

  # Note that some values, notably "location" and "public_key" have no effect after initializing the cluster.
  # This is to keep Terraform from re-provisioning all nodes at once, which would lose data. If you want to update
  # those, you should instead change the value here and manually re-provision each node. Grep for "lifecycle".

  # Customize the SSH port (by default 22)
  ssh_port = 52222

  # * Your ssh public key
  ssh_public_key = file("~/.ssh/id_ed25519_hetzner.pub")
  # * Your private key must be "ssh_private_key = null" when you want to use ssh-agent for a Yubikey-like device authentification or an SSH key-pair with a passphrase.
  # For more details on SSH see https://github.com/kube-hetzner/kube-hetzner/blob/master/docs/ssh.md
  ssh_private_key = file("~/.ssh/id_ed25519_hetzner")
  # You can add additional SSH public Keys to grant other team members root access to your cluster nodes.
  # ssh_additional_public_keys = []

  # You can also add additional SSH public Keys which are saved in the hetzner cloud by a label.
  # See https://docs.hetzner.cloud/#label-selector
  # ssh_hcloud_key_label = "role=admin"

  # If you use SSH agent and have issues with SSH connecting to your nodes, you can increase the number of auth tries (default is 2)
  # ssh_max_auth_tries = 10

  # If you want to use an ssh key that is already registered within hetzner cloud, you can pass its id.
  # If no id is passed, a new ssh key will be registered within hetzner cloud.
  # It is important that exactly this key is passed via `ssh_public_key` & `ssh_private_key` variables.
  # hcloud_ssh_key_id = "xxxxx"

  # These can be customized, or left with the default values
  # * For Hetzner locations see https://docs.hetzner.com/general/others/data-centers-and-connection/
  network_region = "eu-central" # change to `us-east` if location is ash

  # If you must change the network CIDR you can do so below, but it is highly advised against.
  # network_ipv4_cidr = "<IP_ADDRESS>/8"

  # If you must change the cluster CIDR you can do so below, but it is highly advised against.
  # Cluster CIDR must be a part of the network CIDR!
  # cluster_ipv4_cidr = "<IP_ADDRESS>/16"

  # For the control planes, at least three nodes are the minimum for HA. Otherwise, you need to turn off the automatic upgrades (see README).
  # **It must always be an ODD number, never even!** Search the internet for "splitbrain problem with etcd" or see https://rancher.com/docs/k3s/latest/en/installation/ha-embedded/
  # For instance, one is ok (non-HA), two is not ok, and three is ok (becomes HA). It does not matter if they are in the same nodepool or not! So they can be in different locations and of various types.

  # Of course, you can choose any number of nodepools you want, with the location you want. The only constraint on the location is that you need to stay in the same network region, Europe, or the US.
  # For the server type, the minimum instance supported is cpx11 (just a few cents more than cx11); see https://www.hetzner.com/cloud.

  # IMPORTANT: Before you create your cluster, you can do anything you want with the nodepools, but you need at least one of each, control plane and agent.
  # Once the cluster is up and running, you can change nodepool count and even set it to 0 (in the case of the first control-plane nodepool, the minimum is 1).
  # You can also rename it (if the count is 0), but do not remove a nodepool from the list.

  # The only nodepools that are safe to remove from the list are at the end. That is due to how subnets and IPs get allocated (FILO).
  # You can, however, freely add other nodepools at the end of each list if you want. The maximum number of nodepools you can create combined for both lists is 255.
  # Also, before decreasing the count of any nodepools to 0, it's essential to drain and cordon the nodes in question. Otherwise, it will leave your cluster in a bad state.

  # Before initializing the cluster, you can change all parameters and add or remove any nodepools. You need at least one nodepool of each kind, control plane, and agent.
  # The nodepool names are entirely arbitrary, you can choose whatever you want, but no special characters or underscore, and they must be unique; only alphanumeric characters and dashes are allowed.

  # If you want to have a single node cluster, have one control plane nodepools with a count of 1, and one agent nodepool with a count of 0.

  # Please note that changing labels and taints after the first run will have no effect. If needed, you can do that through Kubernetes directly.

  # ⚠ When choosing ARM cax* server types, for the moment they are only available in fsn1.
  # Muli-architecture clusters are OK for most use cases, as container underlying images tend to be multi-architecture too.

  # * Example below:

  control_plane_nodepools = [
    {
      name        = "control-plane",
      server_type = "cpx11",
      location    = "nbg1",
      labels      = [
        "hetzner.silvenia.eu/server-location=nuremberg",
        "hetzner.silvenia.eu/server-type=cpx11"
      ],
      taints      = [],
      count       = 1

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    },
  ]

  agent_nodepools = [
    {
      name        = "worker",
      server_type = "cpx11",
      location    = "nbg1",
      labels      = [
        "hetzner.silvenia.eu/server-location=nuremberg",
        "hetzner.silvenia.eu/server-type=cpx11",
      ],
      taints      = [],
      count       = 1

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    },

  ]
  # Add custom control plane configuration options here.
  # E.g to enable monitoring for etcd, proxy etc:
  # control_planes_custom_config = {
  #  etcd-expose-metrics = true,
  #  kube-controller-manager-arg = "bind-address=<IP_ADDRESS>",
  #  kube-proxy-arg ="metrics-bind-address=<IP_ADDRESS>",
  #  kube-scheduler-arg = "bind-address=<IP_ADDRESS>",
  # }

  # You can enable encrypted wireguard for the CNI by setting this to "true". Default is "false".
  # FYI, Hetzner says "Traffic between cloud servers inside a Network is private and isolated, but not automatically encrypted."
  # Source: https://docs.hetzner.com/cloud/networks/faq/#is-traffic-inside-hetzner-cloud-networks-encrypted
  # It works with all CNIs that we support.
  # Just note, that if Cilium with cilium_values, the responsability of enabling of disabling Wireguard falls on you.
  enable_wireguard = false

  # * LB location and type, the latter will depend on how much load you want it to handle, see https://www.hetzner.com/cloud/load-balancer
  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"

  # Disable IPv6 for the load balancer, the default is false.
  # load_balancer_disable_ipv6 = true

  # Specifies the algorithm type of the load balancer. (default: round_robin).
  # load_balancer_algorithm_type = "least_connections"

  # Specifies the interval at which a health check is performed. Minimum is 3s (default: 15s).
  # load_balancer_health_check_interval = "5s"

  # Specifies the timeout of a single health check. Must not be greater than the health check interval. Minimum is 1s (default: 10s).
  # load_balancer_health_check_timeout = "3s"

  # Specifies the number of times a health check is retried before a target is marked as unhealthy. (default: 3)
  # load_balancer_health_check_retries = 3

  ### The following values are entirely optional (and can be removed from this if unused)

  # You can refine a base domain name to be use in this form of nodename.base_domain for setting the reserve dns inside Hetzner
  base_domain = "hetzner.silvenia.eu"

  # Cluster Autoscaler
  # Providing at least one map for the array enables the cluster autoscaler feature, default is disabled
  # By default we set a compatible version with the default initial_k3s_channel, to set another one,
  # have a look at the tag value in https://github.com/kubernetes/autoscaler/blob/master/charts/cluster-autoscaler/values.yaml
  # ⚠ Based on how the autoscaler works with this project, you can only choose either x86 instances or ARM server types for ALL autocaler nodepools.
  # Also, as mentioned above, for the time being ARM cax* instances are only available in fsn1.
  # If you are curious, it's ok to have a multi-architecture cluster, as most underlying container images are multi-architecture too.
  # * Example below:
  # autoscaler_nodepools = [
  #   {
  #     name        = "autoscaled-small"
  #     server_type = "cpx11"
  #     location    = "fsn1"
  #     min_nodes   = 0
  #     max_nodes   = 5
  #   }
  # ]

  # Add extra labels on nodes started by the Cluster Autoscaler
  # This argument is not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set
  autoscaler_labels = [
    "node.kubernetes.io/role=peak-workloads"
  ]

  # Add extra taints on nodes started by the Cluster Autoscaler
  # This argument is not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set
  autoscaler_taints = [
    "node.kubernetes.io/role=specific-workloads:NoExecute"
  ]

  # Configuration of the Cluster Autoscaler binary
  #
  # These arguments and variables are not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set.
  #
  # Image and version of Kubernetes Cluster Autoscaler for Hetzner Cloud:
  #   - cluster_autoscaler_image: Image of Kubernetes Cluster Autoscaler for Hetzner Cloud to be used.
  #   - cluster_autoscaler_version: Version of Kubernetes Cluster Autoscaler for Hetzner Cloud. Should be aligned with Kubernetes version.
  #
  # Logging related arguments are managed using separate variables:
  #   - cluster_autoscaler_log_level: Controls the verbosity of logs (--v)
  #   - cluster_autoscaler_log_to_stderr: Determines whether to log to stderr (--logtostderr)
  #   - cluster_autoscaler_stderr_threshold: Sets the threshold for logs that go to stderr (--stderrthreshold)
  #
  # Example (using the default values):
  #
  # cluster_autoscaler_image = "registry.k8s.io/autoscaling/cluster-autoscaler"
  # cluster_autoscaler_version = "v1.26.2"
  # cluster_autoscaler_log_level = 4
  # cluster_autoscaler_log_to_stderr = true
  # cluster_autoscaler_stderr_threshold = "WARNING"

  # Additional Cluster Autoscaler binary configuration
  #
  # cluster_autoscaler_extra_args can be used for additional arguments. The default is an empty array.
  #
  # Please note that following arguments are managed by terraform-hcloud-kube-hetzner or the variables above and should not be set manually:
  #   - --v=${var.cluster_autoscaler_log_level}
  #   - --logtostderr=${var.cluster_autoscaler_log_to_stderr}
  #   - --stderrthreshold=${var.cluster_autoscaler_stderr_threshold}
  #   - --cloud-provider=hetzner
  #   - --nodes ...
  #
  # See the Cluster Autoscaler FAQ for the full list of arguments: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca
  #
  # Example:
  #
  # cluster_autoscaler_extra_args = [
  #   "--ignore-daemonsets-utilization=true",
  #   "--enforce-node-group-min-size=true",
  # ]

  # Enable etcd snapshot backups to S3 storage.
  # Just provide a map with the needed settings (according to your S3 storage provider) and backups to S3 will
  # be enabled (with the default settings for etcd snapshots).
  # Cloudflare's R2 offers 10GB, 10 million reads and 1 million writes per month for free.
  # For proper context, have a look at https://docs.k3s.io/datastore/backup-restore.
  # etcd_s3_backup = {
  #   etcd-s3-endpoint        = "xxxx.r2.cloudflarestorage.com"
  #   etcd-s3-access-key      = "<access-key>"
  #   etcd-s3-secret-key      = "<secret-key>"
  #   etcd-s3-bucket          = "k3s-etcd-snapshots"
  # }

  # To enable Hetzner Storage Box support, you can enable csi-driver-smb, default is "false".
  # enable_csi_driver_smb = true

  # To use local storage on the nodes, you can enable Longhorn, default is "false".
  # See a full recap on how to configure agent nodepools for longhorn here https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/373#discussioncomment-3983159
  # Also see Longhorn best practices here https://gist.github.com/ifeulner/d311b2868f6c00e649f33a72166c2e5b
  enable_longhorn = true

  # By default, longhorn is pulled from https://charts.longhorn.io.
  # If you need a version of longhorn which assures compatibility with rancher you can set this variable to https://charts.rancher.io.
  # longhorn_repository = "https://charts.rancher.io"

  # The namespace for longhorn deployment, default is "longhorn-system".
  # longhorn_namespace = "longhorn-system"

  # The file system type for Longhorn, if enabled (ext4 is the default, otherwise you can choose xfs).
  # longhorn_fstype = "xfs"

  # how many replica volumes should longhorn create (default is 3).
  longhorn_replica_count = 2

  # When you enable Longhorn, you can go with the default settings and just modify the above two variables OR you can add a longhorn_values variable
  # with all needed helm values, see towards the end of the file in the advanced section.
  # If that file is present, the system will use it during the deploy, if not it will use the default values with the two variable above that can be customized.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.

  # Also, you can choose to use a Hetzner volume with Longhorn. By default, it will use the nodes own storage space, but if you add an attribute of
  # longhorn_volume_size (⚠ not a variable, just a possible agent nodepool attribute) with a value between 10 and 10000 GB to your agent nodepool definition, it will create and use the volume in question.
  # See the agent nodepool section for an example of how to do that.

  # To disable Hetzner CSI storage, you can set the following to "true", default is "false".
  # disable_hetzner_csi = true

  # If you want to use a specific Hetzner CCM and CSI version, set them below; otherwise, leave them as-is for the latest versions.
  # hetzner_ccm_version = ""
  # hetzner_csi_version = ""

  # If you want to specify the Kured version, set it below - otherwise it'll use the latest version available.
  # kured_version = ""

  # If you want to enable the Nginx ingress controller (https://kubernetes.github.io/ingress-nginx/) instead of Traefik, you can set this to "nginx". Default is "traefik".
  # By the default we load optimal Traefik and Nginx ingress controller config for Hetzner, however you may need to tweak it to your needs, so to do,
  # we allow you to add a traefik_values and nginx_values, see towards the end of this file in the advanced section.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
  # If you want to disable both controllers set this to "none"
  # ingress_controller = "nginx"

  # You can change the number of replicas for selected ingress controller here. The default 0 means autoselecting based on number of agent nodes (1 node = 1 replica, 2 nodes = 2 replicas, 3+ nodes = 3 replicas)
  # ingress_replica_count = 1

  # Use the klipperLB (similar to metalLB), instead of the default Hetzner one, that has an advantage of dropping the cost of the setup.
  # Automatically "true" in the case of single node cluster (as it does not make sense to use the Hetzner LB in that situation).
  # It can work with any ingress controller that you choose to deploy.
  # Please note that because the klipperLB points to all nodes, we automatically allow scheduling on the control plane when it is active.
  enable_klipper_metal_lb = "true"

  # If you want to configure additional arguments for traefik, enter them here as a list and in the form of traefik CLI arguments; see https://doc.traefik.io/traefik/reference/static-configuration/cli/
  # They are the options that go into the additionalArguments section of the Traefik helm values file.
  # Example:
  # traefik_additional_options = ["--log.level=DEBUG", "--tracing=true"]

  # By default traefik is configured to redirect http traffic to https, you can set this to "false" to disable the redirection.
  # The default is true.
  # traefik_redirect_to_https = false

  # Enable or disable Horizontal Pod Autoscaler for traefik.
  # The default is true.
  # traefik_autoscaling = false

  # Enable or disable pod disruption budget for traefik. Values are maxUnavailable: 33% and minAvailable: 1.
  # The default is true.
  # traefik_pod_disruption_budget = false

  # Enable or disable default resource requests and limits for traefik. Values requested are 100m & 50Mi and limits 300m & 150Mi.
  # The default is true.
  # traefik_resource_limits = false

  # If you want to configure additional ports for traefik, enter them here as a list of objects with name, port, and exposedPort properties.
  # Example:
  # traefik_additional_ports = [{name = "example", port = 1234, exposedPort = 1234}]

  # If you want to disable the metric server set this to "false". Default is "true".
  # enable_metrics_server = false

  # If you want to allow non-control-plane workloads to run on the control-plane nodes, set this to "true". The default is "false".
  # True by default for single node clusters, and when enable_klipper_metal_lb is true. In those cases, the value below will be ignored.
  allow_scheduling_on_control_plane = true

  # If you want to disable the automatic upgrade of k3s, you can set below to "false".
  # Ideally, keep it on, to always have the latest Kubernetes version, but lock the initial_k3s_channel to a kube major version,
  # of your choice, like v1.25 or v1.26. That way you get the best of both worlds without the breaking changes risk.
  # For production use, always use an HA setup with at least 3 control-plane nodes and 2 agents, and keep this on for maximum security.

  # The default is "true" (in HA setup i.e. at least 3 control plane nodes & 2 agents, just keep it enabled since it works flawlessly).
  # automatically_upgrade_k3s = false

  # The default is "true" (in HA setup it works wonderfully well, with automatic roll-back to the previous snapshot in case of an issue).
  # IMPORTANT! For non-HA clusters i.e. when the number of control-plane nodes is < 3, you have to turn it off.
  # automatically_upgrade_os = false

  # If you need more control over kured and the reboot behaviour, you can pass additional options to kured.
  # For example limiting reboots to certain timeframes. For all options see: https://kured.dev/docs/configuration/
  # The default options are: `--reboot-command=/usr/bin/systemctl reboot --pre-reboot-node-labels=kured=rebooting --post-reboot-node-labels=kured=done --period=5m`
  # Defaults can be overridden by using the same key.
  # kured_options = {
  #   "reboot-days": "su"
  #   "start-time": "3am"
  #   "end-time": "8am"
  #   "time-zone": "Local"
  # }

  # Allows you to specify either stable, latest, testing or supported minor versions.
  # see https://rancher.com/docs/k3s/latest/en/upgrades/basic/ and https://update.k3s.io/v1-release/channels
  # ⚠ If you are going to use Rancher addons for instance, it's always a good idea to fix the kube version to latest - 0.01,
  # ⚠ Rancher currently only supports v1.25 and earlier versions: https://github.com/rancher/rancher/issues/41113
  # The default is "v1.26".
  initial_k3s_channel = "latest"

  # The cluster name, by default "k3s"
  # cluster_name = ""

  # Whether to use the cluster name in the node name, in the form of {cluster_name}-{nodepool_name}, the default is "true".
  # use_cluster_name_in_node_name = false

  # Extra k3s registries. This is useful if you have private registries and you want to pull images without additional secrets.
  # Or if you want to proxy registries for various reasons like rate-limiting.
  # It will create the registries.yaml file, more info here https://docs.k3s.io/installation/private-registry.
  # Note that you do not need to get this right from the first time, you can update it when you want during the life of your cluster.
  # The default is blank.
  /* k3s_registries = <<-EOT
    mirrors:
      hub.my_registry.com:
        endpoint:
          - "hub.my_registry.com"
    configs:
      hub.my_registry.com:
        auth:
          username: username
          password: password
  EOT */

  # Additional environment variables for the host OS on which k3s runs. See for example https://docs.k3s.io/advanced#configuring-an-http-proxy .
  # additional_k3s_environment = {
  #   "CONTAINERD_HTTP_PROXY" : "http://your.proxy:port",
  #   "CONTAINERD_HTTPS_PROXY" : "http://your.proxy:port",
  #   "NO_PROXY" : "<IP_ADDRESS>/8,<IP_ADDRESS>/8,",
  # }

  # Additional commands to execute on the host OS before the k3s install, for example fetching and installing certs.
  # preinstall_exec = [
  #   "curl https://somewhere.over.the.rainbow/ca.crt > /root/ca.crt",
  #   "trust anchor --store /root/ca.crt",
  # ]

  # Additional flags to pass to the k3s server command (the control plane).
  # k3s_exec_server_args = "--kube-apiserver-arg enable-admission-plugins=PodTolerationRestriction,PodNodeSelector"

  # Additional flags to pass to the k3s agent command (every agents nodes, including autoscaler nodepools).
  # k3s_exec_agent_args = "--kubelet-arg kube-reserved=cpu=100m,memory=200Mi,ephemeral-storage=1Gi"

  # If you want to allow all outbound traffic you can set this to "false". Default is "true".
  # restrict_outbound_traffic = false

  # Adding extra firewall rules, like opening a port
  # More info on the format here https://registry.terraform.io/providers/hetznercloud/hcloud/latest/docs/resources/firewall
  # extra_firewall_rules = [
  #   {
  #     description = "For Postgres"
  #     direction       = "in"
  #     protocol        = "tcp"
  #     port            = "5432"
  #     source_ips      = ["<IP_ADDRESS>/0", "::/0"]
  #     destination_ips = [] # Won't be used for this rule
  #   },
  #   {
  #     description = "To Allow ArgoCD access to resources via SSH"
  #     direction       = "out"
  #     protocol        = "tcp"
  #     port            = "22"
  #     source_ips      = [] # Won't be used for this rule
  #     destination_ips = ["<IP_ADDRESS>/0", "::/0"]
  #   }
  # ]

  # If you want to configure a different CNI for k3s, use this flag
  # possible values: flannel (Default), calico, and cilium
  # As for Cilium, we allow infinite configurations via helm values, please check the CNI section of the readme over at https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/#cni.
  # Also, see the cilium_values at towards the end of this file, in the advanced section.
  cni_plugin = "cilium"

  # You can choose the version of Calico that you want. By default, the latest is used.
  # More info on available versions can be found at https://github.com/projectcalico/calico/releases
  # Please note that if you are getting 403s from Github, it's also useful to set the version manually. However there is rarely a need for that!
  # calico_version = "v3.25.0"

  # If you want to disable the k3s default network policy controller, use this flag!
  # Both Calico and Ciliun cni_plugin values override this value to true automatically, the default is "false".
  # disable_network_policy = true

  # If you want to disable the automatic use of placement group "spread". See https://docs.hetzner.com/cloud/placement-groups/overview/
  # We advise to not touch that setting, unless you have a specific purpose.
  # The default is "false", meaning it's enabled by default.
  # placement_group_disable = true

  # By default, we allow ICMP ping in to the nodes, to check for liveness for instance. If you do not want to allow that, you can. Just set this flag to true (false by default).
  block_icmp_ping_in = true

  # You can enable cert-manager (installed by Helm behind the scenes) with the following flag, the default is "true".
  # enable_cert_manager = false

  # IP Addresses to use for the DNS Servers, set to an empty list to use the ones provided by Hetzner, defaults to ["<IP_ADDRESS>", "<IP_ADDRESS>", "<IP_ADDRESS>"].
  # The number of different DNS servers is limited to 3 by Kubernetes itself.
  # dns_servers = []

  # When this is enabled, rather than the first node, all external traffic will be routed via a control-plane loadbalancer, allowing for high availability.
  # The default is false.
  # use_control_plane_lb = true
  # when this use_control_plane_lb is enabled, change the load balancer type to lb21, the default is "lb11"
  # control_plane_lb_type = lb21

  # Let's say you are not using the control plane LB solution above, and still want to have one hostname point to all your control-plane nodes.
  # You could create multiple A records of to let's say cp.cluster.my.org pointing to all of your control-plane nodes ips.
  # In which case, you need to define that hostname in the k3s TLS-SANs config to allow connection through it. It can be hostnames or IP addresses.
  # additional_tls_sans = ["cp.cluster.my.org"]

  # Oftentimes, you need to communicate to the cluster from inside the cluster itself, in which case it is important to set this value, as it will configure the hostname
  # at the load balancer level, and will save you from many slows downs when initiating communications from inside. Later on, you can point your DNS to the IP given
  # to the LB. And if you have other services pointing to it, you are also free to create CNAMES to point to it, or whatever you see fit.
  # If set, it will apply to either ingress controllers, Traefik or Ingress-Nginx.
  # lb_hostname = ""

  # You can enable Rancher (installed by Helm behind the scenes) with the following flag, the default is "false".
  # ⚠ Rancher currently only supports Kubernetes v1.25 and earlier, you will need to set initial_k3s_channel to a supported version: https://github.com/rancher/rancher/issues/41113
  # When Rancher is enabled, it automatically installs cert-manager too, and it uses rancher's own self-signed certificates.
  # See for options https://rancher.com/docs/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/#choose-your-ssl-configuration
  # The easiest thing is to leave everything as is (using the default rancher self-signed certificate) and put Cloudflare in front of it.
  # As for the number of replicas, by default it is set to the numbe of control plane nodes.
  # You can customized all of the above by adding a rancher_values variable see at the end of this file in the advanced section.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
  # IMPORTANT: Rancher's install is quite memory intensive, you will require at least 4GB if RAM, meaning cx21 server type (for your control plane).
  # ALSO, in order for Rancher to successfully deploy, you have to set the "rancher_hostname".
  # enable_rancher = true

  # If using Rancher you can set the Rancher hostname, it must be unique hostname even if you do not use it.
  # If not pointing the DNS, you can just port-forward locally via kubectl to get access to the dashboard.
  # If you already set the lb_hostname above and are using a Hetzner LB, you do not need to set this one, as it will be used by default.
  # But if you set this one explicitly, it will have preference over the lb_hostname in rancher settings.
  # rancher_hostname = "rancher.xyz.dev"

  # When Rancher is deployed, by default is uses the "latest" channel. But this can be customized.
  # The allowed values are "stable" or "latest".
  # rancher_install_channel = "stable"

  # Finally, you can specify a bootstrap-password for your rancher instance. Minimum 48 characters long!
  # If you leave empty, one will be generated for you.
  # (Can be used by another rancher2 provider to continue setup of rancher outside this module.)
  # rancher_bootstrap_password = ""

  # Separate from the above Rancher config (only use one or the other). You can import this cluster directly on an
  # an already active Rancher install. By clicking "import cluster" choosing "generic", giving it a name and pasting
  # the cluster registration url below. However, you can also ignore that and apply the url via kubectl as instructed
  # by Rancher in the wizard, and that would register your cluster too.
  # More information about the registration can be found here https://rancher.com/docs/rancher/v2.6/en/cluster-provisioning/registered-clusters/
  # rancher_registration_manifest_url = "https://rancher.xyz.dev/v3/import/xxxxxxxxxxxxxxxxxxYYYYYYYYYYYYYYYYYYYzzzzzzzzzzzzzzzzzzzzz.yaml"

  # Extra commands to be executed after the `kubectl apply -k` (useful for post-install actions, e.g. wait for CRD, apply additional manifests, etc.).
  # extra_kustomize_deployment_commands=""

  # Extra values that will be passed to the `extra-manifests/kustomization.yaml.tpl` if its present.
  # extra_kustomize_parameters={}

  # See an working example for just a manifest.yaml, a HelmChart and a HelmChartConfig examples/kustomization_user_deploy/README.md

  # It is best practice to turn this off, but for backwards compatibility it is set to "true" by default.
  # See https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/349
  # When "false". The kubeconfig file can instead be created by executing: "terraform output --raw kubeconfig > cluster_kubeconfig.yaml"
  # Always be careful to not commit this file!
  # create_kubeconfig = false

  # Don't create the kustomize backup. This can be helpful for automation.
  # create_kustomization = false

  # MicroOS snapshot IDs to be used. Per default empty, the most recent image created using createkh will be used.
  # We recommend the default, but if you want to use specific IDs you can.
  # You can fetch the ids with the hcloud cli by running the "hcloud image list --selector 'microos-snapshot=yes'" command.
  # microos_x86_snapshot_id = "1234567"
  # microos_arm_snapshot_id = "1234567"

  ### ADVANCED - Custom helm values for packages above (search _values if you want to located where those are mentioned upper in this file)
  # ⚠ Inside the _values variable below are examples, up to you to find out the best helm values possible, we do not provide support for customized helm values.
  # Please understand that the indentation is very important, inside the EOTs, as those are proper yaml helm values.
  # We advise you to use the default values, and only change them if you know what you are doing!

  # Cilium, all Cilium helm values can be found at https://github.com/cilium/cilium/blob/master/install/kubernetes/cilium/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   cilium_values = <<EOT
ipam:
  mode: kubernetes
devices: "eth1"
k8s:
  requireIPv4PodCIDR: true
kubeProxyReplacement: strict
l7Proxy: false
encryption:
  enabled: true
  type: wireguard
extraConfig:
  mtu: "1450"
  EOT */

  # Cert manager, all cert-manager helm values can be found at https://github.com/cert-manager/cert-manager/blob/master/deploy/charts/cert-manager/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   cert_manager_values = <<EOT
installCRDs: true
replicaCount: 3
webhook:
  replicaCount: 3
cainjector:
  replicaCount: 3
  EOT */

  # csi-driver-smb, all csi-driver-smb helm values can be found at https://github.com/kubernetes-csi/csi-driver-smb/blob/master/charts/latest/csi-driver-smb/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   csi_driver_smb_values = <<EOT
controller:
  name: csi-smb-controller
  replicas: 1
  runOnMaster: false
  runOnControlPlane: false
  resources:
    csiProvisioner:
      limits:
        memory: 300Mi
      requests:
        cpu: 10m
        memory: 20Mi
    livenessProbe:
      limits:
        memory: 100Mi
      requests:
        cpu: 10m
        memory: 20Mi
    smb:
      limits:
        memory: 200Mi
      requests:
        cpu: 10m
        memory: 20Mi
  EOT */

  # Longhorn, all Longhorn helm values can be found at https://github.com/longhorn/longhorn/blob/master/chart/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   longhorn_values = <<EOT
defaultSettings:
  defaultDataPath: /var/longhorn
persistence:
  defaultFsType: ext4
  defaultClassReplicaCount: 2
  defaultClass: true
  EOT */

  # Traefik, all Traefik helm values can be found at https://github.com/traefik/traefik-helm-chart/blob/master/traefik/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   traefik_values = <<EOT
deployment:
  replicas: 1
globalArguments: []
service:
  enabled: true
  type: LoadBalancer
  annotations:
    "load-balancer.hetzner.cloud/name": "k3s"
    "load-balancer.hetzner.cloud/use-private-ip": "true"
    "load-balancer.hetzner.cloud/disable-private-ingress": "true"
    "load-balancer.hetzner.cloud/location": "nbg1"
    "load-balancer.hetzner.cloud/type": "lb11"
    "load-balancer.hetzner.cloud/uses-proxyprotocol": "true"

ports:
  web:
    redirectTo: websecure

    proxyProtocol:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
    forwardedHeaders:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
  websecure:
    proxyProtocol:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
    forwardedHeaders:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
  EOT */

  # Nginx, all Nginx helm values can be found at https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml
  # You can also have a look at https://kubernetes.github.io/ingress-nginx/, to understand how it works, and all the options at your disposal.
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   nginx_values = <<EOT
controller:
  watchIngressWithoutClass: "true"
  kind: "DaemonSet"
  config:
    "use-forwarded-headers": "true"
    "compute-full-forwarded-for": "true"
    "use-proxy-protocol": "true"
  service:
    annotations:
      "load-balancer.hetzner.cloud/name": "k3s"
      "load-balancer.hetzner.cloud/use-private-ip": "true"
      "load-balancer.hetzner.cloud/disable-private-ingress": "true"
      "load-balancer.hetzner.cloud/location": "nbg1"
      "load-balancer.hetzner.cloud/type": "lb11"
      "load-balancer.hetzner.cloud/uses-proxyprotocol": "true"
  EOT */

  # Rancher, all Rancher helm values can be found at https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/chart-options/
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   rancher_values = <<EOT
ingress:
  tls:
    source: "rancher"
hostname: "rancher.example.com"
replicas: 1
bootstrapPassword: "supermario"
  EOT */

}

provider "hcloud" {
  token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
}

terraform {
  required_version = ">= 1.4.0"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.41.0"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

variable "hcloud_token" {
  sensitive = true
  default   = ""
}

Screenshots
No response
Platform
Linux

@Silvest89 You are just probably super tight on ressources.
Try setting allow_scheduling_on_control_plane to flalse, and scaling either horizontally (count) or vertically (node type) your agent nodepool.
Also make sure to upgrade to the latest and greatest, terraform init --upgrade.


TF2.0: Tensorboard The connection was reset

I have the same problem but w/ TF2.0-GPU, and I am on Chrome/Ubuntu, running it inside a docker container w/ juypter, miniconda, cuda-x, tensorrt. The error I get says: The connection was reset when trying to display it in the notebook, despite everything else working fine. (I'm not sure, but even when I goto localhost:6006 it doesn't load either).

RUN make -j4 \
        && make install \
	&& rm /opencv.zip \
        && rm /opencv_contrib.zip \
	&& rm -rf /opencv \
        && rm -rf /opencv_contrib

WORKDIR /

# dlib
RUN cd ~ && \
    mkdir -p dlib && \
    git clone -b 'v19.16' --single-branch https://github.com/davisking/dlib.git dlib/ && \
    cd  dlib/ && \
    python3 setup.py install --yes USE_AVX_INSTRUCTIONS --yes DLIB_USE_CUDA --clean

RUN mkdir /.local && chmod a+rwx /.local

WORKDIR /tf
EXPOSE 8888 6006

RUN useradd -ms /bin/bash container_user

RUN ${PYTHON} -m ipykernel.kernelspec

CMD ["bash", "-c", "source /etc/bash.bashrc && jupyter notebook --notebook-dir=/tf --ip <IP_ADDRESS> --no-browser --allow-root --NotebookApp.custom_display_url='http://localhost:8888'"]

``` #

@joehoeller,
Can you please confirm if you have used   tf.summary.trace_export in your code so that Tensorboard uses the Log Files created using that command. If you have used tf.summary.trace_export, can you please share your code so that we can investigate it further. Thanks!

@rmothukuru, here is the notebook:
`
import tensorflow as tf
import datetime, os
fashion_mnist = tf.keras.datasets.fashion_mnist
(x_train, y_train),(x_test, y_test) = fashion_mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0
def create_model():
return tf.keras.models.Sequential([
tf.keras.layers.Flatten(input_shape=(28, 28)),
tf.keras.layers.Dense(512, activation='relu'),
tf.keras.layers.Dropout(0.2),
tf.keras.layers.Dense(10, activation='softmax')
])
def train_model():
model = create_model()
model.compile(optimizer='adam',
loss='sparse_categorical_crossentropy',
metrics=['accuracy'])
logdir = os.path.join("logs", datetime.datetime.now().strftime("%Y%m%d-%H%M%S"))
tensorboard_callback = tf.keras.callbacks.TensorBoard(logdir, histogram_freq=1)
model.fit(x=x_train,
y=y_train,
epochs=5,
validation_data=(x_test, y_test),
callbacks=[tensorboard_callback])
train_model()
Start TensorBoard within the notebook
%load_ext tensorboard
%tensorboard --logdir logs
train_model()
from tensorboard import notebook
notebook.list() # View open TensorBoard instance
`

@joehoeller,
I have created a New Virtual Environment in Anaconda and installed Numpy, Pandas, Matplotlib and Tensorflow-Gpu. After that, I have executed your code and it worked fine. Please find the below screenshot.
.
Can you please try the same. If it is working with a New Virtual Environment, can you please share your Dockerfile so that we can reproduce it. Thanks!

I did share the Dockerfile, scroll up. It installs Miniconda btw.
On Thu, Oct 10, 2019 at 11:11 PM rmothukuru<EMAIL_ADDRESS>wrote:

@joehoeller https://github.com/joehoeller,
I have created a New Virtual Environment in Anaconda and installed Numpy,
Pandas, Matplotlib and Tensorflow-Gpu. After that, I have executed your
code and it worked fine. Please find the below screenshot.
[image: image]
https://user-images.githubusercontent.com/48206667/66622419-23bb9b80-ec05-11e9-83a5-c5e894d2d5b0.png
.
Can you please try the same. If it is working with a New Virtual
Environment, can you please share your Dockerfile so that we can reproduce
it. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/33161?email_source=notifications&email_token=ABHVQHFXXJ74P7MW62TSP5TQN74FHA5CNFSM4I62KHQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA6VWFY#issuecomment-540891927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHDBWIUQZFRT3JDOO73QN74FHANCNFSM4I62KHQA
.

@joehoeller,
Sorry about that. Got the Dockerfile.

Nah, your fine. Let me know what I need to change in Docker plz.
On Fri, Oct 11, 2019 at 12:31 AM rmothukuru<EMAIL_ADDRESS>wrote:

@joehoeller https://github.com/joehoeller,
Sorry about that. Got the Dockerfile.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/33161?email_source=notifications&email_token=ABHVQHBTXDTWIMW55QIHLKTQOAFUJA5CNFSM4I62KHQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA62QBI#issuecomment-540911621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHCEPXJF27Y3NT7WBLTQOAFUJANCNFSM4I62KHQA
.

Any updates?

Can you please try the suggestion given in this issue and let me know if it helps @joehoeller

There is another issue I found that I am working out. But is this doc accurate, it says I cannot use CUDA 10.x with TF2.0:
`GPU TensorFlow uses CUDA. On Windows only CUDA 9.0 is supported. On Linux CUDA 8.0, 9.0, and 9.2 are supported, and 9.2 is the default.
To install GPU TensorFlow with a non-default CUDA version such as 8.0: `
Link:
https://docs.anaconda.com/anaconda/user-guide/tasks/tensorflow/

Can you please try the suggestion given in this issue and let me know if it helps @joehoeller
I had the same with TF2.0 no GPU running in docker and the information provided on the link solved the problem for me.

Just saw this. Will do at some point today, sit tight. Sorry for the delay.
On Fri, Oct 18, 2019 at 6:17 AM garciacaravantes<EMAIL_ADDRESS>wrote:

Can you please try the suggestion given in this issue
https://stackoverflow.com/questions/48819139/tensorboard-link-wont-load-tensorflow-graphs-page-in-browser-the-connection-wa
and let me know if it helps @joehoeller https://github.com/joehoeller
I had the same with TF2.0 no GPU running in docker and the information
provided on the link solved the problem for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/33161?email_source=notifications&email_token=ABHVQHE3ZQLNFMW54EVPEKDQPGLLZA5CNFSM4I62KHQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBT5YIY#issuecomment-543677475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHFYS5K552CYPL3JMJLQPGLLZANCNFSM4I62KHQA
.

@joehoeller Were you able to solve the issue?

Closing this issue as it has been inactive for more than a week. Please add additional comments and we can open the issue again. Thanks!

Sorry I’ve been busy on project work. You must know how it is — most ppl
are on a 2 week cycle w me.
On Tue, Oct 29, 2019 at 3:44 PM gowthamkpr<EMAIL_ADDRESS>wrote:

Closed #33161 https://github.com/tensorflow/tensorflow/issues/33161.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/33161?email_source=notifications&email_token=ABHVQHCLW5H2YDFI7N53GMTQRCOBFA5CNFSM4I62KHQKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUQRG2XI#event-2753719645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHHAKTCBY63ST7BAO63QRCOBFANCNFSM4I62KHQA
.

Can you please try the suggestion given in this issue and let me know if it helps @joehoeller

I had the same with TF2.0 no GPU running in docker and the information provided on the link solved the problem for me.

I got the same problem with the host too @joehoeller. And the method provided on the link solved my problem. Thank god!

%load_ext tensorboard %tensorboard --logdir /tf/notebooks/graphs --host <IP_ADDRESS>
Solves the problem!

I will try this when I get back from vacation, thank you.
On Wed, Dec 25, 2019 at 10:51 PM ijakparov<EMAIL_ADDRESS>wrote:

%load_ext tensorboard %tensorboard --logdir /tf/notebooks/graphs --host
<IP_ADDRESS>
Solves the problem!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/33161?email_source=notifications&email_token=ABHVQHHYTN67JF5BVL7II2LQ2RA4TA5CNFSM4I62KHQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHU6VCQ#issuecomment-568978058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHGO5X7WUUXMPAUXRODQ2RA4TANCNFSM4I62KHQA
.


Routes not persistent

Hello. Some of my users are reporting that their route settings are reset to default every time they close the browser. All of them are using Firefox punk software.
IndexedDB settings for maps is empty every time they open the browser.
Does anyone know where to get it to work?

What do you mean by "Firefox punk software"?

@FangyCZ Any information about the PF version (e.g. public server)?
Client side settings are stored in IndexDB thats right. But it is never cleared/reset by PF.
If you can not find any JS error in the debug console, and general store/updating IndexDB works for at least the active session, I would check installed browser extensions, active "private mode", maybe Ad-Blocker,... first.
I haven´t seen any issues with the current PF version on latest FF on my side.

Hello,
@exodus4d Thank you for your reaction and sorry for missing details. Server is private and running 1.5.3 version.
Unfortunately I can't reproduce the problem, but more than one user was reporting it. I forced them to clear local PF data in the browser and it seems it is OK for now. (It was more than 14 days ago.)
I think we can close the ticket as the local client bug.


[Node.js SDK, FB Messenger] Redirecting requests from my server to the connector

Bot Info

SDK Platform:  Node.js
SDK Version: 3.14
Active Channels: fb
Deployment Environment: bot service

Issue Description
As a way to handle the inability of Botbuilder to work with multiple page tokens in Facebook (see #1495)
I was wondering if it's possible to redirect requests from my bot server to the connector service.
a scheme what I'm trying to do:
facebook wehbook -> my bot/Azure function -> connector -> my bot -> back to facebook
I tried to redirect the requests from Facebook to https://facebook.botframework.com/api/v1/bots/<my bot>, but I'm always getting back an empty response with code 403.

You can now register a bot to multiple Facebook pages.  If you are still having trouble please open a new issue.

@JasonSowers Any docs regarding this ability?

I was actually mistaken that it was already released, I just got back from a vacation and figured it would have been by now.  Therefore, we did not release any docs yet.  I was also thinking multiple pages to one bot, which should be released in the near future.
Let me be more thorough in my explanation as well.  You can register multiple bots to the same page. You would just need a "Bot channels registration" in Azure for each page using the Facebook credentials (page id, secret).  Then you can set your messaging endpoint to your the bot's endpoint.

@JasonSowers This means I will need to create "Bot channels registration" for each page but will be able to register them all to the same Facebook app?
If so - I see it as the Ideal situation, as it keeps the bots as separate identities (like any other channel), but I don't have to provision a new Facebook app for each page.

@amitbend When you say

This means I will need to create "Bot channels registration" for each page

Do you mean for each bot? If so, yes.  I haven't personally tested this but, there should be nothing on our end preventing you from using your Facebook credentials on multiple bot registrations.
There are 2 pieces of functionality I may be confusing myself with:

Having multiple Facebook pages registered to a single bot, this is in the works and will be released soon.
Having multiple bots registered to a single page.  This should work already by using the process I described above.

I am assuming you are looking for number 2 am I correct?

@JasonSowers
I'm trying not to mix the MS and Facebook terms here :smile:
What I actually mean is not any of those cases, but closer to "1".
The issue is that currently, we need to create a Facebook for each page (per bot).
One solution can be option "1" - Multiple Facebook pages registered for a single bot
Another solution (which I find more correct) - Allow to register 1 page per one bot but on the same Facebook App that you've previously created (The issue today is that each bot product a different webhook, and Facebook allows specifying only one per app)
The result, in that case, will be - 1 bot with 1 page, registered to a Facebook app with multiple pages.
I hope this is clear enough :thinking:

So in your scenario you are using your function to route messages from Facebook to the appropriate bot? Can you elaborate a bit more about th flow you described in your original post? Your situation is unique and I want to make sure it understand it before trying to offer a solution. Maybe if you could share minimal code of how this all works it could help us flush this out.

I was trying to route messages from my single facebook app (myserver/webhook) and redirect them to the appropriate instance of the bot (Microsoft bot/app) -> so I can work with just 1 Facebook app.
I ended up not doing it because I ran into issues with the redirection so currently I have 1 facebook app per 1 Microsoft bot which require me to approve a Facebook app every time I start a new bot.

Do you want to look deeper into the original plan or can we close this issue now?

@JasonSowers Whatever you think, I'm waiting for the release of the multi-page feature to see if will solve my problem

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Support trigger to scroll grid results back to top of list

Corresponding support needs to be added to https://github.com/softlayer/sl-ember-components/blob/develop/addon/mixins/sl-grid-key-controller.js and https://github.com/softlayer/sl-ember-components/blob/develop/addon/utils/sl-grid-key-adapter.js

Closed by https://github.com/softlayer/sl-ember-components/pull/344


boolean type is missing from the permitted data payload

(raised initially by Tilo Blenk)
It appears that Boolean types, which are permitted per Dataset-JSON schema, are not included in the list of applicable data types.
This might have been because the example data included no booleans.
boolean type needs adding to dataset.ts and json schema refreshed

Thanks, we can add it to the list of proposed changes listed at<EMAIL_ADDRESS>Since initially Dataset-JSON is a drop-in replacement for XPT, I think it should be discussed also how boolean values should be interpreted in SAS (Y/N, Yes/No, 1/0)?


Discovery service properties naming

This is a minor issue, although the discovery service naming seems inconsistent, Eureka uses it's own root 'eureka': eureka.client.serviceUrl, while consul is under spring.cloud.consul, ie.:
eureka:
  client:
    serviceUrl:
      defaultZone: http://localhost:8761/eureka

spring:
  cloud:
    consul:
      host: localhost
      port: 8500

spring-cloud-netflix has some naming so it can retain the same properties that eureka archaius uses.  The other projects are more standardized.  Not sure I want to do anything about this.


Todos: Cylinder app

[ ] add surface potential profile (use faked app res. calculation as we did in pseudo-section app)

[ ] add center location of the cylinder

[ ] fix color bar issue

as well, in the plot of the potentials, please add a line that shows the half-space potential

@sgkang , @lheagy , close the issues if you're happy!

#44


Update framework dependencies.

Coverage remained the same at 92.31% when pulling 3a5c83b2270d3fed2dbf786b8d758ac94378b788 on thet-depupdate into ce9e8f25734425f582f55ed6515026ba240fb390 on master.


[Bug]: Updating Host Details in Data Connection doesn't update host details in DSPA

Is there an existing issue for this?

[X] I have searched the existing issues

Deploy type
Directly installing the Dashboard at the latest (eg. odh-dashboard/main)
Version
RHODS 1.29.0
Current Behavior
When setting up a pipeline server in the dashboard, you are required to configure a data connection with the s3 endpoint, secret keys, and bucket.  When a DSPA object is created by the dashboard the AccessKey and SecretKey is loaded by the DSPA directly from the secret, but the dashboard hard codes the values for the bucket, host, port, and schema into the object.
As a user, since I entered this information into a data connection/secret when creating the object implies that the DSPA is consuming the secret directly and if I need to edit the connection details I should edit the data connection.  However, editing the data connection details and restart the pipeline-server pod does not do anything to the DSPA since it is hard coded into the DSPA.
The only way to edit the connection details is to delete the pipeline server and create it from scratch.
Expected Behavior
The UI should reflect the reality of what is actually happening and users should be able to edit the connection information.
There are a couple of different ways this could probably be achieved...
DSPO could potentially add support for loading the connection details from a secret/data connection. An issue related to supporting that has been opened here:
https://github.com/opendatahub-io/data-science-pipelines-operator/issues/199
If a user were to update a data connection the pipeline-server pod would still need to be restarted in order to load that connection.  This may be something the dashboard would want to consider.
Another option would be to make it more clear what is happening when you setup a pipeline server.  Instead of implying that everything is loaded from the data connection directly, the UI could allow a user to select a data connection and automatically fill in the details for the things that are getting hard coded into the DSPA.
This would also require that the DSPA should be editable from the dashboard in case a user does need to update the host details or some other piece.
Steps To Reproduce
No response
Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Anything else
No response

Hey @strangiato! I complete agree with your concern here.
We logged:

https://github.com/opendatahub-io/odh-dashboard/issues/1214

It wasn't flagged as field priority and was pushed down the priority. I just changed that.
I'm going to close your issue. Please post any comments you feel you want on that issue to help with the direction. But effectively our current path is to drop the "data connection" relationship. We spoke with the DSPO folks and they didn't have a lot of flexibility on the rebinding of the Data Connection / Object Storage connection -- this was our plan and priorities shifted and this seemed to have slipped through the cracks. I'll get UX on it and we can look to get moving on this asap.


Wallet > Ethereum token > Exchange with 1inch crashes

Can't reproduce
RC4
v3.40.2 (171)

Is this now resolved? I also couldn't reproduce but suspect it was fixed in the refactor.

Can't reproduce it too. Closing.


JSend 2.0 plans

We are considering a complete rewrite of JSend (2.0) and have the following plans in mind:

Modular structure, with the option to only include the features that one needs
Remove jQuery dependency
Support for Promises (with optionally a polyfill for browsers that doesn't offer support). Which polyfill this will be, isn't decided yet.
AMD / CommonJS support
No more high-level aliases, just one consistent function call
IE7+ support (so no more ActiveXObject crap)
Bower support

Plus, added support for JSONP, which is currently not available.


De-sugar bang ! operator - part 3 - optional {} =

This PR adds to #6599 to make {} = optional for suffixed identifiers.
A statement is valid syntax if it beings with a suffixed identifier i.e. Stdout.line!. Multi-line statements will have an increased ident for the following lines. The {} = will be applied as sugar, and when formatted this will also be removed if it is present.
This PR was tested using the following programs (header excluded).
# Parses as three defs with a return expression
main =
    a = "Foo"
    Stdout.line! a

    b = "Bar"
    Stdout.line b

# Parses as a single def with a return expression
main =
    Stdout.line! "Foo"

    Stdout.line "Bar"

Fix for suffixed without arguments enables the following
main = run |> Task.onErr \err -> Stderr.line "ERROR: $(Inspect.toStr err)"

run =
    sayHello!
    checkJq!

    Task.ok {}

sayHello = Stdout.line "Hello World"

checkJq =
    "jq --version"
    |> Cmd.new
    |> Cmd.status
    |> Task.mapErr UnableToCheckJQVersion

Closing in favour of a new approach that I am working on.
This was helpful to understand the scope of the task, but I think another direction will be more correct.


Allow confirming/prompting before broadcast

Component
Forge
Describe the feature you would like
Here at Endaoment we leverage forge script for multiple processes and on-chain interactions. Given the relevance and care of what we do, it'd be great if before broadcasting the picked-up transactions from a script, forge offered an option of adding a prompt/confirmation that requires the user to see the output (if any) of the script and confirm they want to go ahead with the broadcast.
I imagine this as a feature similar to console, whilst not being an original language construct, could be placed somewhere in code and pinpoint the spot you want the prompt/confirmation to happen.
If this proves to be too hard, a simple "confirm: y/n" after doing all the simulations would also be appreciated.
Hopefully this is useful for others likewise and props on this great project! ;)
Additional context
No response

I think this be closed as a duplicate of https://github.com/foundry-rs/foundry/issues/2399? Give that convo a read and feel free to share any thoughts there, as we came to a decision around UX in that issue


Missing 81_only_full_nus_wide_train.json and 81_only_full_nus_wide_test.json files

Thanks for your great work and the code release.
I am now using your code (extract_nus_wide.py) to extract the features of the NUS-WIDE dataset, but I did not find the 81_only_full_nus_wide_train.json and 81_only_full_nus_wide_test.json files. Could you please provide these two json files?Thank you very much.

I am also looking for the same json files. somebody please help


GPO not working on Livepremier

Hi Dorian,
I just checked with my RS2 and your AWJ module 2.4.1:
Currently, the GPO feedback for a manual GPO is working.
Also, the command "set GPO" is not available.
I don't know if thats just missing on my specific model or if it's a problem with all Livepremier devices.
Could you please check that?

Which version of LivePremier?

Always the most current!

That is not an answer, please give me the version number.

Sorry, it is 4.2.17

You can write a letter of thanks to our friends at AnalogWay. Among the hundreds of unnecessary changes between v3 and v4 is also this one: they renamed the internal path for the GPIO-interface from device/gpio to device/gpios.
I really hope the guy responsible for all that mess has been fired or will be. I really hope, but I'm afraid they rather promote him.
I'm working on an update.

@robertskiba Can you please check if the GPI and GPO actions and feedbacks are working with this version:
pkg.zip

Hi Dorian,
I just had time to check.

Turning GPO on/off or toggle doesn't work
feedbacks only show the current state when reconnecting/enabling the module. No "live-update".
compared to the 2.4.1, the option to set gpo state is correctly displayed.

Log: Connected to Aquilon RS2, S/N: , fw 4.2.17
If you want to try yourself on a live system, just contact me for teamviewer credentials.

Found another typo. Can you please check the attached version. Please check also the GPI as I can't do that with the simulator.
And another question: in the qouted log line, did you delete the S/N by hand or is it not logged? Actually there should be the serial number of the device.
pkg.zip

Hi Dorian,
so I did a full test of all 8 GPO (turning them on, off or toggle them on/off)
Now most things work

GPO 1 to 7 work, GPO8 doesn't work at all (no feedback, no commands). Maybe there's still some typo/bug?
GPI 1 feedback also works fine.

BTW I deleted the serial by hand, it's the correct serial of my device.

Little addition:
GPI 2 doesn't work either! No feedback at all!

One more addition:
I also tested the correct feedback behaviour if GPO are in Tally mode. It also works great, but due to too many possible screen combinations, I only tested it with S1. Is there any special combinations i could test? Maybe like S32?

Thank you, found also the last one.
No need to test other screen combinations as I read only the state, no matter where it comes from.
Closed in b6aa093e7b8e1daf5dca1eebe5e9404276151edd

Just a confirmation: With the current beta (3.5.0+7430), everything about the GPIOs works great now!