wis2box-container exits after 'python3 wis2box-ctl.py start'

On the demo-wis2box, the wis2box-containers exists after restarting the stack stop/start command implemented in wis2box-ctl.py
See error-log below. The issue appears to that the wis2box-api container is not ready yet for connections.
Adding to API configuration
[2022-09-02T13:21:34Z] {/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py:812} WARNING - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7d033795b0>: Failed to establish a new connection: [Errno 111] Connection refused')': /oapi/admin/resources/messages
[2022-09-02T13:21:36Z] {/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py:812} WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7d033794f0>: Failed to establish a new connection: [Errno 111] Connection refused')': /oapi/admin/resources/messages
[2022-09-02T13:21:40Z] {/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py:812} WARNING - Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7d03379070>: Failed to establish a new connection: [Errno 111] Connection refused')': /oapi/admin/resources/messages
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/usr/local/lib/python3.9/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/usr/local/lib/python3.9/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 398, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 239, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/usr/local/lib/python3.9/http/client.py", line 1285, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1331, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1280, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1040, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.9/http/client.py", line 980, in send
    self.connect()
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f7d03379220>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/requests/adapters.py", line 489, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 815, in urlopen
    return self.urlopen(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='wis2box-api', port=80): Max retries exceeded with url: /oapi/admin/resources/messages (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7d03379220>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/bin/wis2box", line 33, in <module>
    sys.exit(load_entry_point('wis2box==0.4.dev0', 'console_scripts', 'wis2box')())
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/wis2box-0.4.dev0-py3.9.egg/wis2box/api/__init__.py", line 101, in setup
    api_config.add_collection('messages', collection)
  File "/usr/local/lib/python3.9/site-packages/wis2box-0.4.dev0-py3.9.egg/wis2box/api/config/pygeoapi.py", line 65, in add_collection
    if self.has_collection(name):
  File "/usr/local/lib/python3.9/site-packages/wis2box-0.4.dev0-py3.9.egg/wis2box/api/config/pygeoapi.py", line 95, in has_collection
    r = self.http.get(f'{self.url}/{name}')
  File "/usr/local/lib/python3.9/site-packages/requests/sessions.py", line 600, in get
    return self.request("GET", url, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/requests/sessions.py", line 587, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.9/site-packages/requests/sessions.py", line 701, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/requests/adapters.py", line 565, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='wis2box-api', port=80): Max retries exceeded with url: /oapi/admin/resources/messages (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7d03379220>: Failed to establish a new connection: [Errno 111] Connection refused'))

After repeating the start-command  the wis2box-container starts successfully.

I haven't seen this error anymore, closing


feat: Enhanced scroll back button to all the pages with a progress ring.

Title of the Pull Request
Enhanced scroll back button to all the pages  with a progress ring.
Related Issue
Closes: #1149
https://github.com/user-attachments/assets/3c61270e-af20-46cf-aab3-94824364f50e
Type of change
Example how to mark a checkbox:-

[x] My code follows the code style of this project.
-->
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[x] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

Please resolve merge conflicts.


Serving on a interface that isn't specified inside the configuration file

Before, I was not really sure where to post this between Caddy, Portainer, Let's Encrypt forums, and here, but I think after my findings today, I think opening the issue here is the best course of action.
Currently I'm experiencing an issue where using this image in Docker deployed from a Portainer interface gives me some issues, and has the Caddy executable exiting even though my certificates are returned successfully. I can successfully reproduce the issue on an DigitalOcean droplet on Debian 9.5 for x86-64 by pulling the image and running it, then editing the Caddyfile as follows and restarting the container.
docker.domain.tld {
     tls<EMAIL_ADDRESS>
     proxy / localhost:port {
          transparent
          websocket
     }
}

Restarting with this configuration yields the following issue that ends up in the logfile.
urn:ietf:params:acme:error:malformed - Error creating new order :: DNS name does not have enough label
This error is pretty generic, and searching around for it yield not many result. But after many hours researching and asking around I came to the conclusion that this error is from this image ignoring some of my Caddyfile settings. When I attach a shell to the container and look for my certs, I can find that they are sent over successfully, meaning there is no issue there, so it seems that this image might have some defaults of it's own that still have some priority.
I have a big suspicion that this image is requesting a cert for either localhost or <IP_ADDRESS> or <IP_ADDRESS>, which are all invalid by ACME standards. I'm not really sure why this is, even after I set my own Caddyfile which removes the <IP_ADDRESS> entry from the top of the file. Is there any way I can prevent it from attempting to register an invalid domain name? Everytime it does this, Caddy exits instead of just staying alive and not serving requests to that IP, meaning it will never actually try serving from interfaces I actually want.

Hmmm. The image has a default Caddyfile at /etc/Caddyfile and that can easily be overridden by mounting yours in the same path or specifying the --conf flag.
How are you starting the docker container, are you using a compose file?

I'm editing the default Caddyfile at /etc/Caddyfile with my desired settings.
The Docker container is started as normal from pulling it and just running it with all the default commandline arguments the image came with (although ACME-AGREE is set to true here).

I attach a shell (standard sh in this instance), and use a TUI Text Editor like GNU Nano to edit the file with the proper correct settings. However, this has the side effect of not be "consistent" in the ways I listed in the Original Post, as it still attempts to server from <IP_ADDRESS>, despite no longer present in the Caddyfile.

The reason I'm asking is that attaching a shell after starting the container is not gonna have an effect. Caddy has already started with the Caddyfile on disk before your edits.
Except you restarted Caddy afterwards or you start Caddy inside the attached shell.

I'm not sure what you are getting at.
Are you saying that editing the config file at /etc/Caddyfile, then restarting the container so changes take effect is not the recommended way to do this? (Despite that the changes go through, it's just the fact that <IP_ADDRESS> persists regardless).

@abiosoft Yeah, it's an issue with this container. I decided to do a test by manually by obtaining the certificates and keyfile by hand, then asking Caddy to load it instead of giving it my email. The default behavior would be for this to successfully load my certs, then do nothing else, instead it loads my certs successfully AND does something else, which I'm not entirely sure of. I think it's trying to grab a certificate for <IP_ADDRESS>, but Let's Encrypt isn't keen on giving me the info on what site was attempted or what the info on the attempt was.
So yeah, it's something with the default behavior on this container. I hope this can be fixed soon!

It appears that it is an issue with Global Directives since as soon as a Scoped Directive is brought in, it no longer works and causes some odd behavior. The maintainers over at https://github.com/mholt/caddy have assured me that this isn't a "bug" but just how directives work https://github.com/mholt/caddy/issues/2314.
I'm rather skeptical of not calling it a bug, as it produces unwanted behavior, but since I've resolved the issue, I see there is no point to keep this GitHub Issue open.


Status Bar Dark Content Not Working On iOS 13 Dark Mode

React Native version: 0.60.0

Steps To Reproduce

StatusBar.setBarStyle('dark-content'); // Not Working

+1

Same here

As a workaround you could probably update the following keys in the Info.plist file, overriding the system dark mode:
<key>UIUserInterfaceStyle</key>
<string>Light</string>
<key>UIViewControllerBasedStatusBarAppearance</key>
<true/>
```

I've already added this: Dark mode disabled, but: status bar does not affect.
<key>UIUserInterfaceStyle</key>
<string>Light</string>

<key>UIViewControllerBasedStatusBarAppearance</key>
<true/>

And the problem is solved when I add it, but this time I get an error like this:

This appears to be the same issue as this https://github.com/facebook/react-native/issues/26369

I solved the problem.
Apple has added a new constant to the status bar with the latest update, so dark-content doesn't work. (in dark-mode)
https://developer.apple.com/documentation/uikit/uistatusbarstyle?language=objc
New Constant: UIStatusBarStyleDarkContent - A dark status bar, intended for use on light backgrounds.

Open XCode

Search: RCTStatusBarManager.m

Pods/Development Pods/React-Core/Modules/RCTStatusBarManager.m (xCode)

Other Editor
node_modules/react-native/React/RCTStatusBarManager.m

RCT_ENUM_CONVERTER(UIStatusBarStyle, (@{
  @"default": @(UIStatusBarStyleDefault),
  @"light-content": @(UIStatusBarStyleLightContent),
  @"dark-content": @(UIStatusBarStyleDefault),
}), UIStatusBarStyleDefault, integerValue);

To Change:
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunguarded-availability"

RCT_ENUM_CONVERTER(UIStatusBarStyle, (@{
  @"default": @(UIStatusBarStyleDefault),
  @"light-content": @(UIStatusBarStyleLightContent),
  @"dark-content": (@available(iOS 13.0, *)) ? @(UIStatusBarStyleDarkContent) : @(UIStatusBarStyleDefault),
}), UIStatusBarStyleDefault, integerValue);

#pragma clang diagnostic pop

#pragma clang diagnostic pop

Seems to work. Can we expect this to be pushed into RN anytime soon?

@mronline's solution worked perfectly on RN 0.59.9

@mronline's solution worked on RN 0.59.2 :tada:

So not just an issue with RN 0.60? Hopefully it can be fixed for 59, 60 and 61 then... Monkey patching the xcode file is awful.

I solved the problem with this commit.
https://github.com/facebook/react-native/commit/796b3a1f8823c87c9a066ea9c51244710dc0b9b5

for hot fixed react-native file can be used this package https://github.com/ds300/patch-package

@wphestiraid You made my day! thank you 😃

+1

+1

This has been fixed in RN 0.61.2 or can be patched as described above. I think this issue can be closed.

#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunguarded-availability"
RCT_ENUM_CONVERTER(UIStatusBarStyle, (@{
@"default": @(UIStatusBarStyleDefault),
@"light-content": @(UIStatusBarStyleLightContent),
@"dark-content": (@available(iOS 13.0, *)) ? @(UIStatusBarStyleDarkContent) : @(UIStatusBarStyleDefault),
}), UIStatusBarStyleDefault, integerValue);
#pragma clang diagnostic pop

Also please make sure you have this enabled in your info.plist file
	<key>UIViewControllerBasedStatusBarAppearance</key>
	<true/>

and edit the code to this, so it supports the newest 13.1.2 as well.
RCT_ENUM_CONVERTER(UIStatusBarStyle, (@{
  @"default": @(UIStatusBarStyleDefault),
  @"light-content": @(UIStatusBarStyleLightContent),
  @"dark-content": (@available(iOS 13, *)) ? @(UIStatusBarStyleDarkContent) : @(UIStatusBarStyleDefault),
}), UIStatusBarStyleDefault, integerValue);

#pragma clang diagnostic pop

Also please make sure you have this enabled in your info.plist file

It wrong no add this to info.plist otherwise you receive red box error.

@fonov I just did that and it works perfectly fine in my iOS 13 device and iOS 13.1.2 as well

Actually StatusBar.setBarStyle('dark-content'); worked for Expo SDK v33.0.0 which is based on RN 0.59.8. We had to use it as we can't do pod install in Expo
Source: expo/expo#3874

Note that now it seems that we need to explicitly set StatusBar.setBarStyle('dark-content'); (in index.js?) to restore pre-0.61.2 behaviour. Before 0.61.2 it defaulted to dark-content when nothing was set.

Successfully fixed this issue by making changes in info.plist describe https://github.com/facebook/react-native/issues/26619#issuecomment-536019357 and changes in RCTStatusBarManager.m describe https://github.com/facebook/react-native/issues/26619#issuecomment-536191518.
credits goes  to @gpawlik & @mronline

Successfully fixed this issue by making changes in info.plist describe here and changes in RCTStatusBarManager.m describe here.
credits goes to @gpawlik & @mronline

It helped me a lot.
We're skipped modifying node_modules file, cuz in React-Native 0.61 its already fixed.
And changed in Info.plist only 1 parameter:
<key>UIViewControllerBasedStatusBarAppearance</key> <string>NO</string>
Cuz its throwing exception if use

I'm running react-native 0.61.5 and am still seeing white content when I want it to be dark.
<StatusBar translucent={true} backgroundColor='transparent' barStyle='dark-content'/>

the changes @mronline suggest is very different from the lines of code in my RCTStatusBarManager.m file. My react native version is: 0.63.4, the string fixes mentioned by @gpawlik in info.plist result in the same red error OP has shown. Although the app does not crash it is still unpleasant to be told its wrong.


cmd/go: "go get: unzip: malformed file path: double dot"

go version
go version go1.11 linux/amd64

downloaded yesterday (27 august)

$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/emacs/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/emacs/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="/home/emacs/Desktop/main/go.mod"
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-build252846370=/tmp/go-build -gno-record-gcc-switches"

I am trying to use ANTLR4 runtime support via go modules, steps to reproduce:

Choose some directory
Create new Go package/module:mkdir newpack
cd newpack
go mod init main

Try to get ANTLR4 runtime support modulego get github.com/antlr/antlr4/runtime/Go/antlr

Obviously, successful download was expected, got an error message instead:go: finding github.com/antlr/antlr4/runtime/Go/antlr latest
go: finding github.com/antlr/antlr4/runtime/Go latest
go: finding github.com/antlr/antlr4/runtime latest
go: finding github.com/antlr/antlr4 latest
go: extracting github.com/antlr/antlr4 v0.0.0-20180728001836-7d0787e29ca8
-> unzip<EMAIL_ADDRESS>malformed file path "runtime/Cpp/demo/Windows/antlr4-cpp-demo/antlr4-cpp-demo-vs2015.vcxproj..filters": double dot
go get github.com/antlr/antlr4/runtime/Go/antlr: unzip<EMAIL_ADDRESS>malformed file path "runtime/Cpp/demo/Windows/antlr4-cpp-demo/antlr4-cpp-demo-vs2015.vcxproj..filters": double dot

I guess double dots in some unrelated file is hardly a reason to diagnose a error

I am also facing this issue. Since DynamoDB uses ANTLR to parse expression grammar, this effectively means we cannot use the aws-sdk in Golang with go modules until there is a fix.

Is there a workaround for this issue? Hitting it trying to depend on https://github.com/SpectoLabs/hoverfly
go: extracting github.com/SpectoLabs/hoverfly v0.17.7
-> unzip<EMAIL_ADDRESS>malformed file path "core/handlers/v2/hoverfly_upstream_proxy_handler..go": double dot

@DanielJonesEB good workaround is to create an issue in the project

good workaround is to create an issue in the project

Sadly I'm depending on an old version of the library, so we can't go back in time to fix it.

Found this same problem in the latest version of the Telegraf repo.  The use of double dots appears to be perfectly legitimate since they are testing that the config loader doesn't descend into directories that start with double dots.  I guess the test could be changed to dynamically create the double dot directory to avoid it being committed to the repo, but would be nice not to have to.

go get -u golang.org/x/tools/... found the same issue.

Used the workaround provided here: https://github.com/golang/go/issues/26672#issuecomment-409685692 to bypass the error, basically add a go.mod file in my test file tree so it is considered as a separate module and it doesn't get zipped with the main one.

i compiled the latest master source and still get this error, am i missing something?
go version devel +3322f3e0ce Wed Oct 9 23:03:55 2019 +0000 darwin/amd64

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/imac/Library/Caches/go-build"
GOENV="/Users/imac/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/imac/Projects/go/bin"
GOPRIVATE=""
GOPROXY="https://goproxy.cn"
GOROOT="/Users/imac/Projects/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/imac/Projects/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/imac/Projects/go/src/go.mod"
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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xb/5ys3kh657kdd45gb9kmlqjq80000gn/T/go-build166768544=/tmp/go-build -gno-record-gcc-switches -fno-common"

alright! vscode use the absolute path /usr/local/bin/go which is still a soft link of  /usr/local/Cellar/go/1.12.7/bin/go, relink to /Users/imac/Projects/go/bin/go will get fix


add versions for v3 migration

Docs Build status updates of commit b6ba959:
:clock10: Full build: the average full build time is 5 min(s) 29 sec(s), this is based on the last 3 build(s) for this repository.
:warning: This is a FULL build due to the 'master' branch being a new branch in Docs Build service and is still building, or there are build errors in 'master' branch so the cache for incremental build is not available. Normally no action is required on your part, but if the full build persists, please contact your repository admin to manually perform a full build on the 'master' branch. For more detailed info, please click here.


rememberSaveable doesn't work since 1.0.0-beta08

To reproduce this issue, just enable "Dont't keep activites" and use this test screen.
class TestScreen : Screen {
    @Composable
    override fun Content() {
        var text by rememberSaveable {
            mutableStateOf("")
        }

        Column {
            TextField(value = text, onValueChange = { text = it })
        }
    }
}

rememberSaveable must work because some components used it under the hood to restore scroll position and other things.

As I can see the value is in rememberSaveable but something wrong in default key calculation when we use it in Screen.Content. If I set key manually, this works fine, but it's still a problem.

Sorry for taking too long. Just tried to reproduce with your TestScreen and "Don't keep activities" enabled, seems the bug was solved in past releases.
Feel free to reopen the issue if still happens with you.

Back to voyager 1.0 RC6 and I'm facing this too.
I'm logging the key in an AndroidScreen and it's properly restored after activity kill.
But rememberSaveable by default does not work, passing a key does work and the value is properly restored.
So
    var curPage by rememberSaveable(key = "Test") {
        mutableStateOf(0)
    }

Will properly restore any changed value
But
    var curPage by rememberSaveable {
        mutableStateOf(0)
    }

will not
This is painful as many Compose rememberXXXX use internal rememberSaveable and we can't pass key there like rememberPagerState and others.
Can this be reopened ? @adrielcafe @DevSrSouza

Bump

We will investigate

Unable to reproduce it here.
I add a simple BasicNavigationScreen and it seems that everything is being proper restaured.
var memoryState by rememberSaveable {
    mutableStateOf(0)
}
Text("Memory State: $memoryState", modifier = Modifier.clickable { memoryState++ })

adb shell am kill cafe.adriel.voyager.sample
Can you share more context and more examples @Tolriq ?

I'm deeper in the hierarchy and using Compose 1.5 but basically I'm having AndroidScreen in different modules.
Like :
class ProviderLocalDeviceAddScreen : AndroidScreen() {

    override val key: ScreenKey
        get() = "ProviderLocalDeviceAdd${super.key}"

    @Composable
    override fun Content() {
        val viewModel = getScreenModel<ProviderLocalDeviceAddScreenViewModel>()
        ProviderLocalDeviceAddScreenContent(viewModel)
    }

    @Module
    @InstallIn(SingletonComponent::class)
    internal class Navigation {

        @Provides
        @IntoMap
        @NavigationDestinationKey(ProviderLocalDeviceAddDestination::class)
        fun provideDestination(): OptionalScreenProvider<*> {
            return OptionalScreenProvider<ProviderLocalDeviceAddDestination> {
                ProviderLocalDeviceAddScreen()
            }
        }
    }
}

In the @Composable ProviderLocalDeviceAddScreenContent I have something simple like :
    val launcher = rememberLauncherForActivityResult(AdvancedOpenDocumentTree()) {
        scope.launch {
            viewModel.handleResult(it)
        }
    }

    var mediaMode by rememberSaveable {
        mutableStateOf(0)
    }
   Text("Memory State: $memoryState", modifier = Modifier.clickable { mediaMode ++ })
   Text("Launch", modifier = Modifier.clickable {  launcher.launch(null) })

With the dev option do not keep activity enabled.
On return from the SAF selection, the mediaMode will be reset to 0 and not restored.
If I change to
    var mediaMode by rememberSaveable(key = "toto") {
        mutableStateOf(0)
    }

Then it properly works. (But we can't do that for most of the Compose internal stuff.
I have absolutely no idea where to start to debug the ComposeHashKey generation issue.

Ok so I did more tests and seems the issue is about FadeTransition @DevSrSouza
FadeTransition(navigator) to navigator.lastItem.Content() fix this. (But I'd love to have transitions :)


XMLReporter listener cannot find file

Since encountering an earlier issue I reported (testNG not creating HTML report #562), which causes the html report to not be generated(and as a result my custom html reporter doesn't get executed), I decided to disable the default listeners and only enable the XMLReporter (since Jenkins requires it for the testNG plugin to report results) as well as my custom listener as shown below.

usedefaultlisteners
false

listener
org.testng.reporters.XMLReporter, com.theyTookOurJobs.MyCustomListener

When running this configuration, I receive this error:
java.io.FileNotFoundException: C:\SeleniumNavigation\selenium-grid-service\targe
t\surefire-reports\testng-results.xml (The system cannot find the path specified
)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:221)
at java.io.FileOutputStream.(FileOutputStream.java:171)
at java.io.FileWriter.(FileWriter.java:90)
at org.testng.internal.Utils.writeUtf8File(Utils.java:107)
at org.testng.reporters.XMLReporter.generateReport(XMLReporter.java:66)
at org.testng.TestNG.generateReports(TestNG.java:1115)
at org.testng.TestNG.run(TestNG.java:1074)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.ja
va:91)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMult
i(TestNGDirectoryTestSuite.java:204)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(Tes
tNGDirectoryTestSuite.java:107)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider
.java:113)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameCla
ssLoader(ForkedBooter.java:200)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(Fork
edBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
103)
I have run this without my listener as well so I know that's not this issue, am I missing a dependency that the XMLReporter needs or is there something else going on here?

Can be closed, duplicate of #592


Support pydantic dataclass models

I am using pydantic.dataclasses.dataclass because I need the __post_init__ dunder. However, I noticed that automodule does not generate the pydantic model documentation for these data classes. Looking at pydantic's docs, I can access the model using __pydantic_model__, but I'm not sure how to get this to happen automatically with automodule?

@GlenNicholls Thanks for raising this feature request here! I agree it would be really helpful to support pydantic.dataclasses.dataclass. At first glance, this should be possible without too much effort but I will need to take a closer look at it. I will come back to you soonish.

Do you need a custom signature prefix for dataclasses to distinguish them from pydantic models/settings?

No, the reason I'm using pydantic dataclass is because I need validation for a config file but also to modify some behavior based on data relationships with __post_init_post_parse__/__post_init__. I don't really care if those docstrings are present as it's taking care of transformations that don't really concern users. The docstring is in the code for devs because it matters to them, but It's not relevant otherwise.

Do you need separate configuration properties for dataclasses to behave differently from pydantic models or do the same configuration settings apply as for pydantic models?

Nope. I'm sure someone will ask for that eventually, but I just want the dataclass model to get documented the same as a pydantic model. I'm happy with the defaults so those would be fine with me for dataclasses.

Okay thanks for your response. I guess I will support explicit configurations for dataclasses right away instead of using the same configuration settings as for models. As you've pointed out, this will become a requirement eventually by someone using dataclasses. Supporting it right from the beginning may prevent backwards incompatibility later on.
This will take me some time to accomplish and it will land in v1.8.0.

Is there a reason, why this is removed? Would be a nice feature.

Thanks to @coretl, there is an initial PR to provide support for dataclasses (see #298).
I would like to disucss further details here instead of the PR to keep others in the loop who might have not noticed the PR.
@coretl I really like the simplicity of your PR by treating dataclasses as a pydantic models. However, dataclasses will not be rendered as dataclasses in the docs but will be shown as pydantic models (more concretely, the signature prefix is not correct, see here). I worry that this behavior is not expected by most users. Instead, dataclasses should probably be specified as a pydantic dataclass instead of a pydantic model. @GlenNicholls @nilsAnso @coretl What is your opinion?
Moreover, there seem to be subtle differences between pydantic base model and pydantic dataclasses (see here and here). I believe it it will be necessary to run all tests on dataclass based models that already exist for pydantic models. Otherwise, we might miss some edge cases here.
Last but not least, I assume that users might want to configure the docs behavior of dataclasses to be different from pydantic models. This would have rather large implications. Ideally, we could leave this out for now.
I'm looking forward to your thoughts.

I worry that this behavior is not expected by most users. Instead, dataclasses should probably be specified as a pydantic dataclass instead of a pydantic model. @GlenNicholls @nilsAnso @coretl What is your opinion?

I suspect you are correct here, I never considered this when making my PR. Unfortunately I don't have any more time to work on this PR, so I will convert it to draft and leave it there in case it is useful for someone else making a final solution.


Could not find queueit_knownuserv3-3.5.0 in any of the sources (Bundler::GemNotFound)

Just a quick note that by yanking down version 3.5.0, we had a Staging deploy fail. Luckily, we caught it before we deployed to Production. A friendly note to remember that yanking a gem can be dangerous.
Users that have the yanked version in their Gemfile.lock will suddenly get errors the next time they deploy. Depending on how your deploy process is setup, this could cause downtime.
Thank you for all of your great work on this gem!

Thank you, Brittany.
You are right that it's dangerous, but in a way the effect you describe is also what we wanted.
We knew that version v.3.5 for ruby was broken, so having it running in production would be bad.
I really appreciate that you reached out and told us this. I hope we will not be yanking more gems in the future :)

I'm closing this one. Anybody using v.3.5 should downgrade to v.3.4.
v.3.5.1 will be out soon.

As a note, I was mistaken. We did deploy this to Production and it just caused us to fail out on our on-sale. If you yank a gem version again, we need to be notified, please.

I'm very sorry to hear that. Next time we will definitively inform you in due time.
One thing that troubles me is that another customer of ours informed us that version 3.5 was broken (would not run) and we could verify this. So how you managed to get it working in your staging and later production environments is a mystery to me.

@frwiqueueit there is a simple answer to that: we deployed 3.5 and did not have an on sale until today. The dependency got locked into the Gemfile.lock when you released it and then we didn't use it until today.


How to send WebSocket's in pathws://url:port/path ?

How to send WebSocket's in pathws://url:port/path ?
if ChatServer Client URL == ws://localhost:8887/chat

@Davidiusdadi - I think what @leesangboo, and what I wish to answer is the following:
How do I connect to a subpath if my websocket server only accepts connections to:
ws://<ip>:<port>/<path>
The question is not asking how one might get a path from a given open connection, but rather how one would connect to a subpath in a websocket server.
Perhaps this can be re-opened?

Yes, this would be pretty useful

Hello @lvivtotoro,
I currently don't understand what exactly would be useful. Could you elaborate more?
Greetings
marci4

No feedback on this issue for a month.
Reclosing the issue then!
Greetings
marci4

Hi,
I have a similar requirement to specify a path, when sparting a WebSocketServer.
A sample how this works in other websocket implementations can be found here:
https://www.oracle.com/technetwork/articles/java/jsr356-1937161.html
The sample on the page uses a context (path): mycontextroot and an endpoint: hello.
Sample URL is :  ws://localhost:8080/mycontextroot/hello
For your framework I only need a way to configure the path.
Regards

This library currently does not provide path/endpoint resolution. Instead of starting 2 different servers ws://localhost:1234/foo and ws://localhost:1234/bar, you start a single server on ws://localhost:1234 and within the onOpen(...) method you can check the requested endpoint using handshake.getResourceDescriptor() which returns a string, like "/foo" or "/foo/bar" and then implement further logic in your own code.
While this library probably won't implement full endpoint resolution, we could potentially offer basic support for registering callbacks to only be invoked for sockets whose handshake endpoint matches a certain path.


Changing amount should not result in PENDING status

This is confusing everyone.
I'm also wondering about keeping the same subscription instead of creating a new one. Subscriptions have histories, so we can track changes that way.

Coverage remained the same at 64.646% when pulling 4727f85120b949b1b78c51e3e0a35efb24249af3 on fix/change-amount-pending into 5df85d49ef10f6a4a9b43f1a6c42fcf2f6c837e0 on master.


'HvacGroupClimateEntity' object has no attribute '_target_temperature'

System Health details
System Information

version
core-2024.1.5

installation_type
Unknown

dev
false

hassio
false

docker
false

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
6.1.63-production+truenas

arch
x86_64

timezone
America/Los_Angeles

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4783

Installed Version
1.34.0

Stage
running

Available Repositories
1383

Downloaded Repositories
32

Home Assistant Cloud

logged_in
true

subscription_expiration
August 30, 2024 at 5:00 PM

relayer_connected
true

relayer_region
us-east-1

remote_enabled
true

remote_connected
true

alexa_enabled
true

google_enabled
true

remote_server
us-east-1-8.ui.nabu.casa

certificate_status
ready

instance_id
8fb2c7ce6af84f0bb82af2f5afeecfef

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

keymaster

zwave_integration
zwave_js

network_status
on

Dashboards

dashboards
19

resources
13

views
21

mode
storage

Recorder

oldest_recorder_run
January 21, 2024 at 10:31 PM

current_recorder_run
January 28, 2024 at 6:42 PM

estimated_db_size
462.57 MiB

database_engine
postgresql

database_version
15.3

Spotify

api_endpoint_reachable
ok

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Working on setting up a group for the first time, and when I change the mode from Off to Heat/Cool, I get this error:
'HvacGroupClimateEntity' object has no attribute '_target_temperature'
The error shows up as a popup at the bottom of the HA web UI and in the logs.
Note that the AC thermostat in this case is using generic_thermostat to give me a virtual thermostat (which then triggers an IR blaster to change settings on the AC unit).  I don't think this is related to the root cause, but wroth noting.
Full callstack:
2024-01-28 18:49:24.315 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140076596258112] 'HvacGroupClimateEntity' object has no attribute '_target_temperature'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 882, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 952, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/config/custom_components/hvac_group/climate.py", line 1218, in async_set_hvac_mode
await self.async_defer_or_update_ha_state(update_actuators=True)
File "/config/custom_components/hvac_group/climate.py", line 837, in async_defer_or_update_ha_state
await self.async_run_hvac(update_actuators=update_actuators)
File "/config/custom_components/hvac_group/climate.py", line 962, in async_run_hvac
or self._target_temperature is not None
^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'HvacGroupClimateEntity' object has no attribute '_target_temperature'
The group has two items, one heat only and one cool only.  Worth noting that in the details popup/card, I don't see the UI to set either the target high or low temp.
Any way, thanks for the help and the integration!  I was looking for something just like this last fall.  Don't actually need it to function right now as the AC units have been removed, just doing some testing before spring gets here.
Reproduction steps

Create new group
Open card from helpers list
Change mode from Off

Debug logs
2024-01-28 18:59:22.014 DEBUG (MainThread) [custom_components.hvac_group] Actutator climate.bedroom_virtual changed state: {'state': 'off', 'attributes': {'hvac_modes': [<HVACMode.COOL: 'cool'>, <HVACMode.OFF: 'off'>], 'min_temp': 45, 'max_temp': 95, 'target_temp_step': 1, 'current_temperature': None, 'temperature': 72, 'hvac_action': <HVACAction.OFF: 'off'>, 'friendly_name': 'Bedroom_virtual', 'supported_features': <ClimateEntityFeature.TARGET_TEMPERATURE: 1>}} (context 01HN9JGERRGN3S2GQGR683A1RA)
2024-01-28 18:59:22.014 DEBUG (MainThread) [custom_components.hvac_group] New min/max temps received from actuator climate.bedroom_virtual: (45, 95). HVAC Group climate.upstairs_climate new min/max temps: 45.0, 45.0
2024-01-28 18:59:23.347 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform esphome does not generate unique IDs. ID C0:49:EF:6F:21:2C-binary_sensor-_mmwave already exists - ignoring binary_sensor.mmwave
2024-01-28 18:59:23.347 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform esphome does not generate unique IDs. ID C0:49:EF:6F:21:2C-binary_sensor-_pir already exists - ignoring binary_sensor.pir
2024-01-28 18:59:23.347 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform esphome does not generate unique IDs. ID C0:49:EF:6F:21:2C-binary_sensor-_occupancy already exists - ignoring binary_sensor.occupancy
2024-01-28 18:59:25.477 DEBUG (MainThread) [custom_components.hvac_group] Actutator climate.upstairs_thermostat_thermostat changed state: {'state': 'unavailable', 'attributes': {'hvac_modes': [<HVACMode.OFF: 'off'>, <HVACMode.HEAT: 'heat'>], 'min_temp': 41, 'max_temp': 86, 'friendly_name': 'Upstairs Thermostat Thermostat', 'supported_features': <ClimateEntityFeature.TARGET_TEMPERATURE: 1>}} (context 01HN9JGJ53F15F214Y1B80FAQF)
2024-01-28 18:59:25.477 DEBUG (MainThread) [custom_components.hvac_group] New min/max temps received from actuator climate.upstairs_thermostat_thermostat: (41, 86). HVAC Group climate.upstairs_climate new min/max temps: 45.0, 45.0
2024-01-28 18:59:25.477 DEBUG (MainThread) [custom_components.hvac_group] Setting temperature (None-None) on HVAC group climate.upstairs_climate
2024-01-28 18:59:25.477 DEBUG (MainThread) [custom_components.hvac_group] Setting mode heat_cool on HVAC group climate.upstairs_climate
2024-01-28 18:59:25.477 DEBUG (MainThread) [custom_components.hvac_group] New temperature received from temp sensor sensor.upstairs_thermostat_current_temperature: unavailable. Setting on HVAC Group climate.upstairs_climate
2024-01-28 18:59:25.478 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/hvac_group/climate.py", line 800, in async_sensor_state_changed_listener
    await self.async_update_temperature_sensor(
  File "/config/custom_components/hvac_group/climate.py", line 935, in async_update_temperature_sensor
    float(new_temperature) if new_temperature is not None else new_temperature
    ^^^^^^^^^^^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'
2024-01-28 18:59:25.484 DEBUG (MainThread) [custom_components.hvac_group] New temperature received from temp sensor sensor.upstairs_thermostat_current_temperature: 72.5. Setting on HVAC Group climate.upstairs_climate
2024-01-28 18:59:25.484 DEBUG (MainThread) [custom_components.hvac_group] Actutator climate.upstairs_thermostat_thermostat changed state: {'attributes': {'current_temperature': (72, None), 'temperature': (72, None), 'current_humidity': (48, None), 'hvac_action': (<HVACAction.IDLE: 'idle'>, None)}, 'state': ('heat', 'unavailable')} (context 01HN9JGJ5B8CCQDSX6P2H3TM66)
2024-01-28 18:59:25.485 DEBUG (MainThread) [custom_components.hvac_group] Actutator climate.bedroom_virtual changed state: {'attributes': {'current_temperature': (72, None)}} (context 01HN9JGJ5CFSGFF6RYN3F22FS4)
2024-01-28 18:59:35.119 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/hvac_group/climate.py", line 825, in _update_at_start
    await self.async_defer_or_update_ha_state(update_actuators=True)
  File "/config/custom_components/hvac_group/climate.py", line 837, in async_defer_or_update_ha_state
    await self.async_run_hvac(update_actuators=update_actuators)
  File "/config/custom_components/hvac_group/climate.py", line 962, in async_run_hvac
    or self._target_temperature is not None
       ^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'HvacGroupClimateEntity' object has no attribute '_target_temperature'
2024-01-28 19:00:21.290 DEBUG (MainThread) [custom_components.hvac_group] Setting mode heat_cool on HVAC group climate.upstairs_climate
2024-01-28 19:00:21.290 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139921429107904] 'HvacGroupClimateEntity' object has no attribute '_target_temperature'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 882, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 952, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/hvac_group/climate.py", line 1218, in async_set_hvac_mode
    await self.async_defer_or_update_ha_state(update_actuators=True)
  File "/config/custom_components/hvac_group/climate.py", line 837, in async_defer_or_update_ha_state
    await self.async_run_hvac(update_actuators=update_actuators)
  File "/config/custom_components/hvac_group/climate.py", line 962, in async_run_hvac
    or self._target_temperature is not None
       ^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'HvacGroupClimateEntity' object has no attribute '_target_temperature'

Diagnostics dump
No response

I tried creating a new group with just two heaters in it (so single mode, no use of generic_thermostat ), and it does not get the same error.  Still no way to set the target temp in the card though.

I've found an edge case and i've added a fix that may address your issue. Could you please let me know if it's working well after updating to 0.1.1?

Confirmed, that fixed the error, thanks for the fast fix!  I am still not able to set the target temp. but I will create a new issue with more info on that.


prevent libgccjit.so download on unsupported os/arch

Alternative to #528, I find it easier to show what I meant rather than tell.
Fixing up the download URL while at it.
fixes #527

Ok, applied your suggestion regarding the message text change, fixed the conditional to be && instead of || and changed the raw-string that shouldn't be raw to a normal string.
Assuming CI agrees, this is good to go from my point.


Allow CORS for get requests

Currently, last-comments.js and counter.js would fail to fetch data from remark instance that requires a cross-domain request.
We can fix it by setting Access-Control-Allow-Origin: *  response header for all get requests.
It doesn't affect the main widget because it's loaded in an iframe with the same origin as remark instance.

We don't have CORS directly on the backend, however, demo site does some CORS on nginx level:
        #CORS
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, OPTIONS';
        add_header Access-Control-Allow-Headers "Content-Type, Authorization, X-Requested-With";
        if ($request_method = 'OPTIONS') {
             add_header 'Access-Control-Allow-Origin' '*';
             add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, OPTIONS';
             add_header 'Access-Control-Max-Age'        86400;
             add_header 'Access-Control-Allow-Credentials' 'true';
             add_header 'Access-Control-Allow-Headers' 'Authorization,DNT,X-Mx-ReqToken,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Cont
             add_header 'Content-Length' 0;
             add_header 'Content-Type' 'text/plain; charset=UTF-8';
             return 204;
         }

@Guria - are you proposing to move it to the backend?

I see your point that it belongs to nginx setup. As for me, I faced with problem while testing on local setup.
If you believe that app shouldn't be aware about cors headers, we can leave it as is and just document necessity of additional setup on nginx or whatever.
And, not neccessary, but would be nice, if we can solve it at least for local testing.

local setup is the valid point. Another valid point - backend should serve fronted without any help (extra setup) and mandatory nginx CORS config breaks this promise.
Do you know what exactly the minimal set of cors headers you need? Probably we can dynamically control 'Access-Control-Allow-Origin' some day and allow access from the real origins only. Currently, we don't know where consumer located, and for now * should be fine. You said "response header for all get requests", does it meant the only thing frontend needs is  add_header 'Access-Control-Allow-Methods' 'GET ? Probably we will have to allow X-XSRF-TOKEN and X-JWT headers as well. Anything else you can think about?

@Guria I have added cors to feature/cors branch, pls see/try if it makes frontend happy for local testing. The code https://github.com/umputun/remark/blob/feature/cors/backend/app/rest/api/rest.go#L121 allows all request types. You can play with this and see what the minimum level you actually need.

@umputun just tested feature/cors and all seems working now.


Refactor BigQuery sync task to optimize memory consumption

This PR is one last attempt at optimizing the sync_bigquery_release_files task. Instead of creating new variables for every computation, these changes minimize the memory footprint of the variables and removes variables from memory if not required. Reducing memory footprint did increase execution time but not by a considerable amount.
Expected usage for 3 million release files,
Peak memory usage for variables: ~50-60MB
Task execution time: ~1 min

This task is currently disabled, so we don't need this.


[TRG 5.01] Released Chart does contain environment specific values

The released Chart archive does contain all of the environment specific yaml files.
This can be fixed by adding specific patterns to the .helmignore like described here
blocks #108

Included in v1.0.0-rc1 as commented before:
https://github.com/eclipse-tractusx/digital-product-pass/blob/main/charts/digital-product-pass/.helmignore


joern-scan: add config for query dump destination

👍🏻 if you want to take it one step further: define a static DefaultDumpDestination e.g. in object JoernScan and refer to it in both the helptext and the parameter

yess, much nicer, danke


Clicking the pause button reloads the entire activity

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Easy Video Player.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Easy Video Player version: 0.3.0
Device OS version: 7.1.1
Device Manufacturer: Oneplus
Device Name: 3T

Reproduction Steps

Open a video using this library
Click on the pause button (specifically pause, not play or anything else)

Expected Result
Well, I would expect the video to pause
Actual Result
The entire screen becomes white for a second and then the activity is reloaded, thus closing the video.
I don't have any logs because for some reason my logcat clears out everytime this happens and says "broken pipe"
Code
VideoPlayerActivity.java:

import android.net.Uri;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;

import com.afollestad.easyvideoplayer.EasyVideoPlayer;

public class VideoPlayerActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_video_player);

        EasyVideoPlayer player = findViewById(R.id.player);
        String path = getIntent().getStringExtra(HaircutAdapter.PATH_KEY);
        player.setSource(Uri.parse(path));
    }
}

activity_video_player.xml:
<android.support.constraint.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context="com.gregskl.haircompare.VideoPlayerActivity">

    <com.afollestad.easyvideoplayer.EasyVideoPlayer xmlns:android="http://schemas.android.com/apk/res/android"
        android:id="@+id/player"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:evp_autoPlay="true"
        />

</android.support.constraint.ConstraintLayout>

I managed to get my logcat to work properly and here's what it logs, first of all:
files/example.mp4: java.io.FileNotFoundException: No content provider: /data/user/0/com.gregskl.example/files/example.mp4
and:
                                                         --------- beginning of crash
11-11 13:40:40.589 14712-14712/com.gregskl.example E/AndroidRuntime: FATAL EXCEPTION: main
                                                                         Process: com.gregskl.example, PID: 14712
                                                                         java.lang.NullPointerException: Attempt to invoke interface method 'void com.afollestad.easyvideoplayer.EasyVideoCallback.onPaused(com.afollestad.easyvideoplayer.EasyVideoPlayer)' on a null object reference
                                                                             at com.afollestad.easyvideoplayer.EasyVideoPlayer.pause(EasyVideoPlayer.java:582)
                                                                             at com.afollestad.easyvideoplayer.EasyVideoPlayer.onClick(EasyVideoPlayer.java:868)
                                                                             at android.view.View.performClick(View.java:5669)
                                                                             at android.view.View$PerformClick.run(View.java:22549)
                                                                             at android.os.Handler.handleCallback(Handler.java:751)
                                                                             at android.os.Handler.dispatchMessage(Handler.java:95)
                                                                             at android.os.Looper.loop(Looper.java:154)
                                                                             at android.app.ActivityThread.main(ActivityThread.java:6321)
                                                                             at java.lang.reflect.Method.invoke(Native Method)
                                                                             at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
                                                                             at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Could it be that pause doesn't work for some reason because the file is in my appliation's cache dir? But what I don't understand is how it manages to even play the video in the first place if it can't access it in my app's cache dir


137513231 : Integration test failure: api-scheduler

Force shutdown in case graceful shutdown timeouts.
Updated Readme.

You are missing tests.

Added tests.

I should have been more clear. An integration test would be far better than a unit test.
Start the server, have a client connect and disconnect, send a SIGUSR2 and watch the process die.
Do it again with a client that connects but doesn't disconnect and send a SIGUSR2, the process shouldn't die. Kill the process with a SIGKILL and it should die.
We really don't need the timeout. If our tests are hanging, we either do one of two things, send a SIGKILL always so we don't worry about this issue or we fix the issue. If we expect to have long running clients, then we go the SIGKILL route, if we don't then we are missing a proper close on the client side.

@rohitsharma04 @pradyutsarma Is this going to be fixed? This is still breaking our pipeline.

@fraenkel We fixed this by opening and closing tcp connections on the apiserver. Were trying to see if there is any other "better" way of achieving this. Will update the PR tonite.

@pradyutsarma I don't mind if we keep connections open. It will help once we switch to SSL. What is important is that we test the shutdown, and that our BOSH drain and BOSH stop send the right signals. This also means that when testing we should use the appropriate signals.  If we don't care about graceful shutdown during tests, just kill the server rather than trigger a quiesce.

After I run API sever - scheduler integration test,  I did not see any opening TCP connections to API sever, but there were remaining TCP connections from API sever to postgres.  In four test cases, the API servers eventually exited after some time. But the other two test cases,  the node processes never exited.

Added integration tests.

Added the one comment that applies to both which seems to show that we are exiting with an open connection.

I have run these tests a few times and have hit a few different issues.
[d][serviceBroker] spawned /usr/local/bin/node (pid: 24921)
[o][serviceBroker] {"timestamp":"2017-02-04T13:28:31.747Z","source":"autoscaler:servicebroker","text":"Service broker app is running","log_level":"info","data":{"port":11002}}
[o][serviceBroker] {"timestamp":"2017-02-04T13:28:31.782Z","source":"autoscaler:servicebroker","text":"Received SIGUSR2 signal, shutting down gracefully...","log_level":"info"}
[o][serviceBroker] {"timestamp":"2017-02-04T13:28:31.790Z","source":"autoscaler:servicebroker","text":"Everything is cleanly shutdown","log_level":"info"}

• Failure [1.099 seconds]
Integration_Api_Broker_Graceful_Shutdown
/Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:206
  Graceful Shutdown
  /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:152
    Service Broker
    /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:150
      waits for in-flight request to finish before shutting down server on receiving SIGUSR2 signal [It]
      /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:148

      Expected error:
          <*net.OpError | 0xc42007a0f0>: {
              Op: "write",
              Net: "tcp",
              Source: {IP: [127, 0, 0, 1], Port: 50729, Zone: ""},
              Addr: {IP: [127, 0, 0, 1], Port: 11002, Zone: ""},
              Err: {Syscall: "write", Err: 0x20},
          }
          write tcp <IP_ADDRESS>:50729-><IP_ADDRESS>:11002: write: broken pipe
      not to have occurred

      /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:142

[d][serviceBroker] spawned /usr/local/bin/node (pid: 25271)
[o][serviceBroker] {"timestamp":"2017-02-04T13:31:12.108Z","source":"autoscaler:servicebroker","text":"Service broker app is running","log_level":"info","data":{"port":11006}}

• Failure [0.537 seconds]
Integration_Api_Broker_Graceful_Shutdown
/Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:206
  Non Graceful Shutdown
  /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:204
    Service Broker
    /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:202
      kills server immediately without serving the in-flight requests [It]
      /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:201

      Expected an error to have occurred.  Got:
          <nil>: nil

      /Users/fraenkel/workspace/app-autoscaler/src/integration/integration_api_broker_graceful_shutdown_test.go:196
------------------------------

There again is something definitely wrong with the API server and shutdown.
I modified the test to PUT a new policy and have the scheduler hang. This means there should be an outstanding request.
The moment the SIGUSR2 happens, the server still shuts down. The request sees an EOF rather than a 200. You see below that the creating/updating schedule does not finish.
[d][apiServer] spawned /usr/local/bin/node (pid: 32389)
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.565Z","source":"autoscaler:apiserver","text":"Autoscaler API server started","log_level":"info","data":{"port":10001}}
[o][apiServer] Executing (default): SELECT 1+1 AS result
[o][apiServer] Executing (default): SELECT 1+1 AS result
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.925Z","source":"autoscaler:apiserver","text":"DB Connection has been established successfully","log_level":"info"}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.926Z","source":"autoscaler:apiserver","text":"DB Connection has been established successfully","log_level":"info"}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.966Z","source":"autoscaler:apiserver","text":"Input policy JSON schema structure is valid","log_level":"info","data":{"app id":"1486219285580474885"}}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.970Z","source":"autoscaler:apiserver","text":"Input policy JSON validated successfully. Creating policy..","log_level":"info","data":{"app id":"1486219285580474885"}}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.970Z","source":"autoscaler:apiserver","text":"Policy creation request received","log_level":"info","data":{"app id":"1486219285580474885"}}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.971Z","source":"autoscaler:apiserver","text":"Policy has schedules, creating/updating schedules ..","log_level":"info","data":{"app id":"1486219285580474885"}}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.989Z","source":"autoscaler:apiserver","text":"Received SIGUSR2 signal, shutting down gracefully...","log_level":"info"}
[o][apiServer] {"timestamp":"2017-02-04T14:41:25.995Z","source":"autoscaler:apiserver","text":"Everything is cleanly shutdown","log_level":"info"}

I have pushed my changes to https://github.com/cloudfoundry-incubator/app-autoscaler/tree/graceful_shutdown
so you can see how I rewrote the API tests.

Thanks for the work to get this fixed properly.
I did some minor cleanup.
Waiting on a green build before I close this out.


Display block not detected

Turns into

while

turns into

The console yields this

The same yields for inline formatting. Using fresh new chrome.

documentation was incorrect; display math actually requires [(; ... ;)]. See #5.


Component without the "bindings" does not get an isolate scope

Hi @toddmotto. I'm using your patch and I noticed that when I omit the bindings property of the component below, it doesn't get an isolate scope, while using angular.js-1.5.0-rc.0 it does. See:

ps: should've cropped the images srry

Fixed in https://github.com/toddmotto/angular-component/commit/33113bf8162b8aa291a190b51499cce35605f663


As a computer science student I want to be able to add new assignments

I want to be able to add new assignments, so I can keep track of what I need to complete.

add n/NAME d/DESCRIPTION c/COMPLETEDNESS e/ENDDATE p/PLANNEDFINISHDATE [t/TAG]


4/5 Publish

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

breadcrumb/toc.yml
:white_check_mark:Succeeded

docs-ref-autogen/TOC.md
:white_check_mark:Succeeded
View

docs-ref-autogen/feature.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment/operation.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/lab.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/lab/secret.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/lock.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/policy.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/policy/assignment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/policy/definition.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/provider.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/refTOC.md
:white_check_mark:Succeeded

docs-ref-autogen/resource.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/resource/link.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/tag.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/availability-set.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/boot-diagnostics.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/diagnostics.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/disk.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/encryption.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/extension.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/extension/image.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/image.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/nic.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/unmanaged-disk.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vm/user.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss/diagnostics.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss/disk.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss/extension.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss/extension/image.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/vmss/nic.pycliyml
:white_check_mark:Succeeded
View

docs-ref-conceptual/TOC.md
:white_check_mark:Succeeded

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View

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


Cloudflare Service Token not working with new Additional headers in 3.28

I'm accessing OctoPrint externally through a cloudflare ZT application and saw where you guys literally days ago added the ability for octopod to utilize this with service tokens. I created a new token and added it to my CF application, pasted the client id and secret in octopod and hit request, but it's telling me "The data couldn't be read because it isn't in the correct format"
My client id and key were pasted in exactly this format with spaces:
CF-Access-Client-Id: 2ecxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.access, CF-Access-Client-Secret: 1axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Does anyone have any ideas? Please and thanks

Thanks! This was on the screen to add a new printer

Has anyone ever had a chance to look into this?

I am having this issue as well
I have my cloudfare tunnel forwarding to NGINX Proxy Manager then to Octoprint (I run pihole and this allows me to keep the traffic local when on the LAN).  So the domain I use resolves to the NGINX IP when on my wifi.
When I get the error I am on cellular data, when I am on my wifi it works but once I turn off wifi it stops working.
So it looks like the issue is with the CF tunnel setup.

Nevermind I fixed it, I didn't select Service Auth under Action when creating the application. I had it as Allow.

@AdmiralMichael , good to hear you got it working. Let me know if I should update the documentation.
Is this still an issue for anyone else?
Thanks,
Gaston

I've just tried this again, verified everything in the instructions, but am getting Invalid HTTP upgrade (302), which is not covered in the instructions


Define the Azure Endpoint and other site-specific options

Added the azureendpoint site-specific option as an ipaddress definition to make it easier for Azure VMs using dhcpcd to get their WireServer endpoint address.
Added binhex definitions for all otherwise undefined site-specific options so that site-specific hooks can use them.

This PR supersedes PR #284 and PR #293.

Thanks!


[Storage] serialize_iso settable decimals place input

This is the proposed proof of concept code change that would allows us to re-use a well-written and sophisticated utility that already exists rather than home-rolling our own solution. I also added a sample test case (but no recordings, we can add recordings when we add these tests after generated code changes roll out)
Sample test case output:
'3005-05-11T12:24:07.0000000Z'
'3005-05-11T12:24:07.0000000Z'
'3005-05-11T12:24:07.0000010Z'
'3005-05-11T12:24:07.0000120Z'
'3005-05-11T12:24:07.0001230Z'
'3005-05-11T12:24:07.0012340Z'
'3005-05-11T12:24:07.0123450Z'
'3005-05-11T12:24:07.1234560Z'
'2023-12-08T07:00:00.0000000Z'
'2023-12-08T08:00:00.0000000Z'

As expected, 😄 properly expanding the microseconds width (with last 2 being time-zone aware PST inputs). And all network calls not being rejected server side!

/azp run python- storage - tests

/azp run python - storage - tests

API change check
API changes are not detected in this pull request.


Fixed issue #3 page scrolling

😀 Fixes: #3
Before :
Page wasn't automatically scrolling to Mental Health Articles section.

Thank You for Contributing. Great Work!


cargo-c: 0.9.13 -> 0.9.19

Description of changes
Changelogs: https://github.com/lu-zero/cargo-c/releases

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Closing because it was done in https://github.com/NixOS/nixpkgs/pull/236611.


fix(set-shas): handle gracefully circle ci api glitches

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nrwl/nx?version=dev:ff01c917b8fe574804c518447b15d927aa453c8e

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nrwl/nx?version=dev:ff01c917b8fe574804c518447b15d927aa453c8e

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nrwl/nx?version=1.6.1


Supporting topics > 127

when running topics of size more than 100, current module doesnt support it. This pr will handle the number of topics more than 100 and also have added hyperparameter tuning according to the ref paper based on the no of topics

Good idea! but you are currently overwriting the alpha parameter if one is set

i was experimenting on different alpha parameters rectified the same, also i have added average coherence which might be useful


Load debug scripts not prompting after page reload

Category

[x ] Question
[ ] Typo
[ ] Additional article idea

Question
I'm on version 1.10.0 and using the configuration within serve.json to debug our SPFX applications. When I run gulp serve I have some profiles to go to the correct environment, and on first load I get the 'Load Debug Scripts' prompt. However when I reload the page I'm not prompted again and lose debug capability, allow the query string params are still there. This wasn't happening previously and I'm not sure what may have changed to cause the issue, but it forces me to restart gulp every time which is obviously very inconvenient. It used to be that any time I refreshed the page it would prompt me correctly. Any help?
Environment details (if applicable)

OS: Windows 10
Framework: Node.js v10
Browser(s): FireFox
Tooling: SPFx v1.10.0

See #5385 or #5395

This is working now today . I am getting the prompts and changes reflected
Browser : MS edge (chromium)


bgutil stats: support prefix command line attribute

What is the main use case ?

To be able to send metrics in observability.graphite. :)

Coverage increased (+0.003%) to 81.665% when pulling 5a5997a689dcff8df6596ce9ed4e640b7e2ff073 on iksaif:stats into 335e1494cd36b4360401ed70fba8e23b5384e263 on criteo:master.


Update WebIDL to use undefined instead of void

We updated weedle to use undefined instead of void in rustwasm/weedle#43, so now the plan is to update all WebIDL too.
The changes here are split into two commits for reviewing. The first commit updates all of the WebIDL and the second commit updates how the tokens are used from weedle.
Overall the changes seem to be fine because the generated bindings don't show any differences.

Looks great to me, thanks! I think the only thing this needs now is a weedle publish, right?

Looks great to me, thanks! I think the only thing this needs now is a weedle publish, right?

Yeah I think we just need to publish a new version of weedle and use it here, which will also unblock progress in #2373. Created a PR at rustwasm/weedle#44

Yeah I think we just need to publish a new version of weedle and use it here, which will also unblock progress in #2373. Created a PR at rustwasm/weedle#44

Ok published!

Ok published!

Thanks! This should be ready now

Thanks! This should be ready now


bug at install on AWS

I'm installing CARTO on AWS (following Michael Minn's excellent tutorial http://michaelminn.net/tutorials/carto-aws/). Did all the steps but I get an error when I try to start the processes.
Specifically, when I try to do the command :
cd cartodb && bundle exec script/resque > /dev/null &
I get the error:
(/home/ubuntu/cartodb/config/app_config.yml): did not find expected key while parsing a block mapping at line 339 column 5
I think that organization should be uncommented in yaml file. I uncommented the line and reran the command. This time I get the following error:
/home/ubuntu/cartodb/app/controllers/carto/api/public/oauth_app_presenter.rb:30: syntax error, unexpected '.'
...es_by_category(oauth_app_user&.all_scopes)
Anyone can help?

I realize that I got an error earlier in the process that I didn't catch at first. This is when I npm install in Windshaft-cartodb directory. They say in the docs that I should do sudo npm install -g<EMAIL_ADDRESS>followed by yarn install. I get the following error:
npm ERR! Linux 4.4.0-1087-aws
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @carto/mapnik package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build

Hi @aginpatrick!
The tutorial you are following is a bit outdated. The syntax error from the first message points to a wrong Ruby version: we require 2.4. I recommend you to double-check the requirements here: https://cartodb.readthedocs.io/en/latest/install.html
If you find more installation issues, there is a forum for this kind of questions: https://groups.google.com/forum/#!forum/cartodb
I hope this helps. I'm closing as it doesn't look like a bug.

Hello there,
i am tring ot install Windshaft  and hit the following issue:
905 verbose stack Error<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
905 verbose stack Exit status 1
905 verbose stack     at EventEmitter. (/data/undp/nodev14/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
905 verbose stack     at EventEmitter.emit (events.js:400:28)
905 verbose stack     at ChildProcess. (/data/undp/nodev14/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
905 verbose stack     at ChildProcess.emit (events.js:400:28)
905 verbose stack     at maybeClose (internal/child_process.js:1058:16)
905 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
906 verbose pkgid<EMAIL_ADDRESS>907 verbose cwd /work/ds/carto/Windshaft
908 verbose Linux 5.4.0-90-generic
909 verbose argv "/data/undp/nodev14/bin/node" "/data/undp/nodev14/bin/npm" "install" "@carto/mapnik"
910 verbose node v14.18.1
911 verbose npm  v6.14.15
912 error code ELIFECYCLE
913 error errno 1
914 error<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
914 error Exit status 1
915 error Failed at the<EMAIL_ADDRESS>install script
the mapnik(nide-mapnik )  is installed. Also ruby 2.4
using node 14....could this be the issue?
thanks


make master the development branch

This PR will increment the development Version on master. All Changes related to Version 2.0.x should be placed in the 2.0.x branch. Deploying to master means that this will be included in the next Major release.

Hi @serious6, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

:+1:

was wondering if master might be 3.0-SNAPSHOT or 2.1-SNAPSHOT ?

Good question.  Given that you called the branch 2.0.x that would make sense.  However, I'm thinking that in master we can break APIs, in release branches we can't.  Hence, we can have a model where:

Branch name would be 2.x.x
For each release we make out of 2.x.x, we call it 2.1.x, 2.2.x, etc.  For releases like 2.1.0, 2.1.1, 2.1.2, they would be tags on 2.1.x branch.
Master would be 3.0-SNAPSHOT
We can also have a 2.0-SNAPSHOT from the 2.0 main branch.
We will have specific packages for each release corresponding to a tag in the codebase.

Thoughts?

Looking at spring or apache they resolve their branch-names like 2.0.x, 2.1.x.
So maybe we just need to create another branch that is named 2.1.x and have 3.0 version on master.


[Fix] (schema change) fix the bug that non light schema change tables can rename column

How to reproduce the problem
1 crate table in 1.1
2 Upgrade to version 1.2
3 rename column
4 select * from table，Report an error.
reason
Tables disable light schema change are not allowed to perform column rename. However, when upgrading from 1.1 to 1.2, maxColUniqueId will be initialized to 0, resulting in invalid judgment

run buildall


'django.contrib.humanize' needs to be in installed_apps

'django.contrib.humanize' needs to be in the installed_apps list, this isn't mentioned in the "read me".

Fixed, thanks!


UTM projections in Graticule labels

The current Map Graticule example displays the labels in LongLat values due to the default projection.
Although I would like to display these values in an UTM projection, e.g. EPSG: 31982.
I have a code here: This merges the reprojection-by-code and map-graticule examples
I want this:

To become this:

The documentation needs improving as it completely fails to mention that the view projection must have both an extent and world extent.
"Layer that renders a grid for a coordinate system" is misleading as currently the only coordinate system is EPSG:4326 which is hardcoded in ol/layer/Graticle, ol/geom/flat/geodesic.meridian and ol/geom/flat/geodesic.parallel.
There seems to be no reason why an option to base a graticule on coordinate system for other projections should not be possible with a few changes (e.g. the default intervals would not be appropriate for projection units other than degrees, nor would world extent be suitable for use in graticules which are not based on degrees).

Supporting UTM independent of map projection would be much appreciated.
I guess for UTM a fixed zone might be a Graticule option. Automatically using the nearest zone from map center could be useful.
I will also look into it, provided I find the time.

I am also looking for UTM support, hope it will be added soon :)

Do you know if you managed to make the grid of the images shown?


feat: add connection string redaction utilities COMPASS-5308

I’ve merged this, but I wanted to leave as a comment here that there is ongoing conversation about the exact format of proxy options in the connection string in https://github.com/mongodb/specifications/pull/1103#discussion_r762362073. We may need to re-adjust the logic here if we do decide to change the spec. However, I don’t see any immediate downside to publishing and using this code as-is.


Connections to non-default MySQL ports fails - Upgrade MySQL Connector/J

The version of the MySQL JDBC driver bundled with Saiku ignores the TCP port in the connection string and always connects to port 3306. Replacing the driver with 5.1.17 fixes the problem.

fixed


Show popup data for unknown terms if any data exists

Per the term import manual page https://luteorg.github.io/lute-manual/usage/terms/bulk-term-import.html, if there is data, the popup should show it.

Added to develop.

Released in 3.6.1.


Starbound - Unstable works

hey @her001, this failed because the line before is missing a comma, and the line you added has a redundant trailing comma :) If you can replace that commit with a fixed one, I can merge.


Remove ViewPropStyle to support newer RN versions

Please merge this if it totally fine and test, because is very important for new RN versions

Thanks and released as part of v0.9.0. Sorry, my life has taken me away from React Native for the past 2 years…


Get 'command failed due to signal segmentation fault 11' when I use JSON as parameter type

I just create a simple function like this   func foo(j:JSON) { }
When Xcode 6.2 compiler throws out error 'command failed due to signal segmentation fault 11' . But if I remove it, it compiles properly.
Thanks
Jake

I've run into this same issue. Love to know if you found any solution.

No, I haven't.I wanted all the logic stay in my Framework target before.
But I have to move those logic from my Framework to the app. Here is my
repo.
https://github.com/JakeLin/SwiftWeather/blob/master/Swift Weather/ViewController.swift#L66
Please let me know if you find any.
Thanks
Jake
On 12 January 2015 at 08:23, Lucas Derraugh<EMAIL_ADDRESS>wrote:

I've run into this same issue. Love to know if you found any solution.
—
Reply to this email directly or view it on GitHub
https://github.com/SwiftyJSON/SwiftyJSON/issues/125#issuecomment-69512164
.

I’m also seeing this. Would be great to have fixed!

:+1:  same problem here :-(

same problem here with 6.1.1

@litan1106 if you scan through the referenced issue https://github.com/SwiftyJSON/SwiftyJSON/issues/129 above you can find a work around.  This issue should probably get closed with a reference to that one since it's got more detail in it.   If you copy the SwiftyJSON.swift  into your project, instead of using cocoapods and/or other methods where you need to include the module, it'll work.  Tests may still break though unless you do some further hackery also listed in the other write up.

yea, i was using git submodule... Thanks.

Hi, I was having this issue and I was reading to throw myself of a cliff. I just found out what the problem was for me. Maybe this will help someone in the future.
I'm using SwiftyJson through CocoaPods.
Here's my code:
HttpClientManager.get(url,
      headParameters: headParams,
      success: { (responseData: JSON) -> Void in
         //If I comment the next line, I get the seg fault 11
         SwiftEventBus.post(Constants.Events.LOGIN_SUCCESS, sender: responseData[""].string)
      }, failure: { (error: String) -> Void in
         //if I comment the next line, I get the seg fault 11
         SwiftEventBus.post(Constants.Events.LOGIN_FAILURE, sender: error)
      })

If I never use the closure variable (responseData in success and error in failure) then I get the segmentation fault 11.

@nunogoncalves +1 this saved me hours of blaming Xcode for crashing!

@michaldudek I'm glad I could help someone. :)
Today was another fight with xcode for no reason was keeping indexing files indefinitely and I lost sintax highlighting. Had to uninstall and reinstall xcode to make it back to work.

Maybe it needn't such complex codes to make segmentation fault 11
func wrongswap( var a :  T, var b : T ) {
let temp = a
a = b
b = temp
}
var a = ""
var b = ""
func wrongswap(&a, &b)
I'm Xcode 6.3.2. In fact i don't know how Swift deals with & , but i guess it's just the confusing & makes compiler reports such a confused seg fault 11. LOL

Same issue here.

@nunogoncalves oh man, thanks for saving my sanity here.. That was it for me: not using the closure variable.

When I import a map stock, the same problem happened. I haven't settle it.
`#ifndef MAMap_Bridging_Header_h
#define MAMap_Bridging_Header_h
#import <MAMapKit/MAMapKit.h>
#import <AMapSearchKit/AMapSearchKit.h>
#endif /* MAMap_Bridging_Header_h */`

@IBAction func Login(sender: AnyObject) {
let parameters = ["username" : InputUsername.text, "pwd" : InputPassword.text]
let url = "http://<IP_ADDRESS>:8080/yuqin/scheduleapp/ScheduleApp_login.action"
Alamofire.request(.GET, url, parameters: parameters)
.responseJSON { response in
//处理结果
switch (response.result) {
case .Success(let value):
print("BeginOrderResult: (value)")
if value["status"] == 1 {
                    //更新本地保存的密码
                    let userDefault = NSUserDefaults.standardUserDefaults()
                    //userDefault.setObject(newPwd, forKey: "password")
                    userDefault.synchronize()
                }
            case .Failure(let error):
                NSLog("Error: %@", error)
            }
    }

}
same problem that  segmentation fault 11

This issue has been inactive for a while so I'm gonna go ahead and consider it fixed. Please let us know if you want to reopen it.


shelfnet share weights?

I am pretty appreciate your work.
I try to re-implement your work, but when I refer to your pytorch code, I don't find any shared-weights operation but it does mentioned in your paper.
I notice that the shared-weights block should appear in every stage in shelfnet's decoder side and the in/out channels of conv2d are not the same, so how can I share the weights of residual block?

Thanks for your interest. The "decoder side" are defined in encoding/models/LadderNet_v6.py, where the module "BasicBlock" is used in many stages. "BasicBlock" is a modification of the standard BasicBlock in ResNet, but it only contains 1 conv layer (self.conv1). self.conv1 is used twice in the forward pass, and this is where the shared-weights work.

Just to clarify, in the same file, although Bottleneck is defined, it's in fact never used.


Check case on Glue Connection dict return object.

Added a case check for the password and username fields for the glue connection connector when retrieving from catalog.
Feature or Bugfix

Bugfix

Detail
Context: When using an aws secret created and managed by RDS as the credential for a glue postgresql connector,
Problem: The awswrangler library throws an error looking for "USERNAME" and "PASSWORD" keys in the connection details dict when the actual key set by RDS is "username" and "password" that is stored in the secret.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 4d0bdd5dac8dd46e38708ad35734044c68299254
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 26c0c639724803318418e48323eabb280333d567
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 35cfcda59e884026dae57733fc176b685a0069f1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 39d8b1c1c127b9c439ed41d1c2d741fdd5b668c3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ada1c7f9a4322b57ade16ff6f2565a9a6c68f182
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 0e4dff7224d3a4820b848371686c7a9266a987ba
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


access_token reqest  ok 200  -What KeyError

File "C:\Program Files\JetBrains\PyCharm Community Edition 2023.2.1\plugins\python-ce\helpers\pydev\pydevd.py", line 1500, in _exec
pydev_imports.execfile(file, globals, locals)  # execute the script
File "C:\Program Files\JetBrains\PyCharm Community Edition 2023.2.1\plugins\python-ce\helpers\pydev_pydev_imps_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "Z:\Pyton\claimclicks_bot\gpt_temp.py", line 4, in
print(bot.prompt("hello"))
File "Z:\Pyton\claimclicks_bot\venv\lib\site-packages\ProGPT\Generative.py", line 84, in prompt
if data["message"]["status"] != "finished_successfully":
KeyError: 'message'
from ProGPT import Generative
access_token="***********"
bot = Generative(access_token)
print(bot.prompt("hello"))
print(bot.prompt("how are you?"))

@avtosubaru25 I've figured out the cause of this problem, and will update you as soon as I implement the solution. Thanks.

Duplicate of #5.


For given root path: "/path/to/table"  if the sub path "/path/to" has deltalog directory, the function return True

Bug
For given root path: "/path/to/table"  if the sub path "/path/to" has deltalog directory, the function return True
Describe the problem
I am using isDeltaTable method (Delta version 2.0.0) in my Jupyter notebook and have weird behavior with this code:
DeltaTable.isDeltaTable(spark, "/path/to/table")
For given root path: "/path/to/table"  if the sub path "/path/to" has deltalog directory, the function return True.

The Documentation the provided is:
"classmethod isDeltaTable(sparkSession: pyspark.sql.session.SparkSession, identifier: str) → bool
Check if the provided identifier string, in this case a file path, is the root of a Delta table using the given SparkSession."
(https://docs.delta.io/latest/api/python/index.html)
So the question is : if the root the I provided path don't contains Delta table ,
but the sub-root path has delta table and 'isDeltaTable' returns True - is this not a bug? or am I missing something?
Expected results
For given root path  isDeltaTable will return True if there is Delta table only in at the root path,
and False otherwise(even if in the sub-path there is delta log)
Environment information

Delta Lake version: 2.0.0
Spark version:3.2
Scala version:2.12

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[X] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[ ] No. I cannot contribute a bug fix at this time.

@bariudin777 Not clear how you got into this state. This doesn't seem like a valid state. Why is there _delta-log under path/to/ and path/to/table? The _delta-log under path/to indicates a Delta table is there, but it shouldn't contain any subdirectories that have _delta-log.

@vkorukanti, thank you for the reply.
This isn't the issue. The concern is about the presence of directories named "_delta_log" along a given path. According to the Delta documentation, it clearly states that the "IsDeltaTable" function returns True/False based on whether the specific path contains a Delta table, not if there are delta logs in some of the directories along the path.
"The main class for programmatically interacting with Delta tables. You can create DeltaTable instances using the path of the Delta table."
Therefore, for a given path without any delta logs, the method should return False instead of True.
So for given path there is no delta log, the method need to return False and not True.

@vkorukanti any suggestion?


Cannot find ElevenLabs API key

I cannot find ElevenLabs API key, it shows xi-api-key is in the 'Profile' tab on https://beta.elevenlabs.io. But the 'Profile' tab doesn't exist.

Click your avatar (or initials) in the top right of the Eleven Labs website, Profile is one of the options under the menu that appears. Your API key should be right at the top of the Profile page.
I’ll make it more clear in the app.

haha


Point of Sale and Inventory System REST API

Requirements:
- IntelliJ
- Docker for Windows
- Postman (optional)
Instructions for running

Open the marpos folder in IntelliJ. This should open the entire folder in the IDE. Make sure to resolve the errors shown by the IDE before proceeding to the next step.
Open your Docker application. In the IntelliJ IDE, there must be a file named docker-compose.yaml in the directory Rest API/Point of Sale/marpos/. Run it once in order to set up the Docker application.
In the containers tab of the Docker application, you should see now see a container labeled marpos. Run this in order to start the Mongo Database.
Run the application in IntelliJ.

The database may be accessed using Port 8081 while requests may be sent to Port 8080.
Features
Classes
Below are the two classes created in this version which are definitely subject to change. Simple attributes have been placed at the moment for ease of testing and development. The id Strings are auto-generated and the names are unique for each class.
Enumeration Class
MenuItem Class

String : id
String : name
List : ingredients

Ingredient Class

String : id
String : name
Double : quantity
Enumeration : unit

Repositories
Repositories are mechanisms for encapsulating storage, retrieval, and search behavior which emulates a collection of objects in Spring. These have the @Component annotation above them.
Controllers
Controllers are responsible for processing incoming REST API requests, preparing a model, and returning the view to be rendered as a response. These are responsible for handling GET, POST, PATCH, PUT, and DELETE requests. In this version, the controllers have been populated with pseudo-code in preparation for the development of those features. These have the @RestController or @Controller annotations above them.
Service Layers
Service layers define an applications boundaries and its set of available operations from the perspective of interfacing client layers and are annotated with @Service.

I'll be creating another branch and redoing things on my side because I want to be more systematic in the way I am doing things. You guys can reopen this if you want though.