Performance tests for the scheduler

This code probably doesn't belong in Spark (at least, it doesn't have a nice home there presently), so for now just opening this as a central place to discuss.
Some crude performance tests for the scheduler using https://github.com/apache/spark/pull/8559
In these tests, you setup a mock backend, and run as many simulated jobs as possible in 10 seconds.  This lets you compare the performance of the scheduler with different simulated backends.  Eg., what happens when there are 1000 nodes?  What about when one executor is bad?
I've tried to design things so that the mocking doesn't get in the way of measuring profile, while still allowing enough flexibility.  Would definitely appreciate a second pair of eyes, in any case.
So far I've just been running this manually in sbt, using the "-z" option to limit to some comparisons, eg.
build/sbt -Pyarn -Phadoop-2.4 -Dhadoop.version=2.6.0
> project core
> test-only org.apache.spark.scheduler.SchedulerPerformanceSuite -- -z "COMPARE D bad execs"
...
[info] SchedulerPerformanceSuite:
ran 57 iterations in 10.3 s (179 ms per itr)
[info] - COMPARE D bad execs with advanced blacklist (11 seconds, 201 milliseconds)
ran 102 iterations in 10.1 s (98 ms per itr)
[info] - COMPARE D bad execs with simple blacklist (10 seconds, 126 milliseconds)

Some observations so far:

scheduling is sloooooooooow when there are lots of executors.  (this is true even before any of the blacklist changes are in place).  on my laptop anyway, it starts to drop off dramatically when there are around 200 nodes (800 executors in my setup).  Almost all the time is spent in taskScheduler.resourceOffers.  I am pretty certain the slowdown is not coming from the mock setup -- it doesn't care how many nodes there are.  The only part of it which does scale is that tasks will get queued up for how many slots there are -- but scheduling is fast even if I have one "super executor" with 20K cores.  The code shown here includes the new blacklist mechanism, but the numbers are basically the same either way.
To be clear -- the super node has about 5x as many cores as the 550 node cluster, yet the scheduling is > 30x slower on the 550 node cluster.

> test-only org.apache.spark.scheduler.SchedulerPerformanceSuite -- -z "COMPARE A"
...
ran 3 iterations in 12.7 s (4.2 s per itr)
[info] - COMPARE A Scheduling speed -- large job on a super node (13 seconds, 707 milliseconds)
ran 3 iterations in 12.5 s (4.2 s per itr)
[info] - COMPARE A Scheduling speed -- large job on 50 node cluster (12 seconds, 550 milliseconds)
ran 2 iterations in 10.1 s (5.0 s per itr)
[info] - COMPARE A Scheduling speed -- large job on 100 node cluster (10 seconds, 96 milliseconds)
ran 1 iterations in 10.5 s (10.5 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 200 node cluster (10 seconds, 531 milliseconds)
ran 1 iterations in 22.4 s (22.4 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 300 node cluster (22 seconds, 460 milliseconds)
ran 1 iterations in 46.9 s (46.9 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 400 node cluster (46 seconds, 954 milliseconds)
ran 1 iterations in 1.1 m (1.1 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 450 node cluster (1 minute, 4 seconds)
ran 1 iterations in 1.6 m (1.6 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 500 node cluster (1 minute, 33 seconds)
ran 1 iterations in 2.3 m (2.3 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 550 node cluster (2 minutes, 20 seconds)

EDIT: The performance issue were mostly just a wrinkle of how I was doing the tests, and that I was stressing the new version more.  After making the tests consistent, its no slower than before.  In fact, after discovering one bottleneck even in the old blacklist code, and fixing it, the new version is 20x faster when there is a bad node and you use the node-blacklist strategy.  I don't fully understand why this is yet, but when there are failures, the advanced blacklist strategy is significantly slower than the "single task" strategy.  (Note that before there are any failures, it is just as fast).  Here its 2x slower on a small example, but with more tasks it can easily be > 5x slower

results running on my laptop using https://github.com/squito/spark/pull/5/commits/456f578121801257bb90b0cbfbd9fa37a117961e
In particular, note how much faster the runs are when (1) we use the advanced blacklist (2) all the bad executors are on one node and (3) there are no nodes with just one bad executor (the run named "COMPARE D bad host with advanced blacklist (12 seconds, 608 milliseconds)")
Iteration 0 finished in 1.1 m
ran 1 iterations in 1.1 m (1.1 m per itr)
[info] - COMPARE D bad exec with simple blacklist (1 minute, 4 seconds)
Iteration 0 finished in 2.4 m
ran 1 iterations in 2.4 m (2.4 m per itr)
[info] - COMPARE D two bad execs with simple blacklist (2 minutes, 21 seconds)
Iteration 0 finished in 1.3 m
ran 1 iterations in 1.3 m (1.3 m per itr)
[info] - COMPARE D bad exec with advanced blacklist (1 minute, 17 seconds)
Iteration 0 finished in 4.2 s
Iteration 1 finished in 4.2 s
Iteration 2 finished in 4.2 s
ran 3 iterations in 12.6 s (4.2 s per itr)
[info] - COMPARE D bad host with advanced blacklist (12 seconds, 608 milliseconds)
Iteration 0 finished in 2.2 m
ran 1 iterations in 2.2 m (2.2 m per itr)
[info] - COMPARE D bad exec and host with advanced blacklist (2 minutes, 10 seconds)

When there are no failures, the blacklist doesn't seem to significantly slow things down.  And on a large cluster, scheduling is already really slow in taskScheduler.resourceOffers, so it doesn't make any real difference.

as of https://github.com/squito/spark/commit/10a83cc73384850b598cddf23de133245c4e0ff5, on my laptop:
ran 111 iterations in 10.0 s (90 ms per itr)
[info] - Scheduling speed -- small job on a small cluster (11 seconds, 49 milliseconds)
ran 3 iterations in 12.7 s (4.2 s per itr)
[info] - COMPARE C Scheduling speed -- large job on a small cluster (12 seconds, 760 milliseconds)
ran 3 iterations in 13.0 s (4.3 s per itr)
[info] - COMPARE C Scheduling speed -- large job on a small cluster with advanced blacklist (13 seconds, 71 milliseconds)
ran 2 iterations in 10.6 s (5.3 s per itr)
[info] - COMPARE A Scheduling speed -- large job on a super node (10 seconds, 617 milliseconds)
ran 3 iterations in 13.2 s (4.4 s per itr)
[info] - COMPARE A Scheduling speed -- large job on 50 node cluster (13 seconds, 262 milliseconds)
ran 2 iterations in 11.1 s (5.6 s per itr)
[info] - COMPARE A Scheduling speed -- large job on 100 node cluster (11 seconds, 142 milliseconds)
ran 1 iterations in 10.7 s (10.7 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 200 node cluster (10 seconds, 676 milliseconds)
ran 1 iterations in 25.8 s (25.8 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 300 node cluster (25 seconds, 787 milliseconds)
ran 1 iterations in 34.2 s (34.2 s per itr)
[info] - COMPARE A: Scheduling speed -- large job on 400 node cluster (34 seconds, 218 milliseconds)
ran 1 iterations in 1.1 m (1.1 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 450 node cluster (1 minute, 3 seconds)
ran 1 iterations in 1.5 m (1.5 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 500 node cluster (1 minute, 28 seconds)
ran 1 iterations in 2.4 m (2.4 m per itr)
[info] - COMPARE A: Scheduling speed -- large job on 550 node cluster (2 minutes, 26 seconds)
ran 2 iterations in 10.6 s (5.3 s per itr)
[info] - COMPARE B: Lots of nodes (10 seconds, 637 milliseconds)
ran 2 iterations in 11.0 s (5.5 s per itr)
[info] - COMPARE B: Lots of executors, one node (11 seconds, 81 milliseconds)
ran 3 iterations in 13.0 s (4.3 s per itr)
[info] - COMPARE B: Super executor (13 seconds, 7 milliseconds)
ran 1 iterations in 58.4 s (58.4 s per itr)
[info] - COMPARE D bad exec with simple blacklist (58 seconds, 433 milliseconds)
ran 1 iterations in 2.2 m (2.2 m per itr)
[info] - COMPARE D two bad execs with simple blacklist (2 minutes, 14 seconds)
ran 1 iterations in 1.2 m (1.2 m per itr)
[info] - COMPARE D bad exec with advanced blacklist (1 minute, 11 seconds)
ran 3 iterations in 12.7 s (4.2 s per itr)
[info] - COMPARE D bad host with advanced blacklist (12 seconds, 756 milliseconds)
ran 1 iterations in 2.1 m (2.1 m per itr)
[info] - COMPARE D bad exec and host with advanced blacklist (2 minutes, 3 seconds)

Some updates on the slow scheduling with lots of nodes:

this was largely an artifact of the testing framework -- when a task completed, it revived offers on all executors, not just the executor that completed.  Fixed here: https://github.com/squito/spark/commit/8ce85969b680424ebda51ff9fe8f6e9ab9a9c4a9 and now there is no noticeable difference in performance

But there was another performance issue this ended up unearthing.  TaskSchedulerImpl.resourceOfferSingleTaskSet indexes into shuffledOffers by index, but that can be really slow if you've got a linkedlist style structure (all that is guaranteed by Seq, and indeed the normal structure you'll get from eg. where its called in CoarseGrainedSchedulerBackend).  This only matters when you first submit tasks to a taskset, though, or when you add a new executor.  With a large cluster, adding and removing executors can happen quite frequently with dynamic allocation, so this can be a notable slowdown.  (though perhaps that call should also use makeOffers(executorId)` instead?  not sure why it doesn't already.)


Broken links in the github docs, v6

Broke pretty much all links. How do I go to all the examples? :( I remember there being lots of examples

We're working on fixing the links. For now:
https://github.com/tannerlinsley/react-table/tree/master/archives/v6-examples
On Tue, Feb 12, 2019 at 11:22 AM Johan de Jager<EMAIL_ADDRESS>wrote:

Broke pretty much all links. How do I go to all the examples? :( I
remember there being lots of examples
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-table/issues/1265, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFUmCV-o7yoOHc8DO1usfwer2GTlifO2ks5vMwZjgaJpZM4a3uOr
.


Add searching in catalog list command

Is your feature request related to a problem?
Right now there are so many applications in the public catalog, and even there might be so many under a single namespace. So it is quite challenging sometimes to find a particular application from the list.
Even though we have search functionalities in UI but not in the CLI.

Describe the solution you'd like
In the current impl command catalog list returns all the app from all the namespace. It can also take <namespace> as arg and print all app from that particular namespace.
My Proposal
Instead of taking the namespace as an argument, we can take that via a flag.
for eg: catalog list napptive will be catalog list -n napptive
Additionally, for searching we can send a Search String as an argument, with this we can match out the application name and print only that will match.
For example:
$./catalog list apache  # We can also add -n namespace-name  to specify a namespace

will print all the app that has "apache" in their name from all the namespace.

Describe alternatives you've considered
As an alternative, we can have a completely different sub command search that will search for an application with the same functionality mentioned above. and we can leave the list command as it is.

/cc @dhiguero

/cc @dhiguero @Carmendelope

Hi @debasishbsws, thanks for opening the issue. Just a couple of questions/comments on the approach. I think it is better to name the command search as it will better reflect the purpose. Do you plan to add the commands using filtering the responses on the cli side, or do you plan to add a new service on the catalog-manager and call that from the CLI?

I am planning to do it on the Cli side.
But I have seen that the admin cli commands there but have not explored that in ditails.
You can suggest to me which one will be a better approach .

Ok, Let's do the implementation incrementally :) Let's do it on the CLI side first, and in the future the team can also help with the backend implementation.

Fixed by #42


As a customer/visitor: view all available products so I can pick from a variety.

Implementation:

[x] BackEnd: Create a model of Products
[x] BackEnd: Create an api route will send all products
[x] FrontEnd: Create a react route '/api/products/'
[x] FrontEnd: Create a component to render all products
[x] FrontEnd: Create a thunk function to use axios to send a request to backend for the data

finished.


[silgen] Rename {was,}InWritebackScope => {was,}InFormalEvaluationScope.

EOM

@swift-ci smoke test and merge

I think the linux failure is not mine.

@swift-ci smoke test linux

I am just going to merge this in the other commit where this was committed. I thought this was going to land first, so I was hoping to test in parallel. But I was wrong = (.


Is the getting started site down?

All down:
http://quantumui.org/
http://quantumui.org/ui/
http://quantumui.org/ui/start/

Yes I have been trying to change hosting provider. Unfortunately, arvixe
suspend my hosting plan due to 10$ :(. I was very angry and changin hosting
provider. It may take some hours.
2015-04-15 9:27 GMT+03:00 Dmitri Zaitsev<EMAIL_ADDRESS>
All down:
http://quantumui.org/http://quantumui.org/ui/http://quantumui.org/ui/start/
—
Reply to this email directly or view it on GitHub
https://github.com/quantumui/quantumui/issues/15.

--
Mehmet Ötkün

Have you tried Github hosting?
No reason to pay for hosting open source projects!

I know, In start I plan the project as commerical, for this reason there
are some c# backend settings for documentation management. After I
transform backend to node, I will host it on github.
2015-04-15 9:41 GMT+03:00 Dmitri Zaitsev<EMAIL_ADDRESS>
Have you tried Github hosting?
No reason to pay for hosting open source projects!
—
Reply to this email directly or view it on GitHub
https://github.com/quantumui/quantumui/issues/15#issuecomment-93219899.

--
Mehmet Ötkün

I imagine you want a clear separation between your open source and commercial parts, so having two separate repos sounds like a good choice.
Documentation is normally generated locally and uploaded as web app. And if you need any database support - try Parse.com!

Actually, I have been preparing a commerical repos which include more components, themes and different configurations. Currently I have some priority issues from transforming documentation app to a github page.
Also there are no more jobs in backend. I just manage routing fallback and call for some ajax demo requests. Currently don't need any database, just some json files I have.


Rotate Image

Hi, Could you provide me an example of image rotation with javascript, Please?

Why you close this open issue ? I also facing the same issue.


Kafka channel dispatcher errors on termination

Describe the bug
We are using Kafka consolidated channel, and running multiple replicas of the dispatcher in Knative 1.1. In the event that a dispatcher pod is restarted, we get "could not connect" to the channel errors throughout the servings publishing messages into the channel.
We are running 3 dispatcher pods, from which only one is terminated/restarted. Once the pod is restarted, we are getting duplicate events as well.
Expected behavior
The service should shut down gracefully and continue from where it left off.
To Reproduce
Push messages to the channel URL and terminate one of the pods of the dispatcher and you will at times not get a 202 accepted response.
Knative release version
1.1
Additional context
On termination, we are not getting errors in the dispatcher, it seems to be exiting gracefully.
{"level":"info","ts":"2022-02-02T13:14:55.339Z","logger":"kafkachannel-dispatcher","caller":"leaderelection/context.go:160","msg":"\"kafka-ch-dispatcher-747bc99d8b-vl9q9_a3957a49-882a-4d6b-9360-ff90d5674768\" has stopped leading \"kafkachannel-dispatcher.knative.dev.eventing-kafka.pkg.channel.consolidated.reconciler.dispatcher.reconciler.00-of-01\"","knative.dev/pod":"kafka-ch-dispatcher-747bc99d8b-vl9q9"}
{"level":"info","ts":"2022-02-02T13:14:55.343Z","logger":"kafkachannel-dispatcher","caller":"controller/controller.go:485","msg":"Shutting down workers","knative.dev/pod":"kafka-ch-dispatcher-747bc99d8b-vl9q9","knative.dev/controller":"knative.dev.eventing-kafka.pkg.channel.consolidated.reconciler.dispatcher.Reconciler","knative.dev/kind":"messaging.knative.dev.KafkaChannel"}

Number of dispatchers running: 3
Kafka CM:
No special configuration, just bootstrap server URL.

We have created a plain and simple NodeJS app that sends requests to a channel URL and we are able to reproduce the same error, so it is not a service-dependent problem.
Furthermore, we have tried to the Kafka channel controller to the latest version as well but we do get the same error.
It seems to us that it is not draining the requests and abruptly terminating. Even though there is code in place in the dispatcher to drain these requests, I don't think those are being adhered to.


feat:[CCM-18219]: Add new governance azure recommendation - delete-orphaned-azure-appserviceplan

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67343d08421d4d7548ab2cb4--harness-developer.netlify.app


Commons chunk plugin

Hi, how can achieve use CommonsChunkPlugin? I have try that with no success:
config-overrides.js:
module.exports = function override(config, env) {

const webpack = require('webpack');

const { CommonsChunkPlugin } = webpack.optimize;

  var commonsChunkPluginCommon = new CommonsChunkPlugin({
    children: true,
    async: 'common',
    minChunks: 2,
  });
  var commonsChunkPluginVendor =  new CommonsChunkPlugin({
    children: true,
    async: 'vendor',
    minChunks: function(module) {
      // this assumes your vendor imports exist in the node_modules directory
      return module.context && module.context.indexOf('node_modules') !== -1;
    },
  });

  config.plugins.push(commonsChunkPluginCommon);
  config.plugins.push(commonsChunkPluginVendor);
  return config;
}

Thanks!

It's been a while since I've used that plugin.  Wondering if this could be a Webpack "1" vs Webpack 2 issue.
The current CRA is still on Webpack "1".
Looking at a manual webpack config I did quite a while ago the setup this quite different to me.
Webpack "1"
https://github.com/timarney/react-setup/blob/master/webpack.config.js

Wow... CRA is using webpack 1? Interesting... 🤔

0.10.0 which is in the master branch is on Webpack 2 but it hasn't release yet.
https://github.com/facebookincubator/create-react-app/milestone/23

Ok!! Thanks ;) Have a nice day ;)
On Wed, 12 Apr 2017 at 19:11, Tim Arney<EMAIL_ADDRESS>wrote:
0.10.0 which is in the master branch is on Webpack 2 but it hasn't release
yet.
https://github.com/facebookincubator/create-react-app/milestone/23
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/timarney/react-app-rewired/issues/29#issuecomment-293646150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWseXL3Gkzt22NaADOJDD-jKP2noGJmks5rvQXHgaJpZM4M7n9D
.


ADR: Update ADR process to use Project board

Update ADR process to use Project board
Context and Problem Statement
Our current ADR process is a bit cumbersome. Let's update it by using Github project boards and PRs!
Decision Drivers

Using just filenames can result in naming collisions if another ADR is updated first
The current "Status" field in the ADR itself can get out of sync with the actual status
It is currently necessary to manually copy a template in order to initiate a PR
The curent process necessitates email list discussion which can become separate from the decision itself

Considered Options

Continuing to use the existing process - this has the above drawbacks
Using a different tool to track issues - this would separate the decision from the discussion

Decision Outcome
We have created:

A new project board
A new issue template
A new process for using them, described below, that supersedes the previous process

Chosen option: use github project boards as described below. Reasoning:

We only update the file when a decision has been reached, thus avoiding naming conflicts
We can use columns in project boards to represent status
We can use the built-in issue template mechanism in github to enforce consistency
Github offers a built-in discussion feature so we can capture discussion next to where the decision is made

Explanation of new process - to be added as a separate description later (updated diagram also to be posted as a comment here):

Draft: To create a new ADR:

Create a new issue in github or zenhub.
Select the template "Architectural Decision Record".
Select "Project", then "Repository", and set it to "Architecture decision records"
This will create a new issue, add it to the "Draft" column (to be done via github actions), and assign the core project maintainers to approve

Screenshots/diagrams: If you need to add diagrams or screenshots/pictures, please add them to the comment section of the issue.

Ready for Discussion : The core project maintainers (for now the USDS folks until we have regularized this process) will review - they will:

Add the "Ready for Discussion" label if the issue is well-formed / has enough detail
Move the issue to the "In Discussion" column
Setup a public comment period - this is the period within which we need to come to a decision (more on this below)

In Discussion : Once the item is in the "In Discussion" column, you have until the period specified to come to a decision. People can leave comments directly on the ticket There are several outcomes:

Consensus In the event of consensus within the expressed timeline, move to the next step
Concerns If there are concerns raised, ensure that those that disagree understand the reasoning behind the decision and address concerns with specific mitigation steps. Request confirmation that concerns have been addressed. If so, move to the next step!
Discuss In the event that disagreement persists, discuss the decision with the group in the next biweekly sync. We will take a vote on next steps (opt-outs are OK!), and move forward.

Decided: Once the comment period has elapsed, move the issue to "Decided". This is where the issue will wait before you have created a Pull Request. Please at this time add one of the following labels:

"Approved" -- Decision Record has been approved
"Rejected" -- Decision Record has been rejected
"Superseded" -- Decision Record has been made obsolete by another record (leave in comment) -- please add this to any record your record supersedes.

Pull Request: Once decided, you should create a pull request to create a file in docs/decisions - name it XXXX where XXXX is one greater than the largest decision record in the directory. Copy and paste the record from the issue. As for diagrams and

We recommend Mermaid for diagrams! Create a file with a .mmd extension and reference filename-mmd.svg in your docs, and Github Actions will automatically create the svg fore you! Preview diagrams with the Mermaid Live Editor.
To keep things organized, create a folder with the name XXXX-files and put supporting ADR material there.

Merge: once the PR has been approved, merge and close

Positive Consequences

ADRs no longer have the above-named limitations

Negative Consequences

We'll need to discuss and socialize these changes.

Pros and Cons of the Options
Leaving as Is

Good, because it's maybe a little less involved
Bad, because it requires keeping a fragile text file up to date, and separates discussion from decision, and is not as integrated into the process

Another tool
e.g. Trello etc.

Good, because there are other tools that are purpose-built to move tickets left -> right
Bad, because this is yet another tool we've got to integrate, and it separates discussion from decision again

Links

Previous ADR process
New project board
New issue template

Updated Diagram:
graph TB
    Start -- Create Issue with ADR Template --> DR["Draft"]
    DR --> RD{"Ready for Discussion?"}
    RD --> |Yes - Maintainer Adds Ready for Discussion label| DI["In Discussion"]
    RD --> |No - Iterate| DR
    DI -- Discuss in Ticket + wait for comment period to expire --> C{Consensus}
    C --> |Yes| PR["Pull Request"]
    C --> |No| A{Concerns Addressed?}
    A --> |Yes| PR
    A --> |No| IP["In Person Discussion"]
    IP --> O{Voting Outcome}
    O --> |Accepted - add label | PR
    O --> |Rejected - add label | PR
    PR --> PRP["Standard PR Process"]
    PRP --> Close

This looks good to me! Thanks for the diagram too!

We will close this issue on Friday May 28th if consensus and/or issues/remediations have been discussed by then!


[Issue]: Improvement "SAP Commissions" to "SAP Incentive Management"

The problem
Due to product name change, update all the places wherever it is mentioned.
Relevant logs
No response

Any recommendations on a new package name?

I went with sapimclient

Also, i have my repo which contains all the information and will keep getting updated..


Fixes a bug when generating scheduled_queries terraform

to: @ryandeivert @blakemotl @chunyong-lin
cc: @airbnb/streamalert-maintainers
Changes

Fixes incorrect input restrictions on URLs
Fixes a bug with scheduled_queries terraform

Testing
Tested on prod yolo!

Coverage remained the same at 95.427% when pulling 5efba6e38ed50df14eb339280f736a33cc4c9ca7 on dw--bug into d31c03c5411d6eed7a06d9109fabae9f7fbc49f2 on release-3-1-0.


Constraints with condition

Hi, I want to add constraints like this:
constraint = cp.sum(cp.multiply(x, a)) > 10 if x*a != 0

where x is decision variable and a is constant. I know if condition and chain constraints are not allowed. But how can I implement this condition?

The way you do it is through binary variables, and it's not documented per se, but from skimming thru the example codes , it can be figured out.
On Tuesday, January 10, 2023 at 07:20:25 PM PST, SightVanish @.***> wrote:
Hi, I want to add constraints like this:
constraint = cp.sum(cp.multiply(x, a)) > 10 if x*a != 0
where x is decision variable and a is constant. I know if condition and chain constraints are not allowed. But how can I implement this condition?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The way you do it is through binary variables, and it's not documented per se, but from skimming thru the example codes , it can be figured out.  On Tuesday, January 10, 2023 at 07:20:25 PM PST, SightVanish @.> wrote: Hi, I want to add constraints like this: constraint = cp.sum(cp.multiply(x, a)) > 10 if xa != 0 where x is decision variable and a is constant. I know if condition and chain constraints are not allowed. But how can I implement this condition? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.*>

yep, you are right. Here is a brief example:
x = cp.Variable(shape=10, boolean=True)
a = np.array([1, 0, 1, 1, 1, 1, 0, 0, 0, 0])

solved, see here.


Import truncates keys, resulting in empty keys that yields error

If the given URL to import from is itself a file, e.g. s3://bucket/some/path/to/key/ -> file, lakeFS will truncate the given URL and will iterate over the keys past it (including it), so it will also try to store the empty key but will fail since pebble does not allow empty keys.
The returned error looks like this:
writing range from entry iterator: writing record: setting key and value: pebble: keys must be added in order: #0,DEL, #0,SET

Yap - lakeFS like S3 doesn't accept empty keys. We should prettify this error - but there's not much we can do given that replacing that key is an awkward ux.

Note that this issue occurs when you import a directory marker (empty name) to the root branch - an empty on the branch level fails.


Update OverlayHub

Two features are being added:

Request Limit: Rejects session-key and registration requests if they exceed a configurable limit.
Unique Session-Key Request: Allows a session-key request from a new connection to succeed only once. Subsequent requests from the same connection will be rejected.

Does it resolve #2: Unique Session-Key Request?


blank page

Hi, looks really interesting project.
I follow the installation using conda env and when I run cfdraw run and I go to http://localhost:5123/ I get a blank white page ;-(
What am I missing

Hi! Are you running the cfdraw run in the right place? Like, do you have an app.py where your cfdraw run takes place?
If it does, it might be a bug - then could you please open the console and see if any error messages are logged, thanks!

Ah, then I found another possibility: I wrongly deleted the 0.0.1a2 version on pypi, so you may download the 0.0.1a1 version, which is error prone.
In this case, since I just published a 0.0.1a3, you can try:
pip install -U carefree-creator

to upgrade the package and see if everything works!

Ah, then I found another possibility: I wrongly deleted the 0.0.1a2 version on pypi, so what you had downloaded was maybe the 0.0.1a1 version, which is error prone.
In this case, since I just published a 0.0.1a3, you can try:
pip install -U carefree-creator

to upgrade the package and see if everything works!

Yes, I updated it and now it is working... thank you :-)

Great! Hope you have fun and feel free to send feedbacks at anytime!


[Bug]: Unhandled exception Puppeter

Version of the software
0.1.26 [Beta]
Operating system
windows server 2019
Browser / Native
95.0.4638.69
What happened?
A bug happened!
Unhandled exception thrown on 11/5/2021 12:12:20 AM
System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (Unable to write data to the transport connection: An established connection was aborted by the software in your host machine..)
---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine..
---> System.Net.Sockets.SocketException (10053): An established connection was aborted by the software in your host machine.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.CreateException(SocketError error, Boolean forAsyncThrow)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.SendAsyncForNetworkStream(Socket socket, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.SendAsyncForNetworkStream(ReadOnlyMemory1 buffer, SocketFlags socketFlags, CancellationToken cancellationToken)    at System.Net.Sockets.NetworkStream.WriteAsync(ReadOnlyMemory1 buffer, CancellationToken cancellationToken)
at System.Net.Http.HttpConnection.WriteToStreamAsync(ReadOnlyMemory1 source, Boolean async)    at System.Net.Http.HttpConnection.RawConnectionStream.WriteAsync(ReadOnlyMemory1 buffer, CancellationToken cancellationToken)
at System.Net.WebSockets.ManagedWebSocket.SendFrameLockAcquiredNonCancelableAsync(MessageOpcode opcode, Boolean endOfMessage, ReadOnlyMemory1 payloadBuffer)    at System.Net.WebSockets.ManagedWebSocket.SendFrameAsync(MessageOpcode opcode, Boolean endOfMessage, ReadOnlyMemory1 payloadBuffer, CancellationToken cancellationToken)
at System.Net.WebSockets.ManagedWebSocket.SendPrivateAsync(ReadOnlyMemory1 buffer, WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken cancellationToken)    at System.Net.WebSockets.ManagedWebSocket.SendAsync(ArraySegment1 buffer, WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken cancellationToken)
at System.Net.WebSockets.ClientWebSocket.SendAsync(ArraySegment1 buffer, WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken cancellationToken)    at PuppeteerSharp.Transport.WebSocketTransport.<>c__DisplayClass21_0.<SendAsync>g__SendCoreAsync|0()    at PuppeteerSharp.Helpers.TaskQueue.Enqueue(Func1 taskGenerator)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at PuppeteerSharp.Helpers.TaskQueue.Enqueue(Func1 taskGenerator)    at PuppeteerSharp.Transport.WebSocketTransport.SendAsync(String message)    at PuppeteerSharp.Connection.RawSendASync(Int32 id, String method, Object args, String sessionId)    at PuppeteerSharp.Connection.SendAsync(String method, Object args, Boolean waitForCallback)    at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)    at PuppeteerSharp.Connection.SendAsync(String method, Object args, Boolean waitForCallback)    at PuppeteerSharp.Page.CloseAsync(PageCloseOptions options)    at PuppeteerSharp.Page.Dispose(Boolean disposing)    at PuppeteerSharp.Page.Dispose()    at RuriLib.Models.Bots.BotData.DisposeObjectsExcept(String[] except)    at RuriLib.Models.Jobs.MultiRunJob.<>c.<<-ctor>b__160_0>d.MoveNext()    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)    at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)    at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)    at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)    at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)    at Microsoft.CodeAnalysis.Scripting.ScriptStateTaskExtensions.CastAsync[S,T](Task1 task)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at Microsoft.CodeAnalysis.Scripting.Script1.RunSubmissionsAsync(ScriptExecutionState executionState, ImmutableArray1 precedingExecutors, Func2 currentExecutor, Func2 catchExceptionOpt, CancellationToken cancellationToken)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState.RunSubmissionsAsync[TResult](ImmutableArray1 precedingExecutors, Func2 currentExecutor, StrongBox1 exceptionHolderOpt, Func2 catchExceptionOpt, CancellationToken cancellationToken)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at Submission#0.<>d__0.MoveNext()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at RuriLib.Blocks.Puppeteer.Page.Methods.PuppeteerNavigateTo(BotData data, String url, WaitUntilNavigation loadedEvent, String referer, Int32 timeout)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at PuppeteerSharp.FrameManager.NavigateFrameAsync(Frame frame, String url, NavigationOptions options)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task1.TrySetResult(TResult result)    at System.Threading.Tasks.Task.TwoTaskWhenAnyPromise1.Invoke(Task completingTask)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at PuppeteerSharp.FrameManager.NavigateAsync(CDPSession client, String url, String referrer, String frameId)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at PuppeteerSharp.CDPSession.SendAsync[T](String method, Object args)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetException(Exception exception, Task1& taskField)
at PuppeteerSharp.CDPSession.SendAsync(String method, Object args, Boolean waitForCallback)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task.FinishSlow(Boolean userDelegateExecute)
at System.Threading.Tasks.Task.TrySetException(Object exceptionObject)
at System.Threading.Tasks.TaskCompletionSource1.TrySetException(Exception exception)    at PuppeteerSharp.CDPSession.Close(String closeReason)    at PuppeteerSharp.Connection.ProcessIncomingMessage(ConnectionResponse obj)    at PuppeteerSharp.Connection.ProcessMessage(MessageReceivedEventArgs e)    at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)    at PuppeteerSharp.Connection.ProcessMessage(MessageReceivedEventArgs e)    at PuppeteerSharp.Helpers.TaskQueue.Enqueue(Func1 taskGenerator)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
at PuppeteerSharp.Helpers.TaskQueue.Enqueue(Func1 taskGenerator)    at PuppeteerSharp.Connection.Transport_MessageReceived(Object sender, MessageReceivedEventArgs e)    at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)    at PuppeteerSharp.Connection.Transport_MessageReceived(Object sender, MessageReceivedEventArgs e)    at PuppeteerSharp.Transport.WebSocketTransport.GetResponseAsync(CancellationToken cancellationToken)    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)    at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)    at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)    at System.Threading.Tasks.Task1.TrySetResult(TResult result)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetExistingTaskResult(Task1 task, TResult result)
at System.Net.WebSockets.ManagedWebSocket.ReceiveAsyncPrivate[TWebSocketReceiveResultGetter,TWebSocketReceiveResult](Memory1 payloadBuffer, CancellationToken cancellationToken, TWebSocketReceiveResultGetter resultGetter)    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)    at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)    at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)    at System.Threading.Tasks.Task1.TrySetResult(TResult result)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetExistingTaskResult(Task1 task, TResult result)
at System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder.SetResult()
at System.Net.WebSockets.ManagedWebSocket.EnsureBufferContainsAsync(Int32 minimumRequiredBytes, CancellationToken cancellationToken, Boolean throwOnPrematureClosure)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task1.TrySetResult(TResult result)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetExistingTaskResult(Task1 task, TResult result)    at System.Net.Http.HttpConnection.RawConnectionStream.ReadAsync(Memory1 buffer, CancellationToken cancellationToken)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(IAsyncStateMachineBox box, Boolean allowInlining)
at System.Threading.Tasks.Task.RunContinuations(Object continuationObject)
at System.Threading.Tasks.Task1.TrySetResult(TResult result)    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.SetExistingTaskResult(Task1 task, TResult result)    at System.Net.Http.HttpConnection.ReadBufferedAsyncCore(Memory1 destination)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.AsyncStateMachineBox1.MoveNext(Thread threadPoolThread)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.InvokeContinuation(Action`1 continuation, Object state, Boolean forceAsync, Boolean requiresExecutionContextFlow)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.OnCompleted(SocketAsyncEventArgs _)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pNativeOverlapped)
--- End of stack trace from previous location ---
--- End of inner exception stack trace ---
at PuppeteerSharp.Helpers.TaskQueue.Enqueue(Func`1 taskGenerator)
at PuppeteerSharp.Connection.SendAsync(String method, Object args, Boolean waitForCallback)
--- End of inner exception stack trace ---
Relevant LoliCode if needed
No response

This happened in native OB2 not in the web version

This happened in native OB2 not in the web version

Should I make new thread?

Nono it's fine, it was just to clarify

This should be resolved in the next version https://github.com/openbullet/OpenBullet2/commit/30d2b526b9559ccd2fcfaa00f8f367608c6431e7


Is the UserClient still working?

i'm getting unauthorized even if i entered the correct API key and secret key.
{'id': 1, 'method': 'private/get-order-history', 'code': 10002, 'message': 'UNAUTHORIZED', ...}

it seems that the Rust version is working but I still can't figure out what's different. https://github.com/maxpowel/rs-crypto-com-exchange

Did you call client.authenticate() before send private message?
Example on the README.md omitted this
await client.authenticate()
event = await client.next_event()
print(event)

Did you call client.authenticate() before send private message? Example on the README.md omitted this
await client.authenticate()
event = await client.next_event()
print(event)

You are right, I have just updated the README.md


feature request: Array sorting

There are many cases where hard-coded arrays must be in order but is manually enforced.
I think ESLint can be taken advantage of to automate it by opting-in via comments on the specific array:
/* eslint-enable array-order */
/* eslint array-order: ["error", "asc"] */
const array = [1, 2, 3];
/* eslint-disable array-order */

Further examples:

So, I'm not interested in implementing this feature into this plugin as it goes against the philosophy of this plugin which is to sort properties, imports, etc. without changing behavior of the runtime code.  Now, to be fair all sorting does have runtime impact as the order of object keys can be important if you are depending on that specific order when iterating over the object properties, but generally speaking it doesn't have a runtime impact.  However, this proposal will almost always have high impact to the code given the fact that arrays are primarily an ordered list of items.
Now, your proposal is reasonable from the standpoint of only sorting when you specify it with comments, but that's a pretty odd way to use an ESLint rule in my opinion as typically comments are going to be for disabling or making minor modifications rather than being the primary way of using a rule.
This coupled with the lack of use cases I see for most users of this plugin, I'm going to close this as I'm not interested in this being part of this plugin.

Understandable. Thank you for the thorough explanation!


Adding Vowpal Wabbit Algorithm

Issue #, if available: NA
Description of changes:
Adding VowpalWabbit algorithm as a default algorithm in Autogluon
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1422-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1422/1/index.html

Job PR-1422-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1422/3/index.html

@killerswitch
Please refer to a PR I opened in your branch to address my latest review comments + add time_limit support: https://github.com/killerSwitch/autogluon/pull/1
Once this PR is merged in, we should be ready to run a benchmark.

Job PR-1422-8 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1422/8/index.html


Gradient averaging mechanism on the validator side

Implemented averaging gradient mechanism on the validator side

[x] Extract gradients from the valid miner responses
[x] Averaged gradients and propagate to miners

Need to implement gradient propagation to all miners

I will create a new ticket and pr for that

Got it
Reviewed and merged


Don't wait for nix show-derivation when deciding whether to provide UI feedback

Before this patch, we diffed the output of nix show-derivation to determine whether to attempt to rebuild the staticFiles derivation. Unfortunately, show-derivation often takes a significant amount of time and seems to do much of the same work involved in building the derivation. While we're waiting for the results of show-derivation to decide whether to embark upon and notify the user of an asset rebuild, the user gets no indication that we've noticed their change.
The tradeoff with this patch is that we'll be a little noisier: changes that don't actually impact the derivation but are within the project directory will cause no-op rebuilds for which the user will receive notifications. However, this is probably superior to a long, brooding silence while we determine whether to rebuild or not. To mitigate the problem, we ignore some common temp files that editors leave lying around, and limit our file-watching to the frontend, common, backend, and static folders.
I have:

[x] Based work on latest develop branch
[x] Followed the contribution guide
[ ] Looked for lint in my changes with hlint . (lint found code you did not write can be left alone)
[ ] Run the test suite: $(nix-build -A selftest --no-out-link)
[x] Updated the changelog
[ ] (Optional) Run CI tests locally: nix-build release.nix -A build.x86_64-linux --no-out-link (or x86_64-darwin on macOS)

Currently experimenting with using hnix to parse and evaluate the static asset derivation, with the hope of only watching the files that the evaluation cares about. That'll get rid of all this ignoredFiles stuff.

Currently experimenting with using hnix to parse and evaluate the static asset derivation, with the hope of only watching the files that the evaluation cares about. That'll get rid of all this ignoredFiles stuff.

Related: https://github.com/haskell-nix/hnix/pull/804

Related: haskell-nix/hnix#804
Once that PR is done, we can try to use that functionality to implement a more nuanced nix watcher.

Not doing this.


Make warning label permanently visible

Pull Request Description

Close #9125

Display the new warning icon to the left of the node, when the node is not being hovered over.

Important Notes
None
Screenshots
Not hovered:

Hovered:

the warning icon MUST be hidden when the node is hovered, otherwise it overlaps with the node name.

this is fine, as the full warning is shown on hover anyway.

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

nvm fixed

nvm. we have an actual icon (plus a more proper spec) for this task now

"re-requesting review" from kaz mainly to remove the approval - this is because this PR has been completely reimplemented because the new icons have now been merged in.

@jdunkerley so i just noticed you mentioned it should appear to the left of the menu, but i'm not sure it's a good idea (see screenshots). is this fine? or perhaps do you have a better solution? (should the name be shifted left too?)

also - should the new icon also be used for the warnings viz? or should that be removed completely?


DOC-3187-bugbash

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Cache Azure Policy Aliases

Related to #181, we should cache Azure Policy Aliases in a JSON file
The format could be something like below:
"Microsoft.AlertsManagement": {
    "smartDetectorAlertRules": {
      "locations": "global",
      "aliasMappings": {
        "Microsoft.AlertsManagement/smartDetectorAlertRules/actionGroups": "properties.actionGroups",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/actionGroups.customEmailSubject": "properties.actionGroups.customEmailSubject",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/actionGroups.customWebhookPayload": "properties.actionGroups.customWebhookPayload",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/actionGroups.groupIds": "properties.actionGroups.groupIds",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/actionGroups.groupIds[*]": "properties.actionGroups.groupIds[*]",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/description": "properties.description",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector": "properties.detector",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.description": "properties.detector.description",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.id": "properties.detector.id",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.imagePaths": "properties.detector.imagePaths",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.imagePaths[*]": "properties.detector.imagePaths[*]",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.name": "properties.detector.name",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.parameters": "properties.detector.parameters",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.supportedResourceTypes": "properties.detector.supportedResourceTypes",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/detector.supportedResourceTypes[*]": "properties.detector.supportedResourceTypes[*]",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/frequency": "properties.frequency",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/scope": "properties.scope",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/scope[*]": "properties.scope[*]",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/severity": "properties.severity",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/state": "properties.state",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/throttling": "properties.throttling",
        "Microsoft.AlertsManagement/smartDetectorAlertRules/throttling.duration": "properties.throttling.duration"
      },
      "apiVersions": [
        "2018-02-01-privatepreview",
        "2019-03-01",
        "2019-06-01",
        "2021-04-01"
      ]
    }

Which would allow us to quickly lookup property paths for a given alias.
The other option was to use Get-AzPolicyAlias, but this would require an API call everytime an alias is needed, which would lead to slower performance.

@ArmaanMcleod Let's be aware of any performance cost of the index. We don't really want to do any iteration down resource types to find the aliases.

I think performance cost should be fine, since we can get namespace & resource type from the alias, then index the full alias to get the path.
Another idea is not even caring about the namespace and resource types, and just dumping aliasMappings as a simple key:value object in the file. That would make things simpler.

@ArmaanMcleod Yes, that might reduce memory and allocations.

@BernieWhite The issue with it is some aliases like Microsoft.Compute/imageId are duplicated across resources. Wouldn't reliably be able to keep alias name as a key for everything.
I think I will keep the first approach for now and think of a better way down the line.

I guess another thing to consider is if we should replace the aliases with the path when assignments are exported, or if that should be done when the assignments are visited.

I guess another thing to consider is if we should replace the aliases with the path when assignments are exported, or if the aliases should be expanded when the assignments are being visited.
To me it would be easier to just convert them when JSON rules are being emitted after the policy rule is visited.

Agreed.

Will also add a github actions workflow for this.


Swagger doesn't generate swagger.json

I follow this instruction step by step with default ASP.NET Core web application (MVC) but swagger doesn't generate swagger.json- it's empty. Target framework .NET Core 2.0.

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

ID: 14fce65f-1337-58cb-2193-8d8e0e62792d
Version Independent ID: 59222460-a971-e76e-4fe9-23d4d7d768ee
Content: Get started with Swashbuckle and ASP.NET Core
Content Source: aspnetcore/tutorials/getting-started-with-swashbuckle.md
Product: aspnet-core
GitHub Login: @zuckerthoben
Microsoft Alias: scaddie

Hey,
Any solution on this?


re-architecting Anchors

some tests were ignored
need improvement

Many syntax of Anchors was changed by re-architecting.
It can be used without difficulty in most general usage
but there is currently no way to use a syntax like Anchors(.lead, .trailing) which is very useful and is also required by some tests.
Do you have any idea?

some tests were ignored
need improvement

Many syntax of Anchors was changed by re-architecting. It can be used without difficulty in most general usage but there is currently no way to use a syntax like Anchors(.lead, .trailing) which is very useful and is also required by some tests.
Do you have any idea?

how about this for interface?
may be we should some of protocols for interface
Anchors.combine(x: ..., y: ..., size: ...) // (x.contaner + y.container + size.container).cap[shoe, ...]


[BUG] tst-reflect: You call getType() method directly. You have probably wrong configuration, because tst-reflect-transformer package should replace this call by the Type instance.

Describe the bug
I have been using this library with NestJS and Typescript, with essentially the same configurations mentioned in readme, to instantiate my objects at runtime.
Observation:
The code executes like 1/5 runs, and fails otherwise with the error : tst-reflect: You call getType() method directly. You have probably wrong configuration, because tst-reflect-transformer package should replace this call by the Type instance.
The code causing the problem

Mapper.map(newObject, getType<MyType>()) as MyType

To Reproduce
Steps to reproduce the behavior:

npx ttsc
npm start to run my NestJS

Expected behavior
Code shall execute successfully each time without any issues
Runtime (please complete the following information):

Node.js version: 17.4.0
npm : 8.18.0
TypeScript version: ^4.7.4
Compiler: [e.g. ttypescript] ^1.5.13
Bundler: [e.g. Webpack@5] NA

Additional context
Add any other context about the problem here.

Hi @Manik-Jain,
I'm expecting that your npm start invokes nest start.
The problem is that nest start executes build too (maybe not always; maybe only when there are some changes; probably it builds always but incremental build is enabled so it does not rebuild when there are no changes). But when the build is initiated by nest, it does not call ttsc it calls just tsc; or webpack in case of monorepo.
So in that case it will not use the tst-reflect-transformer. So I looked up this issue https://github.com/nestjs/nest-cli/issues/1208.
And the answer:

If you want to use a different compiler, simply use it directly (without relying on nest build)

is quite... pointless... since nest start executes the build too.
So I was looking for some options to disable that building by nest start or some else configuration and I found this issue https://github.com/nestjs/nest-cli/issues/725

If you don't need to compile the code, run node dist/main.

So you have to use build: npx ttsc, start: node dist/main and there should be no problem.
Or second option is to use ts-patch, which will override typescript package so the "native" tsc cmd will invoke compilation with transformer, every time. So you can use nest build and nest start cmds.

@Manik-Jain Closing for now, it helped I suppose. Let me know if it doesn't.

Related https://github.com/Hookyns/tst-reflect/issues/37

Hi @Hookyns  thanks for suggesting the work around, it worked for me.
However, I'm running into issues with jest tests. Is there something that you can suggest?

Your tests? What kind of issues?
BTW Jest is configured in this repo and it works just fine.

I'm running the tests with ttsc -p tsconfig.json && jest  with following jest configuration:
"jest": {
    "moduleFileExtensions": [
      "js",
      "json",
      "ts"
    ],
    "rootDir": "src",
    "testRegex": ".*\\.spec\\.ts$",
    "transform": {
      "^.+\\.(t|j)s$": "ts-jest"
    },
    "collectCoverageFrom": [
      "**/*.(t|j)s"
    ],
    "coverageDirectory": "../coverage",
    "testEnvironment": "node"
  }

tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "declaration": true,
    "removeComments": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "target": "es2017",
    "sourceMap": true,
    "outDir": "./dist",
    "baseUrl": "./",
    "incremental": true,
    "skipLibCheck": true,
    "strictNullChecks": false,
    "noImplicitAny": false,
    "strictBindCallApply": false,
    "forceConsistentCasingInFileNames": false,
    "noFallthroughCasesInSwitch": false,
    "useDefineForClassFields": true,
    "allowJs": true,
    "plugins": [
      {
          "transform": "tst-reflect-transformer"
      }
  ]
  },
  "ts-node": {
    "compiler": "ttypescript"
},
}

And getting the following error for each line of code that uses tst-reflect
[ERR] tst-reflect: You call getType() method directly. You have probably wrong configuration, because tst-reflect-transformer package should replace this call by the Type instance.
If you have right configuration it may be BUG so try to create an issue.
If it is not an issue and you don't want to see this debug message, create field 'tst-reflect-disable' in global object (window | global | globalThis)

Your Jest configuration use TS files from src directory.  You have to use your JS files from dist directory.

I had a similar issue. I run my tests from the *.ts files with ts-jest. Looking at your information above @Manik-Jain there is two more things I had to do (using the current alpha releases or rttist and tst-reflect*):

Configure ts-jest to use ttypescript (instead of standard typescript), such that it uses the transformer configured in tsconfig.json. It can be configure like described here https://github.com/cevek/ttypescript#jest-ts-jest which is the outdated ts-jest config format, the new one would be replacing your transform config above "transform": {"^.+\\.(t|j)s$": "ts-jest"} with "transform": {"^.+\\.(t|j)s$": ["ts-jest", { "compiler": "ttypescript" }]}.

Make sure rttist's metadata is available. My project is configured with rootDir ./src and outDir ./bin in tsconfig. I am not sure why, but my tests look in src for the metadata causing them to fail. If I build normally with ttsc and run the built project with node, everything is fine, i.e., the metadata is correctly looked up from bin. I could fix the issue by setting rttist metadata.metadataTypelibPath option to ../bin/metadata.typelib.js (default: metadata.typelib.js). To do so, I replaced my transformer config in ts config with the snippet below. This makes my testing setup work and does not break the built application.

{
    "transform": "tst-reflect-transformer",
    "reflection": {
        "metadata": {
            "metadataTypelibPath": "../bin/metadata.typelib.js"
        }
    }
}


Is this repo still maintained?

The maintainer hasn't responded to neither PRs nor Issues for more than six months.
Yet the project is still asking for donations
https://patreon.com/fusejs
https://www.paypal.com/paypalme2/kirorisk
We need to know if this repo is going to be maintained so that we know whether it's worth sponsoring this project or if we should fork it and continue ourselves.

From what I can tell it looks like he only actively maintains FuseJS which I assume is the original project and not this Swift version. So I'd say fork the Swift version if you want to and do it yourself or try out the JS version that is actively maintained.

It's been over a month and still no response from the repo owner. No response on any other issue or PR. At this stage it's safe to assume that THIS REPO IS ABANDONWARE
@krisk you are setting wrong expectations by not archiving this repo. Please consider archiving this repo.

Yep, July 2021 and this repo still looks abandoned.

@arielelkin Any ideas on a good swift alternative to use?

@arielelkin Any ideas on a good swift alternative to use?


Protocol & Amendments [IG]

See ticket #118
Consider to include Geographic scope or address separately to also be able to link from other places

Updated IG accordingly: See https://wiki.cdisc.org/display/USDMIGv3/Study%2C+Protocols+and+Amendments


Fix documentation links from plugin

Fixes a number of broken documentation links for the plugin.
All the github urls have been checked.

lgtm


HIVE-23988: Remove unused method

What changes were proposed in this pull request?
remove unused method in FunctionRegistry.java
Why are the changes needed?
improve hive code quality
Does this PR introduce any user-facing change?
No
How was this patch tested?
unit test

@jcamachor Could you help review ? Please kindly corrected me if i miss sth. Thanks in advance.


Use bundler-inject

@agrare Please review.

@Fryguy the specs failing are unrelated and have been failing for a while, I added https://github.com/ManageIQ/topological_inventory-amazon/pull/13/commits/a78a50c610ecb91cef32a00edb303e38ca699c8c to fix them as part of https://github.com/ManageIQ/topological_inventory-amazon/pull/13


Asset paths

During deployments both the old and new containers will be active for a small period of time. There also may be lagging requests for older CSS and JS after the deployment.
This can lead to 404s if a request for old assets hits a new container or visa-versa.
This PR makes sure that both sets of assets are available throughout the deployment from before the new version of the app is booted.
This can be configured by setting the asset path:
asset_path: "/rails/public/assets"

The process is:

We extract the assets out of the container, with docker run, docker cp, docker stop. Docker run sets the container command to "sleep" so this needs to be available in the container.
We create an asset volume directory on the host for the new version of the app on the host and copy the assets in there.
If there is a previous deployment we also copy the new assets into its asset volume and copy the older assets into the new asset volume.
We start the new container mapping the asset volume over the top of the container's asset path.

This means the both the old and new versions have replaced the asset path with a volume containing both sets of assets and should be able to serve any request during the deployment. The older assets will continue to be available until the next deployment.
h/t to @jeremy for simplifying the original idea for this 🙏
https://github.com/basecamp/kamal-site/pull/26

Nice work, is there a recommended way to point to this volume for caching with precompilation? As in utilizing this asset volume to reduce asset compilation time. I usually have something like this in my Dockerfile:
RUN --mount=type=cache,id=bld-assets-cache,sharing=locked,target=tmp/cache/assets \
    ./bin/rails assets:precompile

Nice work, is there a recommended way to point to this volume for caching with precompilation? As in utilizing this asset volume to reduce asset compilation time. I usually have something like this in my Dockerfile:

The asset volumes are on the hosts that are deployed to, not where we build (unless you are using the same host for both).
You could use a similar approach to this PR and extract the assets from the latest image and copy them onto the cache mount in a pre-build hook. But if you are usually persisting the cache between builds I'm not sure that is going to buy you that much.


feat!: Rename collections extension to collections.list

In preparation to moving arrays out of the prelude (#1497), this PR renames the collections extension to collections.list. Arrays will then be called collections.array.
I renamed the related module and struct definitions as well.
BREAKING CHANGE: collections extension renamed to collections.list

No... moved files + struct renames breaks the diff move detection :/


Split alt token into 3

lightseagreen

:tada: This issue has been resolved in version 0.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated grpc device code for ModSpectrum APIs and Attributes

What does this Pull Request accomplish?
Updates niRFmxBT in grpc-device to 24.3
Updates the Grpc Device Code for Mod spectrum APIs and attributes.
Updates the Grpc Device Code for Channelsoundingsyncsequence attribute enum update to payload pattern
Why should this Pull Request be merged?
Updated to match the upcoming release of niRFmxBt 24.3.0
What testing has been done?
Manually inspected generated files..
Manually inspected nirfmxbluetooth.proto file

This will match the Upcoming RFmx 24.3 BT Release.

Can you update config.py and the README to bump the RFmx BT version to 24.3?

Updated the Version.

Looks good. FYI there's a Bug right now preventing submission in the repo (it's what's causing the validate_python step to fail). You'll have to wait for that to go in before getting a passing build and ability to merge.
Update: That bug was fixed but I think you'll have to merge main to get those fixes into this branch and the CI build to pass.

Looks good. FYI there's a Bug right now preventing submission in the repo (it's what's causing the validate_python step to fail). You'll have to wait for that to go in before getting a passing build and ability to merge.
Update: That bug was fixed but I think you'll have to merge main to get those fixes into this branch and the CI build to pass.

The Python Validation step is now passed Successfully. Looks like the CI/build_desktop/Windows Build Required step failed.

The Python Validation step is now passed Successfully. Looks like the CI/build_desktop/Windows Build Required step failed.

Oh sorry, I should've mentioned this when you updated config.py. It'll cause the .proto to be updated with that new version at the top of the file. So you'll need to rebuild locally and push up the changed .proto file so the build doesn't complain about a mismatch between what's in the branch's generated folder and what the CI build produces.

@maxxboehme Can you review this PR as this PR is being hold from long time because your review is pending on this


Fix a flaky concurrent test with correct locking

The recent refactoring to clone the bare registry left in an accidental path
where index checkouts could clobber one another. This commit updates the logic
with proper locking and attempt ordering, attempting a full retry of the open
operation after the index locked.

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 7b44acc has been approved by alexcrichton

:hourglass: Testing commit 7b44acc with merge 8e35fd7...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 8e35fd7d8b7b82ff09ee9b7178201a8b01843b98 to master...


Subject name mismatch between metadata and file name

Sometimes the metadata does not match the saved json file name. I noticed this bug during a sanity check in my data pipeline:

Looking at the raw json file, it appears that the subject_id field was changed within a session:

I guess what happened was that the RA corrected the subject_id after session start. This will be a huge problem for data integrity. To avoid this:

I'll ask RAs, whenever they find a metadata error, to stop the session, clear the data, and start again.
@XX-Yin Please disable those metadata fields in the GUI when a session is running. A better way maybe to disallow this kind of trial-by-trial changes in metadata.

Thanks Han. Yes, I agree to disable these metadata fields during running.


Cache SubmarinerConfig only on success

Only cache the config on successful operations, otherwise we should
retry cloud prepare/cleanup as long as it wasn't successful.
Resolves https://github.com/stolostron/backlog/issues/24502
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

@mkolesnik can you please link it to https://github.com/stolostron/backlog/issues/24502? You can edit the first comment and use the "Fixes" keyword. Thanks!

/retest

See https://github.com/stolostron/submariner-addon/issues/455 for my notes on the test failures (which we’ve seen elsewhere).

/approve

@skitt @tpantelis Maxim reported https://github.com/stolostron/backlog/issues/24502 with 2.5.2. Can you please cherry-pick this PR into release-2.5? Hopefully it's a simple backport that can be handled automatically

/cherrypick release-2.5


The problem after a long conversation

After a very long conversation, I found this error. Is there any way to solve this problem now? Or is this the limit?

Same as me. It seems like some kind of limitations.

There's a TODO in BingAIClient. Need to count the tokens and remove older messages. Are you able to check how many tokens the conversation used before that error occurred?

There's a TODO in BingAIClient. Need to count the tokens and remove older messages. Are you able to check how many tokens the conversation used before that error occurred?

Yes. I now clearly know that when the total number of words I chat exceeds 20,000 Chinese characters, there will be an error. Since a Chinese character generally occupies two tokens, I think there will be an error when it exceeds 40,000 tokens. This problem is easy to reproduce. You send an article with about 40,000 words at once, and I think it will definitely report an error.


Support for dotnetcore

Here is the start of adding support for core.
I'm starting a new project in a separate directory while I get the project to work.  Once it works, I'll copy it over the existing directory and bump the version to 3.0.
All of the pre-core support will be on version 2.x.
This will resolve #35

Is it close to be shipped in Nuget?

Hi @darrencauthon!.
I'm trying to add Automoq to awesome-net-core here => https://github.com/thangchung/awesome-dotnet-core/pull/130
Will Automoq have support for netStandard2.0?

Okay, please let me know when everything is okay. I will have a look at the source code later. Thank you 👍


Google Chrome extension secretly redirect users to ad pages

https://nakedsecurity.sophos.com/2016/04/06/chrome-extension-was-secretly-redirecting-users-to-ad-pages/

Reddit user Scarazer wrote that he’d found the same malicious code infecting a number of other Google Chrome extensions, including Chrome Currency Converter, Web Timer, User-Agent Switcher, Better History, 4chan Plus, and Hide My Adblocker.
As of Tuesday afternoon, the only extension in that list that had been removed from Google’s Chrome web store was 4chan Plus. Google also banned Better History after users encouraged each other to write reviews reporting it.

That's not totally unexpected. Users ought to exercise caution when installing software from the Internet, and this certainly includes browser extensions. I'll try to make this point clearer the next time I take a pass at updating the guide. Thanks for bringing this to attention.


Dark Mode button

I can help you add a dark and light mode button to make the website look good.
Please let me work on this issue under GSSOC'23.

@Tathagt  OK! go ahead

Can you please assign me this issue under GSSOC'23?

@KamalSritha-04 sure, go ahead

Hey   @KamalSritha-04 want to collaborate?

@Tathagt any update?

This issue has been inactive for a long time
I would like to work on this issue
Please assign

@SaadAnzar I am working on it

@Tathagt okay, but you need to speed up

@SaadAnzar  Sorry my exams were going on that's why I was unable to work on this.
I have added a button to change the theme from light to dark but its still not changing the theme.
Please tell me what changes need to be done.

@Tathagt share the code snippets and also screenshots


Implements the Schrödinger-Föllmer algorithm.

See this:
https://github.com/blackjax-devs/blackjax/issues/601

I dont know about this algorithm so I will just assume Adrian you know what you are doing haha


July 2023 Release JDK17 triage

Release Summary Report for release-openjdk17-pipeline
Report generated at: Wed, 19 Jul 2023 01:48:54 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk17-pipeline/32/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk17u" build number 1601 at 7/18/2023, 4:43:11 PM

Platforms
Details
Status

aarch64_linux
link
✔

aarch64_mac
link

arm_linux
link
✔

ppc64_aix
link

ppc64le_linux
link

s390x_linux
link

x86-32_windows
link

x86-64_alpine-linux
link

x86-64_linux
link
✔

x86-64_mac
link

x86-64_windows
link

aarch64_linux
1 testcase failure (security/infra/java/security/cert/CertPathValidator/certification/AmazonCA.java), was excluded for all platforms, not sure why is being run, consider non-blocking

arm_linux
1 testcase failure (security/infra/java/security/cert/CertPathValidator/certification/AmazonCA.java), was excluded for all platforms, not sure why is being run, consider non-blocking

x86-64_linux
1 testcase failure (security/infra/java/security/cert/CertPathValidator/certification/AmazonCA.java), was excluded for all platforms, not sure why is being run, consider non-blocking

x86-64_windows
2 testcase failures:

security/infra/java/security/cert/CertPathValidator/certification/AmazonCA.java was excluded for all platforms, not sure why is being run, consider non-blocking
tools/jpackage/windows/Win8282351Test.java known to fail on some machines, rerun on test-azure-win2012r2-x64-1 in Grinder/7344

x86-32_windows
Test_openjdk17_hs_extended.functional_x86-32_windows ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "17.0.8" 2023-07-18
OpenJDK Runtime Environment Temurin-17.0.8+7 (build 17.0.8+7)
OpenJDK Client VM Temurin-17.0.8+7 (build 17.0.8+7, mixed mode, emulated-client)

CryptoTests_0 => deep history 22/53 passed | possible issues - rerun in Grinder/7346

x86-64_alpine-linux

s390x_linux

x86-64_mac

aarch64_mac

ppc64_aix
jdk_security4 1 testcase failure:

sun/security/krb5/auto/NoAddresses.java


2.1 develop - Incorrect number of edges returned

Good morning,
I'm using the develop branch of 2.1 compiled two days ago.

As you can see from the last query in the picture select from CardCode where code = 8330000
The out('CurrentProfile') shows more than one edge.
Actually there is only one (as it should really be as per my code).
In fact, this is shown in the first query of the screenshot.
This is confirmed by the second query. If I try to select the #72:0 RID as listed on the first query, the result is empty.
Due to this, if I try to iterate over the out('CurrentProfile'), the output log shows this:

Hope this helps
Regards
Guglielmo

Hi Guglielmo,
two quick questions:

how did you create these edges? did you use a transaction for it?
did you manually delete edge records, eg. using UNSAFE?

Hi Luigi,

I use the java API either for inserting and for deleting edges. And yes, I use transactions.
No, I don't delete any EDGE manually and/or using unsafe. I discovered this behaviour while reading the output of my software.

Thanks

Sorry Luigi,
I have a script that I use for development purpose for truncating all classes that uses the UNSAFE keyword. The keyword has been added because the script was no more working with 2.1. I used this script with older version of OrientDB without any problems (but without the UNSAFE keywor).
The script is the following:
js var result = db.query('select name from (select expand(classes) from metadata:schema) where name.charAt(0) <> "O"');
for (var i = 0; i < result.length; i++) {
var className = result[i].getRecord().field('name');
db.command('truncate class ' + className + ' UNSAFE');
};
result.length + ' classes truncated';

Hi Guglielmo,
it must be something like that.
When you use Graph API, like DELETE EDGE, the consistency is guaranteed between edge and vertex records.
If you use UNSAFE, raw records are deleted, so you can have dirty data around.
In this case, the structure that contains pointers to edges in the vertex (it's called a RidBag) still contains references to edges that do not exist anymore (maybe they were truncated or deleted with UNSAFE).
It's not a big problem while traversing or using Graph API in general, because OrientDB just ignores hanging references, but for sure you have a dirty db.
I think I can close this issue. If it happened for other reasons and you think it's actually a bug, please reopen
Thanks

@luigidellaquila
I recreted the database from scratch and yes, now it's working as expected.
Unsafe is really UNSAFE ;)
Thanks (and sorry) for your time
Regards

@luigidellaquila
I'm sorry but the issue still persists. I've recreated the database manually.
The message now is different from the past:
(pool-4191-thread-1) Record (#59:3) is null
(pool-4191-thread-1) Record (#59:13) is null
(pool-4191-thread-1) Record (#59:57) is null
(pool-4191-thread-1) Record (#59:72) is null
(pool-4191-thread-1) Record (#59:86) is null
(pool-4191-thread-1) Record (#59:93) is null
(pool-4191-thread-1) Record (#59:100) is null
(pool-4191-thread-1) Record (#59:119) is null
(pool-4191-thread-1) Record (#59:159) is null
(pool-4191-thread-1) Record (#59:178) is null
(pool-4191-thread-1) Record (#59:193) is null
(pool-4191-thread-1) Record (#59:207) is null
(pool-4191-thread-1) Record (#59:213) is null
(pool-4191-thread-1) Record (#59:221) is null
(pool-4191-thread-1) Record (#59:229) is null

This time I've never used  UNSAFE.
The behaviour is the same as the image posted before.
In addition, if I try to run
select out('CurrentProfile') from cardCode where code = 8330000

I get an error message stating "java.lang.NullPointerException"
Also, if I run
select out_CurrentProfile from cardCode where code = 8330000

I get an error message stating "java.lang.NullPointerException: Impossible to add a null identifiable in a ridbag"
Can you reopen the issue? I can't
Regards
Guglielmo

Hi Guglielmo,
Ok, reopening. Can you share the procedure you use to create the db, or a test case to reproduce the problem?

ok,
I'll try to recreate a test case for you, i'll need time. I'll be back as soon as i get a valid test case
Regards

Thanks a lot!!
2015-07-24 13:42 GMT+02:00 Guglielmo Moretti<EMAIL_ADDRESS>
ok,
I'll try to recreate a test case for you, i'll need time. I'll be back as
soon as i get a valid test case
Regards
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/4641#issuecomment-124496955
.


HEAD requests return 'Method Not Allowed'

$ curl -I 'https://play.rust-lang.org/'
HTTP/1.1 405 Method Not Allowed

According to RFC 7231,

The HEAD method is identical to GET except that the server MUST NOT
send a message body in the response (i.e., the response terminates at
the end of the header section).  The server SHOULD send the same
header fields in response to a HEAD request as it would have sent if
the request had been a GET, except that the payload header fields
(Section 3.3) MAY be omitted.  This method can be used for obtaining
metadata about the selected representation without transferring the
representation data and is often used for testing hypertext links for
validity, accessibility, and recent modification.

This causes cargo-deadlinks and linkcheck to report any playground URLs as dead links.
Is this intentional? Most major web frameworks I know will handle HEAD for you automatically.

Also, there's no Allow header:
HTTP/1.1 405 Method Not Allowed
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 05 Jan 2021 01:21:43 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 0
Connection: keep-alive
Vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers

https://tools.ietf.org/html/rfc7231#section-6.5.5 says

The 405 (Method Not Allowed) status code indicates that the method
received in the request-line is known by the origin server but not
supported by the target resource.  The origin server MUST generate an
Allow header field in a 405 response containing a list of the target
resource's currently supported methods.

Also, there's no Allow header:
HTTP/1.1 405 Method Not Allowed
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 05 Jan 2021 01:21:43 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 0
Connection: keep-alive
Vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers

https://tools.ietf.org/html/rfc7231#section-6.5.5 says

The 405 (Method Not Allowed) status code indicates that the method
received in the request-line is known by the origin server but not
supported by the target resource.  The origin server MUST generate an
Allow header field in a 405 response containing a list of the target
resource's currently supported methods.


Is it possible to click within the "share dialog"?

Is it possible with selendroid to click for example on "SMS/MMS" within the share dialog? If yes, is it possible to control the following app too (for example the sms app)?
Thank you very much and best regards

Hallo Patrick,
if the dialogue has been created by your app (rather than by the OS) then you can interact with the dialogue the same way as you've been interacting with your app. Otherwise you can only use coordinates to click somewhere. This is obviously not reliable and not officially supported by selendroid.
Selendroid can't control the following app. However you could still use the same method of blindly interacting using coordinates.
hope this helps.

Hi operatiay,
thank you for your answer. I already got this working like described in your post.
Best regards


Release python lambda sdk v0.1.17

Related issue https://linear.app/serverless/issue/SC-1012/python-sdk-customer-receiving-error-unicodedecodeerror#comment-aeb4836e

@medikoo ready for review 🙏


Add general module or use none for generic errors

RC_CONSENSUS_NULL_PTR
RC_CONSENSUS_NULL_BUNDLE_PTR
RC_NEIGHBOR_NULL_URI
RC_NEIGHBOR_NULL_HASH
RC_NEIGHBOR_NULL_PACKET
RC_NEIGHBOR_NULL_NODE
and many more, how many of these should be just RC_NULL_PTR?
@thibault-martinez  / @th0br0

I have done some in a recent PR, I'll double check and close this issue.


Fix Fix wal mgr heap use after free when stop doris

Problem: When the process stops, there is a heap use after free error with the WAL manager.
Reason: During the startup process, if the storage engine does not initialize successfully and the main program directly returns 0, the WAL manager, which was created during initialization and started a thread to periodically check disk space, will encounter an issue. When the program exits and returns 0, local variables are destroyed first before the thread is properly terminated. If the thread attempts to access those local variables at this point, it leads to a heap use after free error.
Solution: Ensure that the thread for periodically checking disk space is only started after the storage engine has been successfully initialized.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run p0

run buildall

run buildall

run buildall

run buildall

run cloud_p0


Metrics event split

What is the purpose of the change
As a part of dubbo-core refactor, we need to split out the event-related API out of dubbo-metrics-api. This allows users to import only the event API related to the module they are using, rather than all of it.
Brief changelog

Events related APIs are moved from dubbo-metrics-api to dubbo-metrics-event.

Codecov Report

Merging #12888 (0147813) into 3.3 (5ae875d) will increase coverage by 2.34%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.3   #12888      +/-   ##
============================================
+ Coverage     65.81%   68.15%   +2.34%
  Complexity        6        6
============================================
  Files          1843     1710     -133
  Lines         73722    70344    -3378
  Branches      10465    10206     -259
============================================
- Hits          48517    47944     -573
+ Misses        20489    17747    -2742
+ Partials       4716     4653      -63

see 180 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@songxiaosheng @wxbty PTAL

please fix confict


Inconsistency in the text

The link provided on the page (this one https://www.microsoft.com/research/wp-content/uploads/2016/06/Microsoft_Password_Guidance-1.pdf) is not in par with the text on this page (minimum length 14 char).
[Enter feedback here]

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

ID: 523758d0-17ea-7061-d9ce-8f5a31a76b4c
Version Independent ID: 545fd950-8ef0-837b-8839-8aa21da0c6eb
Content: Password policy recommendations - Microsoft 365 admin
Content Source: microsoft-365/admin/misc/password-policy-recommendations.md
Service: microsoft-365-business
GitHub Login: @KwekuA
Microsoft Alias: kwekua

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

@KvR1991 I have received an update from the author. According to the security PMs, I’ve been working with the new guidance is 14-character length.
Hope this helps!
@yogkumgit  There are no changes required in this document.
Thanks
Sri


[FR] Support non-serializable (part) item Return Orders

Adding support for non-serializable (part) item Return Orders
Feature request: #8372

@SchrodingersGat I was not sure how to add a parameter to disable/enable this. If you could point me to the right location, I could try adding it.

@baltuonis thanks for submitting the PR! This approach is not exactly what I had in mind, what I envisioned was that you would simply remove the restriction that the returned item had to be serialized:
https://github.com/inventree/InvenTree/blob/feefa60a8f11971cadd43cc58e33aa43ce68f325/src/backend/InvenTree/order/models.py#L2408
What you have implemented here is a lot more complex, and I am supposing that what you actually want to be able to achieve is to create a "return order" for a stock item which does not "exist" in the system? It that correct?
For example, if a non-serialized item has been shipped to a customer, that item should be able to be returned via the existing processes, if we allow "non serialized" items to be added to a ReturnOrder via the ReturnOrderLineItem model. I do not think that these extra models you are adding here are necessary.
Perhaps you can expand a bit more on what exactly you are trying to achieve, based on the context above?

@SchrodingersGat right, so this was my first "hold my beer, I'm gonna make a PR in 15 mins" approach.
But then I've bumped into an issue where I can't return more than 1 item in the same Return Order (RO), because of unique(item,order) constraint.
 Now imagine, we have return orders with 17 units of item1, 5 units of item2, etc. That where I had to add quantity field.
Another problem (as you've suggested) is that sometimes there are items that are not present in the main warehouse and we have to issue an RO that includes them... That's where I added part field.
So then I've realized that adding those fields + all the surrounding logic inside a ReturnOrderLineItem would result in a weird polymorphic object that will complicate everything long term.
That's why in the end I've added a separate section with a new model. I think that could be turned off/on with a flag in admin settings.

@baltuonis can I suggest a simpler approach, which I think should work for you here.
Let's say you have sent a quantity of 100x books to a customer. This appears as a single StockItem (with quantity 100x) at the customer.
The customer wants to return 15 of these books. Rather than adding another layer of complication with a new model that maps a "quantity" of the item to be returned, I'd suggest the following process:

"Split" the single stock item into two, 1 with quantity 85 and 1 with quantity 15.
Issue a return order for the quantity 15
Repeat the process for returning other smaller quantities

This utilizes processes which already exist, and does not require this additional alternative process.
To make this happen you would need to make at least the following adjustments to the codebase:
a) Allow stock items which are "at" a customer to be "split" - currently this is prevented, I think
b) Enable non-serialized stock items to be part of return orders
Does this make sense? I strongly feel it is a cleaner alternative which will work better for you anyway

@baltuonis I have a PR here which will implement this - https://github.com/inventree/InvenTree/pull/8590
I think this new approach is a bit cleaner, and avoids multiple different edge case conditions that might otherwise need to be accounted for.
If you can provide a small amount of funding against https://github.com/inventree/InvenTree/issues/8372 (via the "Fund This Issue" button) to support the project that would be appreciated :)

Closed by https://github.com/inventree/InvenTree/pull/8590


Update release instructions

See: https://github.com/api3dao/ois/pull/118#issue-2011815012
The instructions are almost correct, but only a few people have access to push directly to main so there should be a workaround to create a PR. Note that merging these versioning PRs should be done using Rebase and Merge strategy to prevent commit hash changing and breaking the git tag (note: it always changes when you use squash and merge).
The release instructions should also mention a new docs release (provided its a major/minor change).

This could also be fixed by migrating to pnpm and using CD via pnpm publish --provenance per https://github.com/pnpm/pnpm/issues/6435. I'd actually prefer this route.

This could also be fixed by migrating to pnpm and using CD

I think that would be a nice to have given the additional work and the amount of releases we do.

merging these versioning PRs should be done using Rebase and Merge strategy to prevent commit hash changing and breaking the git tag

For visibility, I was wrong in the initial comment regarding rebase and merge strategy. In this followup comment you pointed out that that breaks the git tag as well.
I think we can just keep pushing directly to main branch and in a special case people can open a PR and re-tag manually or ask for push to main access.

I think that would be a nice to have

Agreed, created #122 with the "enhancement" label

I think we can just keep pushing directly to main branch and in a special case people can open a PR and re-tag manually or ask for push to main access.

Agreed

Also mention to run yarn before building the package to make sure dependencies are fresh. See https://github.com/api3dao/airnode/pull/1914/files#r1410222824

I think we can say this has been closed by #137 since the README is now updated with instructions using the GitHub Actions publishing with provenance flow.


Add a warning to the translator when identifier hiding is detected

Warn authors when they create an identifier that hides an identifier in a broader scope.

For example, if an alias is the same as a definition name.