Users.update error API

Hello, i meet some trouble with Users.update since one week it looks since API update in mangopay, not sure trouble wasn't present before.
UseCase :
using mangopay2-nodejs-sdk 1.24.1 (same trouble in 1.30.0)
i call
const Mangopay = require('mangopay2-nodejs-sdk');

// [...] some code

api = new Mangopay(initData);

// [...] some code

api.Users.update({
    "PersonType": "NATURAL",
    "FirstName": "Arthur",
    "LastName": "Dent",
    "Tag": "62b2e26a56b5c41b4245794a",
    "Birthday": 0,
    "Nationality": "GB",
    "CountryOfResidence": "GB",
    "Email"<EMAIL_ADDRESS>    "Address": {
        "AddressLine1": "221B Baker street",
        "AddressLine2": "",
        "City": "Westminster, London, UK",
        "PostalCode": "London NW1",
        "Country": "GB"
    },
    Id: "2539616076"
});

I try directly by using mangopay API and got the same errors
API parameters :
{
    "PersonType": "NATURAL",
    "FirstName": "Arthur",
    "LastName": "Dent",
    "Tag": "62b2e26a56b5c41b4245794a",
    "Birthday": 0,
    "Nationality": "GB",
    "CountryOfResidence": "GB",
    "Email"<EMAIL_ADDRESS>    "Address": {
        "AddressLine1": "221B Baker street",
        "AddressLine2": "",
        "City": "Westminster, London, UK",
        "PostalCode": "London NW1",
        "Country": "GB"
    }
}

This is the message return by API
{
    "Message": "The ressource does not exist",
    "Type": "ressource_not_found",
    "Id": "9afb4500-1248-4361-9f84-e3035b5daf6d#1658224148",
    "Date":<PHONE_NUMBER>.0,
    "errors": {
        "RessourceNotFound": "Cannot found the ressource UserNatural with the id=2539616076 "
    }
}

Troubleshooting
Looks my user doesn't exist but he does
I'm sure the user Id exist in mangopay i can load him on mangopay interface
I cant find any content about "ressource_not_found"
Could you help me to find where i'm doing something wrong  ? thanks

Hello @tstocker,
Since using MANGOPAY API directly you have the same error, please contact MANGOPAY support. They will be able to access your request.
Have a nice day,


Data Freshness

[Enter feedback here]
Can you please add how often the data would be updated in the Software inventory and also is there a way to do a trigger on the client for the scan/update

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

ID: 985384b1-44b5-e852-22ab-06936c4903b7
Version Independent ID: 985384b1-44b5-e852-22ab-06936c4903b7
Content: Software inventory
Content Source: microsoft-365/security/defender-vulnerability-management/tvm-software-inventory.md
Service: microsoft-365-security
Sub-service: mdvm
GitHub Login: @siosulli
Microsoft Alias: siosulli

@kuvinod7 Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12042
Once the author approves, the changes will be live.
Thanks
Sri

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Does it able to support img2img? or please indicate the approach to implement it?

At the moment we don't have img2img functionality but you can send an image to our openai text endpoint which should be able to generate a text prompt from an image


Run Conformance checks for v1.27/rancher

Run Conformance checks for k8s v1.27 provisioned through rancher.

Raised a Conformance test result PR on CNCF - https://github.com/cncf/k8s-conformance/pull/2838

PR Merged hence closing the issue


Loser Bracket bug

Hi, I just played around with the brackets-viewer demo and found the following:

'LB 1.2: Loser of WB 1.2' is not set even though there is a loser set in WB 1.2 (named '4')
Instead, Loser of WB 1.2 goes to the second slot of LB 1.1
I also found that this bug extends with bigger brackets:

Unfortunately I am not used with the code enough yet to fix it by myself. I also could imagine that this is only an issue of the demo that generates the brackets as the data is usually coming from brackets-manager / brackets-model.
Also I have to note I tested the demo with flask/jinja engine as an extended html template.
Best regards

Hi! Thanks for testing the project!
You're right, this kind of bug usually comes from the InMemoryDatabase which is used only in the browser... All the unit tests are done with another type of storage so I tend not to find this kind of bug.
I just fixed a bug really close to this yesterday: https://github.com/Drarig29/brackets-manager.js/discussions/125
I'll have a look :wink:

This one is tough... I can only reproduce it every other time...
I fixed something which looks the same yesterday, but this time it's not easily reproducible.

Please be sure you are using the latest version of the viewer, I think I fixed it with the latest release: https://github.com/Drarig29/brackets-viewer.js/releases/tag/v1.4.5

No, actually I tried it again and it still does this. I'll need to investigate more.


unstable type change

Trying multiple types on example in documentation seems to give an error when changing to Float32  ( Float64 and BigFloat works fine).
`using Clarabel, SparseArrays, LinearAlgebra
P = sparse([3.0 1 -1; 0 4 2; 0 0 5])
q = [1, 2, -3.0]
equality constraint
Aeq = [1.0 1.0 -1.0]
beq = [1.0]
inequality constraint
Aineq = [0.0 1.0 0.0
0.0 0.0 1.0]
bineq = [2.0, 2.0]
SOC constraint
Asoc = -I(3) * 1.0
bsoc = [0.0, 0.0, 0.0]
Clarabel.jl constraint data
A_ = sparse([Aeq; Aineq; Asoc])
b_ = [beq; bineq; bsoc]
A = sparse([Aeq; Aineq])
b = [beq; bineq]
Clarabel.jl cone specification
#cones = [Clarabel.ZeroConeT(1), Clarabel.NonnegativeConeT(2), Clarabel.SecondOrderConeT(3)]
cones = [Clarabel.ZeroConeT(1), Clarabel.NonnegativeConeT(2)]
const T = Float64
settings = Clarabel.Settings{T}()
settings64 = Clarabel.Settings{Float64}(
verbose=true,
direct_solve_method=:qdldl)
solver64 = Clarabel.Solver{Float64}()
Clarabel.setup!(solver64, P, q, A, b, cones, settings64)
solution64 = Clarabel.solve!(solver64)
settings32 = Clarabel.Settings{Float32}(
verbose=true,
direct_solve_method=:qdldl)
solver32 = Clarabel.Solver{Float32}()
Clarabel.setup!(solver32, Float32.(P), Float32.(q), Float32.(A), Float32.(b), cones, settings32)
solution32 = Clarabel.solve!(solver32)
`
Hope I have done some elementary error.

Your example above works fine for me, in the sense that I don't get a type error.   The solver does not converge to full accuracy though because the default tolerances are probably too tight for a Float32 problem.
What error do you get, and what version are you using?

Sorry late reply, this is the error message:
`julia> solution32 = Clarabel.solve!(solver32)
LLVM ERROR: Instruction Combining seems stuck in an infinite loop after 1000 iterations.
[48519] signal (6): Abort trap: 6
in expression starting at REPL[26]:1
__pthread_kill at /usr/lib/system/libsystem_kernel.dylib (unknown line)
Allocations: 53219812 (Pool: 53130412; Big: 89400); GC: 16
zsh: abort      /Applications/Julia-1.10.app/Contents/Resources/julia/bin/julia
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...       4 completed.
[Process completed]`
Versioninfo:
julia> versioninfo()
Julia Version 1.10.0-beta3
Commit 404750f8586 (2023-10-03 12:53 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: macOS (arm64-apple-darwin22.4.0)
CPU: 8 × Apple M1
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-15.0.7 (ORCJIT, apple-m1)
Threads: 5 on 4 virtual cores
Environment:
JULIA_NUM_THREADS = 4
julia> using Clarabel
(@v1.10) pkg> st Clarabel
Status ~/.julia/environments/v1.10/Project.toml
[61c947e1] Clarabel v0.6.0
(@v1.10) pkg>

That seems weird - does that happen on the current stable version Julia (1.9.3)?

Still error though no crash of Julia:
`
julia> solution32 = Clarabel.solve!(solver32)
       Clarabel.jl v0.5.1  -  Clever Acronym
               (c) Paul Goulart
            University of Oxford, 2022

problem:
variables     = 3
constraints   = 3
nnz(P)        = 6
nnz(A)        = 5
cones (total) = 2
: Zero        = 1,  numel = 1
: Nonnegative = 1,  numel = 2
settings:
linear algebra: direct / qdldl, precision: Float32
max iter = 200, time limit = Inf,  max step = 0.990
tol_feas = 1.0e-08, tol_gap_abs = 1.0e-08, tol_gap_rel = 1.0e-08,
static reg : on, ϵ1 = 1.0e-08, ϵ2 = 4.9e-32
dynamic reg: on, ϵ = 1.0e-13, δ = 2.0e-07
iter refine: on, reltol = 1.0e-13, abstol = 1.0e-12,
max iter = 10, stop ratio = 5.0
equilibrate: on, min_scale = 1.0e-04, max_scale = 1.0e+04
max iter = 10
iter    pcost        dcost       gap       pres      dres      k/t        μ       step
ERROR: MethodError: no method matching scaled_unit_shift!(::Clarabel.CompositeCone{Float32}, ::Clarabel.ConicVector{Float32}, ::Float64, ::Clarabel.PrimalOrDualCone)
Closest candidates are:
scaled_unit_shift!(::Clarabel.CompositeCone{T}, ::Clarabel.ConicVector{T}, ::T, ::Clarabel.PrimalOrDualCone) where T
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/cones/coneops_compositecone.jl:97
scaled_unit_shift!(::Clarabel.ZeroCone{T}, ::AbstractVector{T}, ::T, ::Clarabel.PrimalOrDualCone) where T
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/cones/coneops_zerocone.jl:42
scaled_unit_shift!(::Clarabel.NonnegativeCone{T}, ::AbstractVector{T}, ::T, ::Clarabel.PrimalOrDualCone) where T
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/cones/coneops_nncone.jl:42
...
Stacktrace:
[1] _shift_to_cone_interior!(z::Clarabel.ConicVector{Float32}, cones::Clarabel.CompositeCone{Float32}, pd::Clarabel.PrimalOrDualCone)
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/variables.jl:193
[2] variables_symmetric_initialization!
@ ~/.julia/packages/Clarabel/AwMRn/src/variables.jl:173 [inlined]
[3] solver_default_start!(s::Clarabel.Solver{Float32})
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/solver.jl:360
[4] macro expansion
@ ~/.julia/packages/TimerOutputs/RsWnF/src/TimerOutput.jl:237 [inlined]
[5] macro expansion
@ ~/.julia/packages/Clarabel/AwMRn/src/solver.jl:188 [inlined]
[6] macro expansion
@ ~/.julia/packages/TimerOutputs/RsWnF/src/TimerOutput.jl:237 [inlined]
[7] solve!(s::Clarabel.Solver{Float32})
@ Clarabel ~/.julia/packages/Clarabel/AwMRn/src/solver.jl:185
[8] top-level scope
@ REPL[26]:1
`

Current version of the Clarabel package is 0.6.0 - perhaps try Pkg.update("Clarabel") ?

Noticed as well, though needed to upgrade a lot of packages. Now it provided a solution though status is ALMOST_SOLVED but anyway seems to give correct answer 👍
A bit strange that v1.10-beta3 is crashing and it seems because of Julia itself. Thanks anyway for your patience and quick replies!
julia> solution32 = Clarabel.solve!(solver32)
       Clarabel.jl v0.6.0  -  Clever Acronym
               (c) Paul Goulart
            University of Oxford, 2022

problem:
variables     = 3
constraints   = 3
nnz(P)        = 6
nnz(A)        = 5
cones (total) = 2
: Zero        = 1,  numel = 1
: Nonnegative = 1,  numel = 2
settings:
linear algebra: direct / qdldl, precision: Float32
max iter = 200, time limit = Inf,  max step = 0.990
tol_feas = 1.0e-08, tol_gap_abs = 1.0e-08, tol_gap_rel = 1.0e-08,
static reg : on, ϵ1 = 1.0e-08, ϵ2 = 4.9e-32
dynamic reg: on, ϵ = 1.0e-13, δ = 2.0e-07
iter refine: on, reltol = 1.0e-13, abstol = 1.0e-12,
max iter = 10, stop ratio = 5.0
equilibrate: on, min_scale = 1.0e-04, max_scale = 1.0e+04
max iter = 10
iter    pcost        dcost       gap       pres      dres      k/t        μ       step
0   6.7343e+00  -1.5943e+01  3.37e+00  0.00e+00  8.40e-01  1.00e+00  1.75e+00   ------
1   5.6728e+00  -2.0018e+01  4.53e+00  1.40e-07  4.41e-02  3.18e+00  2.42e-01  9.90e-01
2   2.5278e+00  -1.1634e+00  3.17e+00  3.46e-08  6.93e-04  5.02e-01  2.73e-02  9.90e-01
3   2.3971e+00   2.1739e+00  1.03e-01  4.92e-08  7.50e-06  3.12e-02  1.50e-03  9.90e-01
4   2.3966e+00   2.3934e+00  1.31e-03  4.95e-08  6.20e-08  4.41e-04  2.10e-05  9.90e-01
5   2.3966e+00   2.3965e+00  1.33e-05  7.43e-08  2.78e-08  4.41e-06  2.10e-07  9.90e-01
6   2.3966e+00   2.3966e+00  1.99e-07  4.76e-08  2.94e-08  4.34e-08  2.14e-09  9.81e-01
7   2.3966e+00   2.3966e+00  9.95e-08  4.01e-08  3.23e-08  2.61e-09  1.06e-10  9.90e-01
8   2.3966e+00   2.3966e+00  2.98e-07  2.76e-08  3.14e-08  3.58e-09  1.25e-09  9.90e-01
9   2.3966e+00   2.3966e+00  0.00e+00  2.59e-08  7.92e-08  1.57e-09  1.56e-10  9.90e-01
10   2.3966e+00   2.3966e+00  9.95e-08  2.58e-08  4.08e-08  7.55e-10  2.46e-10  9.90e-01
11   2.3966e+00   2.3966e+00  1.99e-07  8.81e-08  1.09e-07  1.78e-09  3.51e-11  9.90e-01
12   2.3966e+00   2.3966e+00  0.00e+00  1.05e-08  3.71e-08  2.63e-10  2.57e-12  9.90e-01
13   2.3966e+00   2.3966e+00  9.95e-08  3.21e-08  4.26e-08  1.13e-10  2.99e-12  9.90e-01
Terminated with status = solved (reduced accuracy)
solve time =  1.09s

Clarabel - Results
Status: ALMOST_SOLVED
Iterations: 13
Objective: 2.397
Solve time:  1.09s

julia>

I don't know that there is anything to do here, so will close.


[Task] Add unit test cases for ChatBotFooter component

Task Description:
Currently, we run unit tests using jest which can be found here.
However, the test cases are not yet comprehensive enough and work can be done to cover more grounds. Specifically for this issue, we hope to add test cases for the ChatBotFooter component.
Deliverable(s):
New unit test cases that cover the testing of the ChatBotFooter component.
Additional Context:

The ChatBotFooter components can be found here
An example for AudioButton can be found here which may serve as a good source for reference

Hello would love to take up this issue

Hello would love to take up this issue

Go for it!


Add a new common issue to the  OAuth 2 Troubleshooting guide

Thanks a lot @pstack2021 !!! I am making those changes.


[core-amqp] Address ESLint issues

Remove the || exit 0 part at the end of the lint script in the package.json of core-amqp and fix the errors that appear when running rushx lint.
After https://github.com/Azure/azure-sdk-for-js/pull/8680, the current list of errors and warnings can be seen here: https://gist.github.com/sadasant/232440b8faf6eb9edabb49082f3923d1

Closing this in favor of https://github.com/Azure/azure-sdk-for-js/issues/10775.


backup/restore as part of ci/cd process?

Hi - first, thanks for creating this super useful tool.
I'm curious if it can be extended to support a traditional deployment model. For example, I would like to create Contact Flow(s) in a 'dev' AWS account ('dev' Connect instance), test/qa, and if approved, deploy the update Contact Flow(s) to another AWS account ('prod' Connect instance). I see the json elements use the ARN which includes the AWS account # and the Connect instance ID. Does the tool change these when doing a restore to another account/instance? If not could that be added?

Hey @jyjohnson  , apologies for the delayed response, I've been taking a bit of a holiday.  I'll take a look at your request but it sounds reasonable.  Give me a couple of days to look into it.

Hey @jyjohnson  , apologies for the delayed response, I've been taking a bit of a holiday.  I'll take a look at your request but it sounds reasonable.  Give me a couple of days to look into it.

Ah so a little more work @jyjohnson as ARNS are littered everywhere, and theres no consistent pattern.  Also I should probably consider region as something to be accommodated by this use case.  Still I think it's a worthwhile feature request.

Ah so a little more work @jyjohnson as ARNS are littered everywhere, and theres no consistent pattern.  Also I should probably consider region as something to be accommodated by this use case.  Still I think it's a worthwhile feature request.

Right-o.  So the big challenge here is objects (flows, queues, prompts etc) all have unique id.  They look something like b20f58bb-e5cc-4618-9e7b-3ee3d446539e
These id are uniquely generated when the object is created.  An ARN in connect has the unique id as the suffix of the ARN.
These id are then referenced in contact flows and flows can be nested too.  Also there is no API call right now to create prompts or queues (and perhaps some more things I need to dig into).
So in order to restore a flow to a new connect instance (essentially the prefix of the ARN) you have to ensure all dependencies are created first, then update references to them in the contact flow.  The referencing looks like it can be done in code via a name but you will need to manually create some of the objects (queues, prompts) first and ensure the exact same name is used consistently between your connect instances.  For example if you have an announcement named "Say Hello World" you will need to ensure all of your instances have this announcement manually created with this exact name in order for a restoration of a contact flow to work properly. Same goes for queues.
Given the above AWS Connect limitations, is this feature still useful to you @jyjohnson ?

Right-o.  So the big challenge here is objects (flows, queues, prompts etc) all have unique id.  They look something like b20f58bb-e5cc-4618-9e7b-3ee3d446539e
These id are uniquely generated when the object is created.  An ARN in connect has the unique id as the suffix of the ARN.
These id are then referenced in contact flows and flows can be nested too.  Also there is no API call right now to create prompts or queues (and perhaps some more things I need to dig into).
So in order to restore a flow to a new connect instance (essentially the prefix of the ARN) you have to ensure all dependencies are created first, then update references to them in the contact flow.  The referencing looks like it can be done in code via a name but you will need to manually create some of the objects (queues, prompts) first and ensure the exact same name is used consistently between your connect instances.  For example if you have an announcement named "Say Hello World" you will need to ensure all of your instances have this announcement manually created with this exact name in order for a restoration of a contact flow to work properly. Same goes for queues.
Given the above AWS Connect limitations, is this feature still useful to you @jyjohnson ?

Howdy. I think assuming all dependencies are in place is "ok". I haven't looked at the API methods but could it check that all named resources exist in the target account/instance? Overall I think this would be useful. Thanks.

Howdy. I think assuming all dependencies are in place is "ok". I haven't looked at the API methods but could it check that all named resources exist in the target account/instance? Overall I think this would be useful. Thanks.

Hello.  Thanks for making such a useful tool.  Does connect-backup currently support SSO for aws profiles?  I'm getting an error, but only when I try to use a profile I've signed in as using "aws configure sso":
2021/05/25 14:52:22 NoCredentialProviders: no valid providers in chain
caused by: EnvAccessKeyNotFound: failed to find credentials in the environment.
SharedCredsLoad: failed to load profile, .
EC2RoleRequestError: no EC2 instance role found
caused by: RequestError: send request failed

Started working on this given multiple requests.  It's a lot of work and will involve a few smaller features along the way.  Stay tuned.


Remove the "languages" API for the Lookup component

I'll replace it with a public API so I can publish it

The trouble with it, it's that we must map the content from the API you add to an array of type:
[{ value: "", label: "" }]

Worry not young Jonatan.. I have solved it.

I'll commit shortly

@andrerpena geniuuus!!

Done


Support for Weapon and Apparel Quality Indicators

Alternative to Quality Colors, more performance friendly.
https://steamcommunity.com/sharedfiles/filedetails/?id=2005333573

Having looked into Weapon and Apparel Quality Indicators' source code, it does not seem to expose the quality colour in an accessible way.
It would unfortunately require coupling too tightly on my side to support it.


Add shellcheck

Strange that this didn't fail the build @lox

It is strange indeed 😰

That's better 🚨

Tests are passed! Gonna merge.


Gitlab API v4, Invalid raw blob uri

Ran into this issue with the latest (v4.0.0) version of this client. I kept getting an invalid blob back and I was trying to figure out why. From a quick code read, I see we're still requesting the older style of blobs:
https://github.com/timols/java-gitlab-api/blob/master/src/main/java/org/gitlab/api/GitlabAPI.java#L1533
From the API documentation, this should be pointing at something like:
/projects/:id/repository/blobs/:sha/raw
https://docs.gitlab.com/ce/api/repositories.html#raw-blob-content

Commit with fix up for review.


Feature Request

Would it be possible to add autodelete Support ?

Yes...I will try and release it in the next update 🙂


Connecting signal to inherited function shouldn't create a new one

Godot version: 9c6175db11ff72603ae58789a462b33ec1e910f8
Issue description (what happened, and what was expected):
When signal is connected through editor (i.e. not code) to inherited function (e.g. Node-based: queue_free, emit_signal, etc), a new function with that name is created. Better behavior would be to detect that function exist and automatically deselect "Create Function" option and indicate that the function is already defined on parent class.

Well I'm rather happy with how this works currently. If you have inherited function and you are connecting new signal to it you usually will want to extend this function...

Do you usually extend queue_free, emit_signal and alike?
Not sure about 'normal' inherited functions - i think there are cases where you want and cases where you don't want to extend. So maybe this behavior should only apply to 'system' functions, which are rarely extended.

Well, you can uncheck the "create new function" toggle if you don't want a new function, no?
Also, what if I write "queue_free", then see it unchecks and write "_signal_queue_free", should it recheck?
What if I write "qf", uncheck it for some reason, then write "queue_free", and finally write "_cleanup", should it end up checked or unchecked?

Could be made an option. Or changing only if user hasn't touched checkbox. But to decide what's optimal one has to study typical usecases and workflow and i don't use Godot these days. I can only say that in my workflow back when i created the issue, it was somewhat annoying to either uncheck each time or delete created function.

Well I think the most elegant way to deal with this would be to make the checkbox to remember it's previous state.

This seems to be fixed as of Godot 3.2.1. Connecting a signal to a builtin class method does not create a callback, unless it is a virtual method, in which case this is intended.


URL for image generator is broken

The URL needs to be updated as the current one links to a warehouse company

LOL thanks for noticing, now changed to placehold.co


[ZEPPELIN-3017] fix Spark version in Dockerfiles

What is this PR for?
The PR updates Spark version to the current 2.1.2, since the one which is present now (2.1.1) is not available anymore.
What type of PR is it?
Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-3017
How should this be tested?
manually

ok, I think we can skip this time, for future references, please Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration

merging if no more comment


training data and training method for the GNN model?

Thanks for providing interesting GNN models for metabolic loci testing. Could you please provide the training data and the relevant codes for training the GNN model?
many thanks
Sh-Y

Unfortunately we are not at liberty to share the dataset because it is derived from the RPAIR database obtained by us under an academic license. The training code is heavily dependent on this data and as such is not a part of the repository; however, we do provide detailed description of the method in our paper. To gain access to the RPAIR dataset, we suggest contacting KEGG.

@MachineGUN001, we'll be happy to help you with setting up the model for training. If you're interested, please send us an email: soha (at) cs.tufts.edu. We look forward to hearing from you.


[Nextcloud] 2FA Input

Extension – Nextcloud
Author: @uetchy

Description

Error was way to long…

Error:
Pastebin
Nextcloud Apps

[ ] = Disabled

[x] = Enabled

[x] accessibility: 1.10.0

[x] activity: 2.16.0

[x] admin_audit: 1.14.0

[x] announcementcenter: 6.2.0

[x] approval: 1.0.9

[x] bruteforcesettings: 2.4.0

[x] circles: 24.0.0

[x] cloud_federation_api: 1.7.0

[x] comments: 1.14.0

[x] contactsinteraction: 1.5.0

[x] dashboard: 7.4.0

[x] dav: 1.22.0

[x] deck: 1.7.0

[x] encryption: 2.12.0

[x] federatedfilesharing: 1.14.0

[x] federation: 1.14.0

[x] files: 1.19.0

[x] files_downloadactivity: 1.13.0

[x] files_external: 1.16.1

[x] files_pdfviewer: 2.5.0

[x] files_rightclick: 1.3.0

[x] files_sharing: 1.16.2

[x] files_trashbin: 1.14.0

[x] files_versions: 1.17.0

[x] files_videoplayer: 1.13.0

[x] firstrunwizard: 2.13.0

[x] logreader: 2.9.0

[x] lookup_server_connector: 1.12.0

[x] nextcloud_announcements: 1.13.0

[x] notes: 4.3.1

[x] notifications: 2.12.0

[x] oauth2: 1.12.0

[x] occweb: 0.1.0

[x] password_policy: 1.14.0

[x] photos: 1.6.0

[x] privacy: 1.8.0

[x] provisioning_api: 1.14.0

[x] recommendations: 1.3.0

[x] serverinfo: 1.14.0

[x] settings: 1.6.0

[x] sharebymail: 1.14.0

[x] sharingpath: 0.4.4

[x] support: 1.7.0

[x] survey_client: 1.12.0

[x] systemtags: 1.14.0

[x] tasks: 0.14.4

[x] text: 3.5.1

[x] theming: 1.15.0

[x] twofactor_backupcodes: 1.13.0

[x] twofactor_totp: 6.3.0 (THIS APP GENERATES 2FA CODE)

[x] updatenotification: 1.14.0

[x] user_status: 1.4.0

[x] viewer: 1.8.0

[x] weather_status: 1.4.0

[x] workflowengine: 2.6.0

[ ] cas

[ ] user_ldap

Steps To Reproduce

Login to account (not asking for 2FA code)
API Fails.

The current behavior
Not seeing anything, no decks, no files.
The expected behavior
Asking for 2FA code and working properly
Raycast version
Version: 1.35.1

Did you enter the correct app token?

On May 25, 2022, at 3:14, MV―STNS @.***> wrote:

Extension – Nextcloud
Author: @uetchy
Description
Error:
Pastebin
Nextcloud Apps
= Disabled
= Enabled
accessibility: 1.10.0
activity: 2.16.0
admin_audit: 1.14.0
announcementcenter: 6.2.0
approval: 1.0.9
bruteforcesettings: 2.4.0
circles: 24.0.0
cloud_federation_api: 1.7.0
comments: 1.14.0
contactsinteraction: 1.5.0
dashboard: 7.4.0
dav: 1.22.0
deck: 1.7.0
encryption: 2.12.0
federatedfilesharing: 1.14.0
federation: 1.14.0
files: 1.19.0
files_downloadactivity: 1.13.0
files_external: 1.16.1
files_pdfviewer: 2.5.0
files_rightclick: 1.3.0
files_sharing: 1.16.2
files_trashbin: 1.14.0
files_versions: 1.17.0
files_videoplayer: 1.13.0
firstrunwizard: 2.13.0
logreader: 2.9.0
lookup_server_connector: 1.12.0
nextcloud_announcements: 1.13.0
notes: 4.3.1
notifications: 2.12.0
oauth2: 1.12.0
occweb: 0.1.0
password_policy: 1.14.0
photos: 1.6.0
privacy: 1.8.0
provisioning_api: 1.14.0
recommendations: 1.3.0
serverinfo: 1.14.0
settings: 1.6.0
sharebymail: 1.14.0
sharingpath: 0.4.4
support: 1.7.0
survey_client: 1.12.0
systemtags: 1.14.0
tasks: 0.14.4
text: 3.5.1
theming: 1.15.0
twofactor_backupcodes: 1.13.0
twofactor_totp: 6.3.0 (THIS APP GENERATES 2FA CODE)
updatenotification: 1.14.0
user_status: 1.4.0
viewer: 1.8.0
weather_status: 1.4.0
workflowengine: 2.6.0
cas
user_ldap
Steps To Reproduce
Login to account (not asking for 2FA code)
API Fails.
The current behavior
Not seeing anything, no decks, no files.
The expected behavior
Asking for 2FA code and working properly
Raycast version
Version: 1.35.1
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Oh yea, sorry, I just found this: https://github.com/raycast/extensions/blob/087b69cd172dcf0c7c9d5f33cbba27948671cf0b/extensions/nextcloud/README.md.
Thought I could just log in with my username and password. I was never prompted with this information 🫠 sorry for the inconvenience. Thank you!

You can see the same help text when you move the cursor on the password field though, yeah that's kind of unintuitive I guess.
Hopefully Raycast team would change the UI to show that description above the input field.


Error: MissingPluginException(No implementation found for method locationFromAddress on channel flutter.baseflow.com/geocoding)

I am getting this MissingPluginException error and it is caused by my locationFromAddress call and it prevents the navigator to function.
The code worked properly before I added locationFromAddress. What can this error mean and how do I fix this?
here is my code
`import 'package:flutter/material.dart';
import 'package:flutter/scheduler.dart';
import 'package:geolocator/geolocator.dart';
import 'package:geocoding/geocoding.dart';
@override
void didChangeDependencies() {
super.didChangeDependencies();
SchedulerBinding.instance.addPostFrameCallback((_) async {
userPosition = await getUserPosition();
locs = await GeocodingPlatform.instance.locationFromAddress('my address');
loc = locs.first;
if (context.mounted) {
Navigator.pushReplacementNamed(context, 'map', arguments: {
'userPosition': userPosition,
'loc': loc,
});
}
});
}
Position? userPosition;
Location? loc;
List locs = [];
@override
Widget build(BuildContext context) {...}`

Are you running it on a navigator ?


npm release

I see there is a tag for 4.3.0 and which includes some fixes, but on npm, only 4.2.0 has been released. Can we get an npm release if it is ready?
Thanks!

npm i debug@beta


MONDO:0022858   continuous spike-wave during slow sleep syndrome [Merge]

Mondo term (ID and Label)
MONDO:0022858 continuous spike-wave during slow sleep syndrome
Reason for deprecation
GARD (https://rarediseases.info.nih.gov/diseases/1513/continuous-spike-wave-during-slow-sleep-syndrome ) points to the Orphanet (https://www.orpha.net/en/disease/detail/725) entry
Term to be merged with
MONDO:0019123 continuous spikes and waves during sleep
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

Dear @kanems,
Thank you for reaching out to the Mondo Disease Ontology, part of the Monarch Initiative!
We have received your ticket and will review it as soon as possible.
If you have any additional information or updates relevant to your inquiry, please add them in a comment on this ticket. Your input is valuable in helping us understand and resolve the issue effectively.
Thank you for your patience and for your contributions to Mondo!
Sincerely,
The Mondo Team

I agree the terms should be merged based on the reasons in the original post.


Not working with iPAQ

I have a HP iPAQ and I want to connect it to this chat server. There's just one issue. When connecting, the program I'm using (MobileVT) sends some garbage data. Your code interprets that as a username, so I get:
please enter a username: , you are now in the chat room
Do you think you can fix this?
Also it doesn't seem to work with the telnet client on Windows 10.

Nevermind, i'm supposed to use the included client.


drive pull taking too much memory - linux kill it (out of memory) and freeze the terminal

I am trying to pull a folder (12 files - total 399GB)  from my Google Drive to my local disk in Linux using your program (thank you for this). This folder was a shared one that I had included to my Google Drive, so I could pull it using "drive".
However, after 1 hour and 2 hour, the program is "terminated by signal 9". Checking what could cause it I found  (with dmesg) this:
Out of memory: Kill process 3729 (sshd) score 1 or sacrifice child
(Besides killing the program, it also caused screen session be killed. I captured the message of "terminating by signal 9" in the nohup log after 2 or 3 screen session crash with no clue)
Even after the system killing the program, the amount of memory allocated by the program (almost all 32 GB that the machine has) was held and the only solution to reestablish the system resources was to reboot the system.
System info:
Linux 3.2.0-4-686-pae #1 SMP Debian 3.2.57-3 i686 GNU/Linux
quad-core
32 GB memory
Please, any idea what could be causing this program behavior?

Thank you for reporting this @lintzyli and welcome to drive. This is quite unfortunate but definitely an interesting edge case.
Does it help to pull one massive file at a time?

Btw drive allows for you do stat as well as list on files on the remote. You can find this information in the README, just in case you haven't already looked at it.

Thank you for you messages @odeke-em. I have tried list, but I have not used stat yet (I will).
In case it helps, I was downloading this dataset, which is hosted at Google Drive:
http://www.yli-corpus.org/mediaeval-2014-placing-task-dataset
Yes, when I pull one big file at time, drive is able to finish OK.

Can't really reproduce or debug this. Going to close this for now. Let's re-open if it returns. Thank you @lintzyli for reporting it.


[Bug]: event name mismatch: "connecting" vs "isConnecting"

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
An event listener "connecting" can be added using addEventListener function. https://github.com/cardano-foundation/cardano-connect-with-wallet/blob/main/core/index.ts#L64
The callback will never be triggered because only an event named "isConnecting" would enter the clause where you subscribe to the isConnectingObserver: https://github.com/cardano-foundation/cardano-connect-with-wallet/blob/main/core/index.ts#L83
Expected Behavior
I expect addEventListener("connecting", callback) to trigger the callback.
Steps To Reproduce
import { Wallet } from '@cardano-foundation/cardano-connect-with-wallet-core';

Wallet.addEventListener("connecting", () => {
  console.log("connecting")
});

await Wallet.connect("eternl", "mainnet");

Environment
No response
Anything else?
No response

@robinboening thank you for reporting and fixing this issue ! Much appreciated 💪 (I will trigger the build pipeline and the new version should be available on npm in a few minutes)


[hi] Localize content of "Docs Smoke Test Page" in "docs/test.md" to Hindi

We can see that test.md file present in en language demonstrates how the Kubernetes documentation uses Markdown, it would be useful to have the same file for hi language too (well not just for hi lang, we can do this for other languages as well that doesn't have this,)

I'll take this issue up, if it is something we can work on.
And if we are to proceed with this for all languages then I suggest making a different PR for a different lang linking to this same issue.

/retitle [hi] Localize content of "Docs Smoke Test Page" in "docs/test.md" to Hindi
/language hi

I'll take this issue up, if it is something we can work on. And if we are to proceed with this for all languages then I suggest making a different PR for a different lang linking to this same issue.

@dipesh-rawat any views on this?

Thanks for Raising this Issue!!
Let's Create more Issues like this! Because Hindi Localized Pages are Very less!

/assign

@ShivangShandilya thanks for raising this issue. Please feel free to work on it.
/triage accepted

/good-first-issue
/help

I would like to work on this issue. Could you please assign it to me?

Just as Shivang has done in this comment, please issue the /assign command yourself so the bot can assign it to you.

/assign

/assign

/assign

/assign

/assign


Error on npx everdev sold install

npx everdev sold install
Downloading from https://binaries.tonlabs.io/sold_0_67_0_linux.gz..............................................................................................................................................................................................................................................................................................................................................................................
Error: /home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /home/.everdev/sold/sold)

0.68.0
@local:~/src$ npx everdev sol set --compiler 0.68.0
Downloading from https://binaries.tonlabs.io/solc_0_68_0_linux.gz...........................................................................................................................................................................
Error: /home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/.everdev/solidity/solc)

0.67.0
@local:~/src$ npx everdev sol set --compiler 0.67.0
Downloading from https://binaries.tonlabs.io/solc_0_67_0_linux.gz..........................................................................................................................................................................
Error: /home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /home/.everdev/solidity/solc)
/home/.everdev/solidity/solc: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/.everdev/solidity/solc)

0.66.0
@local:~/src$ npx everdev sol set --compiler 0.66.0
All components already up to date.

npx everdev sold install
Error: /home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/.everdev/sold/sold)
/home/.everdev/sold/sold: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /home/.everdev/sold/sold)


pkg/fuzzer: use a MAB to decide on exec fuzz vs exec gen

I'm currently running experiments to see whether it brings any fuzzing performance improvements.

Cc #1950
Let's try to use a plain delta-epsylon MAB for this purpose.
To better track its effect, also calculate moving averages of the "new max signal" / "execution time" ratios for exec fuzz and exec gen.

Okay, this particular approach will likely not work well because the "new signal / execution time" ratio can get pretty large. The bounded learning rate, even being as small as 0.0005, would not cope with extreme outliers.
I'm currently testing how useful it may be if we just look at the probability of generating any new coverage. This is the easiest implementation-wise.
The "new signal / execution time" ratio itself still sounds like a much better target, but we need to map it to a smaller range of values to use as a reward for a MAB. Perhaps keep some history of values of the last N "new signal / execution time" values and see what share of them is less than the current observed value? Then it would nicely map to [0;1].
The only caveat is that if N is large, we might need some tricky data structures to determine this rate efficiently (balanced trees should be able do it in O(log N), not sure if we can do it better?).

Maybe we could map coverage and execution time to some logarithmic buckets: 1, 10, 100, or finer-grained 1,2,5,10,20,50,100...?
Also amount of coverage may be very different for different syscalls, some may give some huge chunks of coverage, and some just few coverage points.


Uncaught Error: spawn gofmt ENOENT

Hi. I just install go-plus and try to edit file which is created by command in terminal so when I click save I get the exception. Here is the step to reproduce this bug.

Edit file.go
Command+s then I get this exception.

Atom Version: 0.165.0
System: Mac OS X 10.10.1
Thrown From: Atom Core
Stack Trace
Uncaught Error: spawn gofmt ENOENT
At events.js:85

Error: spawn gofmt ENOENT
  at exports._errnoException (util.js:742:11)
  at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
  at child_process.js:1142:20
  at process._tickCallback (node.js:378:11)

Commands
  2x -1:23.9 tree-view:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -0:24.7 golang:goinfo (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -0:16.6 editor:newline (input.hidden-input)
  2x -0:07.9 core:move-right (input.hidden-input)
     -0:00.0 core:save (input.hidden-input)

Config
{
  "editor": {
    "fontSize": 12
  }
}

Installed Packages
# User
atom-beautify, v0.17.2
autocomplete-plus, v1.0.0
go-plus, v3.0.11
gofmt, v0.2.0

# Dev
No dev packages

Thank you @izuzak . It work after install gofmt package.
Best Regards.


outdate NOTE in defmt.ferrous-systems.com

The note in the front page of https://defmt.ferrous-systems.com/ says:

NOTE this hosted version of the defmt book corresponds to the unreleased defmt v0.2.0, which is currently only available as a git dependency. If you are looking for defmt v0.1.x's documentation head to https://defmt.ferrous-systems.com.

but v0.2.0 has already been released

Should we maybe still keep a note for defmt-next.f-s.com indicating that this is served from main?


cmp.Diff() switching from property diffs to "new object" diff when object changes significantly

I am using cmp.Diff() with a reporter to manage some complex tests. The library is excellent but I have encountered confusing behaviour which also seems to be undocumented, unless I have missed it.
When a large portion of a slice struct changes, the slice is reported as an entirely new object. From what I can tell this happens when more than half of the properties change.
I cannot find this behaviour documented anywhere except a passing reference (possibly?) in the searchBudget variable .
https://github.com/google/go-cmp/blob/c3ad8435e7bef96af35732bc0789e5a2278c6d5f/cmp/internal/diff/diff.go#L185-L188
My tests assume that when I change a property of an object with 6 properties, I receive the associated diff, rather than arbitrarily seeing (for example) 3 changes, and then "a new object" when 4 changes are present.
I appreciate this may be unique to me but it caught me by surprise and took a considerable amount of time to troubleshoot.
I have posted a minimum reproducible example here - https://github.com/jgalliers/go-cmp-repro
go run . will show a diff with 3 changes followed by changing a property (bringing the total changes to 4) which converts the diff output to a single change, which is an entirely new object.
3 diffs:
[]*main.Parent{
        &{
                Id: "app",
                Slice: []main.Child{
                        {
-                               Src:              "src",
+                               Src:              "src2",
-                               Dst:              "dst",
+                               Dst:              "dst2",
-                               DstVersion:       "v1",
+                               DstVersion:       "v2",
                                Routes:           {"test1", "test2"},
                                DeployDependency: false,
                        },
                },
        },
  }

4 diffs:
[]*main.Parent{
        &{
                Id: "app",
                Slice: []main.Child{
-                       {
-                               Src:              "src",
-                               Dst:              "dst",
-                               DstVersion:       "v1",
-                               Routes:           []string{"test1", "test2"},
-                               DeployDependency: true,
-                       },
+                       {Src: "src2", Dst: "dst2", DstVersion: "v2", Routes: []string{"test1", "test2"}},
                },
        },
  }

Is this desired or expected behaviour? Is it possible to disable this behaviour?
I would vastly prefer to receive a full property-wise diff, each property of which is reportable via the vx/vy objects rather than suddenly receiving a vy object with IsValid() = false due to the sudden conversion to a null pointer.

Hi, assuming the searchBudget is the cause, we can adjust the value a little but not remove it. The search budget is necessary to keep the diffing algorithm as O(N), while the theoretical optimal diffing algorithm is O(N^2).
Assuming your repro is representative of what you usually do, then we could probably remove the searchBudget constraint if N is below a certain number since N^2 is still not that big if N is small.


Multi Discrete action space

I have a question concerning the multi-discrete action space .I'm supposed to have an action which is a vector not a scalar but for example in pql.py the action is a scalar (for different functions ). multiplying the values of the vector is not logic it's like working on a discrete space but with more actions.

Some algorithms are designed for discrete action spaces (the actions are integers) while others are designed for continuous action spaces (the actions are real-valued vectors). I am not sure I understood your question, how is the action space of your problem?

for example i have " self.action_space = spaces.MultiDiscrete([6,5,5])  " .PQL for example deals with multi-discrete space actions but the way the algorithm works is that you multiply the values of the vector' "self.num_actions =np.prod(self.env.action_space.nvec)'".even in the select_action function it returns a single scalar. whereas I need a vector as my action like for example action=[3 1 1]

Our implementations do not support MultiDiscrete action spaces, unfortunately.


Serialization of uintCV fails

When I make a contract call with a clarity value of uint that was created with uintCV from  @stacks/transaction 2.0.0, I get the following error:
TypeError: cv.value.toArrayLike is not a function
    serializeIntCV serialize.ts:44
    serializeCV serialize.ts:135
    args index.ts:131
    _callee3$ index.ts:127
    Babel 8
    _callee6$ index.ts:183
    Babel 8
    openContractCall index.ts:198
    doContractCall use-connect.ts:81
...

When using @stacks/transaction 2.0.0-beta.1, the serialization is done successfully.

maybe related to #150

From @friedger in Discord:

Could we please have an update of connect's dependency @stacks/transactions to 2.0 ? I am struggling with https://github.com/blockstack/connect/issues/151
I ended up pinning the resolution of transactions lib to 2.0.0-beta.1. This worked.
I would like to have my app working with transactions 2.0.0 or 3.0.0-beta. However, it does not work because there are some dependencies that work with BigInt and others that don't. In particular connect does not use BigInt while transaction 2.0.0+ does. Any app that requires transaction 2.0.0+ and connect might fail.

From @friedger in Discord:

Could we please have an update of connect's dependency @stacks/transactions to 2.0 ? I am struggling with #151
I ended up pinning the resolution of transactions lib to 2.0.0-beta.1. This worked.
I would like to have my app working with transactions 2.0.0 or 3.0.0-beta. However, it does not work because there are some dependencies that work with BigInt and others that don't. In particular connect does not use BigInt while transaction 2.0.0+ does. Any app that requires transaction 2.0.0+ and connect might fail.

@ahsan-javaid could you help with this given your recent work with the transactions package?

@markmhx Created the PR to upgrade the stacks transaction version in connect package.
PR link: https://github.com/blockstack/connect/pull/152
I don't have permissions to assign the reviewers on this PR. It will be great if you can assign a reviewer on this PR.

@friedger can you test this is fixed with the linked PR? https://github.com/blockstack/connect/pull/157
I updated stacks.js packages and need to confirm things are working as expected. I will test on my end with the test-app.

@fbwoolf Can you kindly share the test steps for the issue above?
Thanks

@fbwoolf Can you kindly share the test steps for the issue above?
Thanks

I think this is one that can stay assigned to me through QA. It will be hard to test locally. Basically, we just have to make sure connect modals work as expected and nothing is broken after updating the packages.

I did not find any issues when testing with the test-app so moving to QA done. Will wait for feedback from @friedger before merging.


Handle extra args and kwargs in all POST endpoints

Currently, POST requests fail when DRF's versioning is used:
TypeError: post() got an unexpected keyword argument 'version'

This is because not all endpoints were handling additional arguments (incl. version).

Coverage remained the same at 97.089% when pulling b34250ec94fa13bfcac1fc21ff1dcbb3fd84c052 on sloria:versioning-compat into 42d039b473bc18080d58656f50f379005cd70499 on Tivix:master.

@sloria Can you give us more details on when exactly this happens and what DRF version are you using? (version param should be accessed by request.version)

@mariodev  I am using Django==1.11.6 and djangorestframework==3.7.1 with the following settings and urls:
REST_FRAMEWORK = {
    'DEFAULT_AUTHENTICATION_CLASSES': [
        'rest_framework.authentication.TokenAuthentication',
        'rest_framework.authentication.SessionAuthentication',
    ],
    'DEFAULT_VERSIONING_CLASS': 'rest_framework.versioning.URLPathVersioning',
    'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.CursorPagination',
    'PAGE_SIZE': 10,
}

# core/urls.py
urlpatterns = [
    url(r'^(?P<version>(v1))/', include('api.urls', namespace='api')),
]

# api/urls.py
urlpatterns += [
    url(r'^auth/', include('rest_auth.urls')),
]

When I send a POST request to /v1//auth/password/change/, I get the unhandled TypeError above.

Thanks @sloria


unsupported rserve version

Hi,
I recently upgraded roger to address https://github.com/senseyeio/roger/issues/23 but now when I try to connect to our Rserve daemon roger reports:
The version of RServe installed is not officially supported. Please consider upgrading
to the latest version of RServe.

In terms of the Rserve package version we're using a relatively recent install from cran.rstudio.com. sessionInfo() reports Rserve_1.7-3.
I'm relatively new to R but is there some way to install a newer version? What version is required? We don't install a specific version of Rserve so I'm wondering why our recent install is behind Roger's minimum version?
Thanks,
brian

Hmm...
I did a little more digging and I think the version that's available in cran is 1.7-3, which matches our install, but the latest version of rserve is 1.8-4 (https://rforge.net/Rserve/news.html).
Is there a recommended way to install a version of Rserve that's supported by Roger without using cran?

And, further answering my own question, it seems like this is the recommend installation mechanism:
install.packages("Rserve",,"http://rforge.net/")

Hi, thanks for the issue.
I am running with 1.7.3 and do not experience the warning message. In addition, the docker image used in the tests is running 1.7.3. I have added a print out of the RServe version on the docker image in 831ec5fe3aa59fdb7bf7452609d43008d5608d67 for future reference.
Maybe there is another factor affecting it? Does it work with 1.8.4?

@dareid thanks for the quick response.
There may be something else that caused this but I was able to workaround the issue by installing Rserve 1.8-4. Once I updated to roger commit f8fb1838724 I was unable to connect to Rserve running 1.7-3. Once I installed Rserve 1.8-4 from rforge.net the error went away.
I'm happy to provide more information if that helps, just let me know what I can do.
brian

it looks like install.packages("Rserve",,"http://rforge.net/") installs version 1.7.3, which gives this error.  Weird!

@integrii thanks for the additional information. I have updated the tests to use the rforge version by default and it appears like the tests are passing.
However, I noticed that if I connected to an incorrect port it incorrectly reported that it was not supported instead of a connection issue, any chance that could be the problem you are seeing?

It has been awhile now, but that might have been it.  Thanks for following up!


Fix for SRV records with the standard naming scheme

Currently, the health check lambda gets the service name by parsing the resource record up to the first dot. As the usual naming scheme is _service._protocol.domain, e.g. _xmpp-server._tcp.google.com, the function would search for just _xmpp-server which is then not found in the container list.
This PR just changes the service name to include the first two components. It should probably be made a bit more resilient.
Here's the Wikipedia link to the record format: https://en.wikipedia.org/wiki/SRV_record

Closed in favor of #34


Add chores to the menu

User story
As a User, I want to be able to navigate to the chores page, so that I can see my chores and assign chores
Acceptance criteria
Chores option shows on the left menu
Selecting the chores goes to chores page

Is this completed?

Yes, it is completed.


zero length normals

Hi, I have this sample point cloud collected with Azure Kinect DK: https://www.dropbox.com/s/9qjmqt98n4fpse0/0.1ms_to_0.05ms_Ed_500mm.ply?dl=0
I used the K4A.sln --> transformation_example to create the .ply sample.
I seem to have zero length normals, or normals with infinity/undefined coefficients.
Any clues or settings need to be changed to avoid Nan normals?
Thanks!

Although you can see "it" from color camera,there is a case you will not see "it" from depth camera.
While transformation facing this problem,transformation treat "it" as zero position.
And then,We could not compute normal from point cloud which all of them has exactly same position.

Is there a way to retrieve and save point cloud (.ply for instance) and have the normals as well?

Is there a way to retrieve and save point cloud (.ply for instance) and have the normals as well?

It seems like completely the other question,and I don't know the answer.
I recommend you to create another issue.

The transformation_example does not compute surface normal, it only computes point cloud xyz with color (the example is just leveraging ply as a simple format to allow user visualize the point cloud in MeshLab or other tools). To compute the normal from a depth point cloud, there are many ways to do that, naïve way is estimating normal from neighbor pixels but need to be careful with the depth discontinuity area. Or you can read some more papers with advanced way. Feel free to contribute to the example with normal computation :)


Run prettier on build

From discussion on https://github.com/resin-io/resin-sdk/pull/445#issuecomment-352741660.
With this PR, we'll run prettier in CI, so failing to run it will fail the build, and it'll automatically get run if you run builds or tests locally, which should make it pretty hard to forget to do in the first place. Seems super quick right now. We can reconsider if it becomes a serious slowdown, but for the SDK use case I don't think it matters too much.

We're hitting some new rate limiting problems in #445 - I'm going to resolve them there, merge that, then rebase this on top and these tests should start passing again :crossed_fingers:


"native to"

>>> get_assertion_definitions(u'The giant panda is a bear native to south central China.')
>>> [u'native', u'bear native']

The correct output should be just [u'bear']. We need to find a way to handle "native to".

This is a parsing bug. SpaCy thinks native is the head of a bear native to ....  I tend to leave this be, since we can't fix every bug spaCy produces, unless this a systematic errors that a fix can actually improve a whole class of sentences or unless we really need native to work

In case it's not clear, the correct analysis is (with some structure omitted for brevity):
[NP [det a]
    [N' [noun bear]
        [AP [adj native]
            [PP to [NP south central China]]]]

FWIW, START makes the same parsing error about analyzing "bear native" as a compound instead of parsing the trailing AP (https://github.com/infolab-csail/START/issues/392).  Trailing APs on NPs are rare, and I'm not surprised that both parsers muff this example.


[AUTOPATCHER-kernel] Kernel upgrade to version <IP_ADDRESS> - branch 3.0-dev

[AUTOPATCHER-kernel] Kernel upgrade to version <IP_ADDRESS> - branch 3.0-dev
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=592119&view=results
buddy build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=592123&view=results
Full build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=593157&view=results

Closing in favor of https://github.com/microsoft/azurelinux/pull/9497


[FEATURE] Hope to create a secret in the output page through the UI

Is your feature request related to a problem? Please describe.

secret are useful in the Monitoring&Logging>Logging>output page, but there is no place to create secret in the UI.

Describe the solution you'd like

hope to create secret through the harvester UI
Describe alternatives you've considered

Additional context

Will move to ready for testing after namespace PR is merged.

@n313893254 since https://github.com/harvester/dashboard/pull/550 isn't merged in yet, I'll move this back to Review - if that works?
I noticed that I can create a secret, but not currently in the cattle-logging-system namespace.
Off of Harvester Version: master-6fd9a5bb-head

@irishgordo Sorry. The issue should move back to Review.

validation issue
@n313893254 I noticed that when building an output for ElasticSearch to an local docker ElasticSearch (version: 6.8.23) that the POST sees a 201, but th index page of all "Outputs" is empty.
Do I need to do something in particular to see the list of Outputs?
Also from https://github.com/harvester/dashboard/pull/552:

Go to create a secret in the cattle-logging-system namespace.

I noticed that the cattle-logging-system namespace was not available but the cattle-monitoring-system namespace was and I could create secrets from that.

I'm also noticing in "Cluster Outputs" that I'm not able to see any of the secrets that I created:

Hi @irishgordo ! Thanks for your testing!
We need to enable cattle-logging-system when creating secrets, I'll fix it.
Cluster Outputs only can choose the secrets in cattle-logging-system so you cannot see the secret just created if it's not in cattle-logging-system.
And I'll try to reproduce:

@DaiYuzeng I noticed that when building an output for ElasticSearch to an local docker ElasticSearch (version: 6.8.23) that the POST sees a 201, but th index page of all "Outputs" is empty.

@irishgordo I filed an issue to track:

@DaiYuzeng I noticed that when building an output for ElasticSearch to an local docker ElasticSearch (version: 6.8.23) that the POST sees a 201, but th index page of all "Outputs" is empty.
Do I need to do something in particular to see the list of Outputs?
Also from https://github.com/harvester/dashboard/pull/552:

I guess you created a resource (maybe Secret) in cattle-monitoring-system at first and then you went to create an Output which preset namespace is cattle-monitoring-system.
You would realise that you cannot see it just created.
Can you please have a try to switch Output namespace manually to default after this issue is ready-for-testing?
I guess you will see it on the Output list page.

validation question:
@DaiYuzeng thanks for the response back :smile:
Question:

is it expected that a user must create the secret for Logging-> "Cluster Output" through the "Access Embedded Rancher UI"?

As, I wasn't noticing a way to preselect the cattle-logging-system namespace from the dashboard:

I noticed that I was unable to create a secret via Harvester dashboard and place inside of cattle-logging-system.
I was able to access the Embedded Rancher, https://harvester-vip-ip/dashboard/c/local/explorer#cluster-metrics, and build the secret via a kubectl shell from their with:
> kubectl create secret generic elasticsearchmanualinembeddedrancher --from-literal=passwordtouse='harvestertesting' --namespace cattle-logging-system
secret/elasticsearchmanualinembeddedrancher created

Then once it was built from the "Embedded Rancher", I was able to use that secret for a Cluster Output, before creating a Cluster Flow.
I did notice that after creating the secret via Embedded Rancher on Harvester that when I navigated to "Advanced" -> "Secrets" -> "Create" that the Namespace was already set of cattle-logging-system - yet it was unavailable to be selected from the drop-down list.
I was able to create a Secret in the default namespace with an Output in the default namespace and a Flow in the default namespace and validate that logs got funneled into ElasticSearch, visually through Kibana - leveraging the secret that provided the ElasticSearch password.

I also created https://github.com/harvester/harvester/issues/3527 - to track the UI's tag overflowing if the Cluster Output name was 42 characters long

No, it's unexpected.
I took a record here:

May I know your UI-index? I can create a secret in cattle-logging-system in the latest UI.
(UI Index: https://releases.rancher.com/harvester-ui/dashboard/latest/index.html)

I also created https://github.com/harvester/harvester/issues/3527 - to track the UI's tag overflowing if the Cluster Output name was 42 characters long

We'll fix it at v1.1.2, Thanks!

validation issue
Hi @DaiYuzeng  - thanks for the response back :smile:  - I was working through attempting to re-test to see if I could see the "cattle-logging-system" namespace in the secret dropdown menu selection list, but I'm not seeing it.
The flow was:

install v1.1.2-rc1 on single vm
login
head to Advanced -> Settings:

update ui-index
update ui-source from auto to external

head to Monitoring & Logging -> Logging -> Configuration, click save on fluentbit & fluentd
head to Advanced -> Secrets -> Create, attempt to see "cattle-logging-system" namespace available

It looks like the requests out to /namespace are correct, and we can see the JSON payload coming back with the appropriate results.
Also the KubeConfig from the Harvester node, does show the namespaces.

I've also tried with:
ui-index:
https://releases.rancher.com/harvester-ui/dashboard/latest/index.html
ui-plugin-index:
https://releases.rancher.com/harvester-ui/plugin/harvester-latest/harvester-latest.umd.min.js

In the Settings and wasn't able to see "cattle-logging-system" namespace as an available drop-down selection from the Secret.

@WuJun2016 & @DaiYuzeng
This may have been an environmental issue on my end :sweat_smile:
But I am able to successfully now see the "cattle-logging-system" namespace available in the drop down section from the Secret creation form.
Validating that I'll go ahead and close this out :smile: :+1: - thanks for your help!


refactor(test): remove unnecessary vec! macro

TODO

[x] Use cargo fmt
[ ] Add necessary tests
[ ] Add changelog entry
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Codecov Report

Merging #722 (5ef6244) into master (34da140) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #722   +/-   ##
=======================================
  Coverage   88.31%   88.31%
=======================================
  Files          41       41
  Lines        4500     4500
=======================================
  Hits         3974     3974
  Misses        526      526

Impacted Files
Coverage Δ

src/flags/permission.rs
94.91% <100.00%> (ø)

src/flags/size.rs
98.41% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi @TeamTamoad, maybe we should not change args to argv.
args seems to be more intuitive, argv seems to be a historically reserved choice of c

args seems to be more intuitive

I agree with you, but almost all code in the test use argv. I think it's should be the same for all tests.

As @zwpaper mentioned args is probably better here, but since this is just tests and we are already using argv pretty much everywhere else, it should be fine.


Remove handle inheritance workaround

https://github.com/aspnet/KestrelHttpServer/pull/2944 mitigated the issue on windows for 2.2. https://github.com/dotnet/corefx/issues/32902 fixed it x-plat for 3.0. Remove the 2.2 mitigation once the 3.0 fix is available.

Need to wait until Kestrel retargets to netcoreapp3.0.


[bug?] cannot run integration test

Apache Iceberg version
main (development)
Please describe the bug 🐞
On Mac, anyone having issue running make test-integration on the current main branch?
I'm having issues but not sure if its due to my local env

Been facing the same issue since yesterday when I rebased latest main branch to my dev branch. Just realized that tests are not running on main branch itself.
I did make clean and make test-integration-rebuild and now I'm seeing more errors than before.
Although I did run some of those integration tests through IDE and are running fine.

Full pytest report here: https://gist.github.com/kevinjqliu/a0e8e2199bd8064757eb2b40409e0794
Here's the breakdown of the errors:
171 pyarrow/error.pxi:92: OSError
* 87 pyiceberg/io/pyarrow.py:2426: in write_parquet
* 83 with write_manifest_list(

write_parquet stack trace:
pyiceberg/io/pyarrow.py:2426: in write_parquet
    with fo.create(overwrite=True) as fos:
pyiceberg/io/pyarrow.py:311: in create
    output_file = self._filesystem.open_output_stream(self._path, buffer_size=self._buffer_size)
pyarrow/_fs.pyx:887: in pyarrow._fs.FileSystem.open_output_stream
    ???
pyarrow/error.pxi:155: in pyarrow.lib.pyarrow_internal_check_status
    ???

write_manifest_list stack trace
pyiceberg/table/update/snapshot.py:253: in _commit
    with write_manifest_list(
pyiceberg/manifest.py:924: in __enter__
    self._writer.__enter__()
pyiceberg/avro/file.py:258: in __enter__
    self.output_stream = self.output_file.create(overwrite=True)
pyiceberg/io/pyarrow.py:311: in create
    output_file = self._filesystem.open_output_stream(self._path, buffer_size=self._buffer_size)
pyarrow/_fs.pyx:887: in pyarrow._fs.FileSystem.open_output_stream
    ???
pyarrow/error.pxi:155: in pyarrow.lib.pyarrow_internal_check_status
    ???

One realization is that the manifest cache is implemented as a global cache.
https://github.com/apache/iceberg-python/blob/de47590c6ac4f507cb2337c20504a62c484339f9/pyiceberg/table/snapshots.py#L234-L238
And kept in memory until eviction.
And since ManifestFile has an IO component, I think the file descriptors are kept alive and never cleaned up.
Why does this only affect M1 Mac? I have no idea.

I should be more specific. Reading (and caching) a ManifestFile object (or a list of them) ultimately keeps a bunch of PyArrowFile objects alive (anytime io.new_input is called).
In PyArrowFile, the open and create methods do not automatically clean up resources https://github.com/apache/iceberg-python/blob/de47590c6ac4f507cb2337c20504a62c484339f9/pyiceberg/io/pyarrow.py#L258-L318
I think this was part of the issue since I had to increase the system file descriptors limit.

That's a very interesting observation 👀 I'm so curious to understand what's happening. If that's in fact what's happening, I think your proposed solution sounds promising...
I'm still trying to understand this issue thoroughly
In the lru cached _manifests we are caching a list of manifest files, but in fact we are only reading a single manifest list, and deserializing each of the records as ManifestFile Records. So the only PyArrowFile that I'd expect to be left 'open' according to this theory would be the manifest_list
https://github.com/apache/iceberg-python/blob/de47590c6ac4f507cb2337c20504a62c484339f9/pyiceberg/manifest.py#L623-L639

I took a step back and realized the fundamental issue was the newly introduced cache.
Without the cache, everything works fine.
With the cache, things break.
Going a layer deeper, this probably means the bug is only for cache hits, as cache misses will just recompute.
So the failure scenario is when the cache hits, but the return value is wrong.
Fundamentally, there are a couple issues with the function definition
@lru_cache
def _manifests(io: FileIO, manifest_list: str) -> List[ManifestFile]:
    """Return the manifests from the manifest list."""
    file = io.new_input(manifest_list)
    return list(read_manifest_list(file))

First, the cache key is both io and manifest_list, whereas we just want the key to be manifest_list
Second, the result is a list, which can be mutated leading to the wrong result.
Here’s an example to showcase the different cache keys
cache = {}

def _manifests(io: FileIO, manifest_list: str, snapshot: Snapshot) -> List[ManifestFile]:
    """Return the manifests from the manifest list."""
    # key = (manifest_list, )  # works
    # key = (manifest_list, io)  # fails
    key = (manifest_list, snapshot)  # works
    if key in cache:
        return cache[key]
    cache[key] = list(read_manifest_list(io.new_input(manifest_list)))
    return cache[key]

Without digging into where it is breaking or why only for M1 Macs, there are 2 potential solutions:

Move the manifest cache to the Snapshot instance
Use the cachetools library to specify manifest_list as the only cache key (see stack overflow)

#1185 uses Snapshot instance specific cache
#1187 uses global cache via the cachetools library to specific the cache key
I recommend #1187

Hi, i'm having the same issue. Is there a workaround I can use as a client? Can you do a new point release with the fix? Thanks!

@antonioalegria This is currently fixed in the main branch, which we use to run integration tests.
How are you hitting this issue? We can do a hotfix release if needed

I'm hitting this exact same issue as described in this comment (https://github.com/apache/iceberg-python/issues/1162#issuecomment-2344408943), when running polars on an iceberg table I have in S3.

Thanks!

Hi folks, I'm going through a career transition, so my apologies for arriving on this discussion a little late.
@antonioalegria @kevinjqliu I don't think the bugged Manifest caching feature was ever released. Here's the version of manifest implementation that was released in 0.7.1:
https://github.com/apache/iceberg-python/blob/f92994e85e526502a620506b964665b9afd385fe/pyiceberg/table/snapshots.py#L233-L256
Are we sure we are saying the same exact error? Would you mind sharing the exception trace @antonioalegria ?

Well, maybe the bug is different but I'm getting it when doing a load of a metadata file when doing scan_iceberg in Polars.
It only happens with certain objects:
When reading information for key '' in bucket '': AWS Error NETWORK_CONNECTION during HeadObject operation: curlCode: 6, Couldn't resolve host name
Traceback (most recent call last):

File "", line 351, in scan_table
return pl.scan_iceberg(location)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/.venv/lib/python3.12/site-packages/polars/io/iceberg.py", line 143, in scan_iceberg
source = StaticTable.from_metadata(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/.venv/lib/python3.12/site-packages/pyiceberg/table/init.py", line 1693, in from_metadata
metadata = FromInputFile.table_metadata(file)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/.venv/lib/python3.12/site-packages/pyiceberg/serializers.py", line 113, in table_metadata
with input_file.open() as input_stream:
^^^^^^^^^^^^^^^^^
File "/.venv/lib/python3.12/site-packages/pyiceberg/io/pyarrow.py", line 270, in open
input_file = self._filesystem.open_input_file(self._path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pyarrow/_fs.pyx", line 789, in pyarrow._fs.FileSystem.open_input_file
File "pyarrow/error.pxi", line 155, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
OSError: When reading information for key '' in bucket '': AWS Error NETWORK_CONNECTION during HeadObject operation: curlCode: 6, Couldn't resolve host name

See related issue: https://github.com/apache/arrow/issues/40539

@antonioalegria i think thats a different issue
Couldn't resolve host name

versus the origin issue
AWS Error NETWORK_CONNECTION during CreateMultipartUpload operation: curlCode: 43, A libcurl function was given a bad argument


Generate a static binary by disabling cgo

As part of the Go 1.20 release it seems like the default for CGO_ENABLED is no longer carried over from the tools. This leads to linking issues on systems that use different versions of glibc from what the base image uses. See https://github.com/golang/go/issues/58550 for more details.
This change should fix #16

This also fixes Netreap on Rocky Linux 9 and I presume all other RHEL-9 based distros.

It looks like #21 supersedes this PR?

Ugh, realized I left review comments here instead of on #21. I'll copy them over to that one

Argh, sorry, looks like I stuffed up the branches for the PR. Let me close this one in favor of #21


Please give user a chance to choice the button color.

I really really love it, thanks for your work. But please give me a function to choice the button color.
This is the best third-party FB application I have used.

Different colour schemes will be implemented with Themes (#1).


Simpler diffing

Currently we're using one library to generate a unified diff string, then parse it into a datastructure.
This is inefficient. We should use a lower level myers diff algorithm instead:

https://github.com/hexops/gotextdiff/blob/main/myers/diff.go
https://github.com/aymanbagabas/go-udiff
https://github.com/pkg/diff/tree/main
https://github.com/covrom/diff

It should be fast and memory efficient (check the issues and benchmarks)
This one looks promising: https://github.com/thepudds/patience-diff/blob/main/diff.go
It would have to be modified to output data structures instead of a unified diff script.
Trying this as it seems most uptodate: https://pkg.go.dev/github.com/rogpeppe/go-internal/diff@master

Maybe use a diff-match-patch implementation instead for the initial diffing. It can be used for line diffing
For a SimHash alternative, maybe consider LSH

https://github.com/RyuaNerin/go-krypto

Other articles:

https://fservant.github.io/papers/Servant_Jones_ICSE17.pdf

https://fservant.github.io/papers/Servant_Jones_FSE12.pdf

https://fservant.github.io/papers/Servant_Jones_VISSOFT13.pdf

https://eprints.lancs.ac.uk/id/eprint/148836/2/ICPC_2020_v1_CR_.pdf

https://www.youtube.com/watch?v=ohwMvoZfj1E

SZZ algorithm

SZZ Unleashed: An Open Implementation of the SZZ Algorithm

https://github.com/wogscpar/SZZUnleashed

https://medium.com/carbon-consulting/explaining-lsh-minhash-simhash-c3cc33040030

SZZ tools:

https://github.com/ishepard/pydriller
https://github.com/wogscpar/SZZUnleashed
https://github.com/clowee/OpenSZZ

A neural variant of SZZ: https://baolingfeng.github.io/papers/ASE2023.pdf


Add Chatgpt function call support

Information about this new OpenAI feature:
https://platform.openai.com/docs/guides/gpt/function-calling

relate pr: https://github.com/64bit/async-openai/pull/79

Related async-openai PR merged and released as of v0.12.0. Nice!
https://github.com/64bit/async-openai/releases/tag/async-openai-v0.12.0

yet it is have released！

Tracking:

tiktoken-rs need to update async-openai version to 0.12.0


dmGWAS clean up and documentation

As per the directory structure, clean up things in dmgwas.
Document how it was installed, detailing any custom code modifications, issues found and fixed (as a README or in similar file), any custom alternative approaches followed to make the tool running, that is not described in the existing documentation.

And, of course, actually upload clean code that can be integrated into the
rest of the program...
On Thu, Jan 7, 2016 at 1:43 PM, graphanalytics<EMAIL_ADDRESS>wrote:

Assigned #11 https://github.com/NCBI-Hackathons/Network_SNPs/issues/11
to @hagenaue https://github.com/hagenaue.
—
Reply to this email directly or view it on GitHub
https://github.com/NCBI-Hackathons/Network_SNPs/issues/11#event-508585016
.

--
Megan Hastings Hagenauer, Ph.D.
Research Investigator in the Molecular, Behavioral Neuroscience Institute
Instructor in the Department of Psychology
University of Michigan-Ann Arbor

This is diff output between the original copy of dmGWAS and the version patched yesterday:
https://github.com/NCBI-Hackathons/Network_SNPs/blob/master/dmGWAS.diff
If you're unfamiliar with diff or patch, it creates text file(s) that show the differences between two files (or files in directories) that can be interpreted by the patch program.
Which means:
wget http://bioinfo.mc.vanderbilt.edu/dmGWAS/dmGWAS_3.0.tar.gz
tar zxf dmGWAS_3.0.tar.gz
patch -p0 < dmGWAS.diff

should work, with the dmGWAS/ directory now containing those fixes.
NB: for some reason this my version of patch on OSX 10.10.5 doesn't work with this diff file, but it does work on the Linux instance we've been using (Ubuntu 14.04).

done


Fix property path for definitions

No models were being generated, as the parser was expecting properties to be nested under a deeper path than they are (properties.attributes.properties vs properties).
This change fixes it for the pet store example from swagger.io, as well as other cases I've tried.  If there's a valid reason to support the properties.attributes.properties path, I'm happy to update this PR with a check so that the deeper path is used it present (falling back to simply properties) - juts let me know.

That's weird. Looking at my swagger I have that nesting. What is generating your OpenAPI? I'm using jsonapi-server.
definitions: {
  exhibitions: {
    type: "object",
      properties: {
        id: {
          type: "string"
        },
        type: {
          type: "string"
        },
        attributes: {
          type: "object",
          properties: {
            machine-name: {
              type: "string"
            },
            title: {
              type: "string"
            },

Ah, it looks like we may be striking differences between JSON API and OpenAPI (formerly known as Swagger).  I haven't dug too deeply into the respective specs, but if they're similar enough when it comes to model definitions that this path is all that differs, we should be able to support either by using properties.attributes.properties if it exists, but falling back to properties if not (but it exists).  If you're happy with that approach, I'll push another commit which implements it.
I'm ultimately wanting to generate Ember Data models (and potentially other resources) from OpenAPI generated from gRPC service definitions by protoc-gen-swagger, in order to streamline/automate the end-to-end build process.

After re-reading your readme, it sounds as though you're using jsonapi-server to generate a Swagger/OpenAPI document.  Perhaps jsonapi-server is generating non-standard (or just overly verbose) Swagger/OpenAPI docs?  The JSON you posted here looks more like the JSON API examples than OpenAPI examples, so it may be that jsonapi-server is just conforming the JSON API doc into the OpenAPI structure, but not conforming it to OpenAPI norms...

Yes that's it. But lets support OpenAPI by default (which was the goal of the project) and switch to the version spat out by jsonapi-server when needed (which is my use-case). I can't see a specific flag in my swagger--there are 52 mentions. Any thoughts? I can add a property to info. For example info.generator: 'jsonapi-server' or info.nestedAttributes: true.

Since the properties.attributes.properties path doesn't seem to exist in "normal" OpenAPI, we should be able to get away with just checking for its existence and using it (instead of just properties) if it's there.  Otherwise, info.generator seems like a reasonable approach - that way, if any other Swagger/OpenAPI generators turn out to have similar discrepancies, it's easy enough to add the appropriate conditional logic (coupled with encouraging users to add the info.generator property with the appropriate value).

Super. I'll commit whatever you submit here.

Thanks for your help @pauln !


[SPARK-10991][ML] logistic regression training summary handle empty prediction col

LogisticRegression training summary should still function if the predictionCol is set to an empty string or otherwise unset (related too https://issues.apache.org/jira/browse/SPARK-9718 )

Merged build triggered.

Merged build started.

Test build #43433 has started for   PR 9037 at commit b9cb751.

Test build #43433 has finished for   PR 9037 at commit b9cb751.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BinaryHashJoinNode(
case class BroadcastHashJoinNode(
trait HashJoinNode

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #43446 has started for   PR 9037 at commit 62fa50e.

Test build #43446 has finished for   PR 9037 at commit 62fa50e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

cc @jkbradley who asked for this change

re-ping @jkbradley

LGTM

Hey @jkbradley or @dbtsai could you merge this if it looks ok to you as well? @yu-iskw took a look and the change is similar to the change we did as part of https://issues.apache.org/jira/browse/SPARK-9718 for the other model.

Test build #2149 has started for PR 9037 at commit 62fa50e.

Test build #2149 has finished for PR 9037 at commit 62fa50e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM except the minor style.

Test build #47568 has started for PR 9037 at commit 0c14997.

Test build #47568 has finished for PR 9037 at commit 0c14997.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Merged into master. Thanks.


PostgresDatabaseMigrator Wrong Order

Contact Details
<EMAIL_ADDRESS>Version
8.x (develop, pre-release), 8.x
On which operating system(s) are you experiencing the issue?
Linux
Using which broker(s) did you encounter the issue?
No response
What are the steps required to reproduce the issue?
Wrong SQL scripts order in PostgresDatabaseMigrator:
https://github.com/MassTransit/MassTransit/blob/4fe74cde9368b910f39f990edb0bfbbc605bccaf/src/Transports/MassTransit.SqlTransport.PostgreSql/SqlTransport/PostgreSql/PostgresDatabaseMigrator.cs#L22-L23

Current:
ALTER SCHEMA "{1}" OWNER TO "{0}";
GRANT "{0}" TO "{2}";

Expected:
GRANT "{0}" TO "{2}";
ALTER SCHEMA "{1}" OWNER TO "{0}";

Can't change owner without grant.

What is the expected behavior?
.
What actually happened?
.
Related log output, including any exceptions
No response
Link to repository that demonstrates/reproduces the issue
No response

You'd need to provide a specific scenario where this fails because it works everywhere I've tried it.
Note that you should not be using the same username as the admin username.


Make a safe wrapper for dotenv

To solve #41

@sebashack I think this is ready for another review!

@sebashack It is ready for another review. Could you please take some minutes to take a look? Thanks

@sebashack Sure, I'll do. Thanks.

@sebashack Thanks for the review. Well, I'm not sure how we can deal with null envs. I mean, even if we add something to the scheme.yml to specify that a variable can be empty we won't be able to set it on the environment. Perhaps, I missunderstand the issue. I think we can discuss about it.

@sebashack I change the logic here.
Since, we are going to have envs defined in the dotenvs and the scheme.yml, we need to match those definitions.
In one way, if the envs defined in the dotenvs are missing in the scheme.yml we should report that. So, that we make sure that all envs defined in the dotenvs have their respective configuration in the scheme.yml.
In the second way, if the configurations defined in the scheme.yml are not related to a required env in the dotenvs we should report that, too.
Otherwise, we should start checking the value of the envs with the expected type.
Please, let me know what do you think.


The following code does not compile

I have this code from systemRDL document but cna't get it to compile and generates the following error.
error: Address map 'top' must contain at least one reg, regfile, mem, or addrmap.
fatal: Elaborate aborted due to previous errors
addrmap top {
regfile example {
reg some_reg { field {} a; };
some_reg a  @0x0;
some_reg b  @0x4;
some_reg c;
some_reg d @0x10;
};
};

I think you need to name the regfile. Try adding a name after the closing
brace of the regfile. The way I think of it, "example" is the class name
and the name after the closing brace is the instance name. Not sure if this
is the right way of thinking about it. Maybe someone on this list who knows
more could explain.
On Sun, Jul 7, 2019 at 10:58 PM hmohajeri<EMAIL_ADDRESS>wrote:

I have this code from systemRDL document but cna't get it to compile and
generates the following error.
error: Address map 'top' must contain at least one reg, regfile, mem, or
addrmap.
fatal: Elaborate aborted due to previous errors
addrmap top {
regfile example {
reg some_reg { field {} a; };
some_reg a @0x0 https://github.com/0x0;
some_reg b @0x4 https://github.com/0x4;
some_reg c;
some_reg d @0x10 https://github.com/0x10;
};
};
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SystemRDL/systemrdl-compiler/issues/25?email_source=notifications&email_token=ABB6WGQPGHU3U52UWGKXKMTP6LJQHA5CNFSM4H6YDTAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5YMBQQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABB6WGXXN4MPZ75B3BZ266TP6LJQHANCNFSM4H6YDTAA
.

@PRWald is correct. The example shown in the spec is a little misleading since they do not properly instantiate the regfile declared as example. Declaring the regfile definition only makes the type available in the local namespace. Since the example does not create an instance of the component, it does not exist, and ends up violating one of the semantic checks (components cannot be empty)
A corrected example would create an instance of example as shown here:
addrmap top {
    regfile example {
        reg some_reg { field {} a; };
        some_reg a @0x0;
        some_reg b @0x4;
        some_reg c;
        some_reg d @0x10;
    };
    example example_inst @ 0x0;
};

I already have a running list of typos/oversights the RDL spec authors missed here: https://github.com/SystemRDL/systemrdl-compiler/blob/master/docs/implementation_notes/systemrdl_spec_issues.md
I'll add this one to the list.

Many thanks for the help and appreciate it. The code now works beautifully. Amykyta3, thanks for the errata link.


Sort props

Codecov Report
Base: 55.82% // Head: 53.70% // Decreases project coverage by -2.11% :warning:

Coverage data is based on head (b1e50b3) compared to base (153832f).
Patch coverage: 1.76% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #148      +/-   ##
============================================
- Coverage     55.82%   53.70%   -2.12%
+ Complexity      574      573       -1
============================================
  Files           123      128       +5
  Lines          2250     2333      +83
  Branches        285      298      +13
============================================
- Hits           1256     1253       -3
- Misses          919     1007      +88
+ Partials         75       73       -2

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <ø> (ø)

...rc/main/java/seedu/address/logic/LogicManager.java
37.50% <ø> (+1.50%)
:arrow_up:

...eedu/address/logic/commands/SortBuyersCommand.java
0.00% <0.00%> (ø)

.../address/logic/commands/SortPropertiesCommand.java
0.00% <0.00%> (ø)

...in/java/seedu/address/logic/parser/CobbParser.java
62.06% <0.00%> (-2.22%)
:arrow_down:

.../address/logic/parser/SortBuyersCommandParser.java
0.00% <0.00%> (ø)

...ress/logic/parser/SortPropertiesCommandParser.java
0.00% <0.00%> (ø)

...address/logic/sortcomparators/BuyerComparator.java
0.00% <0.00%> (ø)

.../address/logic/sortcomparators/NameComparator.java
0.00% <ø> (ø)

...address/logic/sortcomparators/PriceComparator.java
0.00% <0.00%> (ø)

... and 12 more

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.