refactor: Made settings (index.html) page responsive, Seperate settin…

PR Description 📜
📌 refactor: Made settings (index.html) page responsive
📌 Seperated game.html from settings (index.html)
📌 Created seperate CSS files, to avoid any possible conflicts
📌 Going back to the settings page is possible after a match. It was earlier not possible.
📌 favicon fixed
Fixes #237

Mark the task you have completed ✅

[X] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X] I have added screenshot for review.

## Add your screenshots(Optional) 📸
Desktop:

Mobile:

Thank you soo much for contributing to our repository 💗

@Durgesh4993 Please review my PR...

@Durgesh4993 In the main branch, which is in sync with the original branch, when I pulled the latest changes, by other contributors, I found that several of the features are not working, like the Exit button, or the rank chart....
So what should I do, should I merged it like that only...? Or should I raise another issue, to fix all of those pseudo features...?
Current version: Several of the contributions are just pseudo, there is absolutely NO functionality attached with it, just simple changes done in the UI...Please go the video, you will get it
https://youtu.be/CqsJ7gw5tiM
My version:
https://youtu.be/UczvESNf7e8
If I have your permission, then I will eliminate all the unwanted changes done by others, in this project...It will also solve all the unnecessary merge conflicts....

@mondalsurojit do one thing reclone the repository and then send the PR


chore: refactor knuu object to use options as argument

This PR proposes a change to use options as an argument in the new function instead of using WithFuncs.

Summary by CodeRabbit

Refactor

Improved code readability and maintainability by centralizing configuration options into a single Options struct.
Replaced individual option functions with a unified Options struct for easier management.

Tests

Updated test cases to use the new Options struct instead of individual options, ensuring consistency and simplifying test setup.

Closes #410

Thanks for finding it. I did not.


Include machineName in message document

What does this PR do?

Add requirement for mongodb extension
Add machineName  to the message document

Checklist

[ ] Pull request contains a clear definition of changes
[ ] Tests (either unit, integration, or acceptance) written and passing
[ ] Relevant documentation produced and/or updated

Coverage remained the same at 100.0% when pulling 8410f03c9a19aaf5c13410fe4433472abe81e68a on chadicus:master into 08e6d6ae6e4097e911a8df6a3b03b9c338cfa37d on traderinteractive:master.

Coverage remained the same at 100.0% when pulling 8410f03c9a19aaf5c13410fe4433472abe81e68a on chadicus:master into 08e6d6ae6e4097e911a8df6a3b03b9c338cfa37d on traderinteractive:master.


test(board-spec-remove): remove board spec temporarily

Due to this bug https://github.com/fabric8io/fabric8-planner/issues/1296

@ldimaggi can you plz look into it!


Added support for SQLITE_OPEN_SHAREDCACHE to facilitate migrating from other sqlite libraries

I have added a sharedCache flag to Connection initializers. This allows multiple connections to be made to the same database within a process. If true, the "SQLITE_OPEN_SHAREDCACHE" bitmask is ORed to the flags passed to the database open function call. This can be useful if gradually migrating from another sqlite3 library to SQLite, so that both libraries can open the same database and read/write to it.
See here for further information: https://sqlite.org/sharedcache.html

I think it would be better to expose all possible flags to sqlite3_open_v2 as an OptionSet which gets passed into the initializer.


⚠ GitLab Server has degraded performance

In 71f711b, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 13454 ms

Resolved: GitLab Server performance has improved in 3a74121.


⚠ SceneTime has degraded performance

In 7fc4306, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1950 ms

Resolved: SceneTime performance has improved in 94c4a4e after 6 minutes.


[tvOS, ATV, fireTV] [Regression] Home screen focus issues on flexn/template

rnv version: 0.36.1-canary.2
flexn template version: 0.16.0

[ ] After clicking right when focused on "Try Me!" screen scrolls down

Be focused on "Try Me!"
Click right -> screen scrolls down

Expected:  nothing should happen

[ ] After clicking down when focused on "Now Try Me!" focus is on twitter icon

Be focused on "Now Try Me!"
Click down -> focus is on twitter icon

Expected:  focus should be on chrome icon

reopening as it was closed by a pr

Tested on tvOS and androidTV simulators - works as expected


feat: add home page link in navbar

Fixes #152
Hi, I hope everything looks good. If possible, can you please add the label hacktoberfest-accepted onto this PR so it can count towards my hacktoberfest contribution. Thank you.

@jainsujay02 Can you please review this?

Hey Ansh, I'm a little busy this week, but I've assigned ACM's dev team director to review your code!

Fixed with #157


Logger

Logger branch

Looks great. If the status checks pass I will merge it.

Ok, I'll write some tests for it tonight. Also about to submit another PR to update the travis config and also run swift build as part of the ci process.
Anyone have any ideas how to run tests with the SPM? We can perhaps do a second build using Xcode.

I don't think there is anyway to run tests in pure SPM right now. It's coming soon. You have to run them through Xcode though which is hard to do on Travis with Swift 2.2.
It's definitely feasible to make sure to police each other and verify we are running the tests before merging, though.

I've changed the example log in the request t o VERBOSE

@mpclarkson Let me know when the tests are done. Also, if you could prepare a Log.md page for the Wiki I will add that when this is pushed. It will be release 0.1.10

@tannernelson yes will add tests later today

@tannernelson tests are written and pushed. Should be fine to merge.
I'll do the Log.md a bit later... I have some 'real' work to get done now.

Hmm... looks like it thinks there's a merge conflict. Try merging master back into your log branch.
I forgot this wasn't merged and was just trying to use it haha.

yeah... there's two. One is in the Xcode project which is a pain.. working on it.


Suggested corrections for repository management tool

First, it is difficult to understand the difference between input and output in the content under the heading Create root
Second, the output of repository.status() doesn't match with the documented output.
Create root - repository.status()
Third, the expiration date in the documentation should be updated.
Create timestamp, snapshot, targets

The documentation uses >>> for input, # for comments, and no symbols for output.
The output of status() in the document was verified to match what is currently printed.
The expiration was set to >>> repository.timestamp.expiration = datetime.datetime(2080, 10, 28, 12, 8)


new: updated node version to 16.17.0

new: updated node version to 16.17.0

I think this PR intersects with #317, since that PR uses Node in a new place. If we ship #317 in the upcoming patch release, then we could rebase this PR on the master branch then.


fix: add background color token and remove font heading token

Hi @cheton
I also added and updated the marked color and selection example of the Text component, please help me to verify again. Thanks

See https://github.com/trendmicro-frontend/styled-ui/issues/255 for the proposal of the new enhancement.

Close this PR in favor of #258


enforce pc in LEM SuperNova

Implements one box in #637

That means each coprocessor circuit must check that the index input is the one statically assigned for the enum variant. This is trivial but must be performed — even for the universal circuit, which must ensure the incoming index is 0.

I think this particular requirement (described above)was actually satisfied by https://github.com/lurk-lab/arecibo/pull/41. However, it's still important that each coprocessor check the CEK context and only produce proofs if it is indeed capable/permitted to reduce a given state. I believe this is being correctly checked elsewhere, but it's hard for me to identify that spot because it's now (hopefully?) buried in LEM code rather than living in a clear, unavoidable, coprocessor wrapper of some kind.


west: Fix unused import and variable

Making a clean slate for a pylint test in CI.
'_' is a common name for non-problematic unused variables in Python.
pylint knows not to flag it.

Nice work!


[CSV-63] CSVPrinter always quotes empty string if it is the first on a

I modified CSVPrinter.printRecords() methods and CSVFormat.printRecord() methods to handle first value of a record differently if it is an empty string and there are following values

Thank you @tha2015 , this is a fix we would very much like to see.

@tha2015
May you please rebase on git master?

Is this still part of the main branch? 🤔

Is this still part of the main branch? 🤔

I don't understand the question.

Could we merge the PR and bring the changes to the main branch? 🤔

is this going to be merged any time soon?

This PR needs to be rebased on master.

Sorry but I'm not working with it anymore. Please feel free to make changes or close it.

Note: My local test on Windows shows that Excel consumes "",r1c2 the same as ,r1c2.


Docker image root directory

Is there a reason that / is set to /dist/docker/bin for the docker image?
I would like to use nsq_to_file and output messages to /dev/null to avoid the queues filling up my server disks while testing, which is not possible because of this.

innnnnteresting
cc @paddyforan

Scratch that, it does not seem to work at all. I tried running it directly on the server instead of in the docker image. Like this:
./nsq_to_file -lookupd-http-address=<IP_ADDRESS>:4161 -channel=dummy -filename-format=null -output-dir=/dev

Which results in:
2015/03/20 14:32:40 LOOKUPD: querying http://<IP_ADDRESS>:4161/topics
2015/03/20 14:32:40 INF    1 [hello/dummy] querying nsqlookupd http://<IP_ADDRESS>:4161/lookup?topic=hello
2015/03/20 14:32:40 INF    1 [hello/dummy] (<IP_ADDRESS>:4150) connecting to nsqd
2015/03/20 14:32:40 INFO: opening /dev/null
2015/03/20 14:32:40 syncing 1 records to disk
2015/03/20 14:32:40 ERROR: failed syncing messages - fsync: invalid argument

Which is the same error message I got when trying to run this in the docker image.

@Bondza you probably want to use nsq_tail which will be more effective to just drop messages.

this probably has to do with the way nsq_to_file is opening the file...

Yes, I ended up using nsq_tail instead. It is not quite as convenient though.
Because I need to run one instance per topic I would like to drop messages from, whereas I could just use the -topic-pattern argument for nsq_to_file to drop messages from all topics.
By the way, the docs for nsq_to_file is missing information about the topic pattern argument.

I didn't try docker. it works on OS X btw.
➜  nsq git:(master) ✗ ./nsq_to_file --lookupd-http-address=<IP_ADDRESS>:4161 -channel=test -filename-format=null -output-dir=/dev
2015/05/04 21:33:54 LOOKUPD: querying http://<IP_ADDRESS>:4161/topics
2015/05/04 21:33:54 INF    1 [message_topi/test] querying nsqlookupd http://<IP_ADDRESS>:4161/lookup?topic=message_topi
2015/05/04 21:33:54 INF    1 [message_topi/test] (<IP_ADDRESS>:4150) connecting to nsqd
2015/05/04 21:33:54 INF    2 [test/test] querying nsqlookupd http://<IP_ADDRESS>:4161/lookup?topic=test
2015/05/04 21:33:54 INF    2 [test/test] (<IP_ADDRESS>:4150) connecting to nsqd
2015/05/04 21:33:54 INFO: opening /dev/null
2015/05/04 21:33:54 syncing 1 records to disk

I don't feel strongly about this one - it could come down to filesystem, etc.
Semantically, I'm not sure we should make it easier to route topics to /dev/null - it seems like ephemeral channels/topics should be sufficient for the original use case here.
Now, whether or not the docker image should be rooted the way it is could be a useful conversation.  I'm going to update the title (again) to reflect that.

I looked through this (rather late, I apologise) and there's an easy fix. If we add the binaries one at a time, instead of the entire directory, it behaves the exact same way, but doesn't overwrite the entire filesystem (which is baaad). This lets people use /bin/sh, /tmp, etc. while maintaining backwards compatibility. I can work up a tiny Dockerfile-only patch for it at some point, if this is a thing we want to support.

That's an acceptable trade off (having to manually add new binaries).  Let's do it!
Thanks for looking into this!

At the same time, we can symlink the binaries to /bin, so you can just docker run nsqio/nsq nsqd and it will be correctly found. Any opinion here or there on whether that's desired behaviour? It's just extra lines in the Dockerfile, so I don't see the harm, but I won't bloat the PR if you'd rather just get this fix in.

That makes me think... could you just
ADD dist/docker/bin/* /

or
ADD dist/docker/bin/ /nsq_bin/
RUN cd / && ln -s nsq_bin/* .

Couldn't you put the binaries in /bin and instead symlink them to /?
That way you could
ADD dist/docker/bin/* /bin
RUN ln -s /bin/nsq_pubsub /
...
RUN ln -s /bin/to_nsq /

You would have to symlink each binary but any new binaries would automatically be added to /bin and possible to use like docker run nsqio/nsq any_new_binary

@Bondza what about @ploxiln's suggestion, seems like the most future proof?

I'd just like to add that, if you use my second suggestion, you can additionally put links in bin, of course:
ADD dist/docker/bin/ /nsq_bin/
RUN cd /    && ln -s /nsq_bin/* . \
 && cd /bin && ln -s /nsq_bin/* .

And also, for docker, fewer directives :arrow_right: fewer layers :arrow_right: faster push/pull/run

Of course that works, I suggested it because I think it's a bit odd to place binaries in the root directory and not in /bin.
Anyways, thanks for fixing this!

RFR @jehiah
/cc @ploxiln


Remove seemingly unnecessary Repeat patterns

This should make the tests in PR #185 much faster.
This was the pattern before my change:
r"""Usage:
  prog a b [-p <param>]...
  prog a c [-p <type> <param>]...
"""
$ program a c -p bool 1 -p bool 0 -p bool 1
{"-p": 3, "<type>": ["bool", "bool", "bool"], "<param>": ["1", "0", "1"]}

Usages:
  Sequence([PatAtom(Command("a")), PatAtom(Command("b")), Repeat(Optional([PatAtom(Short('p')), PatAtom(Positional("param"))]))])
  Sequence([PatAtom(Command("a")), PatAtom(Command("c")), Repeat(Optional([Repeat(PatAtom(Short('p'))), PatAtom(Positional("type")), PatAtom(Positional("param"))]))])

The Repeat(Optional([Repeat(... causes an explosion in the function states.   states was being called 1,421,237 times, and producing a vector of 236,975 elements.
This is the pattern after:
Usages:
  Sequence([PatAtom(Command("a")), PatAtom(Command("b")), Repeat(Optional([PatAtom(Short('p')), PatAtom(Positional("param"))]))])
  Sequence([PatAtom(Command("a")), PatAtom(Command("c")), Repeat(Optional([PatAtom(Short('p')), PatAtom(Positional("type")), PatAtom(Positional("param"))]))])

states is being called 7,843 times, and producing a vector of 2,296 elements.
I'm not sure why the removed code was ever written.  The concept of "has_repeat" means that the short can possibly repeat under some context somewhere, which seems to have a completely separate meaning from the Repeat(...) pattern.  Furthermore, this extra Repeat(...) pattern only affects the second sequence and not the first.  That's because after the first sequence is processed, Short('p') is flagged as something that repeats, which affects only the second sequence.

Hmm, that code was added in a4ee9b to support this feature: https://github.com/docopt/docopt/issues/275
I find it curious that the tests still pass, but I can't yet explain why I added that code in particular. I'll take a closer look when I get a chance.
Thank you for looking into this. :-)


Fixing windows service management

Hubble service management on windows is not optimal.
We have noticed if Hubble process is terminated or killed, Hubble service still shows as running.

Tested on windows server 2016 and 2019. Will also test on windows server 2012.

Tested on windows server 2012 as well.


Update Element Support

PodServe.fm has added support for the locked tag. Not only in our feeds, but block imports if feeds are locked. The funding tag is also enabled at PodServe.fm

Excellent. I’ll update the apps page to reflect on podcastindex.org.

Don’t forget to add yourself to the contributors list as well. Support == contribution.


Feature/1220/deps help

For issue #1220
Add deps info to 'dockstore --help'
Make client-version optional by setting a default version

Coverage increased (+1.1%) to 65.169% when pulling ce7fb62c1c567d2088b1c24e76139bae2c718eae on feature/1220/depsHelp into d43db73e8e0145b19055f310cbed6f0e87ce01ce on develop.


Markers hijacking map zoom even when child views have pointer events none set on them

I have a MapView with custom map markers on them. When initiating a two finger zoom gesture, if one or both of the fingers happens to rest on a marker then the zoom doesn't work. Single finger drag doesn't work either.
The UIView inside the marker has pointerEvents to none on it so it's not those views intercepting it.

Attempted solution

Setting pointerEvents to none on the MapView.Marker itself. This fixed the problem, however, the Marker's onPress no longer works. onSelect does work but has a large delay which makes the UI feel unresponsive.

Any ideas? Using the default iOS markers (ie MapView.Marker's with no subviews) doesn't create the same issue.

The same problem - even with built-in markers with custom images.

Us as well. We've been struggling with it for a while- still not sure how to avoid it.

One way I've found to get around it is to set the MapView.Marker's themselves to have pointerEvents="none" and then respond to map presses (rather than marker presses). Then detect the latitude and longitude of where the user clicked, loop through your markers and try and find if any markers were within a hitbox area.
For that, you'll need to convert latitude and longitude to pixels, which requires you to divide the map's current width by the longitude delta, and height by the latitude delta. Also, know that because of the nature of latitude and longitude, simply dividing won't be accurate for the more zoomed out views because the longitude per pixel changes depending on how far away from the equator you are.
This is some excerpts code from my project that may put you on the right track. It's highly simplified and not particularly optimised however if you have under 1000 markers on the map, and you're zoomed in far enough, it should be fine.
<MapView
       ...
        onPress={(e) => this.onMapPress(e.nativeEvent.coordinate)}
      >

onMapPress(event) {
    if (!event) {
      return;
    }

    const { latitude, longitude } = event;
    const { width, height } = this.state;
    const latPerPixel = (this.state.latitudeDelta) / height;
    const LngPerPixel = (this.state.longitudeDelta) / width;

    const markerWidth = 50;
    const markerHeight = 50;

    const closestMarker = this.state.clusters.find(({ center }) => {
      const { lat, lng } = center;

      const minLng = lng - LngPerPixel * (markerWidth / 2);
      const maxLng = lng + LngPerPixel * (markerWidth / 2);
      const minLat = lat - latPerPixel * (markerHeight / 2);
      const maxLat = lat + latPerPixel * (markerHeight / 2);

      return latitude > minLat && latitude < maxLat && longitude > minLng && longitude < maxLng;
    });

    // Can also set null as the closet marker.
    this.setState({ activeMarker: closestMarker });
  }

Thanks for the code snipped @martsie It's an interesting workaround and I'll try it out as this was driving me nuts for some time. If replacing the apple map with google maps on Ios wasn't causing 100% cpu usage with custom markers then I would have long ditched apple maps in favor of google.
This is issue is also a duplicate of this https://github.com/airbnb/react-native-maps/issues/1539

Duplicate of #1539


Remove .DS_Store file from helmet example

https://github.com/zeit/next.js/pull/1264#issuecomment-282267033

👍 wow that was fast

Trying to stay on top of new PRs 😄 Thanks for the compliment 🤗


The page is opened 2 times, if you open it from recieve push handler

Hello.
My code to handle push notifications:
 this.push.rx.notification()
            .subscribe((msg) => {
                this.navCtrl.push(this.ordesPage);
            });
    }

I send one push notification, but this code open TWO ordesPage.
Why? How can i prevent this?
ps. this only occurs when ordesPage has ion-tabs

Sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md
Actually this looks like a question better asked on the Ionic forums.


Authorized JavaScript Domains Ignored in Stream Settings

The Authorized JavaScript Domains setting in the stream configuration is not working as expected. Events from unauthorized domains are still being tracked, even though they are not listed in the Authorized JavaScript Domains field.
Steps to Reproduce:
1.	Create a stream.
2.	Create a destination.
3.	Create a connection between the stream and the destination.
4.	Add 'mysite.com' to the Authorized JavaScript Domains field.
5.	Add the stream snippet to the <head> section of test.com.
6.	Observe that events from test.com are still being tracked, despite it not being listed in the Authorized JavaScript Domains.

Expected Behavior:
Events should only be tracked from domains listed in the Authorized JavaScript Domains field. Events from test.com should not be tracked in this scenario.
Actual Behavior:
Events from test.com are being tracked, indicating that the Authorized JavaScript Domains setup is being ignored.
System configuration and versions

Artifacts (logs, etc)

We are discontinued this feature, we just forgot to remove it from the UI.
If you want to filter incoming requests based on Origin header, you should do that with Jitsu Functions. See headers field of FunctionContext


Service errors handling

Added several checks in app to handle fault service errors.

Just a small change in the error message but other than that, good to go.


build.py windows support

Would be nice if it would kinda work, even though I don't know how to make commands output ansi colors on windows

fixed in #31


Windows: factor out bridgeConfig from server+config

Signed-off-by: John Howard<EMAIL_ADDRESS>@swernli
This PR is part of the proposal described in issue 10662 to port the docker daemon to Windows. This removes the dependency of "bridge" from the Windows daemon from within api\server and daemon\config. Note there is more to do here to completely remove the dependency. This also brings back Exec and Graph options to common. @tiborvass was right :) While technically we don't have a use for them at present on Windows, the refactoring is significantly eased by leaving them in, and allowing for future usage of course. It also makes getting to the Windows daemon compiling (although non-functional) quicker.

Reworked and rebased after libnetwork integration

Rebased again....

LGTM

LGTM


🐛 [Fix] image size order inconsistencies

Fixes the expected order of image_size to be [width, height] in bounding_box_utils.py/generate_anchors function as in the rest of the repository.
Additionally fixes the same issue in the create_auto_anchor functions of the Vec2Box and Anc2Box classes, where the order does not matter, but for the sake of consistency.
fixes #117

Found and fixed two additional bugs:
1, In yolo/tools/solver.py in ValidateModel the PostProcessor received the image size in the wrong order [h, w] instead of [w, h]
2, A spelling mistake, in which in yolo/utils/bounding_box_utils.py inside Anc2Box the update function updated the wrong variable: "self.anchor_grid" instead of "self.anchor_grids" as defined in Anc2Box.init().


Feature/telemetry docs

Fixed some issues with the devupdate that caused errors when not connected to the internet or when working on a separate branch.
Added support for overview docs of all components in a deployment. Requires passing the fprime root location for loading the imported files.

@nathancheek: does this adjustment have interplay with the problems you experienced with Issue #3?

I noticed that the event parsing ignores the fact that events can have multiple arg fields contained in the args keyword. I can fix this but I'm not sure how this would best fit into the table structure. Would each arg get its own line?

@AaronMcDaniel : Some of the existing table refactoring is fairly extensive, did you have comments in the component input files you used for testing?

I mostly just broke out the parsing portions into methods. I was expecting to leverage this, but ended up just making a general parse_components_file method. I could add the parsing methods back into that method to make it appear more similar to the original, but I did test the command with comments. I've tested it with all types including comments individually (not together) though. The only issue I saw was the one mentioned above

I noticed that the event parsing ignores the fact that events can have multiple arg fields contained in the args keyword. I can fix this but I'm not sure how this would best fit into the table structure. Would each arg get its own line?

So, there is precedent for how this is set up in the upstream docs, but they nixed the Component.md files from the repo in version 1.5.  They used a separate line for each arg that was attached to a command/event/enum in the table.
Because this is an effect of using markdown tables, I would like to convert this output to a restructured text file.  Restructured text has a much richer markup, and is better designed for supporting multiple output types.  I like it better because it is less limited to html.
In any case, an RST table could be generated where the args go into sub-rows, which is not supported by markdown at all (at least, not on GitHub).  Thus, I didn't bother to implement that part of the generator code.


jira: update endpoint URL

We have a new jira server. Update the go-jira config and links.
Comments
To make go-jira work again, you will need to get a new API token and update your go-jira config.

Oooh yay! I've got a couple of helpful things to add, for people who don't use an explicit keyring...

Completely optional PR: https://github.com/input-output-hk/cardano-wallet/pull/2871

Thanks @sevanspowell. You can just push to my PR branches, I don't mind.

bors r+


School Library: decorate a class

In this [PR] I have:

Create Nameable class.
Add a method called correct_name that will raise a NotImplementedError to the Nameable class.
Create Decorator class inherits from Nameable.
Add a method correct_name to the Decorator class that returns the correct_name method of the @nameable.
Create CapitalizeDecorator class inherits from Decorator.
Implement a method correct_name that capitalizes the output of @nameable.correct_name
Create TrimmerDecorator class inherits from Decorator.
Implement a method correct_name that trims the output of @nameable.correct_name (case chars more than 10).

Thank @Whoistolu for the code review.


Receive a connection (or a pool) in the connector

At least 2 projects would rather pass their own connections than have Procrastinate create it for them.

Don't touch the connection if your receive it (no register, etc)
Don't close it at the end

This was done as part of #148


Azure CLI 2021-02 beta release

Docs Build status updates of commit a023344:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/TOC.yml
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-beta.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-windows.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/release-notes-azure-cli.md

Line 3142, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 3298, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelisted' is sensitive and should not be used in content or code. Usage: '* Print a friendly message when the subscription is not whitelisted to use Azure Red Hat OpenShift'
Line 3528, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 4721, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4729, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4895, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4903, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4919, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 4927, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 5612, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 6316, Column 1: [Suggestion-sensitive-language-bl] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 02f8c66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/TOC.yml
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-beta.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-windows.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/release-notes-azure-cli.md

Line 3142, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 3298, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelisted' is sensitive and should not be used in content or code. Usage: '* Print a friendly message when the subscription is not whitelisted to use Azure Red Hat OpenShift'
Line 3528, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 4721, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4729, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4895, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4903, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4919, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 4927, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 5612, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 6316, Column 1: [Suggestion-sensitive-language-bl] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit eac982b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/TOC.yml
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-beta.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-windows.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/release-notes-azure-cli.md

Line 3142, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 3298, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelisted' is sensitive and should not be used in content or code. Usage: '* Print a friendly message when the subscription is not whitelisted to use Azure Red Hat OpenShift'
Line 3528, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 4721, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4729, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4895, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4903, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4919, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 4927, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 5612, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 6316, Column 1: [Suggestion-sensitive-language-bl] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2f96e68:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:bulb:Suggestion
View
Details

docs-ref-conceptual/TOC.yml
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-beta.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli-windows.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/release-notes-azure-cli.md

Line 3155, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 3311, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelisted' is sensitive and should not be used in content or code. Usage: '* Print a friendly message when the subscription is not whitelisted to use Azure Red Hat OpenShift'
Line 3541, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 4734, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4742, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
Line 4908, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4916, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
Line 4932, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 4940, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
Line 5625, Column 1: [Suggestion-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
Line 6329, Column 1: [Suggestion-sensitive-language-bl] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@jiasli , This PR is ready to go.  Please provide date to merge.


[WIP] Conda

@durack1 no need to do anything about it yet

@doutriaux1 no problem - looking forward to testing this out!


Move configuration to .ini files

Instead of .php files as .ini files are more universal and easier to maintain.
Context: I've forked your project and want to modify how config is fetched - instead of getting it from local filesystem, I'd like to add support for Amazon Web Services Beanstalk & S3. In order to do that, I need to pass location of file and SECRET/ACCESS KEY by parameters to the application, download the file by using those parameters and finally parse the file.
This solution is fully compatible with cloud orientation and imo should be incorporated into YOURLS v2 as the future is already here ;) Of course, this type of fetching configuration shouldn't be default at all.

The idea is interesting but will be left for plugin territory. PHP files are indeed not entirely practical to edit, but

they contain critical info and they're not readable via the browser (example) and we cannot reasonably assume everyone will configure their server to make config.ini unreadable
at some point we'll have an installer and no one will ever need to edit config files any more

This said, this is a very cool idea for a plugin. If you try this path and find hooks that are missing to do so, feel free to propose new ones.

As I've checked, I don't think plugin will handle this situation as config file is strictly fetched from disk. In my application I did dirty workaround in loader where I check server attributes and if they exist, I loaded file from S3 and place it on disk.
Anyway, I'd work on that and do the hooks + probably change the configuration loading behaviour, but as you say - there is no sense as installer will come in place of file.
As for installer, it'd be good to keep in mind cloud users as they get more and more popular. If you dump configuration from GUI installer into file, unfortunately it won't work. One way or another, you'd have to either allow plugins to provide configuration or add support for S3.
I'm willing to help in this matter, but I don't want to hop in in the middle of the works :)

Indeed, that won't be a plugin, strictly speaking. But it's only a matter of writing your own config.php with functions that load stuff from the cloud instead of reading settings inline


Detective Pikachu

Game Name (and version if necessary)
Detective Pikachu
Hardware Specs (If necessary)
CPU: 13th Gen Intel(R) Core(TM) i7-13700F   2.10 GHz
GPU: NVIDIA RTX 3060
Operating System
Windows 11
Game State
Won't start.
Error:
[FATAL] Failed to find paddr
Screenshots
No response
Additional information
No response

Duplicate of #24


Content on Home and About pages isn't loading

After navigating between the home and about pages, I need to hard refresh in order to see the proper content on the page and in Tina.
See video: https://www.loom.com/share/561b1e2621464fff97e744bd23130848

This is a duplicate issue (see here), but I'll leave this open incase my loom provides any additional insights that might be needed.

Closing this so we're not confused by the duplicate issue and related PR


Features for designers

Follow-up for #68 to add more design-related features vs the list of JavaScript features we already have …

[ ] CSS Shapes (1040714)
[ ] Web Animations JavaScript API (875219)
[ ] CSS Custom Properties (CSS Variables)
[ ] <picture> Element
[ ] <img srcset>
[ ] CSS Grid Layout
[ ] Animated PNG
[ ] CSS Scroll Snap Points

r? @jensimmons

[ ] <img srcset>
Jet Villegas will likely have more.

:heavy_check_mark: added

You beat me to the publishing of a ticket! Here's the list-in-progress that I started yesterday. I can go through it more carefully next week, once I get off the airplanes.
CSS Layout Properties That Are Ready to be Implemented

[ ] Grid
[ ] Flexbox
[ ] Shapes (level 1)
[ ] Multicolumn Layout (finishing full implementation)
[ ] Viewport Units
[ ]

CSS Layout Properties That Will Come Later (specs in flux)

[ ] Regions
[ ] Exclusions
[ ] Shapes Level 2
[ ]

Other CSS properties

[ ] Clip paths
[ ] Masks
[ ] Filters
[ ] Snap Points

Typography

[ ] Initial Letter
[ ]

HTML

[ ] Srcset attribute
[ ] Picture element
[ ]

@jensimmons may I ask you to add some of them? We just created contribution guidelines and love feedback on how straightforward the flow is and how to improve it.


Workflow milestone.yaml: Milestone's auto-close doesn't work

Describe the bug
Not working milestone's auto-close in workflow milestone.yaml
Error message:
# Get milstones
  milestones=$(curl -q -L -H "Accept: application/vnd.github+json" -H "Authorization: ***" -H "X-GitHub-Api-Version: 2022-11-28" https://api.github.com/repos/obervinov/users-package/milestones)
  # Get the milestone for the current release
  current_version=$(echo refs/heads/main | sed 's/refs\/heads\/.*\///')
  printf "Current version: %s\n" "$current_version"
  milestone=$(echo "$milestones" | jq -r ".[] | select(.title == \"$current_version\") | .number")
  printf "Found milestone with number: %s\n" "$milestone"
  # Check milestone percentage of completion
  milestone_completion=$(echo "$milestones" | jq -r ".[] | select(.number == \"$milestone\") | .closed_issues / .open_issues")
  printf "Milestone completion: %s\n" "$milestone_completion"
  if [ $milestone_completion -lt 1 ]; then
    echo "Milestone is not complete"
    exit 1
  fi
  # Close the milestone
  curl -L -H "Accept: application/vnd.github+json" -H "Authorization: ***" -H "X-GitHub-Api-Version: 2022-11-28" -X PATCH -d "{\"state\": \"closed\"}" https://api.github.com/repos/obervinov/users-package/milestones/$milestone
  shell: /usr/bin/bash -e {0}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3350  100  3350    0     0  13769      0 --:--:-- --:--:-- --:--:-- 13786
Current version: refs/heads/main
Found milestone with number:
Milestone completion:
/home/runner/work/_temp/9aaf732b-90ba-472c-b59c-948d60fa91e0.sh: line 11: [: -lt: unary operator expected
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   103  100    84  100    19    419     94 --:--:-- --:--:-- --:--:--   515
{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest"
}

Additional context
Information about where the bug is happening:

Repository: https://github.com/obervinov/users-package
Link to job run: https://github.com/obervinov/users-package/actions/runs/9276259598/job/25522965105
Template version: v1.2.2.

Possible correction
None
Screenshots

Check list after fixing the bug

[ ] Milestone successful close after PR close

Automatic closing of milestones is no longer relevant, I may come back to this task in the future


GraphicBuffer unflatten test does not detect patched Kitkat

Running VTS on KTU84P 4.4.4_r1 shows that unflatten is still unpatched even though the patch has been applied (as well as the CVE-2015-1528 patch).
Assuming I did not miss anything....
According to VTS code, the test seems to rely on the unflatten() return value, and expects patched code to return BAD_VALUE, but the test uses values that do not trigger the code that returns BAD_VALUE.
Even more so, the values given (r1[6] = 0x1000, r1[7] = 0xFF5, r2[0] = 0x20) result in (size < sizeNeeded) which returns NO_MEMORY, in both patched and unpatched code.
It almost seems as if the values of 0x1000 and 0xFF5 have been selected to test for the patch section that handles native_handle_create's failure (by triggering the CVE-2015-1528 patch), but that code also returns NO_MEMORY, which would still give the indication that the code is unpatched.
IMHO, r1[6], r1[7] and r2[0] values should be changed to (UINT_MAX / sizeof(int)) which should trigger the patched BAD_VALUE return code.
The other option would be to set r2[0] to be larger than 0x1000, but then the patched code would return NO_MEMORY, and unpached code would crash.
HTH.

This issue was reported in https://github.com/nowsecure/android-vts/issues/21 .  It was supposedly fixed there. Can you show which device you are using and possibly your code with the patch applied?

Thanks for your reply.
The VTS I've used is the one published on google play store (v.12). Maybe it is not up to date?
Anyhow, the VTS test code I've commented above was from GitHub and is the latest AFAICT.
My patched unflatten code:
status_t GraphicBuffer::unflatten(
void const*& buffer, size_t& size, int const*& fds, size_t& count) {
if (size < 8*sizeof(int)) return NO_MEMORY;
int const* buf = static_cast<int const*>(buffer);
if (buf[0] != 'GBFR') return BAD_TYPE;

const size_t numFds  = buf[6];
const size_t numInts = buf[7];

const size_t maxNumber = UINT_MAX / sizeof(int);
if (numFds >= maxNumber || numInts >= (maxNumber - 8)) {
    width = height = stride = format = usage = 0;
    handle = NULL;
    ALOGE("unflatten: numFds or numInts is too large: %d, %d",
            numFds, numInts);
    return BAD_VALUE;
}

const size_t sizeNeeded = (8 + numInts) * sizeof(int);
if (size < sizeNeeded) return NO_MEMORY;

size_t fdCountNeeded = numFds;
if (count < fdCountNeeded) return NO_MEMORY;

if (handle) {
    // free previous handle if any
    free_handle();
}

if (numFds || numInts) {
    width  = buf[1];
    height = buf[2];
    stride = buf[3];
    format = buf[4];
    usage  = buf[5];
    native_handle* h = native_handle_create(numFds, numInts);
    if (!h) {
        width = height = stride = format = usage = 0;
        handle = NULL;
        ALOGE("unflatten: native_handle_create failed");
        return NO_MEMORY;
    }
    memcpy(h->data,          fds,     numFds*sizeof(int));
    memcpy(h->data + numFds, &buf[8], numInts*sizeof(int));
    handle = h;
} else {
    width = height = stride = format = usage = 0;
    handle = NULL;
}

mOwner = ownHandle;

if (handle != 0) {
    status_t err = mBufferMapper.registerBuffer(handle);
    if (err != NO_ERROR) {
        ALOGE("unflatten: registerBuffer failed: %s (%d)",
                strerror(-err), err);
        return err;
    }
}

buffer = reinterpret_cast<void const*>(static_cast<int const*>(buffer) + sizeNeeded);
size -= sizeNeeded;
fds += numFds;
count -= numFds;

return NO_ERROR;

}


Adding Custom query for DB(mariaDB,ES, etc)

Hi.
Can I Adding Custom query for other DB.
Currently, I know that only support queries for prometheus and AWS Billing.
I need to add queries for MariaDB.
Is it possible to support other queries?

Today we only support hive for a database backend. Longer term we would like to support other backends for querying and storage, but we're primarily focused on other core reporting features and other integrations for handling upgrades, migrations, etc.
Generally speaking though, adding another DB backend is mostly a matter of the following:

Presto needs to support the backend as a connector
Need to be able to configure it in Presto's configuration files (done via helm templates)
Need to support it as a configuration option in the StorageLocation CRD. That logic is in reporting-operator
Need to support exposing the table using a ReportDataSource. That logic is in reporting-operator.

There's a decent amount of work and design needed for us to accomplish that however. It's not something we plan to support in the short-term, but medium-long term I'd expect more backends to be supported. It will also become easier once we've added the first alternative to hive, as many will likely be similar.

@chancez
Thank you for your feedback.
My question is that operator-metering can support anything other than Prometheus queries.
For example.  MariaDB, ElasticSearch, ETC.
Currently, CRD:ReportDataSource uses CRD:ReportPrometheusQuery.
Is it possible? ,
CRD:ReportDataSource uses CRD:ReportMariaDBQuery.
CRD:ReportDataSource uses CRD:ReportElasticSearchQuery.
This means that operator metering can define a new CRD and query raw_data for every interval time.

No, that isn't possible. It wouldn't work quite that way anyways, as I mentioned, Presto will generally be the component making queries when possible, so ideally we never have to write any queries besides regular SQL queries to Presto.


How to use Chrome headless (V59)?

Chrome 59 has cross-platform headless support. It allows running Chrome in a headless/server environment.
To use via the DevTools remote debugging protocol, start a normal Chrome binary with the --headless command line flag (Linux-only for now):

$ google-chrome --headless --disable-gpu --remote-debugging-port=9222 https://www.google.fr

How can I tell chromedp to send the --headless flag, along with other flags?

Find It. I do
	c, err := cdp.New(ctxt, cdp.WithRunnerOptions(
	   runner.Flag("headless", true),
	   runner.Flag("disable-gpu", true)))
	if err != nil {
		log.Fatal(err)
	}

Can we configure --headless with the chromedb.Pool ?


4x8 block computation in vec_avx.h

@jmvalin , Thank you for sharing your code in Github.
I have a question about 8x4 block computation in vec_avx.h
(My question is based on lpcnet_efficiency branch after reading the paper, NEURAL SPEECH SYNTHESIS ON A SHOESTRING: IMPROVING THE EFFICIENCY OF LPCNET)
https://github.com/xiph/LPCNet/blob/lpcnet_efficiency/src/vec_avx.h#L788
In attached link, vector_ps_to_epi8 function is called and this function converts float type state (_x)  into unsigned char type state (x). And for making signed char to unsigned char, the scalar value 127 is added.
I understand that this operation is for applying _mm256_maddubs_epi16 to vxj and vw.
But, In my opinion, after the operation, there should be some kind of 'compensation' part that needs to subtract the added value, 127. (Because state of GRU is not in range of unsigned char in training step.)
So, for example, I think the following line should be added after the aforementioned operation line.
// Before
tmp = _mm256_maddubs_epi16(vxj, vw);
tmp = _mm256_madd_epi16(tmp, ones);

// After
tmp = _mm256_maddubs_epi16(vxj, vw);
tmp = _mm256_sub_epi16(tmp, _mm256_maddubs_epi16(const_127i, vw));
tmp = _mm256_madd_epi16(tmp, ones);

In summary, I reckon that 127 should be subtracted during the sgemv 8x4 operation to compensate the added value of 127 in vector_ps_to_epi8 and  I wonder if I have missed anything.
In addition, this is far from with what I said above, I wonder why Gaussian Noise added between GRU_A and GRU_B.
gru_out1, _ = rnn(rnn_in)
gru_out1 = GaussianNoise(.005)(gru_out1)
gru_out2, _ = rnn2(Concatenate()([gru_out1, rep(cfeat)]))

Thanks.

Regarding the 127 offset, you're right that there needs to be a computation. That's done offline by changing the bias values we add at the end. See the "bias" vs "subias" values in the model ("su" is for "signed*unsigned multiply). As for the GaussianNoise, it kinda simulates the quantization noise we add to the activation when going from float to int8.

Regarding the 127 offset, you're right that there needs to be a computation. That's done offline by changing the bias values we add at the end. See the "bias" vs "subias" values in the model ("su" is for "signed*unsigned multiply). As for the GaussianNoise, it kinda simulates the quantization noise we add to the activation when going from float to int8.

Thank you for the reply. :-)
Thanks to your comment, I understand the role of "subias" in dump_lpcnet.py & nnet.c script.
Also, I checked that the wav is well synthesized without the line,
tmp = _mm256_sub_epi16(tmp, _mm256_maddubs_epi16(const_127i, vw));
by using su_bias.


Date time range picker

please approve me

Codecov Report

Merging #11 (5aa45cb) into master (123b0ce) will decrease coverage by 9.11%.
The diff coverage is 1.44%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
- Coverage   54.43%   45.32%   -9.12%
==========================================
  Files          12       13       +1
  Lines         338      406      +68
==========================================
  Hits          184      184
- Misses        154      222      +68

Impacted Files
Coverage Δ

lib/src/date_range_picker_field_bloc_builder.dart
0.00% <0.00%> (ø)

lib/src/text_field_bloc_builder.dart
2.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


mysql_database host  is localhost host only ?

I wrote such recipe
rds_connection_info ={:host => "some rds ",....}
mysql_database "aws" do
connection rds_connection_info
action: create
end
but   mysqlclient try to access   user@localhost and error
mysql_database host is localhost only ?
mysql_database could not setup  remote mysql server ?

I made a type miss


Crash render Icon Xaero ResourcePack 1.19.2

crash-2024-08-24_19.43.34-client.txt

Need the full latest.log in .minecraft/logs from when it crashed

just looking at it though i'm pretty sure the cause is not related to XaeroPlus
what you should do:

remove XaeroPlus
reproduce the same crash again
create an issue and post your new crash report to https://legacy.curseforge.com/minecraft/mc-mods/xaeros-minimap/issues

looks like you or another person created an issue on xaero's minimap: https://legacy.curseforge.com/minecraft/mc-mods/xaeros-minimap/issues/1488
and looks like xaero confirmed a fix is coming soon
so im just gonna close this here on my github


⚠ SkipTheCommericals has degraded performance

In bc2fe8b, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 11093 ms

Resolved: SkipTheCommericals performance has improved in edb5143.


chore: turn prettier into its own package

Motivation
Fixes #344.
Change Summary

From eslint-config-custom, extract prettier configs into prettier-config-custom package
Add "prettier-config-custom": "*" to all packages/js, packages/protobufs, packages/utils, and apps/hubble (inside their devDependencies)
Add "prettier --write" to lint-staged in root package.json
Diffs are somewhat large because prettier is applied to packages/protobufs (not sure why protobufs aren't prettified before...)

If we look at the packages/protobufs diffs, it seems to do the stuff defined in .prettierrc.cjs: turn string quote into single quotes, wrap lines longer than 120 chars, etc.
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[x] The title of this PR adheres to the conventional commits standard
[x] The PR has been tagged with the appropriate change type label(s) (i.e. documentation, feature, bugfix, or chore)
[ ] Changes to the protocol specification have been merged

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

thanks @vinliao!
sorry i missed reviewing this and its now a bit out of date, might need a rebase

Should be good now, @varunsrin.

ty!


[FEAT] Orange Pi 5 Plus Support

Objective
Validate support for Orange Pi 5 Plus
Initial Implementation Requirements

Evaluate compatibility with Orange Pi 5B build
Complete any OPi5 Plus-specific build/configuration
Document build options for the new platform as necessary

Other Considerations

How can changes be included in a "universal" image
Can the build be optimized to combine image layers

Initial support with #79
Automation fix in #86

Image was never tested against Orange Pi 5 Plus, only Orange Pi 5B


Whorvath2 patch 1

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:

[x]  I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ]  For content changes, I have completed the self-review checklist.

Xx

อย่าลืม ดิสโก้เทร์คน่ารอบ แห่นางแมวไอเจ๊ปูด้วนนะครับ 5555+ เค้าขอมาครับ
น่าจะไม่ทนอ่อนจริง


AMBARI-25854: Adapt Ambari 2.7.5 from python2 to python3.9

What changes were proposed in this pull request?
This PR show the necessary adaption for Ambari 2.7.5 to adapt python3.9.
related JIRA Issue: https://issues.apache.org/jira/browse/AMBARI-25854
How was this patch tested?
unit tests,
manual tests

I am trying to apply this patch on branch-2.7, but https://github.com/wuzhuoming/ambari-python3/blame/AMBARI-25854-release-2.7.5/ambari-agent/src/main/python/ambari_agent/listeners/ConfigurationEventListener.py#L53 from line 53 to 56 these changes are not present in branch-2.7, seems you haven't applied the changes on top of branch-2.7.
Can you tell me the branch on top of which you have done your changes?

I am trying to apply this patch on branch-2.7, but https://github.com/wuzhuoming/ambari-python3/blame/AMBARI-25854-release-2.7.5/ambari-agent/src/main/python/ambari_agent/listeners/ConfigurationEventListener.py#L53 from line 53 to 56 these changes are not present in branch-2.7, seems you haven't applied the changes on top of branch-2.7. Can you tell me the branch on top of which you have done your changes?

Can you tell me the branch on top of which you have done your changes?

Hello, here ambari 2.7.5 source code is downloaded from the official website of ambari. Link: https://archive.apache.org/dist/ambari/ambari-2.7.5/apache-ambari-2.7.5-src.tar.gz

I am trying to apply this patch on branch-2.7, but https://github.com/wuzhuoming/ambari-python3/blame/AMBARI-25854-release-2.7.5/ambari-agent/src/main/python/ambari_agent/listeners/ConfigurationEventListener.py#L53 from line 53 to 56 these changes are not present in branch-2.7, seems you haven't applied the changes on top of branch-2.7. Can you tell me the branch on top of which you have done your changes?

Can you tell me the branch on top of which you have done your changes?

Hello, here ambari 2.7.5 source code is downloaded from the official website of ambari. Link: https://archive.apache.org/dist/ambari/ambari-2.7.5/apache-ambari-2.7.5-src.tar.gz

Please use the latest code from https://github.com/apache/ambari/tree/branch-2.7

I am trying to apply this patch on branch-2.7, but https://github.com/wuzhuoming/ambari-python3/blame/AMBARI-25854-release-2.7.5/ambari-agent/src/main/python/ambari_agent/listeners/ConfigurationEventListener.py#L53 from line 53 to 56 these changes are not present in branch-2.7, seems you haven't applied the changes on top of branch-2.7. Can you tell me the branch on top of which you have done your changes?

Can you tell me the branch on top of which you have done your changes?

Hello, here ambari 2.7.5 source code is downloaded from the official website of ambari. Link: https://archive.apache.org/dist/ambari/ambari-2.7.5/apache-ambari-2.7.5-src.tar.gz

Please use the latest code from https://github.com/apache/ambari/tree/branch-2.7

Working on it! We are comparing the code between branch-2.7 and release-2.7.5 and making some modification to solve the conflit. Thank you for your comment!

Do not delete .../.gitignore this file...

Hi I am getting below error, while creating ambari rpms
07:46:07,345 [ERROR] error /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass: Command failed.
07:46:07,346 [ERROR] Exit code: 1
07:46:07,346 [ERROR] Command: sh
07:46:07,346 [ERROR] Arguments: -c node scripts/build.js
07:46:07,346 [ERROR] Directory: /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass
07:46:07,346 [ERROR] Output:
07:46:07,346 [ERROR] Building: /workspace/ambari/contrib/views/files/src/main/resources/ui/node/node /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
07:46:07,347 [ERROR] gyp info it worked if it ends with ok
07:46:07,347 [ERROR] gyp verb cli [ '/workspace/ambari/contrib/views/files/src/main/resources/ui/node/node',
07:46:07,347 [ERROR] gyp verb cli   '/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js',
07:46:07,347 [ERROR] gyp verb cli   'rebuild',
07:46:07,347 [ERROR] gyp verb cli   '--verbose',
07:46:07,347 [ERROR] gyp verb cli   '--libsass_ext=',
07:46:07,347 [ERROR] gyp verb cli   '--libsass_cflags=',
07:46:07,347 [ERROR] gyp verb cli   '--libsass_ldflags=',
07:46:07,347 [ERROR] gyp verb cli   '--libsass_library=' ]
07:46:07,347 [ERROR] gyp info using<EMAIL_ADDRESS>07:46:07,347 [ERROR] gyp info using<EMAIL_ADDRESS>| linux | x64
07:46:07,347 [ERROR] gyp verb command rebuild []
07:46:07,347 [ERROR] gyp verb command clean []
07:46:07,347 [ERROR] gyp verb clean removing "build" directory
07:46:07,347 [ERROR] gyp verb command configure []
07:46:07,347 [ERROR] gyp verb check python checking for Python executable "python2" in the PATH
07:46:07,347 [ERROR] gyp verb which failed Error: not found: python2
07:46:07,347 [ERROR] gyp verb which failed     at getNotFoundError (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:13:12)
07:46:07,347 [ERROR] gyp verb which failed     at F (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:68:19)
07:46:07,347 [ERROR] gyp verb which failed     at E (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:80:29)
07:46:07,347 [ERROR] gyp verb which failed     at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:89:16
07:46:07,347 [ERROR] gyp verb which failed     at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/isexe/index.js:42:5
07:46:07,347 [ERROR] gyp verb which failed     at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/isexe/mode.js:8:5
07:46:07,346 [INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
07:46:07,347 [ERROR] gyp verb which failed     at FSReqWrap.oncomplete (fs.js:82:15)
07:46:07,347 [ERROR] gyp verb which failed  python2 { [Error: not found: python2] code: 'ENOENT' }
07:46:07,347 [ERROR] gyp verb check python checking for Python executable "python" in the PATH
07:46:07,347 [ERROR] gyp verb which succeeded python /usr/bin/python
07:46:07,347 [ERROR] gyp verb check python version /usr/bin/python -c "import platform; print(platform.python_version());" returned: "3.9.6\n"
07:46:07,347 [ERROR] gyp ERR! configure error
07:46:07,347 [ERROR] gyp ERR! stack Error: Python executable "/usr/bin/python" is v3.9.6, which is not supported by gyp.
07:46:07,347 [ERROR] gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
07:46:07,347 [ERROR] gyp ERR! stack     at Object.failPythonVersion (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/lib/configure.js:491:19)
07:46:07,347 [ERROR] gyp ERR! stack     at Object. (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/lib/configure.js:473:14)
07:46:07,347 [ERROR] gyp ERR! stack     at ChildProcess.exithandler (child_process.js:204:7)
07:46:07,347 [ERROR] gyp ERR! stack     at emitTwo (events.js:87:13)
07:46:07,347 [ERROR] gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
07:46:07,347 [ERROR] gyp ERR! stack     at maybeClose (internal/child_process.js:829:16)
07:46:07,347 [ERROR] gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
07:46:07,347 [ERROR] gyp ERR! System Linux 3.10.0-1160.88.1.el7.x86_64
07:46:07,347 [ERROR] gyp ERR! command "/workspace/ambari/contrib/views/files/src/main/resources/ui/node/node" "/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
07:46:07,347 [ERROR] gyp ERR! cwd /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass
07:46:07,348 [ERROR] gyp ERR! node -v v4.5.0
07:46:07,348 [ERROR] gyp ERR! node-gyp -v v3.6.0
07:46:07,348 [ERROR] gyp ERR! not ok

Hi I am getting below error, while creating ambari rpms
07:46:07,345 [ERROR] error /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass: Command failed. 07:46:07,346 [ERROR] Exit code: 1 07:46:07,346 [ERROR] Command: sh 07:46:07,346 [ERROR] Arguments: -c node scripts/build.js 07:46:07,346 [ERROR] Directory: /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass 07:46:07,346 [ERROR] Output: 07:46:07,346 [ERROR] Building: /workspace/ambari/contrib/views/files/src/main/resources/ui/node/node /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= 07:46:07,347 [ERROR] gyp info it worked if it ends with ok 07:46:07,347 [ERROR] gyp verb cli [ '/workspace/ambari/contrib/views/files/src/main/resources/ui/node/node', 07:46:07,347 [ERROR] gyp verb cli '/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js', 07:46:07,347 [ERROR] gyp verb cli 'rebuild', 07:46:07,347 [ERROR] gyp verb cli '--verbose', 07:46:07,347 [ERROR] gyp verb cli '--libsass_ext=', 07:46:07,347 [ERROR] gyp verb cli '--libsass_cflags=', 07:46:07,347 [ERROR] gyp verb cli '--libsass_ldflags=', 07:46:07,347 [ERROR] gyp verb cli '--libsass_library=' ] 07:46:07,347 [ERROR] gyp info using<EMAIL_ADDRESS>07:46:07,347 [ERROR] gyp info using<EMAIL_ADDRESS>| linux | x64 07:46:07,347 [ERROR] gyp verb command rebuild [] 07:46:07,347 [ERROR] gyp verb command clean [] 07:46:07,347 [ERROR] gyp verb clean removing "build" directory 07:46:07,347 [ERROR] gyp verb command configure [] 07:46:07,347 [ERROR] gyp verb check python checking for Python executable "python2" in the PATH 07:46:07,347 [ERROR] gyp verb which failed Error: not found: python2 07:46:07,347 [ERROR] gyp verb which failed at getNotFoundError (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:13:12) 07:46:07,347 [ERROR] gyp verb which failed at F (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:68:19) 07:46:07,347 [ERROR] gyp verb which failed at E (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:80:29) 07:46:07,347 [ERROR] gyp verb which failed at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/which/which.js:89:16 07:46:07,347 [ERROR] gyp verb which failed at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/isexe/index.js:42:5 07:46:07,347 [ERROR] gyp verb which failed at /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/isexe/mode.js:8:5 07:46:07,346 [INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. 07:46:07,347 [ERROR] gyp verb which failed at FSReqWrap.oncomplete (fs.js:82:15) 07:46:07,347 [ERROR] gyp verb which failed python2 { [Error: not found: python2] code: 'ENOENT' } 07:46:07,347 [ERROR] gyp verb check python checking for Python executable "python" in the PATH 07:46:07,347 [ERROR] gyp verb which succeeded python /usr/bin/python 07:46:07,347 [ERROR] gyp verb check python version /usr/bin/python -c "import platform; print(platform.python_version());" returned: "3.9.6\n" 07:46:07,347 [ERROR] gyp ERR! configure error 07:46:07,347 [ERROR] gyp ERR! stack Error: Python executable "/usr/bin/python" is v3.9.6, which is not supported by gyp. 07:46:07,347 [ERROR] gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0. 07:46:07,347 [ERROR] gyp ERR! stack at Object.failPythonVersion (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/lib/configure.js:491:19) 07:46:07,347 [ERROR] gyp ERR! stack at Object. (/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/lib/configure.js:473:14) 07:46:07,347 [ERROR] gyp ERR! stack at ChildProcess.exithandler (child_process.js:204:7) 07:46:07,347 [ERROR] gyp ERR! stack at emitTwo (events.js:87:13) 07:46:07,347 [ERROR] gyp ERR! stack at ChildProcess.emit (events.js:172:7) 07:46:07,347 [ERROR] gyp ERR! stack at maybeClose (internal/child_process.js:829:16) 07:46:07,347 [ERROR] gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 07:46:07,347 [ERROR] gyp ERR! System Linux 3.10.0-1160.88.1.el7.x86_64 07:46:07,347 [ERROR] gyp ERR! command "/workspace/ambari/contrib/views/files/src/main/resources/ui/node/node" "/workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" 07:46:07,347 [ERROR] gyp ERR! cwd /workspace/ambari/contrib/views/files/src/main/resources/ui/node_modules/node-sass 07:46:07,348 [ERROR] gyp ERR! node -v v4.5.0 07:46:07,348 [ERROR] gyp ERR! node-gyp -v v3.6.0 07:46:07,348 [ERROR] gyp ERR! not ok

Sorry, the Ambari adapts to the ARM architecture and Python3 based on the openEuler system. Currently, the code of the x86 architecture branch is not verified or adapted. Our team is considering whether to proceed with this task.

Hi I am getting below error for both ambari-agent as well as ambari-server, while adding zookeeper service
Traceback (most recent call last):
File "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py", line 37, in
BeforeInstallHook().execute()
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 302, in execute
logging_level_str = logging._levelToName[self.logging_level]
KeyError: 'INFO'

What your system environment and architecture is? And how did you add the Zookeeper service?

@himanshumaurya09876

Hi,what your system environment and architecture is? And how did you add the Zookeeper service?

I am using RHEL 8 machines. I have installed ambari-agent, ambari-server and through Ambari UI install wizard I am adding Zookeeper service

@himanshumaurya09876

Hi,what your system environment and architecture is? And how did you add the Zookeeper service?

I am using RHEL 8 machines. I have installed ambari-agent, ambari-server and through Ambari UI install wizard I am adding Zookeeper service

You can create an issue and attach the error log or image. I'm not sure where you went wrong.

Hi I am getting below error while adding service trough Ambari UI Install wizard
File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install     self._pkg_manager.install_package(package_name, self.__create_context())    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 211, in install_package     elif context.is_upgrade or context.use_repos or not self._check_existence(name):    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 278, in _check_existence     return self.yum_check_package_available(name)    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 287, in yum_check_package_available     import yum  # Python Yum API is much faster then other check methods. (even then "import rpm") ModuleNotFoundError: No module named 'yum'
While analyzing this I found that yum module is not available in python3, have you also observed same error?

Hi I am getting below error while adding service trough Ambari UI Install wizard
File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install     self._pkg_manager.install_package(package_name, self.__create_context())    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 211, in install_package     elif context.is_upgrade or context.use_repos or not self._check_existence(name):    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 278, in _check_existence     return self.yum_check_package_available(name)    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 287, in yum_check_package_available     import yum  # Python Yum API is much faster then other check methods. (even then "import rpm") ModuleNotFoundError: No module named 'yum'
While analyzing this I found that yum module is not available in python3, have you also observed same error?

@himanshumaurya09876

Hi I am getting below error while adding service trough Ambari UI Install wizard
File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install     self._pkg_manager.install_package(package_name, self.__create_context())    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 211, in install_package     elif context.is_upgrade or context.use_repos or not self._check_existence(name):    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 278, in _check_existence     return self.yum_check_package_available(name)    File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 287, in yum_check_package_available     import yum  # Python Yum API is much faster then other check methods. (even then "import rpm") ModuleNotFoundError: No module named 'yum'
While analyzing this I found that yum module is not available in python3, have you also observed same error?

@himanshumaurya09876
Hi
Python3 has deprecated the use of the yum module. I think we can abandon the call to yum_check_package_available and use the call to rpm_check_package_available.

Hi, I am getting below error while adding Ambari-Metrics to my cluster
Traceback (most recent call last):
File "//AMBARI_METRICS/package/scripts/metrics_collector.py", line 117, in
AmsCollector().execute()
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 361, in execute
method(env)
File "//AMBARI_METRICS/package/scripts/metrics_collector.py", line 38, in install
self.install_packages(env)
File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 863, in install_packages
retry_count=agent_stack_retry_count)
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 164, in init
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 169, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 133, in run_action
provider_action()
File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install
self._pkg_manager.install_package(package_name, self.__create_context())
File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line 219, in install_package
shell.repository_manager_executor(cmd, self.properties, context)
File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 744, in repository_manager_executor
call_result = subprocess_executor(cmd, timeout=-1, env=env)
File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 446, in subprocess_executor
lines = [line for line in output]
File "/usr/lib64/python3.6/contextlib.py", line 92, in exit
raise RuntimeError("generator didn't stop")
RuntimeError: generator didn't stop

File "/usr/lib64/python3.6/contextlib.py", line 92, in exit
raise RuntimeError("generator didn't stop")

This PR seemed to be trying to use Python 3.9, not 3.6. What happens when you upgrade that? @himanshumaurya09876

File "/usr/lib64/python3.6/contextlib.py", line 92, in exit
raise RuntimeError("generator didn't stop")

This PR seemed to be trying to use Python 3.9, not 3.6. What happens when you upgrade that? @himanshumaurya09876
Also, use code fences for formatting, please

Hi, I have tried both python 3.6 as well as 3.9. It's giving same error in both cases.

File "/usr/lib64/python3.6/contextlib.py", line 92, in exit
raise RuntimeError("generator didn't stop")

This PR seemed to be trying to use Python 3.9, not 3.6. What happens when you upgrade that? @himanshumaurya09876
Also, use code fences for formatting, please

Hi, I have tried both python 3.6 as well as 3.9. It's giving same error in both cases.

@himanshumaurya09876
Hi, thank you for your reply. You are advised to use Python 3.7 or later for verification.

Hi I am getting failures for below UT
`======================================================================
FAIL: test_count_hash_sum (TestResourceFilesKeeper.TestResourceFilesKeeper)
Traceback (most recent call last):
File "ambari-server/src/test/python/TestResourceFilesKeeper.py", line 349, in test_count_hash_sum
self.assertEqual(hash_sum, self.DUMMY_UNCHANGEABLE_PACKAGE_HASH)
AssertionError: 'a3a6ed30f109be83e02a4281d427ee237947248a' != 'c83bb4e4e34213300af27bf48dabf2b7568a174b'

a3a6ed30f109be83e02a4281d427ee237947248a

c83bb4e4e34213300af27bf48dabf2b7568a174b

======================================================================
FAIL: test_zip_directory (TestResourceFilesKeeper.TestResourceFilesKeeper)
Traceback (most recent call last):
File "ambari-common/src/test/python/mock/mock.py", line 1208, in patched
return func(*args, **keywargs)
File "ambari-server/src/test/python/TestResourceFilesKeeper.py", line 434, in test_zip_directory
self.assertEqual(hash_val, self.DUMMY_UNCHANGEABLE_PACKAGE_HASH)
AssertionError: 'a3a6ed30f109be83e02a4281d427ee237947248a' != 'c83bb4e4e34213300af27bf48dabf2b7568a174b'

a3a6ed30f109be83e02a4281d427ee237947248a

c83bb4e4e34213300af27bf48dabf2b7568a174b

======================================================================
FAIL: test_collect_zookeeper (TestPortAlert.TestPortAlert)
Traceback (most recent call last):
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1208, in patched
return func(*args, **keywargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 408, in test_collect_zookeeper
alert.collect()
File "/workspace/ambari/ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py", line 189, in collect
self.collector.put(self.cluster_name, data)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 962, in call
return _mock_self._mock_call(*args, **kwargs)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1025, in _mock_call
ret_val = effect(*args, **kwargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 400, in collector_side_effect
self.assertEqual(data['state'], expected_state)
AssertionError: 'CRITICAL' != 'OK'

CRITICAL

OK

======================================================================
FAIL: test_collect_zookeeper_connectionTimeout (TestPortAlert.TestPortAlert)
Traceback (most recent call last):
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1208, in patched
return func(*args, **keywargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 525, in test_collect_zookeeper_connectionTimeout
alert.collect()
File "/workspace/ambari/ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py", line 189, in collect
self.collector.put(self.cluster_name, data)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 962, in call
return _mock_self._mock_call(*args, **kwargs)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1025, in _mock_call
ret_val = effect(*args, **kwargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 518, in collector_side_effect
self.assertEqual(data['text'], expected_text)
AssertionError: "Connection failed: 'str' object has no attribute 'decode' to <IP_ADDRESS>:2181" != 'Connection failed: Socket Timeout to <IP_ADDRESS>:2181'

Connection failed: 'str' object has no attribute 'decode' to <IP_ADDRESS>:2181

Connection failed: Socket Timeout to <IP_ADDRESS>:2181

======================================================================
FAIL: test_collect_zookeeper_warning (TestPortAlert.TestPortAlert)
Traceback (most recent call last):
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1208, in patched
return func(*args, **keywargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 466, in test_collect_zookeeper_warning
alert.collect()
File "/workspace/ambari/ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py", line 189, in collect
self.collector.put(self.cluster_name, data)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 962, in call
return _mock_self._mock_call(*args, **kwargs)
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1025, in _mock_call
ret_val = effect(*args, **kwargs)
File "/workspace/ambari/ambari-agent/src/test/python/ambari_agent/TestPortAlert.py", line 458, in collector_side_effect
self.assertEqual(data['state'], expected_state)
AssertionError: 'CRITICAL' != 'WARNING'

CRITICAL

WARNING

======================================================================
FAIL: test_status_commands_clear_structured_out (TestScript.TestScript)
Traceback (most recent call last):
File "/workspace/ambari/ambari-common/src/test/python/mock/mock.py", line 1208, in patched
return func(*args, **keywargs)
File "/workspace/ambari/ambari-agent/src/test/python/resource_management/TestScript.py", line 85, in test_status_commands_clear_structured_out
self.assertFalse(open_mock.called)
AssertionError: True is not false

`

 ** wuzhuoming **

@wuzhuoming are you observing the same?

@himanshumaurya09876  @bhavikpatel9977  Thank for pointing out the issue, we're trying to reproduce this problem locally.
BTW, can someone tell us what os the CI/CD uses, we need to figure out which python version is supported.

BTW, can someone tell us what os the CI/CD uses, we need to figure out which python version is supported.

Good point. Are we also planning to have new branch for python-3 or we will merge it in the current 2.7.5 branch?

I think we better merge this feature into a new branch, trunk or 2.8 or others.
OK.

When are you guys planning to complete the validation?

When are you guys planning to complete the validation?
we may need one more week to fix some issues and we also welcome more contributors to join for fully validation on different os or scenary.

we may need one more week to fix some issues and we also welcome more contributors to join for fully validation on different os or scenary.

Sounds good!! Let's connect on slack channel, we will also contribute on this.

Due to above changes stderr:/var/lib/ambari-agent/data/errors.txt is filled with below logs WARNING:root:An exception occurred when calling the hasattr method...... WARNING:root:An exception occurred when calling the hasattr method...... WARNING:root:An exception occurred when calling the hasattr method......

@wenwj0 have you observed the same behaviour and fixed the same?

Due to above changes stderr:/var/lib/ambari-agent/data/errors.txt is filled with below logs WARNING:root:An exception occurred when calling the hasattr method...... WARNING:root:An exception occurred when calling the hasattr method...... WARNING:root:An exception occurred when calling the hasattr method......

We have fixed this issue now and you guys can try to test it. @bhavikpatel9977 @himanshumaurya09876
This problem occurs when we try hasattr(xxx) or getattr(xxx), if we want to set a parameter which is not in configuration dictionary, python3 will throw an exception while  python2 will not throw exception.

Hi everyone, we create a new PR (https://github.com/apache/ambari/pull/3751) to the trunk branch.
Please take a look :）


Server archi

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ CPP
clang-format
12
0
0
0.06s

✅ CPP
cpplint
12

0
0.28s

See detailed report in MegaLinter reports
MegaLinter is graciously provided by


Users can get notification when there is new post

https://github.com/mhy/letheapp/commit/3fa7d70abb9ed67266092da16c22e634f8b94f58


[SPARK-39649][PYTHON] Make listDatabases / getDatabase / listColumns / refreshTable in PySpark support 3-layer-namespace

What changes were proposed in this pull request?
make following commands in pyspark support 3-layer-namespace

~setCurrentDatabase~ (per the comments https://github.com/apache/spark/pull/36969/files#diff-e6c98e62b4d35c54acd0481006733a84d6a12dec0a59b3d3024e103d708fae88R70-R71, skip setCurrentDatabase)
listDatabases
getDatabase
listColumns
refreshTable

Why are the changes needed?
to support 3-layer-namespace
Does this PR introduce any user-facing change?
yes, new api added
How was this patch tested?
updated UT

cc @cloud-fan @amaliujia

also cc @HyukjinKwon if you have some time

thanks, merging to master!


NSListContentConfiguration issue

Dragging column cells on an OutlineView that uses NSListContentConfiguration shakes and the row height changes.
let cellView = outlineView.box.makeView(ofClass: NSTableCellView.self, owner: self)
var configuration = NSListContentConfiguration()
configuration.textProperties.font = .monospacedSystemFont(ofSize: 12, weight: .regular)
configuration.textProperties.lineBreakMode = .byTruncatingTail
configuration.margins = .init(top: 3, leading: 6, bottom: 3, trailing: 6)
switch tableColumnIdentifer {
   case .name:
       configuration.image = item.node.kind.ideIcon?.image
       configuration.text = item.node.name ?? "N/A"
   case .value:
       configuration.text = item.hasChildren ? "" : item.node.stringValue ?? ""
   case .index:
       configuration.text = item.isDisplayIndex ? item.siblingIndex.formatted() : ""
       configuration.textProperties.alignment = .center
}
cellView.contentConfiguration = configuration

return cellView

https://github.com/user-attachments/assets/6d46a385-e063-4d16-b783-7d0d736e8f43

Is this an error that happens since a new commit?

@flocked Yes. This is what happens after a certain commit

Can you maybe please create a sample project? I can't reproduce the error.

AppKit-Xib.zip
This is a directory file viewer example. There will be no shakes when the current columns can be fully displayed, but when the width of the outline view cannot accommodate all columns, dragging will cause shakes.

Thanks. It's fixed in the last commit.


Boreas-2021-09-02-11-42 ground truth poses missing/incorrect

Two issues with the 2021/09/02 sequence:

seems to have incorrect radar_poses.csv on AWS - need to compare AWS version with the navlab backup
misses ground truth pose for radar/1630598033806534.png - maybe just remove this scan because there's another scan with timestamp<PHONE_NUMBER>806533 (only 1ms apart)

:)  The file "radar_poses.csv" does not appear to be in the "applanix/" directory as the paper said. Have it been moved to another directory?

@MMOCKING for which sequence, 2021-09-02 ?

I was able to download radar_poses.csv for 2021-09-02. Note that some of the sequences are "test sequences" as in pyboreas/data/splits.py, so in order to get test results you would need to submit your odometry or localization estimates to the automated benchmark on our website. If you really need the ground truth for one of the test sequences for a paper submission, send me an email at<EMAIL_ADDRESS>and we can discuss.

I think I downloaded the the test sequences. Thanks~

Uploaded the ground truth radar poses stored on navlab to S3 for boreas-2021-09-02-11-42 and deleted the duplicate radar image radar/1630598033806534.png


Are there any details about Role Resolvables?

Trying to use memberHasRole(member, role) but seem to run into problem specifying what is resolvable for role. docs doesnt have details too. pls help tyvm and great work overall!

Role object or Role ID, as stated in the docs

Thanks mate. found it. couldn't find that in the doc prior.


Removed stats prefix

#33

You will also need to update the filename in these files:

https://github.com/stefanzweifel/laravel-stats/blob/master/src/ClassFinder.php#L138
https://github.com/stefanzweifel/laravel-stats/blob/master/src/ClassFinder.php#L159
https://github.com/stefanzweifel/laravel-stats/blob/master/src/StatsServiceProvider.php#L14
https://github.com/stefanzweifel/laravel-stats/blob/master/src/StatsServiceProvider.php#L21

@dhavdc 😳 I did not mean to scare you, sorry.

Lol, im on mobile, I can't create a pull request with multiple changes without it being weird. Let someone else have it ;)


UX-11 Add tree data story

Ready for QA

These changes were incorporated into https://github.com/marklogic/design-system/pull/31 to reduce merge conflict badness, and because Table is the main concern of that release.


Require httplib2 0.9 instead of 0.9.1, to support debian jessie.

I would like to run mopidy-gmusc on debian jessie, but it only has httplib2 0.9, while you require httplib2 0.9.1. Is this really necessary to have 0.9.1, and if not, could you revert it to also support 0.9? Because that would make install mopidy-gmusic on a debian jessie machine so much more easier.

Do you have any output? As i can see mopidy-gmusic don't require httplib:
install_requires=[
'setuptools',
'Mopidy >= 1.0',
'Pykka >= 1.1',
'gmusicapi >= 4.0.0',
]

The dependency tree from mopidy deps:
Mopidy-GMusic: 1.0.0 from /home/jodal/dev/mopidy-gmusic
  setuptools: 17.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
  Mopidy>=1.0: 1.0.4 from /home/jodal/dev/mopidy
    setuptools: 17.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    Pykka>=1.1: 1.2.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages/Pykka-1.2.0-py2.7.egg
    tornado>=2.3: 4.1 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
      certifi: 14.5.14 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages/certifi-14.05.14-py2.7.egg
      backports.ssl-match-hostname: <IP_ADDRESS> from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages/backports.ssl_match_hostname-<IP_ADDRESS>-py2.7.egg
  Pykka>=1.1: 1.2.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages/Pykka-1.2.0-py2.7.egg
  gmusicapi>=4.0.0: 5.0.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    oauth2client>=1.1: 1.4.11 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
      rsa==3.1.4: 3.1.4 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
        pyasn1>=0.1.3: 0.1.7 from /usr/lib/python2.7/dist-packages
      pyasn1==0.1.7: 0.1.7 from /usr/lib/python2.7/dist-packages
      six>=1.6.1: 1.9.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
      pyasn1-modules==0.0.5: 0.0.5 from /usr/lib/python2.7/dist-packages
      httplib2>=0.9.1: 0.9.1 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    mutagen>=1.18: 1.29 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    protobuf>=2.4.1: 2.6.1 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
      setuptools: 17.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    mock>=0.7.0: 1.0.1 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    proboscis>=<IP_ADDRESS>: <IP_ADDRESS> from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    python-dateutil!=2.0,>=1.3: 2.2 from /usr/lib/python2.7/dist-packages
      six: 1.9.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    gpsoauth>=0.0.2: 0.0.2 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
      pycrypto: 2.6.1 from /usr/lib/python2.7/dist-packages
      requests: 2.6.2 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    appdirs>=1.1.0: 1.4.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    decorator>=3.3.1: 3.4.0 from /usr/lib/python2.7/dist-packages
    validictory!=0.9.2,>=0.8.0: 1.0.0 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages
    requests!=1.2.0,!=2.2.1,>=1.1.0: 2.6.2 from /home/jodal/dev/virtualenvs/mopidy/lib/python2.7/site-packages

httplib>=0.9.1 is a dependency of oauth2client, which is a dependency of gmusicapi.
You can probably get around the httplib>=0.9.1 requirement by installing an older oauth2client (>=1.1 is required, 1.4.11 is installed on my system). Looking at https://github.com/google/oauth2client/blob/v1.4.7/setup.py, it seems that oauth2client 1.4.7 is the last one requiring httplib >=0.8, and oauth2client 1.4.8 is the first on requiring httplib >=0.9.1.
Thus, this might work:
pip install oauth2client==1.4.7
pip install -U mopidy-gmusic

Looking at https://github.com/google/oauth2client/commit/659869f19aec766f2b0187ecc95e414331892872, it seems that httplib >=0.9.1 is required to have oauth2client work on Python 3.


chore(#47): converting import module to ESModule way

PR for convertion JS import way. All files were converting to use "import" instead "required".
It's need do a test e2e.

@Mayank0255 I added a new config em sample in sample env for set up the port of MYSQL database... Sometimes you will need run MYSQL in other port, so this setting can resolve this issue in future.

@Mayank0255 I added a new config em sample in sample env for set up the port of MYSQL database... Sometimes you will need run MYSQL in other port, so this setting can resolve this issue in future.

So, any port number can be added there and it will run over there? and if we leave it empty then would it set to any default port?

@Mayank0255 I added a new config em sample in sample env for set up the port of MYSQL database... Sometimes you will need run MYSQL in other port, so this setting can resolve this issue in future.

So, any port number can be added there and it will run over there? and if we leave it empty then would it set to any default port?

I don't put default port, but I can.

@fabioalmeida100
In this PR have you setup BabelJS? which allows you to follow ES6 conventions? Or you have just changed the way we import modules by the type change in package.json?

We don't need use Babel for accept ESModule import/export. Any version majo  >= v13 support natively with use ot type: "module" in package.json. See: https://nodejs.org/docs/latest-v14.x/api/packages.html#packages_determining_module_system

@fabioalmeida100
In this PR have you setup BabelJS? which allows you to follow ES6 conventions? Or you have just changed the way we import modules by the type change in package.json?

We don't need use Babel for accept ESModule import/export. Any version majo >= v13 support natively with use ot type: "module" in package.json. See: https://nodejs.org/docs/latest-v14.x/api/packages.html#packages_determining_module_system

Oh, I see
Good job 👍🏽

@Mayank0255 I added a new config em sample in sample env for set up the port of MYSQL database... Sometimes you will need run MYSQL in other port, so this setting can resolve this issue in future.

So, any port number can be added there and it will run over there? and if we leave it empty then would it set to any default port?

I put the default port for the case of the we leave the port config empty.

Congratulations @fabioalmeida100 on your first PR getting merged to this project!! 🎊 🎊