Understanding Quality of Service (QoS)

Proposed title of the article
Understanding Quality of Service (QoS)
Introduction paragraph (2-3 paragraphs):
People optimize their networks so that these networks can perform at their full potential. QoS is an essential set of technologies in networking that allow you to optimize your network, allowing it to run at its full potential. Having an optimized network ensures that intensive applications run efficiently due to the availability of adequate network resources.
Key takeaways:

The reader will gain an understanding of what is Quality of Service

How QoS utilizes traffic marking, queuing, and the resource reservation protocol to guarantee the optimal performance of critical applications on a network.

The importance of QoS on a network.

The best scenarios to use QoS

References:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc787218(v=ws.10)?redirectedfrom=MSDN
https://www.tutorialspoint.com/what-is-rsvp-resource-reservation-protocol

Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

I have immediately closed my previous issue.
On Tue, 11 May 2021, 23:56 hectorkambow, @.***> wrote:

to help avoid a backlog queue we are only accepting one article topic/pr
approved at a time 👍
We can re-open this one when the 1st one is published. @Su-sid
https://github.com/Su-sid
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/issues/2218#issuecomment-839160901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO66GCSHA27IYXXESUGPCDTTNGKZRANCNFSM44CGQPCA
.


Help please, how to set the default paramSerializer to $httpParamSerializerJQLike?

I try the following config to setup $httpProvider defaults, but the $httpParamSerializerJQLike is not invoked when I post a request using $http.post(myUrl, {phone: '18812222'}).then(func1, func2);. The form data in the post request is a JSON string {"phone":"18812222"}, which is not serialized JQLikely.
myApp.config(['$httpProvider', function ($httpProvider) {
    $httpProvider.defaults.headers.post["Content-Type"] = "application/x-www-form-urlencoded";
    $httpProvider.defaults.paramSerializer = '$httpParamSerializerJQLike';
}]);

Thanks

I have the same problem using Angular 1.4.6.

The paramSerializers are for serializing...params (not the payload/data of the request).
I.e. $http.get('/url', {params: {foo: 'bar'}}).
Currently, automatically serializing the data is not supported (but you could use the provided paramSerializers to serialize it manually).
--
Closing as this works as expected atm and the feature request for adding support for serializing data is tracked in #6039.

BTW, you can use a paramSerializer to serialize payload/data, but you need a little setup and it is not guarranteed to work in all edge-cases, as it hasn't been designed/tested for that purpose.
See https://github.com/angular/angular.js/issues/6039#issuecomment-113502695.


Cannot make proper acceleration at uphill.

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
Hi team,
I'm currently running Autoware with Carla, and found a situation that the vehicle stucks at uphill.
Here's the rviz videos of the situation: [rviz1] [rviz2]

rviz1: This video shows a driving with default setting of slope compensation, and it shows that the vehicle cannot go uphill.
rviz2: I tested the situation with planning simulator, and this also shows that the vehicle cannot go uphill either. I checked this because I thought this issue could be from bad localization at the uphill, but it seems not (at least for now).

Also, while running the simulation above, I cannot know why the shape of the drivable area is weird.

Here's more information of the situation:

Starting/Goal point (from launch.log)

initial pose - x: -74.346236, y: 17.611892, z: -0.062959
initial orientation - qx: -0.004039, qy: 0.003657, qz: 0.707924, qw: 0.706268
goal pose - x: -1.848311, y: 87.232613, z: 2.275307
goal orientation - qx: 0.000000, qy: 0.000000, qz: -0.719365, qw: 0.694632

Map: Town03 [Town03]
ros2bag file: [ros2bag]
launch.log file: [launch.log]

Could anyone please check this?
Thanks!
Expected behavior
I hope the vehicle to drive uphill well, and reach to the goal point.
Actual behavior
But the vehicle could not reach to the goal, as it stucks before the uphill.
Steps to reproduce

Pull image from https://github.com/autowarefoundation/autoware/pkgs/container/autoware/321564631?tag=universe-devel-cuda-0.39.1-amd64 and run Autoware with Carla, using autoware_carla_interface.
Run ros2bag file above.

Versions

OS: Ubuntu 22.04 (Docker), Ubuntu 20.04 (host)
Autoware: 0.39.1
Carla: 0.9.15
autoware_carla_interface: link

Possible causes
I guess this issue is from slope compensation, as the issue also occurs at hill, and is observed from the planning simulation too.
Additional context
No response

It looks like the slope where ego stops is too sharp (~0.12 rad) for the default configuration (0.1).
Please try increasing the parameter (e.g., to 0.2 since the map seems to contain slopes of up to 0.2 rad).
https://github.com/autowarefoundation/autoware_launch/blob/main/autoware_launch/config/control/trajectory_follower/longitudinal/pid.param.yaml#L80-L81

Thank you for the response @maxime-clem!!
I tried the planning simulation with your suggested parameter, and I found that the vehicle completes the driving well! Thanks a lot!
By the way, would you mind sharing the idea for the weird shape of the drivable area in z-axis?
In my opinion, the drivable area of uphill in the image above seems not being captured well.
Thank you!


RPC: Implement missing API endpoints

The basic setup for this is done. There's 1 method implemented (getconnectioncount). More could be implemented once the network and core package has more functionality.

@stevenjack could you list up what is already implemented in neo-go for the RPC server? A checklist would be awesome. <3

@anthdm They're all in the README https://github.com/CityOfZion/neo-go/tree/master/pkg/rpc 👍

Closing old issue in favor of rewrite suggested in #128


feat: add e2e runner

What this PR does / why we need it: This PR adds a E2E test runner for local dev and CI

JIRA ID: DT-494

Notes for your reviewer:

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


Fix python directory for python3.6 on mac os

Hi!
Some thing strange with working on Mac OS and Python3.6 (Anaconda). When deploy it fails with a bad python_dir path.
I am interested in continuing developing this plugin, please contact me if you need any help.

Hmm, that is strange. Why Python 2.7 does not work?

@iwitaly Thanks for the PR! I think this is just a matter of updating the tests, as you can see on Travis, both 2.7 and 3.6 is currently failing. Will you take a shot at updating the tests? Since this is mostly FS operations, the tests/fixtures are somewhat convoluted; any improvements are welcome.

@logandk I've never used Travis :) So I don't know how to update tests and how to run them.
I find some tutorial about it or if you have any, please send me.

@iwitaly No problem, it may be something interesting to learn about :) I don't have a good tutorial on hand, but the official py.test docs may be a good starting point: https://docs.pytest.org/en/latest/
If you install it, you can simply run pytest in the root of your repo clone and it will discover and run all the test cases.
We run tests on Travis using both Python 2.7 and 3.6, but your changes should be compatible with both versions

@iwitaly Your changes look good! Tests are passing, the remaining check that is currently failing is the linter (flake8), looks like some indentation is off. If you run pip install flake8 and then run flake8 in a shell at the repo root, it'll output any linter errors.

@logandk Great! I fixed trailing spaces with flake8 (to be honest, with PyCharm). Hope this will work.

Coverage decreased (-0.4%) to 97.101% when pulling 5391b604f237febc6b86d3708049800799c079fb on iwitaly:master into f36cc9e30ffa2272e1b891516d4765d7b4ffa1eb on logandk:master.

Perfect, I'll merge and publish a new version soon

Hi Logan,
Please merge my request, because a current state does not work with python3.6 (I tried on different machines).

@iwitaly Sorry about the delay!


Refactor effect inspection utils

Q
A

Fixed Issues?

Patch: Bug Fix?

Major: Breaking Change?
Yes. See below

Minor: New Feature?

Tests Added + Pass?

Any Dependency Changes?

API changes in this PR:

API asEffect is removed
API is.effect is added to test whether an object is an effect
effectTypes is exported by redux-saga/effects.

I refactor the saga-monitor-example and split it into several modules. During refactoring the sagaMonitor, I find that there is an internal ROOT type. ROOT effects are used by sagaMonitor to indicate that a root saga starts to run. So I add ROOT as an effect type.
Effects inspection utils in this PR are relatively simple and straightforward. Documentation for effects should be updated and tells users that Effect is an object that consists of a type, a payload and a internal symbol IO. So users could import is and effectTypes to test whether an effect is of an specific type like in checkers.
How to inspect the details of the effect payload is still an question. This PR already uses the knowing of payload structure to log effects in a better format. We need to come up with a better way to for users to access data in effect payload. Or maybe we can simply state in our doc: You can log the effects and see the payload structure for debugging purposes, but you should not rely on it since payload structure may change over versions.

By the way, saga-monitor remains the same style of logging output.

Thanks for reviewing. And I'm currently thinking about add another package @redux-saga/inpection that exports some utils to allow users to inspect the internals of effects.  @redux-saga/inpection is for debugging purposes and @redux-saga/core does not depend on it.
I'll update this PR after implementing the @redux-saga/inpection.

Could u rebase this PR?
I'm wondering if we need more inspection utils - they will only abstract simple object property access. I would be good with providing only is.effect + effectTypes. WDYT?

I'm wondering if we need more inspection utils - they will only abstract simple object property access. I would be good with providing only is.effect + effectTypes. WDYT?

Actually I think only is.effect + effectTypes is fine. And as the effect payload shape is stable, I'm inclining to let people inspect the payload directly for (and only for) debugging purposes (we may add some tips into our docs about what an effect looks like).

Rebased on master. And add manager.childIdsMap for bookkeeping a map from parent-id to child-id-array, also removes ROOT from effectTypes.js.

it's better to hoist this to the top level scope to avoid recreating this function inside each detach call

done.

rootSagaStarted hook added.


The window opens and closes quickly

Traceback (most recent call last):   File "C:\Users\Anike\OneDrive\Desktop\Lionrun\2023\CubeCrafter\main.py", line 149, in <module>     game = Game()   File "C:\Users\Anike\OneDrive\Desktop\Lionrun\2023\CubeCrafter\main.py", line 143, in __init__     self.window = Window(config = self.config, width = 800, height = 600, caption = "Minecraft clone", resizable = True, vsync = False)   File "C:\Users\Anike\OneDrive\Desktop\Lionrun\2023\CubeCrafter\main.py", line 25, in __init__     self.cobblestone = block_type.Block_type(self.texture_manager, "cobblestone", {"all": "cobblestone"})   File "C:\Users\Anike\OneDrive\Desktop\Lionrun\2023\CubeCrafter\block_type.py", line 12, in __init__     texture_manager.add_texture(texture)   File "C:\Users\Anike\OneDrive\Desktop\Lionrun\2023\CubeCrafter\texture_manager.py", line 40, in add_texture     gl.glTexImage3D(glglTexImage3dargument) TypeError: this function takes 10 arguments (1 given)

That code doesn't seem to be part of this Minecraft clone, sorry.


helm install throws authentication error with OCI artifacts

System Info
Output of helm version:
version.BuildInfo{Version:"v3.7.1", GitCommit:"1d11fcb5d3f3bf00dbe6fe31b8412839a96b3dc4", GitTreeState:"clean", GoVersion:"go1.16.9"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-29T02:41:56Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Azure (AKS / ACR)
Issue
Hi there, I've been playing with the new 3.7.* release of Helm to get our CICD working without the helm, chart subcommand.
I can publish OCI charts to Azure with no issues, but when I go to install using the aforementioned chart, an auth issue is thrown.
I was hoping you may be able to help me solve this, and suggest a workaround for the meantime, I note that helm chart save was removed, and could not figure out how to pull and export to a folder as a workaround with the new OCI changes
Thanks!
Repro
The steps I followed were as such:
# MS / Azure Docs on Auth
# https://docs.microsoft.com/en-us/azure/container-registry/container-registry-authentication?tabs=azure-cli#individual-login-with-azure-ad

# Authenticate with ACR
REGISTRY_NAME=<myregistryname>
$ az acr login --name ${REGISTRY_NAME}
Login Succeeded

# Grab a token for the registry
TOKEN=$(az acr login --name ${REGISTRY_NAME} --expose-token --output tsv --query accessToken)

# Login with Helm
helm registry login ${REGISTRY_NAME}.azurecr.io   --username "00000000-0000-0000-0000-000000000000" --password $TOKEN

# Package chart
# MS / Azure Docs on Packaging
# https://docs.microsoft.com/en-us/azure/container-registry/container-registry-helm-repos#create-a-sample-chart
$ helm package .
Successfully packaged chart and saved it to: /path/to/dir/helm-php/hero-php-0.2.1.tgz

# Push chart
$ time helm push hero-php-0.2.1.tgz oci://$REGISTRY_NAME.azurecr.io/helm
Pushed: ${REGISTRY_NAME}.azurecr.io/helm/hero-php:0.2.1
Digest: sha256:f1e7e343e084297290158dd0ebecc2449b3ea01679784ea7a00b8a162d6426e5

real    3m4.656s
user    0m0.801s
sys     0m0.057s

# Install chart
$ helm install hero-php-test oci://${REGISTRY_NAME}.azurecr.io/helm/hero-php --version 0.2.1 --namespace testing
Error: INSTALLATION FAILED: failed to download "oci://${REGISTRY_NAME}.azurecr.io/helm/hero-php" at version "0.2.1"

Pulling
Pulling seems to work, which is interesting:
$ helm pull oci://${REGISTRY_NAME}.azurecr.io/helm/hero-php --version 0.2.1
Pulled: linced.azurecr.io/helm/hero-php:0.2.1
Digest: sha256:f1e7e343e084297290158dd0ebecc2449b3ea01679784ea7a00b8a162d6426e5

Debug Logs
When running the final command with --debug I get the following output, apologies for the lack of brevity:
$ helm install hero-php-test oci://${REGISTRY_NAME}.azurecr.io/helm/hero-php --version 0.2.1 --namespace testing --debug
install.go:178: [debug] Original chart version: "0.2.1"
Error: INSTALLATION FAILED: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
helm.go:88: [debug] unexpected status: 401 Unauthorized
github.com/containerd/containerd/remotes/docker/auth.FetchToken
        github.com/containerd/containerd@v1.5.7/remotes/docker/auth/fetch.go:187
github.com/containerd/containerd/remotes/docker.(*authHandler).doBearerAuth
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:304
github.com/containerd/containerd/remotes/docker.(*authHandler).authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:228
github.com/containerd/containerd/remotes/docker.(*dockerAuthorizer).Authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:112
github.com/containerd/containerd/remotes/docker.(*request).authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:486
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:550
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:576
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:589
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
failed to fetch anonymous token
github.com/containerd/containerd/remotes/docker.(*authHandler).doBearerAuth
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:306
github.com/containerd/containerd/remotes/docker.(*authHandler).authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:228
github.com/containerd/containerd/remotes/docker.(*dockerAuthorizer).Authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/authorizer.go:112
github.com/containerd/containerd/remotes/docker.(*request).authorize
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:486
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:550
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:576
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:589
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
failed to authorize
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:551
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:576
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:589
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.7/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
INSTALLATION FAILED
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371

Have you had a chance to look at similar issues like https://github.com/helm/helm/issues/10181 and https://github.com/helm/helm/issues/10122?

Ah, apologies, my search through existing issues did not yield those issues, this is indeed a duplicate.
It seems as though the suggested fix of overriding the registry config has resolved the issue:
export HELM_REGISTRY_CONFIG=/home/<user>/.config/helm/registry.json

Thank you for pointing me to those threads :-)


Add jupyter notebook status file dir to excludes

Add .ipynb_checkpoints to .gitignore
If a notebook is used locally these files represent the state, but should not be checked into the build

This is working for me


feat(detector-aws): add sync version for all detectors

Which problem is this PR solving?
As suggested by @blumamir this PR aggregates the previous PRs to add sync detectors in the @opentelemetry/resource-detector-aws package. Previous PRs will be closed
Short description of the changes

add detectors for Beanstalk, EC2, ECS, EKS & Lambda complying with the DetectorSync interface.
add tests
make use of named exports

Error in hapi tests on node 18 due to a timeout :(
26 passing (2s)
  1 failing

  1) Hapi Instrumentation - Core Tests
       ESM
         should work with ESM modules:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/opentelemetry-js-contrib/opentelemetry-js-contrib/plugins/node/opentelemetry-instrumentation-hapi/test/hapi.test.ts)
      at listOnTimeout (node:internal/timers:569:17)
      at processTimers (node:internal/timers:512:7)


Update FontAwesome to 4.3

Hi again,
I've discovered that many icons I was using were missing because it was an old version.
Therefore, I've updated to 4.3.
I've taken this opportunity to include correct ids and titles (using their YAML file). I’ve also included the categories as classes as it can be useful to create subsets, or organize it in other ways. Inkscape ignores this.
Cheers

Works fine for me, thanks for the update :smiley:


Evaluate Removing Jackson Dependency

Evaluate removing Jackson fasterxml dependency and using the Google GSON library which is packaged as a GRPC dependency already.
This change would be to improve application performance, as Jackson is a fairly heavy-weight library that has reported performance issues on AWS Lambda.

Reduced function image size by 1.8 MB (9.12 MB total) and AppCDS by 6.6 MB (24.3 MB total)


Errors when testing on CPU

layer_name: <class 'torch.nn.modules.conv.Conv2d'>, total_params: 15121584, total_traina_params: 15121584, n_layers: 39
device:  cpu
Traceback (most recent call last):
  File "main.py", line 208, in <module>
    test(epoch)
  File "main.py", line 189, in test
    outputs = net(inputs)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/brcao/Repos/pytorch-cifar/models/dla_simple.py", line 106, in forward
    out = self.base(x)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/container.py", line 117, in forward
    input = module(input)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 423, in forward
    return self._conv_forward(input, self.weight)
  File "/home/brcao/Apps/anaconda3/envs/yolo/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 419, in _conv_forward
    return F.conv2d(input, weight, self.bias, self.stride,
RuntimeError: Expected object of device type cuda but got device type cpu for argument #1 'self' in call to _thnn_conv2d_forward

@bryanbocao Your device is not being set to the GPU. Can you make sure if your Cuda drivers are properly installed and all models and datasets are being sent to the GPU memory?

@Phillibob55 That's a different problem. The current issue is not about CUDA driver installation/configurations.
I can run it on GPU but I intentionally wanted to test the CPU runtime, which requires both the models and data to be in CPU memory instead of GPU.
The model is trained and saved on GPU memory. I've solved this issue by
parser.add_argument('--select_device', type=str, default='gpu', help='gpu | cpu')
...
device = 'cuda' if torch.cuda.is_available() and args.select_device == 'gpu' else 'cpu'
...
checkpoint = torch.load('./checkpoint/{}_ckpt.pth'.format(args.net), map_location=device)

@bryanbocao Your device is not being set to the GPU. Can you make sure if your Cuda drivers are properly installed and all models and datasets are being sent to the GPU memory?

@Phillibob55
Check this out
https://github.com/kuangliu/pytorch-cifar/pull/152

@Phillibob55 That's a different problem. The current issue is not about CUDA driver installation/configurations. I can run it on GPU but I intentionally wanted to test the CPU runtime, which requires both the models and data to be in CPU memory instead of GPU.
The model is trained and saved on GPU memory, need to add map_location=device argument when loading the model where device='cpu' in order to run the model on CPU. I've solved this issue by
parser.add_argument('--select_device', type=str, default='gpu', help='gpu | cpu')
...
device = 'cuda' if torch.cuda.is_available() and args.select_device == 'gpu' else 'cpu'
...
checkpoint = torch.load('./checkpoint/{}_ckpt.pth'.format(args.net), map_location=device)

@bryanbocao Your device is not being set to the GPU. Can you make sure if your Cuda drivers are properly installed and all models and datasets are being sent to the GPU memory?

ooh, yeah. Makes sense that way. OC seems to be inactive. So I'm working on my own version of this, which runs on any image dataset and doesn't have these problems, etc.

@bryanbocao Can you kinda guide to make these models work with image sizes other than 32x32?

@Phillibob55 I am happy to work on that.
Do you mean
(1) simply resize any arbitrary images into 32x32 resolution and feed them into these models? It can simply be done by adding one more argument in the command line and resize method in the code.
or
(2) prepare a set of models whose direct input shape is different from 32x32.

@bryanbocao
I started off with the first approach and just added a resize transform, but that loses a lot of information. For datasets like ImageNet, this doesn't give accuracy above 50%. So I was thinking maybe if I try to make the models accept images of any size, it might give me better results, taking more time training of course.
The codebase on the repo has a lot of hardcoded elements. I combated the 10 output classes by adding an argument for number of classes in every model class. But I don't have the knowledge to know what's going on in the complex models to modify them to be able to accept images of any size.

I've created a repo for it https://github.com/Phillibob55/image-classification

@bryanbocao I started off with the first approach and just added a resize transform, but that loses a lot of information. For datasets like ImageNet, this doesn't give accuracy above 50%. So I was thinking maybe if I try to make the models accept images of any size, it might give me better results, taking more time training of course.
The codebase on the repo has a lot of hardcoded elements. I combated the 10 output classes by adding an argument for number of classes in every model class. But I don't have the knowledge to know what's going on in the complex models to modify them to be able to accept images of any size.
P.S, I'm using a Jupyter notebook instead of my main.py

Sounds good. If you would like to create an easy-to-use repo that we can just change some arguments to train and test many different models, I am happy to contribute in my spare time. I have forked you repo to
https://github.com/bryanbocao/image-classification

@bryanbocao I started off with the first approach and just added a resize transform, but that loses a lot of information. For datasets like ImageNet, this doesn't give accuracy above 50%. So I was thinking maybe if I try to make the models accept images of any size, it might give me better results, taking more time training of course.
The codebase on the repo has a lot of hardcoded elements. I combated the 10 output classes by adding an argument for number of classes in every model class. But I don't have the knowledge to know what's going on in the complex models to modify them to be able to accept images of any size.
P.S, I'm using a Jupyter notebook instead of my main.py

@Phillibob55 Sounds good. If you would like to create an easy-to-use repo that we can just change some arguments to train and test many different models, I am happy to contribute in my spare time. I have forked you repo to
https://github.com/bryanbocao/image-classification

Hello, I would like to ask you what caused the following error after running, and how to deal with it：
D:\anaconda3\envs\datudui\python.exe C:/Users/52254/Desktop/pytorch-cifar-master/main.py
'stty' �����ڲ����ⲿ���Ҳ���ǿ����еĳ���
���������ļ���
Traceback (most recent call last):
File "C:/Users/52254/Desktop/pytorch-cifar-master/main.py", line 15, in
from utils import progress_bar
File "C:\Users\52254\Desktop\pytorch-cifar-master\utils.py", line 45, in
_, term_width = os.popen('stty size', 'r').read().split()
ValueError: not enough values to unpack (expected 2, got 0)

Hello, I would like to ask you what caused the following error after running, and how to deal with it：
D:\anaconda3\envs\datudui\python.exe C:/Users/52254/Desktop/pytorch-cifar-master/main.py 'stty' �����ڲ����ⲿ���Ҳ���ǿ����еĳ��� ���������ļ��� Traceback (most recent call last): File "C:/Users/52254/Desktop/pytorch-cifar-master/main.py", line 15, in from utils import progress_bar File "C:\Users\52254\Desktop\pytorch-cifar-master\utils.py", line 45, in _, term_width = os.popen('stty size', 'r').read().split() ValueError: not enough values to unpack (expected 2, got 0)

Hello, I would like to ask you what caused the following error after running, and how to deal with it：
D:\anaconda3\envs\datudui\python.exe C:/Users/52254/Desktop/pytorch-cifar-master/main.py 'stty' �����ڲ����ⲿ���Ҳ���ǿ����еĳ��� ���������ļ��� Traceback (most recent call last): File "C:/Users/52254/Desktop/pytorch-cifar-master/main.py", line 15, in from utils import progress_bar File "C:\Users\52254\Desktop\pytorch-cifar-master\utils.py", line 45, in _, term_width = os.popen('stty size', 'r').read().split() ValueError: not enough values to unpack (expected 2, got 0)

I have the same problem as you.


Creating a Graphical Password Authenticator using Django

Topic Suggestion
Creating a Graphical Password Authenticator using Django
Writing sample(s):
N/A
Proposal Submission
Proposed title of article
Creating a Graphical Password Authenticator using Django
Proposed article introduction
Today, millions of websites and applications compete to get you to subscribe or signup to their applications. To subscribe to their applications, you need a username and a password. To access your accounts, you need to authenticate using a password and a username. While passwords are the industry's standard for accessing your accounts on software applications, they are often easy to forget due to the numerous accounts you have.
This is why some authentication methods like graphical passwords came up. This is where a user selects a variety of images in a specific pattern only known to them. These images and the pattern in which the user chose them is what will be used when the user tries to log into his/her accounts.
In this tutorial, we will be implementing this method of authentication using Django, a Python web development framework.
Key takeaways
At the end of this tutorial, the reader should be able to:

Understand the basics of security in an application
Understanding the process of authentication
Understanding and implementing projects using Django

Article quality
This is an in-depth tutorial that covers not only the basics about authentication, but also it's implementation using Django.
References
N/A

Hello @omoshII, this seems to be a helpful article. It is approved. Just one note, make sure you create a unique project - different from the ones available online.

Just wanted to follow up on this topic, as we will be clearing up the queue where possible.
Just and FYI I will be closing this topic form just to help clear up the queue where possible - can be REOPENED at anytime when ready. 👍


kkmihai.is-cool.dev Takedown

For the attention of @kkMihai
Dear kkmihai.is-cool.dev Owner,
We are writing to inform you that our team has detected potential hacking and/or keygen activities associated with your domain. As a result, we regret to inform you that we will be terminating your domain, kkmihai.is-cool.dev, effective April 1st, 2023 if no immediate action is taken.
We take any suspicious activity on our platform very seriously, and we have a responsibility to our users to ensure their safety and security. Therefore, we urge you to take prompt action to address any potential security vulnerabilities associated with your domain. If you need assistance with identifying and mitigating these vulnerabilities, please do not hesitate to contact our support team.
We understand that this may be an inconvenience for you, but we must prioritize the safety and security of our platform and our users. If you believe that this termination was made in error, please contact our support team immediately to discuss the matter further.
In order to prevent similar incidents in the future, we encourage you to review and comply with our terms of service, which can be found here: https://github.com/open-domains/register/blob/main/terms.md
We hope that you will take this matter seriously and take immediate action to address any potential security risks associated with your domain. We appreciate your attention to this matter and apologize for any inconvenience that this may cause.
Sincerely,
Open Domains

I believe we should take the domain down.

where is "potential hacking and/or keygen activities associated with your domain." ?
because i dont see any, can you be more explicit?

Update: website modified there is no more any links associated with "potential hacking and/or keygen activities"


[optimization] Dynamic training optimization v2

Added dynamic training v2 final code
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [x]Passed [ ]Failed [ ]Skipped

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #922. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/922-202102011702100.1174430847168-d60669d2b3fd959f3791e39c6bdaff87577940df/.


captchaai.io changed to capsolver.com

A brief description of the problem.
hey, captchaai changed to capsolver

Hi
Yep, main API url already changed: https://github.com/AndreiDrang/python3-captchaai/blob/55590d0c411f8dacea9400f8ddee34e1f3dfc143/src/python3_captchaai/core/config.py#L9
Library name will be changed bit later - after adding last 2 captcha methods.
Thanks.


Data Split

It seems that your data split is different from OmniDepth and BiFuse.
How do you decide to use this split?

Thanks.

We use the same split of OmniDepth and BiFuse, which is obtained from the datasets.


Remove spurious toolchain deps

JavaCC never needed a specific version of java. So we should remove things like toolchain and cobertura from deps so anyone can just build it.
CC: @MarcMazas

If needed we can set source and class file versions in the javac options. But requiring specific runtime should never happen for javacc.

Well:

we introduced toolchains with Francis when I started maintenance; it is a solution for the maven builds (see further), it is not something that javacc itself is dependent on; we had not checked that one could build a full new release or just a new added test case without having configured a toolchain; if this is your case, I'll try to find a way to make the maven build work with (appropriate) java & maven settings.

the cobertura warning appears when you use a jdk > 8, because of a presumably badly built (our org.javacc.plugin.javacc-maven-plugin, which declares this dependency, that it should not); I'll fix this when I'll make a laundry pass on this plugin.

So let's discuss about the different subjects:

java source file version levels in the java part of the user grammars
java source & class file version levels for the generated users parsers
jvm & jdk version levels for running the generated users parsers
jdk version levels for the command line, the ant scripts and the maven plugins (and may be gradle plugins) for building new javacc releases

For 1, it would be nice to allow to use up to the last java version (i.e. 22 today), but this implies either to have a java grammar up to date (currently javacc7 does not support even full java 1.7 - I have a java 1.8 version, which I have not published, reserving it to javacc-8), or have a javacc grammar that does not parse java parts and see them as black boxes (which we do not have).
For 2, I think that sooner or later we shall have to allow to generate parsers complying with jdk > 8 features, like modules..., or taking advantage of improvements of jdk > 8 features, like templates, performance related features...; I don't know if we'll have the resources for developping / maintaining code generators that will generate different code for different java target version levels; for the moment it would be nice to check that we allow to use custom templates customized to any source file version level up to the last java version.
For 3, the user should be able to use a jvm & jdk version level compatible with its generated parser; and I'm 100% ok for embedding no third party (dependent) library in the generated parser.
For 4, only the javac maintainers and contributors are concerned, not all the end users. That people have a large set of development environments and habits: no IDE / Eclipse / IntelliJ / ...,, many different JDK installed and JAVA_HOME may be pointing to anyone of them, many maven versions installed and MAVEN_HOME/M2_HOME pointing to anyone of them, all this because they work on different projects, they build (with ant or maven) inside or outside their IDE...
That's why we choosed to use the toolchains mechanism, which avoids the user to have to change its JAVA_HOME / MAVEN_HOME for each project and avoids nightmares to configure each plugin. As said above, I'll try to find a way to rely on these environment variables if toolchain is not configured.
Also it appeared, when upgrading the poms plugins to their last versions for javacc-8, that some require a JVM > 1.8 to run them, that's why I set it to 11. But the (generated) javacc binary should require JDK 1.8, not 11. I have to check.
So note that if you do not configure toolchains and set JAVA_HOME to JDK 1.8 and that you use a maven plugin that requires JDK 11, your build will fail. So a question is: can you afford to use JDK 11 for building a new javacc snapshot/release (while keeping the generated parser to source & class files versions levels to 1.8?

With javacc 8 we do not need any of those! We just need to keep the source level and generate source that's compatible with that. All other stuff is upto users. So let's not spend time anything else. Just get rid of the corbetura dep and we are good.

From: Marc MAZAS @.>
Sent: Friday, August 23, 2024 3:00 AM
To: javacc/javacc @.>
Cc: Sreeni Viswanadha @.>; Author @.>
Subject: Re: [javacc/javacc] Remove spurious toolchain deps (Issue #290)
Well: we introduced toolchains with Francis when I started maintenance; it is a solution for the maven builds (see further), it is not something that javacc itself is dependent on; we had not checked that one could build a full new release or
Well:

we introduced toolchains with Francis when I started maintenance; it is a solution for the maven builds (see further), it is not something that javacc itself is dependent on; we had not checked that one could build a full new release or just a new added test case without having configured a toolchain; if this is your case, I'll try to find a way to make the maven build work with (appropriate) java & maven settings.

the cobertura warning appears when you use a jdk > 8, because of a presumably badly built (our org.javacc.plugin.javacc-maven-plugin, which declares this dependency, that it should not); I'll fix this when I'll make a laundry pass on this plugin.

So let's discuss about the different subjects:

java source file version levels in the java part of the user grammars
java source & class file version levels for the generated users parsers
jvm & jdk version levels for running the generated users parsers
jdk version levels for the command line, the ant scripts and the maven plugins (and may be gradle plugins) for building new javacc releases

For 1, it would be nice to allow to use up to the last java version (i.e. 22 today), but this implies either to have a java grammar up to date (currently javacc7 does not support even full java 1.7 - I have a java 1.8 version, which I have not published, reserving it to javacc-8), or have a javacc grammar that does not parse java parts and see them as black boxes (which we do not have).
For 2, I think that sooner or later we shall have to allow to generate parsers complying with jdk > 8 features, like modules..., or taking advantage of improvements of jdk > 8 features, like templates, performance related features...; I don't know if we'll have the resources for developping / maintaining code generators that will generate different code for different java target version levels; for the moment it would be nice to check that we allow to use custom templates customized to any source file version level up to the last java version.
For 3, the user should be able to use a jvm & jdk version level compatible with its generated parser; and I'm 100% ok for embedding no third party (dependent) library in the generated parser.
For 4, only the javac maintainers and contributors are concerned, not all the end users. That people have a large set of development environments and habits: no IDE / Eclipse / IntelliJ / ...,, many different JDK installed and JAVA_HOME may be pointing to anyone of them, many maven versions installed and MAVEN_HOME/M2_HOME pointing to anyone of them, all this because they work on different projects, they build (with ant or maven) inside or outside their IDE...
That's why we choosed to use the toolchains mechanism, which avoids the user to have to change its JAVA_HOME / MAVEN_HOME for each project and avoids nightmares to configure each plugin. As said above, I'll try to find a way to rely on these environment variables if toolchain is not configured.
Also it appeared, when upgrading the poms plugins to their last versions for javacc-8, that some require a JVM > 1.8 to run them, that's why I set it to 11. But the (generated) javacc binary should require JDK 1.8, not 11. I have to check.
So note that if you do not configure toolchains and set JAVA_HOME to JDK 1.8 and that you use a maven plugin that requires JDK 11, your build will fail. So a question is: can you afford to use JDK 11 for building a new javacc snapshot/release (while keeping the generated parser to source & class files versions levels to 1.8?
—
Reply to this email directly, view it on GitHubhttps://github.com/javacc/javacc/issues/290#issuecomment-2306742358, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPNYANGTYEUESOVBIMVHQ3ZS4B27AVCNFSM6AAAAABM6LBLJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBWG42DEMZVHA.
You are receiving this because you authored the thread.Message ID: @.***>

I meant to say we should completely stop processing the user actions with javacc 8 they will get compiler error later if they have problems in their actions. We can leave some breadcrumbs in the code for ease of locating errors back to grammar

Commit 7f6d982c0b5e8d299bc280cee8c03be3f002ad24 removed the cobertura plugin and moved the toolchains plugin in a profile.


Override TestClient.__enter__() to support downstream typing.

types our TestClient such that it should support subclassing downstream.
remove redundant casts and ignores from our own source.

Closes #182

For #182

Don't merge yet pls, I've pushed in some changes from my tox branch I need to clean up.

Sure, I don't merge your PRs

Sure, I don't merge your PRs

Thanks


Small typo fix for "pareto/ndb" -> "pareto/nbd"

hm, test failures are unrelated.
Thanks for the quick change!


feat: Automatic Quick Selling after successful buy

Prerequisites

[X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request
If I buy something cheaper than the quick selling price, I would like to quick sell it automatically after I have bought the item successfully
Describe the Use Case
If I buy something cheaper than the quick selling price, I would like to quick sell it automatically after I have bought the item successfully
Describe Preferred Solution
Create a Checkbox with the specific option.
Describe Alternatives
No response
Additional Information
No response

Added in the latest version


Update sp.json

Added "two letter" short names to some books

Hi @tim-hub
I added some short names on a common format on spanish ("two letter" short names), and tryed to merge, but I obtained an error, please could you check it ?

It complains the duplication, break the unique constraint

test failed because of book Job

ok.. fixed and updated

closed this, https://github.com/AntiochTechnology/bible-reference-toolkit/pull/12


Record System Audio

It would be really great if Kap could record system audio without having to install Soundflower. Is it on the roadmap?!

Duplicate of #145.


Autoform and Relations using Transform - Update form not working

I use transform to have a reference between Stores and StoreTypes.
Stores = new Mongo.Collection('stores', {
  transform: function(doc) {
    doc.storetypesObj = StoreTypes.find({
      _id: { $in: doc.types }
    });

    return doc;
  }
});

and in my StoreTypes collection I use:
StoreTypes = new Mongo.Collection('storetypes', {
  transform: function(doc) {
    doc.storesObj = Stores.find({
      types: { $in: [ doc._id ] }
    });
    return doc;
  }
});

However this transform makes it impossible to update my Store using an update form like this:
{{> quickForm collection="Stores" id=updateStoreId type="update" doc=this}}
This will following exception:
Exception from Tracker recompute function:
meteor.js:880 RangeError: Maximum call stack size exceeded
    at Object.EJSON.clone (ejson.js:490)
    at ejson.js:529
    at Function._.each._.forEach (underscore.js:157)
    at Object.EJSON.clone (ejson.js:528)
    at ejson.js:529
    at Function._.each._.forEach (underscore.js:157)
    at Object.EJSON.clone (ejson.js:528)
    at ejson.js:529
    at Function._.each._.forEach (underscore.js:157)
    at Object.EJSON.clone (ejson.js:528)

If I remove the transform I am no longer able to display the properties of my referenced StoreTypes, but am able to update, so it definitely has to do with the transform function.
Insert forms work. Only Update forms a problem.
(If anyone knows a workaround for this those are definitely welcome too :+1: )

@aldeed Could you help me out with this? :)

Would putting a guard in front of the find logic help? For example,
StoreTypes = new Mongo.Collection('storetypes', {
  transform: function(doc) {
    doc.storesObj = doc.storesObj || Stores.find({
      types: { $in: [ doc._id ] }
    });
    return doc;
  }
});


Validation Error logo_URIs

I am trying to add API/RPC for Fetch and Stride chain.json but Stride chain.json is failing validation with following error.
{'path': 'stride/chain.json', 'errors': [<ValidationError: "Additional properties are not allowed ('logo_URIs' was unexpected)">]}
I see "logo_URIs" in definition but not in properties. Is this a problem with schema? See PR #1174 for error.

Apologies, and thanks for pointing this out. 'logo_URIs' and 'keywords' were supposed to be under properties--not $defs. Working on a fix. Should be able to reopen your PR.


Added Github star and adjusted Enter URL text

Added Github star and adjusted Enter URL text
Issue no. #19
Does this look fine?

Thanks for that feature


Unable to do basic web integration, request for example

Hello!
I've been trying to integrate this with the web template for botkit. I couldn't find any examples for it, there are only examples for facebook and slack.
Just to get it to work, my current basic code involves just bot.js and not the features directory.
Please take a look as this doesn't seem to work!  More examples for web integration would also be a blessing.
const { Botkit } = require('botkit');
const { BotkitCMSHelper } = require('botkit-plugin-cms');
//Import dialogflow middleware
const dialogflowMiddleware = require('botkit-middleware-dialogflow')({
    keyFilename: 'keys/testaction-service-key.json',  // service account private key file from Google Cloud Console
});

// Import a platform-specific adapter for web.

const { WebAdapter } = require('botbuilder-adapter-web');

const { MongoDbStorage } = require('botbuilder-storage-mongodb');

const path = require('path');
// Load process.env values from .env file
require('dotenv').config();

let storage = null;
if (process.env.MONGO_URI) {
    storage = mongoStorage = new MongoDbStorage({
        url: process.env.MONGO_URI,
    });
}
const adapter = new WebAdapter({});

const controller = new Botkit({
    debug: true,
    webhook_uri: '/api/messages',
    adapter: adapter,
    storage
});

// if (process.env.cms_uri) {
//     controller.usePlugin(new BotkitCMSHelper({
//         cms_uri: process.env.cms_uri,
//         token: process.env.cms_token,
//     }));
// }

controller.middleware.receive.use(dialogflowMiddleware.receive);

controller.hears(['Default Welcome Intent'], 'message,direct_message,message_received', dialogflowMiddleware.hears, function (bot, message) {
    replyText = message.fulfillment.text;  // message object has new fields added by Dialogflow
    console.log(replyText, typeof replyText);
    bot.reply(message, replyText);
});
// make public/index.html available as localhost/index.html
// by making the /public folder a static/public asset
controller.publicFolder('/', path.join(__dirname,'.','public'));
console.log('Chat with me: http://localhost:' + (process.env.PORT || 3000));

Provided code uses Botkit 4, this middleware hasn't been updated to support it yet.

ok, thanks! any plans to support it?

No confirmed timing, but I will have a look at it.


 Let's ignore all exceptions from killing a process if it has exited.
Additionally, ArgumentException is the wrong exception to catch. I have never seen Process.Kill() throw that. It seems to be a bad copy and paste from line 50.

Agreed, it's reasonable


How do I import Gazebo world.file(Not a URDF) in to Unity?

Hi all,
I am trying to import the following robot and its environment into Unity.

However, I've noticed in this ROS package. Only the robot hand and robot are in URDF file. The whole environment is a world.file of Gazebo.
model.urdf
model_hand.urdf
smart_grasping_mod.world

Anyone knows how to import a world.file of Gazebo into Unity? If not, is it doable that I convert a world file into URDF then import it into Unity? Thanks.

That's part of the world file.

Hello,
to convert a SDF to a URDF file, you might want to take a look at this repo.
A tutorial on how to use it with a robot model can be found here.
Best,
Verena

I'm not aware of a world / SDF -> Unity importer.
In fact we discussed about adding one to ROS# in this issue: #35
We decided against it, as this file format is very Gazebo-specific.
So, in accordance to @roehrlverena 's answer above, I'd also suggest to get URDF files out of the <model> sections in the world/SDF file first and then use the exisiting URDF importer.
Is there data, in the SDF that you would like to have imported in Unity, beside that in the <model> tags?
Please do keep us informed on the progress you make.

Hi @stevensu1838 any update on your sdf model import?
How did you proceed?


Why is Rotation measured "clockwise from midnight"?

@alice-i-cecile While experimenting with #151 I noticed that Rotation is measured "clockwise from midnight". Is this an intentional decision? Does it need to be this way?
It would be much more convenient to interact with standard f32 math as well as things like rapier2d if Rotation were measured counter-clockwise from the positive X axis (or "counter-clockwise from 3 o'clock" to put it in the same terms).
Currently, any angle returned by Rotation::to_radians needs some extra calculations to get the radians value you need for any standard f32 math. For example, I'm trying to determine the angle that a player is attempting to fly in 2D space via the axis returned by a gampad stick. Right now, after I get a value from the input manager, I've got to flip the rotation and shift the rotation origin.
From looking over the implementation of Rotation, it seems like switching to the same measurement system as the rest of mathematics would be fairly straightforward. For example, the order of the first two arguments in this line would go back to the standard y first and then x, and we could stop flipping the sign in some places to restore the counter-clockwise rotation, and use the unit X vector instead of the unit Y vector to measure from the positive X axis.
Is this a change you would be open to? I don't want to make a PR to change this if it needs to be kept this way for some reason I don't know.

This was totally arbitrary. I tend to find it a bit easier to reason about, but have no strong feelings.
I would accept that PR if you made it; the interop argument is reasonable.


When e.target is bigger than viewport...

So I have an element target which is bigger than viewport size,
and
viewHandler(e) fires exit from element before it actually leaves the viewport
here is the printscreen of console.log

I think this is because element is bigger and then something trippy happens to percent in view

Its not a big issue but I think its worth fixing and making this plugin SUPERAWESOME!
Anyway thanks for even making this, it really saved me the time

I am facing the same issue when an element is bigger than the viewport. It also happens with "e.percentTop". Basically it dose not indicates when you are in the middle of an element. It would be nice if you can implement this little feature as well.

Anyway, thank you very much for the great package. Good work!

Yeah this is currently causing me woes too – I really need it to work for longer elements, as my use-case is tracking scroll position down a series of text elements for a navigation which highlights those currently on the screen.

For what it’s worth, this workaround worked for me:
    viewHandler(e, section) {
      if (e.percentTop >= 0 && e.percentTop <= 1) {
        this.visibleSections.push(section);
      } else {
        this.visibleSections = this.visibleSections.filter(item => item._key !== section._key);
      }
    }


Making docs link to application-commands instead of slash-commands

About this pull request
Description of the pr
Replaced links i could find that redirected to https://discord.com/developers/docs/interactions/slash-commands which has been moved over to https://discord.com/developers/docs/interactions/application-commands
Changes
What changes were made?
Replaced 4 links
Checklist

[ ] I've run the pre_push.py script to format and lint code.
[ ] I've checked this pull request runs on Python 3.6.X.
[ ] This fixes something in Issues.

Issue:

[ ] This adds something new.
[ ] There is/are breaking change(s).
[x] (If required) Relevant documentation has been updated/added.
[x] This is not a code change. (README, docs, etc.)

Many of the docstrings on the code itself also link to the old slash-commands link. Eg.: on discord_slash.utils.manage_commands.get_guild_command_permissions

👋🏼 LMK when you're ready for me to review this since I see two PRs involved with fixing docstrings and the RTD.

hey @goverfl0w think the replacement is complete now so i assume it should be good now


Availability of createUseQueryOptions and createUseInfiniteQueryOptions in v1

Is the absence of createUseQueryOptions and createUseInfiniteQueryOptions in v1 intentional? These methods appear to be extremely important when React context is not available.
https://github.com/connectrpc/connect-query-es/blob/main/packages/connect-query/src/index.ts#L19-L24
The README mentions createUseQueryOptions:

What if I have a custom Transport?
If the Transport attached to React Context via the TransportProvider isn't working for you, then you can override transport at every level. For example, you can pass a custom transport directly to the lowest-level API like useQuery or createUseQueryOptions.
Does this only work with React?
Connect-Query does require React, but the core (createUseQueryOptions) is not React specific so splitting off a connect-solid-query is possible.

(README Link: https://github.com/connectrpc/connect-query-es?tab=readme-ov-file#does-this-only-work-with-react)
Is there an alternative method now, or was their removal unintentional? If it's an unintentional, I'm willing to help with a PR.

This was an intentional change to reduce the API surface and create a more focused API. That said, I would be open to exposing these APIs again given a specific use case that can't be served otherwise.

We did expose a helper, callUnaryMethod which can often be used similarly, just without being specific to infiniteQuery or query

I guess I also forgot to mention createConnectQueryKey(), which provides the queryKey.

Thank you for your response. I understand now that it was an intentional change. First, we will try using callUnaryMethod in our product and see if there are any issues. For now, I will close this issue and if anything comes up, we will create a new one!

I think it would be nice if these were exposed. They are useful for building custom hooks but also for some APIs such as queryClient.ensureQueryData
    await queryClient.ensureQueryData(
      createUseQueryOptions(
        rpc,
        {
           input
        },
        {
          transport,
        }
      )
    );

While I could implement this with the unary helpers it ends up being the same code over and over again and the code is basically a copy paste of the internal API.

In our codebase, this kind of pattern arose too, but we ended up going down the path of a custom QueryClient, which provided typesafe variants of the APIs, so invalidateQueries became invalidateConnectQueries with appropriate args. Ditto with setConnectQueryData. It's still a little early within our codebase to publish it, but I personally think it provides a better DX and could even eliminate the need (but keep an option for) the transport.
Obviously one does not negate the other but in the spirit of reducing the number of ways to do things, the custom client feels more directed and adds more value than just removing helper code.
If that would be of interest to you, I can open a tracking issue for that work and we can get a little feedback from the ecosystem in a slightly more visible way.

I'm in the situation that I want to call "context.queryClient.ensureQueryData" (in Tanstack Router's loader as described here https://tanstack.com/router/latest/docs/framework/react/guide/external-data-loading#a-more-realistic-example-using-tanstack-query) But I'm a bit confused as to what the recommendation is right now?
Do I extend the query client? But I'm not sure how to do this, is there an example? I've tried to copy the createUseQueryOptions from the codebase but it is quite a lot it seems, or maybe 'm doing it wrong as well?
Imo it's probably pretty common to use Tanstack query in router data "loaders" where the react context is not available.

So the way we are creating our own custom query client is like so:
import { QueryClient as TSQueryClient } from "@tanstack/react-query";
import {
  callUnaryMethod,
  createConnectQueryKey,
  defaultOptions,
  DisableQuery,
  disableQuery,
  TransportProvider,
  useInfiniteQuery,
  useMutation,
  createProtobufSafeUpdater,
  useTransport,
  ConnectQueryKey
} from "@connectrpc/connect-query";
import { CallOptions, ConnectError, Transport } from "@connectrpc/connect";
import {
  AnyMessage,
  Message,
  MethodInfoUnary,
  PartialMessage,
  ServiceType,
} from "@bufbuild/protobuf";

export class QueryClient extends TSQueryClient {
  invalidateConnectQueries<I extends Message<I>, O extends Message<O>>(
    methodSig: MethodSignature<I, O>,
    input?: PartialMessage<I>,
    options?: InvalidateOptions
  ) {
    return this.invalidateQueries(
      {
        queryKey: createConnectQueryKey(methodSig, input),
      },
      options
    );
  }

  setConnectQueryData<I extends Message<I>, O extends Message<O>>(
    methodSig: MethodSignature<I, O>,
    updater: ConnectUpdater<O>,
    input?: typeof disableQuery | PartialMessage<I> | undefined,
    options?: SetDataOptions | undefined
  ) {
    return this.setQueryData(
      createConnectQueryKey(methodSig, input),
      createProtobufSafeUpdater(methodSig, updater),
      options
    );
  }
}

As for the eslint rule @tanstack/query/exhaustive-deps, it's a valid point. Currently we don't use the transport as part of the key, which means that if the transport changes then related data doesn't auto fetch again. Not actually sure how we'd want to solve that one, since the transport itself can't really be serialized into a string (it's a set of functions) and thus cannot be a part of the query key.

Ah right, the query client is just a class. That make sense, thank you

For the cache key not including the transport. Am I correct that it only means that the cache key might overlap if a project uses different transports with the same method signatures in the same project?

Yes, that is correct. I'm not sure how realistic that scenario is, but it is possible.

Fixed in https://github.com/connectrpc/connect-query-es/releases/tag/v1.3.0


Add OpenBSD specific build targets

-Wl,-s,defs causing linkage issue stumbled accross somewhat
similar issues as #11043.

"somewhat similar", although I assume you got issues building engines.  This PR is a "quick fix", but it drops our attempt to make engines and other DSOs self-contained.  I would very much like to see a log of what went wrong before accepting this fix, it's quite possible that you have uncovered a build issue that should be addressed in a different (better?) manner.

"somewhat similar", although I assume you got issues building engines. This PR is a "quick fix", but it drops our attempt to make engines and other DSOs self-contained. I would very much like to see a log of what went wrong before accepting this fix, it's quite possible that you have uncovered a build issue that should be addressed in a different (better?) manner.

I get pipe, close, write ... as undefined on OpenBSD, it seems this linker flag is broken in this platform.

I get pipe, close, write ... as undefined on OpenBSD, it seems this linker flag is broken in this platform.

???!!!
Wow...  yeahok, if it's at that level, I can't see a better solution.

Is this for 1.1.1 or master or both?

Well master for now I might say.

Well master for now I might say.

Thanks

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

What linker is OpenBSD using?
I am worried that this might introduce regressions for other BSDs (e.g., FreeBSD).

The LLVM's

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

I get pipe, close, write ... as undefined on OpenBSD, it seems this linker flag is broken in this platform.

Interesting!  The "undefined symbol" does seem to match up with #11043 (though I would always prefer to see the actual diagnostic output that you are seeing), but does not match what I've been able to see so far on FreeBSD.
Since the sanitizers are implicated in the (non-)inclusion of -z defs that are affected by this proposed change, I tried building on FreeBSD configured with and without enable-asan.  The normal build went fine, but the enable-asan build dies trying to link fuzz/client-test, complaining about a duplicate symbol (time), defined both in /usr/lib/clang/11.0.0/lib/freebsd/libclang_rt.asan-x86_64.a and fuzz/client.c:38 .  Most interestingly, defs does not appear in either build log!

Maybe, since it affects all BSD, the solution is to close it and allows OpenBSD to locally patch their OpenSSL port.

Maybe, since it affects all BSD, the solution is to close it and allows OpenBSD to locally patch their OpenSSL port.

I don't think we need to resort to that quite yet.  For one, my testing so far has just been on unpatched openssl sources -- I should also try it after applying this PR (or you could, if you're in a position to do so faster than me).

same outcome with this PR.

Interesting! The "undefined symbol" does seem to match up with #11043 (though I would always prefer to see the actual diagnostic output that you are seeing), but does not match what I've been able to see so far on FreeBSD.

Oops, it seems that my initial testing was accidentally based on a 1.1.1 tree and not the master-based tree I thought I was using.  I will need to run them again...

Okay, my test results make more sense now that I am testing what I think I am testing :smile:
I would still very much like to see the build log for the actual failures that this change is fixing; the stuff linked in #11043 is different enough that it's hard to draw many conclusions from it.
Assuming that seeing the build log doesn't bring further enlightenment, I'm inclined to think that the "right thing to do" is to split off a dedicated openbsd configuration stanza to override the dso_ldflags and teach our config how to guess it as the target to pass to Configure.

`
ld: error: undefined symbol: strcmp

referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(bind_engine)

ld: error: undefined symbol: write

referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(dummy_pause_job)

ld: error: undefined symbol: read

referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(dummy_pause_job)

ld: error: undefined symbol: pipe

referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(dummy_pause_job)

ld: error: undefined symbol: close

referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(dummy_pause_job)
referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(dummy_pause_job)
referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(wait_cleanup)
referenced by e_dasync.c
engines/dasync-dso-e_dasync.o:(wait_cleanup)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:23348: engines/dasync.so] Error 1
gmake: *** [Makefile:3206: build_sw] Error 2
`

Indeed a specific setting for OpenBSD might fit better I ll try to come up with something within this weekend

Could we also see the linker invocation?

This got updated and needs a new review

This got updated and needs a new review

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 92 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 123 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 154 days ago

Given this is something that would be under the current rules acceptable even to 1.1.1, can it be merged into 3.0?

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

so long :-) I almost forgot this one

OTC: This is too late for 3.0.0, but would be ok for 3.0.1

This was somehow lost.

Could you please rebase it against fresh master branch checkout?

This PR is in a state where it requires action by @openssl/committers but the last update was 31 days ago

This pull request is ready to merge

Merged to master. Thank you.


Implement BCV Control Design using MUI

User Story
As a developer, I want to choose a UI toolkit to use forever so we can standardize designs with a system so that we can implement UI designs as efficiently as possible.
As a translator or advisor, I want to navigate to different texts and to different books, chapters, and verses within a text. I want to be able to sync navigation across multiple views and tools.
Description
UI Toolkits Bakeoff Contestant # 3, our defending champion, MUI. Implement the BCV control design in the toolkit, doing all you reasonably can to match the design, particularly in appearance so we can get a good feel of how easy the components are to customize.

UI Toolkit Research background doc
Figma Design
UX created sandbox

Code Style Thoughts from Sebastian

Create little components (e.g. for the book name list entry)

Results
Note your thoughts about the usability of the toolkit in Toolkit Evaluation
Be ready to demo BCV at the sprint demo planning meeting.

This issue was not needed in the end to determine which UI toolkit to go with.


Missing zsh completion for home-manager itself

The tab-completion works on bash, but doesn't work on zsh.
It simply suggests files in CWD (the default completion).

If it's useful to anyone, I wrote my own here a while ago.

@Sean1708
Seems great. Would you mind sending an PR here?

I'm not really sure how I'd go about testing that the installation works properly without creating an entirely new user account, but feel free to take the code and submit the PR yourself or you can use my method of doing it until somebody more knowledgeable about testing HM itself comes along.


Watch support for zookeeper

Why is the watch option not supported for zookeeper ?
Since you can subscribe to a node and get pushed as soon as there's a change.
Maybe it's just not implemented yet ?

You are correct. It wasn't implemented when PR'd by a community member.

watch option is not supported because zookeeper doesn't handle recursive watch. It's a little bit tricky to implement the watch behaviour you surely expect.

Is anyone working on this? What's the expected behavior?

I plan  switching from "native" zookeeper client.go to docker/libkv

Cool let me know how this goes. How does this work without watch? I ran confd as a daemon and it never re-rendered templates until I restarted it. In the end I wound up just running it as a cron.

should work now: #405


OSX radios are being clipped in chromium browsers

Chromium browsers clip radio buttons one pixel on the left and bottom if a parent has overflow:hidden. This is an open issue with chromium but over a year old. It was brought up in bootstrap but I thought it should be decided on within normalize since it isn't exclusive there.

Radios and checkbox inside container with overflow:hidden

This also can be seen when radios are naturally against the edge of page.

Demo
This would establish a consistency across all operating systems and browsers.

Doesnt happen to me, maybe. Chrome 44.0.2403.61 beta on lubuntu 14.04. From your demo:

Per http://crbug.com/396726#c1 , only Mac OS X is affected by this.

@walutisme This is an OSX only issue as stated in the title. Windows and Linux are fine.

I’ve recently started addressing issues here, so forgive me for the delay. I’d like to wait till there is a fix, since the fix involves very opinionated defaults on how radio buttons should align. @josephfusco, thoughts or new info?

@jonathantneal I have changed my stance on this and agree that it is too opinionated for inclusion in normalize. Since this is a known chromium bug (although the ticket is approaching 2 years old), developers can simply apply the 1px shift of the radio input by means of margin, padding, or positioning on the affected side of the element.

Filed a WebKit bug since this affects Safari too: https://bugs.webkit.org/show_bug.cgi?id=155577


Parse lua filters in filters argument

Small change to correctly parse lua filters passed to the filters argument.

I've added some tests to check that filter ordering is preserved!


Add integration test for npm install build

I've also verified this fails on the 0.1.8 version of the asset relocator loader.
Resolves #308.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a2ea9b4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #310   +/-   ##
=========================================
  Coverage          ?   68.37%
=========================================
  Files             ?       12
  Lines             ?      370
  Branches          ?        0
=========================================
  Hits              ?      253
  Misses            ?      117
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a2ea9b4...2161d9e. Read the comment docs.


[sdl2pp] Fix SDL_pixels.h cannot be found

When using, SDL_pixels.h cannot be found in project.
Since in SDL2pp/Color.hh file, it included <SDL_pixels.h> instead of <SDL2/SDL_pixels.h>.
Fix #12041
Note: No feature needs to test.

/azp run

Closing this PR since there is no need to fix it in msvc project, just adding the include path manually in the project.


Scheduled callbacks which depend on ISystemClock

There's an interesting edge case in this design, where a scheduled callback can itself depend on the time moving forward.
For example, if a unit test moves the clock forward (AdvanceBy), triggering a timer callback, and that callback does a FluxTime.Sleep.
One workaround would be to just queue the scheduled callbacks to the thread pool, and ignore their completion. But this could conceivably cause problems if callbacks are dependent on each other. E.g., callback1 sets a value, callback2 gets the value. Also, this would introduce race conditions when callbacks schedule callbacks.
A better solution might be to have an async version of AdvanceBy, where all callbacks are async. This wouldn't work if the callbacks do sync-over-async, though.
We might need to detect recursion (hiding the internal IScheduler completely) and do nested callback pumping. But even then, a scheduled loop with SystemClock.Sleep() would cause a stack dive.

Best option is probably to implement IScheduler always scheduling to the thread pool, and also expose the inner IScheduler for synchronous scheduling.

Better option:
Run callbacks within a pauseable thread context. This has to be an independent thread so it can preserve its own callstack (e.g., Task.Run). Then have the callback wrapper just wait for either the user-defined callback to return or be paused. Blocking method such as SystemClock.Sleep would detect that they are running within AdvanceBy (due to the presence of a pauser), schedule a callback, pause the pauser, and then block on the pauser. The new callback will unpause the pauser and then wait for either the user-defined callback to return or be paused again.
Unfortunately, this won't work for sync-over-async scenarios, such as SystemClock.Delay(..).Wait(). We'd have to either capture all blocking calls via Fakes (meh), or use our own Tasklike type. Using our own tasklike causes its own problems (everything else expects Task).

The pauser is probably the way to go.
Sync-over-async scenarios can be caught by the analyzer. Flux can provide replacements, e.g.,
using Flux.System.Threading.Tasks;

FluxTask.Delay(..).Wait(); // still triggers analyzer
FluxTask.Delay(..).FluxWait(); // flux extension method passes

FluxWait works like any other flux blocking replacement, with the pauser.


Stop swallowing VM deployment error

When a VM fails to deploy we swallow the original error resulting in no controller logs entries and no events being generated. Returning the error ensures both occur and provides operator with an indication of the problem.

Codecov Report
Patch coverage: 23.07% and project coverage change: -0.06% :warning:

Comparison is base (a2e323a) 25.47% compared to head (da00c3e) 25.41%.

:exclamation: Current head da00c3e differs from pull request most recent head 1771844. Consider uploading reports for the commit 1771844 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #313      +/-   ##
==========================================
- Coverage   25.47%   25.41%   -0.06%
==========================================
  Files          59       59
  Lines        5554     5563       +9
==========================================
- Hits         1415     1414       -1
- Misses       4000     4010      +10
  Partials      139      139

Files Changed
Coverage Δ

pkg/cloud/instance.go
79.31% <23.07%> (-2.63%)
:arrow_down:

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


enhancementsupport subquery in LogicalGenerator

Proposed changes
select e1 from (select 1) t lateral view explode((select sequence(CURRENT_DATE(), date_add(CURRENT_DATE(), interval 2 day)))) t2 as e1;
The subquery in explode is supported by this pr

run buildall


Texture button stretch mode only works on normal texture

Godot version:

Godot 3.1
OS/device including version:

Issue description:

When using a texture button the stretch mode only works on the normal texture
Steps to reproduce:
Create a new scene with a ui node
Place a texturebutton in the ui node
Set expand to on, stretch mode to keep aspect centered
Use the default icon.png as normal an focused texture and set the texturebutton size to 100 by 300
Run the scene and click on the button
Minimal reproduction project:

TextureButton.zip

https://github.com/godotengine/godot/pull/27088 addresses this.

I'll close this issue as it has been addressed in the master branch (and will be fixed inthe upcoming 3.1.1).


Update readme.md

quick code fix - missing bracket

:santa:
feel free to fix the entire readme lol it's so terrible


rsyslog: 8.1904.0 -> 8.1905.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/rsyslog/versions.
meta.description for rsyslog is: '"Enhanced syslog implementation"'.
meta.homepage for rsyslog is: '"https://www.rsyslog.com/"

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 8.1905.0 with grep in /nix/store/xiapy63dy8g9y47w04v3pf874dnva7an-rsyslog-8.1905.0
directory tree listing: https://gist.github.com/33dd2f014b880d008f741be9782f9864
du listing: https://gist.github.com/5cdd63016c4af04b9d5eb9d053edc174

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
rsyslog
rsyslog-light

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xiapy63dy8g9y47w04v3pf874dnva7an-rsyslog-8.1905.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A rsyslog https://github.com/r-ryantm/nixpkgs/archive/b9023319f43bcc38c8e86fd7349479de2d6c089c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xiapy63dy8g9y47w04v3pf874dnva7an-rsyslog-8.1905.0
ls -la /nix/store/xiapy63dy8g9y47w04v3pf874dnva7an-rsyslog-8.1905.0/bin

@GrahamcOfBorg test rsyslogd

Changelog:
https://github.com/rsyslog/rsyslog/blob/v8.1905.0/ChangeLog


Make calling .prepare() optional

I see my other PR meets some kind of silent resistance, so I'm sending this one that incorporates major part of original but without introducing any new feature so it should be easier to review.
The only purpose of this PR is to make .prepare() call optional when creating custom server (without it development server doesn't work). This change is 100% backward compatible and doesn't introduce any new features. I can update other custom server examples if you agree to merge this.
EDIT:
This PR makes development server to accept connections instantly, the same way production does

I don't think we have to make any changes here.

This PR makes development server to accept connections instantly, the same way production does

This is already the case.
At this point I don't think we should remove / obfuscate the prepare call.

This is not the case for development server. If you omit .prepare() it won't start if you use custom server. This is not obfuscating prepare() call but removing something that is not necessary and makes it really difficult to run custom next server in some cases


[release-v1.33][cherry-pick] Fix security-context for apiserver - audit logs are supported only in Enterprise version

Description
Cherry-pick https://github.com/tigera/operator/pull/2906

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

/sem-approve

/sem-approve

/sem-approve

/sem-approve

/sem-approve


Trying to install compute role on a machine

While trying to assign compute role on machine , puppet tries to install keystone server and running Keystone::Resource::Service_identity , i see in openstack::common::neutron.pp we are including
include ::openstack::common::keystone but are not having any check whether it is a controller.
Adding fixes it
if $is_controller {
neutron auth depends upon a keystone configuration
include ::openstack::common::keystone
class { '::neutron::keystone::auth':
password         => $::openstack::config::neutron_password,
public_address   => $::openstack::config::controller_address_api,
admin_address    => $::openstack::config::controller_address_management,
internal_address => $::openstack::config::controller_address_management,
region           => $::openstack::config::region,
}
}
Is it correct , has nobody else seen this issue.

Confirming, the issue still persists (Role openstack::role::compute):
Error: Could not find resource 'Service[apache2]' for relationship from 'Service[keystone]' on node compute01 Error: Could not find resource 'Service[apache2]' for relationship from 'Service[keystone]' on node compute01


Nuxt fails to preserve a side-effect only import in server build

Environment
Nuxi 3.4.3
RootDir: /home/projects/nuxt-starter-hpuww7
Nuxt project info:

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.3
Nitro Version:    2.4.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction

Install @vintl/compact-number
Import @vintl/compact-number/locale-data/en without any specifiers (side-effect only import)

https://stackblitz.com/edit/nuxt-starter-hpuww7?file=app.vue
Describe the bug
Nuxt successfully preserves the import in both .nuxt/dist/client (search thousand in .nuxt/dist/client/_nuxt/entry.xxxxxx.js) and .nuxt/dist/server (.nuxt/dist/server/server.mjs has the import line), however the Nitro server build in .output fails to preserve the import, which causes an error in real applications. In @vintl/compact-number case it's a locale data required for the package to function properly.
Additional context
N/D
Logs
N/A

Would you try something like this?
export default defineNuxtConfig({
  nitro: {
    moduleSideEffects: ['@vintl/compact-number/locale-data/en']
  }
})

Oh, thank you so much, Daniel! Adding moduleSideEffects: ['@vintl/compact-number/locale-data'] does seem to mitigate this and import appears in .output/server/chunks/app/server.mjs.
Though I'm still not sure why Nitro would want to override the default @rollup/plugin-node-resolve behaviour for deciding side effect only imports, which, as I understand, is based on sideEffects in package.json and more or less universally accepted across different bundlers ^1 ^2 ^3 (changing it made the import appear in .nuxt/dist outputs, but not nitro server build).

cc: @pi0

Hello everyone! I have the same issue but with local modules, and I found a temporary solution.
TLDR: Moving pages to the /components/ directory fixed the issue.
Basically, I have a module with the locales object like this:
export interface LocaleKeys { [key: string]: string }

export interface Locale {
  [scope: string]: LocaleKeys;
}

const locales = reactive<{
  [code: string]: {
    name: string;
    scopes: Locale;
  };
}>({});

To split locales into small pieces (scopes), in each part of the application (components, pages, etc) I modify this object with the helper addKeys() function like so:
addKeys("EN_US", "localeKey", {
  key1: "value1",
  key2: "value2",
});

And I have an index.ts file that imports all locales in a scope.
When I import index.ts in a .vue file inside /components/ directory, it works fine.
When I import index.ts in a .vue file inside /pages/ directory, it prints "hydration mismatch" in a browser when I build my app. I found that Nitro completely ignores this import on server side.
I haven't checked if components or modules in other directories have the same issue.
As a quick and dirty fix, I just moved all my pages to the /components/ directory.
Note: I use /app/router.options.ts file to configure routes. To use this fix, you need to either use this file or change pages directory at nuxt.config.ts file - whatever suits you the most.

If you're still experiencing this, would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏
If it only recurs with Nuxt, let me know and I'll reopen it here.


Warning if WIN32_LEAN_AND_MEAN is already defined

A warning occurs when trying to compile if the WIN32_LEAN_AND_MEAN is already defined. In my windows builds I have that macro defined globally via my build system. I have warnings as errors enabled so I can't compile.
ln116:
#if PLATFORM_WINDOWS
#  define WIN32_LEAN_AND_MEAN

should likely be
#if PLATFORM_WINDOWS
#  ifndef WIN32_LEAN_AND_MEAN
#    define WIN32_LEAN_AND_MEAN
#  endif

Definitely a good idea, see #123


manager.addProvider is not a function.

I always get the error like
"manager.addProvider is not a function. (In 'manager.addProvider', 'manager.addProvider' is undefined)",
How to fix this? Please help me.

Did you run react-native link?

It seems that this will get fixed with a new release since the function is indded available in the current code (https://github.com/fullstackreact/react-native-oauth/blob/master/react-native-oauth.js#L32) but not in the currently latest version 2.1.14 (https://github.com/fullstackreact/react-native-oauth/blob/v2.1.14/react-native-oauth.js).

@auser has merged #111 (thanks) so @akjesto this should work for you.

Seems this still needs to be pushed to npmjs?

I'm having the same issue. Is there a fix?

@nickcobbett look at my comment above https://github.com/fullstackreact/react-native-oauth/issues/109#issuecomment-299994598

2.2.0 closes this one.


Fix DPO with Reference Model

Summary
Thanks to @ByronHsu, he identified that the implementation in https://github.com/linkedin/Liger-Kernel/pull/378 lacked a reference model for DPO, effectively making it a CPO (Contrastive Preference Optimization) instead. To address this issue, I have:

Added a reference model
Implemented ref_chosen_logps and ref_rejected_logps
Incorporated a partial function in the forward pass

These changes ensure that DPO tests and benchmarks now function correctly.
DPO Loss Formulation
As mentioned in the previous PR https://github.com/linkedin/Liger-Kernel/pull/378,
In a reference setting, we get the formula:
$$r_\theta(x,y_c) - r_\theta(x,y_r) = \log(\pi_\theta(y_c|x)) - \log(\pi_\theta(y_r|x))$$
For the loss:
$$-\log(\sigma((\log(\pi_\theta(y_c|x)) - \log(\pi_\theta(y_r|x)) - \log(\pi_{\theta_{\text{ref}}}(y_c|x)) + \log(\pi_{\theta_{\text{ref}}}(y_r|x))) * \beta))$$
This corresponds to the code:
# Policy model log probabilities
policy_chosen_logps = log_probs(policy_chosen_logits)
policy_rejected_logps = log_probs(policy_rejected_logits)

# Reference model log probabilities
ref_chosen_logps = log_probs(ref_chosen_logits)
ref_rejected_logps = log_probs(ref_rejected_logits)

# Compute advantages
chosen_advantages = policy_chosen_logps - ref_chosen_logps
rejected_advantages = policy_rejected_logps - ref_rejected_logps

# policy_chosen_logps - ref_chosen_logps - policy_rejected_logps + ref_rejected_logps
logits_diff = (chosen_advantages - rejected_advantages) * beta

# DPO loss
losses = -F.logsigmoid(logits_diff)

Testing Done
Updated benchmarks:

Hardware Type: NVIDIA A100(40G)
[X] run make test to ensure correctness
[X] run make checkstyle to ensure code style
[X] run make test-convergence to ensure convergence

This is wrong!! The correct implementation is in https://github.com/linkedin/Liger-Kernel/pull/405.
What I did wrong:
# This is incorrect:
ref_chosen_logps = torch.randn(B // 2, device="cuda", dtype=dtype)
ref_rejected_logps = torch.randn(B // 2, device="cuda", dtype=dtype)

Why I'm wrong:
I should not create random tensors for ref_chosen_logps and ref_rejected_logps. Here's why:
In DPO, the reference log probabilities MUST come from evaluating the reference model on the same inputs.
My random tensors break the crucial relationships between:

The input sequences
The policy model's predictions
The reference model's predictions

How to fix:
I need to add a reference model flag to switch on/off reference model usage, and compute proper reference logprobs when it's enabled.
Thanks to @shivam15s The correct implementation is already in PR #405. I'll close this PR to align with that approach.


Recreate UI with MUI

Replace basic HTML tags
Use Material UI library

Closing, issue has been solved in the corresponding pull request.