@jhoneill Wanted to check and see if anything jumps out at you before I dig in #841

@jhoneill  Wanted to check and see if anything jumps out at you before I dig in. Bug reported in #841 about series hearders,  >2 and the all get set to Series 1
https://github.com/dfinke/ImportExcel/blob/master/Public/Add-ExcelChart.ps1#L75-L86


Occur NullPointerException when get an view by view‘s id

this situation often happens when use ViewPager

my anko version: 0.10.4

how solve? why close


errors in attributes uploaded by the healthsites.io editor

Some of the attributed (OSM tags) created by the healthsites.io editor contain errors, i.e. they do not match the documentation on the OSM wiki.

[x] Key:electricity is used instead of the documented tag electricity
[x] the values of certain boolean (true/false) attributes are falsely set to True/False in the uploaded OSM tags. Typically, such OSM tags should read yes/no instead. Affected attributes are for example: dispensing, wheelchair, emergency, …
[x] when a user leaves a field in the form on healthsites.io empty, for example because they do no know the respective attribute or the health site doesn't have such an attribute, the resulting uploaded OSM features will end up having these tags anyway, only with an empty value. Here is an example: https://www.openstreetmap.org/api/0.6/changeset/80901102/download – as you can see, some tags are uploaded with empty value fields, e.g. <tag k="healthcare:speciality" v=""/>. In such situations these "unset" tags should be omitted in the uploaded changes to OSM.
[ ] the source tag should not be set to healthsites.io on the uploaded OSM features. A source tag directly on an OSM feature is in general discouraged (see also #1343), and when used like this would imply that healthsites.io is the source (i.e. provenance/origin) for the changes been made to the respective health site feature. healthsites.io is, however, in these cases only the tool to conduct a change to the OSM database, and already sufficiently documented in the changeset's created_by tag.
[ ] I believe that addr:full should only be used in rather rare circumstances, i.e. when a  feature has an address, but this address doesn't fit to the common "western" address schema of “city/road/hosuenumber”. If possible, the respective tags (addr:housenumber, etc.) should be used.
[ ] health sites wit a non-operational status should probably be marked more explicitly as non-operational, e.g. though lifecycle prefix tags. This would allow data consumers to more easily detect the operational status of such objects. e.g. a disused hospital would not be displayed like a operational hospital on a general purpose map.
[ ] opening hours could be stored in a more condensed manner, for example: https://www.openstreetmap.org/node/6630801588/history has every weekday listed separately, even though the hours are the same for every day. It could be written as Mo-Fr 08:00-16:00; PH off (instead of Mo 08:00-16:00; Tu 08:00-16:00; We 08:00-16:00; Th 08:00-16:00; Fr 08:00-16:00; Sa off; Su off; PH off).

I want to press on number 3 above, the empty values are really annoying. See for example this changeset https://overpass-api.de/achavi/?changeset=76262966 .
I cannot know whether the healthsites user intended to remove the phone number, but this seems like a possible bug also, because the phone number seems to be a current number according to several local sources I checked.

hi @markherringer
can you check point 4 please? are you agree or disagree?

the source tag should not be set to healthsites.io on the uploaded OSM features. A source tag directly on an OSM feature is in general discouraged (see also #1343), and when used like this would imply that healthsites.io is the source (i.e. provenance/origin) for the changes been made to the respective health site feature. healthsites.io is, however, in these cases only the tool to conduct a change to the OSM database, and already sufficiently documented in the changeset's created_by tag.

hi @tyrasd @tilmanb
point 1-3 already fixed : https://github.com/healthsites/healthsites/pull/1352
can check in here : https://overpass-api.de/achavi/?changeset=82284316

Hello, @meomancer
Yes, agree with point 4. Use 'created by' tag to reference healthsites.io input

@shawnsarwar we need to fix the ODK editor as it also indicates 'healthsites.io' as the source. See point 4 above from @tyrasd
'healthsites.io is, however, in these cases only the tool to conduct a change to the OSM database, and already sufficiently documented in the changeset's created_by tag.'

Thanks @tilmanb - we have updated our site to fix item 3 -  busy deploying that now

@meomancer For item 5 (addr:full replacement) I propose:
addr:housenumber
addr:street
addr:postcode
addr:city
addr:country

See https://wiki.openstreetmap.org/wiki/Key:addr#Commonly_used_subkeys for other possible attributes we could ask for.

[…] See for example this changeset https://overpass-api.de/achavi/?changeset=76262966.
I cannot know whether the healthsites user in the mentioned changeset intended to remove the phone number, but this seems like a possible bug also, because the phone number seems to be a current number according to several local sources I checked.

This looks very much like issue #1357 to me. I've fixed it in https://www.openstreetmap.org/changeset/82565921

I believe that addr:full should only be used in rather rare circumstances, i.e. when a feature has an address, but this address doesn't fit to the common "western" address schema of “city/road/hosuenumber”. If possible, the respective tags (addr:housenumber, etc.) should be used.

See https://github.com/healthsites/healthsites/pull/1387 which replaces addr:full with broken out fields. @tyrasd your review would be appreciated.

I've asked @meomancer to add nominatum lookup for town etc - that will come in a subsequent update.

Point collect changesets
Example of changesets:
https://www.openstreetmap.org/changeset/82655197


Implementing Different Objects

Right now, keikan supports:

Planes
Spheres
and Mandelulbs (a fractal).

This is quite a small number of objects. At the least, the following primitives should be implemented:

Triangles
Rectangular Prisms
Cones

To implement a new object, go to objects/ and make a new file with a data structure that implements the March and/or the Trace traits.

I am intrested in contributing. But I dont know much about rendering engine in general. So cant gurantee. And cargo build is failing.

Hey @mustafapc19, thanks for the interest. In light of your failed cargo build, I recently cloned and rebuilt the project myself. It turns out that my most recent changes hadn't saved before commiting, so I've saved them and pushed to master - the project should be buildable now.
Computer graphics is a fun subject, and there are lots of resources to get started.
The way keikan currently works is simple: A scene is a list of objects with a camera. At render time, the camera asks each object to provide information about it. This information is used to calculate light bounces, which renders the final scene.
Currently, keikan supports two rendering techniques, ray-tracing and ray-marching. Ray-marching uses the distance to objects to calculate collisions, whereas ray-tracing uses direct intersections to calculate collisions. Currently, all objects are in the /objects subfolder. Each object is a structure that implements at either of the Trace or March trait, or both.
The March trait requires you implement a function that returns the distance to the nearest point on that object given a point in 3D space. For example, the distance to the nearest point on a sphere is given by the equation:
length(point - sphere_position) - sphere_radius

So to implement that for Keikan you just need to translate that to Rust and wrap it into a neat little function:
impl March for Sphere {
    // ... snip

    fn march(&self, point: Vec3) -> f64 {
        (point - self.position).length() - self.radius
    }
}

There are a lot of cool fractals you can make this way. If you want to see the distance functions for some more shapes, check out Inigo Quilez's website: https://iquilezles.org/www/articles/distfunctions/distfunctions.htm
Ray-tracing is a bit more involved. Given a ray, a ray tracer must determine:

Whether the object was hit (i.e. intersects the ray)
How far away the collision was
And the normal of the collision (which way the face of the object was facing)

There are a lot of well-documented ray-intersection tests online, just google one for the specific shape you're trying to implement. If you need any help getting started, feel free to reach out. Thanks again for the interest.

Thanx. I will look into it. But this a new thing for me and I dont know if I have time to actually contribute. But If I can I surely will.


Flask after_request still execute

I've had a problem with the after_request decorator for a long time,I don't know when the exception will not execute after_request

after_request says:

As of Flask 0.7 this function might not be executed at the end of the request in case an unhandled exception occurred.

teardown_request says:

run at the end of each request, regardless of whether there was an exception


Other modules window shows Hey, Wait! in the title

Not sure what is causing this, but I noticed that with Inline Web Browser an FX Master. See screen shots below:

This will be resolved in the upcoming release.

Now resolved in version 0.4.0 available now.


Link Pipeline concepts page to relevant concept docs

Fixes #1624

This change is

/assign @sarahmaddox

/retest

/retest

/retest

/lgtm
/approve
Thank you for working on this!

Many thanks, @joeliedtke !


Make error after using electron-rebuild

1、rm -rf node_modules
2、npm install && ./node_modules/.bin/electron-rebuild -d https://npm.taobao.org/mirrors/node -v 11.3.0 -m ./
3、npm run make
Always get the following error， can somebody help? what happened?
If you do not execute electron-rebuildand run make directly, no error will be reported
 "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "eslint src --color",
    "rebuild": "electron-rebuild -f -w ffi-napi"
  },

An unhandled rejection has occurred inside Forge:
EPERM: operation not permitted, scandir 'C:\cygwin64\tmp\electron-packager\win32
-x64\docer-win32-x64\resources\app\node_modules\abbrev'
Error: EPERM: operation not permitted, scandir 'C:\cygwin64\tmp\electron-package
r\win32-x64\docer-win32-x64\resources\app\node_modules\abbrev'

Is there a backtrace?

This is a duplicate of https://github.com/electron-userland/electron-forge/issues/2173


Locale Support for YouTube

If one were to add a playlist such as Top Tracks - United Kingdom the language of the country the bot is currently hosted in would be the language of the title, therefore with this you will be able to do this for instance Locale.setDefault(Locale.FRENCH); and then all the titles would be in French (If there is a translation provided by YouTube)

Definitely should not be manually done for each request separately. One option is to just do this:
    manager.setHttpBuilderConfigurator(builder ->
        builder.setDefaultHeaders(Collections.singleton(
            new BasicHeader(HttpHeaders.ACCEPT_LANGUAGE, Locale.FRENCH.getLanguage())
        ))
    );

It affects all HTTP request Lavaplayer makes. I do not want to tie it to any JDK defaults, as all Lavaplayer configuration should strictly be performed only through Lavaplayer itself. Otherwise you may change default locale for some other purpose and suddenly Lavaplayer works differently, causing much confusion.

That works for me 👌


23 create gif animation of use case

Made some adjustments to the dashboard to allow for better readability and screen recorded GIF after tweaks were made. I also added the gif to the README file.
Let me know if there's anything you want me to change!

I am not able to open the render URL above though. @monazhu

I am not able to open the render URL above though. @monazhu

Oh weird - I followed what's in the lecture notes for this section but maybe I'll ask Joel about it today...

The link works. It just takes forever to load.


initial ecdsa verif

This is an example of how ecdsa verif could be done. This is designed to be almost compatible with
https://github.com/starkware-libs/cairo/blob/d6163bdd33e12e0b2d8b1ec7b8f5f6162d9bef54/corelib/src/starknet/secp256_trait.cairo#L66
Scarb 2.8.2 is needed.
I added comment in the file to understand how to generate the hint.
The ideal way for offchain would be to modify this function and send a request to an oracle using https://github.com/reilabs/cairo-hints/
, cairo would send the points and scalars and curve id, and the oracle would respond with the serialized felt252 hint.

Hey @feltroidprime I am closing this for now. Code is parked in batch_esdsa_verification_draft, garaga optimizations will be added to the roadmap.
Big thanks!


Feature/au 757 dialog popup visuals

AU-757

What was done

Dialogs have different style than before
Especially the one when leaving half-filled form

How to install

Make sure your instance is up and running on correct branch.

git checkout feature/AU-757-dialog-popup-visuals
make fresh

Run make drush-cr

How to test

[ ] Clear browser cache
[ ] Log in
[ ] Go on form
[ ] Write something on the email field
[ ] Click on an item in the main menu
[ ] see that dialog box has no yellow koro and that the layout is approximately like this (not identical texts): https://share.goabstract.com/9b7318da-ce27-401b-a02b-20b93b30a1bc?collectionLayerId=33fa2c9c-ac31-4174-9fb7-c2e2a0ed1bc4&mode=design&sha=latest
[ ] Check that code follows our standards

Designers review

[ ] This PR has been visually reviewed by a designer (Heikki)

Leaving form for 10 minutes gives me this still, is it by design?


Better handling of notifications for multiple rooms

This morning, when I turned on my phone (is always in airplane mode at night), I recieved a GCM notification for Riot. I clicked on it and was directly taken to a room where several new messages had arrived over night.
There was a new message in another room, too, however, a direct chat, which I didn't notice because I was directly taken to that other room. Only when I switched back to the room list because I wanted to write something an hour later, I noticed that another (much more important) message had been waiting for me.
An easy improvement would be that clicking on the notification would lead to the room list if notifications for more than one room are pending. For large room lists, though, this won't make things much better.
How could a UI look like that makes clear that there are new messages waiting in other rooms?

It would be good if the notification widget remembered all the notifications (or the n most recent ones), and sort more important notifications to the top.
For example, look at how the clipstack behaves for multiple entries:

And after dragging down, it opens up to:

Tapping on the collapsed Riot notification (or the notification header, when expanded) could open a scrollable view of all notifications, before going to the rooms list. If there is only one notification, it should go directly to the room as before.

Done in Riot 0.8.26


References do not take imports into account

Implemented a first attempt in version 0.2.0

Implemented a first attempt in version 0.2.0


Multiple axes with different scales is not supported? But its mentioned in the documentation

Who is the bug affecting?
All Supervisors
What is affected by this bug?
Analysis
When does this occur?
when try to add another axixs to the chart
As per documentation --
Axis ID
The properties xaxisid and yaxisid from the Data component have to match the scale propertie id of the specific axis type. This is especially needed if multi-axes charts are used.
Creating Multiple Axes
With cartesian axes, it is possible to create multiple X and Y axes. To
Where on the platform does it happen?
on any lwc component with chart
How do we replicate the issue?
just add two axis component with ids and map it to the data
Expected behavior (i.e. solution)
Multiple axis should have shown
Other Comments
Do you have a sample that works?

Hi @nehanagori,
We've exposed the Chart.js functionality to work with multiple axis, but we don't have any example at the moment.
Unfortunately, I've tried to create one and it seems that we might have a bug regarding this topic. We will have a look at it and will let you know.
fyi @scolladon I think we've a bug on the chartServiceConfig module. The merge of axis when they are of the same type is not working correctly. Also, we're exposing the id attribute and it seems that this is a reserved property, so the value is being overwritten. I will work on a fix for that 🚧

Yes you are right, Id attribute is reserved. I even tried to change that in js of the component ,  but that was not enough. Looking forward for the fix from you :)

Hi @nehanagori ,
This issue should have been fixed now 😄
You can take the last commit of the master branch and integrate it in your project. We've also included a new example in the sample gallery, don't hesitate to have a look and try it by yourself. We would love to hear any feedback from your 🚀


Required Number and Boolean Fields throw errors with 0 or false

When creating a new record, if a field is marked required the create operation will fail if the value is set to a "false-y" value like false or 0.
To Replicate:
Create a collection.
Create a number field with required set to true
Use the API or the Web GUI to create a new record with the field = 0
Create a collection.
Create a boolean field with required set to true
Use the API or the Web GUI to create a new record with the field = false
Error:
{code: validation_required, message: Missing required value.}

I also get the error when using the web GUI and try to set a required number field to 0

This was recently reported in https://github.com/pocketbase/pocketbase/issues/436#issuecomment-1248571689.
This is working as expected, although I agree that it is not very well explained at the moment.
Since v0.3.0 PocketBase doesn't support anymore null values (with the exception of the json type field). Full table with the supported PocketBase values could be found in https://github.com/pocketbase/pocketbase/releases/tag/v0.3.0.
The "Required" constraint means "non-empty/non-zero" value.  In PocketBase (and Go) false is the empty/zero value for bools, 0 is the empty/zero value for numbers, empty string for strings, and so on.
I'll consider adding a tooltip explaining better the "Required" constraint behavior for each field after the refactoring.

it's ok for a bool as UI only allow true/false
It's more an issue with number. 0 is a valide value :(.

@sgruhier 0 is a zero-default for the number field. If you want to make a number required, use the min/max field options. This will be better documented in the next release.


Support 8 and 9 digits Indonesian numbers

This document (found here) specifies the min and max number of digits (excluding country and area code) for Indonesian phone numbers starting with
+62 (22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 39 72)
as 7 and 9. This PR updates indonesia.rb to reflect these rules. According to this document 5 digits shouldn't be allowed, but I left it for backward compatibility

cc @floere @czhc @Slike9

Coverage increased (+0.002%) to 98.066% when pulling 3293a626fb3885d98d89911e101ce3975fdf53d7 on lukkry:lukkry/indonesian-phone-number into c7a71244ea42c425cfa680ead3f0bc049a45406d on floere:master.


How do i access rbc-month-row ? There is no row wrapper available

Do you want to request a feature or report a bug?
Discuss a feature
What's the current behavior?
There is no row wrapper available to take control of the entire row in month view

What's the expected behavior?
Want control over rbc-month-row

not sure what you mean by "access", you can write some CSS if you need to style it

Want control over the div which has rbc-month-row

there is not at the moment sorry


Fix exception in Grayscale.cs

TorchSharp Greyscale() transform assumes batch dimension when calculating the channel dim channel = image.shape[1] but this is not correct, as for a non-batched tensor channel = image.shape[0] The channel dim should be calculated using something such as  channel = image.shape[image.ndim - 3]
Example working pytorch:
img = torch.rand((1, 32, 32))
result = torchvision.transforms.functional.rgb_to_grayscale(img)
result = torchvision.transforms.Grayscale()(img)

Example failing Torchsharp
var img = torch.rand(1, 32, 32);
var res = torchvision.transforms.functional.rgb_to_grayscale(img);
var res2 = torchvision.transforms.Grayscale().call(img);

Thank you @GilesBathgate, for starting to contribute to TorchSharp! Much appreciated.
If you have time, please add a brief intro about yourself to this thread: https://github.com/dotnet/TorchSharp/discussions/333. It's nice for everyone (users and other contributors) to know who's been working on the code.


You should not use  outside a

After update react-router to version 5.0.0 and connectedReactRouter to version 6.4.0 still having an error in console:
Error: Invariant failed: You should not use  outside a

I've ran into this issue before, make sure your react-router and react-router-dom are the same version (5.0) do a npm cache clean or yarn cache clean, remove node_modules and package-lock.json/yarn.lock and do a npm install/yarn install.

@austsinovich have you found any solution to this problem?

@ahmedtehseen
To sum it up, the whole concept behind NPM is broken to the bone (and using yarn on top of the same broken concept does not fix it).
You need to resolve dependencies yourself over multiple packages checking their peer dependencies (did not get any warning from npm/yarn, I know why, its just plain stupid, but lets not mess with it here).
yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I found scooping code and package.json's that this versions do match together and work. It fixed the issue for me.

@ahmedtehseen
Stupidity of peer dependency system, where the system fails to realize there is an issue due to lax version requirements. In my case react-router was installed as ^4.3.1 and react-router-dom was installed as ^5.0.0.
yarn add<EMAIL_ADDRESS>fixed it.
 A normal package manager would find out that ^4.3.1 is the only matching package version, however npm is not a normal package manager.
 Yeah but its always some super smart logical reason why that has to do upside down.  Usually excused because "it was always like that, we want bc, but we created a new executable, which does as you expect", introducing thereby other issues which would never have existed in first place if simply being logical.


Avoid stacked toast of the same reason

What this PR does / why we need it:
Before
https://user-images.githubusercontent.com/32532742/138092609-4a40aac1-b4c3-4e03-b167-a8bfb8c4127c.mp4
After
https://user-images.githubusercontent.com/32532742/138092652-2d2ce35f-bdbd-4207-b1d6-ba7d580c562b.mp4
Due to the change in this PR, toast caused by the same reason (same issuer) and has the same message with the latest toast in the toast list will not be added to the toast list, that avoids annoying stacked toasts in case of errors occurred intervally.
Which issue(s) this PR fixes:
Fixes #2411
Does this PR introduce a user-facing change?:

NONE

It has driven me crazy. This is really well done!
/lgtm


SchemaRetriever: invert the order we look up entity records

First look up in the associated class, and only then look up
in Thingpedia. This is because entities.json from Thingpedia
can be out of date in case of developing skills locally.

Pull Request Test Coverage Report for Build 1239

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

Totals

Change from base Build 1237:
0.0%

Covered Lines:
9997

Relevant Lines:
12346

💛  - Coveralls


Incorrect Shortcut for Narrator Developer mode

This is what the page says on how to turn on Narrator mode:

Turn on developer mode when Narrator is already running by pressing Caps Lock + Shift + F12

Upon pressing those keys on Win 10 v1909(build 18363.592), Narrator speaks "Not a narrator command" out loud. I then pressed Caps Lock + F1 to get to the Narrator help screen. This is what I found after searching for Developer mode:

(Now Control + Caps Lock + F12 did work but it took me several bing searches to see what's going on).
Thus, we should update the documentation to echo what the Narrator help screen says, especially since the "Narrator" key can be different as this page describes. (Or use the "Standard" shortcut if we're going to assume that most folks update their systems or provide some sort of hint/link indicating that there might be other key combinations)

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

ID: e908c6bb-72f1-b125-2822-e045951c0f67
Version Independent ID: c2ac959c-12b8-f17b-3383-ef73c613ecaa
Content: Accessibility testing - UWP applications
Content Source: windows-apps-src/design/accessibility/accessibility-testing.md
Product: uwp
Technology: design
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: kbridge

Thanks @keparanj. Topic has been fixed.


TypeError in /clan/mafiya-gang-jl82lrrr

Error in ClashLeaders
TypeError in /clan/mafiya-gang-jl82lrrr
Cannot read property '__symbol@@0.46359006175925277' of undefined
View on Bugsnag
Stacktrace
https://www.clashleaders.com/static/js/vendors.8d68595a3daede5c357b.js:13 - s.Et.Ht.get [as __symbol@@0.46359006175925277]

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/mafiya-gang-jl82lrrr


issue#308 Allow document selector match many documents and skip empty templates

This PR builds on top of:
https://github.com/helm-unittest/helm-unittest/pull/328
Which partially addressed the issue:
https://github.com/helm-unittest/helm-unittest/issues/308
This PR addresses use-case in it's entirety.
Use-case:
I want to assert whether or not all manifests of type "Deployment":

eg. define default resources section.
eg. follow naming convention
eg. set right namespace

I want this assertion to work for current and future deployments I might have in my chart.
I have to use document selector because I keep different types of k8s manifests in a single YAML files (eg. foo-application.yaml contains definition of Deployment as well as the Service)
It is resolved with introduction of two new properties on documentSelector level: matchMany and skipEmptyTemplates
Here's the updated documentation of the module

documentSelector: DocumentSelector, optional. The path of the key to be match and the match value to assert. Using this information, helm-unittest will automatically discover the documents for asserting. Generally you can ignore this field if the template file render only one document.

path: string. The documentSelector path to assert.
value: any. The expected value.
matchMany: bool, optional. Set to true to allow matching multiple documents. Defaults to false which means selector has to match single document across all templates.
skipEmptyTemplates: bool, optional. Set to true to skip asserting templates which didn't render any matching documents. Defaults to false which means selector have to find at least one document in every template.

EXAMPLE:
suite: Document Selector is matching many documents
templates:
  - "*"
tests:
  - it: deployment names should end with -deployment suffix
    documentSelector:
      path: kind
      value: Deployment
      matchMany: true
      skipEmptyTemplates: true
    asserts:
      - matchRegex:
          path: metadata.name
          pattern: -deployment$

Happy to hear any feedback you might have. The code might need some styling fixes etc. but functionally it seems to be doing what it's supposed to do.

@mszygenda Well done!
I finally got around to trying it out, and it works as expected.
Good idea to add the skipEmptyTemplates.
Regarding functionality, it looks to me that it is a nice extension to the current feature-set, without breaking or forcing it on anyone.
I have not spent much time looking into the code, so I dare not comment on code quality.

I would love to see this added, as a way to enforce a general hygeine tests across all resources of a specific type.

One nice addition, though of course it could easily be another PR, is to allow the value: field to be a string or a list of strings. This could enable, for instance, a set of conventions applied to both Deployment and StatefulSet objects.

Any update on when this will be merged?

Resolved merge conflicts.
There was some new unit-test which asserted whether or not invalid DocumentIndex property values are handled as "Index out of bounds error" at the individual assertions level.
Since there it's no longer in the scope of particular assertion implementations to deal with DocumentIndex I removed the test. Instead I added a new one which verifies it at the higher level (assertion.go).

This change impacts nearly 1000 lines of code and 39 files. The project's got some decent testing, but there are spots without any unit tests. So yeah, this is pretty risky stuff. Might be worth putting out your own release just for this change.

We gave it a spin with a bunch of our in-house charts - simple ones and some pretty complex stuff too. Good news: everything seems to be working just like before. Didn't spot any problems.


fix: only apply limit disclosure for matching vcs

When you have a presentation definition with multiple input descriptors, and multiple VCs, it tries to apply the limit disclosure to all VCs. This means that claims are not disclosed that do need to be disclosed.
This PR updates the limit disclosure handler to only apply limit disclosure based on constraints in an input descriptor if the VC matches the requirements of the input descriptor.
It also handles an advance case, where if one VC matches multiple input descriptors. This is handled by combining the constraints and disclosing both requirements. If you only use the VC for one input descriptor in the end it means you disclose some attribute that are not needed, but as this is already an advanced case I think this is fine for now (we at least disclose what is needed). With the current API it would be very hard to fix this, as we need to have a mapping of input descriptor -> disclosed VC. And then maybe just include the same VC twice with different disclosures. But for now I think this already fixes the main bug.

Another one @sanderPostma / @ksadjad :)
We're just now basically starting to explore multi-vp / multi-cred exchanges, and that results in some edge cases being hit

Hey @sanderPostma, has this been released as an unstable release of PEX? It seems the latest (unstable 7) doesn't include this fix yet

Hi @TimoGlastra
After merging in your PR for PEX and OID4VC, tests in other libraries started failing.
There were issues in evaluationClientWrapper.ts,  evaluatePresentations & extractWrappedVcFromWrappedVp
It had to do with the fact that vpResults.value could return both a single item or an array and doing a vp.format === on an array is not going to work.
Sadjad started doing some fixes, but to make the lib work for singleton or one-element-array VPs I have made an emergency release from another branch (develop-20240918) so we could build our other repos again, but the multi-vp tests are failing in that one.
Some of the earlier .unstable releases like 2 or 3 have your changes still in there.


Logical tree depth exceeded while traversing the tree.

The full error is
InvalidOperationException : Logical tree depth exceeded while traversing the tree. This could indicate a cycle in the tree
This is occurring in a drop operation of a IDropTarget, right at the end - .Add(sourceItem);.
  if (dropInfo.DragInfo.SourceCollection != null)
                {
                    if (dropInfo.DragInfo.SourceCollection is ItemCollection)
                        (dropInfo.DragInfo.SourceCollection as ItemCollection).Remove(sourceItem);
                    else
                        (dropInfo.DragInfo.SourceCollection as IList).Remove(sourceItem);
                }
                if (dropInfo.TargetCollection != null)
                {
                    if (dropInfo.TargetCollection is ItemCollection)
                        (dropInfo.TargetCollection as ItemCollection).Add(sourceItem);
                    else
                        (dropInfo.TargetCollection as IList).Add(sourceItem);
                }

Traditionally this is a binding error, but this is not the case here.
What is happening is that the sourceItem is already apart of the TargetCollection. How is that possible?
In the image below, the BLACK container (and all the child elements) are separate controls. Container 0 and ImageSet 1 both have ItemsControl bound to gong. The Image controls do not.
Important to note that the light gray around the container and image controls, is also a separate control which has a ItemsControl bound to gong. So we are looking at multiple nested ItemControls.
The bottom most IMAGE block is outside of the BLACK container, yet when I start a drag from it, the entire container above is shown as the drag adorner.

Effectively I am then dropping a Container back into itself - hence the original error.
I am sure I am doing something incorrect, which is easily explainable. But for the life of me, I dont understand how a drag on a control can be registered as a drag of a completely separate control?
Thoughts and help would be really appreciated.

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on for so long, then it seems no one has the time to implement this.
Please reopen if you still encounter this issue with the latest stable version and then please use the issue template.
If you have enough time then it would be nice to test this issue against the latest alpha version (availabe via NuGet and appveyor, appveyor feed).
Thank you! 🙏

The exception thrown, when we drop something into itself.


[5.8] changed default 401 img from 403.svg to 401.svg

changed default 401 error img from 403.svg to 401.svg.

The 401.img is added in https://github.com/laravel/laravel/pull/4814
Documentation updated - https://github.com/laravel/docs/pull/4639

Will need to be listed in the 5.7 -> 5.8 upgrade docs, because that image wont exist on any current projects.

@laurencei  done

Perfect. 👍


SignatureAttributes requirement needs to be on the ELAM driver requirements page!

Why isn't the note (item #1) about SignatureAttributes on the ELAM drive requirements page where it belongs? Having it only on this page doesn't make sense because the INF file is written early in the development process, and isn't changed once it gets the driver loaded

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

ID: f969a593-1e57-9e24-5fe1-fc1d372fd571
Version Independent ID: 76a0f061-edc8-76cb-dc82-3b3f8532e06e
Content: ELAM Prerequisites - Windows drivers
Content Source: windows-driver-docs-pr/install/elam-driver-submission.md
Product: windows-hardware
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

So is it in https://docs.microsoft.com/en-us/windows-hardware/drivers/install/elam-driver-submission, does that work?

No. All that stuff should either be in one place, or there should be a note to look at the submission page for additional requirements, for the reason that I specified in my original comment, above

Done.  I did a little restructuring of that whole doc node.  Thanks again for the feedback!


Theme toggle don't work on OSX

Describe the bug
Theme toggle don't work on OSX.
Views, Toggle theme, what ever theme you choose nothing change,
To Reproduce
Views, Toggle theme
Expected behavior
Suppose to see the theme color to change
Technical Info (please complete the following information)

OS: High SIerra 10.13.6
Tusk Version: <IP_ADDRESS>2

Please see #88 for more info

It seems to occur no matter which version of Evernote is being used.

@livejamie  Works fine on regular Evernote version

Duplicate of #88


[OSD-17369] Deploy metrics-forwarder to request serving nodes

Adds node selector that requires nodes to be labeled with request-serving-component and CLUSTER_NAMESPACE-CLUSTER_NAME as per discussion in HyperShift Control Plane Serving Component Isolation design doc
What type of PR is this?
feature
What this PR does / Why we need it?
We need a middle level in this spectrum that isolates components exposed to end users (request serving pods) in their own dedicated hosts, while allowing the rest of the control plane workloads to share hosts.
See illustration here
Which Jira/Github issue(s) does this PR fix?
Resolves OSD-17369
Special notes for your reviewer
Pre-checks (if applicable)

[ ] Validated the changes in a hosted cluster
[ ] Included documentation changes with PR

/hold

/unhold


LUCI GUI for some nodes have become corrupt...

This is probably a OpenWRT problem but ...
I have 6 mesh nodes:
5x EA8300
1x EW72
All but 2 EA8300 have recently become corrupt, somehow... and display:

/usr/lib/lua/luci/dispatcher.lua:1081: module 'luci.controller.myapp.haas_mesh_tab' not found:
no field package.preload['luci.controller.myapp.haas_mesh_tab']
no file './luci/controller/myapp/haas_mesh_tab.lua'
no file '/usr/share/lua/luci/controller/myapp/haas_mesh_tab.lua'
no file '/usr/share/lua/luci/controller/myapp/haas_mesh_tab/init.lua'
no file '/usr/lib/lua/luci/controller/myapp/haas_mesh_tab.lua'
no file '/usr/lib/lua/luci/controller/myapp/haas_mesh_tab/init.lua'
no file './luci/controller/myapp/haas_mesh_tab.so'
no file '/usr/lib/lua/luci/controller/myapp/haas_mesh_tab.so'
no file '/usr/lib/lua/loadall.so'
no file './luci.so'
no file '/usr/lib/lua/luci.so'
no file '/usr/lib/lua/loadall.so'
stack traceback:
[C]: in function 'require'
/usr/lib/lua/luci/dispatcher.lua:1081: in function 'createindex'
/usr/lib/lua/luci/dispatcher.lua:1192: in function 'createtree'
/usr/lib/lua/luci/dispatcher.lua:694: in function 'menu_json'
/usr/lib/lua/luci/dispatcher.lua:795: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:478: in function </usr/lib/lua/luci/dispatcher.lua:477>

I have physically restarted but they still come up with the above.
The Mesh is still working. It is only the LUCI interface that has problems.
Should I factory reset? Fix some other way?

Never seen that.
It happens when you go to what webpage? Just <IP_ADDRESS>, for instance? Try from a different web browser on a different computer?

Any web page from any browser. Something to do with Luci Ui

Very weird. Did you attempt to upgrade them or something? These should only be upgraded using the Maxwell webpage. You might need to factory reset to restore, sorry.

Dear Andy
No problem. I have actually only used the Maxwell page to do anything on them…
I haven’t tried to fix them… my main unit still shows the ui and the rest all are now inaccessible!? But still working somehow, so to date I haven’t tried to fix anything.
I thought that maybe you have seen this before but guess I’ll have to reset them before it spreads to my main one!
Thanks
Ian
Sent from my iPhone
On 10 Aug 2024, at 12:48, Andy @.***> wrote:

Very weird. Did you attempt to upgrade them or something? These should only be upgraded using the Maxwell webpage. You might need to factory reset to restore, sorry.
—
Reply to this email directly, view it on GitHubhttps://github.com/drandyhaas/haasmesh/issues/12#issuecomment-2280971707, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADNMPMDK3BDVHLOTLXL4NEDZQXVZLAVCNFSM6AAAAABMJOVSJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBQHE3TCNZQG4.
You are receiving this because you authored the thread.Message ID: @.***>


Do Something, Anything, With The Public Header?

After trolling around on GitHub looking at Swift projects we all seem to share one thing no matter what the aim of the individual repo: we don't do anything with our public header.  Specifically the variables used for tracking version numbers for frameworks.  Is there any reason I shouldn't just nuke it and move on?  Should we start tying releases to that version number?

We should probably update the version number in our plist (which then gets exposed by the public header) in synchrony with the release number on Github.
Besides that, the public header is supposed to be used to import any ObjC components of a mixed-language framework.  For our purposes, it can also be exploited as a kind of "reexport" mechanism; we should probably think about doing that with Swiftz and Swiftx.

But specifically those variables?  I'm not gonna nuke the header, I just want to know what those things are doing there in the first place.

Apple wants them there, apparently.  :P
I suspect that they get used for module-level reflection when importing a framework into a Playground.  Even if that's not the case, I think we should still keep them around just in case they turn out to have some other use.  :)

Okay, I've been informed that the version number variables are entirely unimportant,  and that the imports in the header have no bearing on Swift at all.  We can just keep it empty.

@pthariensflame You gonna take this one when you fix the formatting?

Yup!  See #247 now.

:boom: :camel:


EventData kwargs missing in state conditional

I'm losing my EventData kwargs somewhere before my conditional is called.
The kwargs are present in the frame 5 below, asg=ur_api_asg, api_wait=api_wait, region=region, but when it gets to the conditional (looks like frame 15?), there's no kwargs.
[4]   /Users/bedge/git/server/ml-dev/nim-ml-ingestor/src/seed/fsm.py(283)<module>()
-> fsm.sqs_start(asg=ur_api_asg, api_wait=api_wait, region=region)
[5]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(282)trigger()
-> return self.machine._process(f)
[6]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(831)_process()
-> return trigger()
[7]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(312)_trigger()
-> if t.execute(event_data):
[8]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(198)execute()
-> self._change_state(event_data)
[9]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(209)_change_state()
-> event_data.machine.get_state(self.dest).enter(event_data)
[10]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(77)enter()
-> event_data.machine._callback(oe, event_data)
[11]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(812)_callback()
-> func(event_data)
[12]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(282)trigger()
-> return self.machine._process(f)
[13]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(831)_process()
-> return trigger()
[14]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(312)_trigger()
-> if t.execute(event_data):
[15]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(190)execute()
-> if not c.check(event_data):
[16]   /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(131)check()
-> return predicate(event_data) == self.target
[17] > /Users/bedge/git/server/ml-dev/nim-ml-ingestor/src/seed/fsm.py(217)if_scaled_to_nodes()
-> assert(asg)

Conditional:
    def if_scaled_to_nodes(self, event):
        self.log('if_scaled_to_nodes', event=event)
        asg = event.kwargs.get('asg')
        assert(asg)
        ....

Transitions:
transitions = [
....
    {'trigger':'scale_out',  'source':'scaling_out',  'dest':'scaled_out',  'conditions' ['if_scaled_to_nodes']},
....

I would have expected the EventData present in the 1st stack ame to propagate to the conditional as well.
pdb shows they are getting dropped around the partial wrapper:
[9] > /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(812)_callback()
-> func(event_data)
(Pdb++) l
807             """
808             if isinstance(func, string_types):
809                 func = getattr(event_data.model, func)
810
811             if self.send_event:
812  ->             func(event_data)
813             else:
814                 func(*event_data.args, **event_data.kwargs)
815
816         def _has_state(self, s):
817             if isinstance(s, State):
(Pdb++) event_data
<EventData('<State('scaling_out')@4430001680>', <Transition('idle', 'scaling_out')@4432917200>)@4406552464>
(Pdb++) event_data.kwargs
{'api_wait': 10, 'region': 'us-west-2', 'asg': 'dc-12-ur-api-AppServerGroup-1DFQF3NVKPZ1G'}

Still there, above, gone below.
(Pdb++) down
[10] > /Users/bedge/Virtualenvs/p2/lib/python2.7/site-packages/transitions/core.py(282)trigger()
-> return self.machine._process(f)
(Pdb++) l
277             """
278             self.transitions[transition.source].append(transition)
279
280         def trigger(self, model, *args, **kwargs):
281             f = partial(self._trigger, model, *args, **kwargs)
282  ->         return self.machine._process(f)
283
284         def _trigger(self, model, *args, **kwargs):
285             """ Serially execute all transitions that match the current state,
286             halting as soon as one successfully completes.
287             Args:
(Pdb++) kwargs
{}

ok, found that the args are not present in event.kwargs, rather
(Pdb++) event.args[0].kwargs
{'api_wait': 10, 'region': 'us-west-2', 'asg': 'dc-12-ur-api-AppServerGroup-1DFQF3NVKPZ1G'}

Not sure if this in intentional.
Just feels odd to have to pull them out of event.args[0].kwargs where elsewhere they exist in event.kwargs

Hi @bedge,
event.args[0].kwargs sure looks weird but I cannot tell why this is happening from the current input. Can you provide a minimal example of this issue?

That was it - I had a python namespace overload, where an imported method has the same name as a generated transitions on_enter method.
Renaming the on_enter method fixed the namespace collision.
I suppose one could detect this on initialization and flag the error. I'll leave it to you to decide whether to close this or keep as a wishlist todo item.

It is considered a feature that you can define on_enter_<state_name> methods in your model which will be called if <state_name> is entered. Or do you refer to the dynamically added trigger -- for instance scale_out -- which will be added to the model?

I tested this and it behaves like expected:
from transitions import Machine

class MyMachine(Machine):

    # define on_enter_A in Machine; this will shadow the possibility to add
    #  callbacks with on_enter_A
    def on_enter_A(self, event=None):
        print "entered A"

    def hello(self, event):
        print "Hello"

states = ["A", "B"]

transitions = [
    {'trigger': 'go', 'source': 'A', 'dest': 'B'},
    {'trigger': 'back', 'source': 'B', 'dest': 'A'}
]

m = MyMachine(states=states, transitions=transitions, initial='A', send_event=True)

# the above defined function
print(m.on_enter_A)
# >>> <bound method MyMachine.on_enter_A of <__main__.MyMachine object at ...>>

# the dynamically generated add_callback function
print(m.on_enter_B)
# >>> <functools.partial object at 0x10e56dc58>

# will call the previously defined method
m.on_enter_A()
# >>> entered A

# will call the dynamic add_callback method and pass function name
# 'hello' will now be called whenever B is entered
m.on_enter_B("hello")

# enter B
m.go()
# >>> hello

# enter A
m.back()
# >>> A entered

As you see on_enter_A is not overwritten during instantiation. The error must be caused by something else then. If you could provide further information about the issue or provide a minimal example I could investigate further.

Coming back to this and I can't replicate now. Much has changed, including my switch to using the LockedMachine as I was using timers. So I expect I was violating a lot of the rules of engagement.
Closing as I doubt I'll get time to dig further.
Thanks again for the excellent assistance.


vimc-4298 accomodate all possible orderly.server statuses

I've gone for treating all statuses other than "running" and "queued" as terminal ones, including "unknown" and anything else that isn't recognised. And interpreted "fail" to mean anything other than "success" - so a killed report is still a failed one.

Will also need to result in an incremented version number and re-publish, but presumably this will have to be done after the task q recognises the extra "timeout" argument merged in the previous PR.


Example with user-defined initial values

How does one define initial values per chain per parameter in MatlabStan? I could not find an example on the wiki. Defining initial values incorrectly causes an "Warning: Stan seems to have exited badly." error.

There currently isn't a way to set different initial values for each chain. This has been requested before, so I can have a look at adding this feature.
If you are having a problem setting initial values in general (not per chain), can you paste in an example?

I've updated the wiki to include examples on parameter initializations:
https://github.com/brian-lau/MatlabStan/wiki/Initializing-parameters

Thank you! This solves the initial problem of not having a wiki example.

Separate inits for each chain added with commit ef1666a1. Examples at the bottom of the wiki page here: https://github.com/brian-lau/MatlabStan/wiki/Initializing-parameters/_edit#different-inits-can-be-specified-for-each-chain


openssl list: add an empty row at the end of each printed list of com…

…mands and algorithms
Fixes openssl#19140
Newline at the end of every list indeed increases the readability. This solution uses a macro to decide whether  to print a newline or not. I think it is the easiest way to implement this change, but maybe it increases the coolness factor of the code too much.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Merged!


Fail to fetch error on blueprint planning.

Great util, glad I found it.
Today I've started receiving the following error:
TypeError: Failed to fetch
    at Ba.customFetch (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:27393)
    at Ba.request (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:28692)
    at Object.v1OilFieldPlanCreate (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:29879)
    at ka (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:31615)
    at Proxy.submit (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:77134)
    at https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:9:80365
    at https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:1:55309
    at mt (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:1:14052)
    at qe (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:1:14130)
    at HTMLButtonElement.n (https://factorio-tools.vercel.app/assets/index-9fb5e1c4.js:1:51894)

Associated blue print attached.
I'm dicking around in a sandbox game, and hand 'built' the oilfield with console commands. I've done this before and used the planner without issue, as well as with larger oilfields with more pumpjacks.
oilfield_bp.txt

Thanks for the heads up. I've fixed the bug. Give it a try!


"Feature_Color_network_drives_#11998"

Resolved / Related Issues

[ ] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #11998

Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Open app ...
Click settings button ...

Screenshots (optional)

Thank you for contributing, we still haven't decided to include this feature in Files. I'm closing this PR in the meantime, but we'll let you know if we decide to move forward with this feature. As a side note, you can check the issues status from the right pane.


Change load_balanced_fqdn

After a cluster is setup, is there a way to change the load_balanced_fqdn value?

We currently don't have a supported way of doing this. You may be able to call apply against the existing cluster using the --skip-preflight and --restart-services flags. Changing the load balanced FQDN will need regeneration of certificates, which is why forcing a restart of services is required.

I have a feeling this is causing some networking issues on my side. I wanted to check and see if this has come up since I put the ticket in, and how dangerous it could be to do this on an existing production cluster? cc @alexbrand @dkoshkin

@alexbrand Can you show me where the regeneration of certificates would need to be for this changing this variable? Looking for what certificates would need to be regenerated.

Can you elaborate on what you are seeing @WillPlatnick (symptoms, logs, etc)? Maybe we can help troubleshoot.
I don't think we have seen cases where users change the load balancer's FQDN after the cluster is deployed.

@alexbrand When we first set the cluster up, we didn't have a load balancer ready in front of the masters, so I just set it to be the fqdn of our first master server.
As far as the API is concerned, I have tried to work around this by setting up nginx in tcp mode and route requests to either master01 and master02. I then changed the dns for the load balanced fqdn (same as master01) to point to nginx. However, something about this doesn't seem to work well: when I turned off master01 by shutting down the ethernet interface, the kubelet on a worker also ended up going down. Later on, with master01 back up, I turned off master02's ethernet, and all the kubelets on all worker nodes also went NotReady. Lots of issues talking to the api server in the logs, even though the load balancer was doing its thing when asked. I have a feeling it's something related to my load balanced fqdn and master01 being the same, and wanted to setup a new fqdn so we can get out of the funkiness of this situation and hopefully fix API HA.
However, the bigger issue is that sometimes, when a master is down, network traffic is stopping to some degree within the pods and I can't figure out where and why it's happening. It seems like DNS traffic is definitely affected, but it may be all traffic going out of pods, I'm not sure.  Right now the only thing I can find in the logs of calico-node, kube-proxy, kubelet, etc... is that during these periods of time, there's tons of failed API requests.

@alexbrand @dkoshkin If I move to kismatic 1.6.1 and don't move over the generated dir and change the load_balanced_fqdn, will all the certs be regenerated as part of the upgrade?

Alternatively, can I create additional master nodes and then somehow delete the master node that was named master01?

There is no simple way to do this, if for some reason a new fqdn is required I would recommend reinstalling the cluster.


fix(python): dependency versioning in Python

Fix the generation of the dependency version strings for the install_requires section of setup.py.  Fixes #676.
The version string placed in the setup.py file for dependencies is incorrect.  This results in incompatible modules being installed.  This fix changes the generated version string for dependencies to correct the problem.
Fixes #696

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing this PR without merging. We can dig it up if we end up actually needing to go down that path.

@eladb @RomainMuller this not being merged causes https://github.com/aws/aws-cdk/issues/4957 to cascade into any of my libararies even if I pin them at 1.15.0 because
https://github.com/aws/jsii/blame/fe942b3f358335125f9f0800fc34ac06be93dcff/packages/jsii-pacmak/lib/targets/python.ts#L1096-L1100
is making an incorrect compatible release specification (https://www.python.org/dev/peps/pep-0440/#compatible-release)
aws-cdk.aws-cloudformation~=1.15,>=1.15.0 means >=1.5, ==1.* which then loads 1.16.0.

I think the reasoning is slightly different now however - the code generator generates a dependency statement that is NOT what was declared in the initial module!

@RomainMuller I can understand that concern
Regarding the python dependency itself keying off depInfo.version and exclusively using the ~=X.Y.Z only to keep minor versions from affecting downstream projects pinned at ~= X.Y.0

@RomainMuller just to be thorough. There is a explicit difference in the interpretation of versions that makes an incorrect compatibility presumption with regard to the current python implementation where ~=X.Y,>=X.Y.Z is being returned for the python version.
In npmjs tilde ranges the same ~=X.Y,>=X.Y.Z is equivalent to >=XY.0 <X.(Y+1).0 or >=X.Y.0 <X.(Y+1).0
In python compatible release ~=X.Y,>=X.Y.Z is the equivalent of  >= X.Y, == X.* which is not the same compatibility intention as the npm tilde range.
The change in this PR where the version is set to be exclusively as ~=X.Y.Z is valid and should be accepted to keep the two intended versions compatibility layer between the two package managers.
I wasn't sure if this difference was clear or not so please forgive me posting twice :)

So at risk of being completely redundant if the code was updated such that the python version uses depInfo.version the string still needs to be updated to be exclusively ~=X.Y.Z.


Add Wilmington Area School District

@calebtroyer Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


⚠ Bofrost.de has degraded performance

In 24d40fa, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 898 ms

Resolved: Bofrost.de performance has improved in e7b67cb after 7 minutes.


CupertinoSpinBox initialValue not resetting

Good day, I'm using 2 cupertinospinboxs. Both allow for individual "spins".  When the 1st spinner is set to 0 (zero), the 2nd widget is expected to be reset to 0 as well.  The underlaying data source is managed by Provider and ChangeNotifier.  I console print out the value of initialValue for both spinners and see that the initial build is correct for both initialValues. When the 1st spinner is set to 0, the console print shows the 2nd spinner's initialValue is the expected 0 value but the displayed value remains at the current value, ie not getting reset.
Not sure if this is an issue specific to your script so Im still researching for a solution but was hoping you may have a solution/correction or workaround.
Thank you for your time.

Could you help me to understand the problem by providing a short example snippet that illustrates the problem?

Thxs for getting back to me.  Hopefully below I’ve shown you what the issue is.
Initial value is properly set to “1"
Console log of the print statement showing the initalValue given to the spin box correctly, which is 1
Then when the spin box associated with the column “Caution” is set to zero (0) the initialValue for spin box under column “Time” should be 0 as well.  The value being based to the “Time” spin box is 0, as shown in the console log below, but the screen/UI never refreshes with the new value past to it.

On Dec 15, 2020, at 6:33 PM, J-P Nurmi<EMAIL_ADDRESS>wrote:
Could you help me to understand the problem by providing a short example snippet that illustrates the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jpnurmi/flutter_spinbox/issues/7#issuecomment-745633028, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABKLCSMCZIRNRF4IEMKYT3SU7W3TANCNFSM4U3ERTJQ.

Found a solution.  I added the Key parameter with a UniqueKey, to the widget holding the spinbox.  Now when the value is reset in the other widget, the results are as expected.

On Dec 15, 2020, at 6:33 PM, J-P Nurmi<EMAIL_ADDRESS>wrote:
Could you help me to understand the problem by providing a short example snippet that illustrates the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jpnurmi/flutter_spinbox/issues/7#issuecomment-745633028, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABKLCSMCZIRNRF4IEMKYT3SU7W3TANCNFSM4U3ERTJQ.

I'll take it that the problem was solved. Let me know if you think there's something that should be changed in flutter_spinbox.


TypeError: Cannot read property 'slice' of null

When building on Meteor <IP_ADDRESS> I hit the below error:
W20170423-15:12:38.332(1)? (STDERR) /Users/nzwade/.meteor/packages/meteor-tool/.1.4.4_1.1licv3w++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20170423-15:12:38.334(1)? (STDERR) 						throw(ex);
W20170423-15:12:38.334(1)? (STDERR) 						^
W20170423-15:12:38.334(1)? (STDERR)
W20170423-15:12:38.335(1)? (STDERR) TypeError: Cannot read property 'slice' of null
W20170423-15:12:38.335(1)? (STDERR)     at new Configuration (/Volumes/storage partition/dev/project/project/project_meteor/node_modules/node-celery/celery.js:52:64)
W20170423-15:12:38.336(1)? (STDERR)     at new Client (/Volumes/storage partition/dev/project/project/project_meteor/node_modules/node-celery/celery.js:205:17)
W20170423-15:12:38.337(1)? (STDERR)     at Object.exports.createClient (/Volumes/storage partition/dev/project/project/project_meteor/node_modules/node-celery/celery.js:403:12)
W20170423-15:12:38.338(1)? (STDERR)     at meteorInstall.project_meteor.js (project_meteor.js:460:18)
W20170423-15:12:38.338(1)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:197:9)
W20170423-15:12:38.339(1)? (STDERR)     at require (packages/modules-runtime.js:120:16)
W20170423-15:12:38.339(1)? (STDERR)     at /Volumes/storage partition/dev/project/project/project_meteor/.meteor/local/build/programs/server/app/app.js:1618:1
W20170423-15:12:38.340(1)? (STDERR)     at /Volumes/storage partition/dev/project/project/project_meteor/.meteor/local/build/programs/server/boot.js:303:34
W20170423-15:12:38.340(1)? (STDERR)     at Array.forEach (native)
W20170423-15:12:38.341(1)? (STDERR)     at Function._.each._.forEach (/Users/nzwade/.meteor/packages/meteor-tool/.1.4.4_1.1licv3w++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)

The code I have in Meteor to call node-celery is the same as the docs:
if (Meteor.isServer) {
var celery = require('node-celery'),
	client = celery.createClient({
		CELERY_BROKER_URL: 'amqp://guest:guest@localhost:5672//',
		CELERY_RESULT_BACKEND: 'amqp'
	});
...

It appears the error is triggered on line 52 of celery.js
    self.backend_type = url.parse(self.RESULT_BACKEND).protocol.slice(0, -1);
Why is this error happening despite specifying a RESULT_BACKEND when creating the client?
Thank you,

Getting the same error with Meteor <IP_ADDRESS>. http://stackoverflow.com/questions/43708795/using-meteor-with-node-celery-causes-error-cannot-read-property-slice-of-null

I'm getting the same error, and I'm not even using Meteor:
self.backend_type = url.parse(self.RESULT_BACKEND).protocol.slice(0, -1);
                                                               ^

TypeError: Cannot read property 'slice' of null

I had the same issue and I change the CELERY_RESULT_BACKEND option:
CELERY_RESULT_BACKEND: 'amqp://' and it works.

Fixed by https://github.com/mher/node-celery/pull/89

This problem still exists, the fix below still works

I had the same issue and I change the CELERY_RESULT_BACKEND option:
CELERY_RESULT_BACKEND: 'amqp://' and it works.


Add retry when there ssh connection timeout during image building

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/approve


chore: update README for clarity

Changelog

changes README to make some parts more readable
adds a note about the fsnotify strategy and it's use in projects

Thanks @pavanpej


Access denied

Duplicate of #2070.

@binarymaster bro what
my other one got closed for not enough information so i made a new one with more info


add inverted index of timeseries

Description
Add the inverted index of the timeseries to optimize the time series query for a small number of timelines. Similar to tsi.
Proposal
Build:
Option 1: Add index to memtable and build it when data is written.
Option 2: Build when memtable flushes to sst.
Storage:
Option 1: Store in parquet metadata.
Option 2: Store in separate file.

iox 已经去掉了 inverted index, 全靠 datafusion 执行引擎 table scan

In some scenes(like point query used in alerts), batch scan may be much more expensive compared to scaning/getting filterd rows with the inverted index.
And now inverted index feature is currently in the poc stage, and we will decide the next step based on specific performance tests.

iox 已经去掉了 inverted index, 全靠 datafusion 执行引擎 table scan

In some scenes(like point query used in alerts), batch scan may be much more expensive compared to scaning/getting filterd rows with the inverted index.
And now inverted index feature is currently in the poc stage, and we will decide the next step based on specific performance tests.

@chunshao90 Thank your reply,  I'm looking forward to this feature.

Duplicated with https://github.com/CeresDB/ceresdb/issues/628


Dynamic Functions

While Salesforce does not have first class treatment for functions, we can pass in objects which can simulate the same actions as objects.
For the "Function Functions" of Underscore.js, I had originally believed we could never actually accomplish the goal, but if we wrap the function in an interface, we could conceivably enable all function rules (Bind, Wrap, etc..) in Apex.
For example:
public abstract US_fn{
    SObject obj;
    Map<Object, Object> details;
    US_fn parent;

    public object execute() {
            // The function itself comes in here
    }
}

So the execute function could get a hold of "partially evaluated" items from the details map (which could be populated through the partial function), and wrapping could just involve populating the parent function field and writing the function with that in mind.
public class hello_world extends US_fn{
    public object execute() {
            system.debug('hello world');
    }
}

public class now_you_die extends US_fn{
    public object execute() {
            system.debug('what's up world');
            parent.execute()
            system.debug('goodbye world');
    }
}

hw = new hello_world();
nyd = new now_you_die();

USfn.wrap(hw, nyd).execute();

It isn't clear to me that this is actually valuable, except that it creates a baseline to extend functions and creates a way to build reusability into functions.   We should explore the idea.

Maybe we can use Type for this to improve value.
public class now_you_die extends US_fn {
    public object parent() {
        Type t = Type.forName(classname);
        parent = (US_fn) t.newInstance(obj, details);
    }

    public object execute() {
            system.debug('what's up world');
            parent.execute()
            system.debug('goodbye world');
    }
}

USfn.wrap('hello_world', 'now_you_die', sobj, partial).execute();

As for benefits, we could extract the logging functions from certain types of functions (get a before and after for a "push" function on an array.
public class now_you_die extends US_fn {
    public object parent() {
        Type t = Type.forName(classname);
        parent = (US_fn) t.newInstance(obj, details);
    }

    public object execute() {
            system.debug('what's up world');
            parent.execute()
            system.debug('goodbye world');
    }
}

USfn.wrap('hello_world', 'now_you_die');

public class push extends US_fn {
    public object execute() {
        details.get('array').add(obj);
        return details.get('array');
    }
}

public class logarray extends US_fn {
    public object execute() {
        system.debug(details.get('array'));
        Object o = parent.execute()
        system.debug(o);
        return o;
    }
}

USfn x = USfn.wrap('push', 'logarray')

x.execute(an_sobject, null);  // maybe we should let them pass in information?

I still don't see the benefit vs.
List xyz;
xyz.add(whatever);
system.debug(xyz);


Hot Fix for missing setSubject() method in Sharing builder

Adding missing builder method to set subject for email/sms share
@aaustin @shortstuffsushi

:+1:


Class structure for needs

This issue shall serve as a placeholder for discussions around a UML-like class structure of need types and their fields.
I'm using needs to support and tailor the implementation of the information security management systems TISAX + ISO27001 in our company. This brings already huge value as I have all TISAX requirements defined as needs and can track the fulfillment of the standard on code level using Sphinx. This turns Git+Sphinx into a full blown documentation management / requirement management / risk management / asset management solution. Thanks for this.
In my scenario, I defined a UML class structure for the need items I want to describe using Plantuml.
Beyond others, it contains the classes Asset, Control and Risk with different properties:
class "Control\n(Action, Measure)" as control {
}

Class "Asset" as asset {
  -- One of the following types --
  $txt IT hardware
  $txt IT application
  $txt IT infrastructure
  $txt information electronic
  $txt information physical
  $txt persons keeping secrets
  $txt external services [e.g. cloud]
  --
  $person owner
  $enum protection category\n    [normal, high, very high]
  $enum life cycle status\n    [create, process, stored, deleted]
  $txt[] acceptable use policy
  $txt group\n    [infrastructure, workplace, int, ext]
  $txt usage approval
  $help handling support [tools, methods]
  $key encryption
}

Class "Risk" as risk {
  $txt owner
  $txt[] causes
  $txt[] impacts
  $enum probability [low, normal, high]
  $txt[] impacts_handling
  $txt[] acceptance_criteria
}

The only option in needs to model the class/field structure is to define a need directive for each class and define global fields using needs_extra_options that can theoretically be used on every need.  Also I can create link types using needs_extra_links to define meaningful link names.
The problem I have is that every field and link is global and I will probably have dozens of field names over the whole definition. I will quickly lose overview which field is allowed/required/constrained on which class.
I'm proposing to make extra options and link types specific to needs directives.
Together with the constraint checking in issue #110, this would be a killer feature for me.
I'd like to get your opinions on this.

Maybe #110 is already enough for this.
Just define a constraint, which defines not allowed usages of a field for a specific need-type.
E.g. "type == 'risk' and encryption is not None or encryption != '' " .
I think the common case is that extra_options shall be available for all need-types.
So I would like to not complicate the extra_options registration process for this case.
If more is needed, then an extra configuration option / way shall be used.
In this case #110.

Thanks for the implementation proposal. That sounds like a solution.
Will this provide the option to hide fields per need-type because there is only one global option needs_hide_options. If fields are not set, they are never displayed, right?

Hidding values can be done by #102, so a specific layout is configured/used for a specific need type.
But it is not available yet....


CZML examples in documentation

Would it make sense to add CZML snippets to each object and complete examples that demonstrate the important features?

Do we want to close this given the upcoming CZML examples in #3027?

Closing as duplicate with #3027.  Once the examples ship with Cesium 1.15, we will add a link to them from the CZML Guide.


panic: re-export alias

Describe the bug
When trying to compile a file with a re-export, as of release 1.2.130, this is broken.
Input code
// index.ts
export * as get from "./get";

// get/index.ts

export const byID = (id: string): Promise<string> => {
  // Do some async stuff
  return new Promise((resolve) =>
    setTimeout(() => {
      resolve("result");
    }, 2000)
  );
};

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "dynamicImport": true
    },
    "transform": {
      "legacyDecorator": true,
      "decoratorMetadata": true
    },
    "target": "es2020",
    "keepClassNames": true,
    "loose": true
  },
  "module": {
    "type": "commonjs",
    "strict": true,
    "strictMode": true,
    "lazy": false,
    "noInterop": true
  },
  "sourceMaps": true,
  "exclude": ["node_modules/.*", ".*/node_modules", "dist", ".*.spec.ts"]
}

Playground link
No response
Expected behavior
Should have compiled.
Actual behavior
No response
Version

1.2.130

Additional context
No response

Related: https://github.com/swc-project/swc/issues/1307


Make privacy-related claims more robust and accurate

Tl;dr

[ ] Stop referring to Grin as 'private', in favour of something less definitive-sounding.
[ ] Link to the contents of the Privacy primer to the website to make it clearer what Grin can, and cannot do.

Background
Feedback from Ian Miers (edited for clarity, emphasis mine):

[It's] interesting to compare the privacy claims on [grin-tech.org] and the ones in the Privacy primer. Perhaps [I'm misinterpreting] the intent behind the [primer], but it struck me that it provided a nuanced discussion of how grin improved privacy and how it didn't. It doesn't, for example protect against merchants tracking customers or governments identifying people who wish to receive funds anonymously. It did the right thing, instead of just bluster or claiming "we knew about these issues, why are you bringing them up". In contrast, [grin-tech.org] just says grin is private. With no point about what it doesn't hide, [or] why that might matter. Hard to do in a short blurb. Maybe just say "grin offers better privacy than Bitcoin?"
Given the lack of transaction graph hiding and how that exposes people to both tracking and identification attacks, I wouldn't make [the claim that Grin is privacy-preserving].  As I said I'm not sure what to say, I don't know who wrote the [privacy primer] but they but some thought into it.  Maybe they have an idea?

It makes sense to me to stop sounding so definitive on our web content and make claims to be 'private', as that might be a too bold of a statement. It also makes sense to link to the privacy primer from the website.
Thoughts?

https://github.com/mimblewimble/site/pull/149 now have us described as "privacy preserving", which I believe is good enough for now.


typo in document

there is a typo in text "precendence" at https://reacttraining.com/react-router/web/api/Route/Route-render-methods. hope to correct it with "precedence" :)

You can submit a PR for this! 😄
Go here and click the pencil in the top right: https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/Route.md


UI - Implement build status spinner

Now that we have the build results back in the dev, we should try to integrate it with the spinner in the UI correctly to signify when a build is done. @JonathanRosado @AndreeaDora @soninob

It works! thanks @JonathanRosado and @AndreeaDora.


Warnings with -Wfloat-equal

  CXX      ../../src/AvstpWrapper.lo
  CXX      ../../src/main.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ../../src/fmtc/Matrix.h:33,
                 from ../../src/main.cpp:22:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
  CXX      ../../src/fmtc/Bitdepth.lo
../../src/fmtc/Bitdepth.cpp: In member function ‘void fmtc::Bitdepth::init_fnc_ordered()’:
../../src/fmtc/Bitdepth.cpp:829:47: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  const bool           simple_flag = (_ampo == 1 && _ampn == 0);
                                               ^
../../src/fmtc/Bitdepth.cpp:829:61: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  const bool           simple_flag = (_ampo == 1 && _ampn == 0);
                                                             ^
../../src/fmtc/Bitdepth.cpp: In member function ‘void fmtc::Bitdepth::init_fnc_errdiff()’:
../../src/fmtc/Bitdepth.cpp:865:47: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  const bool           simple_flag = (_ampo == 1 && _ampn == 0);
                                               ^
../../src/fmtc/Bitdepth.cpp:865:61: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  const bool           simple_flag = (_ampo == 1 && _ampn == 0);
                                                             ^
../../src/fmtc/Bitdepth.cpp: In member function ‘void fmtc::Bitdepth::dither_plane(fmtcl::SplFmt, int, uint8_t*, int, fmtcl::SplFmt, int, const uint8_t*, int, int, int, const fmtcl::BitBltConv::ScaleInfo&, const int16_t (&)[32][32], uint32_t)’:
../../src/fmtc/Bitdepth.cpp:958:69: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    || scale_info._gain * ((uint64_t (1)) << (src_res - dst_res)) != 1
                                                                     ^
../../src/fmtc/Bitdepth.cpp:959:30: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    || scale_info._add_cst != 0);
                              ^
  CXX      ../../src/fmtc/Convert.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ./../../src/fmtc/Matrix.h:33,
                 from ../../src/fmtc/Convert.cpp:32:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
  CXX      ../../src/fmtc/ConvStep.lo
  CXX      ../../src/fmtc/fnc.lo
  CXX      ../../src/fmtc/Matrix2020CL.lo
  CXX      ../../src/fmtc/Matrix.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ./../../src/fmtc/Matrix.h:33,
                 from ../../src/fmtc/Matrix.cpp:34:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/cassert:43:0,
                 from ../../src/fmtc/Matrix.cpp:44:
../../src/fmtc/Matrix.cpp: In static member function ‘static void fmtc::Matrix::make_mat_yuv(fmtcl::Mat4&, double, double, double, bool)’:
../../src/fmtc/Matrix.cpp:766:16: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (kg != 0);
                ^
../../src/fmtc/Matrix.cpp:767:16: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (kb != 1);
                ^
../../src/fmtc/Matrix.cpp:768:16: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (kr != 1);
                ^
  CXX      ../../src/fmtc/NativeToStack16.lo
  CXX      ../../src/fmtc/Resample.lo
../../src/fmtc/Resample.cpp: In constructor ‘fmtc::Resample::Resample(const VSMap&, VSMap&, void*, VSCore&, const VSAPI&)’:
../../src/fmtc/Resample.cpp:308:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (s._w == 0)
               ^
../../src/fmtc/Resample.cpp:321:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (s._h == 0)
               ^
../../src/fmtc/Resample.cpp:379:37: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (plane_data._kernel_scale_h == 0)
                                     ^
../../src/fmtc/Resample.cpp:383:37: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (plane_data._kernel_scale_v == 0)
                                     ^
  CXX      ../../src/fmtc/Stack16ToNative.lo
  CXX      ../../src/fmtc/Transfer.lo
../../src/fmtc/Transfer.cpp: In member function ‘void fmtc::Transfer::init_table()’:
../../src/fmtc/Transfer.cpp:412:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  if (_gcor != 1)
               ^
../../src/fmtc/Transfer.cpp:419:19: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  if (_contrast != 1)
                   ^
  CXX      ../../src/fmtcl/ArrayMultiType.lo
  CXX      ../../src/fmtcl/BitBltConv.lo
../../src/fmtcl/BitBltConv.cpp: In member function ‘void fmtcl::BitBltConv::bitblt_int_to_flt(uint8_t*, int, fmtcl::SplFmt, int, const uint8_t*, const uint8_t*, int, int, int, const fmtcl::BitBltConv::ScaleInfo*)’:
../../src/fmtcl/BitBltConv.cpp:225:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    && (   scale_info_ptr->_gain    != 1
                                       ^
../../src/fmtcl/BitBltConv.cpp:226:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
        || scale_info_ptr->_add_cst != 0));
                                       ^
../../src/fmtcl/BitBltConv.cpp: In static member function ‘static bool fmtcl::BitBltConv::is_si_neutral(const fmtcl::BitBltConv::ScaleInfo*)’:
../../src/fmtcl/BitBltConv.cpp:821:45: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
          || (   scale_info_ptr->_gain    == 1
                                             ^
../../src/fmtcl/BitBltConv.cpp:822:45: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
              && scale_info_ptr->_add_cst == 0));
                                             ^
  CXX      ../../src/fmtcl/ChromaPlacement.lo
  CXX      ../../src/fmtcl/CoefArrInt.lo
  CXX      ../../src/fmtcl/ContFirBlackman.lo
  CXX      ../../src/fmtcl/ContFirBlackmanMinLobe.lo
  CXX      ../../src/fmtcl/ContFirCubic.lo
  CXX      ../../src/fmtcl/ContFirFromDiscrete.lo
  CXX      ../../src/fmtcl/ContFirGauss.lo
  CXX      ../../src/fmtcl/ContFirInterface.lo
  CXX      ../../src/fmtcl/ContFirLanczos.lo
  CXX      ../../src/fmtcl/ContFirLinear.lo
  CXX      ../../src/fmtcl/ContFirRect.lo
  CXX      ../../src/fmtcl/ContFirSinc.lo
  CXX      ../../src/fmtcl/ContFirSnh.lo
  CXX      ../../src/fmtcl/ContFirSpline16.lo
  CXX      ../../src/fmtcl/ContFirSpline36.lo
  CXX      ../../src/fmtcl/ContFirSpline64.lo
  CXX      ../../src/fmtcl/ContFirSpline.lo
  CXX      ../../src/fmtcl/DiscreteFirCustom.lo
../../src/fmtcl/DiscreteFirCustom.cpp: In member function ‘int fmtcl::DiscreteFirCustom::compute_real_support() const’:
../../src/fmtcl/DiscreteFirCustom.cpp:76:41: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  ; pos < half_len && _coef_arr [pos] == 0 && _coef_arr [len - 1 - pos] == 0
                                         ^
../../src/fmtcl/DiscreteFirCustom.cpp:76:75: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  ; pos < half_len && _coef_arr [pos] == 0 && _coef_arr [len - 1 - pos] == 0
                                                                           ^
  CXX      ../../src/fmtcl/DiscreteFirInterface.lo
  CXX      ../../src/fmtcl/ErrDifBuf.lo
  CXX      ../../src/fmtcl/ErrDifBufFactory.lo
  CXX      ../../src/fmtcl/FilterResize.lo
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/cassert:43:0,
                 from ../../src/fmtcl/FilterResize.cpp:47:
../../src/fmtcl/FilterResize.cpp: In constructor ‘fmtcl::FilterResize::FilterResize(const fmtcl::ResampleSpecPlane&, fmtcl::ContFirInterface&, fmtcl::ContFirInterface&, bool, double, double, double, fmtcl::SplFmt, int, fmtcl::SplFmt, int, bool, bool, bool)’:
../../src/fmtcl/FilterResize.cpp:107:34: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (spec._kernel_scale_h != 0);
                                  ^
../../src/fmtcl/FilterResize.cpp:108:34: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (spec._kernel_scale_v != 0);
                                  ^
../../src/fmtcl/FilterResize.cpp:111:18: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (gain != 0);
                  ^
../../src/fmtcl/FilterResize.cpp:150:42: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
      || _win_size [dir] != _dst_size [dir]
                                          ^
../../src/fmtcl/FilterResize.cpp:151:32: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
      || _kernel_scale [dir] != 1.0
                                ^
../../src/fmtcl/FilterResize.cpp:153:52: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    || _center_pos_src [dir] != _center_pos_dst [dir]
                                                    ^
  CXX      ../../src/fmtcl/fnc.lo
  CXX      ../../src/fmtcl/KernelData.lo
  CXX      ../../src/fmtcl/Matrix2020CLProc.lo
  CXX      ../../src/fmtcl/MatrixProc.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ../../src/fmtcl/MatrixProc.cpp:34:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
  CXX      ../../src/fmtcl/ResampleSpecPlane.lo
  CXX      ../../src/fmtcl/ResizeData.lo
  CXX      ../../src/fmtcl/ResizeDataFactory.lo
  CXX      ../../src/fmtcl/Scaler.lo
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/cassert:43:0,
                 from ../../src/fmtcl/Scaler.cpp:45:
../../src/fmtcl/Scaler.cpp: In constructor ‘fmtcl::Scaler::Scaler(int, int, double, double, fmtcl::ContFirInterface&, double, bool, double, double, double, double, double, bool, bool, bool)’:
../../src/fmtcl/Scaler.cpp:132:18: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (gain != 0);
                  ^
../../src/fmtcl/Scaler.cpp: In member function ‘void fmtcl::Scaler::build_scale_data()’:
../../src/fmtcl/Scaler.cpp:832:17: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    assert (n != 0);
                 ^
../../src/fmtcl/Scaler.cpp:871:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (accu != 0 || info._kernel_size == 0)
               ^
  CXX      ../../src/fmtcl/TransLut.lo
  CXX      ../../src/fmtcl/TransOp2084.lo
  CXX      ../../src/fmtcl/TransOpAffine.lo
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/cassert:43:0,
                 from ../../src/fmtcl/TransOpAffine.cpp:29:
../../src/fmtcl/TransOpAffine.cpp: In constructor ‘fmtcl::TransOpAffine::TransOpAffine(double, double)’:
../../src/fmtcl/TransOpAffine.cpp:46:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
  assert (a != 0);
               ^
  CXX      ../../src/fmtcl/TransOpCanonLog.lo
  CXX      ../../src/fmtcl/TransOpFilmStream.lo
  CXX      ../../src/fmtcl/TransOpLinPow.lo
../../src/fmtcl/TransOpLinPow.cpp: In member function ‘virtual double fmtcl::TransOpLinPow::operator()(double) const’:
../../src/fmtcl/TransOpLinPow.cpp:91:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    if (_p2 == 1)
               ^
../../src/fmtcl/TransOpLinPow.cpp:119:15: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    if (_p2 == 1)
               ^
  CXX      ../../src/fmtcl/TransOpLogC.lo
  CXX      ../../src/fmtcl/TransOpLogTrunc.lo
  CXX      ../../src/fmtcl/TransOpPow.lo
  CXX      ../../src/fmtcl/TransOpSLog.lo
  CXX      ../../src/fmtcl/VoidAndCluster.lo
  CXX      ../../src/fstb/CpuId.lo
  CXX      ../../src/fstb/fnc.lo
  CXX      ../../src/fstb/ToolsSse2.lo
  CXX      ../../src/vsutl/CpuOpt.lo
  CXX      ../../src/vsutl/FilterBase.lo
  CXX      ../../src/vsutl/fnc.lo
  CXX      ../../src/vsutl/PlaneProcCbInterface.lo
  CXX      ../../src/vsutl/PlaneProcessor.lo
../../src/vsutl/PlaneProcessor.cpp: In member function ‘void vsutl::PlaneProcessor::set_filter(const VSMap&, VSMap&, const VSVideoInfo&, bool, int, const char*, const char*)’:
../../src/vsutl/PlaneProcessor.cpp:154:47: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
      else if (_proc_mode_arr [plane_index] == PlaneProcMode_PROCESS)
                                               ^
../../src/vsutl/PlaneProcessor.cpp: In member function ‘int vsutl::PlaneProcessor::process_frame(VSFrameRef&, int, void*, VSFrameContext&, VSCore&, vsutl::NodeRefSPtr, vsutl::NodeRefSPtr, vsutl::NodeRefSPtr)’:
../../src/vsutl/PlaneProcessor.cpp:271:31: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
   if (_manual_flag || mode == PlaneProcMode_PROCESS)
                               ^
../../src/vsutl/PlaneProcessor.cpp:288:16: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
       (mode == PlaneProcMode_COPY3) ? src_node3_sptr
                ^
../../src/vsutl/PlaneProcessor.cpp:289:16: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
     : (mode == PlaneProcMode_COPY2) ? src_node2_sptr
                ^
  CXX      ../../src/fmtcl/libavx_la-MatrixProc_avx.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ../../src/fmtcl/MatrixProc_avx.cpp:34:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
  CXXLD    libavx.la
  CXX      ../../src/fmtcl/libavx2_la-BitBltConv_avx2.lo
../../src/fmtcl/BitBltConv_avx2.cpp: In member function ‘void fmtcl::BitBltConv::bitblt_int_to_flt_avx2_switch(uint8_t*, int, fmtcl::SplFmt, int, const uint8_t*, const uint8_t*, int, int, int, const fmtcl::BitBltConv::ScaleInfo*)’:
../../src/fmtcl/BitBltConv_avx2.cpp:67:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    && (   scale_info_ptr->_gain    != 1
                                       ^
../../src/fmtcl/BitBltConv_avx2.cpp:68:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
        || scale_info_ptr->_add_cst != 0));
                                       ^
../../src/fmtcl/BitBltConv_avx2.cpp: In member function ‘void fmtcl::BitBltConv::bitblt_flt_to_int_avx2_switch(fmtcl::SplFmt, int, uint8_t*, uint8_t*, int, const uint8_t*, int, int, int, const fmtcl::BitBltConv::ScaleInfo*)’:
../../src/fmtcl/BitBltConv_avx2.cpp:114:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    && (   scale_info_ptr->_gain    != 1
                                       ^
../../src/fmtcl/BitBltConv_avx2.cpp:115:39: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
        || scale_info_ptr->_add_cst != 0));
                                       ^
  CXX      ../../src/fmtcl/libavx2_la-MatrixProc_avx2.lo
In file included from ./../../src/fmtcl/Mat4.h:118:0,
                 from ./../../src/fmtcl/MatrixProc.h:32,
                 from ../../src/fmtcl/MatrixProc_avx2.cpp:35:
./../../src/fmtcl/Mat4.hpp: In member function ‘bool fmtcl::Mat4::operator==(const fmtcl::Mat4&) const’:
./../../src/fmtcl/Mat4.hpp:115:50: warning: comparing floating point with == or != is unsafe [-Wfloat-equal]
    eq_flag = (_data [y] [x] == other._data [y] [x]);
                                                  ^
  CXX      ../../src/fmtcl/libavx2_la-Scaler_avx2.lo
  CXX      ../../src/fmtcl/libavx2_la-TransLut_avx2.lo
  CXX      ../../src/fstb/libavx2_la-ToolsAvx2.lo
  CXXLD    libavx2.la
  CXXLD    libfmtconv.la

There are also plenty of good reasons to compare float with exactness, so you should disable this warning.


data: yashpreet2707

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thanks a lot @khushalarora, I've made the desired change.

@khushalarora, if it is correct now, can you please merge it?

Hey @yashpreet2707, I don't have the access to merge pull requests.
Please wait for another maintainer to merge this pull request :+1:


Cassandra not responding & docker-compose not working

Cassandra seems to not be starting properly.  It also cannot be shutdown unless the VM is restarted :(
OS: OS X 10.11.3
Docker Version: 1.9.1
I also was trying to get a docker-compose.yml file working to start in a single command here is what I have so far:
cassandra:
  container_name: cassandra
  image: yep1/usergrid-cassandra
  volumes:
    - ./cassandra-data:/var/lib/cassandra
elasticsearch:
  container_name: elasticsearch
  image: yep1/usergrid-elasticsearch
  volumes:
    - ./elasticsearch-data:/data
usergrid:
  container_name: usergrid
  image: yep1/usergrid
  ports:
    - "8080:8080"
  environment:
    - ADMIN_PASS=password
    - ORG_NAME=org
    - APP_NAME=app
    - ADMIN_USER=admin
    -<EMAIL_ADDRESS>  links:
    - elasticsearch
    - cassandra
portal:
  container_name: portal
  image: yep1/usergrid-portal
  ports:
    - "80:80"
  environment:
    - USERGRID_HOST=usergrid:8080
  links:
    - usergrid

USERGRID_HOST doesn't seem to work with the link

Yes, USERGRID_HOST does not work with the link. The usergrid portal, written in javascript, has to know how to reach the usergrid API. The portal contains a config.js file in its root path to define the usegrid API endpoint. On container startup, the contents of the USERGRID_HOST variable is put there.
That means you have to pass the public reachable IP of the machine the usergrid container is running on as USERGRID_HOST.
The following docker-compose yaml works for me:
cassandra:
  container_name: cassandra
  image: yep1/usergrid-cassandra
  volumes:
    - ./cassandra-data:/var/lib/cassandra
elasticsearch:
  container_name: elasticsearch
  image: yep1/usergrid-elasticsearch
  volumes:
    - ./elasticsearch-data:/data
usergrid:
  container_name: usergrid
  image: yep1/usergrid
  ports:
    - "8080:8080"
  environment:
    - ORG_NAME=org
    - APP_NAME=app
    - ADMIN_USER=admin
    - ADMIN_PASS=password
    -<EMAIL_ADDRESS>  links:
    - elasticsearch
    - cassandra
portal:
  container_name: portal
  image: yep1/usergrid-portal
  ports:
    - "80:80"
  environment:
    - USERGRID_HOST=public_reachable_ip_of_docker_host_goes_here:8080

There was also a problem with usergrid container stopping immediately, fixed in https://github.com/yep/usergrid-docker/commit/cb7b5ab2a148b26aa700dda7d81cb97af9d4caa9

Hi,
I tried using your docker-compose file but keep on getting the below error:
cassandra.connection.CassandraHostRetryService.verifyConnection(217)<Hector.me.prettyprint.cassandra.connection.CassandraHostRetryService-1>- Downed :(:):9160 host still appears to be down: Unable to open transport to :(:):9160 , java.net.UnknownHostException: :
usergrid         | +++ waiting for cassandra being available to usergrid
My docker-compose.yml is:
version: '2'
services:
cassandra:
container_name: cassandra
image: yep1/usergrid-cassandra:14.04
volumes:
- ./cassandra-data:/var/lib/cassandra
elasticsearch:
container_name: elasticsearch
image: yep1/usergrid-elasticsearch:14.04
volumes:
- ./elasticsearch-data:/data
usergrid:
container_name: usergrid
image: yep1/usergrid
ports:
- "8080:8080"
environment:
- ORG_NAME=org
- APP_NAME=app
- ADMIN_USER=admin
- ADMIN_PASS=password
-<EMAIL_ADDRESS>links:
- elasticsearch
- cassandra
portal:
container_name: portal
image: yep1/usergrid-portal
ports:
- "80:80"
environment:
- USERGRID_HOST=<IP_ADDRESS>:8080

Same issue from my side...
@SinghPrakash0206 did you fix it?


Using Angular CDK overlay

Hi Saeed,
First of all, thank you for this awesome library. Don't know what i would have done without it.
I was wondering if you could maybe use Angular overlay to make this datepicker open on top of other elements instead of just pushing them down.
Like the behavior that Angular material datepicker currently has.
It just opens on top of other elements on the page.
Thank you so much in advance.
Keep up the good work :)

Hi, Sorry for late reply, i'm very busy nowadays ..!
Maybe you can implement it manually? :
https://material.angular.io/cdk/overlay/overview


ISV-4799: update vault preflight-decryption-key-pub

(related to recent CI security breach)

@Allda PTAL

@mporrato PTAL

@Allda updated