The value of callback is not a function configuration ignored

I’m trying to add sign-in with google to my application. I got it working locally based on official documentation, but I’m struggling with enabling it on actual host on internet.

GET
https://accounts.google.com/gsi/select?client_id=1014735478743-it1gbsm9iakjanpoj3p9kvvi8b61875q.apps.googleusercontent.com&ux_mode=popup&ui_mode=card&as=5gG3et1z972I4LJaEFyjhw&channel_id=a9970cd95c0a5b31ea3706057c1695a493e30fcf6e20e6542376473331b53578&origin=http://li2241-254.members.linode.com

And it ends up with error “[GSI_LOGGER]: The given origin is not allowed for the given client ID.”

My configuration looks like this:

I got it working on localhost but what is wrong here?

I will answer myself: It only works for https. So after adding certificate and puting web traffic through it. I change addresses to https and it works. Response message could be more descriptive about that

I will answer myself: It only works for https. So after adding certificate and puting web traffic through it. I change addresses

Pass a named function callback to an old JS library

import { onCleanup, onMount } from "solid-js";

type Props = {

clientId: string;

};

export default (props: Props) => {

function onGoogleSignIn(googleUser: any) {

var profile = googleUser.getBasicProfile();

console.log("ID: " + profile.getId());

console.log("Name: " + profile.getName());

}

onMount(() => {

// TODO: generate random hash to append to function name

(window as any).__onGoogleSignIn = onGoogleSignIn;

});

onCleanup(() => {

delete (window as any).__onGoogleSignIn;

});

return (

<>

<div>

<div

id="g_id_onload"

data-client_id={props.clientId}

data-callback="__onGoogleSignIn"

></div>

<div class="g_id_signin" data-type="standard"></div>

</div>

<script src="https://accounts.google.com/gsi/client" async defer></script>

</>

);

};

GRBCallback#

classGRBCallback#

Gurobi callback class. This is an abstract class. To implement a callback, you should create a subclass of this class and implement a method. If you pass an object of this subclass to method before calling or , the method of the class will be called periodically. Depending on where the callback is called from, you can obtain various information about the progress of the optimization.

Note that this class contains one protected int member variable: . You can query this variable from your method to determine where the callback was called from.

Gurobi callbacks can be used both to monitor the progress of the optimization and to modify the behavior of the Gurobi Optimizer. A simple user callback function might call the or methods to produce a custom display, or perhaps to terminate optimization early (using ) or to proceed to the next phase of the computation (using ). More sophisticated MIP callbacks might use or to retrieve values from the solution to the current node, and then use or to add a constraint to cut off that solution, or to import a heuristic solution built from that solution. For multi-objective problems, you might use to interr

Property Page Callback Function

When a provider creates a property page for its device or device class, it supplies a pointer to a callback function. The callback function is called one time when the property page is created and again when it is about to be destroyed.

The callback is a PropSheetPageProc function that is described in the Windows SDK documentation. This function must be able to handle the PSPCB_CREATE and PSPCB_RELEASE actions.

The callback is called with a PSPCB_CREATE message when a property page is being created. In response to this message, the callback can allocate memory for data that is associated with the page. The function should return TRUE to continue to create the page or FALSE if the page should not be created.

Property pages for a device are destroyed when the user clicks OK or Cancel on the page's dialog box or clicks Uninstall on the Drivers tab.

When a property page is destroyed, the callback is called with a PSPCB_RELEASE message. The function should free any data that was allocated when the property page was created. Typically, this involves freeing the data referenced by the lParam member of the PROPSHEETPAGE structure. The