Generate example struct tag if example is provided

Fixes #2445
My use case might be a bit weird. I have a service, let's call it A which calls service B. Service B has a swagger spec which I use to generate a client for it. Service A has a few cases where it will straight up return a model generated by go-swagger from the spec of service B.
When I generate the swagger spec for service A, I have a problem because the example field in the swagger spec of service B is not rendered on the models. So the service A swagger spec does not contain the examples, which is not ideal.
It might sound a bit convoluted but that's how we setup our thing. We use https://github.com/swaggo/swag to generate the service spec (legacy reasons), and it needs that example tag.

What happens when the example is on an object

That's a good question, I haven't really thought about that. For now it only renders examples for fields, I don't think swaggo/swag supports examples on the entire struct.

I'm getting a timeout when I try to run the tests locally, it's pretty weird. CI is ok though.
panic: test timed out after 10m0s

goroutine 82445 [running]:
testing.(*M).startAlarm.func1()
	/opt/go/src/testing/testing.go:1609 +0xe5
created by time.goFunc
	/opt/go/src/time/sleep.go:167 +0x45

goroutine 1 [chan receive]:
testing.(*T).Run(0xc001861200, 0xe3efc2, 0x23, 0xeaa080, 0x498201)
	/opt/go/src/testing/testing.go:1160 +0x3ad
testing.runTests.func1(0xc000502900)
	/opt/go/src/testing/testing.go:1430 +0x78
testing.tRunner(0xc000502900, 0xc000787d28)
	/opt/go/src/testing/testing.go:1108 +0xef
testing.runTests(0xc000808be0, 0x14459e0, 0x15e, 0x15e, 0xbfea61e3901f2347, 0x8bc4fbfe20, 0x145b440, 0x40f3d0)
	/opt/go/src/testing/testing.go:1428 +0x2e8
testing.(*M).Run(0xc000312c80, 0x0)
	/opt/go/src/testing/testing.go:1338 +0x245
github.com/go-swagger/go-swagger/generator.TestMain(0xc000312c80)
	/home/simon/projects/go-swagger/generator/shared_test.go:33 +0x245
main.main()
	_testmain.go:745 +0x165

goroutine 82623 [runnable]:
bytes.(*Buffer).WriteString(0xc004519bf8, 0xc003410121, 0x56, 0xc003410121, 0x56, 0x0)
	/opt/go/src/bytes/buffer.go:180 +0xfb
github.com/PuerkitoBio/urlesc.Escape(0xc00101ed80, 0xc0001866c0, 0x2000)
	/home/simon/go/pkg/mod/github.com/!puerkito!bio/urlesc@v0.0.0-20170810143723-de5bf2ad4578/urlesc.go:177 +0x1e5
github.com/PuerkitoBio/purell.NormalizeURL(0xc00101ed80, 0x207f, 0xc00101ed80, 0x0)
	/home/simon/go/pkg/mod/github.com/!puerkito!bio/purell@v1.1.1/purell.go:183 +0xbf
github.com/go-openapi/jsonreference.(*Ref).parse(0xc004519cf8, 0xc003410120, 0x57, 0x454827, 0x0)
	/home/simon/go/pkg/mod/github.com/go-openapi/jsonreference@v0.19.5/reference.go:117 +0x65
github.com/go-openapi/jsonreference.New(...)
	/home/simon/go/pkg/mod/github.com/go-openapi/jsonreference@v0.19.5/reference.go:45
github.com/go-openapi/jsonreference.MustCreateRef(0xc003410120, 0x57, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/simon/go/pkg/mod/github.com/go-openapi/jsonreference@v0.19.5/reference.go:53 +0x70
github.com/go-openapi/spec.MustCreateRef(...)
	/home/simon/go/pkg/mod/github.com/go-openapi/spec@v0.19.15/ref.go:130
github.com/go-openapi/analysis.(*Spec).analyzeSchema(0xc002df4c30, 0xdf9f95, 0x5, 0xc003e37d40, 0xc002f08be0, 0x50)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:395 +0x13f
github.com/go-openapi/analysis.(*Spec).analyzeSchema(0xc002df4c30, 0xe202cb, 0x14, 0xc003e37680, 0xc00023e5c0, 0x3b)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:459 +0x1145
github.com/go-openapi/analysis.(*Spec).analyzeSchema(0xc002df4c30, 0xdfb5d8, 0x6, 0xc003e36fc0, 0xc00023e580, 0x34)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:450 +0x11e7
github.com/go-openapi/analysis.(*Spec).analyzeOperation(0xc002df4c30, 0xdf80fc, 0x3, 0xc00418f2a0, 0x1b, 0xc00084f960)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:348 +0x17bb
github.com/go-openapi/analysis.(*Spec).analyzeOperations(0xc002df4c30, 0xc00418f2a0, 0x1b, 0xc00451e058)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:270 +0xa5
github.com/go-openapi/analysis.(*Spec).initialize(0xc002df4c30)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:215 +0x33b
github.com/go-openapi/analysis.New(0xc00280e000, 0xc002b09480)
	/home/simon/go/pkg/mod/github.com/go-openapi/analysis@v0.19.16/analyzer.go:151 +0x5f
github.com/go-openapi/loads.(*Document).Expanded(0xc0020503c0, 0x0, 0x0, 0x0, 0xc00188f801, 0x0, 0x0)
	/home/simon/go/pkg/mod/github.com/go-openapi/loads@v0.19.7/spec.go:220 +0xf9
github.com/go-openapi/validate.(*SpecValidator).validateReferencesValid(0xc00451e8b8, 0xc00451e7e8)
	/home/simon/go/pkg/mod/github.com/go-openapi/validate@v0.19.15/spec.go:754 +0x1a5
github.com/go-openapi/validate.(*SpecValidator).Validate(0xc00451e8b8, 0xda80c0, 0xc0020503c0, 0x0, 0x0)
	/home/simon/go/pkg/mod/github.com/go-openapi/validate@v0.19.15/spec.go:112 +0x375
github.com/go-openapi/validate.Spec(0xc0020503c0, 0xfaa000, 0xc0001f7440, 0x1, 0x1)
	/home/simon/go/pkg/mod/github.com/go-openapi/validate@v0.19.15/spec.go:47 +0xab
github.com/go-swagger/go-swagger/generator.(*GenOpts).validateAndFlattenSpec(0xc0048f7680, 0xc00007e050, 0x203001, 0xc00007e050)
	/home/simon/projects/go-swagger/generator/spec.go:40 +0x12e
github.com/go-swagger/go-swagger/generator.(*GenOpts).analyzeSpec(0xc0048f7680, 0x148c5b0, 0x64, 0x203001, 0x203000)
	/home/simon/projects/go-swagger/generator/spec.go:98 +0x35
github.com/go-swagger/go-swagger/generator.opBuilderWithOpts(0xe2d0aa, 0x1a, 0xc0000c5200, 0x29, 0xc0048f7680, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/home/simon/projects/go-swagger/generator/operation_test.go:362 +0x116
github.com/go-swagger/go-swagger/generator.opBuilderWithFlatten(0xe2d0aa, 0x1a, 0xc0000c5200, 0x29, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/home/simon/projects/go-swagger/generator/operation_test.go:407 +0xbb
github.com/go-swagger/go-swagger/generator.assertParams(0xc001861200, 0xc000a05e18, 0xc0000c5200, 0x29, 0x0)
	/home/simon/projects/go-swagger/generator/parameter_test.go:1243 +0xa78
github.com/go-swagger/go-swagger/generator.TestGenParameter_Issue1536_MoreMaps(0xc001861200)
	/home/simon/projects/go-swagger/generator/parameter_test.go:4002 +0x12d6
testing.tRunner(0xc001861200, 0xeaa080)
	/opt/go/src/testing/testing.go:1108 +0xef
created by testing.(*T).Run
	/opt/go/src/testing/testing.go:1159 +0x386
FAIL	github.com/go-swagger/go-swagger/generator	600.337s

I can't figure out why that test fails... I compiled my branch version and used it to generate a spec and the PrintTags method is found...

I can't figure out why that test fails... I compiled my branch version and used it to generate a spec and the PrintTags method is found...

Will try tomorrow to reproduce your test issue from your branch. Pretty weird

I did a test, I inserted a deliberate panic in PrintTags and I got the same error but at the different assert.
    model_test.go:44:
        	Error Trace:	model_test.go:44
        	            				model_test.go:170
        	Error:      	Received unexpected error:
        	            	template: structfield:6:54: executing "structfield" at <.PrintTags>: can't evaluate field PrintTags in type generator.GenSchema
        	Test:       	TestGenerateModel_SchemaField

So it seems like this can't evaluate field PrintTags error could be because of a panic, the template engine does not display the panic message though :/

Nevermind that above, it's not a panic.
I tried changing the PrintTags receiver from a pointer to a non pointer type and I no longer have the issue... It seems like Go templates have a problem with pointer receivers or something...

It seems like Go templates have a problem with pointer receivers or something...
Not really.
The slice of schema objects that is iterated is made of structs, not pointers. That's why templates don't get passed a pointer receiver. Whatever, if your method doesn't change the receiver, it should not get a pointer receiver.

I was confused about the semantics of pointer vs value receiver, I assumed that it worked like Rust.
I used a pointer receiver at first because I felt like it would be expensive to copy the entire struct on every call. There's like 30 fields in there.

If the receiver is a large struct or array, a pointer receiver is more efficient. How large is large? Assume it's equivalent to passing all its elements as arguments to the method. If that feels too large, it's also too large for the receiver.

Source: https://stackoverflow.com/a/27775558/576488
But I don't mind changing it to a value receiver. Like I said previously, only that test failed. The program runs properly with a pointer receiver.

Thanks guys!


[Suggestion] Bank Value Tracker

Is your feature request related to a problem? Please describe.
I am a senior computer science major and I am looking for a side project, so I started looking into my favorite game client RuneLite! I thought it might be cool to add some sort of metric to track the value of your bank over time and I wanted to gauge community interest.
Describe the solution you'd like
I think it would be fairly simple, I was looking into the code and think it would tie into the BankValue plugin. When enabled, there would be a map where the key is the date and the value would be the user's bank value that would update when they sign in(or out) each day.  This map would be saved to a file and be saved and loaded when the client is running. Then users would be able to track their bank's value over weekly, monthly, or yearly periods. This could be represented in numerous ways but I figure a percentage growth would be good for initial testing, they could also see the exact value of their bank that has been tracked each day in the form of a list.
Additional context
I would love to contribute to this plugin and would appreciate a mentor of sorts who is familiar with the platform to point me in the right direction as well as check my code quality. I think this would be a great learning experience!
Thank you,
Scott

I'm not sure how accurate this would be for cases such as mine where it fluctuate greatly depending on what I'm wearing, what's in my inventory, Grand Exchange offers, Chambers of Xeric chest, etc at any given time.


change tx type (#485)

This PR is related to :
https://app.shortcut.com/oazo-apps/epic/86/oa-sop-default-to-95-gas-oracle-gas-price-estimation
All transactions send from oasis-borrow are now EIP-1559 transactions and gas price parameters comes from
https://www.blocknative.com/gas-estimator
95% confidence

for exgasPricde endpoint returns
{"time":1633954122975,"fromCache":true,"maxPriorityFeePerGas":1.56,"maxFeePerGas":205.42}
notification in metamask is showing 0

when trying to edit maxPriorityFeePerGas and maxFeePerGas are very low numbers with e-7, e-9 etc
one can edit it and increase to make it work. Not sure if testing like this makes sense will try also on goerli or kovan.


Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID

I have recently deployed the CC in my orgainization tenant. One deployed instance is running perfectly fine. But when trying to send message from another deployed instance of the CC getting below error.
System.AggregateException: Failed to acquire token for client credentials. (A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details.  Original exception: AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'GUID'. Trace ID: e2ab7b14-d156-442a-ab84-a8bf8610eb00 Correlation ID: 063a326b-db94-42f8-96cd-e293ed5b6d4c Timestamp: 2024-06-28 14:25:27Z)
Troubleshooting steps done:

I am double-tripple check the correct configuration in environment variables. UserAppPassword has correct keyvault value. Still same issue.
Created a new version(same secret) of app secret in keyvault and updated the environment variables. Re-sync the deployment. Still same issue.
Create a new app secret in azure app registrations. Updated the same in keyvault. Then updated environment variables. Re-sync the deployment. Still same issue.

Could you please help identify the issue and help resolve this.

Hello @sujeetsharma ,
Thanks for reaching out to us! The error seems to be pretty much with mismatch in secret.
Can you please send a screenshot of first 3 letters of secret in App registration and same from the key vault for all 3 app registration (Author, User and Graph apps)?
Also Please make sure Graph app registration type is My organization and for other 2 it should be Multiple organization.

Thank you I will check internally and get back to you soon

Hi @sujeetsharma,
There are multiple places where secret need to be updated- Web app/App Service, Function apps such as Prep-function, Data-Function, Function.
Not only AuthorAppPassword, UserAppPassword, GraphAppPassword but also AzureAD:ClientSecret need to be updated with GraphAppPassword. Can you please cross-verify these places.

Hi @sujeetsharma, There are multiple places where secret need to be updated- Web app/App Service, Function apps such as Prep-function, Data-Function, Function.
Not only AuthorAppPassword, UserAppPassword, GraphAppPassword but also AzureAD:ClientSecret need to be updated with GraphAppPassword. Can you please cross-verify these places.

@tiwariShiv7 The error is specific to the UserAppPassword. And yes, I have updated in the web-app, all function apps.
During provisioning the template, I have used the correct secrets. Same way I had setup another instance.
Original exception: AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'GUID'
The GUID here was for the UserApp.
Do you know if we can debug this and correct the source of this error?
Error Stack.txt

Hey @sujeetsharma, Yes we can discuss this. Meanwhile we are discussing this internally, Can you please share your contact e-mail to contact over Teams / outlook and availability time zone ?

@tiwariShiv7 Please find my contact details as below:
<EMAIL_ADDRESS>Work hours 9AM-6PM CET(12PM-9PM IST)
We are already federated, so you can directly IM me on Teams.

We are following it over the Teams

@tiwariShiv7 @v-jaygupta Update - I have done the redeployment of instance and after which the new deployment is working as expected.


Document the devc goal and the options related to container use.

See if there is anything else the user needs to know to run container mode.
Should we document the reserved Liberty variable io.openliberty.tools.projectRoot?

I don't think we need to document io.openliberty.tools.projectRoot since that is mostly internal.
We should describe the behaviour when dev mode exits though.  e.g. describe that the container will be stopped and deleted.

Also add an entry in the top level README.md here https://github.com/OpenLiberty/ci.maven/blame/master/README.md#L99 with a devc goal, but just link to the dev.md file's devc section.


Just found vulnerable in this CMS

can i contact you on discord?

@muchub Please message us on the discord channel https://discord.gg/c9tmB43kxm


person occupation and main place of activity are not mapped

https://github.com/american-art/aaa/blob/master/data-v3/aaa V3 documentation.docx: "Item_PeopleOccupation.xls and Item_PeoplePlace.xls using the Person ID to provide information on the Person entities occupation(s) and primary place of activity".
@workergnome @azaroth42: I propose to map them thus:

occupation: member of a group having type AAT "occupation"
place: "took place at" of an event having type AAT "floruit"

AAA Occupations are mapped to AAT concepts in "AAA Role Term mapping-final.xlsx".


Update Docs on How to Import a program for CPI

I believe this section of the docs can be improved by using cargo-add since it is natively incorporated into Rust by writing cargo add --path "../puppet/programs/puppet" --features=cpi
https://github.com/coral-xyz/anchor/blob/fd467df93245ceca0ea2a2ce865a0da7967982b7/docs/src/pages/docs/cross-program-invocations.md?plain=1#L101-L105
I also got an error when I used path = ../puppet but I fixed it using path = ../puppet/programs/puppet

Regarding the first part, I think that sure, we could make it easier for people by adding the cargo add command, although I think that is less clear for people to understand what they need to do in future cases. It also helps them to see what's going on.
Secondly I don't think ../puppet/programs/puppet is correct? Maybe you're adding it to a different cargo.toml or perhaps cargo.toml is being called from a different directory. You could totally be right but I would expect the tests to fail if this were the case surely?


Support UTF-16 and wstring

Support building the MusicXML Class Library in wstring mode.  Support import and export of UTF-16 files and strings.

meh


Contribute External*Parser to CommunityModules

Hi, we recently added generic (de-)serialization to the IOUtils module of the CommunityModules (https://github.com/tlaplus/CommunityModules/issues/53).  Perhaps, you want to contribute your parser to the CommunityModules, too?

Sorry for the delay. Yes, of course! I think that change may have caused TLC to throw errors for the current version. I'll make the necessary changes and then add it to the community modules :)

https://github.com/tlaplus/CommunityModules/pull/75


Update deepar_synthetic.ipynb

replace DateTimeIndex with date_range. DateTimeIndex is deprecated and caused an error when I tried running this notebook as is.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I restored the majority of the notebook that I accidentally deleted for this PR. Also, you are correct. The scikit learn change is completely different. Do you want me to break it out as another PR?

I think we can close this as the issue was fixed in another PR.


receive a completely unrelated concept map

Link: https://en.wikipedia.org/wiki/Mary_Anning
Map:

I don't know where it goes wrong.

That is very peculiar. The resulting map is indeed completely unrelated.
Unfortunately, I can’t replicate it – running the tool on the latest version produces a correct (if somewhat rambling) map for me.
￼

On May 21, 2024, at 02:34, yibie @.***> wrote:
Link: https://en.wikipedia.org/wiki/Mary_Anning
Map:
output.png (view on web) https://github.com/jorgearango/llmapper/assets/365484/d916d4b6-8b5e-47ee-9d58-06801bf47ebd
—
Reply to this email directly, view it on GitHub https://github.com/jorgearango/llmapper/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEWSDEDIRCWIXR5K3USUKRTZDL2JVAVCNFSM6AAAAABIBBXAESVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYDONJVGU3TMNA.
You are receiving this because you are subscribed to this thread.


Replace the MLH Fellowship logo with the MLH Prep logo

When you go to the project page, it shows the MLH Fellowship logo at the top. It would be great to replace this with the Prep logo and make sure that's used throughout the website!

Solved without conflict.


Update doc for 5.6

There are references to mbed OS 5.4 and CLI 1.0.0 (which are very old now).
@Patater please have a look to the markdown doc and update what you consider necessary for the 5.6 release (to be done in a branch).
Update: same applies to other uvisor examples.

ARM Internal Ref: IOTSEC-441


Enable build of x86 MSIX package

Enable build of x86 MSIX package

PR Summary
We should support x86 architecture for MSIX package.  Tooling already supports building, just need to publish in our release pipeline.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Have you tested the new build?

Built it locally, signed, installed and confirm it's x86.  Also confirmed that you can't have both x64 and x86 msix installed at same time (cc @rjmholt)

@SteveL-MSFT Can you test the actual new build?  Setup time with me if you need help

doesn't have the latest changes from the other branch

@PoshChan Please remind me in 1 hour

@TravisEz13, this is the reminder you requested 1 hour ago


Feature Request Mouse Inversion on onDrag

When I have transform: rotate(180deg) as a css property being applied to a div which wraps the draggable component, I would like the mouse to not be inverted on drag, is that possible?

I have a use case for 90, 180, and 270 rotate angles.

Use <DraggableCore> and translate the coordinates you receive via callback into modified top/left or translate attributes depending on your use case.


adbc.snowflake.statement.* options are not effective ["python"]

What happened?
I've tried changing adbc.snowflake.statement options, but none of  the settings appear to have any effect with adbc_ingest().
I've tried the following:
"adbc.snowflake.statement.ingest_copy_concurrency": "0",
"adbc.snowflake.statement.ingest_copy_concurrency": "1",
"adbc.snowflake.statement.ingest_target_file_size": "100mb",
"adbc.snowflake.statement.ingest_target_file_size": "100",
"adbc.snowflake.statement.ingest_target_file_size": "100000000",
But the result always ends up with ~120 PUTs with concurrent overlapping COPY INTO(s) running in parallel..
Changing any of the above to int(s) like:
"adbc.snowflake.statement.ingest_copy_concurrency": 0,
results in an error which is expected, so the parameters are being checked, but they just don't impact anything..
  File "../miniconda3/lib/python3.9/site-packages/adbc_driver_snowflake/__init__.py", line 156, in connect
    return adbc_driver_manager.AdbcDatabase(driver=_driver_path(), **kwargs)
  File "adbc_driver_manager/_lib.pyx", line 482, in adbc_driver_manager._lib.AdbcDatabase.__init__
  File "adbc_driver_manager/_lib.pyx", line 276, in adbc_driver_manager._lib._to_bytes
ValueError: value must be str or bytes

I'm also passing a recordbatchreader into adbc_ingest()
Stack Trace
No response
How can we reproduce the bug?
No response
Environment/Setup
No response

@joellubi can you take a look at this when you get a chance? thanks!

@davlee1972 Can you please share the code you used to pass in those parameters?
Based on the traceback the error is occurring during database initialization so my guess is those parameters are being provided as database kwargs. The ingestion parameters are defined on the statement rather than the database. They can be set as follows:
with adbc_driver_snowflake.dbapi.connect(uri) as conn, conn.cursor() as cur:
    cur.adbc_statement.set_options(**kwargs)
    cur.adbc_ingest(...)

FWIW I do think the way parameters handling works right now is kind of awkward. I would be for cleaning it up some way if it can help make this more intuitive.

Ok, I'll try that, but it is a kinda awkward. The documentation isn't clear that these are adbc_statement options as part of the cursor since the options are show right after the database kwargs sample.

I think we should update the documentation to make this clearer, and perhaps make the interface more consistent.
@lidavidm Do you know if adding optional parameters to Connection.cursor() would be a problem for the dbapi spec?
I'm thinking for consistency to allow stmt_kwargs to be specified similar to how the db and conn kwargs already are:
with adbc_driver_snowflake.dbapi.connect(uri, db_kwargs=db_kwargs, conn_kwargs=conn_kwargs) as conn:
    with conn.cursor(stmt_kwargs=stmt_kwargs) as cur:
        cur.adbc_ingest(...)

Thoughts on this?
CC: @zeroshade

I think it would be OK only as a keyword-only argument like adbc_stmt_kwargs


LUC-1600: Uniquify client assets

Summary
This PR introduces an optional namespace prop during TinaCMS initialization to isolate media caching between different instances. This is useful in multi-tenant applications where media should not be shared across different clients, such as lucid-admin.
Changes

Adds an optional namespace property to the TinaCMS constructor.
Modifies the MediaManagerScreenPlugin to accept a namespace prop through a factory function.
Passes the namespace prop to the MediaPicker.

Impact
With these changes, instances of TinaCMS initialized with different namespace values will have isolated media caches. This prevents media from being mistakenly shared or cached between different instances or clients.
Backward Compatibility
The namespace property is optional and the changes are fully backward-compatible.

I'm not seeing the namespace being applied in the storage, can you please explain how you expect this to work?

 I accidentally did not commit my update to the localStorageKey. My last commit should fix the caching issue since we'll have a unique local storage key

I'm not seeing the namespace being applied in the storage, can you please explain how you expect this to work?

 I accidentally did not commit my update to the localStorageKey. My last commit should fix the caching issue since we'll have a unique local storage key

alright, I saw the update. I still one question.
Einstein assets should not be namespaced to the client, since even when you change a client, those assets remain the same. Are you going to handle that in the lucid's side?


Feature Request: Filter Problems from hover

As someone whos code is full of problems, I'd like to be able to filter which problems show up on hover.
There are many ways to denote errors in VS Code - problems tab, red squiggles, Error Lens extension...
Both the problems tab, and the Error Lens extension allow you to pass a glob or regex to filter out errors, but there is no functionality like this for the hover panel.

In the above example, I know there is a spelling mistake from the short underline under the first letter, and I know the variable is unused because it's greyed out. Not a problem. I'd love to be able to filter those out with editor.hover.exclude array.
Examples
Error Lens:

Problems Tab:

eh?eh?

I see your correlation but unfortunately we do not want to filter any problems in the editor area and want extensions generating those errors to provide such. Hence closing this as wont fix.

😢 I see your point, but in my case I don't want to turn off the TypeScript errors, I just want to filter them from showing up in the UI.


File is encrypted or is not a database

I'm using the beta for sqlite-net-sqlcipher and when I try to open the connection then SetKey (or executing PRAGMA), I get the error in the title.  However, I can pull the file off the device and verify it is not encrypted. Furthermore, if I just remove the setkey on subsequent runs, it'll access the DB fine.  Uncommenting any of the three key lines will cause this error.
            var dbSql = new SQLiteConnection(folderPath + "/test.sqlite");

            //dbSql.Execute("PRAGMA Key = 'helloworld'");
            //dbSql.ExecuteScalar<string>("PRAGMA Key = 'helloworld'");
            dbSql.SetKey("helloworld");

            dbSql.CreateTable<fakesql>();
            dbSql.Insert(new fakesql());

What platform?

Xamarin iOS

Is this a newly created sqlite file?  I think it needs to be.  What happens if you change test.sqlite to a name that definitely does not exist yet?
Also, to verify what sqlite library you're actually calling,  call dbSql.ExecuteScalar<string>("SELECT sqlite_version()"); and see what it returns.

<IP_ADDRESS> and BOOM!  You are correct about the new name.  Thanks for your time!


[WIP] Event Details page

[x] Fill in event details page
[x] Add react-native-maps
[x] Add fonts
[ ] Fix all test data to add required fields
[ ] Handle images from contentful

Pre-flight check-list
Before raising a pull request

[ ] Documentation
[ ] Unit tests

Pre-merge check-list

[ ] Tester approved

Opps, misclick on closing.
Intrigued why adding fonts is such a native task? Especially as it creates these ugly conflicts.

Yea it's a bit odd @markholland. It seems that fonts are required to be added to the native layer on both android and ios. It's a much more complicated process for ios than android. It's all handled by react-native link. https://medium.com/react-native-training/react-native-custom-fonts-ccc9aacf9e5e

Do we really need to add the Roboto font to the Android app. I think it should already be available on all Android devices as it's the default system font. What am I missing?

@frigus02 You're not missing anything. The react-native link system adds our custom fonts to both platforms automatically. So we could go in and delete them again, but they would reappear each time someone runs react-native link again.
I could always add them to .gitignore I suppose

Okay. We should probably just leave it as it is then. Maybe a future version of React Native can deal with this automatically. Do they get included in the APK file during build?

I'm not sure. I would assume so, because for android it's just a folder of static files. I don't think it would know to exclude them.


Ensure Decoders for both Http4s and Akka are not capitalized when generating

Fixes issue #416
Add a method to com.twilio.guardrail.generators.syntax.RichString to ensure a string is not capitalized, this is required as capitalised operationIds which are used in the creation of decoder names break the scalameta invariant check (I'm unsure of the actual root cause to this). Now, even when endpoints have capitalised operationIds and a body parameter then will now generate correctly.
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

I'm unsure of the actual root cause to this

Testing out in the REPL yields some more context:
scala> p"fooDecoder: Bleep"
res5: meta.Pat.Typed = fooDecoder: Bleep

scala> p"FooDecoder: Bleep"
<console>:15: error: end of file expected but : found
       p"FooDecoder: Bleep"
                   ^

and by poking around a bit more:
scala> q""" val FooDecoder: Bleep = "boop" """.pats
res17: List[scala.meta.Pat] = List(FooDecoder)

scala> q"""val ${p"fooDecoder: Bleep"} = "boop" """.pats
res18: List[scala.meta.Pat] = List(fooDecoder: Bleep)

and...
scala> res17.head.asInstanceOf[Pat.Var]
res20: scala.meta.Pat.Var = FooDecoder

scala> res18.head.asInstanceOf[Pat.Typed]
res22: scala.meta.Pat.Typed = fooDecoder: Bleep

It looks like in destructuring contexts, there's a completely different AST node representing type constraints with bindings vs "var" patterns, and that capitalized values always parse as a "var" pattern.


[Event Change] Table 5050 - Contact - OnBeforeCreateSalesQuoteFromContact

Hi AL-Team,
can you please add the variable SalesHeader by var to the following Publisher?
    [IntegrationEvent(false, false)]
    local procedure OnBeforeCreateSalesQuoteFromContact(var Contact: Record Contact; **var** SalesHeader: Record "Sales Header")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


fix coverage controller

Codecov Report

Merging #36 into master will decrease coverage by 15.45%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #36       +/-   ##
===========================================
- Coverage   76.61%   61.16%   -15.46%
===========================================
  Files          13        7        -6
  Lines        1035      636      -399
  Branches        0      109      +109
===========================================
- Hits          793      389      -404
+ Misses        242      228       -14
- Partials        0       19       +19

Impacted Files
Coverage Δ

pybmpdb/utils.py
83.87% <0%> (-4.04%)
:arrow_down:

pybmpdb/summary.py
56.85% <0%> (-3.5%)
:arrow_down:

pybmpdb/dataAccess.py
75.94% <0%> (-2.54%)
:arrow_down:

pybmpdb/tests/__init__.py

pybmpdb/tests/test_dataAccess.py

pybmpdb/tests/test_info.py

pybmpdb/tests/test_utils.py

pybmpdb/tests/test_summary.py

pybmpdb/__init__.py

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 75c510a...8846fa6. Read the comment docs.


Add runtime assertions for safe-in-practice operations

Motivation
Almost all operations that are unsafe in the general case may be safe in practice under certain conditions.
For example: when a new feature has a new table or tables to go with it, they tend to change a lot as we iterate. Until the table is actually being used by the app, all changes are effectively safe (except adding a foreign key constraint that involves some other table maybe). We have one mechanism for dealing with this (.nandiignore). It would be good if it wasn't such a binary choice.
Proposal
Add a new layer of runtime assertions that will be run at the beginning of the migration.
Example
# say we have defined a foo field as a number, but we decide that
# a string is more appropriate. This is unsafe unless the table is empty
class MakeFooText < Nandi::Migration
  def up
    assert! :table_is_empty, :my_new_table

    change_column :foo, type: :text
  end
end

With this feature, the above migration would be valid, but would raise an error at runtime if the the table turned out to have data in it.

Yes, please!
Is this a reasonably easy change to make for someone that doesn't know Nandi?
I'd be happy to contribute this

I think this is probably quite a big change, but totally open to PRs.
My own initial idea is:

define the assert! method on Nandi::Migration, which is going to build up a data structure with all the assertions in. Let's say for starters we only implement the :table_is_empty condition.

Come up with a way to mark particular instructions as safe when the assertion is true. Do that for basically everything.

Make the validator respect that.

Implement the assertions in the compiled output.

Could you make your life slightly easier by going:
change_column :table, :foo, type: :text, assert_empty_table: true
And then the validator already knows it's safe because you're going to assert, and the code generator generates the assert.
It'll be more verbose if you're doing multiple things because you have to write that multiple times, and you'll also end up checking the empty table is empty multiple times, but it sounds much easier to implement that way :)


feat(next): ambient type via next-env.d.ts

#439  👈
main

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

Join @hi-ogawa and the rest of your teammates on  Graphite


BUG-000112661  Symbols generated in the Military Symbol Editor Add-In in ArcGIS Pro for the Military Operations Other than War (MOOTW) symbol group with Symbol Code (SIDC) starting with O incorrectly show dashed outlines and/or missing "?" for the following affiliations:  Pending, Exercise Pending, Assume Friend, Exercise Assumed Friend, Suspect, or Joker.

Salesforce ID: BUG-000112661
Salesforce Submitter: Olivia RoDee
Salesforce Submit Date: 3/23/2018 11:03 AM
Salesforce Bug Type: Usability
Salesforce Severity: Medium
Repro Data: \\esri.com\sf_filestore\PRD\Attachments\Defects\BUG-000112661
Work Around: (n/a)
Product: ArcGIS Pro
Functional Category: ArcGIS for Defense
Client Platform: (n/a)
Version Found: 2.0
Planned Version Fixed: (n/a)
Comment: (n/a)

Synopsis:
Symbols generated in the Military Symbol Editor Add-In in ArcGIS Pro for the Military Operations Other than War (MOOTW) symbol group with Symbol Code (SIDC) starting with O incorrectly show dashed outlines and/or missing "?" for the following affiliations: Pending, Exercise Pending, Assume Friend, Exercise Assumed Friend, Suspect, or Joker.
Steps to Repro:
Open the Military Symbol Editor Add-In in ArcGIS Pro.
Search for and select "Incident : Bomb/Bombing".
Navigate to the Symbol tab.  Set the Identity/Affiliation to Pending, Assumed Friend, Suspect, Exercise Pending, Exercise Assumed Friend, or Joker. Note that symbols incorrectly have dashed outlines, but solid outlines are required by MIL-STD-2525B w/CHANGE 2 (see page 47-49 Table I/II of the attached PDF, 2525BChange2)
Set the Identity/Affiliation to Assumed Friend, Suspect, Exercise Pending, Exercise Assumed Friend, or Pending.
Note that a "?" is missing for these affiliations as well.
Repro data: <filestore>\PRD\Attachments\Defects\BUG-000112661

This issue was moved to ArcGIS/military-symbology-styles#48


feat(readme): add details for API

What this PR does / why we need it:

feat(readme): add details for API

Which issue(s) this PR fixes (optional, close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
/assign @ddysher
Release note:

NONE

/lgtm


Replace qrcode library to fix commonjs warning

[webpack-dev-server] WARNING
.../node_modules/angularx-qrcode/fesm2020/angularx-qrcode.mjs depends on 'qrcode'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies
logger @ index.js:556
(anonymous) @ index.js:730
warn @ index.js:189
warnings @ index.js:247
(anonymous) @ socket.js:60
client.onmessage @ WebSocketClient.js:50
Show 6 more frames

@iCodr8
I hope the workaround provided by @eXpertise7 helped you.
I'm closing this for now, please re-open if this is still an issue.

This is not fixing the issue, this is just disables it. I think it's better to try to remove qrcode library from deps to remove this warning and provide better optimization.


DetailComponent.ByCurve Node

Hey guys, is it possible to update this node to receive a list of Family Types instead of only one?  Right now it appears I can input a list of curves, but only assign one family type to all of them.  I want to be able to assign a 1 to 1.  In this way, I can specify which family type I want, per curve.
Is this possible??  Is it an easy python code change you would share?  I posted the question on DynamoBIM forum here as well:
http://dynamobim.com/forums/topic/drawing-in-revit-lines-details-line-based-families/
Thank you!

This is definitely possible - I'll add it in the next release. For the time being, please use the solution Dimitar provided on the forum.

@andydandy74 I'm having an odd issue, and I apologize for posting it here but it is related to this same node.  See attached screenshot.  I fee like I'm feeding the node everything it is asking for and I've gotten it to work in the past.  Neither the List.Combine or grab the top item from each list is working.  I've tried dynamo .9 and .8.2 (.8.2 is where I was using the script and it was working before).  I've tried updating to the most recent version of clockwork in both versoins and it just doesn't work.  I've confirmed that the elevation of the line I'm feeding it is the same elevation of the view, 100'.

Not sure if the error message on the node means anything to you.  Please let me know!

Ok so after a little testing, it errors out when I pass it an "Area Plan" type of view.  Floor Plan view seems to work.  Wierd thing is this script used to work when I passed it an area plan view...any ideas?

@madeforworship - I wonder if this is perhaps caused by the data type set for the view input. Can you please try the following and report back if it solved the issue: In the custom node remove the data type for the view input: " : View"

Hallelujah! That worked!  I was racking my brain over this one!  Thanks so much Andreas

Great. I'll make sure to edit this in for the next release and will file an issue with the Dynamo team.

I am going to close this as there is now a built-in node to make detail curves.


this.$root.$off unsubscribes all instances of component from event

Version
2.5.21
Reproduction link
https://codesandbox.io/s/lrk25l907l
Steps to reproduce
Click buttons in the following order: Step 1 => Step 2 => Step 3
What is expected?
It is expected that only one instance of multiple components will get unsubscribed from event on destroy.
What is actually happening?
All components get unsubscribed instead.

https://stackoverflow.com/questions/55297461/vue-this-root-off-unsubscribes-all-instances-of-the-component-from-the-glob

You need to pass a function to not remove all event listeners:
mounted() {
    this.fn = () => {
      this.toggleWarning();
    }
    this.$root.$on("triggerChildComponents", this.fn);
  },
  beforeDestroy() {
    this.$root.$off("triggerChildComponents", this.fn);
  },

What if you need to grab a parameter from the $emit function and pass it to the callback function?


Single-core performance on T480s does not reach full potential

I ran Geekbench4 on a T480s with an i7-8550U (the same as in the README). Results are here https://browser.geekbench.com/v4/cpu/11625783 and I am surprised that I do not reach the same single-core performance as described in the README. 5391 vs 3757 is a huge difference. Hence, I am wondering what I am missing/how I can debug my setup to get to the same performance.
Setup:

openSUSE Tumbleweed (latest revision) with kernel 4.19.12
BIOS is 1.27
lenovo-throttling-fix (master which is f9c7f515493887cc4b4c122183524803fb942859) is enabled and status is all green
HWP_Mode set to "True"
Secure Boot is disabled in the BIOS
Already rebooted

Looking at s-tui during the benchmarks tells me that the CPU is reaching 4.0GHz.

Sorry for taking so long. I have a huge backlog on GitHub mails, I do not how to work through them at the moment.
I am reading the Tumbleweed mailing list and somebody wrote something related to this problem: most likely it is this https://lists.opensuse.org/opensuse-factory/2019-04/msg00126.html
My score went up to 4488 with  "spectre_v2=retpoline,generic" as additional kernel parameters.


[WIP] Show stream description in compose autocomplete

Implemented stream autocomplete to show description or first 35 characters of description as in the attached screen grab.

Solution for issue #2398

Automated message from Dropbox CLA bot
@akhilmd, it looks like you've already signed the Dropbox CLA. Thanks!

We should switch the styling to the other version you have, but otherwise this looks great!

I changed how the descriptions look. Given that it may be difficult to see the bold text, maybe using font-weight: bolder; is an option?

In the results, streams whose names start with query are first. These are followed by streams whose descriptions start with query and streams whose names/description contain the query. In each category, the streams are sorted by number of subscribers.

This looks great, merged as d8caf16e59a125983d385324286102b961f690fc (only change is to add Fixes: 2398 to the commit message so that it auto-closes the original GitHub issue).  Thanks @akhilmd!!!


Test vectors for hash2curve for bn254

The IETF draft does not have any test vectors for hash2curve for bn254 pairing curve. How was the test vector (https://github.com/ConsenSys/gnark-crypto/blob/master/ecc/bn254/hash_vectors_test.go) generated for the same?

cc @Tabaie

Generated here: https://github.com/Tabaie/h2c-go-ref-tests/blob/autogen-tests/gnark_autogen_test.go#L145
This repo is a fork of h2c-go-ref by Armando Faz, one of the standard's authors.

The repo which you mentioned(https://github.com/Tabaie/h2c-go-ref-tests/blob/autogen-tests/gnark_autogen_test.go#L145) is showing not available. May be the repo is private i guess.

yes! I can see it. Thank you so much @Tabaie !!!


Deploy to prod/beta

Codecov Report

Merging #22 (949f878) into prod-beta (a764354) will increase coverage by 14.24%.
The diff coverage is 22.35%.

@@              Coverage Diff               @@
##           prod-beta      #22       +/-   ##
==============================================
+ Coverage       6.66%   20.91%   +14.24%
==============================================
  Files             13       19        +6
  Lines             60      263      +203
  Branches           0       65       +65
==============================================
+ Hits               4       55       +51
- Misses            56      185      +129
- Partials           0       23       +23

Impacted Files
Coverage Δ

src/App.js
0.00% <0.00%> (ø)

src/AppEntry.js
0.00% <0.00%> (ø)

src/Components/Breadcrumbs/index.js
0.00% <0.00%> (ø)

src/Components/Cluster/index.js
0.00% <0.00%> (ø)

src/Components/ClusterHeader/index.js
0.00% <0.00%> (ø)

src/Routes.js
0.00% <0.00%> (ø)

src/Services/AccountManagementService.js
0.00% <0.00%> (ø)

src/Services/SmartProxy.js
0.00% <0.00%> (ø)

src/Store/index.js
0.00% <0.00%> (ø)

src/Components/ClusterRules/ClusterRules.js
2.18% <2.18%> (ø)

... and 21 more

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 a764354...949f878. Read the comment docs.


Allow gem to be used with ruby 2.5.5

Since it is not possible to update ruby on the api servers at the
current time, prometheus_exporter needs to continue working with
the installed version (2.5.5) This change means that we can use
the recently added features without upgrading ruby

Sorry I can not accept this, Ruby 2.5 was end of life 10 months ago. We have a strong policy of not supporting end of life Ruby which may have critical, unpatched, security vulnerabilities

Oops, apologies for the noise here. I thought I'd made this one against our own fork as a messy and temporary solution but I mistakenly chose the upstream repo

No worries at all @TLischkaRemerge! good luck updating Ruby! 2.7 is better in almost all metrics than 2.5. 3.1 is also a very good release.


Create strategy with custom y-int (z) value

Currently, we do not allow passing the y-int (z) value as part of the create strategy (or edit) flows.
Updated, allow the option to pass a custom value.

outdated


MailSenderImpl breaks when sending multiple emails with String[]

convertToInternetAddress forgets to increment its iterator, leading to converting arrays with multiple elements to an array with a single InternetAddress and nothing but null values, then fails to send the email due to a NullPointerException.

Fixed by #196


Refactored: Extracted class JmdslApplyDefaults from JmdslConfig

I have extracted the class JmdslApplyDefaults from JmdslConfig, which had improved the code quality, and maintainability, and all made the class JmdslConfig focus on a single functionality. I kindly request you to merge this if you find this improves your code quality. Thanks

Thank you again for submitting another PR!
In this scenario, since logic is only used in that class, is tied to JmdslConfig logic and the class is so small, I would rather keep it where it is. Take into consideration that even though removing code from classes makes them easier to maintain, adding classes makes the general project more complex/harder to maintain (more classes=more structure=more dependencies), so there is a balance to keep an eye on between class complexity and project/dependencies complexity.


[IOS] - discoverAllServicesAndCharacteristics throws error

Expected Behavior
The function behaves as expected.
Current Behavior
Central device hangs on discoverServices of the peripheral device for 30 seconds before disconnecting.
Steps to Reproduce

Build Debug App with XCode 10.3
Download app on fresh Iphone 8
Try and connect to peripheral device.
Get rekt

Context

Library version: 1.1.0
React-native: 0.60.5
Platform: iOS 12.1.4
Platform logs (logcat/XCode):
[RxBLEKit|DEBG|21:59:38.374]: CentralManager(10753593984) stopScan()
[RxBLEKit|DEBG|21:59:38.375]: CentralManager(10753593984) retrievePeripherals(
withIdentifiers: [A46D534E-6F8E-A301-6B71-4C46CDCA22BB])
[RxBLEKit|DEBG|21:59:38.377]: CentralManager(10753593984) connect(
peripheral: Peripheral(uuid: A46D534E-6F8E-A301-6B71-4C46CDCA22BB, name: Optional("CEREBRI_HRATE_TEMP")),
options: nil)
[RxBLEKit|DEBG|21:59:39.034]: Peripheral(uuid: A46D534E-6F8E-A301-6B71-4C46CDCA22BB, name: Optional("CEREBRI_HRATE_TEMP")) discoverServices(
serviceUUIDs: nil)
[RxBLEKit|DEBG|22:00:09.035]: CentralManager(10753593984) didDisconnect(from: Peripheral(uuid: A46D534E-6F8E-A301-6B71-4C46CDCA22BB, name: Optional("CEREBRI_HRATE_TEMP")),
error: nil)
2019-11-04 23:00:09.130 [info][tid:com.facebook.react.JavaScript] 'BleWrapper::scanAndConnect:: Error caught: ', '{"message":"Device A46D534E-6F8E-A301-6B71-4C46CDCA22BB was disconnected","errorCode":201,"attErrorCode":null,"iosErrorCode":null,"androidErrorCode":null,"reason":null,"name":"BleError","line":107459,"column":28,"sourceURL":"http://<IP_ADDRESS>:8081/index.bundle?platform=ios&dev=true&minify=false"}'
JS logs: Error caught: ', [BleError: Device 509EF9BE-5CD3-4598-75DD-AFD8E017A9EB was disconnected]

scanAndConnect() {
    this.manager.startDeviceScan(
      null,
      null,
      (error, device) => {
        if (error) {
          console.log(
            'BleWrapper::scanAndConnect:: error caught when scanning: ',
            error,
          );
          return;
        }

        if (this.verifiedDevice(device)) {
          this.manager.stopDeviceScan();

          device
            .connect()
            .then((device) => {
              return device.discoverAllServicesAndCharacteristics();
            })
            .catch((err) => {
              console.log('BleWrapper::scanAndConnect:: Error caught: ', err);
              this.connectionFailure = true;
            });
        }
      },
    );
    return;
  }

Context Peripheral device

chipset: Adafruit Bluefruit Feather nRF52832
Following advertising standards: https://developer.apple.com/accessories/Accessory-Design-Guidelines.pdf ch.25.5 and 25.6

Hi!
I will post this in case someone has a similar problem! The error was a configuration issue on the peripheral side. Feel free to contact me regarding the specifics if you face a similar problem using the same hardware. I won't go into details here as it wasn't an issue with this library!
Best regards


Re-write reaction roles to be persistent

Updated on_raw_reaction_add and reaction_groups to get it's data from the database, not a local variable. Also added update_reaction_roles which will be sure that all users who are reacted to the message have their roles. Useful for re-synchronizing the roles if something gets messed up. Not ran automatically yet, but should probably hook into startup somewhere.
Still need to write a clear command that wipes the database association and possibly removes the roles.

failed test doesn't matter, it's for sponsor audio. closes #11


Add | Changes for 7.3.0-preview release

Codecov Report

Merging #1001 into dev will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #1001      +/-   ##
============================================
- Coverage     50.19%   50.12%   -0.08%
+ Complexity     2885     2882       -3
============================================
  Files           120      120
  Lines         27989    27989
  Branches       4677     4677
============================================
- Hits          14050    14029      -21
- Misses        11684    11706      +22
+ Partials       2255     2254       -1

Flag
Coverage Δ
Complexity Δ

#JDBC42
49.68% <ø> (-0.09%)
2840 <ø> (-6)

#JDBC43
50.06% <ø> (-0.11%)
2878 <ø> (-6)

Impacted Files
Coverage Δ
Complexity Δ

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
43.95% <0%> (-3.3%)
15% <0%> (ø)

...a/com/microsoft/sqlserver/jdbc/PLPInputStream.java
59.76% <0%> (-1.19%)
34% <0%> (-1%)

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
66.33% <0%> (-0.81%)
63% <0%> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
46.86% <0%> (-0.44%)
111% <0%> (-1%)

...oft/sqlserver/jdbc/SQLServerPreparedStatement.java
46.97% <0%> (-0.2%)
189% <0%> (ø)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
55.55% <0%> (-0.17%)
0% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
50.39% <0%> (-0.13%)
245% <0%> (-1%)

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 e432aa1...3bea41e. Read the comment docs.

Codecov Report

Merging #1001 into dev will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #1001      +/-   ##
============================================
- Coverage     50.19%   50.12%   -0.08%
+ Complexity     2885     2882       -3
============================================
  Files           120      120
  Lines         27989    27989
  Branches       4677     4677
============================================
- Hits          14050    14029      -21
- Misses        11684    11706      +22
+ Partials       2255     2254       -1

Flag
Coverage Δ
Complexity Δ

#JDBC42
49.68% <ø> (-0.09%)
2840 <ø> (-6)

#JDBC43
50.06% <ø> (-0.11%)
2878 <ø> (-6)

Impacted Files
Coverage Δ
Complexity Δ

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
43.95% <0%> (-3.3%)
15% <0%> (ø)

...a/com/microsoft/sqlserver/jdbc/PLPInputStream.java
59.76% <0%> (-1.19%)
34% <0%> (-1%)

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
66.33% <0%> (-0.81%)
63% <0%> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
46.86% <0%> (-0.44%)
111% <0%> (-1%)

...oft/sqlserver/jdbc/SQLServerPreparedStatement.java
46.97% <0%> (-0.2%)
189% <0%> (ø)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
55.55% <0%> (-0.17%)
0% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
50.39% <0%> (-0.13%)
245% <0%> (-1%)

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 e432aa1...3bea41e. Read the comment docs.


Remove reliance on Payment PR for Refunds PR to build

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PAY-6040
Change description
Update to add refund dependency apps and CVE suppression.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Recreated under https://github.com/hmcts/ccpay-refunds-app/pull/387 so the branch is named correctly.


accept a data Promise?

It would make dataflow easier if data could be a Promise—Inputs.table(data, options) would then return a promise to the table view of the data.
and the user could give:

viewof values = Inputs.table(FileAttachment("parameters.csv").csv())

A simple indirection does it:
diff --git a/src/table.js b/src/table.js
index 4da75b3..3914fb1 100644
--- a/src/table.js
+++ b/src/table.js
@@ -8,7 +8,11 @@ import {defined, ascending, descending} from "./sort.js";

 const rowHeight = 22;

-export function table(
+export function table(data, options) {
+  return data instanceof Promise ? data.then(data => table0(data, options)) : table0(data, options);
+}
+
+export function table0(
   data,
   {

This might be useful also for Inputs.select and others, but it might add more complication than value. I don't think it would be reasonable to scour the options object for promises, for example.
A difficulty however is that, if something expects the function to return a DOM node (for example to insert it in a dahsboard), it will have to apply the same logic. An alternative would be to throw a more informative error (i.e. the data is a Promise, please await, instead of TypeError: e is not iterable).
(A similar thing might be useful in Plot, with the same caveat that if something—say, a plugin—expects to receive a svg element, it will have to also test for Promises.)

I think that Inputs.table should always synchronously return an HTMLTableElement. The difference is when the data is a promise, the contents are lazily filled when the promise resolves.


Add urls.py to install instructions

I'll start by acknowledging that this appears to be abandoned. unfortunately, there seems to be no option for photologue in Django CMS that is current. VerticalMediaProjects has a version that almost works.
There's some confusion for me in the current state of things over there. The album -> gallery transition appears to be a bit incomplete. I've cleaned things up a bit in my fork. I have some plans to redo the interface a bit for a site that I'm working on, but what I have now fixes a bunch of issues with newer versions of Django CMS and photologue.

I forgot to actually mention in that summary that you need to add urls to the project urls.py or the reverse DNS won't work.


New PR to test SignCLA at 2017-12-12 20:14:59.449580468 -0800 PST m=+68.489557900

Body of PR

corp-pass-staging: test succeeded


Outstreams Line Plot is not working correctly with unsync HistorySet

Issue Description
What did you expect to see happen?
The plots should be continuous.
What did you see instead?

Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

No wrong results are possible but just a bad visualization.
No email required.
closure checklist passed...


Update AzNetSecdeploy_Juice-Shop_AZFW-Rules_Updated.json

Updated AppGW WAF rulesets to DRS 2.1 and added Bot Manager Ruleset 1.0

Tested template in Build.


add MacOS support KinD

This PR adds support for MacOS to run e2e/local/kind scripts (prereq, setup kind and setup test).

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: tvieira
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: gargnupur
If they are not already assigned, you can assign the PR to them by writing /assign @gargnupur in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/e2e/local/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@icygalz you worked on the Debian script for this area, would you mind to take a look this addition?

Hi @tvieira. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@tvieira: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
595001ed2e8d5445e5c5d6f7b71cb23f6be2c8da
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simpleTests

/retest e2e-pilot-noauth-v1alpha3-v2

/test e2e-pilot-noauth-v1alpha3-v2

/assign @gargnupur

/lgtm
looks good to me, but lets wait for John's approval who knows about Kind more

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gargnupur, tvieira
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/e2e/local/OWNERS [gargnupur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tvieira: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
1a7d23697f794f5574a72f61640749e4d432b3a5
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add pagination to all lists

Add pagination to:

Mentors
Users
Support - organisation users
Support - organisation mentors
Support - users

Pagination was already implemented on:

Support - organisations

 Prototype - Add pagination to list pages


Added validation for annotations

Annotations are validated use the same rules as Labels.  Resolves #1992.

Please let me know what other types require annotation validation.  I pretty much copied the validation for labels.

@bgrant0607

Worth doing before Clayton's #3789 generification lands?

The tests are valid before and after #3789.  The changes to validation.go are pretty trivial for the generification work.

LGTM.  Cayton can absorb this merge.

@markturansky - can you verify this will not break OpenShift annotations on a deploy object?

Thanks much. Sorry for being slow.

We use mixed case and periods, so we're broken.  Is mixed case an issue in annotation names?  I don't know that the arguments for making them the same ever depended on anything except "maybe we want to conflate fields and labels in the client api".  An example of an annotation with mixed case would be field names preserved during conversion for a non round tripped value.

Since we don't plan to support query on an annotation, I don't get why they share the same validation rules as labels which can make some sensible restrictions on operator characters for label keys.  For me, an Annotation should really be opaque to kubernetes.
Sent from my iPhone

On Jan 27, 2015, at 9:49 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:
We use mixed case and periods, so we're broken. Is mixed case an issue in annotation names? I don't know that the arguments for making them the same ever depended on anything except "maybe we want to conflate fields and labels in the client api". An example of an annotation with mixed case would be field names preserved during conversion for a non round tripped value.
—
Reply to this email directly or view it on GitHub.

Sorry. We'd always planned to make annotations consistent with labels. We're trying to avoid having lots of different rules for users to remember. I'd be ok with relaxing all of label, annotation, and resource keys, but I don't see a strong case for inconsistency.
I agree that annotation values should be opaque.

It seems like the two use cases - system attached metadata, and query set syntax, really are different.  Are they even used by the same class of users?  I don't mind labels being restrictive to aid in approachability and queryability, but I can imagine a wide range of possible keys for annotations matching with automated processes that need to adapt values from external systems.  But that's just an opinion - convenience for one class of use can be inconvenience for the next class.

On Jan 27, 2015, at 10:46 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Sorry. We'd always planned to make annotations consistent with labels. We're trying to avoid having lots of different rules for users to remember. I'd be ok with relaxing all of label, annotation, and resource keys, but I don't see a strong case for inconsistency.
I agree that annotation values should be opaque.
—
Reply to this email directly or view it on GitHub.

I don't think relaxing label keys is particularly useful, though its
probably not harmful within bounds.
I can buy loosening annotations.  I did not give it much thought, frankly,
and I guess I agree they are essentially opaque.
On Jan 27, 2015 7:46 PM, "Brian Grant"<EMAIL_ADDRESS>wrote:

Sorry. We'd always planned to make annotations consistent with labels.
We're trying to avoid having lots of different rules for users to remember.
I'd be ok with relaxing all of label, annotation, and resource keys, but I
don't see a strong case for inconsistency.
I agree that annotation values should be opaque.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3788#issuecomment-71776585
.

Are we just talking about case sensitivity and more dots? Allowing more characters, such as '=' and '/' would be problematic.

Right now / is allowed in labels and annotations.  I don't know if annotations need spaces, although I'm sure someone at some point will ask for them.

On Jan 27, 2015, at 11:09 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Are we just talking about case sensitivity and more dots? Allowing more characters, such as '=' and '/' would be problematic.
—
Reply to this email directly or view it on GitHub.

For me it's just a matter of how opaque is opaque, but I can defer to @smarterclayton on how much he wants to relax.  In practice, I think I should be able to stick base64 encoded annotation values.
Sent from my iPhone

On Jan 27, 2015, at 11:09 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Are we just talking about case sensitivity and more dots? Allowing more characters, such as '=' and '/' would be problematic.
—
Reply to this email directly or view it on GitHub.

If we want to call annotations opaque, then let's just call them opaque.
On Tue, Jan 27, 2015 at 8:12 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Right now / is allowed in labels and annotations. I don't know if
annotations need spaces, although I'm sure someone at some point will ask
for them.

On Jan 27, 2015, at 11:09 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Are we just talking about case sensitivity and more dots? Allowing more
characters, such as '=' and '/' would be problematic.
--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3788#issuecomment-71778321
.

VALUES are free form in both labels and annotations.  I thought we were
debating keys...
On Tue, Jan 27, 2015 at 8:14 PM, Derek Carr<EMAIL_ADDRESS>wrote:

For me it's just a matter of how opaque is opaque, but I can defer to
@smarterclayton on how much he wants to relax. In practice, I think I
should be able to stick base64 encoded annotation values.
Sent from my iPhone

On Jan 27, 2015, at 11:09 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Are we just talking about case sensitivity and more dots? Allowing more
characters, such as '=' and '/' would be problematic.
--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3788#issuecomment-71778431
.

I also could see people wanting to stick some Xml snippet even if it's a bad idea for other reasons.  Agree with Tim that opaque should be opaque.

Sorry, thanks for reminder Tim, then I am corrected.  I don't care as much on keys.  Been working too much :-)

Yes, I explicitly want to permit json, xml, whatever in the values.

Opened #4017 to slightly relax this until we close the discussion.  It did indeed break OpenShift, and if we decide to keep it strict it's going to take us a while to migrate.


Terminal starts presentation problem

Issue Type: Feature Request
Hello together,
If i open VSC the terminal has a presentation problem. I solve this problem, if I type CLS (clear screen) an then the Cursor is in line with C:\
It seems that mor Lines are added on start of Terminal.
On Mac is there no problem. I think it's a problem in Windows 10 Version.
Thanks
Falk
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17763

And it is not that problem Prevent me from work…. prio 10.
:)

/duplicate of #57803


[INVOICE] Be able to create an invoice, without Delevery note

As user, i can create an invoice without Delevery note

New translate line
Change delevery line id to null in migration


ui2 suppressing error on tool add incorrectly

Bug Report
Expected behaviour
Show error warning, drop out of "refreshing" mode.
Actual behaviour

When adding a tool that doesn't actually exist on GitHub, the modal displays "Please wait, retrieving tool ... " indefinitely.  I see a 400 from the webservice in the console.
Closing and reopening, I see

Seems better, at least the first problem is solved.
However, dialog just closes producing an invalid tool.
Closing in favour of higher priorities.
DockstoreAPI - 1.5.0-beta.0
DockstoreUI - 2.2.0-alpha.8


shadows don't work with non-bone texture skinning

Disable bone textures and you will see that skinned characters no longer have shadows
Add this line to doom 3 gangnam style or another project with skinned characters
 app.graphicsDevice.supportsBoneTextures = false;

Can't reproduce; Running this line in console in the middle of execution is incorrect; Starting engine with supportsBoneTextures = false doesn't affect shadows.

Due to inactivity closing this issue.


Hold a modifier key during window placement to be able to "drag" a selection of zones that the window should fill.

Description of the new feature / enhancement
I'm always modifying my fancyzones configuration because I always find a different need for window sizes and my preset options (even using the combined zones that share a border) don't ever suffice. I want lots of little zones, but be able to span three or more wide zones to create a larges selection. The expanding to select two or three or four zones based on their shared boarders doesn't suffice. say I have my ultra-wide monitor split into 5 vertical columns. I want to be able to have one "big" window that takes up 3 of those vertical columns, but I'm not able to do that because the 3 columns don't share a border that will allow them all to be highlighted, which makes me have to manually extend the window, totally defeating the purpose of fanzyzones in the first place.
Since SHIFT is already used for highlighting the zones while dragging a window, I propose the use of CTRL to allow you to move the dragged window across several different zones to consecutively auto select them, and when you let go, the window occupies an area that covers all the selected zones.
Scenario when this would be used?
Every day. More options for window sizing with the current complex configurations I currently have.
Supporting information
No response

This is already possible. Please have another look at the documentation.

Or - share a screenshot of your layout, and the desired effect, and the reason this doesn't work for you.

Thanks for pointing this out, I was not aware holding control was a thing to help you select multiple zones at once. I think this

Should be in the powertoys configuration settings window to provide discoverability of that feature.

CC @niels9001 @crutkas - is there room in the UI-renovation for this?

most 'how to use' is on the Welcome to powertoys or in the docs.
We could add 'snap to multiple zones' in OOBE

also created a PR for docs.  https://github.com/MicrosoftDocs/windows-uwp/pull/3971

We could add 'snap to multiple zones' in OOBE

Confused for a moment: this text is already in the OOBE (?)

yes but make it much more explicit.  not just a tip&trick

Is this still an issue with the latest version? /needinfo


[ADAP-804] [Bug] published dbt-spark docker images are missing latest versions (1.5.x, 1.6.0)

Is this a new bug in dbt-spark?

[X] I believe this is a new bug in dbt-spark
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
For all other dbt adapters the latest versions are available as docker images in packages. For dbt-spark docker images are available but the latest versions are missing.
Expected Behavior
docker images for dbt-spark in version 1.5.0 and 1.6.0 are available.
Steps To Reproduce
n.a.
Relevant log output
No response
Environment
- OS:
- Python:
- dbt-core:
- dbt-spark:

Additional Context
No response

Just realized that the Docker build from the dbt-core project (https://github.com/dbt-labs/dbt-core/tree/main/docker) does not work for dbt-spark when using the PyHive version (or the default all)
docker build --tag my-dbt-spark:1.6.0 --target dbt-spark --build-arg<EMAIL_ADDRESS>--build-arg<EMAIL_ADDRESS>--build-arg dbt_spark_version=PyHive .
produces an error:
...
107.2   note: This error originates from a subprocess, and is likely not a problem with pip.
107.2   ERROR: Failed building wheel for sasl
107.2   Running setup.py clean for sasl
107.4   Building wheel for future (setup.py): started
108.0   Building wheel for future (setup.py): finished with status 'done'
108.0   Created wheel for future: filename=future-0.18.3-py3-none-any.whl size=492023 sha256=0dced4fde8484b7cf07f3ca722cbe787880c6fcb8eb27af37c82213dd20b48b8
108.0   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/da/19/ca/9d8c44cd311a955509d7e13da3f0bea42400c469ef825b580b
108.0   Building wheel for PyHive (setup.py): started
108.3   Building wheel for PyHive (setup.py): finished with status 'done'
108.3   Created wheel for PyHive: filename=PyHive-0.6.5-py3-none-any.whl size=51554 sha256=b78987c7c11b9d3a18704d5339f9d1caf6221976e1f4c572f609fac9dd9da102
108.3   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/cc/b2/8d/74115da1b8e1ee44544ec7870783c9fbf1127b66d296f6c4be
108.3   Building wheel for pure-sasl (setup.py): started
108.6   Building wheel for pure-sasl (setup.py): finished with status 'done'
108.6   Created wheel for pure-sasl: filename=pure_sasl-0.6.2-py3-none-any.whl size=11423 sha256=ef452afe0aeb515f2ad15f63e0df15ea5c620fef4e4f7d4413de8ebdb05b064e
108.6   Stored in directory: /tmp/pip-ephem-wheel-cache-pgg_8qmj/wheels/be/bd/15/23761a50b737a712aacac51c718906ce3563705a336d2c4ffc
108.6 Successfully built pyspark thrift dbt-spark logbook minimal-snowplow-tracker future PyHive pure-sasl
108.6 Failed to build sasl
108.6 ERROR: Could not build wheels for sasl, which is required to install pyproject.toml-based projects
------
Dockerfile:104
--------------------
 102 |         /tmp/* \
 103 |         /var/tmp/*
 104 | >>> RUN python -m pip install --no-cache-dir "git+https://github.com/dbt-labs/${dbt_spark_ref}#egg=dbt-spark[${dbt_spark_version}]"
 105 |
 106 |
--------------------
ERROR: failed to solve: process "/bin/sh -c python -m pip install --no-cache-dir \"git+https://github.com/dbt-labs/${dbt_spark_ref}#egg=dbt-spark[${dbt_spark_version}]\"" did not complete successfully: exit code: 1

It works fine if I'm using the ODBC spark version.

The issue here is related to the sasl package which does not work with python 3.11 anymore. To make this work, you need to install pyhive with extra hive_pure_sasl which uses pure-sasl instead of the sasl package. To make this work, dbt-spark should use pyhive[hive_pure_sasl] instead of just pyhive when installing dbt-spark[pyhive].
You can easily reproduce this issue by running pip install pyhive vs pip install pyhive[hive_pure_sasl] on a python 3.11 installation.


add permission CRUD

please make review and send me to do any refactor

please resolve conflict

well done 👏 , but please resolve conflict

thanks

please resolve conflict

you can check now


Fix auto_bypass in alarmdecoder

Description:

auto_bypass was introduced in #30002, however some things are missing for a proper implementation which is added in this PR

Related issue (if applicable): #30892
Checklist:

[ ] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Should this go out in 0.105?

I would say so since it completes #30002 which was included in 0.104.

Good!

Just a heads up that these recent commits by themselves do not fix the related issue (#30892) for me.
Changing manifest.json to include the following does fix it:
"requirements": ["alarmdecoder==1.13.2"],

@markdstjohn is the integration completely working after bumping up the version?
Or are there parts of it that are still broken?

@MartinHjelmare should I revert the bump (https://github.com/home-assistant/home-assistant/pull/30303) to fix this component?

Yeah, if we can't figure it out easily, that's probably good.

Yeah exactly, that is what I was thinking too.

The sensors don't work. The services to arm and disarm the alarm work ok.
On Sat, Feb 1, 2020, 12:44 PM springstan<EMAIL_ADDRESS>wrote:

@markdstjohn https://github.com/markdstjohn is the integration
completely working after bumping up the version?
Or are there parts of it that are still broken?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/30961?email_source=notifications&email_token=AGXNMECBA256Y6NUTD7Z67LRAW7HFA5CNFSM4KIV7Z22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRD3IQ#issuecomment-581057954,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGXNMEHSZWCA3GOIP5GSBYDRAW7HFANCNFSM4KIV7Z2Q
.

@markdstjohn yeah I am not really sure why. I have reverted the version back to alarmdecoder==1.13.2 with #31385. This change will be available in 0.105.


States for Android system notification

On Android, the application uses a system notification to "stay alive" so the operating system doesn't shut it down, a that would interrupt syncing. The notification can reflect the current state of the block clock, it can essentially just be the text of the states shown in the design docs. To kick things off, I took screenshots of my Samsung phone, here's what the notifications look like for me (this may differ based on what Android flavor you have).

Expanding simply moves the line of text down and reveals the application name (not super helpful). I am curious why the application logo is so small and has this blue circle around it. Do others see this as well on their devices?
Here's a first draft of changes, reflecting the block clock state.

It is possible to add options to notifications. What I don't know is if there are any limitations, this might be good to investigate (dev docs). Right now I don't think we have a lot of options that would be convenient here, so maybe we just leave it out for now and keep it simple - just text to communicate the primary state?

"proof-of-stake"? NO!

reference:

Why "Loaded" versus using the word "Synced"?

It's an easier term.


Issue with FPS mistake in the article

Hello. First of all,thank you for this work.
I noted you mistake the code about the inf_time and fps.
So I think maybe you  calculation the inference time incorrectly in the article , your article show that YOLOP  have 52ms the infercence time per frame(batch size 1), which mean 20fps? (although 41 fps show in the YOLOP's article).
And sadly in the hybridnets_test.py , i try calculate the HYBRIDNET's inference time but only get 0.06s(only model(x) ) ,which means 17-20fps. （Tesla v100 ）but get 0.021s(only model(x) ) in YOLOP, which means 48 fps（Tesla v100 ）
Sadly , it may not faster than YOLOP and not reach the real-time.

The correct result from our paper is from hybridnets_test.py, while that bug is from hybridnets_test_videos.py. Sorry for the confusion.
Can you provide us with your exact benchmark configuration (cuda, cudnn)? We rented a V100 instance on vast.ai and did our benchmark there, maybe it had something to do with cuda optimization? As referenced in this comment, on newer GPUs (or cuda), YOLOP runs faster than us on pure pytorch.

Maybe you can enhance inference speed by setting cudnn.benchmark = False in line 69 in hybridnets_test.py. After I applied that change, the inference time reduced from 0.050s to 0.353s (batch size 1).

If you don't have question anymore, i'll close this issue.


feat: v2 for multi endpoint mapping

Changes
see https://github.com/PostHog/apps/issues/11

adds a new method for sending events to the salesforce sink that uses a JSON mapping to allow multiple endpoints

Testing locally with v2 config set as:
{
    "$pageview": {
        "salesforcePath": "Lead",
        "propertiesToInclude": "$current_url",
        "method": "POST"
    },
    "$autocapture": {
        "salesforcePath": "Event",
        "propertiesToInclude": "$current_url",
        "method": "POST"
    }
}

I see:

These show 404 as results because I don't know what salesforcePaths are valid but shows we can process and act on v1 and v2 config
Checklist

[x] Tests for new code

@joethreepwood occurs to me we only check highlight in main repo?
This might be worth highlighting. Would be good to get someone to test it since we don't have a salesforce instance to check with

@joethreepwood occurs to me we only check highlight in main repo?

We do, but we also have a weekly Product/Marketing sync too, to catch edge cases like this. :)


Fix CSS instructions in CONTRIBUTING.md

Fixed the task naming, which is actually generate-stylesheets. Also my editor seems to have picked up a whole bunch of trailing whitespaces. I hope it's ok to keep that in this commit.

Codecov Report

Merging #3053 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3053      +/-   ##
==========================================
- Coverage   33.38%   33.38%   -0.01%
==========================================
  Files         270      270
  Lines       39566    39566
==========================================
- Hits        13211    13208       -3
- Misses      24466    24476      +10
+ Partials     1889     1882       -7

Impacted Files
Coverage Δ

models/repo_indexer.go
49% <0%> (-2.98%)
:arrow_down:

modules/indexer/repo.go
60.86% <0%> (-2.61%)
:arrow_down:

models/repo.go
38% <0%> (+0.18%)
:arrow_up:

modules/process/manager.go
81.15% <0%> (+4.34%)
:arrow_up:

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 57edc31...eeddf43. Read the comment docs.

LGTM

LGTM


Picker on IOS

I am facing one issue with NativeBase.. Basically my requirement is to load the values of the Picker within native base from the server side. So on the first Render cycle there are no children to the Picker, i get the attached error because it makes the selected item as the label on the first instance. Is there any way to get around this. Also I do not want to have a default value set want to have some placeholder text what are the options.

You can do something like this
render() {
  var data = [];
  return (
    <Container>
      <Header>
        <Button>
          sefesf
        </Button>
      </Header>
      <Content>
        {data.length > 0 ?
          <Picker
            iosHeader="Select one"
            mode="dropdown"
            selectedValue={this.state.selected1}
            onValueChange={this.onValueChange.bind(this)}>
            {data.map((val, index) => {
              return <Item key={index} label={val} value={val} />
            })}
          </Picker> : <Text>Placeholder text</Text>}
      </Content>
    </Container>
  );
}

This will render Picker conditionally based on the length of array which is populated from server side. If array is empty, you can show another component which displays your placeholder text

Hi
This is my code to render items dynamically. State states is an array of states.
But it's throwing an exception.

![screen shot 2016-12-05 at 1 11 21 pm]
(https://cloud.githubusercontent.com/assets/17562095/20884234/fff0aa34-bb0f-11e6-9eca-52c75b7fdc6d.png)


New Blog: Behind the Scenes with Doodler

Updates in this pull request:

New blog in the website/blog directory called "Behind the Scenes with Doodler"
New images associated with the new blog in website/static/img/DoodlerProjectBlog
Comments added to clarify functionality in the following files:

app_funcs.py
plot_utils.py

Thanks!


Ignore plugin tests marked private_access

is there a way we can run both? e.g. in vision we first run all public (not private_access) and then all private (private_access)

Like this? (Current version)


Change hyperlink for "Create docs issue" to reference issue template

Current Behavior
The hyperlink under this text open a new, blank issue that is missing helpful information contained in the docs issue template.

Desired Behavior
Point to this issue template instead - https://github.com/layer5io/docs/issues/new?assignees=&labels=area%2Fdocs%2C+framework%2Fhugo%2C+language%2Fmarkdown&projects=&template=documentation.md&title=[Docs]

Contributor Guide and Resources

📚 Instructions for contributing to documentation

Layer5 documentation site and source

🎨 Wireframes and designs for Layer5 site in Figma (open invite)
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Hi! I'd like to help with this!
@viv511


Security: Vulnerability alerts: Dependabot: Bump rollup from 2.79.1 to 2.79.2 in /webview-ui in the npm_and_yarn group across 1 directory

Relates to https://github.com/lloydchang/cline-cline-fka-saoudrizwan-claude-dev/pull/6

Bumps the npm_and_yarn group with 1 update in the /webview-ui directory: rollup.
Updates rollup from 2.79.1 to 2.79.2

Release notes
Sourced from rollup's releases.

v.2.79.2
2.79.2
2024-09-26
Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5671: Fix DOM Clobbering CVE (@lukastaegert)

Changelog
Sourced from rollup's changelog.

2.79.2
2024-09-26
Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5671: Fix DOM Clobbering CVE (@lukastaegert)

3.29.5
2024-09-21
Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5671: Fix DOM Clobbering CVE (@lukastaegert)

4.22.4
2024-09-21
Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5670: refactor: Use object.prototype to check for reserved properties (@YuHyeonWook)
#5671: Fix DOM Clobbering CVE (@lukastaegert)

4.22.3
2024-09-21
Bug Fixes

Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (#5669)

Pull Requests

#5669: Ensure impure dependencies of pure modules are added (@lukastaegert)

4.22.2

... (truncated)

Commits

c9bd03d 2.79.2
48aef33 fix: resolve DOM Clobbering CVE-2024-43788 (backport to v2) (#5677)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.

Relates to https://github.com/cline/cline/issues/795#issuecomment-2492667746

Note to my future self:

If / when Saoud and Cline team review my pull requests for cline/cline and if revisions are needed, I'll try the following tactic:

Ask Cline to:

write a test for the changes in [sha]

and

write a test for feedback from Saoud and Cline team: [feedback here]

… to save me the effort from trying to re-remember what I did in pull requests from a long time ago.


Watchers are not set on metrics, params files if there are errors

Based on the #2733 . After I "fix" NaN to 1.0 experiments don't appear, it takes an edit to dvc.yaml to trigger this.
To reproduce. Open the project with already broken table (NaN), and try to fix it.
https://user-images.githubusercontent.com/3659196/200188255-1b04b840-74ce-4182-9bca-ce9987f40f71.mov
Extension version: v0.5.10
DVC version:
DVC version: 2.30.0 (pip)
---------------------------------
Platform: Python 3.9.12 on macOS-12.6-arm64-arm-64bit
Subprojects:
        dvc_data = 0.17.1
        dvc_objects = 0.7.0
        dvc_render = 0.0.12
        dvc_task = 0.1.3
        dvclive = 0.10.0
        scmrepo = 0.1.1
Supports:
        azure (adlfs = 2022.9.1, knack = 0.9.0, azure-identity = 1.10.0),
        gdrive (pydrive2 = 1.14.0),
        gs (gcsfs = 2022.8.2),
        hdfs (fsspec = 2022.5.0, pyarrow = 9.0.0),
        http (aiohttp = 3.8.1, aiohttp-retry = 2.7.0),
        https (aiohttp = 3.8.1, aiohttp-retry = 2.7.0),
        oss (ossfs = 2021.8.0),
        s3 (s3fs = 2022.5.0, boto3 = 1.21.21),
        ssh (sshfs = 2022.6.0),
        webdav (webdav4 = 0.9.7),
        webdavs (webdav4 = 0.9.7),
        webhdfs (fsspec = 2022.5.0)
Cache types: <https://error.dvc.org/no-dvc-cache>
Caches: local
Remotes: None
Workspace directory: apfs on /dev/disk3s1s1
Repo: dvc, git

We get the list of "extra files" to watch from the exp show output. We don't know which metrics files to watch until we have parsed the JSON.
From the demo: in.json is not covered under our default list of files. Therefore the watcher will not be triggered by any change until the JSON can be parsed and the file is added to the list.
FWIW we watch ['dvc.lock', 'dvc.yaml', 'params.yaml', '*.dvc'] by default. This list is updated once we parse the JSON output.
I think we can close this.