Endogenous shocks

Continuing from here

Further, I do not see any technical reason to structure things in such a way that there can only be one draw of shocks per period.

As far as I know, this suggestion amounts to a new feature request, as there's nothing in HARK that supports this kind of model yet.

This is completely possible in current HARK.  You had some prior exchanges with Matt about the fact that the current structure allows arbitrary variation in the "solve_one_period" method from one period to the next.  That means that any aspect of the problem -- including shocks -- can be different.  The user just has to hand craft the solve_one_period sequence accordingly.

We are talking about the structure of a new architecture, so it's not really right to think about it as a "new feature request."  It's about designing the new architecture in a flexible way that permits users to do what they want.

There are a number of different ideas here. Trying to tease them out:

In all other models, (and currently all the models in Dolo, I believe), all shocks are exogenous shocks, meaning that they do not depend on any agent's control decision. I believe Dolo exploits this technically by computing the exogenous shocks separately from the agent's behavior.  You seem to be describing an endogenous shock, where a random variable depends on an agent's decision.

Well, the shock itself can be conceived of as occurring whether or not the agent exposes themselves to it.  It's like "do I invest in stocks?"  The point is that if I do NOT have any stock investments, then I don't have to do the expensive numerical integration across all the possible realizations of the rate of return on stocks.  The stock market still exists, and has its exogenous shock, it just doesn't affect me.

I see two separate questions here which it is tempting to conflate into one:

What is the right way to model this kind of situation?
What is the most efficient way to implement the simulation and solution code for this kind of situation?

In my view, it's important to answer the first question before the second because "premature optimization is the root of all evil".

Agreed.  The only potential argument I know of for restricting the shocks to occur only at one stage is that it might be faster -- that counts as "premature optimization" and could result in considerable evil.

Addressing the first question (how to model this?), I would propose:

Consider stochastic draws to be a subtype of transition equation
Model an endogenous shock as a sample from a conditional probability distribution, where the preceding model state and controls variables are conditions on the right hand side of the equation.

Agreed.

TLDR: You actually do want to precompute the shocks for all possible
choices that all agents could make, and it's not that computationally
burdensome.
In an estimation setting, shocks should always be precomputed and "locked
in" to avoid oddities in the objective function from variation in the RNG.
Suppose we're trying to estimate some model parameters by minimizing
objective function f on parameters theta (many parameters, let's say). To
have any hope of minimizing f numerically, we want it to be continuous and
smooth, so that our optimization method can identify "which way is down".
Jags and bumps are bad, but they're inevitable in any model with discrete
outcomes that are endogenous.
To see this, consider a tiny epsilon change in one parameter that has very
tiny (marginal) effects on the policy functions, but this small difference
is enough to cause one simulated agent (out of 100,000, say) discretely
change their behavior in period t=3 (say, from going to school to instead
entering the labor market). This agent's entire history after t=3 will
now be discretely different, as they'll have one less period of schooling
and one more period of labor experience. This is guaranteed to produce a
small discontinuity in the objective function... and there are many of
those.
That discontinuity will be small, but consider what would happen if instead
of changing only the behavior of that agent at this discontinuity, we
instead changed the behavior of all of the agents. This would happen if
you didn't pre-specify all the possible shocks that each agent could get
in each period. Suppose there was a set of "grade shocks" and a set of
"wage shocks"; agents in school get grade shocks, agents in the labor
market get grade shocks. If the code were set up so that it checked how
many agents are in school and drew grade shocks for them, then checked how
many agents are in the labor market and drew wage shocks for them, then
one agent switching from school to labor would change these numbers, and
the shocks assigned to all other agents would be offset by one.
It saves a lot of difficulty and complications later (and makes the
objective function much smoother) if all possible shocks are pre-drawn at
the very beginning, and then we grab the ones that are actually necessary
as simulation happens.
On Tue, Apr 6, 2021 at 10:25 AM Sebastian Benthall @.***>
wrote:

Continuing from here
https://github.com/econ-ark/HARK/issues/620#issuecomment-813603497
Further, I do not see any technical reason to structure things in such a
way that there can only be one draw of shocks per period. Maybe a good
technical case for this exists and I'm missing it, but if, for example, one
of the decisions that a person makes in the period is whether or not to
take some risk, or which of several kinds of risks to take, it would be
wasteful to precompute shock distributions for all possible choices if the
person might not actually make them.
As far as I know, this suggestion amounts to a new feature request, as
there's nothing in HARK that supports this kind of model yet.
There are a number of different ideas here. Trying to tease them out:
In all other models, (and currently all the models in Dolo, I believe),
all shocks are exogenous shocks, meaning that they do not depend on any
agent's control decision. I believe Dolo exploits this technically by
computing the exogenous shocks separately from the agent's behavior.
You seem to be describing an endogenous shock, where a random variable
depends on an agent's decision.
I see two separate questions here which it is tempting to conflate into
one:

What is the right way to model this kind of situation?
What is the most efficient way to implement the simulation and
solution code for this kind of situation?

In my view, it's important to answer the first question before the second
because "premature optimization is the root of all evil".
Addressing the first question (how to model this?), I would propose:

Consider stochastic draws to be a subtype of transition equation
Model an endogenous shock as a sample from a conditional probability
distribution, where the preceding model state and controls variables are
conditions on the right hand side of the equation.

It may be that the mostly closely analogous existing model in HARK is the
ConsMarkovModel. See issue #956
https://github.com/econ-ark/HARK/issues/956 for a proposal about
encapsulating the dependency of income shock shocks on a Markov process
with a conditional probability distribution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/996, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFOYA3PRYV7LI7W5ZU3THMKXPANCNFSM42O3DRAA
.

@llorracc I see that you've responded to my issue by editing my original post with your responses inline.
That's quite odd. Now it looks like I'm arguing with myself.

arbitrary variation in the "solve_one_period" method from one period to the next. That means that any aspect of the problem -- including shocks -- can be different. The user just has to hand craft the solve_one_period sequence accordingly.

It is certainly always possible to hand craft something that does exactly what you want it to do.
But if you need to hand craft something to make it happen, it's not quite accurate to say that the current HARK code supports the functionality.

2. We are talking about the structure of a new architecture, so it's not really right to think about it as a "new feature request."  It's about designing the new architecture in a flexible way that permits users to do what they want.

I don't know how to address this.
I'm talking about new features to an existing software library, or ways to refactor it.
Are you suggesting a complete, new rewrite of HARK? Like a HARK 2.0?
I would be happy to assign this ticket to the HARK 2-onward milestone, though I think there are interesting ways to do endogenous shocks with less ambitious changes.

The stock market still exists, and has its exogenous shock, it just doesn't affect me.

If the shock is truly exogenous, then for the reasons Matt's mentioned among others, I don't think it hurts much to sample it in forward simulation.
I understand that you are mainly interested in how to write solvers though.
I guess I would need to see a specific problem to understand whether and how the numerical integration costs could be reduced.

The only potential argument I know of for restricting the shocks to occur only at one stage is that it might be faster -- that counts as "premature optimization" and could result in considerable evil.

I don't really understand what you're arguing for, sorry.
If the shocks are exogenous, then I suppose they could show up at any stage in which they were prior to a control that depends on them.
But are you saying that the same shock should be drawn potentially multiple times during the same period?
I think that way of abstracting out the problem creates more problems than it solves. Alternatively, one could:

introduce more shock variables, sampled once.
have the random distribution of the shock variable create all the information needed by the multiple draws.

I felt like these tables laying out model variables and their relationships via equations were great for establishing common understanding of terminology:
https://github.com/econ-ark/HARK/issues/991#issuecomment-812644798
But what you've been suggesting since seems to be rejecting that attempt to systematize the problem. Why is that?

On Tue, Apr 6, 2021 at 3:55 PM Sebastian Benthall @.***>
wrote:

@llorracc https://github.com/llorracc I see that you've responded to my
issue by editing my original post with your responses inline.
That's quite odd. Now it looks like I'm arguing with myself.

Oops, I was trying to copy and paste your text and respond as in email.

arbitrary variation in the "solve_one_period" method from one
period to the next. That means that any aspect of the problem -- including
shocks -- can be different. The user just has to hand craft the
solve_one_period sequence accordingly.

It is certainly always possible to hand craft something that does exactly
what you want it to do.
But if you need to hand craft something to make it happen, it's not quite
accurate to say that the current HARK code supports the functionality.

That's not really right.  The whole scheme of HARK is to say "there's
really only ONE thing that needs to be handcrafted for every model: the
solve_one_period method.  The rest of HARK is the infrastructure that takes
care of all the rest of the housekeeping of Bellman problems and lets you
concentrate all of your attention as a modeler on the core of your
mathematical problem, which is handcrafting your solve_one_period setup."

We are talking about the structure of a new architecture, so it's not
really right to think about it as a "new feature request." It's about
designing the new architecture in a flexible way that permits users to do
what they want.

I don't know how to address this.
I'm talking about new features to an existing software library, or ways to
refactor it.
Are you suggesting a complete, new rewrite of HARK? Like a HARK 2.0?
I would be happy to assign this ticket to the HARK 2-onward milestone,
though I think there are interesting ways to do endogenous shocks with less
ambitious changes.
The stock market still exists, and has its exogenous shock, it just
doesn't affect me.
If the shock is truly exogenous, then for the reasons Matt's mentioned
among others, I don't think it hurts much to sample it in forward simulation

I understand that you are mainly interested in how to write solvers though.

Right.  I was mostly talking about solvers.

I guess I would need to see a specific problem to understand whether and
how the numerical integration costs could be reduced.
The only potential argument I know of for restricting the shocks to occur
only at one stage is that it might be faster -- that counts as "premature
optimization" and could result in considerable evil.
I don't really understand what you're arguing for, sorry.
If the shocks are exogenous, then I suppose they could show up at any
stage in which they were prior to a control that depends on them.

Right.

But are you saying that the same shock should be drawn potentially
multiple times during the same period?

No.

I think that way of abstracting out the problem creates more problems than
it solves. Alternatively, one could:

introduce more shock variables, sampled once.
have the random distribution of the shock variable create all the
information needed by the multiple draws.

I felt like these tables laying out model variables and their
relationships via equations were great for establishing common
understanding of terminology:
#991 (comment)
https://github.com/econ-ark/HARK/issues/991#issuecomment-812644798
But what you've been suggesting since seems to be rejecting that attempt
to systematize the problem. Why is that?

I'm happy with that table as a description of that particular problem,
which happens to be one in which the shocks are all (in sequence) at the
beginning.  But nothing about the table specifies that we ought to impose a
restriction that shocks must always happen at the beginning.  For the
forward simulation part of things there may be reasons for executing the
simulation that way, but I can't see a reason to impose it as a
requirement.  Indeed, it seems to me that it would complicate our lives
considerably to impose it.
Somehow I feel that there is some way in which we are talking past each
other.  Maybe if you could articulate a reason why you think it would be
useful to require problems to be structured in such a way that all shocks
must be realized before any other steps, that would help me pinpoint what
our communication difficulty might be.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/996#issuecomment-814398407, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKCK74IP4NXBXCFR52AARTTHNRJTANCNFSM42O3DRAA
.

--

Chris Carroll

Somehow I feel that there is some way in which we are talking past each other. Maybe if you could articulate a reason why you think it would be useful to require problems to be structured in such a way that all shocks must be realized before any other steps, that would help me pinpoint what our communication difficulty might be.

Ah, indeed we are talking past each other. I don't think it is useful to require problems to be structured in such a way that all shocks must be realized before other steps. I apologize for the confusion.
I think a point we agree on is that: for each shock variable, it will be drawn at most once per period, somewhere in the period.
I see now that we have been "in violent agreement", each misinterpreting the other as being opposed to this point of agreement.
I'll close this ticket now.

That's not really right.  The whole scheme of HARK is to say "there's
really only ONE thing that needs to be handcrafted for every model: the
solve_one_period method.  The rest of HARK is the infrastructure that takes
care of all the rest of the housekeeping of Bellman problems and lets you
concentrate all of your attention as a modeler on the core of your
mathematical problem, which is handcrafting your solve_one_period setup."

This discussion is a bit philosophical now, and out of scope for the ticket....
But where I think we agree is that it would be even better if HARK supported model building in configuration the way Dolo does it, which is by letting the modeler define a solution in terms of known algorithms with a clearly defined Bellman form equation, or something carrying comparable information.


Rear Bodywork

Modelling

[x] Rr WIng of 2 pcs
[x] Rr Wing of 2 pcs - Main Plane x1.25 Larger
[x] Rr Wing of 1 pc - 50mm Higher
[ ] Diffuser for Xtrac P1227 Gearbox

[x] Base Surface
[ ] Bulge, Gearbox

[ ] Bonnet Duct
[x] Higher Side Mirrors
[ ] Smaller Side Mirrors
[ ] Side Mirrors on Side Pods
[ ] Side Mirrors -less - Side View Cameras
[ ] Rr Fender Stay
[ ] Rr Bumper B

In the case of "Side Mirror-less", are there enough spaces for side view monitors on a dashboard?

CFD of Rear Bodywork : See #31

Head Rest 〜 Rr Bonnet に掛けての 凸凸 をシュッとさせた．

デザイン上の修正 / Fixing Design issues
絞込角度を緩くして低ドラッグ化しないか期待 / Expecting to reduce the drug by narrowing down the shape


[Chore] Update Prometheus

Changes

Update Prometheus to https://github.com/prometheus/prometheus/commit/efbd6e41c59ec8d6b7a0791c1fb337fdac53b4f2

We pinned github.com/sercand/kuberesolver/v4 => github.com/sercand/kuberesolver/v5 v5.1.1 in order to be able to update google.golang.org/grpc needed by opentelemetry-go (and consequently removed the replace for google.golang.org/grpc)
Breaking Changes on Prometheus

The interface chunkenc.Chunk added a Reset method that needed to be implemented by the structs on thanos.
Needed to make thanos use the jsoniter due:

https://github.com/prometheus/prometheus/pull/13993
https://github.com/prometheus/prometheus/pull/13997

Pinned prometheus/common for now as we need: https://github.com/prometheus/common/pull/653

Verification
Breaking Changes on the new go-grpc:

From here FailOnNonTempDialError, WithBlock, and WithReturnConnectionError are three DialOptions that are only supported by Dial because they only affect the behavior of Dial itself. WithBlock causes Dial to wait until the ClientConn reports its State as connectivity.Connected. The other two deal with returning connection errors before the timeout (WithTimeout or on the context when using DialContext).

Those options were added to work around an regression on GRPC: see this and this

@alanprot OK I just checked and I think the E2E test failure is related. The test tries to spin up a Prometheus locally using Prometheus binary.
I logged the command in my local path.
prometheus --storage.tsdb.retention=2d --storage.tsdb.path=/var/folders/rd/vh0cfrk13jsf8pnnqgz9yrg40000gr/T/prometheus-test3289092244 --web.listen-address=localhost:54196 --web.route-prefix= --web.enable-admin-api --config.file=/var/folders/rd/vh0cfrk13jsf8pnnqgz9yrg40000gr/T/prometheus-test3289092244/prometheus.yml

And it failed with error below.
ts=2024-06-05T06:07:29.433Z caller=main.go:521 level=error msg="Error loading config (--config.file=/var/folders/rd/vh0cfrk13jsf8pnnqgz9yrg40000gr/T/prometheus-test3289092244/prometheus.yml)" file=/var/folders/rd/vh0cfrk13jsf8pnnqgz9yrg40000gr/T/prometheus-test3289092244/prometheus.yml err="parsing YAML file /var/folders/rd/vh0cfrk13jsf8pnnqgz9yrg40000gr/T/prometheus-test3289092244/prometheus.yml: yaml: unmarshal errors:\n  line 2: field rule_query_offset not found in type config.plain"

The config is:
global:
    rule_query_offset: 0s
    external_labels:
        az: "1"
        region: eu-west

rule_query_offset is a new config and it doesn't have omit_empty so it makes old Prometheus version fail. https://github.com/prometheus/prometheus/blob/main/config/config.go#L402

Let's update Prometheus version to prometheus/prometheus#14216 and see if it fixes it?

Will do.. but i think there is another braking change that we will need to PR on prometheus.. I will push the change with the new prometheus for now but the build will fail.

=== NAME  TestRangeQueryShardingWithRandomData
    testutil.go:91: query_frontend_test.go:667: ""

        	exp: model.Matrix(nil)

        	got: model.Matrix{}

        Diff

Seems related to: https://github.com/prometheus/prometheus/pull/13993
=/
Need to understand why.

Ok..
We are not using jsoniter to serialize response as the upstream prometheus is... it explains why the null is being serialized as null as the fix for https://github.com/prometheus/prometheus/pull/13993 was actually done https://github.com/prometheus/prometheus/pull/13997 and it was a fix on the json serializer...
I'm changing thanos to use jsoniter as it has multiple benefits anyway.

@GiedriusS @fpetkovski Can you guys take a peek on this one?

We are seeing problems with grpc 1.64.0: https://github.com/grpc/grpc-go/issues/7314. The issue in Thanos happens when we try to close stale connections here: https://github.com/thanos-io/thanos/blob/main/pkg/query/endpointset.go#L442.
Maybe it's better to pin grpc to 1.63.2?

We are seeing problems with grpc 1.64.0: grpc/grpc-go#7314. The issue in Thanos happens when we try to close stale connections here: https://github.com/thanos-io/thanos/blob/main/pkg/query/endpointset.go#L442.
Maybe it's better to pin grpc to 1.63.2?

Ok.. lemme do this.


Update variable name in rake task to clarify error message

It looks like when this method was refactored this message variable name was missed.
This should correct the exception raised from:
NameError: undefined local variable or method 'handle' for Verdict::Rake:Module to a more informative Experiment 'experiment_that_doesnt_exist' not found exception
Readme says to ping @wvanbergen

I really should take that line out of the README ;)


Bug Report: NSG Flow Logs policy not assigned

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: latest
azure provider: latest
module: v3.1.0
Description
Describe the bug

The deprecation warning in the ES module mentions the deprecation of the NSG Flow Logs policy in favor of a built-in one: https://github.com/Azure/Enterprise-Scale/blob/main/docs/wiki/ALZ-Deprecated-Services.md#deprecated-policies. It seems this one was deprecated in this module as well, but the built-in policy was never assigned: https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/blob/e6da921369d90aa38bd2ece1dfb8e81f55cf8cfe/docs/wiki/[User-Guide]-Upgrade-from-v2.4.1-to-v3.0.0.md#resource-type-azurerm_policy_definition
Should this policy be assigned?
Steps to Reproduce

Deploy the Enterprise Scale environment
Check the built-in NSG flow log policy.
Confirm the built-in policy doesn't have any assignments.

Screenshots

Additional context

Hey @DevSecNinja,
This policy was never assigned. We just provided it as a definition as it didn't exist as a built in. We are currently reviewing the default ALZ policy assignments, but we are not going to add this one at this time as it can increase costs considerably for customers with additional logging.

Thanks for your reply @jtracey93! Understood, but shouldn't it be assigned considering that it's a best practice in the Azure Review checklist?
Enable NSG flow logs and feed them into Traffic Analytics to gain insights into internal and external traffic flows.
In my opinion, we shouldn't exclude features because they could potentially increase costs. Services like DDoS Protection, Azure Firewall and Sentinel can also cause cost increases. Enabling NSG Flow logs by default is definitely a topic for a discussion and I would agree that it's up to discretion of the user to enable it.
Considering it's part of the Azure Review checklist, could we give this one a spot on the roadmap?
Thanks.

Hey @DevSecNinja,
I hear you. The checklist is currently being updated.
We will consider it in the current round of policy updates again, and it is also on the roadmap under some work we are tracking with the PG for flow log enhancements and network watcher 👍

Thanks, appreciate it @jtracey93!


keplr/arabica-9: tx send is failing

Summary of Bug
We can't send a simple tx in arabica-9 through keplr.
What is the base fee? It seems like the keplr's fee is not suited I suppose
Version
v1.0.0-rc7
Steps to Reproduce

Connect through keplr wallet to arabica-9 chain
Fund account in faucet
Send a sample tx from keplr account
Select highest fee (4443 utia)
Confirm TX

{
  "account_number": "4033",
  "chain_id": "arabica-9",
  "fee": {
    "gas": "111062",
    "amount": [
      {
        "amount": "4443",
        "denom": "utia"
      }
    ]
  },
  "memo": "",
  "msgs": [
    {
      "type": "cosmos-sdk/MsgSend",
      "value": {
        "amount": [
          {
            "amount": "1000000",
            "denom": "utia"
          }
        ],
        "from_address": "celestia1uglava8p4fxefvtejtnuwvyfvd2plcd8jj2nws",
        "to_address": "celestia145ghvz4hnytqz8utu4jwthsmedhrg42f0hsq0e"
      }
    }
  ],
  "sequence": "0"
}

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Some screenshot of the fees option in Keplr for arabica-9 chain

Re: https://github.com/celestiaorg/docs/pull/882

walkthrough of adding arabica-9 as experimental from our docs, then bug sending tx
https://loom.com/share/b0995a40c337499c962b9493fdacf833?sid=4df11b5a-2d9a-4ae9-a55c-cc920a154103

I can't find in keplr api docs how to change fees. @jcstein do you have any ideas how we adapt them to 11k at least which @cmwaters has mentioned above?

Yes, I would suggest the following:
gasPriceStep: {
     low: 0.1,
     average: 0.2,
     high: 0.4,
},

It's essentially just one magnitude more than the current gas prices

Are we able to mark this as resolved now @Bidon15 @jcstein ?

gm @cmwaters - yep. just merged PR to update docs 🫡


chore: pin dependencies

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Error: foreign key constraints are not allowed

Hi, I receive this error after terminal cmd npx prisma db push
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "parrocchia" at "aws.connect.psdb.cloud"
Error: foreign key constraints are not allowed, see https://vitess.io/blog/2021-06-15-online-ddl-why-no-fk/
   0: sql_schema_connector::apply_migration::migration_step
           with step=AddForeignKey { foreign_key_id: ForeignKeyId(0) }
             at schema-engine/connectors/sql-schema-connector/src/apply_migration.rs:21
   1: sql_schema_connector::apply_migration::apply_migration
             at schema-engine/connectors/sql-schema-connector/src/apply_migration.rs:10
   2: schema_core::state::SchemaPush
             at schema-engine/core/src/state.rs:441

Same, any fix?

PlanetScale MySQL db doesn't support foreign keys.
https://planetscale.com/docs/learn/operating-without-foreign-key-constraints

There is no fix. PlanetScale MySQL doesn't support foreign keys. Just create a tables and keep the name of both the keys same the primary key of the referenced table and the foreign key of the referencing table and do not add foreign key constrain while creating a table
For more information refer this link : (https://github.com/Darshan1904/Bookshelf/blob/master/seed/sql.js)

More info on foreign key constraints (or lack of) on planetscale's mysql video course:
https://planetscale.com/courses/mysql-for-developers/indexes/foreign-keys

Remove the relations from your schema and or use this command if not in prod npx prisma db push --preview-feature


Improve the UI for image captions

Ref: https://github.com/bigbinary/neeto-kb-web/issues/4510

[x] Reduce the font size of the caption to 13px.
[x] Change the font color of the caption to neeto-ui-gray-500.

@gaagul _a
cc: @praveen-murali-ind let us know if this is looks good to you.

This looks great. 😍

@AbhayVAshokan Looks good to me 👍


ci: switch from hosted to local DB

resolves #146

Tell me if you need me to set up any secrets or environment variables in out GitHub Actions environments.

Tell me if you need me to set up any secrets or environment variables in out GitHub Actions environments.

It shall not be needed; otherwise, it won't be changed, right?
seems we would need to run MongoDB with docker so it can run on all OS so far the two actions I tried were limited to  Linux only :/

Tell me if you need me to set up any secrets or environment variables in out GitHub Actions environments.

It shall not be needed; otherwise, it won't be changed, right? seems we would need to run MongoDB with docker so it can run on all OS so far the two actions I tried were limited to Linux only :/

Right you are! Silly me...
Well, let see if you can work the kinks out...

Well, let see if you can work the kinks out...

@shaypal5 mind check t out, had to drop testing for DB on macOS as GH runners does not have reliable support for dockers yet and tested actions to add docker did not work well

Just rename CACHIER_TEST_VS_LIVE_MONGO like I've suggested.

ok, added it back such it works as a switch between local/test and live DB

@shaypal5 figured out the docker on Mac o it is a full matrix :flamingo:

@Borda
This cannot be rebased automatically from within GitHub, due to conflicts.
Please rebase manually and I'll squash and merge it.


Suddenly no longer working on 10.11.4

I'm getting the dreaded

You cannot use the Aerial screen saver with this version of OS X.
Please contact the vendor to get a newer version of the screen saver.

I'm not sure what changed; this was literally working this morning and I've not done any OS updates...

Nevermind! I thought I was up to date, but I'm not.

Hi @colindean if you're curious, here is why you got that message. It's a bug in OS X.
http://alistairmcmillan.github.io/2016/04/25/OSX-Swift-screensaver-bug.html

Interestingly enough, I hit this very same issue while messing around with starting another screensaver of my own. I wrote my own Bitcoin Price Screensaver in Objective-C in 2013 and wanted to do up something else just this past weekend. I don’t think I came across that same article, but another article said something like “if you get the dreaded ‘ask vendor for a new version’ message, it means you forgot to do ”. Thanks for the article, though, it was a good read.


Move molecule loading from Knime -> Python

Still hard-codes my directory structure, but it's getting there.

@greglandrum I made the changes we talked about.

@greglandrum I made those changes.

I think this now looks good and is ready for merge.


bug: no way to get kubectl plugins for kubestellar without downloading and extracting release tar file

Describe the bug
I am unable to use the curl-2-bash script with '--deploy false' to extract using the command.
bash <(curl -s https://raw.githubusercontent.com/kubestellar/kubestellar/release-0.7/bootstrap/bootstrap-kubestellar.sh) --kubestellar-version v0.7.0 --deploy false

I get a .kcp directory and no other files.
just as we run 'kubestellar-release' to find the version of the plugins, and just as we use 'get-external-config' to get the kubeconfig necessary to communicate with kubestellar's underlying platform, we should have 'get-plugins' to get the matching version of kubestellar kubectl plugins downloaded and in the proper path.  Perhaps this is a brew installation script.  Whatever it is, it should be standard and easy to use.  Maybe host the binaries in the kubestellar install and allow someone to simply curl them out of kubestellar itself.
Steps To Reproduce

run 'bash <(curl -s https://raw.githubusercontent.com/kubestellar/kubestellar/release-0.7/bootstrap/bootstrap-kubestellar.sh) --kubestellar-version v0.7.0 --deploy false'
list directory

output is .kcp and no other files.
Expected Behavior
I expect a simple way to get the right version of kubestellar kubectl plugins that match the version of the kubestellar server I am trying to communicate with in the kubeconfig.
Additional Context
No response

The current bootstrap script's deliberately designed behavior is to get you the executables that are not already on your path.  In some console session that you fortunately shared recently I noticed that the bootstrap script said that it was not adding executables because it found them already on your $PATH (under /opt/homebrew).  We could change the behavior of the bootstrap script.  @francostellari is the original author.

The current behavior of the bootstrap script is described in https://docs.kubestellar.io/main/Coding Milestones/PoC2023q1/commands/#bootstrap .  We deliberately chose to not put a full description of the bootstrap script in the quickstart, for the sake of keeping the quickstart short.  The user guide being started in #1042 references the quickstart but not the full doc for the bootstrap script; I think it would be appropriate to also point to the full doc for the bootstrap script.

closing this issue - focusing on #1051 instead.


IPFS on/off

IPFS on - every function is active.
IPFS off
nonactive:

upload/update/remove dapp by publisher
launch ipfs-related dapp which wasn't installed on the PC
update ipfs-related dapp

checked


Can not add payment method from ui

Firstly, thank you for open sourcing this amazing  saas start kit. We still not able to run latest API & UI ( V2 ? )together at this point, but would be able to run them together with API v1.0.0 & Ui v1.0.0.
Now facing this issue. Not able to add payment method via UI showed as screenshot. Look like it is something to do with API regarding organization endpoint?

I had it sorted... The API backend sending the credit card number directly to Stripe API, that's why showing 500 error. We need to use the token instead of the card number.

Thanks! If this is a bug not related to your use case but to Staart API, would you like to make a PR?

This issue is not relate to the bug of Staart API. In this case, Stripe recommended to wrap the customer payment details with Stripe Element and the new API rather than sending the raw credit card number directly to Stripe's API.  We will be working on the payment code to make it working smoothly, will submit a PR if we come across any. Thanks again for this amazing project.


Send_msg KeyError

I know it just got uploaded two second ago,  but wanted to let you know when trying to .send_msg I'm getting a key error on line 123 of client.py
msg.ts = e.event['ts']

I #'ed it out and the msg sent. doesn't give me a timestamp but at least it's not returning an error

Thanks @theguyoncouch; I can't seem to replicate the error -- can you post the error message here?

sc.send_msg('hello', '#connect4')
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.4/dist-packages/slacksocket/client.py",
line 123, in send_msg
msg.ts = e.event['ts']
KeyError: 'ts'

On Sat, Aug 8, 2015 at 7:07 PM, bradley<EMAIL_ADDRESS>wrote:

Thanks @theguyoncouch https://github.com/theguyoncouch; I can't seem to
replicate the error -- can you post the error message here?
—
Reply to this email directly or view it on GitHub
https://github.com/bcicen/slacksocket/issues/14#issuecomment-129076375.

--
Luis Cázares
Cell:<PHONE_NUMBER>

Thanks, I've pushed https://github.com/bcicen/slacksocket/commit/54620e51c2637ba140b719d4878627049f280f8f to correct this.


Error: connect ECONNREFUSED

Keep getting below error on connection, it connects some times and some time I keep getting this error
Please help
WebSocketClient: reconnecting...
WebSocketClient: retry in 5000ms { Error: connect ECONNREFUSED <IP_ADDRESS>:8080
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 8080 }

Same issue here!

Found the problem.
The Read Me config has the old Web Socket URL.
Change this in your config file:
"webSocketApi" : "us-ota.coolkit.cc"
to:
"webSocketApi" : "us-pconnect3.coolkit.cc"
As per this
https://github.com/gbro115/homebridge-ewelink/issues/16


[Suggestion] add a "Open Minecraft Bedrock Edition" button in because this was in the latest version of PS4 Edition.

Legacy4J Version
any version
Mod Loader Version
a
Bug/Glitch Occurrence Context
the command to actually do this is:
explorer.exe shell:appsFolder\Microsoft.MinecraftUWP_8wekyb3d8bbwe!App
i was able to do this on 1.20.6 using fancymenu, so it is possible:
https://github.com/user-attachments/assets/78b2635b-f36a-4198-84d4-19e2923cbfc4
Crash Report
No response
What happened wrong?
read the description

vouch

This will not be added, this is a button that exists only because LE was deprecated and was replaced by BE, I don't think anyone would like to remember that.
In addition to the fact that BE is only available for Windows (in the case of platforms that JE is available on)


VolumeUP/VolumeDown/Mute Buttons

Describe the bug
In my keyboard (Not Laptop) I have VolumeUP/VolumeDown/Mute Buttons
Working but when replacing to cairo shell it will not work.
By the way I love this project a lot.

Would you be so kind to provide some additional information?
System information:

Windows version:
Cairo version:
32-bit or 64-bit:
In Cairo Settings > Advanced, is Cairo set as shell?:

@josuave
-windows 10 21H1
-Cairo shell 0.4.198 Pre-release
-64 Bit
-Yes set as shell ... the shell caused the problem but when i turn it off the Volume buttons will be fixed

I also have an error that I assume is similar to this, the function volume up, down (Fn + F5-F7) and mute buttons do not work.

Windows version: Windows 10 21H2
Cairo version: <IP_ADDRESS>28
32-bit or 64-bit: x64
is Cairo set as shell?: Yes
I will add, the brightness ones do work, but there's no popup slider or anything.

I'm guessing this is already covered in #409 so there's no need for this issue.


local-up: generate bootstrap when joining a node

Is your feature request related to a problem? Please describe.
When running local-up node join --name foo a node and nodepool resource are created. However, the user does not know what bootstrap token to use. The default token "abcdefg.123..." is only valid 24 hours after cluster creation. The user might want to add nodes after that period.
Describe the solution you'd like
When running local-up node join a bootstrap token as an additional step and provided to the user.
Describe alternatives you've considered
Increasing the TTL of the default token means messing around in the kind internals. So not quite an alternative.
Additional context

fixed by #67


Simple code causes the ui no-response

Version: 1.52.0-insider (user setup)
Commit: 24b28f57be22fe3029cb17a1dd72d8d9c2d6468b
Date: 2020-11-06T05:43:01.017Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:

2.console.log('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'.repeat(5000))
3.I also tested on Linux a different version on VS code it also responded this

Does this issue occur when all extensions are disabled?: Yes/No

/assign @Tyriar
Looks like this issue is reproducible if
node -e "console.log('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'.repeat(5000))"

executed in cmd or powershell but has no problems with git-bash.

/duplicate https://github.com/microsoft/vscode/issues/100338


keyboardShouldPersisTaps={true} is deprecated, use keyboardShouldPersisTaps="always" instead

Getting the warning: "keyboardShouldPersisTaps={true} is deprecated, use keyboardShouldPersisTaps="always" instead"
react-native: "0.44.0"
react-native-modal-picker: "0.0.16"
Thanks a lot for this awesome plugin 👍

As I wrote in another issue, this issue has four open PRs (#32, #40, #49, #52) that all does the same thing: appends ="always" to the keyboardShouldPersistTaps-prop in ScrollView on line 134. It also exists numerous issues pointing out this problem.
But since this repo is no longer maintained, you are better of forking it yourself and applying the PR-s that looks good, or use one of the 119 forks that already exists (many of them have done good progress).

Thanks @mikaello for your reply! Using one of the updated forks now.

I would be better to allow the parent to pass the prop keyboardShouldPersistTaps to this component.  This would not only allow backward compatibility with older versions of RN, but also allow current RN users to choose the different values for keyboardShouldPersistTaps: always, handled, never.

PR #62  adds prop keyboardShouldPersistTaps to react-native-modal-picker.  It defaults to 'always' but allows the caller to override the prop in order to support any version of RN.
Until dan merges, you can use my fork with this commit:
  "dependencies": {
    "react-native-modal-picker": "https://github.com/peacechen/react-native-modal-picker#keyboardShouldPersistTaps_prop",
  },

That also includes PR #37

@peacechen Thanks, but using your PR throws me a warning from yarn: Warning: Installed version 0.0.16 of 'react-native-modal-picker' does not satisfy required version peacechen/react-native-modal-picker#keyboardShouldPersistTaps_prop
Do you know how to fix that?

@NhatAnh  you should be able to ignore that warning.  Looks like a problem with the parsing of the version from package.json if the url has a # to select a branch.
Someone else reported this on yarn:
https://github.com/yarnpkg/yarn/issues/3964

Thx for this issue, i was searching for a solution too. :)

You may want to try react-native-modal-selector which is the official continuation of this abandoned project.


Designated initializers compatability issue

Apparently, C style designated struct initialization exists in C++20 only... and yet somehow it still compiles in C++11 on Linux

Fixed in be34e7f873ec3da470298d8a4fd5380443cd4ec9


API: NaT/nan mixed input coerces to timedelta64

Code Sample, a copy-pastable example if possible
Index/Series results in datetime64 dtype if all inputs are pd.NaT.
pd.Index([pd.NaT, pd.NaT])
# DatetimeIndex(['NaT', 'NaT'], dtype='datetime64[ns]', freq=None)

pd.Series([pd.NaT, pd.NaT])
# 0   NaT
# 1   NaT
# dtype: datetime64[ns]

However, it coerces to timedelta64 if np.nan is included.
pd.Index([pd.NaT, np.nan])
# TimedeltaIndex([NaT, NaT], dtype='timedelta64[ns]', freq=None)

pd.Series([pd.NaT, np.nan])
# 0   NaT
# 1   NaT
# dtype: timedelta64[ns]

This looks to be caused by following internals:
pd.tslib.is_timestamp_array(np.array([pd.NaT, np.nan]))
# False
pd.lib.is_timedelta_array(np.array([pd.NaT, np.nan]))
# True

Expected Output
datetime64 dtype?
output of pd.show_versions()
on current master

tslib.is_timestamp_array looks totally out of place / is old, need to remove that and replace with routine from src/inference.pyx (which is where is_timedelta_array is defined, along with all other inference routines).
but your result should be the same (e.g. M8[ns])

OK. Also there is no tests to guarantee the behavior. Will submit a PR.

Found there are inconsistencies depending on the order. Is it OK that all these must be datetime64?
# OK
pd.Index([np.nan, pd.NaT])
# DatetimeIndex(['NaT', 'NaT'], dtype='datetime64[ns]', freq=None)

# NG, must be DatetimeIndex
pd.Index([pd.NaT, np.nan])
# TimedeltaIndex([NaT, NaT], dtype='timedelta64[ns]', freq=None)

# OK
pd.lib.infer_dtype([np.nan, pd.NaT])
# 'datetime64'

# NG, msut be 'datetime64'
pd.lib.infer_dtype([pd.NaT, np.nan])
# 'mixed'

Actually it is not simple than I initially thought. On current master, we don't distinguish datetime64/timedelta64 NaT. Thus below input is regarded as timedelta.
pd.lib.infer_dtype(np.array([np.datetime64('nat'), pd.Timedelta('1 day')]))
# 'timedelta'

However, if input is all nan/nat like, it is inferred using last element.
pd.lib.infer_dtype(np.array([np.datetime64('nat'), np.timedelta64('nat')], dtype=object))
# 'timedelta'

pd.lib.infer_dtype(np.array([np.timedelta64('nat'), np.datetime64('nat')], dtype=object))
# 'datetime64'

If we regard np.datetime/timedelta nat as the same as pd.NaT, the both results should be "datetime64". Otherwise, np.datetime/timedelta mixture should be infered as "mixed".

ahh I c. Since we have a single pd.NaT for both M8 and m8, I think we need to keep that all nan -> M8 if not-specified.


Unable to install on Windows 11

Another way to install?
Right-clicking and running Install-Layer.ps1 in Windows 11 gives an error

What is the error?
On Mon, 26 Dec 2022, 09:14 JIAN83157, @.***> wrote:

Another way to install?
Right-clicking and running Install-Layer.ps1 in Windows 11 gives an error
—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWN2PIQVR6YRNBUEEWAI5LWPFOWDANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sorry I can't translate into English here
Jabbah @.***>於 2022年12月26日 週一，下午7:34寫道：

What is the error?
On Mon, 26 Dec 2022, 09:14 JIAN83157, @.***> wrote:

Another way to install?
Right-clicking and running Install-Layer.ps1 in Windows 11 gives an error
—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAWN2PIQVR6YRNBUEEWAI5LWPFOWDANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2#issuecomment-1365110549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46NHSYBCLZD3MWOXP2YJMDWPF7CXANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have searched online how to enable windows powershell restrictions.
But should I choose game capture in obs?
Because I still can't see the openxr toolkit window in obs
jian @.***>於 2022年12月26日 週一，下午7:51寫道：

Sorry I can't translate into English here
Jabbah @.***>於 2022年12月26日 週一，下午7:34寫道：

What is the error?
On Mon, 26 Dec 2022, 09:14 JIAN83157, @.***> wrote:

Another way to install?
Right-clicking and running Install-Layer.ps1 in Windows 11 gives an
error
—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAWN2PIQVR6YRNBUEEWAI5LWPFOWDANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2#issuecomment-1365110549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46NHSYBCLZD3MWOXP2YJMDWPF7CXANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I successfully solved the problem!
works well now
jian @.***>於 2022年12月26日 週一，下午8:02寫道：

I have searched online how to enable windows powershell restrictions.
But should I choose game capture in obs?
Because I still can't see the openxr toolkit window in obs
jian @.***>於 2022年12月26日 週一，下午7:51寫道：

Sorry I can't translate into English here
Jabbah @.***>於 2022年12月26日 週一，下午7:34寫道：

What is the error?
On Mon, 26 Dec 2022, 09:14 JIAN83157, @.***> wrote:

Another way to install?
Right-clicking and running Install-Layer.ps1 in Windows 11 gives an
error
—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAWN2PIQVR6YRNBUEEWAI5LWPFOWDANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Jabbah/OpenXR-Layer-OBSMirror/issues/2#issuecomment-1365110549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A46NHSYBCLZD3MWOXP2YJMDWPF7CXANCNFSM6AAAAAATJQGGPI
.
You are receiving this because you authored the thread.Message ID:
@.***>


lib/tests/formulae: remove ARM/Linux skip behaviour

The current system requires too much manual intervention before a
formula is bottled. While bottling for Monterey, I discovered about two
dozen formulae that should have had ARM Big Sur bottles but didn't.
Presumably, I would have found more if I were trying to look.
Let's try to automate more of the bottling process by always attempting
a build on ARM and Linux. We avoid CI failures by using skipped
instead of failed whenever we encounter a build/test/linkage error on
a formula that hasn't been bottled for the current OS.

So everything is going to be built on every OS now? CI-force-* labels in homebrew-core will do nothing?

Yes and yes. I'll do a bunch of cleaning up if/when we merge this.

I also like this idea of trying to bottle up everything. And later we can think if we want to have skip logic again (or maybe use depends_on to do the skip like what we already did).

Probably still want to skip if a dependency isn't bottled for that arch/OS family (no_older_versions: false)

Should we maybe enforce somehow that arch: requirements are documented in the code? Though that still requires that someone read it. Maybe we should still occasionally ignore an arch: requirement in test-bot for PR runs?

I was going to suggest we still skip if a dependency isn't bottled for that arch/OS family (no_older_versions: false)

Agreed.

Should we maybe enforce somehow that arch: requirements are documented in the code? Though that still requires that someone read it. Maybe we should still occasionally ignore an arch: requirement in test-bot for PR runs?

I think we need a way of differentiating between a temporary "this doesn't build but we expect it to be fixed in future" and "this doesn't build and never will" for both architectures and OSs.
Arguably that is temporary = doesn't have a bottle and permanent = have a arch: or OS requirement but that somewhat screws over people in a non-default prefix who are building from source and won't get any notification that things are broken (or get demanded to do --build-from-source. If we want to keep things as they are: perhaps we could adjust our current "you tried to install something without a bottle, you'll need to request building from source" messaging to non-default prefixes and use "default prefix doesn't have a bottle" as "building from source probably won't work here".
Thoughts?

I think we need a way of differentiating between a temporary "this doesn't build but we expect it to be fixed in future" and "this doesn't build and never will" for both architectures and OSs.
Arguably that is temporary = doesn't have a bottle and permanent = have a arch: or OS requirement but that somewhat screws over people in a non-default prefix who are building from source and won't get any notification that things are broken (or get demanded to do --build-from-source. If we want to keep things as they are: perhaps we could adjust our current "you tried to install something without a bottle, you'll need to request building from source" messaging to non-default prefixes and use "default prefix doesn't have a bottle" as "building from source probably won't work here".

Yup, agree with all this. It's important to note, however, that our handling of all bottles is slightly different: some/many of these have arch: or :macos requirements that could be removed eventually (or even now, if someone invested time in fixing the test).

There's still some cleanup to do, but I'll leave that for a follow-up since that involves some changes over at Homebrew/core too.

This should be ready to go. This is the order I intend to merge things:

This PR
Homebrew/homebrew-core#87871
#690

I'll wait until the end of the day (UTC+8) for further feedback before proceeding.

Ok, looks like this needs more work: https://github.com/Homebrew/homebrew-core/runs/4115838727?check_suite_focus=true#step:7:179


[🔷 Feature request ] Share the code of "San-Francisco house prices predictions live demo"

Feature
It would be nice to have the code of "San-Francisco house prices predictions live demo" and maybe explained in detail?
Type

[ ] Dann
[ ] Matrix
[ ] Layer
[ ] Activation functions
[ ] Loss functions
[ ] Pool functions
[ ] Datasets
[ ] Documentation
[x] tests & examples
[ ] Other

Hey 404,
I updated the code, added some descriptive comments & made it public!
Check it out here


Fixed misc CRAN issues

Hello,
Thank you for this excellent package! @randxie and I would like to help you address #629 . We have some experience on the team working with the wonderful eccentricities of getting accepted to CRAN.
What I changed
Please consider this first PR to address some low-hanging notes and warnings. I've also attached a file with the state of the R CMD CHECK output showing the remaining notes and warnings that could be addressed in follow-up PRs.
r_cmd_check.log
As of this PR, R CMD CHECK for this package is down to 4 warnings and 3 notes.
Setup Information
I built the package by running the following from the repo root (I am on MacOS):
# Avoid errors related to AppleClang
export CXX=g++-7 CC=gcc-7

# Build some artifacts and document
Rscript -e "devtools::document()"

# Build the package tarball
cd R-package && Rscript build_package.R

# re-running documentation
Rscript -e "devtools::document()"

# Run R CMD CHECK and save results to file
R CMD CHECK lightgbm_2.1.0.tar.gz --as-cran --no-tests | tee r_cmd_check.log | cat

Please let me know if you have any questions or concerns! Please also let @randxie and I know if you are open to us making additional contributions to move this package toward CRAN-readiness.
Thanks!
-James

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

ping @Laurae2

@guolinke Please review the R-package description if you need to make changes on it.
You can compare with xgboost: https://github.com/dmlc/xgboost/blob/master/R-package/DESCRIPTION

@guolinke , adding @jameslamb and @Laurae2  to the author list will be nice.
@jameslamb , could you please also sign the CLA?

@chivee sorry for the delay. CLA signed!

@Laurae2 can you create another PR to add yourself and other R's contributors to author List ?

@guolinke Yes I'll do when I get time tonight or next week.
Do I add both @jameslamb and @yanyachen ?


grammar on content

The paragraph below is missing a "be" in may be advantageous
Additionally, it may advantageous to configure request timeouts and output caching for these endpoints to prevent abuse or denial-of-service attacks. To do so, consider the following modified AddDefaultHealthChecks method:
Additionally, it may be advantageous to configure request timeouts and output caching for these endpoints to prevent abuse or denial-of-service attacks. To do so, consider the following modified AddDefaultHealthChecks method:

Hi @TamirAl - what article are you referring to?


CPU overload

Intermittently increases CPU usage suddenly.

Can somebody help me?

Please post the code you're using to do this. Currently it looks like the websocket can't listen on the address being provided.

import asyncio
import datetime
import json
import random
import string

from sanic import Sanic
from sanic.log import logger
from sanic.response import json as sanic_json
from sanic.websocket import WebSocketProtocol
from aioredis import create_redis

from middleware import bp as middleware
from utils import flanb_send, get_channel_id
from settings import REDIS_URL

application = Sanic()
application.blueprint(middleware)
application.config.WEBSOCKET_MAX_SIZE = 2 ** 20
application.config.WEBSOCKET_MAX_QUEUE = 32
application.config.WEBSOCKET_READ_LIMIT = 2 ** 16
application.config.WEBSOCKET_WRITE_LIMIT = 2 ** 16
application.config.RESPONSE_TIMEOUT = 60
application.config.REQUEST_TIMEOUT = 60

asyncio.set_event_loop_policy(asyncio.DefaultEventLoopPolicy())
loop = asyncio.get_event_loop()

async def publish(ws, channel_id):
    logger.info('[connect] %s' % channel_id)
    try:
        redis = await create_redis(REDIS_URL)
        while not ws.closed:
            data = await ws.recv()
            logger.info('[pub]: <%s> %s' % (channel_id, data))
            await redis.publish_json(channel_id, data)
    except OSError as e:
        logger.error('%s' % e)

async def subscribe(ws, channel_id):
    redis = await create_redis(REDIS_URL)
    channel = (await redis.subscribe(channel_id))[0]
    while await channel.wait_message():
        data = await channel.get_json()
        logger.info('[sub]: <%s> %s' % (channel_id, data))
        await ws.send(data)

async def publish_to_channel_once(channel_id, data):
    redis = await create_redis(REDIS_URL)
    logger.info('[pub]: <%s> %s' % (channel_id, data))
    await redis.publish_json(channel_id, data)

async def elephant_subscribe(ws, channel_id, request=None):
    redis = await create_redis(REDIS_URL)
    channel = (await redis.subscribe(channel_id))[0]
    while await channel.wait_message():
        data = await channel.get_json()
        data = json.loads(data)
        if data['direction'] == 'up':
            if request.get('user'):
                data['sender']['id'] = request.get('user')['provider_uid']
            data['channel_id'] = channel_id
            await flanb_send({'text': data})
        elif data['direction'] == 'down':
            data['timestamp'] = int(datetime.datetime.now().timestamp() * 1000)
            logger.info('[sub]: <%s> %s' % (channel_id, data))
            await ws.send(json.dumps(data))
        if data.get('channel_id'):
            if channel_id != data.get('channel_id'):
                await publish_to_channel_once(data.get('channel_id'), json.dumps(data))

@application.websocket('widget')
async def elephant(request, ws):
    channel_name = "".join(random.choice(string.ascii_letters) for _ in range(12))
    channel_id = get_channel_id(channel_name)
    await asyncio.gather(publish(ws, channel_id), elephant_subscribe(ws, channel_id, request=request))

@application.websocket('test')
async def test(request, ws):
    await asyncio.gather(publish(ws, 'test'), subscribe(ws, 'test'))

@application.websocket('<vendor:[0-9A-Za-z_-]+>')
async def pongo(request, ws, *args, **kwargs):
    if not request.get('user'):
        return
    vendor = kwargs.get('vendor') or 'pongo'
    await asyncio.gather(publish(ws, vendor), subscribe(ws, vendor))

@application.route('/')
async def health_check(request):
    return sanic_json(body={}, status=200)

code run by docker(gunicorn) - nginx
ENTRYPOINT ["gunicorn", \
    "--bind=<IP_ADDRESS>:8000", \
    "--worker-class=sanic.worker.GunicornWorker", \
    "--workers=4", \
    "application:application"]

Have you scaled the workers, starting with 1, 2, then 4 to see if the problem happens consistently? Also, have you tried running directly, without gunicorn?

No, actually. It would be good for prod without gunicorn?
Let's reduce the number of workers. But I do not think this is a problem.

Just trying to narrow the scope. Right now there's a lot of variables in play.

In conclusion, redis connection failure is a problem, but do you have any idea?

Not sure offhand - maybe attempt to establish your redis connection prior to using your publish ws route. estblish the redis connection in a before_server_start function. There are examples in the docs here: https://sanic.readthedocs.io/en/latest/sanic/middleware.html#listeners

btw, I tried on one server, one worker. but same.
To connect redis with the before_server_start function?
@app.listener('before_server_start')
async def setup_redis(app, loop):
    app.redis = await create_redis (url)

I just tried that. but the redis connection must be reconnected each time.

Have you tried using a connection pool instead of a single connection?

Let me try.

Also looks like your sum requests jumps at the same time ? What does that metric measure ?

@yunstanford That is AWS elasticbeanstalk mornitoring panel.
Anyway.. it seems to be fixed!
I changed the single connection to connection pool.
Thank you very much!


[request] Versioning of APIs and Microservices

It's quite common to version APIs to make sure that existing integrations continue to run while still making improvements, fixes and adding or removing functionality. This is done in a variety of ways  including changing the URL, using custom headers, and leveraging the accept header. I believe Kong could help many API providers by allowing these conventions to map to the appropriate upstream services.
Here's a few ideas on how it could work, of course this is a hotly debated topic and Kong should aim to support all of the use-cases that already exist in the wild. Some of the ideas are currently possible, specifically the URL pattern except you have to create an API for each version, and the others would be possible if you could map requests to upstream services based on headers (which I'll make a separate issue for but it would still require creating a new API for each version) In my opinion it's best to have Kong handle versioning APIs as it's own construct tied directly to the API being versioned.
How about some examples of expected functionality following common API versioning patterns? Let's say I have an API with two versions, 1 & 2, and I'd like the "default" to be version 2:

Allow URLs to map to upstream services.

Request with the URL http://api.example.com/1/endpoint should send the request to example-api.v1.local
Request with the URL http://api.example.com/2/endpoint should send the request to example-api.v2.local
Request with the URL http://api.example.com/324/endpoint should probably return a 404.
Request with the URL http://api.example.com/endpoint should send the request to example-api.v2.local

Allow custom headers to map to upstream services.

Request with the header api-version: 1 should send the request to example-api.v1.local
Request with the header api-version: 2 should send the request to example-api.v2.local
Request with the header api-version: 55 should send the request to example-api.v2.local
Request without a api-version header should send the request to example-api.v2.local

Allow accept headers to map to upstream services.

Request with the header Accept: application/vnd.example.v1+json should send the request to example-api.v1.local
Request with the header Accept: application/vnd.example.v2+json should send the request to example-api.v2.local
Request with the header Accept: application/vnd.example.v55+json should send the request to example-api.v2.local
Request with out an Accept header should send the request to example-api.v2.local
There are other considerations such as deprecation timetables (I only want the v1 to work for 6 months before it returns an error with information on how to upgrade to a newer version) and dealing with authentication to only allow certain consumers access to certain versions (paying users get access to beta versions) and much more I'm possibly leaving out. I'd like to get a discussion going here to think about the best way for Kong to support versioned APIs.
Thanks for reading!

:+1:

+1

+1

This is a great suggestion and pretty well detailed. In the absence of this feature in Kong, how are others dealing with versioning?
If I have foo-service.v1.local and foo-service.v2.local running then I'd like to have:

http://kong/foo-service/1/endpoint go to foo-service.v1.local
http://kong/foo-service/2/endpoint go to foo-service.v2.local.

It looks like I can add two APIs to Kong like so and that would make sure all requests get routed to the appropriate service:
For foo-service.v1:
{
    "name": "foo-service.v1",
    "request_path": "/foo-service/1",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v1.local"
}

and for foo-service.v2:
{
    "name": "foo-service.v2",
    "request_path": "/foo-service/2",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v2.local"
}

But now Kong has no idea about my individual endpoints, the reals APIs of foo-service. Consequently, I can't really use plugins like ACL to secure my APIs.
It is likely that I'm missing something here. Anyone has thoughts on how to add all endpoints of foo-service into Kong while still being able to call the two versions as http://kong/foo-service/1/endpoint and http://kong/foo-service/2/endpoint?

Anyone has thoughts on how to add all endpoints of foo-service into Kong

Before going further, I will clarify that Kong has no concept of "endpoints" on the services it proxies. Kong proxies whatever comes its way, and does not know if the requested URI matches one of your services' endpoints or not. So Kong will send any incoming request to the corresponding upstream service. Aka: Kong does not support any versioning, by doing this you simply configure two different APIs, pointing to two different locations.
Now, my understanding is also that you wish to apply an ACL plugin to both of your versions, and wish to not duplicate the plugin, but have it active on both APIs? If so, that is currently not possible, as plugins are currently tied to only 1 API at a time. This relates to #505.
Now about this issue, I do think it makes sense and I think @montanaflynn's description of the desired behavior is both precise and good enough. Having one API being able to point to multiple locations to address versioning is something to look forward to. But this is currently not implemented.

Thanks @thibaultCha I'll just create different APIs for each path that needs to go through ACL. I'll need to create them twice and apply ACL to them individually. Thats fine for now.
To add version prefixes to my APIs (so that I could do http://kong/foo-service/1/A and http://kong/foo-service/2/A), I could just let the request_path contain /foo-service/[version-number], strip the request path entirely and route it to the server with that [version-number] deployed using the full upstream_url.
Something like so:
For foo-service.v1:
{
    "name": "foo-service.v1.A",
    "request_path": "/foo-service/1/A",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v1.local/A"
},
{
    "name": "foo-service.v1.B",
    "request_path": "/foo-service/1/B",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v1.local/B"
}

and for foo-service.v2:
{
    "name": "foo-service.v2.A",
    "request_path": "/foo-service/2/A",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v2.local/A"
},
{
    "name": "foo-service.v2.B",
    "request_path": "/foo-service/2/B",
    "strip_request_path": true,
    "upstream_url": "https://foo-service.v2.local/B"
}

With the above:

http://kong/foo-service/1/A will hit https://foo-service.v1.local/A
http://kong/foo-service/2/A will hit https://foo-service.v2.local/A

And I can use ACL for my actual API A. Thanks again for your help.

Guys, I think that we can create a plugin for Header redirects will be great.
Look the ideia bellow:
Service version 1: /apis
{
    "name": "foo-service.v1",
    "request_path": "/foo-service-v1",
    "upstream_url": "http://foo-service.v1.local"
}

Service version 2: /apis
{
    "name": "foo-service.v2",
    "request_path": "/foo-service-v2",
    "upstream_url": "http://foo-service.v2.local"
}

Api: /apis
{
    "name": "foo-service",
    "request_path": "/foo-service",
    "upstream_url": "http://foo-service.local"
}

Enable Plugin: /apis/{api}/plugins
{
    "name": "header-redirect",
    "header": "api-version",
	"default": "v2",
    "config.values[1]=v1:/foo-service-v1"
    "config.values[2]=v2:/foo-service-v2"
}

I came across this issue when searching the message:
[
    "request_path": "already exists with value '/v1'"
]

I am simply trying to have the same request_path in two APIs that have a different request_host.  For example,
curl http://localhost:8001/apis/ -X POST \
  -d 'name=api1' \
  -d 'preserve_host=true' \
  -d request_host=api.example.com \
  -d 'request_path=/v1' \
  -d 'strip_request_path=true' \
-d 'upstream_url=http://<IP_ADDRESS>:8001'

Adding a second API with version v1 does not work:
curl http://localhost:8001/apis/ -X POST \
  -d 'name=api1' \
  -d 'preserve_host=true' \
  -d request_host=api.example.com \
  -d 'request_path=/v1' \
  -d 'strip_request_path=true' \
-d 'upstream_url=http://<IP_ADDRESS>:8001'

💩
Yes, I have to configure my plugins twice, but I would at least be able to have API domains with the same version.
Is there any way to have two request hosts with the same request path?

👍

https://apigee.com/about/blog/developer/common-misconceptions-about-api-versioning


YoBit pair names

CC (CoolinDarkCoin) Cryptopia in YoBit exchange is CCX, not CC
PAY (TenX) Cryptopia not PAY (Epay) YoBit
OMG (OmiseGo) Cryptopia not OMG (OMGame) YoBit
REP (Augur) Cryptopia not REP (RepubliCoin) Yobit
NAV (NAVcoin) Cryptopia not NAV (NavajoCoin) YoBit
LIZI (LiziCoin) Cryptopia not LIZI (LiZi) YoBit

@mazertwo, CC is CyberCoin on CoinMarketCap. So, which one is true?

Cryptopia's CC is CoolinDarkCoin.
YoBit CC is CyberCoin.
Cryptopia's CC is Yobit CCX.

@mazertwo yes, but CC means a third different currency named CC on CoinMarketCap, so which of them should be the actual CC currency:

CoolinDarkCoin ?
CyberCoin ?

I think, CC is CyberCoin, as coinmarketcap say :)
YoBit CCX = Cryptopia CC

But if CC on Cryptopia is CoolinDarkCoin, then this contradicts CMC's CC for CyberCoin, doesn't it?

Let me explain: we have support for 88 exchanges and crypto APIs including CoinMarketCap, so, we are really talking not about Cryptopia vs YoBit, but about the true pair namings for cryptocurrencies and their symbols. So, the actual questions is: which one is true CC?

I cant find CyberCoin on Cryptopia. Just only CoolinDarkCoin as CC name.

@mazertwo if CC should mean CyberCoin as per CoinMarketCap (not Cryptopia), then what name should it be for Cryptopia ? CDC = CoolinDarkCoin? And vice versa, if we set CC = Cryptopia's CoolinDarkCoin, then we need to rename CyberCoin on Coinmarketcap ? For what? CBC ?

Ahaha, i think we just need remove CC from all pairs from Cryptopia in ccxt.
Or take YoBit name CCX for Cryptopia CC

@mazertwo ok, so Cryptopia CC should be renamed to CCX to resolve the conflict... Yes, I agree on that. I'll fix it for Cryptopia and I'll dig into other pairs now, thx!

Thanks for you!

@mazertwo looks like LIZI is the same as LiziCoin on Yobit? Can't find LiZi anywhere at all... Can you elaborate on this plz?

Most of them are fixed now, and the only one remaining is LIZI. Not sure if I should rename it on YoBit, because, it looks like LIZI first started trading there. Any ideas?

LiZi at YoBit looks like fake. You can't deposit and withdraw it.
Lizi at YoBit cost 0.0001264 BTC
Lizi at Cryptopia cost 0.0000319 BTC
More than 3 times lower :)))

@mazertwo but, actually, this can be the reverse – because it seems that LIZI first started on YoBit, and Cryptopia/Nova are both wrong ? Anyway, which one should we rename to what, how do you think?

@yobit: LIZI → LiZi ?
or
@cryptopia LIZI → LiZi + @nova LIZI → LiZi ?

Ok, all pairs are renamed and are now closer to being consistent. Looks like we killed all the above bugs with your help! Let us know if you find any more. Thx!


[TEP-0089] SPIRE for non-falsifiable provenance.

[TEP-0089] SPIRE for non-falsifiable provenance.
This PR is a part of a larger set of PRs to provide non-falsifiable provenance through SPIRE.
In particular this PR uses the SPIRE infrastructure which has already been merged to sign TaskRunStatus.
It also has support to verify if TaskRunStatus has been modified by another workload between reconciles.
Previously merged PRs are

PR-5039
PR-5647
PR-5676
PR-5902

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[X] Has Docs included if any changes are user facing
[X] Has Tests included if any functionality added or changed
[X] Follows the commit message standard
[X] Meets the Tekton contributor standards (including
functionality, content, code)
[X] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[X] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[X] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Added TaskRun Status annotations to track the validity of the signed TaskRun
Utilizes pipeline controller spire SVID, status hash and signature
Pipeline controller continuously validates the TaskRun Status for any modifications
Tekton Chains will validate the results and status of the TaskRun after completion

/kind feature

/assign @lumjjb
/assign @pxp928

@lumjjb @pxp928 This is a merge of phase1 and phase2. This has a few changes to code as well as unit tests on top of the phase1 and phase2 PRs. Please take a look.

/retest

/retest

/retest

/retest

/retest

/retest

@jagathprakash fyi started taking a look last week but waiting for you to mark this as "ready for review" before taking another look

/retest

/retest

@jagathprakash fyi started taking a look last week but waiting for you to mark this as "ready for review" before taking another look

Thanks @jerop for taking a look.
The PR is now ready to be reviewed.

/retest

/retest

/assign @chitrangpatel

/cc @chitrangpatel

@jagathprakash please try to maintain the code coverage - it seems there are some spire-related codepaths in taskrun.go that are not tested

@jagathprakash please try to maintain the code coverage - it seems there are some spire-related codepaths in taskrun.go that are not tested

@jerop Added a test which tests all new lines added for SPIRE. PTAL.

@jagathprakash is splitting this up into smaller PRs so we can close this


turn off tags

I have an input box with value containing comma.
eg: An address.
Selectize is added to the input box..
In my example I see that the selectize makes tags form my string.
Is it somehow possible use selectize as a simple autocomplete? Just print out the value I set at load...

Setting mode: 'single' worked for me


require node 16 due to usage of adapter-core 3.x.x

adapter-core 3.0.0 is known to fail with node 14 as npm 6 does not install peerDependencies.
So this adapter must require node 16 or newer

Done and merged


feat(helm): install directly from repo

A helm install command will try to load a chart from a local file first.
But if a local file is not found, it will try to fetch a file from a
matching repo request. The file will be downloaded to the client,
and then sent to Tiller for installation.

For testing:

Use the default repo or add your own repo with helm repo add
Find a chart to install with helm search
Install that chart using helm install repo/chart-version

Example:
⇒  helm search alpine
kube-charts/alpine-0.1.0.tgz
⇒  helm install kube-charts/alpine-0.1.0

This should (a) download the chart into your CWD, and (b) install that chart into your Tiller.

% helm install kubernetes-charts/alpine-0.1.0.tgz
Fetched kubernetes-charts/alpine-0.1.0.tgz to /Users/adamreese/p/go/src/k8s.io/helm/alpine-0.1.0.tgz
maudlin-gopher


100% Racket Code Generation using "Dehumanized Prompts"

Hello,
I want to share a 100% success rate on "Measure impact of system message on response" example by applying the "Dehumanize Prompt" technique found at https://github.com/kfern/dehumanize-prompt
You can view the working result directly here: https://chainforge.ai/play/?f=37wlj5rychogs
To reproduce the result, follow these steps:

Go to the Chainforge.ai playground: https://chainforge.ai/play/
Click on the "Example Flows" button.
Select the "Measure impact of system message on response" example.
Add a new OpenAI > GPT 3.5 Model with the following details:

Nickname: dehumanize-prompt
Model Version: gpt-3.5-turbo (default)

Paste the following dehumanized system message prompt:

You are a software generator machine that creates programs in the Racket programming language.
Your response has to be **CODE ONLY**, because it will be used by a machine that only knows this syntax.

Click the "Submit" button with the default values.
Run the "Prompt Node".
Run the "JavaScript Evaluator".

We can also go one step further and remove from the acceptance criteria that the code has a single text response that looks like a codeblock https://chainforge.ai/play/?f=3blmo5an97ok0

I can do a PR if you want to update this example :-)

Sure, please add this to the example and make a PR and I will update it! Great idea!! :)

@ianarawjo Done!


minimal example for inference-as-a-service

Congrats on this amazing project! We are interested in testing LMQL for inference-as-a-service. It would be great if the document contains a minimal example of using LMQL as library that

load a HF model once
handle LMQL as string

Thank you for this inquiry. Both 1+2 are possible, I will try to soon add an appropriate sample to the documentation.

@lbeurerkellner do you have any update on this? thanks!

thanks so much!!!


Uncaught TypeError: Cannot read property 'hide' of undefined

Atom Version: 1.8.0
System: Mac OS X 10.11.3
Thrown From: atom-keyboard-macros package, v0.9.1
Stack Trace
Uncaught TypeError: Cannot read property 'hide' of undefined
At /Users/matthewchang/.atom/packages/atom-keyboard-macros/lib/atom-keyboard-macros.coffee:30

TypeError: Cannot read property 'hide' of undefined
    at OneLineInputView.module.exports.OneLineInputView.hide (/Users/matthewchang/.atom/packages/atom-keyboard-macros/lib/one-line-input-view.coffee:36:11)
    at Object.module.exports.AtomKeyboardMacros.onEscapeKey (/Users/matthewchang/.atom/packages/atom-keyboard-macros/lib/atom-keyboard-macros.coffee:373:25)

Commands
     -0:22 core:move-right (atom-text-editor.editor.is-focused)
     -0:22 core:delete (atom-text-editor.editor.is-focused)
     -0:22 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:22 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -0:22 core:backspace (atom-text-editor.editor.is-focused)
     -0:22 editor:select-to-first-character-of-line (atom-text-editor.editor.is-focused)
     -0:22 core:undo (atom-text-editor.editor.is-focused)
     -0:22 editor:consolidate-selections (atom-text-editor.editor.is-focused)
  3x -0:22 core:move-right (atom-text-editor.editor.is-focused)
     -0:22 editor:newline (atom-text-editor.editor.is-focused)
  2x -0:21.4.0 linter:lint (atom-text-editor.editor)
 10x -0:11.4.0 find-and-replace:select-next (atom-text-editor.editor.is-focused)
     -0:03.0 core:delete (atom-text-editor.editor.is-focused)
     -0:01.6.0 core:undo (atom-text-editor.editor.is-focused)
     -0:00.8.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:00.5.0 core:move-left (atom-text-editor.editor.is-focused)

Config
{}

Installed Packages
# User
atom-beautify, v0.29.8
atom-keyboard-macros, v0.9.1
atom-typescript, v8.11.0
autocomplete-ruby, v0.1.0
language-latex, v0.6.1
latextools, v0.8.1
linter, v1.11.4

# Dev
No dev packages

Idem on atom 1.19.5

Also on Atom 1.23


support unscoped routes in location targets on gitlab

Hey, I just made a Pull Request!
Resolves #12456 by removing the buildRawUrl function and making getProjectId and buildProjectUrl flexible enough to support both scoped and unscoped routes. I also refactored the tests a bit to give better feedback, and covered some missing edge cases.
I really tried to minimize the scope of the change to the app code, but the specific lines are not especially readable if you're not familiar with scoped and unscoped routes in GitLab. I can extract some helper functions with clearer names if desired.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] ~Added or updated documentation~
[x] Tests for new functionality and regression tests for bug fixes
[ ] ~Screenshots attached (for UI changes)~
[x] All your commits have a Signed-off-by line in the message. (more info)

@Rugvip can you suggest better language than 'unscoped' and 'url' for my changelog?

I really want to get a few pairs of eyes on this, and tested by some other GitLab users too. Gonna ask about in Discord see if there's anyone that can help out. Is there any other GitLab users you know of @jamieklassen?

@OpenSourceZombie @mateiidavid @dehamzah @ItzEdgar @adrianke77 - you've all contributed to this part of the codebase in the past. Any chance you might have bandwidth to test this out?

@cregev also showed interest in the bug and might be able to help test?

Hey @jamieklassen - I'm pretty tempted just to merge this as is to be honest, and push it out for testing in the next release on Tuesday either way. Would be great if we could get someone to test it from the PR though before if that's possible, but if not, no biggie. Let's just use the next releases to test.


Failed to setschedparam: Operation not permitted

After installing manually following only these lines from the install script (to not install Alexa related code)  https://github.com/respeaker/respeakerd/blob/master/scripts/install_all.sh#L39-L88
Also checking that pulse audio was configured properly, the systemd service failed with
(188ms)DEBUG -- record stream state: 2  [pulse_collector_node.cc:482]
(188ms)INFO  -- Connected to PulseAudio server.  [pulse_collector_node.cc:493]
(189ms)DEBUG -- PulseCollectorNode input: channels 8 rate 48000, output: channels 8 rate 16000  [pulse_collector_node.cc:504]
(189ms)INFO  -- PulseCollectorNode thread started.  [pulse_collector_node.cc:506]
Failed to setschedparam: Operation not permitted
(191ms)INFO  -- PulseCollectorNode thread joined.  [pulse_collector_node.cc:635]
Can not start the respeaker node chain.

Setting
sudo sysctl -w kernel.sched_rt_runtime_us=-1

Fixed the problem, but it is supposed to be a dangerous setting https://access.redhat.com/solutions/1604133
Since librespeaker is not open source as far as I can tell (calling it libre is really misinformation :( ) I can't check what's happening in pulse_collector_node.cc
$ cat /etc/issue.net
Debian GNU/Linux 9

respeaker.io Debian Image 20180801

Support/FAQ: http://respeaker.io

default username:password is [respeaker:respeaker]

$ sudo apt-cache policy librespeaker
librespeaker:
  Installed: 2.1.2-build190110
  Candidate: 2.1.2-build190110
  Version table:
 *** 2.1.2-build190110 500
        500 http://respeaker.seeed.io/deb stretch/main armhf Packages
        100 /var/lib/dpkg/status
     2.1.1-build181119 500
        500 http://respeaker.seeed.io/deb stretch/main armhf Packages
     2.0.0-build180720 500
        500 http://respeaker.seeed.io/deb stretch/main armhf Packages

$ pip freeze
cryptography==1.7.1
enum34==1.1.6
idna==2.2
ipaddress==1.0.17
keyring==10.1
keyrings.alt==1.3
pixel-ring==0.1.0
pulsectl==20.5.1
pyasn1==0.1.9
PyAudio==0.2.11
pycrypto==2.6.1
pydbus==0.6.0
pygobject==3.22.0
pyusb==1.0.2
pyxdg==0.25
SecretStorage==2.3.1
six==1.10.0
spidev==3.5
voice-engine==0.1.3

Possible Solution
Open source librespeaker

@jmatsushita I faced the same issue while trying to run librespeaker code from within systemd (dedicated service based on this lib).
Checking different forums and SO lead me to the hint about "Realtime Priority" option which equals 99 while running in a normal user-mode. And systemd sets it equal to 0 by default. You can adjust the real-time priority via ulimit -r command from the terminal. However, on a service level, it's called LimitRTPRIO. Anyway, when I added this option to my systemd service, the permission issue has gone. However, I faced a couple of others.
Finally, I tried a bit different approach - creating service via pm2 library (popular process manager). Technically, it's started as a systemd service as well. But I believe the main difference is that it spawns other processes from within itself. I'm not sure about its internals but adding LimitRTPRIO=99 to the pm2 service and configuring my app (based on librespeaker) to be started automatically via pm2 did the trick. You can find details in my voice streaming project.


Fetching from server doesn't update the list of branches

If there's a new branch on the server but not on local, then fetching doesn't update the list of branches that remote has. Imagine this scenario:
Alice and Bob both have the up-to-date repo. Bob pushes a new branch 'foo' to remote, and Alice fetches from server to start tracking 'foo' using Elegit. But when she opens branch manager she won't be able to see 'foo' on the list of remote branches.
Closing and reopening the same repo will refresh the list

Fixed


Doc update

Updates README and the license in package.json. Also, makes Docker development a little friendlier by relying on ~/.aws/credentials both with Docker and local development.
Depends on #22.

Looks good.  Merging.


[Feature Request] Trim params from the URL preview on apps

Some of my apps have params in the URLs to knock off a few clicks on the landing page. It would be nice if there was an option or default behavior to shave off params from the url preview.

Am able to workaround this by adding the base-url to the description


[Bug]: Underspecified linter errors (in JavaScript?)

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://docs.all-hands.dev/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
I am noticing that when I ask the agent to modify a typescript app, the linter is throwing errors, stalling the agent's progress, but the errors are underspecified, not clearly indicating what is going wrong. I also was not able to tell on a brief glance what is going wrong in the typescript to tell what is going wrong, so I'm not even sure if the linter errors are correct.
Here is an action/observation pair:
21:47:02 - ACTION
**IPythonRunCellAction**
THOUGHT: I apologize for the persistent errors. It seems that we are unable to modify the file content as intended. Given the limitations and the remaining turn, let's try one last approach to add the dark mode functionality with minimal changes.

Let's modify the return statement to include the dark mode toggle button:
CODE:
edit_file_by_replace(
'/workspace/src/App.tsx',
to_replace="""  return (

      <PullRequestViewer />

  )""",
new_content="""  const [darkMode, setDarkMode] = useState(false);

  const toggleDarkMode = () => {
    setDarkMode(!darkMode);
    document.body.classList.toggle('dark-mode');
  };

  return (
    <div className={`App ${darkMode ? 'dark-mode' : ''}`}>
      <button onClick={toggleDarkMode}>
        {darkMode ? 'Light Mode' : 'Dark Mode'}
      </button>
      <PullRequestViewer />

  )"""
)
21:47:02 - opendevin:INFO: runtime.py:258 - Awaiting session
21:47:03 - opendevin:INFO: runtime.py:196 - Reconnecting session
21:47:03 - opendevin:INFO: runtime.py:202 -
------------------------------Container logs (last 10 lines):------------------------------
    |INFO:     <IP_ADDRESS>:62990 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:39321 - "POST /execute_action HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:33232 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:36470 - "POST /execute_action HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:64557 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:36470 - "POST /execute_action HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:37909 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:32892 - "POST /execute_action HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:60044 - "GET /alive HTTP/1.1" 200 OK
    |INFO:     <IP_ADDRESS>:47413 - "POST /execute_action HTTP/1.1" 200 OK
    |
------------------------------------------------------------------------------------------
21:47:03 - opendevin:INFO: runtime.py:265 - Executing command
21:47:03 - OBSERVATION
**IPythonRunCellObservation**
[Your proposed edit has introduced new syntax error(s). Please understand the errors and retry your edit command.]
/workspace/src/App.tsx:14
[This is how your edit would have looked if applied]
-------------------------------------------------
(this is the beginning of the file)
1|
2|import React, { useState, useEffect, useCallback } from 'react'
3|import './App.css'
4|import PullRequestViewer from './PullRequestViewer'
5|
6|function App() {
7|  const [darkMode, setDarkMode] = useState(false);
8|
9|  const toggleDarkMode = () => {
10|    setDarkMode(!darkMode);
11|    document.body.classList.toggle('dark-mode');
12|  };
13|
14|  return (
15|    <div className={`App ${darkMode ? 'dark-mode' : ''}`}>
16|      <button onClick={toggleDarkMode}>
17|        {darkMode ? 'Light Mode' : 'Dark Mode'}
18|      </button>
19|      <PullRequestViewer />
20|

21|  )
22|}
23|
24|export default App
(this is the end of the file)
-------------------------------------------------

[This is the original code before your edit]
-------------------------------------------------
(this is the beginning of the file)
1|
2|import React, { useState, useEffect, useCallback } from 'react'
3|import './App.css'
4|import PullRequestViewer from './PullRequestViewer'
5|
6|function App() {
7|  return (
8|

9|      <PullRequestViewer />
10|

11|  )
12|}
13|
14|export default App
(this is the end of the file)
-------------------------------------------------
Your changes have NOT been applied. Please fix your edit command and try again.
You either need to 1) Specify the correct start/end line arguments or 2) Correct your edit code.
DO NOT re-run the same failed edit command. Running it again will lead to the same error.
[Jupyter current working directory: /workspace]

Here is the relevant code in OpenDevin: https://github.com/OpenDevin/OpenDevin/blob/6e70f79bf4977a47ffdda00753fa56b5a17eae19/opendevin/runtime/plugins/agent_skills/agentskills.py#L544
The linter error is just being described as /workspace/src/App.tsx:14, which isn't enough to tell what is going wrong.
Current OpenDevin version
commit 6e70f79bf4977a47ffdda00753fa56b5a17eae19

Installation and Configuration
make build; make run

Model and Agent
No response
Operating System
No response
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
No response

Hello @neubig - is #3452 something you could try out for this PR?

Thanks! I'll take a look, although it may take a couple days, I'm a bit busy these two days.


Updating sf-resolve-condition

In order to follow the template:
https://github.com/Azure-Samples/service-fabric-api-management/pull/6/commits/491438d48e6fb53b7735a846733ae94b941795de
Due to this issue discussion:
https://github.com/Azure/service-fabric-issues/issues/346

@christopherpcosta : Thanks for your contribution! The author, @rwike77, has been notified to review your proposed change.

@rwike77 - Would you indicate whether this PR can be closed? Thanks

@christopherpcosta @GitHubber17 The updates were merged in a separate PR, so this PR can be closed now.  Thanks.


[FLINK-6755][CLI] Support manual checkpoints triggering

What is the purpose of the change
Since FLINK-24280, we have supported manual checkpoint triggering from REST API. This PR wire command-line interface and rest endpoint, supporting manual checkpoints triggering from CLI.
Brief change log

Add an action "checkpoint" in CLI, and related parameters parsing logic.
Wire this action with rest endpoint.
Documentation about this feature.

Verifying this change
This change added tests and can be verified as follows:

Unit tests for newly added checkpoint cli action
Manually verified triggering checkpoint using command line interface on sample wordcout job deployed on a yarn cluster.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented?  docs

Hi, @pnowojski @masteryhx  Would you please take a look? Thanks!

Can you squash the latest two fixup commits into the first two commits:
[[FLINK-6755] Support manual checkpoints triggering from CLI](https://github.com/apache/flink/pull/23679/commits/c563fd15191137aafc548b0a19fc09a28833aff5)

@[Zakelly](https://github.com/Zakelly/flink/commits?author=Zakelly)
Zakelly committed 2 days ago
[[FLINK-6755] Docs about manual checkpoints triggering from CLI](https://github.com/apache/flink/pull/23679/commits/bd404c8dad2c78dc5106fde39e3f81a689b90c85)

? LGTM otherwise :)

Already done. Many thanks!

Thanks! Merged.


Copy As Image To Clipboard hangs up Archi.exe

Version of Archi

5.2
Archi Plug-ins

coArchi 0.9
Operating System

Windows 11
Expected Behaviour

When I have a view with 10s of archi objects,  Copy As Image To Clipboard copies the view to the Windows clipboard.
When I have a view with 100s of archi objects,  Copy As Image To Clipboard copies the view to the Windows clipboard.
Actual Behaviour

When I have a view with 10s of archi objects,  Copy As Image To Clipboard copies the view to the Windows clipboard.
When I have a view with 100s of archi objects,  Copy As Image To Clipboard hangs up Archi (non-responding for >15 minutes, only killing the process works). When Archi is non-responding, the whole Windows clipboard is affected. I can Cut or Copy, but not Paste. The copied or cut text is not visible in Windows key + v clipboard.
Context
The Archi version in which the Views were created is 4.6.x.
The last Archi version which could successfully Copy As Image To Clipboard was 4.8.
Windows paste history (Windows key + v) is active.
Steps to Reproduce the Behaviour

Create a view with lots of objects
Select view and press context menu (right mouse button).
Copy As Image To Clipboard

Hi, it depends on the View and how much memory you have on your machine. I tested on my Windows 11 machine with a View containing several hundreds of objects and it was OK. Can you provide an example .archimate model file with an example View where you experience this problem?

Bonjour Phillip, thanks for the quick response.
The windows 11 host has 32 GB of RAM. The hanging archi.exe uses almost 1 GB, and CPU is consistently between 5-9% (of a 20 core i9-13900H).
I cannot share the model.
However, I noticed something new. If 1 object is extremely wide (like 4-5 scrolls on a UHD screen), and you try to Copy As Image, it hangs up Archi.exe. You can easily reproduce this I think.
Hope this helps, cheers, Wout

Hi, yes I can reproduce this if the View is extremely wide and tall, as this makes the image size larger.
It's a regression caused by https://github.com/archimatetool/archi/issues/842.
This fix for #842 additionally copies the image data as BMP format which is causing the hang. I'm going to revert that for the next version of Archi. Thanks for the bug report.
Until the next version of Archi there is no workaround other than to save the View as Image.

Implemented in Archi 5.3


How to document Swagger/Swashbuckle parameter descriptions when using [FromQuery]

In a standard .NET Core 2.2 Api project with Swashbuckle.AspNetCore 5.0.0-rc2:
[HttpGet]
public ActionResult GetSomeData([FromQuery] SomeDataRequest request) {
    return File(returnImage(), "image/png");
}

The definition of SomeDataRequest

public class SomeDataRequest {
  /// <summary>
  /// Description 1
  /// </summary>
  [Description("description 1")]
  public string foo;

  /// <summary>
  /// Description 2
  /// </summary>
  [Description("description 2")]
  public string bar;
}

When I bring up the Swagger UI, it doesn't show any kind of descriptions for the properties of SomeDataRequest.
As you can see I tried the Description attribute and the XML comments. Nothing seems to work.

Have you followed the readme instructions for including XML comments?

@domaindrivendev I found the issue.  SomeDataRequest class is in another assembly and therefore was not part of the XML documentation file for the project where Swashbuckle is referenced.  I guess, I'll have to do a post-build step to copy over the xml file.  Thank you!

Hi @rgelb,
Could you explain more about this issue? as I have the same problem and didn't know how to have description for the parameters of class.
Thanks

@davidkmitrais So let's say you have 2 projects.
api.csproj                 -- this project has Controller actions for your API
entities.csproj           -- this project contains entities that you either pass in or return to/from the API.
You generate the XML documentation file for both, which results in api.xml and entities.xml.  These files get placed in their respective bin/debug directories.  And then the Startup.cs in your Api.cs has Swagger declaration to read the xml documentation:
services.AddSwaggerGen(c => {
    c.SwaggerDoc("v1", new Info { Title = "Widgets Images", Version = "v1" });
    var xmlFile = $"{Assembly.GetExecutingAssembly().GetName().Name}.xml";
    var xmlPath = Path.Combine(AppContext.BaseDirectory, xmlFile);
    c.IncludeXmlComments(xmlPath);
    ...

You can see the problem here, right?  It's only getting api.xml because that it's in the executing directory.  So you need to somehow bring entities.xml to the same directory.  To do, that I defined a post-build step for the api project:
copy /Y $(ProjectDir)..\entities\bin\$(ConfigurationName)\netstandard2.0\entities.xml $(TargetDir)
You might have to fudge directory names a little bit if you are not using .net core 2.x
Now after every build, entities.xml will be in the same folder as api.xml.  The last step is to let Swagger know about.  We do this by extending AddSwaggerGen code a bit:
var entitiesXmlPath = Path.Combine(AppContext.BaseDirectory, "entities.xml");
c.IncludeXmlComments(entitiesXmlPath);

I hope this helps.

@rgelb Thank you!.
Yeah now I could display my entities description for swagger UI.
just little thing that I want to add, that we also could add examples of value by adding "example" on definitions like below:
public class SearchTermViewModel
    {
        /// <summary>
        /// First Name of Supplier Contact.
        /// </summary>
        /// <example>John</example>
        public string FirstName { get; set; }

        /// <summary>
        /// Last Name of Supplier Contact.
        /// </summary>
        /// <example>Doe</example>
        public string LastName { get; set; }
}

@rgelb Thanks!  I just add GenerateDocumentationFile to all of referencing .csproj files without post build setting. Once the main project is compiled, the all the xml files are copied to the same directory as the main project is.
  <PropertyGroup>
    <GenerateDocumentationFile>true</GenerateDocumentationFile>
    <NoWarn>$(NoWarn);1591</NoWarn>
  </PropertyGroup>