Feature Request: implement ddev list --continuous to eliminate UI polling

Feature Request:
implement ddev list --continuous that instead of exiting, the process will remain alive and will broadcast the current sites list when initially run, then will rebroadcast a new, complete site list whenever there has been a change to any site to stdout.
Anything else do we need to know:
currently, we are polling ddev list -j every 1000ms, parsing the JSON output, then comparing it to the current sitelist in the UI. If a difference is found, then the UI is updated accordingly. If the CLI would simply return an entire updated sitelist JSON whenever it detects a change, we can eliminate polling from the UI, as well as removing the "ignore ddev list polling spam" bandaid that we had implemented in logging.
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)
2 (from Randy): This should mean just putting the list functionality in an infinite loop, but exiting after one run if --continuous is not set.

@rickmanelius would love to lobby you on this. It should simplify ddev-ui and make it lighter-weight.

@rfay @andrew-c-tran I'm all good on this but wouldn't the "infinite loop" be even more process intensive when it's on or would be you still anticipate putting a time delay/spacer of ~ 100-1000ms?

+1 for a 1000ms delay in the loop somewhere. I don't think there's not a lot of point in asking the Docker daemon for new data much faster than that anyway.

Yes, it's an infinite loop, but it has a configurable pause that suits ddev-ui.

Yes, it's an infinite loop, but it has a configurable pause that suits ddev-ui.

@rfay how set are you on the loop pause being configurable? It's not a huge deal, but I think we should just pick a sane value and hardcode it. 1000ms will output changes often enough that the UI will be updated by the time the user switches windows to ddev ui.

I would say just make it an extra argument --loop-delay=xxxms ? So maybe the arg could be --loop ? Default the delay to 1000ms?

@cweagans It appears this is in progress but labels were not added and I'm not sure we got to an AC on whether or not the --loop-delay was worth putting in. FWIW since the only thing using this is ddev-ui and since the end-user testing seems to indicate it's a working amount, I don't know when changing that value would ever happen unless it was a preference in ddev-ui. Unless/until that is a request, I say we punt on making that configurable at this time.

PR is ready for review!


Change dependencySet scope of assembly from compile to runtime

Coauthored with Henry Saputra<EMAIL_ADDRESS>
Motivation
Currently, the dependencySet scope of assembly is set to compile for Pulsar deployment, this causes the Pulsar's distribution assembly to not include the transitive dependences that tagged with runtime scope.
Having the dependencySet as runtime instead of scope will actually include both scopes (since runtime scope includes the compile scope implicitly). This needs to be done before next release artifacts by Apache Bookkeeper generated by Gradle.
Modifications
Change dependencySet scope of assembly from compile to runtime in distribution/server/src/assemble/bin.xml
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as integration tests.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (don't know)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (yes)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[ ] no-need-doc
(Please explain why)

[ ] doc
(If this PR contains doc changes)

Closed as stale. Please rebase and resubmit the patch if it's still relevant.


[cxx-interop] ensure that the body of implicit virtual destructor is …

…defined before emitting the clang decl for it
This ensures that the destructor definition is emitted into the module's LLVM IR, fixing a linker error. The failure can be observed only on a Linux target, like Android, and Darwin/MSVC handle this case just fine.

@swift-ci please test

@swift-ci please test


added command for XAML binding

this commit fixes #16

Nice! What about if they pass in parameters? is that covered?


PDF contains garbled characters

The resulting PDF includes garbled characters – I suspect there is an issue with Unicode, as all of these seem to be punctuation characters.
It seems to be OK in HTML version though.
example (see in bold):

If You are an employee and have created the Contribution as part of your employment, You
need to have Your employer approve this Agreement or sign the Entity version of this document.
If You do not own the Copyright in the entire work of authorship, any other author of the
Contribution should also sign this â€“ in any event, please contact Us at ____________________

There are even more if you choose the FLA option.

Seems like incomplete or non-existent unicode handling in pdf generator. Maybe just switch to browser based pdf-generation instead.

Sounds like an OK solution to me.
In the modern age, I would almost consider offering MarkDown more important – see https://github.com/contributoragreements/ca-cla-chooser/issues/5

Or update the html2pdf thing and hope that fixes it. Personally, I disagree on markdown. While I personally like it in some documents, it's only useful in lieu of proper styling and to convert to pdf/html imo. (and the idea is that you can sign the pdf in some way, which does not work with markdown)
But apart from that, I would happily integrate it if there is an easy way. Do you know of a js library for it?

The use case I have in mind re MarkDown is that then it could be easily integrated into projects’ repositories – either as a text in the repository itself or in a Gist and then used by tools like CLA Assistant or CLA Hub.

Upgrading heroku stack and setting encoding seems to have fixed it. (please test) Ideally, use in-browser solution in the future but this was quicker for now.

LGTM, thanks :+1:


renew

renew

@rockedu First stage of verification passed, official domain for 培僑中學 is pkms.edu.hk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@rockedu Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Make build pass with ubuntu 24

I decided to not go this way, since it is easy to install gtest 1.12.0 on ubuntu 24 from source.


refactor concat, snoc, cons, closes #284

@gcanti are you ok with the chain / flatten approach?

@gcanti here are the perf diff I'm proposing (low hanging fruit)
map
map1 x 7,609,379 ops/sec ±0.49% (89 runs sampled)
map2 x 28,970,550 ops/sec ±1.13% (84 runs sampled)

chain
chain1 x 4,413,103 ops/sec ±0.74% (87 runs sampled)
chain2 x 12,084,771 ops/sec ±1.00% (87 runs sampled)

flatten
flatten1 x 7,799,193 ops/sec ±1.78% (84 runs sampled)
flatten2 x 17,044,084 ops/sec ±1.79% (82 runs sampled)

@gcanti basic rule that starts to appear: NEVER use native functions, period.

@sledorze Awesome. Added chain3, filter3 to perf, they look faster. WDYT?

AFK do they or do they are? (Small / big arrays) if so LGTM!

Puzzled by reverse1 variation

Ah it depends on the array length. After more tests:
filter3: yes, it's faster
chain3: nope
Note that for length > 15 chain1 is faster then chain2, so I would keep chain1

@gcanti Ok good! Thanks I had not enough time to do all the small/big collection comparison
May we go the path were we switch the implementation based on the length? I'm hesitating because:

It can change over time and would need to be backed by comparison perf test (which take some time to run)
It may change based on the actual VM (or not).

On the other side, getting a *3 / *4 boost on some operations is a lot.
It looks like a whole subject and may be should be part of another lib on which fp-ts could rely? (maybe there's an existing one)

May we go the path were we switch the implementation based on the length?

IMO no. I'm fine with some changes if the resulting code is not too messy and the gain is big (3x-4x) but I wouldn't go that route


DateTimePicker right click menu appearance

What steps will reproduce this issue?
The appearance of the context menu is not correct

Expected outcome
The context menu should be this way

--
Environment

MahApps.Metro v1.3.0-ALPHA137 (Prerelease)
Windows 7
Visual Studio 2013
.NET Framework 4.5

Te xaml is
<Controls:DateTimePicker SelectedDate="{Binding DatePickerDate, Mode=TwoWay}" IsReadOnly="{Binding ReadOnly}" PickerVisibility="All" />


FASTQ input

Added rudimentary support of input long-read FASTQ files and fixed some compile warnings. It still outputs FASTA since the quality data isn't relevant after correction. Please test.

I'll try to run this either tonight or tomorrow.  Looks straight-forward so I don't anticipate any problems.

So I think the FASTQ changes are working (running one last test currently).    I looked at the types and they were correct before (uint64_t type with %llu in printf), it's throwing a warning for me for each line you changed.  I'd rather keep the types matching unless it's doing something I'm not aware of.

I get exactly the opposite warnings - with llu and not lu - on RHEL. Seems like this is platform specific (https://stackoverflow.com/questions/14073877/printf-and-llu-vs-lu-on-os-x). You can leave it either way, I’ll get over the warnings.


Fix for Issue 314 by adding row to segs_game dbase when adding user

Iterate dbtool to v0.4
Add row to segs_game accounts table when adding new character. Closing #314

This is not needed since the coming changes to the way servers communicate will cause us to create GameDB accounts on the fly, and only AuthDB accounts are created by hand


Build is broken

on 16abf3853bb2907b5b2a0ff6e011509024323255
> apm test
....................F.....................................................................................................................
..........................................................................................................................................
............................................................

AtomicEmacs
  atomic-emacs:forward-sexp
    it moves all cursors forward one symbolic expression
      Expected '  aa
[0](bb cc)[1]
' to equal '  aa[0]
(bb cc)[1]
'.
        at .<anonymous> (file:///C:/Users/Marty/Documents/GitHub/atomic-emacs/spec/atomic-emacs-spec.coffee:137:38)

Finished in 9.732 seconds
336 tests, 422 assertions, 1 failure, 0 skipped

Tests failed

Running on windows 10 creators update.

Based on bisecting, the first commit with this behavior is 66e312bbfe75179504c9ae7b624d199d41a53ae7.  Interestingly before that, atom was different enough that it is possible that this test still failed.

Some further test strings which happen to pass
"[0]  aa (dd)\n[1](bb cc)\n" -> "  aa[0] (dd)\n(bb cc)[1]\n"
"[0]  aa dd\n[1](bb cc)\n" -> "  aa[0] dd\n(bb cc)[1]\n"
yet doesn't pass.  The bug has something to do with newlines.
"[0]  aa\n (dd)\n[1](bb cc)\n" -   aa\n[0] (dd)\n(bb cc)[1]\n"

Thanks!
I'm pretty certain this did work when it was written. A while back I traced it down to a bug (or at least undocumented change) in the core text-buffer package. IIRC it changed how \s is handled with respect to newlines. I had started trying to fix it there but never got around to finishing it.
In the meantime if you can find a simple workaround that'd be awesome.

Found a fix.  I will include it with my pull request for https://github.com/avendael/atomic-emacs/issues/103

apparently:
"\n".match(new RegExp("\W", "gmi"))
-> null
'\n'.match(/[\W]/gim)
-> ["\n"]
"\n".match(new RegExp("[\W\n]", "gmi"))
["\n"]

So, our bug lies someplace in native code.....

And by native code, I mean in Chromium and Chrome.  The same behavior is demonstrated in my web browser's dev tools.

Found my mistakes... now I have to see if I can find the underlying bug.

This time I have got it right.  The difference is that atom text-buffer considers /\W/ a single line regular expression, while /[\W\n]/ is a multi-line regular expression as determined by the regular expression on text-buffer/lib/helpers.js line 6.

Apparently I am on a slightly old version, but the bug is still there. https://github.com/atom/text-buffer/blob/master/src/helpers.js#L3

Root cause: https://github.com/atom/text-buffer/issues/226

Workaround in https://github.com/avendael/atomic-emacs/pull/130

Fix was merged. Thanks @MartyGentillon !


how to remove installed packages that no longer needed?

for example, I just installed the "http" package with:

add "http: ^0.12.0" to the secion dependencies in the file pubspec.yaml
run command "flutter packages get"

That's great, super easy.
but what if I don't need it anymore? I want to remove it from my project. following is what I have done.

I have removed what I added to the file pubspec.yaml
run command "flutter packages get" again
build project

but the http package is still available in my code. What else I need to do, please?

Packages you add to pubspec.yaml are downloaded to
~/.pub-cache/... per version and shared between all your projects.
If a package is from pub.dartlang.org it will be stored in
~/.pub-cache/hosted/pub.dartlang.org/
(if PUB_CACHE is set $PUB_CACHE/hosted/pub.dartlang.org/ would be used instead)
If you remove a package from pubspec.yaml but another dependency depends on it, the package will still be listed in pubspec.lock and therefore will be available in your project.
You should get an error if your custom code imports a package that is not listed in dependencies: in pubspec.yaml, but otherwise this doesn't result in a warning.
You can investigate transitive dependencies using  flutter packages pub deps
Please consider asking support questions in one of the other channels listed at http://flutter.io/support .

It took me more than 3 days to try  all differently way. But finally I found, you need to go into the "pubspec.lock" file. Then go to the library and change the version there. Then go back to the file "pubspec.yaml" and run Packages get and it succeeds.


Dispose statusBarItem if there is no more message

Code Settings Sync Version: 2.7.0
At present, after sync extension displayed some message and then cleared the message after timeout, the statusBarItem still holds a place. This will cause a weird gap between other statusBarItems, e.g.

If I disable the sync extension, this is the normal appearance

So I think it would be better to dispose the statusBarItem if there is no more message. And next time when we need to display a message, we can recreate it or just use setStatusBarMessage API

Its fixed.

cool

Yes, the message 'Reading settings online' is fixed.
But it seems that the message 'you already have the latest settings' isn't fixed?


Windows Server RDS

Would it be possible to include the powershell commands referenced here: https://www.kolmann.at/2016/04/add-ssl-cert-to-rdp-session/
This would allow you to support Remote Desktop Servers.

The issue with this is that this tool requires web access for LE to verify to generate a cert. This means your RDS server will also need IIS (or some other webserver) configured. If you're using IIS on an RDS server, you probably are going to want to setup RD Gateway. Now you would need to import the cert into that as well... so on and so forth.
It's not impossible, but it's probably outside the scope of this tool.

Hi, I'm running RDS with RD Gateway for a charity and I've successfully installed LE certs on IIS thanks to letsencrypt-win-simple and also manually added the cert to RDS Gateway, I was wondering if it would be possible to include and automate that certs are also added to RDS Gateway at the same time as IIS. Automating it would be nice, as at every renewal there wouldn't be no manual setting required any more. Which is the primary advantage of LE. It would be a VERY nice feature. Otherwise I think I'll buy a commercial cert which has a validity of 3 years 💃

As I said above it would probably be outside the scope of this tool to do that, as there are so many variables... but it is possible (I've done it) to use a powershell script to import the certs.
If you configured via server manager in 2012+, you should have a connection broker and the ability to use this suite of cmdlets:
https://technet.microsoft.com/en-us/library/jj215488.aspx
https://technet.microsoft.com/en-us/library/jj215464.aspx

You should be able to do this in 1.9.3 with a script - see: https://github.com/Lone-Coder/letsencrypt-win-simple/wiki/Install-Script


Fix sidebar location on scroll

Problem Description

When scrolling through search results, there is a go-to-top button which will take you to top to change your query or anything.
I suppose the major reason for implementing this, against implementing search bar top fixed is to create more space for the images to fit in
But while scrolling down, the space to the left occupied by the sidebar still exists and it is completely blank, so why not occupy it?

Solution Description

I propose to keep the sidebar location fixed, so that the filters are actually visible even after scrolling, and not just white-space there

Alternatives

None

Screenshots
Initially

After Scrolling

The sidebar is completely white and empty, rather have filters over there.
Additional context

I would like to take up this feature (issue), if it is accepted.
Additionally, I really feel a search bar fixed to the top after scrolling a bit will be helpful. Atleast in larger screens it will be helpful and more intuitive as opposed to the current go-to-top button. Let me know about this.

@nilshah98 feel free to take this up. We've discussed with @brenoferreira and @panchovm and it makes sense to have the fixed search bar at the top, and fixed filters on the left. We will be making some changes to the styles of those in future sprints, but making them fixed will remain part of the design.

Will put in a PR for this in the coming week.
Thanks @annatuma

Hey, fixed siderbar and searchbar has been implemented and referenced in PR #596
This might be out of line, but I have a few suggestions-

To omit a fixed searchbar up top, as we already a back-to-top button.
Also, the fixed search bar at the top just uses a lot of space, which can be rather used to display more of the images.
Whereas an alternative is to remove the back-to-top button since there's little use for it left.


Pipeline fix

Change sourcecodecredential name to avoid conflicts between clusters, fix https://github.com/rancher/rancher/issues/11669
Fix clusterpipeline panic on cluster deletion, partially fix https://github.com/rancher/rancher/issues/11648
Fix reference id with namespace so that pipeline/execution links can list correctly

LGTM


[#776] WebSocket API.

Fixes #776 .
Changes proposed in this pull request:

Implement WebSocket interface as-is in the HTML5.
Implement related events, such as MessageEvent and CloseEvent.

Note: Though #776 is related to #780, it won't be easy to implement .NET ClientWebSocket, as it goes somewhat apart from HTML5 WebSocket (I'm researching this question now).

Hello @Dia6lo,
Thank you very much for the pull request!
Before a review of the pull request we would need the CLA form accepted. You can find more information in CONTRIBUTING.md.
The full CLA is available here.
When you get a chance, please review the CLA and complete the CLA Acceptance Form. If you have any questions, please just let us know.

Okay, I've completed this form.

Thank you, Andrey! We will review the pull request soon and maybe merge into 1.12.

Hi @Dia6lo!
Thank you for your amazing contribution. It is merged into master and will be included into 1.12.


KAFKA-3214: Added system tests for compressed topics

Added CompressionTest that tests 4 producers, each using a different compression type and one not using compression.
Enabled VerifiableProducer to run producers with different compression types (passed in the constructor). This includes enabling each producer to output unique values, so that the verification process in ProduceConsumeValidateTest is correct (counts acks from all producers).
Also a fix for console consumer to raise an exception if it sees the incorrect consumer output (before we swallowed an exception, so was hard to debug the issue).

The new system test passes locally and on Jenkins.

LGTM

Nice @apovzner, thanks for improving our system tests coverage!

re-run impacted system tests, they passed.

@hachikuji and @granders I addressed your comments. Now compression test tests both new and old consumer. Compression test runs until each producer produces at least 1000 messages.

@apovzner Thanks for the updates. LGTM

LGTM.


proposal: Go 2: Replace the 'new' builtin with composite zero literals for all types

This is sort of spawning out of #19642, and may be related to its resolution.
Currently, struct types (and, less commonly, array, slice, and map types) can have a pointer to a zero value constructed in two different ways: new(T) and &T{}. I've never seen a style guide recommending one or the other, but the latter is more clear next to &T{foo}.
Having two ways to do something isn't ideal, so one potential solution is to allow composite literals for all types (with one possible exception I'll get to). For any type for which Go 1 does not allow composite literals  (numeric, boolean, function, interface, channel, and pointer types), the literal must be empty and yields the zero value. So instead of writing new(int), you would write &int{}.
If this is done, the new builtin becomes redundant. We can therefore remove it from the language to simplify. I'm not sure this is necessarily a good idea, but it would remove the duplication.
The only issue is pointer types. Under this proposal, I think that *T{} is ambiguous between "a pointer to a zero T" and "a nil pointer to T" (I frequently mistype *T{} for &T{}). I'm not sure the best resolution for this.

This version would mesh a little better with https://github.com/golang/go/issues/12854, too.

You seem to be suggesting that we permit &T{} for any type, while still permitting &T{V} where T is an aggregate type.  I'm not sure that buys us much.  If we were starting from scratch it might be worth discussing, but given that we have new, we need a significant benefit to providing another way to write new.

That's correct, but it is also a suggestion to get rid of new altogether, because of the redundancy.
It may be a comparatively low-value feature, but it's one that I wanted to put forward especially in connection with other proposals relating to compound literals and zero values.

But getting rid of new altogether is not backward compatible, so now you need a really big benefit.
Every change to the language has benefits and drawbacks.  Eliminating new has a huge drawback: existing code stops working.  It needs a correspondingly huge benefit.
To put it another way: Go is now an existing working language that people are actively using.  It's not a playground for language design.  Breaking existing users is pretty much a non-starter.

Also you are implying that having two ways of accomplishing something is undesirable, rather than not ideal. Unfortunately programming is full of these, and a theoretical computer scientist would probably argue this is unavoidable.
Alternatively, do we get rid of arrays and slices because we have maps?

I am not sure the proposal covers all use cases of new, e.g. if the type to be allocated is determined at the run time. Without it we would have to use reflection and recursion to do so, and in addition the code would break if new builtin types are added to the language.

@ghasemloo The existing new operator only supports static types. To the extent that the situation you describe is a problem, it is already a problem today.

Related to #9097.

This is basically the same idea as #9097.  Closing in favor of the earlier issue.


In which part observation-entity and action-groups match

I am wondering in which part the observation-entity and action-groups match in your released code.

Hi there,
same issue with #12
Cheers


Cloud Load Balancing SKU improvements starting August 1, 2023

Google has written and announced:

After August 1, 2023, you'll see the following changes for SKUs related to Cloud Load Balancing:

We’ll remove the SKUs from their existing Compute Engine product category and create new SKUs in the Networking category.
For all load balancer types:

We’re creating new SKUs for forwarding rules under the Networking category. These new SKUs apply to the forwarding rule minimum and additional charges. Currently, forwarding rule SKUs are in the Compute Engine category.
We’ll split inbound data processing for the three regions that make up the Americas group (us-central1, us-east1, and us-west1) into separate SKUs for each region.

For internal HTTP(S) load balancing:

For consistency with other load balancers, we’re splitting the data processing SKUs into separate inbound and outbound SKUs. Currently, these are grouped into a single SKU (for both inbound and outbound data processing) per region.
We’ll split proxy instance SKUs for the three regions that make up the Americas group (us-central1, us-east1, and us-west1) into separate SKUs for each region.

For internal TCP/UDP load balancing, there is a one to one mapping between the new SKU IDs in the Networking category to the current SKU IDs in the Compute Engine category.
For global external HTTP(S) load balancers, external TCP/SSL proxy load balancers and network load balancers, we're splitting inbound data processing into separate SKUs for each load balancer type. Currently, inbound data processing is grouped into a single SKU per region for all of these load balancers.

I will therefore remove Load Balancer from this calculator. Anyone who wants to deal with the new pricing is welcome to put it in.

Load balancer removed: https://github.com/Cyclenerd/google-cloud-pricing-cost-calculator/commit/6b8da88b525811fa6e0f4523f4d1231eab8af5fe


Add support for flatpak-external-data-checker

We need to add the x-checker-data metadata to the various modules so that flatpak-external-data-checker can tell us about updates. See https://github.com/endlessm/endless-key-flatpak/issues/45 for the equivalent work on the devel flatpak.

According to flatpak-external-data-checker's document, Flathub runs flatpak-external-data-checker hourly for all Flatpak repos under github.com/flathub.  So, we have to add x-checker-data into modules.


Ignite-2.5.1-master-7196

PR seems to be temporary for testing, closing it, for now, feel free to reopen if it is needed.


Help?

Hi!
Dude, congrats! awesome and NEEDED app.
I'm a server side developer, had some experience with Strava API and can help if you need.
(I can even run some sort of web service if you need).
Unfortunetly I'm no good in android developing (Java is not my business), but I'm picking it up again....

Thank you!
I have one idea which I would like to add into it in the future: show all
active cyclists around you on map. I suppose there should be part of
server-side.
But at the moment, I suppose the best priority is to make a bit more stable
in some simple algoritms like interval-detection and strava-calculation.
The next big step is redesign of the main screen.
Regards,
Alexander.
30 авг. 2017 г. 12:58 ПП пользователь "yurisa2"<EMAIL_ADDRESS>написал:

Hi!
Dude, congrats! awesome and NEEDED app.
I'm a server side developer, had some experience with Strava API and can
help if you need.
(I can even run some sort of web service if you need).
Unfortunetly I'm no good in android developing (Java is not my business),
but I'm picking it up again....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/inv2004/cycle-computer/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuETRNzCYvsjtbN3zFTYM2wGhwxRe8eks5sdZTSgaJpZM4PHsBX
.

I will update TODO list soon.

Please find TODO list.


re-add the consolidation controller that was removed after a rebase

Fixes #
Description
Fix error that was introduced by a re-base.
How was this change tested?

E2E test

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

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

@tzneal this fix supposed to solve the problem we have with the consolidation :
one or more objects failed to apply, reason: admission webhook “defaulting.webhook.provisioners.karpenter.sh” denied the request: mutation failed: cannot decode incoming new object: json: unknown field “consolidation”.


fix: drop distutils

Description
I manually tested the changes.
There was also a typo in one of the readme examples.
Fixes #92

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Remove deprecated python package distutils

Upgrade test results for build 933

Modules upgraded from origin/HEAD => fix-92
Terraform upgraded from 1.2 => 1.3

⚠ If plan results are not all 0's, review the plan output to ensure backward compatibility.

Example
Modules to upgrade
Plan
Upgraded?
Patched
Upgraded?

join-path
instance-typejoin-path
0, 0, 0
:white_check_mark:

instance-type
instance-typejoin-path
0, 0, 0
:white_check_mark:


Implement tests in a way that is not timestamp dependent

Will fill details later

@brunobat do you have the details for this issue? If you do, please post it here. Otherwise, please close it.

@Azquelt @yasmin-aumeeruddy will take a look at this.

This issue might be fixed by #95


preauth for pgbackups schedule command

Nice. I think this might be true for some of the other backup commands as well--I can review that soon but I don't have time right now.

this isn't a huge deal, the workaround is simply to preauth before the command, but if you can figure out what those might be sometime next week we could tack them on this PR

Yeah, can do. Feel free to remind me.

I think we can close this as obsolete, yeah?


Handle Secrets management

Issue
We need to handle long term storage/security for the cryptographic secrets of the Mithril networks (especially for mainnet):

Genesis Secret Key
Eras Secret Key
Cardano Era Address Secret Key

To do

[ ] Creation of the secrets by security team and secure access for dev team (IT Ticket to create)
[ ] Create verification keys in Mithril GitHub repository
[ ] Fund Cardano Era Address Secret Key with some ADA

Parent Issue
#767

Ticket: https://input-output.atlassian.net/servicedesk/customer/portal/2/ITCR-6366?created=true

IT grant me with an IOG account in Vaultwarden. @jpraynaud  what should I do with it?


After RequestClientCredentials is not called the ProfileService

I have tried to get access token from my console application like this:
var disco = await DiscoveryClient.GetAsync("http://localhost:7880");
var tokenClient = new TokenClient(disco.TokenEndpoint, "delegation.client", "secret");
var tokenResponse = await tokenClient.RequestClientCredentialsAsync("api1");

I get the access token without claims but I have a created api resource where I specified claims: sub, name.
I have tried debug if is claims getting via ProfileService but the method GetProfileDataAsync is not fired.
My profile service with using Asp.Net Identity:
public virtual async Task GetProfileDataAsync(ProfileDataRequestContext context)
        {
            var profileService = this;
            var subjectId = context.Subject.GetSubjectId();
            var byIdAsync = await profileService._userManager.FindByIdAsync(subjectId);
            var async = await profileService._claimsFactory.CreateAsync(byIdAsync);
            var claims = async.Claims.ToList();
            await AddLocationClaims(claims);

            context.AddFilteredClaims(claims);
        }

This method is not called - after calling: RequestClientCredentialsAsync.
I have used the IdentityServer4 - v 1.5.2 with IdentityServer4.EntityFramework 1.0.1. and IdentityServer4.AspNetIdentity 1.0.1.
How can I get access token with sub and name claims, where could be a problem?
Thank you.

I got it, because I don't use specific user credentials but only client credentials.
I close it. :)


caravel db_upgrade fails on MySql

The command caravel db_upgrade fails with the following error:
2016-05-26 21:49:47,019:INFO:flask_appbuilder.base:Registering class MyIndexView on menu
2016-05-26 21:49:47,025:INFO:flask_appbuilder.base:Registering class UtilView on menu
2016-05-26 21:49:47,030:INFO:flask_appbuilder.base:Registering class LocaleView on menu
2016-05-26 21:49:47,035:INFO:flask_appbuilder.base:Registering class ResetPasswordView on menu
2016-05-26 21:49:47,054:INFO:flask_appbuilder.base:Registering class ResetMyPasswordView on menu
2016-05-26 21:49:47,071:INFO:flask_appbuilder.base:Registering class UserInfoEditView on menu
2016-05-26 21:49:47,087:INFO:flask_appbuilder.base:Registering class AuthDBView on menu
2016-05-26 21:49:47,099:INFO:flask_appbuilder.base:Registering class UserDBModelView on menu List Users
2016-05-26 21:49:47,150:INFO:flask_appbuilder.base:Registering class RoleModelView on menu List Roles
2016-05-26 21:49:47,200:INFO:flask_appbuilder.base:Registering class UserStatsChartView on menu User's Statistics
2016-05-26 21:49:47,233:INFO:flask_appbuilder.base:Registering class PermissionModelView on menu Base Permissions
2016-05-26 21:49:47,268:INFO:flask_appbuilder.base:Registering class ViewMenuModelView on menu Views/Menus
2016-05-26 21:49:47,306:INFO:flask_appbuilder.base:Registering class PermissionViewModelView on menu Permission on Views/Menus
2016-05-26 21:49:48,030:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.tables".
2016-05-26 21:49:48,030:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.tables.TableExtension".
2016-05-26 21:49:48,033:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.fenced_code".
2016-05-26 21:49:48,033:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.fenced_code.FencedCodeExtension".
2016-05-26 21:49:48,034:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.codehilite".
2016-05-26 21:49:48,034:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.codehilite.CodeHiliteExtension".
2016-05-26 21:49:48,043:INFO:flask_appbuilder.base:Registering class TableColumnInlineView on menu
2016-05-26 21:49:48,081:INFO:flask_appbuilder.base:Registering class DruidColumnInlineView on menu
2016-05-26 21:49:48,133:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.tables".
2016-05-26 21:49:48,133:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.tables.TableExtension".
2016-05-26 21:49:48,133:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.fenced_code".
2016-05-26 21:49:48,134:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.fenced_code.FencedCodeExtension".
2016-05-26 21:49:48,134:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.codehilite".
2016-05-26 21:49:48,134:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.codehilite.CodeHiliteExtension".
2016-05-26 21:49:48,138:INFO:flask_appbuilder.base:Registering class SqlMetricInlineView on menu
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.tables".
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.tables.TableExtension".
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.fenced_code".
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.fenced_code.FencedCodeExtension".
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.codehilite".
2016-05-26 21:49:48,167:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.codehilite.CodeHiliteExtension".
2016-05-26 21:49:48,172:INFO:flask_appbuilder.base:Registering class DruidMetricInlineView on menu
2016-05-26 21:49:48,205:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.tables".
2016-05-26 21:49:48,205:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.tables.TableExtension".
2016-05-26 21:49:48,205:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.fenced_code".
2016-05-26 21:49:48,206:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.fenced_code.FencedCodeExtension".
2016-05-26 21:49:48,206:DEBUG:MARKDOWN:Successfuly imported extension module "markdown.extensions.codehilite".
2016-05-26 21:49:48,206:DEBUG:MARKDOWN:Successfully loaded extension "markdown.extensions.codehilite.CodeHiliteExtension".
2016-05-26 21:49:48,208:WARNING:flask_appbuilder.models.filters:Filter type not supported for column: password
2016-05-26 21:49:48,211:INFO:flask_appbuilder.base:Registering class DatabaseView on menu Databases
2016-05-26 21:49:48,261:INFO:flask_appbuilder.base:Registering class TableModelView on menu Tables
2016-05-26 21:49:48,312:INFO:flask_appbuilder.base:Registering class DruidClusterModelView on menu Druid Clusters
2016-05-26 21:49:48,365:INFO:flask_appbuilder.base:Registering class SliceModelView on menu Slices
2016-05-26 21:49:48,406:INFO:flask_appbuilder.base:Registering class SliceAsync on menu
2016-05-26 21:49:48,454:INFO:flask_appbuilder.base:Registering class DashboardModelView on menu Dashboards
2016-05-26 21:49:48,505:INFO:flask_appbuilder.base:Registering class DashboardModelViewAsync on menu
2016-05-26 21:49:48,540:INFO:flask_appbuilder.base:Registering class LogModelView on menu Action Log
2016-05-26 21:49:48,592:INFO:flask_appbuilder.base:Registering class DruidDatasourceModelView on menu Druid Datasources
2016-05-26 21:49:48,639:INFO:flask_appbuilder.base:Registering class R on menu
2016-05-26 21:49:48,646:INFO:flask_appbuilder.base:Registering class Caravel on menu
2016-05-26 21:49:48,709:INFO:flask_appbuilder.base:Registering class CssTemplateModelView on menu CSS Templates
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade  -> 4e6a06bad7a8, Init
Traceback (most recent call last):
  File "/usr/bin/caravel", line 113, in <module>
    manager.run()
  File "/usr/lib/python2.7/site-packages/flask_script/__init__.py", line 412, in run
    result = self.handle(sys.argv[0], sys.argv[1:])
  File "/usr/lib/python2.7/site-packages/flask_script/__init__.py", line 383, in handle
    res = handle(*args, **config)
  File "/usr/lib/python2.7/site-packages/flask_script/commands.py", line 216, in __call__
    return self.run(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/flask_migrate/__init__.py", line 235, in upgrade
    command.upgrade(config, revision, sql=sql, tag=tag)
  File "/usr/lib/python2.7/site-packages/alembic/command.py", line 174, in upgrade
    script.run_env()
  File "/usr/lib/python2.7/site-packages/alembic/script/base.py", line 397, in run_env
    util.load_python_file(self.dir, 'env.py')
  File "/usr/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 93, in load_python_file
    module = load_module_py(module_id, path)
  File "/usr/lib/python2.7/site-packages/alembic/util/compat.py", line 79, in load_module_py
    mod = imp.load_source(module_id, path, fp)
  File "/usr/lib/python2.7/site-packages/caravel/migrations/env.py", line 90, in <module>
    run_migrations_online()
  File "/usr/lib/python2.7/site-packages/caravel/migrations/env.py", line 83, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "/usr/lib/python2.7/site-packages/alembic/runtime/environment.py", line 797, in run_migrations
    self.get_context().run_migrations(**kw)
  File "/usr/lib/python2.7/site-packages/alembic/runtime/migration.py", line 312, in run_migrations
    step.migration_fn(**kw)
  File "/usr/lib/python2.7/site-packages/caravel/migrations/versions/4e6a06bad7a8_init.py", line 71, in upgrade
    sa.UniqueConstraint('datasource_name')
  File "<string>", line 8, in create_table
  File "<string>", line 3, in create_table
  File "/usr/lib/python2.7/site-packages/alembic/operations/ops.py", line 1098, in create_table
    return operations.invoke(op)
  File "/usr/lib/python2.7/site-packages/alembic/operations/base.py", line 318, in invoke
    return fn(self, operation)
  File "/usr/lib/python2.7/site-packages/alembic/operations/toimpl.py", line 101, in create_table
    operations.impl.create_table(table)
  File "/usr/lib/python2.7/site-packages/alembic/ddl/impl.py", line 194, in create_table
    self._exec(schema.CreateTable(table))
  File "/usr/lib/python2.7/site-packages/alembic/ddl/impl.py", line 118, in _exec
    return conn.execute(construct, *multiparams, **params)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 914, in execute
    return meth(self, multiparams, params)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/ddl.py", line 68, in _execute_on_connection
    return connection._execute_ddl(self, multiparams, params)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 968, in _execute_ddl
    compiled
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1146, in _execute_context
    context)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1341, in _handle_dbapi_exception
    exc_info
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 202, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context
    context)
  File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute
    cursor.execute(statement, parameters)
  File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1071, 'Specified key was too long; max key length is 767 bytes') [SQL: u'\nCREATE TABLE datasources (\n\tcreated_on DATETIME NOT NULL, \n\tchanged_on DATETIME NOT NULL, \n\tid INTEGER NOT NULL AUTO_INCREMENT, \n\tdatasource_name VARCHAR(256), \n\tis_featured BOOL, \n\tis_hidden BOOL, \n\tdescription TEXT, \n\tdefault_endpoint TEXT, \n\tuser_id INTEGER, \n\tcluster_name VARCHAR(250), \n\tcreated_by_fk INTEGER, \n\tchanged_by_fk INTEGER, \n\tPRIMARY KEY (id), \n\tUNIQUE (datasource_name), \n\tCHECK (is_featured IN (0, 1)), \n\tCHECK (is_hidden IN (0, 1)), \n\tFOREIGN KEY(user_id) REFERENCES ab_user (id), \n\tFOREIGN KEY(cluster_name) REFERENCES clusters (cluster_name), \n\tFOREIGN KEY(created_by_fk) REFERENCES ab_user (id), \n\tFOREIGN KEY(changed_by_fk) REFERENCES ab_user (id)\n)\n\n']

The app has been configured to use MySQL and the MySQL database is configured with
DEFAULT CHARACTER SET 'utf8'
DEFAULT COLLATE 'utf8_general_ci'

The operating system is CentOs 7.2 and the MySQL database is MySQL 5.5.44-37.3 (Percona Server Release 37.3).
My guess is that there are indexes on a varchar field that is too long (in utf8, each char is 4 bytes, so the limit is 191 char).

Which version of Caravel are you using? I suppose it should have been fixed in #459

I'm using 0.9.0.
I see that your patch have not been included in 0.9. When I looked up the error I've seen it committed at the same time 0.9.0 was released so I assumed it was in 0.9
This means I'll need to checkout from master hoping that it works (Yesterday was broken :-( but I hadn't had time to investigate)


Pose.heading cache is not invalidated when changing orientation.

BUG REPORT
High Level Description
The mutable Pose class does not update the cached heading value when orientation is updated directly. There is a reset_with(..) method that will do that but it is not enforced.
SMARTS version
[e.g. 0.5.0]
Impact [If known]
Heading can become desynchronized from orientation.

When this is fixed properly, we should probably audit and remove places where we've hacked around this in the past (such as lines 458-459 of ros_driver.py).


Curate climate-change topic

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Climate change affects every person on this planet and is one of the big challenges of our century. There are 347 repositories with the climate-change topic. Currently, Hacktoberfest features the climate-change topic amongst the covid-19 topic, which means that the topic is currently shared to a broad audience.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

PS: It would be great if you could add a hacktoberfest-accepted label to this PR or the hacktoberfest topic to this repository :smiley:

👋 @fxedel Sorry, but this repo isn't participating in hacktober fest this year.

@fxedel The topic content looks good, but I'm not sure about the logo. I tried to look it up, but it doesn't seem to be an official logo. If that's the case, could you remove it?

Hey @BlakeWilliams, I used Ed Hawkins' warming stripes as a logo. They are not an official logo (how could a phenomenon like climate change even have an official logo?), but have been widely used as a symbol for global warming. Organizations like Scientists for Future and the United States House Select Committee on the Climate Crisis have adopted the warming stripes in their logo, it has been in the cover of The Economist and The Guardian and it's a reoccurring symbol in climate change protests and campaings.
Furthermore, the covid-19 GitHub topic also has a logo, whereas the covid-19 pandemic can't have an official logo either.
It'll be great if we could keep the image, as it's very strong connected to climate change and is, in my opinion, the best replacement for an official logo (which doesn't exist). However, if you insist on it, I can also delete the picture.

@fxedel That makes sense to me, thanks for the contribution! 🎆


Albums / Collections

As a user, sometimes I have multiple related images I want to share under one URL.

I am going to move this to Icebox since it is potentially a new feature and not a fix to the existing functionality.  What do we want to add here, or is this a change/update to channels?

This is not very important with the addition of channels.

Now that we have channels, we can likely close this unless we want to revisit a concept of collections managed by a DB on Spee.ch.  Likely we can close this; marking icebox for now.


Add Heroku config

Added sbt-heroku plugin, configuration, and documentation for dpeloying to Heroku

Hi @jkutner
Thanks for the PR. It's not going to be merged into master because not everybody uses heroku and wants to have heroku settings in their config. However, I've pushed your commit in a separate branch which can be used if one wants to deploy to Heroku.

Would you accept a PR with Procfile and app.json files in the root directory? This type configuration sits outside of the build.sbt or other configuration.
If not, would you accept a short description, and link to the #deploy-heroku branch in the README.md in the master branch?
The reason I'd like to see this in the master branch is that the project's structure is a little unusual, so deployment can be confusing. I understand your concern about muddling the config, but I figured it wasn't much different to having Eclipse config when many people do not use Eclipse.
Regardless, thanks for create the branch!

The build.sbt is already quite complicated. So I want to avoid adding even more settings.
Eclipse and IntelliJ are the two major IDEs used with Scala, that's why I have to make sure they work out of the box.
I would prefer a Heroku configuration which sits outside of build.sbt. I would be grateful if you could provide a PR with Procfile, app.json and a short description in the README.md.


Upgrade README docs according to <IP_ADDRESS> changes

Currently it says:

Elm type generation coutesy of krisajenkins/elm-export.

But it should be elm-bridge instead. It also would be nice to have updated examples accordingly.

Thanks, fixed! PRs with other fixes would be welcome!


:bug: Title does not contain subevents

What happened?
When having a subevent its name is not used for the image title in the metadata.
What did you expect?
No response
Do you have an idea how to fix the bug or did you create a brach containing the bugfix?
No
Which is the version you found the bug in?
Latest version
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Done with commit: 39c84780fa4213b7397c504db554d93f3de8f61b


Metadata added into spotdata (plus rejigging).

#235
Adding metadata to spotdata cubes, including forecast reference time and forecast period. Also somewhat rewriting cube construction in spotdata in the hope that it can all get factored out to common utilities in a future ticket.
Testing:

[x] Tests need to be rewritten, don't currently work,
[x] CLI tests also fail.

To satisfy the second acceptance test in #235 I think we also need Laurence to review this change. I've added him to the reviewers

Changes look good to me

[x] unit tests have been run and pass.
[x]  command line interface acceptance tests run and pass.
[x] The Acceptance Criteria defined within the associated issue has been met.
[x] The criteria within the Definition of Done has been satisfied.


add more tests

@colinbull Could you take a look at this?  Testing strategy is to have the sample erasing TP simply reify a set of static values which reveal what the type provider is told about the type involved, and to check those things correspond roughly to the values given by .NET reflection over the typeof of the type.
We repeat this for a number of types.
Note there are a fair number of inaccuracies/bugs for the reasons noted in the tests.  The devil is in the detail :)  In particular every time the TAST is different to the .NET compiled form we see it.  (e.g. because of all the crap we do in IlxGen.fs)
Haven't done anything with

generic types
generic methods
custom attributes (these are important I think since they may guide the TP)
events
fields
generic parameters
...

Note I do this steps to run the tests:
build net40 debug
cd tests\fsharp\typeProviders\samples\TypePassing\Erasing
.paket\paket.bootstrapper.exe
.paket\paket.exe install
msbuild
..\..\..\..\..\..\debug\net40\bin\fsc.exe script.fsx
.\script.exe

And then iterate with
msbuild && ..\..\..\..\..\..\debug\net40\bin\fsc.exe script.fsx & .\script.exe

Ok no problem I can have a look at this tomorrow evening.. been fighting the enterprise devils today and it takes all the strength I can muster. ;)


StackOverflow issue when generating OpenAPI specification with cyclic ballerina records which have same type inclusion

Reproduce the issue: run the openapi command with the below sample file
bal openapi -i <service.bal>
import ballerina/http;

type ABC record {|
    string id?;
|};

type Patient record {|
    string id?;
    Reference ref?;
|};

public type Reference record {|
    *ABC;
    string reference?;
    string 'type?;
    Identifier identifier?;
    string display?;
|};

public type Identifier record {|
    *ABC;
    string value?;
    Reference assigner?;
|};

service / on new http:Listener(9090) {

    // Read the current state of the resource represented by the given id.
    isolated resource function get fhir/r4/Patient/[string id]()
    returns @http:Payload {mediaType: ["application/fhir+json", "application/fhir+xml"]}
    Patient {
        Patient patient = {
            id: id
        };
        return patient;
    }
}

Closing with https://github.com/ballerina-platform/openapi-tools/pull/1489


The visitor selects a movie from two displayed lists presented to them.

As a "User", I can choose a film from two presented lists, click on it, and access the desired subtitles and unique words contained in the subtitles of the selected film.
Main Scenario
When choosing a movie from the suggested options, I click on it, and on the new page, I see two active fields. By clicking on the first one, I receive subtitles in a text format.
When clicking on the second field, it displays the number of unique words in the text. The table begins with one column in the first row. Starting from the second row, the table is divided into two columns. The first column contains all the words, and the second column contains their corresponding contextual translations based on the subtitles text.
Alternative Scenario
If, for any reason, the subtitles become unavailable on the external website, the user will be shown an error page and will be automatically redirected to the previous page.

Contextual translation has not been implemented yet. I will implement it through an external API service for machine translation - https://www.deepl.com/.


[NCCH ERROR]

[NCCH ERROR] CXI's ID cannot be modified without the ability to resign the AccessDesc
I am attempting to decrypt Mario Kart 7 from many different sources (none work)

It seems my cia-unix is borked

Note: decrypt.py is not able to decrypt all types of cia.
Try compiling latest cia-unix source to be sure it doesn’t depend on that.

Just flagging that I hit this too
[NCCH ERROR] CXI's ID cannot be modified without the ability to resign the AccessDesc
[RESULT] Failed to build CCI (ret = -3)
Decryption failed

My env is
Crystal 1.5.0 [994c70b10] (2022-07-06)
Python 2.7.16 (default, Aug 30 2021, 14:43:11)

This is using master branch, can try v0.1.1 too

That NCCH ERROR is caused by a non-implemented makerom feature
Code reference
if(/*keys->rsa.requiresPresignedDesc && */!IsCfa(hdr)){
	fprintf(stderr,"[NCCH ERROR] CXI's ID cannot be modified without the ability to resign the AccessDesc\n"); // Not yet yet, requires AccessDesc Privk, may implement anyway later
	return -1;
}

https://github.com/3DSGuy/Project_CTR/blob/319c4c6a24747a6def3c012312ed13a2f76bb369/makerom/ncch.c#L939-L942


A strange feature or bug in shader.

Godot version:3.1.1
**OS/device including version:Windows10 **
Issue description:I found that the SCREEN_TEXTURE in the shader is the entire node window but not viewport. It means that when I's using scroller of mouse to zoom out/in the node window, SCREEN_TEXTURE includes the entire game-maker's viewport but not game's viewport. It results in difficulty debugging some effects of shader. In the example of amberation shader, when zooming the node's window, the proportion of effect changes with the zooming amount(The effect even almost disappear, if I zoom too much in the node's window).If I want to check the real effect of shader, I should every time run the project.
**Steps to reproduce:
code of shader(It is a shader of amberation effect):
shader_type canvas_item;
void fragment()
{
	COLOR.r=textureLod(SCREEN_TEXTURE,SCREEN_UV*(1.0+5.0*SCREEN_PIXEL_SIZE),0.0).r;
	COLOR.g=textureLod(SCREEN_TEXTURE,SCREEN_UV,0.0).g;
	COLOR.b=textureLod(SCREEN_TEXTURE,SCREEN_UV,0.0).b;
}

**
Minimal reproduction project:

This is neither a bug nor a feature. You have misunderstood what SCREEN_UV represents. It is a variable that goes from 0-1 across the Viewport. So when reading from screen_texture, you get the actual screen shown on the Viewport. Not the Viewport as shown by the markers in the editor.

This is neither a bug nor a feature. You have misunderstood what SCREEN_UV represents. It is a variable that goes from 0-1 across the Viewport. So when reading from screen_texture, you get the actual screen shown on the Viewport. Not the Viewport as shown by the markers in the editor.

I think SCREEN_UV goes from 0-1 not accross the Viewport of the game but Viewport of the node editor. I will show you a picture. In this picture, obviously, the bottom left corner is black, which meas the UV_SCREEN at the bottom left corner is (0.0, 0.0). But the bottom left corner is not corner of Viewport of game but Viewport of node editor.

Yes.

Yes.

So, the prorotrtion of effect will change when zooming the viewport, because it just cuts a piece from the whole viweport of editor while those parameters won't change with zooming. Any method to avoid this case?

This is indeed somewhat surprising behavior, because it messes up the preview in the editor. I would have assumed that the editor is aware of the viewport area and the SCREEN_UV and FRAGCOORD built-in get normalized appropriately. But essentially it is only an issue of the editor.

@Obr00007576 Perhaps you could rename this issue to something like Editor viewport affects behavior of SCREEN_UV / FRAGCOORD to make it easier for others to find? I almost opened a new issue, and only found it by chance (generic title).

Yes, a title like this would help. I found the issue thanks to content text search.
And for people who like this behavior for quick previewing, we could make it an option to select current viewport, or a specific one, or the editor viewport to apply shader preview.
In my case I was working with a subtle gradient so it was more disturbing than helpful. My results were asymmetrical when switching x to y and sometimes the gradient was almost invisible.

Yes, a title like this would help. I found the issue thanks to content text search.
And for people who like this behavior for quick previewing, we could make it an option to select current viewport, or a specific one, or the editor viewport to apply shader preview.
In my case I was working with a subtle gradient so it was more disturbing than helpful. My results were asymmetrical when switching x to y and sometimes the gradient was almost invisible.

So, it is not fixed so far? Or I should create a new issue with another titile. I've been not using godot for about a year. I nearly forgot about this issue. This odd behavior of the editor will be fixed?

@Obr00007576 SInce you're not using Godot these days I reopened a new bug for Godot 4 myself, reusing your shader: https://github.com/godotengine/godot/issues/92311
@bluenote10 I couldn't make FRAGCOORD work (it was always (1, 1, 0, 0) causing color to be yellow) so if you want to test that you can add your own shader example on the issue.


[WFRP4e System] Fixed token size with small creatures

When you import the token onto the board of a "small" size creature (or drag the "small" trait onto a creature and put it on the board) the token size is fixed at 0.8 and there is no way to change it . For players who do not use air tokens or tokens, it is a big inconvenience.
Thank you so much,
a cordial greetingFrom<EMAIL_ADDRESS>10.303wfrp4e: 6.6.1wfrp4e-core: 3.1.6Active Modules: babele, barbrawl, chat-images, dice-calculator, dice-so-nice, fateroll, foundryvtt-es, fxmaster, healthEstimate, hex-size-support, hourglass, lib-wrapper, michaelghelfi, token-action-hud, tokenmagic, wfrp4e-castellano

Disable automatic token sizing in actor configuration


Birds eye plot for Visualizations

Requires https://github.com/VEuPathDB/web-components/pull/193
Fixes #234

[x] histogram
[x] barplot
[x] boxplot
[x] mosaics
[x] scatterplot
[x] fix OutputEntityTitle counts

Should be all good - enjoy!


[doc] Minor typos on Modrinth page

Diff:
diff --git a/tmp/quad-modrinth.md b/tmp/quad-fixed.md
index 6bb4897..0594f11 100644
--- a/tmp/quad-modrinth.md
+++ b/tmp/quad-fixed.md
@@ -19,7 +19,7 @@

 located in `data/quad/tags/items` (.json files)

-- `immune_all` be added to all `innume_*` tags
+- `immune_all` be added to all `immune_*` tags
 - `immune_cactus` items won't get destroyed by cacti
 - `immune_explosion` items won't get destroyed by explosions
 - `immune_fire` items won't get destroyed by fire/lava
@@ -79,7 +79,6 @@ tags located in `data/c/tags/items` (.json files)
 - ***Brush*** - replaced item `minecraft:copper_ingot` with tag `copper_ingots`
 - ***Lightning Rod*** - replaced item `minecraft:copper_ingot` with tag `copper_ingots`
 - ***Spyglass*** - replaced item `minecraft:copper_ingot` with tag `copper_ingots`
-- > replaced item `minecraft:amethyst_shard` with tag `amethyst_shards`
 - ***Calibrated Sculk Sensor*** - replaced item `minecraft:amethyst_shard` with tag `amethyst_shards`
 - ***Tinted Glass*** - replaced item `minecraft:amethyst_shard` with tag `amethyst_shards`
 ##

this thing
also missed one after hopper with iron_ingot

what are you changing though?

removing broken list entry?

why removing it?

because it probably shouldn't be here? maybe you just forgot to add the item name here and it made a broken entry in the list. what is it supposed to be?

thats why its got the pop out with the - > in the code, to show its part of the 1 above, unless that isn't clear

ah, fair enough, sorry. maybe doing them on one line would be more intuitive?


Switch logging to promlog

Update logging library to prometheus/common/promlog
Closes: https://github.com/prometheus-community/pgbouncer_exporter/issues/28
Signed-off-by: Ben Kochie<EMAIL_ADDRESS>

The logging here still leaves a lot to be desired. I'm not sure where/why a lot of these log lines exist, and the levels are a bit all over the place. But this is an attempt at a 1:1 conversion.

:+1:


Update version number

What? and Why?

What does this pull request change/fix? Why was it necessary?

Checklist

[ ] CHANGELOG.md updated? (if required)

Codecov Report

Merging #34 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   28.18%   28.18%
=======================================
  Files           4        4
  Lines         518      518
=======================================
  Hits          146      146
  Misses        372      372

Impacted Files
Coverage Δ

rabbit_monitor.py
35.61% <100%> (ø)
: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 8afe03c...140f731. Read the comment docs.


Hide null responses from Metacritic

Don't create a Metacritic score response in Discord message if the Metacritic value is null, which happens to be for a lot of games even though there is Metacritic data available.... ITAD just isn't supplying it.
I can fix this, just making a note here.

Scores aren't even accurate if they even do come in from ITAD. Going to look at changing to Steam reviews or just getting rid of it entirely.


feat: alias sdk error types

Creates an alias for all sdk error functionality in errors/errors.go.
With this, now all functionality we used to have is mirrored in our package.  Now, a chain could import just our error module, instead of importing two (one for functionality, one fore the types). The only difference is that we are registering the errors in the "ignite" codespace, so there are still problems directly checking errors against each other.  This can't be resolved by us, but is a rare case.  Most of the time chains will just use these as general errors.

Nice feature @aljo242 !
Can we add a small package documentation comment in errors/errors.go to explain that ?
Something like
// Package errors mirrors both `types/errors.go` and `cosmossdk.io/errors` to give a handy access to cosmos-sdk error definitions and functions with a single package.
package errors

But in better english :P


Tinker Tank fluids don't all show in system

Issue description:
The Refined Storage system doesn't recognise all fluids in the Tinkers' Construct Tinker Tank.
What happens:
It only recognises the bottom fluid, and ignores all others.
What you expected to happen:
It should recognise and show all fluids in the Fluid Grid.
Steps to reproduce:

Build a Tinker Tank.
Attach an External Storage to a Smeltery Drain on the Tinker Tank.
Look in a fluid grid.

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>15
Refined Storage: 1.5.31

Does this issue occur on a server? Have not tested.

I'm gonna guess this is because of tinkers, the drain will only expose one fluid inventory: the bottom fluid. Things like Waila will also tell you that only the bottom fluid is exposed. Either RS can do something to support tinkers, or you're in bad luck.

Duplicate: #1034


Trouble including hash symbols in text

I'm experiencing some difficulty including literal #s in game text. As per the manual, I've used #, but I'm seeing the following:

If I include # in the game title, the literal text &NUM; is displayed.
If I include # elsewhere in displayed text, # shows up as expected while working with the game in the Gruescript editor, but as soon as I export the game to HTML, any text following a # does not display, as though # is being interpreted as a comment symbol.

I'm using the Gruescript editor on your itch.io page.
Thanks for building Gruescript, I'm having a lot of fun with it!

Thanks for this (and for your patience - I've had a lot going on.)
I believe this is all fixed as of the latest commit. Glad you're having fun!


chore(main): release 0.34.5

:robot: I have created a release beep boop
0.34.5 (2023-06-22)
Bug Fixes

add comment (06f435f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/samuele-cozzi/obsidian-marp-slides/releases/tag/0.34.5 :sunflower:


Packet 0/72 (ii) was larger than expected, 368 extra bytes whilst reading packet 72

What is the output link of /viaversion dump?
http://hastebin.com/cikapileza.json
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
We are running bungeecord version git:BungeeCord-Bootstrap:1.11-SNAPSHOT:9ecdde2:1200
The plugins running are the necessary (custom coded) proxy plugins required for our network and buycraft's bungee version
How does this error happen? login? Using an item?
Whenever someone tries to connect using 1.11
Is there an error in the console? Use pastebin.com. Is there a kick message?
No stacktraces in console, login screen: http://prntscr.com/d8w8mx
Ingame world is visible for a split second until player is disconnected

I can give more detail about the join listener of our server side plugin if necessary, I need to leave not to will begin back in about 2 hours

Update BungeeCord.


Allow disabling of cache cleanup by the end user

This behavior is not wanted by all users, and some users actually find it very helpful. This PR adds a property (org.gradle.disable.cache.cleanup) that can be set in the home folder gradle.properties file, and if this property is set to true, the cache deletion will be skipped.
Context

The caching behavior is useful in many cases, and there are people that don't mind the used space. Having builds always work even in offline scenarios is more important then disk space.

https://github.com/gradle/gradle/issues/6371
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[x] Verify design and implementation
[ ] Verify test coverage and CI build status
[x] Verify documentation
[x] Recognize contributor in release notes

I would be happy to update the docs too.
I think this page would need the property
https://docs.gradle.org/current/userguide/build_environment.html
And this page needs to be updated anyway, as the docs saying it only gets downloaded once is not true anymore.
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.wrapper.Wrapper.html

I fixed the review issues.

Thats a big change to how the caching is implemented, and a complete change in the design. I'm ok doing that, but I would need some help with the gradle internals to figure that one out. How would I change that class to run at the end of builds, and then at that point how would I load properties? Is there some kind of service used?

@oehme  Thats a big change to how the caching is implemented, and a complete change in the design. I'm ok doing that, but I would need some help with the gradle internals to figure that one out. How would I change that class to run at the end of builds, and then at that point how would I load properties? Is there some kind of service used?

That was kind of my thought. This property makes no sense from a build command perspective, because of you forget it, or don't have it in a specific project but have it in others, it's still useless. So it makes more design sense to me to be only a home property. Maybe it just needs to go in a separate file, not gradle.properties to make that behavior even clearer.

It does make sense as a build option the other way round - Disable by default in your user home and then enable for one specific build on the command line for a manual cleanup.
I'd rather avoid another option mechanism.

It was not done that way because no one expressed a need to turn it off on the initial thread and everyone wanted Gradle to do this by default.
I'm on board with adding an option, just not the way it's done here, as it's inconsistent with all other build options. Let's get cache cleanup to the end of the build session, also for the other usability reasons mentioned above.
Another way would be merging this without the documentation to unblock you and refactor it to the proper solution later and only then announce the option. I'll leave that up to @marcphilipp

That works good for me as well. If the undocumented merge gets chosen for now, I'll remove the documentation changes.
I don't mind if a refactor gets added afterwards, as I am happy to change my setup to accommodate any changes. I would have no problem with a temporary fix changing for a better solution in the future.

@marcphilipp I removed the doc changes so this should be good to go in.

I fixed the review issue.

@oehme PTAL

Another use case for this option is Internet connections with a quota.  Downloading a dependency more than once costs money and/or time, depending on the ISP's quota mechanism.  Making very long lived caches important for people in this situation.

Thanks, @ThadHouse!

Cool! We'll be setting this in our projects Java home and it solves a lot of problems.

org.gradle.cache.cleanup
org.gradle.disable.cache.cleanup
which is correct?


Check behavior in case neuron is addressed by account

If we receive a ManageNeuron message (e.g. for changing dissolve delay or so) that identifies the neuron by subaccount, see here: https://github.com/Zondax/ledger-icp/blob/5edf84e624081db9523ad92d2174a9c0b5158d20/app/src/protobuf/governance.proto#L23
Do you know what happens in that case? Do we decline that? (It is fine if we do.)

Test Vectors:

Having the neuron_id_or_subaccount.neuron_id set (field 12). Should Pass.

d9d9f7a167636f6e74656e74a663617267581f620b10e6f6a9a1b7fdad8caa011210220e0a0c0a0a000000000000000301016b63616e69737465725f69644a000000000000000101016e696e67726573735f6578706972791b16ce1ae58e79f5406b6d6574686f645f6e616d65706d616e6167655f6e6575726f6e5f70626c726571756573745f747970656463616c6c6673656e646572581d6115495a57db2550af24f555bbfbfaa08dac8f278ab90e72d5262cc702

Having the ID set (field 1). Should Pass.

d9d9f7a167636f6e74656e74a663617267581f0a0b10e6f6a9a1b7fdad8caa011210220e0a0c0a0a000000000000000301016b63616e69737465725f69644a000000000000000101016e696e67726573735f6578706972791b16ce1bd354b4e3806b6d6574686f645f6e616d65706d616e6167655f6e6575726f6e5f70626c726571756573745f747970656463616c6c6673656e646572581d6115495a57db2550af24f555bbfbfaa08dac8f278ab90e72d5262cc702

Having the subaccount set (field 11). Should fail.

d9d9f7a167636f6e74656e74a663617267575a030102031210220e0a0c0a0a000000000000000301016b63616e69737465725f69644a000000000000000101016e696e67726573735f6578706972791b16ce1c36bd0765806b6d6574686f645f6e616d65706d616e6167655f6e6575726f6e5f70626c726571756573745f747970656463616c6c6673656e646572581d6115495a57db2550af24f555bbfbfaa08dac8f278ab90e72d5262cc702

Having both field 1 and field 11 set. Should fail.

d9d9f7a167636f6e74656e74a66361726758240a0b10e6f6a9a1b7fdad8caa015a030102031210220e0a0c0a0a000000000000000301016b63616e69737465725f69644a000000000000000101016e696e67726573735f6578706972791b16ce1d43bb9618006b6d6574686f645f6e616d65706d616e6167655f6e6575726f6e5f70626c726571756573745f747970656463616c6c6673656e646572581d6115495a57db2550af24f555bbfbfaa08dac8f278ab90e72d5262cc702

Having both field 1 and field 12 set. Should fail.

d9d9f7a167636f6e74656e74a663617267582c0a0b10e6f6a9a1b7fdad8caa01620b10e6f6a9a1b7fdad8caa011210220e0a0c0a0a000000000000000301016b63616e69737465725f69644a000000000000000101016e696e67726573735f6578706972791b16ce1e19783ba4406b6d6574686f645f6e616d65706d616e6167655f6e6575726f6e5f70626c726571756573745f747970656463616c6c6673656e646572581d6115495a57db2550af24f555bbfbfaa08dac8f278ab90e72d5262cc702

I had a chat with @leongb offline and we realized that the reason these test vectors are failing is because of this check. The Ledger app assumes that a principal needs to be exactly 29 bytes, but the correct check is that the principal is <= 29 bytes. I'll create new issue to address this.
The test vectors as far as I can tell are valid.


Fix syslog stack usage is too large

Summary
Using %pV in syslog will lead to nested calls, which will increase the stack consumption
If LIBC_NUMBERED_ARGS is enabled, calling lib_sprintf in syslog will use a few hundred bytes of local variables, but syslog doesn't need it
Impact
Testing

Please fix
Error: stdio/lib_libvsprintf.c:1153:33: error: implicit declaration of function 'sprintf_internal' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                                sprintf_internal(stream,


navigation: dropdown

show dropdown arrow near "EXTRA" menu
same for "CREATE"?
dropdown on hover?
test it on mobile

I'm closing this since it's no longer relevant.


tests and update github action

Work In progress to get Github Actions to verify application startup and basic set of test functionality is working before accepting a push or pull request as valid.
Will come back later and do an automatic publish/push of the docker image and other master branch resources after the initial setup of Github Actions is in place.
To view how this will work in the future (still changing slightly, but wanted to open visibility and conversation around it) -> https://github.com/tmack8001/picobrew_pico/pull/1

@chiefwigms once this is merged Github Actions should be turned on for this repository. I added two simple test suites and we can easily add to them as we go forward to get more coverage and more confidence that small or large changes aren't going to introduce regressions.
I'd love to automate the script of a brew session on each and every device... especially since no one contributor has every device (ex. I'm missing the Zymatic, you are missing a Z PicoStill and PicoFerm). This is putting in place the building blocks and ability to do just that.
Also included here is a default workflow to running flake8. Only things I've opted to fail the build on are syntax errors and undefined names. All other flake8 errors are being returned as --exit-zero so anyone can view the results of the PR/push checks and view the results of the linter.


Sample Readme Wrong for DPS Values

This should be registration ID.

#define RegistrationID  {RegistrationID, which is equal to deviceID}


feat: Self managed certificates

We need to manage transport certificates
We can manage API certificate
Story when new cluster deployement

Generate transport PKI
Generate certificate / key for each node
Generate API PKI if self managed
Generate certificate / key for API (share accross all nodes)

Story when new node added

Generate certificate / key for new node (becarefull to not rolling upgrade other nodes)

Story when remove node

Delete certificate / key of deleted node (becarefull to not rolling upgrade other nodes)

Story when certificate need to be renewed
When one of them certificate need to be renewed, we renewed all certificate. It's removed some complexity and avoid to renew many time certificates.

Generate new transport PKI
Append new CA certificate with current CA certificate
Rolling upgrade all nodes to have current CA and new CA
When all nodes are 2 CA, generate all other certificates (node, API PKI and API certs / key)
Rolling upgrade all nodes
When finished, use only the new CA (clean old CA) -> becarefull to not rolling upgrade again

It's implemented


[Mediaklikk] Fix extractor (fixes #8053)

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Mediaklikk modified its site structure and the extractor broke. bashonly fixed the extractor. I only tested it and updated the included tests.
Old tests:

Dead URL, opens a 404 page. Fixed with a newer video
Dead URL, opens a 404 page. Fixed with a newer video
Live URL. Fixed with extra info
Dead URL, opens the video list page. Fixed with a newer video
Dead URL, opens an empty page.  Fixed with a newer video

Fixes #8053
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[x] I am not the original author of this code but it is in public domain or released under Unlicense (I only fixed the tests, the original code fix was published by bashonly under the issue in a comment)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at a953c5a
Summary
🛠📺🆔

Improved extraction for MediaKlikk videos. The extractor now uses a better way to find the playlist url, updates the tests with fresh data, and adds a new field for the video identifier.

The MediaKlikkIE extractor
Was not very good at its factor
So it got a new way
To find the playlist url
And also a nice display_id actor

Walkthrough

Add display_id field to info_dict of test cases and derive it from url path (link, link)
Update test cases with new urls, ids, upload_dates and thumbnails that match current website layout and content (link)
Extract playlist url from player json using traverse_obj and url_or_none instead of regex and raise error if invalid (link, link)

Old tests:

Dead URL, opens a 404 page. Fixed with a newer video
Dead URL, opens a 404 page. Fixed with a newer video
Live URL. Fixed with extra info
Dead URL, opens the video list page. Fixed with a newer video
Dead URL, opens an empty page.  Fixed with a newer video

Good job finding some new tests.
However, the old tests have some URL formats that we still want to test for matching.
Instead of replacing the dead tests, we should add skip keys to the dead tests, and add the new tests below them. The value for the skip key should be the reason why we are skipping, e.g.
    }, {
         'url': 'https://...',
         'info_dict': {
             'id': '...',
         },
+        'skip': 'Webpage redirects to videos list',
    }, {

Thanks for the info regarding the old tests. I readded them.


Convert CurrentChat/ConversationView/MessagesView to GetX Controllers

This will allow us to better modularize our code and make it more stateful/reactive

Completed in full rewrite


Speed up vault tests

The tests in vault_test.py take a considerable amount of time to run. Perhaps the parameters can be tuned to make the tests run faster without losing confidence that the code works.

Totally agreed @mickvangelderen. Would you be able to make a PR for this? :smile:
I think here:
@pytest.fixture()
def max_length() -> int:
    return 256

@pytest.fixture()
def fake_transition() -> FbxTransition:
    return FbxTransition(
        obs=CustomObservation(
            x=jnp.ones(shape=(1, 2, 3), dtype=jnp.float32),
            y=jnp.ones(shape=(4, 5, 6), dtype=jnp.float32),
        ),
        act=jnp.ones(shape=(7, 8), dtype=jnp.float32),
    )

We can drop the max length to 8 and make the shapes much smaller maybe all of them can be (1,1,2)? I don't think it will save a huge amount of time, but maybe a minute?


Add ballerina lock implementation

Fix https://github.com/ballerinalang/ballerina/issues/4170
design documentation is also in the issue
sample code to demonstrate syntax would be as follows
int count = 0;
function lockTest() {
    lock {
        count = 50;
    }
}

closing this and reopening new PR as this shows already merged commits
https://github.com/ballerina-lang/ballerina/pull/4537


Home Page Banner Updates for Launch Week

We want to add back the small banner in the upper left section of the home page, which will be updated daily on 6/12-6/14 with announcements about that day's launch and link to the highest priority post. Approved copy is below, by date. We would also like the banner background color to be changed each day so it is more noticeable. The 'Learn more' text of each day will link to the relevant blog post, the author of the post will notify @shughes26 at the time of publishing to provide the link and PR for the commit.
Copy:
6/12: New and improved Terraform conversion tool available! Convert HCL and TF modules to Pulumi.
6/13: Introducing Review Stacks: Temporary, on-demand environments for reviewing changes in pull requests.
6/14: New: Search for resources across any cloud by resource property from the Pulumi Cloud console.
Colors:
6/12: #f2ebf3 (background) // #80398d (text)
6/13: #fdf9eb (background) // #eec14d (text)
6/14: #edeffa (background) // #505bd1 (text)
@gthuang please proof the copy / dates one last time
FYI @susanev

Closing as done, feel free to reopen if there's anything more to do here.


Rack::Builder#to_app is not designed to be called for every request.

https://github.com/omniauth/omniauth/blob/9cd7aad3a0bd0f27a6de81973a17722e09d4a7d2/lib/omniauth/builder.rb#L44
It can have less than ideal performance implications.

Thanks for the report, this is an area of the library I haven't looked much into. Would memoizing the to_app call be sufficient?

I think you'd want to do it at build time because memoization is not thread safe.

It's also not necessary to redefine #call since it's the same as the superclass.
https://github.com/rack/rack/blob/ab9cd7416c1b5253cd280d75704bafd87510c120/lib/rack/builder.rb#L261-L263
If OmniAuth::Builder is intended to be used as shown in the README, maybe overridding ::new would be a low-impact way of resolving this?
module OmniAuth
  class Builder < ::Rack::Builder
    def self.new(default_app = nil, &block)
      builder = super
      block ? builder.to_app : builder
    end
  end
end

module OmniAuth
  module Builder
    def self.new(default_app = nil, &block)
      ::Rack::Builder.new(default_app, &block).to_app
    end
  end
end

maybe consider this???

Except that OmniAuth::Builder adds a few methods of its own, of which, the #provider method is probably the main reason for using it.
https://github.com/omniauth/omniauth/blob/7d90ba21c26299df8001684cbfbb6c54ce8ea440/lib/omniauth/builder.rb#L29
What about this:
require 'forwardable'

module OmniAuth
  class Builder
    extend Forwardable

    def_delegators :@builder, :freeze_app, :map, :run, :to_app, :use, :warmup

    def initialize default_app = nil, &block
      @builder = Rack::Builder.new(default_app)
      instance_eval(&block) if block_given?
      @app = to_app if default_app
    end

    def call env
      (@app || to_app).call(env)
    end

    # The rest same as current OmniAuth::Builder class,
    # not duplicated here....
  end
end

It ought to cover people who are currently using it in both ways, as middleware as suggested in the docs or as Rack::Builder is expected to be used.

I don't think side effects in #initialize are a good idea.
I like your original proposal: https://github.com/omniauth/omniauth/issues/1083#issuecomment-1256684769
I'd even suggest just doing it like this:
module OmniAuth
  module Builder
    def self.build(default_app = nil, &block)
      new(default_app, &block).to_app
    end
  end
end

Then use OmniAuth::Builder.build(...).

I'm not opposed to a major bump if need be, so the change can be as breaking as needed

If you had a preference on how you wanted this resolved (or the priorities to take into consideration, e.g., what level of backward-compatibility, etc), I'd be willing to take a crack at it and submit a PR.

I think the biggest downstream consumer is devise, so we'd wanna look if/how devise uses the builder and try and at least keep backwards compatibility for that

If you want an easy way to test external dependencies, you might like https://github.com/ioquatix/bake-test-external

I searched the devise code.  They don't use Builder.  The only reference to "builder" is a form builder.  I also ran their test suite against the code in the PR just in case, and everything passes.

I opened another PR, with the Builder-is-a-module idea.  I don't really have a preference between them, but the module version means there won't be an extra do-nothing piece of middleware in the stack since it just returns the built app.

Thanks @speckins I will take a look as soon as I have some time, I've been very busy

I tripped on this earlier today. How can I help get #1094 merged?

I've just not had the time to manage a large refactor at the moment, I'd love to be able to take care of a few different long standing issues w/ omniauth in the next major release, I just haven't had the time to work on OmniAuth outside of critical maintenance. Namely I'd like to resolve this issue, completely remove the hashie dependency, not dup the entire strategy w/ every request, and shortcircuit out of omniauth early when the request is not on a path that omniauth cares about.

I've just not had the time to manage a large refactor at the moment, I'd love to be able to take care of a few different long standing issues w/ omniauth in the next major release, I just haven't had the time to work on OmniAuth outside of critical maintenance. Namely I'd like to resolve this issue, completely remove the hashie dependency, not dup the entire strategy w/ every request, and shortcircuit out of omniauth early when the request is not on a path that omniauth cares about.

Makes sense! What do you think of doing those changes incrementally? I can help.


Support ie

IMO - instead of supporting IE should rework the code base to be a web component.  Use shadowDOM and be a really nice re-usable HTML element with ondrag attributes etc... See: https://gs.statcounter.com/. - globally in Jan 2021 IE saw less than 1% of traffic.... With Edge being Chromium based  it's never been a better time in the history of the web to use the excellent tools available since the fall of IE6's rain of terror.    Firefox, Chromium and Safari all support class, const, let, () => { console.log("and even this") }...   (async () => { const r = await fetch("http://www.ie6death.com/", {mode: 'no-cors', credentials: 'omit'});  const b = await r.blob(); console.log(b); })();
that said I'm just having fun and all good work should be recognized just saying it might be cool to push to a world of no more IE and moving beyond ES5 to ES6. - just my fly by 2 cents


Addition of "Class-based" and "Next Item Target" Toggles

Class-based toggles
This pull request (PR) supports CSS-based selectors to generate ID's for targeted element.
The [data-target] attribute looks at the target and identifies if element has an id or not. If it does not have an id, it generates one and updates the [data-a11y-toggle] with the generated id.
Add data-a11y-toggle (with no value) and data-target with the value equal to the selector you are targeting in your toggle button.

  <button data-a11y-toggle data-target="div + div" type="button">
    Toggle "div + div"
  </button>

    I am not the target

    I am the target from the selector in data-target

Next Item Target toggles
This PR supports dynamically generated queries to "next siblings" in the DOM Structure.
The [data-target] equal to "next" looks at the next element in the DOM structure and identifies if element has an id or not. If it does not have an id, it then generates one and updates the [data-a11y-toggle] with the generated id.
Add data-a11y-toggle (with no value) and data-target="next"

  <button data-a11y-toggle data-target="next" type="button">
    Toggle next
  </button>

    I am next sibling in the DOM and am the target of the toggle

Demo & Documentation (GH Page)
CodePen Demo

What shall we do!?

Hello Kevin,
Thank you very much for taking the time to contribute to a11y-toggle. Unfortunately, I’m not entirely sure what kind of use case you’re trying to solve here… Would you mind explaining?

Yup. This is to allow for development to use CSS selectors to identify the target in your plugin. When using the new [data-target] it will select the target, check to see if it has an [id] defined –  if it does, it uses that applies it to your generated aria tags - if not, it creates an unique if then applies it. In addition, their a next functionality which is helpful when having a generated grid and multiple contextual toggles in an interface.
See these examples:

a11y-toggle — Class-based toggles - Uses CSS selector to generate ID and/or identify target.
a11y-toggle — Next Item Target toggles - "Next item" toggle (following sibling can be toggled)
"Real life" example - Demo of a current project I'm working on

Basically, allows you to use CSS selectors besides id to be used.... making this plugin a little more dynamic :)

Good morning Kevin.
Thank you for taking the time to explain your intention. I see how that would be an interesting feature for a11y-toggle, however I am not too keen into merging it as this seems like quite some overhead for most use cases. What we could do is updating the documentation with a link to this pull-request to help people who have a similar need maybe. What do you think?

Sounds like a cool idea to me as a fork.  It would be great if maybe Hugo could link to the fork in the readme maybe.

@HugoGiraudel that works and sounds cool to me.


Add factory and new-style config for Prometheus receiver

This is part of remaining migration to new configuration format.
Github issue: https://github.com/open-telemetry/opentelemetry-service/issues/33
Testing done: make

Codecov Report

Merging #42 into master will increase coverage by 0.02%.
The diff coverage is 72.09%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
+ Coverage   68.94%   68.96%   +0.02%
==========================================
  Files          82       83       +1
  Lines        5461     5504      +43
==========================================
+ Hits         3765     3796      +31
- Misses       1480     1488       +8
- Partials      216      220       +4

Impacted Files
Coverage Δ

receiver/prometheusreceiver/factory.go
72.09% <72.09%> (ø)

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 08eae6f...4e58256. Read the comment docs.

I assume the build failure is unrelated to this change?

No, build failure is unrelated. We have a bug to fix the build failure: https://github.com/open-telemetry/opentelemetry-service/issues/43


Predictions are too bad

Hi! Thank you for this repo! I tried the pre-trained model and results are too bad (not sure how could the model achieve such a high metrics on test set). Here are some samples:

Are there any requirements for input images? (e.g.: image size etc.)

@mzhadigerov, this probably has something to do with my custom post processing + visualization rather than with the pre-trained model. Padding needs to be applied on the images before processing, but I added this to the inference code so this shouldn't be the problem.
Try moving the call to the visualization function:
if debug:
            visualization = visualize_structure(image, objs)
            out_path = "./visualization.jpg"
            cv2.imwrite(out_path, visualization)
            logging.info(f"Visualization can be found at '{out_path}'.")

right after this line:
objs = predictions_to_objects(results, threshold, get_class_map(key="index"))
This should visualize all the objects (not only columns and rows which I filtered out for a personal project). To see of which type the objects can be, inspect the get_class_map function.
{
            'table': 0,
            'table column': 1,
            'table row': 2,
            'table column header': 3,
            'table projected row header': 4,
            'table spanning cell': 5,
            'no object': 6
        }

You could also try increasing the score threshold, e.g.,
def predict(self, image_path, debug=True, threshold=0.85):
The post-processing in this fork is very amateuristic. For more advanced post-processing you can inspect the official repository, which I will probably also do in one of the upcoming months. They will probably release more examples in the near future.


fix Linux builds on many systems

see commits messages for details
Ubuntu 16.04 build error
[   90s] g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++1y -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -I../../../include/x86_64-linux-gnu/qt5 -I../../../include/x86_64-linux-gnu/qt5/QtWidgets -I../../../include/x86_64-linux-gnu/qt5/QtGui -I../../../include/x86_64-linux-gnu/qt5/QtNetwork -I../../../include/x86_64-linux-gnu/qt5/QtConcurrent -I../../../include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I../../../lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o chunk.o chunk.cpp
[   92s] chunk.cpp: In member function 'void Chunk::loadLevelTag(const Tag*)':
[   92s] chunk.cpp:170:17: error: must #include <typeinfo> before using typeid
[   92s]      if (typeid(*biomesTag) == typeid(Tag_Int_Array)) {
[   92s]                  ^
[   92s] chunk.cpp:170:51: error: must #include <typeinfo> before using typeid
[   92s]      if (typeid(*biomesTag) == typeid(Tag_Int_Array)) {
[   92s]                                                    ^
[   92s] chunk.cpp:177:24: error: must #include <typeinfo> before using typeid
[   92s]      } else if (typeid(*biomesTag) == typeid(Tag_Byte_Array)) {
[   92s]                         ^
[   92s] chunk.cpp:177:59: error: must #include <typeinfo> before using typeid
[   92s]      } else if (typeid(*biomesTag) == typeid(Tag_Byte_Array)) {
[   92s]                                                            ^
[   93s] Makefile:4103: recipe for target 'chunk.o' failed
[   93s] make[1]: *** [chunk.o] Error 1

Debian 11 (and others) build error (filename my vary, depending on generated targets order)
[  193s] make[1]: *** No rule to make target 'identifier\biomeidentifier.cpp', needed by 'biomeidentifier.o'.  Stop.

this is because GitHub uses Ubuntu 18.04 and 20.04, is these cases build is fine on my side too:

looks like something has changed in qmake, and it became more fragile, or on the contrary it became more strict and required correct syntax instead of guessing and fixing issues, but who knows
in any case, Windows separators are unique , any cross-platform things use Unix path separators, and Windows tools just convert them where it is required


fix: patch secure email change (double confirm) response format.

What kind of change does this PR introduce?
There are two issues the PR aims to resolve:

Currently, a Token Hash can be re-used twice in place of using the token hash send to the new email and a token has in the current mail. A solve attempt was originally made in #1240 but a test was added in this branch.

Currently, the single confirmation response is slightly misformed and has an additional null param

This stems from the return in the transaction. sendJSON doesn't return an error. Consequently, he error returned by the transaction will be nil. This leads to

sendJSON(w, http.StatusOK, token)  being run after sendJSON is callled which will write the token (nil in this case) to the existing singleConfirmationResponse. This in turn affects returned response for the  first confirmation as the client library is unable to unpack the returned JSON with extra null leading to an error.
What is the new behavior?
Returns response

Additional context
TODO

[x] Need to complete a test for the SecureEmailChange TokenHash to prevent a regression

nice one, thanks for catching this!