Get error when make custom post

Cause I want to save some cookies and make Custom UserAgents, I've followed this issue , and made a custom manager like this
    var cfg = NSURLSessionConfiguration.defaultSessionConfiguration()
    var cookies = NSHTTPCookieStorage.sharedHTTPCookieStorage()
    cfg.HTTPCookieStorage = cookies
    cfg.HTTPCookieAcceptPolicy = NSHTTPCookieAcceptPolicy.Always
    cfg.HTTPAdditionalHeaders = ["Accept-Encoding": "gzip;q=1.0,compress;q=0.5",
        "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36", "Accept-Language":"zh-CN,zh;q=0.8,en;q=0.6,zh-TW;q=0.4"]
    var mgr = Alamofire.Manager(configuration: cfg)
    var parameters:[String:AnyObject] = [
        "foo":"bar"
    ]
    var req:Request = mgr.request(.POST, "http://httpbin.org/post", parameters: parameters).responseString { (req, res, string:String?, err:NSError?) -> Void in
    }

when I use this manager to make get requests, it's ok, but when it make post requests like above, it always get NSURLError, which error code is -999.
Error Domain=NSURLErrorDomain Code=-999 "cancelled" UserInfo=0x79f6d440     {NSErrorFailingURLKey=http://httpbin.org/post, NSErrorFailingURLStringKey=http://httpbin.org/post,     NSLocalizedDescription=cancelled}

I have the same problem. Did you find a solution?

@mattt wrote up a good answer here. If the manager is not retained, the running task is cancelled while the underlying NSURLSession is being shut down. That is most likely your issue. If that does not fix it, please open a new question on Stack Overflow.

After trying all the solutions provided above, my code still fails with same error. For my case, it's because I made too many requests within same session, which exceed the maximum limit (https://developer.apple.com/library/ios/documentation/Foundation/Reference/NSURLSessionConfiguration_class/#//apple_ref/occ/instp/NSURLSessionConfiguration/HTTPMaximumConnectionsPerHost).
Sample code:
let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
configuration.HTTPMaximumConnectionsPerHost = 10   // Some arbitrary number that I feel big enough.
let manager = Alamofire.Manager(configuration: configuration)

I have similar problem.
I uses a custom session manager.
"deinit" does not get called for the custom SessionManager so I believe that I am retaining the session manager properly.
The request looks something like this https://<IP_ADDRESS>/IZLogin.php?password=secret&username=davids
<IP_ADDRESS> is a private ip on a test server behind our firewall
The calling code looks like this
                let sessionManager = credentials.usehttps ? credentials.sessionManager : Alamofire.SessionManager.default
                sessionManager.request(url, method: .get, parameters: param)
                .validate(statusCode: 200..<300)
                .validate(contentType: ["application/xml", "text/xml"])
                .responseString { response in
                    print(url, param)
                    print(response)
                }

public class HTTPSManager : Alamofire.SessionManager {
    deinit {
        print("HTTPSManager deallocated")
    }
    fileprivate convenience init(credentials: Credentials) {
        let serverTrustPolicies: [String: ServerTrustPolicy] = [
            credentials.ipwithport: .pinCertificates(
                certificates: ServerTrustPolicy.certificates(),
                validateCertificateChain: false,
                validateHost: true
            ),
            "insecure.expired-apis.com": .disableEvaluation
        ]
        let configuration = URLSessionConfiguration.default
        configuration.httpAdditionalHeaders = Alamofire.SessionManager.defaultHTTPHeaders

        self.init(configuration: configuration, serverTrustPolicyManager: ServerTrustPolicyManager(policies: serverTrustPolicies))
    }
}

// This is a stripped down version of the Credentials class so you get the idea
public class Credentials  {
    private(set) var ipwithport: String
    private var _SessionManager: HTTPSManager? = nil
    var sessionManager: HTTPSManager {
        get {
            if nil == _SessionManager { _SessionManager = HTTPSManager(credentials: self) }
            return _SessionManager!
        }
    }
}

// Here is the console output for this call
[[Request]: https://<IP_ADDRESS>/IZLogin.php?password=secret&username=davids
[Response]: nil
[Data]: 0 bytes
[Result]: FAILURE: Error Domain=NSURLErrorDomain Code=-999 "cancelled" UserInfo={NSErrorFailingURLKey=https://<IP_ADDRESS>/IZLogin.php?password=secret&username=davids, NSErrorFailingURLStringKey=https://<IP_ADDRESS>/IZLogin.php?password=secret&username=davids, NSLocalizedDescription=cancelled}
[Timeline]: Timeline: { "Request Start Time": 496862619.408, "Initial Response Time": 496862619.875, "Request Completed Time": 496862619.875, "Serialization Completed Time": 496862619.875, "Latency": 0.467 secs, "Request Duration": 0.467 secs, "Serialization Duration": 0.000 secs, "Total Duration": 0.467 secs }]

Any help would be appreciated. Thanks.

Sorry about not putting this on StackOverflow. Search engines send me here first. I updated my class to be
public class HTTPSManager : Alamofire.SessionManager {
    deinit {
        print("HTTPSManager deallocated")
    }
    fileprivate convenience init(credentials: Credentials) {
        let serverTrustPolicies: [String: ServerTrustPolicy] = [
            credentials.ipwithport: .pinCertificates(
                certificates: ServerTrustPolicy.certificates(),
                validateCertificateChain: false,
                validateHost: true
            ),
            "insecure.expired-apis.com": .disableEvaluation
        ]
        let configuration = URLSessionConfiguration.default
        configuration.httpAdditionalHeaders = Alamofire.SessionManager.defaultHTTPHeaders

        self.init(configuration: configuration, serverTrustPolicyManager: ServerTrustPolicyManager(policies: serverTrustPolicies))

        delegate.sessionDidReceiveChallenge = { session, challenge in
            let disposition = URLSession.AuthChallengeDisposition.useCredential
            let credential = URLCredential(trust: challenge.protectionSpace.serverTrust!)

            return (disposition, credential)
        }
    }
}

This overcomes the -999 error but it doesn't seem like the right answer. It seems like I shouldn't be over riding the session challenge code and I am just not setting up something right or perhaps Alamofire should provide a way for me to set this up properly.
Thanks in advance


Moved deploy-to-staging to PR checks

Purpose of this pull request
This pull request moves the deploy-to-staging step to PR checks so that you can preview on a server first, prior to pushing to production.
@SumoLogic/open-source-collection-team , would you please take a look? I'll also need to configure this in the repo Settings.
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[x] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Won't do


How do you calculate the<EMAIL_ADDRESS>

Hi~
What is the normalization factor when calculating AUC, is it normalized by A or B ?

@sjzcv Hi, it should be normalised by 0.1, within the width of 0.1 and height of 1.


Wellcome Library => Wellcome Collection

It's not the end of the world if this is wrong but would require a full rebuild.


Add Ability for the power of ParseListeners defined out of the model

Create an interface like ParseListener except it is defined outside the model class
Allow @FieldParseable(parseHandler = MyParseHandler.class) to enable custom parsing outside of the model and many kinds
Add this functionality to the @Parseable annotation as well

in master now 1.3.0


Enable CPack

The current build scripts require root access, since LLVM's SPIRV is installed during the build.
This PR enables CPACK, and allows everything to build without root access.
Having packages instead of an install-during-build, helps me keeping my system clean.
Is this something that's acceptable as a change?

Thank you.

The current build scripts require root access, since LLVM's SPIRV is installed during the build.
This PR enables CPACK, and allows everything to build without root access.

I'm not a cmake expert, but this confuses me. Can you elaborate on your use case? It is already possible to install as a non-privileged user as long as the install directory does not require root permissions. Is this e.g. to allow creating a package that would install to system directories as an unprivileged user?

It is already possible to install as a non-privileged user as long as the install directory does not require root permissions

When I'm compiling with the clang as installed by debian, the build script tries to generate files in the clang installation folder. This folder requires root access to write.
So indeed, I'm trying to build a .deb package, but it's the building process that for me requires root access.
As far as I can see, it is the default behaviour of ExternalProject_Add() to perform and install command of that project during the build step of the main archive.
I'm not a cmake expert either, so this is my best attempt at addressing that, but I could imagine this is not the way you'd want to go.

When I'm compiling with the clang as installed by debian, the build script tries to generate files in the clang installation folder. This folder requires root access to write.

This is not the default behavior. It only tries to write to CMAKE_INSTALL_PREFIX. Are you trying to install into the system-wide clang directory (if so, why?) ?

Are you trying to install into the system-wide clang directory (if so, why?) ?

The build-script I'm using is pasted below, which made me realiase that I upgraded clang,
and therefore also used LLVMSPIRV_BRANCH=main.
Could that explain the trying-to-install-to-/usr behaviour?
#!/bin/bash

CLANG_VERSION=18

export CC=/usr/bin/clang-${CLANG_VERSION}
export CXX=/usr/bin/clang++-${CLANG_VERSION}

BUILD_DEPENDENCIES_DEBIAN="libboost-context-dev libboost-fiber-dev clang-${CLANG_VERSION} libclang-${CLANG_VERSION}-dev libomp-${CLANG_VERSION}-dev spirv-tools libze-dev"
dpkg --verify ${BUILD_DEPENDENCIES_DEBIAN} &> /dev/null
if [ $? -ne "0" ]; then
	sudo apt --no-upgrade -y install ${BUILD_DEPENDENCIES_DEBIAN}
fi

if [ ! -d build ]; then
	cmake -GNinja -Bbuild -S. -DCMAKE_BUILD_TYPE=Release -DCPACK_GENERATOR=DEB \
		-DWITH_LEVEL_ZERO_BACKEND=ON -DWITH_ACCELERATED_CPU=ON -DWITH_ROCM_BACKEND=OFF -DWITH_CUDA_BACKEND=OFF -DWITH_SSCP_COMPILER=ON \
		-DLLVMSPIRV_BRANCH=main
fi

cmake --build build -- package

No, the reason it tries to install to /usr is because you have not set CMAKE_INSTALL_PREFIX to your desired install location, so it just defaults to a system-wide installation in /usr.
PS: We do not recommend using unreleased clang versions, as they tend to have stability issues.

No, the reason it tries to install to /usr is because you have not set CMAKE_INSTALL_PREFIX to your desired install location, so it just defaults to a system-wide installation in /usr.

CMAKE_INSTALL_PREFIX also affects the package that CPACK builds, so I was attempting to build both packages with proper install paths in one go.
It seems that that really doesn't fit the existing workflow very well.  I made this PR to see if my changes would be helpful for the project as well. It looks like that's not the case, so feel free to close this PR if you think it's too far off from being a helpful addition.

Is this still needed? Does PR #1172 resolve this issue?

Is this still needed? Does PR #1172 resolve this issue?

Not fully. I did update the PR the latest branch. In order for CPack to run, it cannot have the install(CODE) in src/compiler/llvm-to-backend/CMakeLists.txt.
I can imagine that the solution in this PR is not exactly what you have in mind.
Do you have some thoughts on how I could make an acceptable PR?


odo add binding documentation

Signed-off-by: Parthvi Vala<EMAIL_ADDRESS>
What type of PR is this:

/kind documentation
What does this PR do / why we need it:
This PR adds documentation for odo add binding.
Which issue(s) this PR fixes:

Fixes part of #5627
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[x] Documentation

How to test changes / Special notes to the reviewer:

/hold
Until #5641 is merged.

/hold cancel

/approve


Destination within multiple NavGraphs is only added to the first one

Hello there! hope you're doing well,

@NavGraph
annotation class NavGraph1(val start: Boolean = false)

@NavGraph1(start = true)
@Destination(/*...*/)
@Composable
fun NavGraph1StartScreen(navigator: DestinationsNavigator) {
    //...
}

@NavGraph
annotation class NavGraph2(val start: Boolean = false)

@NavGraph2(start = true)
@Destination(/*...*/)
@Composable
fun NavGraph2StartScreen(navigator: DestinationsNavigator) {
    //...
}

@NavGraph1
@NavGraph2
@Destination(/*...*/)
@Composable
fun MyScreen(navigator: DestinationsNavigator) {
    //...
}

MyScreenDestination is only being added to the destinations of NavGraph1

At the moment this is expected.
Each Destination can only have a single NavGraph. If you want that behaviour you need to make two Composables one for each NavGraph and both call a common composable.
This forces you to give different names, which creates two different generated Destinations, which in turn makes you be able to navigate to specific one you want 🙂

I’ll leave it open but it’s probably low priority enhancement at best 🙂

I don't even know if this would be possible but is there a way to check if a destination is used multiple times? If so it should be easy to generate a wrapper composable with the same name plus adding a numeric value at the end that contains that composable.
It's not perfect and could eventually be optimized to specify more details but would allow this action without having to manually create said files.

I think this is actually a very useful feature, it'll enable navigating to the same destination from multiple graphs without any workarounds, right? or i'm missing something?

Hi @yallam08!
You can already do that 🤔
Unless with graphs you mean root level graphs aka the ones passed in to DestinationsNavHost calls?
In that case, no this doesn’t help to do it more easily than we can also already do it.
This feature would literally create one destination  for each graph and all would call your composable, that’s it.
You can achieve the same thing by defining multiple destinations which just calls a common composable. Each assigned to its own graph.

@raamcosta
yes, with graphs i mean the root level.
i'm currently using a serparate graph for a flow within my app. e.g, @SignInSignUpGraph , @HomeGraph , @PaymentGraph , etc..
and in many cases i have a screen that's accessed from 3 graphs or more.
now i'll need to define 3 wrapper destinations for the same screen. i'd prefer if the library does this for me and use the same destination. what do you think?
thanks for the great lib btw

Just came here to say that I just tried to do this exact thing and was looking to open a new question about it, so essentially a +1.
Just adding my scenario to it:
I have two separate bottom navigation layouts that is the main navigation, but looks different for different users. Some tabs are shared between the bottom navigations, and I would have liked to just share those destinations. I can't put them to the same NavGraph because they have different starting tabs, among other things.
I think it would be a nice addition, but I understand that it might not feel that high prio :)
I had thought it would just add the same destination to two different NavGraphs, but I guess this could mess up things in ways I'm not familiar with 😅

would be nice if this is implemented

Also +1 although we are currently going with multiple destinations calling common composable and it is totally fine

Implemented for v2! Closing this one.


ES6 style of exports isn't accepted

export default AppName
isn't working. We are using module.exports to accommodate for this

This PR, if accepted, will address your issue: https://github.com/paypal/react-engine/pull/149.

@Ashwin117 v3.2.1 is released with the fix. please re-open if you face any issues


Not Working with Angular 6, Also bug (cannot select date range more than couple months)

This datepicker doesn't work with latest Angular release (please fix the issue reported in #38)
Getting this error:
DaterangepickerComponent.html:28 ERROR TypeError: this.fromDate.format is not a function at DaterangepickerComponent.push../node_modules/angular-2-daterangepicker/daterangepicker-component.js.DaterangepickerComponent.formatFromDate (daterangepicker-component.js:353) at Object.eval [as handleEvent] (DaterangepickerComponent.html:31)

When startDate and endDate is not set or set to NULL
this.daterangepickerOptions = {             startDate: null,             endDate: null,      ...

@playnox https://www.npmjs.com/package/angular-datetimerangepicker

This is fixed in v2.1.1
https://www.npmjs.com/package/angular-datetimerangepicker


do we have any check point to contine unfinished tuning jobs?

do we have any check point to contine unfinished  tuning jobs?
sometimes i have to stop my jobs ,
but i did not find a way to contine my job,
i have to restart from 0
thanks

Thanks @xiebaiyuan please open a new thread on https://discuss.tvm.apache.org/ We generally use the discuss forum for related questions


Refining status when Condition failed

With a one task pipeline, and the task will not executed since the condition will checked failed.
That's means the pipeline not execute any task after running.
But the pipelinerun still express its success and emit event All Tasks have completed executing.
I understand the real mean is "all the tasks has been touched" but it mislead people, could we introduce new state to express this, for example: Succeeded with condition failed or whatever.
Expected Behavior
The state of pipelinerun should express the situation of condition failed
Actual Behavior
Always shows success

/kind question
/cc @dibyom

Yeah, a pipeline with a single conditional task with a condition failure is an interesting edge case. Right now the behavior is by design though like you said, it can be confusing.
  conditions:
  - lastTransitionTime: "2019-11-05T19:57:04Z"
    message: All Tasks have completed executing
    reason: Succeeded
    status: "True"
    type: Succeeded

It  should be simple enough to set the message or the reason to something like Successful but with Condition failure or something like that. Though the type status field  for the condition with type: Succeeded is still going to be True.

/assign @vincent-pli

Given that #1696  was merged, I'm going to close this issue. Feel free to re-open if you disagree @vincent-pli

/close


Bug: Delete Script not functioning

Describe the bug
When logged in and viewing a script the user uploaded, the delete button is non-functional. It correctly prompts whether or not to delete the script, but on clicking "Delete" in the dialogue box, it redirects to a URL that results in an HTML 500 server error.
When did it happen
Several times, but I specifically logged an instance of it happening at 4:32:56 AM CST, 9/15/2023.
Browser details:
Using Chrome 116.0.5845.187 Flatpak release on Pop!_OS 22.04 LTS with all updates applied as of 4:30 AM CST on 9/15/2023.

Thanks for the report! I've tracked down the problem and pushed a fix, should hopefully be working now. Do let me know if you're still having issues.


Update dependencies

Gson dependency is missing and some are not updated and are causing issues in code compilation
Can you assign me on this

Hello! Thanks for reaching out :)
Yes, you can work on updating the dependencies. Also, can you migrate from Groovy to KTS along side, since you are updating dependencies, it would be a good time to migrate to KTS version of build.gradle files :)

Hello! Thanks for reaching out :)
Yes, you can work on updating the dependencies. Also, can you migrate from Groovy to KTS along side, since you are updating dependencies, it would be a good time to migrate to KTS version of build.gradle files :)

Sure will do that, also can you please label it as 'hactoberfest'

This repository is already eligible for Hackotberfest, you can go ahead :)


[rio] k3s unable to pull images from localhost

Version:
Provide the output from k3s -v and provide the flags used to install or run k3s server.
0.10.0 inside of k3d 1.3.4
Describe the bug
Possible network change between 0.9 and 0.10
To Reproduce
Run k3d with
k3d create  -n rio --image rancher/k3s:v0.10.0 --publish 80:80 --publish 443:443  --publish 9443:9443 --publish 9080:9080
rio install --ip-address=<IP_ADDRESS>
# may need to also stop traefik
kubectl delete svc -n kube-system traefik
rio run https://github.com/rancher/rio-demo

image fails to pull from localhost
Expected behavior
This works with k3s v0.9.1
See https://github.com/rancher/rio/issues/602 for more context

Fixed in v0.10.2? Or not yet? https://github.com/rancher/k3s/releases/tag/v0.10.2
@erikwilson
cc: @rancher-max

Yes, fixed in v0.10.2.

Looks good on the rio side! Steps I took:

Created new droplet in DigitalOcean.
ssh'ed into it and Installed k3s v0.10.2: curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v0.10.2 sh -
Using rio v0.6.0-alpha.2, ran rio install into the cluster
Ran the demo: rio run -n gh https://github.com/rancher/rio-demo.
It built successfully and the endpoint was available and returned the expected result.

@rancher-max this works fine in a k3s cluster with external IP and locally with k3d I see now the images being pulled and the build finishes and the pod gets initialized.
I get connection refused from the endpoints locally (installed rio with rio install --ip-address=<IP_ADDRESS>).
This is the same behavior with k3s v0.9.1.
We just need to confirm this is due to a cluster config limitation when running k3s locally.

Deploying Rio control plane....
...
Welcome to Rio!
Run `rio run -p 80:8080 https://github.com/rancher/rio-demo` as an example
root@ip-172-31-8-229:~# rio run -p 80:8080 https://github.com/rancher/rio-demo
default:zealous-solomon
root@ip-172-31-8-229:~# curl  http://zealous-solomon-v0-default.n90no4.on-rio.io:31987
Hi there, I'm running in Rio

Resolved as of k3s v0.11.0-alpha4. Closing issue.


searcher: make indexing of repos concurrent

This patch attempts to improve the startup time of hound vastly in cases
when we have huge number of repositories and hound would generally take
long time to start because of its sequential nature of indexing.
Now, we have the startup indexing in a concurrent way while respecting
the config.MaxConcurrentIndexers parameter set by users in config.json.
Fixes https://github.com/etsy/hound/issues/250

It still needs some work with respect to the logging for different searchers. Right now, it's impossible to make any sense of the logs which are out of order because of the concurrency.
With "max-concurrent-indexers" : 3,, it looks like this:
2017/12/27 00:46:25 Searcher started for checkroot
2017/12/27 00:46:25 Searcher started for hackIDE2
2017/12/27 00:46:25 Searcher started for Hound2
2017/12/27 00:46:29 merge 0 files + mem
2017/12/27 00:46:29 5135 data bytes, 33552 index bytes
2017/12/27 00:46:29 Searcher started for social-media-share
2017/12/27 00:46:36 merge 0 files + mem
2017/12/27 00:46:36 25360 data bytes, 72254 index bytes
2017/12/27 00:46:36 Searcher started for Hound1
2017/12/27 00:46:37 merge 0 files + mem
2017/12/27 00:46:37 1982263 data bytes, 572876 index bytes
2017/12/27 00:46:37 Searcher started for hackIDE1
2017/12/27 00:46:47 merge 0 files + mem
2017/12/27 00:46:48 11896668 data bytes, 2077298 index bytes
2017/12/27 00:46:49 merge 0 files + mem
2017/12/27 00:46:49 1980573 data bytes, 572415 index bytes
2017/12/27 00:46:57 merge 0 files + mem
2017/12/27 00:46:58 11880955 data bytes, 2068178 index bytes
2017/12/27 00:46:58 All indexes built!
2017/12/27 00:46:58 running server at http://localhost:6080...

The rest of the implementation is good for review.
cc @kellegous

You can simplify the goroutine logic by having a single channel that returns a single type with either a searcher or an error.  A quick demo is here: https://play.golang.org/p/7ucBkx6MH_- .  This way you know exactly how many results are coming back from the channel -- one per spawned goroutine.  This layout also removes the waitgroup and the extra collector goroutine, and also makes it clear there are no data races with the maps.  I think it's fine, but by updating them in the main goroutine it's clear by inspection.
For the issue with interleaved log lines, you'd need to thread the repository name into the logging code so each log line was prefixed appropriately.  This could be done by not using the standard global logger but creating separate log.Logger instances and calling SetPrefix.

I agree with @dgryski. The structure he proposes is almost exactly what I had in mind. Specifically, I like to think of this N processes that run independently (ignoring the limiter) and return their results (either good or bad) over a single channel. The main orchestrating routine will consume all N results in sequence and build the searcher map before returning.

Thanks for dropping in. Great suggestions, @dgryski! I'll make changes accordingly.


[Bug] [Module Name] There is a GPU, but embedding is loaded on the CPU by default.

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Windows
Python version information

=3.11

DB-GPT version
latest release
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[X] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[X] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
GPU
Models information
llm：zhipu  embedding:bge
What happened
There is a GPU, but embedding is loaded on the CPU by default.
What you expected to happen
Uploading files is very slow. I found that embedding is not running on the GPU.
How to reproduce
python dbgpt/app/dbgpt_server.py
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Sorry, torch is inexplicably the cpu version.


Core: Added support for Web Components. Fixes #2492

Checklist for this pull request

[x] Your code should contain tests relevant for the problem you are solving.
Test is included
[x] Your commits messages format should follow the jQuery git commit message format (http://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines).
Same as title
[x] The pull request should reference existing issues or link to a reproducible demo.
Referenced issue (feature request) is #2492

Description
This PR tries to add validation support for custom elements (Web Components). See #2492 for a first technical analysis.
It's possible that the current implementation is not good enough. Especially the part where I added the customElements to both, the "focusin.validate focusout.validate keyup.validate" events and to the "click.validate" events. Maybe we would need to try to differ there or we should go with "more settings value" mentioned in #2492 approach?

This looks OK to me.

It's possible that the current implementation is not good enough.

Why? The way you've done it would be my preference over several settings.

Why? The way you've done it would be my preference over several settings.

I was thinking because customElements are now listening to both event types: "focusin.validate focusout.validate keyup.validate" but also to "click.validate" instead of just either one of them. The only reliable way to "split" imo would be to make it configurable by the user (therefore the single vs multiple config entries dilemma).
If we just say that web components will always listen for all events, that would be fine for me as well. It's just a decision in the end 😄


chore: update go linting + update dependencies for controller

This PR makes the following changes:

Updates to dependencies used on the controller:

Go 1.21 -> 1.22
controller-runtime: 0.17.3 -> 0.19.1
golangci-lint: 1.57.2 -> 1.61.0
EnvTest: 1.29 -> 1.31

Updates to dependencies used by backend:

controller-runtime: 0.17.3 -> 0.19.1
golangci-lint: 1.57.2 -> 1.61.0
EnvTest: 1.29 -> 1.31

Improved the linting for all go projects (controller, backend):

We now enforce comment formats
We now enforce license headers
We now do lots of code smell checks
We now have a spell checker

@ederign can you please LGTM when you are ready, this is an important update, and we need to get other PRs to rebase on it so they get the new linting.
/approve

/lgtm


Make createIntInRange work for full int range

Purpose
Closes ballerina-platform/ballerina-standard-library#4744
Examples
The code like
random:createIntInRange(int:MIN_VALUE, int:MAX_VALUE);

no longer causes int range overflow error.
Checklist

[x] Linked to an issue
[ ] Updated the changelog
[x] Added tests
[ ] Updated the spec
[ ] Checked native-image compatibility

Other remarks for reviewers

I will be grateful about any remarks regarding code formatting and organization of the tests,
while working on this I have found a small bug, cf. ballerina-platform/ballerina-standard-library#4892

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

@vil02 The fix looks good, before we accept the solution could you do the following?

Format the code. (bal format)
Update the changelog with the changes.

Thanks!

Code was formatted in: 80cfe223015b0171d5c9792d735004ff4ccfaadc.
Change long was updated in: 636e48191edf24ae30de7cb6de567a1a71b60a3f.
@niveathika thanks for the tip with bal format. Please let me know if something is still missing.

@vil02 Looks good! 👏🏽👏🏽👏🏽
Thanks for the contribution.


Modify workflow description is slightly confusing to users

Modify workflow doesn’t make it clear that this is a symbol from the add-in not a symbol from the map.
Just need to clarify the language a bit here: https://github.com/Esri/military-symbol-editor-addin-wpf#modify-a-symbol
Feedback from @kerryrobinson

Wherever the doc says "after you've selected a symbol", that could be interpreted as selecting the actual feature on the map, and then "Modify a Symbol" could be interpreted to mean modifing the symbol of the feature selected on the map.
Recommend making the doc clear that this tool is only for creating symbols, the worfklow for modifying an existing symbol is to use the Attributes pane, and changing the doc from "after you've selected a symbol" to "after you've selected a symbol in the Search tab" (or something similar).

@kerryrobinson - addressed this in PR:
https://github.com/Esri/military-symbol-editor-addin-wpf/pull/43
Once Travis merges, could you have a look?

@tlauver , looks great!


[logstash] remove goss port test

Goss port test for tcp:9600 is failing on GKE 1.12 due to https://github.com/aelsabbahy/goss/issues/149.
We already had this issue with Elasticsearch goss tests in https://github.com/elastic/helm-charts/commit/de1fef380e94ef6c5a0665f7c7aa4bdbb0385d0a.

jenkins test this please


steam crash on nixos

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit dcd7a92b01a360bbe7afa7299604c4040abb4c62  ().
Date: 2024-01-15
Tag:

flags: (if any)

System Information:
System name: Linux
Node name:
Release: 6.6.10-xanmod1
Version: #1-NixOS SMP PREEMPT_DYNAMIC Tue Jan  1 00:00:00 UTC 1980

GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])

os-release: BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="23.11.20240119.d2003f2"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 23.11 (Tapir)"
SUPPORT_END="2024-06-30"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="23.11 (Tapir)"
VERSION_CODENAME=tapir
VERSION_ID="23.11"

plugins:

Bug or Regression?
Bug
Description
after commit dcd7a92b01a360bbe7afa7299604c4040abb4c62
steam crash on startup
How to reproduce
run steam
Crash reports, logs, images, videos
steam.sh[2753]: Running Steam on nixos 23.11 64-bit
steam.sh[2753]: STEAM_RUNTIME is enabled automatically
setup.sh[2828]: Steam runtime environment up-to-date!
steam-runtime-identify-library-abi: Failed to execute child process "/sbin/ldconfig" (No such file or directory)
run.sh[2840]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig
run.sh[2840]: Warning: An unexpected error occurred while executing "/sbin/ldconfig -XNv", the exit status was 127
steam.sh[2753]: Steam client's requirements are satisfied
tid(2866) burning pthread_key_t == 0 so we never use it
[2024-01-22 23:22:50] Startup - updater built Jan 13 2024 00:51:43
[2024-01-22 23:22:50] Startup - Steam Client launched with: '/home/setsuna/.local/share/Steam/ubuntu12_32/steam'
01/22 23:22:50 Init: Installing breakpad exception handler for appid(steam)/version(1705108172)/tid(2866)
SteamUpdateUI: An X Error occurred
X Error of failed request:  BadAlloc (insufficient resources for operation)
Major opcode of failed request:  149 (GLX)
Minor opcode of failed request:  5 (X_GLXMakeCurrent)
Serial number of failed request:  0
xerror_handler: X failed, continuing
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2024-01-22 23:22:50] Loading cached metrics from disk (/home/setsuna/.local/share/Steam/package/steam_client_metrics.bin)
[2024-01-22 23:22:50] Using the following download hosts for Public, Realm steamglobal
[2024-01-22 23:22:50] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-01-22 23:22:50] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-01-22 23:22:50] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-01-22 23:22:50] Checking for update on startup
[2024-01-22 23:22:50] Checking for available updates...
[2024-01-22 23:22:50] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12
[2024-01-22 23:22:50] Manifest download: send request
[2024-01-22 23:22:50] Manifest download: waiting for download to finish
[2024-01-22 23:22:53] Manifest download: finished
[2024-01-22 23:22:53] Download skipped: /steam_client_ubuntu12 version<PHONE_NUMBER>, installed version<PHONE_NUMBER>, existing pending version 0
[2024-01-22 23:22:53] Nothing to do
[2024-01-22 23:22:53] Verifying installation...
[2024-01-22 23:22:53] Performing checksum verification of executable files
[2024-01-22 23:22:54] Verification complete
Steam logging initialized: directory: /home/setsuna/.local/share/Steam/logs
/nix/store/yga0a4s1ywhf1yww3vjfyiibzcgshqmq-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.so: wrong ELF class: ELFCLASS64
Failed to load module: /nix/store/yga0a4s1ywhf1yww3vjfyiibzcgshqmq-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.so
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf13617b0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf135ffa0
crash_20240122232254_5.dmp[2882]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240122232254_5.dmp
/home/setsuna/.local/share/Steam/steam.sh: line 798:  2866 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"

I can't reproduce it on nixos

I can't reproduce either.

it fix maybe disable gpu accelerated rendering in web views in steam setting


Parse metrics with constant keys/labels in macros

Currently an invocation like increment!(my_labels::METRIC_KEY, my_labels::METRIC_LABEL => label_value); will fail to parse in the macro (e.g., "expected literal" or "unexpected token").
It would be nice if using string constants would in these positions would be an option, so I don't have to repeat string literals in a bunch of places if the same metric can be produced from multiple sources (e.g. multiple different implementations of the same trait).

Yeah, seems pretty reasonable!
Right now the procedural macros are matching directly on literal strings, but maybe there's a way to match on constant expressions?  As long as we can evaluate and determine that an expression is in fact constant, it should be safe to use.
Open to PRs if you're interested in looking into this, otherwise it'll likely take some time to get picked up and worked on.

Yeah, it may be problematic to support the check for legal characters like this, since you probably can't evaluate a constant expression in a macro, even if you can figure out that it is one (which I'm not 100% on either, tbh).
Anyway, it's more of a nice to have, really. No rush :)

So I spent some time looking into this.  Indeed, it doesn't seem like proc macros have a way to distinguish an expression referencing a constant, and thus don't have a way to peek into them for slurping out the constant itself.
One thought I had that was we could potentially newtype the metric name such that it wraps a &'static str directly, and provide a helper macro to generate them.  The main metric macros would still accept literal strings (or this newtype) and do the right thing i.e. checking string literals for conformance, etc.  The helper macro would emulate that and thus we could keep metric name conformance checking while still allowing you to const-ify these things for cleanliness/code reuse/whatever.
I'll have to spend some more time on it, but would that work for you?  Essentially, you'd end up with something like:
const METRIC_KEY: MetricName = name!("metric_key");

Yeah, that'd work well I think. Even cleaner to read, perhaps, then just having &str constants for metric labels.

Cleaning up some old issues, so swinging back around here...
It should be possible to use a constant in the key name position as-is, although labels cannot (yet) use constants for the key portion of a label.  I'll be opening a PR to rectify that shortcoming.
This all comes with the same caveat that due to the reasons explained above, using constants means that there will be some allocations because procedural macros can't see "through" an ident -- i.e. MY_CONST -- to know that it, for example, points to a string literal or &'static str.  Additionally, there is no ability to specify constant functions in traits, so there's no pathway to specialized trait implementations to allow autowiring of these const-vs-not-const conversions without the procedural macros being aware of what's going on.
Additionally, with the merging of #260, constants can also be used for metric descriptions now.  That PR, however, does not yet have a release.

This is now released as part of<EMAIL_ADDRESS>


Languages/Categories should delete themselves if they no longer exist

Suppose we have a language called CSS/Bootstrap and then someone realized that that's two languages and then changes the languages for that resource to be ["CSS","Bootstrap"] instead. What happens to the language CSS/Bootstrap? Well, it gets orphaned. It exists, but there are not resources that have that language.
I think that whenever a resource is updated and the languages attribute is one of the changes, we should check that the old languages still exist on some resource. If they do not, then we should delete the language.
Same thing with categories. If a category gets removed from the last resource with that category, then the category should be deleted as well.

@aaron-suarez any problems with me assigning myself to this one?

No problem at all. Were you there in the meeting when I was going over this one and what it's about? If not, that's fine, just ask if you have any issues.

No I wasn't in the meeting but I think I got it. I'll let you know if I need any pointers.

@aaron-suarez is the issue resolved I can start working on it if not?

The code works as written right now but unit tests are needed to cover the new functionality.

ohh got it @mike-lloyd03 so if the tests are needed I can start working on it if it's alright?

Go for it.

@mike-lloyd03 i wrote some tests but it doesn't seem to work can you have a look
def test_delete_unused_languages(module_client, module_db, fake_auth_from_oc, fake_algolia_save):
    client = module_client
    apikey = get_api_key(client)

    # Happy Path
    response = update_resource(client, apikey)
    assert (response.status_code == 200)
    assert (response.json['resource'].get('name') == "New name")

    #Initial Data
    name = "Language Test"
    url = None
    category = None
    languages = ["Java", "JS/TS"]
    paid = None
    notes = None

    response = update_resource(client,
                               apikey,
                               name,
                               url,
                               category,
                               languages,
                               paid,
                               notes)
    assert (response.status_code == 200)
    assert(response.json['resource'].get('name') == "Language Test")

    languages_response = response.json['resource'].get('languages')
    assert("Java" in languages_response)
    assert("JS/TS" in languages_response)

    languages = ["Java", "Javascript", "Typescript"]
    response = update_resource(client, apikey, name, url,
                               category, languages, paid, notes)
    assert(response.status_code == 200)

    languages_response = response.json['resource'].get('languages')
    assert("Java" in languages_response)
    assert("Javascript" in languages_response)
    assert("Typescript" in languages_response)
    assert("JS/TS" not in languages_response)

    db_languages = client.get('api/v1/languages')
    db_languages = [language.get('name') for language in db_languages.json['languages']]
    # assert(isinstance(db_languages, list))
    assert("JS/TS" not in db_languages)

It's failing on the last assertion :(

@king-11 I haven't ran your test yet, but I would expect that last test to fail because we haven't yet written the code to have the languages delete themselves if they no longer exist. Did you try this on main or on @mike-lloyd03's branch?

@aaron-suarez Languages should auto-delete as well. My last commit implemented that logic.

@mike-lloyd03 would you mind adding that test to #362 so we can get it merged? IIRC, the tests were what we were waiting on.
@king-11 if you want credit for writing this test, go ahead and commit it on a branch and then I'll show @mike-lloyd03 how to cherry-pick it off the branch and stick it on his PR. If you don't care one way or the other how the code makes its way in there, then he can just copy and paste it into there and push up his own commit with your test in there

@aaron-suarez created the PR and yeah now it just fails on the last assertion until the changes are made

Cool I'll get with @mike-lloyd03 about cherry-picking your commit and sticking it on his PR so that way we can get that merged. If he's unavailable, I'll just do it myself since I think I have the power to edit either of your PRs


⚠ Mobitopup has degraded performance

In d277f8a, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4393 ms

Resolved: Mobitopup performance has improved in 648652d.


Update Jekyll to 3.7 gain livereload

Hello,
I was wondering if there were plans to update Jekyll to 3.7.. I found the new livereload feature to be a big time saver :)
Thanks! Love this theme!

Feel free to open a PR, not sure when I will get to it.

@joshgerdes okie =)


Remove "ECS" branding

From gitter:

@paked 09:15 Thoughts on removing ECS from our branding?
@paked 09:16 I have a theory some people are intimidated by the idea of "using ECS"

Thoughts everyone?
Basically I'd like to make us a "game engine", not an "ECS game engine" - even though we will still use ECS under the hood, and the users will still interact with it.

Some ideas from the other camp.
I discovered and became interested in Engo specifically because it was advertised as an ECS game engine. Personally I see the focus on a specific paradigm as a strength, which help guide design decisions and gives a frame of reference from which the project may be evaluated.
That being said, there may be other users who feel intimidated by the ECS paradigm. Do we have any concrete examples of this being the case?

I personally like the idea of using ECS. We might be able to say we use ECS, but also mention it's the default/best-practice. And not make a big deal out of it.

@mewmew We've seen a few people who join the chat and there biggest point-of-failure with Engo is this seemingly abstract concept of ECS.
@EtienneBruines This sounds like the best solution.

After hearing out @mewmew and @EtienneBruines I think like @paked I agree with @EtienneBruines as well which takes both sides into consideration.

@otraore @EtienneBruines @mewmew How do we want to proceed with this issue? I guess we should just start going through things and adapting them to @EtienneBruines's approach...

@paked I'd think documentation/tutorials would be the best way to go.

@paked I'd think documentation/tutorials would be the best way to go.

Definitely, try to ease newcomers into the ECS paradigm, by presenting very clear and educational documentation and tutorials, which help build this understanding in small and digestible steps. Introduce the notion of entities, components and systems as part of the tutorial series, and before the newcomers realise it, they too will be hooked no the ECS paradigm ;)

I actually feel a bit intimidated by ECS. I don't know if it is because of that but I do think I prefer to use another pattern or even make my own.
I would do an engo-core and then you could have engo-esc. This way the framework wouldn't be limited to just one pattern. This may envolve a lot of work though.

@Sendoushi I disagree and engo-core and engo-esc. Also the framework isn't limited to one pattern, it's why we seperated engo.io/engo (core) and engo.io/common (ecs implementation) as we've described here

@otraore Since you still need Scene, World and Systems... There is still ecs implementation. Not entirely separated.

It seems that there are only two lines that don't let me use another pattern:

https://github.com/EngoEngine/engo/blob/master/scene.go#L18 : What if that ecs.World was some kind of interface? Or even... What if there wasn't a world?
https://github.com/EngoEngine/engo/blob/master/engo_glfw.go#L207 What if this was simply a Mailbox.dispatch and whoever wants to listen...

Scene still makes sense in most of the patterns. It already is an interface. It wouldn't be hard to have those outside also though. Like for example:

https://github.com/EngoEngine/engo/blob/master/engo_glfw.go#L228 It could be another dispatch

Just some examples of what it could be done...

My thoughts from gitter related to @Sendoushi's:

I'm personally pro making engo open to other other libraries and moving in the direction of a library, as opposed to a highly opinionated engine.

I would like to show one precise problem that prevented me from using Engo in my game.
In a game that I'm working on, I have to maintain two copies of the same world and be able to update one of them independently of the other one and also be able to synchronize them (copy from one to another, so that they are same).
I found it hard to implement in Engo (at least for the first 30+ minutes of me trying to implement it), since Engo creates an *ecs.World for me that is hard to copy.
So, in my experience, it's actually the ECS (or at least the way Engo implements it) that prevented me from using Engo and made me start developing my own library.

@faiface: Do you think that Engo could provide more value to people if it was not so opinionated?

@paked Possible, but I am not entirely sure about that.
If it was up to me to redesign Engo to perfectly fit my needs, I would probably redesign it to look exactly like the library I'm working on (Pixel, almost ready for alpha release). But it's no point of having two libraries that work exactly same.
So, I that Engo could get better in two ways.

Begin less opinionated and more of a library, but that is related the previous paragraph.
Improve the ECS so that it is super easy to use and more flexible.

Regarding the second option, I haven't thought of the exact redesign of ECS in Engo, but what I'd definitely address is:

Inability to have multiple worlds and interact between them.
Need for manual registration of entities to systems. I think this decreases flexibility, productivity and ease of use.

I'm thinking in scene we could use an interface called Updater that requires Update(dt), and then in the demos and when utilizing common, you can cast the Updater as an ecs.World to access the fields and methods on that. This way it'll be easy to implement a non-ecs update method, and to utilize engo without needing either ecs or common. You could also implement your own updater that uses multiple interacting worlds, or whatever your needs may end up being.

SGTMOn Mar 7, 2018 6:12 AM, Noofbiz<EMAIL_ADDRESS>wrote:I'm thinking in scene we could use an interface called Updater that requires Update(dt), and then in the demos and when utilizing common, you can cast the Updater as an ecs.World to access the fields and methods on that. This way it'll be easy to implement a non-ecs update method, and to utilize engo without needing either ecs or common. You could also implement your own updater that uses multiple interacting worlds, or whatever your needs may end up being.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.


consider using distributed kmeans in distributed mode for a better training

https://github.com/facebookresearch/faiss/blob/b8fe92dfee9ea6f9c8cae27e4fc3ffeb12b5c4d2/benchs/distributed_ondisk/README.md#distributed-k-means

https://github.com/facebookresearch/faiss/tree/main/benchs/distributed_ondisk guide is very nice in general
in particular their concept of verticale slice (what we do with subindices in our merging strategy) vs hslice (they split the ivf in inverted lists slices in order to distributed the index) is really interesting for sharding the index between multiple machines (they used that for a 1T items index POC)


[Eligibility Questionnaire] Contribute questionnaire upstream

[ ] Evaluate whether there is a good way to contribute the questionnaire upstream (content in the pages might be unique for each site)
[ ] Contribute upstream

We need to discuss with Exygy whether they want this contribution and if so, in what form. @seanmalbert - could you tag the right people for this discussion?

@elenm can I help get this addressed by HRD? how can I help unblock? thanks!

This is more a question for Exygy about whether they want to pull in any of the work we've done for the eligibility questionnaire. It's not a launch blocker for us.

thanks for confirming!


custom-dynclass-loader

we produce a -hive and a not hive version of the connector.  Due to how we strip the packages, some Kafka Connect clusters can throw a NoClassDefFound error when it cannot find hadoop/hive in the non-hive version when trying to detect hive/hadoop (e.g. when using a rest catalog). This is fine, however the reflection code we use only converts ClassPathNotFound to nulls.

This brings in DynClasses.java from iceberg (apache license) and adds the additional catch for the NoClassDefFound linkage error

Tested on confluent cloud:
0.6.13 no hive version published on confluent hub -> throws NoClassDefFound during loading of catalog, even though we don't use hive/hadoop
0.6.13 hive version (manually uploaded) ->  works
0.6.13 this version w/ the alternate DynClass manually uploaded, no hive version -> works


Added device listing and selecting functionality

Hey, did you run the format.sh? If yes, and the CI & local test suite agree, I'd like to merge this when conflicts get resolved.


Dependencies of default FormFactory templates

I am getting a bit lost with the dependencies for the default templates with FormFactory. I see that I can modify these templates in order to implement the behavior and styles I want, but it does not seem to work out of the box.
Is there a list of javascript libraries the FormFactory templates depend on?

Hahaha alright, will check! Mind if I create some wiki page describing dependencies for the default templates, if I have time and figure it out?

Very very happy to have doc contributions!
I do favour having the documentation in the example site though, so that it
is versioned alongside the code. Could you add the info to a doc in the
source, then link to it from the wiki?
On Fri, 6 Apr 2018, 13:01 Corstian Boerman<EMAIL_ADDRESS>wrote:

Hahaha alright, will check! Mind if I create some wiki page describing
dependencies for the default templates, if I have time and figure it out?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mcintyre321/FormFactory/issues/60#issuecomment-379232700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQ0-hi4-L-Jej9tYBGlba_ostZE1wuyks5tl1k1gaJpZM4TF6Cz
.


Install a package with its version instead of *

When I install a package, say, flake8 with pipenv install flake8 -d/--dev, it adds this to the pipfile:
[dev-packages]
flake8 = *

How can I install it to do something like this?
pipenv install ~flake8 -d
And I expect it to put this in the pipfile:
[dev-packages]
flake8 = "~=3.8.3"

Right now what I do is before installing a package, I go over to https://pypi.org/project/flake8 and check the version and type pipenv install flake8~=3.8.3 in the terminal

One huge plus of pipenv is that it promotes upgrading. Forcing a pinning strategy on a user / package management tool first requires packages to do semantic versioning consistently and and semantically correct (and the 2nd is the bigger problem). Secondly it makes assumptions about one strategy being better than another.
If this is considered by devs, I would like request the default behaviour to be unchanged and to implement a separate flag that sets the pinning strategy for the project in the Pipfile, instead of a global default.

Yes but this can be an option.
And people will know exactly what version of packages we're using with this.

Yes but this can be an option.

Not sure you get what I'm saying: What you are asking for should be an option, not the default.
If I ask pipenv to install requests for me using pipenv install requests, I express that I do not care about the version. If I say pipenv install 'requests <2.3', it is also clear what I express and what is recorded. If I say "install requests for me, using version x as a base and allow any minor version upgrades", then this you can express as well, as you've clearly stated you know.
But you want the default for pipenv install requests to be "Hey, let me figure out what that latest version is and then pin that version in the Pipfile using a strategy that someone with no knowledge of the project thought was sane". And I don't think that's a good idea.
Let me stress that the python community doesn't even have semantic versioning. It's an exception more than a rule. Semantic versioning dictates that each version component guarantees a certain level of API stability: breakage only in major, additions only in minor and patch should not modify the contract at all, but only internal workings. Django for example uses a deprecation strategy of 2 minor versions: if deprecated in Ma.Mi.P, then remove in Ma.[Mi+2].0 and removal is breaking by design. This makes choosing a default upgrade strategy very project specific and shouldn't be silently set to anything. Explicit > Implicit.

And people will know exactly what version of packages we're using with this.
That's always in the lock file and the upgrade strategy is always in the Pipfile, for each package recorded separately.

But you want the default for pipenv install requests to be "Hey, let me figure out what that latest version is and then pin that version in the Pipfile using a strategy that someone with no knowledge of the project thought was sane". And I don't think  that's a good idea.

In the world of microservices, most projects are [semi-]standalone small services. "knowledge of the project's [strategy]" isn't necessarily required. With the high industry churn, most likely one won't have the entire picture before given a deadline to finish a feature. But, in that same world lives a reality where many companies cannot afford to have auto-updates project-wide each time CI/CD runs. Sometimes, dozens and dozens of microservices are involved and that requires robust testing. Not all of us are at the level of Netflix microservices. Leaving devs to edit the Pipfile manually to pin version on new projects or when they're ready to upgrade.
Let us, please, opt-out of "upgrade when you next test/deploy". A flag that asks pipenv install, when installing a new package, to add it with the installed version rather than *.
The opposite may be viewed as too much responsibility for a single tool. A single tool, pipenv install, both managing env packages and deciding on upgrade alerts+strategy (alerts being a failed CI) is not in the spirit of Linux, "Do one thing well". It is suitable, in the world of microservices, to decouple responsibilities. When we add on top of that the versatile tools DevOps have at their disposal, it is much more prudent to decouple upgrade responsibility away from pipenv install. One tool, such as pipenv install to manage envs and another tool, such as pipenv scan or Dependabot, to alert on upgrade necessity.
This way, we cover all use-cases.
An "opt out" flag that will pin the latest version installed will be amazing.
We shouldn't change the default pipenv install behavior as it may break many existing workflows for others.


restartableFirst don't recognize an object

Hello. I'm trying to execute Facebook graph request inside presenter.
I have that so far:
public void getAccessTokenRequest(LoginResult loginResult) {
        GraphRequest request = GraphRequest.newMeRequest(
                loginResult.getAccessToken(), new GraphRequest.GraphJSONObjectCallback() {
                    @Override
                    public void onCompleted(JSONObject object, GraphResponse response) {
                    }
                });

        Observable currentUserObservable = Observable.just(request) //but at this step we can request.executeAndWait();
                .subscribeOn(Schedulers.io());

        restartableFirst(REQUEST_CURRENT_USER, () -> currentUserObservable,
                (loginActivity, graphRequest) -> {

                        GraphResponse response = graphRequest.executeAndWait();
                              // here IDE don't want to recognize the object and I have a compile error.
                              //look at the picture to see what kind of object I get here.

                        if (response.getError() != null) {
                            Log.d(TAG, response.getError().toString());
                        } else {
                            Log.d(TAG, "success");
                        }
                    });
    }

So it is possible to write somehting like:
Observable.just(request)
                .subscribeOn(Schedulers.io())
                .subscribe(graphRequest1 -> {
                    graphRequest1.executeAndWait();
                });

without restartableFirst and it works!
What should I do in this case?

You need to mention graphRequest type, see lambda syntax in Java language docs.

Thanks. Yep, lambda expressions can have this two types of syntax:
(arg1, arg2...) -> { body }
(type1 arg1, type2 arg2...) -> { body }


Update lgtm.yml to exclude Ui files

Describe the bug
The auto-generated .py files created by pyuic5 should not be analyzed by lgtm
Expected behavior
Do not have lgtm analysis include files starting with Ui_
Additional context
This is specifically related to nasa/cFS-GroundSystem#46
Reporter Info
Leor Bleier, NASA GSFC\Code 582

Wasn't actually solved by commits above.

Wasn't actually solved by commits above (#94 didn't work).

I admit I don't fully understand how lgtm works with this file. The exclude line I added might simply be in the wrong place.


Added Persona 5 Tactica support.

Thanks!

how do you transfer the data? where do you put the folder


replace deprecated ioutil package

golangci-lint run
WARN [runner] The linter 'varcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter.  Replaced by unused. WARN [runner] The linter 'structcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter.  Replaced by unused. pkg/signature/signature.go:12:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
"io/ioutil"
^
pkg/filesystem/fs/fs.go:15:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
"io/ioutil"
^
pkg/converter/convert_unix.go:19:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
"io/ioutil"
^
make: *** [Makefile:52: check] Error 1
Signed-off-by: Changwei Ge<EMAIL_ADDRESS>

Codecov Report
Base: 29.81% // Head: 29.81% // No change to project coverage :thumbsup:

Coverage data is based on head (5fe38f6) compared to base (d2f4610).
Patch coverage: 28.57% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #169   +/-   ##
=======================================
  Coverage   29.81%   29.81%
=======================================
  Files          20       20
  Lines        1650     1650
=======================================
  Hits          492      492
  Misses       1093     1093
  Partials       65       65

Impacted Files
Coverage Δ

config/daemonconfig.go
0.00% <0.00%> (ø)

pkg/filesystem/fs/fs.go
1.15% <0.00%> (ø)

pkg/nydussdk/client.go
21.48% <20.00%> (ø)

pkg/filesystem/fs/stargz/resolver.go
34.78% <100.00%> (ø)

pkg/utils/transport/pool.go
74.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Async/Await

Feature Request
We use Prom a lot in Vapor projects. In the contoller we have to handle the future:
    func index(_ req: Request) throws -> EventLoopFuture<String> {
        let promise = req.eventLoop.makePromise(of: String.self)
        try MetricsSystem.prometheus().collect(into: promise)
        return promise.futureResult
    }

This feature request change the usage to
    func index(_ req: Request) async throws -> String {
        return try await MetricsSystem.prometheus().collect()
    }

Motivation Behind Feature
Vapor itself will turn to fully async/await. It would be nice to habe SwiftPrometheus async/await, too.
Feature Description
Support Async/Await
Alternatives or Workarounds
We could write an extension to wrap it into a/a.

Sounds good, feel free to send in a PR implementing this :-)


feat: Adds localization column in the alerts table

Following (#267), this PR adds a localization field in the alerts table, including minimal necessary changes.
The localization field is meant to be used as a JSON dump of a list of bounding boxes.

Thanks @MateoLostanlen . There is a value that is not None but it was not according to the desired format (conf missing). I added some validation checks and fixed it

Closing this since it has been merged in #267


Fixed #33543 -- Depracated passing False to OrderBy's nulls_first and nulls_last.

@AllenJonathan Do you have time to keep working on this?

I'm busy for a week, (university exams going on). Perhaps can do it after that. If this needs to be done quickly or anyone wants to take over they can.

Superseded by #15682.


[7.x.x] Bump Dependencies #4927626160

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/4927626160

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix genesis block sync

This PR fixes genesis block not accessible issue (https://github.com/paritytech/frontier/issues/78) which blockchains started even before EthereumRuntimeRPCApi runtime API version 4 (current version) still have.
Because some blockchains have runtime API version lower than 4 at genesis block, has_api conditional becomes false for those blockchains. (fn has_api returns false if version mismatch). That means, ethereum genesis block cannot be properly mapped. (For example, our chains have runtime API version 1 at genesis block). Regardless of the runtime version blockchains have at genesis block, it should be properly synced.

@sorpaas @tgmichel @koushiro
Changes should be small, could you kindly give me feedback?
Thank you in advance.

@sorpaas
Thank you so much for reviewing! (For some reason, I didn't receive notification and noticed the review now.)
I see, I didn't know the background about changes to current_block. please let me do it.

In other places, current_block_before_version_2 is called when API version is smaller than 2. If it is equal to 2, current_block is called.
https://github.com/paritytech/frontier/blob/3173b07a166a8930b4cb1e69d34f2ba52ef4e9f3/client/rpc/src/eth/execute.rs#L126
From this definition, I think current_block should be called if version is 2 .
https://github.com/paritytech/frontier/blob/3173b07a166a8930b4cb1e69d34f2ba52ef4e9f3/primitives/rpc/src/lib.rs#L126

Sure, pushed now! and it seems CI got triggered properly this time


KeyError: 'STATES'

User Error 🥴

@DavidJamesAustin  what was the fix? I am encountering the same error.

If you're getting KeyError: 'STATES' it means you don't have the environment variable STATES set.
https://github.com/pcarn/vaccine-watch#deployment-instructions

@pcarn thank you.