SDC: Add progress bar for paginated questionnaire

Is your feature request related to a problem? Please describe.
Feature request from Ona. https://github.com/opensrp/fhircore/issues/1384
Problem: users don't know how far along they are when completing a multi-page questionnaire
Describe the solution you'd like
A visual progress bar at the top of the questionnaire. Use determinate indicators. Material design Implementation guide here
Describe alternatives you've considered
We could also do "1 of 13" in text only. I think this is less useful than a visual progress bar.
Screenshot

Would you like to work on the issue?
Yes, I'll add designs

related to #1539

Move forward with visual progress bar and also make progress bar track scroll progress on a single page questionnaire.

@nsabale7 , would you like to work in this fix?

@nsabale7 , would you like to work on this fix?

Sure @Tarun-Bhardwaj, I can take this

Question: do we want to add page 1 of 3 next to next/back buttons on a paginated.


Flask error handling removes error transactions from APM

Describe the bug:
I'm running a Python Flask application and connected it to APM. However, I've noticed that when I add an error handler to my application as below, APM will see the error without providing a stack trace.
    def handle_anything(error):
        try:
            status_code = error.status_code
        except AttributeError:
            status_code = 500
        response_dict = {"type": str(type(error)), "exception_message": str(error)}
        app.logger.exception(response_dict, status_code=status_code)
        response = jsonify(error=response_dict)
        response.content_type = "application/json"
        response.status_code = status_code
        return response

Without this error handling, the trace appears as expected. Screenshots and further description are provided in https://discuss.elastic.co/t/flask-error-handling-removes-error-transactions-from-apm/281725/3. In that thread Colton suggested it might be a bug, and to report it here.
Environment (please complete the following information)

OS: Linux
Python version: 3.7.7
Framework and version [e.g. Django 2.1]: Flask 1.1.2
APM Server version: 7.11.0
Agent version: 6.3.3

Additional context
Add any other context about the problem here.

Agent config options

Click to expand
    from elasticapm.contrib.flask import ElasticAPM
    from flask_sqlalchemy import SQLAlchemy
    app = Flask(__name__)

    app.config['ELASTIC_APM'] = {
        'SERVICE_NAME': web_config.apm_server_name,
        'SERVER_URL': f"http://{web_config.apm_server_url}:{web_config.apm_port}",
        'ENVIRONMENT': 'development'
    }
    ElasticAPM(app)
    DB = SQLAlchemy()
    DB.init_app(app)

requirements.txt:

Click to expand
'flask',
'flask_cors',
'Flask-SQLAlchemy',
'elastic-apm[flask]',
'pymysql',  # install MySQLdb/mysqlclient for more performance
'python-logstash-async',
'sqlalchemy==1.3',

Ah, ok, I think I've figured this out. Our flask integration only captures unhandled exceptions. By installing an error handler which handles Exception, you've ensured that there will be no unhandled exceptions.
The reason it still shows in the error graph is because we're setting the transaction outcome to a failure (due to the 500 status code).
If you also want the stacktrace in these cases, you need to call elasticapm.capture_exception (assuming you named your ElasticAPM object elasticapm):
@app.errorhandler(Exception)
    def handle_anything(error):
        elasticapm.capture_exception(exc_info=(type(error), error, error.__traceback__))
        try:
            status_code = error.status_code
        except AttributeError:
            status_code = 500
        response_dict = {"type": str(type(error)), "exception_message": str(error)}
        app.logger.exception(response_dict, status_code=status_code)
        response = jsonify(error=response_dict)
        response.content_type = "application/json"
        response.status_code = status_code
        return response

Keep me posted if you have any issues with that!

Interesting, I assumed the status code was the source of truth for errors. I'll see if I can manually capture exceptions, thanks!

It is, but you can have a 500 status code without actually throwing an exception (and thus stack trace). Once you've handled the exception you need to manually collect it if you want to treat it as an error -- many handled exceptions don't result in errors, after all!

Gotcha, that was what I was wondering - if I could manually ship the trace to APM. Looks like your suggestion worked! Thanks for the help


Get company goals

get company goals tab this resolves issues #349

@Asylcreek I have fixed thw conflict please check

There still is a conflict in the Home.jsx file

I dont even know what to do again. please what is the conflict?  @Asylcreek

Just go to the team's repo on Github. Find client/src/pages/Home.jsx. Copy the files, paste it in your local client/src/pages/Home.jsx. Then make the PR again

so I should close this one?

I don't think you have to. Just make the changes and push again

@Asylcreek  please check now

@Asylcreek there are currently no conflicts

He requested a change in file main.yml. You're yet to do so

He requested a change in file main.yml. You're yet to do so

Sorry what are you talking about, the main.yml file is exactly what is on the staging branch like it was copy and paste @abiona01

@abiona01 please check o. There are no conflicts  currently..

please @abiona01  and @Asylcreek  I  want to draw your attention to the source of the conflict in the main.yml file, it is caused by the improper alignment on the part of the staging file..... where we have
#    push
#        branches

all the while I thought I was doing rubbish but the fact is that for every new PR that you merge, it automatically raises conflicts in everyones else PR because ofcourse they are no longer in sync with the staging branch again.

@abiona01 @Asylcreek  please check

this PR resolves issue #349
the test link is right here


Can't install validators via pnpm

Describe the bug
When installing any of the following packages I get an error which prevents the packages being installed. This isn't happening with any other package to must be localised to felte.
EPERM  EPERM: operation not permitted, copyfile 'C:\Users\WayA\.pnpm-store\v3\files\29\4324b67c264be431302ecd00b302ae033132aa3233377e001fc1347c8a245bf8f97bf867e160639e313d3c7606258e87dd495d7bcb6ddcb2b2b1dc8101cf39-exec' -> 'C:\code\lyra-donations-platform\node_modules\.pnpm\@felte+validator-superstruct@1.0.5_superstruct@0.15.4\node_modules\@felte\_tmp_2640_ddc853a480ae5a57def68d01453f40eb\.turbo\turbo-test:ci.log'

Which package/s are you using?
@felte/validator-yup, @felte/validator-zod, @felte/validator-superstruct
Environment

OS: Windows 10
Browser: N/A
Version: N/A

To reproduce
Run pnpm add @felte/validator-superstruct
Small reproduction example
No response
Screenshots
No response
Additional context
No response

I don't have a Windows machine to test on. Is this only happening with ppm? Do other package managers work as expected? This might give me a good starting point to check this.

I've just installed one of the packages successfully via npm install @felte/validator-superstruct .
I also did a complete nuke of my node_modules both in my repository and also globally but it seems that the issue is still present.
Happy to run any commands if you need further info and thanks for getting back to me so quickly 😄

Can you try the latest patch I published? I saw the error happens when trying to copy a file that does not need to be published, so I just excluded it.

FIxed! Happy for this one to be closed!

Perfect, then! I'll be closing this. Thanks for submitting your issue!


Remove legacy rich text image styles

The <div class="rich-text"> wrapper around rich text was disabled by default in Wagtail 2.10 (https://docs.wagtail.io/en/stable/releases/2.10.html#div-class-rich-text-wrappers-removed-from-rich-text) and we'd prefer not to enable the legacy handler, to encourage Wagtail developers to follow current best practice.
There is already a width: 100% rule in place for all img elements, and since an image with width: 100% but no height: auto would render with the wrong aspect ratio, it's reasonable to assume that no images on the site rely on height: auto being absent. Adding this to the img rule therefore makes the rich-text rule redundant.
The width: 100% also meant that the left/right-alignment options for rich text images had no effect - we add a width: 50% to those to make them meaningful again.
Finally, the responsive-object wrapper for media embeds was dropped in 2.9, so those rules are unused since then. Anyone who feels strongly about restoring responsive embeds is welcome to contribute a PR :-)

This all looks sane and works locally for me. 👍

Merged via 2e3b59c8c454ecf83d9072359ab99c0e7c78184b


release.sh on failure

I want to pull requests, but ci is failed,I tried many times.  When i don't make any changes, still so.
errors:
2019/07/09 10:15:05 info: web.go:220: bosun web listening http on: :8070
validate.sh: line 79: kill: SIGTERM: invalid signal specification
2019/07/09 10:15:35 info: main.go:296: Interrupt: closing down...
2019/07/09 10:15:35 info: main.go:298: done
Failed to signal bosun to stop cleanly. Likely crashed before signal sent.
Failed to stop bosun cleanly. Exit code 124 (124=60s test timeout reached)

@AlekSi Can you help me. I want to apply for a pr that is #2424

The failure looks like the test that starts up bosun and shuts it down. My
guess is something you did in the close routine stopped bosun from cleanly
exiting on time.
On Thu, Jul 11, 2019, 2:22 AM ZhiFeiZhang<EMAIL_ADDRESS>wrote:

@AlekSi https://github.com/AlekSi Can you help me. I want to apply for
a pr that is #2424 https://github.com/bosun-monitor/bosun/pull/2424
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bosun-monitor/bosun/issues/2420?email_source=notifications&email_token=AABPAHE6VTOIDEPNEMKTNULP63GQTA5CNFSM4H7A5732YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZVULJQ#issuecomment-510346662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABPAHBJ25MHP3XJCSPGS5LP63GQTANCNFSM4H7A573Q
.

You can leave your pr open. We are behind on reviews at the moment, but
will take a look when we can.
On Thu, Jul 11, 2019, 2:23 AM Craig Peterson<EMAIL_ADDRESS>wrote:

The failure looks like the test that starts up bosun and shuts it down. My
guess is something you did in the close routine stopped bosun from cleanly
exiting on time.
On Thu, Jul 11, 2019, 2:22 AM ZhiFeiZhang<EMAIL_ADDRESS>wrote:

@AlekSi https://github.com/AlekSi Can you help me. I want to apply for
a pr that is #2424 https://github.com/bosun-monitor/bosun/pull/2424
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bosun-monitor/bosun/issues/2420?email_source=notifications&email_token=AABPAHE6VTOIDEPNEMKTNULP63GQTA5CNFSM4H7A5732YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZVULJQ#issuecomment-510346662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABPAHBJ25MHP3XJCSPGS5LP63GQTANCNFSM4H7A573Q
.

Thank you. We've used it in production environments, that is ok. But I'm not sure that's what you want.


Live preview

hello there, I am a beginner in using brackets and new to HTML and CSS. when I click on the element in the CSS file or  HTML file opened in brackets it highlights the element for a second, I want to highlight the element forever until  I am working on it . How it can be done?

Hi
suggestion to you question- i presume you are working on window 10
click on View , then click on Highlight Active Line
that should solved the problem


No recovery of XLM from prepaid wallet after VDC was closed

Description
I deleted a VDC after transfer of remaining TFT to my wallet (even though I thought there was going to be automatic refunding).
However, I left the XLM in place, but I copied the secret into an interstellar wallet.
After closure of the VDC, it showed that the XLMs remained on the created wallet. If I had closed the VDC without copying the secret, the XLMs would have been lost (and no one will think about recovering it as there is no mention of it in the VDC wallet).

Version information

OS: MacOS
Project commit/version: VDC
Browser: Chrome 88

We hold the info of all the wallets in the system, and we merge them back to our activation service on the deleted VDCs every now and then.


Eric Leschinski: Watch https://www.sociat.com

Eric Leschinski requests the watch of the watch_keyword https://www.sociat.com. See the Metasmoke search here and the Stack Exchange search here.

Is the https:// protocol specifier and the www host name important here? Usually we list just the domain name. Also, this is a regex, so the dots should be backslashed. I'll be happy to make these changes and reapprove once I'm sure I understand your intentions properly.

@tripleee Go ahead: he noticed the mistake in chat (SE chat expanded the URL into a full link which included the protocol and all that) but can't edit the PR

I've made an edit to be just the domain.  CI will probably explode, but assuming it doesn't, then I'll resolve the merge conflicts and handle merging this in.

!!/approve

!!/approve


[docs] Demo VirtualElementPopper crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/components/popper/
??
demo VirtualElementPopper crashes

Your Environment

Tech
Version

MUI
v5.4.4

netlify deploy
https://621d92e1fdc7c4000888a83c--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36

Hey @minus199 , thanks for the headsup. I'm not being able to reproduce this issue, can you point me to what exactly crashed for you?


Removed strings.Builder which was a go 1.10 feature. Closes #47

Codecov Report

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

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   50.43%   50.43%
=======================================
  Files          13       13
  Lines        1039     1039
=======================================
  Hits          524      524
  Misses        464      464
  Partials       51       51

Continue to review full report at Codecov.

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

No problem. I'm the one causing the trouble after all. :-) Thanks for the merge!


fix(server): StringPropertyLengthBoundsRule ignores enum strings #1137

No violations created when string property is an enum

Closes #1137

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1141   +/-   ##
=========================================
  Coverage     87.13%   87.13%
  Complexity      262      262
=========================================
  Files           107      107
  Lines          1384     1384
  Branches         92       92
=========================================
  Hits           1206     1206
  Misses          131      131
  Partials         47       47

Continue to review full report at Codecov.

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

Thank @roxspring!

👍

:+1:


Modifications the change detection variables fail to recalculate datapoints

After saving changes to Change Detection Variables, datapoints are not created:

The server log is full of the following errors, I am not sure if it is related:
2024-01-04 16:13:47,340 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,340 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled
2024-01-04 16:13:47,341 ERROR [io.hyp.too.hor.svc.Util] (executor-thread-1811) Tx Synchronization callback failed: SRMSG00028: The subscription to dataset-event-out has been cancelled

The server-side error msg is related to this issue: https://github.com/Hyperfoil/Horreum/issues/1063.
Although the 2 are inter-related, they are not the same mechanism,


Google Sheets Api

google.html:82 Uncaught TypeError: Cannot read property 'signIn' of null
at handleSignInClick (google.html:82)
at HTMLButtonElement.onclick (google.html:4)

Having the same issue.
I copy/past the sample, replace credentials and having the same issue.

Which sample is this?


Bugfix/603 empy bullet for article sans publish date

Description
Describe:

Add {% if %} condition around markup.
Prevent empty <li> from showing in missing condition.

References
Fix #603
Checklist

[x] I have read the contribution guide
[ ] Code lint checked via inv lint
[x] changes file included (see docs)
[ ] Usage documentation added in case of new features
[ ] Tests added

Coverage remained the same at 96.414% when pulling 081ba007ac12cdd6664f3165245c56e7e26f5496 on tacc-wbomar:bugfix/603-empy-bullet-for-article-sans-publish-date into 540d8754dae33ca80ea12b2c398ea0326c4c22d7 on nephila:develop.

@tacc-wbomar thanks a lot for this fix!


MongoDB update alm-examples

This removes the status fields from the examples, addressing https://github.com/mongodb/mongodb-enterprise-kubernetes/issues/48, and updates them to use non-deprecated fields. I also made it a lot easier to read them.
For easy comparison, this is what the unescaped fields were previously:
[
  {
    "kind": "MongoDB",
    "apiVersion": "mongodb.com/v1",
    "metadata": {
      "name": "sample-replica-set"
    },
    "spec": {
      "version": "4.0.10",
      "type": "ReplicaSet",
      "project": "my-project",
      "persistent": false,
      "members": 3,
      "credentials": "my-credentials"
    },
    "status": {
      "version": "4.0.10",
      "type": "ReplicaSet",
      "phase": "Running",
      "members": 3,
      "link": "https://cloud.mongodb.com/v2/5d35f7cdbf994268c3",
      "lastTransition": "2019-07-23T09:00:00Z"
    }
  },
  {
    "apiVersion": "mongodb.com/v1",
    "kind": "MongoDB",
    "metadata": {
      "name": "sample-sharded-cluster"
    },
    "spec": {
      "configServerCount": 3,
      "credentials": "my-credentials",
      "mongodsPerShardCount": 3,
      "mongosCount": 2,
      "persistent": false,
      "project": "my-project",
      "shardCount": 1,
      "type": "ShardedCluster",
      "version": "3.6.8"
    },
    "status": {
      "lastTransition": "2019-07-23T09:00:00Z",
      "phase": "Running"
    }
  },
  {
    "apiVersion": "mongodb.com/v1",
    "kind": "MongoDBUser",
    "metadata": {
      "name": "sample-user"
    },
    "spec": {
      "db": "$external",
      "project": "my-project",
      "roles": [
        {
          "db": "admin",
          "name": "clusterAdmin"
        }
      ],
      "username": "CN=mms-user-1,OU=cloud,O=MongoDB,L=New York,ST=New York,C=US"
    }
  },
  {
    "apiVersion": "mongodb.com/v1",
    "kind": "MongoDBOpsManager",
    "metadata": {
      "name": "ops-manager"
    },
    "spec": {
      "version": "4.2.0",
      "adminCredentials": "ops-manager-admin",
      "configuration": {
        "mms.fromEmailAddr"<EMAIL_ADDRESS>      },
      "applicationDatabase": {
        "members": 3,
        "version": "4.2.0",
        "persistent": true,
        "podSpec": {
          "cpu": "0.25"
        }
      }
    }
  }
]

great work @BenElgar, however you need to sign off your commits by @tonytcampbell as an original contributor.

Thanks @J0zi. For what it's worth, I have contributed to this operator before (https://github.com/operator-framework/community-operators/pull/818) and I work at MongoDB on the Kubernetes Operator development team. Is that still necessary?


Conflict with .alert style from bootswatch bootstrap css

Hello,
Very nice library!
I encounter the following problem: on my page I have the Messenger CSS links as well as a link to a bootswatch theme (//maxcdn.bootstrapcdn.com/bootswatch/3.3.4/flatly/bootstrap.min.css)
This bootstrap.min.css includes an .alert style with a margin-bottom of 21px, see below.
Therefore my Messenger blocks which are aligned to the bottom are shown 21 px above the page bottom...
Any idea how I could solve that?? Many thanks in advance
.alert{
padding:15px;
margin-bottom:21px;
border:1px solid transparent;
border-radius:4px
}

Can confirm that the .alert, .alert-success, .alert-info classes are conflicting with twitter bootstrap's corresponding alert classes... so this is a :+1: for the OP
I just don't understand why is there a need for the alert classes in the package while it also uses .messenger, .messenger-success, .messenger-info classes already...

:+1:
I believe the original intention was specifically for the purpose of inheriting the bootstrap styles, since I believe at the time that decision was made, there weren’t CSS themes yet. Name-spacing makes total sense to me now and probably something we should have done when we implemented theming. PR?

I've forked the repo, modified the coffescript file to leave out the alert classes completely, and updated the alert classes to message and it work beautifully alongside bootstrap without conflicting. However there's been a sass to scss conversion in the process (out of personal taste) and that's I'm hesitant to create a pull request.

hello, any update on this please?


fixresult_filter_data should be filled by 0 when can_filter_all is true

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Added support for Python 3.8 and Django 3.0 #45

Library is already supporting py3.8 and Django3.0, so no changes needed.
Support has been added to test matrix for tox and to readme. #45

Great. Thank you!


Change virtuals in abstract classes to abstract.

We added methods to an abstract class in a minor release and needed to mark them virtual and throw NotImplementedException.
We should take the breaking compile change in the 8.x major release.
TokenHandler
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/TokenHandler.cs#L66
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/TokenHandler.cs#L76
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/TokenHandler.cs#L85
SignatureProvider
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/SignatureProvider.cs#L105
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/SignatureProvider.cs#L118
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/55cc10ea53503b129afd55734ad9e9dd8203b339/src/Microsoft.IdentityModel.Tokens/SignatureProvider.cs#L150

I'm not sure this is a good idea. I understand wanting to make breaking changes in major release, but this is more than a compile-time breaking change. This will likely cause runtime TypeLoadExceptions in scenarios where you would not have gotten a NotImplementedException previously.
Take SignatureProvider for example. There could be code out there in nuget packages or other prebuilt assemblies that only implement byte[] Sign(byte[] input), bool Verify(byte[] input, byte[] signature) and void Dispose(). It'd be nice if it also implemented the new overloads that support offsets and spans, but the existing implementations that don't are still usable as long as no one actually calls the not implemented methods.
If we made the new overloads abstract instead of a virtual that throws a NotImplementedException, apps that upgrade to 8.x would be unable to make use of any the methods that are implemented because will no longer be able to instantiate an instance of a derived type compiled against an earlier version of Microsoft.IdentityModel.Tokens which did not override the now-abstract methods. You'd get an error like the following when trying to construct it:
Unhandled exception. System.TypeLoadException: Method 'Sign' in type 'DerivedSignatureProvider' from assembly 'SomeNugetPackageOrDll, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' does not have an implementation.

This is why types like Stream didn't add any abstract methods to support things like ReadOnlySpan<byte>. Instead, the virtual method copies the span into an array and calls the Write method which has always been abstract. I think SignatureProvider and TokenHandler should do something similar. If the virtual method absolutely cannot be written in terms of other methods which have always been abstract, we should keep the virtual that throws a NotImplementedException.
In order to achieve a compile-time only break, we could add an analyzer that ensure that derived types override these virtual methods. This would be good even if the virtual method does something like copy a span into an array, because overriding will likely make things faster. If the virtual always throws, the analyzer warning could be more severe.

@halter73 I get what you are saying.  Our objective with TokenHandler derived classes was to let users know that unless they implement ValidateTokenAsync, the TokenHandler is pretty much useless. Same with BaseConfigurationManager.GetBaseConfigurationAsync.
I agree with SignatureProviders, we should leave those.

@halter73 so be it.
We will leave it as is, be careful about adding a public method.


soc: stm32: Enable cortex-m systick timer by default

Move systick activation in soc/ as a Kconfig.defconfig file and
remove activation in boards _defconfig files.
This will allow to deactivate it in a more flexible way
with upcoming LPTIMER as tick source when power management
features are enabled.
Additionally, add a comment when selcting CPU_CORTEX_M_HAS_SYSTICK in C-M0(+) based series.

So, is this valid for really all stm32 SoCs?

since there is  no alterntate tick source available today, it has to be.

@FRASTM

@MaureenHelm , can we get this one merged, as we'll never manage to get shippable passed.
FYI, I've run a  ./scripts/sanitycheck -T samples/hello_world/ -l -N ; showing no impact.

@ioannisg , thanks for the review

You could add a help text where the CPU_CORTEX_M_HAS_SYSTICK is defined, to stress that the HW is optional

Ok, I'll replace the comment by yours.

do you think the option should be selected together with CONFIG_SYS_CLOCK_HW_CYCLES_PER_SECOND? Right now, the latter is still at board level, but this clearly depends on the SysTick, AFAIU

If the question is "should we move CONFIG_SYS_CLOCK_HW_CYCLES_PER_SECOND at SoC level", then the response is:
No, since CONFIG_SYS_CLOCK_HW_CYCLES_PER_SECOND depends on each SoC capabilities, but also board configuration itself (either CPU is driven by fixed clock or PLL, and if drivern by PLL, on PLL configuration).


update*: check shim output

The shims Should Not Fail, but when bugs happen, they just cause confusing errors.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Review period will end on 2023-03-23 at 10:33:29 UTC.


Is there a public endpoint for this API?

Thank you for making this project available. We'd like to use this API as public endpoint for Gregorian to Badi date conversion. Is there an endpoint already available?

Is see there is https://www.openode.io/docs/platform/open_source.md that might be used for free open source hosting, but it has the requirement "Must be active on a monthly basis.".
@dragfyre : I could possibly host this on https://bahai-browser.org (currently a Chrome-only experimental website, but I could set aside a folder for this if you didn't have a place for it). Off topic, but I forget if you are keen to review or whether you want me to just go ahead and merge my existing PRs?

ok, thanks @brettz9. i think openode.io could be a good solution. i don't quite know yet what our api resource usage would be, but we should be making requests on a regular basis.
i'm working with a group of friends to build a calendar app to help local communities better manage events and synchronize community life with the Badí calendar. @ketman-io, whom I'm working with to build the app, offered to host an instance using GCP's infrastructure. so please don't feel the need to incur any extra costs to run the service.

There have been a couple of offers to host this API more or less permanently; let me chase down the people who need to be chased down and I'll get back to this thread when it's done.

@kennyr87 For the time being, I think we'll look into getting this set up on bahai-browser.org as @brettz9 said. If/when the API gets enough usage, we can try and move it to openode.io.

@kennyr87 The API now has a public endpoint here on bahai-browser.org:
date/ - https://bahai-browser.org/date
today/ - https://bahai-browser.org/today


Status check not working

PR: https://github.com/SAP/openui5/pull/1363
CLA has been signed, but the status is still not signed yet. Re-check from PR comment and from admin UI didn't work.
Redirect seems to be broken aswell, see https://github.com/SAP/openui5/pull/1363#issuecomment-284247309.

Hi Matthias,
CLA assistant checks the signatures of the committers of the PR, so @sbell-bluefin and not @stu-b-doo should sign the CLA.

ah, that's my old account. Need to change my git email address. Successfully signed - thanks!

@KharitonOff thanks! I missed that. Would be helpful to show the username if it differs from the one opening the PR.

Also worth pointing out that the first time I tried signing this from the committer's github account - I accessed the PR while logged in as the committer but the assistant's 'sign me in with github' was picking up the other account, which was also logged in in a different tab, same browser session.
Not saying this is something that needs fixing as such, just something to be aware of in case of similar issues.


Do renaming

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 4 (50.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 84.186%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hermes/pkgs/maven.py
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

hermes/pkgs/maven.py
2
89.12%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1086

Relevant Lines:
1290

💛  - Coveralls


Andrew Zaw

Methods are documented in README.md

https://runkit.com/andrewzaw/5e99edfb21478b0014104002

https://www.npmjs.com/package/andrewzaw


Support ArgumentException for the GuardClauseAssertion

Currently GuardClauseAssertion supports only ArgumentNullException for the null guard. It's very inconvenient, as sometimes you are checking inputs like following:
if (string.IsNullOrEmpty(path))
{
	throw new ArgumentException(nameof(path), "Value cannot be null or empty.");
}

I suggest to also allow ArgumentException with the right parameter name, as it's still a valid guard clause.

I'm torn about it. I see the need but it opens a can of use cases, like "accepted integer must be greater than zero".

@Kralizek Could you please elaborate a bit more? The current issue is to accept the ArgumentException exception with ParamName == nameof(argument) when it's thrown for null input. It's only about particular check for null we already have and it doesn't enable any other scenario per se (like range validations) - those capabilities are already present anyway 😉

@zvirja oh really?  I couldn't find how to do it! Then nevermind! 😁


[MB-4557] added addl error handling into support api

Description
This PR updates the payment request support api to process the more specific types of errors coming out of the EDI generator
Review Notes
I realize in payment_request.go there are 2 similar switch statements for handling the different types of errors. To be more DRY I tried to break it out into a separate function. However, I was unable to since the case statement returns different types of errors with custom types when defining the function there was no type I could specify for the expected return. If there is a way to encapsulate the switch statement that I've missed, please let me know and I'll update!
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-4557

  Generated by :no_entry_sign: dangerJS against 6a1340fa4975adaf00b1ff5b145da31745ba9081


Impossible to join VirtualTable (FTS4) with usual one

Hi,
I have run into an issue: joining FTS4 table with regular one seems impossible. May be I am missing something, but documentation does not clarify this point.
The issue:
I have two tables:
nodeTable = Table("node") - usual table
nodeIndex = VirtualTable("nodeindex")  - FTS4 table
both tables were created using peewee in python (prepopulated DB is shipping with app)
The queries look like:
Array(self.db!.prepare(nodeTable.join(nodeIndex, on: nodeTable[id] == nodeIndex.match(searchText + "*")[docid]) ))

OR
Array(self.db!.prepare(nodeTable.join(nodeIndex, on: nodeTable[id] == nodeIndex[docid]) ))

when I run joins on nodeIndex I see following exception:
fatal error: 'try!' expression unexpectedly raised an error: **no such column: nodeindex.id**: file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-7<IP_ADDRESS>/src/swift/stdlib/public/core/ErrorType.swift, line 50
error: Execution was interrupted, reason: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0).
The process has been returned to the state before expression evaluation.

And it is correct: nodeindex does not have column id
sqlite> select id from nodeindex;
Error: no such column: id

it has docid instead.
Please advise.
Thank you beforehand!

The queries you posted look correct. If you still have the problem, please post the generated SQL.


[PDI-17699] DragAndDropContainerTest fail on Windows

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  ui/src/test/java/org/pentaho/di/core/dnd/DragAndDropContainerTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:


appliance: Delete unused mongodb appliance

This is completely untested and does not currently ship as part of the standard distribution. It will be resurrected later.

LGTM


fix: not check index exclusion path for null values

This PR fixes issue #1327  🦕
Summary
Considering the following 4 types of index exclusions:

excludeFromindexes: ['foo.*']
excludeFromindexes: ['foo.bar']
excludeFromindexes: ['foo[].*']
excludeFromindexes: ['foo[].bar']

Supplying { entity: { foo: null } } throws for 2 and 3, but not for 1 and 4.
save({ excludeFromIndexes: ['foo.bar'], entity: { sho: 1, foo: null })
// throws TypeError: Cannot read properties of undefined (reading 'properties')

save({ excludeFromIndexes: ['foo[].*'], entity: { sho: 1, foo: null })
// throws TypeError: Cannot read properties of undefined (reading 'values')

With the changes in this PR, the save calls will not throw in any of the 4 cases.

For additional notes on this PR see this.


Add fields EnterpriseID and EnterpriseName to SlashCommand

https://api.slack.com/slash-commands#triggering_a_command

TYVM @suzuki-shunsuke


Pass parameter array as varargs

Pass "Where" paramters as a varargs instead of array.
Fix for #418

Current coverage is 64.49% (diff: 100%)

Merging #419 into master will not change coverage

@@             master       #419   diff @@
==========================================
  Files            44         44
  Lines          1907       1907
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1230       1230
  Misses          550        550
  Partials        127        127

Powered by Codecov. Last update df763b9...51e1979


nfs-client-provisioner volume cannot be expanded

Trying to expand a PVC got warning:
Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.

Create a PVC of 1Gi size:
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: myclaim
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: nfs-client
EOF

Check that pvc, it's successfully bound:
$ kubectl get pvc myclaim
NAME       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
myclaim    Bound    pvc-6ef8eda2-efb5-11e9-9bef-005056bd0410   1Gi        RWO            nfs-client     8s

$ kubectl describe pvc myclaim
...
Events:
  Type    Reason                 Age                From                                                                                Message
  ----    ------                 ----               ----                                                                                -------
  Normal  Provisioning           61s                cluster.local/nfs-client-provisioner_nfs-client-provisioner-58487c669c-jjqpq_a9da7c7e-ec08-11e9-9af1-2228a80fe4ad  External provisioner is provisioning volume for claim "default/myclaim"
  Normal  ExternalProvisioning   61s (x2 over 61s)  persistentvolume-controller                                                                                waiting for a volume to be created, either by external provisioner "cluster.local/nfs-client-provisioner" or manually created by system administrator
  Normal  ProvisioningSucceeded  61s                cluster.local/nfs-client-provisioner_nfs-client-provisioner-58487c669c-jjqpq_a9da7c7e-ec08-11e9-9af1-2228a80fe4ad  Successfully provisioned volume pvc-6ef8eda2-efb5-11e9-9bef-005056bd0410

Try to expand PVC to size of 2Gi:
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: myclaim
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi
  storageClassName: nfs-client
EOF

Check it, and it's still size of 1Gi:
$ kubectl get pvc myclaim
NAME      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
myclaim   Bound    pvc-6ef8eda2-efb5-11e9-9bef-005056bd0410   1Gi        RWO            nfs-client     2m37s

Check the events:
$ kubectl describe pvc myclaim
Events:
  Type     Reason                 Age                    From                                                                                Message
  ----     ------                 ----                   ----                                                                                -------
  Normal   Provisioning           4m14s                  cluster.local/nfs-client-provisioner_nfs-client-provisioner-58487c669c-jjqpq_a9da7c7e-ec08-11e9-9af1-2228a80fe4ad  External provisioner is provisioning volume for claim "default/myclaim"
  Normal   ExternalProvisioning   4m14s (x2 over 4m14s)  persistentvolume-controller                                                                                waiting for a volume to be created, either by external provisioner "cluster.local/nfs-client-provisioner" or manually created by system administrator
  Normal   ProvisioningSucceeded  4m14s                  cluster.local/nfs-client-provisioner_nfs-client-provisioner-58487c669c-jjqpq_a9da7c7e-ec08-11e9-9af1-2228a80fe4ad  Successfully provisioned volume pvc-6ef8eda2-efb5-11e9-9bef-005056bd0410
  Warning  ExternalExpanding      19s                    volume_expand                                                                                Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.

BTW Storage class enabled expansion:
$ kubectl get storageclasses.storage.k8s.io -o nfs-client
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  creationTimestamp: "2019-10-12T09:19:04Z"
  labels:
    app: nfs-client-provisioner
    chart: nfs-client-provisioner-1.2.6
    heritage: Tiller
    io.cattle.field/appId: nfs-client-provisioner
    release: nfs-client-provisioner
  name: nfs-client
  resourceVersion: "4010231"
  selfLink: /apis/storage.k8s.io/v1/storageclasses/nfs-client
  uid: 55e63667-ecd1-11e9-9bef-005056bd0410
parameters:
  archiveOnDelete: "false"
provisioner: cluster.local/nfs-client-provisioner
reclaimPolicy: Delete
volumeBindingMode: Immediate

Yes, the nfs-client-provisioner is not capable of expanding volumes. In fact, it does not enforce the size of volumes at all, so a PV that says 1Gi may in fact have contain/write more than 1Gi of data in its path. AFAIK, there is no standard quota/limit mechanism for NFS. Apologies if this is not clear.

I got it, thanks


Remove 'iam' projects

Description

Following up after #2613 services/iam project is obsolete and has been disabled since ba84808, and technically it should be removed. This will be discussed here on and on the ML to see if there's anyone wants to revive/maintain this.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

Fixes: #2772
Screenshots (if appropriate):
How Has This Been Tested?

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
 I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2261

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

I agree with @DaanHoogland, if we remove the *VO*,  e should remove tables as well. I noticed that this component has a few API methods as well. Out of curiosity, does anybody know what IAM stands for? And what was the purpose of this component?
When I read IAM I tempted to think Identity and Access Management, which ACS could benefit from.

@DaanHoogland I noticed that (the definition of tables in sql files) and I wanted to open the PR as it was and have a discussion around it here. I am completely for removing the tables too (schema-41120-41200-cleanup.sql probably).

@rafaelweingartner It stands for "Identity and Access Management" or like "I am" (as subject and verb)

@khos2ow so it was some sort of integration with policy decision points that was never finished?

I would say so. Most probably started at around the same time AWS introduced their IAM and left alone here?

 Please check and remove any db tables as part of the upgrade path and delete the VOs/Daos classes if any.

@rhtyd @DaanHoogland all the VO java files were inside the project services/iam/server which already has been deleted as part of the first commit of this PR, and I just pushed a schema cleanup to drop corresponding tables as well.

looks good @khos2ow. Just wondering if we should actually remove the upgrade code that adds them. someone installing a new system now goes through the steps of adding those tables only to end up removing them again at the initial start of the system.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✖debian. JID-2275

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2278

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@DaanHoogland that's true but I wouldn't remove the code that adds them in the first place. This will make the schema upgrade path not "immutable". (at least immutable by convention to never change anything that's been released)

Is this one ready to merge???

I think so.

Everything looks in order.  What is the process of getting from this stage to merged?  I could merge the PR (as I am a committer), but what are we doing now as a way to get through the valid PRs to merge?

Click on "squash+merge" as soon as the PR has passed the tests and has been approved by reviewers...

Ok, so basically manual inspection and merging by active members?  Thanks...

That is it. We are not merging PRs automatically yet.


TST: improve array API assertions

Reference issue
https://github.com/scipy/scipy/pull/18930#issuecomment-1705759257 @mdhaber
What does this implement/fix?

the assertions are renamed with the xp_ prefix to avoid conflict with np.testing
assert actual.dtype == desired.dtype is added. This is already checked by default for PyTorch in assert_close and assert_equal,

LGTM but let's see what others think of the name and whether we can add a shape check.

whether we can add a shape check

Ah forgot to mention, I think that this already happens. I checked through all the docs, e.g. https://numpy.org/doc/stable/reference/generated/numpy.testing.assert_allclose.html where it is explicitly stated. I think that it's implied for torch too https://pytorch.org/docs/stable/testing.html?

It doesn't for NumPy when the right hand side is a scalar.

https://numpy.org/doc/stable/reference/generated/numpy.testing.assert_array_equal.html has a strict keyword that gets part of the way to what Matt wants, I think? I still like the "vectorized by default," but I suppose we could do something like that here if we really need it?

In addition to the naming and shape check, we have the option of checking whether the correct namespace is returned inside these functions to consider, as discussed in gh-18930.

+1 for the stricter checks, and +1 for the renames.

@mdhaber does Tyler's comment https://github.com/scipy/scipy/pull/19186#issuecomment-1706965091 help address your strictness concerns?
Also happy to go with your decision on whether or not to include the namespace checks in this PR or not.

@lucascolley The comment is certainly related - assert_array_equal with strict=True would do what I think our xp_assert_equal should do by default (minus the additional array type check, which I wouldn't expect from a function developed before the Array API). The fact that assert_array_equal has this option doesn't resolve the concern, though. Rather, it gives support to the idea that these stricter checks should be added. Actually, see the discussion in numpy/numpy#21595, where these checks were added to NumPy.
https://github.com/scipy/scipy/pull/19186#issuecomment-1710463946 indicated +1 on the strictness checks, so I'd suggest for all three assertions:

add the shape check
add the array type check (this should also fail if the reference is a NumPy scalar but the result is a 0d array or vice-versa)
ensure that the AssertionError message identifies which check failed
(optional) add parameters to turn them off individually (e.g. check_dtype=True, check_shape=True, check_xp=True), or these can be added later if the need arises

As for why these should be strict by default: these checks are not performed strictly by default now, yet the manual additional of the strict checks is often neglected, and there are several inconsistencies/shortcomings/bugs in SciPy that might have been caught had the tests been stricter. So even if these stricter checks are only performed where these xp_asserts are used, I think we would be better off than we are now. (And actually, when developers see these stricter assertions fail, they might be reminded of the other places the assertions are needed.)

(And actually, when developers see these stricter assertions fail, they might be reminded of the other places the strict checks are needed.)

To confirm that: this was my exact experience with the one test on Lucas' fft branch that I tried to refactor.

Sorry, the rebase is messy since I failed to git submodule update - fixing now.

@mdhaber how does this look? Here are the AssertionError messages:
In [1]: from scipy._lib._array_api import xp_assert_equal

In [2]: import numpy as np

In [3]: import torch

In [4]: xp_assert_equal(np.asarray(0), np.asarray([0, 0]))
AssertionError: Array shapes are not equal: actual shape = (), desired shape = (2,)

In [5]: xp_assert_equal(np.asarray([0, 0]), np.asarray(0))
AssertionError: Array shapes are not equal: actual shape = (2,), desired shape = ()

In [6]: xp_assert_equal(np.asarray(0), np.asarray(0)[()])
AssertionError: Desired a numpy scalar, but 0-D array given.

In [7]: xp_assert_equal(np.asarray(0)[()], np.asarray(0))
AssertionError: Desired a 0-D array, but numpy scalar given.

In [8]: xp_assert_equal(0, np.asarray(0)[()])
ValueError: Inputs should be arrays with a dtype attribute, python scalars and arrays are not accepted.

In [9]: xp_assert_equal(np.asarray(0)[()], 0)
ValueError: Inputs should be arrays with a dtype attribute, python scalars and arrays are not accepted.

In [10]: xp_assert_equal(np.asarray([1, 2]), torch.asarray([1, 2]))
AssertionError: Namespaces do not match: scipy._lib.array_api_compat.array_api_compat.numpy and scipy._lib.array_api_compat.array_api_compat.torch

In [11]: xp_assert_equal(np.asarray([1, 2], dtype=np.float32), np.asarray([1, 2], dtype=np.float64))
AssertionError: Desired dtype: float64, actual dtype: float32

In [12]: xp_assert_equal(np.asarray([1, 2], dtype=np.float64), np.asarray([1, 2], dtype=np.float32))
AssertionError: Desired dtype: float32, actual dtype: float64

In [13]: xp_assert_equal(np.asarray([1, 2]), np.asarray([1, 2]))
# passes

This looks almost done now, cc @tylerjereddy @rgommers if you'd like to have a look.

@mdhaber it looks like _lazywhere may need to be updated to satisfy the expected 0D-array / scalar behaviour?

I'll merge this shortly, probably squash-merge given 20 commits and some 1-liners in there, etc.
Things I checked/other thoughts:

Full test suite with no array API stuff on.
Full test suite with array API + cuda. (there's a known torch failure already fixed upstream)
Full test suite with array API on host.
There is a comment above that mentions a few cases we may to make some adjustment for, including this one that doesn't pass (raise an exception) for current non-conformant NumPy (but does for all other backends)--perhaps we should open a separate issue for those few cases if one isn't open already (I don't think I know the answer to what we want for all those cases though...):

--- a/scipy/_lib/tests/test_array_api.py
+++ b/scipy/_lib/tests/test_array_api.py
@@ -106,3 +106,9 @@ class TestArrayAPI:
             with pytest.raises(AssertionError, match="Types do not match."):
                 xp_assert_equal(xp.asarray(0.), xp.float64(0))
             xp_assert_equal(xp.float64(0), xp.asarray(0.))
+
+
+    @array_api_compatible
+    def test_coercion_stringency(self, xp):
+        with pytest.raises(AssertionError):
+            xp_assert_equal(xp.asarray([1, 2]), [1, 2])

So far, upstream (NumPy) doesn't seem to object too much to adding some similar stringency options to their current assertions like Matt's PR here: https://github.com/numpy/numpy/pull/24680 (and they already did it elsewhere as discussed in previous comments)
xp_assert_close isn't tested/used yet--I did note when substituting it in a few assert_allclose() places that it doesn't support float input with default arguments--maybe that's an "ok" usage for the conventional NumPy assertion machinery I suppose. (AttributeError: 'float' object has no attribute 'dtype'). Tests should be easy enough to write like this if we want:

--- a/scipy/_lib/tests/test_array_api.py
+++ b/scipy/_lib/tests/test_array_api.py
@@ -3,7 +3,8 @@ import pytest

 from scipy.conftest import array_api_compatible
 from scipy._lib._array_api import (
-    _GLOBAL_CONFIG, array_namespace, as_xparray, copy, xp_assert_equal, is_numpy
+    _GLOBAL_CONFIG, array_namespace, as_xparray, copy, xp_assert_equal, is_numpy,
+    xp_assert_close,
 )
 import scipy._lib.array_api_compat.array_api_compat.numpy as np_compat

@@ -106,3 +107,9 @@ class TestArrayAPI:
             with pytest.raises(AssertionError, match="Types do not match."):
                 xp_assert_equal(xp.asarray(0.), xp.float64(0))
             xp_assert_equal(xp.float64(0), xp.asarray(0.))
+
+    @array_api_compatible
+    def test_assert_close(self, xp):
+        with pytest.raises(AssertionError):
+            xp_assert_close(xp.asarray([0.0001, 0.0001]), xp.asarray([0.00009, 0.00009]))
+        xp_assert_close(xp.asarray([0.0001, 0.0001]), xp.asarray([0.00009, 0.00009]), atol=1e-05)

I imagine a few rough spots will get ironed out when these assertions start getting used more heavily.

it doesn't support float input with default arguments

This was intentional, given the discussion in https://github.com/scipy/scipy/pull/19157#discussion_r1312983982.

Thanks for the thorough review Tyler, and all of the help on this one Matt!

However, if check_namespace is turned off, it should accept plain floats and do the conversion automatically.

Maybe, although if they are both floats you're still hosed it seems:
--- a/scipy/spatial/tests/test_hausdorff.py
+++ b/scipy/spatial/tests/test_hausdorff.py
@@ -6,6 +6,7 @@ import pytest
 from scipy.spatial.distance import directed_hausdorff
 from scipy.spatial import distance
 from scipy._lib._util import check_random_state
+from scipy._lib._array_api import xp_assert_close

 class TestHausdorff:
@@ -146,7 +147,7 @@ class TestHausdorff:
         # verify fix for gh-11332
         actual = directed_hausdorff(u=A, v=B, seed=seed)
         # check distance
-        assert_allclose(actual[0], expected[0])
+        xp_assert_close(actual[0], expected[0], check_namespace=False)

Since that functionality probably isn't even planned for array API support anytime soon it doesn't matter much. On the flip side, I was perhaps wondering if longer-term we'd want to consider completely switching over to that set of assertions everywhere and/or having the error message explain what to do in that case.

although if they are both floats you're still hosed it seems

Sure. That's just a consequence of the way https://github.com/scipy/scipy/pull/19157#discussion_r1312983982 went.

On the flip side, I was perhaps wondering if longer-term we'd want to consider completely switching over

Sounds great to me.


ImportError: cannot import name 'openai' from 'openpipe' (unknown location)

Getting the above import error, once i have installed the openpipe via
pip install openpipe

Should we follow any more steps as well, like this one
I'm trying to execute the jupyter notebooks available on the examples folder, hope someone can help me setting this up.

Hey @attili-sanjeet, I just tried using openpipe in a Jupyter notebook and wasn’t able to reproduce your error. Have you gotten it resolved?

Yes I have resolved it, internal instance issue
Thanks!
Get Outlook for iOShttps://aka.ms/o0ukef

From: arcticfly @.>
Sent: Thursday, September 7, 2023 7:15:08 PM
To: OpenPipe/OpenPipe @.>
Cc: Sanjeet Attili @.>; Mention @.>
Subject: Re: [OpenPipe/OpenPipe] ImportError: cannot import name 'openai' from 'openpipe' (unknown location) (Issue #211)
CAUTION: This is an external email originated outside of Uniphore. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hey @attili-sanjeethttps://protect2.fireeye.com/v1/url?k=31323334-501d2dca-313542b9-454455534531-d5dfd5ee3b205deb&q=1&e=b4cc3764-a123-49c5-b3da-1ef5ba81bb34&u=https%3A%2F%2Fgithub.com%2Fattili-sanjeet, I just tried using openpipe in a Jupyter notebook and wasn’t able to reproduce your error. Have you gotten it resolved?
—
Reply to this email directly, view it on GitHubhttps://protect2.fireeye.com/v1/url?k=31323334-501d2dca-313542b9-454455534531-148cbd507ab51a64&q=1&e=b4cc3764-a123-49c5-b3da-1ef5ba81bb34&u=https%3A%2F%2Fgithub.com%2FOpenPipe%2FOpenPipe%2Fissues%2F211%23issuecomment-1710180834, or unsubscribehttps://protect2.fireeye.com/v1/url?k=31323334-501d2dca-313542b9-454455534531-dc2190f3fd0df987&q=1&e=b4cc3764-a123-49c5-b3da-1ef5ba81bb34&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA5NEKRWQIUS36HGYJISXV6DXZHFWJANCNFSM6AAAAAA4J2WCOQ.
You are receiving this because you were mentioned.Message ID: @.***>
This transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
This transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

Awesome, glad to hear it.


microsoft/surface: Update to kernel 6.11.4

Description of changes
Update the Surface kernel to 6.11.4. This aggregates the work already done by @mexisme in #1183 and @nickodei.
Things done

[X] Tested the changes in your own NixOS Configuration
[X] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input
[X] Tested on a Surface Pro 8 and Surface Pro 9

Probably a good decision to create a new PR. I checked out your branch and tested it to make sure. Everything looks good on my surface pro 8.

Looks pretty good, after a quick browse.
I'll try to test it out over the weekend on my Surface Go.
I have too much on over the next few days.

Dropped the old kernel version and re-tested ✅

Dropped the old kernel version and re-tested ✅
@Mic92 @mexisme

LGTM

Running this branch on my surface pro 8 and everything looks fine so it has my approval as well.


Define Plugin::~Plugin() inline

This change will allow the compiler to create the destructor without needing the template to be explicitly specified.
Essentially it means these lines:
https://github.com/free-audio/clap-examples/blob/main/plugins/core-plugin.cc#L16
aren't needed.
This gets more complex if the required type might change - as here (which is only two variants, but there could be more):
https://github.com/iPlug2/iPlug2/blob/9845fc59abc0ca72be0aec4fd44152c76aaa10b7/IPlug/CLAP/IPlugCLAP.cpp#L22
Obviously, I can work around this if it stays as it is, but I think this makes things nicer.

Sorry, I've forgot to come back to this PR!


making ipv4 and ipv6 optional

Addressing #198
Aligning these values as "optional" instead of "required" with the documentation.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

FYI, @dirtyonekanobi  made a good point when chatting with him today that an update to the flatten method for vpn/route_via also needs done. Added a commit for that.
If I get some extra cycles, I will try and throw together some tests that account for default sites.

FYI...
Been mucking with this a bit more. I believe I have it narrowed down to just the "route_via" section under "vpn"... Specifically what was noted in my last comment about
The error it is throwing (parts removed, including relevant sections):
panic: interface conversion: interface {} is map[string]interface {}, not *schema.Set
...
2021-12-27T15:19:34.937Z [DEBUG] plugin.terraform-provider-appgatesdp_v0.8.3: github.com/appgate/terraform-provider-appgatesdp/appgate.resourceAppgateSiteRead()
2021-12-27T15:19:34.937Z [DEBUG] plugin.terraform-provider-appgatesdp_v0.8.3: 	github.com/appgate/terraform-provider-appgatesdp/appgate/resource_appgate_site.go:601
...
2021-12-27T15:19:34.941Z [DEBUG] plugin: plugin process exited: path=.terraform/plugins/registry.terraform.io/appgate/appgatesdp/0.8.3/linux_amd64/terraform-provider-appgatesdp_v0.8.3 pid=320 error="exit status 2"
2021-12-27T15:19:34.941Z [WARN]  plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2021/12/27 15:19:34 [DEBUG] appgatesdp_site.dv_test_site: apply errored, but we're indicating that via the Error pointer rather than returning it: rpc error: code = Unavailable desc = transport is closing
2021/12/27 15:19:34 [TRACE] eval: *terraform.EvalMaybeTainted
2021/12/27 15:19:34 [TRACE] EvalMaybeTainted: appgatesdp_site.dv_test_site encountered an error during creation, so it is now marked as tainted
...

The interesting thing is... this actually does create the site... But TF seems to not be able to read/validate. RPC errors occurring on both creating a new site and when trying to run a plan against a state that has pre-existing sites that have the "route_via" section included under "vpn".
If you want to test, you can use this sample resource:
resource "appgatesdp_site" "default_test_site" {
    name = "default test"
    short_name = "DT"
    entitlement_based_routing = false
    notes = "Managed by terraform"
    default_gateway {
        enabled_v4       = true
        enabled_v6       = false
    }
    name_resolution {
        use_hosts_file = false
        dns_resolvers {
            name = "test"
            update_interval = 60
            servers = ["<IP_ADDRESS>"]
            search_domains = ["example.com"]
        }
    }
    vpn {
        state_sharing = false
        ip_access_log_interval_seconds = 120
        snat = false
        tls {
          enabled = true
        }
        dtls {
            enabled = false
        }
        route_via {
            ipv4 = "<IP_ADDRESS>"
            ipv6 = "fdf8:f53b:82e4::53"
        }
      }
    tags = ["terraform", "api-created","default_test_site"]
}

Added another pr which I think addresses the panic... I don't think route_via was being returned as the correct type.


Terminal/std_out control

Hey again, thanks for all the great work and effort that has gone into this library It has been very helpful and a pleasure to utilize; I was wondering if it was possible, via utility function or otherwise, to put text to the Terminal? As I understand Monomer, and SDL2 use the std_out. Is there anyway to interact with the same pipe that monomer itself is using to, say, output a statement?
Thanks for all your help!

Hi @MilesLitteral!
To output text to the console you can use a Task, since it receives an IO action, and use any of the regular output functions you would use in console programs. For example:
newtype AppModel = AppModel {
  _clickCount :: Int
} deriving (Eq, Show)

data AppEvent
  = AppInit
  | AppIgnore
  | AppIncrease
  | AppPrint
  deriving (Eq, Show)

makeLenses 'AppModel

buildUI
  :: WidgetEnv AppModel AppEvent
  -> AppModel
  -> WidgetNode AppModel AppEvent
buildUI wenv model = widgetTree where
  widgetTree = vstack [
      label "Hello world",
      spacer,
      hstack [
        label $ "Click count: " <> showt (model ^. clickCount),
        spacer,
        button "Increase count" AppIncrease
      ]
    ] `styleBasic` [padding 10]

handleEvent
  :: WidgetEnv AppModel AppEvent
  -> WidgetNode AppModel AppEvent
  -> AppModel
  -> AppEvent
  -> [AppEventResponse AppModel AppEvent]
handleEvent wenv node model evt = case evt of
  AppInit -> []
  AppIgnore -> []
  AppIncrease -> [
      Model (model & clickCount +~ 1),
      Event AppPrint
    ]
  AppPrint -> [
      Task $ do
        putStrLn $ "Count is now: " ++ show (model ^. clickCount)
        return AppIgnore
    ]

It is also possible to request a Task to be run in AppIncrease; I just split them to avoid confusion with what to model contains (until handleEvent is called again, the model variable will still point to the non-updated value).

I'll close the issue for now. If you have any other questions, please re-open it or create a new one. Thanks!

Sorry I'd forgotten to submit my comment thanks again for all your help :)

Just in case you are using Windows and are still having problems with outputting text to the console, I saw this issue on SDL2's repository which may be related: https://github.com/haskell-game/sdl2/issues/86.
The fix seems to require adding this to your package.yaml (copied from this PR mentioned in the issue):
when:
  - condition: os(windows)
    ghc-options: -optl-mconsole


Better handling of non OK HTTP status codes in injector

At the moment, when the injector receives a message from the origin, it only checks the error code. But this error code has nothing to do with the response HTTP status code.
We need to check that, and handle non OK responses appropriately.
Sample 304 response I found in the cache:
HTTP/1.1 304 Not Modified
Content-Type: image/png
Last-Modified: Tue, 03 Jan 2017 21:29:30 GMT
Cache-Control: max-age=1661425
Expires: Tue, 02 Jan 2018 16:25:41 GMT
Date: Thu, 14 Dec 2017 10:55:16 GMT
Connection: keep-alive
Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *

I added first workaround to only store HTTP/OK responses for now:
https://github.com/equalitie/ouinet/commit/cb31fe4cc4d8cf4cabe18afdba00c5512fd23eb3


Fix bug when copying images when input_dir = output_dir

Two things in this bug fix:

Remove the output_directory iff it is not the same as the input_directory containing images (we don't want to delete valuable user data accidentally).
Bypass shutil.SameFileError when copying files with a simple try catch. Works fine when input_dir = output_dir.

For some reason my ns-dev-test reformatted some of the longer arguments. I have a recent version of nerfstudio so not sure why it did that.

Have you rerun pip install -e .[dev]?

Have you rerun pip install -e .[dev]?

Yep. I think the problem was that I also had a format on save setting also applied to ruff in my vscode settings. I think this was messing with all the formatting and running ns-dev-test did not fix it for some reason. My local ruff was adding some more formatting it seems.


Cannot auth with certificate to azure when targeting .NET 4.5.2

I cannot authenticate to Azure using certificates available in release 1.1.0
       public AzureCredentials FromServicePrincipal(string clientId, string certificatePath, string certificatePassword, string tenantId, AzureEnvironment environment) when my project is targeting 4.5.2, but it works when I target the NetCore framework.
This fails with the exception System.Security.Cryptography.CryptographicException: The specified network password is not correct, when actually trying to auth ( e.g. calling azureClient.TrafficManagerProfiles.GetByResourceGroup  where azureClient is of type IAzure).
The only difference I saw was that for 4.5.2 Microsoft.IdentityModel.Clients.ActiveDirectory is set to 2.28.3 while for NetCore is set to 3.13.9. This is referenced by Microsoft.Rest.ClientRuntime.Azure. Authentication 2.3.0.

For now you will need to have a custom implementation of AzureCredentials and overload ProcessHttpRequestAsync

We should add an overload which will take X509Certificate2 as a parameter.

For who is having this issue, here is a sample implementation of the CustomAzureCredentials which you can use it then to pass it to the Azure Client like this:
            this.azureClient = Azure
                .Configure()
                .WithLogLevel(HttpLoggingDelegatingHandler.Level.Basic)
                .Authenticate(credentials)
                .WithSubscription(subscriptionId);

CustomAzureCredentials implementation:
    {
        private readonly X509Certificate2 certificate;
        private readonly string clientId;

        public CustomAzureCredentials(string appId, string tenantId, X509Certificate2 certificate, AzureEnvironment azureEnvironment)
            : base((ServicePrincipalLoginInformation)null, tenantId, azureEnvironment)
        {
            this.certificate = certificate;
            this.clientId = appId;
        }

        public override async Task ProcessHttpRequestAsync(HttpRequestMessage message, CancellationToken cancelToken)
        {
            var assertionCertificate = new ClientAssertionCertificate(this.clientId, certificate);
            ServiceClientCredentials scc = await ApplicationTokenProvider.LoginSilentWithCertificateAsync(this.TenantId, assertionCertificate, TokenCache.DefaultShared);

            await scc.ProcessHttpRequestAsync(message, cancelToken);
        }
    }

Fixed for .Net 452 in Fluent v1.1.3


Branch patch2

Codecov Report
Base: 63.79% // Head: 63.93% // Increases project coverage by +0.13% :tada:

Coverage data is based on head (7af1ca6) compared to base (676ea6b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #320      +/-   ##
============================================
+ Coverage     63.79%   63.93%   +0.13%
- Complexity     1223     1225       +2
============================================
  Files           189      189
  Lines          4389     4389
  Branches        529      529
============================================
+ Hits           2800     2806       +6
+ Misses         1392     1387       -5
+ Partials        197      196       -1

Impacted Files
Coverage Δ

...ogic/commands/filtercommands/FilterPetCommand.java
95.23% <0.00%> (+4.76%)
:arrow_up:

...main/java/seedu/address/model/person/Supplier.java
89.28% <0.00%> (+17.85%)
:arrow_up:

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

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


Types, types, types

implements types for all methods under the classes folder

Thanks Gal 👏

I made a bit of a mess of this pr as I had to revert it and then revert the revert 😛 but rest assured types will be in the next release - thanks


Improve Driver Container Image Size

Summary:
The dockerfile copies unnecessary files and directories to the final UBI minimal based driver container image. The goal is to copy only the necessary ko files and firmware binaries to keep the driver container image size as small as possible.
Solution:
Initial analysis of current driver container image shows we can safely copy all *.ko and *.ko.xz files under /lib/modules/4.18.0-372.46.1.el8_6.x86_64/. The following ko files would be copied. Note: *.ko.xz files are not shown below since there are several. The xz extension indicates it is a compressed ko file so it takes less space than a traditional ko file.

For firmware binaries, the proposed solution is to copy only dg2* firmware binaries since those are the only binaries that are needed for Intel Data Center GPU Flex Series. We will continue to copy the copyright license in /firmware/i915/license/ and the firmware binaries in /firmware/i915/.
Task Checklist:

[x] 1. Make above changes in dockerfile
[x] 2. Re-build and deploy driver container using updated dockerfile and KMM
[x] 3. Test updated driver container to ensure no regression issues.
[x] 4. Review and compare updated compressed driver container image size. Current compressed size is 256 MiB.
[x] 5. Submit PR to update dockerfile after reviewing results.

New driver container compressed image size is down from 256 MiB to 180.1 MiB. Reduced by 75.9 MiB. build log


Fix TypeError w/r to bytestring on Py3

A PDF couldn't be loaded with PDFQuery on Python 3.5 because of a TypeError.
label_format['P'] appeared to be a bytestring, which clashes with the unicode string page_label.
This patch ensures that only unicode strings are returned.
Unfortunately, I cannot attach the PDF that caused the TypeError because of NDA reasons.

Sorry, missed this when it came in. Thanks!


Better GDPR compliance

While looking into preparation of a workshop with @kegl , it made me realize that a number of things regarding GDPR, handling of personal data and informing users could probably be improved, even for the https://ramp.studio/ instance.
In particular,

[ ] adding an optional template for the privacy policy explaining how their personal data (mostly name, email and submitted code) is stored and processed (which should be customized for deployed instances). Also clarifying the copyright situation with the submitted code (i.e. that users keep the copyright).
[ ] when users sign-up having a check-box that that agree with the privacy policy and likely more specific actions their email is used for
[ ] add UI to remove an account, which should also remove all the submitted data
[ ] add information about usage of cookies. Currently one is used by flask-login with a storage policy of 1 year (used to remember credentials). This can probably  be reduced to a few months by default.
[ ] likely discuss the the data retention policy. The easiest here might be that events after X years are removed, though say Kaggle doesn't do it, so I'm not sure how they get around it.

For the https://ramp.studio/ instance, some of this should probably discussed on a different channel.

+1000 !


Example: "Perform TLS origination with an egress gateway" not working

Bug description
I was following the doc about "Perform TLS origination with an egress gateway" but in the step 5 I don't get the expected result.
Instead I get:
$ curl http://edition.cnn.com/politics -v
* About to connect() to edition.cnn.com port 80 (#0)
*   Trying <IP_ADDRESS>...
* Connected to edition.cnn.com (<IP_ADDRESS>) port 80 (#0)
> GET /politics HTTP/1.1
> User-Agent: curl/7.29.0
> Host: edition.cnn.com
> Accept: */*
>
< HTTP/1.1 502 Bad Gateway
< location: http://edition.cnn.com/politics
< date: Fri, 21 Jun 2019 22:14:33 GMT
< server: envoy
< content-length: 0
<
* Connection #0 to host edition.cnn.com left intact

Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastrcture
Expected behavior
It should return HTTP/1.1 200 OK instead of HTTP/1.1 502 Bad Gateway
Steps to reproduce the bug
Follow instructions on https://istio.io/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/#perform-tls-origination-with-an-egress-gateway up to step 5.
Everything before that step is as show.
I tried with both mutual tls enabled and mutual tls disabled.
I also tried with global.outboundTrafficPolicy.mode=ALLOW_ANY and with global.outboundTrafficPolicy.mode=REGISTRY_ONLY as showed here.
Version (include the output of istioctl version --remote and kubectl version)
$ istioctl version --remote
client version: 1.2.0
citadel version: 1.2.0
galley version: 1.2.0
ingressgateway version: 1.2.0
pilot version: 1.2.0
policy version: 1.2.0
sidecar-injector version: 1.2.0
telemetry version: 1.2.0

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T10:09:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-06-20T16:29:27Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Using Helm
Environment where bug was observed (cloud vendor, OS, etc)
Fedora 29
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

Sorry, I didn't install the Istio egress gateway. Will install and report back.

When istio egress gateway is present it works as expected, sorry.


multi core cpu issue(server vs local)

My local computer is mac : i7 quad core 2.2GHz .  (2015 model)
My server computer is centos7 : 120-core (8 sockets × 15cores) Intel Xeon E7-8870
My tensorflow version : v1.0.1
I build tensorflow source with this option :
bazel build -c opt --copt=-msse4.2 --copt=-msse4.1 --copt=-mavx --copt=-mavx2 --copt=-mfma --config=opt //tensorflow/tools/pip_package:build_pip_package
With under simple code, my local computer time is 8 seconds and my server computer time is 22 second.
`
import tensorflow as tf
from tensorflow.examples.tutorials.mnist import input_data
import time
mnist = input_data.read_data_sets("MNIST_data/", one_hot=True)
x = tf.placeholder(tf.float32, [None, 784]);
y_ = tf.placeholder(tf.float32, [None, 10]);
W1 = tf.Variable(tf.random_normal([784,240], stddev=0.35));
W2 = tf.Variable(tf.random_normal([240,120], stddev=0.35));
W3 = tf.Variable(tf.random_normal([120,10], stddev=0.35));
b1 = tf.Variable(tf.zeros([240]));
b2 = tf.Variable(tf.zeros([120]));
b3 = tf.Variable(tf.zeros([10]));
y1 = tf.nn.sigmoid(tf.matmul(x,W1)+b1);
y2 = tf.nn.sigmoid(tf.matmul(y1,W2)+b2);
y = tf.nn.softmax(tf.matmul(y2,W3)+b3);
cross_entropy = tf.reduce_mean(-tf.reduce_sum(y_*tf.log(y), reduction_indices=[1]))
train = tf.train.GradientDescentOptimizer(0.5).minimize(cross_entropy)
NUM_THREADS = 100
sess = tf.InteractiveSession(config=tf.ConfigProto(intra_op_parallelism_threads=NUM_THREADS))
tf.global_variables_initializer().run()
start_time = time.time()
for _ in range(3000):
batch_xs, batch_ys = mnist.train.next_batch(100)
sess.run(train, feed_dict={x: batch_xs, y_: batch_ys})
end_time = time.time()
print (end_time - start_time)
correct_prediction = tf.equal(tf.argmax(y, 1), tf.argmax(y_, 1))
accuracy = tf.reduce_mean(tf.cast(correct_prediction, tf.float32))
print(sess.run(accuracy, feed_dict={x: mnist.test.images, y_: mnist.test.labels}))
`
I think it is impossible because my server computer have so many cores.
Isn't it multi-core issue?

I7 cores are faster than Xeon cores. My 4 year old macbook outperforms brand new Xeon V3s on single-core stuff
Your network is tiny, so it's hard to use more than one core
Increasing number intra_op_parallelism_threads above 1 can hurt performance for small work-loads. I've recently dealt with a network where setting all parallelism to 1 gave a 50% speed-up in average time.


fixes bower mismatch

bower mismatch      Version declared in the json (0.9.2) is different than the resolved one (0.9.3)

https://github.com/bower/bower.json-spec/tree/0b34d2bb0bdd4fa31fa9728f787f49e170e41f99#version

Intended to be used in the future when Bower gets a real registry where you can publish actual packages, but for now just leave it out.

Coverage remained the same at 100.0% when pulling c9f89b1b1a0eb544061236d0cb7387bd7d208dc3 on austinpray:patch-1 into 23b132ab7c5c92e4d091212493b3640015aaba32 on mariocasciaro:master.

well it makes sense I guess. it always bother me the need to keep the version inside bower.json up par to package.json as well, and usually get's left behind (like just happened). since bower uses the github tags, makes no sense to leave it there


KCE-80 Datamux does not exit cleanly

KCE-80

@mruedac Indeed, I am already updating the doc and adding one more example in a different ticket: KCE-91


Can't install on Laravel 10

Hello!
On laravel 10 composer require alexstewartja/laravel-attribute-observer results in
Problem 1
- alexstewartja/laravel-attribute-observer[1.0.0, ..., 1.0.2] require illuminate/contracts ^8.37 -> found illuminate/contracts[v8.37.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- alexstewartja/laravel-attribute-observer[1.0.3, ..., 1.2.1] require illuminate/contracts ^7.0|^8.0 -> found illuminate/contracts[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- alexstewartja/laravel-attribute-observer[1.3.0, ..., 1.4.3] require illuminate/contracts ^7.0|^8.0|^9.0 -> found illuminate/contracts[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.7] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires alexstewartja/laravel-attribute-observer * -> satisfiable by alexstewartja/laravel-attribute-observer[1.0.0, ..., 1.4.3].
On laravel 10 there is no  illuminate/contracts package, tried to install it, but nothing changed..
Can't figure out whats wrong, can you help me please ?

@rstanislav Issue resolved. v1.4.5 has been released with compatibility for Laravel v10.x


Response deserialization broken on master branch

I've been trying out the master branch because of #201, but unfortunately deserializing the Response signal contents is broken there:
◀ method_call: CreateSession [serial = 20]
  path = /org/freedesktop/portal/desktop
  sender = :1.393
  destination = org.freedesktop.portal.Desktop
  interface = org.freedesktop.portal.RemoteDesktop
  Data (a{sv}): (
       {'handle_token': ('s', 'ashpd_I0STYhaO0z'),
        'session_handle_token': ('s', 'ashpd_qvxZHxJk6z')},,
    )

▷ method_return:  [serial = 12403]
  Flags: 1 (no_reply_expected)
  destination = :1.393
  reply_serial = 20
  sender = :1.16
  Data (o): ('/org/freedesktop/portal/desktop/request/1_393/ashpd_I0STYhaO0z',)

▷ signal: Response [serial = 12404]
  Flags: 1 (no_reply_expected)
  path = /org/freedesktop/portal/desktop/request/1_393/ashpd_I0STYhaO0z
  interface = org.freedesktop.portal.Request
  destination = :1.393
  sender = :1.16
  Data (ua{sv}): (
       0,
       {'session_handle': ('s',
                           '/org/freedesktop/portal/desktop/session/1_393/ashpd_qvxZHxJk6z')},
    )

2024-05-19T18:44:59.575343Z  INFO ashpd::desktop::request: Received signal 'Response' on 'org.freedesktop.portal.Request'
Error: ZBus Error: invalid type: character `u`, expected `v`, `a` or `(`

It was apparently broken by https://github.com/bilelmoussaoui/ashpd/commit/7e754fb8ba601c635e7395e47aaefb28a836de54, if I revert it locally, everything works fine.

Seems like a zbus bug to me to be honest as the signature is ua{sv} and not (ua{sv})
The funny thing is that
        assert_eq!(
            <(ResponseType, HashMap<&str, Value<'_>>)>::signature(),
            Response::<()>::signature(),
        );

Passes, so the changes mentioned in the commit shouldn't affect things that much but somehow it does...

See https://github.com/bilelmoussaoui/ashpd/commit/595a9655f69164286d4e0074b908baabf1540469


Uncaught Error: tunneling socket could not be established, cause=connect ECONNREFUSED <IP_ADDRESS>:1080

[Enter steps to reproduce:]

...
...

Atom: 1.31.1 x64
Electron: 2.0.7
OS: Unknown Windows version
Thrown From: Atom Core
Stack Trace
Uncaught Error: tunneling socket could not be established, cause=connect ECONNREFUSED <IP_ADDRESS>:1080
At internal/streams/legacy.js:59

Error: tunneling socket could not be established, cause=connect ECONNREFUSED <IP_ADDRESS>:1080
    at ClientRequest.onError (/app.asar/node_modules/tunnel-agent/index.js:177:17)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Commands
     -4:07.1.0 core:cut (input.hidden-input)
     -4:05.1.0 core:paste (input.hidden-input)
  2x -4:04.6.0 core:move-right (input.hidden-input)
     -4:03.7.0 core:backspace (input.hidden-input)
     -4:02.6.0 core:save (input.hidden-input)
  7x -2:29.4.0 core:backspace (input.hidden-input)
     -2:27.1.0 core:save (input.hidden-input)

Non-Core Packages
atom-beautify 0.33.2
atom-runner 2.7.1
autocomplete-paths 2.12.2
docblockr 0.13.7
emmet 2.4.3
file-icons 2.1.25
minimap 4.29.9
platformio-ide-terminal 2.8.4
simplified-chinese-menu 5.3.5

Thanks for the report! Are you using a network proxy? This seems like it could be a temporary network issue, please try again later and see if you continue getting the same error.


requirements issue

Hello, I would like to run your minimal code, but I need help with the environment setup. Could you provide the exact version of the library?

did you have issues when installing pip install -r requirements.txt? If so can you link to the issue

I've tried using Colab, referred to "installation details", and even attempted pip install -r requirements.txt, but the code still doesn't run smoothly. When I downgraded the torch version to 1.7.1, I got the msg that the bottleneck's size didn't match.

I solved it by checking the requirements/environment.yaml. Thank you for your interest.


Update to Go 1.11.2

Includes minor changes to go fmt and fixes for some errors that
the updated linter picked up.
Signed-off-by: Justin Cormack<EMAIL_ADDRESS>

Updated to 1.11.2

closing in vavour of #1416


Feature/149 resolution parameter

This is basically a copy of the #157 Pull request, done by @akshaykolte, with some issues fixed.

@akshaykolte Are you fine being referenced in the Changelog?

No problem @brototyp .


Incorporate generators into README

https://github.com/github/actionview-component/pull/106 introduced a generator for components. Might we update the main README to incorporate this new ability?

Maybe you could take this one @vinistock?

That makes perfect sense. We should add example usage to the README. I'll put together a PR and ask feedback on the copy.


can any body say me how to run this code and where can i see output????

Version
Tell us which versions you are using:

tcomb-form v0.8.?
react v0.14.?

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Steps to reproduce

Stack trace and console log
Hint: it would help a lot if you enable the debugger ("Pause on exceptions" in the "Source" panel of Chrome dev tools) and spot the place where the error is thrown

Your question is too generic. In the future, consider asking questions like this in StackOverflow, thanks.


is bookbaby is Vulnerable or not ?

Bookbaby
I found a subdomain with CNAME has records to  Bookbaby records and doesn't belong to the main Subdomain Records
After I dig A making sure that it's possible to Subdomain Takeover but is that Really Vulnerable or Not ?

Have you tried / tested it? The intention of this repository is a documentation of knowledge, but not a support desk where this is verified for you.


PCA scores plot

Color of samples that have no metadata mapping is black and first group is also black.
Maybe we should just always add a dataset for missing values and then the first group will always be non black

Good idea!
Lets avoid black and white completely in all stats plots, especially scores and box plots. If the dataset color is black, you cant see the median. Same with white in dark mode.

My idea would have been to use black/white if the metadata mapping is missing in the scores plot.

Then you still end up with the color problem in the boxplot

Maybe we could assign colors to each group within a column. Similar to the raw data files.
Default may be in alphabetical order. Then its always the same in all plots.

box plot legend says null when no group is selected


Issue with transactions and commits on loading of DayRecipe Class

The DayRecipe class holds the recipe which is planned for a given date + status information.
there is a number of actions which Updates the DayRecipe records, and should return the updated version. However they return the version from before the update.
Hence it seems something with transactions or commits is going wrong.
Example1:
When the root URL is opened for a date range, which is new/ not loaded before, the controller will initiate the DayRecipe Records.
These will have recipe NULL.
Next the controller method will call the fuction to schedule dinners. This will ensure Recipe != null and status =1
After this action, the controller will find the DayRecipe's and pass them to the model for the frontend.
However, what is passed is recipe NULL, so the inital version.
After a refresh, the creation and planning steps will be skipped, and now it returns the correct recipe.
Example 2:
If a DayRecipe has status = 1 and Recipe != null.
The suggested recipe can be accepted (status =2) by an API PUT call to:
localhost:8080/api/v1/dayrecipe/accept/{ID}
(In class) DayRecipeRestControllerV1
This will update the status to 2, and return the record.
But here again, it returns the Pre-updated record instead of the actual record.

Closed by not using the custom Query in the Repository, but rather updating the values using the setter methods and calling save()


Push stack on another stack

Is there a way to to push a new stack onto an already existing stack navigator -- meaning have the stack as a view for a route?
I have it set up like this
return StackNavigator({
   Home: {screen: HomeView},
   Settings: {screen: SettingsStack}
})

where SettingsStack is
return StackNavigator({
   MainSettings: {screen: SettingsView}
})

And it is telling me that it is converting circular structure to JSON

You need to do the following for your settings StackNavigator:
const SettingsStack = StackNavigator({
    MainSettings: {screen: SettingsView}
})

export default class Settings extends Component {
  render() {
    return <SettingsStack/>
  }
}

and then the parent StackNavigator should be like so:
return StackNavigator({
   Home: {screen: HomeView},
   Settings: {screen: Settings}
})

Cool... thanks. I will give that a shot

Yes, you can (and should) do what you wrote above. You don't need to wrap it in a component.

@satya164 Without wrapping it, I am getting an error

what's the error?

As I wrote above, converting circular structure to JSON

Can you post your code and stacktrace for error? It's not possible to tell why the error is happening without a stacktrace

Wrapping it in a component does in fact work. However, it then renders two headers

@satya164

This is a little late but @stief510, were you passing params in your navigate() action?
This error may be complaining about the type of param you were passing.

This is very peculiar. I banged my head on the wall with this for two hours (with beta 11).
Problem seems to be at general navigationOptions vs screen specific navigationOptions. I had one screen without screen specific options and I got this error. After adding some empty options, things started to work... 😠

I'm seeing the same thing @zvona, going from a screen which defines headerLeft to one which doesn't (for example) is crashing my app.

@AndrewIngram +1,
Have you found a solution for that?

I'm also having the same issue when going from headerLeft - does anyone have any fixes for this?


[5.1] Backport pagination fix

@GrahamCampbell When will this be in a tagged release?

Soon I think.