DecodeError with key, value example functionality

I haven't debugged this much yet and it may be a tower-abci issue, but for awareness the basic setup with pd (running the node) and pcli (running the client) using the existing example key, value functionality on main gives a DecodeError
Steps to reproduce are:

Follow the readme, installing Tendermint by compiling from v0.35.0-rc3. The node will start generating blocks as expected.
Try to send a request e.g. cargo run --bin pcli -- tx key value

I get:
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: DecodeError { description: "invalid wire type: ThirtyTwoBit (expected LengthDelimited)", stack: [("Request", "value")] }', /Users/redshiftzero/.cargo/git/checkouts/tower-abci-3fc79852fd8d3c75/f911c04/src/server.rs:165:70

Is that panic in pcli or pd?
Trying to reproduce with current main and tendermint 0.35.0-rc4 works on my machine; I can set a key with pcli tx and recover it with pcli query.

It was in pd but... it turns out this is an error I introduced in the client-state branch.... main is indeed working, apologies for the noise


Not working with Node 8.8.1 and Meteor 1.6

I've not upgraded to 1.6 yet.  I'll try to do that next week, but will accept a PR on this too.

Any updates?

I haven't gotten around to updating my system to 1.6.  When I do I'll update this repo of course.  I don't expect it to be too long before I update, but take into consideration it might be good to wait until 1.6.1 due to the magnitued of the changes.
In the mean time, feel free to submit a PR for 1.6.

Okay.

Meteor 1.6.1 is updated already. If not can you suggest a mup version that works?

For anyone else that needs a mupc version working for 1.6.1 you can use my forked version.

Will you add a PR to this repo to help?

@formspoint I can, but my solution isn't exactly 'good', since I just removed some code to make it work.

Made the pull request, you can just check my changes which were just 1 line. Or maybe you could look into it further and provide a better solution. @formspoint


Fix ExchangeBenchmark and PrefixSortAlgorithmBenchmark

terminate called after throwing an instance of 'facebook::velox::VeloxRuntimeError'
what():  Exception: VeloxRuntimeError
Error Source: RUNTIME
Error Code: INVALID_STATE
Reason: The memory manager is not set
The reason for the error is that the benchmark object is initialized before the main function is called. We need to ensure that the memory manager instance is initialized before the benchmark object.

@skadilover Would you rebase?

@skadilover Would you rebase?

done


pyproject.toml with duplicated PyPi and Conda deps still requires PyPi solving

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
I'm working with the following Pixi configuration
[project]
name = "tester"
version = "0.1.0"
requires-python = ">=3.10,<3.13"

dependencies = [
    "numpy>=1.24,<1.27",
]

# -------------------------- Pixi Config --------------------------- #
[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-64", "osx-arm64"]

[tool.pixi.environments]
default = { features = ["py312"], solve-group = "312" }
dev311 = { features = ["py311"], solve-group = "311" }

[tool.pixi.dependencies]
numpy = "*"

[tool.pixi.feature.py312]
dependencies = { python = "3.12.*" }

[tool.pixi.feature.py311]
platforms = ["linux-64"]
dependencies = { python = "3.11.*" }

This unexpectedly raises the error:
× Unable to solve pypi dependencies for the dev311 environment because no compatible python interpreter can be installed for the current
  │ platform
...
  help: Try converting your [pypi-dependencies] to conda [dependencies]

Using Pixi 0.34.0 on a MacOS ARM machine.
Issue description
I'm aware of the error message provided. It is related to https://github.com/prefix-dev/pixi/issues/1051, and I understand the reasons behind it. I do not understand why this error appeared in this example, since I attempted to avoid using any PyPi dependencies.
From my understanding, any dependencies specified in project.dependencies will normally be treated as PyPi dependencies under the default feature. But based on the docs in https://pixi.sh/latest/advanced/pyproject_toml/#dependency-section, I expected that respecifying Numpy in tool.pixi.dependencies would override the requirement. But checking pixi info, I see:
Environments
------------
       Environment: default
          Features: py312, default
       Solve group: 312
          Channels: conda-forge
  Dependency count: 2
      Dependencies: python, numpy
 PyPI Dependencies: numpy
  Target platforms: osx-arm64, linux-64, osx-64

       Environment: dev311
          Features: py311, default
       Solve group: 311
          Channels: conda-forge
  Dependency count: 2
      Dependencies: python, numpy
 PyPI Dependencies: numpy
  Target platforms: linux-64

Numpy as specified as both a PyPi and Conda dependency. If I were to comment out the dev311 environment and run pixi install, I see that Pixi attempts to solve for PyPi deps, but the resulting lockfile doesn't contain any.
Is this a bug, or is there an edge case or scenario that I'm not considering where this makes sense? If so, is there a way to explicitly ignore the project dependencies, or should I just use a pixi.toml?
Expected behavior
My expectation is that Numpy would not be considered a PyPi dependency when running pixi info, and that the original Pixi configuration would solve on my existing system on Pixi 0.34.0

Thanks for the input! This sounds like a good improvement! Since we have the mapping now we should be able to short circuit this.


Permissions for Github App seem too permissive for the current functionality

When self-hosting the Allstar app, it seems the permissions required / listed here are a little too permissive.
I'm not sure why it needs read-only access to Environments, Deployments, Pages, Projects, Discussions, Commit Statuses, Secret scanning alerts (not that we have this option) or Webhooks as an example.

Yes, on the read side, I was liberal to future-proof against any new policies that could be added.


FIX: Add endianness missing flag when reading data

Added endianess flat to data type to allow data to be read cross platforms
closes #8688

@yarikoptic @jreback I think this one is ready.

@yarikoptic ok on these platforms?

@bashtage IIRC the tests are disabled on non-small so is this actually tested?

All of the tests were re-enabled for big-endian a few releases ago.
There are only three tests that are skipped on any platform:
https://github.com/pydata/pandas/blob/master/pandas/io/tests/test_stata.py#L256
I would like to kill these in a different PR since they rely on proprietary data and so will never be re-enabled.

ok, ping on green

@jreback It is ready.

thanks!


go test github.com/travisjeffery/jocko/server deletes $TMPDIR

https://github.com/travisjeffery/jocko/blob/master/server/server_test.go#L189
https://github.com/travisjeffery/jocko/blob/master/server/server_test.go#L222

You probably want https://golang.org/pkg/io/ioutil/#TempDir instead.

Woh, thanks. Yeah I use ioutil.TempDir to create the dir that's actually used (dataDir).  At least I can tell people I've been shamed by Dave Cheney in an issue in the Go repo.


Idea

A fork of cellpond in which instead of clicking rectangles to change the color you use a proper rgba color picker

Bonus on the bottom there is a option which when you click swaps the color to the color of the air

A fork like that would be cool!
What do you mean by the bonus idea? Like, do you mean it would set your brush to the air colour? Or set the air to your brush colour? 🤔

Yeah. Exactly

I think it would be cool to have the second one as well.


transition to new docs

when do we want to finish:

[ ] remove old docs section
[ ] link to new location

@dcnb is going to add new header and better theming to cb-docs first


Trials with repeated set of hyperparameters

Hi @himkt !
I'm running other studies now, and I'm noticing that I'm getting a lot of trials with the exact same set of hyperparameters:

This is just an example, but I've noticed this behavior in other studies.
I'm attaching here all my config files and the shell script I'm using to run the studies.
allennlp-optuna-competicao (shell script).txt
optuna.json.txt
optuna_competicao_pass_through.jsonnet.txt
search_space_pass_through_2.json.txt
Thanks!

A sampler could return the same parameter over trials. As a workaround, you can skip a trial and use a past trial for the reporting value.
https://stackoverflow.com/questions/58820574/how-to-sample-parameters-without-duplicates-in-optuna
https://github.com/optuna/optuna/issues/717

@himkt don't you think this is a bug? I don't understand why the optuna team didn't handle this as a bug. It doesn't make sense to run the same trial more than one time. In my scenarios here, I'm getting quite a waste of computational efforts...for one study I got the same set of parameters 45 times out of 137, and for the other I got 33 out of 95.
How do you feel about adding the suggestion from stackoverflow to allennlp-optuna? And enabling it according to a parameter. I like the raise optuna.structs.TrialPruned('Duplicate parameter set') suggestion better, how about you?
I can help with a PR, if you agree.

Yes, I think it is not a bug. An objective function has a noise in nature, and an algorithm could sample a point near the specific point to get more information around it. However, I understand your situation that too many trials searched the same point is not desirable.
TPE places significance on exploitation under the trade-off between exploitation and exploration. And TPE behaves like a majority voting on a histogram for a categorical variable (@hideakiimamura, Optuna core team member told me). He also told me that the optimization could be improved by converting your categorical variable into a discrete variable and using TPE with multivariate=True(For example, lr could be a discrete variable of floating points on [1e-5, 5e-5] with step 1. weight_decay is a little bit difficult but it could be a variable on floating points on [0.0, 0.3] in the log domain...).

How do you feel about adding the suggestion from stackoverflow to allennlp-optuna?

I don't think it's good to introduce a duplicate parameter set logic to allennlp-optuna since this library is a thin wrapper of Optuna. If we introduce the trick, implementing it in Optuna would be better.
@hideakiimamura Please correct me if I wrote something wrong or could be modified. And do you think if we can support skipping evaluation of an objective function for a duplicated parameter set in Optuna?

Closed because it is not bug but Optuna specification.


Hardcode extensions for GIF figures

This is just until the next nireports release is made, since GIFs aren't supported yet and that's breaking the HTML report generation.
Changes proposed in this pull request

Hardcode extensions for figures that are actually GIFs as PNGs so they get skipped until nireports can support GIFs.

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

Project coverage is 28.48%. Comparing base (f268f2a) to head (36d38bc).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #880   +/-   ##
=======================================
  Coverage   28.48%   28.48%
=======================================
  Files          68       68
  Lines       10152    10152
  Branches     1146     1146
=======================================
  Hits         2892     2892
  Misses       7162     7162
  Partials       98       98

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

Will this still place the gifs in the figures directory? If so then I like this solution

The figures will still be created, but nireports won't be able to find them because it'll be looking for PNGs (which don't exist) instead. Then when the new release goes out, we can just drop the ".png" extension part and it should find the GIFs.


placeholder not visible when select2 is on a tab

We have implemeted the tabs of jquery-ui when the multiselect2 is on the visible tab placeholder is shown. When the multiselect2 is on a hidden tab the placeholder is not visible. The style of width of the search input is 0. When I click on the multiselect2 the search input gets the right width.
The this.getMaxSearchWidth() function causes the problem. because the this.selection.width() is 0.

This should be fixed in 4.0.
If it is not fixed, please add a :+1: to the ticket to bring it to our attention. Please also include an example that we can test to verify that it is not actually working.


set ingressClassName

Purpose

How does the solution address the problem

Changes made

/deploy

Failed to deploy prnet

Failed to deploy prnet

Failed to deploy prnet

/deploy

Failed to deploy prnet

Failed to deploy prnet

/deploy

Failed to deploy prnet

Failed to deploy prnet

Failed to deploy prnet

PR NET pr-2505 Successfully deployed!explorerhttps://explorer-pr-2505.prnet.taraxa.io  RPChttps://rpc-pr-2505.prnet.taraxa.io Indexerhttps://indexer-pr-2505.prnet.taraxa.io Boot NodesBoot Node <IP_ADDRESS>Boot Node <IP_ADDRESS>Boot Node 3<IP_ADDRESS> RPC NodesRPC Node <IP_ADDRESS>RPC Node 2<IP_ADDRESS>RPC Node 3<IP_ADDRESS>

prnet cleaned-up successfully


fix: import security PS module as file

We should import preview modules as script files, so let's use that for all.

/azp run CI - Arcus.Scripting


Live-Reload is not working properly. Add manual live reload via command-line/keyboard shortcut.

Description
Live-Reload is currently not picking up every filechanges. It is really annoying having to pick up the device to shake it only to press reload.
Could we add an cli-command like react-native reload and react-native reload --hot?
Ideally one could add shortcuts to ones favorite IDE to enable something like cmd-r to reload the app manually, whenever it is suitable. When changing multiple files at once, e.g. refactoring method parameters, the app will often reload prematurely on filechange and crash with the red screen. It would be nice to be able to issue a reload command from within the IDE, without having to shake the device.
Additional Information

React Native version: 0.44.0-rc.0
Platform: both
Development Operating System: MacOS

+1 to command-line/keyboard shortcut

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/live-reload-is-not-working-properly-add-manual-live-reload-via-command-linekeybo


Bug: TextClause default value in mapped_column raises ValueError: Unexpected default type

Description
When I write a statement that generates a TextClause (such as the text function) to populate the default value of a column, I get ValueError: Unexpected default type.
This seems to be a related issue: https://github.com/litestar-org/litestar/issues/1851
URL to code causing the issue
No response
MCVE
from litestar import Litestar
from litestar.contrib.sqlalchemy.plugins import SQLAlchemySerializationPlugin

from datetime import datetime
from sqlalchemy import text, MetaData
from sqlalchemy.orm import mapped_column, Mapped, DeclarativeBase
from uuid import UUID

class Base(DeclarativeBase):
    metadata = MetaData(
        schema="test"
    )

class TestItem(Base):
    __tablename__ = "testitem"

    id: Mapped[UUID] = mapped_column(primary_key=True)

    archived_at: Mapped[datetime] = mapped_column(
        # Change this line to another default to stop the error
        default=text("'infinity'::timestamp with time zone")
    )

@get("/test")
async def do_test(self) -> TestItem:
    return TestItem()

app = Litestar([do_test], plugins=[SQLAlchemySerializationPlugin()])

Steps to reproduce
1. Attempt to run `litestar run`
2. See error

Screenshots
"![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs
2024-07-11 18:28:23   File "/server/app/__init__.py", line 30, in <module>
2024-07-11 18:28:23     app = Litestar(routes, cors_config=cors_config, on_app_init=[initialize_application], plugins=[SQLAlchemySerializationPlugin()])
2024-07-11 18:28:23           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/app.py", line 484, in __init__
2024-07-11 18:28:23     self.register(route_handler)
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/app.py", line 668, in register
2024-07-11 18:28:23     route_handler.on_registration(self)
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/handlers/http_handlers/base.py", line 560, in on_registration
2024-07-11 18:28:23     super().on_registration(app)
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/handlers/base.py", line 544, in on_registration
2024-07-11 18:28:23     self.resolve_return_dto()
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/handlers/base.py", line 504, in resolve_return_dto
2024-07-11 18:28:23     return_dto.create_for_field_definition(
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/dto/base_dto.py", line 183, in create_for_field_definition
2024-07-11 18:28:23     backend_context[key] = backend_cls(  # type: ignore[literal-required]
2024-07-11 18:28:23                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/dto/_codegen_backend.py", line 73, in __init__
2024-07-11 18:28:23     super().__init__(
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/dto/_backend.py", line 108, in __init__
2024-07-11 18:28:23     self.parsed_field_definitions = self.parse_model(
2024-07-11 18:28:23                                     ^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/litestar/dto/_backend.py", line 140, in parse_model
2024-07-11 18:28:23     for field_definition in self.dto_factory.generate_field_definitions(model_type):
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/advanced_alchemy/extensions/litestar/dto.py", line 280, in generate_field_definitions
2024-07-11 18:28:23     yield from cls.handle_orm_descriptor(
2024-07-11 18:28:23                ^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/usr/local/lib/python3.11/functools.py", line 946, in _method
2024-07-11 18:28:23     return method.__get__(obj, cls)(*args, **kwargs)
2024-07-11 18:28:23            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/advanced_alchemy/extensions/litestar/dto.py", line 116, in _
2024-07-11 18:28:23     default, default_factory = _detect_defaults(elem)
2024-07-11 18:28:23                                ^^^^^^^^^^^^^^^^^^^^^^
2024-07-11 18:28:23   File "/root/.venv/lib/python3.11/site-packages/advanced_alchemy/extensions/litestar/dto.py", line 311, in _detect_defaults
2024-07-11 18:28:23     raise ValueError(msg)
2024-07-11 18:28:23 ValueError: Unexpected default type

Litestar Version
2.9.1
Platform

[X] Linux
[X] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

I think for now, there's no way to use this type of approach with a DTO.  Can you try using server_default instead for these specific use cases?

We can re-open this in the Advanced Alchemy repo if there is a way to fix this.


runtime: debug.Stack() and runtime.Callers() PCs differ on panic trigger site

What version of Go are you using (go version)?

go1.12.4 linux/amd64

Does this issue reproduce with the latest release?
Can´t tell for the time being, the only repro we have is on a web app and we still don´t have docker images with go 1.13/1.12.7 on our end
What operating system and processor architecture are you using (go env)?

Linux e5d326139ac1 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build601602077=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Quoting my original issue on https://github.com/newrelic/go-agent/issues/100:
I'm working on a custom gin recover middleware that prints the offending stacktrace whenever a panic goes uncatched. In this scenario, we noticed an application's code path in which the line number on the printed stacktrace is wrong, returning line 59 instead of line 61 (it took me a long time to realize that something was wrong with the stacktrace itself and not the reported line):
func (ls LocationsMutableService) getChildren(ctx context.Context, tree string, loc string) (LocationChildren, error) {
	url := ""
	var children LocationChildren

//line 59 - panic not possible here
	response, err := ls.Client.GET(url, &children)

//line 61 - actual place of panic (response == nil)
	if response.StatusCode == http.StatusNotFound {
		return nil, errors.New("")
	}

	if err != nil {
		return nil, err
	}

	return children, err
}

We fixed this by writing a implementation based on debug.Stack() but, surprisingly, after deploying the fix to verify it I'm observing that the internal stacktrace used by txn.NoticeError has the same inaccuracy that our original middleware implementation had:
2019/08/30 14:33:09 /go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/nr_stack.go 19 mlhandlers.GetStackTrace
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go 58 mlhandlers.RecoveryWithWriter.func1.1
/usr/local/go/src/runtime/panic.go 522 runtime.gopanic
/usr/local/go/src/runtime/panic.go 82 runtime.panicmem
/usr/local/go/src/runtime/signal_unix.go 390 runtime.sigpanic
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 59 gateways.LocationsMutableService.getChildren
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 51 gateways.LocationsMutableService.GetChildren.func1

After some research the main culprit seems to be a wrong PC being used when retrieving the stack frames, but I'm still not certain about the concrete cause. I changed the stacktrace generator code that manually generated the frames via https://github.com/newrelic/go-agent/pull/101 but I keep noticing the same issue, so I guess it boils down to a difference between how runtime.Stack and runtime.Callers manipulate the systemstack
The scenario I've been showing is on a specific branch of a web app we use at work (thus being unable to share it here), and unfortunately I've been trying to create a local repro case  to no avail

Marking as release-blocker since this sounds serious.  But it's going to be hard for us to investigate without a reproduction case.

@ianlancetaylor I edited the issue with the container go env and uname values
In the meanwhile I can add some more info I found while trying to diagnose this that may (or may not) be helpul:

systemstack is handled differently between Stacktrace and runtime.Callers. I can´t tell if this can affect the panic site pc though
Doesn´t look like an inlining or compiler issue at a glance? this occurs in a single function block (altough lower levels of the stack itself at that call site are indeed funcs passed as params to a handler)
It likely is an off by one error on the panic site pc; in this case it is being decremented when it shouldn`t. Or, it should come incremented as it is required to decrement program counters if traversed manually (as referred at https://github.com/go-stack/stack/issues/11#issuecomment-306045884)

Here are the different stacktraces built on the same recovery middleware for comparison (some package paths ommited for policy):
custom implementation (debug.Stack)

runtime error: invalid memory address or nil pointer dereference
	/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go:103 +0x37
	/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go:93 +0x3c
	/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go:48 +0x64
	/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:61 +0x1a8 -------------------- PANIC SITE
	/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:51 +0xe5
	/go/src/github.com/.../src/api/vendor/github.com/.../gorelic/gorelic.go:24 +0xd8
	/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:107 +0x98
	/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:50 +0x171
	/go/src/github.com/.../src/api/gateways/service_centers_service.go:21 +0xd5
	/go/src/github.com/.../src/api/controllers/service_center_controller.go:35 +0x62
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/server/middlewares.go:41 +0xa0
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/server/middlewares.go:26 +0x72
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go:87 +0x5a
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/server/middlewares.go:87 +0x376
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/mlmetrics.go:19 +0x62
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 +0x43
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go:361 +0x597
	/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go:326 +0x134

2019/09/05 21:07:24 GIN (runtime.Caller & runtime.FuncForPC)

2019/09/05 21:07:24 /usr/local/go/src/runtime/panic.go:82 (0x444620)
/usr/local/go/src/runtime/signal_unix.go:390 (0x44444f)
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:59 (0xad66d7) -------------------- PANIC SITE
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:51 (0xadf614)
/go/src/github.com/.../src/api/vendor/github.com/.../gorelic/gorelic.go:24 (0xad47d7)
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:107 (0xad7277)
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go:50 (0xad64d0)
/go/src/github.com/.../src/api/gateways/service_centers_service.go:21 (0xade744)
/go/src/github.com/.../src/api/controllers/service_center_controller.go:35 (0xaeb1c1)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/server/middlewares.go:41 (0xb0c61f)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/server/middlewares.go:26 (0xb0c461)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go:87 (0xb091a9)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/server/middlewares.go:87 (0xb0f595)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/mlmetrics.go:19 (0xb081d1)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go:108 (0x993972)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go:361 (0x99c1a6)
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go:326 (0x99b9e3)
/usr/local/go/src/net/http/server.go:2774 (0x6c6c47)
/usr/local/go/src/net/http/server.go:1878 (0x6c2830)
/usr/local/go/src/runtime/asm_amd64.s:1337 (0x45dce0)

2019/09/05 21:07:24 newrelic own fix (runtime.Callers & runtime.CallersFrames)

2019/09/05 21:07:24 /go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/nr_stack.go 19 mlhandlers.GetStackTrace
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go 58 mlhandlers.RecoveryWithWriter.func1.1
/usr/local/go/src/runtime/panic.go 522 runtime.gopanic
/usr/local/go/src/runtime/panic.go 82
/usr/local/go/src/runtime/signal_unix.go 390 runtime.sigpanic
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 59 gateways.LocationsMutableService.getChildren -------------------- PANIC SITE
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 51 gateways.LocationsMutableService.GetChildren.func1
/go/src/github.com/.../src/api/vendor/github.com/.../gorelic/gorelic.go 24 gorelic.WrapDatastoreSegment
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 107 gateways.LocationsMutableService.newRelicSegment
/go/src/github.com/.../src/api/gateways/locations_mutable_service.go 50 gateways.LocationsMutableService.GetChildren
/go/src/github.com/.../src/api/gateways/service_centers_service.go 21 gateways.(*ServiceCentersService).DoPanic
/go/src/github.com/.../src/api/controllers/service_center_controller.go 35 controllers.(*ServiceCenterController).DoPanic
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/server/middlewares.go 41 server.accessLog
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/server/middlewares.go 26 server.setUUID
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/recovery.go 87 mlhandlers.RecoveryWithWriter.func1
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/server/middlewares.go 87 server.newRelic.func1
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/vendor/github.com/.../gingonic/mlhandlers/mlmetrics.go 19 mlhandlers.Datadog.func1
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/context.go 108 gin.(*Context).Next
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go 361 gin.(*Engine).handleHTTPRequest
/go/src/github.com/.../src/api/vendor/github.com/gin-gonic/gin/gin.go 326 gin.(*Engine).ServeHTTP
/usr/local/go/src/net/http/server.go 2774 http.serverHandler.ServeHTTP
/usr/local/go/src/net/http/server.go 1878 http.(*conn).serve
/usr/local/go/src/runtime/asm_amd64.s 1337 runtime.goexit

@randall77 I'm with some blockers on our side regarding being able to test 1.13 at work but I'll be back with these things on 1.12

@randall77 here's the things you requested, these were on 1.12.9, with changes on extern, mprof and traceback files to print the program counters: dumps.zip
@ianlancetaylor while I was investigating this and looking into the runtime I found some more details that might be of help on diagnosing this and even coming up with a portable repro

This issue happens from go 1.12 and afterwards, including 1.13. 1.11 seems unaffected (can't say anything about prior versions)
It can be observed that PCs are being decremented on traceback.callers when it shouldn't, but only in some specific cases like the repro I have at work (and, for the time being, only on the panic site as we don't any any proof yet that suggests otherwise)
I see that some heavy work was done on tracebacks for 1.12 which involves how PCs are manipulated, this particular PR stood out since the description and changes seem directly related to this issue: https://github.com/golang/go/commit/232c9793092115870a430ef3c9ef9ae04f9e25c9#diff-5a2de8a1053d4e11fbc71407a5361e93

Ok, I think I can piece together what's happening here. The problem is that when an instruction faults, we record in the results of runtime.Callers the PC of the instruction that faulted. Then when we process the trace in runtime.CallersFrames and friends, we subtract 1. That gives us the immediately preceeding instruction. Instead, we must pre-increment by 1 for faulting instructions (as opposed to function calls, where we shouldn't).

Thanks for the quick response, in a couple days you managed to fix this after all the time I spent trying to pin it down, amazing!
I didn't have time to set up my docker image to build the revision locally, but I hope I can do so soon. Is the milestone confirmed to be 1.14 only or there's a chance of a backport to 1.13/1.12?

Interestingly on Go1.13.1 I can't reproduce @randall77's repro in the CL
please see https://play.golang.org/p/8A6HGud329v
which properly executes

but I can reproduce it on tip/master
$ go run main.go
devel +740d2c8c22 Thu Sep 26 18:47:41 2019 +0000
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: expected line 24, got line 23
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x109769e]

goroutine 1 [running]:
main.main.func1()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:36 +0x238
panic(0x10b00e0, 0x116cae0)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/runtime/panic.go:679 +0x1b2
main.f()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:24 +0xe
main.main()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:43 +0x74
exit status 2

and on Go1.12.10
$ go run main.go
go1.12.10
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: expected line 24, got line 23
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x109480e]

goroutine 1 [running]:
main.main.func1()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:36 +0x29e
panic(0x10ada00, 0x116e480)
	/Users/emmanuelodeke/go/src/go.googlesource.com/go/src/runtime/panic.go:522 +0x1b5
main.f()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:24 +0xe
main.main()
	/Users/emmanuelodeke/Desktop/openSrc/bugs/golang/34123/main.go:43 +0x67
exit status 2

So that's going to be an interesting backport but also perhaps there is something extra at play.

Thanks for the explanation @randall77 in https://go-review.googlesource.com/c/go/+/196962/2#message-1b08a694cb1ee65964a69e436361f75eb5c8fe67

@randall77 I´m still able to repro this on my local container using gotip:
go version devel +bf49905 Wed Nov 13 15:52:21 2019 +0000 linux/amd64
I can go back to get the a new set of dumps like you requested before if needed

Luis, please do so :)
On Wed, Nov 13, 2019 at 8:47 AM Luis Gabriel Gómez<EMAIL_ADDRESS>wrote:

@randall77 https://github.com/randall77 I´m still able to repro this on
my local container using gotip:
go version devel +bf49905 Wed Nov 13 15:52:21 2019 +0000 linux/amd64
I can go back to get the a new set of dumps like you requested before
https://github.com/golang/go/issues/34123#issuecomment-531039505 if
needed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/34123?email_source=notifications&email_token=ABFL3V55ZFEULCIT4NOYKPTQTQVSVA5CNFSM4IUBLLOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6YYEI#issuecomment-553487377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFL3V5JBBV5ANYXCD7TNQLQTQVSVANCNFSM4IUBLLOA
.

Yes, a new set of dumps would be helpful.

@odeke-em @randall77 nevermind, the fix works on all frontiers, thank you for the hard work
Took me a while to figure it out but the issue is on gotip: it uses the toolchain compiled from nightly but not its goroot so I had to run GOROOT=~/sdk/gotip gotip run main.go to effectively use the tip runtime. Closing


ci: bump toolchain

:tada: This PR is included in version 3.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Forecr DSB ORNX

Contracts for the machine configurations in balena-jetson-orin PR #532.

@asuykov let's use the Orin Nano icon for the Nano 8GB device-type, unless you have a Forecr icon already. The Nano 4GB and NX contracts can be dropped for now.


Fix missing space in misc.zsh

Without this fix, I am seeing the error:
parse error near then'`

Nevermind - others beat me to it :)


fixing ROS package and adding setup.py for the python package

Hi Mau,
I've added the following:

setup.py to install the package once
deleted redundancies in the ROS package
created readme file inside the ROS package for installation and run
made changes to the code to include subpackages inside SFA_3d_object_detection package

Hi @AhmedARadwan
Thanks for your great work.
Please:

Rename the SFA_3d_object_detection to sfa
In the ros/src/super_fast_object_detection/README.md, if you can, please describe in details the Subscriber and the Publisher.
If you can, please make a video demonstration on ROS node output.
Make sure that you test carefully the source code on your side.
Then make a new pull request on it.


Uncaught TypeError: window.wrap is not a function

Upstream issue: https://github.com/asciinema/asciinema-player/issues/145

Workaround:
<script>var wrap = undefined;</script>
[@asciinema](/casts/tmpoht4gen6-ascii.cast)

@mythsman Why did you closed it? I see no fix in https://github.com/mythsman/hexo-filter-asciinema/commits/master

I just thought you don't need my fix any more , since it's been too loog .
Now , let me fix it ...

I have fixed it at version 1.0.6 , so I'm gonna close this issue.


(#59) Upgrade to choco-theme 0.5.6

Description Of Changes
This updates to choco-theme 0.5.6 to ensure choco-theme is up to date with the latest release. While many changes went into the re-theming of pages on chocolatey websites, nothing notable happened on boxstarter.org.
Motivation and Context
Keeping choco-theme up to date an inline with styles.
Testing

Preview the site
Everything should look the same

Operating Systems Testing
n/a
Change Types Made

[ ] Bug fix (non-breaking change).
[x] Feature / Enhancement (non-breaking change).
[ ] Breaking change (fix or feature that could cause existing functionality to change).
[ ] Documentation changes.
[ ] PowerShell code changes.

Change Checklist

[ ] Requires a change to the documentation.
[ ] Documentation has been updated.
[ ] Tests to cover my changes, have been added.
[ ] All new and existing tests passed?
[ ] PowerShell code changes: PowerShell v2 compatibility checked?

Related Issue

ENGTASKS-3160
https://github.com/chocolatey/choco-theme/issues/336
https://github.com/chocolatey/choco-theme/pull/337
#59

I have put this in Draft because the version of choco-theme it depends on has not been published yet to npm, but rather is linked in the package.json file temporary for testing purposes.
This PR is ready to be taken for a spin, and then once choco-theme is published, that will be update here.

@st3phhays thanks for getting this fixed up!


0.0.9 is broken

When using the 0.0.9 of this image, we receive this error:
{
  "delayTime": 14006,
  "error": "{\"error_type\": \"<class 'requests.exceptions.JSONDecodeError'>\", \"error_message\": \"Extra data: line 1 column 5 (char 4)\", \"error_traceback\": \"Traceback (most recent call last):\\n  File \\\"/usr/local/lib/python3.10/dist-packages/requests/models.py\\\", line 974, in json\\n    return complexjson.loads(self.text, **kwargs)\\n  File \\\"/usr/lib/python3.10/json/__init__.py\\\", line 346, in loads\\n    return _default_decoder.decode(s)\\n  File \\\"/usr/lib/python3.10/json/decoder.py\\\", line 340, in decode\\n    raise JSONDecodeError(\\\"Extra data\\\", s, end)\\njson.decoder.JSONDecodeError: Extra data: line 1 column 5 (char 4)\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \\\"/usr/local/lib/python3.10/dist-packages/runpod/serverless/modules/rp_job.py\\\", line 134, in run_job\\n    handler_return = handler(job)\\n  File \\\"//runpod_wrapper.py\\\", line 39, in handler\\n    return response.json()\\n  File \\\"/usr/local/lib/python3.10/dist-packages/requests/models.py\\\", line 978, in json\\n    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)\\nrequests.exceptions.JSONDecodeError: Extra data: line 1 column 5 (char 4)\\n\", \"hostname\": \"r3ou2qejjpemuh-64410faa\", \"worker_id\": \"r3ou2qejjpemuh\", \"runpod_version\": \"1.6.2\"}",
  "executionTime": 155,
  "id": "sync-905e51be-fc3c-46c9-9188-c66f0aa631f0-e1",
  "status": "FAILED"
}

for providing this input:
{
  "input": {
    "method_name": "generate",
    "input": {
      "prompt": "why the sky is blue?"
    }
  }
}

Everything works fine with 0.0.8. So something from #10 is breaking the worker.

Thanks for flagging. I think it’s related to the method_name property. Can you change it to:
method_name: “api/generate”?

Hey @TimPietrusky!
Could you recheck this issue?

@pooyahrtn sorry for the late reply, I will do so tomorrow!

@TimPietrusky no worries at all 😊
We actually need to use the api/generate.
The reason is, the Ollama’s OpenAI’s api starts with v1/… instead of api/…. Previously, the server’s wrapper (the Docker image) was appending the api to all the requests.
Thanks again for checking, and sorry for not announcing this properly.

@pooyahrtn ok so this means that we only have this behavior when directly interacting with the worker, but not via the OpenAI-compatible API, right?


HA 0.108.1

After update to 0.108 and further to 0.108.1 no colors based on CustomUI is visible, all is the deafult blue/grey.
Google Chrome Version 80.0.3987.163
CustomUI: 20190518
Home Assistant 0.108.1
Examples of non-working:
homeassistant:
customize:
sensor.alice_fonster_power:
icon: mdi:flash-circle
custom_ui_state_card: state-card-custom-ui
templates:
hs_color: "if (state >3) return [55, 90];
else if (state >1) return [55, 90];
else if (state >0) return [30, 70];
else return [0, 0];"
brightness: "if (state >3) return 250;
else if (state >1) return 150;
else if (state >0) return 200;
else return 50;"
sensor.badrum_temp:
friendly_name: Badrum Temp
custom_ui_state_card: state-card-custom-ui
templates:
hs_color: "if (state >=25) return [0, 70];
else if (state >22) return [30, 70];
else if (state <18) return [240, 100];
else return [55, 90];"
brightness: "if (state >=25) return 150;
else if (state >22) return 250;
else if (state <18) return 150;
else return 250;"
From log:
Log Details (ERROR)
Logger: frontend.js.latest.202004071
Source: components/system_log/init.py:209
First occurred: 12:13:29 PM (2 occurrences)
Last logged: 12:19:27 PM
https://ha.sweden.se:8123/local/custom_ui/state-card-custom-ui-es5.html.js:2:24017 Uncaught ReferenceError: regeneratorRuntime is not defined
Clicking that error shows MANY lines within that error message.

😩 I have the same problem

Still working nicely here, Ha 108.1
Custom-ui: local set in customizer

Only the Color change dies Not work

Color changes works fine. Check your install method

How shall it be installed instead?

I have tested both the below activating options, no difference:
#customizer:
custom_ui: local
frontend:
extra_html_url:
- /local/custom_ui/state-card-custom-ui.html
extra_html_url_es5:
- /local/custom_ui/state-card-custom-ui-es5.html

I use the hosted version

As said: use customizer and set custom-ui: local. Simply read the instructions on how to do so, it is all automatic using the update.sh script.
The extra html url setup is deprecated long ago..

Are you adding "custom_ui: local" as a resource in "Configuration" -> "Loelace Dashboards"?

Got this error message now:
Log Details (ERROR)
Logger: frontend.js.latest.202004071
Source: components/system_log/init.py:209
First occurred: 11:24:25 AM (16 occurrences)
Last logged: 11:38:38 AM
http://<IP_ADDRESS>:18124/local/custom_ui/state-card-custom-ui.html.js:27:8908 Uncaught TypeError: e.push is not a function

No. You really should read the instructions and follow them.
Custom_ui is from before Lovelace, and was designed to customize States .

I have read several times...
So add this to configuration.yaml:
customizer:
custom_ui: local
Having the files in "custom_components/customizer".
That's it?

no that is no it, you have to activate custom_ui. see 4 posts up

I used this to activate (added to configuration.yaml):

I have th files in place:

I have the customizer files in place:

NOW i use the local version.
But now i have an error 😓
Protokolldetails ( ERROR )
Logger: frontend.js.latest.202004072
Source: components/system_log/init.py:209
First occurred: 13:13:39 (2 occurrences)
Last logged: 13:13:39
:0:0 Script error.

I use in my configuration.yaml
customizer:
custom_ui: local
and in my customize_glob.yaml
custom_ui_state_card: state-card-custom-ui

It shows the template code but the color is not change

and in my customize_glob.yaml
“.“:
custom_ui_state_card: state-card-custom-ui

this shouldn't be used anymore.

templates:
state:
if .....

not sure what you are doing here, but customizing the state is not advisable... it can cause very unexpected results. you should really post the full template if you want assistance, and please add it in code blocks, because it is unreadable right now.

What is with the rgb color code?
Can i use this?

Which rgb code?
You  can use any valid css color code as stipulated

Ok thank you 👍🏻

@bitdevil007
All my configuration was using hs_color as well, which stopped working in HaasV108.x (and i seem to remember me changing all my customisations to hs_color back in the Haas V80.x days as the icon_color stopped working back then)
Here are some tips i found which could help now i've got it working in V108.x
http://colorizer.org/
use this site to get the rgb values of your hs_color values.  Just bear in mind, for the lightness / brightness value set it to 50, as this value wasn't considered in Haas anyway, only the first H & S values
I found also, for some reason, my statements mostly had 'else if' or 'elif' as part of my entity templates in customize.yaml, once I removed those and made them simply "if" for each line of the tempate, it got it going
here is one entity entry from my customize.yaml file thats working in V108.x
sensor.iotawatt_channel_2_acdaikin:   icon: mdi:air-filter   templates:     icon_color: >       if (state > 1200) return 'rgb(255,85,0)';       if (state > 900) return 'rgb(255,170,0)';       if (state > 600) return 'rgb(255,255,0)';       if (state > 300) return 'rgb(0,255,255)';       if (state > 14) return 'rgb(0,0,255)';       if (state <= 14) return 'rgb(128,128,128)';       if (state === 'unavailable') return 'rgb(128,128,128)';       else return 'rgb(128,128,128)';
The other little gotcha i found was in some of my entity customization templates, i was using both icon & hs_color, and my hs_color entry was first item in my templates, which stumped me for a while.  I found after a bit of mucking around, that if i put in my templates entry the icon entry first, and icon_color second, that it started to work (all my templates are originally ordered as hs_color, then icon)
example as follows
`sensor.modbus_sb_operating_status_description:
friendly_name: SB Status
icon: mdi:solar-power
templates:
icon: >
if (state === 'NoPvVoltage') return 'mdi:weather-night';
if (state === 'Fault') return 'mdi:alert-circle';
if (state === 'Start') return 'mdi:reload';
if (state === 'Stop') return 'mdi:stop';
if (state === 'Shutdown') return 'mdi:power-settings';
if (state === 'StandaloneOp') return 'mdi:electric-switch';
if (state === 'Waitforgrid') return 'mdi:power-plug-off';
if (state === 'unknown') return 'mdi:help-circle';
else return 'mdi:solar-power'
icon_color: >
if (state === 'MaxPwrPnt') return 'rgb(0,255,0)';
if (state === 'StandaloneOp') return 'rgb(255,170,0)';
if (state === 'NoPvVoltage') return 'rgb(0,0,255)';
else return 'rgb(125,125,125)';
`
I had to roll back to 107 regardless as modbus broke in my setup, but on my dev instance, i was able to get the icon color portion of this to work with a bit of tinkering in V108.x
now i've just got to sit down and change all my customize.yaml entries to rgb from hs_color.

@bitdevil007
All my configuration was using hs_color as well, which stopped working in HaasV108.x (and i seem to remember me changing all my customisations to hs_color back in the Haas V80.x days as the icon_color stopped working back then)
Here are some tips i found which could help others now i've got it working in V108.x if they happen to use hs_color, and its stopped working for you in V108.x
Firstly, i use
http://colorizer.org/
I use this site to get the rgb values of your hs_color values. Just bear in mind, for the lightness / brightness value on the colorizer convertor, set it (lightness or brightness that is on colorizer.org) to be 50, as this value wasn't considered in Haas anyway, only the first H & S values
I found also, for some reason, my statements mostly had 'else if' or 'elif' as part of my entity templates in customize.yaml, once I removed those and made them simply "if" for each line of the tempate, it got it going
here is one entity entry from my customize.yaml file thats working in V108.x which is looking at a numeric value for icon color change
sensor.iotawatt_channel_2_acdaikin:
  icon: mdi:air-filter
  templates:
    icon_color: >
      if (state > 1200) return 'rgb(255,85,0)';
      if (state > 900) return 'rgb(255,170,0)';
      if (state > 600) return 'rgb(255,255,0)';
      if (state > 300) return 'rgb(0,255,255)';
      if (state > 14) return 'rgb(0,0,255)';
      if (state <= 14) return 'rgb(128,128,128)';
      if (state === 'unavailable') return 'rgb(128,128,128)';
      else return 'rgb(128,128,128)';

The other little gotcha i found was in some of my entity customization templates, i was using both icon & hs_color, and my hs_color entry was first item in my templates, which stumped me for a while. I found after a bit of mucking around, that if i put in my templates entry the icon entry first, and icon_color second, that it started to work (all my templates are originally ordered as hs_color, then icon)
example as follows where i'm updating the icon itself as well as its color, and in this case notice the single quotes, as the value of the status is text only, not numeric
sensor.modbus_sb_operating_status_description:
  friendly_name: SB Status
  templates:
    icon: >
      if (state === 'NoPvVoltage') return 'mdi:weather-night';
      if (state === 'Fault') return 'mdi:alert-circle';
      if (state === 'Start') return 'mdi:reload';
      if (state === 'Stop') return 'mdi:stop';
      if (state === 'Shutdown') return 'mdi:power-settings';
      if (state === 'StandaloneOp') return 'mdi:electric-switch';
      if (state === 'Waitforgrid') return 'mdi:power-plug-off';
      if (state === 'unknown') return 'mdi:help-circle';
      else return 'mdi:solar-power'
    icon_color: >
      if (state === 'MaxPwrPnt') return 'rgb(0,255,0)';
      if (state === 'StandaloneOp') return 'rgb(255,170,0)';
      if (state === 'NoPvVoltage') return 'rgb(0,0,255)';
      else return 'rgb(125,125,125)';

I had to roll back to 107 regardless as modbus broke in my setup, but on my dev instance, i was able to get the icon color portion of this to work with a bit of tinkering in V108.x
now i've just got to sit down and change all my customize.yaml entries to rgb from hs_color.

@peterhoe
Code:

Error log:
Error loading /config/configuration.yaml: while scanning a simple key in "/config/configuration.yaml", line 8, column 9 could not find expected ':' in "/config/configuration.yaml", line 9, column 9
while scanning a simple key in "/config/configuration.yaml", line 8, column 9 could not find expected ':' in "/config/configuration.yaml", line 9, column 9

@nolenjohan
be careful with formatting
notice in my example above that there are 2 additional spaces, from line 8 onwards under your line 7 "icon_color: >" entry
I'd suggest also to not do this in your configuration.yaml file, cause you could break things easily
take a read through the following link
https://www.home-assistant.io/docs/configuration/customizing-devices/
and do your customizing in a file called "customize.yaml"
make a mistake in your customize.yaml file, and it wont break your setup, if you get it wrong in there, worst case the customzing wont work, but your system will still load and function

@peterhoe
Thanks! Missed those extra spaces! :-)
Would I replace both "customize:" and "customize_glob:" with the "customize.yaml" file?
I assume no need for "customize:" entry in that file?
How about "customize_glob:", how will the distinction between those be in that file?

you should take out the line with custom_ui_state_card, this is no longer use, and was for States.

@nolenjohan
this particular place, eg: github is for the report of issues, it isnt meant for these types of questions of configuration
there is complete documentation on all of this.
customize_glob is a seperate file for global customisations (think of glob as being global), where you can use wildcards
eg
  customize_glob:
    "light.kitchen_*":
      icon: mdi:description

to customise all entities with "light.kitchen_*" at the beginning of each name
there is a reference to customize_glob found here
https://www.home-assistant.io/docs/configuration/basic/
point is, if you already had this working using hs_color values, change to rgb or any valid css color code, as mentioned by marius previously

Sorry I’m late to the party, but I got the same error.
What ended up being the solution to get rid of this error? I read the whole thread but couldn’t really find it. I re-read the activation instructions and everything is in order for local install.


How to change the dropdown text size?

Hi,
How can i change the dropdown text size as well as list text size?

Nevermind. I got it. Awesome library though. Thanks

Hi @rajdhakate, it's a pleasure to hear that you like the lib!


use official docker client in mesos tests.

fixes https://github.com/contiv/netplugin/issues/603
enable mesos integration tests

Do we need to use official docker client at other places in the code as well ?

only if it fails with the latest version of docker.

I think we should replace with official docker client everywhere in our code.

these tests require the latest client. it may not be necessary in other places.
yea, its good to move to the official client.

@rchirakk : Could you please take care of adding official docker client to all other places in the code ?
I am ok with other PR as well. for this PR : LGTM.

LGTM


Deleting Entity from Navigation Property Collection Causes Update Exception

Given the nature of the way related collections are only exposed via navigation properties, I assumed it was necessary to perform change resolution for each navigation property on write-back of a record. However, I can't delete related entities because there are no identifying relationships established with foreign keys either in the model builder or with decorators. Any attempt to call .Remove() on the navigation property produces the following exception:

A relationship from the 'Client_ClientSecrets' AssociationSet is in the 'Deleted' state. Given multiplicity constraints, a corresponding 'Client_ClientSecrets_Target' must also in the 'Deleted' state.

The code looks similar to:
private void SyncClientSecrets(Thinktecture.IdentityServer.EntityFramework.Entities.Client entity, Client model)
{
    // Insert logic here

    var removedSecrets = entity.ClientSecrets.Where(cs => true).ToArray(); // Not actual remove test logic

    foreach (var secret in removedSecrets)
    {
        entity.ClientSecrets.Remove(secret);
    }
}

If this was not the intended method for updating related entities or I simply don't know of a better way EF offers to set the the related collection of entities, please let me know and feel free to disregard the report.

Are you seeing this on 1.x? This was fixed on the dev/2.0.0 branch.

That's correct. If it's already corrected in the next release, please disregard.

np


application: init webhook

What type of PR is this?
/kind feature
What this PR does / why we need it:

The Fleet Manager currently lacks a webhook, so this PR introduces one. Currently, it shares the same certificate with the Cluster Operator. A separate certificate can be created, if necessary.

This PR also initializes a validator webhook for the Application.

part of #336
also the relization of #316 , because fleet must be consistent throughout the application when using current validator
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

add validator for application

@Xieql Please take a look at the left question

fixed

/label tide/merge-method-squash


On Windows capture and log the username of named pipe client peer

On Windows the collector (usually) runs as a Control Panel Service process and therefore inherits whatever system identity (LOCAL SERVICE).  Logging the username of the collector in the OTLP data stream is not very useful.
We should use the feature of named pipes to get the (Windows) SID of the client process upon receiving an incoming named pipe connection and map that to a username and log that.
This is PII-sensitive, so it should only be done if requested in the pii.yml.
On Linux/Mac Unix domain sockets have a similar feature and IIRC is already being used.

To get the client peer data you need the OS handle to the pipe (rather than just the GO wrapper). This wasn't available at the time, so I couldn't do it then.  But now that I've forked the relevant parts of the go-winio libraries to handle the multi-threaded problems, we can hack it a little further to get the peer data.


[WIP] doc: add proposal for fetching ceph credentials from KMS

Add proposal to support fetching Ceph credentials from KMS
Signed-off-by: Prashanth Dintyala<EMAIL_ADDRESS>
Describe what this PR does
Ceph-CSI currently relies on K8s secrets for ceph user (provisioner, node-stage, expand-secret)  credentials. Given that ceph-csi already supports managing volume encryption keys through vault and other KMS, it should be possible to extend the existing implementation to fetch Ceph user credentials as well.
This PR has a high level design proposal for this feature.
Related slack discussion with @Madhu-1  @nixpanic: https://cephcsi.slack.com/archives/CJV6G2DFT/p1662485493014329

Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any test
progress or results

@saiprashanth173 thanks for the proposal!
Looking into this, I am really confused and here is why.

Ceph-CSI relies on K8s CSI components for fetching Ceph user credentials.
K8s CSI uses the following reserved StorageClass parameters for fetching
credentials and passes them to Ceph-CSI.

csi.storage.k8s.io/controller-expand-secret-name
csi.storage.k8s.io/controller-expand-secret-namespace
csi.storage.k8s.io/provisioner-secret-name
csi.storage.k8s.io/provisioner-secret-namespace
csi.storage.k8s.io/node-stage-secret-name
csi.storage.k8s.io/node-stage-secret-namespace
>

These secrets and its management has nothing to do with the CSI driver itself. This is the mechanism co-ordinated from CO ( ex: Kube) based on the CSI spec . We ( as in Ceph CSI drivers) just consume it in the path! It is not something like "go and fetch" from "secrets" from CSI driver pov. These are provided as part of the RPC call to the driver like any other SC-> CSI driver combo.
These entries in the SC is common for all CSI drivers and nothing specific to Ceph CSI driver thus Ceph CSI driver has no role here.

>> * *StorageClass* parameters cannot be used for credentials as
> they are not passed in all CSI requests e.g DeleteVolumeRequest.

This is well intended and its not supposed to be used and it works.

Regardless, keeping the Ceph user information in KMS/Kube object is something we have to get the discussions on and we dont have to clobber it with above secrets..etc. In that light, adding more details on "use case" , "advantages compared to existing model" , "security aspects" (if any), "backward compatibliity" , "integration to rook as it comes in the workflow"  ...etc would be value added to the proposal.

@humblec  thanks for your feedback.
Sorry it took me some time to get back, I was out of the office last week.

These secrets and its management has nothing to do with the CSI driver itself. This is the mechanism co-ordinated from CO ( ex: Kube) based on the CSI spec . We ( as in Ceph CSI drivers) just consume it in the path! It is not something like "go and fetch" from "secrets" from CSI driver pov. These are provided as part of the RPC call to the driver like any other SC-> CSI driver combo.
These entries in the SC is common for all CSI drivers and nothing specific to Ceph CSI driver thus Ceph CSI driver has no role here.

I initially added the background section to give some context on how the current flow works. My intention was not to comment on the mechanism, it was just to summarize it. I removed the background section for now as it appears to add confusion and isn't solving the intended purpose.

This is well intended and its not supposed to be used and it works.

Just to clarify, I was trying to set context for why kmsID in case of credentials should be a part expand-secret, provisioner-secret or node-stage-secret instead of specifying it as a StorageClass parameter, like we do in the case of volume encryption. If you feel this isn't very clear, I can restructure this section a bit. Please let me know.

Regardless, keeping the Ceph user information in KMS/Kube object is something we have to get the discussions on and we dont have to clobber it with above secrets..etc. In that light, adding more details on "use case" , "advantages compared to existing model" , "security aspects" (if any), "backward compatibliity" , "integration to rook as it comes in the workflow" ...etc would be value added to the proposal.

I tried to add some more details to the proposal. I will try to refine the proposal further. Please let me know if you have any other suggestions on the latest version. Happy to make further changes based on your feedback :)

@Madhu-1 @humblec @nixpanic do you have any suggestion/comments on the proposal? Please let me know.

@saiprashanth173 is this still WIP design doc?

Overall looks good but as mention this is kind of overhead and have performance impact if someone chooses security over performance its good for them.
IMHO again it wont solve this issue, if the kubernetes secrets are compromised anyone can gain access to KMS(as all the KMS details are stored in kubernetes configmap and secret) and get the ceph cluster access.

+1

Overall looks good but as mention this is kind of overhead and have performance impact if someone chooses security over performance its good for them.
IMHO again it wont solve this issue, if the kubernetes secrets are compromised anyone can gain access to KMS(as all the KMS details are stored in kubernetes configmap and secret) and get the ceph cluster access.

+1

@saiprashanth173 can you please comment on this one, this helps to take this forward.

Overall looks good but as mention this is kind of overhead and have performance impact if someone chooses security over performance its good for them.
IMHO again it wont solve this issue, if the kubernetes secrets are compromised anyone can gain access to KMS(as all the KMS details are stored in kubernetes configmap and secret) and get the ceph cluster access.

+1

@saiprashanth173 can you please comment on this one, this helps to take this forward.

This is also what I wonder mostly about. The advantage of placing the Ceph credentials in a KMS is not clear to me. Kubernetes still stores credentials to access the KMS, so getting to the Ceph credentials is still possible without much additional effort?

IMHO again it wont solve this issue, if the kubernetes secrets are compromised anyone can gain access to KMS(as all the KMS details are stored in kubernetes configmap and secret) and get the ceph cluster access.

Sorry, I missed commenting on this.
I mostly agree that this solution wouldn't solve the issue completely for the KMS integrations that require storing auth tokens in K8s secrets. If we take vault service account based approach, it would make it more difficult (if not impossible) to access credentials compared to K8s secrets, for following reasons:

In K8s 1.24+, service account token secrets are not auto-generated and starting Ceph-CSI 3.7 we always attempt to create a service account token and use it with vault. These tokens are short-lived, and creating them would require additional privileges, e.g. RBAC with serviceaccounts/token|create . Related: https://github.com/ceph/ceph-csi/pull/3174 https://github.com/ceph/ceph-csi/pull/3377
Even with cases where a service account token is compromised, the impact will be restricted only to the vault path which the vault role linked to the service account has access to.

I believe storing secrets in KMS can provide additional level of security. Even with compromised access tokens, most KMS support additional security tightening measures which imposes restrictions on who can access the KMS endpoints, making it slightly more difficult to access sensitive secrets.
Additionally, I see this feature solving another issue, specifically for external Ceph setups, where the process of sharing and rotating keyrings can be made more seamless and secure.
Please let me know what you think. Happy to discuss this further.


AngularJS 2 compatibility

Hello guys,
Yesterday AngularJS 2 Final Released ! Anyone think work or started work on a extern for compatibility ?

Please ask questions at: https://groups.google.com/forum/#!forum/closure-compiler-discuss
The angular team provides externs for every angular version.


Issues while adding support for Intel RealSense T265

I'm picking up ROS to write a launch files to run live metric reconstruction (no semantic annotation yet) via the Intel RealSense T265 (tracking provided by two grayscale fisheye cameras). Running into a few issues:

I saw from previous issues that camera pose is provided via the sensor_frame argument according to the Voxblox node documentation. I recorded my current TF graph (published from the realsense-ros node)
.

Unfortunately, there is no frame  called world being published, which is the default argument for world_frame - what should I set world_frame and sensor_frame to?

Since the T265 doesn't provide depth information, I'm setting run_stereo_dense to true to obtain depth predictions via stereo_image_proc. Unfortunately, the node is throwing errors since it requires RGB stereo input, while the T265 only provides grayscale pairs. Do you know of any alternatives to this package?

Thanks!

If you have enough computing power , maybe you can get depth with t265 as a stereo camera following the rtabmap metod of the link, a depth msg will be published.
http://official-rtab-map-forum.67519.x6.nabble.com/Comparison-between-realsense-D435-vs-T265-vs-T265-D435-dual-setup-td6456.html
I ask my self if your errors with stereo_image_proc are because you didn't calibrate the camera. If you use t265 as an stereo camera, getting the depth from the L&R streamings, you must do it. Rtabmap will give you a easy way, but there is a few reliable ways .
T265 streamings are RGB, (RGB8) I think stereo_image_proc should work with the calibration.
Stereo depth from a t265 in a SBC or embebed computer will be a hard job, but probably you are using a desktop.
The ideal should be a d435 if you need a easy and performance friendly way.
Im not a expert, so please take my comment as just a way more to explore.
I guess myself what you mean with "live metric reconstruction" could you link for me a example, video, paper to it?
Ahh, world frame is basically related to a GPS frame, should be better use the map frame, which apply better for indoors map, were probably kimera is more used. Rtabmap will give you a map frame in the top of the frame tree, you can republish with the world name, with same TF 0,0,0 0,0,0


Markdown text in report comment is handling<EMAIL_ADDRESS>input wrong

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Markdown text in report comment is handling<EMAIL_ADDRESS>input wrong by adding redundant email domain to it.
Version Number: 1.4.52-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Jakub Szymczak - Software Mansion external agency
Slack conversation:
Action Performed:

Have somebody(eg. jakub.szymczak) in your "proposed mention list" and this person sould have the same email domain as you do(see video).
Send message: "mail@" concatinated with email name of that person(in this case<EMAIL_ADDRESS>
Expected Result:
Email domain shouldn't be added to this message. It's not even contained in email link body!
Actual Result:
The email domain was added to the sent message.
Workaround:
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/88395093/1c12257a-54d4-41a6-88de-63ad19cbd2c9

View all open jobs on GitHub

This but was found when I was working on https://github.com/Expensify/App/issues/38025. Might be connected with another bug I've found: https://github.com/Expensify/App/issues/38305.


Bad state: NoSuchMethodError: The getter 'length' was called on null.

I'm having this error when running aqueduct db generate command but only if an initial migration file exists. In order to make changes to my db I have to delete it and then I can generate one..
What should I check out to troubleshoot it?
Many thanks.
This is the print from console :
vinnytwice@Vinnys-iMac fixit_server % aqueduct db generate
-- Aqueduct CLI Version: 3.3.0+1
-- Aqueduct project version: 3.3.0+1
    Replaying versions: 1...
*** Uncaught error
    Bad state: NoSuchMethodError: The getter 'length' was called on null.
Receiver: null
Tried calling: length
  **** Stacktrace
  * #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51:5)
  * #1      _ClassMirror.newInstance (dart:mirrors-patch/mirrors_impl.dart:653:44)
  * #2      Executable.instanceOf (<data:application/dart>:14:813)
  * #3      SchemaBuilderExecutable.execute (<data:application/dart>:13:873)
  * #4      main (<data:application/dart>:9:35)
  * #5      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:297:32)
  * #6      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)
  ****

I tried Dart 2.8 and it worked just partially and only with dependency_overrides: Postgres: 2.2.0 set in pubspec.yamlfile . Now, aqueduct db generatecommand works with this version but I'd still get the RangeError when running aqueduct db upgrade command.. so still pretty useless..
I then tried 2.9 but it seems that this version doesn't allow CLI.. #903
So I finally tried 2.7 and both commands now work properly and without dependency_overrides: Postgres: 2.2.0.
What would be the correct Dart/Aqueduct/PostgreSQL setup to work with higher Dart versions like the latest stable 2.10 ?
Thank you vey much.

I tried Dart 2.8 and it worked just partially and only with dependency_overrides: Postgres: 2.2.0 set in pubspec.yamlfile . Now, aqueduct db generatecommand works with this version but I'd still get the RangeError when running aqueduct db upgrade command.. so still pretty useless..
I then tried 2.9 but it seems that this version doesn't allow CLI.. #903
So I finally tried 2.7 and both commands now work properly and without dependency_overrides: Postgres: 2.2.0.
What would be the correct Dart/Aqueduct/PostgreSQL setup to work with higher Dart versions like the latest stable 2.10 ?
Thank you vey much.

We need to wait for next release which should arrive soon. In Slack they mentioned about releasing it Q12021 if my memory is not wrong. Try to run it with pub run, it solved my problem temporarily.

We need to wait for next release which should arrive soon. In Slack they mentioned about releasing it Q12021 if my memory is not wrong. Try to run it with pub run, it solved my problem temporarily.

@ayazthemre that would be a version 4?
Apparently to make it work with Dart 2.8 this pubspec.yaml file setup would work.
ubspec.yaml file:

name: mysecurename description: mysecuredescription version: 0.1.0 environment: sdk: ">=2.7.0 <3.0.0" dependencies: aqueduct: ^4.0.0-b1 analyzer: '>=0.32.0 <0.41.0' runtime: ^1.0.0-5 http: ^0.12.0+4 mime: ^0.9.6+3 dev_dependencies: test: ^1.0.0 aqueduct_test: ^2.0.0-b1

Havent tested it yet dough..
What benefits does have aqueduct 4 over 3 ?

@ayazthemre that would be a version 4?
Apparently to make it work with Dart 2.8 this pubspec.yaml file setup would work.
ubspec.yaml file:

name: mysecurename description: mysecuredescription version: 0.1.0 environment: sdk: ">=2.7.0 <3.0.0" dependencies: aqueduct: ^4.0.0-b1 analyzer: '>=0.32.0 <0.41.0' runtime: ^1.0.0-5 http: ^0.12.0+4 mime: ^0.9.6+3 dev_dependencies: test: ^1.0.0 aqueduct_test: ^2.0.0-b1

Havent tested it yet dough..
What benefits does have aqueduct 4 over 3 ?

@ayazthemre that would be a version 4?
Apparently to make it work with Dart 2.8 this pubspec.yaml file setup would work.
ubspec.yaml file:

name: mysecurename description: mysecuredescription version: 0.1.0 environment: sdk: ">=2.7.0 <3.0.0" dependencies: aqueduct: ^4.0.0-b1 analyzer: '>=0.32.0 <0.41.0' runtime: ^1.0.0-5 http: ^0.12.0+4 mime: ^0.9.6+3 dev_dependencies: test: ^1.0.0 aqueduct_test: ^2.0.0-b1

Havent tested it yet dough..
What benefits does have aqueduct 4 over 3 ?

I don't know the benefits but since it will be latest stable version after breaking dart updates we should not be having any problems out of the box. Current as you can see there is -b after version number which I guess means beta. Even in v4 some people seem to have problems so do not use it for production release.

@ayazthemre that would be a version 4?
Apparently to make it work with Dart 2.8 this pubspec.yaml file setup would work.
ubspec.yaml file:

name: mysecurename description: mysecuredescription version: 0.1.0 environment: sdk: ">=2.7.0 <3.0.0" dependencies: aqueduct: ^4.0.0-b1 analyzer: '>=0.32.0 <0.41.0' runtime: ^1.0.0-5 http: ^0.12.0+4 mime: ^0.9.6+3 dev_dependencies: test: ^1.0.0 aqueduct_test: ^2.0.0-b1

Havent tested it yet dough..
What benefits does have aqueduct 4 over 3 ?

I don't know the benefits but since it will be latest stable version after breaking dart updates we should not be having any problems out of the box. Current as you can see there is -b after version number which I guess means beta. Even in v4 some people seem to have problems so do not use it for production release.

Got it. I'll stay on current setup then untill a  stable issue-free version 4 gets published.
Cheers

Got it. I'll stay on current setup then untill a  stable issue-free version 4 gets published.
Cheers


Stopped changing the Minimum Version

The script seems to work at least once then it stops updating the minimum required version for unknown reasons.
Using VS2019 & Windows 10

Hmmmm, that's strange that it would work once and then stop. A bit more info would be help me troubleshoot your issue easier.
Questions:

Are any errors reported in the Visual Studio Output window?
Is it a regular .Net Framework project, or a .Net Core project?
Are you using the NuGet package to install it?
Do you see the same problem occur if you create a brand new vanilla project?
Are you building via Visual Studio or a build server?

Thanks!

See the Build Output below. It says it changed the Minimum Required Version from <IP_ADDRESS> - <IP_ADDRESS> but it did not.
.net Framework
Nuget Package - Version 1.5.4
This is a fairly new project
Visual Studio Build

===========================================================
1>------ Build started: Project: DispatchTracker, Configuration: Debug Any CPU ------
1>C:\Users\Codestalker\Documents\Visual Studio Projects\DispatchTracker\DispatchTracker\RadMainForm.cs(47,30,47,32): warning CS0168: The variable 'ex' is declared but never used
1>  DispatchTracker -> C:\Users\Codestalker\Documents\Visual Studio Projects\DispatchTracker\DispatchTracker\bin\Debug\DispatchTracker.exe
1>EXEC : warning : [string]The term 'tf.exe' is not recognized as the name of a cmdlet, function, script file, or operable
1>  program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
1>  & : The term 'tf.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
1>  spelling of the name, or if a path was included, verify that the path is correct and try again.
1>  At C:\Users\jbs31047\Documents\Visual Studio
1>  Projects\DispatchTracker\DispatchTracker\PostBuildScripts\AutoUpdateProjectsMinimumRequiredClickOnceVersion.ps1:235
1>  char:8
1>  +             { & "$TfPath" checkout "$Path" }
1>  +                 ~~~~~~~~~
1>      + CategoryInfo          : ObjectNotFound: (tf.exe:String) [], CommandNotFoundException
1>      + FullyQualifiedErrorId : CommandNotFoundException
1>
1>  Updated Minimum Required Version of 'C:\Users\jbs31047\Documents\Visual Studio Projects\DispatchTracker\DispatchTracker\DispatchTracker.csproj' from '<IP_ADDRESS>' to '<IP_ADDRESS>'
Building DispatchTracker...
2>------ Publish started: Project: DispatchTracker, Configuration: Debug Any CPU ------
Connecting to 'ftp://SupplyChain/DispatchTracker/'...
Publishing files...
Publish success.
http://supplychain/AppPublishing/DispatchTracker/publish.htm
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========

Thanks for the info @jbs31047 . It looks like the issue may be that it can't find the tf.exe; although that may just be a red herring. I've pushed up a new v1.0.8 version of the NuGet package, as well as updated the docs on the project homepage. Can you take a look and give it another shot with the new version please.
I'm using VS 2019 and Windows 10 as well and created a new project and everything worked as expected.
If the problem persists, are you using the package.config style of NuGet in your project, or the package reference format?
Thanks!

Nothing changing according to the version at all for me for .NET 4.6.1 project

Hey @arteny , your issue is different than this one, and I haven't been able to reproduce the issue. I've updated the ReadMe docs to show how to manually install the script though (for .NET Core projects), so you can follow that if you are still having the issue.
I'm going to close this issue since I've been waiting for more info for a couple years and am still unable to reproduce this problem. If you have more information @jbs31047 , feel free to reopen this.


Error when Building the export templates from linux to android (thirdparty/vulkan/loader/loader.c: fatal error: 'loader_cmake_config.h' file not found)

Godot version:
https://github.com/Federico-Ciuffardi/godot/commit/24c94a877ee83d6a4b02a984aae4eb9b69522ad7
OS/device including version:
Linux 5.5.7-1-MANJARO
Issue description:
I tried to build the export templates using the following guide. When executing scons platform=android target=release android_arch=armv7 this error happens:
[ 45%] Compiling ==> thirdparty/vulkan/loader/loader.c
thirdparty/vulkan/loader/loader.c:81:10: fatal error: 'loader_cmake_config.h' file not found
#include "loader_cmake_config.h"
         ^~~~~~~~~~~~~~~~~~~~~~~

Steps to reproduce:

I tried to build the export templates for android using the following: https://github.com/Federico-Ciuffardi/godot/commit/24c94a877ee83d6a4b02a984aae4eb9b69522ad7
And followed the steps of this guide http://docs.godotengine.org/en/stable/development/compiling/compiling_for_android.html#building-the-export-templates

The Android platform has not been ported to support Vulkan yet, so this is expected.

Is there any way to compile despite this?

Yes, you can merge #36919 locally.

Fixed by #36919.


Height in mobile version

The height in mobile is not correct.
The textarea is over the last mensaje.

Hmm, thanks for the catch @MiguelAngelLV; I've just pushed a fix for it in the latest, would you mind rebuilding and seeing if this is still an issue for you? It looks ok on my browser phone emulators, but I don't have a phone to test with at the moment.

It works fine now.


fix: MapActorsHandlers support minimal APIs

Description
I'm using minimal APIs, I found endpoints.ServiceProvider.GetService<ActorRuntime>() always return null. I fix this.
But I found another exception #705 , thanks @jcdickinson fix it.
Now, my fix and #711 can make actor run success.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #695 #705 #711
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

@doddgu - is there a change needed here? The issue was closed without an explanation so I'm working if there is a fix needed in the SDK or not.

@doddgu - is there a change needed here? The issue was closed without an explanation so I'm working if there is a fix needed in the SDK or not.

It works on preview 7. I think this pr can close.


Update how-to-deploy-at-scale.md

Number of module is now 50 (instead of 20 or 30):
References:
https://github.com/Azure/iotedge/issues/3105
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-quotas-throttling#other-limits)

@sandervandevelde : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thank you Sander. #sign-off


updated the spellbook like you asked

i did everything i discovered plus some other stuff i tried in game. is this satisfactory?

I am going to merge this into a branch first and clean it up before merging to main.
Will auto-format the document and remove incantations which are incorrect. Bear with me.


Value is not stored in storage with TestHelper

Implementation of storing data in storage never work with running truffle test, although the same data process in initialize function works and also manually running oz code in command line with the same contract works successfully.
No error showed up.
Here is the sample code.
testToken.sol
pragma solidity ^0.5.0;
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
contract testToken is Initializable, ERC721Full {
    mapping(uint256 => mapping(bytes32 => string)) public _stringStorage;

    function initialize(string memory _tokenName) public {
        tokenName = _tokenName;
        _stringStorage[1][keccak256("test")] = "new1";
    }

    function setTest() public {
        _stringStorage[1][keccak256("test")] = "new2";
    }

    function getTest() public view returns(string memory) {
        return _stringStorage[1][keccak256("test")];
    }

　function getStaticTest() public view returns(string memory) {
        return "StaticTest";
    }

}

test.js
const { TestHelper } = require('@openzeppelin/cli');
const { Contracts, ZWeb3 } = require('@openzeppelin/upgrades');
ZWeb3.initialize(web3.currentProvider);
const testToken = Contracts.getFromLocal('testToken');

contract('ABNMarket deploy', function () {
  let proxy;

  beforeEach(async function () {
    this.project = await TestHelper();
    proxy = await this.project.createProxy(testToken, {
      initMethod: "initialize",
      initArgs: ["TEST"]
    });
  })

  it('mint', async function () {
    await proxy.methods.setTest("abntoken").call();
    let res = await proxy.methods.getTest().call();
    console.log(res); // returns "new1", I expected "new2"
  });
});

After running await proxy.methods.setTest("abntoken").call();,
the value res should be new2 but it is actually new1, regardless of some attempts.
(getStaticTest function works properly, which indicates static value is successfully returned)
Version information is as follows:
Truffle v5.0.30 (core: 5.0.30)
Solidity v0.5.0 (solc-js)
Node v11.14.0
Web3.js v^1.2.0

"@openzeppelin/cli": "^2.5.2",
"@openzeppelin/contracts-ethereum-package": "^2.2.1",
"@openzeppelin/upgrades": "^2.5.2",

Any help and comments are appreciated.

I've just found the answer by myself.
We have to use send method with a particular EOA address  instead of call method .
await proxy.methods.setTest("abntoken").send({from: YOUR_EOA});
Replacing the code above works successfully.

Hi @toshiboy86 I was reproducing your issue and spotted that you were doing a call when I saw that you had already found it.  Great that you were able to resolve.
For support questions you can ask in the Community Forum: https://forum.openzeppelin.com/


Live Unit Tests menu option is missing.

Description
When I installed VS 2017 Enterprise, after it was released earlier in March, I was able to try out the Live Unit test feature without a hitch. At some point, which I'm not certain of, I've noticed that the Live Unit Test menu option is now missing. It's not displayed in the IDE at all. I cannot find the command in the menu bar customize dialog either. It's simply vanished.
I have re-run the VS installer and can confirm that 'Live Unit Test' was ticked in the component selection.
I recall that I did install a VS 2017 product update (via Extensions and Updates) about two weeks ago. Whether the menu item went missing after this is unclear.
For reference, I mentioned about this here:(https://developercommunity.visualstudio.com/content/problem/8275/live-unit-testing-menu-option-missing.html)
Steps to reproduce
Open a unit test project in Visual Studio 2017 Enterprise.
Click the 'Test' menu.
Expected behavior
In the 'Test' menu a 'Live Unit Tests' option should appear.
Actual behavior
There is no 'Live Unit Tests' option visible in the 'Test' menu.
Environment
Microsoft Visual Studio Enterprise 2017
Version 15.0.26228.9 D15RTWSVC
Microsoft .NET Framework
Version 4.6.01038
NCrunch <IP_ADDRESS> (Though uninstalling this did not result in the Live Unit Tests menu option appearing).
Windows 10 v1511

Er, OK this is weird.
I just started VS 2017 now, and opened the unit test project I mentioned, and the  'Live Unit Tests' menu option has suddenly just appeared again in the 'Test' menu. However, when I click 'Start' I'm seeing a message
"Expected 1 export(s) with contract name 'Microsoft.CodeAnalysis.LiveUnitTesting.Orchestrator' but found 0 after applying application constraints"
I'm going to Goole that error now, to see what it could be. But it's was really weird that the live unit tests menu option finally turned up after another VS restart. It would be better if it was enabled all the time, less confusing. Ah well.

As a test, I just closed VS 2017 and re-opened the unit test project again. The 'Live Unit Test' menu option has vanished again. I give up. This is doing my head in.

@ManishJayaswal

This is likely because the MEF cache is dirty. Can you please run Developer Command Prompt for VS 2017 as administrator and run the following command - "devenv /clearcache /setup"


⚠ Bofrost.de has degraded performance

In aa07482, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1448 ms

Resolved: Bofrost.de performance has improved in 7bdbffe after 36 minutes.


set license_preset based on product

LGTM, but, why do you using if else instead of {coco: , oz: }[config.product] like our other solutions 😂

Haha, Adam has made all changes in this format using that util in merge PR so just keeping it similar!! No preference as such!!


Grey span on settings

Closing this PR, because grey span on settings is added on another one.
Solved!


production es upgrade from 1.30 to 1.31 doesnt work

Describe the bug
After upgrading a simple production instance with elasticsearch, es doesnt come up again.
To Reproduce
Steps to reproduce the behavior:
kubectl create namespace observability
kubectl apply -f https://github.com/jaegertracing/jaeger-operator/releases/download/v1.30.0/jaeger-operator.yaml -n observability
kubectl apply -n testing -f examples/openshift/simple-prod-deploy-es.yaml
kubectl apply -f https://github.com/jaegertracing/jaeger-operator/releases/download/v1.31.0/jaeger-operator.yaml -n observability

Expected behavior
ES boots up.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):

OS: Linux
Jaeger version: 1.30 to 1.31 or higher
Deployment: OpenShift 4.10

Additional context
Log line from Jaeger-Query not finding the es instance.
{"level":"fatal","ts":1654780962.9546692,"caller":"./main.go:101","msg":"Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout: Head \"https://elasticsearch:9200\": dial tcp: lookup elasticsearch on <IP_ADDRESS>:53: no such host: no Elasticsearch node available","stacktrace":"main.main.func1\n\t./main.go:101\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.3.0/command.go:856\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.3.0/command.go:974\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.3.0/command.go:902\nmain.main\n\t./main.go:161\nruntime.main\n\truntime/proc.go:255"}

Operator logs:
time="2022-06-09T13:38:02Z" level=warning msg="failed to upgrade managed instance" error="failed to delete Elasticsearch, deletion is needed for certificate migration to Elasticsearch operator: elasticsearches.logging.openshift.io \"elasticsearch\" not found" instance=simple-prod namespace=testing to=1.31.0
time="2022-06-09T13:38:02Z" level=error msg="failed to apply the changes" error="failed to delete Elasticsearch, deletion is needed for certificate migration to Elasticsearch operator: elasticsearches.logging.openshift.io \"elasticsearch\" not found" execution="2022-06-09 13:38:02.622392807 +0000 UTC" instance=simple-prod namespace=testing
2022-06-09T13:38:02.647Z	ERROR	controller-runtime.manager.controller.jaeger	Reconciler error	{"reconciler group": "jaegertracing.io", "reconciler kind": "Jaeger", "name": "simple-prod", "namespace": "testing", "error": "failed to delete Elasticsearch, deletion is needed for certificate migration to Elasticsearch operator: elasticsearches.logging.openshift.io \"elasticsearch\" not found"}

cc @iblancasa @rubenvp8510

ok seems to be fixed in here: https://github.com/jaegertracing/jaeger-operator/pull/1913

i tried to upgrade to the latest commit https://github.com/jaegertracing/jaeger-operator/commit/7303b94ae3a3162039817df27810e391c3d057f1. And saw this in the log messages.
time="2022-06-09T14:10:28Z" level=error msg="failed to store the upgraded instance" error="Internal error occurred: failed calling webhook \"mjaeger.kb.io\": failed to call webhook: Post \"https://jaeger-operator-webhook-service.observability.svc:443/mutate-jaegertracing-io-v1-jaeger?timeout=10s\": dial tcp <IP_ADDRESS>:9443: connect: connection refused" instance=simple-prod namespace=bb-testing

I will close this for now and reopen when iam wrong.


Send Page Layout: It is hard for the user to realize that you have a contacts book!

On the send page you should have 2 buttons and one input field only!
I did not realize that you have any contacts book function until recently when you added the new choose screen after scanning a QR code, because that information was always hidden on the bottom and I simply did not had any reason to swipe down.

On the top the input field for the address to paste it

In the middle you should have a contacts book button

Below that you should have a button to send from one internal wallet to the other

All the buttons should have the same background and color!
All buttons should have one icon and text, not only text like the specific amount button!
The Icon should always be on the left side of the text!

Thanks for reporting your concerns. We'll take them into account in a future redesign.


Devise default commands registration mechanism

This issue covers decision how we wanted to handle default commands (like help or version command). Crucial decisions are:

Should we allow user to write own implementations of those commands
Registration of the commands - via Map<T,Z> method, via custom method (ex. MapHelpCommand() or other option?
Should we make some bundle method (ex. MapDefaultCommands) which register all the default commands with different parameters?

I would left a choice to the user. So registering both help and version or better yet info commands should be optional.
I have deleted MapHelpCommand extension method as one can simply call Map<T, Z> method to achieve the same results - I wouldn't add any additional overlay there.
For me the question is how should default registration look like?

services.AddCLI(config => {
                config.Map<MoveCommand, MoveCommandHandler>(true);
            });

or
services.AddCLI(config => {
                config.MapDefault<MoveCommand, MoveCommandHandler>();
            });

We had an interesting discussion with @matiduck and here's what I think about applying default commands.
First let's understand what default commands do we expect to support as "default"? I can imagine help (explains all available commands with their parameters) and version (lists executing assembly version). Any other ideas? Even if so, probably there won't be many of them.
I would see enabling these default behaviours by writing:
var config = new CLIConfiguration()
    .MapDefaultHelpCommand()
    .MapDefaultVersionCommand()
    .Map<MyCommand, MyCommandHandler>()
    ...

If I want to use my custom help command (which I may not want to be called with help keyword) I just write:
var config = new CLIConfiguration()
    .Map<MyHelpCommand, MyHelpCommandHandler>()
    .MapDefaultVersionCommand()
    .Map<MyCommand, MyCommandHandler>()
    ...

If I don't want any help or version commands - I just don't add MapDefault... calls.

Also I don't understand the part quoted below.

Why are we talking "default" commands and the example is based on custom user command - MoveCommand?
What is the purpose of boolean parameter in first call?
How does Map differ from MapDefault in these examples?

For me the question is how should default registration look like?
services.AddCLI(config => {
                config.Map<MoveCommand, MoveCommandHandler>(true);
            });

or
services.AddCLI(config => {
                config.MapDefault<MoveCommand, MoveCommandHandler>();
            });

@jmarlew I think any command can be set as default - even when it has required options.
So you would be perfectly fine writing:
config.MapDefault<HelpCommand, HelpCommandHandler>();

What I don't understand in the above examples is how would I be able to register (map) my own HelpHandler as default?
Assuming that .MapDefaultHelpCommand() will map existing HelpHandler.

It might not been clear but I would assume that mapping MoveCommand as default would result in calling:
> myapp.exe move --from "C:\SamplePath" --to "D:\OthePath"
to works just as fine as calling
myapp.exe --from "C:\SamplePath" --to "D:\OthePath"

OK, I thought that we are talking about default help or version commands. But it seems we are talking about single default command only. So it's clear that I should be able to register only one default command. So subsequent calls to MapDefault should cause an exception?

InvalidOperationException probably - yes.

@matiduck since it's last change needed for v2.0 - would you implement it - or should I do it?

I will continue it from now.

Resolved with #30