confirmPlatformPaySetupIntent / confirmPlatformPayPayment issues

Describe the bug
The following refers to iOS, we have not yet tested the functionality on Android.
confirmPlatformPaySetupIntent() does not seem to confirm the setup intent, ApplePay shows 'Processing' for a while and then shows 'Payment not completed'. The sdk returns an error 'The payment has been cancelled'.
Calling confirmPlatformPayPayment() with the setup intent secret seems to work according to the dashboard logs, but the application crashes immediately afterwards.
Additional context
clientSecret is returned from stripe.setupIntents.create() on the server

confirmPlatformPaySetupIntent(clientSecret)
ApplePay shows 'Processing' followed by 'Payment not completed'
Sdk return the error 'The payment has been cancelled' with the code 'Canceled'

The Stripe dashboard logs show that there was no attempt to confirm the setup intent:
1 POST /v1/setup_intents
2 POST /v1/tokens
{
  "pk_token_instrument_name": "Simulated Instrument",
  "pk_token_payment_network": "PKPaymentNetwork(_rawValue: AmEx)",
  "pk_token": "******",
  "pk_token_transaction_id": "ApplePayStubs~4242424242424242~0~USD~F3A35ADC-807D-4785-9A3E-7E5AF9BD59DC",
  "payment_user_agent": "stripe-ios/23.3.2; variant.legacy; STPApplePayContext; STPPaymentCardTextField"
}
3 POST /v1/payment_methods
{
  "type": "card",
  "card": {
    "token": "tok_1MPokBL5TYql0F3I6qUC1PxH"
  },
  "payment_user_agent": "stripe-ios/23.3.2; variant.legacy; STPApplePayContext; STPPaymentCardTextField"
}

confirmPlatformPayPayment(clientSecret)
ApplePay shows 'Processing' followed by 'Done'
Sdk crashes

The Stripe dashboard logs show that the setup intent was confirmed:
1 POST /v1/setup_intents
2 Post /v1/tokens
{
  "pk_token_instrument_name": "Simulated Instrument",
  "pk_token_payment_network": "PKPaymentNetwork(_rawValue: AmEx)",
  "pk_token": "******",
  "pk_token_transaction_id": "ApplePayStubs~4242424242424242~0~USD~F2294540-97F7-49FC-ABE7-FBA56D67E485",
  "payment_user_agent": "stripe-ios/23.3.2; variant.legacy; STPPaymentCardTextField; STPApplePayContext"
}
3 POST /v1/payment_methods
{
  "type": "card",
  "card": {
    "token": "tok_1MPoq2L5TYql0F3IgNZQcCei"
  },
  "payment_user_agent": "stripe-ios/23.3.2; variant.legacy; STPPaymentCardTextField; STPApplePayContext"
}
4 POST /v1/setup_intents/seti_1MPopnL5TYql0F3IBxurXLuz/confirm
{
  "use_stripe_sdk": "true",
  "client_secret": "********************************************************************",
  "payment_method": "pm_1MPoq2L5TYql0F3I6CbTUXbj"
}

Crash report:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: A61EA39E-3E95-4A45-B550-C9182D4B7F41
CrashReporter Key:   FE225A63-58CC-D89E-66AA-83F40719E775
Hardware Model:      MacBookPro17,1
Process:             AppName [81893]
Path:                /Users/USER/Library/Developer/CoreSimulator/Devices/98664955-822D-4F19-A31E-DB95B1E8F656/data/Containers/Bundle/Application/6D9DD687-982C-4E4B-B0E1-1CCFB115B565/AppName.app/AppName
Identifier:          com.appname.mobile
Version:             3.0.6 (4)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd_sim [25371]
Coalition:           com.apple.CoreSimulator.SimDevice.98664955-822D-4F19-A31E-DB95B1E8F656 [6194]
Responsible Process: SimulatorTrampoline [4040]

Date/Time:           2023-01-13 15:06:41.8325 +0000
Launch Time:         2023-01-13 15:04:51.1877 +0000
OS Version:          macOS 13.0 (22A380)
Release Type:        User
Report Version:      104

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000018bd55174
Termination Reason: SIGNAL 5 Trace/BPT trap: 5
Terminating Process: exc handler [81893]

Triggered by Thread:  0

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libswiftCore.dylib            	       0x18bd55174 _assertionFailure(_:_:file:line:flags:) + 308
1   libswiftCore.dylib            	       0x18bd55174 _assertionFailure(_:_:file:line:flags:) + 308
2   AppName                        	       0x105dae870 STPAPIClient.paymentIntentEndpoint(from:) + 860 (STPAPIClient+Payments.swift:382)
3   AppName                        	       0x105daedd0 STPAPIClient.retrievePaymentIntent(withClientSecret:expand:completion:) + 124 (STPAPIClient+Payments.swift:418)
4   AppName                        	       0x105daf278 @objc STPAPIClient.retrievePaymentIntent(withClientSecret:expand:completion:) + 256
5   AppName                        	       0x105daebe0 STPAPIClient.retrievePaymentIntent(withClientSecret:completion:) + 236 (STPAPIClient+Payments.swift:400)
6   AppName                        	       0x105daec8c @objc STPAPIClient.retrievePaymentIntent(withClientSecret:completion:) + 144
7   AppName                        	       0x10610c0d4 StripeSdk.applePayContext(_:didCompleteWith:error:) + 588 (ApplePayViewController.swift:187)
8   AppName                        	       0x10610d844 @objc StripeSdk.applePayContext(_:didCompleteWith:error:) + 128
9   AppName                        	       0x1058533a4 static STPApplePayContextLegacyHelper.performDidComplete(_:) + 1056 (STPApplePayContextDelegate.swift:80)
10  AppName                        	       0x105853844 @objc static STPApplePayContextLegacyHelper.performDidComplete(_:) + 56
11  AppName                        	       0x1059665d0 STPApplePayContext.callDidCompleteDelegate(status:error:) + 744 (STPApplePayContext.swift:667)
12  AppName                        	       0x105961300 closure #1 in closure #3 in STPApplePayContext.paymentAuthorizationControllerDidFinish(_:) + 76 (STPApplePayContext.swift:418)
13  AppName                        	       0x10582f588 thunk for @escaping @callee_guaranteed () -> () + 48
14  libdispatch.dylib             	       0x180133fa4 _dispatch_call_block_and_release + 24
15  libdispatch.dylib             	       0x180135768 _dispatch_client_callout + 16
16  libdispatch.dylib             	       0x180145018 _dispatch_main_queue_drain + 1220
17  libdispatch.dylib             	       0x180144b44 _dispatch_main_queue_callback_4CF + 40
18  CoreFoundation                	       0x180372ca4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
19  CoreFoundation                	       0x18036d360 __CFRunLoopRun + 1956
20  CoreFoundation                	       0x18036c7a4 CFRunLoopRunSpecific + 584
21  GraphicsServices              	       0x188ff7c98 GSEventRunModal + 160
22  UIKitCore                     	       0x11e72e37c -[UIApplication _run] + 868
23  UIKitCore                     	       0x11e732374 UIApplicationMain + 124
24  AppName                        	       0x104f17e5c main + 96 (main.m:8)
25  dyld_sim                      	       0x10a1fdfa0 start_sim + 20
26  dyld                          	       0x10a319e50 start + 2544

Is this happening in live mode or test mode?

This is in test mode

Are you passing any options to confirmPlatformPaySetupIntent / confirmPlatformPayPayment besides the client secret? Haven't been able to reproduce this so far so if you could share your callsite that would be useful

Yep, currently passing these options:
{
    testEnv: true,
    merchantCountryCode: 'GB',
    currencyCode: 'GBP',
    merchantName: 'test',
    allowCreditCards: true,
    existingPaymentMethodRequired: true,
  },
  applePay: {
    merchantCountryCode: 'GB',
    currencyCode: 'GBP',
    cartItems: [{
      label: 'test',
      amount: '9.00',
      paymentType: PlatformPay.PaymentType.Immediate,
    }],
  }
}

So a minimal reproduction would be...
stripe-react-native 0.23.0
react-native 0.69.7
Simulator running iOS 16.2
const handlePlatformPay1 = async () => {
  const clientSecret = 'seti_xxx'; // returned from stripe.setupIntents.create()
  const { error, setupIntent } = await confirmPlatformPaySetupIntent(clientSecret, {
    googlePay: {
      testEnv: true,
      merchantCountryCode: 'GB',
      currencyCode: 'GBP',
      merchantName: 'test',
      allowCreditCards: true,
      existingPaymentMethodRequired: true,
    },
    applePay: {
      merchantCountryCode: 'GB',
      currencyCode: 'GBP',
      cartItems: [{
        label: 'test',
        amount: '9.00',
        paymentType: PlatformPay.PaymentType.Immediate,
      }],
    }
  });
  if (error) {
    console.log(error);
  } else {
    console.log(setupIntent);
  }
};

const handlePlatformPay2 = async () => {
  const clientSecret = 'seti_xxx'; // returned from stripe.setupIntents.create()
  const { error, paymentIntent } = await confirmPlatformPayPayment(clientSecret, {
    googlePay: {
      testEnv: true,
      merchantCountryCode: 'GB',
      currencyCode: 'GBP',
      merchantName: 'test',
      allowCreditCards: true,
      existingPaymentMethodRequired: true,
    },
    applePay: {
      merchantCountryCode: 'GB',
      currencyCode: 'GBP',
      cartItems: [{
        label: 'test',
        amount: '9.00',
        paymentType: PlatformPay.PaymentType.Immediate,
      }],
    }
  });
  if (error) {
    console.log(error);
  } else {
    console.log(paymentIntent);
  }
};

<PlatformPayButton onPress={handlePlatformPay1 / handlePlatformPay2} />

Would it be possible to use createPlatformPayPaymentMethod() instead and then somehow confirm the setup intent afterwards?

I have the same problem, I've tried you solution, it works for me too. Thank you @tobydeh

Hm, the code you shared is working for me 🤔
@tobydeh is there anything substantially different in this screen vs your test screen:
export default function ApplePayScreen() {
  const [clientSecret, setClientSecret] = useState<String | null>(null);
  const { confirmPlatformPayPayment } = usePlatformPay();

  useEffect(() => {
    fetchPaymentIntentClientSecret();
  }, []);

  const fetchPaymentIntentClientSecret = async () => {
    const response = await fetch(`${API_URL}/create-payment-intent`, {
     ...
    });
    const result = await response.json();
    setClientSecret(result.clientSecret);
  };

  const pay = async () => {
    const { paymentIntent, error } = await confirmPlatformPayPayment(
      clientSecret as string,
      {
        applePay: {
          merchantCountryCode: 'GB',
          currencyCode: 'GBP',
          cartItems: [
            {
              label: 'test',
              amount: '9.00',
              paymentType: PlatformPay.PaymentType.Immediate,
            },
          ],
        },
      }
    );
    if (error) {
      Alert.alert(error.code, error.localizedMessage);
    } else {
      Alert.alert('Success', 'Check the logs for payment intent details.');
      console.log(JSON.stringify(paymentIntent, null, 2));
      setClientSecret(null);
    }
  };

  return (
    <PaymentScreen>
      <View>
        <PlatformPayButton onPress={pay} style={{ width: 200, height: 40 }} />
      </View>
    </PaymentScreen>
  );
}

The only difference is that your example is using a payment intent and we are using a setup intent, have you tried using the setup intent secret with confirmPlatformPaySetupIntent() / confirmPlatformPayPayment() ?

You can't use confirmPlatformPayPayment with a setup intent, but I found the issue with confirmPlatformPaySetupIntent and have opened a PR. We should publish the fix later this week!

I'm having issues using confirmPlatformPayPayment in Expo SDK 47.
Expo suggests using Stripe 0.19.0 but the latest is 0.25.0.

I've tried using 0.19 and 0.25.  For both instances when running locally I get the following error:
TypeError: _NativeStripeSdk.default.confirmPlatformPay is not a function. (In '_NativeStripeSdk.default.confirmPlatformPay(clientSecret, params, true)', '_NativeStripeSdk.default.confirmPlatformPay' is undefined)

The Apple Pay modal never appears.
Contrarily when I use useApplePay it opens the Apple pay dialogue as expected.  But notice that the api docs doesn't say the functions this hook returns are all deprecated.  What is even more bewildering is that even though they are deprecated, the functions still exist in the SDK so you can call them... So if you do this:
const { confirmApplePayPayment, presentApplePay } = useApplePay();
const handlePress = useCallback(async () => {
  const variables = {
    amount: Number(amount) * 100,
  };
  const {
    data: { response },
  } = await createPaymentSecret({
    variables,
  });
  const clientSecret = response;
  const { paymentMethod, error } = await presentApplePay({
    currency: 'usd',
    country: 'US',
    cartItems: [{ paymentType: 'Immediate', label: applePayLabel, amount }],
  });
  if (!error) {
// THIS NEVER HAPPENS BECAUSE I GET ERRORS with presentApplePay (but no details of what the issue is)
    const { error: confirmApplePayError } = await confirmApplePayPayment(
      clientSecret,
    );
    if (confirmApplePayError) {
      Bugsnag.notify(confirmApplePayError.message);
    } else {
      console.log('Success', 'The payment was confirmed successfully!');
    }
  } else {
    Bugsnag.notify(`Present Apple Pay Error: ${error}`);
  }
}, [confirmApplePayPayment, presentApplePay]);

the Apple pay dialogue opens but then it never completes the processing.
So then I try to do what is suggested above:
const { confirmPlatformPayPayment } = usePlatformPay();

const handlePress = useCallback(async () => {
  const variables = {
    amount: Number(amount) * 100,
  };
  const {
    data: { response },
  } = await createPaymentSecret({
    variables,
  });
  const clientSecret = response;
  const { paymentIntent, error } = await confirmPlatformPayPayment(
    clientSecret,
    {
      applePay: {
        merchantCountryCode: 'US',
        currencyCode: 'usd',
        cartItems: [
          {
            paymentType: PlatformPay.PaymentType.Immediate,
            label: applePayLabel,
            amount,
          },
        ],
      },
    },
  );
  if (!error) {
    console.log('Success', 'The payment was confirmed successfully!');
  } else {
    Bugsnag.notify(`Apple Pay Error: ${error}`);
  }
}, [confirmPlatformPayPayment]);

I get an error claiming that the function confirmPlatformPayPayment does not exist (see the beginning of this post).  What is awfully peculiar is that when I drill into the node_modules I see this function in lib/commonjs/hooks/usePlatformPay.js (its minified but I see it).

Maybe I'm digging up the wrong tree and I simply cannot use Stripe with Expo, even though the docs say otherwise?

When using Expo, you have to use Expo's suggested version, otherwise your JS code and native code don't mesh together. The PlatformPay API was introduced in v0.22.0, and the most recent Expo SDK (48) supports v0.23.3, so as long as you use SDK 48 you should be good to go

Upgrading to SDK 48 has improve the situation; however, I'm still getting an error 🤔
This is the code that I'm using:
const { confirmPlatformPayPayment } = usePlatformPay();

const handlePress = useCallback(async () => {
  const variables = {
    amount: Number(amount) * 100,
  };
  const {
    data: { response },
  } = await createPaymentSecret({
    variables,
  });
  const clientSecret = response;
  const { paymentIntent, error } = await confirmPlatformPayPayment(
    clientSecret,
    {
      applePay: {
        merchantCountryCode: 'US',
        currencyCode: 'usd',
        cartItems: [
          {
            paymentType: PlatformPay.PaymentType.Immediate,
            label: applePayLabel,
            amount,
          },
        ],
      },
    },
  );
  if (!error) {
    console.log('Success', 'The payment was confirmed successfully!');
  } else {
    Bugsnag.notify(`Apple Pay Error: ${error}`);
  }
}, [confirmPlatformPayPayment]);

Within Expo Go iOS Simulator the Apple Pay dialogue appears as expected but after requesting a payment I get the following error: "Your payment information is formatted improperly. Please make sure you're correctly using the latest version of our iOS library. For more information see https://stripe.com/docs/mobile/ios." from the confirmPlatformPayPayment() method.
This is what Stripe's logs say:

This is what the payment information looks like:
{
  applePay: {
    merchantCountryCode: 'US',
    currencyCode: 'usd',
    cartItems: [
      {
        paymentType: "Immediate",
        label: "$1.00 to buy 1 credit",
        amount: "1.00"
      },
    ],
  },
},

Which appears to conform to the docs.

The above code snippet works when in production (in TestFlight) but not locally, which is likely to be expected but the error is confusing.

In Android, im getting a crash issue with  confirmPlatformPayPayment (see the image below).
Please help!
My env:
"@stripe/stripe-react-native": "^0.33.0",
react-native 0.72.4

This is the code that I'm using::
const pay = async () => {
  const clientSecret = await fetchPaymentIntentClientSecret();

  const { error } = await confirmPlatformPayPayment(clientSecret, {
    googlePay: {
      testEnv: true,
      merchantCountryCode: 'CA',
      currencyCode: 'CAD',
    },
    applePay: {
      merchantCountryCode: 'GB',
      currencyCode: 'GBP',
      cartItems: [
        {
          label: 'test',
          amount: '9.00',
          paymentType: PlatformPay.PaymentType.Immediate,
        },
      ],
    },
  });

  if (error) {
    Alert.alert(error.code, error.message);
    // Update UI to prompt user to retry payment (and possibly another payment method)
    return;
  }
  Alert.alert('Success', 'The payment was confirmed successfully.');
};

@vietdung97 You'll need to upgrade your library version, there is a bug in 0.33.0


Add Blinker font as the main font for the app

Closes #90.
Adds the Blinker font from Google Fonts, as specified by @jtomeck. I also fixed the import of roboto to use the new css2 endpoint from google

I really love this font, but don't actually like how it's styled on the buttons. It looks out of vertical alignment for some reason. Do you guys agree? @JackWilb @waxlamp

It looks like the text is shifted down a little to me, yeah. Do you want to try pull the changes locally Jared and try playing with some different fonts until you find one that works better, @jtomeck?

I really love this font, but don't actually like how it's styled on the buttons. It looks out of vertical alignment for some reason. Do you guys agree? @JackWilb @waxlamp

It looks like the text is shifted down a little to me, yeah. Do you want to try pull the changes locally Jared and try playing with some different fonts until you find one that works better, @jtomeck?

If we're talking about the "name", "cluster", and "interacts" buttons, then they look a little bit (just barely) too high, if anything.
Changing the font again won't fix that issue; I assume it's some CSS magic that needs to happen. That being said, I'd suggest we merge this PR (if we're all happy with it), then file an issue to fix any alignment problems in a separate effort (since alignment is a separate problem from what font to use).


Crypt filter EFF key should have StmF value as default, not StrF

This fixes #5935.

/botio test

For verification, this is the exact location in the specification: https://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#page=65&zoom=auto,-274,714

well done, just for curiosity: how does one find such a bug without a document? Or do you have such doc, but you cannot share it?

I'm currently studing the PDF1.7 spec and comparing various implementations. The Adobe PDF1.7 spec as well as the ISO-32000-1:2008 spec (more or less equivalent to the Adobe PDF1.7 spec) are available online from Adobe, see @timvandermeij comment.

/botio-windows test

Thanks for the patch!


hasManyThrough Related question?

Exist method class:
class Users extends Model
{
    protected $table = 't_users';

    public function metas()
    {
        return $this->hasManyThrough('App\Models\UsersMeta', 'App\Models\DUsersMeta', 'id_user', 'id_meta');
    }
}

App\Models\UsersMeta - Table: t_users_meta
App\Models\DUsersMeta - Table: d_users_meta
DataBase Structure:

Users::meta->toSql() generate sql:
select * from t_users_meta inner join d_users_meta on d_users_meta.id = t_users_meta.id_meta where d_users_meta.id_user = ?
???  d_users_meta.id_user = ?
maybe it should be?
t_users_meta.id_user ?

Please post on the forums with more information. Laravel issues is not for support tickets

ok. sorry!

just wanted to ask casually is not a mistake ?? if the error is possible to consider as Bug

@taiyaei If this is a bug, then it's fine here. Please do not tell people where to post. Taylor and I do that.

It's belongsToMany not hasManyThrough relation, that's all. hasManyThrough won't work for hasMany - belongsTo chain.

Thanks. Sorry!


[Spike] Cookie Parsing

[x] Client-side setting of cookies
[x] Server-side setting of cookies
[x] Parse cookies in form processing

The premise of this is that cookies live in your app state.
Calling
app-state.get('cookies.user').update(function(){
  return {
    value: 'person',
    options: {
      httpOnly: true,
      secure: true
    }
  };
});

from anywhere will set cookies for that environment. When done server-side, it will tell the client to keep that cookie header. Options adhere to RFC6265 (uses https://github.com/expressjs/cookie-parser and https://github.com/jshttp/cookie behind the scenes)
The cookies state piece is populated on the server from client cookie headers and the app can access them that way.
To clear/unset a cookie:
app-state.get('cookies.user').update(function(){ return null });
Also fixed in this:

Form processing breaking when on-change handler not present (e.g. hidden input field)
Route observables not being called server-side (for both form processing and SSR)

:heart: this is brilliant.

I'm now thinking we could change the redirect API to go work through updating the route path in app-state instead of a special API call... :)
I'm a little worried about creating a massive state schema for these things though... Need to be careful with the balance.


CFP: Add workqueue metrics for cilium-agent

Cilium Feature Proposal
It would be helpful to add workqueue metrics such as the depth, current depth of a workqueue, and the latency, how long an item stays in a workqueue to monitor the agent's k8s watcher performance.
https://github.com/kubernetes/client-go/blob/5a019202120ab4dd7dfb3788e5cb87269f343ebe/util/workqueue/metrics.go#L73-L90
Resource[T k8sRuntime.Object] relies on workqueue(enqueue items on cache.ResourceEventHandler), and some watchers, such as the EndpointSlice watcher, are using it with the latest implementation.
https://github.com/cilium/cilium/blob/9dc8dae85b50415ce4483962e2b0efb9d170b39b/pkg/k8s/resource/resource.go#L339
Is your feature request related to a problem?
We sometimes see the agent's sync delay when a large number of Pods restart, and the following logs from client-go is appearing when delays occur.(v1.12) With the new Resource[T k8sRuntime.Object] implementation, we should monitor the workqueue instead of DeletaFIFO.
2023-04-17 19:09:48 level=info msg="Trace[1730758035]: \"DeltaFIFO Pop Process\" ID:app/moco-mysql-675dn,Depth:1026,Reason:slow event handlers blocking the queue (17-Apr-2023 10:09:48.471) (total time: 109ms):" subsys=klog

Describe the feature you'd like
Add workqueue metrics using workqueue.SetProvidor
(Optional) Describe your proposed solution
Currently, there's a conflict with the controller-runtime metrics registration. So we need to fix it.

Sounds like a good idea to me, cc @cilium/metrics

+1 to work queue metrics, they're arguably one of the most useful ones.

@joestringer @chancez Can this be done for the operator as well? I am seeing issues with IPAM initialization and this warning appears frequently:
2023-06-13T14:07:31.756702202Z level=info msg="Trace[1582166779]: \"DeltaFIFO Pop Process\" ID:kube-system/hubble-metrics-5cprm,Depth:2040,Reason:slow event handlers blocking the queue (13-Jun-2023 14:07:31.155) (total time: 600ms):" subsys=klog

Currently, there's a conflict with the controller-runtime metrics registration. So we need to fix it.

controller-runtime calls workqueue.SetProvider in its init function, and we can't use it to register the workqueue metrics to our registry because it can be called only once, and subsequent calls will be ignored.
controller-runtime registers the workqueue metrics to its registry using workqueue.SetProvidor in its init function here.
https://github.com/kubernetes-sigs/controller-runtime/blob/451530c09937350ff7f5ebf7a00d059b4334e8ee/pkg/metrics/workqueue.go#L99
github.com/cilium/cilium/operator/metrics imports sigs.k8s.io/controller-runtime/pkg/metrics
https://github.com/cilium/cilium/blob/be2cb2bcc5300c7c634d8d5596b7869f3e7799be/operator/metrics/metrics.go#L13
cilium-agent doesn't use controller-runtime, however, it has an indirect dependency on controller-runtime. For example, these are the dependency graphs below.
- github.com/cilium/cilium/daemon/cmd -> github.com/cilium/cilium/pkg/ipam -> github.com/cilium/cilium/pkg/ipam/metrics -> github.com/cilium/cilium/operator/metrics
- github.com/cilium/cilium/daemon/cmd -> github.com/cilium/cilium/pkg/ipam -> github.com/cilium/cilium/operator/watchers -> github.com/cilium/cilium/operator/pkg/ciliumendpointslice -> github.com/cilium/cilium/operator/metrics

I think that the root cause is that github.com/cilium/cilium/pkg/ipam depends on the operator's package.

The possible solutions:

Remove the dependency from github.com/cilium/cilium/pkg/ipam to github.com/cilium/cilium/operator/metrics
Add a feature to controller-runtime to opt out of automatic registration of metrics
Use controller-runtime metrics registry instead of Cilium metrics registry

Also, we need to create a rateLimitingQueue with a name like this to export workqueue metrics
workqueue.NewRateLimitingQueueWithConfig(rateLimiter, RateLimitingQueueConfig{Name: name})

We discussed this during the APAC call on 2023-06-20. Regarding this solution:

Remove the dependency from github.com/cilium/cilium/pkg/ipam to github.com/cilium/cilium/operator/metrics

It's surprising to us that daemon depends on operator packages. This should probably be cleaned up anyway, so it seems like a good target for the fix. If we dependency-inject the metrics, then the ipam package shouldn't need to depend on metrics.

I'm working on it
https://github.com/cilium/cilium/pull/27042


Add fixer for django.db.models.AutoField in Django 3.2

Description
I was migrating a Django 2.0 to 4.2 and Django complained about models.W042
app.MyModel: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the MyAppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

Based on the docs, if a primary key is not set for each model, Django will need either this key in settings DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' or a config  for each app.
from django.apps import AppConfig

class MyAppConfig(AppConfig):
    default_auto_field = 'django.db.models.AutoField'
    name = 'my_app'

Do you think it's possible to add a fixer to include the default_auto_field in each app?
I can work on it and make a PR.

No I don't believe this can be automatically fixed. Projects should choose which auto field they want, and sometimes on an app-by-app or model-by-model basis.


python3Packages.slugid: init 2.0.0

Motivation for this change
cos why not ...
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

cos why not ...

cos the slugid "library" has only 20 lines of code, which can be reduced to 16 lines
(the current default.nix has 28 lines)
# Licensed under the Mozilla Public Licence 2.0.
# https://www.mozilla.org/en-US/MPL/2.0
import sys, uuid, base64

def _ascii(s):
    if sys.version_info.major != 2 and isinstance(s, bytes):
        return s.decode('ascii')
    return s

def encode(uuid_):
    return _ascii(base64.urlsafe_b64encode(uuid_.bytes)[:-2])

def decode(slug):
    return uuid.UUID(bytes=base64.urlsafe_b64decode(_ascii(slug) + '=='))

def v4():
    return encode(uuid.uuid4())

def nice():
    s = v4()
    if s[0] == '-' or s[0] == '_':
      s[0] = 'f'
    return s


Change regex to match option v

Before this PR
Doesn't match client versions in the form Client Version: 4.7.12
After this PR

==COMMIT_MSG==
Match an option v in the client version text
==COMMIT_MSG==
Possible downsides?

Thanks for your interest in palantir/palantir-cloudpak, @yyli! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


Intl package: add NumberFormat support for multiple group sizes

This issue was originally filed by<EMAIL_ADDRESS>
Feature request for Intl NumberFormat:
Some number systems require more than one grouping size when formatting numbers. For example, see the Indian Numbering System, which groups by ten-thousands rather than by hundred-thousands: http://en.wikipedia.org/wiki/Indian_Numbering_System. This would render 1,00,000 rather than 100,000; which would require a number format of something like "#,##,##0"

This issue has been moved to dart-lang/intl#38.


Website link not working

When I click on the web link, it takes me to a 404 page.

Yeah, thanks nothing has been built on it yet, if you wanna pick it up,
it's cool
On Sat, 26 Mar 2022, 7:52 am Pelumi Eyitimonwa Akintokun, <
@.***> wrote:

When I click on the web link, it takes me to a 404 page.
[image: Screenshot_20220326-074910_Chrome]
https://user-images.githubusercontent.com/63044364/160228438-cbb1dc67-2c09-493f-af44-90c43c843ab0.jpg
—
Reply to this email directly, view it on GitHub
https://github.com/OSCA-Ado-Ekiti/tech-companies-in-africa/issues/15,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUJDDXZLBYWXLUH2YTKY4I3VB2X3HANCNFSM5RWEOMZQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ok. I can do that.

Thanks for picking up this issue
On Sat, 26 Mar 2022, 10:21 am Pelumi Eyitimonwa Akintokun, <
@.***> wrote:

Ok. I can do that.
—
Reply to this email directly, view it on GitHub
https://github.com/OSCA-Ado-Ekiti/tech-companies-in-africa/issues/15#issuecomment-1079647575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUJDDX7Y5UTYS7B56HCMPHDVB3JK5ANCNFSM5RWEOMZQ
.
You are receiving this because you commented.Message ID:
@.***>

Good day, all the names of the company and founders in the Json file are their twitter handles right? Also can I modify the Json file. I want to include the links to the websites in it so that one can click on the links to the website and twitter handles.

Yeah, sure , you can go ahead and modify it😃, thank you for your
contribution
On Wed, 30 Mar 2022, 1:37 pm Pelumi Eyitimonwa Akintokun, <
@.***> wrote:

Good day, all the names of the company and founders in the Json file are
their twitter handles right? Also can I modify the Json file. I want to
include the links to the websites in it so that one can click on the links
to the website and twitter handles.
—
Reply to this email directly, view it on GitHub
https://github.com/OSCA-Ado-Ekiti/tech-companies-in-africa/issues/15#issuecomment-1083087649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUJDDX3VJP56KMWUQKIKJATVCRDJ5ANCNFSM5RWEOMZQ
.
You are receiving this because you commented.Message ID:
@.***>

Cool, and you are welcome.


Dual procedural and object-oriented interface

Please try to implement this feature for one of nexts releases it is helpful. Such as other drives it would be nice have a class named sqlsrv.

Hello @sirio3mil can you please shed some more light on what is your feature request is here? Some more details around the scenarios and use case will help!
Cheers,
Meet

Hi @meet-bhagdev what I mean is the option to have not only f.e. sqlsrv_query but its version in OOP, just like mysqli.
For example, Mysqli have mysqli_query in a procedural way but have mysqli::query in an OOP enviroment.
Cheers

@sirio3mil This driver provides the sqlsrv_* functions. As far as a SqlSrv class goes that's just a waste of time since they are developing a PDO driver as well.
You can do like doctrine/dbal, and create your own wrapper for specific database engines though.
class SqlSrv extends SomeBaseClass
{
    public function __construct($dsnOrPdo = null)
    {
        $this->connect($dsnOrPdo);
        // ....
    }
}

Hi @dhazelett thanks for your comment but thats exactly what I have and thats why this is a request for new feature.
Regards.

We have no plans to develop another interface for this driver. Closing this issue.


Add DataFrame API: UnionAll, Subtract, Drop, DropNa

Add DataFrame API: UnionAll, Subtract, Drop, DropNa
Optimization on DataFrame Select API

Hi @jayjaywg, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Guan Wang). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Event bubble / leak to grand parent issue

Vue version
3.2.38
Link to minimal reproduction
https://kasheftin.github.io/vue3-event-bubble-leak/
Steps to reproduce

drag the item around
watch (console.log) the @change event triggers every time when items are resorted, hovewer there's no $emit(change) in the target component and the target component explicitly sets emits:['run'].

What is expected?
Events should not leak from the child component to the grand parent.
That's how it was in vue2.
What is actually happening?
@change event bubble/leak happens every time when 3-rd party component triggers something inside.
System Info
No response
Any additional comments?
Basically there're 3 components: root -> child -> draggable.
The root component has @change event listener.
The child component has nothing and it explicitly sets emits: ['run'] meaning it can emit run event only. It can not emit change event.
The draggable component is 3rd party. It does not matter how it works and what it emits. All that matter is it does not have @change event listener in the child component.
Basically, the vue2 logic was pretty straight-forward and simple. If a grand-child requires some property from grand-parent, it had to be specified in the intermediate component and passed down. The same happend with events - a child emits @change event which is required to be caught on grand-parent, then the intermediate component had to have explicit @change=$emit('change', $event). It was a bit verbose, but it worked like a charm.

In Vue 3, all event listeners passed to a component which are not declared in that component's emits, will be applied as native event listeners to the root element.
https://vuejs.org/guide/components/attrs.html#v-on-listener-inheritance
In Vue 2, you could create the same issue by adding the .nativelistener:
<Child @change.native="handler" />

Now, is it a bit easier to accidentally pass a native event when you don't want to in Vue 3 compared to Vue 3? Yes. But it's not a bug, you can handle it yourself.
So that's how it works for now. We can think about changing it someday in Vue 4, but for the foreseeable future that's how it is.

Thanks a lot!
You are correct - if emits option includes change, then the @change event does not leak to the grand parent. But a few questions still remain:

Since it worked differently in vue2, would not it be reasonable to implement a configurable setting defining if the non-specified event should pass through the component? There's inheritAttrs prop, it might be something like passChildEventsThrough default to true.

The https://kasheftin.github.io/vue3-event-bubble-leak/ code was updated. emits prop is not specified intentionally. The question is about this line: https://github.com/Kasheftin/vue3-event-bubble-leak/blob/61784ac38a3a13f9c38ef94bf45ddf8db50c6aa4/src/Test1.vue#L6. Some component has @change event listener. It's natural to expect that any change event emitted inside will be caught by the listener. However this does not happen. The demo shows that while an item is being dragged, the change event popups up in the grand parent, going around change event listener in Test1.vue. Then, only on mouseup, the correct change event happens. I would be grateful for any clarification of what's going on there.

About 1:  I think ìnheritAttrs: false is allowing for what you want, pretty much.
All you would maybe need to do is filter any properties starting with on[A-Z] from $attrs and you have an object that contains only parent attributes, not parent listeners.
About 2: Seems like the implementation of that <draggable> component triggers a native change event -which bubbles up- at a different point in time before it emits a custom change event. A general recommendation would be to not use event names that mirror native events that are also triggered. While I am aware you are not in control of this library's implementation, you could emit a differently named event yourself.
If you have additional questions towards this specific example, please use the repo's discussion feature or our discord to discuss it with the wider community.


code_base64 from string -> string[] for loadcppplugin

在browser中CPP plugin支持上传多个插件，修改了tugraph-db的proto文件，需要对应修改web（只修改了参数类型，实际在web中依然只能上传一个文件）
code_base64： string -> string[]
新增 file_name: string[]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhangyan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


How to draw rect on image/slice at correct position

Hi,
I'd like to

Click link to navigate and go to a slice by calling switchToImageByIndex(imageIndex)
Draw a rectangle on display image(slice)

I've done

I can draw by below code but the position of rectangle is incorrect.
At first time series display, I click "View slice", the rect position is incorrect.
If I click any button (on header menu), the position of rectangle is moved to new one that as my expected. Please find the attach.
What is my wrong? How can I draw at correct position as my expected one?
I think I need convert the coordinate system but no way. Please help me.
Template.XXX.events({
	'click ul li a'(event) {
	   ...
	   const $element = $('.imageViewerViewport');
	   $element.on('cornerstoneimagerendered', onImageRendered);

	}
})
const onImageRendered = (event, eventData) => {
    const detectedSopInstanceUId = Session.get("detectedSopInstanceUId");

    const instance = aiUtils.getViewportInstanceInfo();
    const currentSopInstanceUid = instance.sopInstanceUid;
    // Checl sopId
    if (currentSopInstanceUid == detectedSopInstanceUId) {

        // Call mark
        drawRect();
    }
}

function drawRect() {
    ....
    const canvas = activeViewport.querySelector('canvas');
    const context = canvas.getContext('2d');

    context.beginPath();

    // Mark rectangle
    context.strokeStyle = 'red';
    context.lineWidth = 2;
    context.rect(Number(currentPosition.x) - area/4, Number(currentPosition.y) - area/4, area/2, area/2);
    // Draw
    context.stroke();
}

Hmm.. I'm not 100% sure why you're seeing an initially incorrect placement. It looks like the code snippet you've included is incomplete. Either way, if you're trying to display an annotation, and you want it to be correctly positioned, you'll likely want to work with the underlying cornerstone.js and cornerstoneTools.js APIs instead of drawing directly on the canvas yourself.
Those libraries take into account viewport scaling, translation, etc. As well as a host of other factors that might be prohibitive to account for in a one-off custom annotation.
Cornerstone already supports rectangle annotations, and the OHIF Viewer has this tool added:

You would likely want to "restore state" for the rectangle roi tool using the stateManagement exposed by cornerstone-tools: https://github.com/cornerstonejs/cornerstoneTools/blob/master/src/index.js#L142-L149

Hi @dannyrb,
Yes, you're right! I've done by calling cornerstoneTools.addToolState(element, 'rectangleRoi', measurementData) . Thank you so much!
I have a trouble.
When series display, I click "view slice" slices will scroll to my slice (eg, slice index 40) automatically and draw rectangleRoi on. How can I wait until my slice display and then draw the rect?
Now when I click "View slice" the rect will be drew on current display slice and then scroll to my slice without rect.

@iam0620, cornerstone emits an event each time a new image is rendered. You can listen for the event, and add the rect when the ID matches the one you expect?
For a list of events, check out the cornerstone repository.
Also, most tooldata is specific to an image ID. Cornerstone tools should conditionally render the annotation when the corresponding image is displayed.

Thanks @dannyrb
I changed my above drawRect() to as below and the rect is drew correctly when click "View slice".
I draw the rect in onImageRendered = (event, eventData){} event and only when currentSopInstanceUid == detectedSopInstanceUId (scroll image sop instance = expected sop instance)
However, The zoom,  pan tool don't work on the current slice/image (that the rectangleRoi is drew) . The view state always returns to the initial state (state when scrolling to and drawing rect firstly)  after doing zoom/pan action.
(I think due to  cornerstoneTools.addToolState(element, 'rectangleRoi', measurementData) )
Could I need to check if zoom/pan event, don't  do rectangleRoi?
function drawRect() {
    const activeViewport = Viewerbase.viewportUtils.getActiveViewportElement();

    if (!activeViewport) {
        // No selected main viewer
        return;
    }

    const canvas = activeViewport.querySelector('canvas');
    const context = canvas.getContext('2d');

    const enabledElement = Viewerbase.viewportUtils.getEnabledElement(activeViewport);
    var element = enabledElement.element;

    cornerstone.enable(element);

    // x: 357.841, y: 95.88900000000001
    var start = {x:Number(currentPosition.x) - area/4, y:Number(currentPosition.y) - area/4};
    // end = {x: 135, y: 135}
    var end = {x:(start.x + area/2), y:(start.y + area/2)};

    // Rect data
    const measurementData = {
                                visible: true,
                                active: true,
                                invalidated: true,
                                handles: {
                                    start: {
                                        x: start.x,
                                        y: start.y,
                                        highlight: true,
                                        active: false
                                    },
                                    end: {
                                        x: end.x,
                                        y: end.y,
                                        highlight: true,
                                        active: true
                                    },
                                    textBox: {
                                        active: false,
                                        hasMoved: false,
                                        movesIndependently: false,
                                        drawnIndependently: true,
                                        allowedOutsideImage: true,
                                        hasBoundingBox: true
                                    }
                                }
                            }

    // Clear and re-draw
    cornerstoneTools.clearToolState(element, 'rectangleRoi');
    cornerstoneTools.addToolState(element, 'rectangleRoi', measurementData)
}

Hi @dannyrb
No any exceptions  in my console.
When zooming or panning, onImageRendered = (event, eventData){} event trigger looply and of course it call cornerstone.enable(element) and draw rectangleROI . It is causing my issues.
I dived deeply investigation but I can not find how to check an element is already enable to don't call cornerstone.enable(element) again as well as how to check exptected image is displaying?.
When "View slice" clicked, I get into debug mode at onImageRendered = (event, eventData){} event, imageId value is my expected image but actually imageId doesn't display/scroll to yet (current displaying image isn't my expected)
I would be appreciated if you could help!

怎么实现随鼠标移动画封闭图形算面积

How to realize the area of closed graphics with mouse moving painting

@Iam0620, sorry for the delay. It's getting a bit hard to follow which parts you are doing yourself, and which parts are being handled by cornerstone tools. If I'm going to help further, I would appreciate:

A fork of this repo with only your changes applied
What your current result is, versus your expected result

The hope is that what you're asking should only require adding toolstate to the rectangle tool. So I'm not sure where the disconnect is. Any additional context you can provide to help would be :fire:

Hi @dannyrb
I've just solved my issues.
I check sopInstanceUid is my expected SopId and current element has no toolData, made rectangleRoi.
toolData = cornerstoneTools.getToolState(element, 'rectangleRoi');
Thank you for your support.


Handle Insufficient Capacity when starting instances

#599 minimizes the effect, by partitioning calls per type/zone, afaics the only option we have on improvements is configuring an optional auto purchasing of scheduled reserved.


WIP: Add very basic Certificates based conformance suite

What this PR does / why we need it:
Adds a very simple set of conformance tests that can be run against any Issuer implementation.
Initially this covers a very basic set of functionality, but we can expand this suite and eventually move all issuer types to share a common set of tests 😄
Special notes for your reviewer:
I'm still iterating on this, and opening it now to get some feedback from the e2e test job
Release note:
NONE

/retest

/lgtm


fix: SQL -> Explore Overwrite flow

SUMMARY

In prod overwrite flow causes an error when landing in the explore view. We've fixed this by doing a refresh before returning the payload on update.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Goto SQLLab
Write and run query
Click Explore
Save as new query
Edit query in SQLLab
Save as overwrite
Verify explore view doesn't throw an error

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


Revert EditorList type changes

Revert some of the changes introduced in https://github.com/grafana/grafana-experimental/pull/56 regarding EditorList type changes.
This is needed to safely update the version of this package in grafana, which at the moment crashes, see https://github.com/grafana/grafana-experimental/issues/68.

@jackw I agree, I don't have much knowledge on this repo and am open to any recommendations on who to add in the reviewer list. It seems that many of the people that know the codebase are on leave and this PR needs to be merged asap to unblock our colleagues. Not sure who to connect with.


Upgrade tar version

The current version of tar being used has a vulnerability.

Overview
The tar module earlier than version 2.0.0 allow for archives to contain symbolic links that will overwrite targets outside the expected path for extraction.
Remediation
Update to a version 2.0.0 or greater

https://nodesecurity.io/advisories/57

"tar": "~2.2.1",


Add Etherspot

Added Etherspot - Account Abstraction development platform
Web: https://etherspot.io
Docs: https://etherspot.fyi

Can you run npm run lint and modify project-words.txt so the lint checker passes? @arddluma

hey,
Apologies for late reply. Could you please double check ?
Thank you!

hihi looks like lint is still failing?
/home/runner/work/doc.zk-evm/doc.zk-evm/docs/build-on-linea/tooling/account-abstraction/etherspot.md:13:6 - Unknown word (Skandha)
/home/runner/work/doc.zk-evm/doc.zk-evm/docs/build-on-linea/tooling/account-abstraction/etherspot.md:15:6 - Unknown word (Arka)

@arddluma

lol I did run it locally and it passed just fine.

hihi looks like lint is still failing?
/home/runner/work/doc.zk-evm/doc.zk-evm/docs/build-on-linea/tooling/account-abstraction/etherspot.md:13:6 - Unknown word (Skandha)
/home/runner/work/doc.zk-evm/doc.zk-evm/docs/build-on-linea/tooling/account-abstraction/etherspot.md:15:6 - Unknown word (Arka)

@arddluma

one more try ?!

LGTM

yoooo finally 🔥🔥🔥
ty


Crashes Godot on my Windows 10 Machine

This approach looked very promising unfortunately I noticed cracks and pops in the sound probably from the microphone de / activation process involved in this.
(and when I use the microphone effect like that on my (and others) machines running Windows 10 in some more sophisticated application, we suffered from Godot Engine crashes which seemed to be caused by the microphone effect but for now it was not really possible to tackle these crashes down to the exact point of failure)

Have not been able to reproduce this problem. Likely a internal Godot issue if it still exists.


Epub output file (for issue #96)

Summary
This PR uses the mdbook-epub crate to generate an epub file so I can read the book on an ebook reader.

[ ] 👯 This PR is not a duplicate
[ ] 📬 This PR addresses an open issue
[ ] ✅ This PR has passed CI

mdbook-epub wants mdbook 0.1, I'll open a PR for mdbook-epub to update


kubeadm reset unmounts /var/lib/kubelet

This is to document the behavior of kubeadm reset that unmounts /var/lib/kubelet (regression since 1.15).
cc: @neolit123

thanks
/lgtm
/assign @tengqm

/approve


[Cherry-pick 2.2][BugFix] Late recycle if repair tablet from recycle bin (#8254)

Submitting repair tasks only if no expired db/table/partition involved to avoid NPE when tablet is added after its db/table/partition is dropped.
Fixes #6776
Note: This is not exactly a cherry-pick from #d0c8eb082eb6ca5fd2bf6b4543e3d351bafa66bb. Lots of conflicts are handled manually.

run starrocks_fe_unittest


AlwaysOn Profiler - Native code naming convention

Why & What
Native code naming convention based on Google recommendations
https://google.github.io/styleguide/cppguide.html#Naming
Version delivered by ReSharper C++
Tests
CI

Proposals (can be as different PR):

can you describe how to configure it in Rider/Resharper https://github.com/signalfx/signalfx-dotnet-tracing/blob/main/docs/internal/developing.md ?
can we make Nuke target for it and run it also on CI? we could use clang-format to achieve it

We can then add it to https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation

The easiest way is to commit generated *.sln.DotSettings then it will be shared by the repository by all developers.
I decided to not commit because in on our case it is one time job.
I have cleaned newly created code but other parts should be untouched - as we are making upstream syncs.
If you want to set up this Resharper C++ configuration you should
Extension -> ReSharper -> Manage Options - Solution Team-shared (double click) -> Code Editing => C++ -> Naming Style -> Reset To Scheme -> Google


New version: CombinatorialEnumeration v0.1.2

Registering package: CombinatorialEnumeration
Repository: https://github.com/kris-brown/CombinatorialEnumeration.jl
Created by: @kris-brown
Version: v0.1.2
Commit: 1298d489528f25004de56445939faa5bb789ebc9
Git reference: HEAD
Description: Enumerate models of finite limit sketches up to isomorphism

@kris-brown did you skip a version number on purpose?  What exactly do you want to do? (Please be clear, I can't read minds yet)
[noblock]

Sorry, I missed github-actions' message 10 days ago, thanks for the reminder! Skipping version numbers was definitely an accident! This PR can be closed now. I will register v.0.1.1 soon.


Pilz Industrial Planner fails to compute plans with collision objects in the planning scene

Description
When using the Pilz Planner, if a collision object is in the planning scene between some starting and ending point, the planner fails to find a path around the object. This is confirmed when testing with OMPL and it's ability to find a valid path around the object in the surrounding free space.
Your environment

ROS Distro: Humble
OS Version: 22.04.5 LTS
Source or Binary build? Binary
If binary, which release version? 2.5.5-Alpha
If source, which branch? N/A

Steps to reproduce
This was utilizing a customized URDF with a custom end-effector. However, it's based on a UR robot. This was tested with some other robot configurations we have.
General Process:

Launch Robot/Controller interfaces (Gazebo is what we're testing with)
Launch Move Group interfaces
Utilizing the Motion Planning plugin on Rviz, Move the robot to some point in space.
Use the Scene Objects tab to create a box that is near the end effector of the robot and publish to the scene.
Using Context select pilz_industrial_motion_planner and select PTP.
Move the robot through the center of the collision object.
Attempt to plan.

Expected behaviour
A collision free path around the collision object is found, and previewed.
Actual behaviour
I see the planner previewing a plan that's a direct path through the collision object, and returns a failure.
Backtrace or Console output
Just to show output, thisis my current pilz_industrial_motion_planner_planning.yaml:
planning_plugin: pilz_industrial_motion_planner/CommandPlanner
request_adapters: >-
  default_planner_request_adapters/FixWorkspaceBounds
  default_planner_request_adapters/FixStartStateBounds
  default_planner_request_adapters/FixStartStateCollision
  default_planner_request_adapters/FixStartStatePathConstraints
default_planner_config: PTP
capabilities: >-
    pilz_industrial_motion_planner/MoveGroupSequenceAction
    pilz_industrial_motion_planner/MoveGroupSequenceService

Obsolete


First Contribution by Himangi Malik

Name: Himangi Malik
Project assigned: PySAL
Link to official webisite: http://pysal.org/
Link to Github https://github.com/pysal/pysal
Link to Governance model:https://github.com/pysal/governance
PySAL, the Python spatial analysis library, is an open source cross-platform library for geospatial data science with an emphasis on geospatial vector data written in Python. It supports the development of high level applications for spatial analysis, such as

detection of spatial clusters, hot-spots, and outliers
construction of graphs from spatial data
spatial regression and statistical modeling on geographically embedded networks
spatial econometrics
exploratory spatio-temporal data analysis

GOVERNANCE MODEL
The governance of PySal is led by a group of core developers who oversee the technical direction of the project. The core developers are responsible for making decisions about the library's design, features, and functionality. They are also responsible for reviewing and merging pull requests submitted by contributors.  The community welcomes contributions from anyone, regardless of their level of expertise. The governance process is guided by a code of conduct that promotes respectful and constructive communication and behavior.
Decisions regarding the future direction of PySal are made through a combination of discussion, consensus-building, and voting. The community uses various communication channels, including mailing lists, GitHub issues, and social media, to discuss and collaborate on issues related to the library's development
The foundations of Project governance are:

Openness & Transparency
Active Contribution
Institutional Neutrality

Traditionally, Project leadership was provided by a Benevolent Dictator for Life (BDFL: Sergio Rey) and a subset of Contributors and Package Maintainers, called Core Developers, whose active and consistent contributions have been recognized by their receiving “commit rights” to the Project GitHub repositories. In general all Project decisions are made through consensus among the Core Developers with input from the Community.. In summary, the governance model of PySal is community-led and transparent, with core developers responsible for the technical direction of the project and the community working together to maintain and improve the library.
DECISION MAKING PROCESS
The decision-making process of PySal is community-driven and follows a transparent and inclusive approach. The community welcomes input and contributions from anyone interested in the development and improvement of the library. The process for making decisions in PySal typically involves the following steps:

Discussion: A topic or issue is raised on one of the communication channels, such as the PySal mailing list or GitHub issue tracker. The community members are encouraged to provide their opinions, insights, and suggestions on the issue.
Consensus-building: The community strives to build consensus on the topic or issue under discussion. This involves active listening, acknowledging differing viewpoints, and finding common ground among the participants.
Voting: In some cases, a decision may be put to a vote to determine the preferred course of action. Typically, the community uses a simple majority voting system to decide.
Implementation: Once a decision is made, the core developers and community members work together to implement the agreed-upon solution.
Throughout the decision-making process, the community follows a code of conduct that promotes respectful and constructive communication and behavior. The PySal community also seeks to be transparent in its decision-making by documenting the process and outcomes in public forums, such as mailing lists, GitHub issues, and documentation.

During decision making by the Steering Council, they will then utilize a voting system similar to that of the Apache Foundation. This is a structured version of consensus, where +1 votes indicate agreement, -1 votes are vetoes (and must be supported by the justification mentioned above), and one can even vote fractionally (e.g., -0.5, +0.5) to convey a viewpoint without filing a full veto. These numerical votes are frequently used informally to gauge public opinion on a subject, therefore they shouldn't typically be interpreted as official votes. A formal vote only takes place when it is officially proclaimed, and if it does, it should be kept available for at least one week to allow all interested Council Members to respond.
PROJECT ROLES

BDFL (Benevolent Dictator For Life)
Package Maintainers
Steering Council Members
Release Managers

How hard was it to understand the governance model?
Given my extensive experience of data analysis, it was fairly easy for me to understand the governance model. Very clear-cut and precise information was available on the Github pages.

@arliss-NF Eagerly waiting for your input in this!

Hi @Himangi-Malik - thanks for completing your first task.  I am trying to use the links you provided; however, they do not seem to work.  Could you please take a moment to check them and ping me again?  Thanks so much.


Improve User-Friendly Error Message for Nonexistent Search Results

Problem:
Currently, when a user searches for items that do not exist, we display a generic error message. This error message doesn't provide a positive user experience and can leave users feeling frustrated or lost.
Suggested Improvement:
We should enhance the user experience by providing a more user-friendly error message along with a relevant image. This will help users understand the situation better and guide them towards a solution or alternative action.

please assign me this issue . I will do my best to generate PR as soon as possible

I am interested to work on this issue. Please assign me

Assign this to me @Anandsg

What abt this?


Cannot set headers after they are sent to the client

Hello i reduced the code for login page to this.
  @ResolveField(() => Account)
  async login(
    @Args("input") { service, params }: LoginInput,
    @Context() context: any
  ): Promise<Account> {
    const auth = await context.authenticate("graphql-local", {
      email: params.email,
      password: params.password,
    });
    context.login(auth.user);
    return {
      id: auth.user.id,
      user: auth.user,
    };
  }

Yet still i receive and error when i try to login the user. The error disappears when i remove context.login(auth.user) function.
(node:432) UnhandledPromiseRejectionWarning: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client

at ServerResponse.setHeader (_http_outgoing.js:518:11)

at ServerResponse.header (/ftw/node_modules/express/lib/response.js:771:10)

at ServerResponse.send (/ftw/node_modules/express/lib/response.js:170:12)

at ServerResponse.json (/ftw/node_modules/express/lib/response.js:267:15)

at ExpressAdapter.reply (/ftw/node_modules/@nestjs/platform-express/adapters/express-adapter.js:24:57)

at ExceptionsHandler.handleUnknownError (/ftw/node_modules/@nestjs/core/exceptions/base-exception-filter.js:33:24)

at ExceptionsHandler.catch (/ftw/node_modules/@nestjs/core/exceptions/base-exception-filter.js:17:25)

at ExceptionsHandler.next (/ftw/node_modules/@nestjs/core/exceptions/exceptions-handler.js:16:20)

at /ftw/node_modules/@nestjs/core/router/router-proxy.js:24:35

at Layer.handle_error (/ftw/node_modules/express/lib/router/layer.js:71:5)

at trim_prefix (/ftw/node_modules/express/lib/router/index.js:315:13)

at /ftw/node_modules/express/lib/router/index.js:284:7

at Function.process_params (/ftw/node_modules/express/lib/router/index.js:335:12)

at next (/ftw/node_modules/express/lib/router/index.js:275:10)

at Layer.handle_error (/ftw/node_modules/express/lib/router/layer.js:67:12)

at trim_prefix (/ftw/node_modules/express/lib/router/index.js:315:13)

(node:432) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

(node:432) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

What might cause the error ?

@dayrim this not really clear why that error happens. Might be good to probe it


[TypeScript] Rename overloaded type "Icon" in StepButton.d.ts

In my "mui to react-native" effort I need to have all enums, interfaces and types in single ambient d.ts file. StepButton's Icon is last duplicity.

Looks like this broke an import.

Ok, I am closing this PR, thanks for cooperation.

You didn't have to close it, you could've just fixed the import 🙂

It is not the error, only inconvience when you need to have all definitions in a single namespace.
In this case, Stepper/StepConnector.d.ts  and StepButton.d.ts both export Icon symbol.

I understand, and I think it's a good change because it makes the types unambiguous for import-completion purposes. So I would merge it if you fixed the build error.

Do you mean to change both Typescript and flow part of the problem (it means StepLabel.js, StepLabel.ts, StepButton.js, StepButton.ts files)?
E.g. change also Icon name in Stepper/StepButton.js too?
export type Icon = Element<any> | string | number;
==>
export type StepButtonIcon = Element<any> | string | number;

Feel free to change the Flow definitions as well, although I think that's less important since Flow seems to be broken and may be getting removed from the project soon.

Ok

Stepper/StepLabel.d.ts, Stepper/StepButton.ts and Stepper/StepConnector.d.ts modified


Space Travelers Hub: Mission badge

Activities done:

[x] Change badges according to status.
[x] Style the layout as per design.
[x] Add every joined mission in the profile section.

Thank you so much @edenlisk.


[Question] Is there a proper way to control modern laser printers to print on dot level?

Do you know a way to control modern laser printers (I use Brother MFC-9342CDW) so that they print really "dot-by-dot" ?

Back in the days, there was a raster image processor (RIP) and it's job was to convert stuff like postscript to a exact raster image which was then printed by the printer. The RIP had to be matched to the printer and the data flow between RIP and printer was usually proprietary. Usually you had many options and settings you could tweak on the RIP and were able to get pixel-perfect printouts.
Now the RIP is usually integrated into the printer and you just have very few options you can tweak. Also the printer do tricks like half-dots which further blurs the lines.
Only film exposer equipment still has RIPs with pixel-exact exposure.
So I guess you have to tweak your printout by moving and scaling the picture a bit and analyzing the results under maginfication.


[3.x] Fix 3D moving platform logic

3D physics port of #50166 on 3.x (master version: #51457)
Fixes #30311
Co-authored-by: @fabriceci
Same thing that was already done in 2D, applies moving platform motion by using a call to move_and_collide that excludes the platform itself, instead of making it part of the body motion.
Helps with handling walls and slopes correctly when the character walks on the moving platform.
Also made some minor adjustments to the 2D version and documentation.

Thanks!


v1: how to expire nodes only during certain times?

In 0.37 this config allows us to expire nodes only during weekdays/working hours:
 disruption:
  consolidationPolicy: WhenUnderutilized
  expireAfter: 48h
  # Number of nodes: disrupt 1 node at a time, only during weekdays, from 10 to 18 UTC.
  # Schedule: zero disruptions (0) are allowed starting at 8am UTC on Friday, lasting 3 days + 2hrs.
  budgets:
  - nodes: "1"
   schedule: "0 10 * * mon-thu"
   duration: 8h
  - nodes: "0"
   schedule: "0 8 * * fri"
   duration: 74h

After migrating to v1 the config looks more like this:
apiVersion: karpenter.sh/v1
kind: NodePool
metadata:
 name: generic
spec:
 template:
  spec:
   nodeClassRef:
    apiVersion: karpenter.k8s.aws/v1
    kind: EC2NodeClass
    name: generic
   expireAfter: 48h   ### I don't want this to take effect during nights and weekends.

 disruption:
  consolidationPolicy: WhenEmptyOrUnderutilized
  consolidateAfter: 30m
  budgets:
  - nodes: "1"
   schedule: "0 10 * * mon-thu"
   duration: 8h
  - nodes: "0"
   schedule: "0 8 * * fri"
   duration: 74h

And nodes are expired also during weekends. How can I keep the behaviour of karpenter 0.37 in v1? From the documentation, it is unclear to me how to achieve this.
Thanks

This isn't currently possible to achieve with expiration on v1. Expiration was changed from a graceful to a forceful expiration method at v1 (RFC: https://github.com/kubernetes-sigs/karpenter/pull/1303) which means it can no longer be restricted by disruption budgets. This enabled enforcing strict maximum node lifetimes through expiration and termination grace period. Graceful disruption methods are still subject to disruption budgets (i.e. drift and consolidation). I'm wondering if your goals can be better met by drift, what are you trying to achieve by rolling nodes roughly every 48 hours?

From the Karpenter 0.37 NodePool example config: https://karpenter.sh/v0.37/concepts/nodepools/
# Avoiding long-running Nodes helps to reduce security vulnerabilities as well as to reduce the chance of issues that can plague Nodes with long uptimes such as file fragmentation or memory leaks from system processes

Since I ever started working with Kubernetes I was always taught to avoid long-running nodes. So even after all these years I try to keep my nodes "fresh" by rotating them.
If you have an alternative mechanism to achieve this with Karpenter v1, please share. I would like to avoid having my production nodes reaching 2 weeks of life (that's how often we deploy). But at the same time, I'd like to retain more control over when nodes rotate.

I would like to avoid having my production nodes reaching 2 weeks of life (that's how often we deploy). But at the same time, I'd like to retain more control over when nodes rotate.

There is no existing mechanism on v1 to achieve this. You can of course still use expiration, but it no longer respects disruption budgets. This was needed to ensure it could be used to enforce a true maximum node lifetime. I would recommend opening a feature request over in kubernetes-sigs/karpenter to introduce a "soft expiration" mechanism if control via disruption budgets for expiration is important to you.

I'm going to go ahead and close this out since there's no further action to take in this repository.


[fix] - handling external network spec

What this PR does / why we need it:
As part of https://jira.linode.com/browse/CNS-2959 we want to support external controlplane endpoint and skip creating a new NodeBalancer or DNS entries in this case.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
TODOs:

[ ] squashed commits
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

Although the deletion logic works out of box, I feel this is an opportunity to refactor it quite a bit.  as it a bit complex. Let me know your thoughts? Also an observation,  		if len(clusterScope.LinodeMachines.Items) > 0 {}, clusterScope.LinodeMachines.Items only has controlNodes in the item List, I think we might want to wait for all the machines to be deleted and not just the controlplane nodes.

STILL FIXING THE DELETION LOGIC.


Plugin needs to be signed to work with Grafana 8

Please submit your plugin to be signed by the Grafana Team so we can all use it w/ Grafana 8

Grafana 8.1.1 shows the Discrete plugin as signed in the plugin list for me, but it's still unusable (not available when creating a panel).

@kfot have you checked out the State Timeline Panel that ships with Grafana 8? It can visualize discrete states:
https://play.grafana.org/d/YI95GyqMz/1-new-features-in-v8-0?orgId=1

Unfortunately the State Timeline Panel does not support scrolling. Does not play well with many rows. Would be appreciated if this plugin were to be signed for Grafana 8. Thanks.


subsys: console: deprecate console_register_line_input()

console_register_line_input() is a legacy function which forces console subsystem to keep dependency on drivers/console. The two console implementations are meant to be independent.
Console subsystem provides console_getline() function, which should be used instead.
Console subsystem is still marked as experimental. If we decided to remove the function rather than deprecate a more extensive clean up would be possible. E.g. we could remove Kconfig dependencies on CONSOLE_HANDLER, UART_CONSOLE_DEBUG_SERVER_HOOKS.

First of all, I appreciate looking into this stuff.
Some comments though:

console_register_line_input() is a legacy function which forces console subsystem to keep dependency on drivers/console. The two console implementations are meant to be independent.

Yes, they're meant to be independent, and ideally, subsys/console should supersede drivers/console. Implementation-wise however, some of the functionality of subsys/console (e.g. console_getline()) is implemented on top of drivers/console.
The story behind console_register_line_input() is specifically that we had that code (calls to uart_register_input(), telnet_register_input(), etc.) repeated in the client code, so I proposed to move that to a function, and put that function in subsys/console (as an interim measure, with the plan I have in my mind, it wouldn't exist when console subsys is fully developed).

Console subsystem is still marked as experimental. If we decided to remove the function rather than deprecate a more extensive clean up would be possible.

Right. And even more refactoring is conceived, e.g. console_getline() should be implemented in terms of console_getchar(), fully in "userspace", and remove all that code from drivers/console (which would likely enable removing it altogether). But now we have new shell subsys with its own (?) line editing capabilities, so need to think how to fit it into that.
All in all, I see that console_register_line_input() isn't used in the current master codebase (it was before), so I'm +1 for deprecating it for 1.14. Not sure about complete removal for 1.14 though - it would likely just obscure ties between subsys/console and drivers/console (and per above, there're ties).

Codecov Report

Merging #14696 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14696   +/-   ##
=======================================
  Coverage   51.97%   51.97%
=======================================
  Files         309      309
  Lines       45582    45582
  Branches    10555    10555
=======================================
  Hits        23691    23691
  Misses      17082    17082
  Partials     4809     4809

Continue to review full report at Codecov.

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

But now we have new shell subsys with its own (?) line editing capabilities, so need to think how to fit it into that.

I need to implement a simple M2M communication over UART. In my case using the shell subsystem would be an overkill and I neither want to deal with the low lever UART API. Console subsystem feels like the best choice (also logically, from the application architecture point of view) and I'm happy someone has already put some work here.

And even more refactoring is conceived, e.g. console_getline() should be implemented in terms of console_getchar(), fully in "userspace", and remove all that code from drivers/console

Indeed, more refactoring is needed to fully separate console subsystem from drivers/console. I was wondering however if console_getline() shouldn't be implemented using the new async UART API as a long term goal. But that's probably subject for a separate issue.


Remove NetworkX patch from series file

this is only used for automatic testing on GitLab it does not have any effect
on the conda package.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Feature/50-add agenda screen and logos

I am not on the same page as Claudia, the image of the wheel is partly non visible , if you look at the sentence that it has at the right, you can not aprecciate well the words.

The blurry of the picture is made on purpose because it is the style of the homepage that should be followed


Ode quadrature space

@cdaversin I think this looks very good! Great that you managed to fix the converge rates! :D


Add basic frontend

We should have a basic Blazor frontend that has the functionality required to communicate with our backend and visualize the response, such that we can further develop on it in future issues

Closed by #75


[BUG] Fix widget scroller

Summary
Fix the scroller limit on the widget show.
Details and comments

[x] Delete limit size of the window widget to let Jupyter adapt it by default
[x] Jupyter test notebook

Closes #83
Closes #82

@IceKhan13 & @mentesniker ready for your review :)
The problem was the general size was blocking the sublayout scroller.
At the same time I updated the requirements


Linux download not working missing a library

Prerequisites

[ ] Can you reproduce the problem with Debug -> Reload Without Extensions?
[ ] Did you perform a cursory search to see if your bug or enhancement is already reported?
[ ] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
Please include the OS and what version of the OS you're running.
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)

On linux mint 18.2
I downloaded the file from brackets
when package installer does its check for dependencies - there is a problem with a libgcrypt 11 (>=1.4.5)
the repository of linux mint says the lib has been replaced by 2.0
I installed the upgraded lib but brackets still does not install.
the people from linux mint say that ppssible problem is that the libgcrypt11  has been hard coded and this prevents the next libegcrypt that is supposed to replace the libgcrypt 11 take effect.
any how brackets does not work on my linux mint 18.2

Hi @wisdomlight, could you try the 1.11. pre-release which should (finally) fix this issue: https://github.com/adobe/brackets/releases/tag/release-1.11-prerelease-1

Hey, I got this problem on ubuntu 17.04. The last version seems to work, thanks for the fix =)

It works!!

Awesome! Thanks for confirming @facchettos & @wisdomlight!

On Ubuntu 16.04 I had the issue with the downloaded .deb file from the website  and libgcrypt11 and I made sure libgcrypt20 is installed and updated (since libgcrypt11 is deprecated).
The pre-release 1.11 works fine with the libgcrypt20.
Thanks all for the thread.


Web/update files for preview

Summary
Currently, the data displayed in Analyze my sleep page comes from a night of a subject in our dataset. Therefore, data displayed was manually classified, and not acquired through an OpenBCI.
Thus, we want to display, as a preview of our web app, a night which were acquired with an OpenBCI and classified by our classifier. The night displayed is the one where we also manually tagged, which we will also present in the performance page in order to display the classifier accuracy.

 [<IP_ADDRESS>] Aperçu du produit


Is it possible to get rpc_methods parameters and documentation?

I want to make auto generation for API documentation. There is convenient way to do almost all what I need by parsing metadata state_getMetadata of my pallets. There are Extrinsics, storages, etc. with name, type and documentation.
Is there any way to take the same information about RPC calls(information about parameters and documentation)?
I found only rpc_methods method that retrieves the list of RPC methods without additional information.

No sorry there is not automated way for doing this.


Use ClusterShell to ease nodes declaration

Coverage increased (+0.3%) to 84.579% when pulling 25520d115bc3ec0eb0e44c29cde4f7552e6f7697 on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.3%) to 84.579% when pulling b898729faeefacfd5f83d174069f962cf9c2a1f8 on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Damned! ClusterShell does not support Python 3

Coverage decreased (-32.6%) to 51.633% when pulling b41c533f3a54124cbbad3fa065ce0688d8e4e3cb on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage decreased (-32.6%) to 51.633% when pulling b41c533f3a54124cbbad3fa065ce0688d8e4e3cb on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.09%) to 84.334% when pulling 42ad6d5367db0efa80e768f110d7415e52e37870 on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.09%) to 84.334% when pulling 42ad6d5367db0efa80e768f110d7415e52e37870 on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.09%) to 84.334% when pulling 04d417aa6cecf59bb3cc330a36af5dda3db60f6f on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.09%) to 84.334% when pulling c019fe661dfed32dd822c3cdf2161ebe391ffd7d on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.

Coverage increased (+0.09%) to 84.334% when pulling 1b3048edffd0e47b446e9bf2e3b5e531c9827fe8 on enh/nodes-list into 192f4bbf5572d2edc3f6dd247567dda8881d31dd on master.


fun. will try it.

Cool! Let me know what you make with it.

I made thelistenheargame.ml
Look at the source code!
Vào 07-07-2016 00:24, "Zeke Sikelianos"<EMAIL_ADDRESS>đã viết:

Closed #2 https://github.com/zeke/an-array-of-english-words/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeke/an-array-of-english-words/issues/2#event-714655395,
or mute the thread
https://github.com/notifications/unsubscribe/AQ3KUEbpZEWc541ZXimN8n6hQONOPxICks5qS-TRgaJpZM4JGEWT
.

Cool!
Feedback:

repeat the word automatically every second or two
show visual feedback when my guess is wrong

Are you storing the user input somewhere? That could be interesting. I typed 'weak', then 'week'. Could be a good way to find homonyms and stuff.


NumberInput doesn't fire on:focus, on:blur and on:input

What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
It makes impossible to use with form validation libraries. Currently the only way to get notified of value change is the on:change event, but this is not sufficient.
In which browser(s) did the problem occur?
No response
Steps To Reproduce
Bind event handlers to NumberInput
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
No response

Hey, thank you so much for these bug reports! :raised_hands: I really appreciate you taking the time to report them and help us make the library more bug free and useful!


When using the associations in a notebook and plot=False, the plot gets closed (i.e. removed) without ever being shown.

Hi, thank you for your work on this library.
Version check:
sys.version_info(major=3, minor=12, micro=5, releaselevel='final', serial=0)
0.7.7
However, this problem is still present in 0.7.8.
Describe the bug:
When calling nominal.associations with plot=False when using a notebook and passing an axis, the plot gets closed. What I expect to happen here is that the plot is not closed, the chart is added to the axis and then I can control what happens to it afterwards. Currently, the plots gets closed before that is possible.
Code to reproduce:
from dython.nominal import associations
df = pd.read_csv('fake_test_sample.csv')
fig, ax = plt.subplots(1, 2, figsize=(20, 8))

  fake_corr = associations(
      fake,
      nominal_columns=fake.select_dtypes(['object', 'category']),
      plot=False,
      nom_nom_assoc='theil',
      mark_columns=True,
      annot=annot,
      ax=ax[1],
      cmap=cmap,
  )['corr']
plt.show(). # This is currently empty, rather than having one plot on it.

Error message:
Error message:
<Figure size 640x480 with 0 Axes>

Input data:
real_test_sample.csv
fake_test_sample.csv
Though this issue will persist regardless of what data is used.

Seems to be an issue with how #147 was handled.. I'll have to come up with something else


Revert breaking API changes in casper-ee

After analyzing all the changes in casper-execution-engine, the following breaking changes were found:

removal of DEFAULT_MAX_DELEGATOR_SIZE_LIMIT
removal of DEFAULT_MAX_STORED_VALUE_SIZE
changes and renames in the storage::Error hierarchy (result of the LMDB -> rocksdb migration)
removal of max_delegator_size_limit
removal of max_stored_value_size
removal of the Runtime traits and subsequently moving most of the methods to the Runtime struct itself
introduction of TrieOrChunkedId
introduction of ChainspecRegistry

After inspecting the relevant code and trying to make these changes backwards compatible, I found there is no feasible way to do this because it would mean reverting most of the functionality added since the last release, which defeats the point.
The core of this issue is that the execution engine API is too permissive as of right now, publicly exporting most of its modules, where the structs and fns are mostly public as well. At some point we should refactor the API to only expose the relevant endpoints. This will allow us to restrict the set of user-facing changes when we consider releasing a new version and also allow more flexibility for changes under the hood. Because of the graph-like dependencies inside the execution engine and the fact that most things are public in the API, almost any change would be a breaking one.
For now, in order to respect semver standards, we must release a major version of casper-execution-engine.
The PR for this issue will add non-exhaustive to error enums and also restore write_scratch_to_db in a deprecated state (replaced by write_scratch_to_lmdb as part of the DB migration).


lib/ffmpeg/transcoderbase: show all frame's HDR info

In case of input has audio stream which will influence frame number of output video. The other reason is that vframes for filter showinfo is not accurate. For example, when use 'vframes 1', the output of showinfo will be 2 frames' info. Use all frame number to make sure the otuput will be same for diffferent case.

Is the performance impacted when the frame number is large ?

Is the performance impacted when the frame number is large ?

Is the performance impacted when the frame number is large ?

Re-pushed to disable audio stream. Which fix the input has different video frames comapre with output.

@feiwan1 Please fix errors in pre-check.

Hi @Bin-CI, could you help to check container build fail issue in pr check? Thanks.


Unable to get property 'handleEvent' of undefined or null reference

mediaelement-and-player.js:
1832: t.globalUnbind('mousemove.dur touchmove.dur mouseup.dur touchend.dur'); //callback is undefined
1857: t.globalUnbind('mousemove.dur'); //callback is undefined
3081: t.globalUnbind('mousemove.dur'); //callback is undefined
...
4655: key: 'globalUnbind',
4666: value: function globalUnbind(events, callback) {
...
4665: doc.removeEventListener(e, callback, false); //callback cannot be undefined or null
Unable to get property 'handleEvent' of undefined or null reference  error raised in Edge, haven't tested other browsers

Can you provide a URL where I can see this issue please? And which version are you using?

Oh I see what you mean. Those unbindings shouldn't even exist. I have removed them so you should see no errors right now. Let me know and thanks for reporting this. Please star the project to continue supporting it

Closing this issue since fix is now in place. If you like this to be reopened, please let us know. Thanks and please star the project to continue supporting it


fix(chips): mobile select

Description
Fixed select on Chips Autocomplete on mobile devices.
Closes #1044
What's included?

Modified: src/platform/core/chips/chips.component.ts

Reason of the bug: touchend events is canceling click events on mobile

Fix explanation: Added debounceTime to prevent both events from being fired together

Test Steps

[ ] Go to Chips demo page
[ ] Try selecting autocomplete on desktop
[ ] Try selecting autocomplete on mobile view
[ ] With ng serve --host <IP_ADDRESS>, try on a real phone opening the application on port 4200

General Tests for Every PR

[ ] npm run serve:prod still works.
[ ] npm run tslint passes.
[ ] npm run stylelint passes.
[ ] npm test passes and code coverage is not lower.
[ ] npm run build:lib still works.

Screenshots or link to StackBlitz/Plunker

BTW, I removed the touchend event altogether and the application worked on a real iPhone/Chrome device.
I don't know if the touchend evnt is necessary for other OS or browsers.

Thanks for the investigative work! Just left a small comment 🎉

Hi @emoralesb05 , I just pushed the fix to the comment!


#23 Reopen: Issue with i2c_slave_receive procedure when I2C VIP used as Master and Slave in a Test Harness

Hi Marius,
I am reopening the thread again. This thread is in continuation to the old thread #23.
Please consider adding additional command as given below after the i2c_master_transmit command. Still it fails. Use the same setup what you have described.
i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");
i2c_master_transmit(I2C_VVCT, 1, C_FPGA_DEVICE_ID, x"AA", "I2C TX"); -- CHANGED by Marius
await_completion(I2C_VVCT,1,100 * 10*C_BIT_PERIOD); -- ADDED by AHHarish
Regards,
AHHarish

Hi,
My simulation run fine, even with the await_completion() command.
Please see my files : https://1drv.ms/f/s!AojzQFNf4hf7gcJ_1XJI-0CoQ2kAkA
Best regards,
Marius

Are you using the following version. I have considered this as the latest release.
This project uses the following versions:
uvvm_vvc_framework, version v2.0.7
uvvm_util, version v2.1.1
bitvis_vip_sbi, version v2.0.6
bitvis_vip_uart, version v2.0.5
bitvis_uart, version v1.0.4
bitvis_irqc, version v1.0.4
bitvis_vip_axilite, version v2.0.7
bitvis_vip_axistream, version v3.0.5
bitvis_vip_avalon_mm, version v2.0.7
bitvis_vip_i2c, version v2.0.5
bitvis_vip_spi, version v2.0.3
bitvis_vip_gpio, version v1.0.1

You can refer to a Git hash instead of publishing all single file versions :). E.g. 1fb806af5a23440dd2caf1a8fd23c22506b6e655 to point to the version from June, 8th. Or you can use tag names like v2.4.1
This eases reproduction, because the support team can checkout the specific version you used.

Hi,
No, I don't get any time out issues.
Try running my setup ( https://1drv.ms/f/s!AojzQFNf4hf7ge0f0W8j5xiEpOP_WA ) by running run.sh from the /sim folder.
Br.
Marius


refactor(coverage): remove sourcemap snapshot

#5782  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Boshen and the rest of your teammates on  Graphite


Markdown to plain text (and/or using ANSI terminal codes)

I'm interested in parsing markdown and generating well-formatted plain text, and possibly also text for display at a terminal that uses ANSI terminal codes to provide some minimal formatting (e.g. emphasis).  My goal in doing so is to be able to use Markdown to write the usage/help information for command line programs, and then a) process the MarkDown to plain text or something close to it for display at the terminal and b) process it into HTML for generation of a documentation website.
I see that another user was asking about this in #63 that was closed.  I wasn't sure if I should re-open that issue, or open a new one, so apologies if I did the wrong thing.
I took a look at the various documentation and the rendering/writing classes for HTML and didn't get a clear picture of what a minimal implementation would look like, such that I could start on one myself.  Any of the following would be great:

A fully realized implementation that writes plain text using just whitespace and symbols for layout and styling
A shell of a renderer that I could take and start customizing to do the layout (which I'd be happy to walk away with, or contribute back when I'm done)
Just some clear guidance around what an implementation would look like as I'm having trouble piecing that together by myself

In the closed issue you asked about how to style various things.  I'd be more than happy to take a crack at answering those questions and others if you're still interested in answers.  The only things I think would be rather tricky would be:

Tables (do-able, but a lot of effort to lay out nicely)
Line wrapping for indented lines (since my goal is to produce nice output on a terminal it's critical to be able to set a line-length limit and wrap appropriately)

I'd appreciate any help or guidance you can give.  Thanks!

@tfenne,  what you need to create is a custom Formatter that will strip out markdown markers and convert them to plain text.
The easiest thing is to create a custom formatter, start with the flexmark-formatter CoreNodeFormatter and modify the rendering of nodes to only output text part of the node.
You will also need to include custom extension nodes that you want to support such as flexmark-ext-tables. Formatting tables is handled by the extension so you can use that code as a starting point.
The flexmark-java-samples module contains a few samples of custom extensions, including formatter.

Thanks @vsch - I ended up doing a different direction and implementing something akin to your visitor stuff to traverse the AST and output plain text.  I found the Formatter/Renderer APIs difficult to understand, but doing a top-down AST traversal seemed relatively simple.
I'm also working in scala, which makes some of the recursive pattern matching simpler.  If you're curious where I ended up here's my work in progress: https://github.com/fulcrumgenomics/dagr/pull/279/files

@tfenne, I am adding tests and fixes for the missing text elements for inline code and fenced code.
This means that Code and FencedCode nodes will now have a Text node with the text for these elements.
This is potentially an API breaking change because the issue is caused by the AST for these elements missing a Text child node that contains the element's text like is done for emphasis and strong emphasis nodes.
Note that the new release 0.19 will have these changes.

@vsch I was trying to build a custom formatter and found the process -- a lot of work, but -- quite straightforward, but I hit a dead end with NodeRendererContext. It's not obvious what the implementation should look like, current implementation for HTML cannot be reused, and most of the methods are not documented.
I'm going to try a similar thing to @tfenne.


chore: enable dependabot for the repository

This change adds dependabot for the repository for the various package managers

The errors are CI errors are unrelated to the PR. Ubuntu had an outage today:
https://status.canonical.com/
Re-running now

The outage resolved itself and the actions passed as expected.


Add the new registry "font"

Hello,
Could you please add the new font registry to your script ?
Thanks,
Olivier

Hi Olivier, thanks for this PR. Are you able to add a valid test case to unit.js?

Thank you very much, I'll include this in a new npm-published version soon.

v0.3.1 now available, first release for almost 2 years, thanks again!