Linter info is not updated when file contents changed on autosave

When you have autosave enabled and a package which updates contents of file on save linter information is not updated.
See example gif:

Packages used:
linter 1.11.2
linter-rubocop 0.4.4
atom-beautify 0.28.19
autosave 0.23.0
Atom 1.2.4
OS X 10.10.5
What's happening:

linter via linter-rubocop detects incorrect styling.
autosave saves file on losing focus
On save atom-beautify removes incorrect styling.
File has correct styling, however "Project" status still shows an error. (minor bug)
File has correct styling, however linter shows errors. (major bug)
Editing\resaving file triggers linter checks and updates information to correct one.

@pluff I once see one bug here instead of many, that one "bug" is actually a feature, we only lint text editors that are active and it's very important for performance. Unless you have a very compelling reason for us to change that behavior, I would like it to stay that way :)

Can you add optional updating of information on save? I hope it will not be a performance decrease and linter status will show correct numbers. For some users it will be good alternative to "lint as you type" feature.

Another issue that might even be the core issue here is that there is no prioritization of handlers on the save event, this means that linter may be triggering on save, but only before Beautifier runs, thus it still sees the same contents as it did before the save.


Feat 246 json configs

Closes #246

Uses pydantic validator classmethod to perform datetime parsing
Adds option to submit all job configs as a json string (will make it easier to run a job with a rest request)
Pins spikeinterface

@alejoe91 I had to pin the spikeinterface dependency because the latest minor release broke the unit tests


[Gitlab] Add Dropdown to Search Projects

Description

At work we have over 500+ gitlab repositories. The Raycast Gitlab extension has a great "Search Projects" to quickly navigate to a repository, but it's searching through the whole public Gitlab. You get a lot of noise when searching because it's listing projects from random strangers when searching for a partial name (e.g. analytics, data, infrastructure, ...)
I expect the Gitlab "Search Projects" command to look for matching repositories where you are a member of. This is easy to restrict by using the membership: true parameter of the Gitlab Projects API.
Therefore, I added a simple search filter scope to the "Search Projects" command, similar to #6213
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the update @jessedobbelaere and thanks @jfkisafk for suggestions
@tonka3000 can you check this?

@pernielsentikaer Looks good. I agree with the code suggestions from @jfkisafk . After the change I will approve.

Applied the suggestions and tested it locally 👍 The filter value seems to persist now, excellent!

Hi 👋
Looks good to me, approved 🔥


Configure level for specific crate

I wanna to know if it's possible to init the logger with specific level for a crate ?
Something like: https://docs.rs/env_logger/0.10.0/env_logger/struct.Builder.html#method.filter_module
Thank you very much.
Marc-Antoine

This is possible, but you have to use the fern crate to do this with console_log. The console_log::log can be passed to fern's chain method. See the console_log::log docs for an example.


Cumulative Flow Chart dates not ordered correct

When using the cumulative flow chart, it orders the dates wrong.
It seems to mix up some dates, not all.
In the screenshot you can see 7, 8 and 12th of januari being out of place.

Some information to add after playing around today..
If i press execute a couple of times without changing any settings it will change the order of the dates.
It seems to be a random order of some sorts..

Just for my information, what type of database do you use? mysql or postgres or sqlite?

Database driver: postgres

This issue has been fixed in the development branch. Thanks!


Object to companion convertion function

sometimes I need to convert class to it's companion with all the filled fields set to it's value and all null fields set to Value.absent()  without doing it manually ..
example : convert a Message class to MessagesCompanion  with message.toCompanion();
could this be generated automatically for each table class ? or there is another way of doing that ?

Yup! You can just enable the data_class_to_companions build option. Drift will then generate a toCompanion(bool) function, where the parameter controls whether null fields should be mapped to Value.absent() or to Value(null).


postgres module not working as expected.

TL;DR
I want to create postgres cloudSQL instance with below code but it's create MySQL 5.7 type instance.
Please correct me if I doing wrong or missing something.
Expected behavior
with above code it must create postgres instance
Observed behavior
it's create mysql instance.
Terraform Configuration
`module "sql-db" {
  source                    = "GoogleCloudPlatform/sql-db/google//modules/postgresql"
  version                   = "10.0.0"
  name                      = "dev-mvault-test"
  project_id               = var.project
  region                     = var.region
  zone                       = data.google_compute_zones.available.names[0]
  database_version   = "12"
  enable_default_db  = false

}`

Terraform Version
$ terraform --version
Terraform v1.1.7
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v4.15.0
+ provider registry.terraform.io/hashicorp/google-beta v4.15.0
+ provider registry.terraform.io/hashicorp/null v3.1.1
+ provider registry.terraform.io/hashicorp/random v3.1.2

Additional information
No response

It's resolved. using below changes.
database_version  = "POSTGRES_12"
but it must be descriptive in variable definition.


Compiled Clarabel code sometimes producing wrong results compared to cvxpy only

Hi,
I noticed that the cvxpygen C code, with the python wrapper, may produce some wrong results even when solving with cvxpy works fine.
I say may because I've noticed that this behavior is not consistent and varies based on the problem.
I also think that this is related to #45 and #46 (and the associated commits).
Here are my observations. Note that in all cases, using cvxpy works fine.
Observations
MPC.ipynb benchmark

with cvxpygen v0.3.2:

ECOS produces a wrong result on the second run.
CLARABEL, OSQP, SCS work (even on the second run)
This was resolved through #45 and now with cvxpygen v0.3.3 or v0.3.4 all four solvers produce correct results even on the second run.

mpc_2d_robot benchmark (see code below)

with cvxpygen 0.3.2:

ECOS fails (again, this was addressed in #45) (control value jumps between max/min)
CLARABEL, OSQP, SCS work fine.

with cvxpygen 0.3.3 or 0.3.4

CLARABEL fails (control value constant and robot fails to reach the goal)
OSQP, SCS, ECOS work fine.

Notes
I'm on MacOS Sonoma 14.4.1 and using AppleClang. Python environment:

Python 3.10 (with Anaconda)
cvxpy 1.4.3
osqp 0.6.5
scs 3.2.4.post1
ecos 2.0.13
clarabel 0.7.1

The main issue is that with cvxpygen v0.3.3 and v0.3.4, CLARABEL compiled code sometimes doesn't work as expected.
Going back to v0.3.2, ECOS produced wrong code on the second run, but CLARABEL worked fine.
Code
mpc_2d_robot benchmark
import time
import cvxpy as cp
import numpy as np
from cvxpygen import cpg
from matplotlib import pyplot as plt

def mpc_2d_robot(use_cpg=False, gen_cpg=False, plot_res=False, solver=cp.CLARABEL):
    """
    Certainty equivalence MPC. Linear dynamics with additive noise.
    :return:
    """
    # Dynamics
    A, B = np.eye(2), np.eye(2)

    def dyn(x, u):
        return A @ x + B @ u  # dynamics

    T = 7  # horizon
    x0_val = np.array([-2, -0.8])  # initial state
    Q, R = np.diag([1, 1]), np.diag([1, 1])  # object cost matrices

    # params and vars
    x0 = cp.Parameter(2, 'x0')
    ctrl = cp.Variable((2, T), 'ctrl')
    state = cp.Variable((2, T + 1), 'state')

    def find_xQx(t_future, u, x_now):
        xt = find_xt(t_future, x_now, u)
        return cp.QuadForm(xt, Q)

    def find_xt(t_future, x_now, u):
        At = np.linalg.matrix_power(A, t_future)
        xt = At @ x_now
        for i in range(t_future):
            Ai = np.linalg.matrix_power(A, i)
            Bu = B @ u[:, t_future - 1 - i]
            AiBu = Ai @ Bu
            xt = xt + AiBu
        return xt

    # define optimization problem
    obj = 0
    for t in range(T):
        obj += find_xQx(t + 1, ctrl, x0)
        obj += cp.quad_form(ctrl[:, t], R)

    constr = [state[:, 0] == x0]
    for t in range(T):
        constr += [state[:, t + 1] == dyn(state[:, t], ctrl[:, t])]
    constr += [ctrl <= np.array([[0.2, 0.2]]).T,
               ctrl >= np.array([[-0.2, -0.2]]).T]

    prob = cp.Problem(cp.Minimize(obj), constr)

    if use_cpg:
        if gen_cpg:
            cpg.generate_code(prob, code_dir='mpc_2d', solver=solver)
        from mpc_2d.cpg_solver import cpg_solve
        prob.register_solve('cpg', cpg_solve)

    # sim settings
    steps = 20
    current_state = x0_val
    # plotting results
    x_hist = [current_state]
    u_hist = []
    t_hist = []
    for t in range(steps):
        x0.value = current_state
        if use_cpg:
            if solver in [cp.ECOS, cp.OSQP]:
                ts = time.time()
                prob.solve(method='cpg', updated_params=['x0'])
                te = time.time()
            else:
                ts = time.time()
                prob.solve(method='cpg', updated_params=['x0'], verbose=False)
                te = time.time()
        else:
            ts = time.time()
            prob.solve(solver)
            te = time.time()

        t_hist.append(te - ts)
        print(prob.status)
        u_now = ctrl.value[:, 0]
        next_state = dyn(current_state, u_now)
        x_hist.append(next_state)
        current_state = next_state
        print(current_state)
        u_hist.append(ctrl.value[:, 0])

    x_hist = np.array(x_hist)
    u_hist = np.array(u_hist)
    if plot_res:
        plt.plot(x_hist[:, 0], x_hist[:, 1])
        plt.scatter(0, 0)
        plt.show()
        fig, axs = plt.subplots(2)
        axs[0].plot(range(steps), u_hist[:, 0])
        axs[1].plot(range(steps), u_hist[:, 1])
        plt.show()
    return t_hist

if __name__ == "__main__":
    # solver_list = [cp.OSQP, cp.SCS, cp.CLARABEL, cp.ECOS]
    solver = cp.CLARABEL
    mpc_2d_robot(use_cpg=False, gen_cpg=False, plot_res=True, solver=solver)
    mpc_2d_robot(use_cpg=True, gen_cpg=True, plot_res=True, solver=solver)

# in all cases, cvxpy solves fine
# results for codegen:
# cvxpygen 0.3.2:
# - works: OSQP, SCS, CLARABEL
# - fails: ECOS
# cvxpygen 0.3.3:
# - works: OSQP, SCS, ECOS
# - fails: CLARABEL
# cvxpygen 0.3.4:
# - works: OSQP, SCS, ECOS
# - fails: CLARABEL

MPC.ipynb code (slightly modified version of MPC.ipynb)
import cvxpy as cp

# cvxpygen v0.3.2:
# - works: CLARABEL, OSQP, SCS,
# - fails: ECOS
# cvxpygen v0.3.3:
# - works: CLARABEL, OSQP, SCS, ECOS
# - fails: /
# cvxpygen v0.3.4:
# - works: CLARABEL, OSQP, SCS, ECOS
# - fails: /

# solver_list = [cp.OSQP, cp.SCS, cp.CLARABEL, cp.ECOS]
solver = cp.ECOS

# define dimensions
H, n, m = 10, 6, 3

# define variables
U = cp.Variable((m, H), name='U')
X = cp.Variable((n, H+1), name='X')

# define parameters
Psqrt = cp.Parameter((n, n), name='Psqrt')
Qsqrt = cp.Parameter((n, n), name='Qsqrt')
Rsqrt = cp.Parameter((m, m), name='Rsqrt')
A = cp.Parameter((n, n), name='A')
B = cp.Parameter((n, m), name='B')
x_init = cp.Parameter(n, name='x_init')

# define objective
objective = cp.Minimize(cp.sum_squares(Psqrt@X[:,H]) + cp.sum_squares(Qsqrt@X[:,:H]) + cp.sum_squares(Rsqrt@U))

# define constraints
constraints = [X[:,1:] == A@X[:,:H]+B@U,
               cp.abs(U) <= 1,
               X[:,0] == x_init]

# define problem
problem = cp.Problem(objective, constraints)

import numpy as np

# continuous-time dynmaics
A_cont = np.concatenate((np.array([[0, 0, 0, 1, 0, 0],
                                   [0, 0, 0, 0, 1, 0],
                                   [0, 0, 0, 0, 0, 1]]),
                         np.zeros((3,6))), axis=0)
mass = 1
B_cont = np.concatenate((np.zeros((3,3)),
                         (1/mass)*np.diag(np.ones(3))), axis=0)

# discrete-time dynamics
td = 0.1
A.value = np.eye(n)+td*A_cont
B.value = td*B_cont

# cost
Psqrt.value = np.eye(n)
Qsqrt.value = np.eye(n)
Rsqrt.value = np.sqrt(0.1)*np.eye(m)

# measurement
x_init.value = np.array([2, 2, 2, -1, -1, 1])

val = problem.solve(solver=solver)

from cvxpygen import cpg

cpg.generate_code(problem, code_dir='MPC_code', solver=solver)

from MPC_code.cpg_solver import cpg_solve
import numpy as np
import pickle
import time

# load the serialized problem formulation
with open('MPC_code/problem.pickle', 'rb') as f:
    prob = pickle.load(f)

# assign parameter values
prob.param_dict['A'].value = np.eye(n)+td*A_cont
prob.param_dict['B'].value = td*B_cont
prob.param_dict['Psqrt'].value = np.eye(n)
prob.param_dict['Qsqrt'].value = np.eye(n)
prob.param_dict['Rsqrt'].value = np.sqrt(0.1)*np.eye(m)
prob.param_dict['x_init'].value = np.array([2, 2, 2, -1, -1, 1])

# solve problem conventionally
t0 = time.time()
# CVXPY chooses eps_abs=eps_rel=1e-5, max_iter=10000, polish=True by default,
# however, we choose the OSQP default values here, as they are used for code generation as well
val = prob.solve(solver=solver)
t1 = time.time()
print('\nCVXPY\nSolve time: %.3f ms' % (1000 * (t1 - t0)))
print('Objective function value: %.6f\n' % val)
cvxpy_only_val = prob.value

# solve problem with C code via python wrapper
prob.register_solve('CPG', cpg_solve)
t0 = time.time()
val = prob.solve(method='CPG')
t1 = time.time()
print('\nCVXPYgen\nSolve time: %.3f ms' % (1000 * (t1 - t0)))
print('Objective function value: %.6f\n' % val)

prob.register_solve('CPG', cpg_solve)
t0 = time.time()
val = prob.solve(method='CPG')
t1 = time.time()
print('\nCVXPYgen\nSolve time: %.3f ms' % (1000 * (t1 - t0)))
print('Objective function value: %.6f\n' % val)

cvxpygen_val = prob.value

print("~~~~~~~~~~~~~~~~~~~~~~~~~~~~~")
print("Summary: ")
print("cvxpy only:\n\t", cvxpy_only_val)
print("cvxpygen (2nd solve):\n\t", cvxpygen_val)

Thanks for pointing this out, it is fixed in version 0.3.5.

Thanks!


Support for designated (non-simple) initializers on OS X

In lib/motion-kit/helpers/tree_layout.rb the protected method initialize_element has the comment:
# This will need to be smarter going
# forward as new isn't always the designated initializer
I am hoping that time is now.
To create a NSMatrix control on an OS X view the designated initializer is initWithFrame:mode:cellClass:numberOfRows:numberOfColumns:
Unfortunately once an NSMatrix view is created, there is no setter for the number of columns or rows, you need to call addRow and addColumn multiple times.
Allowing the elem parameter to be either a Class or an instance would allow the add method in the to work like:
add NSMatrix.alloc.initWithFrame([[0,0],[0,0]], mode: NSRadioModeMatrix, cellClass: thing, numberOfRows: 4, numberOfColumns: 3), :my_radio_grid

Actually, the add method already accepts an instnace!  It's only when you use the shorthand:
add NSMatrix, :my_radio_grid
that new is called on the class.  You can pass in an instance instead, like you are doing here.

Cool, works perfectly, sorry to have caused you any trouble Colin. Thanks to you Jamon for such a great gem.

:+1: Glad you're finding it useful!

(I assume you meant "you and Jamon" -- Colin is the primary dev on this!)

Yeah, should always take one last read before hitting submit. Thanks to both of you
And it is extremely useful, I can't imagine working without it


The inspect command should accept a second argument

Currently, the inspect command only take one argument. It used to take a second argument. See http://getfirebug.com/wiki/index.php/Inspect
Florent

Shouldn't this also drop the developer on to the DOM Panel eg running inspect(document) doesn't take you to the DOM panel


bbl should have a teardown command

It should be called bbl burst or bbl pop.

We will optimize for puns in the 2.0 release ;)


Switch from davinci to gpt-3.5-turbo

Switching to gpt-3.5-turbo seems to make the most sense now. As per https://openai.com/blog/introducing-chatgpt-and-whisper-apis
Model: The ChatGPT model family we are releasing today, gpt-3.5-turbo, is the same model used in the ChatGPT product. It is priced at $0.002 per 1k tokens, which is 10x cheaper than our existing GPT-3.5 models. It’s also our best model for many non-chat use cases—we’ve seen early testers migrate from text-davinci-003 to gpt-3.5-turbo with only a small amount of adjustment needed to their prompts.

Does work nicely. Maybe could even alter the code somehow to keep the context, if needed, to improve on previous responses like in chatgpt.
However there are a lot of pointless descriptions or explanations.. Maybe should prepend omit explanations/descriptions to each prompt? :D
If this isnt taken care of, I suppose you might have to reject this change as the difference in output is significant in some cases. Well, as OpenAI wrote: with only a small amount of adjustment needed to their prompts.

Thanks for you contribution @dennislapchenko. We do need to get rid of the explanations and only emit code, and we are actually already working on that with the new ChatGPT API. However, before aiac's first release, it actually worked against the unpublished ChatGPT API, and had two outputs: one for only the code, and the other for the full Markdown of the explanation (the latter being optional). We are revisiting this option and will make our decision soon.

Thanks again @dennislapchenko, we have decided to extract the code by default, and also allow keeping the complete output with a flag (--full). We're also allowing selecting different models. A new release is pending.


[pkg/collectors/corechecks/snmp] Move implementation to internal

What does this PR do?

Move all folders but common (used by pkg/snmp) to an internal folder.
Motivation

Reduce public API surface to make it easier to modularize Datadog Agent codebase. See here for explanation of internal packages.
Additional Notes

No-op, detected by this WIP tool.
Possible Drawbacks / Trade-offs

None: it can be reverted if needed. However, if you know that you want any of these packages to be part of the public API of your folder, maybe it doesn't make sense to merge (all of) this.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

🤔 I probably need to rewrite some references to the test folder on some of the tests


Make receive v2 compatible with Python 3

Use urlencode already imported in util.py.

Fixed by #29


[SMALLFIX] Remove getChannel from BlockWriter interface

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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


what do you have against module.hot?

Why does the following code trigger this rule?
if (module.hot) {
    console.warn('module.hot');
}

Not doing any require, but just by accessing this property, eslint starts complaining. Doesn't make sense, or am I missing something here?

What complaint? Can you provide the warning output?
(Either way, module.hot isn't a standard node thing, so relying on it is a super bad idea)

There is nothing else other than eslint complaining that this rule has been violated:
The complete error message is this:

Cannot use import declarations in modules that export using CommonJS (module.exports = 'foo' or exports.bar = 'hi')eslint(import/no-import-module-exports)

It prints this error for each line of import inside the file that used the above code

Just as I said that, I found the correct way of checking for hot module replacement using es6 syntax:
if (import.meta.webpackHot {
    console.warn('module.hot');
}

module indeed doesn't exist in ESM modules. Glad you figured it out!


Objs doesn't return anything when removing a class

The definition of the Objs method tells that it will always return an instance of a class, but returns nothing when called for removing a class. It must return the removed class when found.

Now the Objs("some.classpath",null) remove the associated class from the internal map and return it


added ingest url to config

Please add support for this as this is likely to change with the base_url too :
client.base_ingest_url = "..."


Sticky header with CSS

The current solution for sticky headers is based on JavaScript. Please check whether it is possible to revert that solution and to use position. sticky (See http://gedd.ski/post/position-sticky/). If that is impossible, please describe why.
Browser support is listed there: http://caniuse.com/#feat=css-sticky
Demo: http://html5-demos.appspot.com/static/css/sticky.html
Refs https://github.com/ultimate-comparisons/ultimate-comparison-BASE/pull/31

Hint: Use top css in addition - see https://stackoverflow.com/a/43707215/873282

#wontfix
Sticky headers do not work together with table header display: table-header-group;.
Other display styles do synchronize the dynamic width between the table header and the table data.
A css-grid solution might come handy in the future but the feature display: subgrid has been excluded for Firefox and Chrome in the first Version of css-grid (https://github.com/w3c/csswg-drafts/issues/958).


UP board

Dear Sir,
Can I use this library on Up board that runs on Ubuntu 16.04 LTS instead of a raspberry pi?
Thank you,

@joekh1 You have to install all required drivers first, check https://github.com/google/aiyprojects-raspbian/blob/aiyprojects/HACKING.md for details.

Please open new issues if you have problems installing our drivers to Ubuntu.


manifest not working with provisionedConcurrency

it seems that the plugin is not working with the provisionedConcurrency property..
  Error: File "src/functions/static/get-genders.js" not found. /Users/orrlevinger/projects/BlindChat/blind-chat-backend/src/functions/static/get-genders.js missing
      at getFunctionPath (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/serverless-manifest-plugin/src/index.js:535:11)
      at Object.keys.reduce.urls.apiGateway (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/serverless-manifest-plugin/src/index.js:317:30)
      at Array.reduce (<anonymous>)
      at getFormattedData (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/serverless-manifest-plugin/src/index.js:213:52)
      at /Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/serverless-manifest-plugin/src/index.js:85:30
      at tryCatcher (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/promise.js:729:18)
      at _drainQueueStep (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/async.js:93:12)
      at _drainQueue (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues [as _onImmediate] (/Users/orrlevinger/projects/BlindChat/blind-chat-backend/node_modules/bluebird/js/release/async.js:15:14)
      at processImmediate (internal/timers.js:461:21)

getGenders:
handler: src/functions/static/get-genders.handler
provisionedConcurrency: 5
all other functions works..

If you are using typescript you want to use the srcPath option https://github.com/DavidWells/serverless-manifest-plugin/pull/18/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R44
This should resolve the file

https://github.com/DavidWells/serverless-manifest-plugin/pull/18

If you are using typescript you want to use the srcPath option https://github.com/DavidWells/serverless-manifest-plugin/pull/18/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R44
This should resolve the file

https://github.com/DavidWells/serverless-manifest-plugin/pull/18

Not sure i understand what you mean by that..
where to use srcPath


feat(MLflow)[KLV-30]:  Support mlflow

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #103
Reference to #

Special notes for your reviewer:
/cc @your-reviewer

Release note:

NONE

/assign @simon-cj

/kind feature

/lgtm


Version from pip package & CI

Set the snap version from the pip package and add a snap CI workflow.
To automatically publish the snap to the store you will need to set up the credential in SNAPCRAFT_STORE_CREDENTIALS, see the action doc.

Unfortunately there aren't arm-based runners as of now.
The only solutions at the moment are using some qemu-based container for emulation or self-hosted runners...

Just discovered this, but did you play in the past with run-on-architecture? It looks like a plug-and-play wrapper over QEMU.

I haven't used this action, other similar exists.
I'll leave it to you to support arm in CI tho ;)


Feature request: extrapolation of regional scoreboard values

A frequently-asked question during play is roughly "if things stay about how they are, which team will win this cycle in the region?" A good way to represent this, I think, would be to show (on a checkbox selected, presumably) what the end-of-cycle score would look like with some sort of extrapolation for checkpoints that haven't yet happened.
As far as a method of extrapolation, my best idea would be to use the median values of past checkpoints (to exclude e.g. the effects of single-checkpoint mega field spikes as well as more general fluctuation). Another option would be to use the most recent checkpoint's values.

It should be the median to match expectations against the ingame median line.

@ryantheleach: What makes you think the in game line is the median, when the in game score shown is the mean?
I do agree that median and most recent checkpoint are both good extrapolations to look at, unfortunately it varies which one is more useful. For example, if a large field was up overnight near the beginning of a cycle, it can take awhile for the median to adjust to something reasonable.


Join ON fails to parse from Oracle

the following does not parse:
SELECT * FROM a JOIN b JOIN c ON b.id = c.id ON a.id = c.id
It is legal in Oracle.
Parsing fails on master.
following one succeeds:
SELECT * FROM a JOIN (b JOIN c ON b.id = c.id) ON a.id = c.id

This join construct is not (yet) implemented.
-------- Ursprüngliche Nachricht --------Von: dondank<EMAIL_ADDRESS>Datum: 26.03.18  12:56  (GMT+01:00) An: JSQLParser/JSqlParser<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Betreff: [JSQLParser/JSqlParser] Join ON fails to parse from Oracle (#596)
the following does not parse:
SELECT * FROM a JOIN b JOIN c ON b.id = c.id ON a.id = c.id
It is legal in Oracle.
Parsing fails on master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/JSQLParser/JSqlParser","title":"JSQLParser/JSqlParser","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/JSQLParser/JSqlParser"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Join ON fails to parse from Oracle (#596)"}],"action":{"name":"View Issue","url":"https://github.com/JSQLParser/JSqlParser/issues/596"}}}

is this planned? JOIN-ON  is very common in most databases.
Thanks.

Let me take a look. If parenthesis parsing succeeds it should not be that hard. Cheers Tobias

This would introduce a circular production hell. Its not so easy as I thought. Sorry.

There are any plans to support it? I have a lot of cases with queries that have it.

Works with JSQLParser-4.2


react-components: improve test cov

What's new

Self-checks

[ ] I'm familiar with and follow this Typescript guideline
[ ] I added unit-tests for new components
[ ] I tried testing edge cases
[ ] I tested the behavior of the components that interact with the backend, with an e2e test

Discussion

  custom-lookup-filter.tsx                  |      65 |    58.33 |   42.86 |   64.71 | 61-71

@matiasbavera can you see if you can help to add some tests for the above lines? Feel free to add commits to this pr.

@matiasbavera can you see if you can help to add some tests for the above lines? Feel free to add commits to this pr.

Done! Thanks for the tagging


✏ Rename resizeable to resizable

Context:
When working with OrbTK, resizeable has been causing me some pain. This pull request corrects its spelling to resizable and provides migration / depreciated functions for the old spelling.
Reference to a related issue in the repository. Still no clue
Contribution checklist:

[x] Add documentation to all public structs, traits and functions.
[ ] Add unit tests if possible
[x] Describe the major change(s) in the CHANGELOG.MD
[x] Run cargo fmt to make the formatting consistent across the codebase
[x] Run cargo clippy to check with the linter

Thanks for this PR. Looks good to me. Merged!


python312Packages.sqlalchemy-utils: 0.41.2 -> 0.42.2

Diff: https://github.com/kvesteri/sqlalchemy-utils/compare/refs/tags/0.41.2...0.42.2
Changelog: https://github.com/kvesteri/sqlalchemy-utils/releases/tag/0.42.2
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

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

@ofborg build python312Packages.sqlalchemy-utils python311Packages.sqlalchemy-utils pacu python312Packages.starlette-admin

Part of #345326


Add global data collection switch.

NOTE: This shouldn't be public until all SDKs conform to the setting.
This allows developers to enable/disable all collection at compile time and override it at runtime.

Closing and rebasing on master, will open again shortly.


Expansion Panel - Remove from DOM when closed/minimized

Please describe the feature you would like to request.
I would like the "expansion-panel" be removed from the DOM when minimized/closed and not hidden with CSS style.
What is the use-case or motivation for this proposal?
I have a "mat-accordion" with a list of "mat-expansion-panel" - a very long list, between 500 to 1000 items.
Each "mat-expansion-panel" has a child element: "mat-expansion-panel-content". This element is hidden with CSS style (visibility: hidden;) when the mat-expansion-panel is minimized/closed.
Due to this there is a big performance issue, since the browser need to handle all of these hidden DOM objects.
I would like "mat-expansion-panel-content" will be removed from the DOM when the "mat-expansion-panel" is closed - with *ngIf or any other way and not only hidden.
Is there anything else we should know?
I would like to know if there is any work around this issue, if a framework solution (development) will not be presented soon.

You could use the matExpansionPanelContent to render the content lazily only after one of the panels is opened. Note that this won't remove it again after it is closed. Docs: https://material.angular.io/components/expansion/overview#lazy-rendering.

I have developed a work-around for this issue, by adding a isOpen parameter to each "mat-expansion-panel". And put the "mat-expansion-panel-content" in a *ngIf.
<mat-accordion>
  <mat-expansion-panel *ngFor="let item of list"
                       (opened)="item.isOpen = true"
                       (closed)="item.isOpen = false">
    <mat-expansion-panel-header>
      <mat-panel-title>
        Self aware panel
      </mat-panel-title>
      <mat-panel-description>
        Currently I am {{item.isOpen ? 'open' : 'closed'}}
      </mat-panel-description>
    </mat-expansion-panel-header>

I'm visible because I am open

  </mat-expansion-panel>
</mat-accordion>

see: stackblitz
however since this isn't a native solution the animation isn't so smooth.

I was able to construct a directive that does just that:
https://stackblitz.com/edit/angular-os5cc6?file=src%2Fapp%2Fexpansion-overview-example.ts

check the js console
there is not changeDetection when expansionPanels are closes

Why is this feature not on board? I assume this improves speed of a CD cycle meaning overall performance. --> Problem with my approach - you will loose state (filled forms etc, because you create new instances all the time)
I tried accessing the ChangeDetectorRef of ExpansionPanelComponent but I had no success. It still checks my "cd-check-components".
Same is true for "material tabs" there should be an option for "what I dont See, please dont check".
Any input/ ideas?
@crisbeto @jelbourn @kara ?

Duplicate of https://github.com/angular/components/issues/20680.


ci: Combine labeller and size labels steps in PR workflow

Pull Request
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

#138  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 26, 4:17 PM EDT: A user merged this pull request with Graphite.


The code for creating user with AdditionalData does not seem to be correct

I have tried This Code to create users with custom data. Evenything was working fine with AD Graph Client, but with MS Graph Client (All new app was created and permissions were set according to all docs) .. but I keep getting this error when I call AddAsync:
Message: One or more properties contains invalid values.
Inner error:
	AdditionalData:
	date: 2021-06-22T14:24:45
      . . .

When I use wrong attribute name or wrong extention app id I get this error
Code: Request_BadRequest
Message: The following extension properties are not available: extension_XXXX...XXX_MyProp.
Inner error:
	AdditionalData:
	date: 2021-06-22T15:11:44

Apparently the issue is about missing identity but the error is not clear at all and writes AdditionalData: which made me think the problem is in AdditionalData!

AdditionalData just means "here is some extra information that could be related to your issue"...


Licensing doc

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a8466904919b2ff80fff1a525b7ad427ede948f5/

@robert-s-lee Can you check the doc for technical accuracy and completeness?
@jseldess Structural review please :)

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a8466904919b2ff80fff1a525b7ad427ede948f5/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a8466904919b2ff80fff1a525b7ad427ede948f5/

Had a question from a customer in the past about whether the license can be set in --insecure as well as --secure mode.  May make sense to show both insecure and secure examples.  Do we want to describe what happens when the license expires in this doc?

@robert-s-lee We do talk about license expiration in the doc. Are you suggesting we don't talk about it, or talk about it in more detail?

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a8466904919b2ff80fff1a525b7ad427ede948f5/

maybe more in detail.  One concrete example is after the expiration, the restore and backup commands will not work until the license is renewed.

@robert-s-lee Apart from including more details in the expiration section, and including examples of secure and insecure, the rest of the doc looks okay?

Yes, the rest looks good.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a89d3133041522263b7239e6b491f0160a00f737/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/482bcb7910545b6ae077f9a07d0b9e5a4b368e4d/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1813fbad3e0f52dd3bf153f4c75c0f95fccf7b13/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c4b938ad1e12a6103bf37c215c2d203f82fb3ad1/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/47acf94faffa94ca02281463ce7cc9c46af60cfb/


Update algorithm

https://github.com/open-spaced-repetition/fsrs4anki/wiki/The-Algorithm
https://www.reddit.com/r/Anki/comments/15mab3r/fsrs_explained_part_1_what_it_is_and_how_it_works/?share_id=X4krPVjObRd2xu3G57Icq&utm_content=2&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=9

https://github.com/open-spaced-repetition/swift-fsrs
@kevinzhow  should we transfer to this library?


React >= 15.5.0 support

Use prop-types module instead of React.PropTypes, standardised usage
Updated react-docgen version constraint
Updated yarn lockfiles

Addresses https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html#new-deprecation-warnings

When is this going to be release?

@jarzuaga It's already released.

It's on npm, however GitHub doesn't have a tag/release for 0.4.3 yet.
BTW, I've noticed some other dependencies are giving deprecation warnings but haven't been updated yet. See below for relevant issues.

react-copy-to-clipboard: https://github.com/nkbt/react-copy-to-clipboard/issues/55
radium: https://github.com/FormidableLabs/radium/issues/895

@OscarBarrett I've added new release on Github. We'll take a look on these warnings later, thanks for pointing it out.

@OscarBarrett thanks


parseIP Error ip=[172 17 0 2 0 0 0 0 0 0 0 0 0 0 0 0]

I am using libnetwork/ipvs to fetch the destinations for each ipvs service.
following is the code statement.
		destinations, err := c.ipvsHandle.GetDestinations(service)
After latest commit I am getting error while fetching destinations of service.
parseIP Error ip=[172 17 0 2 0 0 0 0 0 0 0 0 0 0 0 0]
Please help me on this. I am not able to fetch the destinations of each ipvs service.

I'm tracking this error too, it's a BUG from https://github.com/docker/libnetwork/pull/2416


Implemented console script creation via pip approach, now `ansible-li…

Solving #148

I'd rather large PRs were discussed before submission.
The README is not updated to say how to run from source (as bin/ansible-lint will no longer work).
This will need rebasing onto the new v3.0 branch, as that'll be the next release.
Might be worth doing git mv bin/ansible-lint lib/ansiblelint/__main__.py as one commit and then making changes afterwards (otherwise I suspect the history will be harder to follow)

I think I've now implemented the console_scripts stuff separately. If there are any outstanding improvements remaining in this PR, please rebase them on current master, otherwise I'll close this one.

Yep, this PR become obsolete and I will have to create another one if I find some minor bugs that were not fixed yet.
I really hate that github is not able to keep forks in sync with upstream.


Missing hyperlink?

In the Configure for the Web section of https://firebase.google.com/codelabs/firebase-get-to-know-flutter#3:

Feel free to read more about Firebase Hosting here. << Is "here" supposed to be a link? Right now it's just text.

Hi @Khongchai thanks for filing this issue, I was able to reproduce it.

My bad, I forgot to ask the question. I can't see the text you are alluding to in the codelab. Can you please re-check https://firebase.google.com/codelabs/firebase-get-to-know-flutter#3 for the area that you are looking for? It may have been taken out when we simplified the integration story.

Yeah, it's no longer there.


docs(text-input): add docs for text input component

:tada: This PR is included in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


trace_file don't work, if env "log_root" is set.

This is a little bugfix for trace_file funktion.

This should get into 3.0, if not a 2.x point release @jonmeredith @macintux

Rebased and merged into intg => all tests pass

Also going to put this on mra/otp-17 as it seems like a good bug fix for 2.x


chore(deps): Remove peerDependencies

peerDependencies seems useless and generate warnings https://github.com/jhipster/jhipster-lite/issues/9030

Hello, this breaks installation in a big monorepo if there are multiple vue versions for different parts of the monorepo.
For example here using pnpm, vue test utils is incorrectly installed in a<EMAIL_ADDRESS>folder:

This causes the require('vue') to resolve to a potentially incorrect version of vue and can lead to multiple versions of vue being evaluated in vitest:

Pinning vue test utils to 2.4.4 solves this as pnpm is able to install the correct versions of vue-test-utils and vue so they are resolved correctly:

Which makes the test pass (no duplicate vue):


feat(schema) add support for subschemas

This resolves three difficulties that would appear when porting the Plugins entity over to the new DAO: loading the plugin configuration schema dynamically, the fact that this schema depends on a value of the entity row itself, and the fact that the specific plugin type can impose further constraints on values.
The old DAO implemented this by allowing records to have a schema field that would be either a table or a function evaluated at validation time, and using an ad-hoc validation that checked for a no_consumer field to restrict the value of consumer_id to null.
The new DAO implements this by allowing an entity (such as Plugins) to declare that it is extensible via subschemas:

a schema may declare that it allows subschemas, tagged by one specific string key of the schema, with the top-level subschema_key property.

essentially, the set of all plugins taken as one works like a tagged union.
for Plugins, subschema_key will be "name"

a schema may declare where it gets subschemas from, with the subschema_module.

for Plugins, subschema_module will be "kong.plugins.?.schema"

the parent schema may declare fields as "abstract", which are meant to be specialized by the subschema. Abstract records don't need their fields property to be set, and they must be given in the specialized ones.

for Plugins, config will be abstract

the set of fields considered when validating an entity is that of the parent schema

subschemas cannot introduce new fields, those need to be declared in the parent schema ("abstract" if needed)
the data model of strategies can be inferred from parent schema alone

subschemas may override both abstract and non-abstract fields.

they cannot change the type of a field
a field declared in the subschema overrides the parent schema's field completely (constraints are not merged)
for Plugins, plugins will override config, and for the no_consumer feature, they can override consumer using the eq = null validator

I am not sure the parent needs to know where his subschemas are: the  "kong.plugins.?.schema" part is not needed as far as I know - as long as we "keep track of the list of subschemas" when a new subschema is found.
Similarly, I don't think the abstract field abstraction is needed. It seems to me that the only reason to have them is to raise an error if someone wants to instantiate a Plugin without the correct subschema. But in that case we can still raise an error by detecting that the subschema_key doesn't correspond with any of the loaded subschemas.

I am not sure the parent needs to know where his subschemas are: the "kong.plugins.?.schema" part is not needed as far as I know - as long as we "keep track of the list of subschemas" when a new subschema is found.

We need that otherwise the knowledge of this path ends up hardcoded somewhere. This is already a problem with core entities because foreign relationships assume that other entities are core entities: https://github.com/Kong/kong/blob/master/kong/db/schema/init.lua#L1182-L1183 (@james-callahan has had problems with that line already). I don't want to repeat this. For foreign-key relationships we could have made it such that the reference field needs a full module path, but for subschemas we don't have this luxury because the "name" field of plugins needs to be backwards-compatible.
Unless you are proposing that we load every plugin beforehand, including their config schemas and eventual custom DAOs, and store them all in the same flat/single namespace. I think keeping these namespaces separate is less prone to conflict.
For example, one possible (far off) future application of subschemas would be in a redesign of the Upstream entity into a more general Balancer entity where instead of a bunch of fields for hashing method, where we need to add fields each time we add a new method (e.g. hash_on_cookie), we could have a Balancer.config field and implement kong.runloop.balancer.methods.?.schema without worrying if there's another plugin called cookie out there when you create a cookie hashing method. (Of course one could fall into the age-old "but then let's create a convention that every X is prefixed by Y" which is always true for single-namespace propositions, but namespaces exist for a reason. :) )

Similarly, I don't think the abstract field abstraction is needed. It seems to me that the only reason to have them is to raise an error if someone wants to instantiate a Plugin without the correct subschema. But in that case we can still raise an error by detecting that the subschema_key doesn't correspond with any of the loaded subschemas.

The reason it is there is so that the parent schema alone can used to produce the DDL stuff for creating the database table in the strategy, without knowledge of the concrete ones, and for forcing certain fields to be specialized (config, in Plugins case).

@kikito I pushed a fixup commit (to be squashed when merged), based on the feedback you gave me today. It removes the subschema_module property, making the (pre-)loading of subschemas a separate concern from the schema library itself.
I think it reaches a nice middle-ground between the various approaches we suggested. Let me know what you think!


Where is the option in Azure portal

The page descibes you can set cutomerrors on global level  and/or listener level. But it is not vclear where the option in the Azure portal is located for global level.

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

ID: 8876a502-81db-4ef1-9e22-ebff4a63cabe
Version Independent ID: c9676383-40c2-44fc-2d26-ef571466712f
Content: Create Azure Application Gateway custom error pages
Content Source: articles/application-gateway/custom-error.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@owingruters , Thank you for your feedback. We will investigate and get back to you shortly.

It is mentioned in the Note section that global config of the custom error is not supported in portal today.

@owingruters , Do you have any update on this issue?

@owingruters , Tag me if you have any further questions.


androidx support please

For jetpack, this library can not be used if I use androidx namespace.

@XinyueZ can you explain the error you're getting and how to reproduce it?

@samtstern
I have a project with androidx namespace which is from jetpack,
i.e.
androidx.appcompat.app.AppCompatActivity
androidx.appcompat.app.Fragment
....

however, the library is using android.support.v4.app.Fragment etc which is not awesome.
Actually, I can not use this library for jetpack project.
Can the library starts snapshot for Jetpack, androidx namespace?

@XinyueZ We can't do that until everyone has migrated. In the meantime, enable the Jetifier:

OK thanks, I close the ticket just for info of your side.

Thanks @XinyueZ and @SUPERCILEX for resolving this!

Just a minor question related to this, I decided to switch to AndroidX. In the UI of Android Studio I do see the following errors:

The error says cannot resolve method (due to the fact that the method now receives a androidx.fragment.app.Fragment). Compilation works fine (using the Jetifier method). Is it normal that the UI shows these errors, or do I miss something?

Are you using Android Studio 3.2?

@SUPERCILEX, yes, I'm using 3.2 RC2, but nevermind: the error seems to have disappeared today. This could be related to a new version of the SDK Platform tools (28.0.1) which I installed today.

If anyone has problem with easypermissions on Jetpack or under androidx namespace,
I've converted easypermissions to support Jetpack which has androidx namespace
http://tinyurl.com/y7qb2rr7
This is a workaround to mirror origin project, it won't be supported for any bug fixing etc, it is only for androidx namespace.
implementation "com.github.xinyuez:easypermissions:1.3.0"


dump api is missing from the latest version

Sorry, I'll keep the dump function on hold until there's a clear demand for TOML output.


neonvm-controller: Add '--skip-update-validation-for'

Copying the second commit's message:

This flag is a new escape hatch to allow arbitrary updates to an object, bypassing the webhook update validation (but still within the CRD).
Sometimes when trialing things on staging, we end up with objects in a bad state that can't be deleted because update validation fails when removing the finalizer (e.g., due to destructive CRD changes).

This PR comes in two parts:

Refactoring — moving webhook setup in to the controller, so that it's easier to control from there
Feature — adding the --skip-update-validation-for flag to neonvm-controller, and using our newfound control over webhooks to skip the update webhook for objects named with the flag.

Probably worth merging via rebase-and-merge.

Does kubectl apply --validate=false do something different? From the man:
    --validate='strict':
	Must be one of: strict (or true), warn, ignore (or false). 	"true" or "strict" will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not. 		"warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. 		"false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields

I think it would be much more convenient to have a bypass method always-on.

I didn't know about kubectl apply --validate=false, but the main benefit I was thinking of here was allowing neonvm-controller to make changes without validation. Specifically because:

Sometimes when trialing things on staging, we end up with objects in a bad state that can't be deleted because update validation fails when removing the finalizer (e.g., due to destructive CRD changes).

Could you elaborate on what you mean by

I think it would be much more convenient to have a bypass method always-on.

?


feat: add zig runner

I couldn't quite figure out your test environment. Would one of the maintainers allow the pipeline to run?
I don't have much motivation for maintaining this code in the long run (however trivial it may be). I have it in my local configs already, and it's working there. However, I figured I would share the code in case someone else can benefit from it.


Zephyr message queue: add LIFO operation

Most RTOSes support both FIFO and LIFO operations for the message queues. For example, ThreadX has: tx_queue_send() and tx_queue_front_send(). EmbOS has: OS_PutMailCond() and OS_PutMailFrontCond(). Currently, Zephyr has only k_msgq_put().
This feature request is for adding k_msgq_put_front(), for LIFO operation.

The feature request is still relevant. I'm not sure what kind of additional information is needed, as the request is straightforward and the feature is already supported by most other RTOS kernels. A compelling use case for the LIFO policy for message queues is the self-posting of messages. Typically, a thread that posts a message to self is in a certain state and is ill-prepared to handle other messages (ahead of the self-posted one) because these other messages might change the internal state. This is very common for deferring messages, for example.

Am I missing something?  k_lifo/k_fifo are special cases of k_queue, which does indeed support operations at both ends of the list.   Closing; please reopen if the k_queue_append/prepend/remove() APIs don't meet the requirements here.

Oh, never mind.  Reopen.  The comment above used the words LIFO and FIFO, but it was actually talking about the k_msgq API, not queues.

This feature request is about supporting both message-posting policies (FIFO and LIFO) in the same RTOS primitive (message queue). If I understand correctly, the k_lifo RTOS primitive is a different than k_fifo, which is NOT what I mean.
If it would be helpful, my feature request for the Zephyr message queue corresponds to the two policies supported by the FreeRTOS queue. These policies are documented as xQueueSendToBack() and xQueueSendToFront(). I hope that this clarifies the requested semantics.


Can't connect to MongoDB

The connection to mongodb fails, using vapor 4, the fluent-mongo-driver and the connection string
mongodb://UserAdmin:ABCDEF@localhost:27017/admin
Following error is produced in MongoKitten:
[ ERROR ] Connection to Host(hostname: "localhost", port: 27017) disconnected with error MongoGenericErrorReply(ok: 0, errorMessage: Optional("BSON field 'saslContinue.conversationId' is the wrong type 'long', expected type 'int'"), code: Optional(14), codeName: Optional("TypeMismatch"))
The connection works using e.g. MongoDB Compass. I tried as mechanisms SCRAM-SHA-1, SCRAM-SHA-256 and auto. If I disable the authorization the connection works.
The mongodb user account looks as follows:
[ { _id: 'admin.UserAdmin',
userId: UUID("5f48a642-221b-4399-bfe5-2524587d7d5a"),
user: 'UserAdmin',
db: 'admin',
roles:
[ { role: 'readWriteAnyDatabase', db: 'admin' },
{ role: 'userAdminAnyDatabase', db: 'admin' } ],
mechanisms: [ 'SCRAM-SHA-1', 'SCRAM-SHA-256' ] } ]
Environment:

macOS
mongodb community: 5.0
MongoKitten Version: 6.x up to 6.6.7

Thanks for the heads up! This is a super simple fix, but I'm surprised they changed the SASL mechanism in this way.

Can you try the latest master branch

I haven't updated my environments just yet, as I just had a vacation. I'll be able to better evaluate this once I'm all updated.

I checked it against the master/6.0 branch and it seems fixed!
However, the first connection takes about 10-15 seconds - is that expected behavior.
This was the fastest response and fix ever - Thank you!

@jjabo You're welcome! On DEBUG mode, the password hashing used to authenticate to MongoDB is unfortunately quite slow. Swift is extremely unoptimised in DEBUG compilation. You'll notice a significant performance improvement on RELEASE builds, which is what production must always be compiled on. The credential proof is only computed once, and cached after that. However, inbetween launches this cache is lost.  If you're interested in that, please poke me on Discord :)

Thanks again. That is super helpful info and advice! :)
Looking forward to the next tag/release including the bugfix.

Tagged!


Add logging to the assembler

It may be good to add some basic logging functionality to the assembler. We could use log crate for this similar to how we do it in miden-vm crate. When logging is enabled, we'd be able to see extra output from the assembler and we'd also be able to report warnings (for something like #515).
We can start out with some minimal logging at first - e.g., log when a new module is being compiled (and maybe a coupe of other things) - and then we can expand this later on.

@bobbinth Do we want to allow user to decide what level of logging to use?
Currently in prove CLI command implementation we use hardcoded debug level, so usage of the debug!("..."), warn!("...") and error!("...") macro instructions is equivalent to the usage of the standard println!().
We can remove this restriction, so logging level can be specified with RUST_LOG environment variable on the VM execution stage:
$ RUST_LOG=debug target/optimized/miden run -i example.inputs -a example.masm

Disadvantage of this approach is that by default (if we don't specify the RUST_LOG variable) logging level is set to error!, so only error messages will be displayed.
I can extend the CLI to be able to specify the logging level environment variable with new feature (something like --log), in that case we can provide the user with the ability to specify the logging level, but at the same time the default level can be set to  "debug".

A couple thoughts:

Allowing the user to specify logging level is a good idea. I think it is OK to do it via an environment variable - but I wonder we should use a more custom name (e.g., MIDEN_LOG). Scanning through the docs of env_logger, seems like it should be possible.
We should probably enable logging for all commands. Maybe move logger initialization here?.
I think we should set the default log level to warn. If users want to see more, they could enable lower levels manually.

Closed by #1139.


http2: more cleanup in preparation for removing nghttp2 callbacks

This PR removes a few references to the nghttp2_frame type in codec API methods.
Commit Message: http2: more cleanup in preparation for removing nghttp2 callbacks
Additional Description:
Risk Level: low; refactoring, no functional change intended
Testing: ran unit and integration tests locally
Docs Changes:
Release Notes:
Platform Specific Features:

/assign @diannahu
/assign @RyanTheOptimist

Sorry, had to run the format fix script.

I think this needs a final approval by a committer.

I think this needs a final approval by a committer.

sigh I enabled auto-merge but I guess I didn't re-approve. Done,


Recover PR build setup.

Terms

THIS SOFTWARE IS CONTRIBUTED SUBJECT TO THE TERMS OF THE TERMS OF THE CCLA DATED 2017-11-07 WITH FINOS/LINUX FOUNDATION (FORMERLY THE SYMPHONY SOFTWARE FOUNDATION CCLA).
  THIS SOFTWARE MAY BE REDISTRIBUTED TO OTHERS ONLY BY EFFECTIVELY USING THIS OR ANOTHER EQUIVALENT DISCLAIMER IN ADDITION TO ANY OTHER REQUIRED LICENSE TERMS.

Closing because it's a duplicate of #1176


Add page finishing function when over scrolled to SessionDetailActivity

Issue

https://github.com/DroidKaigi/conference-app-2017/issues/228

Overview (Required)

Finish SessionDetailActivity when page overscrolled

Links

none

Screenshot

Before
After

Cool 🆒

Interesting implementation 👀
I thought it's better to make custom activity, but your custom CoordinatorLayout also looks good and reasonable. Let me taste this on my device after CI success 👍

Sorry to be late review 🙇
I checked on my device. It's really awesome! Thank you so much 👍
LGTM! 💯

Thank you for your review!! 😄

Oops, I didn't notice this PR was merged 😇

I'd like to make another PR to fix your commet! 👍

@jmatsu Thanks for great review 😄
@chibatching Appreciate you. Looking forward to next PR 👍