Plugins (Like VSC)

I would like to see community supported plugins, like VSCode, but not from there, I mean new ones from scratch. It would really help with features the community would like to see, but the devs don’t have time or are not ready to add/support in the recent updates.

This could be possible, but it would be rather restricted. I can see syntax highlighting for new languages, or color themes could be supported, and possibly code snippets since they can be represented as JSON files and contains no executable codes.
But ideally you'd want some degree of logic in the extension. Downloadable scripting languages like Python and Javascript are actually allowed on iOS. To achieve that, we would need to build a bridge between the native platform and those scripts. This could be rather difficult since the project isn't really stable enough to maintain a stable set of APIs.
Of course it would be even more ideal if the app could actually use VSCode extensions. Since VSCode extensions are written in Javascript anyway, extensions that don't need a node environment or other executable binary could work. (though I'm not ruling out the possibility to run node on iOS :) )
As a side project, I am actually also attempting to bring the web version of VSCode to iOS and it has some degree of VSCode extension support: https://medium.com/@thebaselab/my-attempt-to-run-vs-code-on-ipad-687aceaa82f4
In that way, it might be a better idea to port VSCode to iOS with the large existing community support.
Anyway, I'd like to hear more about the use cases of the plugins. What would you want to do with them?

They don’t necessarily have to be written in JS, they could be written in SwiftUI, as I assume that is the language that this app is written in, based on the platform, but that could cause even more restriction, due to the cause of presumably less knowing Swift, over JS.
I would use it to allow programs to have certain user inputs in terminal, adding live previews (on iPadOS) for certain languages, in split screen mode, and much more.

Also, I would like to see a plugin added for language terminal offline capabilities.

You could also add Programming languages as downloadable in plugins which will further enhance the Terminal and This App by adding an Option to compile online with the server and then Offline with the plugins Downloaded Earlier

You could also add Programming languages as downloadable in plugins which will further enhance the Terminal and This App by adding an Option to compile online with the server and then Offline with the plugins Downloaded Earlier

That is a splendid idea, that is probably the best way to go for this type of feature.

Also, I just reread:

Of course it would be even more ideal if the app could actually use VSCode extensions. Since VSCode extensions are written in Javascript anyway, extensions that don't need a node environment or other executable binary could work. (though I'm not ruling out the possibility to run node on iOS :) )

and the last part in parentheses, really stood out to me:

(though I'm not ruling out the possibility to run node on iOS :) )

Since the app now can run NODE, this would open up more possibilities to add plugins that are already in VSCode, contrary to my original request, although I would prefer it at some point, I can live with importing the important plugins from VSCode, for a while. @bummoblizard, let me know what you think. Thanks!

I would love to get the SSH plugin, as that's my main use for an app like this. I don't have a way to edit my sever's files without it :/

I would love to get the SSH plugin, as that's my main use for an app like this. I don't have a way to edit my sever's files without it :/

Noted

I would love to get the SSH plugin, as that's my main use for an app like this. I don't have a way to edit my sever's files without it :/

Noted! I understand this is quite useful.

I was actually able to access my files using Samba Share, however, the app doesn't allow me to open network folders, for some reason. It just crashes. Probably related to #62

I would love to get the SSH plugin, as that's my main use for an app like this. I don't have a way to edit my sever's files without it :/

Noted! I understand this is quite useful.

I was actually able to access my files using Samba Share, however, the app doesn't allow me to open network folders, for some reason. It just crashes. Probably related to #62

Yeah, I would say it is related to #62. Also, @bummoblizard Is there going to be some sort of milestone attached to this, or is this too far in the future to know when or if it will be implemented?

I would love to get the SSH plugin, as that's my main use for an app like this. I don't have a way to edit my sever's files without it :/

Noted! I understand this is quite useful.

I was actually able to access my files using Samba Share, however, the app doesn't allow me to open network folders, for some reason. It just crashes. Probably related to #62

Yeah, I would say it is related to #62. Also, @bummoblizard Is there going to be some sort of milestone attached to this, or is this too far in the future to know when or if it will be implemented?

I'll try to add this in the next release.

+1 for vscode plug-ins. Sadly I can’t use this app because our company repos use  es-lint and when I run
npm run serve
it fails with…

@bummoblizard Are there any updates on this?

is LiveShare an option in this app?

is LiveShare an option in this app?
I do not think so, yet.

Why was this issued referenced in that commit 🤔

I've introduced something called extensions in the recent commits. Although it cannot be dynamically loaded, nor compatible with VS code extensions, it allows a way to extend the editor functionalities in an enclosed environment.
For instance, this single file adds support for viewing images in Code App.
//
//  ImageEditorExtension.swift
//  Code
//
//  Created by Ken Chung on 22/11/2022.
//

import SwiftUI

private class Storage: ObservableObject {
    @Published var data: Data? = nil
}

private struct ImageContextMenu: View {

    let uiImage: UIImage

    var body: some View {
        Button {
            UIImageWriteToSavedPhotosAlbum(uiImage, nil, nil, nil)
        } label: {
            Label("Add to Photos", systemImage: "square.and.arrow.down")
        }
        Button {
            UIPasteboard.general.image = uiImage
        } label: {
            Label("Copy Image", systemImage: "doc.on.doc")
        }

    }

}

private struct ImageView: View {

    @EnvironmentObject var storage: Storage

    var body: some View {
        if let data = storage.data {
            if let uiImage = UIImage(data: data) {
                Image(uiImage: uiImage)
                    .resizable()
                    .scaledToFit()
                    .contextMenu {
                        ImageContextMenu(uiImage: uiImage)
                    }
            }else{
                Text("Unsupported image")
            }
        }else{
            Text("Loading Image")
        }
    }

}

class ImageEditorExtension: CodeAppExtension {

    override func onInitialize(app: MainApp, contribution: CodeAppExtension.Contribution) {
        let provider = EditorProvider(
            registeredFileExtensions: ["png", "tiff", "tif", "jpeg", "jpg", "gif", "bmp", "bmp", "BMPf", "ico", "cur", "xbm", "heic", "webp"],
            onCreateEditor: { url in
                let storage = Storage()
                let editorInstance = EditorInstanceWithURL(
                    view: AnyView(ImageView().environmentObject(storage)),
                    title: url.lastPathComponent,
                    url: url
                )

                app.workSpaceStorage.contents(at: url, completionHandler: { data, error in
                    storage.data = data
                    if let error {
                        app.notificationManager.showErrorMessage(error.localizedDescription)
                    }
                })

                return editorInstance
            }
        )
        contribution.editorProvider.register(provider: provider)
    }
}

That's exactly what I was looking for to be added! Is there a way we can make our own .swift extension files, and import them - preferably from the app? If not, I know that may be a lot of work, but it'd be sick! Keep up the awesome work!

Right now you need to compile the app from Xcode. But in the future it is possible to build a JS bridge to enable dynamic extensions.

Right now you need to compile the app from Xcode. But in the future it is possible to build a JS bridge to enable dynamic extensions.

Ah, ok. Got it. I know this is probably in the README, or another issue, but what version of Xcode and Swift is needed to compile the app? Right now I am stuck on Swift 5.x.x, and Xcode 12.x, if I recall correctly.

I’m using the latest version but Xcode 12 should be fine.
「BatemaDevelopment @.***>」在 2022年12月2日 週五，21:39 寫道：

Right now you need to compile the app from Xcode. But in the future it is
possible to build a JS bridge to enable dynamic extensions.
Ah, ok. Got it. I know this is probably in the README, or another issue,
but what version of Xcode and Swift is needed to compile the app? Right now
I am stuck on Swift 5.x.x, and Xcode 12.x, if I recall correctly.
—
Reply to this email directly, view it on GitHub
https://github.com/thebaselab/codeapp/issues/28#issuecomment-1335247750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJE6T22H2DX2JRTWDYZL6MTWLH32TANCNFSM4XNDFP7A
.
You are receiving this because you were mentioned.Message ID:
@.***>

I’m using the latest version but Xcode 12 should be fine.
「BatemaDevelopment @.***>」在 2022年12月2日 週五，21:39 寫道：

Right now you need to compile the app from Xcode. But in the future it is
possible to build a JS bridge to enable dynamic extensions.
Ah, ok. Got it. I know this is probably in the README, or another issue,
but what version of Xcode and Swift is needed to compile the app? Right now
I am stuck on Swift 5.x.x, and Xcode 12.x, if I recall correctly.
—
Reply to this email directly, view it on GitHub
https://github.com/thebaselab/codeapp/issues/28#issuecomment-1335247750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJE6T22H2DX2JRTWDYZL6MTWLH32TANCNFSM4XNDFP7A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for the info! I'll try to do so!


To add cloning and starting project steps in readme.

I will update the readme and add the required steps to clone the project and run it on live server

@ayush-848
There is already a document "Learn.md" linked with Readme.md file for this.


feat: add is_unique flag for mysql and postgres, partially fixes #20

Just for mysql and postgres
Additionally help needed for mssql, oracledb, sqlite
Partially fixes #20

MSSQL Added

It's created automatically when it's missing 👍🏻

My bad, i thought it was a leftover from a seeded test, but the structure is slightly different from the other DB vendors 👍🏻

I tried getting Oracle to run, but for the life of me can't get it to work.. @kibertoad do you have any insight? I tried copying over Knex's setup, but that doesn't seem to run (get some vague ORA-01012: not logged on error) on my end.

I'll merge this for now, as everything else is looking good 🙂
We can figure out Oracle testing separately from this


Authentication Controller Module

Agent,
Your second task is to build a controller module that handles the third-party authenticated login requests.
To do so you will first edit the passport builder to include google OAuth2 strategy.
Once the strategy configuration is done you will be able to prefer the controller. The controller module creates and returns an express router to which you shall add the /google and /google/callback paths.
The function handling the login request who will be provided the user instance that is injected by the passport strategy, will use the provided user instance to return the logged in user's token in response.
You will also be required to create a new application via google developers to be provided with a client ID and secret and to be able to test that it all works.
Good luck!

commit edefd7ed73c485487b50752e41827db3f0ad6f1f

Commit edefd7ed73c485487b50752e41827db3f0ad6f1f


Added the functionality to upload routes

Now, when uploading routes, you can actually upload a .gpx file and see it in the map

I´ve merged this branch to load_routes branch in order to keep working there with the process of loading the routes into the state.
Maybe we can close and not merge this Pull Request and keep working in the other branch(a lot of things are different from this branch) and when we finish there doing a pull request again.
What do you think? @alvarogarinf

Okey


Speed up "push" builds.

Travis has two build types that we use: "push" and "pull request". On a "pull request" commit the TRAVIS_BRANCH env. var. tells us what we are diff-ing against and makes it easy to limit the build jobs based on the changed files.
In "push" builds, the best we have is TRAVIS_COMMIT_RANGE but this is not a very dependable value. I propose we rely instead on the GitHub API to determine the changed files.

Try our best to parse the PR number from the commit message (if this fails, just bail and run every single test)
Verify the PR number by checking if the TRAVIS_COMMIT (and the HEAD commit in our local checkout) matches the merge_commit_sha in the PR endpoint: https://api.github.com/repos/GoogleCloudPlatform/google-cloud-python/pulls/2450
Once we have the PR, hit the PR files endpoint to get a list of changed files, e.g.: https://api.github.com/repos/GoogleCloudPlatform/google-cloud-python/pulls/2461/files

As an alternative to the first step, there is an "unpublished" API which helps associate a commit SHA with a PR. For example, see the parenthetical 2461 below:

which tells us that 4e8afa8c3877376d7e9a6df79e6a272ae1cdfee7 came as part of #2461. The actual API returns an SVG with the payload containing

(#2461)

The API simply requires the commit hash in TRAVIS_COMMIT (i.e. just the HEAD commit on our local checkout), e.g. https://github.com/GoogleCloudPlatform/google-cloud-python/branch_commits/4e8afa8c3877376d7e9a6df79e6a272ae1cdfee7

@tseaver @jonparrott PTAL and LMKWYT
FYI this will build on top of work done for #2277.

Also worth noting that even if the files endpoint didn't exist, the PR endpoint has a base key which tells what state the main branch was in before the PR was merged. For example,  https://api.github.com/repos/GoogleCloudPlatform/google-cloud-python/pulls/2450 has
  "base": {
    "label": "GoogleCloudPlatform:master",
    "ref": "master",
    "sha": "042daf5f2db6fdcc5323cfbdbcabcbf241fa7278",
    ...


[UH-402] WIP, Add trigger and validation

Tests are missing

reviewed

I just added a testcase. Looks fine


Default behaviour of the Terminate/Restart Current Task if only one task to choose that task automatically

If one were to run workbench.actions.tasks.terminate or workbench.actions.tasks.restart after setting a custom keybinding for them, the UI will always prompt for the user to choose which tasks to restart/terminate.
This is great if there's multiple tasks running. But if there's only one task running then it can be a major annoyance and slow down your workflow.
I propose that the behaviour can be set (with a workbench setting) to select the only running item by default if there's no other running tasks. (A naive tasks.length == 1 check would do it or something like that?)

Dups https://github.com/Microsoft/vscode/pull/47853.

I ended up implementing a workaround using the new tasks API:
https://marketplace.visualstudio.com/items?itemName=vshaxe.terminator

that's not really related to this issue at all...it does get rid of the popup I suppose, which is another unrelated issue. @Gama11

Yeah, I suppose you're right. It's a bit different, but still related. :)


Update config-validator to 0.2.0

Config validator is now at 0.2.0 can this dep be updated as well?

@googlebot I signed it!


Batch moving data always logs a few warnings which don't make sense

When I do a batch request (copying/removing a whole directory), I get several of these messages:
urllib3.connectionpool - WARNING - Failed to parse headers (url=https://www.googleapis.com:443/batch): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ''
Traceback (most recent call last):
  File "/opt/conda/default/lib/python3.6/site-packages/urllib3/connectionpool.py", line 441, in _make_request
    assert_header_parsing(httplib_response.msg)
  File "/opt/conda/default/lib/python3.6/site-packages/urllib3/util/response.py", line 71, in assert_header_parsing
    raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ''

It seems like something is wrong, but the operation is succesfull. Is there an idea what this means?

Anecdotally, I have heard that this may be an issue with openSSL. Can you try with different versions to see if it goes away?

This is with the latest version of openSSL though:
> openssl version
OpenSSL 1.1.1d  10 Sep 2019

They just released a new version about a week ago, I might be able to check next week.


feat(styled-component): register default theme in main project

Codecov Report

Merging #5 into master will decrease coverage by 23.91%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           master       #5       +/-   ##
===========================================
- Coverage     100%   76.08%   -23.92%
===========================================
  Files           5        7        +2
  Lines          35       46       +11
  Branches       11       12        +1
===========================================
  Hits           35       35
- Misses          0       11       +11

Impacted Files
Coverage Δ

src/component/atoms/button/button.component.tsx
0% <0%> (ø)

src/component/atoms/button/style/style.tsx
0% <0%> (ø)

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 3aa9760...5eda4fb. Read the comment docs.


feat: record daily link clicks

Fixes Issue
Record stats for daily clicks for each link

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thanks @srkds

Have a doubt about understanding the date field in the model. Is it referring to the last click timestamp or storing the clicks count day-wise?

It is storing it for each day. So it will collect how many clicks there were per day

It is storing it for each day. So it will collect how many clicks there were per day

Sounds good 👍
Thanks, Eddie!


Use Constraints instead of Frames

Closes #142

Are these really the only usages of frames? I'm surprised.
Minor thing: It seems more of a 📐 than a 💄 to me. ¯_(ツ)_/¯

Any more we are going to do on this?


Basic Metadata support

Be part of #1
Support basic metadata like title, author, datetime, tag

Covered by 803ddcf9602239cbc58e3d3c0075dbc8a9cdd3d4


Fix pysnmp import error

@CameronGoedinghaus, after working on the trap forwarding module, what are your thoughts about being able to update to the latest release of pysnmp instead of having our own custom version?

@evan-quest I think it may be better, this is a bug that was fixed in the official version, but it only causes issues when I'm testing locally. There are likely other bugs that are fixed in the latest version. Although it would require reworking some things.


Process fails when input file contains spaces

Lambda TextractAsyncJobSubmitFunction runs to success, but actually fails to process the file.  The following errors can be seen in CloudWatch:

An error occurred (InvalidParameterException) when calling the StartDocumentAnalysis operation: Request has invalid parameters
An error occurred (InvalidParameterException) when calling the StartDocumentTextDetection operation: Request has invalid parameters

Two issues: 1. the problem specified above, and 2. the Lambda itself should probably fail under these circumstances (can't perform operation after retries).
Thanks for this code.

Thanks for bringing this to attention. The code in job submission Lambda now checks for invalid parameter exception, and fails gracefully with failure message captured in Log and returned to invocation source.

I don't think spaces are the root cause; it has to do with the fact that the S3 event is URL encoding the S3 key name and the Lambda isn't decoding it before passing to Textract. I opened issue #2 with PR #3 to decode the key name which should allow spaces to be used.


Bug 2058794: Bump Jenkins LTS Version

ART request: https://issues.redhat.com/browse/ART-3978

/assign @gabemontero @akram @jkhelil

/approve

I think this is all that is not required for 4.x jenkins core bumps, but @akram is more familiar with the latest needs than I am ... ideally he plus one's that we are doing the correct things upstream (while the ART req @coreydaley opened handles downstream)
let's see if he is back this week from PTO and can chime in and lgtm

so yeah just heard in scrum @akram is still on PTO this week so I'll
/lgtm
and if something comes up during QE verifications we'll circle back with additional PRs


Allow passing in options object

As in:
app.use(frameguard({action: 'ALLOW-FROM', domains: ['foo', 'bar']});

Would make it easier to implement https://github.com/helmetjs/helmet/issues/112..

Note: most if not all other helmetjs plugins seem to accept an options object, so would help consistency as well.

A check to see if first arg is an object might allow backwards-compatibility..

Completed this in 400df656289e8a257f8663332412e5de76360dae.

I've released<EMAIL_ADDRESS>and a new release of helmet is soon to follow!


Fix link text for staging URLs

Also a few edits to the readme to make it easier to get started.

Awesome stuff, thanks! 👍


Fix package tests

Forward port of 1c214ec2d
JIRA Issues: MARATHON-8725

How does this relate to #7149?

How does this relate to #7140?

https://github.com/mesosphere/marathon/pull/7140/files#r380167981


Errors symlinking/copying files

We're getting the following errors during container build.  @kbrock is https://github.com/ManageIQ/manageiq/blob/c495e7615d92da26b8cf3842e691660e2e2870e7/Dockerfile#L17 or https://github.com/ManageIQ/manageiq-appliance/blob/a6fe83b1f151e8a73be1883a868e13273a8b20e3/setup#L5 necessary now that the RPM is putting files in the correct location?
This is not urgent, the build still succeeds, just logging some errors
STEP 5: RUN source /etc/default/evm &&     $APPLIANCE_SOURCE_DIRECTORY/setup &&     echo "# This file intentionally left blank. ManageIQ maintains its own SSL configuration" > /etc/httpd/conf.d/ssl.conf
'/opt/manageiq/manageiq-appliance/LINK/etc/cron.hourly/miqtimestamp-hourly.cron' -> '/etc/cron.hourly/miqtimestamp-hourly.cron'
cp: cannot create symbolic link '/etc/cron.hourly/miqtimestamp-hourly.cron' to '/opt/manageiq/manageiq-appliance/LINK/etc/cron.hourly/miqtimestamp-hourly.cron': File exists
'/opt/manageiq/manageiq-appliance/LINK/etc/cron.hourly/pg-inpsector-server-hourly.cron' -> '/etc/cron.hourly/pg-inpsector-server-hourly.cron'
cp: cannot create symbolic link '/etc/cron.hourly/pg-inpsector-server-hourly.cron' to '/opt/manageiq/manageiq-appliance/LINK/etc/cron.hourly/pg-inpsector-server-hourly.cron': File exists
'/opt/manageiq/manageiq-appliance/LINK/etc/default/evm' -> '/etc/default/evm'
cp: cannot create symbolic link '/etc/default/evm' to '/opt/manageiq/manageiq-appliance/LINK/etc/default/evm': File exists
cp: cannot create symbolic link '/etc/default/manageiq-productization.properties' to '/opt/manageiq/manageiq-appliance/LINK/etc/default/manageiq-productization.properties': File exists
'/opt/manageiq/manageiq-appliance/LINK/etc/default/manageiq-productization.properties' -> '/etc/default/manageiq-productization.properties'
'/opt/manageiq/manageiq-appliance/LINK/etc/default/manageiq.properties' -> '/etc/default/manageiq.properties'
'/opt/manageiq/manageiq-appliance/LINK/etc/profile.d/evm.sh' -> '/etc/profile.d/evm.sh'
'/opt/manageiq/manageiq-appliance/LINK/etc/sudoers.d/repmgr' -> '/etc/sudoers.d/repmgr'
cp: cannot create symbolic link '/etc/default/manageiq.properties' to '/opt/manageiq/manageiq-appliance/LINK/etc/default/manageiq.properties': File exists
cp: cannot create symbolic link '/etc/profile.d/evm.sh' to '/opt/manageiq/manageiq-appliance/LINK/etc/profile.d/evm.sh': File exists
cp: cannot create symbolic link '/etc/sudoers.d/repmgr' to '/opt/manageiq/manageiq-appliance/LINK/etc/sudoers.d/repmgr': File exists
'/opt/manageiq/manageiq-appliance/LINK/root/.ansible.cfg' -> '/root/.ansible.cfg'
cp: cannot create symbolic link '/root/.ansible.cfg' to '/opt/manageiq/manageiq-appliance/LINK/root/.ansible.cfg': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/cloud_ds_check.sh' -> '/usr/bin/cloud_ds_check.sh'
cp: cannot create symbolic link '/usr/bin/cloud_ds_check.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/cloud_ds_check.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/cockpit-auth-miq' -> '/usr/bin/cockpit-auth-miq'
cp: cannot create symbolic link '/usr/bin/cockpit-auth-miq' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/cockpit-auth-miq': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm-failover-monitor' -> '/usr/bin/evm-failover-monitor'
cp: cannot create symbolic link '/usr/bin/evm-failover-monitor' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm-failover-monitor': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm_watchdog' -> '/usr/bin/evm_watchdog'
cp: cannot create symbolic link '/usr/bin/evm_watchdog' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm_watchdog': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm_watchdog.rb' -> '/usr/bin/evm_watchdog.rb'
cp: cannot create symbolic link '/usr/bin/evm_watchdog.rb' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/evm_watchdog.rb': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/evminit.sh' -> '/usr/bin/evminit.sh'
cp: cannot create symbolic link '/usr/bin/evminit.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/evminit.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/evmserver.sh' -> '/usr/bin/evmserver.sh'
cp: cannot create symbolic link '/usr/bin/evmserver.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/evmserver.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/fix_auth' -> '/usr/bin/fix_auth'
cp: cannot create symbolic link '/usr/bin/fix_auth' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/fix_auth': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/generate_miq_server_cert.sh' -> '/usr/bin/generate_miq_server_cert.sh'
cp: cannot create symbolic link '/usr/bin/generate_miq_server_cert.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/generate_miq_server_cert.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/generate_rpm_manifest.sh' -> '/usr/bin/generate_rpm_manifest.sh'
cp: cannot create symbolic link '/usr/bin/generate_rpm_manifest.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/generate_rpm_manifest.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/manageiq-initialize.sh' -> '/usr/bin/manageiq-initialize.sh'
cp: cannot create symbolic link '/usr/bin/manageiq-initialize.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/manageiq-initialize.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/miq_config_sssd' -> '/usr/bin/miq_config_sssd'
cp: cannot create symbolic link '/usr/bin/miq_config_sssd' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/miq_config_sssd': File exists
cp: cannot create symbolic link '/usr/bin/miqldap_to_sssd' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqldap_to_sssd': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqldap_to_sssd' -> '/usr/bin/miqldap_to_sssd'
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqselinux.sh' -> '/usr/bin/miqselinux.sh'
cp: cannot create symbolic link '/usr/bin/miqselinux.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqselinux.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqtop.sh' -> '/usr/bin/miqtop.sh'
cp: cannot create symbolic link '/usr/bin/miqtop.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqtop.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqvmstat.sh' -> '/usr/bin/miqvmstat.sh'
cp: cannot create symbolic link '/usr/bin/miqvmstat.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/miqvmstat.sh': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/normalize_userid_to_upn' -> '/usr/bin/normalize_userid_to_upn'
cp: cannot create symbolic link '/usr/bin/normalize_userid_to_upn' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/normalize_userid_to_upn': File exists
'/opt/manageiq/manageiq-appliance/LINK/usr/bin/pg_inspector_server.sh' -> '/usr/bin/pg_inspector_server.sh'
cp: cannot create symbolic link '/usr/bin/pg_inspector_server.sh' to '/opt/manageiq/manageiq-appliance/LINK/usr/bin/pg_inspector_server.sh': File exists
'/opt/manageiq/manageiq-appliance/COPY/etc/issue.template' -> '/etc/issue.template'
'/opt/manageiq/manageiq-appliance/COPY/etc/motd.manageiq' -> '/etc/motd.manageiq'
'/opt/manageiq/manageiq-appliance/COPY/etc/cloud/cloud.cfg.d/10_miq_cloud.cfg' -> '/etc/cloud/cloud.cfg.d/10_miq_cloud.cfg'
'/opt/manageiq/manageiq-appliance/COPY/etc/cloud/cloud.cfg.d/10_miq_logging.cfg' -> '/etc/cloud/cloud.cfg.d/10_miq_logging.cfg'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-balancer-api.conf' -> '/etc/httpd/conf.d/manageiq-balancer-api.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-balancer-ui.conf' -> '/etc/httpd/conf.d/manageiq-balancer-ui.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-balancer-websocket.conf' -> '/etc/httpd/conf.d/manageiq-balancer-websocket.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-host-config' -> '/etc/httpd/conf.d/manageiq-host-config'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-http.conf' -> '/etc/httpd/conf.d/manageiq-http.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-https-application.conf' -> '/etc/httpd/conf.d/manageiq-https-application.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-https.conf' -> '/etc/httpd/conf.d/manageiq-https.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-redirects-api' -> '/etc/httpd/conf.d/manageiq-redirects-api'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-redirects-cockpit' -> '/etc/httpd/conf.d/manageiq-redirects-cockpit'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-redirects-ui' -> '/etc/httpd/conf.d/manageiq-redirects-ui'
'/opt/manageiq/manageiq-appliance/COPY/etc/httpd/conf.d/manageiq-redirects-websocket' -> '/etc/httpd/conf.d/manageiq-redirects-websocket'
'/opt/manageiq/manageiq-appliance/COPY/etc/logrotate.d/miq_logs.conf' -> '/etc/logrotate.d/miq_logs.conf'
'/opt/manageiq/manageiq-appliance/COPY/etc/manageiq/postgresql.conf.d/01_miq_overrides.conf' -> '/etc/manageiq/postgresql.conf.d/01_miq_overrides.conf'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/cloud-ds-check.service' -> '/usr/lib/systemd/system/cloud-ds-check.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/evm-failover-monitor.service' -> '/usr/lib/systemd/system/evm-failover-monitor.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/evm-watchdog.service' -> '/usr/lib/systemd/system/evm-watchdog.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/evminit.service' -> '/usr/lib/systemd/system/evminit.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/evmserverd.service' -> '/usr/lib/systemd/system/evmserverd.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/manageiq-initialize.service' -> '/usr/lib/systemd/system/manageiq-initialize.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/miqtop.service' -> '/usr/lib/systemd/system/miqtop.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/lib/systemd/system/miqvmstat.service' -> '/usr/lib/systemd/system/miqvmstat.service'
'/opt/manageiq/manageiq-appliance/COPY/usr/sbin/ifup-local' -> '/usr/sbin/ifup-local'

I think all of this is probably handled by the RPM or can be if it isn't already.

Do you want to go ahead with https://github.com/ManageIQ/manageiq/pull/21449 or do you have another approach you want me to try?


Build error

Can someone help make sense of this?
rm -f *.o
rm -f */*.o
rm -f vdexExtractor
make: Leaving directory '/home/laptop/vdexExtractor/src'
make: Entering directory '/home/laptop/vdexExtractor/src'
gcc -c -std=c11 -D_GNU_SOURCE -Wall -Wextra -Werror -DVERSION=\"dev-78f283b\" -c dex.c -o dex.o
gcc -c -std=c11 -D_GNU_SOURCE -Wall -Wextra -Werror -DVERSION=\"dev-78f283b\" -c dex_instruction.c -o dex_instruction.o
dex_instruction.c:655:43: error: argument 2 of type ‘u4[kMaxVarArgRegs]’ {aka ‘unsigned int[kMaxVarArgRegs]’} declared as a variable length array [-Werror=vla-parameter]
  655 | void dexInstr_getVarArgs(u2 *code_ptr, u4 arg[kMaxVarArgRegs]) {
      |                                        ~~~^~~~~~~~~~~~~~~~~~~
In file included from dex_instruction.c:23:
dex_instruction.h:278:32: note: previously declared as an ordinary array ‘u4[]’ {aka ‘unsigned int[]’}
  278 | void dexInstr_getVarArgs(u2 *, u4[]);
      |                                ^~~~
cc1: all warnings being treated as errors
make: *** [Makefile:56: dex_instruction.o] Error 1
make: Leaving directory '/home/laptop/vdexExtractor/src'
[-] build failed

i have the save problem to , have you solved,bro?

same here... is it related to the current zlib update (just guessing here).

Check this PR: https://github.com/anestisb/vdexExtractor/pull/75

yes but you can skip it by edit src/Makefile and remove '-Werror'


create public access for DelegateManager class

I found it necessary to create a extension for the DelegateManager class to customise the behaviour of the delegate. In my case I wanted to handle redirects in a custom way so an extension was created which implements the willPerformHTTPRedirection method.

Cool thanks!


add_points_from_xy() raise AttributeError if the input dataframe contains column names not supported by namedtuples

Environment Information

leafmap version: 0.9.3
Python version: 3.8
Operating System: Windows 10

Description
Tested add_points_from_xy() using dataframes with column names that are not supported by namedtuples (e.g., starts with "_" or has space). It will raise AttributeError (like: 'Pandas' object has no attribute <column_name>) in the line generating html for popup_html:
for row in df.itertuples():
        html = ""
        for p in popup:
            html = html + "" + p + "" + ": " + str(getattr(row, p)) + "
"

In df.itertuples(), the column names not supported by namedtuples will be automatically renamed (e.g., '_col1' will be change to '_0'). And in getattr(row, p), it will not be able to retrieve the attribute with the original column name.
What I Did
A code example to track which fields have changed by namedtuples
from collections import namedtuple

columns = ["_col1", "_col2", "column name", "col4"]
a = namedtuples("Table", columns, rename=True)

old_fields = columns
new_fields = a._fields

mapper = {}
for f1, f2 in zip(old_fields, new_fields):
    mapper[f1] = f2

print(mapper)

{"_col1": "_0", "_col2": "_1", "column name": "0_2", "col4": "col4"}

Solutions
A quick solution would be changing df.itertuples() to df.iterrows() and corresponding str(getattr(row, p)) to str(row[p]) or suggest users to rename the dataframe columns which are not supported by namedtuples.
The code block in foliumap.py to be changed for example:
for idx, row in df.iterrows():
    html = ""
    for p in popup:
        html = html + "" + p + "" + ": " + str(row[p]) + "
"
    popup_html = folium.Popup(html, min_width=min_width, max_width=max_width)

    if items is not None:
        index = items.index(row[color_column])

Thanks for reporting. Would you like to submit a pull request so that you can get credit for this?

Hi Qiusheng,
So nice to have your reply! Your geospatial python libraries are so useful!
BTW, a brief introduction of myself. My name is Junjie Zhang. I have a
background in geoinformation science and had my bachelor from Wuhan
University.
The geospatial python libraries you have created. I was amazed when I came
across them and found your webpage online. They are so useful and fill some
gaps that are long-existing in the GIS field. You have created such
wonderful tools and made such great contributions to the community!
Hope to connect with you and hope to continue to contribute to the project.
Best regards,
Jason
On Wed, Jun 1, 2022 at 11:53 PM Qiusheng Wu @.***>
wrote:

Thanks for reporting. Would you like to submit a pull request so that you
can get credit for this?
—
Reply to this email directly, view it on GitHub
https://github.com/giswqs/leafmap/issues/248#issuecomment-1144406776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISRFWB3JXXTMX4OSLQGXLVNAV43ANCNFSM5XSPWRFQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Segmentation fault when importing TensorFlow

After installing TensorFlow 0.10.0rc0 with pip in a virtualenv
import tensorflow as tf
results in
Segmentation fault (core dumped)
Importing numpy before tensorflow results in the same segfault
OS: RedHat 6, 64-bit
(Installed glibc 2.1.4 from source)
Python Version 3.4.5
pip packages (cpu versions):
tensorflow-0.10.0rc0-cp34-cp34m-linux_x86_64.whl
protobuf-3.0.0b2.post2-cp34-none-linux_x86_64.whl
six-1.10.0-py2.py3-none-any.whl
numpy-1.11.1-cp34-cp34m-manylinux1_x86_64.whl
(same problem with numpy-1.8.2-cp34-cp34m-manylinux1_x86_64.whl)
Debugger Output:
gdb python
run tf.py
(tf.py contains: import tensorflow as tf)
[Thread debugging using libthread_db enabled]
Missing separate debuginfo for /home/rolf/tfenv3/lib/python3.4/site-packages/numpy/core/../.libs/libgfortran-ed201abd.so.3.0.0
[New Thread 0x7ffff352a700 (LWP 2920)]
[New Thread 0x7ffff2b29700 (LWP 2921)]
[New Thread 0x7ffff0128700 (LWP 2922)]
[New Thread 0x7fffed727700 (LWP 2923)]
[New Thread 0x7fffead26700 (LWP 2924)]
[New Thread 0x7fffe8325700 (LWP 2925)]
[New Thread 0x7fffe5924700 (LWP 2926)]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff793878b in init_one_static_tls (map=0x0) at allocatestack.c:1171
1171      void *dest = (char *) curp - map->l_tls_offset;
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-7.el6_0.x86_64 glibc-2.12-1.192.el6.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-57.el6.x86_64 libcom_err-1.41.12-22.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64

I think this kind of error is caused by dueling versions of glibc.  Something linked with TensorFlow is using the wrong version, and two separate versions of glibc in the same process is bad.

This seems to have been the case.
I have replaced six and numpy with the source versions and reinstalled tensorflow with pip.
This removed the segfault but left me with the problem that libstdc++ was too old.
Finally, the following way of setting up a local glibc/libstdc++ environment solved my problem:
http://stackoverflow.com/questions/33655731/error-while-importing-tensorflow-in-python2-7-in-ubuntu-12-04-glibc-2-17-not-f/34897674#34897674

@bardeli Glad you found away around it!

I meet this question,too. then how to get the correct version of glibc?


Fix spacetobatchnd assertion

Description
Fix for SpaceToBatchND spatial dimensions assertions

For repository owners only:
Please remember to apply all applicable tags to your pull request.
Tags: FEATURE, BREAKING, BUG, PERF, DEV, DOC, SECURITY
For more info see: https://github.com/tensorflow/tfjs/blob/master/DEVELOPMENT.md

This change is

https://github.com/tensorflow/tfjs/issues/597

Any update on this ? Who is supposed to review it ?
@dsmilkov


IRGen: Don't use the demangler to realize imported Objective-C class metadata for now [5.2]

Recently we started using the runtime demangler to realize imported
Objective-C class metadata, to save on code size since no metadata
accessor function needs to be emitted in this case.
This introduced a regression where OBJC_CLASSREF symbols were no
longer being emitted in some cases, which breaks autolinking.
The fix for this was tracked by rdar://56136123, but unfortunately
had to be reverted because it caused other problems.
Until the original fix can be re-applied, let's put in a temporary
workaround where we avoid going through the runtime demangler for
imported Objective-C classes. This regresses code size but unblocks
everyone involved, until the fix for the demangling code path
(824752547129f0cfdbbfd358a164031a9024972d) can be re-applied.
Fixes rdar://56621277.

@swift-ci Please test

Would we need to also disable using demangling for types that structurally contain ObjC classes?

@jckarter You're absolutely right... but this is the narrowest fix that unblocks folks here. Let's invest the energy into getting @gottesmm's fix re-applied instead, so we can revert my hack altogether.


Improve Struct.new

https://bugs.ruby-lang.org/issues/19416
The last commit describes some curious behaviour in Struct.new, I added an upstream bug report for this.

I fixed the issue with const_set in #939, so I'm just going to add a dependency here. I would guess the change to const_set is more relevant


Messages to slack are not delivered

Description
The CloudWatch alert messages are not delivered to the Slack Channel.

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: 6.0.0

Terraform version:

Terraform v1.5.0
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.10.0
+ provider registry.terraform.io/hashicorp/external v2.3.1
+ provider registry.terraform.io/hashicorp/local v2.4.0
+ provider registry.terraform.io/hashicorp/null v3.2.1

Reproduction Code [Required]
I have the following code:
inputs = {
  sns_topic_name = "notify-slack-topic"

  # The below URL is currently in Github Secret as: TF_VAR_slack_webhook_url.
  slack_webhook_url = ""
  slack_channel     = "example_alerts"
  slack_username    = "reporter"
  kms_key_arn       = dependency.sns_topic_kms.outputs.key_arn
  sns_topic_kms_key_id = dependency.sns_topic_kms.outputs.key_id

  lambda_description = "Lambda function which sends notifications to Slack"
  log_events         = true

  # VPC
  lambda_function_vpc_subnet_ids         = dependency.vpc.outputs.private_subnets
  lambda_function_vpc_security_group_ids = [dependency.lambda_vpc_security_group.outputs.security_group_id]

  # Added this argument not to recreate the missing package once it was created
  recreate_missing_package = false

  tags = local.environment_vars.locals.tags
}

In the AWS Dashboard, I can confirm that the Lambda has got the value of slack_webhook_url successfully:

The KMS Key used has the necessary permissions (the last statement allows everything for testing purposes):
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Default",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::66666666:root"
            },
            "Action": "kms:*",
            "Resource": "*"
        },
        {
            "Sid": "KeyAdministration",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::66666666:root"
            },
            "Action": [
                "kms:Update*",
                "kms:UntagResource",
                "kms:TagResource",
                "kms:ScheduleKeyDeletion",
                "kms:Revoke*",
                "kms:Put*",
                "kms:List*",
                "kms:Get*",
                "kms:Enable*",
                "kms:Disable*",
                "kms:Describe*",
                "kms:Delete*",
                "kms:Create*",
                "kms:CancelKeyDeletion"
            ],
            "Resource": "*"
        },
        {
            "Sid": "CloudWatchLogs",
            "Effect": "Allow",
            "Principal": {
                "Service": "logs.ap-southeast-2.amazonaws.com"
            },
            "Action": [
                "kms:ReEncrypt*",
                "kms:GenerateDataKey*",
                "kms:Encrypt*",
                "kms:Describe*",
                "kms:Decrypt*"
            ],
            "Resource": "*",
            "Condition": {
                "ArnLike": {
                    "kms:EncryptionContext:aws:logs:arn": "arn:aws:logs:ap-southeast-2:66666666:log-group:*"
                }
            }
        },
        {
            "Sid": "CloudWatch",
            "Effect": "Allow",
            "Principal": {
                "Service": "cloudwatch.amazonaws.com"
            },
            "Action": [
                "kms:ReEncrypt*",
                "kms:GenerateDataKey*",
                "kms:Encrypt*",
                "kms:Describe*",
                "kms:Decrypt*"
            ],
            "Resource": "*"
        },
        {
            "Sid": "SNS",
            "Effect": "Allow",
            "Principal": {
                "Service": "sns.amazonaws.com"
            },
            "Action": [
                "kms:ReEncrypt*",
                "kms:GenerateDataKey*",
                "kms:Encrypt*",
                "kms:Describe*",
                "kms:Decrypt*"
            ],
            "Resource": "*"
        },
        {
            "Sid": "Allow AWS services to use the key",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "kms:GenerateDataKey*",
                "kms:Decrypt"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "AWS:SourceAccount": "66666666"
                }
            }
        }
    ]
}

Actual behavior
I'm using this payload to run tests directly to the Lambda using the AWS Dashboard.
When I do so, I get the following error:
START RequestId: e6e0486a-0dc5-46e6-a9a7-8771fbb320b7 Version: $LATEST
2023-08-21T07:26:43.859Z e6e0486a-0dc5-46e6-a9a7-8771fbb320b7 Task timed out after 30.03 seconds

END RequestId: e6e0486a-0dc5-46e6-a9a7-8771fbb320b7
REPORT RequestId: e6e0486a-0dc5-46e6-a9a7-8771fbb320b7	Duration: 30032.62 ms	Billed Duration: 30000 ms	Memory Size: 128 MB	Max Memory Used: 28 MB

If I do a curl directly to the Slack Channel Webhook URL, it works:
curl -X POST -H 'Content-type: application/json' --data '{"text":"Hello, World!"}' https://hooks.slack.com/services/T__________E/6__________ov

I found the issue. It was a typo in my Lambda Security Group that had the egress rule invalid. Closing this issue.


Error executing query: "Unexpected token '<',' <h'.. is not a valid json

Thanos and Prometheus version:
Thanos: 0.28.1
Prometheus: 2.38.0
Object Storage Provider: S3
What happened: I'm using Prometheus and Thanos to Monitor Jira, when I try to query older data (7 days or older) using sum or rate it gives me:
Error executing query: "Unexpected token '<','<html> <h'.. is not a valid json

Note: It works fine for recent data that is not older than 7 days.
How to reproduce it (as minimally and precisely as possible): Here's the one of the query in which I'm getting the issue:
sum(rate(jira_request_duration_on_path_count{job="job name"}[5m])) by (instance_id)

Environment:

OS : Ubuntu 20.04.5

I would appreciate any help in resolving this issue. Thank you!

SyntaxError: Unexpected token '<', "
<h"... is not valid JSON

This looks like a timeout or an error response from a proxy like nginx. Is there any way you can verify whether this is the root cause

I'm actually running Thanos query behind a nginx reverse proxy, so probably that can be the issue.

You can try setting the timeout on nginx to a higher value to see if it helps.

Thanks, I'll give it a try

Uncaught Javascript Error > Unexpected token <
<h"... is not valid JSON can you help solve this problem

Uncaught Javascript Error > Unexpected token <
<h"... is not valid JSON can you help solve this problem in odoo website

Hi @fpetkovski, I tried adding timeout in nginx config but still getting the same issue.

I found that one simple solution is by deactivating Modsecurity in my NGINX ingress.

How do you deactivate mode security in NGINX?  I'm getting the same error

Before for me nginx virtual host file details
client_max_body_size 5M;
I fix this to new value
client_max_body_size 20M;
Same concern resovled successful
Thanks,
Tejaskumar Tank


bug: Screen Reader reads ion-select just as a button

Bug Report
Ionic version:

[ ] 4.x
[x] 5.x
Current behavior:
ion-select when used along with ion-select-option is not read by screen reader software like NVDA screen reader properly. It’s just read as a “button”.
Expected behavior:
As per the violation highlighted by the AXE chrome extension, the combobox role (added by ion-select) should have child elements tagged to with role textbox for accessibility tools to work as expected. However, ion-select-option adds html elements with role as “option”
Related code:
Sample Usage:
<ion-select id="input-user-address-state" formControlName="state">
  <ion-select-option *ngFor="let state of stateList" [value]="state.value">{{state.name}}</ion-select-option>
</ion-select>

Refer to item 1 in the document shared in Slack for further details.
https://ionicteam.slack.com/archives/C7CGXAVTL/p1592319616186200

It appears that the relationship when using aria-labelledby is broken in the shadow dom. In this instance, using aria-labelledby in the shadow dom and referencing an element outside of the shadow dom does not work. Looks like other people are running into this too: https://developer.paciellogroup.com/blog/2012/07/notes-on-web-components-aria/
I do not know if this is a flaw in the spec, or if this is a bug in browsers. This does not appear to be a bug in the framework. Still investigating.

When fixing this, we should also ensure it resolves the second/related issue described in https://github.com/ionic-team/ionic/issues/21601#issuecomment-649636418.


Update README.md by adding 'design.md' to docs

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

Added a link from the main README as well.


release-1.1: backported changes

https://github.com/bitnami/kube-prod-runtime/pull/388
https://github.com/bitnami/kube-prod-runtime/pull/355

bors r+


Please add information about the possibilities or lack of possibilities to set or influence access keys

Can the access keys be set in any way either using a function or directly writing a field/property? Is it for example possible that we set our own access key instead of a generated one? Use cases would be for example systems/applications that do not support 512-bit passwords or in cases where the key rotation was accidental and needs to be reversed.

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

ID: 3463d1c7-f458-738a-2317-b756a1be7de0
Version Independent ID: 40f9e40a-0f2f-f510-7ee4-39e55158c99e
Content: Manage account access keys - Azure Storage
Content Source: articles/storage/common/storage-account-keys-manage.md
Service: storage
GitHub Login: @jimmart-dev
Microsoft Alias: jammart

@picotron84
Thanks for your feedback! We will investigate and update as appropriate.

@picotron84
Azure Storage access key
When we create a storage account, Azure generates and assigns two 512-bit storage access keys to the account. These keys are required for authentication when accessing the storage account. Two access keys are generated, one is the primary access key, and another is the secondary access key. Remember, these keys can be regenerated whenever required. When you generate a new key, the earlier ones are retired.
Use access keys to authenticate your applications when making requests to this Azure storage account. Store your access keys securely - for example, using Azure Key Vault - and don't share them. We recommend regenerating your access keys regularly. You are provided two access keys so that you can maintain connections using one key while regenerating the other.
When you regenerate your access keys, you must update any Azure resources and applications that access this storage account to use the new keys. This action will not interrupt access to disks from your virtual machines.
Note: If you provide the access key to the client, customer or any one it's like giving complete access to the Storage account( root password) It's not recommend to give to others.
Always be careful to protect your access keys. Use Azure Key Vault to manage and rotate your keys securely. Avoid distributing access keys to other users, hard-coding them, or saving them anywhere in plain text that is accessible to others. Rotate your keys if you believe they may have been compromised.
Instead of giving Access key to other, please provided SAS key --> Shared Key authorization : https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview , This article provides complete detailed information how to access SAS for clients with ceratin duration, time and access level.
Microsoft recommends using Azure Active Directory (Azure AD) to authorize requests against blob and queue data if possible, instead of Shared Key. Azure AD provides superior security and ease of use over Shared Key. For more information about authorizing access to data with Azure AD, see Authorize access to Azure blobs and queues using Azure Active Directory.
Azure storage connection string : A connection string includes the authorization information required for your application to access data in an Azure Storage account at runtime using Shared Key authorization. You can configure connection strings to:
Connect to the Azure storage emulator.
Access a storage account in Azure.
Access specified resources in Azure via a shared access signature (SAS).
For more information, refer to this article
If you look in the Azure portal under the storage account in question, and look in the "Access Keys" item in the left-side nav, there it shows you the two provided keys and the entire connection string needed to access the storage account.
Reason for two keys? it's to avoid downtime. let's say, if you had only one key and used it multiple places. Suddenly you had to share it to someone for some reason. So, you might need to regenerated this key(As you have already shared it) and update it in all places where you used it previously. So, to avoid this, we have secondary key, which you can share and regenerate it so that, primary key will be still valid.
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@picotron84
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


fix: Use fully qualified module names

This PR fixes an issue that manifests in projects that use newer versions of Webpack:
ERROR in ../trystero/src/index.js 4:0-45

Module not found: Error: Can't resolve './torrent' in '/home/project_path/node_modules/trystero/src'
Did you mean 'torrent.js'?
BREAKING CHANGE: The request './torrent' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

A similar issue is described in solana-labs/wallet-adapter#200, but manifests in Trystero as well. Among other things, this change will make Trystero compatible with Create React App version 5 (the latest version).
I also added a .gitignore so that node_modules is not tracked by Git.

Thanks for the PR @jeremyckahn. I'm a little confused as to why this change is necessary on Trystero's side and what upstream is throwing that error. Is this a Webpack-specific issue? I'm hesitant to make this change since it would imply all my other JS projects will need to update all of their import statement to fully qualified, but I haven't seen any guidance  on that being a new standard. Do you have any more info?

Is this a Webpack-specific issue?

Yes. This is the Webpack configuration rule that is responsible for this behavior: https://webpack.js.org/configuration/module/#resolvefullyspecified. I've seen this issue reported in a number of other places, such as:

https://github.com/facebook/create-react-app/issues/11865.
https://github.com/graphql/graphql-js/issues/2721
https://stackoverflow.com/questions/69427025/programmatic-webpack-jest-esm-cant-resolve-module-without-js-file-exten
https://community.redwoodjs.com/t/syntaxerror-cannot-use-import-statement-outside-a-module/3636

In general, the recommended solutions seem to involve tweaking the consuming project's Webpack config as such:
{
  test: /\.m?js/,
  resolve: {
    fullySpecified: false,
  },
}

However, in an un-ejected Create React App 5 project, that doesn't seem possible to achieve at the moment because the Webpack configuration is abstracted away.
Short of ejecting from Create React app and making the suggested Webpack configuration change, the best solution seems to be making changes to upstream projects like the one in this PR. It is frustrating that Webpack and Create React App collectively made this breaking change, but I'm not sure what a better solution for Create React App projects would be.

@dmotz what do you think about the solution that's offered here? Is there anything you'd like to see changed before it can be merged?

In case it's helpful, the issue that this PR fixes is now manifesting in my other Create React App-based project that uses Trystero. Here's a recent example of a breakage introduced by an automated Dependabot version update:

PR: https://github.com/jeremyckahn/farmhand/pull/322
Breaking CI build: https://vercel.com/jeremyckahn/farmhand/9JUE14qfL8u66AhT2Zb7UaShi3Le

...
[11:30:47.283] > react-scripts build
[11:30:47.283]
[11:30:49.141] Creating an optimized production build...
[11:30:58.986] Failed to compile.
[11:30:58.986]
[11:30:58.987] Module not found: Error: Can't resolve './torrent' in '/vercel/path0/node_modules/trystero/src'
[11:30:58.987] Did you mean 'torrent.js'?
[11:30:58.987] BREAKING CHANGE: The request './torrent' failed to resolve only because it was resolved as fully specified
[11:30:58.987] (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
[11:30:58.987] The extension in the request is mandatory for it to be fully specified.
[11:30:58.987] Add the extension to the request.

It seems that others who use Trystero with Create React App will likely experience this issue unless some kind of solution is implemented.

Sorry for the wait on this, I've been busy. I merged this and published a new version (0.11.2) to npm. This still looks like a CRA problem to me caused by a Webpack strictness quirk, but I'm curious if full qualified import paths are expected for all frontend libraries going forward.

No worries! I appreciate you following up with a merge and release. I agree that this is something that CRA should fix by addressing https://github.com/facebook/create-react-app/issues/11865, but until then downstream PRs like this seem like the most sensible workaround.

I'm curious if fully qualified import paths are expected for all frontend libraries going forward.

Me too. I haven't seen documentation either way regarding this.


update for Laravel 6

Really helpful package!
Too late to find this package..
Could you update this package for Laravel 6 ? Thanks😊

updated.


Update Gradle wrapper to 3.1

This updates Gradle wrapper to 3.1, and also increases the maximum Gradle daemon heap space which allows dex to run in process, speeding up the build.

Thanks!


Any chance to create the window in main.rs?

I'm trying to create a window in main.rs instead of specifying it in tauri.conf.json but the app crashes when I open it from the tray. The reason I'm doing this is because I'm trying to use the localhost plugin which will allow me to log in to some site that won't allow non http(s) protocols/schemes. It seems like the react app is not initialized (shows blank page when I make it visible).
Platform Tested: MacOS Ventura, M1
This is what I got:
main.rs:
// Prevents additional console window on Windows in release, DO NOT REMOVE!!
#![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]

mod command;
mod fns;
mod tray;

use tauri::{Manager, webview::WebviewWindowBuilder, WebviewUrl};
use tauri_nspanel;

fn main() {
    let port: u16 = 9527;

    tauri::Builder::default()
        .invoke_handler(tauri::generate_handler![
            command::init,
            command::show_menubar_panel
        ])
        .plugin(tauri_nspanel::init())
        .plugin(tauri_plugin_localhost::Builder::new(port).build())
        .setup(move |app| {
            app.set_activation_policy(tauri::ActivationPolicy::Accessory);

            let app_handle = app.app_handle();

            tray::create(&app_handle)?;

            let url = format!("http://localhost:{}", port).parse().unwrap();
            WebviewWindowBuilder::new(app, "main".to_string(), WebviewUrl::External(url))
                .title("menubar")
                .fullscreen(false)
                .resizable(false)
                .decorations(false)
                .transparent(true)
                .visible(true)
                .build()?;

            Ok(())
        })
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

tauri.conf.json:
{
  "build": {
    "beforeDevCommand": "npm run dev",
    "beforeBuildCommand": "npm run build",
    "frontendDist": "../dist",
    "devUrl": "http://localhost:1420"
  },
  "bundle": {
    "active": true,
    "targets": "all",
    "icon": [
      "icons/32x32.png",
      "icons/128x128.png",
<EMAIL_ADDRESS>      "icons/icon.icns",
      "icons/icon.ico"
    ]
  },
  "productName": "tauri-macos-menubar-app-example",
  "version": "0.2.0",
  "identifier": "com.example.dev",
  "plugins": {},
  "app": {
    "security": {
      "csp": null
    },
    "macOSPrivateApi": true
  }
}

Thanks in advance.

I think the issue was because I didn't unwrap the window


[rust] Reduce number of allocations

Use fxhash crate directly with the HashMap from std so we can set an initial capacity.

Hey, I'm in the process of switch the VM from azure to aws c7a.xlarge which is more powerful and modern CPU. This is slower on the new machine.
 Can you confirm that what you posted above for "main" is indeed a fresh run from clean main head on c7a.xlarge? With Rust 1.74/1.73 I get ~21ms for 5k for main. With optimizations I get 15.6ms.

Here is a fresh run:
Rust:

        Processing time (w/o IO): 16.110144ms
        total: 0.02s memory: 12416k
        Processing time (w/o IO): 16.424593ms
        total: 0.03s memory: 12288k
        Processing time (w/o IO): 16.130734ms
        total: 0.04s memory: 12416k
        Processing time (w/o IO): 16.436733ms
        total: 0.03s memory: 12416k
        Processing time (w/o IO): 16.369473ms
        total: 0.02s memory: 12544k
        Processing time (w/o IO): 16.074224ms
        total: 0.02s memory: 12416k
        Processing time (w/o IO): 16.015375ms
        total: 0.02s memory: 12416k
        Processing time (w/o IO): 16.480684ms
        total: 0.02s memory: 12416k
        Processing time (w/o IO): 18.177838ms
        total: 0.02s memory: 12544k
        Processing time (w/o IO): 17.46669ms
        total: 0.02s memory: 12416k

Rust:

        Processing time (w/o IO): 231.80284ms
        total: 0.29s memory: 35536k
        Processing time (w/o IO): 239.382938ms
        total: 0.30s memory: 35408k
        Processing time (w/o IO): 235.18608ms
        total: 0.30s memory: 35540k

Rust:

        Processing time (w/o IO): 2.088027485s
        total: 2.33s memory: 119164k
        Processing time (w/o IO): 2.057614801s
        total: 2.29s memory: 119164k
        Processing time (w/o IO): 2.038391585s
        total: 2.28s memory: 102684k

This is the old run used for the leaderboard:
https://github.com/jinyus/related_post_gen/blob/636cf10a96209ef457da0ede37067a33b7fa62c4/raw_results.md?plain=1#L55

> uname -a
Linux ip-172-xxxx-aws #12~22.04.1-Ubuntu SMP Thu Sep  7 14:01:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

> cat /proc/cpuinfo | grep model
model           : 17
model name      : AMD EPYC 9R14
model           : 17
model name      : AMD EPYC 9R14
model           : 17
model name      : AMD EPYC 9R14
model           : 17
model name      : AMD EPYC 9R14

> sudo docker run -it --rm databench bash
[root@51460ba4e95b app]# rustc --version
rustc 1.74.0 (79e9716c9 2023-11-13)

@cloneable Let's see your rustc verison
I would like to see your numbers in docker. Here is a single command to install docker and run the test:
sudo apt update &&
    sudo apt install -y apt-transport-https ca-certificates curl software-properties-common &&
    curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg &&
    echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list >/dev/null &&
    sudo apt update &&
    apt-cache policy docker-ce &&
    sudo apt install -y docker-ce &&
    sudo docker pull ghcr.io/jinyus/databench:latest &&
    sudo docker tag ghcr.io/jinyus/databench databench &&
    sudo docker run -it --rm -e TEST_NAME=rust databench

Thank you! That works. Now I get similar numbers.


Missing java.util.BitSet

It would be useful to have a java.util.BitSet implementation. It looks like most Java collections are available but this one fell through the cracks (perhaps because it's not part of the Collection hierarchy).

There is a PR https://github.com/scala-js/scala-js/pull/4217 but it has stalled. Would you like to pick it up?

@sjrd I'd be interested in picking this up. I'm wondering how best to copy over the work that's already been done, though.

Whatever you see fit. You can fetch the PR branch and rebase, or just create a new branch from master and manually copy paste. It doesn't matter. In the end we'll need a squashed commit sitting in top of a recent commit from master anyway.
It would probably be nice of you too include the appropriate Co-Authored-By line in the commit message.

Whatever you see fit. You can fetch the PR branch and rebase, or just create a new branch from master and manually copy paste. It doesn't matter. In the end we'll need a squashed commit sitting in top of a recent commit from master anyway.
It would probably be nice of you too include the appropriate Co-Authored-By line in the commit message.

Sounds like a plan

@jyoo980 I just updated the PR

Fixed in c0be6b6bb7e579ae6381648673a8faac1386ecf6


Update readability.js

Return document tree of jsdom as well, so user won't need to load another jsdom instance if he need to get another data from page

Thank you.

Thanks. would you please update it's version, so I can see this change in npm too?

I have updated the version to 0.1.3, thank you for you contribution.

Actually, this program is still worthy of improvement, where it could not throw an exception when fail to extract the main content. I'm right busy recently, if you someone could help, that's was really good.

I don't know what's wrong bug npm is not updated yet


[WIP] GitHub actions

@blueyed have you tried GitHub actions? :)

Looks nice.  However at least with https://github.com/jazzband/pip-tools/pull/875/checks?check_run_id=195390732 there's an error:
  tox -e pipmaster
  shell: /bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.7.4/x64
GLOB sdist-make: /home/runner/work/pip-tools/pip-tools/setup.py
pipmaster create: /home/runner/work/pip-tools/pip-tools/.tox/pipmaster
pipmaster installdeps: -egit+https://github.com/pypa/pip.git@master#egg=pip, mock, pytest
pipmaster inst: /home/runner/work/pip-tools/pip-tools/.tox/.tmp/package/1/pip-tools-4.0.1.dev17+gc8ca9be.zip
pipmaster installed: atomicwrites==1.3.0,attrs==19.1.0,Click==7.0,importlib-metadata==0.19,mock==3.0.5,more-itertools==7.2.0,packaging==19.1,pip-tools==4.0.1.dev17+gc8ca9be,pluggy==0.12.0,py==1.8.0,pyparsing==2.4.2,pytest==5.1.0,six==1.12.0,wcwidth==0.1.7,zipp==0.5.2
pipmaster run-test-pre: PYTHONHASHSEED='617537163'
pipmaster run-test-pre: commands[0] | pip --version
pip 19.3.dev0 from /home/runner/work/pip-tools/pip-tools/.tox/pipmaster/src/pip/src/pip (python 3.7)
pipmaster run-test: commands[0] | pytest
ImportError while loading conftest '/home/runner/work/pip-tools/pip-tools/tests/conftest.py'.
tests/conftest.py:10: in <module>
    from piptools._compat import (
piptools/_compat/__init__.py:7: in <module>
    from .pip_compat import (
piptools/_compat/pip_compat.py:37: in <module>
    is_vcs_url = do_import("download", "is_vcs_url")
piptools/_compat/pip_compat.py:24: in do_import
    return getattr(imported, package)
E   AttributeError: module 'pip._internal.download' has no attribute 'is_vcs_url'
ERROR: InvocationError for command /home/runner/work/pip-tools/pip-tools/.tox/pipmaster/bin/pytest (exited with code 4)
___________________________________ summary ____________________________________
ERROR:   pipmaster: commands failed

Looks nice. However at least with https://github.com/jazzband/pip-tools/pull/875/checks?check_run_id=195390732 there's an error:

Do you mean it should be failed check?

@atugushev
Sure.

@atugushev
It should not fail in the first place (since it was not failing before), but when it fails it should report the status correctly, of couse.

Yeah, right. That’s because of continue-on-error. Couldn’t  find a way to set correct (neutral?) check status.

Close this for now. In general, it looks good to me, but, unfortunately, there is no way to set up allow_failures (continue-on-error works slightly different).


Update React Scripts

Ran into a bug during testing, found the solution has been fixed in the latest Jest following this.
The current version that we're using of react-scripts uses the old Jest v20.
But when React Scripts 2.0 is released it'll have Jest v22 and we can make the fix.
I know there are some bots that will auto-submit outdated dependencies as issues on our board, but I feel like that'd be a bit much. Maybe there's a Slackbot that could post them to a dedicated BarTop channel so we don't have to waste time tracking stuff down that would be fixed with a dependency bump 😄

Seconded on this. Was trying to test some throws and its quite annoying without this feature working.


More defensive coding against missing APIs on Windows 7 and ARM64

See https://github.com/timsneath/win32/runs/1645786081?check_suite_focus=true:
00:00 +6 -1: test\api_test.dart: Test kernel32 functions Can instantiate ClosePseudoConsole [E]
  Invalid argument(s): Failed to lookup symbol (127)
  dart:ffi            DynamicLibrary.lookup
  test\api_test.dart  main.<fn>.<fn>

00:00 +10 -2: test\api_test.dart: Test kernel32 functions Can instantiate CreatePseudoConsole [E]
  Invalid argument(s): Failed to lookup symbol (127)
  dart:ffi            DynamicLibrary.lookup
  test\api_test.dart  main.<fn>.<fn>

00:00 +56 -3: test\api_test.dart: Test kernel32 functions Can instantiate IsWow64Process2 [E]
  Invalid argument(s): Failed to lookup symbol (127)
  dart:ffi            DynamicLibrary.lookup
  test\api_test.dart  main.<fn>.<fn>

00:00 +66 -4: test\api_test.dart: Test kernel32 functions Can instantiate ResizePseudoConsole [E]
  Invalid argument(s): Failed to lookup symbol (127)
  dart:ffi            DynamicLibrary.lookup
  test\api_test.dart  main.<fn>.<fn>

00:00 +201 -5: test\api_test.dart: Test user32 functions Can instantiate GetSystemDpiForProcess [E]
  Invalid argument(s): Failed to lookup symbol (127)
  dart:ffi            DynamicLibrary.lookup
  test\api_test.dart  main.<fn>.<fn>

00:19 +503 -6: test\winmd_test.dart: Find a specific WinMD token [E]
  Expected: <33554435>
    Actual: <33554490>

  package:test_api           expect
  test\winmd_test.dart 25:7  main.<fn>

Open question: is the right solution to disable these tests on older Windows versions? Or to fail differently on those versions?
My thinking:

We do want to support (and test on) older versions of Windows, in particular Windows 7 and Windows Server 2016
We shouldn't add a version check in each API call wrapper (that's expensive).
We could catch the exception in each wrapper, but it's unclear that we'd do much different than throw an exception.
We could add a minVersion check on each API that is not present on Windows 7

Open question: is the right solution to disable these tests on older Windows versions? Or to fail differently on those versions?
My thinking:

We do want to support (and test on) older versions of Windows, in particular Windows 7 and Windows Server 2016
We shouldn't add a version check in each API call wrapper (that's expensive).
We could catch the exception in each wrapper, but it's unclear that we'd do much different than throw an exception.
We could add a minVersion check on each API that is not present on Windows 7

Now fixed for Windows Server 2016, with tests enabled in GitHub Actions. Win7 (32-bit) and Win10 (ARM) will both need some extra work.

Now fixed for Windows Server 2016, with tests enabled in GitHub Actions. Win7 (32-bit) and Win10 (ARM) will both need some extra work.

I'm told that ARM64 works fine on native hardware, although I see a failure to load bthprops.cpl on an Apple M1 via Parallels. Might be the limitations of that platform's emulator, however.

I'm told that ARM64 works fine on native hardware, although I see a failure to load bthprops.cpl on an Apple M1 via Parallels. Might be the limitations of that platform's emulator, however.


Fix typo: MultipleInputQuestion

You've got a typo in your definitions.
I've changed all occurrences in this PR.

Thanks for the contribution! We're currently working on the alignment of the ontology to other vocabularies, if you have any feedback to improve the ontology feel free to contact us or open an issue in the repository


[SPARK-5093] Set spark.network.timeout to 120s consistently.

Test build #25063 has started for   PR 3903 at commit 7c2138e.

This patch merges cleanly.

Test build #25063 has finished for   PR 3903 at commit 7c2138e.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
              SparkSubmit.printErrorAndExit(s"Cannot load main class from JAR $primaryResource")
class BinaryClassificationMetrics(

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25063/
Test PASSed.

LGTM

Thanks. Merging in master.


ARROW-4645: [C++/Packaging] Ship Gandiva with OSX and Windows wheels

crossbow builds:

kszucs/crossbow/build-448

Code looks good, but the crossbow tasks fail

Maybe so. How are the Windows and macOS wheels for numba built?

There are special conda recipes in llvmlite that don't use the defaults/conda-forger compiler toolchains: https://github.com/numba/llvmlite/tree/master/conda-recipes

Can We depend on the llvmlite wheel as well?

llvmlite doesn't ship the "raw" LLVM libraries so I don't think that helps

OSX wheels working now, I'm trying llvmdev for windows.

Crossbow builds: kszucs/crossbow/build-488

Codecov Report

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

@@             Coverage Diff             @@
##           master    #3832       +/-   ##
===========================================
- Coverage   87.84%   64.48%   -23.37%
===========================================
  Files         734      350      -384
  Lines       90423    51273    -39150
  Branches     1252        0     -1252
===========================================
- Hits        79430    33061    -46369
- Misses      10876    18212     +7336
+ Partials      117        0      -117

Impacted Files
Coverage Δ

cpp/src/arrow/util/memory.h
0% <0%> (-100%)
:arrow_down:

cpp/src/parquet/hasher.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/extension_type.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/util/sse-util.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/json/chunker.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/util/uri.cc
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/compute/logical_type.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/compute/operation.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/compute/operations/cast.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/compute/operations/literal.h
0% <0%> (-100%)
:arrow_down:

... and 556 more

Continue to review full report at Codecov.

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

kszucs/crossbow/build-493

kszucs/crossbow/build-496

kszucs/crossbow/build-502

@kou the build should pass now kszucs/crossbow/build-523

kszucs/crossbow/build-530

kszucs/crossbow/build-536

wheel-win-cp35m and wheel-win-cp36m on AppVeyor are failed:

https://ci.appveyor.com/project/kou/crossbow/builds/23383931
https://ci.appveyor.com/project/kou/crossbow/builds/23383928

I don't look into them yet but they may be related to this.

https://issues.apache.org/jira/browse/ARROW-5025


add: format parameters

Added new formatting options that allow you to change the output
:lower :upper :title :capitalize.
It can be used with
{{name :upper:empty:remove:list}}
or without triggers
{{name :upper}}

@8thgencore tests should pass, then we can go further.

@8thgencore tests should pass, then we can go further.

update code

Added tests and moved to https://github.com/bobiverse/docxplate/pull/37


Initial implementation of telemetry store watermill middleware

This is a simple initial implementation of the middleware for logging
telemetry store data.
closes: #1879

One thing to note about this implementation is that yet again it parses the entity from the Watermill message. I think at this point we can have a separate middleware to do this parsing once and set it in the message's Context. But I rather leave this optimization for a separate PR.

Looks good! let me know when this is out of draft so I can ack

Thanks for the test! This looks close enough to iterate on later in the codebase if you want, or you can address the "why not use the logger from context" now if you prefer. (In fact, it may be that the logger adapter already adds some of the fields we need, I'm not sure...)

I think your comments are valid, but my 2c is to merge the PR quickly so I can propose mine over it (I did a local rebase this afternoon and there appeared a wild import loop, so I'd rather get all the pieces into main..)

I'll get this merged and address the comments on separate PRs


Support for HDR videos

I noticed it doesn't support HDR or 4k videos. Any way to get that working with react-player?

bump

bump

Hi, ok this is a react wrapper over the browser native player or other players (e.g. youtube, vimeo etc via their own libraries). This library doesn't play anything, its function/purpose is to wrap a player.
The question now is what do you expect to play an HDR or 4k video, that this library is supposed to wrap?


Current Rasa for Botfront has critical bug in intent recognition

The currently available release of Botfront has a severe bug in the intent recognition, that makes Rasa completely unusable. We experienced the bug, when upgrading from v1.1.7-bf.4 to v1.3.3-bf.6. The intent recognition's accuracy of our test instances dropped below 30%. It turns out, that the confidence is somehow impacted and returns the same confidence value for a lot of intents.
I skimmed through the changelogs / PRs and issues of Rasa and finally found the related isssue: https://github.com/RasaHQ/rasa/issues/4573
The related PR with a bugfix has been merged: https://github.com/RasaHQ/rasa/pull/4581
Long story short: The current v1.3.3-bf.6 can not be used. Upgrading Rasa to v1.3.9 or manually applying the patch of the PR to the current 1.3.3 version should resolve the issue.

@pheel dire 1.3.9 fix the CORS issue that made us roll back to 1.3.3?

Not quite sure, which CORS issues appeared in your case, but there where a few fixes on that front too: https://github.com/RasaHQ/rasa/pull/4521 (https://github.com/RasaHQ/rasa/issues/4459)

Stay tuned for 1.3.9-bf.1!

https://github.com/botfront/rasa-for-botfront/releases/tag/v1.3.9-bf.1

@pheel: Unfortunately I cannot confirm the issues being resolved with the changes of v1.3.9-bf.1. I tested the following setup / versions and the issue does still occur:
rasa-for-botfront:v1.3.9-bf.1
botfront:v0.16.4
botfront-api:v0.16.3

The plain Rasa (without BF patches) seems to work flawlessly in comparison.

The bugfix you mentioned earlier has been merged into the fork's codebase.
cf. https://github.com/botfront/rasa-for-botfront/commit/d19861a33dee58320c056473c01200eca0d10027 <= https://github.com/RasaHQ/rasa/commit/d19861a33dee58320c056473c01200eca0d10027
Most likely the problems you're encountering are due to something else. Can you share some more details?

Yeah, I already checked the source files and the issue should be gone. Nonetheless, it still seems to appear in our case. We have several intents with the following naming scheme faq.foobar.1, faq.foobar.2, faq.foobar.3. The feature at least 2 example utterances that are quite distinctive. The training runs smoothly and the intent recognition for all other intent works flawlessly. But as soon as I put in an utterance from the faq.foobar.* intents, the confidence values are messed up: All intents starting with faq.foobar.* have the very same confidence. The F1 score drops below 40% and the model is unusable.
I tested the very same training data with the plain Rasa image. In v1.3.8, I was easily able to reproduce the behavior, whereas v1.3.9 seems to resolve the issue properly. Unfortunately, I am not able to validate this with the Botfront-Rasa images, as I can't train directly from the CLI (an exception about the nlu_config,... is thrown).

@beevelop can you paste the content of the .botfront/botfront.yml file?
If the Rasa image is the right one, we could try to repro the issue if you share a dataset/pipeline with us (hi_at_botfront.io)

@beevelop I'll look into this some more, but for the moment it seems like the bug only happens if your digit is directly preceded by a period. What is puzzling is that you don't have the same bug with vanilla 1.3.9...

At first face the problem doesn't seem to come from CountVectorsFeaturizer...

Yep, I already tested the very same configuration with Vanilla Rasa: In 1.3.9 the issue does definitely not appear anymore. Whereas 1.3.8 seems to be affected by the behaviour described in the CountVectorsFeaturizer bug.
It seems to be the combination of a dot followed by a digit. If we replace the digits in the intent naming, the issue is gone.

Yep, sounds like something to report over at RasaHQ! Good find.

Is this issue resolved??


Tauri updater feature - to handle version updates distribution.

What we want in ideal scenario is:

when the app starts, it should check for updates
if there are no updates, it shall continue as normal
if there is an update present, it should prompt the user for whether they want to upgrade their software
if the user approves, it shall update itself via downloading and auto-starting the installer
if the user declines, it shall continue as normal

@ozgunozerk I think we should also query if there is an update periodically because users might start the app only once and let it run for weeks until they face an issue

Yes, let me edit the above list, thank you!

As for the update server, we can use gist (it may look like this), but if we have tens of thousands of users it could become a bottleneck, especially if we query periodically (not just on launch), so we would probably need a proxy. @nazar-pc what do you think?

I think it would be preferred to either keep it in the repo or even in a separate S3 bucket or something that is automatically kept up to date.
We could also automate things by pushing into custom branch like it is used with gh-pages for statically generated HTML.

I think periodic in our case means once per hour of a few times per day, right?

I think so, 1-2 times per day should be enough

I think so, 1-2 times per day should be enough

Periodic updates should be no issue, the built in tauri updater has a events function to listen for new updates https://tauri.app/v1/guides/distribution/updater#events

we show update dialog on launch
we check new updates and show same dialog if there is a newer version

Probably we also need smth like "Install update" button in the settings dropdown (in case the user closed the dialog previously)


Yatin: Watch complete[\W_]+vision[\W_]+formula

Yatin requests the watch of the watch_keyword complete[\W_]+vision[\W_]+formula. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

complete[\W_]+vision[\W_]+formula has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Update bower.json

Updating the angular to latest version and iframe-resizer to the latest available at this time

Are there no breaking changes to iframe-resizer?

My intention to upgrade iframe-resizer. Also upgraded angular


feat: (IAC-403): Update AzureRM Terraform provider version

Changes:
Upgrade azurerm provider version from 2.62.0 to 3.21.1. Followed the upgrade document 3.0-upgrade-guide
Tests:
Following Scenarios were verified. Cluster creation was successful for all the scenarios. See internal ticket for details.

All defaults
Azure monitor enabled: create_aks_azure_monitor = true
create_container_registry = true, container_registry_sku = "Premium" and container_registry_geo_replica_locs = ["eastus", "southcentralus"]
create_container_registry = true, container_registry_sku = "Premium", container_registry_geo_replica_locs = null
default_nodepool_availability_zones = ["1","2"]

Minor doc update that can also be included with this change:
https://github.com/sassoftware/viya4-iac-azure/blob/IAC-403/README.md?plain=1#L121
The link to the azurerm kubernetes cluster doc is currently invalid, just need to remove the '.html' part from the end

Minor doc update that can also be included with this change: https://github.com/sassoftware/viya4-iac-azure/blob/IAC-403/README.md?plain=1#L121 The link to the azurerm kubernetes cluster doc is currently invalid, just need to remove the '.html' part from the end

Done


Add support for RDF feeds

Steps to Reproduce

Press Add Feed button
Add the link: "https://distrowatch.com/news/dww.xml"
Couldn't find feed

Expected behavior
Feed be added and loaded
Also, when I put only the website it gives me some feeds to add but not all of them.
Screenshots or screen recording

Device, Operating system, and app version
Lenovo Tab P11 Plus, Android 12, 2024.08.1028-dev

Thanks for the link @goliv04053. That feed isn't showing up because it's an RDF feed, not an RSS feed. The library I use to fetch feeds doesn't support RDF. I'll see if I can add it.

@goliv04053 RDF support is added in the latest version, 2024.08.1034-dev. There's some table formatting I want to add to make this distrowatch feed work with full content mode. That will be added with https://github.com/jocmp/capyreader/pull/294.
Please reopen this if you run into any issues adding this feed.


Add support for a=keywds

a=keywds is specified in RFC4566.
It is a session-level attribute.
The example SDP file was generated by a Glensound AoIP44 in AES67 mode, which has a Dante Ultimo X4 chipset.
Note that the SDP also contains the following two lines. I will raise a further PR to add support for them:
a=ts-refclk:ptp=IEEE1588-2008:00-00-00-FF-FE-00-00-00:0
a=mediaclk:direct=3560866135

Full SDP in Gist here:
https://gist.github.com/njh/90e8b7f44f5c79a76a5e12cc922220c6

Sorry, I completely missed this! Reviewing now!

Released in<EMAIL_ADDRESS>Thank again.

Thanks! 👍


alertmanager container fails to start with ansible-2.9.12

Bug Report
Tried deploying TripleO(which uses ceph-ansible to deploy ceph services) with ansible-2.9.12 https://review.rdoproject.org/r/#/c/28996/ but alertmanager container is not able to start. It's due to ansible-2.9.12 made the file permissions strict[1] and now "mode" needs to be specified explicitly, alertmanger.yml create task[2] doesn't have "mode" defined so permissions are set to 600 instead of 666 as in earlier ansible versions.
Warning is also reported for /etc/prometheus/prometheus.yml but issue not seen in it as "owner" is set[3] and it has read permission.
[1] https://github.com/ansible/ansible/commit/0199b1cf05e1838bc65ac26d99f2c5505c24ad0f
[2] https://github.com/ceph/ceph-ansible/blob/622d9feae924b216d02fc10a90c5a2089ab98794/roles/ceph-prometheus/tasks/main.yml#L41-L45
[3] https://github.com/ceph/ceph-ansible/blob/622d9feae924b216d02fc10a90c5a2089ab98794/roles/ceph-prometheus/tasks/main.yml#L15
What you expected to happen:
Deployment should succeed with ansible-2.9.12.
How to reproduce it (minimal and precise):

A deployment of alertmanager with ansible-2.9.12 should reproduce it.
Share your group_vars files, inventory and full ceph-ansibe log
Log link:- https://logserver.rdoproject.org/96/28996/1/check/rdoinfo-tripleo-master-testing-centos-8-scenario004-standalone/e13825e/logs/undercloud/home/zuul/standalone-ansible-0ofy65b3/ceph-ansible/ceph_ansible_command.log.txt.gz
Pasting relevent warnings from log here:-
[WARNING]: File '/etc/prometheus/prometheus.yml' created with default permissions '600'. The previous default was '666'. Specify 'mode' to avoid this warning.
[WARNING]: File '/etc/alertmanager/alertmanager.yml' created with default permissions '600'. The previous default was '666'. Specify 'mode' to avoid this warning.
Environment:

OS (e.g. from /etc/os-release): CentOS-8
Kernel (e.g. uname -a): Linux ykarel-ansible-debug.localdomain 4.18.0-147.3.1.el8_1.x86_64 #1 SMP Fri Jan 3 23:55:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Docker version if applicable (e.g. docker version): Using podman-1.6.4-10.module_el8.2.0+305+5e198a41.x86_64
Ansible version (e.g. ansible-playbook --version): 2.9.12
ceph-ansible version (e.g. git head or tag or stable branch): ceph-ansible-4.0.25-1.el8.noarch
Ceph version (e.g. ceph -v): docker.io/ceph/daemon:v4.0.8-stable-4.0-nautilus-centos-7-x86_64

Caused by https://github.com/ansible/ansible/issues/71200