Make new endpoints to expose data

Description
We need to make some new endpoints where we can access the raw data. We're still not sure what data will be useful, as this is still an experiment. Start with the three queries we already have.
Example
https://got-issues.herokuapp.com/top_ten_clicked_issues
[
  {
    "issue" : "https://github.com/GSA/data.gov/issues/464",
    "clicks" : 71
  } ,
  ...
]

Files
run.py
Tasks
Make a new endpoints for:

[ ] Total clicks
[ ] Top Ten Clicked Issues
[ ] Most recently clicked issue
[ ] Tests

Re: "Top Ten Clicked Issues", see https://github.com/codeforamerica/gotissues/issues/3#issuecomment-112017032
I think this data would be more meaningful if it was normalized somehow against its prominence on the Civic Issue Finder site. So a good endpoint (if it can be collected from Google Analytics...maybe it would require some hacking on the UI to get GA to pick it up) would be "Number of times issues have been displayed on the front page (and in what order)."

Another related thing I realized, too, was that some issues are getting more face time on some sites. For example, only SF Brigade projects are shown on the Code for San Fransisco page, so it might be useful to look at the number of times the issue has been displayed on each page the widget exists if also possible?

:+1: @eunicekokor

We've got some database tables set up with the data we think to be useful.
We can expose these through an api for @sbenthall to do some analysis with.
/issues
{
"html_url": "https://github.com/codeforamerica/gotissues/issues/8",
  "id": 87136867,
  "title": "Pull in data from GitHub about the clicked issues",
  "labels": [
    { "url": "https://api.github.com/repos/codeforamerica/gotissues/labels/enhancement",
      "name": "enhancement",
      "color": "84b6eb"
    }
  ],
  "state": "closed",
  "comments": 1,
  "created_at": "2015-06-10T23:03:05Z",
  "closed_at": "2015-06-23T00:43:26Z",
  "body": "TEST BODY",
  "closed_by": {
    "login": "ondrae",
    "id": 595778
  },
  "clicks" : 10000000,
  "views" : 777,
  "view_sources" : ["www.codeforamerica.org","http://testurl.com"]
}

and
/activity
{
  "issue_url": "https://github.com/codeforamerica/gotissues/issues/8",
  "click_timestamp": "2015-12-27 07:30:00",
  "activity_type": "PushEvent",
  "activity_timestamp": "2015-06-06 23:16:56"
}


Preseed immunity and vaccination effects in the simulation

This is to enable model execution with start point after the initial outbreak of the pandemic as a whole.

I think we should aim for at least rudimentary support for this for FACS 2.0

[ ] add fixed pre-infection %
[ ] add randomly generated immunity durations.


Idle detector (auto) triggering false positives

This issue requires more information.
It seems that the idle detection service, when set in auto mode (the default), is marking healthy channels as unhealthy. Waiting for more details from the client, but this seems to be happening on low traffic scenarios (for example, sending/receiving every 10 seconds).
The workaround is to disable auto mode and use an explicit read/write/both timeout.
channel.AddIdleChannelService( options =>
{
    options.DetectionMode = IdleDetectionMode.Both;
    options.Timeout = TimeSpan.FromSeconds( 60 );
} );

The idle channel service was deprecated in v1 and replaced with a simpler and more efficient internal mechanism, configurable via channel options.


Remove redundant clone

Current dependencies on/for this PR:

main

PR #494   👈

This comment was auto-generated by Graphite.


Mafia updates

Thanks to the people who helped me with this (amazing failure of a) first test run.

Fixed that pesky travis build


[Technical] Tests for header and footer in DynamicTableViewController

Test that the header/footer title is the header/footer text for enum type .text(_:)
Test that header/footer title is nil if section is hidden
Test that header/footer title is nil if it's not text.

You really fell in love with this thing :D

I love to write tests. 🤷♀

I love to write tests. 🤷♀

You will be the perfect candidate to write tests for the new home screen. 😀 boom shakalaka


controlboardwrapper2 deprecation

device controlboardwrapper2 was deprecated in previous yarp releases and it will be completely removed in the upcoming yarp 3.8.
The correct devices to use are: controlBoard_nws_yarp / controlboardremapper.
An update of the robot configuration files is highly recommended, otherwise, the robot will be not able to startup anymore.

We ran a campaign in the past to update the robots to the use of the NWS/NWC layers.
However, there are still some leftovers, which pertain to:

Robots/Setups/Folders
Status
Notes

iCubLisboa01
❌
Needing fix

R1SN000
❌
Needing fix

iCubTemplates
❌
Needing fix

iRobCub-Mk1
❔
We may have kept it unchanged upon request

experimentalSetups
❔
We need to judge case by case as some setups are old

vizzy
👍🏻
We don't maintain it

@davidetome who was the main developer in charge may add more insights.

From this seems that the new iCubGenova11 is using controlboardwrapper2.
Maybe the template for the new robots has to be updated? Otherwise we continue to introduce it

Maybe the template for the new robots has to be updated? Otherwise we continue to introduce it

Very true!
I'll update the OP to include iCubGenov11 too.
cc @AntonioConsilvio @davidetome

From this seems that the new iCubGenova11 is using controlboardwrapper2.
Maybe the template for the new robots has to be updated? Otherwise we continue to introduce it

Ciao @Nicogene , actually the templates are not used to create a new robot folder, but only to explain files structure, params meaning and so on.
In fact inside them all robot-files are missing (i.e. https://github.com/robotology/robots-configuration/tree/master/iCubTemplates/iCubTemplateV6_0/hardware/motorControl).
Usually to create a new robot a copy of the last delivery is made.
cc @pattacini @AntonioConsilvio

done w/ this PR :

https://github.com/robotology/robots-configuration/pull/446

cc @Nicogene @pattacini


BUG: Endpoints not querying up until 2022

Actual Results
All emissions sub types and facility/ unit attributes should query up until the latest reporting quarter. Fix the UI validation so that the CDD query's up until the latest reporting quarter and update the error messages
1.Fix the validation on the font end to query up until the latest reporting quarter for annual, ozone, and facility/unit attributes

Update error messages for an out of range date on the front end for all emission sub types and facility/unit attributes

Update error messages on the back end for  all emission sub types and facility/unit attributes

Remove the  '  from the error messages. This is happening on the backend for hourly and daily emissions

This issue is applicable to the following data types

all emissions sub types (including the emissions filter logic endpoint)
facility/ unit attributes

Updated UI  Error Messages
UI error Messages for an out of range date:

Hourly Emissions:
Enter dates between < insert valid range >  and the quarter ending on < insert valid range >

Daily Emissions:
Enter dates between < insert valid range >  and the quarter ending on < insert valid range >

Monthly Emissions:
Enter month(s) and year(s) between <  insert valid range > and the quarter ending on < insert valid range >

Quarterly Emissions:
Enter quarter(s) and year(s) between <  insert valid range > and the quarter ending on <  insert valid range >

Ozone Season:
Enter year(s) between 1995 and the quarter ending on <  insert valid range >

Annual Emissions:
Enter year(s) 1980, 1985, 1990, or a year between 1995 and the quarter ending on <  insert valid range >

Facility/ Unit Attributes:
Enter year(s) 1980, 1985, 1990, or a year between 1995 and the quarter ending on <  insert valid range >

Updated API error messages
API error Messages for an out of range date

Hourly Emissions
Update the beginDate to a date between  <  insert valid range > and the quarter ending on <  insert valid range >
Update the endDate to a date between <  insert valid range > and the quarter ending on <  insert valid range >

Daily Emissions
Update the beginDate to a date between  <  insert valid range > and the quarter ending on <  insert valid range >
Update the endDate to a date between <  insert valid range > and the quarter ending on <  insert valid range >

Monthly
Update one or more years to a year between <  insert valid range > and the quarter ending on <  insert valid range >
Update one or more months to a month between  <  insert valid range > and the quarter ending on <  insert valid range >

Quarterly
Update one or more years to a year between <  insert valid range > and the quarter ending on <  insert valid range >
Update one or more quarters to a quarter between  <  insert valid range > and the quarter ending on <  insert valid range  >

Annual
"Update one or more years to 1980, 1985, 1990, or to a year between 1995  and the quarter ending on <  insert valid range  >

Ozone
Update one or more years to a year between 1995 and the quarter ending on <  insert valid range  >

Facility/ Unit Attributes
"Update one or more years to 1980, 1985, 1990, or to a year between 1995  and the quarter ending on <  insert valid range  >

@tlageman-epa Based on the discussion during dsu on 1/20, I updated the error messages for an out of range date
for all emissions sub types and facility/unit attributes . Let us know if you have any comments/ concerns.

@JanellC  @sdhawan16 I think this looks fine but I think we'd run into an issue with ozone data? I'm assuming the  is the last reported quarter?  Ozone data is only between May 1st and Sept 30th. For example, once data is reported for the 1st quarter of this year, 2022 (Jan - Mar), the error message would say that you could enter in the year 2022, even though no data would exist yet. This is not an issue for annual data because it's value is updated with each reported quarter.

@tlageman-epa For the ozone data error messages, the < insert valid range > is for the latest reporting quarter date. Right now, the way that the validation is working for the ozone API endpoint is that it queries up until the latest reporting quarter. Based on the information you provided, we would need to update the validation for the ozone API endpoint and the ozone data type on the cdd.
We can proceed with updating the validation for ozone, but it would increase the estimate of this ticket and we would need some more clarification surrounding the requirements for ozone validation.
For example, we are unclear when a user should be able to start querying for ozone data in the current year. Should the system provide an error message for the current year until May 1st?  or would the validation function similarly to the latest reporting quarter where the data wouldn’t be made available until after September 30th?

Hourly Emissions
https://api.epa.gov/easey/dev/emissions-mgmt/apportioned/hourly?api_key=T8r7OW4f12XtWKLY7CPgKmKu1WoP3TVG0x4eqmlB&beginDate=2022-01-01&endDate=2022-01-01

Open defect in TestQuality D105

Test Validation for Monthly Emissions API in Run Validation for Monthly Emissions API (linked to Cycle Monthly Emissions API/ UI).

Defect D105 resolved @tlageman-epa


adding data view for GLCFS

created for review and feedback
still needs tests

There are dataset specific tests in MapViewSpec, "Tests for workflow model event handlers" that should also be added for consistency.

There should also be dataset specific tests added to VariableSummary (not sure if that was on your list of remaining things)


fix: push args

@danitseitlin this should be all of them now 👍🏻

@dane-stevens Please notice that this PR caused some errors in existing Redisearch tests so I opened this issue https://github.com/danitseitlin/redis-modules-sdk/issues/42.
If you're interested, you can assign it to yourself. Else ~ I'll take it myself later on. Just please let me know ✌

@dane-stevens Please notice that this PR caused some errors in existing Redisearch tests so I opened this issue https://github.com/danitseitlin/redis-modules-sdk/issues/42.
If you're interested, you can assign it to yourself. Else ~ I'll take it myself later on. Just please let me know ✌


Added Windows 11 to favored topics

Docs Build status updates of commit a81dfd8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add an order parameter to /v2/content

This pull request adds an order parameter to allow publishing apps to order their results by a field other than public_updated_at which was previously hardcoded. We have used the same interface as documented here as suggested by @tijmenb.
This work was completed as part of this ticket:
https://trello.com/c/XJRTeF9f/130-spv2-orders-by-the-wrong-timestamp-on-the-search-index
We decided to limit the fields that you may order by to those that had indexes and left a comment indicating that we should be careful to add an index to any additional fields with which we wish to order. Otherwise, performance would be affected when running the query.

The order direction behaviour feels a bit magic and inflexible (what if you want to order descending on a custom field). Is there a good reason to disallow setting it through a parameter as well?

Please could you elaborate? What do you mean by custom field? Are you referring to a field such as publication_state which is an alias of states.name ?

Actually, ignore me - I misread the code. It's fine :+1:


Remove deprecated workflows

What this PR does / why we need it:
rancher/highlander#89

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist:

[ ] squashed commits into logical changes
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

Looks like we need to remove the 2 required checks now that we've removed the workflows.


Declare cell size as a constant

Many places in the code had distances expressed as magic numbers related to the cell size. This change is intended to make the cell size a configuration constant so that the code is more readily modified for other cell sizes.

Thank you. Just waiting to hear from the original requester before committing.


Build gem locally?

Checked out latest src. Running rake build :
rake build
rake aborted!
Don't know how to build task 'build' (see --tasks)
(See full trace by running task with --trace)

hades:~/Dev/cerberus/gcloud-ruby[master]$ rake --tasks

rake acceptance[project,keyfile,key]   # Runs acceptance tests for all gems
rake acceptance:cleanup[bundleupdate]  # Runs acceptance:cleanup for all gems
rake acceptance:coverage               # Runs acceptance tests with coverage for all gems
rake acceptance:each[bundleupdate]     # Runs acceptance tests for all gems individually
rake console[bundleupdate]             # Start an interactive shell
rake each[bundleupdate]                # Runs rubocop, jsodoc, and tests for all gems individually
rake jsondoc[bundleupdate]             # Runs jsondoc report for all gems individually
rake rubocop[bundleupdate]             # Runs rubocop report for all gems individually
rake test                              # Runs tests for all gems
rake test:coverage                     # Runs tests with coverage for all gems
rake test:coveralls                    # Runs coveralls report for all gems
rake test:each[bundleupdate]           # Runs tests for all gems individually
rake travis:acceptance                 # Runs acceptance tests for CI

To build the v0.12.1 gem try checking out the v0.12.1 tag instead of the master branch. The master branch is transitioning to a new source code layout and not all the guidance is up to date.

Switched to the 0.12.1 tag. Works perfect!
thanks!


Fixes #465 - Allow importing 'ragged' .xlsx files

Thanks!

@hugovk Do you think it's now time to release 2.0?

Yes, now's a good time.

Done.

Thanks! I did the last step in RELEASING.md to create a GitHub release:
https://github.com/jazzband/tablib/releases/tag/v2.0.0


Data file not found

Hi Rakshith
I am looking at your code for reference.
But there is one issue you have used this file  "new_test.csv " in your code file (Home credit Model.ipynb) .But in kaggle there is no such data file .can you please let me know about this .
Regards
Savya

Did you get any solution?


meeko 0.4.0 fails to prepare sample ligand

Taking the sample ligand https://github.com/ccsb-scripps/AutoDock-Vina/blob/develop/example/basic_docking/data/1iep_ligand.sdf.
In docu https://github.com/ccsb-scripps/AutoDock-Vina/blob/develop/docs/source/docking_basic.rst it's said:
mk_prepare_ligand.py -i 1iep_ligand.sdf -o 1iep_ligand.pdbqt
On Meeko 0.2.0 everything was fine.
After upgrade to Meeko 0.4.0 now I have this error:
mk_prepare_ligand.py -i 1iep_ligand.sdf -o 1iep_ligand.pdbqt
/home/lawliet/.local/lib/python3.8/site-packages/meeko/preparation.py:109: RuntimeWarning: Skipping mol (name=STI): has implicit hydrogens
  warnings.warn("Skipping mol (name=%s): has implicit hydrogens" % name, RuntimeWarning)
Traceback (most recent call last):
  File "/home/lawliet/.local/bin/mk_prepare_ligand.py", line 303, in <module>
    pdbqt_string = preparator.write_pdbqt_string()
  File "/home/lawliet/.local/lib/python3.8/site-packages/meeko/preparation.py", line 205, in write_pdbqt_string
    raise RuntimeError("Molecule not OK, refusing to write PDBQT\n\nLOG:\n%s" % self.log)
RuntimeError: Molecule not OK, refusing to write PDBQT

LOG:
molecule has implicit hydrogens

Is this sample not correct anymore or am I missing any additional command like parameter that is required now?

The sample is not correct anymore. Thank you for finding this.
Since v0.3.0 meeko requires input molecules to have explicit hydrogens. We should have added this error message back then.
I've updated the sample in the Vina repository.

@diogomart, thank you for the quick fix. I can confirm now mk_prepare_ligand.py -i 1iep_ligand.sdf -o 1iep_ligand.pdbqt works successfully.


Remove reference to the file macros.vm in module.properties

This was causing errors when loading the extension because the file didn't exist.
Fixes: #101

This also fixes https://github.com/OpenRefine/OpenRefine/issues/6580 and https://github.com/OpenRefine/OpenRefine/issues/6581. Not sure if and how I should refer to them in the commit message.


Parsley.remote loading problem

Hi,
I upgraded to the last version and I use parsley.remote instead parsley but when I load the script through requirejs I have an error

Uncaught TypeError: Cannot read property 'on'

caused by this code at line 2065 in parsley.remote.js

  window.Parsley.on('form:submit', function () {
    this._remoteCache = {};
  });

Any idea?

Are you loading just parsley.remote or both parsley and parsley.remote? It should be only the latter, but the instructions were misleading a while back...

Only parsley.remote, this script seem include parsley

Which version are you using?

2.1.3, I tried the both solutions (import only parsley.remote or parsley and parlsley.remote) same result

Ah ah!
That API is only for 2.2... Please check that out :smile:

Is not the master version the 2.1.3 version? I installed it via bower, how I can use the stable version?

Well, 2.2 is still as a release candidate. Not too sure how to load it via bower, sorry.

Actually, I was wrong, window.Parsley.on should work in 2.1 anyways. Reopening

I can't figure out why you'd get that with 2.1.3.
Can you double check that's the result you get in the console with window.Parsley.version?
I made a fiddle with that version and the remote code loads fine.

The fiddle doesn't use requirejs though, so the problem has to be there... Sorry I can't easily help any further. If you could make a simple jsfiddle that would be great.

http://jsfiddle.net/zfmph5w6/1/
As you can see in console the problem is with window.Parsley

This problem occur only with the minified version

Hi,
I've installed parsley 2.1.3 via npm for browserify. I use require('parsleyjs/dist/parsley.remote') and I have the same error described in the original post.
I don't use the minified version and it still throws this error.

I can confirm this.  I have several sites that use Parsley (thank you!) with RequireJS.  Using the same code, if I use the dist/parsley.min.js loaded via RequireJS, it fails in mysterious ways.  Forms will simply not validate, with no console errors.
If I substitute in the dist/parsley.js version, everything works as expected.  For now, I've just uglified the dist/parsley.js and am using that successfully.  Something is amiss with the dist/parsley.min.js version with RequireJS.

I tried substituting in the latest 2.2.0-rc2 version of Parsley, but it exhibits the same problem.  Unfortunately, Parsley appears to be broke with RequireJS.
Unlike other posters in this thread, I'm not getting any errors.  Parsley just doesn't work, whether initialized via JS or via data-parsley-validate.
Again, loading Parsley via a plain old <script> tag works; loading it via RequireJS fails.

Sorry about this. We're very close of merging the es6 branch into master, which will resolve this loading issue (and also remove the non-remote version)...

Thanks for the response.  I look forward to it, I'll check regularly for the merge.  In the meantime, my forms go on unvalidated :)

FWIW, I tried the es6 branch to see if that'd work for me... but it's still having intermittent issues loading properly when loaded via RequireJS.

What issues exactly with the es6 branch, @khalwat ?

@marcandre I may not have done it exactly right; I just replaced the dist folder from the release branch with the dist folder from the es6 branch.
The issues I had were very similar to what I was having with the release branch:
When loaded with RequireJS, sometimes, ParsleyJS would not work for underdetermined reasons.  The symptoms are the Parsley won't validate blocks, and won't validate on form submission (it'll just hang).
In the same environment, if I load it via a <script> tag, it works properly.
I can give you a live staging URL to take a look at if it'll be helpful.  Should I be doing anything other than grabbing parsley.min.js from dist from the es6 branch?

@marcandre Let me know if there is anything I can do to assist you in tracking down this issue.

A live link would help for sure.
The es6 branch landed in master, btw, so you can use the 2.2.0rc4 release.
Do you have an estimate at how often you get a problem?

@marcandre I updated to 2.2.0rc4 and it seems to be working!  Here is a live URL for you:
http://imawhale.com/apply

Cool. So I'm closing this, but if anybody runs into issues with the current version, let me know!

I just installed it yesterday and have the issue as described at the top of @SebT's post trying to work with Parsley Remote.

@jessemorton Please upgrade to 2.2.0rc4

Thanks for the speedy reply, @marcandre Maybe the NPM module just needs updating on your end? I installed via npm yesterday, but it looks like its v2.1.2. Doing npm update parsleyjs isn't accomplishing anything today.


Biodiesel production testing, per request.

Assuming zero pre-existing stockpile of raw materials, a 15x15 (max size octadic) EIO farm with only AA earthworms for "acceleration" can produce 6400mb of diesel fuel in 10 minutes using wheat and potatoes, assuming sufficient light to grow constantly (lighting or perma-day). The potato growth slightly edges out wheat seed production over 10s of minutes.
This is no-where near close to maxing out even a single processing setup. Without accelerators or agricraft crops for melon abuse, this is the still the most effective crop selection setup. Hemp's higher seed oil rate is counteracted by it's slower growth rate, unless sufficient accelerators are brought to bear to make both crop types an equal harvest speed.
However, assuming sufficient accelerators on the crops to keep a single squeezer and single fermenter supplied at full rate, a single refinery will produce 19000mb of diesel in 60 seconds. The refinery is the restriction in this configuration, with the ratio of Refineries to Squeezers/Fermenter pair at 3 Refineries per 2 of each Squeezer/Refinery.
Difference of 10 mb/s vs 315 mb/s biodiesel production from normal crop growth rate vs full refining rate.

And follow-up testing with Compression Dynamo:
Diesel Gen will turn out ~500k Rf for a bucket of diesel fuel at 4096 rf/t.
Compression dynamo will turn out ~3 million rf for a bucket of diesel fuel at 40 rf/t.
Doesn't seem to be a way at present to upgrade compression dynamos.

compression dynamos can be upgraded now, rf values look solid, biodiesel should be a viable midgame power


Env token

The env doesn't work wherever I put my token in env it says invalid token so I have to use the token from config file please fix it asap

Make secret with token and then put your token over there!


DxDataGrid always displays the loading panel if its data source is provided using a function

See Plunker. As you can see the loading panel is always displayed.

Isn't creating a new datasource on each call the problem? Angular's change detection kicks then in.
Try this:
export class App {
  ds: ODataStore;

  constructor() {
    this.buttonText = 'DevExtreme button!';
    this.ds = new ODataStore({
        url: "http://services.odata.org/V4/Northwind/Northwind.svc/Orders",
        version: 4,
        key: "OrderID",
        keyType: "Int32"
    });
  }
  getDataSource(grid: DxDataGridComponent): ODataStore {
    return this.ds;
}
}

Set the changeDetection option to OnPush to prevent Angular from tracking component entire changes. See the ANGULAR CHANGE DETECTION EXPLAINED article to learn more. I've updated your example.


No coverage information on android

I compiled the honggfuzz for android and got the libhfuzz.a and honggfuzz of arm64-v8a
$ ls ../../honggfuzz/libs/arm64-v8a
android_api.txt  honggfuzz  libhfuzz.a  ndk_toolchain.txt

Then use the democode fuzz_test.c
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <string.h>
#include <inttypes.h>
extern HF_ITER(uint8_t** buf, size_t* len);
void test(char* buf){
    if (buf[0] == 'f') {
      if (buf[1] == 'o') {
        if (buf[2] == 'o') {
          if (buf[3] == '!') {
            abort();
          }
        }
      }
    }
}
int main(void) {
  for (;;) {
    size_t len;
    uint8_t *buf;

    HF_ITER(&buf, &len);
    test(buf);

  }
  return 0;
}

Android.mk
LOCAL_PATH:= $(call my-dir)

include $(CLEAR_VARS)
LOCAL_PATH = .
LOCAL_MODULE := hfuzz
LOCAL_EXPORT_C_INCLUDES := ../../honggfuzz/include
LOCAL_SRC_FILES := ../../honggfuzz/libs/$(TARGET_ARCH_ABI)/libhfuzz.a
include $(PREBUILT_STATIC_LIBRARY)

include $(CLEAR_VARS)
LOCAL_PATH = .
LOCAL_MODULE := hfuzzcommon
LOCAL_EXPORT_C_INCLUDES := ../../honggfuzz/include
LOCAL_SRC_FILES := ../../honggfuzz/obj/local/$(TARGET_ARCH_ABI)/libcommon.a
include $(PREBUILT_STATIC_LIBRARY)

include $(CLEAR_VARS)
LOCAL_STATIC_LIBRARIES := hfuzz hfuzzcommon
LOCAL_SRC_FILES := fuzz_test.c
LOCAL_MODULE := fuzz_test

include $(BUILD_EXECUTABLE)

I can compile fuzz_test successfully. Then put it to android to run, but there is no crash and no coverage update.
------------------------[  0 days 00 hrs 00 mins 06 secs ]----------------------
  Iterations : 3971 [3.97k]
  Mode [3/3] : Feedback Driven Mode
      Target : fuzz_test
     Threads : 4, CPUs: 8, CPU%: 350% [43%/CPU]
       Speed : 552/sec [avg: 661]
     Crashes : 0 [unique: 0, blacklist: 0, verified: 0]
    Timeouts : 0 [1 sec]
 Corpus Size : 1, max: 8192 bytes, init: 2 files
  Cov Update : 0 days 00 hrs 00 mins 06 secs ago
    Coverage : edge: 0/0 [0%] pc: 0 cmp: 0
---------------------------------- [ LOGS ] ------------------/ honggfuzz 2.2 /-
de: 1
[2020-06-04T12:12:45+0800][W][4606] arch_checkWait():233 Persistent mode: pid=11261 exited with status: EXITED, exit code: 1
[2020-06-04T12:12:45+0800][W][4605] arch_checkWait():233 Persistent mode: pid=11263 exited with status: EXITED, exit code: 1

What I did wrong? Could you suggest something, please?

You probably need to add the following flags to fuzz_test.c compilation (as copts/linkopts).
-fsanitize-coverage=trace-pc-guard,trace-cmp,trace-div,indirect-calls

Thanks for your help!  My problem solved after adding the flags.😀
robertswiecki<EMAIL_ADDRESS>于2020年6月4日周四 下午9:23写道：

You probably need to add the following flags to fuzz_test.c compilation
(as copts/linkopts).
-fsanitize-coverage=trace-pc-guard,trace-cmp,trace-div,indirect-calls
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/honggfuzz/issues/342#issuecomment-638844335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQQBG4ICVNEZBBZI3MFVLTRU6N6DANCNFSM4NSICTGQ
.

You probably need to add the following flags to fuzz_test.c compilation (as copts/linkopts).
-fsanitize-coverage=trace-pc-guard,trace-cmp,trace-div,indirect-calls

Thanks for your help!  My problem solved after adding the flags.grinning


Dao with asset

Proposed Changes

Create proposal with asset.

TODO

[ ] update change log

Potential followups

[ ]  please update the changelog.

Update


feat: Adds updateTorrentTrackers function and fixes issue #70

Solves issue #69 and #70.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make this module friendly to users who store their logstash config in a separate git (or other) repo

As it stands, this module doesn't support users who store their logstash configs in a repository separately to their puppet config. I suspect most users who have non-trivial logstash configs would rather store their configs outside of Puppet.
Here are a couple of the issues that prevent the use of a git repo:

Ownership of the files under /etc/logstash (they are all forced to be root only, something that was previously configurable)
The /etc/logstash/conf.d (and /etc/logstash) are created using puppet, meaning that any vcsrepo resource cannot be created there - they have to be placed somewhere else, or underneath those dirs.
No direct support for the vcsrepo resource anywhere in the code

Ideally, the module would either allow the user to store their entire /etc/logstash dir in git, or even just particular subdirs, such as /etc/logstash/conf.d.
Thanks,
Nick

Sorry for the slow reply.
I see the primary use of this module as allowing people to programatically generate pipeline configuration with Puppet and ERB. Apart from that, the module doesn't really do very much except install the package and start the service.
Having said that, it's easy to manage your pipeline config another way and still use the module. Just put the config outside the location that the module is trying to manage and let Logstash know:
$pipeline = '/usr/local/etc/logstash/config/'

class { 'logstash':
  manage_repo  => true,
  repo_version => '5.x',
  settings => {
    'path.config' => $pipeline,
  }
}

vcsrepo { $pipeline:
  ensure   => latest,
  provider => git,
  source   => 'https://github.com/jarpy/logstash-config.git',
  notify   => Service['logstash'],
}

Is something like that appropriate for your site?
Cheers,
Toby.


Last modified date is set to "never"

I'm not sure if this should be open with you or with every project that decided to sanity-check the last-modified date by comparing it against 0, but it appears that, by default, a docker image will (rightfully?) set the last-modified date of a file to an epoch time of 0.
This makes some amount of sense, but does lead at least spring-core's sanity checker for AbstractResource to freak out.  I had to log into the image and modify the image in order to make this go away.
My proposed solution? Honor the last modified dates in the original files,  have a way to declare what date i am modifying by, or use the date that Docker built the image at. All of these sound more truthful than saying it happened on Jan 1, 1970.

Echoing my comment from https://jira.spring.io/browse/SPR-12862, please note that java.io.File.lastModified() is defined to return 0 as an indicator for a non-existing file or an I/O error when checking the underlying resource.
So any Java-based code is unable to differentiate between actual Jan 1, 1970 timestamps and I/O errors. Setting the timestamp one second ahead to Jan 1, 1970, 0:00:01 would help already :-)

@nwertzberger Can you explain how you managed to create these files? Which filesystem are you using?
When I add a file to a container with COPY or ADD, it gets the date from the file. Could you append your output from docker info and docker version as well?

  I am using the ADD tool's functionality for adding tarballs.
FROM java:8
MAINTAINER Nicholas Wertzberger

ADD decision-engine/*.tar.gz /

EXPOSE 9030
EXPOSE 9010
EXPOSE 9009

CMD touch -m /decision-engine/etc/pages/*
ENTRYPOINT /decision-engine/bin/decision-engine console

Related StackOverflow
http://stackoverflow.com/questions/29337432/spring-templates-in-docker-container/29337588?noredirect=1#comment46934375_29337588

+1

Hello!
We are no longer accepting patches to the Dockerfile syntax as you can read about here: https://github.com/docker/docker/blob/master/ROADMAP.md#22-dockerfile-syntax
Mainly:

Allowing the Builder to be implemented as a separate utility consuming the Engine's API will open the door for many possibilities, such as offering alternate syntaxes or DSL for existing languages without cluttering the Engine's codebase

Then from there, patches/features like this can be re-thought. Hope you can understand.


Add option to limit the number of backups created using the backup scheduler feature

Currently when scheduled a recurrent backup, it will create any number of backups.
Add a setting to set the maximum number of backups created by a scheduled backup.

Implemented feature


TEST(day_10): add find_next_neighbors test

First step: find neighbors for starting_pipe
Second step : find neighbors for previously found first neighbor

@dariannax3, please bear in mind, that to run the uts, you need to comment out two last tests.


Handle Windows network drives

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

21 of 23 (91.3%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 83.176%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hooks/useConfig.ts
1
2
50.0%

src/utils/Path.ts
10
11
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2216

Relevant Lines:
2592

💛  - Coveralls


Allow reinstalling packs

Adds a flag for a forced pack installation.
Either a --force-reinstall or -F on the add /  pack add commands enables installing an already installed pack, purging it before reinstalling.
Closes #77.

Maybe just a detail, however could we do the purge of the existing pack only if we successfully installed the pack to a temporary folder. In this way the user still retains the current state in case the installation fails, or in case the installation process is "cancelled" using ctrl-c ?

Maybe just a detail, however could we do the purge of the existing pack only if we successfully installed the pack to a temporary folder. In this way the user still retains the current state in case the installation fails, or in case the installation process is "cancelled" using ctrl-c ?

Ok, so a sort of a "dry run" before purging the pack? Could avoid download/cache issues, will look into it

I would not call it a "dry run" as such as you are actually executing the installation, however you wait until the extraction into a temporary directory successfully completed, then you remove the previous installation, followed by renaming the temporary folder to the installation folder.
ARM.CMSIS.5.8.0.pack usually installs to $CMSIS_PACK_ROOT/ARM/CMSIS/5.8.0
You could e.g. always unzip the pack to $CMSIS_PACK_ROOT/ARM/CMSIS/tmp_5.8.0
once complete you could check whether $CMSIS_PACK_ROOT/ARM/CMSIS/5.8.0 exists and remove it if it does
and then rename to $CMSIS_PACK_ROOT/ARM/CMSIS/5.8.0
Maybe there are smarter ways to do it, this should just outline the process.

Yes, "dry run" wasn't the best term to describe it, and the process you mentioned is how we intend on approaching it.

It looks good to me, Thanks for the updates @lud0v1c !


Navbar reloads every time a new page is opened

https://github.com/frappe/wiki/assets/139349833/e12432b5-5ebb-4f77-9a81-c2331711ece5
@BreadGenie I know you're not focussed on Wiki right now, but this is a buggy issue. Why do we reload and scroll the navbar every time a page opens? It leads to a poor reading experience. Can we please look into this?
CC: @rmehta

Why do we reload and scroll the navbar every time a page opens? It leads to a poor reading experience. Can we please look into this?

I agree with it being poor UX. This happens because Wiki is a static site. So everytime you navigate to a different page it'll load all the HTML again and again. We are doing it for a good reason which is SEO. This particular issue could be solved by either a Vue SSR rewrite or by adding client side routing using a router library (but I reckon it could impact SEO (take it with a pinch of salt though)). Both needs a good chunk of time to implement.
I'll take a look at this again once I make some time.

Thanks for acknowledging. Let us implement the fix.
Most of the traffic we get on the docs is directly from google search... so it might not impact SEO.
Most other docs are significantly easy to navigate. eg. https://docs.stripe.com/payments


[9.0] Destroy authentication

With the release of Laravel 8, the development team has released a new starter kit Jetstream.
It is a replacement for the laravel/ui package currently used by the platform. This is a major change for which, in fact, it was impossible to prepare in advance. New product releases are hidden and not shown until the release.
Some features began to compete with the official packages:

Authorization / Password recovery and other pages began to differ
Two-factor authentication
Roles (Groups)

In fact, this will soon become mainstream and other options will not be competitive.
I have no desire to go against the prevailing trend (I have no joy about this), so I see the current decision to release a major release, which completely removes authorization from the package.
In fact, we will completely lose the login pages, password recovery pages, the blocked page, two-factor authentication, and some other less noticeable things that I have been working on for a year.
This will make the login threshold higher as users won't get it out of the box. But the entire platform is built for an authorized user, so I suggest using a neutral authorization method via HTTP Basic Authentication.
To at least somehow ease the entry threshold, you can add a new page to the documentation, where it was reported that the user himself needs to choose a package for this.
As far as roles and teams are concerned, little time has passed to make a decision about any decision on this matter. Therefore, I propose to leave the system of roles and permissions.
If you have any suggestions, comments or want to help, please write here.

Hey @RomainMazB.
Now there is no question of removing roles and permissions.
Only authorization and what is connected with it.

Ok I've misread this part:

As far as roles and teams are concerned, little time has passed to make a decision about any decision on this matter. Therefore, I propose to leave the system of roles and permissions.

I was definitely not in my shoes yesterday!
If only the authorization is concerned, my though as I've said would be 'ok, I never use it anyway and if I want, I just need to create a Jetstream auth page and point to its controller and redirect to the Orchid Home'
But now I'm on the other side of the line: why would you keep the roles and permission if it's already done in Jetstream?
For your mindsafe, you could just leave the responsibility to maintain this part to the Laravel team, so you won't never see any issue about Role or Permission. Just put some examples in the documentation to let us know how to work with them in Orchid. I could write this part in the documentation for you ( but not in Russian, that's out my capabilities ^^' ).
I feel like Orchid Permissions is mostly the same as Jetstream Permissions purpose, and so do Roles.

I read the Jetstream docs and I think it's more for the public part.
As an example, organizations or groups within an organization on GitHub. Small quote:

Jetstream's team features allow each registered user to create and belong to multiple teams. By default, every registered user will belong to a "Personal" team. For example, if a user named "Sally Jones" creates a new account, they will be assigned to a team named Sally's Team. After registration, the user may rename this team or create additional teams.

Therefore, now it is very similar, but should not be a complete replacement. I will learn it soon.
Also, it is not included by default even in Jetstream, but at Orchid a very important access system, for example, to upload a file to the server. Many examples, such as filters use roles.

I have new information.
This change will also affect resource publishing.
Due to the fact that she relies entirely on https://laravel.com/docs/7.x/frontend#adding-presets
Example from the documentation:
use Laravel\Ui\UiCommand;

UiCommand::macro('nextjs', function (UiCommand $command) {
    // Scaffold your frontend...
});

This means that the commands: 'php artisan ui orchid' and php artisan ui orchid-source will not work.
This was added here https://github.com/orchidsoftware/platform/issues/915
As far as I understand, there is no alternative in jetstream for this.

I've just tested with a fresh installation of Laravel 8 + Jetstream with the livewire frontend, the commands you said are ok.
But another stuff is the fact that the /dashboard uri is used by jetstream as default, Orchid must use another to not be in conflict with the jetstream dashboard
During my test I've ran into a tiny problem though, the assets compilation files crashed due to a not found on frappe-charts.min.css. I've made a PR to fix it.

I've just tested with a fresh installation of Laravel 8 + Jetstream with the livewire frontend, the commands you said are ok.

They are fine as long as there is a laravel/ui dependency. The removal of which we are discussing here.

But another stuff is the fact that the /dashboard uri is used by jetstream as default, Orchid must use another to not be in conflict with the jetstream dashboard

Thank you for paying attention to this. have to change this to admin

I'm currently trying to make Orchid work with Jetstream (I definetely want the bests of both :) ). With the Jetstream Roles and Permissions.
If it's ok for you, I will edit this comment to list some conflictual/cloned stuff:

The User migration and model stubs: both implements 2fa authentication

I have made the following changes so far:

Changed the default prefix to admin
Removed dependency on laravel/ui
Removed password recovery option
Removed last login column
Removed two-factor authentication feature
Removed UI presets

Important.
Simple authorization and remembering remained in the package.
Everyone at any moment can turn off this page.

Думаю роли точно пока трогать смысла нет. Тут как много пакетов так и велосипедов, и наврятли все метнутся куда-то сразу по крайней мере.
С аутентификацией изначально виделся такой вариант более подходящим. Но сейчас из пакета это очень удобно работает.  У Nova, Spark есть альтернативы и проектов которым нужен этот функционал меньше чем тем, кому требуется авторизация. Пакет laravel/ui они убивают, фактически на официальном уровне остался только laravel/fortify, для которого есть оболочка Jetstream, которую конечно можно будет поменять и надеюсь сообщество сделает такие же расширения с другими js/css фреймворками.
Думаю логичным шагом будет так же уйти от использования laravel/ui. И предложить выбирать это на вкус.
Обращаю внимание, что страница входа остаётся в пакете, просто больше не привязана к пакету laravel/ui.
То есть фактически, в плане выбора или кастомных страниц входа/восстановления пароля ничего не меняется.
Проблема заключается только, в том, 2fa может конфликтовать/конкурировать c официальным пакетом.

Может быть следует сделать отдельный пакет? Например, orchid-fortify для возможности сохранить функционал прошлых версий для 2fa


CompoundGeometry meshing failing

Describe the bug
Under certain conditions, the CompoundGeometry mesh creation step (geometry.create_mesh) is failing.
To Reproduce
import sectionproperties.pre.sections as sections
from sectionproperties.analysis.cross_section import Section

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)

geometry = sections.CompoundGeometry([s1,s2])
geometry = geometry.rotate_section(angle=30, rot_point='center')

geometry.plot_geometry()
geometry.create_mesh(mesh_sizes=[0.2, 0.1])
section = Section(geometry)
section.display_mesh_info()

triangle.build produces errors in geometry.create_mesh(mesh_sizes=[0.2, 0.1]):
Internal error in segmentintersection():
  Topological inconsistency after splitting a segment.
  Please report this bug to<EMAIL_ADDRESS>  Include the message above, your input data set, and the exact
    command line you used to run Triangle.

In more extreme cases such as example_mirr_rot.py (after updating to run with v2) the process crashes.
Interestingly if the rotation step is either 0, 90, 180, ... the meshing is successful. For example,
import sectionproperties.pre.sections as sections
from sectionproperties.analysis.cross_section import Section

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)

geometry = sections.CompoundGeometry([s1,s2])
geometry = geometry.rotate_section(angle=90, rot_point='center')

geometry.plot_geometry()
geometry.create_mesh(mesh_sizes=[0.2, 0.1])
section = Section(geometry)
section.display_mesh_info()

Mesh Statistics:
--48 nodes
--17 elements
--2 regions

Expected behaviour
Meshing step completing.
Additional context
After some investigation, I think it is because the triangle is having a hard time with the facets:
import sectionproperties.pre.sections as sections
from sectionproperties.analysis.cross_section import Section

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)

geometry = sections.CompoundGeometry([s1,s2])
print(f"points: {geometry.points}")
print(f"facets: {geometry.facets}")

points: [[0.0, 0.0], [1.0, 0.0], [1.0, 1.0], [0.0, 1.0], [1.0, 0.25], [1.5, 0.25], [1.5, 0.75], [1.0, 0.75]]
facets: [[0, 1], [1, 2], [2, 3], [3, 0], [4, 5], [5, 6], [6, 7], [7, 4]]

These are the facets of the individual geometries and I think the meshing would prefer the combined shape facets:
points: [[0.0, 0.0], [1.0, 0.0], [1.0, 1.0], [0.0, 1.0], [1.0, 0.25], [1.5, 0.25], [1.5, 0.75], [1.0, 0.75]]
facets: [[0, 1], [1, 4], [4, 7], [7, 2], [2, 3], [3, 0], [4, 5], [5, 6], [6, 7], [7, 4]]

So:
import sectionproperties.pre.sections as sections
from sectionproperties.analysis.cross_section import Section

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)

geometry = sections.CompoundGeometry([s1,s2])
geometry_aug = sections.CompoundGeometry.from_points(
    geometry.points,
    [[0, 1], [1, 4], [4, 7], [7, 2], [2, 3], [3, 0], [4, 5], [5, 6], [6, 7], [7, 4]],
    geometry.holes,
    geometry.control_points
)
geometry_aug = geometry_aug.rotate_section(angle=30, rot_point='center')

geometry_aug.plot_geometry()
geometry_aug.create_mesh(mesh_sizes=[0.2, 0.1])
section = Section(geometry_aug)
section.display_mesh_info()

Mesh Statistics:
--52 nodes
--19 elements
--2 regions

@normanrichardson Thanks for finding this. Am going to investigate.

@normanrichardson, yes, I see what's happening here. When a transformation is performed on this geometry, we get a floating point error gap between the two shapes. This can be observed by using their _repr_svg_() as shown below:

Where the red shapes indicate an "invalid" geometry (in shapely's eyes, not sectionproperties), because the geometries share an edge, and the green shapes indicate a "valid" geometry because they are not actually touching.
Currently, the code in the sectionproperties transformation methods (e.g. .rotate_section()) iterate through each geometry and performs the transformation on each geometry separately. I thought, "Why not just perform the transformation on the MultiPolygon instead of each individual Polygon?" So, I tried that but it did not fix the problem.
It seems to be an inconsistent problem, as one might expect from a floating point error. I tried iterating the rotation from 1 - 360 degrees and displaying the svg each time. It seems that it's only on certain angles where I get green geometries instead of red geometries.
I see your solution and that makes sense. It falls in the category of what I call "advanced geometry" where the user has to override the default shapely behaviour to make it give you the section you want (with nodes and facets exactly where you want them). I will have to think more on this.

@normanrichardson Ah! Yes! It is just like the example I give in the "Advanced Geometry" section in the docs. This is excellent because the example I used does not cause an error if done in the conventional way. HOWEVER! This example DOES cause an error which makes for a better example.
Here is the way to model the geometry to not cause a mesh error:
import sectionproperties.pre.sections as sections
from sectionproperties.analysis.cross_section import Section

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)

# geometry = sections.CompoundGeometry([s1,s2])
geometry = ((s1 - s2) | s1) + s2
geometry_rot = geometry.rotate_section(angle=30, rot_point='center')

geometry_rot.plot_geometry(labels=["points", "facets"])
geometry_rot.create_mesh(mesh_sizes=[0.2, 0.1])
section = Section(geometry_rot)
section.display_mesh_info()

So, I should update the example in the Advanced Geometry with this example to illustrate what a meshing error looks like, clues on how to identify the cause (disconnected geometry), and how to model it to remedy it.

@connorferster thanks I see, that seems to work and the mesher can find the common edge.
Are there any drawbacks to performing these operations in the CompoundGeometry constructor? Looking at the overridden operators I'm guessing that if two geometries share a domain with 2 different materials, then the "1st" material will be assigned to that domain.

@normanrichardson,
Using the CompoundGeometry constructor should be the same as using the + operator. Here is an example:
import sectionproperties.pre.sections as sections
from sectionproperties.pre.pre import Material
from sectionproperties.analysis.cross_section import Section

mat_1 = Material("Material 1", 200e3, 0.3, 300, "yellow")
mat_2 = Material("Material 2", 72e3, 0.25, 100, "purple")

s1 = sections.rectangular_section(1,1)
s2 = sections.rectangular_section(0.5,0.5).shift_section(1,0.25)
s1.material = mat_1
s2.material = mat_2
geometry_fixed = sections.CompoundGeometry([(s1 - s2), s2])
geometry_fixed_rotated

The materials assigned to each geometry stay with the geometry and then each gets added to the CompoundGeometry.
The other operators, |, -, &, ^ do take the first geometry's material as precedence when the geometries become combined but the + operator just keeps both geometry material assignments.

Thanks for finding @normanrichardson and thanks for investigating @connorferster!
Now that the docs have been updated are we happy to close this one?


Elasticsearch 5.x  NewCompletionSuggester 返回score 为0

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[*] elastic.v5 (for Elasticsearch 5.x)
Please describe the expected behavior
在用 NewCompletionSuggester  发现返回结果得分全部为0
Please describe the actual behavior
源码search.go 中
// SearchSuggestionOption is an option of a SearchSuggestion.
// See https://www.elastic.co/guide/en/elasticsearch/reference/5.6/search-suggesters.html.
type SearchSuggestionOption struct {
Text         string           json:"text"
Index        string           json:"_index"
Type         string           json:"_type"
Id           string           json:"_id"
Score        float64          json:"score"
Highlighted  string           json:"highlighted"
CollateMatch bool             json:"collate_match"
Freq         int              json:"freq" // from TermSuggestion.Option in Java API
Source       *json.RawMessage json:"_source"
}
Any steps to reproduce the behavior?
Score        float64          json:"score"  应该 为   Score        float64          json:"_score"

Oh well... now also ES 5.x... we had that in 6.x as well. See #747.

Here's the fix for ES 6.x: https://github.com/olivere/elastic/pull/747#issuecomment-385431239

Fixed in #1364


[BUG] After configuring http-proxy, harvester is not accessible

Describe the bug

http-proxy configure some wrong values, harvester will be inaccessible, the page appears 503 error
To Reproduce
Steps to reproduce the behavior:

Go to the http-proxy setting page
Set the values as follows,  click Save button.

Expected behavior

Support bundle

Environment

Harvester ISO version:  v1.0.3-rc2
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Changing this setting might cause a short downtime for single-node clusters.
https://docs.harvesterhci.io/v1.0/settings/settings/

This is as expected, so close the issue.


[nrfconnect] Bump SDK version in Docker

Problem
The new version of NRF SDK contains a new API for performing multi-image DFU for nrf53.
Change overview
Updated nRF Connect SDK to 5ea8f7fa9 revision that includes the new DFU API.
Testing
Did smoke tests.

/rebase


Batman™: Arkham Origins Blackgate [PCSE00269]

App summary

App name: ?
App serial: ?
App version: ?

Vita3K summary

Version: v?
Build number: ?
Commit hash: https://github.com/vita3k/vita3k/commit/[commit]
CPU backend:
GPU backend:

Test environment summary

Tested by: ?
OS: Windows 10/macOS/Linux Distro, Kernel Version?
CPU: AMD/Intel?
GPU: AMD/NVIDIA/Intel?
RAM: ? GB

Issues

Screenshots

Log
Recommended labels

A?
B?
C?

the graphics is a bug

the graphics is a bug

you issue is totaly invalid, you  have writed nothing


List all accounts in the service

As a [role]
I need [function]
So that [benefit]
Details and Assumptions
* [document what you know]

Acceptance Criteria
gherkin
Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Hello, we tried to solve the issue.
This is what we did:
Added the list_accounts function to handle GET requests for all accounts. Updated the test file to include a test case for listing accounts.
You can review changes in this commit: https://github.com/mnmnk43434/elabbk-devops-capstone-project-8/commit/6e8845a3e126a34ab601660b987094afdd33d9f6.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


Declare support for SAI in Persistence

Avoid relying on the Persistence name to
determine whether SAI is supported.

something failing.

Socket timeouts :face_with_head_bandage:


Fix axis Bug in MKLDNN Softmax

Description
Apply CheckAxis to MKLDNN Softmax function in order to call MKLDNN correctly.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@pengzhao-intel @TaoLv

@szha unit tests with negative axis have been added and passed.

@szha what's the difference of softmax/log_softmax/SoftmaxActivation in mxnet? and which one is the most widely used by mxnet users? Seems only softmax is optimized here with mkldnn primitive.

right, the SoftmaxActivation is an older operator and is not actively developed anymore. Going forward we are using softmax/log_softmax.

@szha same question for SoftmaxOutput operator? https://github.com/apache/incubator-mxnet/blob/master/src/operator/softmax_output.cc#L47


Serve the web page from mainpy

server mounts frontend and serve the html along with all the dependencies, game runs on http://<IP_ADDRESS>:8000/game. could not serve at root.

test and then merge


IAP needs some code cleanup to comply w/ Google Code Style.

Found in #5379
#
# iap
#

[ERROR] src/main/java/com/example/iap/BuildIapRequest.java:[18,1] (whitespace) EmptyLineSeparator: '//' should be separated from previous line.
[ERROR] src/main/java/com/example/iap/VerifyIapRequestHeader.java:[18,1] (whitespace) EmptyLineSeparator: '//' should be separated from previous line.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2:check (default-cli) on project iap-samples: You have 2 Checkstyle violations. -> [Help 1]

Fixed with #5621


python: Add python3-autobahn package definition

Add python3-autobahn package definition for Debian, Ubuntu, Fedora.
python3-autobahn package definition is required for rosbridge_suite, specifically for https://github.com/RobotWebTools/rosbridge_suite/pull/460 to work.

Oh, sorry! Sure, hope this is enough:
Ubuntu: https://packages.ubuntu.com/bionic/python3-autobahn, https://packages.ubuntu.com/focal/python3-autobahn
Debian: https://packages.debian.org/stretch/python3-autobahn, https://packages.debian.org/buster/python3-autobahn
Fedora: https://apps.fedoraproject.org/packages/python3-autobahn


Corrected typos and formatting

@hderry please correct the merge conflicts.  This can usually be done with pulling in the main branch changes, correcting the conflicts, and updating this PR.

@underwoo merge conflicts have been corrected


Confusion about _etag concurrency control for single-region writes

Reading the section about optimistic concurrency control one gets the impression that Cosmos DB automatically ensures on a protocol level that an update on an item always happens on the latest version of that item for single-region writes. Using _etags and the If-Match header is not mentioned for single-region writes.
The usage of _etag is only mentioned in the next section about multi-region writes.
This is confusion. I ran a little experiment and without setting the _etag for updates in an account configured for single-region writes only the last update always wins, even if it is based on a then outdated version of that item. So there is no magic single-region write way of handling concurrency control. Tracking the _etag and setting the If-Match header is always required.

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

ID: 58a1f8fb-77e3-acac-eb1e-05571fc4e018
Version Independent ID: 4bd2399c-7298-848d-e04d-88b74b132dde
Content: Database transactions and optimistic concurrency control in Azure Cosmos DB
Content Source: articles/cosmos-db/sql/database-transactions-optimistic-concurrency.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

@thomasbrueggemann Thank you for your feedback. We will investigate and update the thread further.

#assign:seesharprun
Hello @thomasbrueggemann, your assumption is correct. If you do not set the If-Match header, then the latest update always wins. Setting the If-Match header only conditionally updates the item with the eTags match, otherwise it rejects the operation outright. Optimistic Concurrency Control is really something you implement client-side, and there's no server-side magic behind this.
My reading of this paragraph leads me to believe this is explained in the article:

Every item stored in an Azure Cosmos container has a system defined _etag property. The value of the _etag is automatically generated and updated by the server every time the item is updated. _etag can be used with the client supplied if-match request header to allow the server to decide whether an item can be conditionally updated. The value of the if-match header matches the value of the _etag at the server, the item is then updated. If the value of the if-match request header is no longer current, the server rejects the operation with an "HTTP 412 Precondition failure" response message. The client then can re-fetch the item to acquire the current version of the item on the server or override the version of item in the server with its own _etag value for the item. In addition, _etag can be used with the if-none-match header to determine whether a refetch of a resource is needed.

With docs, we are always looking for improvement. Is there another way you would word this to be clearer?
#label:"awaiting-customer-response"

@seesharprun Thanks for your feedback!. I agree the paragraph you quoted explains this clearly if read on its own. I read it in context of the multi-region writes mentioned just before the quoted paragraph.
My suggestion would be to move this paragraph up above the paragraph about single-region writes. Then it establishes the baseline that the _etag is always needed + explanation why. And then the next two paragraphs about single region and multi region writes are understood as specific details per write region configuration of how the _etag behaves.

We are publishing a new version of the article with that section re-organized to be a bit clearer.
This issue will auto-close once the new article enters our publishing pipeline, and it should be available shortly after.
Thanks @thomasbrueggemann!


strip spaces from the name of classes in affinity.csv or classes.csv

I created a new dataset and started getting a lot of  errors, number of data being zero, etc. Turns out I formed the classes.csv and affinity.csv as follows:
classes.csv
item1, item2
affinity.csv
item1, item2
1, -1
-1,1
because both have a space behind item2 it doesn't through the error but it also doesn't recognise the name in the list of data

Related to #63

with open(self.filename, 'r') as f:
reader = csv.reader(f, delimiter=',', quoting=csv.QUOTE_NONE)
return [[x.strip() for x in row] for row in reader]

Save colours in a df for each class and call from data frame


Add discard draft confirmation

Description
Add a confirmation modal when admins discard a question draft.
Checklist
General

[x] Add confirmation modal for Discard Draft button

Issue(s) this completes
Fixes #2105

Some failing browser tests. Will resolve before sending back for review.

https://user-images.githubusercontent.com/30369272/217658410-93ae0c66-af02-4ade-9014-d2ad17b14761.mov
Screen recording of the confirmation box is above.


[SPARK-33673][SQL] Avoid push down partition filters to ParquetScan for DataSourceV2

What changes were proposed in this pull request?
As described in SPARK-33673, some test suites in ParquetV2SchemaPruningSuite will failed when set parquet.version to 1.11.1 because Parquet will return empty results for non-existent column since PARQUET-1765.
This pr change to use dataSchema instead of schema to build pushedParquetFilters in ParquetScanBuilder to avoid push down partition filters to ParquetScan for DataSourceV2
Why are the changes needed?
Prepare for upgrade using Parquet 1.11.1.
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Pass the Jenkins or GitHub Action

Manual test as follows:

mvn -Dtest=none -DwildcardSuites=org.apache.spark.sql.execution.datasources.parquet.ParquetV2SchemaPruningSuite -Dparquet.version=1.11.1 test -pl sql/core -am

Before
Run completed in 3 minutes, 13 seconds.
Total number of tests run: 134
Suites: completed 2, aborted 0
Tests: succeeded 120, failed 14, canceled 0, ignored 0, pending 0
*** 14 TESTS FAILED ***

After
Run completed in 3 minutes, 46 seconds.
Total number of tests run: 134
Suites: completed 2, aborted 0
Tests: succeeded 134, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

cc @wangyum

Test build #132381 has started for PR 30652 at commit be6cfc8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36981/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36981/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36981/

Test build #132381 has finished for PR 30652 at commit be6cfc8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132381/

Thanks for fixing this so quickly.

Test build #132402 has started for PR 30652 at commit fb01c3f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37002/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37002/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37002/

Test build #132402 has finished for PR 30652 at commit fb01c3f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132402/

retest this please.

Test build #132424 has started for PR 30652 at commit fb01c3f.

Test build #132424 has finished for PR 30652 at commit fb01c3f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37024/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132424/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37024/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37024/

Local test org.apache.spark.sql.hive.thriftserver.HiveThriftHttpServerSuite all passed
Discovery starting.
Discovery completed in 906 milliseconds.
Run starting. Expected test count is: 3
HiveThriftHttpServerSuite:
20:03:14.455 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
20:03:14.455 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.transport.mode is deprecated.
20:03:14.455 WARN org.apache.hive.jdbc.Utils: Please use transportMode like so: jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
20:03:14.456 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
20:03:14.456 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.thrift.http.path is deprecated.
20:03:14.460 WARN org.apache.hive.jdbc.Utils: Please use httpPath like so: jdbc:hive2://<host>:<port>/dbName;httpPath=<http_path_value>
20:03:38.415 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
- JDBC query execution
20:03:38.417 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.transport.mode is deprecated.
20:03:38.417 WARN org.apache.hive.jdbc.Utils: Please use transportMode like so: jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
20:03:38.417 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
20:03:38.417 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.thrift.http.path is deprecated.
20:03:38.417 WARN org.apache.hive.jdbc.Utils: Please use httpPath like so: jdbc:hive2://<host>:<port>/dbName;httpPath=<http_path_value>
- Checks Hive version
20:03:38.901 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
20:03:38.901 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.transport.mode is deprecated.
20:03:38.901 WARN org.apache.hive.jdbc.Utils: Please use transportMode like so: jdbc:hive2://<host>:<port>/dbName;transportMode=<transport_mode_value>
20:03:38.901 WARN org.apache.hive.jdbc.Utils: ***** JDBC param deprecation *****
20:03:38.901 WARN org.apache.hive.jdbc.Utils: The use of hive.server2.thrift.http.path is deprecated.
20:03:38.901 WARN org.apache.hive.jdbc.Utils: Please use httpPath like so: jdbc:hive2://<host>:<port>/dbName;httpPath=<http_path_value>
- SPARK-24829 Checks cast as float
Run completed in 52 seconds, 636 milliseconds.
Total number of tests run: 3
Suites: completed 2, aborted 0
Tests: succeeded 3, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

Test build #132456 has started for PR 30652 at commit b9f8eb2.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37057/

Test build #132456 has finished for PR 30652 at commit b9f8eb2.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Waiting for SPARK-33705 to fix UTs in thriftsever module

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132456/

Test build #132749 has started for PR 30652 at commit 13bfda3.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/37349/

Thank all. Merged to master.

Thanks for your review @wangyum @viirya @cloud-fan @gengliangwang  ~

Test build #132749 has finished for PR 30652 at commit 13bfda3.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait CheckAnalysis extends PredicateHelper with LookupCatalog
case class UnresolvedView(
case class Decode(params: Seq[Expression], child: Expression) extends RuntimeReplaceable
case class StringDecode(bin: Expression, charset: Expression)
case class NoopCommand(
case class ShowTableExtended(
case class DropView(
case class RepairTable(child: LogicalPlan) extends Command
case class AlterViewSetProperties(
case class AlterViewUnsetProperties(
case class CacheTable(
case class CacheTableAsSelect(
trait BaseCacheTableExec extends V2CommandExec
case class CacheTableExec(
case class CacheTableAsSelectExec(


[WIP] Tests for Proxy

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

moved to #19


HDDS-2037. Fix hadoop version in pom.ozone.xml.

@anuengineer Until now all the testing is done with hadoop 3.2.0 and also the previous ozone release (0.4.0-alpha) was done with hadoop 3.2.0 as dependency.
Is there any reason to go to 3.1.0 now?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
72
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
261
Maven dependency ordering for branch

+1
mvninstall
1771
trunk passed

+1
compile
1417
trunk passed

+1
mvnsite
1706
trunk passed

+1
shadedclient
5936
branch has no errors when building and testing our client artifacts.

+1
javadoc
517
trunk passed

_ Patch Compile Tests _

0
mvndep
29
Maven dependency ordering for patch

+1
mvninstall
2166
the patch passed

+1
compile
1418
the patch passed

+1
javac
1418
the patch passed

+1
mvnsite
1620
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
6
The patch has no ill-formed XML file.

+1
shadedclient
777
patch has no errors when building and testing our client artifacts.

+1
javadoc
526
the patch passed

_ Other Tests _

-1
unit
3594
root in the patch failed.

+1
asflicense
60
The patch does not generate ASF License warnings.

16897

Reason
Tests

Failed junit tests
hadoop.ozone.container.server.TestSecureContainerServer

hadoop.ozone.client.rpc.TestOzoneRpcClientForAclAuditLog

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.security.TestRaceWhenRelogin

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1351/2/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 1f29a6d56193 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
personality/hadoop.sh

git revision
trunk / 4379370

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1351/2/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1351/2/testReport/

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

modules
C: . hadoop-hdds hadoop-hdds/server-scm hadoop-ozone/ozone-recon U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1351/2/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

I think we already started to use 3.2 specific APIs. Some of our requirements are included in hadoop 3.2 but not in 3.1.
If we need any fixes in the hadoop common we should wait until hadoop 3.3. Using 3.1 it would be even harder.
I would use 3.2 as before.


When using userlist I get KeyError: 'profile_banner_url'

Hi,
Running a simple: twint --userlist inputlist --user-full
(the userlist.txt file is in the same directory)
I get the following output: -
MY-MACKBOOK:~ myusername$ twint --userlist inputlist --user-full
CRITICAL:root:twint.get:User:'profile_banner_url'
ERROR:root:twint.run:Twint:Lookup:Unexpected exception occurred.
Traceback (most recent call last):
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 307, in Lookup
await get.User(self.config.Username, self.config, db.Conn(self.config.Database))
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/get.py", line 228, in User
await Users(j_r, config, conn)
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/output.py", line 177, in Users
user = User(u)
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/user.py", line 49, in User
_usr.background_image = ur['data']['user']['legacy']['profile_banner_url']
KeyError: 'profile_banner_url'
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.8/bin/twint", line 8, in
sys.exit(run_as_command())
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/cli.py", line 339, in run_as_command
main()
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/cli.py", line 324, in main
run.Lookup(c)
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 386, in Lookup
run(config)
File "/Users/davidbarrowcliff/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 329, in run
get_event_loop().run_until_complete(Twint(config).main(callback))
File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 235, in main
await task
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 270, in run
await self.Lookup()
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/run.py", line 307, in Lookup
await get.User(self.config.Username, self.config, db.Conn(self.config.Database))
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/get.py", line 228, in User
await Users(j_r, config, conn)
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/output.py", line 177, in Users
user = User(u)
File "/Users/myusername/Library/Python/3.8/lib/python/site-packages/twint/user.py", line 49, in User
_usr.background_image = ur['data']['user']['legacy']['profile_banner_url']
KeyError: 'profile_banner_url'

All sorted - I saw the fix posted.


Smile: proper use of private functions and parameters

I have made a start with the Smile code. The Stick code is probably next...

Version not yet updated, let's include related Stick-code updates as well.


fix(passcode): presentation style fullscreen (16388)

https://issues.developers.mega.co.nz/issues/16388

I saw one thing non related with this PR. The status bar when the passcode is presented is white instead of black, I did not saw anything related with the UIStatusBarStyle in the code 😕

I saw one thing non related with this PR. The status bar when the passcode is presented is white instead of black, I did not saw anything related with the UIStatusBarStyle in the code 😕

I merged the PR because the issue you found is not related with this PR. Please fill an issue in redmine with the issue you observed.
Thanks

Yes, sure. Here you have the ticket


Redirect Manager: support for 307 and 308 redirects

Required Information
This is not a bug, but a request for feedback on supporting 307 and 308 redirection codes.
Expected Behavior
As a Redirect Manager, when I set up a redirect I usually want to set a status code of 301 or 302, indicating a permanent or a temporary redirect.
In some cases, though, a 307 or 308 is required, e.g. for some SPA functionality that will not work properly with a 301.
Therefore, these values should also be available to support borderline cases out of the box.
Adding these two codes will not increase the cost for ACS but if the case comes around for a client it will provide great value to be able to support it, otherwise, the client would have to adapt the core functionality of the ACS Commons value for something quite trivial.

@sozores here you go: https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/3034

Thank you @YegorKozlov !


buku: fix failing bukuserver build

Description of changes
SQLAlchemy-Utils v0.36.6 package override build is failing.

This is due to a patch in the original SQLAlchemy-Utils package which
broke the build of this package override:

```bash
> applying patch /nix/store/pd6anhwbf0in3r3jhi3sbn5v2fjs0mf2-skip-database-tests.patch
> patching file conftest.py
> Hunk #1 FAILED at 61.
> Hunk #2 succeeded at 98 (offset -10 lines).
```

These SQLAlchemy package overrides were originaly added to fix
incompatibilities with Flask-Admin.

See commit 05ae01fcea6c7d270cc15374b0a806b09f548a9a

However with Flask-Admin >= v1.5.6, several SQLAlchemy compatibility patches were added:
* https://flask-admin.readthedocs.io/en/latest/changelog/

We can now safely remove these package overrides to make bukuserver work again.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build buku

@ofborg eval


Automate uboot fw_env update

This is associate with uboot fw_env update https://github.com/openbmc/openbmc/issues/1315
[] Action is stop at uboot
[] Update fw_env, setenv, etc..

I believe this is still needed. We dont have any test associate with it.
We can leverage serial console.


simplify the clusteroperator status logic

Simplify the logic for building CO status and make all conditions union conditions so we can set multiple *Available conditions
/assign @soltysh @sanchezl

/hold
holding for proof.  learned by my lesson today

LGTM (add comment and fix imports and self-tag after proving this works)

testing in https://github.com/openshift/cluster-kube-apiserver-operator/pull/271

comments addressed.  proof pul passed.

/retest


Map pin moves while panning

I have been working through the reference app to get an understanding of how Here Maps works. One thing I have noticed is that while panning, the map pins seem to move while the marker does not move at all. Is there any way to avoid this?
https://user-images.githubusercontent.com/7745380/197228546-f9d21fe7-b3bc-48b8-a656-d9fc0f5a31e1.mp4
SDK Version: 4.12.3

Hi,
a view pin is allways attached to a map but not part of the map. That's the reason why you see these delays in the movement while panning the map. A workaround would be to use inline data SVGs instead as we did for the POIs along the route. Please have a look into this code.

@stefan-troyke, thanks for the reply. To clarify, do you mean using SVGs and markers instead of using pins?

Yes, you can use a map marker and load a SVG data as string, see:

https://developer.here.com/documentation/flutter-sdk-navigate/api_reference/mapview/MapMarker/MapMarker.withAnchor.html
https://developer.here.com/documentation/flutter-sdk-navigate/api_reference/mapview/MapImage/MapImage.withImageDataImageFormatWidthAndHeight.html with ImageFormat.svg
https://github.com/heremaps/here-sdk-ref-app-flutter/blob/master/lib/routing/poi_svg_helper.dart


Website layout jumping when navigating between docs pages

🐛 Bug Report
The default CSS (I guess this is the reason) is making navigating between documentation sections pretty annoying, because the whole layout jumps around (example in "Actual behavior").
Have you read the Contributing Guidelines on issues?
Yes.
To Reproduce
Just roam around the sections in the official docusaurus docs page. This also happens after initial project bootstrap.
Expected behavior
I'd expect the default initial setup to be slick. For example, this does not happen in the Prettier docs.

Actual Behavior

Reproducible Demo

docusaurus docs
draft docs

For some reason I assumed that docusaurus docs are server-side rendered, but they're not and I guess that's the reason - the content is being loaded after initial page load - am I right?

@sarneeh - I actually don't see that behavior on https://docusaurus.io. May I ask what OS and browser you are using?
Also, no, this is not server-side. Everything is pre-built and served as static html.

@JoelMarcey Yeah I've already noticed that this is just static html - my bad! :)
I'm working on Ubuntu 18.04 + Chrome 72.0.3626.109.

I tested it on Firefox and this issue does not occur there. It might be something wrong with my Chrome on Linux :cry:

Do you have the latest Chrome version? I want to indeed make sure this is not a Docusaurus issue, but it does sound like it may be your browser specifically.

@JoelMarcey Yes, this is the latest version. I've also tried on incognito mode (without any plugins) and I have the same issue. What's interesting (or depressing :smile:) is that I didn't see this kind of behavior on any other site before :smile:

Do you see the problem on other Docusaurus sites? https://docusaurus.io/en/users
Prettier uses Docusaurus, I want to know if you see the problem in other places?

@JoelMarcey Yes, but I see this is completely non-deterministic. It sometimes happens, sometimes not. As you may already guess - it's this kind of a bug that I have no idea where could I look at to find the cause :cry:

It's the transition property on input#search_input_react that's causing that jump on Ubuntu Chrome.

From the screenshots, this is probably due to the expanding/collapsing feature after the page loads. Docusaurus 1 initially renders the page with collapsing of all the categories, only after the page loads will we find which page is currently active and expand the category containing that page. One potential fix is to move the expansion/collapsing into the React component so that when we prerender during build we get the final UI, without any need for expanding/collapsing on page load. Docusaurus 2 does this.

We probably won't ever address this due to how v1 pages are rendered. Please use v2 if this issue is bugging you!


Use overloads for Field and PrivateAttr functions

This typechecks the default and default_factory arguments, and removes the need for a custom mypy plugin hook.

Change Summary

Related issue number

Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Pending happy mypy, I'm good with this 👍

Update: disabled mypy tests bc they're being flaky. We will investigate before closing #10623


Move qier222.yesplaymusic 0.2.5 to qier222.YesPlayMusic 0.2.5

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/156289#issuecomment-2146097791

[Policy] Reset Labels


Unable to inject DLLs (SOLVED)

idk maybe im just dumb but when using this i open cs and i cannot inject a dll but then i close steam reopen it normally and im able to inject dlls normally

nevermind i had to run my injector as admin never had to do that before sorry xD


Add gnomad_qc to requirements file

Ruchit was running code in the RMC repo and found that he needed to import the gnomad_qc repo. The RMC repo does not import code from gnomad_qc, but it imports code from this repo, which relies on gnomad_qc:
Traceback (most recent call last):
  File "/tmp/624521a536a54578b9f93b99d1d4524f/calculate_mpc.py", line 17, in <module>
    from rmc.utils.mpc import (
  File "/tmp/624521a536a54578b9f93b99d1d4524f/pyscripts_8dkg66yu.zip/rmc/utils/__init__.py", line 1, in <module>
  File "/tmp/624521a536a54578b9f93b99d1d4524f/pyscripts_8dkg66yu.zip/rmc/utils/constraint.py", line 41, in <module>
  File "/tmp/624521a536a54578b9f93b99d1d4524f/pyscripts_8dkg66yu.zip/rmc/utils/generic.py", line 20, in <module>
  File "/opt/conda/default/lib/python3.10/site-packages/gnomad_constraint/utils/constraint.py", line 36, in <module>
    from gnomad_constraint.resources.resource_utils import (
  File "/opt/conda/default/lib/python3.10/site-packages/gnomad_constraint/resources/resource_utils.py", line 17, in <module>
    from gnomad_qc.v4.resources.release import release_coverage, release_sites
ModuleNotFoundError: No module named 'gnomad_qc'

It would be super helpful to add gnomad_qc to the requirements for this repo!

gnomad_qc and gnomad_methods have already been included at the top of the requirements file above the part that is automatically generated
https://github.com/broadinstitute/gnomad-constraint/blob/e8b42132bf2874e7af611af72aecf801afa7aaaa/requirements-dev.txt#L4


There are several children view in a group,It's will expansion too slow.

If there are several children item in a group, these will expansion too slow.How to fix it?(Only 8~12 children view, use Samsung Note2)

Sorry for the very late reply. I have not noticed the issue on my devices. Can you see the same issue when using the demo app running on Samsung Note 2?
Demo app:

https://play.google.com/store/apps/details?id=com.h6ah4i.android.example.advrecyclerview

+1 same issue for me..

@jyoungrok Could you provide an example project which can reproduce this issue?

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [android-advancedrecyclerview] There are several children view in a group,It's will expansion too slow. (#14)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.

@h6ah4i

@h3clikejava I have created a sample code which is using Glide library for image loading into child items. I think it is not so slow on my Nexus 5 with Android 6.0, how about on your device?
https://github.com/h6ah4i/android-advancedrecyclerview/tree/debug/expand_too_slow
<img src="https://cloud.githubusercontent.com/assets/2552365/10563556/b053795c-75c9-11e5-8313-30e73c8b988a.png" width=200" />


Receiving ERROR: yaml.scanner.ScannerError: while scanning for the next token found character '\t' that cannot start any token   in "./docker-compose.yml", line 17, column 1..

version: '3'
services:
db:
image: mongo:latest
ports:
- "27017:27017"
volumes:
- "db-data:/data/db"
db-setup:
build: db
depends_on:
- db
api:
image: hygieia-api
depends_on:

db

ui:
build: UI
image: hygieia-ui
depends_on:
- api
ports:
- "3000:80"
volumes:
db-data:
certs:

VSCode can't figure out how to format my file, and I keep finding \t being inserted. FFS so frustrating.


Update Composer dependencies (2021-11-11-00-04)

Visual regression test passed!
View the visual regression test report