Adds buffering for variables deleted.

Gurobi.Optimizer now have fields next_column and columns_deleted_since_last_update. The behavior now is to not force a update before deleting, but instead: update the list of variables in Julia side but not their column indexes, and save the column indexes of the ones deleted; when updating the model then update the column indexes in Julia side.
The code pass all tests. But maybe we need to devise new ones.
This fix #315 in my code (that unfortunately is not a MWE).
I will be out for about 2 hours now, @odow, after this I will check if you have suggested something to me to improve in this PR.

deepcopy is not needed per se, is just an habit of mine to not assume
fields will not be changed to mutable types after. It should be compiled to
a no-operation, but I can remove it if you think it is better.
I will make your example a test then. Just not now.
Em seg., 4 de mai. de 2020 às 16:13, Oscar Dowson<EMAIL_ADDRESS>escreveu:

@odow commented on this pull request.
We definitely need some tests for this one.
My example from this issue should be fine.
In src/MOI_wrapper.jl
https://github.com/JuliaOpt/Gurobi.jl/pull/317#discussion_r419664660:

@@ -419,6 +453,12 @@ function _info(model::Optimizer, key::MOI.VariableIndex)
throw(MOI.InvalidIndex(key))
end

+function _get_next_column(model::Optimizer)

old_value = deepcopy(model.next_column)

Why is deepcopy needed?
In src/MOI_wrapper.jl
https://github.com/JuliaOpt/Gurobi.jl/pull/317#discussion_r419665251:

@@ -419,6 +453,12 @@ function _info(model::Optimizer, key::MOI.VariableIndex)
throw(MOI.InvalidIndex(key))
end

+function _get_next_column(model::Optimizer)

old_value = deepcopy(model.next_column)
model.next_column += 1
return old_value

function _get_next_column(model::Optimizer)
model.next_column += 1
return model.next_column - 1end
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaOpt/Gurobi.jl/pull/317#pullrequestreview-405270098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADLVVGYZSGBHF2DOCCNAVD3RP4HWRANCNFSM4MZAGVKA
.

@odow The test was a little harder to create than I expected. Many common attributes are cached on the wrapper (name, bounds, type, ...) and other are discarded (Start, VBasis, ...) if any variables are deleted. This explains how this bug did not surface immediately, and how the code seems to work in some situations that it shouldn't work, given the nature of the bug.
The testset has 4 fails in current master branch and none with the changes introduced by this branch. I think it is a solid test.

Which are the tests that fail?

Buffered deletion test: Test Failed at /home/henrique/AreaDeTrabalho/Gurobi.jl/test/MOI/MOI_wrapper.jl:519
  Expression: vars_obj[2] == MOI.get(model, obj_attr, vars[2])
   Evaluated: 42.0 == -77.0
Buffered deletion test: Test Failed at /home/henrique/AreaDeTrabalho/Gurobi.jl/test/MOI/MOI_wrapper.jl:521
  Expression: fourth_var_obj == MOI.get(model, obj_attr, fourth_var)
   Evaluated: -77.0 == 0.0
Buffered deletion test: Test Failed at /home/henrique/AreaDeTrabalho/Gurobi.jl/test/MOI/MOI_wrapper.jl:526
  Expression: vars_obj[2] == MOI.get(model, obj_attr, vars[2])
   Evaluated: 42.0 == -77.0
Buffered deletion test: Test Failed at /home/henrique/AreaDeTrabalho/Gurobi.jl/test/MOI/MOI_wrapper.jl:528
  Expression: fourth_var_obj == MOI.get(model, obj_attr, fourth_var)
   Evaluated: -77.0 == 0.0

Basically the tests that check the value of the property set. The ones before the implicit update_model! caused by MOI.optimize! and the ones after it. In the patched version such errors do not exist (all tests pass). So I am confident the code, while not bug-free, solves the bug it intends to solve and do not break any other test.

Oops. I mis-read your comment. I understood it as 4 different tests were failing, but these ones were passing.

Oh, no. With this PR all older tests pass and the new ones too. In the master branch, the 4 @test I cited of the new @testset I created fail (because the bug the PR solves).

@odow, do you want me to improve this PR in some way? While this is not approved, Gurobi.jl will cause subtle bugs to users when deletion is followed by attribute changes. It is also good for me if I can refer to the Gurobi version I used in my paper, instead of saying I used a patched local copy, XD.

Sorry, merging since this is a strict improvement in correcting an existing bug. Thanks!


Package deemix-gui

Project description
deemix-gui is (as the name suggests) a GUI to use deemix as an application, not as a library. Note that deemix as a (Python) library is already packaged.
Metadata

homepage URL: deemix homepage, deemix GUI homepage (not very useful as it only contains links to binaries)
source URL: gitlab repo
license: gpl3
platforms: cross-platform (is an electron-based portage of a web app)

I'm gonna try and give this one a go.


[#1846] Fixed functionality and a11y issues with generic service editor dialog.

#1846
===
The <KvPair/> component was actually broken and did not work. Additionally, the accessibility was not satisfactory.
Before, the control would try to auto-add new rows as you started filling in the previous rows, but did not work properly. The new, simplified approach provides buttons to add or remove rows.
The component will now also focus the newest row after adding a row, as well as announce to the screen reader when the user deletes a row.
Before:

After:

Coverage decreased (-0.02%) to 65.74% when pulling 7144a141d35119716d02039e77bc49cd2c461d76 on toanzian/acc-#1846 into 10efb6735a51d2d5c841015b1b1c0c08ec0596f1 on master.


Added four smart speakers

Sonos Arc
Sonos Sub
Sonos Amp
Apple HomePod Mini

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.214%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2860

Relevant Lines:
2912

💛  - Coveralls

Thanks a lot. Let's merge.


docs & slightly nicer interface for reporting scripts

[ ] use argparse w help instead of just sys.argv[1]
[ ] docs for the reporting
[ ] output html to a file, maybe based on the report, instead of stdout
[ ] make html report sections collapsible
[ ] add meta info to html report
[ ] add project link to html report
[ ] mention in main docs that reporting exists

I recommend this for the CLI: https://typer.tiangolo.com/ (instead of argparse).

thanks, there's a lot that argparse doesn't do well. it looks nice so far, and the reporting scripts are probably great place to trial it before introducing it in the main cli module


Optic doesn't support Symbol.

Well, Optic is support String, Array ...etc
However, the ES6 new type Symbol is mostly support by modern browser and Node.js.
But, if we create a new Optic like this:
[
  Symbol(),
  'string'
]

The error is throw.

Yes, currently Partial Lenses do not support symbols and in non-production mode the library raises an exception as seen here.
I'm not opposed to supporting symbols, but I'm not entirely sure what the best way to support them would be.  Ramda, for example, does not currently support symbols.  It seems that the use case of symbols is to avoid name clashes.  Even JavaScript itself seems rather undecided on how symbol properties should be treated: object spread ignores them, while Object.assign copies them as seen here.
I did some quick tests and it seems that copying symbol properties (using builtin Object.assign or Object.getOwnPropertySymbols) would cause something like a 2x performance hit in latest Node for property lenses.  Note that I mean this in the sense of supporting the possibility of having symbol properties—I actually tested this on objects that did not have symbol properties, so there was no extra cost of actually copying more.  Hopefully future JS engines will have faster implementations of Object.assign and then supporting symbol properties could be done without taking a performance hit.
For the above tow reasons, namely

that there currently does not seem to be a consensus on what the best way to support them is (copy or not copy), and
that copying them would cause a 2x performance hit,

I'd rather not enhance the default property lenses in Partial Lenses to support symbol properties at this point.
Note that you can always write a custom optics for accessing objects with symbol properties.  Here is a simple example using L.lens and here is a version that also provides the symbol or string as the index.  At the moment this is what I'd recommend if you need to access objects with symbol properties.

I read your example. However, the variable name like xi2yF confuse me. What it's name mean? When I want to read this project source code. This problem tangle me, I want to contribute my code, but first , how to understand this, which knowledge I miss. Thanks

Also, my latter example had a bug—I just fixed the link.

Got it ,thanks

@Justin-ZS Oops.  Thanks for the correction!  Here is the fixed playground.

If someone, like me, needs to not loose Symbols using lenses this a patch I have done to infestines.

diff --git a/node_modules/infestines/dist/infestines.cjs.js b/node_modules/infestines/dist/infestines.cjs.js
index 3d711b4..a1a4f30 100644
--- a/node_modules/infestines/dist/infestines.cjs.js
+++ b/node_modules/infestines/dist/infestines.cjs.js
@@ -438,14 +438,8 @@ var assocPartialU = function assocPartial(k, v, o) {
   var r = {};
   if (o instanceof Object) {
     if (!isObject(o)) o = toObject(o);
-    for (var l in o) {
-      if (l !== k) {
-        r[l] = o[l];
-      } else {
-        r[k] = v;
-        k = void 0;
-      }
-    }
+    // Symbol Support
+    Object.assign(r, o);
   }
   if (isDefined(k)) r[k] = v;
   return r;
@@ -456,10 +450,9 @@ var dissocPartialU = function dissocPartial(k, o) {
   if (o instanceof Object) {
     if (!isObject(o)) o = toObject(o);
     for (var l in o) {
-      if (l !== k) {
-        if (!r) r = {};
-        r[l] = o[l];
-      } else {
+      // Symbol Support
+      if (!r) {r = {...o}}
+      if (l === k) {
         k = void 0;
       }
     }


Update copyright holder in license

Description

This PR changes the LICENSE file to update the copyright holder. By making both this repo and the frontend (WordPress/openverse-frontend#2034) use the same license we

make the licenses consistent
avoid a future merge conflict 😉

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb drafting this while we await conformation on the validity of the suggestion. Thanks for waiting.

@zackkrida @dhruvkb Any news on whether the license move is valid? This is also blocking WordPress/openverse-frontend#2034.


source.transform(transformation) ?

I'm currently looking at how to integrate operations received from firebase at the same time as local operations. The problem is source.settleTransforms. When I receive operations over the wire from firebase I don't know when to call settleTransforms because that information is lost when another firebase client sends them.
Admittedly I'm still getting up to speed with the finer points of orbit.js but it seems that source.settleTransforms is used to mark the end of a transformation i.e. a bunch of operations are sent to the source and when all the operations in a transformation have been received source.settleTransforms is called to indicate that the source should start processing them. This means that there are 2 lines of communication, the stream of operations and the call to settleTransforms which marks groups of transactions (as a transformation). This poses a problem when you have two concurrent streams of operations, when settleTransforms is called, which transfomation should be processed? Currently it's the transformation that started receiving operations first that will be transformed. It's possible that you'll have a sequence like:
operation1(transformation1)
operation2(transformation1)
operation3(transformation2)
operation4(transformation2)
settleTranforms(for transformation 2) => but transformation1 is the currentTransformation
operation5(transformation1)
settleTransforms(for transformation 1)
As mentioned earlier, when you only have the stream to provide the information (in my case when receiving operations from firebase) it's not even possible to know when to call settleTransforms (my naive implementation was to just call settleTransforms after every operation was received - as expected, this causes timing issues).
It's quite possible that I've misinterpreted things so please correct me if I'm wrong. Assuming I'm correct though I've been giving some thought to how to solve it.
Internally, the sources are operating at the level of transformations, the operations that constitute a transformation are transmitted individually but they're then pieced back together before they're processed. If instead of transmitting operations it was the transformations that were transmitted (source.transform(transformation)) then settleTransforms becomes redundant. The source doesn't need to worry about how to group operations because that information is provided directly by the Transformation. This not only simplifies a lot of the logic in the sources but it means that all information is transmitted in a single stream (solving the firebase issue of not knowing when to call settleTransforms).
@dgeb I'd love to know your thoughts on this, I realise it's a bunch of work to make the change but if my interpretation is correct this would be a useful change(actually essential in my case :) ) and I'd be happy to dig in.

I'm seeing a few related issues, to do with how operations are received from firebase. To set up the demo I'm working against do:

checkout https://github.com/opsb/peeps-ember-orbit#orbit-firebase
checkout https://github.com/opsb/orbit-firebase#master
cd orbit-firebase && bower link
cd peeps-ember-orbit && bower link orbit-firebase
ember s

The issue I'm looking at is that when you create a contact in peeps it will save phone numbers correctly but if you try and add one later it will fail with a path not found error.
I've experimented with receiving operations from firebase in a couple of ways but currently it's set up to simply apply them directly to the cache.

@opsb thanks for the example repo and for making orbit-firebase public. I've finally got some time now to pull it down and check it out the errors you're seeing.

Admittedly I'm still getting up to speed with the finer points of orbit.js but it seems that source.settleTransforms is used to mark the end of a transformation

settleTransforms can be called to ensure that all the transforms in the queue are settled and the queue is cleared before settling a promise, say. This is useful for resolving Requestable methods.
It's not strictly necessary to call settleTransforms because queues will be autoprocessed.
Anyway, I'll see what I can track down here.

It's not strictly necessary to call settleTransforms because queues will be autoprocessed.

Ok, that makes a lot of sense.
I've explored two different designs for orbit-firebase:

Stream operations to other clients directly, they're queued in firebase and distributed as is. The client that generates the orbit operations applies changes to models in firebase so that the requestable methods can run queries.
Operations are applied to firebase, it generates events which are then converted back into orbit operations.

At the moment orbit-firebase is set up for (1) but (2) is actually a simpler design and has less potential for syncronisation issues (i.e. with (2) it's possible for the operations queue to be slightly out of sync with the model store in firebase).
If possible I'd prefer to get (2) running, this was actually the initial design so I still have the components. @dgeb do you see anything that would prevent (2) from working?

@opsb I've never used firebase. When you make a request to firebase, such as adding a record, is there a way to track its success or failure? Or are the requests and responses completely disconnected and untrackable?

Yes, firebase does give you an error if there's a problem. This was an area that I was unsure of though. To ensure a consistent execution path across all clients the firebaseSource.transform methods don't actually touch the cache. They send the changes to firebase and then separate firebase listeners are fired which apply the changes to the cache (for all listening clients). Currently this means that orbit-firebase only operates as a non blocking source but as this is the most likely usage anyway I haven't worried about it yet.

I wanted the consistent execution path because this means that events are in the same sequence across all clients. If the changes are applied to the cache by the initiating client then there's potential for it to receive operations in a different sequence to the other clients. I did actually see this being an issue early on because sometimes the clients would get into a flip-flopping state i.e. you would get add / remove operations flipping backwards and forwards indefinitely.

BTW, orbit-firebase was forked from orbit.js so it has the same Broccoli setup.

Another related point on this, I wasn't sure what the semantics of a blocking connector should mean. Should the source return when firebase has been successfully updated or when the changes have actually been applied to the cache?

@dgeb you caught me on the hop a bit today. I've now implemented strategy (2) from above, see https://github.com/opsb/orbit-firebase/tree/direct. It's a simpler implementation and if you try it with peeps-ember-orbit you'll see that it mostly works (including live updating in another window). There are concurrency issues that only seem to turn up with more activity(my actual app has an action which generates a graph of objects) but I'll probably have a look at them next week (I'm travelling tomorrow and meetings all day friday...). The most obvious issue is that I'm currently having to use eager loading. This is fine for the peeps app but it obviously isn't going to scale up too well. There's some more information about it at https://github.com/orbitjs/ember-orbit/issues/57.

I think this one has been solved in 0.6.1. Will reopen if I find any related cases that still fail.


Update did, did-imp, did-method-peer to 0.1.0-M11 in main

About this PR
📦 Updates

app.fmgp:did
app.fmgp:did-imp
app.fmgp:did-method-peer

from 0.1.0-M10 to 0.1.0-M11
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "app.fmgp" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "app.fmgp" }
}]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, version-scheme:early-semver, commit-count:1

Superseded by #155.


Rendering the top left box is broken on these two pages

https://docs.influxdata.com/chronograf/v1.4/guides/transition-web-admin-interface/
https://docs.influxdata.com/chronograf/v1.4/guides/transition-web-admin-interface/

It looks like these pages were removed from the docs, so the published pages aren't being updated with the template changes which include the "View in Chronograf" functionality. There's a js error that is keeping the rest of the js from running, so the ads aren't loading.
From what I understand, deleted pages remaining on the published site is a known issue. @stevebang, didn't Gunnar have to ssh into each docs host and manually remove deleted pages?

Clarification. This doc wasn't removed, it was moved from /guides/ to /administration/.

we link to these pages from inside the chronograf app. if they are removed, could you set up a redirect link so that users don't see a 404?

Sure, that'll need to be updated in the nginx.confs on each of the docs hosts. I don't have the necessary access on AWS to view the host details and connect, but I believe @gunnaraasen can do it.
I'm wondering if it may be better to store the nginx.conf in the project so things like this don't require direct write access to the host servers. On deploy, nginx would need to be restarted using the nginx.conf in the project directory.
nginx -c /abs/path/to/nginx.conf

Fixed this using Hugo's built-in aliasing functionality.

@sanderson cool, I think Hugo redirects are the preferred way to deal with redirects for one-off page location changes like this.
Good suggestion about keeping the nginx.conf in source control.


No way of ignoring bed explosions

Beds aren't considered entities and therefore their explosions cannot be ignored.

I'm hesitant to solve this by simply checking if the block is a bed, because it could be a plugin-induced explosion on a bed

I'm not sure, but I tried including it in the ignored_entity_explosions list but it wasn't recognized (- BED)

I'm hesitant to solve this by simply checking if the block is a bed, because it could be a plugin-induced explosion on a bed

That would be enough I think

It would work, but again, it would interfere with e.g. projectiles from a plugin that has explosive projectiles whenever they hit a protected block.

Could you detect the radius of the explosion? Because the only explosions with radius 5 are beds and respawn anchors, they could be detected and then verify the block maybe?


More FC test cases

[Notes for myself]

should_update_justified_checkpoint:

compute_slots_since_epoch_start(get_current_slot(store)) == SAFE_SLOTS_TO_UPDATE_JUSTIFIED

and get_ancestor(store, new_justified_checkpoint.root, justified_slot) == store.justified_checkpoint.root
and get_ancestor(store, new_justified_checkpoint.root, justified_slot) != store.justified_checkpoint.root

do we want to get this into the test suite prior to the Bellatrix spec release coming soon?

I'm good with anything and everything that's best for everyone, doesn't harm anyone is critical.   I was hurt by an error that i tried to report 1000 times to no avail... it also denied me any and all credit for everything I have ever done and had bots spamming every account I made further widening the gap to help, oh and I am technically a noob to all this so I didn't know what to do as I literally was blown off by everyone... I lost hope and really believe in doing the next right thing.  It messed my already suffering self up really bad.. I'm still in disbelief the bots are finally connecting all my work... slowly but it's done this before and I was cut out again when I asked for help... I think on purpose but it was certainly mean and not cool.  I straight up tried to disclose the naming variables as the vAriable name itself issue when making first project and idk the dude didn't respond to my email telling him I emailed him exactly what blew up the project.  I feel like he knew and tried to cut me out but I don't know if my perception was correct.  I also specifically requested reasonable assistance for a disability that has been hard and is part of ADA law.... no response.  I also told him not to feel bad and I think I need someone else to review correspondence to figure out if it was criminal or not cuz it was def really messed up morally speaking. Probably legally as well being as I used language from ADA law in my request for help after being blocked from all my credits and they were systematically taken and used in a project I did not sign SLA for then he tried to cut all my work out... but my work is better and I think it's kinda taking care of that on its own... how do I get help when every account I make is instantly labeled spammy because of misbehaving GitHub bots? I only ever reached one sales guy and he didn't care to even look into it or help me get a human who could help.  I have so much more work out there and I documented my work, saved all my hard drives, backed up multiple places and ways. I have my proof of my innovations with Linux dev, networking breakthroughs and more.  I clocked my moms old iMac as the fastest computer on the planet but didn't believe it until I found out all my work really was pretty cool.. the insane compression also... whomever reads this please help me get in tough with someone who can help me understand all the stuff I did.. I was just doing what I thought could build cool stuff from antiquated hardware and there's more... a lot more.... my name is Todd Gifford and I'm a dog dad to my amazing blue heeler Chiefy<EMAIL_ADDRESS>and chiefy01@outlook and tgifford37@gmail and tgifford37@outlook please send any messages to all of them I have hard time getting my emails sometimes being as I have multiple iterations of the same emails on diff devices and services and all my devices are prototypes by default... thank you


Update how to deploy ML.NET in Web API

Summary
Describe your changes here.
Fixes #32841
Preview Link

@JakeRadMSFT can I get a review on this please. Thanks.


api docs: Document the /dev_fetch_api_key endpoint.

This might need some changes after #10102, but I think it's worth having around anyways.

Rebased, edited the description, and merged, thanks @YagoGG!
I think with this one finished, you now have just the "notification settings" PR still open for API docs.  I'd love to see you work on the "upload realm emoji" endpoint, since we've been getting user feedback interested in it.


Expose tunning options via expvar

Which problem is this PR solving?

Resolves #1333

Short description of the changes

Mounts expvar handler (/debug/vars) on the admin port regardless of --metrics-backend
Stores the following collector's options in expvar:

collector.num-workers
collector.queue-size

Store the following agent's options in expvar:

processor.*.server-max-packet-size
processor.*.server-queue-size
processor.*.workers

Store the following storage-related options in expvar:

memory.max-traces
downsampling.ratio
span-storage.type

This test has indeed been flaky...

Tests are passing now :-)

Sure, wilco

@jpkrohling Is it known issue https://travis-ci.org/github/jaegertracing/jaeger/jobs/729295839?

Doesn't sound like it, looks like it's a real problem with the new test:
github.com/jaegertracing/jaeger/plugin/storage.TestSetExpvarOptions(0xc000229080)
	/home/travis/gopath/src/github.com/jaegertracing/jaeger/plugin/storage/factory_test.go:364 +0x337

Doesn't sound like it, looks like it's a real problem with the new test:
github.com/jaegertracing/jaeger/plugin/storage.TestSetExpvarOptions(0xc000229080)
	/home/travis/gopath/src/github.com/jaegertracing/jaeger/plugin/storage/factory_test.go:364 +0x337

My bad, didn't notice...

I am going to merge it, please put another PR for otel/go.mod


(chore)(test)Adding Kerberos DNS check to the Hive connection case

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run buildall

run buildall

run external

run buildall

run External

run buildall

run external

run external


What is difference between this repository and EasyMicroservices/Laboratory

Hi @alighodrati .
The laboratory is about mocking.
And Network is about HttpClient, you know we don't have HttpClient in old dotnet or some methods in HttpClient.
We have to make an interface to implement HttpClient, WebRequest, WebClient, etc.

Thanks @Ali-YousefiTelori


Remove notify from JobConfig

/packit copr-build

Merging this will break (already broken) tests in p-s because the JobNotifyType is being used there:
./tests/unit/test_copr_build.py:12:    JobNotifyType,
./tests/unit/test_copr_build.py:57:            notify=JobNotifyType.from_list([]),

could you please send a PR over there as well?

packit-service/packit-service#260


Create stu

This folder is for student in "National Tainan Second Senior High School."

@Alexenderrrrr lib/domains/tw/edu/tn/tnssh/stu: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Alexenderrrrr lib/domains/tw/edu/tn/tnssh/stu: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Alexenderrrrr Pull request merged. Thank you!


Blank mission support for dependency editor

Tracks :

https://github.com/openshiftio/openshift.io/issues/3244

Depends on :

https://github.com/fabric8-analytics/fabric8-analytics-dependency-editor/pull/105

@edewit pls review .

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FEAT] Implement Sign-in with Token Authentication (EMAIL)

Description
Implement a sign-in functionality where users can log in using a 6-digit token sent to their email.
Acceptance Criteria

Endpoint is correctly versioned.

Request Token Endpoint:

Accepts an email address in the request body.
Checks that the user has a valid account.
Generates a 6-digit code.
Sends the generated code to the provided email.
Responds with a message indicating the code has been sent.
Handles invalid email input by responding with a 400 Bad Request status.

Verify Token Endpoint:

Accepts an email address and 6-digit code in the request body.
Verifies the code and email combination.
Responds with a session token (e.g., JWT) upon successful verification.
Handles invalid token or email input by responding with a 401 Unauthorized status.

Token Management:

Ensure the 6-digit code has an expiry time (e.g., 5 minutes).
Securely store the generated code until it expires or is used.
Invalidate the code after successful verification or expiration.

Purpose
Instead of requiring users to remember and manage complex passwords, this feature leverages a one-time 6-digit code sent to the user's email for authentication.
Expected Outcome
The user should be able to sign in to their account successfully and receive a JWT authentication token.
Endpoint
Request Sign-In Token:

Description: Generate and send a 6-digit sign-in token to the user's email.
Endpoint: GET /api/v1/auth/signin-token
Request Body:

{
  "email"<EMAIL_ADDRESS>}

Response (Success)
{
  "message": "Sign-in token sent to email",
  "status_code": 200
}

Response (Error)
{
  "message": "Failed to send sign-in token",
  "status_code": 400
}

Verify Sign-In Token:

Description:  Verify the 6-digit sign-in token and log in the user.
Endpoint: POST /api/v1/auth/signin-token
Request Body:

{
  "email"<EMAIL_ADDRESS>  "token": "123456"
}

Response (Success)
{
  "message": "Sign-in successful",
  "token": "JWT token containing user id and email",
  "status_code": 200
}

Response (Error)
{
  "message": "Invalid token or email",
  "status_code": 401
}

Task:

[ ]  Create the GET /api/v1/auth/signin-token endpoint.

[ ]  Implement logic to generate a 6-digit token.

[ ]  Integrate email service to send the token.

[ ]   Handle invalid email input.

[ ]  Write unit tests for the GET /api/v1/auth/signin-token endpoint.

[ ]   Create the POST /api/v1/auth/signin-token endpoint.

[ ]  Implement logic to verify the token and email combination.

[ ]   Generate a session token (e.g., JWT) upon successful verification.

[ ]   Handle invalid token or email input.

[ ]   Write unit tests for the POST /api/v1/auth/signin-token endpoint.

[ ]  Set token expiry time (e.g., 20 minutes).

[ ]   Securely store and manage tokens.

Testing

Write unit tests for both the request token and verify token endpoints.
Include integration tests to verify the end-to-end functionality.

REFERENCE: APPROVED ISSUE

Fix your merge conflict


Add generic deriving for PIsDataRepr

Should Plutarch.Generic and Plutarch.DataRepr.Internal.HList.hs be moved under ./Plutarch/Util - because they are independent of the Plutarch itself?


Landscape prob

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: [e.g. Debian, Windows, macOS...]
scrcpy version: [e.g. 1.12.1]
installation method: [e.g. manual build, apt, snap, brew, Windows release...]
device model: Realme 1
Android version: 9
Describe the bug
A clear and concise description of what the bug is.

On errors, please provide the output of the console (and adb logcat if relevant).
Please paste terminal output in a code block.

Please do not post screenshots of your terminal, just post the content as text instead.
I have a problem in REALME 1 that is if i screen mirror any game or using the phone in landscape mode it is looking like blue and red with a line and its looks like 3D

Please screenshot.

I also have a problem when rotating. For example, if I am in Firefox in portrait mode, but left-click to go back to the « desktop » of the phone, then the device rotates back to portrait and then crashes. Here is the log:


[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:

I am on OS X Ventura and i am receiving this error message:
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)>
I am running bark-gui using miniconda in its own env.   Any help would be appreciated.

OS X seems to dislike downloading the model weights. Try downloading them manually and put them into the models folder.


v0.5.0

Changes

Revamped the !speedruns command and the accompanying documentation in README.md
Replaced config.json with IDs.yml – Neater syntax, smaller files size, easier to expand when needed
Made some grammar and wording changes to README.md
Added the !request command

Never mind, I don't want a pull request.


Tests fail on big-endian systems

Tests fails on big-endian systems. Here is an example:
  test/Data/StaticBytesSpec.hs:65:20:
  14) Data.StaticBytes, Primitive Vector, handles bytes16
       Falsifiable (after 4 tests and 3 shrinks):
         [1]
       expected: [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
        but got: [0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0]

  To rerun use: --match "/Data.StaticBytes/Primitive Vector/handles bytes16/" --seed<PHONE_NUMBER>

  test/Data/StaticBytesSpec.hs:75:20:
  15) Data.StaticBytes, Primitive Vector, handles bytes32
       Falsifiable (after 4 tests and 3 shrinks):
         [1]
       expected: [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
        but got: [0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]

  To rerun use: --match "/Data.StaticBytes/Primitive Vector/handles bytes32/" --seed<PHONE_NUMBER>

  test/Data/StaticBytesSpec.hs:83:21:
  16) Data.StaticBytes, Primitive Vector, fuzz with encodeUtf8
       Falsifiable (after 2 tests and 1 shrink):
         "a"
       expected: [97,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
        but got: [0,0,0,0,0,0,0,97,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]

  To rerun use: --match "/Data.StaticBytes/Primitive Vector/fuzz with encodeUtf8/" --seed<PHONE_NUMBER>

For the full build log see https://buildd.debian.org/status/fetch.php?pkg=haskell-static-bytes&arch=s390x&ver=0.1.0-1&stamp=1729262862&raw=0

@iliastsi, thanks for reporting. In case the build log is ephemeral, I'm posting more from it below:
Data.StaticBytes
  ByteString
    padding is the same as trailing nulls [✘]
    handles bytes16 [✘]
    handles bytes32 [✘]
    fuzz with encodeUtf8 [✘]
  Storable Vector
    padding is the same as trailing nulls [✘]
    handles bytes16 [✘]
    handles bytes32 [✘]
    fuzz with encodeUtf8 [✘]
  Unboxed Vector
    padding is the same as trailing nulls [✘]
    handles bytes16 [✘]
    handles bytes32 [✘]
    fuzz with encodeUtf8 [✘]
  Primitive Vector
    padding is the same as trailing nulls [✘]
    handles bytes16 [✘]
    handles bytes32 [✘]
    fuzz with encodeUtf8 [✘]

and
test/Data/StaticBytesSpec.hs:60:47:
  13) Data.StaticBytes, Primitive Vector, padding is the same as trailing nulls
       Falsifiable (after 1 test and 2 shrinks):
         (0,0,1,0)
       expected: Right "\NUL\NUL\SOH\NUL\NUL\NUL\NUL\NUL"
        but got: Right "\NUL\NUL\NUL\NUL\NUL\SOH\NUL\NUL"

  To rerun use: --match "/Data.StaticBytes/Primitive Vector/padding is the same as trailing nulls/" --seed<PHONE_NUMBER>

As an accident of its history (spun out of Stack via pantry), I think this package implicitly assumes the architecture, and Word64 values, are little endian. Possibly because the GHC project only distributes GHC binaries for little endian architectures (x86_64, AArch64).

As an accident of its history (spun out of Stack via pantry), I think this package implicitly assumes the architecture, and Word64 values, are little endian. Possibly because the GHC project only distributes GHC binaries for little endian architectures (x86_64, AArch64).

I see that in Debian we have disabled the tests for pantry, with a comment that they try to access the network (which is not allowed). This is probably why we failed to detect this earlier, and we have shipped (possibly broken) Stack on big-endian systems so far. For now, I will remove Stack from those systems.

@iliastsi, the version of the package in branch fix1 is intended to fix the problem, but I have no means to test it on a big-endian machine architecture. Would you be able to do so?

@mpilgrem PR #4 solves the issue. Tests are now passing on big-endian systems. See here for the build logs https://buildd.debian.org/status/fetch.php?pkg=haskell-static-bytes&arch=s390x&ver=0.1.0-3&stamp=1729513039&raw=0.
Thank you for the quick fix.


Add different variants of p-multgrid

@lpsaavedra you want to do the documentation in this PR or you want to regroup the new docs in another PR?

I have now added the documentation for the new strategies in this PR


BSD Python API does not validate SSL certificates

Example (<IP_ADDRESS> is the IP address of google.com):

import httplib
conn = httplib.HTTPSConnection('<IP_ADDRESS>')
conn.connect()
conn.request('GET', '/')
resp = conn.getresponse()
print resp.read(32)

https://www.python.org/dev/peps/pep-0476/
but at least on a recent OS X Yosemite install, no checking is done, so I don't think it's wise to rely on this.
A popular library that does validation by default is requests: http://docs.python-requests.org/en/latest/user/advanced/#ssl-cert-verification
Maybe you could move to that as a dependency instead?

Also, sorry for not including this -- you import/use httplib here:
https://github.com/bluestatedigital/bsd-api-python/blob/master/bsdapi/BsdApi.py#L23

(and while I'm piling on, https://github.com/bluestatedigital/bsd-api-python/blob/master/bsdapi/BsdApi.py#L53 -> would be great if 'https=True' was the default if BSD Tools installations enable TLS by default, given the revelations about widespread data collection of unencrypted internet traffic)

Thanks @pames . I believe I have addressed your concerns here:
https://github.com/bluestatedigital/bsd-api-python/pull/9
Unfortunately, requests v 2.7.0 is not compatible with the Google App Engine environment (something to do with it's sockets use), so for my integration I had to go back to an older version (2.1.0).  It does still do cert checking.
https://code.google.com/p/googleappengine/issues/detail?id=11942&thanks=11942&ts=1431082804

Hi @davvblack, thanks for the referenced PR.  Looks great, and thanks for changing the default to assume https!
I don't know if there is any incompatible API change between 2.1.0 and 2.7.0 but given that this library isn't GAE specific, I hope you agree the move to requests is safer for the general population?  And GAE applications which need to depend on this will have to simply depend on (or patch) a specific version of requests to operate within the GAE environment as you have suggested with version 2.1.0.
There are a few CVEs which impact 2.1.0 -> 2.7.0 (from http://docs.python-requests.org/en/latest/community/updates/#software-updates, CVE-2014-1829, CVE-2014-1830, CVE-2015-2296), but I'd say it's up to whoever's running the app on GAE to determine whether or not they apply in the context of their use of the API.


Support for GPU Arrays?

Is it possible to use AxisKeys.jl together with GPU arrays, e.g. those in KernelAbstractions.jl or CUDA.jl?

Yes.

OK!
The package's approach is always to un-wrap, call whatever function on the parent array, and then re-wrap. So if the parent is a CuArray, this may just work. But nothing is explicitly tested against this, and there may be unexpected bugs.


Add ability to add custom host mapping

Docker provides for --add-host host:ip.add.re.ss to allow adding entries to the hosts file in the container

Support for custom host entry added, check PR #19 for more information.


Found 9411 pd legal cards in the database but the list was 9414 long {'Jotun Owl Keeper', 'Jotun Grunt', 'Akki Lavarunner'}

This is from the EMN legality list

I let @binarySwordsman know on chat.

Good spot Katelyn. @binarySwordsman fixed the umlauts. I fixed Akki. All is well.


Add Gabriel Fouasnon

LGTM! Thanks, @gabalafou and welcome to the team!
Test failures appear unrelated.

Apparently, I don't have merge rights on this repo 😅
ping @jupyter/executive-council  for review/merge.

I restarted the failing jobs, they appear unrelated but want to give them another go before merging.


Android development with flutter

Description 📜
Added Fluttter Intoduction Video
Fixes #135

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Android Dev Flutter

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@iamayushkr
Delete all other domains from your comment.. like mentioned in official GWOC PR template directives
Kindly follow the issue template from next time ... & preach this to your fellow contributors

Done Sir @Suvraneel

@iamayushkr Yes perfect... Since, this is new, kindly preach this to your batchmates as well (wherever you can... its appreciated)


roleAssignmentID added to solutions properties

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] public repo review queue, private repo review queue
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

Adding one optional field of roleAssignmentId in solution properties to solutions installation API

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@IshitaAsthana  Please validate if other solution Crud examples are to be updated apart from Solutions_CreateOrUpdate. Last I checked, it was decided that request and response would have same model for Solutions, so Get example Response might have to be updated as well.

this js sdk breaking is not caused by this pr


Handles OmitSpecimen in AutoConfiguredNSubstituteCustomization

This PR fixes #395

I see your point.
Do you think OmitSpecimen should only be handled with PropertyInfo and FieldInfo? If that's the case, I'll have to refactor the NSubstituteVirtualMethodsCommand to request a PropertyInfo instead of Type in such cases.
#394 describes the OmitSpecimen returned when a Type is requested. Do you think it makes sense? Should it be supported?

OmitSpecimen indicates a NOOP. Its purpose is to indicate to the caller that whatever it's currently attempting to do (such as mutating a field or property), it should abort.
This makes sense for a Command, but I fail to see how this could ever be appropriate for a Query. How can a Query ever be a NOOP?
In AutoFixture, Commands are usually used to mutate the state of an object by assigning a value to a property or field. This is the primary use case for OmitSpecimen, but there may be other I've forgotten about...

I think you raised an important question. OmitSpecimen usually means "don't assign anything to this field/property".
In the context of setting up a method, I guess it could mean:

Don't set it up, at all. Instead, let the mocking framework decide what to do. The framework might then decide to either return null, 0, a mock (e.g., in Moq if DefaultValue is set to DefaultValue.Mock), or maybe even throw an exception.

This definition seems to fit the overall goal of OmitSpecimen.
The problem with that is: the specimen is resolved (and OmitSpecimen is returned) lazily inside a delegate executed by the framework. When the delegate is executed, the framework already expects us to tell it what value to return - it's no longer up to the framework, it's up to us. It's simply not possible to halt and do a NOOP.
Given this limitation, I believe the most sensible thing to do would be to return default(T), even if that's not ideal.

Don't set it up, at all. Instead, let the mocking framework decide what to do. The framework might then decide to either return null, 0, a mock (e.g., in Moq if DefaultValue is set to DefaultValue.Mock), or maybe even throw an exception.

I like that specification :+1:
Converting OmitSpecimen to default(T) is wrong. The entire reason OmitSpecimen exists is exactly to enable downstream clients to make an informed decision about what it means. Converting to default(T) removes this information.
Originally, AutoFixture handled recursion issues by either throwing exceptions on detected recursions (to this day, this is the default, built-in behaviour), or alternatively, as an opt-in customization, by assigning null.
The problem with assigning null is that a writeable property may have a Guard Clause that protects against null values.
Therefore, the motivation for introducing OmitSpecimen was to signal that the request in question should be aborted.
This is clearly explained in the commit message for 4ffec5ea53f409406819aa97870891c8aa501fc0, which explains:

Added the OmitSpecimen class, which is a pure marker object that can be used to indicate that a particular request should be omitted. The primary purpose is to notify the AutoPropertiesCommand that a property or field should be omitted.

I've managed to handle OmitSpecimen as it was supposed to.
Done in: 685d0e3 and 5567178.

Thank you for your contribution! It's now live as AutoFixture.AutoNSubstitute 3.30.4.


CONTRIBUTING.md: point to the Matrix Staging room

Description of changes
As suggested by @alyssais on Matrix after a regrettable systemd merge. Not sure if this will make much difference, but if nothing else it might help get people involved in staging work!
cc @mweinelt @vcunat for staging procedures
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Maybe it’d be better to put this as a separate warning block to avoid interrupting the description of the basic procedure, but I fear alert blindness.

Pushed with slightly different wording; let me know what you think.


add jekyll-cloudinary

https://github.com/nhoizey/jekyll-cloudinary

Oh no! Our tests are borked!
  *  External link https://github.com/jekyll/plugins/edit/master/_plugins/jekyll-cloudinary.markdown failed: 404 No error

Of course it doesn't exist; the PR hasn't been merged yet 😭😭😭

@jekyllbot: merge


HARP-7400: Added fallback for target and targetDistance

Codecov Report

Merging #1365 into master will decrease coverage by 0.09%.
The diff coverage is 70.27%.

@@            Coverage Diff            @@
##           master    #1365     +/-   ##
=========================================
- Coverage   54.25%   54.15%   -0.1%
=========================================
  Files         256      267     +11
  Lines       23493    23782    +289
  Branches     5268     5322     +54
=========================================
+ Hits        12745    12879    +134
- Misses      10748    10903    +155

Impacted Files
Coverage Δ

@here/harp-mapview/lib/Utils.ts
58.57% <ø> (-8.58%)
:arrow_down:

@here/harp-mapview/lib/MapViewFog.ts
68.11% <ø> (ø)
:arrow_up:

@here/harp-map-controls/lib/MapControls.ts
23.78% <ø> (ø)
:arrow_up:

@here/harp-mapview/lib/ClipPlanesEvaluator.ts
51.7% <ø> (ø)
:arrow_up:

@here/harp-mapview/lib/MapView.ts
62.67% <70.27%> (-0.49%)
:arrow_down:

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

@here/harp-utils/lib/UrlUtils.ts
84.09% <0%> (-7.81%)
:arrow_down:

... and 35 more

Continue to review full report at Codecov.

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

@harpgl-bot retest this please


Coder.Coder version 0.15.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

@microsoft-github-policy-service agree company="Coder Technologies, Inc."

cc: @deansheather @matifali 🤖

cc: @deansheather @matifali 🤖

Wow, 1st automated winget release. 🥳


Fix errorState.msg propType

Fixes build failure:
components/ListView/BlueprintContents.js
  59:28  error  'errorState.msg' is missing in props validation  react/prop-types

This was previously erroneously changed the other way around in commit
56f688dde48dc6, which got reverted in commit 5b38c5efbf.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5b38c5e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #716   +/-   ##
=========================================
  Coverage          ?   78.26%
=========================================
  Files             ?       66
  Lines             ?     3326
  Branches          ?      685
=========================================
  Hits              ?     2603
  Misses            ?      723
  Partials          ?        0

Impacted Files
Coverage Δ

components/ListView/BlueprintContents.js
60.71% <ø> (ø)

Continue to review full report at Codecov.

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


WIP - Fixes from load testing

Issue: closes #380

[ ] Tick here to confirm that you have run RunCodeFormatter.ps1

Description:

Catch and log analytics exceptions on ScoreEvent

Test:
Build and run Nether.Web
Run Integration tests
Run load tests

@stuartleeks,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Generate docs from ocean-lib

Generate docs from ocean-lib important modules comments & doc strings.

You know we did this already, right? Via Akshay.
And there was a huge amount of work to make it pretty. And in the end, it was pretty.
So if you're gonna do that, you should leverage all the past work done for this.

I am sorry maybe I missed that. I didn't know that we have docs generated by our Python doc strings or Python comments. Can you share with me Akshay's work so I can iterate on that please?
Thank you for letting me know!

About the previous docs:

First, know that it probably took 6+ man-months of work to make it look good. There were a lot of gotchas to tune it, across different chunks of code and software stacks. Not easy at all.
The first thing to do is: play with what the final result looked like. For that, just revive an older version of docs.oceanprotocol.com (perhaps 3-6 months ago).
Then dig around oceanprotocol org to see the repos that made this. (There were a few).
Pros: look good, thorough, "automated"
Cons: not very readable, super-hard to maintain, hard to make updates

Tbh I don't think auto-generating is the way to go. It might look like less work to get "something". But better is to have shorter docs that are well-targeted and explain well, rather than super-thorough but without good guidance on what matters.
Good example docs, at a similar level of maturity to ocean.py, are:

Zama. https://docs.zama.ai/concrete
Brownie. https://eth-brownie.readthedocs.io/en/stable/

Zama docs were built with gitbook. Much simpler flow to update compared to our current docs repo. IIRC Ana & others were exploring that. I'm not sure the status.
I strongly recommend to go a route to have our docs look something like Zama or Brownie, eg via gitbook. The outcome will be way better, and way easier to continually involve.

About the previous docs:

First, know that it probably took 6+ man-months of work to make it look good. There were a lot of gotchas to tune it, across different chunks of code and software stacks. Not easy at all.
The first thing to do is: play with what the final result looked like. For that, just revive an older version of docs.oceanprotocol.com (perhaps 3-6 months ago).
Then dig around oceanprotocol org to see the repos that made this. (There were a few).
Pros: look good, thorough, "automated"
Cons: not very readable, super-hard to maintain, hard to make updates

Tbh I don't think auto-generating is the way to go. It might look like less work to get "something". But better is to have shorter docs that are well-targeted and explain well, rather than super-thorough but without good guidance on what matters.
Good example docs, at a similar level of maturity to ocean.py, are:

Zama. https://docs.zama.ai/concrete
Brownie. https://eth-brownie.readthedocs.io/en/stable/

Zama docs were built with gitbook. Much simpler flow to update compared to our current docs repo. IIRC Ana & others were exploring that. I'm not sure the status.
I strongly recommend to go a route to have our docs look something like Zama or Brownie, eg via gitbook. The outcome will be way better, and way easier to continually involve.

I understand your point and thank you for putting the resources here & giving more context. I'll tag @AnaLoznianu, maybe she'll provide an opinion as well.

@trentmc We are currently working on upgrading our docs and having better documentation for our components. Ocean.py and ocean.js are part of this.
I don't envision importing the generated documentation in the docs repo but having a few pages detailing some of the functionalities with references to the autogenerated content.
I know it's not perfect but I want to start somewhere

I agree that ocean.py needs better documentation.
And I agree with having a few pages detailing some of the functionalities, to start somewhere.
And I agree to not import the generated documentation.
But: the title of this issue is "Generate docs from ocean-lib". That - along with the description and the PR -- appears contradictory with the previous point.
We already had this. It was pretty. It took a lot of work to get there. Why was it removed, only to replace with a super basic version?
Btw there's already a github issue for good docs for ocean.py: #1184. For the style of eth-brownie or zama, like I mentioned above. @AnaLoznianudrecronjetech and I discussed this a few months ago and it seems that was the direction. So, what's changed?

Nothing has changed. We want to get to a point where we have good documentation for our components. As you can imagine this is a tone of work.
Having this autogenerated content for the ocean.lib that we can reference from the docs.oceanprotocol.com is one of the steps

If we auto-generate then we are repeating work of the past. Why would we repeat that?
And auto generated had big flaws. That's why it was removed.
Then everyone agreed (iirc) that we should have actually-useful docs. I wrote #1184 to reflect this, which also incorporated my discussions with you @AnaLoznianu .
I propose:

we close this issue as wontfix. And the associated pr
and we do #1184. For docs that people might actually use.

Closing this due to https://github.com/oceanprotocol/ocean.py/pull/1434#issuecomment-1566876612


Handle exceptions thrown in shutting-down process

Context
We've seen org.gradle.launcher.daemon.server.BadlyFormedRequestException: Unexpected authentication token in command Build{id=5bd12d2f-010d-4bfb-a376-4b23cc9f4b0b, currentDir=/home/tcagent1/agent/work/e67123fb5b9af0ac} received from socket connection from /<IP_ADDRESS>:37339 to /<IP_ADDRESS>:39124 twice this week. Looking at the daemon log, there's something interesting.
This is a normal daemon shutting down log:
Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt.
16:49:53.127 [DEBUG] [org.gradle.launcher.daemon.registry.PersistentDaemonRegistry] Removing daemon address: [d3ef27ea-fb4d-4e49-8c3f-2523f559ad50 port:60038, addresses:[/0:0:0:0:0:0:0:1%lo0, /<IP_ADDRESS>]]

The current running daemon was correctly removed from daemon registry. This is the problematic daemon log:
Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt.
failed to abort Gradle Test Executor 2
org.gradle.process.internal.ExecException: A problem occurred waiting for process 'Gradle Test Executor 2' to complete.
        at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241)
        at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218)
        at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369)
        at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87)
        at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: Shutdown in progress
        at java.base/java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
        at java.base/java.lang.Runtime.removeShutdownHook(Runtime.java:243)
        at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33)
        at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208)
        at org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365)
        at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108)
        at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84)
        ... 7 more

End of file

So it looks like that during shutting down process, an exception was thrown, interrupting the shutdown hook which removes current daemon from daemon registry. This PR catches this exception.
However, this shouldn't be a problem, because even daemon exits unexpectedly, the daemon registry file should not be broken. The token information is recorded in daemon log for further investigation. IIUC, the token is not credential, right? cc @big-guy @adammurdoch

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QFL

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test QFL

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test QF

OK, I've already cancelled the old build and triggered a new QuickFeedback build for you.

@bot-gradle test QF

OK, I've already cancelled the old build and triggered a new QuickFeedback build for you.

@bot-gradle test RFM

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test this

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.

@bot-gradle test SC

@bot-gradle test SC

OK, I've already triggered SanityCheck build for you.

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle test SC

OK, I've already triggered SanityCheck build for you.

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history


strtotime returns false on 2.0.11

Description
Previously on versions prior to 2.0.11 like 2.0.10 or 2.0.9 it was possible to parse strings like Mon Apr 27 18:49:44 2020. On latest 2.0.11 it just returns false.

I'll take a look.

The parser that was introduced in 2.0.10 release falls with parsing "Apr 27 18" into datetextual category https://github.com/php/php-src/blob/73734eee6ca30953b9725f683738a141b6b28ebf/ext/date/lib/parse_date.re#L1454 so the remaining :49:44 is not recognized as time. I will try to adjust the rule order to get closer to PHP rules.

PHP in turn recognizes it as dateshortwithtimelong, which is not yet supported. I will try to provide support within next days.

Thanks!

Pull request implementing the missing date formats has just been merged to master.

strtotime(new Date().toISOString()) also returns false

@Falseclock this is probably due to yet missing timezone support. I will add some basic support (for Z and [+-]HH:MM) shortly.

The following PR adds initial timezone support https://github.com/locutusjs/locutus/pull/432
Support for full timezone names will be added in separate PR.

For me strtotime is undefined after import. (locates: "^2.0.14").

I'm closing the issue. If you think the issue is not properly solved, please feel free to re-open.


Missing libostree-1-1 for Ubuntu Xenial

When trying to install CRI-O from the Ubuntu Atomic PPA, I get the following error:
# apt-get install cri-o
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cri-o : Depends: libostree-1-1 but it is not installable

I'm on Xenial:
# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

As a matter of fact, there seems to be no libostree-1-1 package for xenial:
https://packages.ubuntu.com/search?keywords=libostree-1-1

cc @lsm5 @runcom

We should just remove ostree from building, there's a go build tag to remove it we should use when building for ubuntu.

On Wed, Aug 30, 2017 at 12:28:04PM +0000, Antonio Murdaca wrote:

We should just remove ostree from building, there's a go build tag to remove it we should use when building for ubuntu.

I'll check it out.
@sameo until I get a new build out, please try this:
add-apt-repository ppa:alexlarsson/flatpak
apt update
apt install libostree-1-1

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes-incubator/cri-o/issues/817#issuecomment-325975030

--
Lokesh
Freenode, OFTC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

This is the build tag we need to use when building for ubuntu containers_image_ostree_stub

Just pushed a new cri-o build cri-o_1.0.0-alpha.0.2-1~ubuntu16.04.2~ppa1
for xenial to PPA that shouldn't need
libostree-1-1. Check it out.
On Wed, Aug 30, 2017 at 05:35:09AM -0700, Antonio Murdaca wrote:

This is the build tag we need to use when building for ubuntu containers_image_ostree_stub
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes-incubator/cri-o/issues/817#issuecomment-325976546

--
Lokesh
Freenode, OFTC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

@lsm5 We should be calling it beta.0.x as that was the last cri-o release.

On Wed, Aug 30, 2017 at 08:21:51AM -0700, Mrunal Patel wrote:

@lsm5 We should be calling it beta.0.x as that was the last cri-o release.

I've been building master branch.
I called it alpha.0 because I see this in cmd/crio/main.go
app.Version = "1.0.0-alpha.0"
Should that be changed to beta? Or should I be building the beta git tag
instead?

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes-incubator/cri-o/issues/817#issuecomment-326025127

--
Lokesh
Freenode, OFTC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

We missed bumping it last time. https://github.com/kubernetes-incubator/cri-o/commit/f35147e23c13440ff7e18d04ef138596ad79401b
We could carry that.

On Wed, Aug 30, 2017 at 05:01:42PM +0000, Mrunal Patel wrote:

We missed bumping it last time. https://github.com/kubernetes-incubator/cri-o/commit/f35147e23c13440ff7e18d04ef138596ad79401b
We could carry that.

ack thanks, will rebuild in a bit..

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes-incubator/cri-o/issues/817#issuecomment-326054950

--
Lokesh
Freenode, OFTC: lsm5
GPG: 0xC7C3A0DD
https://keybase.io/lsm5

I think this is fixed so closing.

Still getting the same error as originally reported.  Same output as reported by @sameo

@jsmickey are you on either of xenial or zesty?

The latest cri-o should figure out whether or not libostee is supported and turn it off.  I actually think for CRI-O we should just not compile ostree in.  For kpod we need this support if it is supported since an output format of containers/image is ostree.

so skopeo ends up pulling in libostree-1-1. I gotta check and change the deps to use skopeo-containers instead.

Xenial
On Oct 30, 2017 9:19 AM, "Lokesh Mandvekar"<EMAIL_ADDRESS>wrote:

@jsmickey https://github.com/jsmickey are you on either of xenial or
zesty?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/cri-o/issues/817#issuecomment-340458078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADu2h2iUmrY1NuW-0vKhx-vkdbh7zNy3ks5sxdsIgaJpZM4PHSco
.

ah btw, make sure you've enabled https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak as well. I'll do new builds to change dep to skopeo-containers


How to load a local model file?

I want to load a local model which has the same file with the files downloaded from huggingface.
However, right now this repository seems to only support load from website.

The model directory is like follows

I also have the same problem.

@BUAADreamer @liulfy The model argument in LLM or api_server can also take the path to your local directory that contains the weight files.

But this code seems to request huggingface website
from vllm import LLM, SamplingParams
prompts = [
    "你好，请介绍一下你自己",
    "中国的定义是什么？"
]
sampling_params = SamplingParams(temperature=0.01, top_p=0.01)
llm = LLM(model="/path/to/llama")

@BUAADreamer Thanks for providing the example. It should not use the remote HF repo if the path is valid. Could you try this and let us know if it works?
from transformers import AutoConfig

config = AutoConfig.from_pretrained("your/path/to/llama")

If this doesn't work, then it means your path is somehow incorrect (or it's a bug in HF).

@WoosukKwon in my case, I cannot load from LLM, but I can load from AutoConfig:

I use Build from source and run seccessfully. Thanks!

please describe the solution more detail, very thanks!

Indeed. I built from source: https://github.com/vllm-project/vllm/releases/tag/v0.1.1, and this problem solved.

https://vllm.readthedocs.io/en/latest/getting_started/installation.html
just use the Build from source in this website and run like above, if it only report error, then set tokenizer_mode='slow'

Indeed. I built from source: https://github.com/vllm-project/vllm/releases/tag/v0.1.1, and this problem solved.

Yes, this version works


stub /community page [WIP]

Please provide feedback on this WIP Pull Request

Closing as stale, on the assumption that the need will resurface if it still exists.


Tutorial in Bengali language

If given the permission i could make bengali tutorials for at least 100+ problems within a month , many of them already have tutorials in English though.

@walleeva2018 Hello dear, please feel free to contribute. We will merge.

@walleeva2018 If you are still working on this, propose a PR when you add a new translation or editorial in Bangla. Remember to create individual PRs for each problem.
I am closing this issue since it doesn't help anybody in anyway knowing you want to do some work on some problems.


Retaining prior manually generated logs

Is there any way to retain prior manually generated logs that exist in CHANGELOG.md at the time of generation while still adding new release changelogs to the same file?
I have some manually generated changelogs of changes to the project prior to using this action, but when I run this on push to that branch, the existing logs are overwritten with only the latest version existing in the logs after the action runs. Subsequent runs of the action add to this file--keeping the logs generated by this action as expected. I have added tags and versions that match the versions in the changelog, and the action is incrementing that version correctly, but it replaces any preexisting content within CHANGELOG.md.
Can I keep the preexisting content of CHANGELOG.md intact while using this action somehow?
My action config:
- name: Generate Changelogs
        uses: TriPSs/conventional-changelog-action@v3
        with:
          config-file-path: "./packages/[package-name]/config/conventional-changelog.js"
          git-path: "./packages[package-name]/"
          github-token: "${{ secrets.BUILD_TOKEN }}"
          tag-prefix: [package-name]@v
          version-file: "./packages/[package-name]/package.json"
          output-file: "./packages/[package-name]/CHANGELOG.md"
          release-count: 0

This is not possible as it's not supported by conventional-changelog package. You could create a CHANGELOG.old.md file (or something similar) where you could store the old ones.

Maybe it's an additional flag we than need to provide to that package?

PR would be awesome!

PR open here.


How to let AppDelegate listen for events originating from the Fabulous app

As an example, while the Fabulous app is running a counter, I want to update the MacOS menu bar's title attribute with the current value of the counter.
I can set the title in AppDelegate.fs directly with
        let statusBarItem = NSStatusBar.SystemStatusBar.CreateStatusItem(NSStatusItemLength.Variable)
        statusBarItem.Title <- "5:00"

The idea of the MVU loop is clear for updates within the Fabulous app itself, but I wonder how to pass the message from the Fabulous app to AppDelegate in this case.
It would be a similar issue for mobile notifications (e.g. update a running counter in the notification), but I would guess for mobile Xamarin.Forms has some utilities to do so.

Thanks, that sounds like a good solution.


Few items are not indexed into GSI

i have two Global Secondary Indexes.
One GSI contains only hash key and another GSI one have both hash key and range key.
both will back fill items but few items are not indexing in first GSI and few items are not indexing in  another GSI.
I thought it as index key violation. Then i tried to Detecting and Correcting Index Key Violations using Violation Detector based on http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.ViolationDetection.html
but it didn't find any violated items and i got result as
"
2017-07-13 12:58:33,141 INFO [com.amazonaws.services.dynamodbv2.online.index.PrintHelper] - Violation detection finished: Records scanned: 1252976, ### Violations found: 0, Violations deleted: 0, see results at: ./gsi_violation_check.csv
"
is there any wayto find why the items are not indexed(backfillled) into global secondary indexes and add violated items into index ?
Thank you.

What do you mean by backfilled?  I am not familiar with that idea in the context of global secondary indexes on DynamoDB.
The only relevant thing I think may be related is that if you add fields to an index you have to create a new index, the old index won't get updated with the new field for old entries.

Hi @pboling , Thank you for your reply.
Backfilling means- For each item in the table, DynamoDB determines which set of attributes to write to the index based on its projection (KEYS_ONLY, INCLUDE, or ALL). It then writes these attributes to the index. During the backfill phase, DynamoDB keeps track of items that are being added, deleted, or updated in the table. The attributes from these items are also added, deleted, or updated in the index as appropriate.
I have created new index and it have all the items in its index. While retrieving I am getting only few items. Unable to fetch all the items from index.
EX: I have a table called students with attributes/fields  name, school_name, standard
Have a GSI with school_name as partition key.
when i try to retrieve students based on school_name
Syntax: Student.find_all_by_secondary_index({school_name: "primary School"})
it is not retrieving all the students in primary school. I scanned students table to get promary school students, i got more results than GSI result.
There is anything i missed ?

How is your GSI defined?
I have a GSI defined like this:
global_secondary_index hash_key: dynamo_primary_key_column_name,
                             range_key: :observed_at,
                             projected_attributes: [:vendor_id, :service_id, :analyzed_at]

And it is working when queried like this:
range_modifier = 'between'
find_all_by_secondary_index(
          {
              dynamo_primary_key_column_name => dynamo_primary_key_value
          }, # The signature of find_all_by_secondary_index is ugly, so must be an explicit hash here
          :range => {
              "observed_at.between" => [1.week.ago.to_f, Time.current.to_f] # array of 2 timestamps converted to float
          },
          # false is the same as DESC in SQL (newest timestamp first)
          # true is the same as ASC in SQL (oldest timestamp first)
          :scan_index_forward => false
)


Index shard flush and delete actions need to target the nodes that the shard live on

The UI tries to apply the action to all nodes which often means the status is updated more than once


Support Sign In with GitHub

Is your feature request related to a problem? Please describe.
I've been frustrated setting up GitHub Login with Cognito & Amplify.
This might be more of a feature request for Cognito itself than amplify-cli.
Describe the solution you'd like
Support GitHub Login as you do with Facebook, Google, Amazon, and Apple.
Describe alternatives you've considered
One way to setup GitHub is use a custom OIDC provider to handle logging in with GitHub. There is an open source repo here: https://github.com/TimothyJones/github-cognito-openid-wrapper that provides this integration.
I've bumped into different issues with it. Refresh tokens and accessing fields I would like.
Currently, the easiest solution is to use Firebase for Auth and Amplify for other services.

cc @undefobj

related federated login provider requests:

GitHub: https://github.com/aws-amplify/amplify-cli/issues/2529
Twitter: https://github.com/aws-amplify/amplify-cli/issues/995
Apple:

https://github.com/aws-amplify/amplify-cli/issues/3434
https://github.com/aws-amplify/amplify-cli/issues/3929

Closed in favor of #2529.

Closed in favor of #2529.


1.1.6-1.1.9 /dev/shm sets non-CIS option "size=2G" by default

Describe the Issue
1.1.6-1.1.9 /dev/shm sets non-CIS option "size=2G" by default. Setting the size is not actually recommended by the CIS Benchmark and not really a hardening step  -  though, it's included in an example in the benchmark document.
Fortunately, the implementation makes it possible to modify the default options using the variable - but still,  the default should not include a non-hardening related size-option.
Expected Behavior
Should not set size by default  for /dev/shm.
Actual Behavior
Sets size by default for /dev/shm.
Control(s) Affected

dunno

Environment (please complete the following information):

not applicable

Additional Notes

N/A

Possible Solution

N/A

hi @karniemi
Thank you for taking the time to raise this issue.
We have merged this fix into the devel and main branches.
Regards
uk-bolly


Add DBD keywords used by EPICS base DBDs

DBD language definition does not include all keywords used by EPICS base DBD files.
Add missing keywords (see dbLex.l)

Hello,
I am working on this ticket. This ticket is here to allow tracking and visibility. Thus, would it be possible to assign it to me, please?
Thank you.
Sincerely,
Ivo

Since the pull request #31 has been merged, this issue is read for testing. Alternatively, it might be closed.


HDFS-16625.

Description of PR
There are unit tests that require native PMDK libraries which aren't checking if the library is available, resulting in unsuccessful test.  This patch checks the assumption about PMDK availability.  The same changes have been applied and tested against trunk (3.4.0-SNAPSHOT), branch-3.3 (3.3.4-SNAPSHOT), and branch-3.3.3.
How was this patch tested?
This patch has been applied to a local build that runs in the Hadoop development environment, which doesn't include the PMDK shared libraries.
For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

LGTM

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 46s

trunk passed

+1 :green_heart:
compile
1m 27s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 21s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  6s

trunk passed

+1 :green_heart:
mvnsite
1m 31s

trunk passed

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 28s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 53s

trunk passed

+1 :green_heart:
shadedclient
23m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 18s

the patch passed

+1 :green_heart:
compile
1m 21s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 21s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 53s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
1m 32s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 28s

the patch passed

+1 :green_heart:
shadedclient
23m  2s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
255m 42s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 52s

The patch does not generate ASF License warnings.

363m 10s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4414

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 9ecd4ea00f04 4.15.0-169-generic #177-Ubuntu SMP Thu Feb 3 10:50:38 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 63c6681369fec3c1ad4541d01f04e0753ba1db45

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/1/testReport/

Max. process+thread count
3237 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

The test failure looks unrelated. I see that this test failed in a nightly from a few days ago too https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/878/#showFailuresLink. This PR is a change to tests only and the changed tests are not the test that failed. Let me merge.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
66m 49s

trunk passed

+1 :green_heart:
compile
1m 44s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 25s

trunk passed

+1 :green_heart:
mvnsite
1m 48s

trunk passed

-1 :x:
javadoc
1m 25s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-hdfs in trunk failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

+1 :green_heart:
javadoc
1m 50s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 43s

trunk passed

+1 :green_heart:
shadedclient
23m  5s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 21s

the patch passed

+1 :green_heart:
compile
1m 27s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
1m 27s

the patch passed

+1 :green_heart:
compile
1m 18s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  2s

the patch passed

+1 :green_heart:
mvnsite
1m 24s

the patch passed

-1 :x:
javadoc
0m 58s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-hdfs in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

+1 :green_heart:
javadoc
1m 32s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 24s

the patch passed

+1 :green_heart:
shadedclient
22m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
242m 19s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 15s

The patch does not generate ASF License warnings.

380m 48s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestClientProtocolForPipelineRecovery

hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4414

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d77ddca68a62 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e9adf41a6af39660df8ac83d6c7a7339670aace2

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/2/testReport/

Max. process+thread count
3107 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4414/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Javadoc build fails are unrelated to this PR's add of a check to two unit tests. The TestRollingUpgrade failure we've flagged already as pre-existing condition and the TestClientProtocolForPipelineRecovery failure is not a test changed here. Let me merge.

Thanks for the contrib. Do you want to put up a backport for branch-3.3 when you get a chance @snmvaughan ? Thanks.


Block edge 4.4.29

4.4.29 needs to be disabled:
3 clusters currently failing (12%),  2 gone ( 8%),and 19 successful (73%), out of 26 who attempted the update over 7d
Currently failing classification:
* Down nodes: 1
* Logging issues: 1
* SDN issue: 1

4.4.29 can be enabled again:
2 clusters currently failing ( 8%),  1 gone ( 4%),and 16 successful (64%), out of 25 who attempted the update over 7d
Currently failing classification:
* Down nodes: 1
* SDN issue: 1
* Slow etcd: 1


Add self_reported_ethnicity to obs

See the proposal in Deprecate ethnicity and ethnicity_ontology_term_id for details.

@jahilton - per our earlier discussion, there are no requirements related to delimiters to be enforced by the validator. Any comments?
self_reported_ethnicity

Key
self_reported_ethnicity

Annotator
Curator

Value
categorical with str categories. If organism_ontolology_term_id is "NCBITaxon:9606" for Homo sapiens, this MUST be either free-text or "unknown" if unavailable. Otherwise, for all other organisms this MUST be "na".

@jahilton - this is addressed in #258. Please reopen this issue if further refinements are required.

there are no requirements related to delimiters to be enforced by the validator.

Correct. I think we can give some guidance
If listing multiple ethnic categories in the same string, we STRONGLY RECOMMEND separating the values with a comma
(need to decide what that suggested delimiter is though - i'll browse to see if there are any categories that might include commas)
Personally, I find that using quotations and the code formatting for exact values ("unknown", "NCBITaxon:9606") to be redundant and the quotes should be removed. Read literally, someone may interpret it as the quotes should be included in the value.

Re-opening for pending editorial changes.

Per July 12 call with Norbert, @jahilton, and @hthomas-czi - we agreed to rename and reuse the current ethnicity field with its HANCESTRO value. Closing.


Formatting sometimes hangs indefinitely

We have received reports of RuboCop formatting hanging indefinitely. Notice that it does not seem like the issue is performance on large files, which is a separate issue.
It seems that somehow the LSP either gets stuck or returns something invalid to VS Code (which in turn makes the "Running Ruby LSP formatter" dialogue never disappear).
Both reports we have received mentioned that there's nothing in the output tab, other than the default message of "Starting the Ruby LSP...".
Suggestion
We should consider making format on save false in the extension pack, while we work on improving the situation.
Suggestion on how to debug
The difficult part of this is reproducing the issue, given that we do not know what causes it. Some possible steps:

Make sure "ruby lsp.trace.server": "messages" is turned on in .vscode/settings.json
When formatting hangs, check the output tab and see if any other requests are still being made. If you manage to get requests going for any file, then it's unlikely that the server is stuck - which probably means we returned something invalid to VS Code (or didn't return anything when it was expecting something)

Definition of done
This ticket is considered closed when the root cause of the bug (hanging formatting) is identified and addressed.

Make sure "ruby lsp.trace.server": "messages" is turned on in .vscode/settings.json

Is this
    "ruby.lsp.trace.server": true,

or
    "[ruby]": {
        "lsp.trace.server": true,

VSCode says the former is unknown and the later is not per-language setting 🤔


fix: merge the missing groups with max annotation gap

Coverage report

Click to see coverage of changed files

FileStatementsMissingBranchesMissing
Coverage         Coverage         (new stmts)
Lines missing
Branches missing

  codecov

  diff_grouper.py42->43, 47->48
  main.py

Project Total

Click to see whole project coverage

FileStatementsMissingBranchesMissing
Coverage
Lines missing
Branches missing

  codecov

  badge.py
  coverage.py
  github.py
  github_client.py
  groups.py
  log.py
  settings.py
  template.py

Project Total

This report was generated by [CI-codecov]