Improving Cairo programs with imputs

Here's a simple example of a main function in Cairo that takes input parameters:
type MyContract:
data: felt
func main(input_param1: felt, input_param2: felt) -> (result: felt):
// Perform some operations using the input parameters
// For example, let's add the two input parameters and store the result in the 'data' field.
data := input_param1 + input_param2
// Return the result
result := data
In this example:
MyContract is a simple contract with a single variable data of type felt (a 256-bit integer in Cairo).
The main function takes two input parameters, input_param1 and input_param2, both of type felt.
Inside the function, it performs a simple addition of the input parameters and stores the result in the data variable.
The result is then returned.
This is a very basic example, and in a real-world scenario, you would have more complex logic in your main function, interacting with the blockchain, other contracts, or external data.
Keep in mind that Cairo is often used for smart contracts, so the main function is typically called automatically when the contract is executed on the blockchain. If you have a specific use case or more details about what you're looking for, feel free to provide additional information!

This should be done in the VM, since Cairo1 programs are runned there. After that, we can discuss adding some public inputs


hermes keys balance doesn't show all denoms

Summary of Bug
hermes keys balance only shows the balance of the config's gas_price denom.
$ hermes --config config.toml keys list --chain ibc-1
SUCCESS
- relayer (cosmos1zc7qkhjr4delcr785q0a4jsqcchjef4vvpup70)
- wallet (cosmos14ev9kx7tj4kl48jgm698qqpeth54ykz6l2x3k5)
- user1 (cosmos1gef995hlygyyqfqcjkgt0a58rt356ssh4zmy2j)
- user2 (cosmos15jyrwymfshhsjznelhvleklzjas0vjga3wrrk5)
- testkey (cosmos1wn7kusrmrn2ms6e2cex7uud3uhvsm6xt3p96jj)

$ hermes --config config.toml keys balance --chain ibc-1 --key-name testkey
SUCCESS balance for key `testkey`:<PHONE_NUMBER>8 stake

$ gaiad query bank balances cosmos1wn7kusrmrn2ms6e2cex7uud3uhvsm6xt3p96jj --node http://<IP_ADDRESS>:26557
balances:
- amount: "30"
  denom: ibc/27A6394C3F9FF9C9DCF5DFFADF9BB5FE9A37C7E92B006199894CF1824DF9AC7C
- amount: "100000000000"
  denom: samoleans
- amount: "99999998688"
  denom: stake
pagination:
  next_key: null
  total: "0"

I am pretty sure this used to work like the gaiad query bank balance counterpart but haven't traced the PR that change this.

Version

Steps to Reproduce

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

The current hermes keys balance command was introduced with this PR, https://github.com/informalsystems/hermes/pull/2232. As I recall the idea was to output the balance of the token used for gas, as the interest was knowing if there was enough funds to submit a transaction.
I think it would be a good idea to improve this command, the following solutions come to my mind:

Add an optional flag --denom to specify the denom to query, with a special value to query all denom. For example:

hermes keys balance --chain <CHAIN_ID> --key-name <KEY_NAME> --denom samoleans to display only the amount of samoleans
hermes keys balance --chain <CHAIN_ID> --key-name <KEY_NAME> --denom all to display the balance for all denom
hermes keys balance --chain <CHAIN_ID> --key-name <KEY_NAME> to display the balance of the gas_price denom

Add an optional flag --all which outputs the balance for all denom when used, and only the balance of the gas_price denom if not used. For example:

hermes keys balance --chain <CHAIN_ID> --key-name <KEY_NAME> to display only the balance of gas_price denom
hermes keys balance --chain <CHAIN_ID> --key-name <KEY_NAME> --all to display the balance of all denom

Update the command to always output the balance of all denoms

I have a preference for the first solution, adding a --denom flag, as it keeps the actual command as it is, but gives the user the possibility to have a more specific output.
What do you think ?

Option 1 looks good.


Use --ignore-platform-req=php+ for ignoring PHP deps

Feature Request

Q
A

New Feature
yes

RFC
no

BC Break
no

Summary

Composer with v2.2 released support for ignoring upper bounds of platform requirements.
To do so, adding the + suffix to the platform requirement will suffice.
This is quite useful, since --ignore-platform-req=php will mostly ignore any dependency and thus, depending on the constraint ranges, will also allow older PHP versions which weren't supported previously. This must not be related to laminas components but since laminas does sometimes use transitive dependencies, these dependencies could have a more wider range of supported PHP versions which then might install dependencies in case of --prefer-lowest which do definitely not support the latest PHP version we are actually trying to test.

From composer documentation:

--ignore-platform-req: ignore a specific platform requirement(php, hhvm, lib-* and ext-*) and force the installation even if the local machine does not fulfill it. Multiple requirements can be ignored via wildcard. Appending a + makes it only ignore the upper-bound of the requirements. For example, if a package requires php: ^7, then the option --ignore-platform-req=php+ would allow installing on PHP 8, but installation on PHP 5.6 would still fail.

This is of limited utility since with this feature any version of dependency can be installed anyway on the new php version where we do need platform ignore and we got no reason to do platform ignore on like php 8.1 which then would prevent packages for >8.2 installed on 8.1


support legacy clusterset

Ref: https://github.com/stolostron/backlog/issues/15278
Signed-off-by: haoqing0110<EMAIL_ADDRESS>

/assign @qiujian16 @elgnay @ldpliu


Adds ACL, ACLProvider, Keychain, KeychainProvider

These new types provide implementations using CRDTs for ACLs and Keychains. The *Provider classes are simple factories for their corresponding ACL/Keychain implementation.
Please note that this does add security concerns to the CRDT ACL implementation. This potentially could open up the door to ACL/Keychain CRDT attacks if the attacker is somehow able to bypass our message encryption/signing.

Splitting into smaller chunks


Correct a typo for multipath

Sorry about that, @mingxiao please help review and merge.

@mattcui this PR has a simple string change in the It statement. Are you sure you are not missing some more changes for this PR...

I think the PR is complete and in response to this comment.

Merged to develop in 6606cbdbf9395bb75256883b67cf54c1f63b9a9f - thanks for following up!


Make a full run of the HT29 dataset

This dataset will be our public demo so it needs to be fully incorporated into our testing, and added to the microscopium.io machine.

[x] nomalise, stitch, stack images
[ ] extract features
[ ] build mongo

Whoo! One down! That was quick... =P
@starcalibre see https://github.com/microscopium/microscopium-scripts/pull/5

The cool thing is that with the new streaming data system I can do it all in ~30CPU.h, virtually no memory required! Now I just need an easy, convenient way to parallelise... ;)

What's the best way to do this in Python these days? The multiprocessing module?

I'm not really sure... I think IPython.parallel is the best choice currently. (Soon to be jupyter_parallel I think...!)

Did this! I love it when you go over issues and discover they're finished! =P


fix(ssr): remove pure CSS dynamic import

Description
The pure chunk was removed but the dynamic import importing that chunk was not removed.
This if condition is true for SSR code.
https://github.com/vitejs/vite/blob/147e9228bb1c75db153873761eb7a120a2bd09a4/packages/vite/src/node/plugins/importAnalysisBuild.ts#L321
Dynamic import for non-SSR code is removed here.
https://github.com/vitejs/vite/blob/147e9228bb1c75db153873761eb7a120a2bd09a4/packages/vite/src/node/plugins/importAnalysisBuild.ts#L410-L422
fixes #17366
refs #16078

/ecosystem-ci run

The SvelteKit tests has been failing on various different tests on each run, so it's hard to tell this is causing it to fail. I'll merge this for now and will backport to 5.2.13 soon.


RecursiveComparisonDifferenceCalculator - Stack overflow

Describe the bug
RecursiveComparisonDifferenceCalculator is fetching field values preferred via property accessor and not via plain field reflection.
This becomes to an issue in case the property accessor is returning new instances on each invocation and a cyclic graph structure exists for comparison. In that case it might happen that RecursiveComparisonDifferenceCalculator (assertThat(...).usingRecursiveComparison()...) is ending up with an unexpected stackoverflow.

assertj core version: 3.23.1 and previous versions (3.18.1)
java version: 11
test framework version: JUnit Jupiter 5.9.0
os (if relevant): Windows 10

Test case reproducing the bug
See also attached sandbox.zip. There is a single test class contained called "StackOverflowTest".
package sandbox;

import static org.assertj.core.api.Assertions.assertThat;

import java.util.Collections;
import java.util.HashSet;
import java.util.Set;

import org.junit.jupiter.api.Test;

/**
 * @author Philipp Förmer
 *
 */
public class StackOverflowTest {

    /**
     * This test case will cause a stack overflow during reflection comparison, as the
     * {@link org.assertj.core.api.recursive.comparison.RecursiveComparisonDifferenceCalculator RecursiveComparisonDifferenceCalculator}
     * is fetching field values preferred via property accessor and not via plain field reflection.
     *
     * Scenario:
     * It is a simple cyclic graph constructed A1 <-> A2. A1 and A2 contain pointer collections to each other.
     * The getter of the pointer collection is only returning a copy of the pointer collection and not the plain instance.
     * So every access of the getter of the pointer collection is returning a new collection instance.
     * This will trick the RecursiveComparisonDifferenceCalculator visited DualValue collection, to not see an already visited field
     * as visited and cause stack overflow death.
     *
     * Possible solutions:
     * 1. Always use field reflection in RecursiveComparisonDifferenceCalculator, never make use of property getter reflection.
     *    Maybe this might not work reliable in case of proxy objects, where parts are initialized over getter access.
     *    This is for example problematic for JPA entity classes with annotations mapped by getters.
     * 2. Provide a configuration option for {@link org.assertj.core.api.recursive.comparison.RecursiveComparisonConfiguration RecursiveComparisonConfiguration}
     *    to enable/disable usage of property getter reflection. The default value should be to make use of plain field reflection.
     * 3. ...
     */
    @Test
    public void overflowDueToPropertyInspection() {
        final A actual = new A();
        final A a2 = new A();
        actual.add(a2);
        a2.add(actual);

        final A expected = new A();
        final A e2 = new A();
        expected.add(e2);
        e2.add(expected);

        assertThat(actual).usingRecursiveComparison()
            .ignoringCollectionOrder()
            .isEqualTo(expected);
    }

    private static class A {

        private Set<A> elements = new HashSet<>();

        public void add(final A a) {
            elements.add(a);
        }

        public Set<A> getElements() {
            return Collections.unmodifiableSet(elements);
        }
    }

}

That should be addressed by https://github.com/assertj/assertj/issues/2189 where you would be able to use your own introspection strategy

Closing it since https://github.com/assertj/assertj/issues/2189 has been addressed


Fix typos

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context
It fixes typos in the output of fastlane action ...
Description
It fixes typos in the output of fastlane action ... for the commands snapshot, scan and gym

@Blackjacx Thanks for the contribution. I allowed myself to incorporate the review comments into your code. Let's merge this!

Oh Hey there 👋 thanks for dealing with my PR. I was very short on time and did not have  alook in here for a long time. Sorry for that.
And hello @rogerluan - nice to meet you again 👋


Use fix bcos console version

Codecov Report

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

@@            Coverage Diff            @@
##             master     #229   +/-   ##
=========================================
  Coverage     28.33%   28.33%
  Complexity      330      330
=========================================
  Files           110      110
  Lines          3578     3578
  Branches        258      258
=========================================
  Hits           1014     1014
  Misses         2484     2484
  Partials         80       80


Present memcached server list as part of CR status

This introduces the two new fields to present list of memcached servers to Memcached CR. This allows each operator to check ready condition and list of memcached endpoints by only querying Memcached CR instance, instead of querying Pod list separately.

Tested in my local env.
$ oc get memcacheds/memcached -o yaml
apiVersion: memcached.openstack.org/v1beta1
kind: Memcached
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"memcached.openstack.org/v1beta1","kind":"Memcached","metadata":{"annotations":{},"name":"memcached","namespace":"openstack"},"spec":{"replicas":1,"secret":"osp-secret","storageClass":"local-storage"}}
  creationTimestamp: "2023-05-25T01:34:47Z"
  generation: 1
  name: memcached
  namespace: openstack
  resourceVersion: "9146492"
  uid: 57c78c5a-886b-4b91-8fac-81b7c3b14f1d
spec:
  containerImage: quay.io/podified-antelope-centos9/openstack-memcached:current-podified
  replicas: 1
status:
  conditions:
  - lastTransitionTime: "2023-05-25T01:35:03Z"
    message: Setup complete
    reason: Ready
    status: "True"
    type: Ready
  - lastTransitionTime: "2023-05-25T01:35:03Z"
    message: Deployment completed
    reason: Ready
    status: "True"
    type: DeploymentReady
  - lastTransitionTime: "2023-05-25T01:34:52Z"
    message: Exposing service completed
    reason: Ready
    status: "True"
    type: ExposeServiceReady
  - lastTransitionTime: "2023-05-25T01:34:52Z"
    message: RoleBinding created
    reason: Ready
    status: "True"
    type: RoleBindingReady
  - lastTransitionTime: "2023-05-25T01:34:52Z"
    message: Role created
    reason: Ready
    status: "True"
    type: RoleReady
  - lastTransitionTime: "2023-05-25T01:35:03Z"
    message: ServerList completed
    reason: Ready
    status: "True"
    type: ServerListReady
  - lastTransitionTime: "2023-05-25T01:34:52Z"
    message: ServiceAccount created
    reason: Ready
    status: "True"
    type: ServiceAccountReady
  - lastTransitionTime: "2023-05-25T01:34:52Z"
    message: Service config create completed
    reason: Ready
    status: "True"
    type: ServiceConfigReady
  serverList:
  - memcached-0.memcached:11211
  serverListWithInet:
  - inet:[memcached-0.memcached]:11211

Takashi could you elaborate on how you envision this list of pods will be consumed? Maybe the field is still a nice to have, but it should be generated out of the spec and not out of list of pods? Maybe you disagree with my point?

You can find the example implementation to leverage these fields in https://github.com/kajinamit/horizon-operator/commit/8a05c84f3b9ad43255ec4b94d6eaca06aeaf7c36 . In short the plan is to let operators deploy memcached and obtain these list from status, then put the list items into config file.
We can probably create the list statically instead of querying pods, though we have to be aware that we have to simulate the logic inside Statefulset for it (the logic can be broken by any change in kore k8s though I think that unlikely happen).
I'll look for the way to implement these in more static manner but I still think we should have the common logic in memcached operator, because

We need the same logic in all operators deploying memcached
We still need to properly detect IP version used by memcached (unless we can detect this in a different way, instead of querying pod addresses)

OK we can probably query service instead of pods to get ip version.
$ oc get services/horizon -o yaml
apiVersion: v1
kind: Service
...
spec:
  clusterIP: None
  clusterIPs:
  - None
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: memcached
    port: 11211
    protocol: TCP
    targetPort: 11211
  selector:
    app: memcached
  sessionAffinity: None
  type: ClusterIP

Hostname format is heavily dependent on how these pods are deployed, and memcached controller is maintaining that
One good example is the service name. How memcached controllers deploys service name according to instance name, and because of that if we deploy Memcached with name horizon then it creates a service with name: heat.

This is quite confusing and we ideally should have memcached- prefix but if we keep the logic to generate hostnames in each operators then we have to update all operators when we fix that.

So looking into k8s blueprint and actual behavior in my env, I concluded that Service.spec.IPfamilies[0] can be used to determine which IP version is used for a service. A remaining problem is that we need additional handling for dual-stack use case but we've never support it in TripleO and we have to address more problems (eg we have to implement the way that all services use preferred IP version)  so I think we can leave the problem for a future TODO.
I've submitted https://github.com/openstack-k8s-operators/lib-common/pull/282 so that we have that information exposed by lib-common then I'll update it once that PR is merged.


update zh kubelet-config-file doc

change kubelet-config version from alpha to v1beta1
change kubelet-config types address
add example translation according to en version

/lgtm

it would be good to split the content/zh and content/en, which is generally what we do.

/lgtm

/approve


Added the complete program of the AVL Trees

Done removing the bubble sort Program

PR accepted @mananaggarwal2001
Successfully merged to HacktoberFest_22 repo.
Need to Star this repo incase not done.
🚀🚀👍


Browser Support?

Hi
I want to make sure this library is right for me.
What I am trying to achieve is this.
I want to do the same thing on apple devices (iphone and ipad), load up safari (not sure if they got chrome and Firefox on these devices. I don't own apple), click a button and load up their devices cameras and scan a bar code.
I seen that there been some issues with iOS and wanted to double check that I will be able to do barcode scanning at least through safari and what versions of safari do they need.

For the most part, it works on modern iOS devices, as far as I'm aware.  In the current betas, it even works in Chrome on iOS, not just in Safari, now that they've got camera support for WebView.

Hi there,
I can confirm that this library works flawless on most likely all modern browsers (yes also on Android and iOS) that supports getusermedia etc etc.
Please bare in mind that you should use Safari on iOS to get the best experience out of this library... (since it's the most updated browser on apple devices)
And finally :) this library also works perfectly in progressive web apps as well :)... iOS had some issues before, but if I could recall they have fixed it in iOS 14 already.
https://bugs.webkit.org/show_bug.cgi?id=185448 <--- we have complained for almost 2/3 years to get this problem fixed.

this library also works perfectly in progressive web apps

This is a trick I need to learn! :-D

For the most part, it works on modern iOS devices, as far as I'm aware. In the current betas, it even works in Chrome on iOS, not just in Safari, now that they've got camera support for WebView.

When you say current betas, you mean of the iOS operating system or browser versions?
What you mean it does not work in Safari? So the newer devices like iphone 11 safari won't work with this library.
I don't know much about apple stuff, I have a contract to see if it is possible to implement a barcode reader into a responsive webpage.
I am just not sure how possible it will be apple and wanted to double check. I tried on a 6 year old ipad mini with the example and it worked fine, I don't have an iphone but the company said they would send me one but warned it might be older version so that does not help if new iphone versions may have problems.

Hi there,
I can confirm that this library works flawless on most likely all modern browsers (yes also on Android and iOS) that supports getusermedia etc etc.
Please bare in mind that you should use Safari on iOS to get the best experience out of this library... (since it's the most updated browser on apple devices)
And finally :) this library also works perfectly in progressive web apps as well :)... iOS had some issues before, but if I could recall they have fixed it in iOS 14 already.
https://bugs.webkit.org/show_bug.cgi?id=185448 <--- we have complained for almost 2/3 years to get this problem fixed.

So if I am reading this right, anything running iOS 10.3 or less can't use it?
I would hope most people using iphone and ipads would be using safari but since I am implementing this in a responsive website, I don't get the luxary of getting the users to use what I want them to use.
I guess best I can do is test for getusermedia and only show the icon to launch this library if present.
I am also not sure what "progressive web apps" are.

So if I am reading this right, anything running iOS 10.3 or less can't use it?

You are correct, this library will not work beneath iOS 11...
You should always test if "mediadevices/getusermedia" is available for your specific device.
Please bare in mind that devices with multiple camera's will not work correctly with getusermedia and it's constraints(specifically when choosing environment).
So try to use navigator.mediaDevices.enumerateDevices() instead and loop through your devices and it's label.

I am also not sure what "progressive web apps" are.

You can create an "app" experience by creating an progressive web app.
It enables your users to install your website on their homescreen.
Please read this article : https://web.dev/what-are-pwas/
That's why I referred to iOS and it's problems in it's own webview and PWA technology. (luckily it's solved)

When you say current betas, you mean of the iOS operating system or browser versions?

Current betas of iOS allow getUserMedia to work in WebView, so people using those can use Chrome or whatever other 3rd party browser with the library.  It's worked with Safari for a few years now, I believe.  Older iThings that will not update beyond iOS 10 will not work with it (this makes me sad, as I have several old iPads that I hoped to use as testing devices, but that didn't end up working out)

So if I am reading this right, anything running iOS 10.3 or less can't use it?

You are correct, this library will not work beneath iOS 11...
You should always test if "mediadevices/getusermedia" is available for your specific device.
Please bare in mind that devices with multiple camera's will not work correctly with getusermedia and it's constraints(specifically when choosing environment).
So try to use navigator.mediaDevices.enumerateDevices() instead and loop through your devices and it's label.

I am also not sure what "progressive web apps" are.

You can create an "app" experience by creating an progressive web app.
It enables your users to install your website on their homescreen.
Please read this article : https://web.dev/what-are-pwas/
That's why I referred to iOS and it's problems in it's own webview and PWA technology. (luckily it's solved)

When you say multiple cameras are you talking about phones that have front and back camera or are you talking about the phones that have like 5 cameras in the back?
Also could you give an example of code how to test for this?
So try to use navigator.mediaDevices.enumerateDevices() instead and loop through your devices and it's label.
Anyways I can emulate this situation as well? if you talking about multiple cameras in the back I won't be able to get my hands on something like that.

When you say current betas, you mean of the iOS operating system or browser versions?

Current betas of iOS allow getUserMedia to work in WebView, so people using those can use Chrome or whatever other 3rd party browser with the library. It's worked with Safari for a few years now, I believe. Older iThings that will not update beyond iOS 10 will not work with it (this makes me sad, as I have several old iPads that I hoped to use as testing devices, but that didn't end up working out)

I tried on an ipad mini my wife has had over for 6 years and it worked with the example app.  I have to check what version it is running so at least older things to a certain point are supported.

There are a lot of old iPads out there that are limited to iOS 9 or 10, though :(
Quagga does offer a wrapper, Quagga.CameraAccess.enumerateDevices() i believe it's called, though it's been a while since i've looked at it, so i may have the name slightly off.
Most all phone devices have at least two logical cameras -- a front and a back, some have several, even if they only appear to have a single front and back lense.  My LG G6, and many of the other top end phones report several back cameras, one with a wide-angle, one with normal proportions, etc ,as well as the front camera.  Some phones, if you just ask for 'environment' camera, you'll get something wide-angle that fish-eyes the view, making it near impossible to scan the barcodes.  Others, you'll get something that works well.  My brand new Moto G Stylus works fantastically with the default camera device, and it even auto-focuses, which is not something we can control inside the browser currently.
Personally, I use React for my application that I use Quagga in, with a Redux data/state store, and I use this helper lib I wrote for determining available cameras: https://github.com/ericblade/quagga2-redux-middleware
I use that to get the camera devices, then I offer the user a choice of which device.  Unfortunately, phones often do not provide any useful names for the devices, just "front" or "back", so the user has to use trial and error to figure out which one works best sometimes.   Once the user has selected a device, you can pass it in with a "deviceId" in the constraints block.
You can do the same thing on a regular PC, by plugging in multiple cameras, or if you have a laptop with a built in camera, plugging in a single external USB camera.  On PCs you almost always get the USB device name of the camera, though, which is a lot more useful.

Some phones, if you just ask for 'environment' camera, you'll get something wide-angle that fish-eyes the view, making it near impossible to scan the barcodes. Others, you'll get something that works well. My brand new Moto G Stylus works fantastically with the default camera device, and it even auto-focuses, which is not something we can control inside the browser currently.

Yes, I am currently using a Samsung Galaxy S20+.
When I'm trying to set facingMode to environment (with getUserMedia) it returns "NotReadableError: Could not start video source".
But when trying enumerateDevices(). it shows a list of inputdevices :) which I can choose from.

There are a lot of old iPads out there that are limited to iOS 9 or 10, though :(
Quagga does offer a wrapper, Quagga.CameraAccess.enumerateDevices() i believe it's called, though it's been a while since i've looked at it, so i may have the name slightly off.
Most all phone devices have at least two logical cameras -- a front and a back, some have several, even if they only appear to have a single front and back lense. My LG G6, and many of the other top end phones report several back cameras, one with a wide-angle, one with normal proportions, etc ,as well as the front camera. Some phones, if you just ask for 'environment' camera, you'll get something wide-angle that fish-eyes the view, making it near impossible to scan the barcodes. Others, you'll get something that works well. My brand new Moto G Stylus works fantastically with the default camera device, and it even auto-focuses, which is not something we can control inside the browser currently.
Personally, I use React for my application that I use Quagga in, with a Redux data/state store, and I use this helper lib I wrote for determining available cameras: https://github.com/ericblade/quagga2-redux-middleware
I use that to get the camera devices, then I offer the user a choice of which device. Unfortunately, phones often do not provide any useful names for the devices, just "front" or "back", so the user has to use trial and error to figure out which one works best sometimes. Once the user has selected a device, you can pass it in with a "deviceId" in the constraints block.
You can do the same thing on a regular PC, by plugging in multiple cameras, or if you have a laptop with a built in camera, plugging in a single external USB camera. On PCs you almost always get the USB device name of the camera, though, which is a lot more useful.

would like to use reactjs as what I like, but the project I am doing apparently is some old version of angular (version 3 I think). I am planning to do it more in plan javascript anyways. The project is not hard in sense of programming but handling all thse different cameras and stuff as I have very limited amount of devices.
Basically project is, scan bar code and put in a textbox.
I will have to look for this "Quagga.CameraAccess.enumerateDevices()" and see what going on with it.
If a user has a old device, nothing I can do. Can't make things work if libraries are not supported.

Some phones, if you just ask for 'environment' camera, you'll get something wide-angle that fish-eyes the view, making it near impossible to scan the barcodes. Others, you'll get something that works well. My brand new Moto G Stylus works fantastically with the default camera device, and it even auto-focuses, which is not something we can control inside the browser currently.

Yes, I am currently using a Samsung Galaxy S20+.
When I'm trying to set facingMode to environment (with getUserMedia) it returns "NotReadableError: Could not start video source".
But when trying enumerateDevices(). it shows a list of inputdevices :) where I can choose from.

How will you figure out which camera to choose?
I am still not clear on how to choose best camera.  I don't really want to have another dropdown list that they have to choose camera but maybe I might have to do this?

it seems like the best one can do is either use the outdated facing environment constraint in your Quagga init, or filter the enumerate devices to pick one that appears to be facing back, and provide some way for the user to force a specific device if you pick wrong.
i'd hope for something better, but enumerateDevices doesn't support a constraint, and so.. there's not even a way to combine constraints with selection, there's no way to tell from anything but the device name, which might not even exist, anything about the camera.  Once you've actually passed it through Quagga.init() you can start querying the media properties to find out what you actually got, resolution wise, but there's no way to reliable say "front" or "back" or "wide-angle" or whatever.
If you try that same call from a laptop with a built-in camera and an external camera, your labels will be "name/model number of built-in camera" and "name/model number of external camera" usually.

fwiw, i was just glancing at the quagga2-redux-middleware package, and realized it's dependency tree was a mess, and released an update just now that hopefully fixes it.

ok, well the redux stuff won't help me in this situation unless it can be easily extracted to be used in plan JS. If it is ok, I going to take a crack at this and post my code and maybe someone can help me to handle the multiple cameras and such.

Some phones, if you just ask for 'environment' camera, you'll get something wide-angle that fish-eyes the view, making it near impossible to scan the barcodes. Others, you'll get something that works well. My brand new Moto G Stylus works fantastically with the default camera device, and it even auto-focuses, which is not something we can control inside the browser currently.

Yes, I am currently using a Samsung Galaxy S20+.
When I'm trying to set facingMode to environment (with getUserMedia) it returns "NotReadableError: Could not start video source".
But when trying enumerateDevices(). it shows a list of inputdevices :) where I can choose from.

how do I call enumerateDevices()?

@ericblade @tinnielam @seanhussey @UziTech
Hey
So I gone and made my first crack at it and I do have a few questions (not sure if I should start a new post?)

How can I get the cameras canvas to do 100% of visible screen?
I have a problem with sometimes the camera does not seem to want to load up. I have to restart the page. I am not sure if that is because I do the full init on every click? How can I check if initialized and if so just start it?
I have a dropdown to do choose the camera how do I pass it in Quagga on selection?
I am trying to get the box outline to work. I copied the code from one of the Example sin onProcessed but it never draws the boxes in the right area (it is always outside of my canvas)
Let me know if there is anything I can do better

$(function () {
  $("#close-camera-container").click(function () {
    hideCamera();
  });

  function hideCamera() {
    $("#container").hide();
    $(".form-group").show();
    Quagga.stop();
  }

  function startCamera() {
    Quagga.start();
    $("#container").show();
    $(".form-group").hide();
  }

  function setupCameraSelectList() {
    navigator.mediaDevices.enumerateDevices().then(function (devices) {
      var $cameras = $("#cameras-selection");
      $cameras.empty();
      var videoInputs = devices.filter(function (device) {
        return device.kind === "videoinput";
      });

      if (videoInputs.length == 1) {
        $cameras.append(
          new Option(videoInputs[0].label, videoInputs[0].deviceId)
        );
      } else {
        $cameras.append(new Option("Select a Camera", ""));
        devices.forEach((device) => {
          if(device.deviceId !== "default"){
            $cameras.append(new Option(device.label, device.deviceId));
            $('#test').append(`<p>${device.deviceId} ${device.label}</p>`)
          }

        });
      }
    });
  }

  $(".fa-barcode").click(function () {
    var w = window.innerWidth;
    var h = window.innerHeight;

    $("#container").hide();
    // how to check if initialized?
    Quagga.init(
      {
        inputStream: {
          name: "Live",
          type: "LiveStream",
          target: "#container",
          constraints: {
            width: w,
            height: h,
            facing: "environment",
          },
        },
        decoder: {
          readers: ["upc_reader", "ean_reader"],
        },
      },
      function (err) {
        if (err) {
          console.log(err);
          return;
        }

        startCamera();
        setupCameraSelectList();
      }
    );
  });

  Quagga.onDetected(function (result) {
    if (result.codeResult) {
      $(".search-box").val(result.codeResult.code);
      hideCamera();
    }
  });

  Quagga.onProcessed(function (result) {
    var drawingCtx = Quagga.canvas.ctx.overlay,
      drawingCanvas = Quagga.canvas.dom.overlay;

    if (result) {
      if (result.boxes) {
        drawingCtx.clearRect(
          0,
          0,
          parseInt(drawingCanvas.getAttribute("width")),
          parseInt(drawingCanvas.getAttribute("height"))
        );
        result.boxes
          .filter(function (box) {
            return box !== result.box;
          })
          .forEach(function (box) {
            Quagga.ImageDebug.drawPath(box, { x: 0, y: 1 }, drawingCtx, {
              color: "green",
              lineWidth: 2,
            });
          });
      }

      if (result.box) {
        Quagga.ImageDebug.drawPath(result.box, { x: 0, y: 1 }, drawingCtx, {
          color: "#00F",
          lineWidth: 2,
        });
      }

      if (result.codeResult && result.codeResult.code) {
        Quagga.ImageDebug.drawPath(
          result.line,
          { x: "x", y: "y" },
          drawingCtx,
          { color: "red", lineWidth: 3 }
        );
      }
    }
  });
});

live code: https://barcodes.z4.web.core.windows.net/

In your constraints, you can specify the deviceId instead of the facing, to get a specific camera device.  i think it's actually supposed to be something like deviceId: { exact: "...deviceId..." } but just specifying a deviceId seems to work.
I honestly have not been able to figure out how to get my layout to do exactly what I want on mobile, Chrome on mobile acts differently than Chrome on desktop with video elements that are displaying cameras, and i'm not sure how it's different to try to adjust.  I got my app mostly displaying something sort of what i want, via trial and error, and stopped fiddling with it at that point. :|
I noticed when I just switched from a LG G6 to a Moto G Stylus, though, that with the G Stylus, I get what appears to be the entire camera viewfinder in the page, whereas my G6 only gets about half.  There's probably something that I don't understand, so I can't make sense out of it.
If you're not seeing drawing results, but your onProcessed is running the code, it's probably something in the html/css causing the canvas to not be visible, or to be under something.

In your constraints, you can specify the deviceId instead of the facing, to get a specific camera device. i think it's actually supposed to be something like deviceId: { exact: "...deviceId..." } but just specifying a deviceId seems to work.
I honestly have not been able to figure out how to get my layout to do exactly what I want on mobile, Chrome on mobile acts differently than Chrome on desktop with video elements that are displaying cameras, and i'm not sure how it's different to try to adjust. I got my app mostly displaying something sort of what i want, via trial and error, and stopped fiddling with it at that point. :|
I noticed when I just switched from a LG G6 to a Moto G Stylus, though, that with the G Stylus, I get what appears to be the entire camera viewfinder in the page, whereas my G6 only gets about half. There's probably something that I don't understand, so I can't make sense out of it.
If you're not seeing drawing results, but your onProcessed is running the code, it's probably something in the html/css causing the canvas to not be visible, or to be under something.

Do I have to call the whole init function again when I want to set the deviceId? Or is there some other function I can call? I am still looking through the example code and see it has a dropdown that allows you to change the device but I have not really found what it actually changes.
So you have not been able to get it full screen on mobile either?
I know the processing is working as I do see the boxes that codes is drawing, the thing is it is drawing it like in the wrong areas. I don't know if I need more css styling as I saw what I think is alot of styling in the example css but since there is no comments on it I have no clue how it works.

oh, right, i misunderstood.  That likely means that your drawing canvas is not positioned over the top of your video element.  I get the same situation when I rotate my phone, because I think Chrome automatically rotates the video element, but doesn't do anything with the canvas, and I haven't investigated how to handle that yet.
If you have Quagga already running (Quagga.start()) then call Quagga.stop() before calling Quagga.init() again.  That should work.  Otherwise, if you haven't called start() already then just call init() again.  I think. :-D
In the first version of my app, I tried to do a full-screen but I'd always end up with half of the video element off screen, OR it only taking up a quarter of the screen.  Now I've got it inline in my page, in a little drawer that slides out, and imo, it looks quite nice like that. :)

oh, right, i misunderstood. That likely means that your drawing canvas is not positioned over the top of your video element. I get the same situation when I rotate my phone, because I think Chrome automatically rotates the video element, but doesn't do anything with the canvas, and I haven't investigated how to handle that yet.
If you have Quagga already running (Quagga.start()) then call Quagga.stop() before calling Quagga.init() again. That should work. Otherwise, if you haven't called start() already then just call init() again. I think. :-D
In the first version of my app, I tried to do a full-screen but I'd always end up with half of the video element off screen, OR it only taking up a quarter of the screen. Now I've got it inline in my page, in a little drawer that slides out, and imo, it looks quite nice like that. :)

what do you set your width and height too?
Is it possible to see your html and css? I am still trying to get the sizing right and the boxes correct.

Also anyone have tips on how to reduce false positives? I am doing UPC/EAN

This could really use some cleanup, I've hacked it together from posts on the original repo, as well as my own ideas
function getMedian(arr) {
    const sorted = [...arr].sort((a, b) => a - b);
    const half = Math.floor(sorted.length / 2);
    if (arr.length % 2 === 1) {
        return arr[half];
    }
    return (arr[half - 1] + arr[half]) / 2;
}

function getMedianOfCodeErrors(decodedCodes) {
    const errors = decodedCodes.filter((x) => x.error !== undefined).map((y) => y.error); // TODO: use reduce
    const median = getMedian(errors);
    return { probablyValid: !(median > 0.10 || errors.some((err) => err > 0.1)), median };
}

    const errorCheck = useCallback((result) => {
        if (!onDetected) {
            return;
        }
        const err = getMedianOfCodeErrors(result.codeResult.decodedCodes);
        const validated = barcodeValidator(result.codeResult.code);
        console.warn('* errorCheck', result.codeResult.code, err, validated);
        if (err.probablyValid || (err.median < 0.25 && validated.valid === true && (validated.type === 'upc' || validated.type === 'isbn10' || validated.type === 'isbn13'))) {
            const resultCopy = { ...result };
            resultCopy.codeResult.code = validated.modifiedCode;
            onDetected(result);
        }
    }, [onDetected]);

basically, if the median of errors is less than 0.1, accept it. if the median of errors is less than 0.25 and it appears to be a valid upc, isbn10, or isbn13, then accept it.  otherwise, continue scanning
I believe this is a simplified version of what i'm using https://github.com/ericblade/quagga2-react-example
though it has been a while since i put that together, and there's probably ways to improve it.

This could really use some cleanup, I've hacked it together from posts on the original repo, as well as my own ideas
function getMedian(arr) {
    const sorted = [...arr].sort((a, b) => a - b);
    const half = Math.floor(sorted.length / 2);
    if (arr.length % 2 === 1) {
        return arr[half];
    }
    return (arr[half - 1] + arr[half]) / 2;
}

function getMedianOfCodeErrors(decodedCodes) {
    const errors = decodedCodes.filter((x) => x.error !== undefined).map((y) => y.error); // TODO: use reduce
    const median = getMedian(errors);
    return { probablyValid: !(median > 0.10 || errors.some((err) => err > 0.1)), median };
}

    const errorCheck = useCallback((result) => {
        if (!onDetected) {
            return;
        }
        const err = getMedianOfCodeErrors(result.codeResult.decodedCodes);
        const validated = barcodeValidator(result.codeResult.code);
        console.warn('* errorCheck', result.codeResult.code, err, validated);
        if (err.probablyValid || (err.median < 0.25 && validated.valid === true && (validated.type === 'upc' || validated.type === 'isbn10' || validated.type === 'isbn13'))) {
            const resultCopy = { ...result };
            resultCopy.codeResult.code = validated.modifiedCode;
            onDetected(result);
        }
    }, [onDetected]);

basically, if the median of errors is less than 0.1, accept it. if the median of errors is less than 0.25 and it appears to be a valid upc, isbn10, or isbn13, then accept it. otherwise, continue scanning
I believe this is a simplified version of what i'm using https://github.com/ericblade/quagga2-react-example
though it has been a while since i put that together, and there's probably ways to improve it.

ok, I will try this and see how it goes. I need EAN so I guess I would need to add that to the if statement?
Also where do I put this code? Is this on processes?

@tinnielam
Hey, can you please test my POC on your samsung s20 and let me know if it works(ie can you scan a barcode) and if it did not work what browser
https://barcodes.z4.web.core.windows.net/
I sent it out for testing and I heard on 1 s20 it works and on another it did not.

@chobo2  your POC works yes.

@chobo2 your POC works yes.

So it could load up and Scan a barcode (did the rectangles go over the right area?)
Could you please tell me what version of Android and which browser you used? Also is your s20 plus or s20?
Thanks


568 update navigation

This PR:

Removes jQuery from header and footer
Updates navigation and footer links
If travis checks do not pass, redirects are in place on opentrons.com

Closing for now. New PR pending in tomorrow based off current master.


Command to run create_composer-rest-server.sh script is wrong

The command given in this section does not work
https://github.com/IBM-Blockchain/ibm-blockchain.github.io/blob/master/_pages/03_Interacting with your blockchain.md#4-start-and-access-the-composer-rest-server
It looks like the script used to rely on a hard-coded business network name somewhere  but now it requires one to be passed in from the command line.
This also makes the comment above it, about the .yaml file, wrong, since it is no longer set up for a default business network

@hancockp-at-ibm yes seems like Pull Request changed that. @sstone1 Can you change the documentation to what is required to be passed?

@hancockp-at-ibm fixed!


Host-coherent texel buffers

MVKDeviceBuffer cache management code calls the flushToDevice and pullFromDevice methods on MVKBuffers without regard to their location and overlap with given range. In the first commit I changed those methods to check for overlap and adjust the range, similarly to how it's done in MVKImage.
The other one allows host-coherent texel buffers to be bound as plain buffers using proper host-coherent memory directly, and not the auxiliary buffer. It is only used for buffer views, when a Metal texture needs to be created.
This fixes a problem which arised when using dxvk, which creates buffers with VK_BUFFER_USAGE_UNIFORM_TEXEL_BUFFER_BIT set when the more general D3D11_BIND_SHADER_RESOURCE is used. The root cause of the problem is cache management, or rather the lack of it, for persistently mapped buffers, which I'm not sure how to fix. Even if it was fixed though, this way is still more efficient.
I'm unsure about thread safety here. Should not MVKBuffer::getMTLBuffer (and MVKBuffer::getMTLBufferCache alike) be protected with a lock?

Are you comfortable adding these locks here...following the pattern for getMTLTexture() implementations in MVKBufferView and MVKImagePlane?

I think for double-checking to be bullet proof, one also needs to use atomic operations with proper memory barriers. I'm not sure how it's handled in Objective-C++. Might be worth looking into to prevent heisenbugs..

to be bullet proof...use atomic operations with proper memory barriers.

Good point. I'll look into this later on. Thanks for adding the basics for now.


Is there any vanilla JavaScript version of this library?

To use current netless-io/video-js-plugin we required to include react, react-dom as dependencies. But I want to use inside an angular project. So if there is any Vanilla JavaScript version available of this library then no need to include react unnecessary.
Thank You.

No.
The plugin API in white-web-sdk requires a react component to be returned, besides white-web-sdk also has a dependency of react. So in fact you cannot get rid of a copy of react anyway, the sdk is heavily built on top of that.
It is recommended to try window manager with fastboard if you're new to the whiteboard sdk, the former defines a nicer plugin api called "netless app" which does not depend on any frameworks or abstract classes. It also includes built-in apps of media player and docs viewer that are ready to use without any extra installation steps. (However keep in mind that all of them are built on top of white-web-sdk, so a dependency of react will not vanish.)

Okay Thanks for information @hyrious. I will try window manager. I think we can also use window manager with white-web-sdk, right ?

Yes, the relations between them are as follows:

white-web-sdk provides data sync service and whiteboard render engine
@netless/window-manager wraps white-web-sdk, provides multi-window features and the api for netless apps

@netless/app-media-player the player app that implements the netless app api, built-in in window-manager

@netless/fastboard wraps white-web-sdk and window-manager, provides many simplified api for common use case

Although you can directly use window-manager, we found that the initialization code is a bit complicated for everyone to write correctly, that's why we made fastboard to simplify users' works.

Okay. Thanks. I will follow this.


fix for invalid expires value

Fixes bug for PHP 7.1+:

A non-numeric value encountered

When attempting to add a non-numeric value $expires to getTimeNow an error is thrown. This should be non-breaking and preserve PHP 5 behavior.

Merged to the master branch in https://github.com/thephpleague/oauth2-client/commit/8cee80a295a66c6542159596ae0391a557afa7a2
Thank you for contributing! 🎉


Sophus ensure failed

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
When playing back svo2 and doing positional tracking GEN2, it works like normal for a while and then I get this error. This only happens to some svo2 files, but I have no idea what causes it. This is a problem because I am using the zed for data collection, so I need to be able to reliably run the positional tracking offline.
Link to svo file: https://drive.google.com/file/d/1y0ktUFY-hM0JCA84siHiju32R7aO7TsW/view?usp=sharing
Sophus ensure failed in function 'static IOFTRACKER_Sophus::SO3<Scalar_> IOFTRACKER_Sophus::SO3<Scalar_, Options>::expAndTheta(const Tangent&, IOFTRACKER_Sophus::SO3<Scalar_, Options>::Scalar*) [with Scalar_ = float; int Options = 0; IOFTRACKER_Sophus::SO3<Scalar_, Options>::Tangent = Eigen::Matrix<float, 3, 1>; IOFTRACKER_Sophus::SO3<Scalar_, Options>::Scalar = float]', file '/builds/sl/ZEDKit/lib/include/sl_core/tracking/Tracker/IOFTracker/sophus/so3.hpp', line 612.
Steps to Reproduce

Load SVO2 file
Enable Positional Tracking
Get positions and grab camera frames
Error appears out of nowhere
...

Expected Result
Positional Tracking continues and finishes when svo runs out.
Actual Result
The program aborts
ZED Camera model
ZED Mini
Environment
Zed SDK 4.2 (using the python SDK)
Python Version = Python 3.10.12
Ubuntu 22.04

Anything else?
My function:
def process_svo_gen2(file_path, all_data, use_viewer = False, show_image = False, skip_slam = False, use_imu = True):
    # Create a ZED camera object
    zed = sl.Camera()

    # Initialize the parameters for opening the SVO file
    init_params = sl.InitParameters()
    init_params.set_from_svo_file(file_path)
    init_params.svo_real_time_mode = False  # Disable real-time mode for better processing
    init_params.coordinate_units = sl.UNIT.METER
    init_params.coordinate_system = sl.COORDINATE_SYSTEM.RIGHT_HANDED_Z_UP # Set a coordinate system for tracking
    init_params.depth_mode = sl.DEPTH_MODE.ULTRA

    # Open the SVO file
    status = zed.open(init_params)
    if status != sl.ERROR_CODE.SUCCESS:
        print(f"Failed to open SVO file: {status}")
        return

    if not skip_slam:
        # Enable positional tracking
        tracking_params = sl.PositionalTrackingParameters()
        tracking_params.set_gravity_as_origin = False
        tracking_params.enable_area_memory = True
        tracking_params.enable_pose_smoothing = False
        tracking_params.enable_imu_fusion = use_imu
        tracking_params.mode = sl.POSITIONAL_TRACKING_MODE.GEN_2
        # tracking_params.area_file_path = "test.area"

        status = zed.enable_positional_tracking(tracking_params)

        if status != sl.ERROR_CODE.SUCCESS:
            print(f"Failed to enable positional tracking: {status}")
            zed.close()
            return

    all_episodes = sorted(all_data.keys())

    for ep in all_episodes:
        all_data[ep]["imu_data"] = []
        all_data[ep]["tracked_pose"] = []
        all_data[ep]["trans_pose"] = []
        all_data[ep]["SLAM_failed"] = False

    curr_ep = all_episodes[0] # get the first episode in the list

    if use_viewer:
        camera_info = zed.get_camera_information()
        viewer = gl.GLViewer()
        viewer.init(camera_info.camera_model)

    left_image = sl.Mat()
    image_res = sl.Resolution(320, 240)

    fail_count = 0

    # Loop through frames in the SVO file
    while not use_viewer or viewer.is_available():
        zed_pose = sl.Pose()

        if zed.grab() == sl.ERROR_CODE.SUCCESS:
            # Get the pose of the camera relative to the world frame
            timestamp = zed.get_timestamp(sl.TIME_REFERENCE.IMAGE).get_nanoseconds()

            if use_imu:
                sensor_data = sl.SensorsData()
                if (zed.get_sensors_data(sensor_data, sl.TIME_REFERENCE.IMAGE) == sl.ERROR_CODE.SUCCESS):
                    linacc = sensor_data.get_imu_data().get_linear_acceleration() # meters per second squared
                    angvel = sensor_data.get_imu_data().get_angular_velocity() # degrees per second

                    lx = linacc[0]
                    ly = linacc[1]
                    lz = linacc[2]

                    # convert degrees to radians
                    ax = angvel[0] * np.pi / 180
                    ay = angvel[1] * np.pi / 180
                    az = angvel[2] * np.pi / 180

                    all_data[curr_ep]["imu_data"].append([timestamp, lx, ly, lz, ax, ay, az])

            if not skip_slam:
                state = zed.get_position(zed_pose, sl.REFERENCE_FRAME.WORLD)
                tracking_status = zed.get_positional_tracking_status()

            zed.retrieve_image(left_image, view = sl.VIEW.LEFT, resolution = image_res)

            img = left_image.get_data()

            if show_image:
                cv2.imshow("Image", img)
                key = cv2.waitKey(10)

            if not skip_slam and state == sl.POSITIONAL_TRACKING_STATE.OK:
                # translation_left_to_center = zed.get_camera_information().camera_configuration.calibration_parameters.get_camera_baseline() / 2
                # Display translation and timestamp

                py_translation = sl.Translation()
                tx = zed_pose.get_translation(py_translation).get()[0]
                ty = zed_pose.get_translation(py_translation).get()[1]
                tz = zed_pose.get_translation(py_translation).get()[2]

                #Display orientation quaternion
                py_orientation = sl.Orientation()
                ox = zed_pose.get_orientation(py_orientation).get()[0]
                oy = zed_pose.get_orientation(py_orientation).get()[1]
                oz = zed_pose.get_orientation(py_orientation).get()[2]
                ow = zed_pose.get_orientation(py_orientation).get()[3]

                if use_viewer:
                    rotation = zed_pose.get_rotation_vector()
                    translation = zed_pose.get_translation(py_translation)
                    text_rotation = str((round(rotation[0], 2), round(rotation[1], 2), round(rotation[2], 2)))
                    text_translation = str((round(translation.get()[0], 2), round(translation.get()[1], 2), round(translation.get()[2], 2)))

                    viewer.updateData(zed_pose.pose_data(sl.Transform()), text_translation, text_rotation, tracking_status)
                ```

Hello @boardd,
Replace "crucial" with "important" in the revised message:
Thank you for your feedback. I have tested your SVO2 on the provided code snippet but have been unable to reproduce the issue. To assist further, could you please provide additional details about your configuration setup, such as your CPU/GPU specifications and whether you are running the program independently or concurrently with other processes?
While we have addressed many issues in the upcoming version that could potentially be related to your problem, this particular issue has not been encountered before. It is important for us to reproduce it to determine if it has been resolved with our recent fixes. Kindly share any pertinent information necessary for replicating the error, especially details about your configuration setup and system, as we suspect a synchronization issue may be at play.
Regards,
Tanguy

It appears that there may be a synchronization issue at play. Several significant improvements have been implemented and are slated for next release. These enhancements are intended to address the issue you are experiencing. If these changes do not resolve the problem, we will further investigate to find a solution.
In real-time mode, your SVO2 data is replayed as if it were being captured by a connected camera. If the time taken for runtime frame grabs is less than that of a real camera grab, the system will wait during the subsequent grab to synchronize with the real-time interval specified in the SVO2 data. Conversely, if the grab takes more time than the runtime frame grab specified in the SVO2 data, frames and sensor samples will be skipped to align with the timing of the grab process.
Regards,
Tanguy

Probably. However it is hard to respond without replicating it on our side. If it do not solve your issue, we are close to release a patch with our fix contained in it. Your issue is supposed to be fixed in it. If not we will investigate further.
Regards,
Tanguy


Ideal way to unmount it ? Too many DOM elements present after explosion !

Please suggest a recommended way |!

Sorry to comment on a closed issue but would you mind sharing how to unmount this after explosion? Thanks!


Update submodules for 1.12

I need to 1.7 - 1.12 support still and it hasn't been updated on your Jenkins yet.

Yes! Forge support and 1.12 for networks using 1.7+ would be great.
Sidenote: Tried Hexacord's update, but no luck.

@trebiluk I built Travertine on my own Jenkins. https://ci.incursio.net/job/Travertine/

it seems your custom build doesn't support 1.7.10, have yet to test 1.8-1.10, however 1.11 and 1.12 work fine

Yes, @EXilE-EXistance and I get Custom Payload error with 1.7.10 Forge 1614 (SpaceAstronomy 1.6.6 FTB pack)

Hmm. I guess it needs to be resolved with a patch.


Training

Hello,
If there are 10,000 lines in training_text file and there are 120 fonts then each line is rendered for all fonts, that is there will be total 120,0000 lines in the image? Or is better to randomly pick a font for each line and render it on that font so that we have 10,000 lines in the image?
For training is it better to use line by line images or full page text images?

Please use our forum for asking questions.


Spelling Error

In the formatting section of the tutorial where users are asked to add a background shape for visuals 2 and 3. The following instruction is provided:
Fill section, set the coloer to White, 10% darker
The word color is spelled incorrectly.

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

ID: 1e0083e3-c11c-2462-6f0f-a166759f14c0
Version Independent ID: 927cc95e-d442-db4d-75ae-d4a2fa64ae71
Content: Tutorial: From Excel workbook to stunning report in Power BI Desktop - Power BI
Content Source: powerbi-docs/create-reports/desktop-excel-stunning-report.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks, @skstanley11 ! Fixing it now, will be live this afternoon June 23, Pacific time. Love those easy fixes! 😊

@maggiesMSFT thanks for picking this one up and knocking it out of the park! These tutorials are absolutely wonderful, we appreciate them and your efforts!


Is it suitable for the project which don’t have many different sizes of images?

In our project there are not many different sizes of images，just one kind of size，weather the image pipeline is still suitable for  our project ?

Absolutely.  Multi-variant support and optimizations are but one of the many features.  You still get so many other features built in.  See issue #9

Thanks a lot!

when different threads accessing to CGContext based functions at the same time will cause sigkill?


Frontend development

Closes #16

Added react library + typescript
Added husky, prettier, eslint
Added components based on designs
Added a hook to fetch the deals
Used https://jenil.github.io/chota/ as a base css framework

Searching for this FileCID bafk4chzacz25vocaikhd5ymybajp2nzloftpugfvnuksfbw2fmspa4jmdina will going to return all the data (status information)

Some images how it looks

Looks good to me.
Since the UI application is pretty small and uses standard things there is not much to explain or document. One can pretty much start checking the dependencies and infer what files should be modified to start applying changes.

Great, I will create some small issues to improve the README file, and close this PR. Thanks


Use the proper version of SINTEF/ci-cd

Closes #33
Closes #35
Return to using v1 for SINTEF/ci-cd callable workflows.

Codecov Report
Base: 73.57% // Head: 73.57% // No change to project coverage :thumbsup:

Coverage data is based on head (6d49dfc) compared to base (95f1d4c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #36   +/-   ##
=======================================
  Coverage   73.57%   73.57%
=======================================
  Files          10       10
  Lines         598      598
=======================================
  Hits          440      440
  Misses        158      158

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat(app): Integrate the block-sdk

🤜  🤛 From Skip!
In This PR

I integrate the block-sdk

I integrate the mev, default lanes (ordered accordingly) into the LaneMempool which will be used as the app's Mempool
I integrate the Prepare / ProcessProposal handlers and custom CheckTx handlers

Prepare / ProcessProposal will be responsible for building blocks
The CheckTx handler is responsible for

Performing extra verification on bid-txs
Purging txs from cometBFT's mempool if they aren't in the app

Modules

I integrate the x/auction module, and the corresponding AnteHandler for the auction module

Testing

We've tested this integration against our own set of load-tests. These tests, spin up a network of 5 nodes (3 val, 1 seed, 1 full). Perform various perturbations against them (killing, restarting, disconnecting from the network, etc.), and periodically send a load of 350 tx/sec for 90s. The output from one of our trials is here, happy to go through these in more depth / review the methodology.

Let's Discuss

I configured the x/auction module in the v202 upgrade handler. The params chosen are here, happy to change these if requested
I also configured the lane mempool capacities / other parameters here

Thx!


Introduced behavior_label, and changed risk_score to integer

Example of library-api-labels updated in accordance to what is reported in deliverable D2.5

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.824%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
117

Relevant Lines:
170

💛  - Coveralls


Consider adding cgroup driver or other workaround to support pod level QoS

Encountered this issue when working on pod level QoS support: #271. This feature is important for fine grained QoS tiers, and meaningful to hypervisor containers like runV, CC to figure out its VM's resource boundary.
Background:
The basic idea of pod level QoS is: kubelet will create a pod level cgroupParent path and pass this value to runtimes, so for example, in CRI+docker we will have /Bu/Bu-podxxx/ as parent, and create cgroupfs like this:
/Bu/Bu-podxxx/containerID/memory_limit_of_container
/Bu/Bu-podxxx/memory_limit_of_pod

That's why runtime should be aware of cgroup driver and convert /Bu/Bu-podxxx/ to /Bu.slice/Bu-podxxx.slice/ if needed.
The Problem:
But I see now cri-o just pass cgroupParent directly to runC, which would not work for pod level QoS because cri-o is expected to add containerID after /Bu/Bu-podxxx/ and make sure this newly created cgroupPath in right syntax.
Proposal:
So, we can:

make cri-o become cgroup driver aware
stick to only one type of cgroup driver
make runC be able to deal with syntax convert
make kubelet generate cgroupParent in right syntax. (This is unlikely since CRI does not assume runtime expose cgroup information or define a Info() api)

One concern is cgroup awareness requires taking care of consistency with runC's configuration.
Any suggestion on this problem?

@mrunalp @cyphar

I would recommend just sticking with runC's cgroupfs driver. The systemd one is ... questionable at best.

while @mrunalp thought both cgroup type should be supported, https://github.com/kubernetes-incubator/cri-o/pull/271#issuecomment-267198572  ...
btw, is runc using systemd by default (did not look code, just based on my env)

Default is cgroupfs.

@cyphar So could you please explain more details about your concern about systemd?

We have had a very long history if issues with systemd. The TransientUnit DBus API that they provide does not have enough controls for our cgroup modification requirements in runC -- so what we do is that we manually modify the cgroup settings after setting up a systemd slice (using the cgroupfs code).
So the only difference between cgroupfs and systemd is that with systemd we tell systemd about the container we're creating. The problem with that is that systemd quite often has issues where it will randomly start moving cgroups around which then means that containers get broken. This has been moving to be more usable in more recent versions of systemd (especially with the Delegate keyword).
However, I'm still not one to trust systemd. I think their model (one daemon that manages absolutely everything) clashes with how runC operates -- and trying to resolve the issue completely would require us to effectively reimplement systemd-nspawn (and thus become rkt).

I think we should continue to support both.  At some point Systemd might be come the sole controller/designator for Cgroups, as cgroup2 gets implemented.

@rhatdan

as cgroup2 gets implemented.

Heh, cgroup2 is already implemented (in the kernel, the runC code still isn't there because I still haven't managed to boot a system using cgroupv2) and systemd is basically enshrined as the only controller for the whole stack. The only way to get out of it is to ask systemd to delegate to you (which Docker already requires and ocid will also require), at which point you should be using cgroupfs.

OK, so let's stick to cgroupfs in code and close this for now. Thank you for all advices.


fix broken link:http://kubernetes.io/docs/contribute/style/page-templ…

…ates/

/language vi

/cc @kubernetes/sig-docs-vi-reviews

/remove-lifecycle stale

Hello @CriaHu .
I plan on closing this pull request.
When you are ready to resume work, feel free to reopen.
Thanks!
/close


New release of Graph Pages API does not return any Webparts

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Describe the bug / error
The Graph endpoint for getting Webparts for a SharePoint page always returns an empty array or a Bad Request - 400.
There are 3 methods of getting Webparts for a page as
https://learn.microsoft.com/en-us/graph/api/webpart-list?view=graph-rest-beta

Tested in Graph Explorer with different pages:
https://graph.microsoft.com/beta/sites/{site-id}/pages/{pageId}/webparts

This always return an empty array:
{
<EMAIL_ADDRESS>"https://graph.microsoft.com/beta/$metadata#sites('{site-id}')/pages('{page-id}')/webParts",
"value": []
}

GET /sites/{sitesId}/pages/{sitePageId}/canvasLayout/verticalSection/webparts
The following endpoint just gives a "Bad Request - 400".

GET sites/{sitesId}/pages/{sitePageId}/canvasLayout/horizontalSections/{horizontalSectionId }/columns/{horizontalSectionColumnId}/webparts

In order to use this endpoint I should first get the horizontalSectionId:
GET /sites/{sitesId}/pages/{sitePageId}/canvasLayout/horizontalSections
This also just gives a "Bad Request - 400".
So I cannot retrieve any information about the Webparts. Seems that these API's are not working yet? Any ETA?
Steps to reproduce

Create a SharePoint page. Add 1 text block with text 'test' and set title to 'test graph page'
Log into Graph Explorer and use the list pages endpoint to get the Id of the just created page
https://graph.microsoft.com/beta/sites/{site-id}/pages
With the page id, run: https://graph.microsoft.com/beta/sites/{site-id}/pages/{page-id}/webparts

Expected behavior
Expected is to get 1 webpart for the text entered in the newly created page
{
<EMAIL_ADDRESS>"https://graph.microsoft.com/beta/$metadata#sites('site')/pages('page')/webParts",
"value": [ {EXPECTED WEBPART DATA} ]
}

Hi, seems like you're fixing this API :-)
I get some webpart data but not all of it. When I edit a page and add a new section, I get that data but not existing/unmodified pages. Can you please confirm that you are currently rolling out updates or is this a caching issue? I can do some further tests if that would help in my region. Let me know.. Other tenants still have the 'operation not supported' issue by the way. Is this a deliberate status in the meantime that updates are rolled out? Any ETA would be appreciated.

@redlab-chris - Based on testing I've been doing with API as it's currently deployed, the endpoint format for retrieving the webParts collection might now be:
https://graph.microsoft.com/beta/sites/{site-id}/pages/{page-id}?expand=webParts
It's still not 100% working, and I opened up a bug report #8657 about a specific issue I did see while working on breaking changes in this updated API.

@redlab-chris : Does this still repro? We were in the middle of code rollout and had some issues which we think have been resolved. Can you please check and confirm?


Add merge_operations and merge_moments transformer primitives

The PR introduces new transformer primitives -- merge_operations and merge_moments, as proposed in https://tinyurl.com/moment-preserving-transformers.
Part of roadmap item #3237 and #4483

@dabacon @maffoo Please let me know if you have any further comments or if you are okay with merging this.

@dabacon @maffoo Gentle reminder. PTAL.


Simulation Stop Rule

Hello! I've been finding this simulation tool extremely useful, and think a feature that would enhance this is to be able to have a rule type which will terminate a simulation when a specified condition is met. What I have in mind I think would be a heaviside function that would end the simulation when a species, or the sum of a subset of the species (kept track of by an additive rule) exceeds or goes below some threshold. Ideally it would return the truncated simulation.
Thanks @rlwillia for the suggestion

@rlwillia: would an algebraic expression with =, <, or > stopping the simulation as soon as the expression is true be sufficient? Code for this kind of rule already exists in lineages in order to divide so we could very easy extend it to stop a non-lineage simulation.

Yeah! That sort of rule would be perfect.
Best,
Rory
Get Outlook for iOShttps://aka.ms/o0ukef

From: William Poole<EMAIL_ADDRESS>Sent: Tuesday, April 28, 2020 10:26:46 AM
To: biocircuits/bioscrape<EMAIL_ADDRESS>Cc: Williams, Rory L<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [biocircuits/bioscrape] Simulation Stop Rule (#27)
@rlwilliahttps://github.com/rlwillia: would an algebraic expression with =, <, or > stopping the simulation as soon as the expression is true be sufficient? Code for this kind of rule already exists in lineages in order to divide so we could very easy extend it to stop a non-lineage simulation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/biocircuits/bioscrape/issues/27#issuecomment-620746641, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFIOWTTVGODMR6FT26GO4L3RO4GVNANCNFSM4MTAWDPQ.


Make configurable no-javascript message to please indexers

🚀 Feature
Currently this message is indexed (google it) on ALL sites using docusaurus:
"Your Docusaurus site did not load properly."
It would be nice to let us configure that message so that we at least have some control over our crawl presence on the web.
Have you read the [Contributing Guidelines on issues]
yes

Thanks for reporting this.
Can you explain how this affects your site exactly?
I mean, no one is googling for "Your Docusaurus site did not load properly.", so how did you find it was a problem, and how customizing the message will solve it?
Maybe we should also add an opt-in option to remove it?

Thanks for reporting this.
Can you explain how this affects your site exactly?
I mean, no one is googling for "Your Docusaurus site did not load properly.", so how did you find it was a problem, and how customizing the message will solve it?
Maybe we should also add an opt-in option to remove it?

I see a lot of docusaurus doc sites be indexed by google that way, probably since it is hosted as static only.
I was just offering you to search for that exact string so you can see the scale of the problem.
Maybe crawlers can be told to ONLY index meta description instead of that message, but I am not very deep into html specs any more...

I see a lot of docusaurus doc sites be indexed by google that way, probably since it is hosted as static only.
I was just offering you to search for that exact string so you can see the scale of the problem.
Maybe crawlers can be told to ONLY index meta description instead of that message, but I am not very deep into html specs any more...

https://www.google.com/search?q="Your+Docusaurus+site+did+not+load+properly."&rlz=1C5CHFA_enFR749FR749&oq="Your+Docusaurus+site+did+not+load+properly."&aqs=chrome.0.69i59.4303j0j7&sourceid=chrome&ie=UTF-8
I do agree that these Docusaurus 2 sites get indexed in an unexpected way, and we should likely offer a way to disable that.
I just wonder why specifically it is a problem for you and your users?
How does it impact your business/SEO in a concrete way?
What did a regular user type, and why was he disappointed?
It is very unlikely that a user will type such a string on Google, and when searching for "Docusaurus 2"

I'm just trying to understand better your motivations to figure out the best way to do something about it.
Maybe by default we could write "your site www.xyz.com did not load properly" or something?
Does a new config option really solve the problem? As many site owners wouldn't even be aware of that option?

https://www.google.com/search?q="Your+Docusaurus+site+did+not+load+properly."&rlz=1C5CHFA_enFR749FR749&oq="Your+Docusaurus+site+did+not+load+properly."&aqs=chrome.0.69i59.4303j0j7&sourceid=chrome&ie=UTF-8
I do agree that these Docusaurus 2 sites get indexed in an unexpected way, and we should likely offer a way to disable that.
I just wonder why specifically it is a problem for you and your users?
How does it impact your business/SEO in a concrete way?
What did a regular user type, and why was he disappointed?
It is very unlikely that a user will type such a string on Google, and when searching for "Docusaurus 2"

I'm just trying to understand better your motivations to figure out the best way to do something about it.
Maybe by default we could write "your site www.xyz.com did not load properly" or something?
Does a new config option really solve the problem? As many site owners wouldn't even be aware of that option?

I found our site to be indexed with that message, so it's not about how and via what route I found out about that. Only then did I do an extra search for that string, to reveal the scale of this.

I found our site to be indexed with that message, so it's not about how and via what route I found out about that. Only then did I do an extra search for that string, to reveal the scale of this.

I have to say I am not aware anymore of what I searched for, but it was the day of a media announcement and was generating some keyword combos and then saw it indexed like that. I just tried some again but can't reproduce.

I have to say I am not aware anymore of what I searched for, but it was the day of a media announcement and was generating some keyword combos and then saw it indexed like that. I just tried some again but can't reproduce.

I understand.
Will try to find a solution, not sure I can totally prevent it to be indexed but at least it should be possible to disable/customize it.

I understand.
Will try to find a solution, not sure I can totally prevent it to be indexed but at least it should be possible to disable/customize it.

Thanks for being so sweet. Sorry about my hammering. It's no prio.

Thanks for being so sweet. Sorry about my hammering. It's no prio.

Same problem with us (https://atman-iot.com)
Our site was built on docusaurus 2.
If you search on google for "atman iot" you will see the following snipet:
Your Docusaurus site did not load properly. A very common reason is a wrong site baseUrl configuration. Current configured baseUrl = / (default value).
At the same time the page loads properly from my pc. Any ideas?

Same problem with us (https://atman-iot.com)
Our site was built on docusaurus 2.
If you search on google for "atman iot" you will see the following snipet:
Your Docusaurus site did not load properly. A very common reason is a wrong site baseUrl configuration. Current configured baseUrl = / (default value).
At the same time the page loads properly from my pc. Any ideas?

Hey,
Totally forgot about this, but it's already possible to disable this message 😅
https://v2.docusaurus.io/docs/next/docusaurus.config.js/#baseurlissuebanner
Still trying to find a solution, will attempt a few things to make the message not indexed by default, but not sure about the Google Crawler behavior :

Hey,
Totally forgot about this, but it's already possible to disable this message 😅
https://v2.docusaurus.io/docs/next/docusaurus.config.js/#baseurlissuebanner
Still trying to find a solution, will attempt a few things to make the message not indexed by default, but not sure about the Google Crawler behavior :

https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore. This should prevent the google indexation.
As it is possible to disable this banner with config, and it should normally not be indexed anymore, I don't think it's worth it to be able to customize that message.
Going to close this for now, but we'll check if the message is still indexed or not soon.

https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore. This should prevent the google indexation.
As it is possible to disable this banner with config, and it should normally not be indexed anymore, I don't think it's worth it to be able to customize that message.
Going to close this for now, but we'll check if the message is still indexed or not soon.

The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber<EMAIL_ADDRESS>wrote:

#4125 https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore.
This should prevent the google indexation.
As it is possible to disable this banner with config, and it should
normally not be indexed anymore, I don't think it's worth it to be able to
customize that message.
Going to close this for now, but we'll check if the message is still
indexed or not soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4028#issuecomment-769916816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ
.

The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber<EMAIL_ADDRESS>wrote:

#4125 https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore.
This should prevent the google indexation.
As it is possible to disable this banner with config, and it should
normally not be indexed anymore, I don't think it's worth it to be able to
customize that message.
Going to close this for now, but we'll check if the message is still
indexed or not soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4028#issuecomment-769916816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ
.

But if it was disabled by default it would not have any effect 😅 users
generally have this problem when they first try to deploy their site in
production.
Not sure what to do if my latest attempt does not work. Hope it will work!
😄
Le ven. 29 janv. 2021 à 20:42, kkhoury38<EMAIL_ADDRESS>a
écrit :

The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber<EMAIL_ADDRESS>wrote:

#4125 https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore.
This should prevent the google indexation.
As it is possible to disable this banner with config, and it should
normally not be indexed anymore, I don't think it's worth it to be able
to
customize that message.
Going to close this for now, but we'll check if the message is still
indexed or not soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/facebook/docusaurus/issues/4028#issuecomment-769916816
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4028#issuecomment-770009695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PVJZO3S6EXGVYYRL7TS4MFSXANCNFSM4V7E3VYQ
.

But if it was disabled by default it would not have any effect 😅 users
generally have this problem when they first try to deploy their site in
production.
Not sure what to do if my latest attempt does not work. Hope it will work!
😄
Le ven. 29 janv. 2021 à 20:42, kkhoury38<EMAIL_ADDRESS>a
écrit :

The message is a helpful pointer for new users but in general I think it
could be omitted. By searching online for the exact message, there is a
number of docusaurus pages that have the issue so my opinion is that it
creates more problems that the problems it solves.
An idea could be to disable it by default on anything except localhost.
Anyway, thanks a lot for your response!
On Fri, 29 Jan 2021 at 18:44, Sébastien Lorber<EMAIL_ADDRESS>wrote:

#4125 https://github.com/facebook/docusaurus/pull/4125
This PR will ensure that the help banner is not server-rendered anymore.
This should prevent the google indexation.
As it is possible to disable this banner with config, and it should
normally not be indexed anymore, I don't think it's worth it to be able
to
customize that message.
Going to close this for now, but we'll check if the message is still
indexed or not soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/facebook/docusaurus/issues/4028#issuecomment-769916816
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AL4R4HGEGJAUG5VRL5FTE3TS4LQXBANCNFSM4V7E3VYQ
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/4028#issuecomment-770009695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PVJZO3S6EXGVYYRL7TS4MFSXANCNFSM4V7E3VYQ
.

Searching for site:v2.docusaurus.io + "your docusaurus site did not load properly." does not show any result with that exact string, so it should be fixed in next release


Model-based unit test for multiframe reassembly runs out of memory

The currently ignored test model_sequence_test_multi_frame_receiver in many cases causes an extremely high memory usage. Either the parameters for the sequence generation need to be tuned down, or the potential memory leak in the state machine fixed.

Fixed in 1189f05 and ancestors in casper-network/juliet


Heroku Deploy Error:  "pysqlite is not supported on Python 3"

-----> Python app detected
-----> Installing python-3.6.7
-----> Installing pip
-----> Installing SQLite3
-----> Installing requirements with pip
pysqlite is not supported on Python 3. When using Python 3, use the sqlite3 module from the standard library.
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-hubzk065/pysqlite/
Push rejected, failed to compile Python app.
Push failed

mrbelvedere doesn't work with Python 3 and likely never will.  We're actually pretty far along in the development process of the replacement for mrbelvedere which will be called MetaDeploy.  I'd recommend waiting until MetaDeploy is ready (likely in a few months), instead of trying to deploy a new instance of mrbelvedere on Heroku now.


Support collection view items with different height

E.g. some items would contain an icon and be taller than text-only items.

Dup of #173.


Plenty of missing crafting recipes

So far the missing crafting recipes I've found are:
Brush
Soul torch
Tipped arrows
Beehive
Recovery compass
Spyglass
There could be more, so here's website that could help you find all of the missing crafting recipes:
https://www.minecraft-crafting.net/

Added in version 1.5, thanks for reporting.


feature: POST /invocation/{AwsRequestId}/response API

Codecov Report

Merging #6 (2bb8957) into main (3b2773b) will increase coverage by 2.05%.
The diff coverage is 100.00%.

:exclamation: Current head 2bb8957 differs from pull request most recent head 43ef83f. Consider uploading reports for the commit 43ef83f to get more accurate results

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   92.94%   95.00%   +2.05%
==========================================
  Files           4        4
  Lines          85      120      +35
==========================================
+ Hits           79      114      +35
  Misses          4        4
  Partials        2        2

Impacted Files
Coverage Δ

runtime/invocation/types.go
100.00% <ø> (ø)

runtime/invocation/api.go
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update Copyright information from 2021 to 2022

Update the copyright information in all files in the directories and subdirectories recursively using bash stream editor - sed
Command used:
find . -type f -not -path '/.' -exec sed -i 's/2021/2022/g' {} +
Number of files changed:
273
Number of replacements made:
275

Nice one. Could you also change it in editorconfig file?

Nice one. Could you also change it in editorconfig file?

Sure. I just skipped the hidden files. I'll do it now.

@WhiteBlackGoose  I have made the necessary changes.
Feel free to reach out in case of any other changes needed.

Awesome, thanks!


python312Packages.aiooss2: 0.2.9 -> 0.2.10

Diff: https://github.com/karajan1001/aiooss2/compare/refs/tags/0.2.9...0.2.10
Changelog: https://github.com/karajan1001/aiooss2/blob/0.2.10/CHANGES.txt
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 298396 run on x86_64-linux 1

8 packages built:

python311Packages.aiooss2
python311Packages.aiooss2.dist
python311Packages.ossfs
python311Packages.ossfs.dist
python312Packages.aiooss2
python312Packages.aiooss2.dist
python312Packages.ossfs
python312Packages.ossfs.dist

Result of nixpkgs-review pr 298396 run on x86_64-linux 1

8 packages built:

python311Packages.aiooss2
python311Packages.aiooss2.dist
python311Packages.ossfs
python311Packages.ossfs.dist
python312Packages.aiooss2
python312Packages.aiooss2.dist
python312Packages.ossfs
python312Packages.ossfs.dist


Use binary release of dep

Thank you for your contribution to Go-AutoRest! We will triage and review it as soon as we can.
As part of submitting, please make sure you can make the following assertions:

[ ] I've tested my changes, adding unit tests if applicable.
[ ] I've added Apache 2.0 Headers to the top of any new source files.
[ ] I'm submitting this PR to the dev branch, except in the case of urgent bug fixes warranting their own release.
[ ] If I'm targeting master, I've updated CHANGELOG.md to address the changes I'm making.

Fixes https://github.com/Azure/azure-sdk-for-go/issues/1006

actually no version increase ?

I didn't bump the version since this doesn't impact any shipping assets.


Make default connection count 1, add a flag for more

This is kinda subjective, perhaps we can wait and see if others agree, but I expect most users need just one proxied connection as they're doing development, where a flag to overwrite the connection count could be helpful, I'm guessing you yourself had a need for more connections for example.

Yeah, have a configurable flag to set the max connection makes a lot sense. Have the default connection count set to be the one from localtunnel server seems better to make client and server consistent.

@kaichaosun by the way, I'm in no hurry for this to work! I just switched to using tunnelto, works well, but also costs money. I'd love for a solid rust tunneling library to exist to help devs. So I thought I'd still report what I'd need to be able to use this instead of other tools, but paying $2 / month for tunnelto is no big deal either in the meantime.
RE: default matching the localtunnel server, that makes total sense! 👍


add loader for file: URLs

I used the url crate was the to_file_path method, which I don't think iref provides.
You're right, I should add a similar function into iref.


Customize port forwarding

Setup

Rancher version:
Browser type & version:

Describe the bug
Following the request of this issue
https://github.com/rancher-sandbox/rancher-desktop/issues/791
I will propose a visual mockup that will address the custom post forwarding
To Reproduce

Result
Expected Result

Screenshots

Additional context

Detailed Description

Context

I am transferring this issue to the Rancher Desktop repo. Let me know if it needs to be tracked here instead


Convert rvgo's memory implementation to radix trie

Description
Detailed design doc is at: https://www.notion.so/op-tip/Asterisc-Memory-Optimization-Design-Doc-Draft-b64a61f0c844403d99b59b120cc3222b?pvs=4

Codecov Report
Attention: Patch coverage is 86.04651% with 36 lines in your changes missing coverage. Please review.

Project coverage is 73.08%. Comparing base (636210a) to head (89460e6).
Report is 20 commits behind head on master.

Files with missing lines
Patch %
Lines

rvgo/fast/radix.go
87.98%
15 Missing and 13 partials :warning:

rvgo/fast/page.go
55.55%
8 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #83      +/-   ##
==========================================
+ Coverage   72.30%   73.08%   +0.77%
==========================================
  Files          16       17       +1
  Lines        2723     2913     +190
==========================================
+ Hits         1969     2129     +160
- Misses        670      689      +19
- Partials       84       95      +11

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


Android module and Async Dns

Primarily an Android specific implementation of AsyncDns.
This is intended to unblock the Happy Eyeballs, fast follows implementation to handle IPv4 and IPv6 separately.
AsyncDns should be considered an experimental public API.
@swankjesse I don't know how to do this in okhttp core using Flow. Bringing in kotlinx.coroutines is probably awkward for JVM clients already frustrated at getting kotlin, and more likely to introduce versioning issues that stdlib (which has been perfect).
Also an optional okhttp-android module, to allow specific implementations that are network aware*. Published as an AAR file which might help with android specific optimisations like baseline profiles.
Android apps may often need to understand network conditions, choose the appropriate network, and when doing so
should use the appropriate socket factory, dns, and even proxy.

Two remaining topics

When to pull over the changes for DnsOverHttps
When to consider the design for other Dns records like Svcb, Https (draft RFC https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/)

What if we make it so each request gets a single response, and let the caller pick what’s in that response? If the caller wants one callback we can give them that, and if they want two callbacks we can give them that too?

Makes sense, I'll simplify to this API.  But I'll leave the union implementation and the predefined constants out for now.
    /** Unions the results from [SYSTEM_IPV4_ONLY] and [SYSTEM_IPV6_ONLY]. */
    val SYSTEM: AsyncDns
    val SYSTEM_IPV4_ONLY: AsyncDns
    val SYSTEM_IPV6_ONLY: AsyncDns


json 2 sql server

Hi! i was looking for a tools that let me convert the json to standard .sql files, i'm trying to import a release package into sql server using this structure https://kingfisher-views.readthedocs.io/en/latest/database.html , and wondering if there is a tool that's already inside kingfisher that may help me in this job.
is there a tool available that may help me with this data import 2 sql server using kingfisher database structure?
i am aware of this .sql files: https://github.com/open-contracting/kingfisher-views/tree/master/sql
but they are prepared to get data from a json / jsonb postgresql data type,i was wondering if there are any openjson() input sql server files
thanks!
love the project!

Hi @vlasvlasvlas, I see your other issue here: https://github.com/open-contracting/kingfisher-process/issues/314
Can you send an email to the OCDS Helpdesk at<EMAIL_ADDRESS>? They will be happy to better understand your needs, and suggest some options.

Closing in favor of OCSD Helpdesk support.