Wrong route name for registration

There is a misspelling of the route name: it says rivnex instead of rinvex
`InvalidArgumentException in UrlGenerator.php line 314: Route [rivnex.fort.auth.login] not defined.
in UrlGenerator.php line 314
at UrlGenerator->route('rivnex.fort.auth.login', array()) in Redirector.php line 157
at Redirector->route('rivnex.fort.auth.login') in helpers.php line 38
at intend(array('route' => 'rivnex.fort.auth.login', 'with' => array('rinvex.fort.alert.success' => 'Registration completed successfully!'))) in AuthenticationController.php line 142`

Generally i have gone through the source and found the problem on line 141 of file AuthenticationController.php
// Registration completed successfully     case SessionGuard::AUTH_REGISTERED:        default:              return intend([                     'route' => 'rivnex.fort.auth.login',                     'with'  => ['rinvex.fort.alert.success' => Lang::get($result)],              ]);        }

Thank you @emahuni for that catch 😅 To be fixed


SearchVideo details

Describe your question
In the searchVideo method, should we show the video whose relevance is 0 (cannot match any keywords)?

no


Bad results on values larger than 2^31

from ncls import NCLS
import numpy as np

ncls = NCLS(np.array([1000000000,<PHONE_NUMBER>], dtype=np.int64), np.array([1100000000,<PHONE_NUMBER>], dtype=np.int64), np.array([42, 43], dtype=np.int64))

it = ncls.find_overlap(1010000001,<PHONE_NUMBER>)
for i in it:
    print(i)

ncls = NCLS(np.array([4000000000,<PHONE_NUMBER>], dtype=np.int64), np.array([4100000000,<PHONE_NUMBER>], dtype=np.int64), np.array([42, 43], dtype=np.int64))

it = ncls.find_overlap(4010000001,<PHONE_NUMBER>)
for i in it:
    print(i)

Output:
(1000000000,<PHONE_NUMBER>, 42)
(1010000000,<PHONE_NUMBER>, 43)
(4000000000,<PHONE_NUMBER>, 42)

Thanks for reporting. Will look at it :)

This also happens in find_all_overlaps_both, which leads me to believe the error is in this function.
>>> ncls.all_overlaps_both(np.array([4010000001], dtype=np.int64), np.array([4010000002], dtype=np.int64), np.array([0], dtype=np.int64))
(array([0]), array([42]))

I've always used Linux for testing, but now I only have access to a mac. Which system are you on?

It should be fixed in 0.0.54. I am grateful for the report!


add aux_files and imports flag support to _gomock_source

Just needs the mapping.

Handled in #29 and #30


server cannot detect client disconnection state

[ ] server cannot detect client disconnection state

Server can't release connection thread correctly when user press disconnect button.
the threads will killed after stop simulation.

[ ] crash: quickly press connect and disconnect.  socket ptr change to  0xffffffff

client can't detect too.
cause by winsock: the second send will detect disconnection.


Rental frontend shift from main frontend

Pull Request
Title
Separate Rental-frontend from AgroTech AI Frontend
Description
This PR separates the Rental-frontend from the existing AgroTech AI frontend, allowing for better organization and maintainability of the rental functionalities. The new structure facilitates independent development and deployment of rental-related features.
Related Issues

Closes #321

wait a min. let me solve the issues

add app.css in frontend..you accidentally removed it

add app.css in frontend..you accidentally removed it

yeah. I was onto it


redirection in firefox

Turns out to be a feature, not a bug. So I'd just like to thank someone for doing this:
I use https://duck.duck.go in the URL bar of Firefox for searching, so "!yt" searches youtube.
But tonight I missed the !, found your site, and came straight to GitHub to check for an update, and I found I'm a year behind. Oops.
I'm a Release Manager by day, and all releases should be so easy! Kudos.
So I'll say
Thanks Guys n Gals.
Oh, found it in another tab: https://www.youtube.com/watch?v=6apMFqg28fw

Carefully read new issue template and provide all requested information.


JSON Patch

Document how to use the JSON Patch support in MVC.
This should be more of a ref style doc (unlike ben's blog) - but we still want code samples

https://github.com/aspnet/Entropy/tree/dev/samples/Mvc.JsonPatchSample.Web

Darren Schwarz<EMAIL_ADDRESS>

I can give this a whirl, if this is still needed.

@tdykstra - any guidance of where it should reside would be appreciated.

I'd make it a sibling to https://docs.microsoft.com/en-us/aspnet/core/web-api/action-return-types

@daveabrock Let me know if you’re still interested in this.

Hey @Rick-Anderson - looking to get it going in the next week or so. Does that work for you?

@wadepickett 	can you work with @daveabrock 	on this. Post an outline. Doc should be in the format of  View components - Ref style first then a walk-through. This is not a beginning tutorial so no screen shots. You can assume the developer has completed Create a web API.

@daveabrock  just checking in.

Hey @Rick-Anderson - sorry for the delay. I don't know that I'll be able to contribute for a little while. Things are pretty crazy personally. You might want to have someone else on this for the time being. :(


infinite British deport the chagos islanders decision.

reichtangly
Bug: infinite British deport the chagos islanders decision.

Deport the Chagos Islanders #960


null checks

Current coverage is 89.19%

Merging #801 into master will decrease coverage by -0.07% as of 7affdb1

@@            master    #801   diff @@
======================================
  Files           78      78
  Stmts         8067    8076     +9
  Branches      1738    1738
  Methods          0       0
======================================
+ Hit           7201    7203     +2
  Partial        376     376
- Missed         490     497     +7

Review entire Coverage Diff as of 7affdb1

Powered by Codecov. Updated on successful CI builds.

Towards #449


Reset signatures seem outdated

Most reset signatures are of the form reset(self, reset_dic = None). This is to account for the forced reset mechanism of bundles, where a component can be reset to an arbitrary state. However, currently, this forced reset is taken care of by base_reset methods, and therefore the reset_dic = None kwarg is likely not needed anymore.

Fixed with PR #52


my side of the story

@floridop

Hi! Thanks for your submission. I'm guessing you want to progress with this exercise.
Unfortunately it seems that there were changes in the main that conflict with yours.
Could you please perform a merge as described in Tutorial 5 slides 82-96 and integrate those changes?
We do not want to lose any of them, so you should keep what others have written and add yours.
You're free to reorganize the content blocks so that it still makes a story, but please do not modify
the content of what others have written.
Please do as soon as possible and if you can't make it please let me know.
Add a comment when you are so that I can progress with the next student!

Hey, I have now solved the conflicts with the main branch.


add suport for aws_cloudtrail resources

Q
A

🐛 Bug fix?
no

🚀 New feature?
yes

⚠ Deprecations?
no

❌ BC Break
no

🔗 Related issues
#

❓ Documentation
yes

Description
add suport for aws_cloudtrail resources

Codecov Report

Merging #1593 (8b054ff) into main (a28bac9) will decrease coverage by 2.38%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1593      +/-   ##
==========================================
- Coverage   81.04%   78.66%   -2.39%
==========================================
  Files         226      220       -6
  Lines        7113     6959     -154
==========================================
- Hits         5765     5474     -291
- Misses       1154     1288     +134
- Partials      194      197       +3

Impacted Files
Coverage Δ

pkg/resource/resource_types.go
76.47% <ø> (ø)

pkg/resource/aws/aws_cloudtrail.go
100.00% <100.00%> (ø)

pkg/resource/aws/metadatas.go
100.00% <100.00%> (ø)

pkg/resource/azurerm/azurerm_container_registry.go
12.50% <0.00%> (-87.50%)
:arrow_down:

pkg/resource/google/google_compute_address.go
14.28% <0.00%> (-85.72%)
:arrow_down:

...g/resource/google/google_compute_global_address.go
14.28% <0.00%> (-85.72%)
:arrow_down:

...ce/google/google_compute_instance_group_manager.go
14.28% <0.00%> (-85.72%)
:arrow_down:

pkg/resource/google/google_compute_disk.go
16.66% <0.00%> (-83.34%)
:arrow_down:

pkg/resource/google/google_compute_image.go
16.66% <0.00%> (-83.34%)
:arrow_down:

pkg/resource/google/google_bigquery_table.go
16.66% <0.00%> (-83.34%)
:arrow_down:

... and 30 more


The content returns nil in the ViewComponent

I want to render a block content render_component Button::Component.new { "Welcome!" }
# button/component.html.erb

<div class="bg-primary text-white">
   <%= content %>
</div>

But the content is nil. The original ViewComponent can render a content properly.
Is it a bug, or there is a different way to render the content?
Environment
Ruby Version: ruby 3.0.2p107
Rails: 7.0.0.alpha2
View Component version: 2.40.0
View Component Contrib Version: 0.1.0

Following @thomasklemm guide, I debug this issue and found that render_component doesn't have a block attribute.
I solved this issue by using a render instead
https://github.com/github/view_component/blob/main/lib/view_component/preview.rb#L10
Example:
<%= render(Button::Component.new) do %>
    Delete
<% end %>

@palkan my View Component version: 2.40.0


Clarification of the handling of leap seconds

Title
Clarification of the handling of leap seconds
Moderator
Requirement Summary
In order to correctly compute timestamps of measured variables where the reference date in the units attribute and the point in time of the measurement are separated by one or more added (or removed) leap seconds, it is required to know if leap seconds are to be counted or not.
Technical Proposal Summary
Add a sentence like the following to §4.4 Time coordinate:

Leap seconds are ignored during the calculation of all dates and times. That is, they are treated as if all clocks stand still during the presence of an added leap second or as if the clocks jump by one second across a removed leap second (if that should ever occur).

Benefits
Anyone who is working on high-frequency (sub-minute intervals) measurement data will benefit from this clarification. Without this change, time series wich cross an added (or removed) leap second can not be stored unambiguously using CF Conventions.
Furthermore, there there is considerable demand of specifying time in seconds since 1970-01-01 for historical reasons or other reference date far from the measured point in time. This specification is also not exact if the handling of leap seconds is not defined.
Errors due to different handling of leap seconds between data producers and data consumers lead to bugs which are hard to track and annoying. These errors can likely be reduced if handling of leap seconds is specified unambiguously.
Drawbacks
If leap seconds are ignored, measurements which happen exactly on the leap second can not be represented. This however is currently already the case in practice. In order to fix this additional issue, proper handling of leap seconds, TAI clocks and UTC clocks would have to be included. That topic is already being discussed in #148 and thus should not be part of this issue. Once #148 is settled (I hope that will be soon!), the added statement will not be true in general, but will be dependent on the specified calendar or other attributes and thus might need to be reworded slightly. I however don't think that this issue will affect the possibility to implement #148 in any negative way.
Status Quo
Leap seconds are not mentioned anywhere in CF Conventions. Usual libraries like cftime or numpy ignore leap seconds, but there's no specification that this library must be used and that what these libraries do is how it is intended to be. Thus for all implementations which I am currently aware of, nothing will change in practice, but discussions about how to implement custom solutions will become much simpler.
Associated pull request
none yet
Detailed Proposal
(this is the same as above)
Add a sentence like the following to §4.4 Time coordinate:

Leap seconds are ignored during the calculation of all dates and times. That is, they are treated as if all clocks stand still during the presence of an added leap second or as if the clocks jump by one second across a removed leap second (if that should ever occur).

This issue is intentionally separate from #148. My hope is that this issue can be settled a lot quicker. I also think that these really are two different concerns as #148 would add additional, desirable functionality while this issue only removes ambiguity from the current specification. It is incomplete in the sense of the mentioned drawbacks in order to make the scope smaller and simpler to implement.

Dear @JonathanGregory,
thank you for this motivating reply! I am also fine with handling this as an enhancement. This will add some more pressure towards a good formulation, but that shouldn't be a bad thing 😄 I also have a use case for a new version of CF-Conventions which are able to handle leap seconds, but I want to get this one fixed first.

My Idea was to keep it general, such that the sentence covers all the cases. I.e. if a calendar does not know about leap seconds anyways, it does not matter if the "ignore leap seconds" rule is applied or not. We could

[ ] go one step further and include special wordings for all of the calendars, in anticipation of new calendars which handle things differently or
[ ] we could postpone calendar-specific wording to the point in time when it will become relevant.

If we do calendar-specific wording, we should still ensure that no ambiguity regarding leap seconds may occur for the others. That is,

we need something like "ignore leap seconds in counting time deltas" (i.e. the sentence from above) for default, standard, gregorian, proleptic_gregorianand most likely also julian (I don't know much about the Julian calendar, but Wikipedia says "For any given event during the years from 1901 to 2099 inclusive, its date according to the Julian calendar is 13 days behind its corresponding Gregorian date.", thus it would make a lot of sense if the same rules which apply to gregorian apply to julian as well.
For noleap,  365_day, all_leap, 366_day and 360_day we should state something like "there are no leap seconds", if there really are no leap seconds.
none might be the only calendar which does not need any wording about leap seconds.

Regarding the second part of your post on describing this as an issue of the computation of time-deltas. I agree with all what you have written. I would probably rephrase one sentence a little:

When this calculation is done, it is assumed in CF calendars that 00:00 on any calendar day is 60 seconds after 23:59 on the previous calendar day.

into

When this calculation is done, it is assumed in CF calendars ( or in this calendar? ) that every increment of one minute  occurs exactly after a difference of 60 counted seconds (e.g. 00:00 on any calendar day is 60 seconds after 23:59 on the previous calendar day).

This will also cover the case in which the leap second is not inserted at midnight of the calendar (i.e. when using time-zone aware reference times).
There's just one more subtlety which might or might not be worth noting (and I have great fear while writing it as I really hope that it does not trigger a long discussion):

The component-wise date time (year month day hour minute second) is synchronized with the underlying civil calendar (i.e. Gregorian, Julian etc...)

This might be clear to everyone, but the thing is that in principle there would be another solution to the constraints you mentioned which would be to continue counting the component-wise date time which then would get out of sync with the "real" calendar. (This is what std::tai_clock does in the recent C++ standard library, but we do not want in this issue).

I am currently thinking of creating a term like leap second ignorant counting, which could be added to §4.4.
If you like, I could draft a PR which could be used as a base to talk about the wording.
All the best,
Tobi

@chris-little said:

But UTC and the Gregorian calendar have leap seconds by definition.

Be careful here.  The real-world Gregorian calendar does not have leap seconds by definition.
In general world usage, "UTC" is a precise timekeeping system which includes leap seconds.  "Gregorian" is a system of labeling calendar dates only, and has nothing to do with length of day, or leap seconds in particular.
In CF we use the calendar attribute "gregorian" in an extended sense, to identify a particular timekeeping system which combines both the real-world Gregorian calendar, and a fixed length day which does not use leap seconds.
I support the general premise of this issue, all currently defined CF calendars have fixed length days and do not include leap seconds.  If this notion is generally accepted, then it will become easier to start adding some of the more precise timekeeping systems later.

I support this proposal and favor pushing forward on #148 rather than adding more about leap seconds here.

Dear Tobi @d70-t
Thanks for preparing the pull request.
I notice that you prefer the word "count", in "A time coordinate value is a number which represents a date-time as a count", "the counting unit" (meaning the unit of time in the units string), and "exactly 60 seconds to count" in each minute. I didn't use the word "count" because to me "count" specifically refers to integers (e.g. as in countable infinity versus uncountable infinity), so I find it misleading for floating-point numbers. I described a coordinate value as a "number" rather than a "count" because I understand "number" as possibly non-integral. However, quite possibly you find "number" misleading! I hope we can find some word that everyone likes for a number is not necessarily an integer. That's also why I wouldn't call it a "counting unit" - the coordinate value might be e.g. 3.142 days, but I don't think I'd say "We count 3.142 days".
My idea in drafting that text was that we can avoid the problem which @chris-little raises at this stage by being clear that the calendar is just concerned with the rules for calculating time coordinates from date-times and vice-versa. If we introduce UTC or other calendars with leap seconds we will have to introduce another distinction, but I hope we can agree this PR first. It sounds like you and others would also rather do that. In fact that was your original aim with this issue, I think.
Regarding your other questions

You should add yourself to the end of the list of additional authors.

The conformance document is in the same repository, and necessary changes should be included in the pull request, consistent with this change. Although this is not actually a change, we could add the requirement that the reference date-time in time units is not allowed to contain seconds equal to or greater than 60.

The next version will be 1.9. I expect it's already been changed by some other pull request.

Best wishes
Jonathan

Dear @JonathanGregory,
yes, I also wasn't entirely happy with the word "count". I assumed that something like a fractional count would not be uncommon, but that might well be due to a lack in my understanding of the english language. I am happy with the term number as well.
It think the first instance of as a count can be removed. I just added it to create a reference from the unit in the units attribute to the number. We could probably change the wording of the units to ... units of the time coordinate variable (containing the unit of the number and the reference date-time).... I just want to avoid the unit of time as referring to time in this place feels a little bit like a cycle in reasoning.
Then for the last part we could maybe try something like ...it is assumed that the coordinate value advances by exactly 60 seconds from the start of any minute... or something similar in more proper english 😬. I'd like to point out that the 60 seconds are not about the actual time passed but about the amount of seconds the number has changed.
I'll have a look at the other points.
All the best,
Tobi

Dear @JonathanGregory,
I've added me as an additional author and added the note on the 60th second to the conformance document.
Regarding the version, there are sill many occurrences of version 1.8 in the document as well as the conformance document. This is the reason why I didn't check the other items. I could update these, but it doesn't feel like all of these should be part of this PR.
Tobi

Dear Tobi @d70-t
OK, thanks. Those changes look fine to me.

I think the first instance of "as a count" can be removed.

Maybe we could just depend on the word "value", which has that meaning.

I just want to avoid the unit of time as referring to time in this place feels a little bit like a cycle in reasoning.

Yes, I sympathise.
I suggest rewriting the start in a different order:

A date-time is the set of numbers which together identify an instant of time, namely its year, month, day, hour, minute and second, where the second may have a fraction but the others are all integer. A time coordinate value represents a date-time. In order to calculate a time coordinate value from a date-time, or the reverse, one must know the units attribute of the time coordinate variable (containing the time unit of the coordinate values and the reference date-time) and the calendar. The choice of calendar ...

Is that better?

it is assumed that the coordinate value advances by exactly 60 seconds from the start of any minute ... I'd like to point out that the 60 seconds are not about the actual time passed but about the amount of seconds the number has changed.

Yes, I see what you mean. Maybe, "it is assumed that the coordinate value increases by exactly 60 seconds from the start of any minute." That sounds more definitely a statement about the numerical value, I think.
I'm sure the version number will be updated when the next version is made.
Jonathan

Dear @JonathanGregory,
I like your suggestions. I've included them into the PR and am also happy now with the current state of the PR.
All the best,
Tobi

Dear Tobi @d70-t
That looks fine to me. Since @davidhassell @taylor13 @Dave-Allured @sethmcg have also said they're in favour of it, we've got the required amount of support and no objections which haven't been addressed at present. If no-one raises any further concerns within three weeks from now, the proposal will be accepted.
Thanks and best wishes
Jonathan

To be consistent with the single occurrence in the existing version of the standard, and also with https://github.com/cf-convention/cf-conventions/pull/315, we should write "date/time" in the new text introduced by this issue, instead of "date-time", which I wrote. I assert that this isn't a material change to the proposal, so we don't need to "reset the clock". This proposal will be accepted on Friday 2nd April if there are no further concerns expressed by then.

Thanks @JonathanGregory. I agree that this is not a material change and I also don't have a particular preference for either variant. But as you say in #298, "date/time" is what has been in the conventions before. I've updated the PR accordingly.

Thanks for doing that, Tobi

I have merged https://github.com/cf-convention/cf-conventions/pull/316. Thanks for initiating this proposal, Tobi @d70-t

🎉


Access YT Player.mute() to make autoplay on IOS

Is there a way to access the Youtube player ref and then access the mute method?
Because this way it's autoplayable on IOS.
Look at an non-react-player example here:
http://jsfiddle.net/BFDKS/1228/
Thanks

It is a bit convoluted, but it is possible:
<ReactPlayer
  ref={rp => this.rp = rp}
  url='https://www.youtube.com/watch?v=Y_hc07rAQlc'
  playing
  onReady={() => this.rp.player.player.mute()}
/>

https://jsfiddle.net/99ee3atp/9/

awesome. Thanks!


Remove stray 'in' that was preventing build

There was a what looked like a stay 'in' that prevented me from building the solution

Hi, I can build the solution.

Actually I can build the solution without removing the 'in'. Can you clarify?


Release notes stopped appearing on the GoHugo.io-website

If it's done manually, then someone forgot to add the release notes to the website. If it's done automatically, something is broken.
https://gohugo.io/news/ - release notes for 0.90.0 and 0.90.1 are missing.

We stopped doing it. Too much work, now releases is GH only.

Well, wouldn't that be a nice test of the capabilities of getJSON then? Add a list of recent releases with https://docs.github.com/en/rest/reference/repos#releases linking to the release pages.


fix: condition for no encrypt config

:tada: This PR is included in version 1.4.0 :tada:
The release is available on:

GitHub release
v1.4.0

Your semantic-release bot :package::rocket:


Bump to v1.16.9

We'll bump our k8s version to v1.16.9 and release k3s v1.16.9+k3s1
Reference https://github.com/kubernetes/kubernetes/releases/tag/v1.16.9

There are build failures that @ibuildthecloud needs to review. We're on standby waiting for this to be completed before we can release.


Quality Check - All pages

To be checked for JS errors in the browser:

missing assets
404 files
missing JS files

Validated. Closing.
Ty @mominur-helios


my go version dont support Generics

Hi ,I like your project, but it used Generics type, My project's go version is below 1.17.
so .what can I do..

Hi  I think I can fork and change those strict array type to slice
thank you

Hi @lovelydeng,
Thank you for the question.
Actually, Gomoji doesn't use Generics but our dependent libary github.com/rivo/uniseg does. So you can create an issue there and ask to avoid Generics.
Thank you.


Add Depthwise Deconvolution support?

@crazy-cat Hi cat. You have make the convolution faster when the num_filter==num_group(depthwise convolution).
I have a question for that, the mx.sym.Deconvolution is the opposite operator of convolution, Can it benefit from the num_filter==num_group? This trick is sometimes used in the FCN semantic segmentation to upsample features from lower layers and keep the deconvolution weights less.

I think so，you can try it yourself. It's not supported yet.


docs: Document possible phase values

Document values for phase field in CR. In response to a question in slack.
This is a documentation only change.

For posterity, this PR was replaced by #10698


10951 issuing distributor access tokens

This PR has changes for Adding new get token endpoint in apim.
Changes on swagger document to add new endpoint
Changes on terraform scripts for policy
pipeline changes for passing parameter.

Please hold the merge as there are some changes need to be added after today discussion


Refactor & bug fixes

Fixed SSR functionality
Changed 'IS_SRR' tier type to 'SSR' BREAKING CHANGE (Reasoning: SRR should be SSR and the IS_ prefix is not used in other tier types.
Added SSR test
Added test for loadBenchmarks throwing
Removed undefined from return type of loadBenchmarks override
Updated changelog
Bumped version to 3.0.0 due to breaking change (I am guessing we are following semver here)
Saved 5% on gzip size by not including the complete package.json in the dist

Other non breaking changes are described in commit messages.

(We should also update the benchmarks data before publishing to NPM)

Thanks @puckey, I'll have a look at your MR in the next few days.

Thanks for the PR @puckey, merging into development to make some small modifications.

v3.0.0 has been published!


Re-enable skipped tests and remove dead tests

Resolves https://github.com/aspnet/EntityFramework/issues/5346

@natemcmaster So we really have zero skipped tests after this change?

Looks like there are skipped tests in:

InheritanceRelationshipsQueryTestBase
OptimisticConcurrencyTestBase
FieldMappingTestBase
AsyncQueryTestBase
QueryTestBase
ComplexNavigationsQueryTestBase
GearsOfWarQueryTestBase

Sorry, should have been more clear. I mean we are re-enabling some skipped tests, not all.

@natemcmaster That's great, but then it doesn't resolve the issue assigned to Lawrence which was to scan the code for all skipped tests and either re-enable them or check that there is a bug associated with the test and that the skipped test is mentioned from that bug.

I edit the description above so #5346 is still open when the PR merges. This re-enabled tests here are only for the tests concerning design-time tools

:shipit:


[SDP-626] Extend bug

I was able to reproduce the 626 bug where extension of certain questions wouldn't allow you to add selected RS sets to the right via drag and drop or the button. It took awhile to figure out but the fix is very simple (the selected rs was empty for non choice on extension but the state for extension was storing an undefined when extending into a choice type).
Make sure you include the related JIRA issue in the title e.g. '[SDP-007] Fixed navbar issue'
Make sure you have checked off the following before you issue your Pull Request:

[x] Passed all unit tests using rails test with 90%+ coverage
[x] Passed all cucumber tests using bundle exec cucumber
[x] Passed overcommit hooks, including running all code through Rubocop

Steps to reproduce: Create a question with response type != choice or open choice, Extend a question without a choice/open choice type, change type to choice/open choice, try to add response sets.


Multi-stack parser

Problem
Source:

Our current syntax can't express things defined as a sequence of other things, like this:
function ::= <title> '=' <params> '->' <body>

The problem here is that you don't know that you're in a function definition until you get to the -> symbol. Our parser can start a new parsing mode based only on a single starting lexeme: an opening quote, a keyword, a number, etc.
To work around that we use a horrible kludge:

Match the whole body of the mode with a single regex.
Start a new mode at the beginning of the matched string.
Return the whole thing back to the parser.
Parse it again, by the rules of the new mode.

Not only it's ugly, it also works only when we're lucky that the whole body can actually be parsed by a regex.

Solution design
We need to implement a "multi-stack" parser: instead of keeping track of a single stack of parsing modes the parser should be able to keep multiple stacks representing alternative parsing strategies to which it can go back if the current stack dead-ends for some reason. This effectively becomes a tree:
                                      stacks
                                      +----+
[root]---[ ]---[ ]---[ ]---[top]  <---|    |
          |           |               +----+
          |           +---[x]     <---|    |
          |                           +----+
          +---[x]                 <---|    |
          |                           +----+
          +---[x]                 <---|    |
                                      +----+

This is an inverted tree with the stacks array keeping references to alternative parsing strategies (stacks) with each mode having a reference to its parent.
The topmost (or the rightmost) branch is the only long one and it represents the current alternative being parsed. Every other branch is exactly one level deep — a lead node representing a point from which to restart parsing if the current branch fails.
Operations:
Discover: upon finding lexemes (one or more) opening new possible modes add them to the beginning of the stacks array in the order they're defined. The old top is updated with the current index in the source so we could parse farther if all new strategies fail. stacks[0] becomes the new top.
Cancel: upon finding a canceling condition remove top from stacks, set top to the next available stack. If stacks is empty, treat as we currently do illegals — drop parsing.
Commit: if the mode successfully reaches its end lexeme, it is removed from the top stack and stacks is cleaned up from any items pointing to that mode
Syntax
Current idea is to have something like this:
var PARAMS = {
  className: 'params',
  begin: /\(/, end: /\)/,
  contains: [...]
}

var FUNCTION = {
  className: 'function',
  is: [hljs.TITLE_MODE, PARAMS, /=>/]
}

Where is array is a syntactic sugar for something like this:
{
  className: 'title',
  starts: {
    cancel: /\S/,
    contains: [
      {
        className: 'params',
        begin: /\(/, end: /\)/,
        starts: {
          cacncel: /\S/,
          contains: [
            {
              begin: /=>/, relevance: 0
            }
          ]
        }
      }
    ]
  }
}

It's pretty obvious why we need some syntactic sugar for this :-)
cancel is a new attribute, similar to the current illegal with the exception that it only cancels the current parsing strategy, not the whole thing.
More syntactic sugar:

Treat literal strings as keyword lists: 'a b c' ⇒ {className: 'keyword', begin: /\b(a|b|c)\b/}
Treat literal regexes as lexemes: /=>/ ⇒ {begin: /=>/, relevance: 0}

Simplifications
Unless I'm very much mistaken, implementing all this will allow us to drop returnBegin, returnEnd and also beginKeywords and make the whole definition syntax less convoluted. Fingers crossed :-)

This is a work in progress…

I agree that using returnBegin and returnEnd is not most elegant, but usually the syntax parser is built a with specific linear approach in mind. I'm trying to envisage your new proposal applied to markdown, for example, which is reknown to present some hard-to-deal with edge cases (especially if the document is not well formated, or if uses "lazy" syntax instead of a cleaned up one).
Even PEG parsers have to resort to hacks to handle properly Markdown.
Will this new approach allow coders to mentally trace what actually goes on? Often, when writing my first syntax file, I'd realize that build failed (without error reports, just failed to build). So I would know that something wasn't right in the code, and I'd start to go through it mentally, tracing steps and looking for bugs.
Is this stack going to make "mental debugging" more complex? Are there risks of infinite loops and/or recursiveness? Presently, restorting to returnBegin and returnEnd is a precise strategy that one adopts when there is a clear picture in mind of what the limits are — and even though it isn't the most elegant approach, it's still quite linear.
Are there going to be some means to log the new parsing process, and trace what failed where and when? with some references to the stack states?
These considerations aside (it's difficoult to imagine the changes it will bring without having the code to play with), it seems that it would expand the parsing power of hjs — after all, the limits is proposes to address are significant ones, not trival.
Is it going to make parsing more resources-demanding? time consuming? or is it going to slim down execution times?

Some food for thought here:
var CLASS = {
  className: 'class',
  keywords: "class extends",
  is: [/class/, TITLE_MODE, /extends with/, TITLE_MODE, /{/]
}

This looks reasonable but what is the scope of those keywords? The "flat" nature of is makes me want to assume this would "just work", but do keywords always get inherited? Do they only get inserted for static regex matches?
And how do I do a variant?
var CLASS = {
  className: 'class',
  keywords: "class extends",
  variants: [
    {is: [/class/, TITLE_MODE, /extends with/, TITLE_MODE, /{/] },
    {is: [/class/, TITLE_MODE, /{/] }
  ]
}

And purely talking syntax I'd like to consider functions also:
var CLASS = {
  className: 'class',
  keywords: "class extends",
  match: is([/class/, TITLE_MODE, /extends with/, TITLE_MODE, /{/], {allowSpaceBetween: true})
}

I really wonder if you couldn't just hack this by making highlight take a MODE (not a language name) and then just calling itself recursively and just let the JS stack manage all the messy state. ie:
// inside main loop
while (...) {
 if (top.contains) {
   // pursue matches as usual
 } else if (top.is) {
     let restOfCode = ...
     let result = _highlight(restOfCode, {using: top.is})
     trimAfterLastMatch(result)
     if (result.illegal) {
       // failed match
     } else {
       emitter.addTree(result.emitter)
       lastIndex += result.matchSize
     }
   }
}

But actually you have to deal with how do you start an is match in the first place... it's probably going to be precipitated by an actual match of a begin expression, probably the first "block" of the chain.  You could have a quick auto-returnBegin though... so that when it hit a mode that had an is it returned the content and then entered that mode... so the next iteration would be running the is branch shown above.

Then the question becomes is writing (and maintaining) (and having grammar writers) reason about the is to insane super complex ruleset better than just expanding the parser to actually have some time of true/real sequencing mode when it just jumps from one mode to another in a linear fashion rather than trying to find one of many possibilities.

(Just a heads-up, I've seen your messages but haven't got to actually reading through them and understanding :-) )

Some food for thought here:
var CLASS = {
  className: 'class',
  keywords: "class extends",
  is: [/class/, TITLE_MODE, { begin: /extends|uses/ }, TITLE_MODE, /{/]

}
This looks reasonable but what is the scope of those keywords?

Re-reading my own description (at the end, in "syntactic sugar") I think there wouldn't be a need to specify keywords in the parent mode. Any literal string inside is will be considered a keyword, or a list of them with some reasonable separator (initially I thought space separated, but a | is probably more familiar). So:
var CLASS = {
  className: 'class',
  is: ['class', TITLE_MODE, 'extends|uses', TITLE_MODE, /{/]
}

And purely talking syntax I'd like to consider functions also:

I actually wanted to move away from anything executable in language definitions. Eventually I wanted to provide dedicated syntax for everything case where language definitions currently use JavaScript, so they would become inert data. It just makes everything simpler. There wasn't any refactoring plan for that, it was more like a general gravitational pull to keep in mind when making any changes to the grammar: less imperative, more declarative.

I really wonder if you couldn't just hack this by making highlight take a MODE (not a language name) and then just calling itself recursively and just let the JS stack manage all the messy state.

Interesting :-) It should be theoretically equivalent to my original proposal with keeping stacks explicitly. And I can't predict which one of the ways will turn out to be easier.

But actually you have to deal with how do you start an is match in the first place... it's probably going to be precipitated by an actual match of a begin expression, probably the first "block" of the chain. You could have a quick auto-returnBegin though...

I really wanted to get rid of returnBegin… This is why I imagined is as a syntactic sugar expanding to starts with the first mode in the chain. This is incompatible with the recursion though… I really don't know :-)

Then the question becomes is writing (and maintaining) (and having grammar writers) reason about the is to insane super complex ruleset better than just expanding the parser to actually have some time of true/real sequencing mode when it just jumps from one mode to another in a linear fashion rather than trying to find one of many possibilities.

Well, the whole problem is that you can't parse some languages linearly. Like, in C++ when a function definition can starts with arbitrary identifier, and it's not until you hit the parentheses of the argument list you even know what it was.
I don't think it's going to be hard to reason about for grammar authors. It's a simple pattern-matching idea: either this entire chain of modes matches or it doesn't. You don't need to know how it's implemented under the hood.


Make hosts in inventory/group_vars/all.yml dynamic

Hi and first of all : thanks for your work !
I'm trying to apply this on vm without vagrant, and I think this part of inventory/group_vars/all.yml file should by dynamic based on inventory.
In fact, IPs (which are dynamics) and hostname are wrong in my case.
https://github.com/TOSIT-IO/tdp-getting-started/blob/930956873a8129ea10d570658d068217a1d57bbc/inventory/group_vars/all.yml#L3-L11

Hello,
These variables are used to generate a Vagrantfile (which you won't need) and the Ansible inventory/hosts file. The generation happens at the ansible-playbook generate-node-deployment-config.yml step.
Replace the IPs with whatever your VMs IPs berfore running the command are and you should be good to go. You might also want to manually update the ansible_ssh_private_key_file key in the generated inventory to connect to your VMs.

I've already managed the inventory/hosts file but didn't planned to edit the groups_vars files (until now).
Indeed, I still have to edit these hosts values because they are used to generate the /etc/hosts files on servers (in the deploy-vms.yml playbook).
To do so, I wrote a preconfig playbook but my way of doing it didn't suit me. Even a small change in the groups_vars  could make my pre-playbook not working anymore ...
Anyway, I should have mentionned that this issue is more a question/feature request than a real issue (my bad).
As I have a workaround for my usecase, I let you decide if this issue is still relevant.

Personally for a sandbox environment, I think it's simpler and more precise to keep the IP declaration explicit in the inventory/group_vars/all.yml file.

Duly noted !
I keep dealing with this file on my own.
Thanks for your answer and guidelines :)
I close this issue.


Not working on other android device. Big issue

Hi Team,
I have implemented the pdf viewer in my app but its only working on android devices.  Its not working on other android devices

only working on android devices? not working on other android devices? can you provide devices list?

@vinod1988 Maybe it is because you created android application? Try to create another application for other devices)


Dampening update: set correct TriggerId to dampening object

When updating trigger dampening (also for a group trigger) with a wrong triggerId, the getCleanDampening() would generate a wrong dampening.
In addition, in the case of missing DampeningId or TriggerId, only the DampeningId is mentioned in the Bad Argument HTTP error message. This change also suggests a missing TriggerId.
fixes: https://issues.jboss.org/browse/HWKALERTS-215

Thanks for the fix @dkorn.
It looks good to me.
As soon as Travis CI is fine with it, I will merge it.


Boolean column values view. Textboxes-mode field customisation and COLOR

Please, consider following proposition that allows comfortable boolean-values differentiation among thousands of DB records, but ordered by other (say, non-boolean) prioritized columns. At the attached picture you can see custom text-inside-cell-value INDENTATION with whitespaces made by user text input and custom COLOR pick for 'textboxes' depicture mode.
Cell itself should stay clickable (as it already implemented before) to be able to change value in general DB Editor
#7787
#9327
#10645
#11190
All for user viewing comfort :)
Best regards for DBeaver dev-n-test team as so as users.
#HighUsability

We will implement the feature. Thank you for not forgetting it.

in addition:
Bold text would be more contrast for the eye

Also, please, implement text assertional limitations against intentional malicious delusion input such cases as:
KEY : VALUE

true != false
true != NULL
true != faIse
...
(NULL) != not null
(NULL) != false
(NULL) != true
...
false != true
false != NULL
in case insensitive text and any similar characters from other non-english language alpabets or Latin extended/Latin-1 Supplement characters i.e. 'tяие', 'truè' and so on...
I believe, your advanced testers could generate different such negative scenarios input

@tati-kru why do you keep postponing this feture?

@ghYura we do our best to close as much issues as possible, sometimes we need to move some issues to other milestones to make process more efficient.

@ghYura we do our best to close as much issues as possible, sometimes we need to move some issues to other milestones to make process more efficient.

Thanks for your feedback

Also, please, implement text assertional limitations against intentional malicious delusion input such cases as:
actual KEY : text VALUE depicted in cell for this mode

true != false
true != NULL
true != faIse
...
(NULL) != not null
(NULL) != false
(NULL) != true
...
false != true
false != NULL
...

in case insensitive text and any similar characters from other non-english language alpabets or Latin extended/Latin-1 Supplement characters i.e. 'tяие', 'truè' and spaces/underscores/special (group or combination of) characters among/between/before/after them, and so on...
I believe, your advanced testers could generate different such negative scenarios input. There is a bunch of negative delusion scenarios
Powerful regexp comparator probably required

@ghYura why do we need to overcomplicate it in a such weird way? If user decided to make his live harder by swapping true and false, it's his choice.
It will only make sense if you want to share your DBeaver configuration with others. And some may not like the textual representation of booleans. For example, I prefer the image-based one.

@ghYura why do we need to overcomplicate it in a such weird way? If user decided to make his live harder by swapping true and false, it's his choice.
It will only make sense if you want to share your DBeaver configuration with others. And some may not like the textual representation of booleans. For example, I prefer the image-based one.

1). in case if former co-worker leaves old config for company but no time to figure out whats wrong with 3rd party soft, that this is only option, while CI/CD (in this case DBeaver RDBMS)
2). constant imroving of anything (perfect code - unachievable, but worth to be aspired)
3). I agree that you prefer image-based one, other - strict boolean meaning, other - decorated. If you take a look at linked closed issues you will see that I came to idea of a very custom way for its depicture (by user taste). That's why we got this Feature request (satisfy as much user/customers taste as possible). :)
Anyway, this is additional "Wish for the best for many cases as possible" issue IMO,
but custom |        text| indentation in cell (in bold contrast for the eye to differ)
and its color picking (also contrast for thousands DB records)
are the core for this issue and higly desirable

And some may not like the textual representation of booleans. For example, I prefer the image-based one.
[https://user-images.githubusercontent.com/42974628/99234979-eeb54b80-27fd-11eb-8ea5-d3908f675b6f.jpg](image-based one)
(You cannot indent pictograms/icons and colorize the while image-based, can you?)

Okay, I get it now. We'll see what we can do. Unfortunately, it's impossible to handle every case (e.g. your team speaks in other language and words for true and false are different, we don't want to involve translation API for that, of course).
You can't colorize image-based one, that's true. As of now, this is true for text-based too. It is possible to allow colorization for image-based by allowing user to adjust their hue individually, but that's a different story :)

Okay, I get it now. We'll see what we can do. Unfortunately, it's impossible to handle every case (e.g. your team speaks in other language and words for true and false are different, we don't want to involve translation API for that, of course).
You can't colorize image-based checkboxes, it's true. As of now, it's true for text-based checkboxes too. It's possible to allow colorization for image-based checkboxes by allowing user to adjust their hue individually, but that's a different story :)

and INDENTATION!
Beleve me, I want to improve DBeaver and make it better for everyone, not less than any of you, team!
Best regards! :)

BTW, pictogram/icon could(?) be colored from the start and not squared, but rectangled (stretched) and bool-depicture from the start, what satisfies each to other indentation and color. NULL-values somehow placed between their positions.
But I want to replace 'pass' - for 'true', and 'fail' - for 'false'... other replace his/her own meaning, which only(?) text-mode does(?)
See, bunch of propositions, as you can realize.
Up to you, for the best and easy-to-implement

Implemented custom definition of text labels, changing alignment and colors:

Current implementation does not include following requests:

Image checkbox colorization support
Assertions against malicious input in text mode

Separate FRs should be created instead.

Avaiting for release roll out to test

win: verified

Verified on Linux

Additional sub-issue (not for now):
For very further improvement assertion against text/icon similar color with background color of the cell/row match against it become invisible or smth.
Writing this sub-comment to not forget in the future, keeping beared in my mind yet, sharing with all of you.

There's a way to use font color of your active theme. It always be a contrast one.

There's a way to use font color of your active theme. It will be the contrast color.

Up to you all, team! I have infected you with the main idea - rest for the best - up to you. Since I know we are on the same way about this main feature idea - I trust you, your expirience and your choice for the best of any further details :)

One more issue/feature/bug/odd_behavior of Github detected. But that is a different story.
QA-teams will always(?) have a job :)
Be mistaken - my credo

@ShadelessFox Can we associate custom adjustment for each boolean column boolean-view adjustments individually? Now we have general-for-all boolean representation. How about each column individual representation binding (in terms of code - each object - own sub-object adjustments), that overrides general?

No, we can't.
You can create a separate FR and we'll discuss it in the future.
But I think it would be an overkill for such a small feature.


How to start an emulator for android app Espresso UI Testing in Windows environment?

Would like to ask, as titled,
How to start an emulator for android app Espresso UI Testing in Windows environment?
Below is my yml.
name: Run Espresso UI Testing

on:
  workflow_dispatch:
  push:
    branches:
      - TestGithubActionEspresso
jobs:
  run-espresso:
    runs-on: windows-latest
    steps:
      - name: Checkout code
        uses<EMAIL_ADDRESS>      - name: Set up JDK 11
        uses<EMAIL_ADDRESS>        with:
          distribution: 'adopt'
          java-version: '17'

      - name: Grant execute permissions for gradlew
        run: chmod +x ./gradlew

      - name: Set up Android SDK
        uses: android-actions/setup-android@v3
        with:
          api-level: 34
          build-tools: '34.0.0'
          components: platform-tools, emulator

      - name: Install system image for emulator
        run: |
          sdkmanager.bat "system-images;android-34;google_apis;x86_64"
          sdkmanager.bat --licenses

      - name: Create and start the emulator
        run: |
          emulator.exe -avd test -no-window -no-audio -no-boot-anim
          timeout /t 120
          adb wait-for-device
          adb shell input keyevent 82

So far it works great till the last part
emulator.exe -avd test -no-window -no-audio -no-boot-anim
With error "The term emulator.exe is not recognized ..."

What did i miss?
Thanks in advance.

my bad, i overlooked the fact that the emulator isn't added into the path. Means i have to check run it from ANDROID_SDK_ROOT


Split the claim forms into 2

Context
Previously the claim form was used for the support user and normal user journey. These journeys start to diverge a bit, mainly when redirecting the user so to make our code a bit more manageable we decided to split the claim forms into 2.
This commit also fixes some issues with redirecting the support user to the correct page
Changes proposed in this pull request
Created new ::Support claim forms with their redirect paths
Guidance to review
Log in as Colin
Create a claim
On the check page change the mentors
Add a mentor and click continue
Hit the back link to not input any training hours
Hit the back link again
The Mentor you added without mentor training hours should not be on the check page again
Screenshots
https://github.com/DFE-Digital/itt-mentor-services/assets/11318084/1f9d44d3-7ecb-4ff0-a7aa-7039a736bdf7

 Create Support variants of the Claims-flow form objects


Adding a note about consulting in the README.

exchangeId on Client Events does not seems to work. It appears that exchangeId is not being passed as described by the documentation. I even tried setting exchangeId on the initial request and it didn't seem to make any difference.

Coverage remained the same at 93.273% when pulling 2112331f431059e5122ec668d3528b82df72f5aa on consulting-reference into 9ae5b29501a25ff3cbc04141d4063c492dea9f08 on master.

@nonedeactivated I think your branch has some issues.


Implementation of prefix, suffix, and char inclusion string abstract domains

Description
This pull request implements the prefix, suffix, and char inclusion string abstract domains, as described here.
Further content
The aforementioned domains just model the abstract semantics of operations concerning just strings (e.g., concatenation) and not the others (e.g., substring)

Related to #232


Maybe better to reset some elements like h1 ... h6

Hi,
Maybe better to reset some elements like h1 ... h6 regarding margin and padding.
Here is an example regarding on what generate sass compass reset
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, embed,
figure, figcaption, footer, header, hgroup,
menu, nav, output, ruby, section, summary,
time, mark, audio, video {
  margin: 0;
  padding: 0;
  border: 0;
  font: inherit;
  font-size: 100%;
  vertical-align: baseline;
}

@yourchoice
From the README:

[normalize] Preserves useful defaults, unlike many CSS resets.

In other words, normalize is not about resetting property values.

k, you are right


semver2 version constraint in dependencies is wrong

Output of helm version:
version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.18.2"}
Output of kubectl version: N/A
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS

I published an own keycloak-operator to ACR, with versions: [
18.0.0_18
0.0-setDuringBuild_17
0.0-setDuringBuild_16
0.0-setDuringBuild_15
18.0.0_14
17.0.1_13
]
my umbrella chart dependencies contain:
dependencies:
  - name: keycloak-operator
    version: "~18.0.0" # this version must be pinned as ~ does not work
    repository: "oci://ACR.azurecr.io/helm"

helm dependency update

resolves "Pulled: ACR.azurecr.io/helm/keycloak-operator:18.0.0_14"
This is wrong. I have to pin the version to version: "18.0.0+18" to make it work.

Closing this issue as answered. Please feel free to comment here and let us know if you have further questions. Thanks!


Pivot Table Time Column  Time Grain not working

Version: 0.28.1
DB       :Oracle
hi all
i meet a problem is the Time Grain not working on Visualization Type Pivot Table ,but on Type Time Seriese is working.

I found that the pivot table is different from the SQL of the Time Series on time column.
the pivote table is create_time
the Time Series is trunc(create_time,'DD')

Issue Has been resolved by Generate a new column where copy from time column

Issue Has been resolved by Generate a new column where copy from time column

Hello, I am encountering the same problem ( with the pivot visualization, it does not apply the defined time grain period ) and I tried to use your workaround but it does not seem to work in my case. May you please give more details about your solution?
Many thanks!


Epub onTap "freeze" on device rotation

Bug Report
What happened?
When device is rotated in landscape for example, the onTap functionality seems to stop working. It doesn't seems to fix itself after rotating the device back to the original orientation. As I said in slack it happens on certain devices/models. For example it never happened on my personal OnePlus Nord (android 12). I am attaching a video captured on emulator using the readium test app.
Expected behavior

How to reproduce?
Open the test app and load a book (in this example i used Le Mystere from the OPDS Test catalog). Once the book is loaded rotate the device orientation and tap in the middle or the sides.
https://github.com/readium/kotlin-toolkit/assets/109721963/7be1ed47-05fa-4b39-b99e-c5c4eca550fb
Environment

Readium version: 2.3.0

Development environment

OS: Windows 11
IDE: Android Studio Chipmunk | 2021.2.1 Patch 2

Testing device

Android version:
Model: Xiaomi 11 Lite 5G NE | MIUI 14.0.6
Is it an emulator? No

Android version:
Model: Pixel 5 API 33
Is it an emulator? Yes

Additional context

@LubomirGanchev Let me know if this helps: https://github.com/readium/kotlin-toolkit/pull/361

Hi Michael, sorry for the late answer, but this change seems to fix the problem!


default_version_upgrade_config.yml file missing from aca-py release

default_version_upgrade_config.yml is missing from aca-py python release - this file is required to run the aca-py upgrade command.
See this issue:  https://github.com/bcgov/openshift-aries-mediator-service/issues/25

The file is in the correct location and contains the correct content.  It just needs to be included in the release.
I did find it strange that you can only specify versions that are explicitly listed in the config file and that when upgrading to v0.8.0 you have to specify --from-version=v0.8.0 rather than indicating the version you're actually upgrading from.

The file existing in the source code; https://github.com/hyperledger/aries-cloudagent-python/tree/main/aries_cloudagent/commands
But is not included in the PyPi distributions; https://github.com/bcgov/openshift-aries-mediator-service/issues/25#issuecomment-1481453249
and therefore is not installed on the images.

OK — some somewhere there is a manifest of things to include in the PyPi release.  I’ll see what I can figure out.

But that means we need to do a 0.8.1 immediately, right?

I can’t see how to add it to the package. AFAIK, the PyPi release should pickup everything in aries_cloudagent, which should include that file.
@ianco — if you know what update is needed, please do it. If not, I’ll get someone else to investigate.  I’m assuming this is trivial.


Nitpick: missing git tags for recent versions

A nitpick: the git tags for v4.2.1 - v4.3.1 seem to be missing, and could be useful to push to make it easier to compare released versions.

From attempting to track these down locally, here's what I believe the commit history for the affected range-to-date looks like:
8c41c1da7739c4cace893d95fe78a9d35b3877c9 (HEAD -> master, tag: v4.3.7, origin/master, origin/HEAD) Added roundTo function
e721cb793ff9625ebf8e5e964dc5d226a91b3396 (tag: v4.3.6) New version
b634c068c5ae3a31979544bca61f349bfd9dbbba Fixed legacy import
e7a04d2c1d2ee39f8903de56a041a7a7b5f48be1 (tag: v4.3.5) solved ESM issues
b8f1f38098ec62743f9349039c01ced3914209a5 (tag: v4.3.3) revert changes
1f9f8b223cd9c355314af743a1f72f840161d1c2 Added module exports
e45a4180b29aee490d9a8013c3beb1cf14c82390 (tag: v4.3.2) Fixed import error
fdd86bce3ae64a1b1f9f86d46a1a14fe6e446648 (tag: v4.3.1) New version
c0d48d892c3823791c629a0b1ae93cdd1220d94d Fixed main entry
0c573e6f06372334dfc51a3dab34723347433c05 Update README.md
e03962a94ee5b3a8ba4794a15c77f988d0d1f6c9 Update LICENSE
ac859f071c84740749746dbc1fe66bbb0bbb81eb Update README.md
5c66d93d17b7a1c80f88e0d01a62e4d2497e58ac Update README.md
47102bdde4d8bf8f6d0d24b8aef3b50b41ed9949 (tag: v4.3.0) Native ES module support
4006900b6f7569d53abf9ea7377f0ddfb9708a08 Update README.md
eb0e1094434ecf4397685a2be287ddd5c15f073d (tag: v4.2.1) Improved throwing behavior
60d6cd8b0866b047b0aa2306ff615d5af90d5382 Update bigfraction.js
a7d0920af49a542779a16e1ac540d46a8c725d23 Update fraction.js
71e151fd5ccf542018307cee4a3639f42254d231 Update README.md
66027448d0a3ce7d8f8e9f2072a383a27cfb6245 Update README.md
d872774425760ca4b28cf3570c93b7de5be74ad8 Update README.md
3fddf47b671f7acafe68008bd48f69ccc02cfdef Improved abs expression for bigfraction
08a9f094c396ae7bc25ed9246bcd4229964fe38c Improved abs expression
1e7fddbf208f21f7c43213fef93de83667f7c448 Update README.md
d05ef555c1cf45bc2ea7ac5111fbe1e6c65871d6 Update hesse-convergence.js
c2b06917f801ce5aee26f95466b22ddc7e003704 Update bigfraction.js
5bb55ba9f3c06c3bbab1205494a24aade3a8a6e0 Update README.md
9d2f3d4abe58918cf19c82167784d36204834a1e (tag: v4.2.0) New relase

@infusion please could you push the absent release git tags to this repository?  I've attempted to find the commits that they correspond to in the previous comment.
To explain the request: when upgrading between versions of dependencies I try to compare the changes between the two versions using source control.  Depending on the number and nature of those changes, it can be difficult to do that review - but in any case it's much more difficult in cases where tagged versions aren't available.

Adding to the previous list, I think the corresponding tags for 5.0.0 to 5.0.2 are:
c64b1d6d738641dee01dfca6b66cf37de9989aca - 5.0.2
e440f9cd01dfe30f97fca3b179ca08d3de4f8d99 - 5.0.1
1adcc765e0ae4bed39b4039309ec48c70d5b7701 - 5.0.0

The tags were added, thanks!

Thank you!


"a" key no longer works

New user here. After adding kwm to launchd it seems that the "a" key no longer works in any application. unloading the service fixes things, but of course ends the kwm process. Any ideas why this might happen?

I had installed using homebrew, and symlinked the plist into the Library/LaunchAgents, then launchctl load -w ......

duplicate #243


Problems calling createLocalVue

I'm trying to set up some unit tests with Vuex according to the instructions to mock with modules. I'm using mocha-webpack.
However, I'm getting an error like the person is having here.
RUNTIME EXCEPTION  Exception occurred while loading your tests

TypeError: key.charAt is not a function
    at Object.has (/path/to/.tmp/mocha-webpack/1514500595138/bundle.js:24884:50)
    ...

So in my test spec:
// Hello.spec.js

import Vuex from 'vuex';
import { createLocalVue } from 'vue-test-utils';

import myModule from "../../../../store/modules/users";
const localVue = createLocalVue(); // Problem goes away if this is commented out.

describe("Hello World", () => {
});

I think there's some collision with Vue.use(Vuex) during bootstrap? But, it's not easy for me to separate that and the components usage of it during my tests cases.
My package.json test script looks like this
    "unit": "BABEL_ENV=test mocha-webpack --webpack-config build/webpack.test.conf.js --require test/unit/.setup src/**/*.spec.js --watch",

UPDATE WITH MORE INFO
My problem may have something to do with how webpack is not resolving index.js correctly from the directory name.
This configuration results in the charAt error I listed above. However, it still remains true that if I exclude createLocalVue() I get no problems and tests are able to run fine.
// ../../../../store/modules/users.js

import { foo } from "../../../libs";
console.log('foo is', foo)
// foo is function foo(bar) {
//  return bar;
// }
export default { } ;

This configuration (when I change to import { foo } from "../../../libs/foo" works fine with all my tests running successfully.
// ../../../../store/modules/users.js

import { foo } from "../../../libs/foo";
console.log('foo is', foo)
// foo is function foo(bar) {
//  return bar;
// }
export default { } ;

// foo.js

export const foo = bar => bar;

// ../../../libs/index.js

export { foo } from "./foo";

Here's my  webpack config. I have no issues running the code in other environments (e.g. development, production).

Normally you don't use the real Vuex store in your tests, since vue-test-utils is for testing components.
Can you post the whole test (what you want to test) and component? There is probably a better alternative that using your actual Vuex store.
I write a lot about this here, you can take a look there, or I can help you work through testing your component here.

Are you able to provide a minimal reproduction?

Thanks guys, I'll provide some more code later today.
@lmiller1990 Thanks for the post, but yeah I'm not trying to use the real Vuex store and as you can see in my test spec I'm trying to create a local Vue to mock it (I didn't include the localVue.use(Vuex) because it was already breaking before that as noted in my comments.
However, Webpack seems to still need to bundle all the other components that depend on Vuex, and there's some conflict going on somewhere when I call createLocalVue().

Potentially this is caused by a previously installed plugin.
Either way, we should wrap createLocalVue in a try/catch and throw a more user friendly error message.

@eddyerburgh I have wrapped createLocalVue in a try/catch but get the same error message.
try {
  const localVue = createLocalVue();
  localVue.use(Vuex);
}
catch(err) {
  console.log('err is', err)
}

Actually doing a reproduction may be a little more complicated, so before I do that, do you know of any existing examples of vue-test-utils+mocha-webpack+vuex? @eddyerburgh The closest I see is your example but it uses Karma. Maybe I can compare my setup to existing examples to get ideas to solve my problem However, I updated the original question with a little more info that may spark some ideas.

Sorry been slow to respond. We're using vuetify and suspect the problems lies there too

Same using the vue-js-modal, trying to figure out what's going on.


Fix MirrorResources relative path exception on mac

On macOS and .NET Core 3.0, a relative href is interpreted as a file://
uri and will be parsed into a Uri object successfully.  This causes the
MirrorResources module to fail when trying to create an http request
with a file:// scheme.  Only http:// and https:// schemes are valid.

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


Recursive QAOA

Description of changes:
Adding the Recursive QAOA to the portfolio of textbook algorithms.
The implementation is based on the OpenQAOA library
Testing done:
I have installed the dependencies needed by OpenQAOA and successfully run the notebook. I will need some feedback on how you want to structure the quantum part though!
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[X] I have read the CONTRIBUTING doc
[X] I used the commit message format described in CONTRIBUTING
[X] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have checked that my tests are not configured for a specific region or account (if appropriate)

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

@Q-lds Thank you again for this contribution.
Per an offline discussion we agreed to close this request. While it showcases the OpenQAOA algorithm and can run on Braket it doesnt fit the content of this repo for reasons listed below. We will update the contribution guidelines to offer clarity for future contributions. Thanks again!

In this repository we expect algorithms to be built on top of the Braket SDK to provide a unified user experience and to give us a single contract to test against. The notebook in your PR uses the OpenQAOA  interface to setup a device and to run tasks.
All functional code relies on pulling in OpenQAOA as written but the expectation in the algorithm library is that algorithms are actually added under https://github.com/aws-samples/amazon-braket-algorithm-library/tree/main/src/braket/experimental/algorithms. This allows unit tests to happen in the repository and allows users of the library to easily modify the algorithms.


Love it! Quick fork with col1 as x-axis + float support

For those discovering this repo but want the first column to be an x-axis, here's a fork. also adds support for floats and renders the x axis
https://github.com/kumavis/chart-csv/commit/01f61ec4777b80bf47193491e0feeeab543cf509

@kumavis
Hi! Your version works great!
Is the a chance, to use dates ( format: yyyy-mm-dd ) as x-axis (column 1) and how can this be done?


feat(permissions): Update Application Permissions

Coverage remained the same at 55.83% when pulling 45bfb4e927e11c80a649075c3f89a9088d4c9147 on permissions into 53e40fda7feb4a87591524c87bc4d863507ab246 on master.


Add Support for HttpContext.RewritePath of 2 params and 4 params

Summary
The HttpContext in adapter only supports RewritePath(String). But there is also usage of RewritePath(String, Boolean) and RewritePath(String, String, String, Boolean).
Motivation and goals
RewritePath(String, Boolean) and RewritePath(String, String, String, Boolean) are used in SharePoint Online. But they are not supported in the adapter. I use the code below instead.
// case1: 2 params
// old one
context.RewritePath( newFilePath + originalPathInfo, true);
 // my workaround
context.RewritePath(newFilePath + originalPathInfo)

// case2: 4 params
// old one
context.RewritePath( newFilePath, originalPathInfo, originalQueryString, true);
// my workaround
context.RewritePath(newFilePath + originalPathInfo + "?" + originalQueryString)

I wonder if there is plan to support the API.
In scope
Add support of RewritePath(String, Boolean) and RewritePath(String, String, String, Boolean)
Examples
context.RewritePath( newFilePath + originalPathInfo, true);

context.RewritePath( newFilePath, originalPathInfo, originalQueryString, true);

Happy to take a PR for this. Here's what ASP.NET Framework is doing here: https://referencesource.microsoft.com/#System.Web/HttpContext.cs,e1239e4275e728f9. That's more to understand the importance of the parameters - the code won't be a drop in replacement :)


Migrate notes

Tasks

[ ] Migrate @hyschive's notes on Evernote to GitHub

@hyschive Do we still need this? Like anything else you want to add.

@cindytsai You can close it.


Create towers of hanoi

What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


ci: downgrade 16/8 core runners

Feature or Problem
This PR downgrades our use of 16 and 8 core runners to assist with the ask of CNCF project maintainers to use the default runners where possible. I plan on watching the CI on this PR to understand what takes a long time, and I think we should optimize from there.
Other things that I'd like to do

[ ] Combine CI runs when merging to main by merging multiple PRs in the merge group at the same time
[ ] Remove unneeded action runs on PR where possible

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

If the general ask is to reduce our usage -- maybe we could start not running some builds (ex. the windows build takes forever) until we're doing a release?

@vados-cosmonic 100%, looking at the actions it looks like the Windows builds and windows tests take 20+ minutes, and we should run those perhaps only on main. The only other action that takes more than 10 minutes is wash integration tests, which we should try and optimize

I mean I'd say the windows tests should be done before releases, not even on main -- I think the number of people using random commits to run on windows rounds to zero -- and the problem is that despite our best efforts the main CI results are red from time to time, I'm not sure anyone is watching that signal.
Maybe the windows tests are a good candidate for some sort of scheduled daily spot checks or something, but then again someone would need to be responsible for that signal-- it seems like the real touch-point for making sure windows works is releases, as most people will be using the project based on an official release.
As for the wash tests, since we now are OK with testcontainers, they are trivially serializable. What might be more important may be figuring out why they weren't so serializable with just baremetal instances... I think someone could solve that effectively given some time to really dig into it.


Convert exceptions to Kotlin

Towards #532

@JSunde  PTAL?

Codecov Report

Merging #1283 (7aef4e6) into master (4830f7a) will increase coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1283      +/-   ##
============================================
+ Coverage     29.38%   29.60%   +0.22%
- Complexity      798      813      +15
============================================
  Files           295      298       +3
  Lines          7045     7106      +61
  Branches        405      407       +2
============================================
+ Hits           2070     2104      +34
- Misses         4856     4881      +25
- Partials        119      121       +2

Impacted Files
Coverage Δ

...com/google/android/ground/ui/map/CameraPosition.kt
0.00% <0.00%> (ø)

...oogle/android/ground/ui/home/HomeScreenFragment.kt
0.00% <0.00%> (ø)

...le/android/ground/ui/map/gms/GoogleMapsFragment.kt
0.00% <0.00%> (ø)

...round/ui/home/mapcontainer/MapContainerFragment.kt
0.00% <0.00%> (ø)

...ound/ui/home/mapcontainer/MapContainerViewModel.kt
0.00% <0.00%> (ø)

...ogle/android/ground/ui/common/BindingAdapters.java

...gle/android/ground/ui/common/ViewModelFactory.java

...d/ground/persistence/remote/NotFoundException.java

...ogle/android/ground/ui/common/ProgressDialogs.java

...rsistence/local/LocalDataConsistencyException.java

... and 13 more

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


Intergartions tests for authentication policies

[ ] Verify the policies are distributed correctly, to the expected workloads.

[ ] Verify the interaction behaviors with other APIs (e.g gateways, sidecar, VS)

[ ] Combine with DRs, verify connection can be made

Note: some of these are overlapping with https://github.com/istio/istio/issues/14195

This can be closed I believe? @diemtvu


Show section name as symbol name in fileinfo relocation tables

Right now, fileinfo relocation tables show an empty symbol name if the relocation is referring to a section. This also causes some issues when it gets passed to the decoder.
Example from readelf:
Relocation section '.rel.text' at offset 0x2e54 contains 118 entries:
Offset     Info    Type            Sym.Value  Sym. Name
00000774  00000105 R_MIPS_HI16       00000000   .text
00000778  00000106 R_MIPS_LO16       00000000   .text
00000e90  00000405 R_MIPS_HI16       00000000   .rodata
00000e9c  00000406 R_MIPS_LO16       00000000   .rodata
00000f48  00000405 R_MIPS_HI16       00000000   .rodata
00000f50  00000406 R_MIPS_LO16       00000000   .rodata
00000ffc  00000105 R_MIPS_HI16       00000000   .text
00001008  00000106 R_MIPS_LO16       00000000   .text
00001110  00000705 R_MIPS_HI16       00000000   .bss
0000111c  00000706 R_MIPS_LO16       00000000   .bss
00001114  00001f05 R_MIPS_HI16       00000e90   abcd_1
00001124  00001f06 R_MIPS_LO16       00000e90   abcd_1
RetDec fileinfo output:
i     type      offset         symbol name                                       symValue  addend    calcValue
0     5         0x0774                                                           0         0         0
1     6         0x0778                                                           0         0         0
2     5         0x0e90                                                           0         0         0
3     6         0x0e9c                                                           0         0         0
4     5         0x0f48                                                           0         0         0
5     6         0x0f50                                                           0         0         0
6     5         0x0ffc                                                           0         0         0
7     6         0x1008                                                           0         0         0
8     5         0x1110                                                           0         0         0
9     6         0x111c                                                           0         0         0
10    5         0x1114         abcd_1                                            3728      0         0
11    6         0x1124         abcd_1                                            3728      0         3728

Maybe we could do this, it may not be a problem.
Can you do the following?

Provide a sample where this occurs?
Describe the issues in this statement: This also causes some issues when it gets passed to the decoder.

Hello,
If i recall correctly, I believe the problem was happening when there is a function at the start of a section, but the function name isn't in the symbol table.... But, it turns out the real issue with this may be do to the .note section being decompiled as code somehow, which messes up the decoding.
Here is the kernel module in question:
oem.ko.zip

Thanks, if these issues happen while decompiling the given sample, I will look into them as well.


[bug report] when there are disabled nodes in El tree, select all (top node) to select the disabled node, but select its child node to select the disabled node;

Element UI version
2.15.3
OS/Browsers version
win10 版本20H2/chrome 版本 91.0.4472.124（正式版本） （64 位）
Vue version
2.6.14
Reproduction Link
https://codepen.io/qd-pangyongkang/pen/eYWZvVX?editors=1111
Steps to reproduce
当二级存在禁用时，选择第一级全选，无法选中二级禁用的选项，但是选择其全部三级子项，可以选中二级，并且此时操作全选，无法控制该三级子项
When the second level is disabled, select the first level to be all selected, and the second-level disabled option cannot be selected, but select all the third-level subitems, and the second level can be selected, and the operation is all selected at this time, and the third-level subitems cannot be controlled
What is Expected?
选择全选时，将树所有节点选中
When selecting All, select all nodes of the tree
What is actually happening?
选择全选时，存在“非禁用状态的子级”的父级无法被选中
When you select all, a parent with a "child in a non-disabled state" cannot be selected

规则貌似是子集有禁用的，父级是无法控制


Add Clubstep [Piano Cover] by PNG - Music

Song Name
Clubstep [Piano Cover]
Artist Name
PNG - Music & Covers
Source
Youtube
Youtube Link
MEk1Mf02L7U
Direct File Link
No response
Song ID
13
Start Offset [ms]
2800
Extra
Created from Auto Nong by OmerAras55.

Please add this cover.


Typing '@' doesn't work on German keyboard layout (Windows)

Not only the @ symbol is affected, but most symbols that are produced using the AltGr key, like ~ and €.
The symbol '{' works (AltGr + 7), however, '}' doesn't (AltGr + 9). Until this is fixed Terminus is basically unusable for German users.
Doesn't matter which shell is used.

Duplicate of #17


enter press in card

by default deletes one item
better when press enter add new item

also strange that press enter always deletes first item - very confusing

press enter result in delete only when card item selected, when item not focused - all ok, nothing happens


[RESOLVED] High ICMP ping response time

Problem started at 02:09:14 on 2023.07.10
Problem name: High ICMP ping response time
Host: MF-FG
Severity: Warning
Operational data: Value: 189ms
Original problem ID: 32031
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23132&eventid=32031

Problem has been resolved in 1m 0s at 02:10:14 on 2023.07.10
Problem name: High ICMP ping response time
Host: MF-FG
Severity: Warning
Original problem ID: 32031


refactor: remove use of 'any' type

Description

Replaced any Type: Updated the code to use specific types instead of any.
Removed ESLint Comments: Deleted unnecessary eslint-disable-next-line comments that were bypassing type-related linting rules.

Why

Replacing any type with specific types improves type safety, helps catch errors early, and makes the code easier to read and maintain.

Issue
311
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally

We had tried few changes like this couple of months back(in older package version) where all issues are resolved in shared-component repo but portal app got broken because of these changes. Pls make sure that you build portal app locally with this change and do a sanity check all the pages where these components are being used.

@manojava-gk , Thanks for the reminder. I’ve already built the portal app locally with these changes and performed a thorough sanity check on all relevant pages. I’ve shared the details in the PR: #1113. Please review it and let me know if there are any additional concerns.


Need support for error message while forming a Node class object in Jsonpatch

Hi, I was working on removing property values from a json for a given JsonPointer using jsonpatch.remove from main branch / jsonpatch.apply_remove from v9.0
example_json = {
    "foo": variable
}
json_pointer = JsonPointer("/foo/{}".format(pointer))

Scenarios:

While forming a Node class why do we have an assert statemet. In production all the assert statements will be removed.
When the variable has a  value of None or integer and assertion was removed In that case we will be getting an error as AttributeError: Node object has no attribute type in line 256
Are we considering string as list of characters (Sequence). when  the Variable has a value of String and the pointer has a integer value less than length of the string we will get a error as TypeError: str object doesn't support item deletion in line 260
When the Variable has a value of String and the pointer has a integer value greater than or equal to the length of the string. we will get error as jschon.exceptions.JSONPatchError: Invalid array index {pointer_value} in line 219

Note:
In all the scenarios listed above we are giving a invalid JsonPointer for removing the value from json. Whether can we get a error response which says Invalid jsonpointer was passed {str(jsonpointer)}
Doubt:

In line 210 why we are not checking whether the given key can be converted into integer or not by using isdigit()

Thanks for raising this issue. I agree with all your points and will look into improving the handling of invalid pointers and other edge cases / ambiguities.
The jsonpatch module in fact has the lowest test coverage (~65%) of all jschon modules, so there's a clear case for more comprehensive testing of the JSON patch functionality, too.


agoragames-pyevent fails to build against libevent 2.x

On Mac OS:

built libevent-2.0.17 in a private (non-system) directory.

Downloaded agoragames-pyevent-0_4_2-0-g93d1ba3.tar

modified pyevent's setup.py to include this search block for libevent (to reference my private libevent build location) {code}
elif glob.glob('/Users/vkruglikov/Packages/libevent/libevent-2.0.17-stable/.libs/libevent.*'):
basePath = '/Users/vkruglikov/Packages/libevent/libevent-2.0.17-stable'
print 'found libevent under: ', basePath, '/.libs'
event = Extension(name='event',
sources=[ 'event.c' ],
libraries=[ 'event' ],
include_dirs=[os.path.join(basePath, 'include'), basePath],
library_dirs=[os.path.join(basePath, '.libs')])
{code}

Ran: python setup.py build

This failed with the following errors:
Vitalys-MacBook-Pro:agoragames-pyevent-93d1ba3 vkruglikov$ python setup.py build
found libevent under:  /Users/vkruglikov/Packages/libevent/libevent-2.0.17-stable /.libs
running build
running build_ext
building 'event' extension
llvm-gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe -I/Users/vkruglikov/Packages/libevent/libevent-2.0.17-stable/include -I/Users/vkruglikov/Packages/libevent/libevent-2.0.17-stable -I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c event.c -o build/temp.macosx-10.7-intel-2.6/event.o
event.c: In function ‘__pyx_pf_5event_5event_add’:
event.c:2069: warning: implicit conversion shortens 64-bit value into a 32-bit value
event.c:2076: warning: implicit conversion shortens 64-bit value into a 32-bit value
event.c: In function ‘__pyx_pf_5event_11bufferevent_read’:
event.c:4137: error: dereferencing pointer to incomplete type
event.c:4149: error: dereferencing pointer to incomplete type
event.c:4177: error: dereferencing pointer to incomplete type
event.c: In function ‘__pyx_pf_5event_11bufferevent_write’:
event.c:4247: warning: passing argument 2 of ‘PyObject_AsCharBuffer’ from incompatible pointer type
event.c:4247: warning: passing argument 3 of ‘PyObject_AsCharBuffer’ from incompatible pointer type
event.c: In function ‘__pyx_pf_5event_dns_resolve_reverse’:
event.c:5307: warning: passing argument 1 of ‘evdns_resolve_reverse’ from incompatible pointer type
event.c: In function ‘__pyx_pf_5event_dns_resolve_reverse_ipv6’:
event.c:5463: warning: passing argument 1 of ‘evdns_resolve_reverse’ from incompatible pointer type
event.c: In function ‘__pyx_pf_5event_12__wsgi_input_read’:
event.c:6320: warning: pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’ differ in signedness
event.c: In function ‘__pyx_f_5event___path_handler’:
event.c:6607: warning: assignment discards qualifiers from pointer target type
event.c:6630: warning: assignment discards qualifiers from pointer target type
event.c:6653: warning: assignment discards qualifiers from pointer target type
event.c: In function ‘__pyx_pf_5event_5event___simple_callback’:
event.c:1689: warning: implicit conversion shortens 64-bit value into a 32-bit value
event.c: In function ‘__pyx_pf_5event_5event_add’:
event.c:2069: warning: implicit conversion shortens 64-bit value into a 32-bit value
event.c:2076: warning: implicit conversion shortens 64-bit value into a 32-bit value
event.c: In function ‘__pyx_pf_5event_11bufferevent_read’:
event.c:4137: error: dereferencing pointer to incomplete type
event.c:4149: error: dereferencing pointer to incomplete type
event.c:4177: error: dereferencing pointer to incomplete type
event.c: In function ‘__pyx_pf_5event_11bufferevent_write’:
event.c:4247: warning: passing argument 2 of ‘PyObject_AsCharBuffer’ from incompatible pointer type
event.c:4247: warning: passing argument 3 of ‘PyObject_AsCharBuffer’ from incompatible pointer type
event.c: In function ‘__pyx_f_5event___evdns_callback’:
event.c:4536: warning: cast from pointer to integer of different size
event.c: In function ‘__pyx_pf_5event_dns_resolve_ipv4’:
event.c:4995: warning: cast to pointer from integer of different size
event.c: In function ‘__pyx_pf_5event_dns_resolve_ipv6’:
event.c:5151: warning: cast to pointer from integer of different size
event.c: In function ‘__pyx_pf_5event_dns_resolve_reverse’:
event.c:5307: warning: cast to pointer from integer of different size
event.c:5307: warning: passing argument 1 of ‘evdns_resolve_reverse’ from incompatible pointer type
event.c: In function ‘__pyx_pf_5event_dns_resolve_reverse_ipv6’:
event.c:5463: warning: cast to pointer from integer of different size
event.c:5463: warning: passing argument 1 of ‘evdns_resolve_reverse’ from incompatible pointer type
event.c: In function ‘__pyx_pf_5event_12__wsgi_input_read’:
event.c:6320: warning: pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’ differ in signedness
event.c: In function ‘__pyx_f_5event___path_handler’:
event.c:6607: warning: assignment discards qualifiers from pointer target type
event.c:6630: warning: assignment discards qualifiers from pointer target type
event.c:6653: warning: assignment discards qualifiers from pointer target type
lipo: can't open input file: /var/folders/my/whcrb5rn1rqc3g8klvk_vk580000gn/T//cctX4zKQ.out (No such file or directory)
error: command 'llvm-gcc-4.2' failed with exit status 1
Vitalys-MacBook-Pro:agoragames-pyevent-93d1ba3 vkruglikov$ uname -a
Darwin Vitalys-MacBook-Pro.local 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
Vitalys-MacBook-Pro:agoragames-pyevent-93d1ba3 vkruglikov$

pyevent doesn't compile against libevent2, only libevent1


PointerPressed event didn't work

Describe the bug
I just tried using the PointerPressed event as described in the discussion #10673 but it didn't work at all.
Expected behavior
I would like to use the PointerPressed event.
Desktop (please complete the following information):

OS: Windows 11
Version 11.0.0-rc1.1

Additional context
Example project that use PointerPressed:
AvaloniaApplication1.zip

Added a valid answer after trying out for 11.0 again. See: https://github.com/AvaloniaUI/Avalonia/discussions/10673#discussioncomment-6155908
I hope it helps.
Note: I'm closing this issue for now as I think it's by design. If someone disagrees, please let me know.

thanks for the sample btw. This was useful ;-)

Added a valid answer after trying out for 11.0 again. See: #10673 (reply in thread)
I hope it helps.
Note: I'm closing this issue for now as I think it's by design. If someone disagrees, please let me know.

I can confirm it behaves the same in WPF, MouseLeftButtonDown event will not be triggered, only PreviewMouseLeftButtonDown can be triggered.


[GLUTEN-3722][CH] Improve shuffle writer

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #3722)
Changes

Improve style of some codes in shuffle writer.
Make sure that columns buffer do not exceeds split size in shuffle writer
Remove all the locks in shuffle writer for write/spill/stop are executed in single jvm thread.
Protect memory spill from being called recursively.

@taiyang-li 看起来改动不下，能不能描述下设计？

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_3728_time.csv
log/native_master_11_29_2023_0ac1dc42d_time.csv
difference
percentage

q1
34.32
34.61
0.292
100.85%

q2
24.90
24.87
-0.028
99.89%

q3
37.98
36.61
-1.372
96.39%

q4
37.47
36.91
-0.564
98.50%

q5
72.38
71.43
-0.949
98.69%

q6
7.10
7.22
0.125
101.75%

q7
85.01
85.50
0.490
100.58%

q8
86.24
88.07
1.828
102.12%

q9
124.53
127.33
2.801
102.25%

q10
43.33
44.31
0.989
102.28%

q11
20.44
20.45
0.007
100.03%

q12
25.91
27.02
1.114
104.30%

q13
46.36
46.05
-0.308
99.34%

q14
18.57
18.98
0.404
102.18%

q15
27.95
29.21
1.258
104.50%

q16
15.31
15.65
0.348
102.27%

q17
102.53
101.75
-0.787
99.23%

q18
151.02
150.75
-0.272
99.82%

q19
12.82
13.94
1.123
108.76%

q20
28.02
30.32
2.305
108.23%

q21
225.61
225.21
-0.404
99.82%

q22
13.15
13.20
0.056
100.42%

total
1240.93
1249.39
8.457
100.68%


I3042 - !Sub arn:aws:iam::${AWS::AccountId}:root identified as having a hardcoded partition or wrongly placed pseudo param

cfn-lint version: 0.48.3 (latest at the time of writing)
Both !Sub arn:aws:iam::${AWS::AccountId}:root and arn:aws:iam::111122223333:root identified as having a hardcoded partition or wrongly placed pseudo param.
I haven't checked the code, but as it raises in both scenarios, I reckon the logic regards 'root' as hardcoded while I think this is something that should be an exception to this rule.
You could of course argue that arn:aws:iam::111122223333:root has a hardcoded partition and although this is actually used as example everywhere in the CFN documentation, I would be fine if this still raises I3042.
Resource example:
  KmsKey:
    Type: AWS::KMS::Key
    Properties:
      Description: Key to encrypt CodeArtifact items
      Enabled: true
      EnableKeyRotation: true
      KeyPolicy:
        Version: 2012-10-17
        Statement:
          - Sid: Allow access for Key Administrators
            Effect: Allow
            Principal:
              AWS:
                - !Sub arn:aws:iam::${AWS::AccountId}:root  # Keep it simple right now
            Action:
              - kms:Create*
              - kms:Describe*
              - kms:Enable*
              - kms:List*
              - kms:Put*
              - kms:Update*
              - kms:Revoke*
              - kms:Disable*
              - kms:Get*
              - kms:Delete*
              - kms:TagResource
              - kms:UntagResource
              - kms:ScheduleKeyDeletion
              - kms:CancelKeyDeletion
            Resource: '*'
          - Sid: Allow direct access to key metadata to the account
            Effect: Allow
            Principal:
              AWS:
                - !Sub arn:aws:iam::${AWS::AccountId}:root  # Keep it simple right now
            Action:
              - kms:Describe*
              - kms:Get*
              - kms:List*
            Resource: '*'
          - Sid: Allow Encrypt/Decrypt
            Effect: Allow
            Principal:
              AWS:
                - !Sub arn:aws:iam::${AWS::AccountId}:root  # Keep it simple right now
            Action:
              - kms:Encrypt
              - kms:Decrypt
              - kms:ReEncrypt*
              - kms:GenerateDataKey*
            Resource: '*'

I reckon the logic regards 'root' as hardcoded

That rule isn't suggesting changing root but rather suggesting !Sub arn:${AWS::Partition}:iam::${AWS::AccountId}:root
The reasoning for the suggestion is to increase portability of templates across partitions

I reckon the logic regards 'root' as hardcoded

That rule isn't suggesting changing root but rather suggesting !Sub arn:${AWS::Partition}:iam::${AWS::AccountId}:root
The reasoning for the suggestion is to increase portability of templates across partitions

Ah, that partition.. Thanks.


Fix typo in 'Gradient Descent, revisited' section

Fix typo in 'Gradient Descent, revisited' section, the labels are y and not w

Good catch, thanks for the PR!


proxy_pass Issue on nginx.conf File

Related Issues
There is an issue on Nginx test configuration (Nginx 1.18.0 on Ubuntu 22.04.3 LTS) after applying the config file: /etc/nginx/nginx.conf taken from Setting up an NGINX Load Balancer page:
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
    worker_connections 768;
    # multi_accept on;
}

stream {
    upstream rancher_servers_http {
        least_conn;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
    }
    server {
        listen 80;
        proxy_pass rancher_servers_http;
    }
}

http {
	sendfile on;
        tcp_nopush on;
        types_hash_max_size 2048;

        include /etc/nginx/mime.types;
        default_type application/octet-stream;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
        ssl_prefer_server_ciphers on;

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        gzip on;

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;

        upstream rancher_servers_https {
          least_conn;
          server <IP_ADDRESS>:443 max_fails=3 fail_timeout=5s;
          server <IP_ADDRESS>:443 max_fails=3 fail_timeout=5s;
          server <IP_ADDRESS>:443 max_fails=3 fail_timeout=5s;
        }

        server {
            listen 443 ssl;
            proxy_pass rancher_servers_https;

            ssl_certificate /etc/letsencrypt/live/rancher.devs.example.com/fullchain.pem;
            ssl_certificate_key /etc/letsencrypt/live/rancher.devs.example.com/privkey.pem;

            location / {
                proxy_pass https://rancher_servers_https;
                proxy_set_header Host rancher.devs.example.com;
                proxy_ssl_server_name on;
                proxy_ssl_name rancher.devs.example.com;
            }
        }
}

The error message:
nginx: [emerg] "proxy_pass" directive is not allowed here in /etc/nginx/nginx.conf:52
nginx: configuration file /etc/nginx/nginx.conf test failed

The line number 52 is at:
            proxy_pass rancher_servers_https;

Summary
What do you suggest to deploy the properly Load Balancer (based on Nginx) as guided on Rancher Docs to provide High Availability RKE2 Kubernetes Cluster?

Can you try the suggestion from https://github.com/rancher/rancher-docs/pull/819, which is to remove the proxy_pass rancher_servers_https; line from the http.server block.


Front matter support

I was wondering if front matter support (via yaml, f.e.) will be available in the future.
It would allow extra metadata such as date
---
title: Remote Working Policy
author: Giovanni Lanzani
date: 2024.06.14
---

This isn't something that I have any plans for, but wouldn't be against it if there were sufficient demand.

I just started using flatnotes (nice app btw) and was surprised it wasn't already using front matter. It's more common in flat file blogging platforms in my experience, but I had assumed going in that that's where it would keep track of tags and other metadata. I also imagine that knowing the creation date would be helpful as your notes library grows, and creation date could possibly be another sorting option too.

I agree with adding front matter support. So my markdown notes will also be usable across other platforms. Thanks.


Semantic issues

Thanks for the fix/improvements. In the future, you might want to make changes via Markdown Here's Crowdin project: https://crowdin.com/project/markdown-here/es-ES
(I'll upload these changes to there right now.)