E2E tests failing on kind with the TLS / missing certs

The resources are not only not becoming ready, they are not even being reconciled. However, this doesn't seem to be happening locally when I run these.
One example of a failing run:
https://github.com/knative-sandbox/eventing-rabbitmq/pull/152/checks?check_run_id=1355961403
2020-11-05T01:36:52.2576105Z + echo '===================== Brokers =============================='
2020-11-05T01:36:52.2576558Z ===================== Brokers ==============================
2020-11-05T01:36:52.2579031Z + kubectl get broker --all-namespaces=true -oyaml
2020-11-05T01:36:52.4540215Z apiVersion: v1
2020-11-05T01:36:52.4540494Z items:
2020-11-05T01:36:52.4541426Z - apiVersion: eventing.knative.dev/v1
2020-11-05T01:36:52.4541825Z   kind: Broker
2020-11-05T01:36:52.4542066Z   metadata:
2020-11-05T01:36:52.4542327Z     annotations:
2020-11-05T01:36:52.4542799Z       eventing.knative.dev/broker.class: RabbitMQBroker
2020-11-05T01:36:52.4543574Z       eventing.knative.dev/creator: kubernetes-admin
2020-11-05T01:36:52.4544339Z       eventing.knative.dev/lastModifier: kubernetes-admin
2020-11-05T01:36:52.4545364Z     creationTimestamp: "2020-11-05T01:32:20Z"
2020-11-05T01:36:52.4545703Z     generation: 1
2020-11-05T01:36:52.4546183Z     name: broker-direct-jdiihoxq
2020-11-05T01:36:52.4546714Z     namespace: rigging-jhnnbhvq
2020-11-05T01:36:52.4547083Z     resourceVersion: "9723"
2020-11-05T01:36:52.4547936Z     selfLink: /apis/eventing.knative.dev/v1/namespaces/rigging-jhnnbhvq/brokers/broker-direct-jdiihoxq
2020-11-05T01:36:52.4549064Z     uid: 0a87398b-710d-4847-9e23-9c6ea64806a0
2020-11-05T01:36:52.4549591Z   spec:
2020-11-05T01:36:52.4549819Z     config:
2020-11-05T01:36:52.4550300Z       apiVersion: rabbitmq.com/v1beta1
2020-11-05T01:36:52.4550735Z       kind: RabbitmqCluster
2020-11-05T01:36:52.4551090Z       name: rabbitmqc
2020-11-05T01:36:52.4551627Z       namespace: rigging-jhnnbhvq
2020-11-05T01:36:52.4551981Z   status:
2020-11-05T01:36:52.4552238Z     address: {}
2020-11-05T01:36:52.4552474Z kind: List
2020-11-05T01:36:52.4552730Z metadata:
2020-11-05T01:36:52.4553054Z   resourceVersion: ""
2020-11-05T01:36:52.4553387Z   selfLink: ""
2020-11-05T01:36:52.4568722Z + echo '===================== Triggers ============================='
2020-11-05T01:36:52.4569307Z ===================== Triggers =============================
2020-11-05T01:36:52.4570182Z + kubectl get trigger --all-namespaces=true -oyaml
2020-11-05T01:36:52.5412882Z apiVersion: v1
2020-11-05T01:36:52.5413737Z items:
2020-11-05T01:36:52.5415633Z - apiVersion: eventing.knative.dev/v1
2020-11-05T01:36:52.5416238Z   kind: Trigger
2020-11-05T01:36:52.5417104Z   metadata:
2020-11-05T01:36:52.5417402Z     annotations:
2020-11-05T01:36:52.5418138Z       eventing.knative.dev/creator: kubernetes-admin
2020-11-05T01:36:52.5419030Z       eventing.knative.dev/lastModifier: kubernetes-admin
2020-11-05T01:36:52.5419798Z     creationTimestamp: "2020-11-05T01:32:21Z"
2020-11-05T01:36:52.5420178Z     generation: 1
2020-11-05T01:36:52.5420460Z     labels:
2020-11-05T01:36:52.5421138Z       eventing.knative.dev/broker: broker-direct-jdiihoxq
2020-11-05T01:36:52.5421950Z     name: broker-direct-puluaekl
2020-11-05T01:36:52.5422485Z     namespace: rigging-jhnnbhvq
2020-11-05T01:36:52.5422840Z     resourceVersion: "9754"
2020-11-05T01:36:52.5423704Z     selfLink: /apis/eventing.knative.dev/v1/namespaces/rigging-jhnnbhvq/triggers/broker-direct-puluaekl
2020-11-05T01:36:52.5424605Z     uid: bc98ed37-ee32-4721-8073-69b9a7986bde
2020-11-05T01:36:52.5424946Z   spec:
2020-11-05T01:36:52.5425395Z     broker: broker-direct-jdiihoxq
2020-11-05T01:36:52.5425745Z     filter: {}
2020-11-05T01:36:52.5425987Z     subscriber:
2020-11-05T01:36:52.5426218Z       ref:
2020-11-05T01:36:52.5426447Z         apiVersion: v1
2020-11-05T01:36:52.5426712Z         kind: Service
2020-11-05T01:36:52.5426970Z         name: recorder
2020-11-05T01:36:52.5427417Z         namespace: rigging-jhnnbhvq
2020-11-05T01:36:52.5427726Z   status: {}

2020-11-05T01:36:55.1770743Z {"level":"error","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:526","msg":"Reconcile error","commit":"9f3fb3f","error":"secret \"eventing-webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:526\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:512\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:449"}
2020-11-05T01:36:55.1774550Z {"level":"info","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:513","msg":"Reconcile failed. Time taken: 38.101µs","commit":"9f3fb3f","knative.dev/traceid":"db27fbee-de34-4067-9ba9-e7a075ca9801","knative.dev/key":"containersources.sources.knative.dev"}
2020-11-05T01:36:55.1778651Z {"level":"error","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:526","msg":"Reconcile error","commit":"9f3fb3f","error":"secret \"eventing-webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:526\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:512\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:449"}
2020-11-05T01:36:55.1782317Z {"level":"info","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:513","msg":"Reconcile failed. Time taken: 25.601µs","commit":"9f3fb3f","knative.dev/traceid":"3beba17d-eda3-4061-b850-251a3793890f","knative.dev/key":"brokers.eventing.knative.dev"}
2020-11-05T01:36:55.1786263Z {"level":"error","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:526","msg":"Reconcile error","commit":"9f3fb3f","error":"secret \"eventing-webhook-certs\" is missing \"ca-cert.pem\" key","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:526\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:512\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20200812224206-44c860147a87/controller/controller.go:449"}
2020-11-05T01:36:55.1790023Z {"level":"info","ts":"2020-11-05T01:18:13.522Z","logger":"eventing-webhook.ConversionWebhook","caller":"controller/controller.go:513","msg":"Reconcile failed. Time taken: 38.402µs","commit":"9f3fb3f","knative.dev/traceid":"d1cb9876-7a19-43d4-aa3b-6b7783753361","knative.dev/key":"sequences.flows.knative.dev"}

And there's bunch of these in the logs as well:
2020-11-05T01:36:55.2612746Z 2020/11/05 01:18:47 http: TLS handshake error from <IP_ADDRESS>:59342: server key missing
2020-11-05T01:36:55.2613415Z 2020/11/05 01:18:48 http: TLS handshake error from <IP_ADDRESS>:59348: server key missing
2020-11-05T01:36:55.2613874Z 2020/11/05 01:18:49 http: TLS handshake error from <IP_ADDRESS>:59356: server key missing
2020-11-05T01:36:55.2614316Z 2020/11/05 01:18:50 http: TLS handshake error from <IP_ADDRESS>:59372: server key missing
2020-11-05T01:36:55.2614754Z 2020/11/05 01:18:51 http: TLS handshake error from <IP_ADDRESS>:59380: server key missing
2020-11-05T01:36:55.2615190Z 2020/11/05 01:18:52 http: TLS handshake error from <IP_ADDRESS>:59388: server key missing
2020-11-05T01:36:55.2615630Z 2020/11/05 01:18:53 http: TLS handshake error from <IP_ADDRESS>:59394: server key missing
2020-11-05T01:36:55.2616065Z 2020/11/05 01:18:54 http: TLS handshake error from <IP_ADDRESS>:59404: server key missing

Ok so looks like this is probably because we were using 0.17 version of eventing, which had a bug. Updated in the dot releases, but bumped to 0.18.4 to pick up all the fixes. I suppose in the future we could also have matrix tests for these as well so we test various versions of eventing.
https://github.com/knative/eventing/issues/4165


TypeError: undefined is not a function, webpack/node_modules/tapable/lib/Tapable.js:164

Im trying to configure webpack without success in case that im trying to add aliasing for angularjs submodules.
When I put out resolve, it works properly. The problem is that I need alias:
...
resolve: {
   ...
},
...

Here is configuration:
var webpack = require('webpack'),
    ngPlugin = require('angular-webpack-plugin'),
    path = require('path');

module.exports = {
    resolve: {
        root: [path.join(__dirname, "src", "vendor")],
        alias: {
            "ngSanitize": "angular-sanitize"
        }
    },
    entry: {
        'entry' : './src/js/module/Application'
    },
    output: {
        path: "./src/webpack",
        filename: "bundle.js"
    },
    plugins: [
        new webpack.ResolverPlugin([
            new webpack.ResolverPlugin.DirectoryDescriptionFilePlugin("bower.json", ["main"]),
            ["normal", "loader"]
        ]),
        new ngPlugin()
    ]
};

Directory structure is:
/
/webpack.conf.js
/src/js
/src/js/module/
/src/js/module/Application.js
/src/vendor
/src/webpack

It was my fault. Wrong syntax.

    plugins: [
        new webpack.ResolverPlugin(
            [new webpack.ResolverPlugin.DirectoryDescriptionFilePlugin("bower.json", ["main"])],
            ["normal", "loader"]
        ),
        new ngPlugin()
    ]


TM1Service doesn't provide possibility to retain live connection

Describe the bug
Imagine a situation when connection is already established from outside of Python with known SessionID and TM1Service object is constructed with this SessionID.
Currently TM1Service implements a cleanup of connection in its exit method, but for the approach described above the cleanup will close the connection. It would be nice to keep the connection live for instances like this.
To Reproduce
Allocate SessionID (token) outside Python, use it to initiate TM1Service. After TM1Service is discarded, the session is closed and SessionID can't be used anymore.
Expected behavior
A new switch in TM1Service configuration to retain connection.
Version
TM1py 1.3.1
TM1 Server Version: 11.6.00000.14
Additional context
NA

PS: this is not bug per se, but rather a feature request. As a temporary solution I can define a new descendant of TM1Service class that will redefine exit method by own implementation.

Hi @pbuncik ,
We have a similar feature already implemented. Perhaps what you need intend to do can be accomplished with the save_to_file and restore_from_file methods
Here is a sample how to use them:
https://github.com/cubewise-code/tm1py-samples/blob/master/Administration/session_persist.py
https://github.com/cubewise-code/tm1py-samples/blob/master/Administration/session_reuse.py
does it work ?
Cheers,
Marius

Hi @MariusWirtz ,
I'm not convinced the approach proposed in session_persist.py would work. Here is why:
The idea is:

Open TM1 session outside TM1py in a web application (running on a web server). This is interactive application that uses the connection to query TM1 database frequently and also maintains the connection open for given user until the user logs out.
At some point of time we will launch a tool written in Python and utilizing TM1py.
The tool will reuse session open in step 1) by using session ID token that is transferred from the web application to the tool.
After the tool is finished it must retain the session open otherwise the user would experience logout from TM1 and would have to login again from within the web application again - this is unwanted behavior.

This approach is briefly what your second example is demonstrating - the session token is reused to hook-up to already connected session.
First example is demonstrating how to serialize the session into a file, but it doesn't solve problem with logging of the session during __exit__ method call when TM1Session or RESTService objects are destroyed by garbage collector. At this point I need to avoid the call to logout the session to leave it open for the web application. The user should not be logged off and the call to the tool should be transparent to the user.
The issue I want

Hi @pbuncik ,
sorry for the late response.
What's the advantage of this new parameter retain_connection over instantiating the TM1Service without the with statement ?
The way I see this, in order to not invalidate the session, you could as well write it like this:

from TM1py import TM1Service

ADDRESS = '<IP_ADDRESS>'
PORT = 12354
USER = 'admin'
PASSWORD = 'apple'
SSL = True

tm1 = TM1Service(address=ADDRESS, port=PORT, user=USER, password=PASSWORD, ssl=SSL)

elements = tm1.dimensions.hierarchies.elements.get_element_names(
    dimension_name="d1",
    hierarchy_name="d1")

for element in elements:
    print(element)

Hi @MariusWirtz
My understanding of the use case is  we want to call tm1py from another application to do a specific task and we want to get the existing session token the other application and use that to authenticate the tm1py session rather than having the user need to re-enter credentials. This part we can already do. But when tm1py is finished we don’t want the session token invalidated as this leaves the original calling application without a connection. When tm1py exits we don’t want it to log out or close any sessions.
From: Marius Wirtz<EMAIL_ADDRESS>Sent: Sunday, 24 November 2019 21:13
To: cubewise-code/tm1py<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [cubewise-code/tm1py] TM1Service doesn't provide possibility to retain live connection (#190)
Hi @pbuncikhttps://github.com/pbuncik ,
sorry for the late response.
What's the advantage of this new parameter retain_connection over instantiating the TM1Service without the with statement ?
The way I see this, in order to not invalidate the session, you could as well write it like this:
from TM1py import TM1Service
ADDRESS = '<IP_ADDRESS>'
PORT = 12354
USER = 'admin'
PASSWORD = 'apple'
SSL = True
tm1 = TM1Service(address=ADDRESS, port=PORT, user=USER, password=PASSWORD, ssl=SSL)
elements = tm1.dimensions.hierarchies.elements.get_element_names(
dimension_name="d1",

hierarchy_name="d1")

for element in elements:
print(element)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/issues/190?email_source=notifications&email_token=AHALZBEUMM3W3ZZGBT3SEGLQVLN4TA5CNFSM4JNYQDPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFATY2Q#issuecomment-557923434, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHALZBHOOSUGT6DOI35HIIDQVLN4TANCNFSM4JNYQDPA.

Hi @MariusWirtz - got your point, which is legit. When proposing this solution I was considering more robust approach to it as I thought it should be systemic solution embedded into the library rather than particular solution in one's code.
Should we use the solution you have proposed?

Petr, you can do this already, tm1service and restservice take key word arguments. When you initialize a TM1 service object just pass it a session_id instead of a user name and password.
https://github.com/cubewise-code/tm1py/blob/fbc6393884ad140fea25c479930a84bd881c98d2/TM1py/Services/RESTService.py#L117
Ryan Clapp
AWS Business Systems
Sr. Manager
Sent from my mobile device
On Nov 25, 2019 12:50 AM, Petr Buncik<EMAIL_ADDRESS>wrote:
Hi @MariusWirtzhttps://github.com/MariusWirtz - got your point, which is legit. When proposing this solution I was considering more robust approach to it as I thought it should be systemic solution embedded into the library rather than particular solution in one's code.
Should we use the solution you have proposed?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/issues/190?email_source=notifications&email_token=AEK7GZV6VGWO4U4CSIVPQHTQVOGURA5CNFSM4JNYQDPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFBTNPQ#issuecomment-558053054, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEK7GZRZD2KODIHMKAI6CT3QVOGURANCNFSM4JNYQDPA.


Debug MaxInputBufferLength failures on Travis OSX

PR to debug MaxInputBufferLength failures on Travis OSX.  Fixes will be rolled into #912.

Delete? Or still investigating?


Fixing incorrect closing tag in comments

identify: to identify:

Thanks!


Device selection should use device name, not unique_id

UI version
1.0.57
Your idea
The Joulescope UI's Device Control widget has a Device name setting.  This name should be used instead of the unique_id everywhere that device selection occurs.  Some places include

Accumulator widget.
Multimeter widget
Value widget
Waveform widget's WaveformSourceWidget

Available in 1.0.59


Custom event system and Action management

Q
A

Bug fix?
no

New feature?
yes

Needs wipe?
no

Fixes
#413 #414

Description:
Event system that allows to subscribe to mission events, foundation for more extensible framework.
Content:

[x] Local events
[x] Global (remote) events
[x] Add events where appropriate
[x] Create spreadsheet with available events and their arguments as initial documentation  Gist with examples should be enough for now

Tested on:

[x] Local MP Vanilla
[x] Local MP ACE
[x] Dedicated MP Vanilla
[x] Dedicated MP ACE

I'm closing this for now.
I will use this PR as base for 0.97 translation. I will keep translation branch on my fork until all strings in 0.97 are ready.
You can expect that polish translation will be available around 0.97 release ("done when its done").


settings: Move deactivate account button under "User settings".

This moves the deactivate account which was previously placed under
"SETTINGS / YOUR ACCOUNT" -> "Deactivate account" to "SETTINGS / YOUR
ACCOUNT" -> "User settings" for making it more visible.

@timabbott FYI.

Thanks @shubhamdhama! I think it's a bit too prominent here; what do you think of moving it below the User avatar?
I think in that case we can also keep the heading. So "Deactivate account" as a heading, followed by the button.

The other option to consider would be to keep the position in this PR make the button more of a normal-size button.

@shubhamdhama can you try doing the smaller button approach I suggested?

Updated the button with medium size:
Is this looks right position wise or it needs some CSS tweaks?


Sending failed event to the cli

Sending failed event to the cli

No test updates here?

No test updates here?

Yes, because there is no meaningfull test for this. Same as java sdk. So skipping this.


postgres INCLUDE clause non-key columns parsed as part of index

Bug description
Postgres has the ability to INCLUDE non-key columns in an index which allows the columns to be returned by the index scan without having to lookup on the table.
https://www.postgresql.org/docs/11/sql-createindex.html
Currently, prisma migrate dev (or introspection) thinks the non-key columns in the INCLUDE clause are key columns that are part of the index. Instead it should exclude non-key columns when checking for schema drift
How to reproduce

Clone https://github.com/awinograd/prisma-include-clause-bug
yarn install
yarn run dev:database (runs docker database instance compatible with .env)
prisma migrate dev

Expected behavior
Should apply migration cleanly without wanting to drop/regenerate index on the user.email column
Prisma information
https://github.com/awinograd/prisma-include-clause-bug
Environment & setup

OS: any
Database: PostgreSQL
Node.js version: 14.16.0

Prisma Version
Environment variables loaded from .env
prisma               : 2.28.0
@prisma/client       : 2.28.0
Current platform     : darwin
Query Engine         : query-engine 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 89facabd0366f63911d089156a7a70125bfbcd27
Studio               : 0.417.0

Prisma currently does not support INCLUDE in indexes - that leads to this problem. Prisma does not "ignore" that part, as the index indeed is different from what Prisma Migrate would create on an empty database.
The real solution here is to actually add support for this kind of index to Prisma. Can you please open a feature request issue? Thanks.

Thanks for your reply @janpio. Sure I'll close this in favor of a feature request


Add favicon

[ ] Add favicon as dependency in makefile compile
[ ] Generate favicons for ios and msapplication


Consider account requirements on a per suite/test basis

Problems

Some suites, for example eventsApi.test.ts, require that the active account selected in the CLI is a Teams or Business account
We may want to test behaviour when there is no active account selected in the CLI

In both of these instances we encounter problems because jest.setup.ts forces the suites to sign in as the account configured in the OP_ACCOUNT env variable. The configured account may not be a Teams or Business account, and forcing this sign in precludes us from testing signed out behaviour.
Thoughts

Can we create helpers for op signin and op signout that we use on a per suite/test basis to configure the CLI as we need it for the specific tests, and remove the setGlobalFlags call from jest.setup.ts?
Do we need separate env variables for each account type for testing functionality available only to specific account types? if so, how does this affect external contributors who cannot create 1Password accounts at will?

Closing as wontfix for now while we prioritize work.


make api.add_paths() exception handler work in python 2.7

The re-raising of the exception in this version fails in python 2.7raising an AttributeError since  "with_traceback" is know known.
using the  ei.__traceback__ = tb and than just raising ie again works fine in Python 2.7.
Note: I did not test this in Python 3, but I assume this should work just fine there to !

Could you please update the test and verify if the AttributeError that is being thrown is the correct one (just check if the correct missing method is in the exception message)?

I looked into it, and found that indeed the original code raises an AttributeError in python 2.x as expected in the test, however it is not the Attribute Error you expected. I will change the test  (and the code).
However wonder with module you would expect in the test. The api loading fails because of in deep ImportError in fakeapi.module_with_error it would be good to see that error.

Please also fix the flake8 formatting errors.

flake 8 should be OK now

Still flake8 does not pass. Please also review the previous comments and I will be happy to move your PR forward.

width the simple setup for the example:

import connexion
app = connexion.App(name, specification_dir='swagger/')
app.add_api('api.yaml')
app.run(port=8080)

And the envoronment show, and i have the following error message:

(env) iMac:miserver$ pip freeze
connexion==1.0.76
Flask==0.10.1
functools32==3.2.3.post2
httpie==0.9.3
itsdangerous==0.24
Jinja2==2.8
jsonschema==2.5.1
MarkupSafe==0.23
pathlib==1.0.1
Pygments==2.1.3
PyYAML==3.11
requests==2.9.1
six==1.10.0
strict-rfc3339==0.6
swagger-spec-validator==2.0.2
Werkzeug==0.11.4

(env) iMac:miserver$ python api.py
No handlers could be found for logger "connexion.api"
Traceback (most recent call last):
File "api.py", line 4, in
app.add_api('api.yaml')
File "~/.pyenv/versions/miserver/lib/python2.7/site-packages/connexion/app.py", line 133, in add_api
debug=self.debug)
File "~/.pyenv/versions/miserver/lib/python2.7/site-packages/connexion/api.py", line 122, in init
self.add_paths()
File "~/.pyenv/versions/miserver/lib/python2.7/site-packages/connexion/api.py", line 187, in add_paths
raise ei.with_traceback(tb)
AttributeError: 'exceptions.AttributeError' object has no attribute 'with_traceback'

I think this is the same issue you are talking about
¿How to solve it?
Thanks in advance

@srlopez That's exactly the problem this PR is trying to solve. The problem is that one of your operationId is pointing to a inexistent function in your python path. The actual error is being shadowed by this AttributeError with the with_traceback.
I am hopping to hear from @TNGPS, if not I will move this PR forward myself.

Coverage increased (+0.6%) to 99.415% when pulling afed9ade06b9a405d4bea9449ba574b0f225dd00 on TNGPS:patch-1 into 652088f3a47d3e5f6b9405f3c975f965e2ee1f9e on zalando:master.

Looks like all checks are OK now, this should do it.
Sorry for the delay, had a view deadlines to catch the last view weeks.

@TNGPS Sorry, this issue was solved by the PR #186. We needed a simple implementation and it was getting more complicated here.
For your improvement I will list the problems I had with this PR:

Too many commits to handle a small change; How to do better? When sending a PR try to squash the commits that do not add any useful information or concise block of code that would make it easier to understand the code.
Obscure comments around the code and commented code. Commented code is dead code and just confuse whoever is trying to understand the codebase.
Long iteration loops. Do not need to work immediately since we are working usually in our free time and in things we care, but it was also an issue here.

I appreciate your investment in time and effort here and I hope to see more PR's from you in the future.

thanks for the time taken anyways. Let me point out that this was indended to be a single line change, one commit and all should be fine, however the Python2 vs Python3 made this a bit more complicated than I hoped.  What we can take away from this (as I see it) that the test for the orginal change, did fail to see the problem in python 2 by not failing the test.
Changing the test to prevent future problems here may still be a good idee ?


feat: repo submit button

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

repo submission handler function is added, and tried adding existing repos like freeCodeCamp or opensauced hot repo, but it's getting me back 500 or 404 response.

Sign in.
Click User Emoticon at top right corner, and click submit repo.
Type in repo URL (I tried putting freeCodeCamp's repo & OpenSauced/hot repo)
API call returns an error with 500 or 404 response.

Related Tickets & Documents

Resolves #352
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[x] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Hi @janie-lee-developer I'm going to make a couple of minor edits to this PR title/description so it goes smoothly out of draft later.

repo submission handler function is added, and tried adding existing repos like freeCodeCamp or opensauced hot repo, but it's getting me back 500 or 404 response.

Looking at your description. Can you provide more details on this or Loom recording? I believe we had a chat on this, but trying to catch up on the context.

I tested the deploy preview as follows:

Signed in as GitHub user "mtfoley"
clicked avatar in upper right, chose "submit a repo" option
typed in "https://github.com/httpie/httpie" for text field
Clicked submit
No visual feedback (e.g. toast message or otherwise), but I checked on Fetch XHR:
Request:
PUT https://beta.api.opensauced.pizza/v1/repos/httpie/httpie/submit
Response Body:

{
"repo_id":"3544424",
"user_id":"3792749",
"deleted_at":null,
"id":"5",
"is_accepted":false,
"created_at":"2022-11-03T17:31:14.321Z",
"updated_at":"2022-11-03T17:31:14.321Z"
}

I will also note that submitting with the text field filled with "httpie/httpie", it seemed to make an attempt to submit and came back with an error message of an invalid repo.

As per our conversation with Ted, submitting a new repository is not workable at this moment, because we would need to implement a way to have an access to millions of repos out there in Github. Only repos that are already in the supabase db from last version of the app can be accessible.

Going to take this one over. We do not need to index millions of repos, but instead, we will queue repos for indexing here. https://github.com/open-sauced/open-sauced-goals

Closing in favor of #408


push media dynamically

hi again
since i,m getting my video and images media urls separately from server i have to push them in Media array as the response comes from the server.
but for example when i push second item after first item, i have still one media in gallery view.(although media array has two members ). i need to add medias dynamically when ever I needed to.
thanks

Great catch, I will try to update this tomorrow with observable, trigger an event data changed for example, I will keep you up to date

Should be fixed now @elibushehri can you confirm ?

@RLoris Yeah that's ok, Perfect work. Good Luck


Update idb2pat.py to Python3

Updated idb2pat.py for Python3 after IDA 8.0 Officially ended support for Python 2.x.  Took the liberty of also implementing the TODO for using an enum for config modes.

Use built-in range from py3 stdlib that can handle larger sizes
Add missing import for os
Convert Config Modes to Enumeration
Simplify output file logic and convert str args to bytes for py3

No problem. Thanks for the useful script!

Thank you!


jQuery loads page slow and hence encounter improper state

It happen when the page is loaded slowly because of background processes like audio file download.
Solution : Hide pop-boxes in CSS rather than jQuery because CSS will load fast.

Solved here https://github.com/fossasia/open-event-webapp/pull/366

Closing it, its done!!!


3.0.0: Questions about the structure of the app

After getting to know more about the boilerplate I was wondering about a few things:
Where should reducers & actions go which are not connected to any container?
I know this calls for an opinionated answer but it would be interesting to know how you would solve this. Is there maybe a reason why separate actions and reducers are not implemented in the example (except for the global state)?
Where would separate reducers be registered?
Independent from where I keep the code for them, the most reasonable location I found to register any separate reducers with the store is the function createReducer in app/reducers.js. Is that correct?
How about generators for these?
The generators are a great. Would you support generators for reducers and actions as well? I would happily try out creating these as PRs.

There shouldn't be any reducers/actions that aren't associated with any container, if they're global add them to the uppermost App! (more info)
I'd be interested to hear what sort of actions and reducers that you cannot put anywhere.

I was wondering about that while I was trying to implement an i18n reducer (together with actions) and it didn't seem to fit the directory structure.
I'm sure all reducers and actions fit in somewhere. Thanks for sharing the blog post. This makes things very clear and understandable. I guess it is fine that anything global goes into App. Just as the blogpost said, my opinion was influenced by other boilerplates/configurations which use global reducers and actions.

I totally understand, glad you found the blog post helpful – that reminds me to write something about the philosophy somewhere in the documentation! :+1:

I am also using appReducer and appSelector to be kind of kitchen sink for small things, like storing user preferences or information about app being online / offline. Works really well!

What about using ducks?

I have worked with  React Redux Universal Hot Example which uses ducks. See /src/redux/modules.
I found that starter kit/boilerplate to be very difficult to understand (could be just me). In contrast, I find the layout of this boilerplate example to be intuitive and easy to grasp.
I would advocate for maintaining the present layout.

I've read https://github.com/mxstbr/react-boilerplate/issues/27, and saw why this decision was took.


ui.Eval does not return a value

Grabbing HTML value from document via Eval returns no value. Not sure if this is a bug or I have bad HTML. I do not get any runtime errors.
My code
package main

import (
	"fmt"
	"net/url"

	"github.com/zserge/lorca"
)

var (
	ui1        lorca.UI
	HTML_entry string = `
<html>
    <body>
        <input hidden type="text" name="MYVAR" value="testVal">
        <input type="submit" onclick="golangfunc()"
    </body>
</html>
`
)

func main() {
	ui1, _ = lorca.New("data:text/html,"+url.PathEscape(HTML_entry), "", 480, 320)
	ui1.Bind("golangfunc", golangfunc)
	defer ui1.Close()
	<-ui1.Done()
}

func golangfunc() {
	htmlvar := ui1.Eval(`document.getElementsByName('MYVAR').value`).String()
	fmt.Println(htmlvar)
}

I dont think its with Eval , it probably the getElementsByName() is undefined , can you do getElementById and specify and Id to the the control in the dom

@vinchauhan I do need to get elements by name, I thought HTML5 has this & I'm not getting an error when using it, but it doesn't return any value either. As for the panic though, I had accidentally created a local var ui1 using := instead of = which caused the panic. However, I still don't have the MYVAR value.

@vinchauhan I do need to get it by name rather than ID. Is there another way of getting by name? I have an arbitrary number of input fields to work with & the HTML I'm working on is being generated. I also tried changing to getElementById just to test, but still no value coming through.

@cmdpwnd - I tested it last night but I didnt have any luck with the panic - Unfortunately I am unable to go get the package from the place I am at at the moment. I will check again tonight.
I am planning to use this package myself to give GUI to my cli based api testing tool.

@vinchauhan Yes, I corrected the panic err - sorry forgot to mention - just needed to change the ui1 declaration in main() from := to = since it was already declared globally. Let me know if you get anywhere with passing that value.

@cmdpwnd - It works with getElementById.
package main
import (
"fmt"
"net/url"
"github.com/zserge/lorca"

)
var (
ui1        lorca.UI
HTML_entry = `

`
)
func main() {
ui1, _ = lorca.New("data:text/html,"+url.PathEscape(HTML_entry), "", 480, 320)
ui1.Bind("golangfunc", golangfunc)
defer ui1.Close()
<-ui1.Done()
}
func golangfunc() {
htmlvar := ui1.Eval(document.getElementById('MYVAR').value).String()
fmt.Println(htmlvar)
}


[Bug] Malformed protocol detected: (:host github :repo "...")

What's wrong
When I try to grab xeft from sourcehut I am getting a malformed protocol detected error. This was working fine previously, but I just nuked my straight directory and recompiled everything when moving between diff emacsen. Strangely, this worked quite fine last week.

Version information

Emacs version: 29.0.60.
Operating system: OSX 13.2.1

Your recipe is inherting the :host keyword from the gnu-elpa-mirror for xeft.
Adding :host nil or :inherit nil should bypass the inheritance.

Test Case
(straight-bug-report
  :post-bootstrap
  (condition-case nil
      (straight-use-package
       '(xeft :repo "https://git.sr.ht/~casouri/xeft" :inherit nil :files
              (:defaults "*.h" "Makefile" "xapian-lite.cc")))
    (error
     (message "recipe source: %S"
              (straight-recipe-source "xeft")))))

Test run at: 2023-02-16 23:56:21
system-type: gnu/linux
straight-version: prerelease (HEAD -> develop, origin/develop) 3fa415c 2023-01-20
emacs-version: GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.36, cairo version 1.17.8) of 2023-02-06

Output
Bootstrapping straight.el...
Bootstrapping straight.el...done
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) 56a8b6c 2023-02-04
Cloning xeft...
Cloning xeft...done
Building xeft...
 Thank you !!! I was unaware of that switch in that case.


Merge projects

Merged Markdig.Xaml into Markdig.Wpf and removed shared projects. There are a few reasons to do this:

I want to include the library in https://github.com/github/VisualStudio - to do this we need to sign the assembly, and the easiest way to do that currently is to include the .csproj in the solution via submodule. I prefer to just include one project rather than 3.
Styles and Commands were included in both the projects, which would cause problems if both were consumed
There's not much in each assembly

Depends on #3

The original idea of keeping both assembly separated was to be able to have one version that is only Xaml (and possibly support Xaml Standard later on, although at the time it didn't know it would exist, but I had hope it would) and one that is WPF specific. Now that said, I have to admit that even the current Xaml version is kind of bound to the dialect used by WPF and might need more work/effort to fit into Xaml Standard.
Another reason was that I wanted to benchmark (once completed) the two solutions and see which one was better with small or rather large markdown documents. And depending on the result either drop one or add some documentation to explain which one to use in which case(s). There was also a possibility that some markdown support would be easier to do in one or the other.
The question to ask now is should we keep both solutions (is there a point of doing so) or drop one and stick to the other?
I'm not against merging the two in principle, but I would prefer other arguments that just it is more convenient to use in X or Y project. Ideally a user of the library only need one so even if the library is quite small, I always prefer to package the minimum required set of features into a library.
What do you think?

Yes, firstly I should apologise for dropping a PR like this without discussion!

The original idea of keeping both assembly separated was to be able to have one version that is only Xaml (and possibly support Xaml Standard later on, although at the time it didn't know it would exist, but I had hope it would) and one that is WPF specific. Now that said, I have to admit that even the current Xaml version is kind of bound to the dialect used by WPF and might need more work/effort to fit into Xaml Standard.

That makes sense, but assuming flow documents make it into the XAML standard etc etc, wouldn't both renderers be able to target XAML standard?

Another reason was that I wanted to benchmark (once completed) the two solutions and see which one was better with small or rather large markdown documents.

TBH I can't see a case where outputting XAML to parse the XAML to create the objects would be quicker than just creating the objects?

The question to ask now is should we keep both solutions (is there a point of doing so) or drop one and stick to the other?

I guess one utility of the XAML renderer would be for creating XPS documents? I'm not sure how many people would want to do that however, and you can always serialize the output of the WPF renderer to get the same results.

I'm not against merging the two in principle, but I would prefer other arguments that just it is more convenient to use in X or Y project. Ideally a user of the library only need one so even if the library is quite small, I always prefer to package the minimum required set of features into a library.

I think the smoking gun here is that if you include both libraries, you will get a duplicate definition of Styles and Commands. The way to fix that is to either have a base assembly that contains the shared types, to have 2 sets of styles and commands in different namespaces, or to merge the assemblies. To me the last option makes the most sense.

Let's merge the two projects together as you said. It will be easier to package into a single NuGet after all. Anyone interested into only one part can always fork and extract what they need, per the MIT license.
I'll do that after #3 is merged.


pills in user input of the past should have same hover & click color changes

Testing #229436
Look at the 2 pills rendered here (the one in the previous model response and the one in my next question)

Steps:

hover over the top one
hover over the bottom one
🐛 the bottom has no hover feedback (background doesn't get darker)
🐛 the top one has a tooltip of src/indexes.ts the bottom has /workspaces/vscode-toolstest/src/indexes.ts

Also

click the top one
click the bottom one
🐛  the bottom one has no click feedback (text doesn't change blue)

They should have consistent behavior.

Had the same idea: #228993
Does feel inconsistent right now


"resourceGroupName" should satisfy the constraint - "Pattern": /^[-w._()]+[^.]$/

Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: "resourceGroupName" should satisfy the constraint - "Pattern": /^[-w._()]+[^.]$/
Version: 0.15.0
OS: darwin
Product: Visual Studio Code
Product Version: 1.37.1
Language: ja

Call Stack
WebApps.V [as _getConfiguration] extension.bundle.js:262:1531359
module.exports.e.exports.getConfiguration.Promise extension.bundle.js:262:2795056
WebApps.getConfiguration extension.bundle.js:262:2795034
SiteClient.<anonymous> extension.bundle.js:332:362597
module.exports.n extension.bundle.js:332:359717
module.exports.n extension.bundle.js:332:359494
SiteClient.getSiteConfig extension.bundle.js:332:362420
Object.<anonymous> extension.bundle.js:157:229903
o extension.bundle.js:157:228103

Hi @kataday,
Could you provide repro steps?  What name did you use for the resource group?

Hi @nturinski,
I'm sorry...,
When I checked the name of the resource group that I created, it contained Japanese.
Close because there is no problem.


Make sure nightly pyarrow is installed in upstream CI build

pyarrow on conda-forge recently had a packaging refactor and now there's a pyarrow-core package we also need to account for in our upstream CI build. This PR makes sure we're able to install the latest nightly version of pyarrow.

Going to merge this in to get the upstream build running again. Happy to address any comments in a follow-up PR


Implement subscription duplication prevention

Related: https://praekelt.atlassian.net/browse/NDOH-127

Fixed in other issues


Sentence text type identification using FCGEC-Joint

Hello, I have finished  the error correction according to the steps you provided, but now I want to predict the error type identification for every text at the same time. Can I use FCGEC-Joint  and get the desired result  by changing some params? If so could you please give me an example?Thank you very much.

Hi,
The main code in our repository is for Error Correction task. Since for the two sub-tasks of error detection and error type identification, we only utilized the simplest pre-trained model with the fully connected layers for fine-tuning, we did not provide the code for this part directly in the repository.
However, you can refer to the code for type identification in the TaggerModelTTI class of the tagger_model.py file.


0.1.18 -> 0.4.1 is a major change

This error kept showing for npm install -g now@canary for Now CLI:

This is because the download script is run through ncc.
Downgrading fixed it. In turn, it seems like one of the releases in between should've been a major one.

I think it's more of a bug, not a breaking change. @leo can you point us to:

the source file on GitHub
the ncc build instruction on GitHub
ideally, the generated output

You can test this by running npm install -g<EMAIL_ADDRESS>

More details:

Entrypoint
Build instruction
Build output

Resolved!


(maxthon.commandline) Migrated from ferventcoders repo

Description
Migrated package to this repository
reference issue #900
Motivation and Context
It have been outdated for quite some time
How Has this Been Tested?
Using the chocolatey test environment
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Migrated package (a package have been migrated from another repository)

Checklist:

[X] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this mean usually the notes in the description of a package).
[ ] I have updated the documentation accordingly (this mean usually the notes in the description of a package).
[X] All files is up to date with the latest Contributing Guidelines
[X] The added/modified package passed install/uninstall in the chocolatey test environment.
[X] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues

None for maxthon.commandline

[X] PR Removal
[X] The migration guidelines have been followed

@AdmiringWorm I have just merged the PR into @ferventcoder repository and added the chocolatey user, so this should be good to go 👍


[bug] @azure-tools/typespec-python keyError: OperationGroups

With the recent typespec versioning updates to the rest-api-specs repo it looks like this error is back again for EventGrid System Events (a models only package): cmdout	[automation_generate.sh] 2024-12-17 21:40:57 [ERROR] KeyError: 'operationGroups'
as seen here: https://github.com/Azure/azure-rest-api-specs/pull/31739/checks?check_run_id=34561185899
Was there a design change? I believe we ran into this before and resolved it.

Ah looks like this still might be open? https://github.com/Azure/autorest.python/issues/2630

I'm also seeing it after bumping from 0.35.1 to 0.37.1. Stack trace:
Error: Command failed: /home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/http-client-python/venv/bin/python <EMAIL_ADDRESS>--output-folder=/home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator --cadl-file=/tmp/cadl-codegen/python-yaml-path1cce935f-08a8-4ee4-82a0-c60f918da792.yaml --package-version=0.3.13 --generate-packaging-files=false --flavor=azure --package-dir=apiview-stub-generator --package-name=treestyle-parser --generate-test=false --generate-sample=false --models-mode=dpg --emit-cross-language-definition-file=true --from-typespec=true
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 41, in <module>
    codegen.CodeGenerator(output_folder=args.output_folder, cadl_file=args.cadl_file, **unknown_args).process()
  File<EMAIL_ADDRESS>line 336, in process
    self.sort_exceptions(yaml_data)
  File<EMAIL_ADDRESS>line 247, in sort_exceptions
    for group in client["operationGroups"]:
KeyError: 'operationGroups'

    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:882:11)
    at execSync (node:child_process:954:15)
    at $onEmit (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/http-client-python/dist/emitter/emitter.js:110:9)
    at async Object.$onEmit [as emitFunction] (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@azure-tools/typespec-python/dist/src/emitter.js:3:5)
    at async runEmitter (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/compiler/dist/src/core/program.js:366:13)
    at async compile (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/compiler/dist/src/core/program.js:123:9)
    at async compileTsp (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/typespec.js:97:21)
    at async generateCommand (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:248:35)

--------------------------------------------------
Library Version                0.37.1
TypeSpec Compiler Version      0.63.0
--------------------------------------------------
    at runEmitter (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/compiler/dist/src/core/program.js:369:19)
    at async compile (file:///home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/compiler/dist/src/core/program.js:123:9)
    at async compileTsp (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/typespec.js:97:21)
    at async generateCommand (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:248:35)
    at async updateCommand (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:307:5)
    at async Object.handler (file:///home/swathip/.nvm/versions/node/v23.4.0/lib/node_modules/@azure-tools/typespec-client-generator-cli/dist/index.js:151:5) {
  info: {
    kind: 'emitter',
    metadata: {
      type: 'module',
      name: '@azure-tools/typespec-python',
      homepage: 'https://github.com/Azure/autorest.python',
      bugs: [Object],
      version: '0.37.1'
    },
    error: Error: Command failed: /home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator/TempTypeSpecFiles/apiview-treestyle-parser-schema/node_modules/@typespec/http-client-python/venv/bin/python <EMAIL_ADDRESS>--output-folder=/home/swathip/repos/azure-sdk-tools/packages/python-packages/apiview-stub-generator --cadl-file=/tmp/cadl-codegen/python-yaml-path1cce935f-08a8-4ee4-82a0-c60f918da792.yaml --package-version=0.3.13 --generate-packaging-files=false --flavor=azure --package-dir=apiview-stub-generator --package-name=treestyle-parser --generate-test=false --generate-sample=false --models-mode=dpg --emit-cross-language-definition-file=true --from-typespec=true
    Traceback (most recent call last):
      File<EMAIL_ADDRESS>line 41, in <module>
        codegen.CodeGenerator(output_folder=args.output_folder, cadl_file=args.cadl_file, **unknown_args).process()
      File<EMAIL_ADDRESS>line 336, in process
        self.sort_exceptions(yaml_data)
      File<EMAIL_ADDRESS>line 247, in sort_exceptions
        for group in client["operationGroups"]:
    KeyError: 'operationGroups'

Update: I have found the root cause and will fix it ASAP.


Whitelisted IP Error not being caught

Description
When trying to scrape from a Public IP that is not whitelisted by PasteBin, the error is not being caught properly.  Since the error is not being caught, the program continues to run instead of stopping.
Steps To Reproduce
Steps to reproduce the behavior:

Have an account that is not a Pro Account.
Run the main.py example in the README.
When a request made to the PasteBin API URL, you receive a JSON parsing error since the regex (pastebin_error_pattern) in the PastbinScrapper class is not matching in the API request.

Error from Pastebin request response: Forbidden: YOUR IP: xxx.xx.xxx.xxx DOES NOT HAVE ACCESS. VISIT: https://pastebin.com/doc_scraping_api TO GET ACCESS!
Below is the error received to the console:
2023-04-01 13:40:44,193 - pastepwn.scraping.pastebin.pastebinscraper - ERROR - Expecting value: line 1 column 1 (char 0)
Expected behavior
Error to be handled and logged to the console and the program stops.
Additional context
I fixed the issue by editing the pastebin_error_pattern variable int he PastebinScraper class to the following:
pastebin_error_pattern = re.compile(r"^Forbidden: YOUR IP: ((\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3})|((([0-9A-Fa-f]{1,4}:){7})([0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){1,6}:)(([0-9A-Fa-f]{1,4}:){0,4})([0-9A-Fa-f]{1,4}))) DOES NOT HAVE ACCESS.\s+VISIT: https://pastebin.com/doc_scraping_api TO GET ACCESS!")
I can submit a pull request with this fix if needed.

Hi @bellcha and thank you for raising the issue. I changed the regex. It should work now.


chore(triangle): Add triangle mixin

Added triangle mixin with tests.
My first PR, hope it helps.

Current coverage is 100% (diff: 100%)

Merging #77 into master will not change coverage

@@           master   #77   diff @@
===================================
  Files          38    39     +1
  Lines         198   217    +19
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
+ Hits          198   217    +19
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update c4eab78...a8ddce8

Should be fixed now, cheers for feedback 👏🏼

Hopefully ready now 👍🏼

Now we've got conflicts! 😕 This should solve it:
git merge master # Don't forget to pull the newest changes into master first!
# There'll be conflicts, which are easy to resolve just by doing:
npm run build:docs
# Now finish the merge
git commit
# and push to this repo!

How about now?

Awesome, cheers 👍🏼 started working on Opacity - transparentize 😊


Depends on apparmor cookbook

https://github.com/sous-chefs/mysql/blob/844036bde95721c401ce5309007787babdfc412d/libraries/mysql_service_base.rb#L126
Breaks if apparmor cookbook is not installed. Either needs to depends on that cookbook, or to leave out installation if apparmor attribute is undefined.
I also find it strange that the mysql cookbook is installing the apparmor package. Shouldn't that be left for the apparmor cookbook?

Apparmor installation also breaks on ubuntu 20.04, due to missing template files

Apparmor installation also breaks on ubuntu 20.04, due to missing template files

Dupe of #654

Dupe of #654

Closing as duplicate of #654

Closing as duplicate of #654


Add history slider to scroll forward and back through history.

seecode.run uses Firepad as its code editor. Firepad enables multiple clients to synchronize edits with the same pastebin in realtime using a Firebase backend. To keep clients in sync while minimizing bandwidth use, Firepad sends diffs describing edits to the code as they occur. These are then recorded in Firebase. Thus, seeCode.run's Firebase contains the complete edit history of each of its pastebins.
The goal of this issue is to surface this edit history to users. Users should provided a slider at the bottom of the editor window. Moving the slider scrubs through the edit history of the code, updating the Ace Code editor to show the corresponding version of the code. Unless the user edits the code, scrubbing through the edit history does not result in code edits being propagated to Firebase. If the user scrubs through the history and then scrubs back to the end of the slider, the current version of the code that they started with should again be visible. If the user selects a past version of the code and edits it, this will by synced to Firebase as an edit to the code, creating a new entry at the end of the history that should be accessible on the history slider. If, while the user is viewing the history, another user edits the code, this should be similarly visible by setting the history slider to the end.


Failed when deploy dev box infrastructure due to missing implicit dependency

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy dev box using the instruction in the Read Me file
RG=devcenter
DEPLOYINGUSERID=$(az ad signed-in-user show --query id -o tsv)
az group create -n $RG -l eastus
DCNAME=$(az deployment group create -g $RG -f bicep/common.bicep -p nameseed=devbox devboxProjectUser=$DEPLOYINGUSERID --query 'properties.outputs.devcenterName.value' -o tsv)
az deployment group create -g $RG -f bicep/devbox.bicep -p devcenterName=$DCNAME
The error show at the last command

Any log messages given by the failure

The deployment show error as below
"code": "ParentResourceNotFound",
"message": "Can not perform requested operation on nested resource. Parent resource 'developers/developers-win11plain-eastus' not found."
However rerun the same command fix the error
az deployment group create -g $RG -f bicep/devbox.bicep -p devcenterName=$DCNAME
Expected/desired behavior

az deployment group create -g $RG -f bicep/devbox.bicep -p devcenterName=$DCNAME
will run correctly first time

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful
I think this might be because the schedule stop using the string manupilation so the implicit dependency is not created.

Thanks! We'll be in touch soon.

Closed by #6


Add images/federation-v2/controller-manager to git ignore

Recent changes to rename binary name in image to hyperfed caused https://github.com/kubernetes-sigs/federation-v2/pull/326/files to push a binary image accidentally. To avoid such things happening to other authors, the binary name is added to git ignore list temporarily.
/cc @marun

/lgtm


Fix missing md5.c in CMakeLists

In commit 9bbd1f01405578d8fa73705aa22a88c7219f0856 "Removed LibreSSL..." the files md5.h, md5.c were added to the source code and VS build system but not in CMakeLists. This led to linker errors while building on my linux machine.

Thanks!


Fixed the logout styling Issue

Please close this PR as I forgot to merge previous change

Forgot to merge from main


add debugging helper which lists size and first bytes of extra data

See what's in the unparsed data.
Might be especially interesting for XML data?

Or maybe contribute changes to fq instead? https://github.com/wader/fq


chore: operating-system -> os

Schema validation was flagging the old property name

which schema validation?  os isn't a well known property - the matrix leg name can be whatever we want.  was it because of the hyphen?

which schema validation?  os isn't a well known property - the matrix leg name can be whatever we want.  was it because of the hyphen?

Through VS Code, but I don't really feel strongly about this, since either seems to work. I think os is just more commonly used in examples and snippets.

Through VS Code, but I don't really feel strongly about this, since either seems to work. I think os is just more commonly used in examples and snippets.

cool.  merged.  just wanted to understand

cool.  merged.  just wanted to understand


Renderring errors in "Variant selection errors"

Issue type
Typo
Problem description

Context (optional)
No response
Page with the problem
https://docs.gradle.org/current/userguide/variant_model.html

This issue is a good choice for first-time contributors to Gradle, it is actionable and ready for contribution.
See CONTRIBUTING.md for more information.

The fix should be done in variant_model.adoc, where a missing new-line prevents list rendering.

In addition to the problem noted in the screenshot, which uses * for the bullet points, there are several rendering issues in the same document which use - for bullet points. They should also be fixed here

There is no rendering issue.

I guess it is fixed.

Turns out it was fixed by

https://github.com/gradle/gradle/pull/24818

It was merged a long time ago and was released with 8.2.
@AlimurtuzaCodes Sorry for the inconvenience.


Remove hardcoded Java home path

This change is

The description may be confusing to non-Google readers. Better change it to "remove hardcoded Java home path".

Done.


Auto-cancel old unit test Actions Runs

Fixes #23089
The concurrency condition works: https://github.com/Abacn/beam/actions/runs/3016483393
Get message like "Canceling since a higher priority waiting request for 'Java Tests @ Abacn:dumb' exists"
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damccorm

This looks great! Could we add it to some other workflows as well? I'm thinking local_env_tests, build_wheels, and the playground workflows would all benefit from this

Yeah thanks for pinning to the workflows. Specifically including build_wheels would be very helpful (they take long time)


Cycle 4: Cruz Leadership and Spectroscopy

Issue to track progress of Cycle 4 funding request which was approved in #396.
Project Description
Awarded Amount:  $18,847 (US), Sub-award
Period of Performance: 2024-05-01 through 2024-08-31 (TBD)
Finance Committee Contact: @aaryapatil
COTR: TBD

Email sent to NumFOCUS to get the subaward process started.


Can wavesurfer play audio in chunks like soundcloud?

if you've ever tried to download music on soundcloud or tidal using idm (internet download manager), you'll discover that they tend to be serving their audio files in chunks. This make it difficult for idm to grab the file as its served in small kilobytes (250kb). I'm trying to apply the same technique on a project i'm working on but can't get it figured out just yet.
I'm using WaveSurfer to play the audio file (mp3) via a url which reads the file on the server (PHP). How do i get it to play/stream the audio file in partials/chunks

Have you tried StackOverflow?

Yes please similar question here: http://stackoverflow.com/questions/41385292/how-to-read-audio-file-in-chunks-like-soundcloud-php

The stackoverflow post is no longer available, idea?

@daslicht @interwap  seems stackoverlow removed it for moderation issue, you may use hls to achieve this as it will send chunks based on a playlist of the actual file.
see this comment for hls usage, continue on this ticket #1078
https://github.com/katspaugh/wavesurfer.js/issues/1078#issuecomment-713392663

@daslicht @interwap  seems stackoverlow removed it for moderation issue, you may use hls to achieve this as it will send chunks based on a playlist of the actual file.
see this comment for hls usage, continue on this ticket #1078
https://github.com/katspaugh/wavesurfer.js/issues/1078#issuecomment-713392663


Group transforms, represented by matrices (SO2, SE3, etc)

Sorry for a dummy question, but is there a way to parametrize transformation matrix by some parameters. E.g. rotation matrix on a plane  has single parameter (angle) and of 2x2 size. Toy problem i want to solve is
argmin_{theta} \sum_k ||R(theta) x_k - y_k||
x_k and y_k are given points on a plane
Thanks in advance
P.S. Tried to implement my own Atom, stuck at  graph_implementation
atom_exp_so2.py.txt

Hi @morzh, welcome to the CVXPY GitHub. You can't create a general-purpose convex atom for optimizing over SO2 or SO3, largely because the set of rotation matrices in either situation is not convex. An analytic solution might be available for your toy problem. You can try looking at the orthogonal Procrustes problem: https://en.wikipedia.org/wiki/Orthogonal_Procrustes_problem. Further discussion of this kind is better suited for either Stack Overflow or our recently created (and currently beta) GitHub Discussions board: https://github.com/cvxgrp/cvxpy/discussions.


timeline plugin: fix ready listener when loading multiple audio files

Coverage remained the same at 68.607% when pulling 0d08197030d7fe548618b0ee6574211c7b086dc7 on timeline-ready into caa455a8c89ccef145bdb1be6c4028a69eccab7c on master.


'expression not well-formed' error when parsing PDDL

Grounder generated 'expression not well-formed'.
To reproduce,
from unified_planning.io import PDDLReader
from unified_planning.shortcuts import *

planning_task = PDDLReader().parse_problem('domain.pddl', 'p1.pddl')
with Compiler(problem_kind=planning_task.kind, compilation_kind=CompilationKind.GROUNDING) as grounder:
     g_task grounder.compile(planning_task, compilation_kind=CompilationKind.GROUNDING).problem

I get this error:
unified_planning.exceptions.UPTypeError: The expression '(depot0 == market1)' is not well-formed

files.zip

@MFaisalZaki the issue should be fixed by #457. Can you confirm?

@alvalentini, Yup, it works. Thanks a lot.


WIP:[CARBONDATA-2402] Optimize allocated buffer size while converting objects

Currently while converting objects to byte array, for value of int/short, reduce allocated buffer size from 8 bytes to 4/2 respectively.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
NO

[x] Any backward compatibility impacted?
Not sure

[x] Document update required?
NO

[] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4230/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/4536/


Group gcp-data-analysts, gcp-data-engineers  does not exist., badRequest

Not sure anyone else ran into this  error -
It might not be an real issue. Probably I missed some setup.
I am trying the blueprints/datya-solutions/data-platform-minimal
When I run "terraform apply", it created over 100 resources, and then always fails with the following error:
╷ │ Error: Error applying IAM policy for service account<EMAIL_ADDRESS>Error setting IAM policy for service account<EMAIL_ADDRESS>googleapi: Error 400: Group<EMAIL_ADDRESS>does not exist., badRequest │  │   with module.processing-sa-0.google_service_account_iam_binding.roles["roles/iam.serviceAccountTokenCreator"], │   on ../../../modules/iam-service-account/iam.tf line 80, in resource "google_service_account_iam_binding" "roles": │   80: resource "google_service_account_iam_binding" "roles" {
It complains the groups   gcp-data-analysts, gcp-data-engineers   do not exist.
As a matter of fact, I did create the following groups at the organization level and I can see all of them in web console (I created the two sets of groups as I am not sure what exact group name the code uses).
gcp-data-analysts
<EMAIL_ADDRESS>gcp-data-engineers
<EMAIL_ADDRESS>gcp-datya-security
<EMAIL_ADDRESS>Can I get some help what I am missing?
Thanks.

The error message is pretty explicit: the groups don't exist. The format used by the blueprint is <group>@<organization_domain>
Make sure they exist and ensure they are part of the organization var.organization_domain. Also check for typos (e.g. data vs. datya). You can use the following command to list the groups in your organization:
gcloud identity groups search \
  --labels="cloudidentity.googleapis.com/groups.discussion_forum" \
  --organization=[ORGANIZATION_ID]

@juliocc    Thanks for the info.
I got it going now - I thought the group display name is used - but actually the email address is the  key, which becomes the group id.


Add a test for flang include target

LGTM, thanks. Our makefiles are too wet, will open an issue for that. Doesn't block this though.


add discord,github logo

adding more social media links to the footer like discord github
please assign me @pa

plz assign it to me


make build fails on OSX

It fails with the following info:
➜ make build
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 go build -v -o dist/bin/packet-cloud-controller-manager-darwin-amd64 -L/usr/local/opt/libffi/lib ./
flag provided but not defined: -L/usr/local/opt/libffi/lib
usage: go build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.
make: *** [dist/bin/packet-cloud-controller-manager-darwin-amd64] Error 2

You must have the env var LDFLAGS set. Check if that is true, and, if so, unset it.

Thanks, it works. Before closing the issue, can you please help with make image-all fails with this error
Do I need to set any flag before running this make command?
➜ make image-all
docker buildx build --load -t packethost/packet-ccm:latest-arm64 -f Dockerfile --build-arg ARCH=arm64 --platform darwin/arm64 .
[+] Building 0.1s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                          0.0s
 => => transferring dockerfile: 523B                                                                          0.0s
 => [internal] load .dockerignore                                                                             0.1s
 => => transferring context: 2B                                                                               0.0s
 => [internal] load metadata for docker.io/library/alpine:3.11                                                0.0s
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to load LLB: runtime execution on platform darwin/arm64 not supported
make[1]: *** [image] Error 1
make: *** [sub-image-arm64] Error 2

I tried hardcoding it to ARCH to amd64 and OS as linux, but it still fails

Ah, got it why it fails. It had to change the binary name locally. Cool


Error while processing QGIS project: 'LayerSource' object has no attribute 'pk_attr_name'

I am testing the docker stack locally on my laptop. Version 0.21.2
When I create a new project and send it via QFieldSync plugin in QGIS, I get the following error in the job:
I tried with two newly created projects in QGIS Desktop 3.28, one with a geopackage layer, and this one with 2 PostgreSQL layers (and a OSM TMS)
Type: Process QGIS Project File
Output pre:

::<<<::647e626d-e2fc-480c-9ce0-a8a88c44f919 Start QGIS Application
11:51:50.972 root      INFO     Starting QGIS app version 33203 (67d46100b5)...
11:51:52.619 root      INFO     QGIS app started!
::>>>::647e626d-e2fc-480c-9ce0-a8a88c44f919 2
::<<<::974989f6-61b4-4e0a-8a2a-c74ffccb6c7b Download Project Directory
11:51:52.620 root      INFO     Preparing a temporary directory for project files…
11:51:52.776 root      INFO     Downloading project files…
11:51:52.990 root      INFO     Downloading file "observation.gpkg"…
11:51:53.111 root      INFO     Downloading file "photos.gpkg"…
11:51:53.212 root      INFO     Downloading file "test_qfield_cloud.qgs"…
11:51:53.322 root      INFO     Downloading file "test_qfield_cloud_attachments.zip"…
11:51:53.322 root      INFO     Downloading project files finished!
11:51:53.322 root      INFO     Getting project files list…
11:51:53.324 root      INFO     Local files list for project "12eb97a6-7fff-4f59-8c24-e442b8bc1290":
Name                                 Size  MD5 Checksum
---------------------------------  ------  --------------------------------
observation.gpkg                    98304  74781cc704bf5d9668bc9776da7fa373
photos.gpkg                         73728  88330d54e9b948a67013b9c1356d40b1
test_qfield_cloud.qgs              101746  1d6742b7b9ee037fe2c116a161c5eb91
test_qfield_cloud_attachments.zip    1007  eb40ba7b887222a946f001a151c13670
::>>>::974989f6-61b4-4e0a-8a2a-c74ffccb6c7b 2
::<<<::4ff2b700-f3aa-43e1-b117-731fb7c6f942 Project Validity Check
11:51:53.324 PROCPRJ   INFO     Check QGIS project file validity…
11:51:53.328 PROCPRJ   INFO     QGIS project file is valid!
::>>>::4ff2b700-f3aa-43e1-b117-731fb7c6f942 2
::<<<::85b5145d-0891-4bf7-97d1-e49bb3b67eee Opening Check
11:51:53.329 PROCPRJ   INFO     Open QGIS project file…
11:51:53.826 PROCPRJ   INFO     QGIS project file opened!
::>>>::85b5145d-0891-4bf7-97d1-e49bb3b67eee 2
::<<<::dad949e1-92f0-44dc-aa85-2d497430dae4 Project Details
11:51:53.827 PROCPRJ   INFO     Extract project details…
11:51:53.828 PROCPRJ   INFO     Reading QGIS project file…
11:51:55.311 PROCPRJ   INFO     Extracting layer and datasource details…
::>>>::dad949e1-92f0-44dc-aa85-2d497430dae4 1
11:51:55.318 QGSSTDERR WARNING  QFSFileEngine::open: No file name specified
11:51:55.318 root      INFO     Stopping QGIS app…

Feedback pre:
{
  "container_exit_code": 0,
  "error": "'LayerSource' object has no attribute 'pk_attr_name'",
  "error_class": "AttributeError",
  "error_origin": "container",
  "error_stack": [
    "  File \"/usr/src/app/lib/qfieldcloud/qgis/utils.py\", line 526, in run_workflow\n    return_values = step.method(**arguments)\n",
    "  File \"/usr/src/app/lib/qfieldcloud/qgis/process_projectfile.py\", line 116, in extract_project_details\n    details[\"layers_by_id\"] = get_layers_data(project)\n",
    "  File \"/usr/src/app/lib/qfieldcloud/qgis/utils.py\", line 624, in get_layers_data\n    \"qfc_source_data_pk_name\": layer_source.pk_attr_name,\n"
  ],
  "error_type": "UNKNOWN",
  "feedback_version": "2.0",
  "outputs": {
    "download_project_directory": {},
    "opening_check": {},
    "project_validity_check": {},
    "start_qgis_app": {}
  },
  "steps": [
    {
      "id": "start_qgis_app",
      "name": "Start QGIS Application",
      "returns": {},
      "stage": 2
    },
    {
      "id": "download_project_directory",
      "name": "Download Project Directory",
      "returns": {
        "tmp_project_dir": "<non-serializable: PosixPath /tmp/tmp3uuvip74>"
      },
      "stage": 2
    },
    {
      "id": "project_validity_check",
      "name": "Project Validity Check",
      "returns": {},
      "stage": 2
    },
    {
      "id": "opening_check",
      "name": "Opening Check",
      "returns": {
        "project": "<non-serializable: QgsProject <QgsProject: '/tmp/tmp3uuvip74/files/test_qfield_cloud.qgs' (singleton instance)>>"
      },
      "stage": 2
    },
    {
      "id": "project_details",
      "name": "Project Details",
      "returns": {},
      "stage": 1
    },
    {
      "id": "generate_thumbnail_image",
      "name": "Generate Thumbnail Image",
      "returns": {},
      "stage": 0
    },
    {
      "id": "stop_qgis_app",
      "name": "Stop QGIS Application",
      "returns": {},
      "stage": 0
    }
  ],
  "workflow_id": "process_projectfile",
  "workflow_name": "Process Projectfile",
  "workflow_version": "2.0"
}

Gentle up 🐝

Make sure all you git submodules are updated to the correct commit, I am pretty sure you did not do that. Also I guess you would prefer to bump to the latest QFieldCloud version.

Make sure all you git submodules are updated to the correct commit, I am pretty sure you did not do that. Also I guess you would prefer to bump to the latest QFieldCloud version.

I confirm upgrading corrected the issue. Sorry for the noise and thanks for your answer


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In c6ec0e9, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 9674 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 7ee67b7 after 7 minutes.


Window creation examples for SDL and GLFW

Basic examples can be found at https://github.com/icefoxen/gfx/tree/master/examples/triangle-glfw and https://github.com/icefoxen/gfx/tree/master/examples/triangle-sdl

cc @icefoxen

See, now I'm going to have to eat my words about "keeping those up to date is trivial", since they're not up to date...  XD

and an example with glutin too?

#1271 provides an sdl window example, run with (cd src/window/sdl && cargo run --example window)

Fixed by #1258 and #1271
Thanks everyone!


Fix hook parser

Noticed an error when running the hooks example (also on the video). Looked into it and seems that we're passing a str type as the arg_type always and so were always hitting the TypeError exception. Not sure if this is the solution, but proposing it as a possible solution.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Thanks for catching this! Could you let me know what the error is exactly (Is it an exception or a warning or something?).

@htahir1 This is the message that is output when you run it without the fix.
@schustmi I didn't dive deep into the hooks code so not sure where the string annotations come from, but I'll take a look and see if we can just improve it at the source.

So the hooks never worked at all if i understood this correctly?

So the hooks never worked at all if i understood this correctly?

I think not.


Seconds Hours Minutes

Is there anyway to show Hours minutes o seconds cause i only see you can use Days, months , Years

If you're referring to the timescale axis, then you need to configure it via timeVisible. Example:
const chart = LightweightCharts.createChart(
  document.getElementById('container'),
  {
    timeScale: {
      timeVisible: true,
    },
  },
);

You can use a formatter function for the time:

https://tradingview.github.io/lightweight-charts/docs/api/interfaces/LocalizationOptions#timeformatter


Move expected indexes into config

Codecov Report

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

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   96.34%   96.34%
=======================================
  Files          20       20
  Lines        1452     1452
=======================================
  Hits         1399     1399
  Misses         41       41
  Partials       12       12

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 9e0f529...6be0a5b. Read the comment docs.


Pickup and Delivery: no solution

Hi. I need to resolve simple problem using or-tools. It consists in calculating the optimal route for transporting passengers. I added one constraint to ensure that the passenger is first taken from the house and then delivered. I have two instances of relations between nodes:

OK. The solution is found within a millisecond: 1 -> 2, 3 -> 4, 5 -> 6, 7 -> 8, 9 -> 10, 13 -> 14, 11 -> 12, 15 -> 16, 17 -> 18

FAILED. With some additional relations: 1 -> 2, 1 -> 3, 3 -> 4, 3 -> 5, 5 -> 6, 5 -> 7, 7 -> 8, 7 -> 9, 9 -> 10, 9 -> 11, 11 -> 12, 11 -> 13, 13 -> 14, 13 -> 15, 15 -> 16, 15 -> 17, 17 -> 18

1 -> 2 means that the node with index 1 must be visited before the node with index 2.
Node with index 0 is start depot and with index 19 is end depot.
I've tried to use different first solution strategies but result was the same.
It's my first time with or-tool and maybe I didn't read anything in the documentation.
Thanks for all the advice.
std::vector<std::pair<RoutingModel::NodeIndex, RoutingModel::NodeIndex>> depots(1);
depots[0] = std::make_pair(RoutingModel::NodeIndex(0), RoutingModel::NodeIndex(size - 1));

// Create routing model for 'size' nodes and one vehicle
routing = new RoutingModel(size, 1, depots);

// SimpleRoadResolver::evaluateCost returns travel time from one node to another from matrix
routing->SetArcCostEvaluatorOfAllVehicles(NewPermanentCallback(this, &SimpleRoadResolver::evaluateCost));

// Create "time" dimension used to ensure order. It uses the same method as the main cost.
int64 someBigValue =<PHONE_NUMBER>;
routing->AddDimension(NewPermanentCallback(this, &SimpleRoadResolver::evaluateCost), someBigValue, someBigValue, true, "time");
const RoutingDimension &timeDimension = routing->GetDimensionOrDie("time");

// For each relation add constraint. Pair {4, 7} means that the fourth node must be visited before the seventh node.
Solver *solver = routing->solver();
for (std::pair<int, int> relation : relations)
{
    int64 pickUpNodeIndex = routing->NodeToIndex(RoutingModel::NodeIndex(relation.first));
    int64 deliveryNodeIndex = routing->NodeToIndex(RoutingModel::NodeIndex(relation.second));
    solver->AddConstraint(solver->MakeLessOrEqual(
        timeDimension.CumulVar(pickUpNodeIndex),
        timeDimension.CumulVar(deliveryNodeIndex)));
}

RoutingSearchParameters parameters = RoutingModel::DefaultSearchParameters();
parameters.set_first_solution_strategy(FirstSolutionStrategy::PATH_CHEAPEST_ARC);
parameters.set_time_limit_ms(5000);

// solution is NULL
const Assignment *solution = routing->SolveWithParameters(parameters);

The API has changed a lot since 7.0.
I hope the new API removed the problems.


Fireworks shot from Dispensers never disappear and face the wrong direction.

Note: Normal fireworks go infinitely however Custom Fireworks still disappear!

Check #161 for an update on this bug.


Update requirements.txt to fix pydantic version minimum

[] I have added the tests to cover my changes.
[X] I have updated the documentation and CHANGELOG accordingly.
[X] I have read the CONTRIBUTING document.

Closes #1765. Essentially, the existing minimum version for Pydantic causes the UI not to render appropriately. Pydantic > 2 is needed now for Covalent. As such, I have set the minimum version to 2.1.1. I chose 2.1.1 intentionally because: a) I tested it and it works; b) FastAPI strictly does not support 2.0.0, 2.0.1, or 2.1.0 so we can't use 2.0 through 2.1.0 anyway.

@arosen93 thanks a lot for identifying the exact cause ! This could have been quite nasty to debug sans UI logs !
@kessler-frost  can you take a look at this please 🙏🏻

Upgrading Pydantic might break certain things I believe (hopefully I'm wrong), but let's see what happens. This PR looks gtg from my side.

🙏

I added the py.typed file to MANIFEST.in as well here.

Just a heads up to the team Pydantic 2 has been known to not work on AWS Lambda, so keep an eye out for this during the next round of QA
https://twitter.com/pydantic/status/1678298418983124992
https://stackoverflow.com/questions/76650856/no-module-named-pydantic-core-pydantic-core-in-aws-lambda-though-library-is-i
CC @AlejandroEsquivel

There also is a case where pydantic 2 has been supported only for fastapi versions > 100. So we might need to tweak the fastapi limits in the requirements as well. (Currently <100 also can be installed)
Also when we install fastapi, pydantic gets installed automatically with a fastapi compatible version. So we might need to set both the fastapi and pydantic version correctly to avoid any failures.
cc : @kessler-frost @arosen93 @wjcunningham7


Deprecate the specification repository and move documentation inline

This is merely a suggestion of how to handle documentation that could fit the current workflow:
Main Suggestions

Archive the spec repository (It's last update was in Dec 2021, 2 months ago although new features (seemingly?) got merged/proposed)
Move all developer-facing documentation inline in the respective tedge crate
Move 'use cases' etc that are not yet implemented to issues so that they can be discussed/worked on
Move descriptions of features/specs to a special spec folder

New spec parts should then be submitted as PRs, this will allow better discussion handling through features like commenting on specific lines/blocks

I believe this would help others to join in and help implement things they might need.

It seems, but I'm not sure, that this is aligned to what I propose here.

Whoops, it absolutely is. I can swear I looked over the discussions, but must have missed it! I'll merge it with that discussion.


Extend build lmp from source to refer to the lmp-manifest repo used by a factory

https://docs.foundries.io/latest/reference-manual/linux/linux-building.html covers the build from source process using the public repos (public lmp) only.
We should extend that page covering how to build lmp from source based on a certain factory/branch, and explain the difference between a factory build and our public build.

Moving issue to Jira. It appears this has been partially addressed, but the difference isn't really detailed.


Fix typo in dashboard tip

Fixed a small typo in the dashboard tips ;)

Can one of the admins verify this patch?

Hello, @tobiasdierich I was having a look to your PR. I saw a new feature that is cloud-services. Could you describe what will include it?

Hi,
only the first commit was supposed to be part of this PR. Sorry about that, I'll fix it.


PortAudio library not found

When I try to start the "Ghost.py" file, this happens. (I tried a few times and got the same thing)

Hi, I need a bit more information from you so I can help. Please answer the below questions.

What operating system are you using?
What version of Python do you have?
What version of Ghost are you using?

When I try to start the "Ghost.py" file, this happens. (I tried a few times and got the same thing)

install something like "portaudio-dev"


Typo on "query informations"

Hi,
I noticed two typos in this file
The word should be "information". Letter "r" is misplaced and the word has no plural.
Thank you.

Fix on master. Thank you @mfgabriel92 for pointing it out :)


When switching between Gnosis Chain and other networks, the wrong safe address is used in requests

Description
When switching between networks on Gnosis chain the wrong safe address is used in requests
Environment

Browser: Chrome
Wallet: Mobile app
Chain: Gnosis chain

Preconditions
each network has added safe
connect mobile app to the web
Steps to reproduce

switch between the networks and open Gnosis chain with connected mobile app key

Current result: Where often either safe not found error on screen is displayed or the queued/history lists are empty and no request to get it in the console( networks)
Expected result
Make sure that the correct safe address is used in the requests to the CGW on networks switching
Screenshots
see the safe address in URL and the 404 not found request from CGW - wrong safe address was sent

@liliya-soroka we can't seem to reproduce this. Any specific conditions to fulfill?


BLD: add -std=c99 flag to scipy.special extensions using cosine.c

This fixes the manylinux1 builds. Closes gh-13840
Also clean up an outdated try-catch.

Still a 32-bit Windows failure. This code is quite fishy:
    // M_PI is not exactly π.  In fact, float64(π - M_PI) is
    // 1.2246467991473532e-16.  h is supposed to be x + π, so to compute
    // h accurately, we write the calculation as:
    h = (x + M_PI) + 1.2246467991473532e-16;

Not only should you not rely on M_PI being available, but if it is available, the exact numerical value is going to be a compiler-dependent approximation to \pi. It's very hard to believe that all implementations are going to be off by exactly np.finfo(np.float64).eps - 1e-16.
I'd prefer to mark this as a knownfail and open an issue to follow up (if desired, it's quite a niche failure). @WarrenWeckesser can you have a look at this?

That hexadecimal representation fixed it, merging. Thanks @WarrenWeckesser

Maybe upstream it to npy_math.h's definition of NPY_PI ?

That could make sense. Would you want to do that @WarrenWeckesser?


Update console.md

Added note regarding build action

@matthiasguentert I cannot really validate that as i do not work with Visual Studio. @michaelstaib  do you still have a installation?


Added multiples presence actions for cationbot

closes #8

Codecov Report

Merging #9 (c2443b0) into development (49f3a82) will not change coverage.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           development        #9   +/-   ##
=============================================
  Coverage       100.00%   100.00%
=============================================
  Files                5         6    +1
  Lines               72        80    +8
=============================================
+ Hits                72        80    +8

Impacted Files
Coverage Δ

cationbot/core/__init__.py
100.00% <100.00%> (ø)

cationbot/core/activities.py
100.00% <100.00%> (ø)

cationbot/core/env.py
100.00% <100.00%> (ø)

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 49f3a82...c2443b0. Read the comment docs.


Token is never assigned in this example

The Token is never assigned within the method in this example...

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

ID: 27fb3418-db2e-54a1-9faa-7ba09c5259dc
Version Independent ID: 87329ec8-d7d4-f66a-0562-13a9b6032543
Content: Get an authentication access token - Power BI
Content Source: powerbi-docs/developer/automation/walkthrough-push-data-get-token.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks for the feedback, @ssisjoost. I'm assigning this to the author to take a look at the method.

Hi @ssisjoost,
Following your comment I added a token declaration (var token) to the code in Get an authentication access token.
Thank you for highlighting this issue,
Kesem


Update to 1.18.0 resources

Update to 0.18.0 version pod package for both ORT and ORT Extensions
Copy over latest objectivec/ folder source file from ORT source repo

Actually we appear to be missing a 1.17 tag. Do we need to copy from 1.17 first and tag that?

right I missed that when updating the 1.17.0 package - thought would just overrides with a 1.18.0 tag.
but realized this might be mandatory as user usually consumes swift package manager via a version tag. sorry about this.
So I created a v1.17.0 tag just now with the current main - and after merging this PR, will create a v1.18.0 accordingly


--header_file flag is not in generated codeg

Describe the bug
When using the --header_file flag the resulting generated file has the following go generate line:
//go:generate wire

This implies when someone later runs go generate ./..., the header file that was originally in the file will be removed.
To Reproduce
wire --header_file=./path/to/header/file
go generate

Expected behavior
After running wire with the --header_file flag, running go generate again would not produce a delta.
Version
v0.3.0
Additional context

How would you expect this to work? Would you want wire to emit something like
go:generate wire --header_file=./path/to/header/file

? That path may not exist for a subsequent call to go generate....

I think I would want that or an option to not include the go generate line

WDYT about always omitting the //go:generate wire line if a header is provided? It seems like a signal that the user is not actually using go generate to generate the file, but some other script/process.

@zombiezen

I am bit concerned to add too much logic here: folks that use Wire in complex builds should likely be using a tool more sophisticated than go generate.

Does that imply the go generate line should be removed from the generated output?

--output_file_prefix has the same issue.


Milestone M5 Summary Document

Milestone: Expansion of Caching Services and Monitoring for Cardano Infrastructure
This document summarizes the completion of the milestone for the expansion of caching services for Cardano node, Kupo, and Cardano DB Sync. The milestone covers the fulfillment of acceptance criteria and the evidence supporting the work completed.
More details can be found here:
Project Catalyst Milestone
Details on Acceptance Criteria Fulfillment

Caching services for Cardano node, Kupo, and Cardano DB Sync remain online and accessible throughout the milestone (excluding temporary downtime):

The caching services have been continuously available, with minimal temporary downtime, providing access to the Cardano node, Kupo, and Cardano DB Sync.

Tutorials clearly show how to utilize snapshots and restore scripts for Cardano node, Kupo, and Cardano DB Sync:

Comprehensive tutorials have been created and published, demonstrating how to quickly spin up instances of Cardano node, Kupo, and Cardano DB Sync using snapshots and restore scripts. These tutorials provide step-by-step guidance for users.

Tutorials require no prior knowledge of the project:

The tutorials are designed to be accessible to users with no prior knowledge of the project, ensuring that anyone can follow along and use the caching services effectively.

Gaps in documentation reported by the community are resolved:

The community did not report any gap in the documentation.

Health checks exist for each caching service to determine if they are operational without manual testing:

Health checks have been implemented for each snapshot exported service (mainnet, preview, preprod), allowing for automated validation of service availability without manual intervention.

Alerts notify the MLabs team if caching services go down:

A robust alert system is now in place to notify MLabs team members if any of the caching services experience downtime, ensuring a quick response to any service disruptions.

A status page displays recent uptime information:

A public status page has been created and provides detailed uptime information for the caching services, helping users monitor the reliability and availability of each service.

Evidence of Milestone Completion
The following evidence demonstrates the successful completion of the expansion of caching services for Cardano infrastructure:

[x] Publicly accessible caching services for Cardano node, Kupo, and Cardano DB Sync are available at this link. (Note: While "services" is mentioned, the project actually provides publicly accessible snapshots rather than full services. Additionally, regarding the Cardano node, this was relevant historically when the project was approved. However, after Mithril was released shortly afterward, we agreed to rely on Mithril snapshots, as directly providing Cardano node snapshots would offer a less secure alternative.)
[x] Publicly accessible tutorials and supporting documentation have been made available, detailing how to use the services: Tutorials and Documentation.
[x] A public dashboard displaying uptime and status information is available (without credentials) here: Status Page.
[x] Video demo explaining the documentation, alerts, and dashboard page: YouTube video.
[x] Summary document explaining everything added in this milestone, with relevant links: Summary Document.

Video Timestamps
The following sections can be found in the video demo:

Intro
Documentation Overview
Restore Script Documentation
Deployment Documentation
Monitoring Documentation
Public Healthcheck Dashboard
Host Machine Dashboard
Application Dashboard, Traces, Logs
Alerts

Testing and Health Checks
Automated health checks for the caching services are in place to continuously monitor their status. These checks are integrated into the system and do not require manual intervention. Furthermore, alerts are configured to notify the MLabs team immediately in the event of any service downtime.

Approved by catalyst team


Remove allow_untrusted for synology-cloud-station-drive 4.2.3-4385

It is not required for me. I think it has been added by mistake.
Signed-off-by: Jean-Pierre Matsumoto<EMAIL_ADDRESS>
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you, and welcome.


Not able to use severless-plugin-typescript

I see what warmup is not compatible with serverless-plugin-typescript.
I am wondering if there will be any support for this soon.

This is a duplicate of #85. You can read there about the problem.
In short, there is nothing wrong with this plugin but with the typescript plugin which breaks any function that's not using TS.
There is also an issue in the serverless-plugin-typescript repository which has been unattended for 1.5 years (see my last comment in #85). So my expectations of them fixing this are very low.
I (and many others) moved to serverless-webpack a long time ago and I'd suggest that you do the same 🙂


Use root level channel argument for filtering and sorting

Drop channel field from filters and sorters. Use channel argument from root level for filtering and sorting.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[x] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[x] Changes are mentioned in the changelog

Task linked: SALEOR-2979 Refactor all queries to take channel as root level argument

Blocked - waiting for frontend.