Large number of nonzeros in (very sparse) SDP solving

Heya MosekTools team!
I've been running into a problem with Mosek (similar to the one given in #40): when solving a very sparse SDP, the number of nonzeros that I've been running into has been huge. For example, here's a simple problem (with optimal value 0):
using MosekTools, JuMP, SparseArrays, LinearAlgebra

m = Model(Mosek.Optimizer)

n = 100

@variable(m, x[1:100])
@variable(m, t)

@objective(m, Min, t)
Q = [
    sparse([t])     x'
    x               sparse(I(n))
]
@constraint(m, Q ∈ PSDCone())

optimize!(m)

Running this, we get:
Presolve terminated. Time: 0.00
Problem
  Name                   :
  Objective sense        : min
  Type                   : CONIC (conic optimization problem)
  Constraints            : 5151
  Cones                  : 0
  Scalar variables       : 101
  Matrix variables       : 1
  Integer variables      : 0

Optimizer  - threads                : 4
Optimizer  - solved problem         : the primal
Optimizer  - Constraints            : 5151
Optimizer  - Cones                  : 1
Optimizer  - Scalar variables       : 102               conic                  : 102
Optimizer  - Semi-definite variables: 1                 scalarized             : 5151
Factor     - setup time             : 2.18              dense det. time        : 0.00
Factor     - ML order time          : 1.43              GP order time          : 0.00
Factor     - nonzeros before factor : 1.33e+07          after factor           : 1.33e+07
Factor     - dense dim.             : 0                 flops                  : 4.57e+10

The problem here is specifically Factor     - nonzeros before factor : 1.33e+07 (!). The number of nonzeros here should be something like 3n + 1. In fact, this is so large, I'm not even sure where this number could come from! (Certainly even concretizing the whole matrix Q yields only a total number of 101^2 nonzeros. There are probably some additional affine constraints in the cone embedding, I'm sure, but still.)
Additionally, comparing the number of nonzeros with something like COSMO.jl is many times larger than presented. (E.g., I think this might rule out the issue that JuMP/MOI is not correctly handling sparsity, but I could be wrong.)
Anyways, it would be extraordinarily helpful to be able to solve these big SDPs using a relatively robust interior point method, so I'd love to know if I'm doing something wrong here :)
Thanks!

Note sure what this Factor - nonzeros before factor means and why it is so large.
Note that Mosek does not support PSD constraints and it is reformulated as a PSD variables. Therefore, you don't need to create free variables t and x, you can just take it from Q. For instance, you can do:
using MosekTools, JuMP

m = Model(Mosek.Optimizer)

n = 100

@variable(m, Q[1:(n + 1), 1:(n + 1)], PSD)
t = Q[1, 1]
x = Q[1, 2:(n + 1)]
for j in 2:n
    for i in 2:j
        if i == j
            @constraint(m, Q[i, j] == 1)
        else
            @constraint(m, Q[i, j] == 0)
        end
    end
end

@objective(m, Min, t)

optimize!(m)

However, I still have a lot of nonzeros before factor:
Problem
  Name                   :
  Objective sense        : min
  Type                   : CONIC (conic optimization problem)
  Constraints            : 4950
  Cones                  : 0
  Scalar variables       : 0
  Matrix variables       : 1
  Integer variables      : 0

Optimizer started.
Presolve started.
Linear dependency checker started.
Linear dependency checker terminated.
Eliminator started.
Freed constraints in eliminator : 0
Eliminator terminated.
Eliminator - tries                  : 1                 time                   : 0.00
Lin. dep.  - tries                  : 1                 time                   : 0.00
Lin. dep.  - number                 : 0
Presolve terminated. Time: 0.00
Problem
  Name                   :
  Objective sense        : min
  Type                   : CONIC (conic optimization problem)
  Constraints            : 4950
  Cones                  : 0
  Scalar variables       : 0
  Matrix variables       : 1
  Integer variables      : 0

Optimizer  - threads                : 4
Optimizer  - solved problem         : the primal
Optimizer  - Constraints            : 4950
Optimizer  - Cones                  : 0
Optimizer  - Scalar variables       : 0                 conic                  : 0
Optimizer  - Semi-definite variables: 1                 scalarized             : 5151
Factor     - setup time             : 1.39              dense det. time        : 0.00
Factor     - ML order time          : 0.99              GP order time          : 0.00
Factor     - nonzeros before factor : 1.23e+07          after factor           : 1.23e+07
Factor     - dense dim.             : 0                 flops                  : 4.05e+10
ITE PFEAS    DFEAS    GFEAS    PRSTATUS   POBJ              DOBJ              MU       TIME
0   0.0e+00  1.0e+00  2.0e+00  0.00e+00   1.000000000e+00   0.000000000e+00   1.0e+00  1.39
1   0.0e+00  0.0e+00  0.0e+00  1.00e+00   0.000000000e+00   0.000000000e+00   0.0e+00  2.38
Optimizer terminated. Time: 2.39

cc @erling-d-andersen

MOSEK has no auto dualizer for SDPs. That means if your problem is really on LMI form you should formulate on dual form if you care about efficiency.
In other words you should study what is Mosek primal form and make sure the problem you input fits that.
Mosek may get more clever about this in the future.

For the dualization, we have a solver-independent solution in https://github.com/jump-dev/Dualization.jl

For now does not that solve the problem?
I mean if solve the dual problem then Mosek should work efficiently.

It does indeed solve the problem in this (particular) scenario! Thanks. More generally, I do wonder why Mosek does not generally recognize chordal SDP sparsity patterns? This seems like it would be huge for general SDPs!
(On the other hand, it would also be great if there was an MOI bridge for chordally sparse SDPs which automatically would convert such problems to the appropriate form. I think I'll make a script that does something similar, but it would probably need to have plenty of work to be added as an MOI bridge and recognized by JuMP correctly.)

We do not recognize chordal structure. There are no plans to add such a feature Mosek any time soon.

There is chordal sparsity reduction implemented in https://github.com/jump-dev/SumOfSquares.jl/, you should use
using DynamicPolynomials, SumOfSquares
@polyvar x[1:n]
@constraint(model, x' * Q * x in SOSCone(), sparsity = VariableSparsity())

Instead of
@constraint(model, Q in PSDCone())

Phenomenal! This would be absolutely amazing! I'll take a look! :)


[HOLD for payment 2023-08-14] [HOLD for payment 2023-08-07] [$1000] Invite Member - No way to remove RBR from avatar after inviting an invalid number into a workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Create a workspace and go to invite members page
Paste an invalid number like "+916541237890" inside the search field and select it
Click next > invite
Go back to LHN and observe there is a RBR on it
Click on avatar > follow the RBR and click on workspace > members

Expected Result:
There should be a way to remove the RBR from avatar and settings
Actual Result:
There is no way to remove RBR from settings after inviting an invalid member into a workspace
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.37-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/6df7a971-b2ea-4bd6-89fe-2e2d8270bde2
https://github.com/Expensify/App/assets/93399543/0c39d983-3e6e-4949-b4c8-25729f2e9885
Expensify/Expensify Issue URL:
Issue reported by: @Nathan-Mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688630661683609
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012f84973149e5c0ce
Upwork Job ID:<PHONE_NUMBER>916169216
Last Price Increase: 2023-07-18

might be related to - https://github.com/Expensify/App/issues/20961#issuecomment-1624300468

Just as an info, this issue was introduced on this week's latest release, I think #20961 was reported 20 days ago. This issue was not there then.

Ah okay, thank you @Nathan-Mulugeta! It does sound like it might be separate then but I'll wait to confirm with @PauloGasparSv. Thanks!

watching for an update https://github.com/Expensify/App/issues/20961#issuecomment-1627793915

Not related to https://github.com/Expensify/App/issues/20961#issuecomment-1629927291 - moving forward with treating this separately!
I can reproduce but I'm not sure how we want to remove the RBR - any suggestions @Nathan-Mulugeta

I'm going to be ooo until August 31st so going to unassign and assign a new teammate.
@JmillsExpensify At this time, we're receiving and reviewing proposals.

Reviewing proposals today

@tienifr's proposal looks good to me!

We need to optimistically add the member details (with login) to personalDetails when we add a member to the workspace.
In successData, we'll clear the above member details since it has the dummy ID, and the back-end already returns correct accountID in personalDetails for that member.

🎀👀🎀 C+ reviewed!

Sorry for the delay, agreed that @tienifr's proposal looks good 👍

Yep 😅 I did

@eVoloshchak Can you get us kicked off with the BZ checklist?

Back from ooo! Thanks for handling this @JmillsExpensify - I'm happy to take it off your plate!

@eVoloshchak If you wouldn't mind kicking off the BZ checklist above in the next week, thank you!

Payouts due:
Issue Reporter: $250 @Nathan-Mulugeta
Contributor: $1000 + $500 bonus (need confirmation this is true) @tienifr
Contributor+: $1000 + $500 bonus (need confirmation this is true) @eVoloshchak
Eligible for 50% #urgency bonus? Yes - @eVoloshchak @NikkiWines can you confirm?
Upwork job is here.
Internal job posting - https://www.upwork.com/ab/applicants/1678916595916169216/job-details

@Christinadobrzyn, this has introduced a regression (https://github.com/Expensify/App/pull/23947), so no urgency bonus, and the bounty should be reduced 50%

Regression Test Proposal

Create a workspace and go to invite members page
Paste an invalid number like "+916541237890" inside the search field and select it
Click next > invite
Verify that there's an error indicator (RBR) for the newly invited account
Verify that you can dismiss the error by pressing a close button

Do we agree 👍 or 👎

looks like the regression is resolved and the payment date for this should have been 8/16. I don't know why this didn't revert to a daily for payment but paying this now!
Payouts due after regression based on https://github.com/Expensify/App/issues/22359#issuecomment-1677417081
Issue Reporter: $250 @Nathan-Mulugeta
Contributor: $500
Contributor+: $500
Eligible for 50% #urgency bonus? No - because of regression
Upwork job is here.
Internal job posting - https://www.upwork.com/ab/applicants/1678916595916169216/job-details

It looks like the penalty is based on this comment - https://github.com/Expensify/App/issues/22359#issuecomment-1677417081
We announced the regression penalty on July 28th. The regression related to this issue was found on July 31st so I believe the penalty would apply here as this regression was after the announcement.


Timestamp event doesn't performance as timeSlice sets

Description
Briefly describe the issue.
In most cases, timestamp can work as expected, but sometimes, "timestamp" event doesn't performance as timeSlice sets
Code is here:
const videoJsPlayerOptions = {
        controls: false,
        fluid: false,
        plugins: {
                record: {
                        audio: true,
                        video: true,
                        debug: true,
                        timeSlice: 1000,
                        maxLength: videoLength
                }
        }
    }

player.on("timestamp", function () {
      const currentTime = Math.floor(player.record().getCurrentTime())
      setCurrentTime(formatTime(currentTime))
      console.log(`Current Time: ${formatTime(currentTime)}`)
})

In the console, the current time doesn't increment 1s by 1s, sometimes it will jump 2s.

Steps to reproduce
Explain in detail the exact steps necessary to reproduce the issue.
set up a video and timestamp event, console that current time .
Results
Expected
Please describe what you expected to see.
The currentTime should increment 1s by 1s
Actual
Please describe what actually happened.
Sometimes, the currentTime jump 2s and get normal.
Error output
If there are any errors at all, please include them here.
No error
Additional Information
Please include any additional information necessary here. Including the following:
versions
videojs
^7.15.4
what version of videojs does this occur with?
^4.5.0
browsers
Chrome: Version 99.0.4844.84 (Official Build) (arm64)
MacOS Safari: Version 15.2 (176<IP_ADDRESS>.6)
OSes
what platforms (operating systems and devices) are affected?
MacBook Pro (16-inch, 2021), MacOs: version 12.1

Same issue

Any update on this?


How to replace contrib.rnn.stack_bidirectional_dynamic_rnn in tf2.0

I use contrib.rnn.stack_bidirectional_dynamic_rnn in my code, but I upgrade my tf to 2.0 now, how to replace it?

So there are two ways to build bidirectional RNN in tf 2.0 with keras layers, and the existing stack_bidirectional_dynamic_rnn() is using the second approach. There isn't any right/wrong between those 2 approaches, the major difference is that whether the cell state will be feed to next layer as initial states.

Does not feed cell states to next layer as initial states, note that forward and backward cellls are just simpleRNN cells and you can replace them with LSTM or GRU cells.

import tensorflow as tf
import numpy as np
from tensorflow.keras import layers

batch = 32
timestep = 10
input_shape = 8

cell_size = 4
num_layers = 6
cells = [layers.SimpleRNNCell(cell_size) for _ in range(num_layers)]

model = tf.keras.Sequential()

model.add(tf.keras.Input(shape=(None, input_shape)))
model.add(layers.Bidirectional(
    layers.RNN(cells)
))

result = model.predict(np.ones(shape=(batch, timestep, input_shape), dtype=np.float32))
print(result)

Using the previous layers end state as the initial state for the next layer. Since now we need to probably pass the states between layers, we will need to use functional API, rather than just the Sequential model as the example above.

import tensorflow as tf
import numpy as np
from tensorflow.keras import layers

batch = 32
timestep = 10
input_shape = 8

cell_size = 4
num_layers = 6
# cells = [layers.SimpleRNNCell(cell_size) for _ in range(num_layers)]

inputs = tf.keras.Input(shape=(None, input_shape))
output = inputs
states = None
for _ in range(num_layers):
  result = layers.Bidirectional(
      layers.RNN(layers.SimpleRNNCell(cell_size),
                 return_state=True, return_sequences=True))(output, states)
  output, states = result[0], result[1:]
# If you only care about the output for the last time step, you can just slide it here.
output = output[:, -1, :]

model = tf.keras.Model(inputs, output)

result = model.predict(np.ones(shape=(batch, timestep, input_shape), dtype=np.float32))
print(result)

Hope this resolve your question.


[stable/external-dns] Digitalocean spelling mistake above providers setting - external dns

What this PR does / why we need it:
Simple spelling mistake that caused me to copy and paste the wrong value in the provider.
This could stop this mistake happening if people like me, copy and paste the digital ocean provider.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

@ltatakis
Could you sign DCO and bump the chart version to latest please? Thank you.

@zanhsieh @carrodher sorry for the delay, did the DCO and also  upped the version

/ok-to-test


Setup unit tests on CI

Setup unit tests on CI

Unit tests has been added via https://github.com/RedHatInsights/insights-operator-controller/blob/master/.travis.yml#L24


Investigate vue3 suspense for async dependencies of a component

https://vuejs.org/guide/built-ins/suspense.html
This surfaced because of an error I got for a component variable which was initialized as ref(null) and which is the binding variable for the items of a v-select component, i.e. it should be an iterable:
[Vue warn]: Unhandled error during execution of render function
  at <VSelect items=null item-title="name" label="Select a Node"  ... >

and further on:
Uncaught TypeError: items is not iterable

which lead me to this explanation: https://stackoverflow.com/a/65843026
This particular case can be solved easily by initializing the variable as ref([]), but the use of suspense can possibly be used in many cases where previously I have used, for example, v-if="dataset_ready" which will show a component only once custom logic has set the dataset_ready variable to true.

Closing until this becomes actually needed


Update Builder and ClusterBuilder definition

Move namespace to Builder code and remove from ClusterBuilder code

Codecov Report

Merging #299 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #299   +/-   ##
=======================================
  Coverage   67.26%   67.26%
=======================================
  Files          77       77
  Lines        3125     3125
=======================================
  Hits         2102     2102
  Misses        773      773
  Partials      250      250

Continue to review full report at Codecov.

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


How can we add full day task and move where task day wise

How can we add full day task and move where task day wise. right now if we create 24 hr task it looks like full day task however while moving it it can be dropped in between days. We want to restrict that. it should be droppable to entire day not partial in 2 dates.

Did you try the daily attribute ?

For me daily doesn't work. One day task is not filling cell.

Hello, that function would be useful :+1:

Another way would be to listen to the task change event and then adjust the task to the full day in case it was dropped in between two days. The documentation has more info about how to listen to events.


feat: make CodePipeline and CodeBuild annotations backwards-compatible

Issue
Closes #7
Reason for this change
Some people already have a catalog that utilizes the annotations of the now deprecated @aws/aws-codeservices-backend-plugin-for-backstage. Updating to this version would require updating the catalog-info.yaml file of every entity, which can be a big undertaking depending on the amount of entities they have.
Description of changes
I added support for the previous annotations for CodePipeline and CodeBuild, while not recommending to use them anymore by leaving them out of the MissingAnnotationEmptyState.
Description of how you validated changes
I tested these changes locally and extended the current unit tests where applicable.
Checklist

[x] My code adheres to the CONTRIBUTING GUIDE

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

I was hoping to get some time to get to this issue soon, so glad you were able to get this PR done.


Change LazyListState to be scroll-aware

Reduce the size of the preload window while actively scrolling
Once scrolling is completed, optimize the preload window so that, for example, if the user is scrolling down, we load more items below than above

This addresses issue #2002

[x] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

#2013 was reverted in #2022--turns out the TODO we left should've been tackled in the same PR.


remove TODO with merge of https://github.com/ziglang/zig/pull/7082

The standard library also had realpathAlloc which replaced another TODO.

still 2 more places I think (that didn't have the TODO comment)


how to use 3d obj in solufa?

How to use 3d obj model in solufa? I want to use 3d obj rather then boxes or lines so please provide a suitable way for using 3d obj in solufa.

I'm sorry. Reply was slow because not accustomed to GitHub.
Please tell me the extension of the model data you want to use.
For example, ".obj", ".stl", ".dae"....


Can't do :w in vim mode. : does not work

Check for existing issues

[X] Completed

Describe the feature
In vim mode if I try save file with :w it would actually do a jump to a word. Basically : seems fully broken with recent update.

cc @ConradIrwin

This just shipped in Zed 0.106 preview if you want to try it out and leave feedback (here or through :feedback, please do!).


Getting mixed up response when sending TWO AT commands on the same device.

I'm trying to send multiple AT commands.
From time to time, the response that should have belonged to the first function gets outputted to the second function.
Verified by removing the console.log in the on data event listener in the first function, and removing the send function in the second one.
The output(from the AT command in the first function) gets printed on the second one.
'use strict';

const serial = require('serialport-js');

var obj = {
	first: function(port) {
		port.on('data', function(data) {
			console.log('first AT+QNWINFO AT+QNWINFO', data);
		});

		port.send('AT+QNWINFO\r');
	},
	second: function(port) {
		port.send('AT+QTEMPDBG=0\r');
		port.on('data', function(data) {
			console.log('second', data);
		});
	}
}

setInterval(function() {
	serial.open('/dev/ttyUSB2', obj.first, 'OK')
}, 1000);

setInterval(function() {
	serial.open('/dev/ttyUSB2', obj.second, 'OK')
}, 1000);

Thanks

you are sending them b oth at the same time. Your device probably needs more time to handle the requests.


Grumpy' stdlib have preference over CPython' stdlib

This is needed when a CPython stdlib module tries to import another. E.g. zipfile imports os:
Should be provided the Grumpy os module but there is an os.py on the same folder of stdlib zipfile.py.

👨🎤 "Nobody complains I will be merging..."


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-cognitiveservices-account
Module Details
I have a sample starter implementation in the style of AVM here;
https://github.com/kewalaka/terraform-azurerm-avm-res-cognitiveservices-account/
Do you want to be the owner of this module?
No
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Hi @kewalaka thanks for opening this pr, our team intends to promote OpenAI TF module and we'd like to use an AVM module, so I'd like to create a cognitive account module, and migrate code in terraform-azurerm-openai into this new module. Would you mind let me create this new module, so we can avoid duplicated work? Thanks a lot!
And I believe the module's name should be terraform-azurerm-avm-res-cognitive-account, right?

@lonegunmanb appreciate your response to @kewalaka comment above

@kewalaka I've composed one and I think it's ready for a review: https://github.com/lonegunmanb/terraform-azurerm-avm-res-cognitiveservices-cognitive-account

Would we keep the yor tags? I like them, be a good addition to the spec.

Yor tags will be the foundation of AVM, yes we will support them very soon.

Closing this module proposal as duplicate and in favor of this one raised by @lonegunmanb


custom information for all file types

.nam is the neural amp modeler model file type
open audio should have a database of file types containing mininal info about them for https://github.com/open-audio-stack/open-audio-stack-registry/issues/57
(the below is a studiorack issue)
ir should then be able to list all plugins capable of using that file type like the below does for plugins found within projects
https://github.com/studiorack/studiorack-site/issues/44

this database may also be necessary for the sake of how metadata should be listed.
tonehunt.org shows what .nam files need to be presented for example
a plugin dev should honestly PR any metadata structures they need for their stuff into openaudio, most plugins just use presets which are general enough to use our generic preset metadata but some, like NAM, are not 'presets' but rather extra files the plugin uses to work. another example of something like that would be if this were implemented in terrain https://github.com/aaronaanderson/Terrain/issues/5
some plugins essentially use 'presets' that are not contained within the plugin but link to other files.
ive tried to imagine how this would work with tagging, metadata, and downloading through out these issues

another example, theoretically in the future, would be rvc files for plugins that use voice conversion tech

I am adding details for every file format Open Audio Stack references in code:

https://github.com/open-audio-stack/open-audio-stack-core/blob/main/src/types/FileFormat.ts
https://github.com/open-audio-stack/open-audio-stack-core/blob/main/src/types/PluginFormat.ts
https://github.com/open-audio-stack/open-audio-stack-core/blob/main/src/types/PresetFormat.ts
https://github.com/open-audio-stack/open-audio-stack-core/blob/main/src/types/ProjectFormat.ts

They are then added to the config:
https://github.com/open-audio-stack/open-audio-stack-core/blob/main/src/Config.ts#L37
And generated in the Registry static files e.g.

https://open-audio-stack.github.io/open-audio-stack-registry/config/file-formats/
https://open-audio-stack.github.io/open-audio-stack-registry/config/plugin-formats/
https://open-audio-stack.github.io/open-audio-stack-registry/config/preset-formats/
https://open-audio-stack.github.io/open-audio-stack-registry/config/project-formats/

So I consider this feature already built, and it will be extended over time.

So I consider this feature already built, and it will be extended over time.

then add to the readme how to upload a new file format. youve added to the readme how to add plugins, projects, and presets so just add that too

description	"macOS and iOS software package installer."
value	"pkg"
name	"Apple package"

.nam files need to be presented for example (e.g light, feather or nano)

the ability to add more metadata points is crucial
also, im not sure i like the name "file formats". these should be labelled as storage formats and things like .sfz, .nam, .rvc, etc. should be "file formats". anything which falls into the description of a 'preset' that is used by a plugin but not contained within the plugin but use other files. i guess you could argue most plugins' presets fall into that description but im thinking more in the lines of plugin agnostic files. for example, an impulse response can be used by any plugin that supports it. it isnt designed for a specific plugin.
is this making sense? theyre like presets but plugin agnostic and classifying them as presets isnt correct at all, theyre "file formats" that are standardised across plugins and they each require their own metadata points

So I consider this feature already built, and it will be extended over time.

then add to the readme how to upload a new file format. youve added to the readme how to add plugins, projects, and presets so just add that too

Only file formats used in the specification will be supported for now.

description	"macOS and iOS software package installer."
value	"pkg"
name	"Apple package"

.nam files need to be presented for example (e.g light, feather or nano)

the ability to add more metadata points is crucial
also, im not sure i like the name "file formats". these should be labelled as storage formats and things like .sfz, .nam, .rvc, etc. should be "file formats". anything which falls into the description of a 'preset' that is used by a plugin but not contained within the plugin but use other files. i guess you could argue most plugins' presets fall into that description but im thinking more in the lines of plugin agnostic files. for example, an impulse response can be used by any plugin that supports it. it isnt designed for a specific plugin.
is this making sense? theyre like presets but plugin agnostic and classifying them as presets isnt correct at all, theyre "file formats" that are standardised across plugins and they each require their own metadata points

FileFormats are the formats supported in the Registry package files specification.
They are archive and installer formats which are used to bundle and distribute other files.
I don't want individual files to be supported in package files, otherwise every Package Manager will have to handle every file format. That's usually not how package managers work. They require packages to be distributed using a fixed list of archive/installer formats.

let me rephrase, i know youre storing all the files within 'file formats' but when youre uploading the files within those file formats to the registry, they need custom metadata around them

nam files need to be presented for example (e.g light, feather or nano)

According to the docs:
https://neural-amp-modeler.readthedocs.io/en/stable/model-file.html
.nam are not presets but trained neural network model files. At the moment I don't plan to support plugin-specific file formats.

At the moment I don't plan to support plugin-specific file formats.

okay but the problem is plugins need them to function. maybe re-open and make this a long term low priority issue

When a manager installs a plugin, it can copy all files to the default plugin directory:

Platform
Path

Linux platform
$HOME/usr/local/lib/$format

Mac platform
$HOME/Library/Audio/Plug-ins/$format

Windows platform
C:\Program Files\Common Files$formatC:\Program Files (x86)\Common Files$format

When the manager installs a preset, it can copy all files to the default preset directory:

Platform
Path

Linux platform
$HOME/.vst3/presets

Mac platform
$HOME/Library/Audio/Presets

Windows platform
$HOME/Documents/VST3 Presets

If there needs to be custom installation paths, either the plugin can distributor an installer executable file containing the logic. OR we can support some mapping from file extensions to paths which is covered in another ticket.

okay but if youre downloading a project and open audio cant recognise what file has been used in a plugin and it has no metadata or info to link in back to in our registry, that would be a disaster.
also these arent "presets", theyre not really "plugin-specific file formats" either, though some are. some are howeve plugin agnostic and classifying them as presets isnt correct at all, theyre "file types" that are standardised across plugins and they each require their own metadata points. .nam, my example, is used in so many plugins (mod desktop, neural amp modeler, ratatouille, aida-x, etc.). you wouldnt say that impulse responses are presets would you https://github.com/open-audio-stack/open-audio-stack-registry/issues/40
i think that down the line, plugin devs should be able to upload metadata scheme for plugin types and open audio can decide if it's worth it, which is honestly a documentation concern almost


Can't build on Intel MBP

Whenever I try to use 'make' it gives the error :
"make[1]: *** No rule to make target `osx-arm64'.  Stop."
Any ideas ?
NB : I already added every submodule I could find.

In Makefile, line 38. Change
BGFX_DEPS_TARGET=osx-arm64
to
BGFX_DEPS_TARGET=osx-x64

You need to do a few adjustments both to bimg and bx because their Makefile is broken for osx-x64 (points to incorrect build directory).
Change the following lines in lib/bimg/makefile and lib/bx/makefile:
diff --git a/makefile b/makefile
index c2e23f8..0410858 100644
--- a/makefile
+++ b/makefile
@@ -156,9 +156,9 @@ vs2017: vs2017-debug32 vs2017-release32 vs2017-debug64 vs2017-release64 ## Build
 .build/projects/gmake-osx-x64:
 	$(GENIE) --gcc=osx-x64 gmake
 osx-x64-debug: .build/projects/gmake-osx-x64
-	make -C .build/projects/gmake-osx config=debug
+	make -C .build/projects/gmake-osx-x64 config=debug
 osx-x64-release: .build/projects/gmake-osx-x64
-	make -C .build/projects/gmake-osx config=release
+	make -C .build/projects/gmake-osx-x64 config=release
 osx-x64: osx-x64-debug osx-x64-release

 .build/projects/gmake-ios-arm:

Then update the Makefile in the project root:
diff --git a/Makefile b/Makefile
index dce485d..8eafe7f 100644
--- a/Makefile
+++ b/Makefile
@@ -37,6 +44,11 @@ ifeq ($(UNAME_S), Darwin)
 	# TODO: select based on ($ arch)
 	BGFX_DEPS_TARGET=osx-arm64
 	BGFX_TARGET=osx-arm
+
+	ifeq ($(UNAME_M),x86_64)
+		BGFX_DEPS_TARGET=osx-x64
+		BGFX_TARGET=osx-x64-release
+	endif
 endif

 ifeq ($(UNAME_S), Linux)

Then run make run.

Hint: You can also compile the individual libraries from their project folder with make -j8 instead. Change the Makefile with the following, before running make -j8 run:
diff --git a/Makefile b/Makefile
index dce485d..35de073 100644
--- a/Makefile
+++ b/Makefile
@@ -74,9 +86,9 @@ all: dirs libs shaders build

libs:
	export LD_PATH="$(FRAMEWORKS)"
-	cd lib/bx && make $(BGFX_DEPS_TARGET)
-	cd lib/bimg && make $(BGFX_DEPS_TARGET)
-	cd lib/bgfx && make $(BGFX_TARGET)
+	cd lib/bx && make -j8 $(BGFX_DEPS_TARGET)
+	cd lib/bimg && make -j8 $(BGFX_DEPS_TARGET)
+	cd lib/bgfx && make -j8 $(BGFX_TARGET)
	cd lib/glfw && cmake . && make
	cd lib/noise && make
	export LD_PATH=""

Building for earlier macOS (i.e. Mojave):
Xcode 11 does not come with a version of LLVM that has C++20 support, nor the libraries necessary. You will need to install at least LLVM 13.0.0 to get appropriate support.
This can be done with Homebrew:
brew install llvm

Note: Homebrew does not provide pre-compiled binaries for Mojave. When installing it will compile LLVM from scratch. This will take a long time, so grab a cup of coffee and sit back. Or take a nap. I did the latter.

Once installed, restart your terminal and confirm the versions with the following command:
$ `brew --prefix llvm`/bin/clang++ --version
Homebrew clang version 13.0.0
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin

Note the Homebrew clang and version number.
Now update the Makefile in the project root to use the appropriate compiler and frameworks:
diff --git a/Makefile b/Makefile
index dce485d..35de073 100644
--- a/Makefile
+++ b/Makefile
@@ -2,8 +2,14 @@
 print-%  : ; @echo $* = $($*)

 UNAME_S = $(shell uname -s)
 UNAME_M = $(shell uname -m)

+LLVM_PREFIX=$(shell brew --prefix llvm)
+LLVM_BIN=$(LLVM_PREFIX)/bin
+LLVM_LIB=$(LLVM_PREFIX)/lib
+
-CC = clang++
+CC = $(LLVM_BIN)/clang++

 INCFLAGS  = -iquotesrc
 INCFLAGS += -Ilib/glm
@@ -14,6 +20,7 @@ INCFLAGS += -Ilib/glfw/include
 INCFLAGS += -Ilib/bgfx/3rdparty/fcpp
 INCFLAGS += -Ilib/tomlplusplus
 INCFLAGS += -Ilib/noise
+INCFLAGS += -L $(LLVM_LIB)

 CCFLAGS  = -std=c++20 -O2 -g -Wall -Wextra -Wpedantic -Wno-c99-extensions
 CCFLAGS += -Wno-unused-parameter

Didn't work for me (I'm on M1 Pro MBP with macOS Big Sur), still gives me
export LD_PATH="-framework QuartzCore -framework Cocoa -framework Carbon -framework Metal -framework CoreFoundation -framework IOKit"
cd lib/bx && make osx-arm64
make[1]: *** No rule to make target `osx-arm64'.  Stop.
make: *** [libs] Error 2

after $ make

Hi I also have this same issue but I am not sure if I have installed all of the submodules yet plus I don't know which ones to install


Better CI/CD or Full CI/CD

We need to construct a more complete CI/CD flow during PRs. In particular when it comes to integration, both with authenticator.js and attestation.id.

@abcfy2 do you know the hardhat testing flow?
This is actually not trivial - we might do a small project for getting this right, proper CI/CD setup between attestation.id, authenticator.js, attestation.jar and the smart contracts take a bit of effort to figure out.

In relation to this it should also be mentioned that there are some issues with the hardhat tests in attestation.jar, see issue #254
As part of this CI/CD task these should also be reenable.

there are some issues with the hardhat tests

yes, that's why I suggest we get our dependencies graph first, ;).

It looks really good! Thanks @foxgem!
I think the only thing we might also want to add is the smart contract hard hat testing when attestation.jar has been updated. See issue #254.

currently attestation JS code located under https://github.com/TokenScript/attestation/tree/main/src/main/javascript/crypto
to test it I do next steps:

in the root folder  gradle test --rerun-tasks to regenerate test output files
in the main/src/main/javascript/crypto folder I run npm run testjest , it read output files from gradle test and tests agains them.

So we can run grable test and npm test one by one or find another solution and generate JAVA output before each NPM test
another note - TN includes attestation npm module and use it to decode magicLink, to test attestation, make proof etc., so ideally TN should be updated when attestation npm changed

Phase#1
Goals:

attestation github clean up
attestation <> attestation.id CI integration

Action Plan

Attestation main branch

java component (java-main-p1)

build - test - grype

js component (js-main-p1)

build - test

contract component (contract-main-p1)

build - test

Attestation stage branch

java component

java-p1 - prerelease - attestation.id/backend-main-p1
js-p1 - prerelease - attestation.id/frontend-main-p1

attestation.id main branch

backend (backend-main-p1)

build - test

frontend (frontend-main-p1)

build - test

attestation main enhancement

java-main-p1: trigger js-main-p1 and contract-main-p1
js-main-p1: security scanning
contract-main-p1: security scanning

after discussing with @jot2re , the output of grype will be like:
success
% grype attestation-0.3.18-all.jar
 ✔ Vulnerability DB        [updated]
New version of grype is available: 0.40.0
 ✔ Indexed attestation-0.3.18-all.jar
 ✔ Cataloged packages      [23 packages]
 ✔ Scanned image           [0 vulnerabilities]

failure
% grype build/libs/backend-0.1-all.jar
 ✔ Vulnerability DB        [no update available]
New version of grype is available: 0.40.0
 ✔ Indexed build/libs/backend-0.1-all.jar
 ✔ Cataloged packages      [83 packages]
 ✔ Scanned image           [25 vulnerabilities]

NAME                         INSTALLED     FIXED-IN      TYPE          VULNERABILITY        SEVERITY
netty-codec-http             4.1.73.Final  4.1.77.Final  java-archive  GHSA-269q-hmxg-m83q  Medium
netty-reactive-streams       2.0.5                       java-archive  CVE-2019-20445       Critical
netty-reactive-streams       2.0.5                       java-archive  CVE-2021-21290       Medium
netty-reactive-streams       2.0.5                       java-archive  CVE-2021-37136       High
netty-reactive-streams-http  2.0.5                       java-archive  CVE-2015-2156        High

so, the grype task is to find if there is "0 vulnerabilities" in the output. cc @abcfy2

I've committed java-p1 CI, which will run gradle build & test & grype check after push / pull_request to main branch.
Sample: https://github.com/TokenScript/attestation/actions/runs/2532698892

js-p1 CI added. When push/pull_request code changes to main branch in src/main/javascript/crypto/ directory will trigger this CI.
Sample: https://github.com/TokenScript/attestation/actions/runs/2536158552

contract-p1 CI addes.

stage branch workflow finished.
Result sample:
java CI: https://github.com/TokenScript/attestation/actions/runs/2596014131
js CI: https://github.com/TokenScript/attestation/actions/runs/2595982268

Phase#2
Goals: including TN project
Length: 1~2 weeks
Action Plan

TN main branch (tn-p1)

build - test

if the stage branch changed in tokenscript/attestation or attestation.id

pre-release-of-dependencies - call tn p1

Phase#2 done.
Sample: https://github.com/TokenScript/attestation/actions/runs/2648616646

@abcfy2 as we discussed, please enhance the CI with E2E testing.


Trying to use on Mac (.NET MAUI) throws exception

Tried to add package through nuget on VS for Mac Preview (most up-to date version), and get	{System.DllNotFoundException: uiohook    at SharpHook.Native.UioHook.SetDispatchProc(DispatchProc dispatchProc, IntPtr userData)    at SharpHook.GlobalHookBase.<>c__DisplayClass16_0.b__0()}	System.DllNotFoundException
when running
var hook = new TaskPoolGlobalHook();   hook.KeyPressed += OnKeyPressed;   await hook.RunAsync();

Hi! Thanks for using SharpHook! Yes, there's currently a bug on macOS - the libuiohook.dylib file is not copied to the build directory on macOS for some reason. I haven't had the chance to investigate it yet as I don't have a Mac. You can find a workaround for this issue in this discussion thread.
Also, I'm going to close this issue as a duplicate of issue #26. If you want to discuss it further, let's move the discussion to that issue. If you believe that this is a separate issue, we can always reopen this issue instead.

Thank you so much!
Leo

From: Tolik Pylypchuk @.>
Sent: Friday, January 20, 2023 2:16 AM
To: TolikPylypchuk/SharpHook @.>
Cc: Simanonok, Leo P @.>; Author @.>
Subject: Re: [TolikPylypchuk/SharpHook] Trying to use on Mac (.NET MAUI) throws exception (Issue #31)
External Sender. Be aware of links, attachments and requests.
Hi! Thanks for using SharpHook! Yes, there's currently a bug on macOS - the libuiohook.dylib file is not copied to the build directory on macOS for some reason. I haven't had the chance to investigate it yet as I don't have a Mac. You can find a workaround for this issue in this discussion threadhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTolikPylypchuk%2FSharpHook%2Fdiscussions%2F22%23discussioncomment-4184955&data=05|01|lsimanonok%40tulane.edu|1d59d07b6fd4475e003f08dafab64572|9de9818325d94b139fc34de5489c1f3b|0|0|638097958018428858|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=48cnYTE1JuE4s51GJ7py0LZ%2BifgG%2BGRsRZJN0G%2FbHEE%3D&reserved=0.
Also, I'm going to close this issue as a duplicate of issue #26https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTolikPylypchuk%2FSharpHook%2Fissues%2F26&data=05|01|lsimanonok%40tulane.edu|1d59d07b6fd4475e003f08dafab64572|9de9818325d94b139fc34de5489c1f3b|0|0|638097958018428858|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2F3Je01l06UC4FyfR2CqaQafK6CPgopI1ox4WAvnLsq8%3D&reserved=0. If you want to discuss it further, let's move the discussion to that issue. If you believe that this is a separate issue, we can always reopen this issue instead.
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTolikPylypchuk%2FSharpHook%2Fissues%2F31%23issuecomment-1398003898&data=05|01|lsimanonok%40tulane.edu|1d59d07b6fd4475e003f08dafab64572|9de9818325d94b139fc34de5489c1f3b|0|0|638097958018428858|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=OtV%2BCXoc2lJwLELnfrCLNRbRa94OwnAhAILliljXoxE%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANWCANACV3AOJOCANS3OFITWTI3VJANCNFSM6AAAAAAUAZBF7Q&data=05|01|lsimanonok%40tulane.edu|1d59d07b6fd4475e003f08dafab64572|9de9818325d94b139fc34de5489c1f3b|0|0|638097958018428858|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=799UCTA4qHwXUnkO6wfXUSOePJzbeh%2BIDjQCTQcKFto%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

Hi @leosimanonok! Mac Catalyst support has been added in version 5.0.0 which I've just released, so this issue can be closed as completed now :)


Incorrect formatting for elvis operator with comments over options

Expected Behavior
This snippet represents good formatting according to IntelliJ IDEA and should survive after ktlint
    fun get(): String =
        // first way to get value
        first() ?:
        // otherwise use second way
        second()

Observed Behavior
This formatting is applied by ktlint
    fun get(): String =
        // first way to get value
        first()
            ?: // otherwise use second way
            second()

This has 2 problems

Second option has indentation despite it has the same meaning as first option
Elvis operator is merged into next comment

Your Environment

Version of ktlint used: 0.50.0
Kotlin version = 1.9.0
Gradle version = 8.1.1

This snippet represents good formatting according to IntelliJ IDEA and should survive after ktlint

This assumption does not hold true for ktlint. Ktlint is more strict than IntelliJ IDEA and disapproves the usage of the elvis operator as the last code element on a line.
The correct assumption is that code produced by Ktlint for code styles intellij_idea and android_studio should not conflict with the IntelliJ IDEA default formatter. Note that this assumption is also dropped for the code style ktlint_official as the the IntelliJ IDEA default code style has formatting errors which after years are still not fixed.


Watch config changes for log level setting

Summary
What change needs making?
Now we are reloading the log level config ad hoc, we should a systematic way that watch the config changes and only reload the config if changes happen. The same goes for reload auth and other configs.
When would you use this?
Reflect config changes in a systematic way.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Is this a duplicate of this bug? I've added a comment on all of the  background information there.

Is this a duplicate of this bug? I've added a comment on all of the background information there.

yaa, it's looks like duplicate of #189 , so I'll fix this issue then validate #189 if that was still happening.

Hey @chandankumar4 - are you already working on this? Or if not, maybe I can take it?
I submitted a PR which was merged which calls this logger.RefreshBaseLoggerLevel() from syncer.RunOnce() and from the gitsync_controller.go Reconcile() function, which basically updates the central logger if the log level changes. But this is happening from multiple goroutines and theoretically doesn't have to.
We're still not updating the LogrLogger log level passed to the underlying cache in gitops-engine. That is constructed here and never gets updated. This is the one place where the logging is still not changing if you look at the log lines.
For both of these...I think you may have mentioned this @xdevxy - but I was thinking of adding a callback feature where the OnConfigChange() function could invoke the callbacks.

Sure, Thanks!! you can take it.
I have worked on similar issue here https://github.com/numaproj-labs/numaplane/issues/189#issuecomment-2095727035 and it was closed as it was not our code issue.

Okay, thanks!On May 7, 2024, at 4:07 AM, Chandan Kumar @.***> wrote:
Sure, Thanks!! you can take it.
I have worked on similar issue here #189 (comment) and it was closed as it was not our code issue.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>


Add Retry Logic To Zuul Using Spring Retry

This PR adds retry logic back to Zuul when using the Apache HTTP Client or the Ok HTTP Client.  This is the last piece to fixing #1295.

Codecov Report

Merging #1680 into 1.2.x will increase coverage by 0.44%.

@@            Coverage Diff            @@
##           1.2.x    #1680      +/-   ##
=========================================
+ Coverage   74.4%   74.84%   +0.44%
=========================================
  Files        190      191       +1
  Lines       5883     5935      +52
  Branches     735      742       +7
=========================================
+ Hits        4377     4442      +65
+ Misses      1191     1178      -13
  Partials     315      315

Impacted Files
Coverage Δ

...loud/netflix/ribbon/RibbonClientConfiguration.java
100% <ø> (ø)
:white_check_mark:

...ud/netflix/ribbon/support/ContextAwareRequest.java
100% <100%> (+45.45%)
:white_check_mark:

...x/ribbon/apache/RibbonLoadBalancingHttpClient.java
79.06% <72.22%> (+9.37%)
:white_check_mark:

...tflix/ribbon/okhttp/OkHttpLoadBalancingClient.java
71.42% <73.68%> (+5.8%)
:white_check_mark:

...x/ribbon/support/RetryableLoadBalancingClient.java
91.66% <91.66%> (ø)

...oud/netflix/ribbon/okhttp/OkHttpRibbonRequest.java
89.13% <ø> (+2.17%)
:white_check_mark:

...cloud/netflix/ribbon/RibbonLoadBalancerClient.java
76.31% <ø> (+2.63%)
:white_check_mark:

...netflix/ribbon/apache/RibbonApacheHttpRequest.java
96.42% <ø> (+3.57%)
:white_check_mark:

...x/ribbon/RibbonLoadBalancedRetryPolicyFactory.java
95.65% <ø> (+4.34%)
:white_check_mark:

... and 3 more

Continue to review full report at Codecov.

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


[ Milestone 6 ] Unit Testings

We set up the react testing library.
We created unit testing for operate.js and calculate.js.
We used jest snapshots to test the components.
We used the react testing library.
Checked all tests and They passed.

@Mihndim2020 thanks for the review. :smile:


Downloads and store operations should not be performed as root

Issue description
I noticed on my new multi-user Nix install on macOS that fetches and store operations are performed as the root user. Builds are done by a nixbld user, as expected.
On macOS, at least, the store is g+w and the group is nixbld, so store operations should be done as a nixbld user for reasons of least privilege -- ditto for downloads.
On irc, @grahamc confirmed that this behavior is also manifest on NixOS. Presumably this behavior is also unwanted there.
Steps to reproduce
Use nix-env to build a package that hits the cache. While this is downloading and unpacking, use ps auxww | grep nix and observe that the downloads and store operations are performed by root.

Whoops, I guess this needs to be reported on nix.


Add support for Muut commenting

Muut is commenting system similar to Disqus. Muut's features do distinguish it from Disqus, and Muut's business model does not depend on advertisements or ad-related data harvesting.

Thanks!


Add iterator of time series entries to MetricTimeSeries

Currently, a whole time series is backed by lists in memory. I don't know if there are plans to switcht to an iterator based access scheme to the underlying data store.
Either way, it would be convinient to have iterator based interfaces in the MetricTimeSeries class. I suggest:
Get all time series entries
Iterator<MetricTimeSeries.TimeSeriesEntry> getTimeSeriesEntries();`
Get sub timeseries by window definition
For some transformations is is required to access the time series data in a time-windowed fashion (movingaverage, resampling). It would be convinient to incoporate this feature directly into the time series class instead of programming it redundantly in the transformation classes..
Iterator<Window<MetricTimeSeries>> getWindowedTimeSeries(Unit unit, long windowSize, long slide );`
with Window(Start,End)

I am back at work on Monday and will answer this in detail. Thx.


narsil: 1.3.0-350-ga51756908 -> 1.4.0

update narsil to latest upstream release
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360714

x86_64-linux

:white_check_mark: 1 package built:

narsil

@Nanotwerp can you take a look at this one when you get a chance? Not urgent at all, but I can't seem to request you for review so i'm tagging you here, hope you won't mind.


Overhaul Solarized theme

Make gutter more similar to official Solarized style

Remove border
Use highlighted line color

Custom fat cursor style

Before
Light

Dark

After
Light

Dark:

Looks good. Merged as 320b301


Adding the slim apss capability on FHIR Core.

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #1167
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

@dubdabasoduba This should be addressed in this PR #1217

Closing this because it's no longer needed. We implemented flavours instead.


Ubuntu 24.04 LTS should be included as tested version

Currently the documentation has supported OS versions in the Requirements table.

Ubuntu (LTS releases) | 18.04+, 20.04+, 22.04+ | 20.04+, 22.04+
-- | -- | --

It should include Ubuntu 24.04 LTS as well now that the OS version image became Generally Available.
https://azure.microsoft.com/en-us/updates/generally-available-ubuntu-2404-lts-for-azure-virtual-machines/
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 00f29580-ea89-9c2d-d973-9b839c958f03
Version Independent ID: 2986809f-2c86-a7f0-c3c4-6e734cf67c68
Content: Azure Linux VM Agent overview - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/agent-linux.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @GabstaMSFT
Microsoft Alias: gabsta

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

@thiruma0203, the update has been submitted, it should be live in the next 24 hours on the site.

@thiruma0203
Thank you for bringing this to our attention! @GabstaMSFT initiated a pull request (PR) to address this issue. Once its reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


[HOLD for payment 2023-03-16] Web - Login screen - Language drop down options are too much to the left and cut by rounded corners

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com/
Click Language drop down to expand options

Expected Result:
Language options should be well displayed
Repro in 24 inch monitor, not repro on 15 inch laptop
Actual Result:
Language drop down options are too much shifted to the left and cut by rounded corners
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/93399543/222856536-8f084722-9640-4c4f-8519-b7422dffcf03.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ad6951ff75c45479
Upwork Job ID:<PHONE_NUMBER>910655488
Last Price Increase: 2023-03-06

Triggered auto assignment to @tjferriss (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@grgia Am I supposed to review the linked PRs? If so please assign me there. Thanks!

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.80-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/15675

If no regressions arise, payment will be issued on 2023-03-16. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@s77rt / @grgia] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@s77rt / @grgia] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@s77rt / @grgia] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@tjferriss] Determine if we should create a regression test for the bug.
[ ] [@s77rt] If we decide to create a regression test for the bug, please propose the regression test steps to the appropriate location to ensure the same bug will not reach production again.
[ ] [@tjferriss] Review the proposed regression test steps and location.
[ ] [@tjferriss] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Looks like something related to react-navigation may have been mentioned in this issue discussion.
As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.
Feel free to drop a note in #expensify-open-source with any questions.

The PR that introduced the bug has been identified:

being cut by rounded corners: https://github.com/Expensify/App/pull/4134
being too much to the left: https://github.com/Expensify/App/pull/12447

The offending PR has been commented on: I'm not sure if we can blame any of those PR, the first seems intentional and the second did the right thing and the bug could not have been caught since it's only reproducible on Windows. cc @grgia
A discussion in #expensify-bugs has been started: cc @grgia Can you work on this as I'm not sure if it's worth it

@tjferriss Please tag me if a regression test is required.

@s77rt, In general, it's always best to assume test steps are needed.  As there are PRs that introduced a bug, it sounds like we'll want to ensure this doesn't happen again.  Please propose the steps, you don't need to recommend where in TestRail the test case should be included or updated though (per a post earlier today in #contributor-plus)
Also, can you please apply to the job in Upworks for payment? https://github.com/Expensify/App/issues/15653

Regression Test Proposal

Open App (without logging in)
Scroll down to language picker and open it
Verify that the options are displayed correctly and not being cut by rounded corners

@tjferriss Sure, no problem.  regression steps ^
I have applied on Upwrok as well :+1:

I just hired @s77rt and created the regression test issue. Once we hit 3/16 I'll process the payment.

I think payment is handled in https://github.com/Expensify/App/issues/15676 since it's same PR

@tjferriss actually hired @s77rt for the PR that fixed the bug in this issue, and the one I was assigned to above. So I held off on hiring them in mine. We chatted 1:1 and TJ was going to pay them here, but I don't think payment has been issued yet.
Re-opening for now, so we can pay $s77rt for their PR review!

My mistake, payment has now been made to @s77rt


docs: Update EAS installation instructions

Thank you for having great setup instructions! I noticed that this part was slightly out of date and no longer required so I updated it for future readers.

Interesting, if the default image now contains it, but the version numbers are going to out of date in the future (r21 will become r22+, ubuntu 20 will go to 22 etc), perhaps there is a more future proof + prescriptive way to word it?
something like:

if you are using EAS default image you are set (do we need to specify EAS greater than or equal to some version or date? I'm not sure how EAS works, if it is all in cloud and everyone is updated, or if there are versions)
if you are not using the EAS image you must specify one that includes JDK11. You may find them (link to Expo docs...)

Then we don't have to worry about versions

Makes sense! I will rework this to make it more future proof.


Prevent modification of /_users/_security object

Expected Behavior
Modifying the _security object inside of _users is unsupported, and can lead to some unusual behaviour - see #1556.
Current Behavior
We allow people to shoot themselves in the foot by modifying _users/_security.
Possible Solution
Always return a 403 on write attempts for _users/_security. @rnewson do you have any comment on this?
Steps to Reproduce (for bugs)

dev/run -n 1 --with-admin-party-please
`curl -X PUT http://localhost:15984/_users/_security -d '{"foo": "bar"}'

Context
People are trying to change the rules for who can read/write documents in _users and it goes very badly.
Your Environment

Version used: 2.2.0

It's a difficult thing to remove at this late stage, though I agree with the proposal.
Should we fold this into the broader push to hide these databases behind an API that enforces only the semantics we wish?

@rnewson If a naive block is a problem for 2.x, we can just say this is backwards-incompatible and fold it into #1504 if you want, sure. I just thought maybe a 2.3 that blocked _users/_security writes wouldn't be too hard to implement, and shouldn't affect TOO many people...

Alternatively, like we've done with default db security and making _all_dbs an opt-in config value could help folks until we have a proper fix.

yes, I can see that. [couchdb] users_db_security_editable=false|true or something, defaulting to false in the new default.ini

If we're OK with that alternative for 2.x, I'll re-open this.


fix: replace useEffect with useLayoutEffect for React 17

useEffect cleanup runs since React 17 asynchronously thats why it needs to be changed
We deployed this change to a web application with quite a lot of users and could verify that the Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'. errors were gone.
Fixes #259
cc @Andarist

@Andarist like that?

Thanks!


terminal garbled

VSCode Version: Code 1.17.0 (be377c0faf7574a59f84940f593a6849f12e4de7, 2017-10-04T23:44:50.318Z)

OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

Bookmarks
ale
0.16.0

bracket-pair-colorizer
Coe
0.10.9

vscode-markdownlint
Dav
0.10.1

vscode-instant-markdown
dba
1.3.0

githistory
don
0.2.3

python
don
0.7.0

vscode-great-icons
emm
2.1.16

php-debug
fel
1.11.1

code-python-isort
fre
0.0.3

easy-icons
jam
0.3.1

format-php
Kas
1.1.2

vscode-JS-CSS-HTML-formatter
lon
0.2.3

start-git-bash
McC
1.2.1

vscode-filesize
mkx
1.0.0

vscode-docker
Pet
0.0.18

vscode-icons
rob
7.14.0

code-settings-sync
Sha
2.8.3

guides
spy
0.8.4

python
tht
0.2.3

vim
vsc
0.10.1

bootstrap-3-snippets
wcw
0.1.0

(11 theme extensions excluded)

Steps to Reproduce:

Reproduces without extensions: Yes/No

Somewhat similar issues for me too.

I did spot a random log message in the terminal on the first run of 1.17.0 which was along the lines of something doesn't match, be prepared for trouble, but I haven't been able to have it report again.
VS Code 1.17.0 on Fedora 25.

Is theme problem. But "终端显示中文是有问题的",and background color is garbled.

Duplicate https://github.com/Microsoft/vscode/issues/35660


feat: increase number of production email and sms celery pods

What happens when your PR merges?
- `feat:` - tag `main` as a new minor release

What are you changing?

[ ] Releasing a new version of Notify
[ ] Changing kubernetes configuration

Provide some background on the changes
change max celery pods from 30 to 40 ~, and sms-send pods from 11 to 20.~
This was done and tested on staging.

Checklist if making changes to Kubernetes:

[ ] I know how to get kubectl credentials in case it catches on fire

After merging this PR

[ ] I have verified that the tests / deployment actions succeeded
[ ] I have verified that any affected pods were restarted successfully
[ ] I have verified that I can still log into Notify production
[ ] I have verified that the smoke tests still pass on production
[ ] I have communicated the release in the #notify Slack channel.

sms already done and we'll do email after we move to its own deployment.


Error when trying to use the mod With forge 1.20

When ever i use the Mod it almost always gives me an error
it worked fine for like 3 days and now it no longer works
here is the error i get

can you help me fix this?

you also take fall damage when using teleport and elytra's

nvm, i fixed it by resetting the config file


Full YOLOv3 Support

Start with the why:
Although DepthAI already supports tiny-YOLOv3 (implemented in https://github.com/luxonis/depthai/pull/131), it can be useful in some cases it is advantages to use full YOLOv3 instead. Example include as when higher accuracy, more classes, or smaller objects need to be identified take precedent over the faster framerate of tinyYOLOv3.
Move to the how:
We already support the model itself, so likely the only additional items needed is the tensor output processing on the host.
Ideally, we should do this on the host to start, and then later support it on the DepthAI standalone as we are doing for tinyYOLOv3 in https://github.com/luxonis/depthai/issues/137.
Move to the what:
Implement support for YOLOv3 on DepthAI.

Hi Brandon, I am curious on what's the estimated FPS YoloV3 full?

Hi @zhijietan94 ,
Great question.  So full YOLOv3 seems to run about at 3.8FPS on DepthAI.
And actually thanks for the prod because this now does work in DepthAI in master.
Here's an example of running full YOLO:
Copy into /resources/nn/yolo-v3/yolo-v3.blob
Then change default blob in depthai.py to:
if default_blob:
    #default
    shave_nr = 14
    cmx_slices = 14
    NCE_nr = 2

https://drive.google.com/file/d/1uSnB_g0AL-zYPQjgBXJ7bkp-_CP5dpMu/view?usp=sharing
And then you can run it with ./depthai.py -cnn yolo-v3 -dd -sync -rgbf 3.8

The sync works fine up to 3.8 fps, and the lag is about 570ms (about 260ms -- 1 frame, is because of NN delay).  This is the standard 416x416 YOLOv3 full model.
So in develop branch that will be main (and the default branch) this will all be done automatically.  The model will be downloaded and compiled to the desired number of NCE and SHAVE/CMX.  Many other niceties (like a smaller repo) will come with develop as well.
But for now you can run it with the above.
Thoughts?
Thanks,
Brandon

Also the IOU and NMS are processed on DepthAI/megaAI directly in the https://github.com/luxonis/depthai/tree/openvino_tensor_representation branch as requested in https://github.com/luxonis/depthai/issues/137.  This will be going mainline as well.  And will allow https://github.com/luxonis/depthai/issues/140 .

Looks great! Would like to try it but the google drive link for YOLOv3 blob is restricted access. @Luxonis-Brandon Can you help to adjust the access rights for download? Thanks!

Yes, sorry about that.  One of my teammates owns the file so I'm re-uploading now and will make the permissions so that anyone can read it.  I'll change the link above and circle back shortly when that's done... uploading now.

Just updated it above @zhijietan94

Support added in #202


[securitycenter] v2 client's apiEndpoint property is wrong when a regional endpoint is specified

Please make sure you have searched for information in the following guides.

[X] Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
[X] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
[X] Check our Troubleshooting guide: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/troubleshooting
[X] Check our FAQ: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/faq
[X] Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
[X] Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
[X] Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples

A screenshot that you have tested with "Try this API".
n/a
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
https://gist.github.com/hegemonic/cf807026d8b83c14aa0b225b16967599
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
Run the code. It creates a v2 SecurityCenterClient; sets the apiEndpoint to securitycenter.me-central2.rep.googleapis.com; and prints the expected and actual apiEndpoint for the client.
A clear and concise description of what the bug is, and what you expected to happen.
The code prints the following:
expected apiEndpoint: securitycenter.me-central2.rep.googleapis.com
actual apiEndpoint: securitycenter.googleapis.com
client._opts.apiEndpoint: securitycenter.me-central2.rep.googleapis.com

I expected it to print the following:
expected apiEndpoint: securitycenter.me-central2.rep.googleapis.com
actual apiEndpoint: securitycenter.me-central2.rep.googleapis.com
client._opts.apiEndpoint: securitycenter.me-central2.rep.googleapis.com

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

If I specify an API endpoint, the client object shouldn't say that it's using the default endpoint.
You shouldn't need to look at private properties to figure out which endpoint the client is using.

@sofisl Why was this bug closed? I provided a valid link to a publicly visible gist.


NameError / typo in master

Hey,
thanks for creating this project!
When running with wait=False, I ran into a "NameError: name 'solver_proces' is not defined". The reason are typos in minizinc.py at lines 340 +341 (see https://github.com/paolodragone/pymzn/blob/a5de87f9b7fc2732fdd3cdc6640b681f46fdafdb/pymzn/mzn/minizinc.py#L340 ). In both lines the variable name should read 'solver_process', right now there is an 's' missing at the end.
Best,
-Matthias

Thank you for spotting this!
Fixed in a2c3b867b95.


125 implement upload files widget

Issue ticket number and link
Closes #125
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I have added tests

@evshi Please check this issue https://github.com/EnsembleUI/ensemble-react/issues/129


Drop superfluous 'global' statements from command.py

I don't see any reason that these statements should be necessary and find their presence confusing.
I'd love to hear feedback either way from any Pythonistas out there who might have some idea why these were added to begin with.

Probably just to make it clear/explicit that they are global variables. I don't see any other reason either.

Probably just to make it clear/explicit that they are global variables. I don't see any other reason either.

If we assume that there's no technical value, do you (subjectively) find it to be a helpful pattern?

The one upside I can think of is if the code changes and an assignment is added, then it doesn't sneakily turn into a local variable (IIUC), although linters might catch that.
I personally don't have a strong opinion; maybe some more experienced/opinionated people want to chime in.

Thanks for your thoughts.
I might suggest converting the variables to use MACRO_CASE to make it more clear that they're globals rather than the global statement.

This has been sitting for a while, and my preference is still to drop the statements, so I'm going to merge this.
Thanks everyone for your thoughts.


Docs redirect is intermittently working

The documentation website is https://kubeslice.io and this redirects to https://docs.avesha.io/documentation/open-source/0.2.0. This works intermittently and when hitting the link from the README, this doesn't open for new users.

kubeslice.io is now hosting the documentation @ https://kubeslice.io/documentation/open-source/0.2.0.


Incorrect tags on Wallet/Vault tabs.

Tags are incorrect
XD link: https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/379c47b1-90ba-488c-8763-e69db4b0768d/
see the comments in Xd link.

Verified this issue on keeper app v 1.1.11(295)


Using simulation to replace analytic dynamics

Hi, thanks for releasing this great work!
I am a researcher in robotics, and I am interested in applying learning of contraction metrics to certain settings where dynamics are not known or difficult to model analytically (and are instead found through e.g. simulation.) However, I noticed that the method for learning contraction metrics depends on matrices A = J_x(f), B = J_u(f) respectively.
To get around this restriction, one option is to approximate A, B with numerical estimates of the dynamics, e.g. by perturbing each dimension of x, u a small amount, running the pertubed inputs through simulation, and using the finite differences to construct the Jacobian.
Do you foresee that this will break the theoretical guarantees established for the contraction metric learning or cause any other issues for the learning process? Thanks very much!

Hi! Sounds like a cool project! I think we might be limited in terms of how much I can modify this codebase to support your use-case, but I'm happy to discuss how you might go about implementing this.
Thinking out loud on this:
To evaluate the contraction metric condition (and thus train the contraction metric + policy networks using our framework), we need the Jacobian of the dynamics w.r.t. both x (i.e. A) and u (i.e. B). The current code is implemented with the assumption that all of your dynamics are control-affine, but that is only necessary to solve the quadratic programs that arise in CLF/CBF/CLBF settings, and are not needed afaik for contraction metrics. If you have a simulator for your dynamics (i.e. f(x, u)), then you don't need analytical dynamics to get the Jacobians; all you need is to be able to auto-diff your dynamics function (using PyTorch, JAX, etc.), or you could use finite-differences (as you suggest). Another option is to ignore the negative-semidefinite contraction metric condition and instead just define a loss based on how much you observe the metric $(x^* - x)^T M (x^* - x)$ decrease over time along trajectories of your simulated system.
tl;dr

If you can implement your simulator using an automatically-differentiable framework (PyTorch, JAX, etc.), then just do that and define the contraction condition in the standard way for A and B
If you can't do that and still want to take the self-supervised "certificate learning" approach, then you can use finite differences as you suggest.
If you are fine taking a less-mathematically-justified but possibly-empirically-successful strategy, you could approximate the "contraction loss" by simulating a bundle of trajectories that all start out close to each other and observing how the metric between the trajectories changes over time. Each pair of trajectories gives you a metric value at each timestep, so you can numerically approximate $d/dt [(x_1 - x_2)^T M (x_1 - x_2)]$ and make a loss to encourage $d/dt (x_1 - x_2)^T M (x_1 - x_2) <= -2 * lambda * (x_1 - x_2)^T M (x_1 - x_2)$, averaged across all trajectories in the bundle. You could then minimize that using policy gradient (RL) or gradient descent (if you have an auto-diff-able simulator, but in that case it would be interesting to compare how effective this would be vs. the approach in 2.)

Hope that helps! I'm closing this issue, since this seems like more of a new research project and not something I want to add as a new feature to this existing project, but feel free to continue the discussion in this thread.

Thanks so much for the detailed response! I think I will go with option 2 for now, but potentially all the options you suggested sound promising, and would be interesting to implement and compare. Keen to revisit those at some point

Sounds good; good luck!


Dropdown with object as value throws warning

The Dropdown options property accepts a single value or an array of values.
In most cases however, the 'dataprovider' of a dropdown would be an array of objects retrieved from a service.
Referencing a selected object in the dropdown is important. So I set the value property in the options to the object itself.
To see an example, here's a codesandbox.
As you can see, this works perfectly but two warnings will be thrown in the console:
Warning: Failed prop type: Invalid prop `options[0].value` supplied to `Dropdown`.
in Dropdown`
Warning: Failed prop type: Invalid prop `value` supplied to `DropdownItem`.
in DropdownItem`

If passing object as value to the options property works without a problem, then the warning should be omitted.

You should pass value as string it's a known limitation and there will be no changes in a short-term.

Has there been a discussion in the past on this topic? It's a very handy feature and it actually works

You can search in our issues. actually it's works partially. There are many places in the Dropdown component where it uses === (deep equal) check on values and will silently break the object compassion.

It would be very helpful if we could pass objects as values instead of a string or arrays of strings. A common use case is when somebody changes the state on the onChange function and uses the value which is an object to update the state. If the value is a string, an id for example, you should make one more step, for e.x a lookup to an array of objects to find the object to update the state with.

No updates on that yet?
This is very useful if you want to pass in some react component. I was trying to use icons (not from the package, but an svg) in the content and, although it works, it throws that annoying error.

Same issue here. The code works fine when passing a react component to Dropdown text property, but throws an annoying warning in the console. Should the warning be removed and the text prop be updated to be {object|string}?


poetry Build System

Hey Raul,
I wanted to make some contributions around the issues I've been posting. As a first step I thought I'd offer up a build-system update.
This PR updates semversioner with the Poetry build system, which is a PEP517-based package management tool.
The tasks in the makefile have been replaced with poethepoet tasks. These can be invoked via:
poetry run poe lint
poetry run poe test
poetry run poe clean
# this will run semversioner release, generate a changelog, and update pyproject.toml
poetry run poe release

# additional parameters can be passed in as well, e.g.
poetry run poe test --junitxml=tests.xml

The release flow is also a little different. The publish script assumes that you're got a PyPi Trusted Publisher configured, which means you don't need $TWINE_USERNAME and $TWINE_PASSWORD. It also expects that developers have run poetry run poe release in a release branch.
If you'd like to use this, I'd be glad to help with any configuration issues you run into.
Thanks!
Chris

Hi @darthtrevino ,
Thanks for your contribution. I like the idea of moving to Poetry as well as setting up PyPi Trusted Publisher. Let's work on the details to make this merged.
Cheers!
Raul


Error deploying into production

Deployment into Sandbox is successful. Attempts to deploy in production result in the below error.
_Deployment CompleteTest failure, method: GetEventWhoRelationSObjectsInvocableTest.test_get_contacts -- System.DmlException: Insert failed. First exception on row 0; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: [] stack Class.GetEventWhoRelationSObjectsInvocableTest.test_get_contacts: line 23, column 1
Test failure, method: GetTaskWhoRelationSObjectsInvocableTest.test_get_contacts -- System.DmlException: Insert failed. First exception on row 0; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: [] stack Class.GetTaskWhoRelationSObjectsInvocableTest.test_get_contacts: line 23, column 1_

This issue was happening because we did not have a default Contact record type associated to our profile.


when i run python3 train_snli.py, it happens

pytorch:1.8.0
cuda:11.1

Apparently the issue seems to be that the data doesn't get loaded on the same device as the model. This shouldn't happen normally, since the scripts explicitly move the data on the same device as the model. Are you using a GPU to train your model ? Do you have multiple GPUs in your machine ?
If you know the specific identifier of the GPU you are using, you could try to replace line 58 in train_snli.py with device = torch.device("your_device_id") (where your_device_id is replaced by the actual id, something like cuda:0 or cuda:1 for example).
Please also note that this model was implemented with an older version of PyTorch (0.4), so maybe something has been broken in newer versions. The last version I tried the model on was PyTorch 1.0, and everything worked fine.

thank you, when i change the torch=1.5.1, its work


Clean up code climate issues

Code climate has many warnings about the code, one big one is related to a separate issue about our use of static and level. None of them would I consider to be necessarily high priority bugs, but it would be nice to get rid of them all so that future PRs that are only touching old code don't result in erroneous errors.

I pull #140 into 1.2.0 to refactor the levels which should resolve a lot of Code Climate issues and we have been looking to get this done for a while.

For tracking
There is currently:
224 Code Climate issues
310 Codacy issues

This is ready for review in PR https://github.com/rollbar/rollbar-php/pull/205


Feature/run storages

Run storages are available via /v2/actor-runs/{runId}/{key-value-store | log | request-queue | dataset} .. see https://docs.apify.com/api/v2#/reference/actor-runs/run-object-and-its-storages

Added the same tests as for actor().lastRun()

Please add simple tests.
There is a skeleton prepared already.
https://github.com/apify/apify-client-js/blob/master/test/runs.test.js#L204

Added the same tests as for actor().lastRun()


PI-3473 Rename "engine.provides" (#3590)

During work on #3556, it became clear to me that the use of engine.provides within the pyke rules, and in a few places within iris.fileformats.netcdf is confusing :  Because this term collides with the special reserved meaning of "provides" within Pyke rules, as seen in the repeated usage of facts_cf.provides(..) in most of our Pyke rules.
In fact, although engine is a Pyke object,  engine.provides is just a monkey-patched additional property attached by our netcdf code, to keep track of cube component objects created during rules evaluation (coordinates, cell-measures and ancillaries).
So, this PR just renames it to something less confusing.
This should produce no functional change.
Note - See #3590 for comments.  This PR is identical to it, but re-checks the tests as one of the travis tests had stalled for an unknown reason and couldn't be restarted.

Closed. Duplicate oof #3590


Auto SARIMA not picking up the Periodicity of the seasonality and when i try to give the start and end params, it throws a stationarity error. But for the same dataset if i use auto SARIMA in R i dont get any error.

Description

Steps/Code to Reproduce

Expected Results

Actual Results

Versions

Please fill out the fields above, or I can't help you.

Hey,
Sorry about the bad title.
Yes i was looking if i can give the seasonality manually. Thank you so much


chore: get test coverage above 70%

Codecov Report

Merging #15 into master will increase coverage by 3.79%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   64.65%   68.44%   +3.79%
==========================================
  Files          23       23
  Lines         447      450       +3
  Branches       14       14
==========================================
+ Hits          289      308      +19
+ Misses        154      137      -17
- Partials        4        5       +1

Impacted Files
Coverage Δ

src/app/shared/selection-changeset.ts
100% <100%> (+50%)
:arrow_up:

...app/preferences-page/preferences-page.component.ts
66.66% <0%> (-3.34%)
:arrow_down:

src/app/core/services/mocks.ts
80.85% <0%> (ø)
:arrow_up:

src/app/core/services/package.service.ts
59.25% <0%> (+7.4%)
:arrow_up:

src/app/app.component.ts
83.33% <0%> (+16.66%)
:arrow_up:

src/app/shared/focus-on-keys.directive.ts
100% <0%> (+20%)
:arrow_up:

Continue to review full report at Codecov.

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


Quit testing taggit on dj110

See https://github.com/alex/django-taggit/issues/384

The commit that required this was reverted in django.

The revert was not complete in django.

[Current coverage][cc-pull] is 97.07%

Merging [#665][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master    #665   diff @@
=====================================
  Files         104     104
  Lines        1608    1608
  Methods         0       0
  Branches        0       0
=====================================
  Hits         1561    1561
  Misses         47      47
  Partials        0       0

Powered by Codecov. Last updated by [00a110f...7668393][cc-compare]
[cc-base-branch]: https://codecov.io/gh/yourlabs/django-autocomplete-light/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/yourlabs/django-autocomplete-light/compare/00a110f46b8042d916e90260e92d411b245919f4...766839377e26ab73e031f65ca287333f43d9f351
[cc-pull]: https://codecov.io/gh/yourlabs/django-autocomplete-light/pull/665?src=pr

Fixed in django + we pass on dj110


NoMethodError: undefined method `symbolize_keys' for "na":String

Check full details on Airbrake: #1554496081057264962
Backtrace:
[PROJECT_ROOT]/app/models/topology.rb:38:in map
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:40:in block in each_node
[PROJECT_ROOT]/app/models/topology.rb:38:in each
[PROJECT_ROOT]/app/models/topology.rb:38:in each_node
[PROJECT_ROOT]/app/models/topology.rb:61:in validate_node_names
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:424:in block in make_lambda
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:184:in call
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:184:in block in simple
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:185:in call
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:185:in block in simple
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:185:in call
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:185:in block in simple
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:86:in call
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:86:in run_callbacks
[GEM_ROOT]/gems/activemodel-4.1.8/lib/active_model/validations.rb:376:in run_validations!
[GEM_ROOT]/gems/activemodel-4.1.8/lib/active_model/validations/callbacks.rb:111:in block in run_validations!
[GEM_ROOT]/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:82:in run_callbacks
[GEM_ROOT]/gems/activemodel-4.1.8/lib/active_model/validations/callbacks.rb:111:in run_validations!
[GEM_ROOT]/gems/activemodel-4.1.8/lib/active_model/validations.rb:317:in valid?
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/validations.rb:70:in valid?
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/validations.rb:77:in perform_validations
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/validations.rb:51:in save
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/attribute_methods/dirty.rb:21:in save
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:268:in block (2 levels) in save
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:329:in block in with_transaction_returning_status
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/database_statements.rb:199:in transaction
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:208:in transaction
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:326:in with_transaction_returning_status
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:268:in block in save
[GEM_ROOT]/gems/activerecord-4.1.8/lib/active_record/transactions.rb:283:in rollback_active_record_state!


Dashboard landing: Add a Dashboard + FlowFuse section

Description
Add a section highlighting the benefit or the power of the FlowFuse + FlowFuse dashboard package
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

@joepavitt could you please help me out with the text? Just adding a comment here would be enough, I'll take care of the web

I'm not great with words, but that's something

Thanks Joe!!


[TACHYON-1612] Use thread safety annotations in the integration module

Addresses: https://tachyon.atlassian.net/browse/TACHYON-1612
@apc999 @aaudiber

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8165/
Test PASSed.

+1 LGTM


Implemented all JSHandle tests

closes #10

It seems we have a real fail here @Meir017

just a flaky fail - PuppeteerSharp.Tests.Puppeteer.PuppeteerLaunchTests.UserDataDirArgument


Unhandled Rejection (TypeError): _globalThis.crypto.subtle is undefined

I believe env file is configured correctly.
This appear on ubuntu aws lightsail hosting.
env file :
nano
solana configs:
Config File: /home/ubuntu/.config/solana/cli/config.yml
RPC URL: https://api.devnet.solana.com
WebSocket URL: wss://api.devnet.solana.com/ (computed)
Keypair Path: /home/ubuntu/.config/solana/devnet.json
Commitment: confirmed

Hey figured this one out!.
It was coming from trying to run the program without SSL enabled. try to run HTTPS=true yarn start


feat: Added source_hash parameter to modules/object

Description

I added the source_hash parameter for the S3 bucket object.
Fixes #171
Motivation and Context

Attribute etag is not compatible with KMS encryption, so I can`t use it during update of uploaded file via terraform. Need to use attribute source_hash instead etag, but this attribute is missing in current object module.

Breaking Changes

No breaking change.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 3.4.0 :tada:


When project is in cargo's workspace, infer_schema! fails for "Failed to load environment variable POSTGRES_URL: environment variable not found"

My cargo workspace's structure is below:
workspace/
     |----Cargo.toml
     |----mydieselproject/
                |----Cargo.toml

When I build or test in the dir workspace with option "--all", building is failed. The message is
 --> diesel/src/schema.rs:2:1
  |
2 | infer_schema!("dotenv:POSTGRES_URL");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: message: called `Result::unwrap()` on an `Err` value: "Failed to load environment variable POSTGRES_URL: environment variable not found"
  = note: this error originates in a macro outside of the current crate

I think it is because the .env is not in dir workspace.

Did you figure out this issue? The error is saying it can't find your env variable, likely because you are missing your .env file as you suggested.

@lancecarlson
Hi, I've encountered the same issue. I'm not using dotenv, instead, I'm using
set_var("DATABASE_URL", db_path);
infer_schema!("env:DATABASE_URL");

Any suggestion?


devtoolset-6 6.1 candidate fails postgresql build due to hard-coded gcc 6.2 check

Looking at https://ci.centos.org/view/SCLo-pkgs-cbs/job/SCLo-pkg-devtoolset-6-rh-C7-candidate-x86_64/, it's been failing since build 42, when it started trying to build with devtoolset-6 6.1, including gcc 6.3.
The postgresql build script has a hard-coded test for gcc 6.2.
The fix for last time was 30ba89c0fe9cfa10320ffd950699d50a8cadd421 which just changed the hardcoded version from 5.2|5.3 to 6.2.
The simplest fix would be to check for 6.2|6.3. I feel like a check for gcc 6.* would be better, since that's the naming basis of devtoolset-6.

Thx, fixed by #23.