App.PageData proper typing isn't enforced in layouts

Describe the bug
Given the following app.d.ts:
declare namespace App {
  interface PageData {
    foo: number;
  }
}

If you do the following in a +page.ts load function:
import type { PageLoad } from './$types';
export const load: PageLoad = () => {
  return {
    foo: 'not a number'
  };
};

You'll get an error (and rightly so) stating that the type of the property foo isn't correct.
However, if you do the same thing in a +layout.ts load function:
import type { LayoutLoad } from './$types';
export const load: LayoutLoad = () => {
  return {
    foo: 'not a number'
  };
};

Now you don't get any errors; you should, obviously, foo has to be a number.
I actually just spent a relatively long time beating my head against the wall trying to figure out what was wrong with some part of my app and eventually found out it came down to me setting the wrong value for a certain property in my +layout.ts, which I wasn't noticing due to there not being any type errors or anything.
Reproduction
Explained above.
Logs
No response
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
    Memory: 953.19 MB / 3.77 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.15.1 - /usr/bin/node
    npm: 8.11.0 - /usr/bin/npm
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.64
    @sveltejs/adapter-node: ^1.0.0-next.86 => 1.0.0-next.86
    @sveltejs/kit: next => 1.0.0-next.445
    svelte: ^3.44.0 => 3.49.0
    vite: ^3.0.0 => 3.0.8

Severity
annoyance
Additional Information
No response

Can't reproduce this, if I paste the code into a +layout.ts and generate the types I get
Type '() => { foo: string; }' is not assignable to type 'LayoutLoad<void | (Partial<PageData> & Record<string, any>)>'.
  Type '{ foo: string; }' is not assignable to type 'MaybePromise<void | (Partial<PageData> & Record<string, any>)>'.
    Type '{ foo: string; }' is not assignable to type 'Partial<PageData> & Record<string, any>'.
      Type '{ foo: string; }' is not assignable to type 'Partial<PageData>'.
        Types of property 'foo' are incompatible.
          Type 'string' is not assignable to type 'number'.ts(2322)

@dummdidumm I just noticed that this problem only exists when there's also a +page.ts, here you go, a repro: https://github.com/aradalvand/sveltekit-load-typing-problem

Still can't reproduce it, I get the expected error in +layout.ts

Wow, that's pretty weird... 🤔
I don't know, maybe you can close this issue and wait to see if this is reported again, if not, then it's probably a glitch on my side. Thanks.

Does that mean it's consistently reproducible on your end with your repo, or can't you reproduce it either reliably?

I can reproduce it like 50% of the time, which is strange.
Sometimes it works as expected and there's an error, sometimes there isn't — for what it's worth, in my actual project I couldn't get it to produce an error no matter how many times I cleared the .svelte-kit directory or restarted the TS server, but in the repro I linked above, it fluctuates. Strange.

I think this used to work before but after some update to sveltekit I am currently not getting ts errors in neither pages not layout. Anybody having the same issue?

@aradalvand I think the problem happens if the load function is async. Can you confirm?

@alialaa It seems like you're right:

Let's see if @dummdidumm can reproduce this now.

I think I understand the problem better now.

Right now the logic is "if there's a page(.server) file, assume that it has a load function". This isn't always correct. We may need to statically analyze each of those files to see if that's really true
(possible bug uncovered while playing around) when I delete a +page.js file next to a layout.js file the types don't get updated
Even with 1 and 2 getting resolved, there's still the "problem" that the type of LayoutLoad assumes that it's the PageLoad's job to fill out the required fields. LayoutLoad will only get more strict typings if not all children have load functions. I don't see a way to make this work so that it works as wanted here, since this is a cyclic relationship: In order to know what type LayoutLoad is, it would need to know what return type PageLoad has. To know what type PageLoad to restrict to, it needs to know the return type of LayoutLoad (properties already set in LayoutLoad are no longer required in PageLoad).


Add support for multiple Pod and Service subnets

Adds dual stack (IPv4 + IPv6) support for:

Service subnets
Pod subnets
API service
DNS service

Ref issue #1079
Signed-off-by: Seán C McCord<EMAIL_ADDRESS>

Still need to hook up template/rendering consolidation.

CLA signed

/approve

@rmenn When you get a chance.

/lgtm


Issue with checkbox

Hi,
there is problem with displaying object with boolean field through do-control component as it uses and sets value, but for checkbox it should use checked property.
Therefore I have to set up something like:
{{#do-form model submit=(action 'update' model) as |form|}}
   {{#form.do-field 'hasName' as |f|}}
      {{f.do-control 'checkbox' checked=model.hasName}}
...

which is very inconvenient. I wonder if there is a workaround?
Thanks.

Hey @firstsano, I'm using the same pattern and I agree that the ergonomics could be improved.
There are plans of including a checkbox control in the same lines as the input-field component for the next version, which should be landing soon.

Ok, thanks. Now I feel relieved that I didn't miss anything, and can use that code for a while :)


Use ruff for linting and error checking

Ruff integrating flake8, many of its plugins and isort all into a single program. It's substantially faster, can auto-fix some types of errors, and allows enabling additional checks in future.
Needs: https://github.com/edoburu/sphinxcontrib-django/pull/48

Codecov Report

Merging #50 (bbc5d4d) into main (09744e4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines          317       317
=========================================
  Hits           317       317

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


Feature/gunderman/bezier polygon

Summary

This PR adds intersection capabilities for polygons with curved edges

This PR adds a CurvedPolygon class and implements an algorithm for computing the intersections of curved polygons and their areas and centroids.  It leaves out some special cases, including tangent polygon intersection and intersections of polygons whose component curves overlap for the following reasons:

Typically tangent polygon intersection won't come up often in practice.
Intersecting polygons whose component curves overlap could come up, but we haven't gotten to this yet.

It also leaves out a full mesh-mesh intersection example, because I'd like to add arbitrary polynomial field transfer (not just areas and centroids) functionality before pushing a full example.

@davidgunderman -- I pushed some changes/bugfixes to this branch.
Here is a brief summary:

I pushed an mfem nurbs mesh to the axom_data submodule.
The quest example no longer depends on a missing mesh.
(This should be converted to a command line argument in the future)
The code now builds and passes all tests on MSVC.
BezierCurve::dt() now returns a primal::Vector, rather than a primal::Point
Some additional minor improvements/corrections in the API
Looks like there is still a compilation problem with macos
(related to sorting? -- https://dev.azure.com/axom/axom/_build/results?buildId=604 )

Superseded by #590, which brings this PR up to date with our develop branch and touches up the code a bit


fix: use the correct status code for timedout

The HTTP status code for timedout is 408 not 308.  This PR:

fixes the status code int used in Page#timedout?
changes the name of the method to is_timedout? for consistency with other methods
aliases the changed method to timedout? for consistency with other methods
moves the method within the file so it's in the correct place with respect to the sequential ordering by status code (probs not necessary but I'm not a total monster)
updates the rspec

I couldn't find any guidance on contributing, so if I've missed anything anywhere, LMK! 🎈

and merged. Thanks!


4-1g

Compared to CLRS2e's 4-1f, doesn't have an explicit assumption that T(n) is constant for n \le 2.


WebComponentWrapper not passing props to the web element

Whne using the WebComponentWrapper and setting the props property this does not appear to set the value into the web element component.
[props]={ 'user': 'test'}

However when checking for the property in a React component the value is null.

Has anyone else experienced the same issue.

class ReactMfe extends HTMLElement {
connectedCallback() {
const mountPoint = document.createElement('div');
this.attachShadow({ mode: 'open' }).appendChild(mountPoint);
const user = this.getAttribute('user');
console.log('🚀 ~ file: app.tsx: ~ user:', user)
const root = ReactDOM.createRoot(mountPoint as HTMLElement);
root.render();
}
}
customElements.define('caracal-admin', ReactMfe);

Maybe you should try accessing this.user from within the ReactMfe class

Super thank you yes that worked. There doesnt seem to be any good examples of using the props with the wrapper. Thanks again


Explicitly enable go modules

If for some reason go modules is not enabled, go get will report an error:
JYANG-MB at ~/go ❯ go get github.com/open-telemetry/opentelemetry-collector-builder
cannot find package "github.com/hashicorp/hcl/hcl/printer" in any of:
	/usr/local/Cellar/go/1.15.2/libexec/src/github.com/hashicorp/hcl/hcl/printer (from $GOROOT)
	/Users/yang/go/src/github.com/hashicorp/hcl/hcl/printer (from $GOPATH)

This is because hashicorp/hcl is currently V2 but viper depends on its V1 via Go modules (and viper is one of the dependencies of this repo). This will trigger the error above if (for some reason) Go modules is not enabled.
Therefore, I suggest to set the environment variable explicitly and run the command GO111MODULE=on go get github.com/open-telemetry/opentelemetry-collector-builder instead in the README.

Would you mind sending a PR with the proposal?

@jpkrohling Please see the PR above. Thanks!


Optimize / Parallelize InstructionLookups::polynomialize

For a 64 core machine at a cycle count of ~16M Jolt spends ~4% of its time on segment called InstructionLookups::polynomialize here. This segment allocates and computes the offline memory checking (a,v,t) polynomials and other inputs for the Jolt instruction execution.
Currently much of the time is spent serially. We should parallelize this to get a speedup as the core count increases.
Similar to #292.
It may be helpful to review the tracing strategy for performance testing.

Hi @sragss I'm willing to work on this issue.

@sragss I am interested. Could you assign it to me?

Hi , can i take on this issue ?


 If so, how?
Tested on colleagues machine. Tested command on our machine. Would need external validation about behavior with ps on more operating systems/versions.

LGTM

LGTM. But consider adding some docs. :)

Sorry, I don't really have much time for a few weeks and I understand that this is a very hazardous sort of patch. Maybe you could solicit some other contributors to test out the command on various OS's?

I tested it on my Ubuntu servers and OSX laptop. It matches the man pages for those too.

Okay. I merge this to fix the bug. But I would appreciate if we could follow up where you document your research efforts as comments in the code. :)

Unfortunately this fix doesn't work on busybox (e.g. Alpine Linux) because it uses the 'w' option that busybox's ps doesn't support. (similar to #1530)
How about to use /proc/pid/cmdline if platform.system() == 'Linux'?

Unfortunately this fix doesn't work well on busybox (e.g. Alpine Linux) because it uses the 'w' option that busybox's ps doesn't support. (similar to #1530 )
How about to use /proc/(pid)/cmdline if platform.system() == 'Linux'?

@keitap, any solution that works sounds fine for me ^^

@keitap Doesn't that only work if you know the pid beforehand?
Ugh. I almost hate to mention this, but maybe luigi really needs to depend on psutil if this is an important functionality? That's supposed to be cross platform.

I think this is an important functionality. But it would be nice if we could avoid a dependency. :)

Ok, well, should ps even be used at all? Would it better to walk /proc and catch FileNotFound exceptions?

Oh, yea maybe procfs is the right thing here. I for one don't know. :)

@daveFNbuck @nugend @keitap @erikbern, I have some alarming experience regarding the locking. I don't remember how slot it was before this patch. But I've upgraded to the latest version of luigi. And I experience that startups (just the lock checking!) takes 3 minutes. This needs a fix soon!
We should think if we can use procfs or some other algorithm for this. Alternatively find out why this is slow. I could experiment with this a bit further. But I would like to hear from you if you've seen any regressions.

Hmm... this seem to be because my .pid file have 7027 entries in it for some reason... I'll investigate this further ....

Oh this seems to be for many many files.
❯ wc -l /tmp/luigi/*
   1892 /tmp/luigi/03446b0238b6510876b4425b09ed4915.pid
   2085 /tmp/luigi/0394d228c401cc829c75afaac48b37a1.pid
   1896 /tmp/luigi/04633b957affa2565e67230450ab59d5.pid
   2084 /tmp/luigi/047a05715ee5ee9fcfd748c08f1cf556.pid
   1901 /tmp/luigi/049fc7eb10a773ff47c4da2a287d88e4.pid
   1895 /tmp/luigi/04d258946980574465457efc20c9f5f3.pid
   1895 /tmp/luigi/0503079a80d05e1f83e3ffe11ea0b751.pid
   1897 /tmp/luigi/078d6e1853656612934393d0833e9dca.pid
   1901 /tmp/luigi/082cf3864ae947f18e4ddd52487af814.pid
   1900 /tmp/luigi/08ae7c0344667b28a706aa7ee94767a0.pid
   1897 /tmp/luigi/095195163887c4c6b44db29f9a4ce694.pid
   1900 /tmp/luigi/0da99d2a9b7a86ec64352c4548f50677.pid
   1900 /tmp/luigi/0e1466533f00a00177dca96aebca2522.pid
   1894 /tmp/luigi/0e98c56f7cfd5b8ff2a0bc7233603c09.pid
   2093 /tmp/luigi/0ecc28a934f3efd9141a5c0a81e831fd.pid
   1899 /tmp/luigi/0f5c8d615681e10d642490cabcb9ff7a.pid
    ....

This is clearly unrelated to this patch I see. Sorry for alarming. Though I'll work on getting something up that cleans the .pid files and send a PR by tomorrow.


Add email value type

As part of the Contacts refactoring an email value type is added to avoid using a String representation directly.

I think I'd prefer the name EmailAddress. Even though there's no name conflict because we use the term "message" instead of "email" in the code base, shortening "email address" to "email" feels wrong.

I think I'd prefer the name EmailAddress. Even though there's no name conflict because we use the term "message" instead of "email" in the code base, shortening "email address" to "email" feels wrong.

Yeah EmailAddress describes better what it is -> changed


Bootstrap4 migration

@azizmashkour : can you please update to use Bootstrap 4.1?
https://blog.getbootstrap.com/2018/04/09/bootstrap-4-1/
Thank you!

Are you having issues with Bootstrap 4.1? Is this fully functional on Bootstrap4?

have pulled locally and does not work properly with 4.1 in current state. Fails to open anything if only one step, and then even with 2 steps it opens but there is no title or content

Having had a play with the source, I think the issue for lack of title and content is due to the default template, currently it is
template: '

 <button class="btn btn-sm btn-secondary" data-role="prev">« Prev</button> <button class="btn btn-sm btn-secondary" data-role="next">Next »</button> <button class="btn btn-sm btn-secondary" data-role="pause-resume" data-pause-text="Pause" data-resume-text="Resume">Pause</button>
 <button class="btn btn-sm btn-secondary" data-role="end">End tour</button>

',
but it should be
template: '

 <button class="btn btn-sm btn-secondary" data-role="prev">« Prev</button> <button class="btn btn-sm btn-secondary" data-role="next">Next »</button> <button class="btn btn-sm btn-secondary" data-role="pause-resume" data-pause-text="Pause" data-resume-text="Resume">Pause</button>
 <button class="btn btn-sm btn-secondary" data-role="end">End tour</button>

',
Note I have just changed the classes
popover-title
popover-content
to
popover-header
popover-body

I can confirm that @BenMaxfield solution solves the issue with Bootstrap v4.1+

@azizmashkour @BenMaxfield @asseti6
Thank you for all of your work that you've done!  It helped a ton today for me.  I posted a gist that uses all this goodness here:
https://gist.github.com/peteristhegreat/0678620341f6af725b23cd4cd395ec48

Thank you all guys, I will definitively recheck and retest all submitted pull requests in the repository then prepare a new version that will contain all new features and fixed issues.

How long does it still take to do this? @azizmashkour


Support mixed-type arrays.

The spec has been updated to allow arrays of mixed types (https://github.com/toml-lang/toml/pull/676), so it might be good to relax that restriction.

Looks like this is fixed by #358.


Allow users to control the maxPageSize used by listing based jobs

Generated from an ICM where a customer hit some kind of bandwidth limitation by their internet service provider when running our blob listing based jobs. We currently hardcode the maxPageSize to be 5000 for those jobs. When the limit is hit, the ISP drops the connection.

We have added a setting to override the default maxPageSize for these batch operations. The setting's id is "transfers.network.maxBatchSize". It is hidden in the settings panel. To configure it, open the settings file from settings panel and add one entry with the desirable value (e.g. 1000) for the setting.

The settings file is a json file. If you add the "transfers.network.maxBatchSize" as the last entry,  make sure you also add the trailing comma after its preview entry to separate them.


Not able to launch the stack

I tried multiple times from the blog link and from the git, but I am not able to launch the stack.
Can you please help me out with this?

Could you please provide the CloudFormation logs (from the AWS Console) or the console output from your Terminal/Shell, so I can diagnose the failure reason?

https://user-images.githubusercontent.com/38581611/65492383-6d4e7b80-dece-11e9-859e-28a9a2fc1d67.PNG
I am getting the same window for more than 45 minutes.
I tried it with both lite vesion and full version in your git post but unfortunately every time I am stuck with the same window.

Do you have full admin privileges on the AWS account you are launching the stack in?

Yes, I do have full administrative privileges yet not able to perform the launch function.

It appears that AWS did a site-wide update of its online console interface.
The new CloudFormation interface is buggy and the "Launch stack" links do not work.
You have two options:

If you need to get this working urgently, disable the new console interface. Then visit the "Launch stack" link again using the old interface.

Wait for AWS to fix the bug in their new console interface. I have also just submitted a support ticket informing AWS of this bug in their interface.

I am totally willing to work with it as soon as possible.
But I have no idea about how to disable the new console interface.
How to go with it and will it affect my other ongoing projects in my same account?

Okay, so now I am able to create the stack successfully but as soon as I execute it, it goes to the rollback stage and finally shows the message as ROLLBACK_FAIL.
Please help me out witj this.
https://user-images.githubusercontent.com/38581611/65725403-2def7d00-e0d0-11e9-8bca-f1bb6c4dc11e.JPG

Hi, I have updated the repo documentation with new links and screenshots to reflect AWS’s new online console interface.
I have upgraded the Lambda Node.js version, which was causing your stack deploy to fail.
Please re-fetch this repository, delete all Cloudformation resources and S3 buckets associated with this stack, and attempt to relaunch the stack.

Hello sir, I refered your updated repo documentation. I tried launching the stack once again from scratch but I found the "Access Denied" error. This may be because the S3 link provided while creating the stack is not open to all.
Can you help me with this?
https://user-images.githubusercontent.com/38581611/65793379-47053600-e183-11e9-95ec-85c0ab3cac42.PNG

Sorry, the template file was private. Just fixed

I am not able to implement it with the updates too. I tried it for last two days but not able to fix it.
Can you help me with this?
https://user-images.githubusercontent.com/38581611/65850129-28fa2a00-e36b-11e9-87a2-9486f64e0e43.JPG

CloudFormation Event logs are useful in diagnosing why a stack deploy fails.

Could you screenshot those (click on the "Events" tab), and indicate which event gave an error?

https://user-images.githubusercontent.com/38581611/65911991-1c1d1b00-e3eb-11e9-8836-bcfe5fd76983.JPG
https://user-images.githubusercontent.com/38581611/65912002-1fb0a200-e3eb-11e9-8c34-b6773558fd7e.JPG
https://user-images.githubusercontent.com/38581611/65912008-2212fc00-e3eb-11e9-9c4f-dfc9f1c0275b.JPG
It rollbacks and deletes the failed resources.

Hello sir,
I hope you are not busy these days. After you asked me for the screenshots, I have attached 3 images of errors occuring.
I wish to get the response from you soon.

@yasteeShah you need to DELETE the stack AND any resources that might have been leftover. This screenshot shows the earliest error chronologically. You can see WebAppBucket already exists and Cloudformation is complaining.

The S3Key for the S3ToKVSLambda function is invalid and hence stack creation is failing with an S3 Access Denied error. Please verify by trying to access the following URL: https://s3.amazonaws.com/brain-power-fidgetology-demo-bootstrap/11cf97b799cc8689b2f0bc0f6e68069b
Please fix urgently.

I am seeing the same error, would love a fix as urgently as possible. the s3 access is being denied for brain-power-fidgetology-demo-bootstrap/11cf97b799cc8689b2f0bc0f6e68069b

Are you guys not allowing open access to this project any more? If so, it is super uncool to leave the repo and ReadMe still up. Hoping to have access soon!

I am seeing the same error, would love a fix as urgently as possible. the s3 access is being denied for brain-power-fidgetology-demo-bootstrap/11cf97b799cc8689b2f0bc0f6e68069b

same issue here as well..

I am seeing the same error, would love a fix as urgently as possible. the s3 access is being denied for brain-power-fidgetology-demo-bootstrap/11cf97b799cc8689b2f0bc0f6e68069b

I'm also having the same issue

I think the bucket is created with wrong permissions likely.
I was able to work around this by

Downloading the full template which is created when you click the Launch button.
Creating my own bucket in us-east-1
Uploading [https://github.com/brain-power/Brain-Power-Amazon-Fidgetology/blob/master/lambda/S3ToKVS/S3ToKVS.jar](jar file) to that bucket
Changing the CodeUri field in the template to point to the file in bucket instead of the default one
Launching with my template

Omg, this is still open :(

Anyone mind giving me a hand with this?


refactor(transformer): fix indentation

Fix indentation.

#3617  👈
main

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

Join @overlookmotel and the rest of your teammates on  Graphite

Trivial change, so merging.


bug: Handle NoClassDefFoundError when loading YAML recipes with missing recipe dependencies

What's changed?
Added logic to catch NoClassDefFoundError errors when loading YAML recipes with missing recipe dependencies
What's your motivation?
NoClassDefFoundError errors were previously not handled compromising troubleshooting.
Anything in particular you'd like reviewers to focus on?
Potential for regressed behaviour.
Anyone you would like to review specifically?
@timtebeek
Have you considered any alternatives or workarounds?
No
Any additional context
No
Checklist

[ ] I've added unit tests to cover both positive and negative cases
[ ] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

Had another look; when I modify the test case here to use an invalid class, it seems we're not entering the new catch block where I had expected that:
https://github.com/openrewrite/rewrite/blob/03c458404073082275a752063887c188d213afbe/rewrite-core/src/test/java/org/openrewrite/config/YamlResourceLoaderTest.java#L303

Also note that the new catch block is only added for Yaml resources that contain more than one document (or at least a --- separator), whereas it might be quite common to find resources without such a block and handle missing classes there as well.
Perhaps we should still add a test if possible to ensure we're catching in the right place and not missing certain cases.

Perhaps we should still add a test if possible to ensure we're catching in the right place and not missing certain cases.
I've added exception handling for the String recipeData case. I've also added unit testing as suggested. The tests validate the behaviour when a NoClassDefFoundError is thrown when attempting to instantiate a recipe, however it does so in a contrived manner that is not analogous to how the Moderne customer encountered it.


Add run triggers support

Adds tfe_run_trigger support.
Workspace triggers can be created via run_triggers or workspace_run_triggers similar to other workspaced resources like variables or tags.
Added unit tests for the parse functions, a tf validate run and an integration test.

Code looks 👍🏻  other than the comment about name vs ID and the fuzzy finding

glad i got back in there, i had totally forgot about importing! added support for it


Check command token substitution seems to break when commas are used

Hello.
I believe there might be something strange happening when a check command token substitution string contains commas.  When I setup my cpu-load check via chef in this fashion:
command "check-load.rb --warn=:::cpu-load.upperwarn|5,10,15::: --crit==:::cpu-load.uppercrit|15,20,25::: --per-core"
The actual on-disk json file has these contents:
{
  "checks": {
    "cpu-load": {
      "command": "check-load.rb --warn=:::cpu-load.upperwarn|5,10,15::: --crit==:::cpu-load.uppercrit|15,20,25::: --per-core",
      "handlers": [
        "base",
        "default"
      ],
      "subscribers": [
        "base_centos"
      ],
      "interval": 60,
      "team": "ops",
      "occurrences": 5,
      "interval": 60,
      "refresh": 120,
      "ticket": true
    }
  }
}

... And, unfortunately, the check is constantly critical, even when the machine is not under load.
When I redefine the check in this fashion:
command "check-load.rb --warn=:::cpu-load.upperwarn5min|5:::,:::cpu-load.upperwarn10min|10:::,:::cpu-load.upperwarn15min|15::: --crit=:::cpu-load.uppercrit5min|15:::,:::cpu-load.uppercrit10min|20:::,:::cpu-load.uppercrit15min|25::: --per-core"
So that the on-disk json looks like this:
{
  "checks": {
    "cpu-load": {
      "command": "check-load.rb --warn=:::cpu-load.upperwarn5min|5:::,:::cpu-load.upperwarn10min|10:::,:::cpu-load.upperwarn15min|15::: --crit=:::cpu-load.uppercrit5min|15:::,:::cpu-load.uppercrit10min|20:::,:::cpu-load.uppercrit15min|25::: --per-core",
      "handlers": [
        "base",
        "default"
      ],
      "subscribers": [
        "base_centos"
      ],
      "interval": 60,
      "team": "ops",
      "occurrences": 5,
      "interval": 60,
      "refresh": 120,
      "ticket": true
    }
  }
}

...then the check is OK (as it seems the thresholds are being populated properly).

It looks like the token substitution pattern does not exclude commas https://github.com/sensu/sensu/blob/master/lib/sensu/client/process.rb#L124 Have you captured the run time command via ps? Does the Sensu plugin support comma delimited numeric values?

I have not captured the runtime command via ps; however, the plugin does support comma delimited numeric values.  The second method - whereby I do an individual token for each of the three numbers and move the commas "outside" of the token - works as expected.
mobile

On Jul 9, 2015, at 8:17 PM, Sean Porter<EMAIL_ADDRESS>wrote:
It looks like the token substitution pattern does not exclude commas https://github.com/sensu/sensu/blob/master/lib/sensu/client/process.rb#L124 Have you captured the run time command via ps? Does the Sensu plugin support comma delimited numeric values?
—
Reply to this email directly or view it on GitHub.

The code was able to substitute your tokens w/ the defaults as expected, but notice the double equals == for the critical thresholds.
[1] pry(main)> def find_client_attribute(tree, path, default)
[1] pry(main)*   attribute = tree[path.shift]
[1] pry(main)*   if attribute.is_a?(Hash)
[1] pry(main)*     find_client_attribute(attribute, path, default)
[1] pry(main)*   else
[1] pry(main)*     attribute.nil? ? default : attribute
[1] pry(main)*   end
[1] pry(main)* end
=> :find_client_attribute
[2] pry(main)> def substitute_check_command_tokens(check)
[2] pry(main)*   unmatched_tokens = []
[2] pry(main)*   substituted = check[:command].gsub(/:::([^:].*?):::/) do
[2] pry(main)*     token, default = $1.to_s.split("|", -1)
[2] pry(main)*     matched = find_client_attribute(@settings[:client], token.split("."), default)
[2] pry(main)*     if matched.nil?
[2] pry(main)*       unmatched_tokens << token
[2] pry(main)*     end
[2] pry(main)*     matched
[2] pry(main)*   end
[2] pry(main)*   [substituted, unmatched_tokens]
[2] pry(main)* end
=> :substitute_check_command_tokens
[3] pry(main)> check = {:command => "check-load.rb --warn=:::cpu-load.upperwarn|5,10,15::: --crit==:::cpu-load.uppercrit|15,20,25::: --per-core"}
=> {:command=>"check-load.rb --warn=:::cpu-load.upperwarn|5,10,15::: --crit==:::cpu-load.uppercrit|15,20,25::: --per-core"}
[4] pry(main)> substitute_check_command_tokens(check)
NoMethodError: undefined method `[]' for nil:NilClass
from (pry):13:in `block in substitute_check_command_tokens'
[5] pry(main)> @settings = {:client => {}}
=> {:client=>{}}
[6] pry(main)> substitute_check_command_tokens(check)
=> ["check-load.rb --warn=5,10,15 --crit==15,20,25 --per-core", []]

Ah, entirely embarrassing on my part.  Thanks for pointing it out to me, and I apologize for your trouble.


ENDOC-576 7.1 check docs for needed changes wrt bundle-id, plugin-id

@Lyd1aCla1r3 did you also test the profile and env variables tutorials with these changes? Just checking if we need to run that test still.

@nshaw i did not. i got as far as working through your scratch pad instructions. i have a bunch of questions about where to go from there; some i can probably answer myself just thinking things through, but it might be better to just cut to the chase next standup. i'll see what i can piece together in the meantime


Bring in a faster Transform stream

https://github.com/mcollina/syncthrough offers 3x the throughput of Transform. https://www.npmjs.com/package/minipass offer similar characteristics.
I think bringing in a faster set of Streams that enforce backpressure would speed up an area of Node.js that is showing its time.

I don't think we should have another stream implementation, this will be confusing and need to maintain multiple implementations for complex topic

There is room to further optimize stream.Transform to be close to synchthrough. To begin with we should avoid the double buffering and implement stream.Transform as a stream.Readable with stream.Writable compatible api.

Also rather than adding another stream api, I think we should add support for sync functions in pipeline, i.e.
stream.pipeline(src, val => val.toUpperCase(), res)

There is room to further optimize stream.Transform to be close to synchthrough. To begin with we should avoid the double buffering and implement stream.Transform as a stream.Readable with stream.Writable compatible API.

I would love this, whoever the world depends on _readableState and _writableState. If you have ideas, I'm all ears.

Also rather than adding another stream api, I think we should add support for sync functions in pipeline

@ronag that would have almost the same effect. Maybe we could internalize SyncThrough or analog and use ti to support pipeline

@ronag I remember u had some pr to remove the double buffering but stopped, do you remember what blocked you?

@ronag I remember u had some pr to remove the double buffering but stopped, do you remember what blocked you?

Time was a blocker.


Doesn't work for some destructured types

It works for simple types, but I have some types deep in my project that typescript is kindly showing as a string on hover but the extension sidebar claims it is of type any.

@anguskeatinge Can you provide types that can reproduce the problem?

I was more just flagging this for any future users who are trying to understand if they are facing a novel issue or if other people have had trouble with this before.

Okey.
Thank you for your valuable report.

If I come across a shareable repro, I'll be sure to do so.

Yes, I would appreciate it if you could share some repo.


Set up GitHub Actions for tests

Hi @bennylope , I would like to work on this.

Closed with 17f2c9132e066d30fb1666137e45c0f484532050


QEP 1: Implicitly-Scoped Qubit Allocation

This issue tracks the implementation of QEP 1: Implicitly-Scoped Qubit Allocation. The feature branch is feature/inline-qubit-scope.

[ ] Deprecate using and borrowing keywords and replace with use and borrow (#804)
[ ] Allow use and borrow statements to be followed by either a block { ... } or a semicolon ; (#803)
[x] Deprecate parentheses around block statement headers (#791)

Thinking about using → use and borrowing → borrow a bit more, it feels a bit awkward to use present participles to represent an action taken by an operation, given that we elsewhere use finite verb phrases to directly indicate the tense and subject of that verb. Concretely, the gerund "using" on its own doesn't have a tense to make it clear when something is used. Moving to "use" makes that tense explicit, which strikes me as a very good thing for readability.

Thinking about using → use and borrowing → borrow a bit more, it feels a bit awkward to use present participles to represent an action taken by an operation, given that we elsewhere use finite verb phrases to directly indicate the tense and subject of that verb. Concretely, the gerund "using" on its own doesn't have a tense to make it clear when something is used. Moving to "use" makes that tense explicit, which strikes me as a very good thing for readability.

When this change becomes breaking, will we offer the users a tool to mass-migrate to the new syntax automatically, like we did in the past (I think it was around 0.3 version)? I've seen a mention of a code action in the proposal, but migrating a sizeable code base would require a lot of effort without such tool.

When this change becomes breaking, will we offer the users a tool to mass-migrate to the new syntax automatically, like we did in the past (I think it was around 0.3 version)? I've seen a mention of a code action in the proposal, but migrating a sizeable code base would require a lot of effort without such tool.

We've been discussing using QsFmt to automatically update deprecated syntax across an entire project. It needs some more work to be able to do that, though.

We've been discussing using QsFmt to automatically update deprecated syntax across an entire project. It needs some more work to be able to do that, though.


Implement CANCELLING state and CancelledException

Implement the CANCELLING state as described here: https://docs.google.com/document/d/14s7D6KP1IKNS1K3OrVbZNKGNei9TO_-9Sk0YC5mpht8/edit#heading=h.d6pdcztkz6gj
The CancelledException could be child of TerminalException. Perhaps it's worth splitting TerminalException as well between UserTerminalException and CancelledException, to reduce potential mistakes when using compensations (as in #95) and try catch at the same time.

It would be great to outline a bit more how exactly the SDK side of the cancellation feature in the first implementation step looks like. One idea could be the following:
When in Canceling mode, then we invoke the user code with a RestateContext that inserts a CanceledEntry when appending a new entry and throws a CanceledException. Additionally, the SDK offers a way to register compensations. Once the user code terminates with a TerminalException, all collected compensations will be executed with a normal RestateContext (which means that we are back in Processing mode).


humidity sensor

Identify a low-cost humidity sensor (or an alternative temperature sensor that also measures humidity) and modify the code to add the data to each log entry.

closed with c3d0c17


Add missing DeleteBastionShareableLinkByToken API back to swagger

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

This is a Pull Request for new Microsoft.Network API version (2023-06-01) branch. Endpoint 'DeleteShareableLinksByToken' has been available to public since 2019. It was released together with 'CreateShareableLinks', 'GetShareableLinks' and 'DeleteShareableLinks' endpoints. However, for some reason this 'DeleteShareableLinksByToken' endpoint was not added to the swagger at that time, causing public documentation & SDK missing this endpoint. This PR aims at adding it back to swagger.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Any clarifications you'd like to add? please complete the purpose of PR section

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
Update existing version to fix swagger quality issues in S360.
Other, please clarify:
edit this with your clarification

Any clarifications you'd like to add? please complete the purpose of PR section

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.) Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.) Update existing version to fix swagger quality issues in S360. Other, please clarify: edit this with your clarification

Hello @TimLovellSmith I updated the purpose of this PR

Hello @TimLovellSmith I replied to the comments, could you please review again? Thanks!

I see some lintdiff errors again, so I'm not sure lintdiff is working correctly on this PR @rkmanda
One issue that seems to be mentioned is a cyclic dependency between mfe.json and machineLearningServices.json
 {
2023-09-11T14:58:42.8166189Z           "pluginName": "spectral",
2023-09-11T14:58:42.8166898Z           "extensionName"<EMAIL_ADDRESS>2023-09-11T14:58:42.8167461Z           "level": "fatal",
2023-09-11T14:58:42.8169476Z           "message": "openapiValidatorPluginFunc: Failed validating:Error: Dependency Cycle Found: file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/machineLearningServices.json -> file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json -> file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/machineLearningServices.json"
2023-09-11T14:58:42.8170932Z         },

...or at least make sure the dependencies are unidirectional

Tagging this as FixS360 since purpose is to revise docs for existing workign API.

Tagging so the change to an existing stable version can be signed off for breaking changes. Even though it looks mostly safe to me.

My mistake, breaking change review not required because its updating a release branch.


Update CelOS logo

#1804

Your pull request has unrelated changes.

Your pull request has unrelated changes.

For some reason, the spaces in other logos have been removed


Sema: Resume diagnosing @backDeployed on functions with opaque result types as errors

Reverts https://github.com/apple/swift/pull/66930
Resolves rdar://111335791

@swift-ci please smoke test


Pin gast to <0.3.0

Workaround for #97 - gast < 0.3.0 has the old-style API needed by LITERALS in tangent.grammar (gast.Num, gast.Str, etc.).

@googlebot I signed it!


[internal/8.0.1xx] Installer CI building fails due to missing packages

https://dev.azure.com/dnceng/internal/_build/results?buildId=2510490&view=results (internal Microsoft link)

This is expected and will be resolved once the August release is done.

Close this issue, it has been resolved in Aug servicing release.


Can't get input event for mouse then window losing|regaining focus

Godot version
3.3.2
System information
Linux Manjaro, Win10, any hardware
Issue description
Working on some software, need to make drag'n'drop feature for files, but need to drop files on specific controls.
When you switch to Godot window and some mouse button is pressed, there are no Input Events fired for mouse motion|buttons unless you release button (releasing button also not fired). get_global_mouse_position() returns last mouse position before window switching.
Steps to reproduce
1 Start any app
2 drag'n'drop any file into window, or just press mouse button and then alt-tab to your app
3 As you can see InputEvents will fire only AFTER you release mouse button
Minimal reproduction project
Small project with label shows mouse global coordinates
MouseBug.zip

Also I think it's connected with
https://github.com/godotengine/godot/issues/33928


[ci] Update EOL GitHub Actions

actions/checkout@v2 and actions/upload-artifact@v2 use Node.js 12, which will be deprecated from GitHub's Ubuntu runner in the summer of 2023.
Update: also updated<EMAIL_ADDRESS>to v6 to use Node.js 16. This is used in the pr-lint-review pipeline which isn't run on this pull request's context, so isn't checked here.
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

actions/checkout@v3 and actions/upload-artifact@v3 should be safe updates, and we can see them working in this PR.
actions/github-script I'm a bit more wary of. We're only running it in the pr_lint_review workflow which for this PR runs using the repo's HEAD configuration and not this PR's updated version, so I can't see it working. See https://github.com/lowRISC/ibex/pull/1427 for why it works like this.
This action is updated from v3 to v6 which is a fairly large jump. It runs some Node.js script directly, which in theory could break between Node.js 12 and 16. I don't see any easy way of testing this without just merging the PR. I think the worst that would happen is we don't get verible lints posted to PRs as review comments.
If we don't want to blind-update this action in the pr_lint_review workflow, I'm happy to exclude it - we no longer need this split of two workflows where one runs in the HEAD context (see https://github.com/chipsalliance/verible-linter-action/pull/31), and I'm planning on making this change today in which case we no longer need this action.

LGTM, I think you could merge this PR in an Idle day and if it breaks we quickly revert the last commit.

The github-script update did break CI :smile: - here's the revert for that commit: https://github.com/lowRISC/opentitan/pull/19107


Add additionalProperties to HttpLink, LocalizedString, ea

Following https://github.com/belgif/rest-guide/issues/110 and the decision to not accept unknown properties, some objects in openapi-commons must be changed to mark them explicitly extensible

HttpLink: to add other fields next to href
LocalizedString: to add other languages
e.a ??

I don't think it is needed:
HttpLink
It is usually only used in the response, not in requests (and the rule only applies to requests).
Also, APIs usually use HttpLink in combination with an allOf, so the other properties are known, e.g.
PersonReference:
    allOf:
      - "$ref": "./common/v1/common-v1.yaml#/definitions/HttpLink"
      - type: object
        properties:
          ssin:
            "$ref": "#/definitions/Ssin"

LocalizedString
If a Belgian API deviates from the three declared languages (nl, fr, de), it usually declares its own variant type to be explicit about which languages are provided.  E.g. if the server supports "nl", "fr" and "en", using the LocalizedString from openapi-common would lead the client to believe that "de" would be processed by the server but it would be silently ignored, and that "en" isn't supported.
Such a type can still evolve in a backwards-compatible manner. E.g. removal of a language is covered:

In specific situations, where a (known) input parameter is not needed anymore and can be safely ignored:

either it can stay in the API definition with a deprecation flag and a "not used anymore" description
or it can be removed from the API definition as long as the server ignores this specific parameter.

If types are meant to be extended then I think there is no issue in configuring that explicitly in the common schemas.
LocalizedString documents in the schema that additional languages can be added (#nl, fr, de are predefined, but additional languages can be added). I don't think it is necessary to subclass LocalizedString into LocalizedStringWithEnlishAdded to add en for example.
The same applies to HttpLink and also Problem. Problem is meant to be enriched with additional properties in the specification. For some problem types we want to make it very explicit by subclassing it, but it should not be an obligation.

I think there are two closely related issues in this discussion: how to best document extensions of types, and how to implement open-world polymorphism. The latter issue is about the loss of extra properties when deserializing a Problem.
How to best document extensions of types
When the occurrence and types of the properties are known at time the API is being developed, I believe it would be best to always document this in OpenAPI, rather than requiring an out-of-band documentation that risks being out of date and erroneous because its not integrated in any tooling.
When the properties are of dynamic nature, unknown at development time (e.g. dynamically retrieved from a DB), additionalProperties seems a good fit. Dynamic metadata may be provided by the API in such a case e.g. GET /refData/supportedLanguages in case of localization.
I think most types fall under the "design time" cases, except for LocalizedString where it depends on the API if the supported languages are dynamic or determined design time.
How to implement open-world polymorphism
OpenAPI code generators currently only have good support for closed-world polymorphism through the use of discriminator: the list of known subtypes has to be exhaustively listed on the parent type in mapping .
Without mapping, the discriminator property has to specify the exact name of the schema which would be very limiting e.g. for problem type URNs.
For serialization, a subtype (in the code) can still be used without a discriminator to add all properties in a typed way, but for deserialization it's not possible to cast a value down to a subtype by default.
Also, subtypes that aren't explicitly referenced in OpenAPI, are sometimes not generated by the openapi-generator (I believe when they're referenced in an external file).
Possible workarounds:

explicitly register subtypes in code for deserialization, e.g.: [for jackson|https://leoniedermeier.github.io/docs/java/snippets/java_misc/jackson_polymorphic.html]
generate additional properties for the parent type, and work with weakly typed properties

In addition for error responses for Java clients, I believe they're not serialized to their types specified in OpenAPI out-of-the-box, even if it specifies a more specific type (TBC).


Ability to show noContentRenderer result in only one grid

Currently, if I have fixedColumnCount and noContentRenderer set, it displays the no content text in both panels, but that doesn't look good.

Would be possible to either have to props, e.g: noContentRightGridRenderer and noContentLeftGridRenderer or anything to avoid this behaviour?

1

@vcardins did you found any workaround for this issue?

@vcardins did you found any workaround for this issue?

i think maybe we can use css classNameTopLeftGrid, classNameTopRightGrid to hidden empty view.


document meson and that it is preferred over cmake

Add a nice summation of the following to https://github.com/simd-everywhere/simde/blob/master/CONTRIBUTING.md
ninja test will run all the tests (in parallel)

I usually just run the executables individually, (INSN=x86/sse; ninja test/${INSN}-{native,emul}-c && test/${INSN}-native-c && test/${INSN}-emul-c is pretty standard), but you can also run specific tests… see https://mesonbuild.com/Unit-tests.html

So, for example, meson test x86/sse/{native,emul}/{c,cpp} will run all 4 SSE tests.

mkdir build
cd build
meson ..
ninja test
``

Partially fixed in https://github.com/simd-everywhere/simde/commit/15f0e244669c084646c2527ca53522c98935ff37

hi, using https://github.com/simd-everywhere/simde/blob/master/CONTRIBUTING.md build method, still not pass build. it report following error.
The Meson build system
Version: 0.47.2
Source dir: /home/ll/simde/test
Build dir: /home/ll/simde/test/build
Build type: native build
ERROR: First statement must be a call to project

Hello @luozero , can you share the commands you ran?
I followed the instructions at -- and it worked for me
~/src/simde$ mkdir build
~/src/simde$ cd build
~/src/simde/build$ CFLAGS="-march=native" CXXFLAGS="-march=native" meson ..
The Meson build system
Version: 0.56.0
Source dir: /home/michael/src/simde
Build dir: /home/michael/src/simde/build
Build type: native build
Project name: SIMDe
Project version: 0.7.0-rc.1
Using 'CFLAGS' from environment with value: '-march=native'
C compiler for the host machine: ccache cc (gcc 10.2.1 "cc (Debian 10.2.1-1) 10.2.1 20201207")
C linker for the host machine: cc ld.bfd 2.35.1
Using 'CXXFLAGS' from environment with value: '-march=native'
C++ compiler for the host machine: ccache c++ (gcc 10.2.1 "c++ (Debian 10.2.1-1) 10.2.1 20201207")
C++ linker for the host machine: c++ ld.bfd 2.35.1
Using 'CFLAGS' from environment with value: '-march=native'
Using 'CXXFLAGS' from environment with value: '-march=native'
Host machine cpu family: x86_64
Host machine cpu: x86_64
Library m found: YES
Compiler for C supports arguments -fopenmp-simd: YES
Compiler for C++ supports arguments -fopenmp-simd: YES
Compiler for C supports arguments -Wpsabi: YES
Compiler for C++ supports arguments -Wpsabi: YES
Build targets in project: 854

Found ninja-1.10.1 at /usr/bin/ninja
~/src/simde/build$ ninja test
[ lots of output]

Version: 0.47.2

Meson is too old.  I'm not actually sure what version is required, but IIRC something around 0.52.
You probably want to install via pip: https://mesonbuild.com/Getting-meson.html#installing-meson-with-pip.  Or, of course, you can use CMake; a big part of the reason it's still in tree is to support old distros.

update meson, still can not build, following is the log,
[root@ecs-f81d build]# CFLAGS="-march=native" CXXFLAGS="-march=native" meson ..
The Meson build system
Version: 0.56.0
Source dir: /home/ll/simde/test
Build dir: /home/ll/simde/test/build
Build type: native build
ERROR: First statement must be a call to project
A full log can be found at /home/ll/simde/test/build/meson-logs/meson-log.txt
using CMAKE, in x86_64 can pass build an test.
but in aarch64， it report following issue.
make
Scanning dependencies of target simde-test-emul
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/mmx.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/sse.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/sse2.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/sse3.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/ssse3.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/sse4.1.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/sse4.2.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/avx.c.o
[  1%] Building C object CMakeFiles/simde-test-emul.dir/x86/avx2.c.o
In file included from /home/ll/simde/test/x86/avx2.c:25:0:
/home/ll/simde/test/../simde/x86/avx2.h: In function ‘test_simde_mm256_srl_epi64’:
/home/ll/simde/test/../simde/x86/avx2.h:4779:25: internal compiler error: in expand_shift_1, at expmed.c:2245
r_.u64 = a_.u64 >> HEDLEY_STATIC_CAST(int64_t, shift);
^
Please submit a full bug report,
with preprocessed source if appropriate.
See http://bugzilla.redhat.com/bugzilla for instructions.
Preprocessed source stored into /tmp/ccqFYaqs.out file, please attach this to your bugreport.
make[2]: *** [CMakeFiles/simde-test-emul.dir/x86/avx2.c.o] Error 1
make[1]: *** [CMakeFiles/simde-test-emul.dir/all] Error 2

in aarch64, need to modify two files
/home/ll/simde/test/../simde/x86/avx2.h :4779
r_.u64 = a_.u64 >> (uint8_t)(HEDLEY_STATIC_CAST(int64_t, shift));
vim /home/ll/simde/test/../simde/x86/avx512/srl.h:168
r_.u64 = a_.u64 >> (int8_t)(count_.i64[0]);
then can pass build and test.

What compiler, compiler version, and architecture(s) (host and target) are you using?  Also, since you're using -march=native, what features does your CPU support (since you're using -march=native)?  If you're using distro packages, it might be helpful to know what distro and release, too.  There are a few known issues with AVX-512 on old compilers which we can't really work around, though they only occur when AVX-512 is enabled in the compiler but SIMDe isn't allowed to use them (SIMDE_NO_NATIVE is defined), which really should only happen during testing.
As for the Meson issue, did you delete the build directory after updating Meson?  Meson is usually quite good about handling configuration changes gracefully, but honestly I haven't tried updating Meson the rebuilding the project.  That error is definitely the same error you see when trying to build with old versions of Meson and I've never seen it with newer versions, so I'm pretty confident that it's related.

thanks nemequ,
compile and target are the same one.  used Architecture:  aarch64
CMake can work, it's ok to build.

What about compiler and flags?
I'm not really concerned about the issue with Meson (I still think that should be resolved with a fresh build on a newer version), but I'd like to figure out what is going on with that ICE.  The changes you mentioned should not be necessary, that's definitely a compiler bug and in order to work around that I need to be able to reproduce it. It sounds a bit like GCC #94488, but that should have been fixed in more recent GCC and there are work-arounds in place in SIMDe to avoid it in older versions of GCC…


Use encodeUriComponent and decodeUriComponent and add tests

Description & motivation 💭
Remove custom Svelte encode/decode logic and use encodeUriComponent and decodeUriCompoent. Trim the end of schedule names.
Tested with schedules with space at end and correctly fetches schedule.
Screenshots (if applicable) 📸

Design Considerations 🎨
Testing 🧪
How was this tested 👻

[x] Manual testing
[ ] E2E tests added
[x] Unit tests added

Steps for others to test: 🚶🏽♂🚶🏽♀
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
Docs
Any docs updates needed?

Maybe eventually we replace all the encodeURIForSvelte and decodeURIForSvelte calls with encodeURIComponent and decodeURIComponent but this is good for now

Yeah I kept it in that function in case there's some other tweaks we need to make.


Multilanguage support (in the checkout flow)

Currently the views are hardcoded in English.
It would be better if they could be translated, or customised, without modifying the views directly.
@mattbrailsford I need to implement this for a project and can to contribute the changes back if you're happy with the approach.
Was thinking of just using the Dictionary with namespace-like keys e.g. "VendrCheckout.Confirmation.EmailSent" and using string.Format() compatible strings where necessary. e.g. "A confirmation email has been sent to {0}"

@mattbrailsford I need to implement this for a project and can to contribute the changes back if you're happy with the approach.
Was thinking of just using the Dictionary with namespace-like keys e.g. "VendrCheckout.Confirmation.EmailSent" and using string.Format() compatible strings where necessary. e.g. "A confirmation email has been sent to {0}"

@JasonElkin absolutely! And yup, I agree, dictionary items would be the way to go 👍

Just worth noting, I've restructured this repository recently as I've reworked the package for use in Vendr v2 so you may need a clean fork if you created one previously. Also, you'll need to make sure to target the right version. If you are using Vendr v1x then you'll need to target v1/dev otherwise on Vendr v2 target v2/dev

Closing this issue as all latest views now use the dictionary for their values


Fix/spacing in home page and link resources page with the about and contact us page

fixex #568

I have removed the extra space as you can see in the attached image of home page  .

I have linked the resources page with the contact us and about page .

BEFORE :
https://github.com/mdazfar2/HelpOps-Hub/assets/159682348/29187ab5-10a6-499f-bcd9-56dba6b020db
AFTER FIXING :
https://github.com/mdazfar2/HelpOps-Hub/assets/159682348/4ac8cdec-472d-4b9b-9c26-5462d26741a2

@mdazfar2 Please review it once .

@ANKeshri please update sync fork

@ANKeshri please update sync fork

it is updated


[GO Live][June 08]

Push to live

Docs Build status updates of commit 0449618:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Call to DownloadFileAsync() not returning when called from new thread

Downloading a Photo from the UI thread in a Windows Forms Application works.
When using Task.Run to move the download to a background task in order to keep the UI repsonsive, a call to
DownloadFileAsync(Photo, Stream) fails to return.
Example:
private async Task SearchAndDisplayAsync()
{
...
...

    else if (msg.media is MessageMediaPhoto)
    {
      MessageMediaPhoto photo = (MessageMediaPhoto)msg.media;
      Photo thePhoto = (Photo)photo.photo;
      var mi = new MessageItem(thePhoto);
      Image largeImg, smallImg;
      using (MemoryStream memStream = new MemoryStream())
      {
       await tgAPI.DownloadAsync(thePhoto, memStream, thePhoto.sizes[0], null);
        smallImg = Image.FromStream(memStream);
      }
      using (MemoryStream memStream = new MemoryStream())
      {
        await tgAPI.DownloadAsync(thePhoto, memStream, thePhoto.sizes[thePhoto.sizes.Length - 1], null);
        largeImg = Image.FromStream(memStream);
      }
...
...
}

The code above is trying to download a small photo and a large photo.
When called from the UI thread of a Windows Forms application (await SearchAndDisplayAsync();), both calls succeed and both images are downloaded.
When using await Task.Run(() => SearchAndDisplayAsync()); to run the method on a background thread, only the first download succeeds (the smallest photo). The second call just hangs and does not return.
If I reverse the order of the calls and download the largest file first, the call does also not return.
tgApi.DownloadAsync() is a wrapper around WTelegramClient's DownloadFileAsync():
public async Task DownloadAsync(Photo photo, Stream file, PhotoSizeBase thumbSize, Client.ProgressCallback progress)
{
    await Client.DownloadFileAsync(photo, file, thumbSize, progress);
}

Excerpt from the log:
2023-12-08 16:00:53 [D]             → Upload_GetFile                         #2656
2023-12-08 16:00:53 [D]             → MsgsAck
2023-12-08 16:00:54 [D] 2>Receiving RpcResult                                2023-12-08 19:00:54Z
2023-12-08 16:00:54 [D]              → Upload_File                           #2656
2023-12-08 16:01:29 [D] 2>Receiving Updates                                  2023-12-08 19:01:29Z
2023-12-08 16:02:04 [D] 2>Receiving Updates                                  2023-12-08 19:02:04Z
2023-12-08 16:03:00 [D] 2>Receiving Updates                                  2023-12-08 19:03:00Z
2023-12-08 16:04:03 [I] 2>Disposing the client

System: Windows 10 pro 22H2
WTelegramClient: 3.6.1

Created a reproduction solution.
The gist of the issue seems to be that if you create a usercontrol within (here) a foreach loop in which large images are downloaded, the download eventually will hang.
The solution appended is as minimal as I could make it. It should automatically download all referenced libraries upon first build.
Please make sure to be subscribed to Telegram's news channel: https://t.me/telegram
The program is hardcoded to search in this channel.
The App will write its session storage to %appdata%\TelegramApp\sessionStoreTGD
Logs are redirected into the output build directory as WTelegram.log
Steps to reproduce:

Load solution. Breakpoint is already set on the DownloadAsync method (line 120 in TDForm.cs)
Edit TelegramApi.cs and insert valid api_id and api_hash in Config() method.
Add your telephone number in TDForm.cs in the GetTelephone() method.
Build
Run (Debug)
Press Login button. The first time, the app should ask you for the security code (popup window) and, if configured, for your 2FA password.
Enter news in the search box and press enter. The program will then search in Telegram's news channel.
The program will eventually stop at the breakpoint (first iteration).
Press F5 to continue debugging to arrive again at the breakpoint.
Step over it and the program should now hang.

TelegramAppBugReproduction.zip

I've spent an unreasonable amount of time debugging your code and found the root cause of the problem is in your code, not in the library.
You're mixing UI code & threadpool-tasks in your code. It's often a recipe for disaster.
You have two solutions:

either remove all the Task.Run() from your program (WTC runs fine on WinForms task synchronization context)
or make sure ALL code (from those Task.Run tasks) accessing WinForms UI are protected inside a call to Form.Invoke((Action)(() => { ... })), even the simple creation of a UserControl instance.

For the experts, the advanced diagnostic is that the UserControl instance contains a PictureBox, and its instanciation force the reinstallation of WinForms synchronizationcontext as Current, when it should stay null in background tasks.


[Question]: About moving to ReactJS

Background:
I'm currently exploring the latest updated branch which is feat/react.
Upon exploring I noticed that the GUI is still in progress of migration. (inside client2 folder)
I would like to contribute but wasn't able to do so as I didn't found any resources regarding the migration process.
Question:
Where is the roadmap regarding the migration process from current setup to ReactJS?

I was just going to do it myself as it was a large task with a lot of things being changed, so I figured it wasn't worth splitting up at this point until most of it was already done.
There are a few bits of the GUI left of the things I wanted migrating over, then this branch would become the base for the items rework work, as that will require creating new panels for (not just simple conversions of the existing ones) of the bank panel, crafting panel, shop panel, inventory panel, and inventory hotbar.
Now that I have a better idea of what is going to be involved, I'll create a project roadmap for the item rework and add those as tasks to it.

I see, right now I'm working at #99 and I'm trying to piece everything together based on your previous work.
Feedback would be highly appreciated especially with regards to the folder structure.

The folder structure is a bit of a mess. There are a lot of parts that don't fit nicely together: Phaser related files, gameplay logic files, the React components, networking/event logic. I just organised them however I thought was OK at the time and was going to go through and tidy it up when I had a better understanding of all the parts and how they fit together.
So, the folder structure isn't well defined and can be changed.


docs: Update CONTRIBUTING.md

I think the right thing to do is to list any extensions used by the project. But we are not there yet. :(

I created an issue for that. https://github.com/ietf-tools/www/issues/420
The extension list in the doc will be updated as we go.


ci: Bump rust stable version for twotx build

Problem
The two-tx build is failing due to unsupported language features, following the bump to rust 1.65 on the monorepo. See https://github.com/solana-labs/solana-program-library/actions/runs/3446859167/jobs/5752258103 for an example
Solution
Bump the version to 1.65 for the twotx build

@samkim-crypto are these errors expected?
failures:
    ct_configure_token_account
    ct_enable_disable_balance_credits
error: test failed, to rerun pass `--test confidential_transfer`
    ct_new_account_is_empty

Sorry, I introduced an error while I was cleaning up the ElGamal pubkey derivation in the zk-token-sdk. It is addressed in 28792 and the tests should now pass.


move to gproc and move the acceptor pool start

This moves the acceptor pool's startup to be done after a role has been assigned a node. This doesn't work if we go from active to inactive and our role changes, but that wasn't supported before this move anyway.
Also switched the cluster mgr to being local on the head node instead of a global registration and move active-segment to use gproc instead of binary to atom.

I was actually thinking this might make more sense. If the role changes the existing connections are closed and new connections have to be opened.


update gisce/ooui to v2.2.0

Automated changes by create-pull-request GitHub action

:tada: This PR is included in version 2.4.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.5.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Broken drawing of raw peaks

When the resolution is small enough rendering pre-generated peaks (on the newest version of wavesurfer) is broken.

Once the screen estate is big enough, stuff is back to normal:

On wavesurfer version 1.1.1 I had no problems whatsoever:

Browsers:

FF 47
Chromium 51.0.2704.79

Source code of examples:

broken (wavesurfer 1.3.7)
http://public.adw1n.com/wavesurfer_issue/broken.html
same code was working on version 1.1.1
http://public.adw1n.com/wavesurfer_issue/working.html

The problem raises whenever you provide more peaks than the canvasWidth.
The drawWave function of Canvas and drawLineToContext function of MultiCanvas has been broken since #924 by @mspae that has changed the rendering loop from looping the entire peaks array to looping only up to "end" or "canvasEnd" respectively which is both cases the canvas width. In this way, the last point drawn x-coordinate is canvasWidth * scale which is less than canvasWidth whenever you have more peaks than pixels.

#924 is the v2 port of #909 – v2 hasn't been released yet – not that it matters :)

Related? https://github.com/katspaugh/wavesurfer.js/issues/994

I confirm this issue. V1.2.8 was fine and 1.3.0 is broken.

closing, will continue on issue #1067 if pr #1072 doesn't fix it 100%


New Function Optimizer Proposal

I've created a new stochastic function optimizer which you may be interested in evaluating. It's written in C++, but interfacing with it should not be hard. What I'm interested in is hearing your opinion, based on your benchmarking routine. I'm using a slightly different test function set, and the optimizer solves most problems given at least 50 optimization attempts are performed, up to 2000 iterations each.
Of course, you may include it into your project if you find it interesting.
https://github.com/avaneev/biteopt

Hello Aleksey! It is a really nice project indeed, we will definitely take a further look onto it and try to understand what it does. Meanwhile, do you have the source paper from where you implemented the algorithm, so it would easier our lifes in trying to understand the math behind it?
Thank you for your attention!

Thanks for your interest. This is a completely original work, I do not have a dedicated paper - but the algorithm is described in the source "bitefan.h" file.

Thank you, Aleksey! We are now in a process of studying and including new techniques. Usually, we include only techniques that have been published elsewhere. But we are working on it, anyway.  Best,

As I'm not associated with any academic institution, I have no plans to produce a paper even if this algorithm is worth it. Beside that, the analysis of this strategy is complicated due to its probabilistic nature.

Thanks for letting us know. Aleksey. We keep in touch. Best,

It would be interesting to know which test functions this optimizer fails to optimize in 50 attempts - if you have an automated benchmark that can print that information. I would like to add them to my still small list of unsolvable functions, to possibly improve algorithm in the future.

Yes, that would be nice. If you implement your technique on LibOPT, you can make use of all functions implemented there (more than 100). Best,

Well, I do not understand your library like you do. Maybe you can include it yourself. The source code is free, under MIT license.

Please refer to the wiki in order to know how to work with the library, i.e., https://github.com/jppbsi/LibOPT/wiki


feat/TablePagination - Table with Pagination

#1318
this PR adds the Pagination Component to the Table.

Summary by CodeRabbit

New Features

Introduced pagination for the <Table> component to efficiently manage and navigate through large data sets. Users can now choose between numbered page navigation or Prev/Next buttons for easier data exploration.

on dark theme it has no active item

on dark theme it has no active item

Okay!. I'll check and update it. Thanks for point it out..

@SutuSebastian Sir, one question though it arises in my mind is like, in the current Pagination component, we're limiting the size to 5 without allowing or giving an option to the User, that whether they need to show more or not on the single page by-default. e.g. by-default I want to show 10 rows per Page, but with the current Pagination it's restricted or can say it isn't allowed, then I guess we need to modify the Pagination to allow the User to pass an arbitrary value that how many rows/result they want to show on a single page instead of not allowing them to modify this behavior.
Please share your @SutuSebastian inputs & feedbacks on this, and if this makes a valid point, then I would be happy to go ahead and make this necessary changes.

@dhavalveera totally agreed. Lets fix and extend the pagination component properly and make it production ready once in for all.
The current state is broken.

While u're at it, investigate how a pagination component should work and the flexibility of it, and try to make a controller for it (a hook) and expose that as well, for the headless approach

@dhavalveera totally agreed. Lets fix and extend the pagination component properly and make it production ready once in for all.
The current state is broken.

For this one, I'll dig into the existing Pagination Component and we check it out how I can extend one to fix it and it production ready.

While u're at it, investigate how a pagination component should work and the flexibility of it, and try to make a controller for it (a hook) and expose that as well, for the headless approach

while working with Table.Pagination Component I understood a little bit is like we need to provide different kind of Pagination to the Users as like below:

Next / Previous Button
Next/Previous Button with Numbers in between if they want that as way
one more possible option could be something like a dropdown menu thing where there're possibilities => 1. a Dropdown Menu with predefined options if not passed by User or with the list Users want. and along with it Left/Right Icon for Prev/Next
then Pagination for Numbers with Square/Circle as an Border & maybe different colors.

those are some possibilities I came across for the Pagination Components.
Furthermore @SutuSebastian -- above suggestions & possibilities I came across for the Pagination components aren't implemented in the Flowbite's Core Package, so how we can proceed it with flowbite-react?
@SutuSebastian please share your feedback & input on this.

@SutuSebastian - can you please review?


Feat: Export app

This PR introduce zip and download feature for Wave projects created with web IDE.

Closing due to incorrect base branch (in favor of https://github.com/h2oai/wave/pull/1489)


cmd/compile: spurious inference error with undefined value

% cat /tmp/x.go
package p

import "slices"

var s struct{ x int }

func _() {
	slices.Clip(s.y)
}
% go build /tmp/x.go
# command-line-arguments
/tmp/x.go:8:13: cannot infer S ($GOROOT/src/slices/slices.go:403:11)
/tmp/x.go:8:16: s.y undefined (type struct{x int} has no field or method y)
%

The first error should not be printed, since it is caused by the second error.

Hi, can I try fixing it? I am new to GO, not sure if I will be able to anyways

Dont wanna sound dumb, but should I look into the slices package or some other package to get a fix?

Really?
On Sun, May 28, 2023 at 11:43 AM Gyanendra Singh @.***>
wrote:

Hi, can I try fixing it? I am new to GO, not sure if I will be able to
anyways
—
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/60434#issuecomment-1566178524, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A65XM66C2ZLIAXPZ6UGQDIDXINXDFANCNFSM6AAAAAAYPCWMWI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@gyanendrasng This is a compiler issue; the only relation to the slices package is that the example uses slices. I prefer fixing this myself - also this is not urgent. But thanks for offer.

Here is another related issue. This one might be worth fixing for Go 1.21 if it's an easy fix. The error message does not explain enough about the context:
% cat /tmp/x.go
package p

func Clip[S ~[]E, E any](s S) S {
	return s
}

var versions func()
var _ = Clip(versions)
% go build /tmp/x.go
# command-line-arguments
/tmp/x.go:8:13: S does not match []E
%

It would be helpful to say what function is being called and what S is, as in:
/tmp/x.go:8:13: in call to slices.Clip, S (type func()) does not match []E

In my actual program, I had imported slices and written append(slices.Clip(versions), more things), and all I got was S does not match []E. Obviously since S and E don't appear in the program, it's a mysterious message.
Eventually I removed the call to slices.Clip entirely and that left me with:
x.go:144:16: first argument to append must be a slice; have versions (value of type func(ctx context.Context, path string, allowed AllowedFunc) (versions []string, origin *codehost.Origin, err error))

That made clear what I'd done wrong, by telling me the type of versions. Even when I started this bug report I hadn't figured that out yet and thought versions was simply an undeclared variable (my actual bug was deleting the local declaration of versions without updating the slices.Clip call).

problem: why the first error printed before the second error. it means why the first error occurred when the second one is the reason of first one!?
reason: it's not about "Slice" package or "Slice.Clip" function. it's all about the compiler. for take a look at this and this. as you can see both errors are in the same level but with different priority.
now it is what happening: compiler start the "Type checking" phase or "semantic Analysis" and in this phase The compiler attempts to resolve types and check for type compatibility before checking for undefined fields or methods. Therefore, when it encounters the line slices.Clip(s.y), it tries to determine the type of S in the "Slices" package, leading to the first error. Since it encounters this error first, it does not proceed to check for the undefined field s.y, resulting in the second error being reported afterwards.
so now we know the reason but what can we do to get the second error first?
package p

import "slices"

var s struct{ x int }

func _() {
        tmp := s.y
	slices.Clip(tmp)
}

and what you get is this:
s.y undefined (type struct{x int} has no field or method y)
cannot infer S ($GOROOT/src/slices/slices.go:403:11)

and it is obvious that now priority of them are different for the compiler.


persistence: bootstrap from the DHT

This works as an alternative to having a CRDT-specific pinning service.
Instead of having an external service that tracks the CRDT and persists it for it to be available when all the seeders are offline, a peer that wants to share a collaboration should then create a DHT record that contains:

the collaboration name
the bootstrap peers
the (encrypted and signed) CRDT state.
any more meta-data?

The name of this record can be shared via an URL (to be included, for instance in the URL shared in Peer-Pad). Then new peers can try to get this record from the DHT, decrypt it and bootstrap from there.
//cc @diasdavid @satazor

Just wanted to give here a quick comment on this strategy:
This strategy is quite interesting and is actually undoubtedly decentralized. Though, there are a few use-cases in which it's hard to use it. The issue is that it assumes that a user will be sharing something with other user, which might not always be the case. For instance, you will be able to comment on public discussions on Discussify, where a user may simply type the URL of the page that he/she wants to comment.
I will be thinking more about the overall replication issue during bath-time and during sleep (😂) and will provide some more ideas (hopefully).


[ANDROID] Getting white flash on background while qr code is being generated

Ignore ActivityIndicator, I just made sure that flash isn't related to animation

My modal that is storing component which is storing qr code:
`const Modal = (props: Props) => (

{props.children}

)
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: 'yellow', //rgba(0,21,43,0.75)
alignItems: 'center',
justifyContent: 'center',
padding: 24,
} as ViewStyle,
wrapper: {
backgroundColor: 'white',
padding: 16,
paddingTop: 32,
alignItems: 'center',
justifyContent: 'center',
alignSelf: 'stretch',
borderTopRightRadius: 24,
borderBottomLeftRadius: 24,
} as ViewStyle,
})
export default Modal`
And Im using react-navigation modal to show this on screen
only problem occurs on android emulator, ios is fine

Same issue here

Same issue here

Same issue here

Only in Andriod

same issue. Any new update for this?

@AGFarhat @sertony @mroozspace  @Jobel91
Followed advised pattern and have working QR code on iOS and on Android simulator, but when published, on real Android device I have blank WebView(scrollbars that being hidden within couple seconds). I have React Native 0.57. Can you please report RN version and confirm that hacks works on real Android device. Thanks!

@todorone , it works on Android real device, React Native version : 0.57.1

@AGFarhat @sertony @mroozspace @Jobel91
Followed advised pattern and have working QR code on iOS and on Android simulator, but when published, on real Android device I have blank WebView(scrollbars that being hidden within couple seconds). I have React Native 0.57. Can you please report RN version and confirm that hacks works on real Android device. Thanks!

Yea i got that randomly one day... its weird.
Anyways i think i found a fix that works for me. Basically make sure that for props bgColor and fgColor you insert either in the form 'black' or 'white' or as 'rgb(xxx,xxx,xxx)'. try it (y)

Ignorar ActivityIndicator, me aseguré de que el flash no esté relacionado con la animación

Mi modal es el componente de almacenamiento que almacena el código qr:
`const Modal = (props: Props) => (
{props.children}
)
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: 'yellow', //rgba(0,21,43,0.75)
alignItems: 'center',
justifyContent: 'center',
padding: 24,
} as ViewStyle,
wrapper: {
backgroundColor: 'white',
padding: 16,
paddingTop: 32,
alignItems: 'center',
justifyContent: 'center',
alignSelf: 'stretch',
borderTopRightRadius: 24,
borderBottomLeftRadius: 24,
} as ViewStyle,
})
export default Modal`
And Im using react-navigation modal to show this on screen
only problem occurs on android emulator, ios is fine

Como hiciste para mostrar el ActivityIndicator mientras se genera el Qr?

Ignore ActivityIndicator, I just made sure that flash isn't related to animation

My modal that is storing component which is storing qr code:
`const Modal = (props: Props) => (
{props.children}
)
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: 'yellow', //rgba(0,21,43,0.75)
alignItems: 'center',
justifyContent: 'center',
padding: 24,
} as ViewStyle,
wrapper: {
backgroundColor: 'white',
padding: 16,
paddingTop: 32,
alignItems: 'center',
justifyContent: 'center',
alignSelf: 'stretch',
borderTopRightRadius: 24,
borderBottomLeftRadius: 24,
} as ViewStyle,
})
export default Modal`
And Im using react-navigation modal to show this on screen
only problem occurs on android emulator, ios is fine

How do you show the ActivityIndicator while the QR is generated?

For me, when the QR code is rendered it makes invisible any TextInputs. Using Expo API version 32.
I was able to take the sample code on the README of this project and replicate the issue on two android devices as the sample code includes a TextInput. It's a bit intermittent, sometimes they show and you can click on them and enter text even though you can see them and then sometimes they show after entering text.
Putting the QRCode inside a ScrollView with overflow hidden solved the problem for me so thanks for those who offered that solution to the flicker. I'd raise a specific issue but as the same solution fixed the problem for me, I suspect this might be the same bug.

@AGFarhat Many Thanks

@AGFarhat it's work for me, many thanks

I had the same issue, fixed it with a little 'hack'.
Add a view component around your QR code and apply overflow:'hidden' style to it.
Let me know if that works for you too

It's work, thank much

I had the same issue, fixed it with a little 'hack'.
Add a view component around your QR code and apply overflow:'hidden' style to it.
Let me know if that works for you too

@AGFarhat it's work, thank much

same issue  and it's work,very thanks

@AGFarhat It Worked, Thanks :)


Question about the LinearKFPositionVelocityEstimator

Sorry to interrupt, but I am confused by the codes below:
_ps.segment(i1, 3) = -p_f;
_vs.segment(i1, 3) = (1.0f - trust) * v0 + trust * (-dp_f)
pzs(i) = (1.0f - trust) * (p0(2) + p_f(2))
I wonder what the _ps and the _vs are, it seems that _ps is negative value of the position of four legs in the world coordinate.

_ps is the position vector from foot to CoM in the world frame, _vs is the relative velocity vector of CoM with respect to foot (just personal unstanding)

_ps is the position vector from foot to CoM in the world frame, _vs is the relative velocity vector of CoM with respect to foot (just personal understanding)


Bug in custom layer input tensor

System: Python 3.8.3 64-bit | Qt 5.12.9 | PyQt5 5.12.3 | Linux 5.8.0-55-generic
keras (newest version)
from keras.layers import Layer
import numpy as np
from keras.layers import Input
from keras.models import Model

InputTensor = [0.1,0.2,0.3]      # Attention! Different tensors cause errors.
                                 # See  below the code!

InputTensor = np.array(InputTensor)

class MyLayer(Layer):

    def __init__(self, **kwargs):
        super(MyLayer, self).__init__(**kwargs)
    def build(self, input_shape):
        self.built = True
        super(MyLayer,self).build(input_shape)

    def call(self, x):
        return x

inputlayer = Input(shape = InputTensor.shape)
layer = MyLayer()(inputlayer)

model = Model(inputlayer, layer )
model.summary()

Output = model.predict(InputTensor)
output = np.array(Output)
print("dim(Output) = "+str(output.ndim))
print("Output = "+str(Output))

Input tensor [0.1,0.2,0.3] cause no problems. Output is [[0.1][0.2][0.2]]. Access to tensor elements are possible. model.summary is (None,2), ndim is 2.
Input tensor [[0.1, 0.2,0.3],[0.2,0.3,0.4],[0.3,0.4,0.5]] has an output as [[0.1 0.2 0.3][0.2 0.3 0.4][0.3 0.4 0.5]] and model.summary indicate a shape like (None,3,3) so that a tensor of tree dimensions is expected. ndim should be 3 instead of 2! Access to tensor elements is possible if you consider 2 dimensions instead of 3.
Input tensor [[0.1,0.2,0.3],[0.2,0.3,0.4]] generates an error message. It expected a shape of (None,2,3) and found only (None,3) although model.summary shows (None,2,3).

It shouldn't have any influence how many dimensions a tensor has, nor how big its elements are!
My task is, to get access to single elements of a tensor to generate an output tensor something like
class MyLayer(Layer):
    def __init__(self, **kwargs):
        super(MyLayer, self).__init__(**kwargs)
    def build(self, input_shape):
        self.built = True
        super(MyLayer,self).build(input_shape)

    def call(self, x):
        OutputTensor = [[0.0, 0.0],
                        [0.0, 0.0]]
        OutputTensor[0][0] = x[0][0]
        OutputTensor[1][1] = x[1][0]
        OutputTensor[1][0] = x[2][0]
        return OutputTensor

@Oezkan23
Could you please share the colab gist to analyse more of it.Thanks

@Oezkan23
Could you please share the colab gist to analyse more of it.Thanks
See:
https://gist.github.com/Oezkan23/630ed43d3a80b550e025037fa2439484

@Oezkan23
Please post this issue on keras-team/keras repo.
To know more refer to:
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999


[Explore] Cannot set y-axis lower bound to 0 on Line Chart

On the Line Chart ("viz_type": "line") you cannot use the controls to set a y-axis lower bound of 0. As a hacky workaround you could set the lower bound to a small number (0.0001) or manually update the form data.
Expected results
Setting y-axis lower bounds should update the form data and change the y-axis lower bound to 0.
Actual results
Setting y-axis lower bounds to 0 keeps the form data as: "y_axis_bounds":[null,null] and nothing changes
Screenshots

How to reproduce the bug

Create a line chart
Try to set the y-axis lower bound to 0

Environment
(please complete the following information):

superset version: master

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

closed by: https://github.com/apache/superset/pull/15091


Can't install using bower

bower extract       angular-utils-pagination#* archive.tar.gz
bower EMALFORMED    Failed to read /tmp/sebas/bower/angular-utils-pagination-6041-TkX6q1/bower.json

Maybe something wrong on yout bower.json? Missing comma?

Yes, malformed json. Fixed now.


Remove support for deprecated gatsby-image

      ✋

Maybe this is done?
Have a look:
https://github.com/raae/gatsby-transformer-cloudinary/pull/8#pullrequestreview-1120251123


[merge block] 4899 flake8 #3

Resolves #4899
Similar to https://github.com/hydroshare/hydroshare/pull/4909 but with a "lighter touch" because this PR uses autopep8 instead of black for autoformatting (black is opinionated).
Merge blocked pending https://github.com/hydroshare/hydroshare/pull/4877

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4911


Implement improved snow falling level functionality in a plugin

As the IMPROVER product owner I would like IMPROVER to have the capability to compute rain/snow probabilities robustly: this requires implementing the improved snow-melting (falling) level functionality (which is able to extrapolate below ground for all temperature profiles).
Related issues: #IMPRO-558
Prerequisites: #IMPRO-616
Acceptance criteria:

Following on from IMPRO-616, which uses the wet bulb temperature profile directly in calculating the falling snow level below sea level - implement the suggested solution (following confirmation from Nigel that we wish to go ahead). This might involve modifying the existing plugin, or creating a new plugin entirely.
Create new unit tests as required.
(If creating a new plugin) update the CLI (to use the new plugin).
CLI/acceptance tests may need updating - but plot the differences between new and old data and check that it is sensible.
Plot the output on a cold day when the falling snow level will be below sea level.
If the CLI changes, create a follow-on ticket to capture the work required to update the suite to use this new interface.

Done.


[Bug] Make StaticText instance a class attribute of the app  [sf#211]

Reported by brendansimon on 2017-06-25 13:52 UTC
The name of a StaticText instance generated is local to the OnInit() function, therefore I can't reference the widget from outside the class (or the function).
I would like to be able to update some StaticText based on various application events.
e.g. "Pass" or "Fail" or a numerical result.
Should all widgets be accessible ?  Maybe an option (checkbox) in the builder to allow any widget to be exposed or not?

Commented by dschwertberger on 2017-06-25 14:15 UTC
Set "Store as attribute" on the Widget tab of the Properties window.

Updated by dschwertberger on 2017-06-25 14:16 UTC

status: open --> closed
assigned_to: Dietmar Schwertberger


Decorated Request in case of third-party Server Request Creator

Hi there
Related to #2709, how is it possible to get a decorated request?
I mean, to get a response factory that would create a decorated response, we could use \Slim\Factory\Psr17\SlimHttpPsr17Factory. But I can't use \Slim\Factory\Psr17\SlimHttpServerRequestCreator to achieve that for decorated requests, could I?
declare(strict_types=1);

use Nyholm\Psr7\Factory\Psr17Factory;
use Nyholm\Psr7Server\ServerRequestCreator;
use Psr\Http\Message\RequestInterface as Request;
use Psr\Http\Message\ResponseInterface as Response;
use Slim\Factory\AppFactory;
use Slim\Factory\Psr17\SlimHttpPsr17Factory;

require __DIR__.'/../vendor/autoload.php';

$responseFactory = new Psr17Factory();
$app = AppFactory::create(
    SlimHttpPsr17Factory::createDecoratedResponseFactory(
        $responseFactory, $responseFactory
    )
);

$app->get('/', function (Request $request, Response $response, array $args) {
    $response->getBody()->write(get_class($request).', '.get_class($response));

    return $response;
});

// Create the nyholm server request creator.
$creator = new ServerRequestCreator(
    $responseFactory, $responseFactory, $responseFactory, $responseFactory
);

// Create the request.
$request = $creator->fromGlobals();

$app->run($request);

Requesting the route would return
Nyholm\Psr7\ServerRequest, Slim\Http\Response

I just saw, that instead of using the server request creator, we could use \Slim\Http\Factory\DecoratedServerRequestFactory:
$decoratedServerRequestFactory = new DecoratedServerRequestFactory($responseFactory);
$request = $decoratedServerRequestFactory->createServerRequest(
    'GET', $responseFactory->createUri('/'), []
);

Unfortunately there is no createServerRequestFromGlobals() method.

Another workaround would be the following:
declare(strict_types=1);

use Nyholm\Psr7\Factory\Psr17Factory;
use Nyholm\Psr7Server\ServerRequestCreator;
use Psr\Http\Message\RequestInterface as Request;
use Psr\Http\Message\ResponseInterface as Response;
use Slim\Factory\AppFactory;
use Slim\Factory\Psr17\ServerRequestCreator as SlimServerRequestCreator;
use Slim\Factory\Psr17\SlimHttpPsr17Factory;
use Slim\Factory\Psr17\SlimHttpServerRequestCreator;

require __DIR__.'/../vendor/autoload.php';

$psr17Factory = new Psr17Factory();
$app = AppFactory::create(
    SlimHttpPsr17Factory::createDecoratedResponseFactory(
        $psr17Factory, $psr17Factory
    )
);

$app->get('/', function (Request $request, Response $response, array $args) {
    $response->getBody()->write(get_class($request).', '.get_class($response));

    return $response;
});

// 1) Create the Server Request Creator.
$nyholmServerRequestCreator = new ServerRequestCreator(
    $psr17Factory, $psr17Factory, $psr17Factory, $psr17Factory
);

// 2) Use Slim to create a new `Slim\Factory\Psr17\ServerRequestCreator`.
$slimServerRequestCreator = new SlimServerRequestCreator(
    $nyholmServerRequestCreator, 'fromGlobals'
);

// 3) Use Slim-Http to create a decorated creator.
$slimHttpServerRequestCreator = new SlimHttpServerRequestCreator($slimServerRequestCreator);

$app->run($slimHttpServerRequestCreator->createServerRequestFromGlobals());

Step 1 assumes that the third-party PSR-7 implementation has a Server Request Creator (Nyholm has one).
Step 2 assumes that the Server Request Creator of the third-party PSR-7 implementation has a fromGlobals method, that can be used to create the server request (Nyholm has one).
If the third-party PSR-7 implementation has another method (like for example Slim-PSR7 createFromGlobals), then the second param should be changed accordingly.
Is this the way to go?

You can simply instantiate a decorated server request like this:
<?php
declare(strict_types=1);

use Slim\Factory\ServerRequestCreatorFactory;
use Slim\Http\ServerRequest as DecoratedServerRequest;

$serverRequestCreator = ServerRequestCreatorFactory::create();
$request = $serverRequestCreator->createServerRequestFromGlobals();
$decoratedRequest = new DecoratedServerRequest($request);

Ah I see. This would only work for the supported psr17 implementations. But we can always add a new implementation by calling \Slim\Factory\Psr17\Psr17FactoryProvider::addFactory(), can't we?