Fix: CanBeSent does not rely on existing object

What type of PR is this?
bug
What this PR does / why we need it?
The bug:

with the latest fix of a nil ptr deref in ocm-agent-operator, recorditems with a nil lastUpdatedTimestamp are automatically garbage collected
we currently need to pre-create recorditems for the CanBeSent() function, but the timestamp isn't set

Result: the recorditems we create are instantly garbage collected by ocm-agent-operator
The fix:
FiringCanBeSent() defined in ocm-agent-operator (API) requires a managedfleetnotificationrecord to exist: https://github.com/openshift/ocm-agent-operator/blob/e0178327b55ced0475e276c147e7b73b7c4cbfe1/api/v1alpha1/managedfleetnotificationrecord_types.go#L145
Due to this, we needed to create it before the check.
This PR re-implements firingCanBeSent() to not rely on the existing record: if no record exists, the notification can automatically be sent.
With this change, the creation and update of the managedfleetnotificationrecord / item was moved into a single function that is called once OA handles a managed fleet notification. This allows creating the recorditem directly with the timestamp in a single Update() call.
Note that we can delete the FiringCanBeSent in ocm-agent-operator after this PR.
Which Jira/Github issue(s) this PR fixes?
Fixes #
Special notes for your reviewer:
Pre-checks (if applicable):

[x] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

Codecov Report
Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (8d59690) 49.07% compared to head (933ff1f) 49.17%.

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
+ Coverage   49.07%   49.17%   +0.09%
==========================================
  Files          20       20
  Lines        1459     1452       -7
==========================================
- Hits          716      714       -2
+ Misses        700      698       -2
+ Partials       43       40       -3

Files
Coverage Δ

pkg/handlers/helper.go
95.65% <ø> (ø)

pkg/handlers/webhookrhobsreceiver.go
54.16% <79.16%> (+0.90%)
:arrow_up:

/lgtm
/approve


Remove myself from reviewers

@jeffmendoza - you seem to be the only approver in this file. Can you approve and lgtm this please?

/lgtm


Refactor tests to start and stop server from hooks

The FTs are still failing. I know these are unrelated to the changes. I can merge this, but wanted to check if you want to fix them before merge?

I feel we can merge this. Investigating on the switchTo failure will raise a separate PR for that.


bufio.Scanner: token too long - When installing platform in a namespace

I have a k8s cluster on GKE and trying to install the platform as described in https://funktion.fabric8.io/docs/#install-platform and I get this error:
funktion install platform --namespace cheese
kubectl apply --namespace cheese -f https://repo1.maven.org/maven2/io/fabric8/platform/packages/funktion-platform/2.4.24/funktion-platform-2.4.24-kubernetes.yml

bufio.Scanner: token too long
Failed: exit status 1

What version of kubectl are you running?  You could try making sure you have the latest.

I upgraded to 1.5.3 and running on minikube. When I run the above command I now get:
$ funktion install platform --namespace cheese
Failed: Cannot get version to deploy from url https://repo1.maven.org/maven2/io/fabric8/platform/packages/funktion-platform/maven-metadata.xml due to: Get https://repo1.maven.org/maven2/io/fabric8/platform/packages/funktion-platform/maven-metadata.xml: dial tcp: lookup repo1.maven.org on <IP_ADDRESS>:53: no such host

@frankscholten are you behind a HTTP proxy or something? It looks like the shell you are in can't access the internet to resolve repo1.maven.org

I'm not behind a proxy. I did an strace and then it started uploadin configmaps but it stopped with this error:
deployment "configmapcontroller" created
deployment "exposecontroller" created
deployment "fabric8" created
deployment "funktion-operator" created
The ConfigMap "catalog-letschat" is invalid: metadata.annotations: Too long: must have at most 262144 characters
Failed: exit status 1
 <unfinished ...>
+++ exited with 0 +++

I now tried this on my desktop and run into another error:
frank@desktop:~$ minikube version
minikube version: v0.17.1
frank@desktop:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.3", GitCommit:"029c3a408176b55c30846f0faedf56aae5992e9b", GitTreeState:"clean", BuildDate:"2017-02-15T06:40:50Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.3", GitCommit:"029c3a408176b55c30846f0faedf56aae5992e9b", GitTreeState:"clean", BuildDate:"2017-02-15T06:34:56Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
frank@desktop:~$ funktion version
funktion version: 1.0.10
frank@desktop:~$ funktion install platform
created Namespace funktion-system
kubectl apply --namespace funktion-system -f https://repo1.maven.org/maven2/io/fabric8/platform/packages/funktion-platform/2.4.24/funktion-platform-2.4.24-kubernetes.yml

namespace "user-secrets-source-admin" configured
serviceaccount "configmapcontroller" created
serviceaccount "exposecontroller" created
serviceaccount "fabric8" created
serviceaccount "funktion-operator" created
service "fabric8" created
service "jenkinshift" created
configmap "catalog-apiman" created
configmap "catalog-apiman-gateway" created
configmap "catalog-artifactory" created
configmap "catalog-cd-pipeline" created
configmap "catalog-chaos-monkey" created
configmap "catalog-chat-irc" created
configmap "catalog-chat-letschat" created
configmap "catalog-chat-slack" created
configmap "catalog-configmapcontroller" created
configmap "catalog-content-repository" created
configmap "catalog-elasticsearch" created
configmap "catalog-elasticsearch-v1" created
configmap "catalog-exposecontroller" created
configmap "catalog-fabric8-docker-registry" created
configmap "catalog-fabric8-forge" created
configmap "catalog-fluentd" created
configmap "catalog-funktion" created
configmap "catalog-funktion-operator" created
configmap "catalog-funktion-runtimes" created
configmap "catalog-gerrit" created
configmap "catalog-git-collector" created
configmap "catalog-gitlab" created
configmap "catalog-gogs" created
configmap "catalog-grafana" created
configmap "catalog-ingress-nginx" created
configmap "catalog-jenkins" created
configmap "catalog-keycloak" created
configmap "catalog-kibana" created
configmap "catalog-kiwiirc" created
configmap "catalog-kubeflix" created
configmap "catalog-logging" created
configmap "catalog-manageiq" created
configmap "catalog-management" created
configmap "catalog-maven-shell" created
configmap "catalog-message-broker" created
configmap "catalog-message-gateway" created
configmap "catalog-messaging" created
configmap "catalog-metrics" created
configmap "catalog-nexus" created
configmap "catalog-prometheus" created
configmap "catalog-prometheus-blackbox-exporter" created
configmap "catalog-prometheus-node-exporter" created
configmap "catalog-social" created
configmap "catalog-taiga" created
configmap "catalog-turbine-server" created
configmap "catalog-zipkin" created
configmap "catalog-zookeeper" created
configmap "exposecontroller" created
configmap "fabric8" created
configmap "fabric8-environments" created
configmap "nodejs" created
deployment "configmapcontroller" created
deployment "exposecontroller" created
deployment "fabric8" created
deployment "funktion-operator" created
The ConfigMap "catalog-letschat" is invalid: metadata.annotations: Too long: must have at most 262144 characters
Failed: exit status 1

This is a known issue (see #33). You should be able to safely ignore the error - funktion should still work fine.

this finally got fixed now for good - the installation is now lean and mean and has been tested on the latest minishift and openshift online too


Added Page  Objectives

Description
Added Page Objectives
Fixes #206

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

ATTACH SCREEN-SHOTS
https://rohank2502.github.io/SFC-foundations/pages/About-Us/objectives.html

@himanshu007-creator  Please Have a look when you are free do suggest changes

ATTACH SCREEN-SHOTS
https://rohank2502.github.io/SFC-foundations/pages/About-Us/objectives.html

Link doesn't work yet, check again.

ATTACH SCREEN-SHOTS
https://rohank2502.github.io/SFC-foundations/pages/About-Us/objectives.html

Link doesn't work yet, check again.

Yes because it was deployed for master just give me a min

Yes @himanshu007-creator  @1502shivam-singh  Please give a look its working


developer.paypal.com doc improvements

[ ] Example of payment.execute() with payment details returned in response
[x] Better example of mark integration
[x] Links to demo app, when deployed
[x] Pass experience profile to payment.create

It will be best to have a detailed error response structure and example response. For example, error message seems to return a javascript error instead of a human readable error.
{       "name": "ERROR_NAME",     "message": "ERROR_DESCRIPTION",     "information_link": "ERROR_DOCUMENTATION_LINK",     "details": "ERROR_DETAILS" }
https://developer.paypal.com/docs/api/errors/


argv out-of-bound access is silently ignored

Might be related to #103.
Input:
#include <assert.h>

int main(int argc, char * argv[])
{
    assert(argc == 1);
    const char *ptr = argv[10]; /* error */
}

Output:
$ symbiotic --prp=memsafety argv-oob.c
8.0.0-pre-llvm-12.0.0-symbiotic:66916f64-dg:06c8ca8c-sbt-slicer:b0864a5b-sbt-instrumentation:ad1d134f-klee:10e5fae9
INFO: Looking for invalid dereferences, invalid free, memory leaks, etc.
INFO: Starting instrumentation
wrapper: `which slllvm` failed with error code 1

INFO: Instrumentation time: 0.05532646179199219
INFO: Optimizations time: 0.02613091468811035
INFO: Starting slicing
INFO: Total slicing time: 0.020180940628051758
INFO: Optimizations time: 0.026351213455200195
INFO: After-slicing optimizations and transformations time: 3.0517578125e-05
INFO: Starting verification
KLEE: WARNING: undefined reference to function: klee_make_nondet
No error found.
NOTE: In the future, the result is going to be reported in SV-COMP format only with --report=sv-comp switch
RESULT: true
INFO: Total time elapsed: 0.5680685043334961

Yep, solving this should probably solve also #103 .
We need to:

[ ] enable symbolic argv in KLEE (and other verification backends). KLEE allows only a bounded argv, so we must pick a good bound (and make sure to catch the cases where the bound is not enough to avoid incorrect answers).
[ ] check that slicer works in this scenario. I think that slicer should work well, but is imprecise with argv (https://github.com/mchalupa/dg/issues/280.)


Fix bugs when integrating with Chat service endpoint

do not add request.uri in the url template.
remove unnecessary properties in RequestViewModel that are not used
Pull 'ContentType' header from request parameter.
Refactor a function to generate the required, optionals query params and headers
Move logic to build optional header /query params to the unwrapped options code block.

Fixes #89.


Theming: introduce border colors for individual components to override contrastBorder

I wanna add a border to the right side of the sidebar. The only way to do it now that I know of is to use contrastBorder but that's adding a lot of other borders too which I don't want. Is it possible to do it in another way? And can you add support for it if it's not possible? Needed for https://github.com/teabyii/vscode-ayu/issues/7

There are still many borders that are not configurable on their own but coming in via contrastBorder. More examples include: status bar border, activity bar border, tabs container border.

I added specific border colors to override contrastBorder:

editorGroupHeader.tabsBorder
statusBar.border
activityBar.border
sideBar.border


fishplot analysis - demo

This module is for inferring subclones in tumor samples across cancer types and patients in the PBTA dataset. This code is an example of six LGG patients that fishplot worked for.
Issues in the fishplot so far:

To generate fishplots, clusters of CCF are needed (frac.table). Here, I used tumor_fraction column, but I need to figure out how to run sciClone/PyClone.
Similar to (1), I need to figure out how to set up parents table.
To run this for multiple patient samples at the same time.

Please review code logic and results/output files for clarity.

The following were addressed:

Fixed issue with selecting patient samples with multiple time points
Used tumor fraction for frac.table
Run for 6 patients with LGG

The module is updated now to process and generate input files for clone phylogenies and fishplot. Scripts are still in process, but they can be reviewed for logic. For more details about the steps and logic of the module, please see  files: README.md and 02A-CloneFinder.sh
I also need to update Dockerfile for some additional R packages and for python (CloneFinder).
@jharenza

The module is updated now to process and generate input files for CloneFinder. Scripts are still in process, but please review "01-process-data.Rmd" for logic. For more details about the steps and logic of the module, please see the file: README.md.
In step 3, generating a wide table for the list of the df runs into an error. It doesn't return for one file. Any insights are welcome.

There is a bug when merging multiple data frames across a list of data frames: data_all[[i]]$merge_read_counts

There is one library not included in the Docker image (library(future)). I will update it accordingly and create a new PR.

I am closing this as it will be addressed in a different branch that will follow the https://github.com/d3b-center/pbta-tumor-evolution/pull/60


Pushkar Singh

This is Pushkar Singh. And I will be adding my data to do my first contribution as well as get a card on the website.

can you please assign this to me

Hi , I would like to contribute to this . Please assign this issue to me

Go ahead


how to use it when using docker-compose

how to use it when using docker-compose

Hey,
You can build image and use it instead of official one with community-provided docker-compose.yml.
To do so, you have to replace this line:
x-superset-image: &superset-image apache/superset:latest-dev
with this
x-superset-image: &superset-image data-diving/superset-xlsx


Required rule when using nested v-model and updating field programmatically

Versions:

VueJs: 2.4.2
Vee-Validate: 2.0.0

Description:
When using nested v-model, required rule doesn't work when there is a change by the code. Editing field normally works.
Edit: same issue when validating a computed property with getter and setter.
Steps To Reproduce:
https://jsfiddle.net/upfb35Lh/

Currently vee-validate does not watch fields with models with indices access for various reasons so it falls back to the input event. I'm exploring possible improvements for it.
You can solve it by changing the access methods to the dot syntax instead and it should work:
https://jsfiddle.net/logaretm/upfb35Lh/5/
another solution is to emit the event manually via dispatchEvent method on html elements.

Thanks! Didn't think about using dot notation there :)
Sent from my OnePlus ONEPLUS A3003 using FastHub


LAS to PCD then std::invalid_argument error

Hi guys, @apburt
I have .las data that i can viz in cloudcompare. When I Run getdemslice I run into this error:
I had .las and exported it in CC as .pcd

Cheers,
Sam

Hi Sam,
My first guess would be that this is do with the file name. The permitted naming convention is currently very inflexible (see getFileID in treeseg.cpp).
I think this should work:
Nursery_6000pt_Nurstrial17_combined_crop1.tile.1.pcd
Also getdemslice has 5 inputs (see getdemslice.cpp). The purpose of the binary is to load the point cloud, fit a DEM, and then generate and output a slice, along the z-axis, of the input cloud. The four parameters: 1) the resolution of the DEM in metres, 2) the percentile which is considered to constitute the ground (i.e., if all the points inside each DEM tile are lined up by their z coordinate - the point closest to the Nth percentile is considered the ground - sometimes useful for noisy data). 3)&4) The zmin and zmax of the slice. So e.g.,:
getdemslice 2 3 3 6 Nursery_6000pt_Nurstrial17_combined_crop1.tile.1.pcd
This month I am going to try and put together some documentation as I'm aware it is sorely missing!
Hope this helps,
Cheers,
Andy

Hi Andy @apburt thanks for your prompt reply,
It appears that I was getting the error because I was missing a parameter. I have renamed the file and added the extra param and it tries to execute because it pauses for 6 seconds before throwing the segmentation fault error.

(I already removed the ground in cloud compare and it's on a flat surface so I probably need to use another command and not DEMSLICE)
Cheers,
Sam

Hi - it's difficult to diagnose what is happening here, but the input is expected to be a larger-area point cloud (either a single tile, or many if a large dataset (e.g., > 4GB) - mydata.tile.*.pcd). I you want you can send me the data - I'm happy to take a quick look.

Hi Andy, I'll ask my manager if I can send through the data. Should be okay. I sent you an email about using docker. It's strange because downsample worked and stored the output on my machine, but then I pulled the latest version of treeseg last week and downsample still seems to run but it's no outputting anything anymore. Really looking forward to the rest of the tutorial documentation aswell! I understand that a special REIGL account is needed if people want to use your data for the tutorial?

Apologies for the long delay - the tutorial has now been completed and the preprocessed tutorial data (i.e., does not require the rivlib libraries etc) are available at https://zenodo.org/record/4661301. Hope this all helps. Cheers, Andy


[Spark] Fix compile error on Spark master due to ParserInterface changes

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

https://github.com/apache/spark/pull/46665 introduced a new parseScript method in ParserInterface, which broke compilation against Spark master:
[error] /home/runner/work/delta/delta/spark/src/main/scala/io/delta/sql/parser/DeltaSqlParser.scala:75:7: class DeltaSqlParser needs to be abstract.
[error] Missing implementation for member of trait ParserInterface:
[error]   def parseScript(sqlScriptText: String): org.apache.spark.sql.catalyst.parser.CompoundBody = ???
[error] class DeltaSqlParser(val delegate: ParserInterface) extends ParserInterface {
[error]       ^
[warn] 100 warnings found
[error] one error found
[error] (spark / Compile / compileIncremental) Compilation failed

This PR fixes the issue by shimming the ParserInterface since parseScript is not available in Spark 3.5
How was this patch tested?

Existing DeltaSqlParserSuite
Does this PR introduce any user-facing changes?

No

@zedtang can you check the failure are related?

@zedtang can you check the failure are related?

I don't think it's related. I'm seeing the same error on my other PR's run.
### Executing cmd: pip3 install /home/runner/work/delta/delta/dist/delta_spark-3.3.0_SNAPSHOT-py3-none-any.whl
Traceback (most recent call last):
  File "/home/runner/work/delta/delta/python/run-tests.py", line 183, in <module>
    run_pypi_packaging_tests(root_dir)
  File "/home/runner/work/delta/delta/python/run-tests.py", line 156, in run_pypi_packaging_tests
    run_cmd(install_whl_cmd, stream_output=True)
  File "/home/runner/work/delta/delta/python/run-tests.py", line 84, in run_cmd
    raise Exception("Non-zero exitcode: %s" % (exit_code))
Exception: Non-zero exitcode: 1
##### Running SBT tests #####
Running command: ['/home/runner/work/delta/delta/build/sbt', 'clean', '++ 2.12.18', 'sparkGroup/test', '-v', '-J-XX:+UseG1GC', '-J-Xmx6G']
##### Running Python tests #####
Calling script %s /home/runner/work/delta/delta/python/run-tests.py
Running command: ['python3', '/home/runner/work/delta/delta/python/run-tests.py']
Traceback (most recent call last):
  File "run-tests.py", line 233, in <module>
    run_python_tests(root_dir)
  File "run-tests.py", line 86, in run_python_tests
    run_cmd(["python3", python_test_script], stream_output=True)
  File "run-tests.py", line 102, in run_cmd
    raise Exception("Non-zero exitcode: %s" % (exit_code))
Exception: Non-zero exitcode: 1
Error: Process completed with exit code 1.


Saucelabs errors sometimes not reported

I discovered this bug because our task is using environment variables that were not set on my local setup. A null value was added to the tags array which created an invalid JSON. Saucelabs instead of returning a 400 or any HTTP error, it returns a 200 but adds a "status": "test error".
This error is not caught and creates a un-ending loop until the timeout is reached.

For what its worth, I'm currently seeing something similar:
{
    "completed": false,
    "js tests": [
        {
            "status": "test error",
            "platform": [
                "OSX 10.9",
                "chrome",
                "latest-1"
            ],
            "id": "some-id...",
            "job_id": "job not ready"
        }
    ]
}

No job shows up in the Dashboard.


Error: Context has not been properly initialized. Please call the .initialize() method to setup your app context object.

Issue summary
Upgraded to @shopify/shopify-api 2.0.0 and @shopify/koa-shopify-auth 4.1.2.
Actual behavior
In server.js ShopifyContext is being initialized as typically done, however upon visiting the application route it throws an error that Context has not been properly initialized.  Logging the Context shows that it is indeed initialized.
Shopify.Context.initialize({   API_KEY: process.env.SHOPIFY_API_KEY,   API_SECRET_KEY: process.env.SHOPIFY_API_SECRET,   SCOPES: process.env.SCOPES.split(","),   HOST_NAME: process.env.HOST.replace(/https:\/\//, ""),   API_VERSION: ApiVersion.October21,   IS_EMBEDDED_APP: true,   IS_PRIVATE_APP: false,   // This should be replaced with your preferred storage strategy   SESSION_STORAGE: new Shopify.Session.CustomSessionStorage(     storeCallback,     loadCallback,     deleteCallback   ), });
Currently trying to track down the problem looking at updates to the repos for both packages, granted the app was working fine before upgrading.
Things I noticed so far in my detective work:
-New documentation for @koa-shopify-auth mentions using shopifyAuth() instead of createShopifyAuth().  However, if you generate a new skeleton app project via the CLI with 4.1.2 it uses the old createShopifyAuth().  Using either one doesn't seem to make a difference.
Background
App was generated using the CLI.  Not much has changed in server.js besides switching to a CustomSessionStorage using a database.  App was working prior to update.  Wanted to update as @shopify/shopify-api seems to be rapidly rolling out bugfixes.  One the ones being when I discovered webhook registry was taking place in memory causing webhooks to fail on server restart (implemented a fix but yeah) =P

Realized that koa-shopify-auth has shopify-api as a dependency already.  Was due to some sort of conflict.

Realized that koa-shopify-auth has shopify-api as a dependency already. Was due to some sort of conflict.

Yeah I saw in another thread that they actually plan on deprecating koa-shopify-auth soon as most of it's functionality is now included in the official shopify-api package.

We just ended up getting rid of koa-shopify-auth completely in favor of the new 2.0 version of shopify-api.  After coming back with fresh eyes it was only ~30-1hr to swap it out =). @limeforadime

Cool! Glad to hear it's an easy fix, because I was actually going to switch over to the shopify-api solution as well.

We just ended up getting rid of koa-shopify-auth completely in favor of the new 2.0 version of shopify-api. After coming back with fresh eyes it was only ~30-1hr to swap it out =). @limeforadime

I'm actually having a heck of a time getting the shopify-api auth methods to work. I keep getting Oauth Cookie errors. Could I bother you and ask to see the code for your auth routes? The /auth and /auth/callback routes in particular. Following the Oauth documentation for shopify-node-api didn't work at all for me.

@conspireagency @limeforadime Hey I'm trying to get rid of koa-shopify-auth as well, could either of you share more on what you had to do to swap it out?
These are the two routes for me:
router.get("/auth", async (ctx) => {
    let authRoute = await Shopify.Auth.beginAuth(
      ctx.req,
      ctx.res,
      ctx.query.shop,
      "/auth/callback",
      true
    );
    return ctx.redirect(authRoute);
  });
  router.get("/auth/callback", async (ctx) => {
    try {
      const session = await Shopify.Auth.validateAuthCallback(
        ctx.req,
        ctx.res,
        ctx.query
      );
      ACTIVE_SHOPIFY_SHOPS[SHOP] = session.scope;

      const { accessToken } = session;

    } catch (error) {
      console.error(error);
    }
    return ctx.redirect(`/?host=${ctx.query.host}&shop=${ctx.query.shop}`);
  });

but it leads to a "CookieNotFound [Error]"

@conspireagency @limeforadime Hey I'm trying to get rid of koa-shopify-auth as well, could either of you share more on what you had to do to swap it out?
These are the two routes for me:
router.get("/auth", async (ctx) => {
    let authRoute = await Shopify.Auth.beginAuth(
      ctx.req,
      ctx.res,
      ctx.query.shop,
      "/auth/callback",
      true
    );
    return ctx.redirect(authRoute);
  });
  router.get("/auth/callback", async (ctx) => {
    try {
      const session = await Shopify.Auth.validateAuthCallback(
        ctx.req,
        ctx.res,
        ctx.query
      );
      ACTIVE_SHOPIFY_SHOPS[SHOP] = session.scope;

      const { accessToken } = session;

    } catch (error) {
      console.error(error);
    }
    return ctx.redirect(`/?host=${ctx.query.host}&shop=${ctx.query.shop}`);
  });

but it leads to a "CookieNotFound [Error]"

@aurnik Currently in the process of fixing mine, had some trouble but I think I hit a breakthrough. Will update you when I get it working.

It was an ugly fix but after reading the breaking changes introduced by #253 I fixed this by forking my own version of koa-shopify-auth and isolating the part that broke with the shopify-api v2.0 update and changing it from this:
// koa-shopify-auth -> src/auth/index.ts, line 97
await Shopify.Auth.validateAuthCallback(ctx.req, ctx.res, ctx.query);
ctx.state.shopify = await Shopify.Utils.loadCurrentSession(ctx.req, ctx.res, config.accessMode === 'online');

to this:
const session = await Shopify.Auth.validateAuthCallback(ctx.req, ctx.res, ctx.query);
ctx.state.shopify = session;

Koa-shopify-auth has functions that assist with dealing with top level redirects vs inline redirects for embedded apps, which I wasn't able to get working with just the shopify-api package alone. In fact koa-shopify-auth is built upon shopify-api so it made more sense to me to keep on using it.

I'm actually using the instructions Shopify has given here.
I'm trying to make a rails app but always get this error once I enter the shop URL. Is there any fix to this?
I have used the gem Figaro to save the Shopify API and secrets.

I seem to be getting an internal server error 500
`Started POST "/login" for <IP_ADDRESS> at 2022-05-20 01:25:48 +0530
Processing by ShopifyApp::SessionsController#create as HTML
Parameters: {"authenticity_token"=>"[FILTERED]", "shop"=>"hyperr-delivery.myshopify.com"}
Rendering /Users/ameyacharya/.rvm/gems/ruby-3.0.0/gems/shopify_app-19.0.2/app/views/shopify_app/shared/redirect.html.erb
Rendered /Users/ameyacharya/.rvm/gems/ruby-3.0.0/gems/shopify_app-19.0.2/app/views/shopify_app/shared/redirect.html.erb (Duration: 61.8ms | Allocations: 31728)
Completed 200 OK in 64ms (Views: 62.7ms | ActiveRecord: 0.0ms | Allocations: 32578)
Started GET "/login?shop=hyperr-delivery.myshopify.com&top_level=true" for <IP_ADDRESS> at 2022-05-20 01:25:48 +0530
Processing by ShopifyApp::SessionsController#new as HTML
Parameters: {"shop"=>"hyperr-delivery.myshopify.com", "top_level"=>"true"}
Shop Load (0.5ms)  SELECT "shops".* FROM "shops" WHERE "shops"."shopify_domain" = ? LIMIT ?  [["shopify_domain", "hyperr-delivery.myshopify.com"], ["LIMIT", 1]]
Completed 500 Internal Server Error in 14ms (ActiveRecord: 0.7ms | Allocations: 6618)
ShopifyAPI::Errors::ContextNotSetupError (ShopifyAPI::Context not setup, please call ShopifyAPI::Context.setup):
shopify_api (10.1.0) lib/shopify_api/auth/oauth.rb:23:in begin_auth' sorbet-runtime (0.5.10020) lib/types/private/methods/call_validation.rb:161:in bind_call'
sorbet-runtime (0.5.10020) lib/types/private/methods/call_validation.rb:161:in validate_call' sorbet-runtime (0.5.10020) lib/types/private/methods/_methods.rb:270:in block in _on_method_added'
shopify_app (19.0.2) app/controllers/shopify_app/sessions_controller.rb:47:in start_oauth' shopify_app (19.0.2) app/controllers/shopify_app/sessions_controller.rb:40:in authenticate'
shopify_app (19.0.2) app/controllers/shopify_app/sessions_controller.rb:14:in new' actionpack (7.0.3) lib/action_controller/metal/basic_implicit_render.rb:6:in send_action'
actionpack (7.0.3) lib/abstract_controller/base.rb:215:in process_action' actionpack (7.0.3) lib/action_controller/metal/rendering.rb:53:in process_action'
actionpack (7.0.3) lib/abstract_controller/callbacks.rb:234:in block in process_action' activesupport (7.0.3) lib/active_support/callbacks.rb:118:in block in run_callbacks'
actiontext (7.0.3) lib/action_text/rendering.rb:20:in with_renderer' actiontext (7.0.3) lib/action_text/engine.rb:69:in block (4 levels) in class:Engine'
activesupport (7.0.3) lib/active_support/callbacks.rb:127:in instance_exec' activesupport (7.0.3) lib/active_support/callbacks.rb:127:in block in run_callbacks'
activesupport (7.0.3) lib/active_support/callbacks.rb:138:in run_callbacks' actionpack (7.0.3) lib/abstract_controller/callbacks.rb:233:in process_action'
actionpack (7.0.3) lib/action_controller/metal/rescue.rb:22:in process_action' actionpack (7.0.3) lib/action_controller/metal/instrumentation.rb:67:in block in process_action'
activesupport (7.0.3) lib/active_support/notifications.rb:206:in block in instrument' activesupport (7.0.3) lib/active_support/notifications/instrumenter.rb:24:in instrument'
activesupport (7.0.3) lib/active_support/notifications.rb:206:in instrument' actionpack (7.0.3) lib/action_controller/metal/instrumentation.rb:66:in process_action'
actionpack (7.0.3) lib/action_controller/metal/params_wrapper.rb:259:in process_action' activerecord (7.0.3) lib/active_record/railties/controller_runtime.rb:27:in process_action'
actionpack (7.0.3) lib/abstract_controller/base.rb:151:in process' actionview (7.0.3) lib/action_view/rendering.rb:39:in process'
actionpack (7.0.3) lib/action_controller/metal.rb:188:in dispatch' actionpack (7.0.3) lib/action_controller/metal.rb:251:in dispatch'
actionpack (7.0.3) lib/action_dispatch/routing/route_set.rb:49:in dispatch' actionpack (7.0.3) lib/action_dispatch/routing/route_set.rb:32:in serve'
actionpack (7.0.3) lib/action_dispatch/journey/router.rb:50:in block in serve' actionpack (7.0.3) lib/action_dispatch/journey/router.rb:32:in each'
actionpack (7.0.3) lib/action_dispatch/journey/router.rb:32:in serve' actionpack (7.0.3) lib/action_dispatch/routing/route_set.rb:852:in call'
railties (7.0.3) lib/rails/engine.rb:530:in call' railties (7.0.3) lib/rails/railtie.rb:226:in public_send'
railties (7.0.3) lib/rails/railtie.rb:226:in method_missing' actionpack (7.0.3) lib/action_dispatch/routing/mapper.rb:19:in block in class:Constraints'
actionpack (7.0.3) lib/action_dispatch/routing/mapper.rb:48:in serve' actionpack (7.0.3) lib/action_dispatch/journey/router.rb:50:in block in serve'
actionpack (7.0.3) lib/action_dispatch/journey/router.rb:32:in each' actionpack (7.0.3) lib/action_dispatch/journey/router.rb:32:in serve'
actionpack (7.0.3) lib/action_dispatch/routing/route_set.rb:852:in call' rack (2.2.3) lib/rack/tempfile_reaper.rb:15:in call'
rack (2.2.3) lib/rack/etag.rb:27:in call' rack (2.2.3) lib/rack/conditional_get.rb:27:in call'
rack (2.2.3) lib/rack/head.rb:12:in call' actionpack (7.0.3) lib/action_dispatch/http/permissions_policy.rb:38:in call'
actionpack (7.0.3) lib/action_dispatch/http/content_security_policy.rb:36:in call' rack (2.2.3) lib/rack/session/abstract/id.rb:266:in context'
rack (2.2.3) lib/rack/session/abstract/id.rb:260:in call' actionpack (7.0.3) lib/action_dispatch/middleware/cookies.rb:697:in call'
activerecord (7.0.3) lib/active_record/migration.rb:603:in call' actionpack (7.0.3) lib/action_dispatch/middleware/callbacks.rb:27:in block in call'
activesupport (7.0.3) lib/active_support/callbacks.rb:99:in run_callbacks' actionpack (7.0.3) lib/action_dispatch/middleware/callbacks.rb:26:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/executor.rb:14:in call' actionpack (7.0.3) lib/action_dispatch/middleware/actionable_exceptions.rb:17:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/debug_exceptions.rb:28:in call' web-console (4.2.0) lib/web_console/middleware.rb:132:in call_app'
web-console (4.2.0) lib/web_console/middleware.rb:28:in block in call' web-console (4.2.0) lib/web_console/middleware.rb:17:in catch'
web-console (4.2.0) lib/web_console/middleware.rb:17:in call' actionpack (7.0.3) lib/action_dispatch/middleware/show_exceptions.rb:26:in call'
railties (7.0.3) lib/rails/rack/logger.rb:40:in call_app' railties (7.0.3) lib/rails/rack/logger.rb:25:in block in call'
activesupport (7.0.3) lib/active_support/tagged_logging.rb:114:in block in tagged' activesupport (7.0.3) lib/active_support/tagged_logging.rb:38:in tagged'
activesupport (7.0.3) lib/active_support/tagged_logging.rb:114:in tagged' railties (7.0.3) lib/rails/rack/logger.rb:25:in call'
sprockets-rails (3.4.2) lib/sprockets/rails/quiet_assets.rb:13:in call' actionpack (7.0.3) lib/action_dispatch/middleware/remote_ip.rb:93:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/request_id.rb:26:in call' rack (2.2.3) lib/rack/method_override.rb:24:in call'
shopify_app (19.0.2) lib/shopify_app/middleware/jwt_middleware.rb:24:in call_next' shopify_app (19.0.2) lib/shopify_app/middleware/jwt_middleware.rb:12:in call'
rack (2.2.3) lib/rack/runtime.rb:22:in call' activesupport (7.0.3) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/server_timing.rb:20:in call' actionpack (7.0.3) lib/action_dispatch/middleware/executor.rb:14:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/static.rb:23:in call' rack (2.2.3) lib/rack/sendfile.rb:110:in call'
actionpack (7.0.3) lib/action_dispatch/middleware/host_authorization.rb:137:in call' railties (7.0.3) lib/rails/engine.rb:530:in call'
puma (5.6.4) lib/puma/configuration.rb:252:in call' puma (5.6.4) lib/puma/request.rb:77:in block in handle_request'
puma (5.6.4) lib/puma/thread_pool.rb:340:in with_force_shutdown' puma (5.6.4) lib/puma/request.rb:76:in handle_request'
puma (5.6.4) lib/puma/server.rb:441:in process_client' puma (5.6.4) lib/puma/thread_pool.rb:147:in block in spawn_thread'
`

@limeforadime @aurnik late response here, but I scrapped the koa library completely and just used the framework independent latest version of shopify api.  If you look at the library itself (outside of node modules) it's very cleanly written, was able to modify to support multiple public apps in a single codebase and more.  10/10 recommend going this route.

Hi am using "@shopify/koa-shopify-auth": "^5.0.3" and am getting this error when I start the server, is there any fix
/Shopify/Development/Shopify_Twilio/server/server.js:40
_shopifyApi["default"].Context.initialize({
^
TypeError: Cannot read properties of undefined (reading 'Context')
at Object. (/Shopify/Development/Shopify_Twilio/server/server.js:35:9)
at Module._compile (node:internal/modules/cjs/loader:1255:14)
at Module._compile (/Shopify/Development/Shopify_Twilio/node_modules/pirates/lib/index.js:99:24)
at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
at Object.newLoader [as .js] (/Shopify/Development/Shopify_Twilio/node_modules/pirates/lib/index.js:104:7)
at Module.load (node:internal/modules/cjs/loader:1113:32)
at Function.Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1137:19)
at require (node:internal/modules/helpers:121:18)
at Object. (/Shopify/Development/Shopify_Twilio/server/index.js:7:18)
Node.js v20.3.0
[nodemon] app crashed - waiting for file changes before starting...

Hi am using "@shopify/koa-shopify-auth": "^5.0.3" and am getting this error when I start the server, is there any fix
/Shopify/Development/Shopify_Twilio/server/server.js:40
_shopifyApi["default"].Context.initialize({
^
TypeError: Cannot read properties of undefined (reading 'Context')
at Object. (/Shopify/Development/Shopify_Twilio/server/server.js:35:9)
at Module._compile (node:internal/modules/cjs/loader:1255:14)
at Module._compile (/Shopify/Development/Shopify_Twilio/node_modules/pirates/lib/index.js:99:24)
at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
at Object.newLoader [as .js] (/Shopify/Development/Shopify_Twilio/node_modules/pirates/lib/index.js:104:7)
at Module.load (node:internal/modules/cjs/loader:1113:32)
at Function.Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1137:19)
at require (node:internal/modules/helpers:121:18)
at Object. (/Shopify/Development/Shopify_Twilio/server/index.js:7:18)
Node.js v20.3.0
[nodemon] app crashed - waiting for file changes before starting...


Update request: burpsuite 2023.1.2 → 2023.2.2

Package name: burpsuite
Latest released version: 2023.2.2

Current version on the unstable channel: 2023.1.2
Current version on the stable/release channel: 2021.12

[X] Checked the nixpkgs pull requests

Notify maintainers

Note for maintainers: Please tag this issue in your PR.
@bennofs
Also could it be described why there is this huge gap version between the stable and unstable version ? Some tests are probably failing for the unstable version ?

Closed by #223260


[e2e]: nodejs push branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/8586657628
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Sun Apr  7 06:14:03 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/8595349758
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Mon Apr  8 06:11:44 UTC 2024
Tests are passing now. Closing this issue.


Propertie extra_rows seems not to be working

I am using grister as follows and would expect to get an extra row - but that does not happen.
(With "extra row" I mean getting a second, empty row with no data in it - which I guess ultimatelly would mean that the height of the ul is increased by the the heigt of an extra row)

$(".gridster ul").gridster({
widget_margins: [10, 10],
widget_base_dimensions: [wid_base_dim_x, 200],
min_cols: 1,
extra_rows: 1,
max_cols: nrOfCols,

I can confirm this problem. I would like an extra blank row but can't it to appear.


rotateBy surpasses 360 & 0

While the rotation looks fine on screen, the number output is wrong. It should clamp to 0, and 360, then roll over to the next value as it goes past either. The reason I request this is i'd like to rotate to an angle by the shortest route. I realized this is tricky to calculate when the rotation surpasses 360deg.

https://github.com/libgdx/libgdx/wiki/More-Info

package com.badlogic.gdx.tests.lwjgl;

import com.badlogic.gdx.backends.lwjgl.LwjglApplication;
import com.badlogic.gdx.ApplicationAdapter;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.graphics.GL20;
import com.badlogic.gdx.graphics.g2d.Batch;
import com.badlogic.gdx.scenes.scene2d.Actor;
import com.badlogic.gdx.scenes.scene2d.Stage;
import com.badlogic.gdx.scenes.scene2d.actions.Actions;

class MyActor extends Actor {
    public MyActor() {

    }

    @Override
    public void draw(Batch batch, float alpha) {
        addAction(Actions.rotateBy(100));
        System.out.println(this.getRotation());
    }
}

public class MyGdxGame extends ApplicationAdapter {
    private Stage stage;

    @Override
    public void create () {
        stage = new Stage();
        stage.addActor(new MyActor());
    }

    @Override
    public void render () {
        Gdx.gl.glClearColor(1, 0, 0, 1);
        Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);
        stage.act();

        stage.draw();
    }

    public static void main (String[] args) throws Exception {
        new LwjglApplication(new MyGdxGame());
    }
}

Here's a simple code example to try. Can see how each frame the angle output just keeps going up rather than looping around back to zero.

I'm pretty sure, that this is intended. However in your case you can just use the modulus operator to get a degree between 0 and 360: rotation % 360

@mbrlabs yeah if it's intended, then you can close it. Just came off as odd behaviour given how we learn rotation in grade school as 0-360 :)

Having an angle below zero or above 360 degrees is perfectly valid (at least it was at my grade school :)). If the class would keep the angle within the 0-360 range then it might remove information the user might need. For example, the number of times it has been fully rotated ((int)(angle / 360)). Also, it would imply that adding a value might result in a lower value (x > 0 && a + x < a). Whether or not this is useful depends on the use-case. You can normalize the angle (a < 0 ? 360 - (-a % 360) : a % 360) if needed (although commonly the range -180 - 180, is often used as well).

@xoppa fair point. I have dealt with the -180 to 180 somewhere in games/graphics, though I don't recall which library :). I'll implement the modulus in my game as the solution, just used rotateTo until we figured something out. Thanks for the responses!


add prometheus and grafana to local deployment

This adds an option to deploy prometheus and grafana servers in the kpng-local-up.sh script.
These aren't yet connected to anything so they won't show any kpng data.  Yet.  Coming soon in subsequent PRs!

/lgtm
/approve

/retest

/retest

/retest

/lgtm
/approve
thanks Matt let us know what you find here !


Hubspot cleanup and access sharing with team

Clean up the hubspot data and share access with the entire team for management of contacts of users of MapLibre.

Prepared a new form but some links are broken. Investigating.


fix docs/repos links on crates.io

Umm, it's correct the way it is??

currently the "repository" link points to your documentation and the "homepage" link points to your repository

oh, I got confused, sorry. But the "homepage" link still points to the documentation

Ok that can change. Thanks!


Some help on setting up Elastic Cloud

Hi Guys,
I was super excited to notice this json-logging-with-direct-eleastic-search-integration add-on for django, no need for Logstash or Fluentd > great!
However, I need some help in setting this up.
I have the installation working, I still have DISABLE_EXISTING_LOGGERS = False so I see the JSON logs appearing inside my command-line.
However, they don't get pushed toward my Elastic Cloud environment. I think this has to do with the way I am setting up the Host and AUTH inside the settings.py.
It would be great if somebody could help me out here.
here are my settings inside settings.py:
CONSOLE_LOG = True # Log to console.

SQL_LOG = True # Log SQL queries.

SQL_THRESHOLD = 0.5 # Log slow queries only.

LOG_LEVEL = 'debug' # If settings.DEBUG is set to True, otherwise LOG_LEVEL is set to 'info'

DISABLE_EXISTING_LOGGERS = False #True # Set this to False if you want to combine with multiple loggers.

LOG_PATH = '{}/logs'.format(BASE_DIR) # If the logs folder does not exist, it will be created.

IGNORED_PATHS = ['/admin', '/static', '/favicon.ico'] # List of URL endpoints to ignore.

RESPONSE_FIELDS = ('status', 'reason', 'charset', 'headers', 'content') # List of response fields to log.

CONTENT_JSON_ONLY = True # Log response content only if its a JSON document.

ROTATE_MB = 100 # Maximum size in MB that the log file can have before it gets rotated.

ROTATE_COUNT = 10 # Maximum number of rotated log files.

INDENT_CONSOLE_LOG = 2 # Indent console log by "n" spaces.

ELASTICSEARCH_ENABLED = True # Set to yes to enable elasticsearch support.

ELASTICSEARCH_HOSTS = ["https://e89046cda63602fdc974e90502252d6a.eu-west-1.aws.found.io:9243"] # Elasticsearch hosts

ELASTICSEARCH_INDEX = "django-logging-json" # Elasticsearch index name

ELASTICSEARCH_SSL = True # Elasticsearch connection via SSL (:443)

ELASTICSEARCH_AUTH = "elastic:xxxxxxx-my-password-xxxxxxx"

Thanks, r

Hi there @radzia2,
The ELASTICSEARCH_AUTH needs to be a tuple of the form: (settings.ADMIN_USER, settings.ADMIN_PASSWORD)
I'll make sure to update the README to reflect this.
Hope this helps

HI @cipriantarta ,
I changed this and for every log I see appearing on my terminal, I get a log in my elastic cloud but... All logs are like this:
[2017-11-13T17:09:10,403][WARN ][org.elasticsearch.deprecation.rest.RestController] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.
This is how the output in my Terminal looks like:
18:26:27 web.1      |  { 'INFO': { '2017-11-13T17:26:27': { 'duration': 0.009902238845825195,
18:26:27 web.1      |                                       'request': { 'data': {},
18:26:27 web.1      |                                                    'meta': { 'http_host': 'localhost:5000',
18:26:27 web.1      |                                                              'http_user_agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, '
18:26:27 web.1      |                                                                                'like Gecko) Chrome/62.0.3202.89 Safari/537.36',
18:26:27 web.1      |                                                              'path_info': '/dashboard/',
18:26:27 web.1      |                                                              'remote_addr': '<IP_ADDRESS>'},
18:26:27 web.1      |                                                    'method': 'GET',
18:26:27 web.1      |                                                    'path': '/dashboard/',
18:26:27 web.1      |                                                    'scheme': 'http',
18:26:27 web.1      |                                                    'user': 'admin'},
18:26:27 web.1      |                                       'response': {'charset': 'utf-8', 'headers': {'Content-Type': 'text/html; charset=utf-8'}, 'reason': 'OK', 'status': 200}}}}

Any thoughts on this?
thanks,
Pieter-Jan

What ES version are you using?
On Mon, 13 Nov 2017 at 19:27, radzia2<EMAIL_ADDRESS>wrote:

HI @cipriantarta https://github.com/cipriantarta ,
I changed this and for every log I see appearing on my terminal, I get a
log in my elastic cloud but... All logs are like this:
[2017-11-13T17:09:10,403][WARN
][org.elasticsearch.deprecation.rest.RestController] Content type detection
for rest requests is deprecated. Specify the content type using the
[Content-Type] header.
This is how the output in my Terminal looks like:
18:26:27 web.1      |  { 'INFO': { '2017-11-13T17:26:27': { 'duration': 0.009902238845825195,
18:26:27 web.1      |                                       'request': { 'data': {},
18:26:27 web.1      |                                                    'meta': { 'http_host': 'localhost:5000',
18:26:27 web.1      |                                                              'http_user_agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, '
18:26:27 web.1      |                                                                                'like Gecko) Chrome/62.0.3202.89 Safari/537.36',
18:26:27 web.1      |                                                              'path_info': '/dashboard/',
18:26:27 web.1      |                                                              'remote_addr': '<IP_ADDRESS>'},
18:26:27 web.1      |                                                    'method': 'GET',
18:26:27 web.1      |                                                    'path': '/dashboard/',
18:26:27 web.1      |                                                    'scheme': 'http',
18:26:27 web.1      |                                                    'user': 'admin'},
18:26:27 web.1      |                                       'response': {'charset': 'utf-8', 'headers': {'Content-Type': 'text/html; charset=utf-8'}, 'reason': 'OK', 'status': 200}}}}
Any thoughts on this?
thanks,
Pieter-Jan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cipriantarta/django-logging/issues/15#issuecomment-343993723,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2skY2a9tkgVg5-BRhAq-MKa5uPCJeVks5s2HwMgaJpZM4QWsxy
.

--
Thanks,
Ciprian

I am using the cloud version from elastic itself. So that is the 5.6.4.
I am still figuring this thing out, so please bear with me :-)
I now started a new cluster and the errors are gone. I don't have any indexes configured yet in Kibana on this new cluster. Maybe that is the reason or has totally nothing to do with is - i am not sure.
Somehow, log's don't appear, except from the snapshots being created by elastic itself.
How could i verify if the connection between Django and Elastic is good?
Through CURL i did some succesful posts on elastic so I know it is "listening" to posts.
Thanks,

In the app.log, or even on the console, you should see exceptions from the logging library if it wouldn't be able to connect to ES.
If you look into the README, you will see ELASTICSEARCH_INDEX = "django-logging-json"
That's the index used by default by this library(you can change it to anything)
please do this:
curl -u user:pass https://<es_host>/_cat/indices?v and tell me what you have.
Use http instead if you don't have ssl support. And no user:pass if you are not using authentication

My output:
had to use https
yellow open .watcher-history-6-2017.11.14   txcikCG_SpqUvkuS5VrNkQ 1 1 2380 0   3.8mb   3.8mb
yellow open my_index                        Bhi1HV0sQiaKFzN130MIhA 5 1    3 0  12.1kb  12.1kb
green  open .security                       EblR7y4LSLGEhL7RKYbRVQ 1 0
yellow open .watches                        XCb0GzVmQk2ZWmHZ3K-cgA 1 1    4 0  39.1kb  39.1kb
yellow open .monitoring-kibana-6-2017.11.14 882cNYzsTDuD9gSx24a6rQ 1 1 3569 0   2.8mb   2.8mb
yellow open .watcher-history-6-2017.11.13   82MwUKV1QbWld2_biQz9nQ 1 1 1452 0   1.3mb   1.3mb
yellow open .monitoring-kibana-6-2017.11.13 QjnqsUQYTkqdVCHlyprFTQ 1 1 2183 0 981.9kb 981.9kb
yellow open .kibana                         s6u6OeY3Rhyp5_keHOI_KA 1 1    1 0   3.8kb   3.8kb
yellow open .triggered_watches              gqaUZOeCRYGTVjR_5pWKSQ 1 1    0 0  24.1kb  24.1kb

And your DJANGO_LOGGING settings ?

On 14 Nov 2017, at 11:57, radzia2<EMAIL_ADDRESS>wrote:
My output:
had to use https
yellow open .watcher-history-6-2017.11.14   txcikCG_SpqUvkuS5VrNkQ 1 1 2380 0   3.8mb   3.8mb
yellow open my_index                        Bhi1HV0sQiaKFzN130MIhA 5 1    3 0  12.1kb  12.1kb
green  open .security                       EblR7y4LSLGEhL7RKYbRVQ 1 0
yellow open .watches                        XCb0GzVmQk2ZWmHZ3K-cgA 1 1    4 0  39.1kb  39.1kb
yellow open .monitoring-kibana-6-2017.11.14 882cNYzsTDuD9gSx24a6rQ 1 1 3569 0   2.8mb   2.8mb
yellow open .watcher-history-6-2017.11.13   82MwUKV1QbWld2_biQz9nQ 1 1 1452 0   1.3mb   1.3mb
yellow open .monitoring-kibana-6-2017.11.13 QjnqsUQYTkqdVCHlyprFTQ 1 1 2183 0 981.9kb 981.9kb
yellow open .kibana                         s6u6OeY3Rhyp5_keHOI_KA 1 1    1 0   3.8kb   3.8kb
yellow open .triggered_watches              gqaUZOeCRYGTVjR_5pWKSQ 1 1    0 0  24.1kb  24.1kb
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cipriantarta/django-logging/issues/15#issuecomment-344205146, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2skfoOpee2p_smfVCC_42sHj9SKQ2nks5s2WPqgaJpZM4QWsxy.

I have no DJANGO_LOGGING in my settings.py. I kept it to the default settings up to today and was mainly using print() to log to the console

By default, ELASTICSEARCH_ENABLED  is set to False
You need to add DJANGO_LOGGING = {‘ELASTICSEARCH_ENABLED’: True, …} and other settings for auth, ssl, etc., which you can see in the README, in order for ES to work.

On 14 Nov 2017, at 12:17, radzia2<EMAIL_ADDRESS>wrote:
I have no DJANGO_LOGGING in my settings.py. I kept it to the default settings up to today and was mainly using print() to log to the console
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cipriantarta/django-logging/issues/15#issuecomment-344210864, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2skdehQple4aXjc26B0sIToeMwJCVsks5s2WiigaJpZM4QWsxy.

My Friend, Thank you so much, you made my day!
I totally misinterpreted the Read-Me and thank you for guiding me to this solution.
I dropped the individual settings straight in my settings.py and not in the format DJANGO_LOGGING = {‘ELASTICSEARCH_ENABLED’: True, …}
Thanks!


Not clear when you are cloning a project using extensions (storage etc.) that you need to perform a func extensions sync

I was receiving the error "binding type(s) 'blobTrigger' are not registered” on trying to run a sample my colleague had written - not able to find anything on the docs on how to resolve this and eventually managed to fix by running a func extensions sync command. It would be useful to have more info on how this works and common gotchas with extension registration in Python on the docs

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

ID: 572c4d02-183a-44c9-b0c3-3b2d0376e30a
Version Independent ID: cc9af7dd-8d54-252c-14fa-25b445888893
Content: Add an Azure Storage queue binding to your Python function
Content Source: articles/azure-functions/functions-add-output-binding-storage-queue-python.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @jjgriff93  Thanks for your feedback. We will review and update as appropriate.

@jjgriff93 I have assigned this to content author for further review and update as appropriate.

Now that we have extension bundles, you don't need to mess with extensions yourself as long as you have this in the host.json:
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[1.*, 2.0.0)"
  }

#please-close


[tuify][design] Update the Tuify default design

TODO

Update the Tuify default design to appear more appealing.
Create few more styles that users can choose from out of the box.
Write a section in tuify README.md on how to choose default or few other pre-designed style for single and multi select components.
Make sure all the designs work on editors with light or dark theme.

Current default designs
Single select default design

Multiple select default design

Idea for default design:

Idea for theme "Seaweed"

Idea for hot pink

They're all amazing

Note: added a darker background color to all 3 styles to increase readability via contrast.
Default style implemented in code (screenshot)

Focused item is also the selected item

Sea foam style implemented in code (screenshot)

Focused item is also the selected item

Hot pink style implemented in code (screenshot)

Focused item is also the selected item


host can only set one consul host?

Question
please guidance me why the property spring.cloud.consul.host can only set one consul host?
how spring-cloud-consul keep availability when the given host was unavailable in such way ?

If you want to make it highly available, maybe you could make the host property point to a load-balancer? Would that solve your issue?

It should point to an agent not an actual consul cluster node

It should point to an agent not an actual consul cluster node

How to point to an agent withs spring-cloud-consul ? Is this way really highly available?

Please stop commenting on multiple issues


Long time to load asset-manifest.json.

Bug report

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Other relevant information:
webpack version:
Node.js version:
Operating System: Linux Ubuntu 16.04
Additional tools: atom
Hi, I am running one git page and I received one feedback from China user. When my git page is loaded from China, there is significant requesting time when loading.

25
http://emanual.robot.../asset-manifest.json
text/html; charset=utf-8
66.851 s
-
125 ms
-
408 ms
3815 ms
11.6 KB
-
404
-

Is there way to improve the speed for the asset-manifest.json?
Or just delete? I am not sure what the asset-manifest.json is, and I can't find .json file from my reposi or any folder too.
Thank you for reading !
Have a good day :)
For your reference, below is the information on the asset-manifest.json file when loaded.

Request 25: http://emanual.robotis.com/asset-manifest.json
URL: http://emanual.robotis.com/asset-manifest.json
Host: emanual.robotis.com
Error/Status Code: 404
Request Start: 66.851 s
Initial Connection: 125 ms
Time to First Byte: 408 ms
Content Download: 3815 ms
Bytes In (downloaded): 11.6 KB
Bytes Out (uploaded): 0.0 KB
Request Headers:

GET /asset-manifest.json HTTP/1.1
Host: emanual.robotis.com
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 PTST/19.04
Accept: /
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://emanual.robotis.com/
origin: http://emanual.robotis.com
Connection: keep-alive
Response Headers:
HTTP/1.1 404 Not Found
Content-Type: text/html; charset=utf-8
Server: GitHub.com
ETag: W/"5ecdc066-23eb5"
Access-Control-Allow-Origin: *
Content-Encoding: gzip
X-Proxy-Cache: MISS
X-GitHub-Request-Id: CDDE:601A:588FF:5FBAC:5ECF5663
Content-Length: 11854
Accept-Ranges: bytes
Date: Thu, 28 May 2020 06:12:52 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-tyo19939-TYO
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1590646372.298839,VS0,VE172
Vary: Accept-Encoding

I can't help you here. This isn't webpack-related.

Ops
Sorry about that, but thank you for quick reply


Duplicated source roots

Hello! I am happily using your library for testing my KMP project but I have an issue getting it to work with Kotlin 2.0.0 (and the issue also happens on 1.9.23 for me).
All Mock* and *_injectMocks.kt files are generated for androidUnitTestDebug (which, if I understand it correctly is working as intended), but then they are linked to both the source set for androidUnitTestDebug and commonTest which is a warning in Kotlin 1.9.23 and unfortunately a crash in 2.0.0 (currently RC2).
There also seems to be an open issue at jetbrains which might or might not be linked:
https://youtrack.jetbrains.com/issue/KT-65426
It would be great if you could help me track this issue down (and especially tell me whether the 1.9.23 warning is intended/common)

just for tracing: The issue persists with Kotlin 2.0.0-RC3

I've seen this.
I will address it ASAP, bit probably not within the next two weeks.

Thanks a lot for the response :) If you can point me into a rough direction I can also have a look and make a pull request

this is also happening with me, only after migrating to kotlin 2.0.0

I've opened #77 with a lot of information of why this is happening, and why I haven't found a solution yet.
Make sure to read it, and provide insight if you can.
I'm closing this in favor of #77.


Refactored tests

This PR has been moved from https://github.com/bencergazda/sass-extract/pull/2

@Aapzu I updated the three commits to match the original code style and fixed a few tests in the last commit that were failing.

This branch is base on #1, I recommend to check that first. If you want to check only the changed parts, you can check the diff.

The original repo, jgranstrom/sass-extract, seems to be completely dead so I'll open my pull requests here. It would be amazing to publish a new version of this package then.
I started by fixing the feat-dart-sass branch, but realized that some refactoring needs to be done first. To make the reviewing easier, I'll open separate pull requests for the refactorings, and then the actualt fixes to the Dart Sass branch. This is the second one of them and will make testing of the dart-sass branch easier.

About this PR:

Update babel
Change mocha to jest
Rename test files from test/something.js to test/something.test.js` (Jest supports this better)
Try to get rid of all repetition in test files by using jest's describe.each and it.each
Create and utilize custom jest matchers for different types of sass variables
Rename test/sass to test/scss since there weren't any SASS in there

P.S. I did my best to keep the file references in the test files while renaming then but it appears that Git still shows them as deleted + added. Sorry about that.

@Aapzu I cannot invite you for review somehow. Please drop me a comment if I can merge the PRs.


Custom gpu ops partitioning

PR to update tutorial to demonstrate the use of custom_partitioning instead of xmap when writing a custom primitive in JAX

General comment: should we perhaps choose a simpler op/ops for this? RMSNorm needs a lot of CUDA code which is not directly relevant here.

People don't need to read the CUDA code here.
If we took something simpler, we won't be able to show all features, like multi-output.
If we find something simpler that still show all features, that would be great. But I don't have an idea.
But this should be a follow up PR I think.

General comment: should we perhaps choose a simpler op/ops for this? RMSNorm needs a lot of CUDA code which is not directly relevant here.

People don't need to read the CUDA code here. If we took something simpler, we won't be able to show all features, like multi-output.
If we find something simpler that still show all features, that would be great. But I don't have an idea. But this should be a follow up PR I think.

@jaro-sevcik had similar perception I believe ... any ideas here?

If we took something simpler, we won't be able to show all features, like multi-output.

What are some of the other features we want to demonstrate?

If we find something simpler that still show all features, that would be great. But I don't have an idea. But this should be a follow up PR I think.

Yeah, I agree this could be done in a follow up.

Yes, I think it should be good to go

Can you squash the commits, please? I suspect that could be the reason for the import/copybara check failing.

@superbobry It still seems like copybara is failing despite squashing all the commits

It looks like Copybara is unhappy that some files are missing the Apache license header. Can you make sure all files have one, please?

Can you squash the commits, please?

Done!


when user doesn't have root sudo, install should print the commands to run with root privileges

Root privilege with sudo is common on ubuntu but it's not the only linux distribution !
"Normal" users without sudo are common, with admin task done with a lot of others way (root ssh access, root password, other admin user…).
In that case, a mkcert -install fails (it loops on asking the sudo password that doesn't exists), it should ask if user wants to try another sudo pass or give the root password or print the commands that needs to be run by root.

I think you can install CA manually by using Firefox.
Go to Settings on Firefox then Search  Certificate, click on the View Certificate button then Import.
You can find the rootCA.pem installed location by running mkcert --CAROOT.


add t-izbassar to fans

@yegor256/z please, pay attention to this pull request

Job #25 is now in scope, role is REV

@t-izbassar thanks!

Job gh:yegor256/elegantobjects.github.io#25 is not assigned, can't get start time

The job #25 is now out of scope


Send unique keymap file descriptors

Fixes #1192
To prevent wl_keyboard keymap being written to by clients, use a unique
file descriptor for each wl_keyboard resource.
Reference: weston, commit 76829fc4eaea329d2a525c3978271e13bd76c078

Thanks!


Tips: Using STL in the HyperPlatform User Document is not accurate

Description
The Tips: Using STL section explains "Define _HAS_EXCEPTIONS as 0 and include any STL headers after that." but at the current master  df00162, it is expected to include kernel_stl.h instead of it since master is not updated to take off the header yet.
Update master or the document to reflect the latest status.
Expected behavior
The document reflect the latest status of master and explains accurate instructions to use STL.
Actual behavior
The instructions in the document is inconsistent with the current code base (master)
Steps to reproduce the problem
N/A
Specifications

Commit (eg, 2099af7): df00162

OS version (ie, outout of the "ver" command): N/A

Architecture: N/A

Hardware (eg, Physical, VMware 11, Bochs): N/A

Details:
Link: http://tandasat.github.io/HyperPlatform/userdocument/#__RefHeading___Toc906_1354011707

Should be fixed with b41f7e95065fbc69c29f4578ca849d30215f6ae3.


travis: split build into matrix of 3

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

This adds a 3rd matrix to be built by Travis. The new matrix "checks"
the NixPkgs evaluation so the other 2 can save their resources for
building. Hopefully, this will lead to less "out of space" errors that
seem to be happening with Travis.

I'm hoping Travis uses the new .travis.yml, but I'm not sure if that's how it work.

I'm going to give @domenkozar a chance to look at it, we can merge this tomorrow and see if it still works then :)

What surprises me is that in https://travis-ci.org/NixOS/nixpkgs/builds/140654568 the Darwin build worked fine, but in the subsequent ones it always fails, due to payload['title'] apparently not having that key. Any idea what could be going on?
@madjar can you review this too?

I can't figure out why Nox keeps getting built… AFAICT it should be
available in the binary caches.
On Tue, Jun 28, 2016 at 1:22 AM Wout Mertens<EMAIL_ADDRESS>wrote:

What surprises me is that in
https://travis-ci.org/NixOS/nixpkgs/builds/140654568 the Darwin build
worked fine, but in the subsequent ones it always fails, due to
payload['title'] apparently not having that key. Any idea what could be
going on?
@madjar https://github.com/madjar can you review this too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/16563#issuecomment-228959116, or mute
the thread
https://github.com/notifications/unsubscribe/AABKXApfIQHeU6UIYi4QlsV4xfol1NV_ks5qQL2ggaJpZM4I_h7l
.

maybe nix-shell uses the cloned nixpkgs somehow? Maybe it tries the current dir first?

It looks like it's related to madjar/nox#26.

It's using nox-0.0.2 while nox-0.0.3 fixes the issue

nox-0.0.3 shold be in nixpkgs-unstable, right?

Okay nixpkgs-unstable is still at 0.0.2. https://github.com/NixOS/nixpkgs-channels/blob/nixpkgs-unstable/pkgs/tools/package-management/nox/default.nix

This PR is great!
The transient failure we are talking about is not really fixed in nox-0.0.3, and I explain in https://github.com/madjar/nox/issues/29#issuecomment-229607171 that it won't be easy to fix.

So I'm going to put this on hold until we can get the latest from nox pulled into master. I'm willing to sacrifice a personal access token if that's the only way to prevent the error. It might be safer to just create a dummy GitHub user and just use that. I can't imagine there's much you can do with a scopeless personal access token though.

I think this makes sense. It's easier to see what check actually failed without looking at logs.

Yeah, if we still get as many errors as we do now in Linux and OSX builds we could make the "nox-review pr" part optional because there's about a 50% chance the Travis build will just run out of space.

@madjar Could you bump the version of nox in nixpkgs in the next week or so so that I can put all of the Travis changes in one pull request?

@matthewbauer Here you go: https://github.com/NixOS/nixpkgs/pull/16700. I'll let you merge it :)

Ok, so once Travis gets "Nix" included as a language this should be okay to merge!

It looks like it's now available in production on Travis so this should be okay to merge!
https://travis-ci.org/matthewbauer/nixpkgs/jobs/144277096

@matthewbauer shouldn't we encrypt that github token?

@matthewbauer also i'm seeing we're hitting quite few times Github API limit. Does each Github API token get its own limit or is this tied to the Github account?

So, if we encrypt it, the variable will only be available to "trusted" builds. That excludes PR from a fork of nixpkgs which is what 99% of PRs to nixpkgs are. I decided to just make an account @nixtravis and create that personal token without any of the scopes so the damage done from it being public should be close to 0.
Without the API token, you get 60 requests/hour for each IP address. I think because Travis shares IP addresses it's hitting it much faster. Each GitHub token should get 6000 requests/hour so I think we should be okay sharing one for all Travis builds. We only need those when Nox builds pull requests so it shouldn't be an issue.

So everything seems to be working on some of the latest PRs:
https://travis-ci.org/NixOS/nixpkgs/builds/145050229
@domenkozar One thing I'm confused about is why Nix is trying to build some of these drvs on OS X instead of just downloading them:
these derivations will be built:
  /nix/store/10hbs719c0hl6lc7mgfli74cjscdgbs8-python3.5-characteristic-14.1.0.drv
  /nix/store/b9knv9dh1c98jiqg2l5cz1qw133a1vs0-git-2.9.1.drv
  /nix/store/y5lpr6grqrip3s6q1sz3zpmag3a32jn7-python3.5-dogpile.core-0.4.1.drv
  /nix/store/krzdmwdl25abmvc68nrda089ckgwlbnw-python3.5-dogpile.cache-0.5.4.drv
  /nix/store/gn5abmpxv0rlg19d9v60hiljh0kz1vz4-nox-0.0.4.drv

Shouldn't these be available in the binary cache?

Okay here's another one:
these derivations will be built:
  /nix/store/xi2g7593l27rlqsyq6b6jzzz9gb7kxn4-fontconfig-2.11.1.drv
  /nix/store/zcgq15si83ff1wy0xqcpyg1rc2sb5w7k-libXft-2.3.2.drv
  /nix/store/r6wv03mk53wgcvg6p33bnxl086l0sfiy-tk-8.6.4.drv
  /nix/store/2gfi1mp1cirwx1l04asrlqp9bl1a4453-python3-3.5.2.drv
  /nix/store/h51sh3iic8r6vl22yk52r4zg1q318q8l-hook.drv
  /nix/store/lc1nr4s3gw5nmf516miiwyrq3790v8cf-python-3.5.2-bootstrapped-pip-8.1.2.drv
  /nix/store/rz8javidgjay6dq6qkl4kl1nvn9bhwrl-python3.5m-setuptools-19.4.drv
  /nix/store/xx8qlcbn18fa0bshl6ycd1flfx787i7a-python3.5-py-1.4.31.drv
  /nix/store/jibbfz1ibxb9fbibqmnkqan757bnzj8c-python3.5-pytest-2.9.2.drv
  /nix/store/1k8x05ff2fb8i3hizihnp6avsjqpqjrm-python3.5-requests-2.9.1.drv
  /nix/store/3vswjlsqjwjz0mm200bfhri4g7qyr4mb-python3.5-characteristic-14.1.0.drv
  /nix/store/sx476is5v3kvn22r0pvskypk4n8apkx7-python3.5-dogpile.core-0.4.1.drv
  /nix/store/6kd4f1i6wml7bjzhyl6pvxdaqc1a8sn3-python3.5-dogpile.cache-0.5.4.drv
  /nix/store/8i0m3nmyxwhjyy7q7xlayxzhj1r65far-python3.5-pbr-1.8.1.drv
  /nix/store/9585mrb9a9s2b2qh0mpdc8ps5m993qd3-python3.5-click-6.6.drv
  /nix/store/b9knv9dh1c98jiqg2l5cz1qw133a1vs0-git-2.9.1.drv
  /nix/store/k23743dvs5hmsnixksrxhp7r8z5lly04-nox-0.0.4.drv

I don't know how the binary stores works to really understand this properly.

It looks like the issue is from using Nox and Git from master instead of from the channels.


add pod security labels

Adds pod security labels for backup and precaching namespaces. This is needed to allow these workloads to run privileged.
Signed-off-by: Vitaly Grinberg<EMAIL_ADDRESS>/cc @jc-rh  @sabbir-47

/lgtm

/cherry-pick release-4.11


seata支持redis集群么

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
store.mode配置为redis集群
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
Seata version:
OS :
Others:

sentinel & 主备

啥时候能支持啊，我们现场生产环境现在是基于pg数据库的，经常性的报TransactionException[Could not found global transaction xid = <IP_ADDRESS>:8081:1594602970694709515, may be has finished.] ，想切换成，然而redis又是集群模式

这个问题跟redis没有任何关系，官网faq好好看


[Bug]: Google Auth from Supabase JS client doesn't work on Appsmith

Is there an existing issue for this?

[X] I have searched the existing issues

Description
I would like to use Supabase JS client with the custom JS library feature. However, I can't use the Google Auth function provided by supabase.js directly by calling supabaseClient.auth.signInWithOAuth(), it appears that calling URL is blocked when executing JS code.
Calling the signin function should normally redirect the user to a Google official login screen, but in Appsmith gives an error:
Steps To Reproduce

In your Appsmith application, add the @supabase/supabase-js library.
Create a JS Object and write the neccesary code to create a new Supabase client, based on your credentials, and to sigin with Google OAuth authorization. The code should look like this:

export default {
  async myFun1() {
    const supabaseURL = '<<Your supabase URL>>';
    const supabasekey = '<<Your supabase Key>>';
    const ss = supabase.createClient(supabaseURL, supabasekey);
    await ss.auth.signInWithOAuth({
      provider: 'google'
    });
  }
};

Execute the JS Object function (myFun1 if you copied the code above) and look at the TypeError: Cannot set property href of [object WorkerLocation] which has only a getter error.
Note: To obtain the supabase credentials from your project, you can follow this guide.

Public Sample App
https://app.appsmith.com/app/cnv-118jjarw/page1-6490daf06298f54ae199fefd
Environment
Production
Issue video log
No response
Version
Cloud v1.9.24 / Self - Hosted v1.9.22

it's over a year now, is there any update? this is preventing me from using appsmith altogether.

@d-mok this is not a priority for us right now. You can use supabase as a database and connect to it using the postgres integration but not as an auth provider.


Multiple extensions

Adds a "Fake" and "Paket" extension alongside the "all-in-one" extension.
It's surprisingly simple to package a task into multiple extension. The question is if this leads to problems when multiple extensions contain the same task. Something left to test... I think I will add another round of extensions without public: true (which is the currently suggested official solution) and test on my instance.

Yeah, I think this might be more confusing than not (as we discussed) but happy to see how it feels when you test it out.

:(

Even if we decide to not publish the individual extensions I'd like to merge this PR because having them makes testing a bit easier for me. We can change the default publishing code. At the very least we need to public <> nonpublic switch and the bugfixes from this PR.

Ok I was able to get fake deployed on staging with these task. Even found a bug in the vault implementation of fake. But I'd this PR is working


Expose the Cobb's Angle tool from cornerstone.

PR Checklist

[ Expose the Cobb's Angle tool from cornerstone.] Brief description of changes
[ https://github.com/OHIF/Viewers/issues/2399 ] Links to any relevant issues
[ ] Required status checks are passing
[ ] @ a maintainer to request a review

Hello!
The code is implementing cobb's angle just fine, but the clear (trash) button is not deleting cobb's angle measures.
Any idea on how to solve this problem?

Closing in favor of https://github.com/OHIF/Viewers/pull/4127


valueLabels in the slider component are overlapping

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔

Maybe show the values inside of a tooltip-like component with a specific margin.
Current Behavior 😯

https://codesandbox.io/s/material-demo-h63rn

Context 🔦

I am using the slider component only to display a range with no user interaction. But if the min and max-values are too close to each other the labels are overlapping (see codesandbox link above). Ideally, inorder to be readable, they should not overlapp, and look like what is shown in the figure (with better css ;) ).
I have seen in the API docs, that we are able to pass an array for "marks", which can contain different marking styles for individual instances (https://material-ui.com/components/slider/#discrete-sliders). If it were possible to pass a rich-array for "values", it would do the trick.
Many thanks for your support and the wonderful project you have running.

@krupniok Reducing the size of the label helps a bit:

What visual output do you have in mind with the marks path?

Hi @oliviertassinari, thanks for answering. But, your solution will not help in generalizing my problem. Because, many times I am showing about 1% of the total range. In such cases, I will end up overlapping the two labels, even if I reduce the size.
I was a bit wrong about the "marks path". What I intented to say was, it would be good to somehow pass styling object along with the values, so that each value label can be styled differently. In my specific case, I would make the min-value left-aligned and the max-value right-aligned -- thereby, preventing overlapp.

it would be good to somehow pass styling object along with the values, so that each value label can be styled differently. In my specific case, I would make the min-value left-aligned and the max-value right-aligned -- thereby, preventing overlapp.

@krupniok You can provide your own ValueLabelComponent prop.  I have done a quick hack with the internal module. Maybe we could consider a stable solution to the problem

https://codesandbox.io/s/material-demo-y76cj
import React from "react";
import { withStyles, makeStyles } from "@material-ui/core/styles";
import Typography from "@material-ui/core/Typography";
import Slider from "@material-ui/core/Slider";
import ValueLabel from "@material-ui/core/Slider/ValueLabel";

const StyledValueLabel = withStyles({
  offset: {
    top: -28,
    left: props => props.index === 0 ? "calc(-50% + -20px)" : "calc(-50% + 12px)"
  },
  circle: {
    transform: props => props.index === 0 ? "rotate(-90deg)" : "rotate(0deg)"
  },
  label: {
    transform: props => props.index === 0 ? "rotate(90deg)" : "rotate(0deg)"
  }
})(ValueLabel);

const useStyles = makeStyles({
  root: {
    width: 300
  }
});

const MySlider = withStyles({
  root: {
    color: "#3880ff",
    height: 2,
    padding: "15px 0"
  },

  track: {
    height: 4
  },
  thumb: {
    background: "transparent",
    "&:focus,&:hover,&$active": {
      boxShadow: "inherit"
    }
  },
  rail: {
    height: 4,
    opacity: 0.5,
    backgroundColor: "#bfbfbf"
  },
  mark: {
    backgroundColor: "#bfbfbf",
    height: 8,
    width: 1,
    marginTop: -2
  }
})(Slider);

function valuetext(value) {
  return `${value}°C`;
}

export default function RangeSlider() {
  const classes = useStyles();
  const [value] = React.useState([31, 37]);

  return (
    <div className={classes.root}>
      <Typography id="range-slider" gutterBottom>
        Temperature range
      </Typography>
      <MySlider
        defaultValue={value}
        valueLabelDisplay="on"
        ValueLabelComponent={StyledValueLabel}
        aria-labelledby="range-slider"
        getAriaValueText={valuetext}
      />
    </div>
  );
}

In this case, it's probably best to display both values on the side.

When implementing this in TypeScript you'll get the error, "Could not find a declaration file for module '@material-ui/core/Slider/ValueLabel'" and will need to add a .d.ts file for ValueLabel.
I think this works:
import { ValueLabelProps } from '@material-ui/core/Slider';
declare const ValueLabel: React.ComponentType<ValueLabelProps>;
export default Slider;

The component is private, my demo isn't correct.

Hi, thanks for a great idea on how to make the range not overlap.
I tried recreating your codesanbox in material-UI v5 and I can't get the ValueLabelComponent to appear styled using withStyles. The props log is being fired, but no classes are being applied.
https://codesandbox.io/s/customizedslider-material-demo-forked-zpjbi?file=/demo.tsx
Thanks for any feedback! 👍


Reset icon cache on install

Add such a checkbox to the installer.

Don't care. No idea how to implement.


Traffic to DaemonSet port in another namespace is not allowed while no policies are defined.

Expected Behavior
Traffic to the DaemonSet port exposed on the Host IP should be allowed from the pod on different namespaces as no Calico or K8S policies are defined.
Current Behavior
Traffic to the DaemonSet port exposed on the Host IP is denied if the DaemonSet is on a different namespace than the namespace of the pod initiating a connection.
Context
Possibly issue could be related to all cross namespace traffic without policies applied.
Your Environment

Calico version v3.16.5
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes v1.19.3
Operating System and version:  Ubuntu 20.04.1 LTS Linux 5.4.0-54

Updating with Slack communication
lrobson  6 hours ago
Agree that this is unexpected.
Can you explain what you mean by "DaemonSet port exposed on the Host IP"?  Is this a Nodeport service or is that daemonset host-networked?
Artur Pietrzyk  6 hours ago
Something different.
Artur Pietrzyk  6 hours ago
The DeamonSet can be exposed to NodePort without the Service. It's defined in the DaemonSet Yaml.
Artur Pietrzyk  6 hours ago
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/.
Artur Pietrzyk  6 hours ago
My actual problem is with https://github.com/hashicorp/consul-helm/blob/master/templates/client-daemonset.yaml ports are exposed starting from 252 line.

Hi @Svisstack , what happens if you apply a policy that explicitly allows the host ports? I'm trying to distinguish if this is an issue with our policies or networking.

@mgleung I have no longer possibility to check that.

@Svisstack it's not clear to me how your pod is running. Is it doing one of the following?

DaemonSet running with hostNetwork: true?
DaemonSet running with hostNetwork:false, but hostPorts defined?
DaemonSet running with hostNetwork:false, but using a service NodePort?

Each of those is quite different, and so would be important to know.

Going to close this for now since it's stale, if you run into this again with details please reopen, thanks!


Builds on macOS 13 are randomly failing on all channels

Description
I've been trying to debug this all day and I'm getting no where it seems.
I'm randomly getting the following error on a macOS 13 GitHub Actions runner and locally on macOS 13.4, running v6.0.0 (which at first I thought had fixed it until another run later on revealed it hadn't):
Building the DMG failed. Error: Command failed: hdiutil detach /Volumes/AutoClicker

I'm not getting any more information out of it than that.
https://github.com/othyn/macos-auto-clicker/actions/workflows/cicd.yml
The really weird thing is there is no consistency or pattern that I can see as to whether it does it or not, it seems to be truly random from my current understanding, which is kind of evident from the mixture of succeeding and failing builds.
I've about ran out of steam on this today and I'll resume debugging with a fresh head tomorrow.
This wasn't an issue on macOS 12 using version 5.3.0, only after upgrading today to macOS 13 and v6.0.0 am I starting to have issues.
Also posted a bug report here: https://github.com/sindresorhus/create-dmg/issues/83
Version

= v1.6.2

Steps to Reproduce
Unknown at this time, appears to be random
Screenshots
No response
Device
Any Mac
Operating System
macOS 13.x
Additional Context
No response

I just don't understand. I had one successful build of both staging and main, then all successive builds since are failing again with the same error.
Succeeded: https://github.com/othyn/macos-auto-clicker/actions/runs/5432982099/jobs/9880382387
Errored: https://github.com/othyn/macos-auto-clicker/actions/runs/5433076720/jobs/9880546146
What. The. Fuck?
Could it be the caches? But that doesn't make sense as the two are running from the same cache, the later run using the cache that the first run created.
The environments are identical, versions and all.
I've even diff'd the instance logs and they are the same, except for the few commit message and version number changes for the app, oh and timestamps on the log lines to obviously.
This is one of those impossible to debug problems as well, as it seems no one else in the world has had this problem.

In typical fashion, the one time I want it to fail and it succeeds:
https://github.com/othyn/macos-auto-clicker/actions/runs/5439743287/jobs/9891992415
Ffs... oh well the next build will more than likely fail, maybe I should swap to using this:
https://github.com/advoryanskiy/fastlane-plugin-dmg

https://github.com/actions/runner-images/issues/7522

DMG's were hopeless, think its a bug with the runner. Just using zip's for now, does the same thing just not as nice/user friendly.


Get working under ECS/EKS

Originally from the https://github.com/Islandora-Devops/isle-buildkit/README.md

Get working under ECS/EKS

This ticket is from a time before we split the repo to have a separated isle-dc. The repository is now only responsible for constructing the images not for any orchestration. If we do eventually have a public implementation using ECS/EKS  it will live in a different repository and just consume the images produced by this one.


[DO NOT MERGE] pitzer version

Jupyter notebook on Pitzer
Three kernels available:

Temporary alert:

Issue:
Need Pitzer debug node information. The current version is using description from Owens.
       **debug** - (*1-40 cores*) For short sessions (= 1 hour) the debug queue
        will have the shortest wait time. This is only accessible during 8AM -
        6PM, Monday - Friday. There are 6 of these nodes on Pitzer.

Look here: https://www.osc.edu/supercomputing/computing/pitzer/queues_and_reservations Ends up there is Debug-regular and Debug-GPU. I'm not sure how to request Debug-GPU yet. @treydock any comments?

I'm going to keep this open, tag it, and make an rpm based on it.

I created a new repo for now: https://github.com/OSC/bc_osc_jupyter_pitzer

@ericfranz The debug reservation and gpu debug reservations on Pitzer are purposely omitted at this time.  There is also no debug queue defined.


feat: Add network filter to top collection

PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Needs Design check

@exezbcz please review

Context

[x] Closes #8816

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI;

Copilot Summary
copilot:summary
copilot:poem

uwu nice!
could you please align it

@exezbcz pls check again

last thing, mobile

last thing, mobile

can you elaborate? margin missing or/and should be at the end of the row
thanks

@hassnian yeah margin under the network button

hmmm, lets remove rmrk2 from the options, the top collection section is not visible on the network

would be nice if we would have top collections for rmrk2 as well, but not prio

@roiLeo yup, lets remove it then

cc @prury ?

Thanks!
pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 7.46 USD/DOT ~ 6.702 $DOT
🧗 13QUj3pZyFNfYj4AM336hRdyLQbevj5H3sR4PKmLEXLdwZhh
🔗 0xc0101a84db039c53ef7de9d8269e2045c76170cd42bc11f0d21d3eee9d68e574
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Predicate.Accumulates[varX, varY].If(...)

Add temporary tables (of sorts) to Predicates to simplify the following pattern:
Locations = FromCsv("Locations", "locations.csv", location, position.Key, founded, opening);
NewLocations = Predicate("NewLocations", location, position, founded, opening);
NewLocations.If(FreeLot[position], location == NewLocation["Location name", LocationType], ...);
Locations.Accumulates(NewLocations);

Ideally the pattern would allow for statements like:
Locations = FromCsv("Locations", "locations.csv", location, position.Key, founded, opening);
Locations.Accumulates[location, position, founded, opening].If(FreeLot[position], location == NewLocation["Location name", LocationType], ...);

OR (using the same variables specified in the Predicate):
Locations = FromCsv("Locations", "locations.csv", location, position.Key, founded, opening);
Locations.Accumulate.If(FreeLot[position], location == NewLocation["Location name", LocationType], ...);

One last want would be for these temporary tables to be accessible as a regular predicate in the case that there is some additional logic to be done on them. Above, NewLocations is used for some logic that drives tile generation and as such Locations.Accumulate would need to have similar accessibility. However, such cases may be better represented as separate predicates - as they already are - so this may not be needed.

Done, but ended up naming it Add rather than Accumulates


Players can bypass

Paperspigot configuration BungeeGuard:

BungeeGuard Configuration
Allowed authentication tokens.
allowed-tokens:

"DEoezLcojw6kHYZWnTNrghPW7BzxYXrbNlnPdL6jdkuuARnH8WmJYgNuCxLGByY1"

Messages
no-data-kick-message: "&cUnable to authenticate - no data was forwarded by the proxy."
no-properties-kick-message: "&cUnable to authenticate."
invalid-token-kick-message: "&cAn invalid authentication token was provided."

BungeeCord configuration BungeeGuard:
token: DEoezLcojw6kHYZWnTNrghPW7BzxYXrbNlnPdL6jdkuuARnH8WmJYgNuCxLGByY1
Informations:
Im not using Spigot, im using PaperSpigot
Im not using SkinRestored
Players can enter on skyblock without acces the BungeeCord, can you help me please?

You need to use Paper.
https://papermc.io/
BungeeGuard does not support Spigot.