updated Docker image conda environment.yml for osmnx=1.3.*

Updated Docker image conda environment.yml for osmnx=1.3.* (released Jan 2023) and sqlalchemy>=1.4,<2.0, with related code changes (mostly to address/avoid sqlalchemy deprecation warnings).
As per #179 (which this pull request addresses), I wasn't able to successfully migrate all sqlalchemy-related code for the newer version 1.4,  which appeared with the updated dependencies arising from updated OSMnx.  This version prints to console verbose warnings in colour about impending changes in 2.0.  The difficulties in migration were partly because pandas and geopandas don't yet support sqlalchemy 2.0.   As such, I ultimately set the environment variable suggested by sqlalchemy for suppressing the not-yet-relevent deprecation warnings, as I couldn't address all of them.
The pull request also deals with the dependabot alert for Pillow >=9.2.0 ,<9.3.0  (updates to Pillow 9.4.0).
I haven't pushed the updated Docker image to DockerHub yet; I will do that after code review.
Incidentally I updated the template to include the new ghent_v3 entry, which displays some more complicated/complete study region area data sourcing than we've used elsewhere.  It queries a layer in geopackage by attributes to identify Ghent's municipal boundary.  This is just done via config file (passing ogr2ogr arguments for "-where"), not via code.  I thought it useful to retain as a usage example.

I've done over-zealous tagging of reviewers, to compensate for not doing this on previous commits (sorry) --- trying to change ways!  Let's discuss protocol/preferred way of doing this in our next meeting perhaps :)

In the above I updated environment.yml to use Python 3.10.*  which I verified as working.  First I tried Python 3.11.* but this wouldn't resolve.
I did a whole load of commits testing out getting unittest to work as a local pre-commit; I couldn't really, so I removed that for now.  I can figure that out later (probably better to launch these within Docker anyway...).
@global-healthy-liveable-cities/software-spatial  I think this is ready to review now.   It incorporates the bug-fixes that were addressed in the main branch earlier today (including adding a test file), but also upgrades OSMnx to latest version, addresses a Pillow-related depend-a-bot alert, and updates Python.   Also added some more pre-commit hooks.


NameError: global name 'data' is not defined

In these two histogram functions, the argument is datum but the code inside refers to data:
https://github.com/scikit-hep/uproot/blob/8032dae00c89e643690dbf9dc22913e75331db39/uproot/hist.py#L123-L143
It should be made consistent to avoid undefined variable errors.

It's consistent now: datum is always one scalar value and data is always a collection of them (usually Numpy array).


vendor folder not published on npm

Hey, it seems that the vendor isn't published on npm, so it doesn't work, it just fails silently.
Also maybe you should return an error message when it fails.

Holy moly. Thanks! Fixed in version 0.1.3.


Update ES translation

Update Spanish translation for next release.

Coverage remained the same at 59.496% when pulling 7a5ae779da1f9acf1466f97449477ee00eac110a on Roboron3042:master into 641443237cba6315f3c6b4b7c4c84f95433df538 on newsboat:master.


Return timestamps in API as ISO8601

Right now, timestamps are returned in a format that is not easily parsable in JS, e.g. 2022-08-24 15:10:34.961, there's also no timezone information, though one could assume it's always UTC.
It would be nice if the API returned timestamps in the ISO8601 format (2022-08-24T15:10:34.961Z), this way its possible to parse the strings with native JS new Date(). Many other libraries that consume JSON also kind-of assume the timestamps are ISO8601.

That's correct. The date is stored as UTC string in the format "Y-m-d H:m:s.u".
We cannot change the API response format because this will be a major breaking change. You can create a tiny wrapper around the response if you want to adjust the format to your needs. If you are using the JavaScript SDK you can make use of the client.afterSend function hook - https://github.com/pocketbase/js-sdk#send-hooks


[BREAKING]: Change whitelist to allowlist & blacklist to denylist

I noticed during a PR review that Alex.js suggested the term whitelist and blacklist as potentially being insensitive. I am suggesting to change from whitelist to allowlist.
I am not wholly sure if this change is desirable. This is primarily a way to start a discussion on the topic.
The migration path would likely be that we support the whitelist naming convention for backwards compatibility for a while, potentially forever. However, the docs would update to use the phrasing allowlist or passlist or allow-list or pass-list, and denylist or deny-list.
Note that currently there is no usage of the term blacklist in the project, just adding the usage here for consistency.

I added #153 as an interim solution.


Support for jedi 0.17.0

Problem Description
I am running spyder 4.1.2 and the only version of jedi it supports is 0.15.2 but I have 0.16.0 installed on my system. Since spyder doesn't support the latest version of jedi I get the dependency error when I launch spyder. I guess the autocomplete feature is also not working because of it.
I want to know if I need to downgrade the version of jedi or is it possible to support the latest version of jedi in spyder 4.1.2.
 I changed the dependencies to not have spyder pinned to a single version of jedi and spyder ran without throwing any warnings.
my autocomplete is still not working for some reason. neither the tab nor the ctrl+space is working for autocompletition.

That's because PyLS does not fully work with the newer Jedi without the patches. You need to patch it yourself (Only use the patch up to https://github.com/palantir/python-language-server/pull/781/commits/afafa62b680a7f4762937b956bc2fee57126c56d if you really need to use Jedi 0.16 instead of 0.17) or wait until that PR is finally accepted and released. Afterwards, spyder likely also needs some fixes. I am already seeing deprecation warnings related to Jedi in my test runs with a patched PyLS.

I am running spyder 4.1.2 and the only version of jedi it supports is 0.15.2 but I have 0.16.0 installed on my system

Jedi 0.16.0 is broken for Pandas. We're going to aim at supporting Jedi 0.17.0 in our 4.1.4 version, to be released at the end May (most probably).

I guess the autocomplete feature is also not working because of it

That's not the reason. You need to have Jedi 0.15.2 and Parso 0.5.2 installed for things to work correctly.

I want to know if I need to downgrade the version of jedi

Yes, you need to, and also your Parso version, as I said above.

is it possible to support the latest version of jedi in spyder 4.1.2.

That's basically not possible, unless you're very knowledgeable about our dependencies and how they work among them. And even if you manage to sort out all issues with them (as @bnavigator was suggesting above), you could get dependency errors (not generated by Spyder but by other packages) at runtime.

@ritesh024 yes it is possible, you just won't get any help from @ccordoba12.

unless you're very knowledgeable about our dependencies and how they work among them

That's why I clearly said unless above. Please don't try to start an out-of-place discussion here with your comments.

Then stop stating wrong facts. He does not need to downgrade to things to work correctly.
BTW, next IPython will require Jedi >=0.16 https://github.com/ipython/ipython/pull/12207, so why not pin that too while you are at it.

He does not need to downgrade to things to work correctly.

He does unless @ritesh024 is an expert on how our entire code completion machinery works. I really don't understand why you keep pushing with this (as I said, it seems you'd want to start a discussion about it).

BTW, next IPython will require Jedi >=0.16 ipython/ipython#12207, so why not pin that too while you are at it.

Thanks for letting me about it! Sure will do in our next release.

Sure will do in our next release.

And completely unnecessary, if you just would accept the pending and reviewed PR in PyLS.

I have always used notepad++ or jupyter notebooks for my python related needs, this is my first time trying to use an IDE for python. I didn't know there would be so many dependencies an IDE has to obey for it to function normally. I'll just wait for the new version of Spyder. Thanks for the replies.

Thanks for understanding @ritesh024!


Add tflint

Description

Motivation and Context

[x] I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer (required)

https://github.com/alexellis/arkade/issues/1016
How Has This Been Tested?

If updating or adding a new CLI to arkade get, run:
❯ go build && ./hack/test-tool.sh tflint

+ ./arkade get tflint --arch arm64 --os darwin --quiet
+ file /Users/c.bruyland/.arkade/bin/tflint
/Users/c.bruyland/.arkade/bin/tflint: Mach-O 64-bit executable arm64
+ rm /Users/c.bruyland/.arkade/bin/tflint
+ echo

+ ./arkade get tflint --arch x86_64 --os darwin --quiet
+ file /Users/c.bruyland/.arkade/bin/tflint
/Users/c.bruyland/.arkade/bin/tflint: Mach-O 64-bit executable x86_64
+ rm /Users/c.bruyland/.arkade/bin/tflint
+ echo

+ ./arkade get tflint --arch x86_64 --os linux --quiet
+ file /Users/c.bruyland/.arkade/bin/tflint
/Users/c.bruyland/.arkade/bin/tflint: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=WWuwDB_27el8d0Owu5C5/V1NSxV_ARrmHxMYnw287/VcDSdvy_44maSnQ5R3Kz/hlgDa7Isc-tcMr0gHuK7, stripped
+ rm /Users/c.bruyland/.arkade/bin/tflint
+ echo

+ ./arkade get tflint --arch aarch64 --os linux --quiet
+ file /Users/c.bruyland/.arkade/bin/tflint
/Users/c.bruyland/.arkade/bin/tflint: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=I3AT8Q__zGf1ic63i1iD/1kusLN4EK5KqHHnMKSP2/URGpnL_YRVhEpnkP_0jG/WXPnEECfFyyc_7lrTfEE, stripped
+ rm /Users/c.bruyland/.arkade/bin/tflint
+ echo

+ ./arkade get tflint --arch x86_64 --os mingw --quiet
+ file /Users/c.bruyland/.arkade/bin/tflint.exe
/Users/c.bruyland/.arkade/bin/tflint.exe: PE32+ executable (console) x86-64, for MS Windows
+ rm /Users/c.bruyland/.arkade/bin/tflint.exe
+ echo

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Documentation

[x] I have updated the list of tools in README.md if (required) with ./arkade get --format markdown
[ ] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s

[x] I have tested this on arm, or have added code to prevent deployment

@Shikachuu Could you merge this, as I'm a new contributor I have no permission to do so.


If a DataSink sampling rate is low (<143) it might end up not pulling any data

From this MicroPython bug:

https://github.com/microbit-foundation/micropython-microbit-v2/issues/201

Trying to do an audio recording with a sampling rate of 142 or lower results in no data being pulled from the DataSource.
This is replicable with the default StreamRecording, however before being able to set a sampling rate of 142, we are first hit with issue https://github.com/lancaster-university/codal-microbit-v2/issues/427  (triggered with a sample rate lower than 320) which hides this problem.
Using a custom DataSink, like MicroPython, we can confirm that no data is pulled from upstream if the sampling rate is set to 142 or lower:

Source code with custom DataSink
#include "MicroBit.h"
#include "StreamRecording.h"

MicroBit uBit;

const int SAMPLE_RATE = 142;
const int BUFFER_LEN = SAMPLE_RATE * 5;

int cur_len = 1;
uint8_t buffer[BUFFER_LEN];

class MyStreamRecording : public DataSink {
    public:
    SplitterChannel *upStream;

    public:
    int *dest_pos_ptr;
    uint8_t *dest;
    size_t dest_max;
    bool request_stop;

    MyStreamRecording(SplitterChannel *source);
    virtual ~MyStreamRecording();

    virtual int pullRequest();

    bool isRecording();
    void recordAsync();
    void erase();
};

MyStreamRecording::MyStreamRecording(SplitterChannel *source) : upStream(source) { }

MyStreamRecording::~MyStreamRecording() { }

int MyStreamRecording::pullRequest() {
    uint8_t *pull_buf = this->dest + *this->dest_pos_ptr;
    size_t n = this->dest_max - *this->dest_pos_ptr;

    if (n > 0) {
        n = this->upStream->pullInto(pull_buf, n) - pull_buf;
    }

    if (n == 0 || this->request_stop) {
        this->upStream->disconnect();
        this->request_stop = false;
    } else {
        // Convert signed 8-bit to unsigned 8-bit data.
        for (size_t i = 0; i < n; ++i) {
            pull_buf[i] += 128;
        }
        *this->dest_pos_ptr += n;
    }

    return DEVICE_OK;
}

bool MyStreamRecording::isRecording() {
    return upStream->isConnected();
}

void MyStreamRecording::recordAsync() {
    upStream->connect(*this);
}

void MyStreamRecording::erase() {
    *dest_pos_ptr = 0;
    request_stop = false;
    // set buf to zero using memset
    memset(this->dest, 0, this->dest_max);
}

int main() {
    uBit.init();

    SplitterChannel *splitterChannel = uBit.audio.splitter->createChannel();
    splitterChannel->setFormat(DATASTREAM_FORMAT_8BIT_UNSIGNED);
    splitterChannel->requestSampleRate( SAMPLE_RATE );

    MyStreamRecording *recording = new MyStreamRecording(splitterChannel);
    recording->dest = buffer;
    recording->dest_pos_ptr = &cur_len;
    *recording->dest_pos_ptr = 0;
    recording->dest_max = BUFFER_LEN;
    recording->request_stop = false;

    MicroBitAudio::requestActivation();

    while (true) {
        if (uBit.buttonA.isPressed()) {
            recording->erase();
            recording->recordAsync();
            while (recording->isRecording()) {
                uBit.display.print("R");
                uBit.sleep(5);
            }
            uBit.display.clear();
        }
        uBit.sleep(200);
    }
}

Essentially it comes down to SplitterChannel::resample():

codal-core/source/streams/StreamSplitter.cpp#L56-L70
It gets the upstream sampling rate as 45454

From an ADC sampling period set to 22 microsec 1000000/22 = 45454, which is configured when the audio pipeline sets the sampling rate to to 44100 and that calculates the period as an int with 1000000/44100=22.67

The DataSource pull contains 256 samples
With the DataSink sampling rate set to 142, you end up with

byteDeficit = 45454-142 = 45312
packetsPerSec = 45454 / 256 = 177
dropPerPacket = 45312 / 177 = 256   <-- Basically drop the entire packet
samplesPerOut = 256 - 256 = 0  <-- Or in other words, keep zero samples

Also interesting to note that samplesPerOut is set to zero, but the division in StreamSplitter.cpp#L84 doesn't cause an exception 🤷♂

A simple fix would be to change the zero samplesPerOut to one, unless totalSamples is zero, which would make 177 the minimum rate.
Perhaps slower rates could calculate the skip between readings and remember an index from block to block, something like... if skip is 300 take samples from successive blocks 0, 44 (=300-256), 88, 132, 176, 220, miss one, 8, 52, etc.


intermittent failures in tests/kernel/common: test_timeout_order: (poll_events[ii].state not equal to K_POLL_STATE_SEM_AVAILABLE)

Describe the bug
starting test - test_timeout_order
thread 0 synced on timer 0

    Assertion failed at /home/buildslave/src/github.com/zephyrproject-rtos/zephyr/tests/kernel/common/src/timeout_order.c:95: test_timeout_order: (poll_events[ii].state not equal to K_POLL_STATE_SEM_AVAILABLE)

To Reproduce
Seen only intermittently. Keeps happening in CI runs. Not sure how this can be induced repeatedly.
Expected behavior
Test case passes without incident.
Impact
Unclear. Might be a test case implementation issue. Might be a QEMU problem. Might be a subtle bug in the kernel that needs fixing.

Looks like another issue in timer. Let me check...

Unfortunately I cannot reproduce this...

Oooh, good timing (because I'd already almost forgotten).  I stumbled on this one too in x86_64, then it went away when I fixed other bugs.  But this one I believe to be a bug in poll.
The relevant state being checked is that the poll event (the struct owned by the caller of k_poll() that returns information about what has happend) is only set in is_condition_met() in poll.c.  This gets called out of the loop at the top of k_poll() on entry to see what has already expired.
BUT, if k_poll() then goes to sleep and is woken up by the event being signaled, we do not travel through is_condition_met so the result state never gets set and k_poll() returns anyway.
That sounds fatal, but it's almost undetectable: poll is traditionally done in a loop: call it, see what changed and take appropriate action, and call it again.  So typical user code will just wake up, see that nothing has changed, do nothing, go back into poll and see the state variable the second time through.
The test, though, seems not to be calling poll in a loop, so it will be sensitive to timing issues depending on whether k_poll() gets through its initial check before or after the event is signaled.
I'm a little crushed for the next day or three, but if someone else has time to dig before I get to it, I'll put $20 down that this is the root cause.  Otherwise just assign it to me :)

@andyross I have some time today, I'll take a look

BUT, if k_poll() then goes to sleep and is woken up by the event being signaled, we do not travel through is_condition_met so the result state never gets set and k_poll() returns anyway.

The object-specific handle_poll_events seems to do this for us. Otherwise this test would never work, the k_poll() call in test_timeout_order() always blocks.
The problem AFAICT is priority setting; the test main thread wants to lower priority to let the child threads all run, but instead of setting to a priority lower than the child threads, it gets set to the SAME priority, which means the k_poll() call may complete when some of the child threads have done their thing, but not all of them.

Notice output:
===================================================================
starting test - test_timeout_order
thread 0 synced on timer 0

    Assertion failed at /home/buildslave/src/github.com/zephyrproject-rtos/zephyr/tests/kernel/common/src/timeout_order.c:95: test_timeout_order: (poll_events[ii].state not equal to K_POLL_STATE_SEM_AVAILABLE)

FAIL - test_timeout_order
===================================================================

Only thread 0 sychronized on the timer. We expect to see:
===================================================================
starting test - test_timeout_order
thread 0 synced on timer 0
thread 1 synced on timer 1
thread 2 synced on timer 2
PASS - test_timeout_order
===================================================================

This looks like another annoying QEMU icount thing; threads 1 and 2 just never got a chance to release their semaphores. Trying to see if there is some way I can make this more robust.

@gnuless I would sync with @andyross once you start looking at this.

We can close this one.  This test is very reliable on all platforms under the various workarounds detailed in #12553.  There's nothing to do here in particular.


Use regular unix socket to connect shim

Fixes #3032
Signed-off-by: Eric Lin<EMAIL_ADDRESS>

Thanks for working on this, but I think we should freeze v1 and prioritize v2 for this.

Thanks for working on this, but I think we should freeze v1 and prioritize v2 for this.

As long as it's compatible, I think there is no harm for fixing v1 : )

The socket file can't be found on the actual system.. Is it removed after establishing the connection? (where?)
:+1: for forking instead of Chdir
doesn't seem to apply to v2

* The socket file can't be found on the actual system.. Is it removed after establishing the connection? (where?)

No, It was my fault. I didn't do well with the socket file in last commit that golang closed listener along with unlinking the socket file. I just re-push the new commit, please check it out.

* 👍 for forking instead of Chdir

As https://github.com/containerd/containerd/blob/master/sys/mount_linux.go#L93.  Forking to implement socket(), bind(), listen() syscall is really tiresome.

* doesn't seem to apply to v2

May you provide the way to test it ? : )

Codecov Report

Merging #3046 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3046   +/-   ##
=======================================
  Coverage   43.46%   43.46%
=======================================
  Files         103      103
  Lines       11033    11033
=======================================
  Hits         4795     4795
  Misses       5503     5503
  Partials      735      735

Flag
Coverage Δ

#linux
47.48% <ø> (ø)
:arrow_up:

#windows
40.28% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #3046 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3046   +/-   ##
=======================================
  Coverage   43.46%   43.46%
=======================================
  Files         103      103
  Lines       11033    11033
=======================================
  Hits         4795     4795
  Misses       5503     5503
  Partials      735      735

Flag
Coverage Δ

#linux
47.48% <ø> (ø)
:arrow_up:

#windows
40.28% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

1. no shim v2 change here `runtime/v2/shim/util_unix.go`

2. update your commit message because there is still abstract socket

Fixed, thanks

@linxiulei I think we can also add test case for regression :p

LGTM


HSEARCH-2595 Upgrade to Hibernate ORM 5.2.8.Final

https://hibernate.atlassian.net/browse/HSEARCH-2595

Seems integration tests are failing, we should have a look...

retest this please

It failed because there's a WildFly instance running on CI which wasn't property terminated by some other job.
It works locally; you can ignore it.

Thanks; merged.


"The specified value is not a valid quoted string." being thrown from calendar client on PATCH.

What steps will reproduce the problem?
1. GET a calendar item from the API using the .Net client
2. Attempt to PATCH the item

What is the expected output? What do you see instead?
I expect the patch to go through, but before the request is even sent an
exception thrown. Exception detail follows below, and a capture of our GET is
attached.

What version of the product are you using? <IP_ADDRESS>0
What is your operating system? Windows 7
What is your IDE? Visual Studio 2013
What is the .NET framework version? 4.5

Please provide any additional information below.

The Exception Information,
Message: The specified value is not a valid quoted string.
Stack Trace:
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Google.Apis.Requests.ClientServiceRequest`1.<ExecuteAsync>d__0.MoveNext() in c:\code\google.com\google-api-dotnet-client\default\Tools\Google.Apis.Release\bin\Debug\output\default\Src\GoogleApis\Apis\Requests\ClientServiceRequest.cs:line 126

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 13 May 2014 at 6:21
Attachments:

[Google Calendar GET.saz](https://storage.googleapis.com/google-code-attachments/google-api-dotnet-client/issue-464/comment-0/Google Calendar GET.saz)

Reopening this, as I don't think swallowing the value is an appropriate course of action.
Looking at BigQuery and Storage as two examples using etags, BigQuery sends back an etag that does include quotes (escaped in the JSON), but Storage sends back an etag not in quotes.
It's not clear to me how an etag that includes quotes should be handled.
I would suggest that a better fix for this issue would be the one suggested at #issuecomment-93003612. Let's add quotes if and only if the value doesn't start/end with quotes.
We should probably keep the existing try/catch for backward compatibility in case there are other malformed values that would cause problems.
This does introduce a somewhat-breaking change, in that if clients are currently expecting etags to be applied but that's not actually happening, then they may suddenly see a load of conflicts they didn't see before. That's probably better than continuing to not report those real conflicts though.

Useful references:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-None-Match
An ETag value should always be quoted. But can have a W/ prefix (before the initial quote) to indicate a weak etag. And can be just a * (no quotes).
We'll need to heuristically add quotes given these cases. Which shouldn't be too difficult.


942160 bypass detection with trailing /

Description
The rule 942160 seems not to trigger if the injection is followed by a /. It seems that, since only REQUEST_BASENAME is considered from the path, there's nothing to test against. When adding REQUEST_FILENAME to the list of vars to test against, it works.
Is this the intended behavior? Wouldn't such a blind test also work if it's only part of the path?
How to reproduce the misbehavior (-> curl call)
Bypassed
# curl -H "x-format-output: txt-matched-rules" 'https://sandbox.coreruleset.org/id/365059-1)%20OR%20556=(SELECT%20556%20FROM%20PG_SLEEP(15))/' -I
HTTP/1.1 200 OK
Date: Wed, 24 Jul 2024 20:59:03 GMT
Content-Type: text/plain
Connection: keep-alive
X-Unique-ID: ZqFrF6U-6vZH3vTca4PLZwAAAIM
x-backend: apache-nightly
x-crs-last-commit: none

blocked
# curl -H "x-format-output: txt-matched-rules" 'https://sandbox.coreruleset.org/id/365059-1)%20OR%20556=(SELECT%20556%20FROM%20PG_SLEEP(15))--comment'
942160 PL1 Detects blind sqli tests using sleep() or benchmark()
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=5-0-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=5, XSS=0, RFI=0, LFI=0, RCE=0, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)

Your Environment

CRS version: 4.3.0
Paranoia level setting: PL1
ModSecurity version (e.g., 2.9.6): 2.9.7
Web Server and version or cloud provider / CDN (e.g., Apache httpd 2.4.54): HAProxy 3.0 with ModSecurity via SPOE
Operating System and version:

Confirmation
[x] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

Thanks for the report. I doubt this behaviour is intentional. Would you be willing to open a PR with a fix?

Yes, will do :+1:


VisualStudio 2015 x64 compilation fixes for 1.9.x

Description
There were a couple of compilation failures on VisualStudio 2015 (64-bit community edition tested) with the latest 1.9 code. This patch is to address those.
Tests
I ran the render-cornell test using testrender.exe after a successful build, comparing the generated .exr with previous versions of OSL on Windows (comparable results).
Checklist:

[x] I have read the contribution guidelines.
[x] I have previously submitted a Contributor License Agreement.
[N/A ] I have updated the documentation, if applicable.
[N/A] I have ensured that the change is tested somewhere in the testsuite (adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

LGTM. Merging.


What's the best way to compartmentalize redux-logger messages?

redux-logger will be very helpful for my project, but I'm finding that the output of messages is difficult to manage. My console window is polluted with action messages, causing me to miss legitimate warnings and errors. Filtering (in Chrome) doesn't seem to help, as there's no way to filter out the logging groups; even if I click the "Errors" button in the filter toolbar, the redux logging groups still appear.
I would love to keep all the log messages, but have them directed to another location that I can check on demand, that way my console remains useful. Is it possible to redirect redux-logger messages to another DevTools panel? Or to another entry in the <top frame> drop-down list?
My only idea at this point is to write a Chrome extension that exports a very thin console wrapper object, which would be passed to redux-logger. All the messages would be proxied to the console as usual, except now they'd be coming from a browser extension, which means they'd only be visible if you selected the extension from the <top frame> drop-down list. (I'm assuming that's how that works.)
I'd rather not embark on this if there's an easier way to do this filtering. Thoughts? Any ideas on a simple solution would be greatly appreciated. :smile:

In my project I using collapsed option, it's very useful as for me. Messages built in structured table.

Right, I'm using the collapsed option as well, but I still can't filter out
those groups from appearing in the console.
On Feb 21, 2016 2:15 PM, "Eugene Rodionov"<EMAIL_ADDRESS>wrote:

In my project I using collapsed option, it's very useful as for me.
Messages built in structured table.
[image: image]
https://cloud.githubusercontent.com/assets/775692/13205794/337f6a58-d901-11e5-9b30-8dcd86db0ef6.png
—
Reply to this email directly or view it on GitHub
https://github.com/fcomb/redux-logger/issues/133#issuecomment-186930538.

But how are you can miss errors and warnings? They have different colors than black logger. And you can use predicate option to filter unnecessary messages (blur and touch for every field in redux-form, for example). If anyone wants to make extension — feel free, I'll add method in core.

My project produces a lot of redux logging messages because the redux state changes as the mouse moves over the page. All those messages fill up the console and push the errors/warnings off the screen, so that's why I've been missing them.

Seems like predicate can resolve your problem.

No, it doesn't really solve the problem, because I want to keep all the messages for debugging later. I just don't want them in my main console window.

It doesn't seem like this problem has been solved in general. The best solution I've seen is to group everything into a single logging group, but that won't work here because the code can never call console.groupEnd() because actions will be emitted for as long as the page is open.
If I figure out a worthwhile solution at any point, I'll post it here.

@evgenyrodionov What's the best way to filter from redux-form?
I gave it:
predicate:(getState, action) => action.type !== @@redux-form/FOCUS || @@redux-form/BLUR || @@redux-form/FOCUS
Which was my best interpretation based on the recipe:
predicate: (getState, action) => action.type !== AUTH_REMOVE_TOKEN

@zach-is-my-name !action.type.includes('@@redux-form')

Perfect timing. Best wishes, thanks again.
On Thu, Jun 15, 2017 at 4:33 PM, Evgeny Rodionov<EMAIL_ADDRESS>wrote:

@zach-is-my-name https://github.com/zach-is-my-name
!action.type.includes('@@redux-form')
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/evgenyrodionov/redux-logger/issues/133#issuecomment-308858037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APUadAe1ub8pD_4EUyi5v7AbrQUoV8uGks5sEZUqgaJpZM4Hedja
.

Hi - I am able to make the individual sections be logged in debug like this:
middleware.push(createLogger({
      collapsed: false,
      level: {
        prevState: 'debug',
        action: 'debug',
        nextState: 'debug',
        error: 'error'
      }
    }))

Is there a way to print the main action SET_APP_STATE @ 11:57:00.155 message to the console as a debug as well?
Thanks

@jordanpapaleo hi! Don’t understand your question, can you explain your use case?

Thanks for the quick reply! I love the details available in the logging from redux-logger.  We have a extremely large app and the console can get a little crowded.  We feel the pain when we are trying to specifically log out and debug.  In chrome dev tools we can filter what is displayed in my console, super cool.

I would like to set where redux-logger reports to.  Right now it appears to be showing on the console.log view.  I would love to set a flag that will set it to only report under a console.debug as that only shows up when I have the console set to show verbose debugging.  I am able to get the prevState, action, and nextState to log in debug mode by this config:
createLogger({
      collapsed: false,
      logger: console,
      level: {
        prevState: 'debug',
        action: 'debug',
        nextState: 'debug',
        error: 'error'
      }
    })

Is there a way to set the entire message to be logged out as a console.debug allowing me to only show them when I have chrome devtools showing the console.debug messages (verbose mode)
Thank you for your time :)

Ill try to dig into the code this weekend if I get some free time and take a look as well

1.) I think the OP is pointing out that the actions cannot be filtered out by chrome dev tools when you type something in the filter box and it gets in the way of debugging things when even after filtering you still see a clogged console filled with many logs.
2.) Another similar issue is, in the filtered view, if you filter out a particular action name, you can see it but expanding it does nothing except the arrow changes to down arrow. One would want to filter out a particular action in the huge list of actions but even if Point 1 worked as expected, you wouldn't be able to see any data from the filtered action log.

This should be open, this issue is still there

This should be open, this issue is still there

exactly what @kaushikwavhal said.  It's really annoying that when I put anything into the filter input and I still see redux-logger logs. And I definitely am not putting any filter text that would match anything in the redux-logger logs
Also, why is it that they still show up when I hide all logging. It's very frustrating.


Addition of strings produces 0

Bug report
According to Appendix 2 to Lil documentation: Binary Primitives operator + when acting on two strings should concatenate them:

Note that using , on two strings will result in a list of two strings, whereas using + will result in a single string!

How to reproduce
Open the Listener and run query "a" + "b".
Expected outcome
Listener returns the string "ab".
Actual outcome
Listener returns the number 0.

Resolved by #17


fix: added default value for rule8Document.path

Ticket: https://pins-ds.atlassian.net/browse/ASB-1771

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


Out of memory error during training

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 / Google Colab
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary (Win10)
TensorFlow version (use command below): 2.0.0rc1
Python version: 3.6.8 (Colab) / 3.6.9 (Win10)
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: Cuda 10 CuDNN <IP_ADDRESS> (Win10)
GPU model and memory: Geforce 1080 Ti, 12 GB (Win10)

Describe the current behavior
I am getting an out of memory error during the training of a encoder-decoder model using the subclassing api of tensorflow 2.
Describe the expected behavior
Once the graph is built and the batch size is constant, the memory usage of the model should stay the same so that there is no out of memory error upcoming during the training process.
Code to reproduce the issue
I have created a minimum example out of my model in google colab:
https://colab.research.google.com/drive/1Xbzcj0ZlALhLhJhv-JaKSVUu3rfB3Urh
Other info / logs
The error occurs at about example index (current_index) 25000 of 80000, so there must be an issue that something is written on the gpu memory which leads to the following oom error:
<ipython-input-2-fe0e8431350e> in train_model(self, data, batch_size)
     27
     28             with tf.GradientTape() as tape:
---> 29                 batch_output = self.model([input_sequences_batch, output_sequences_batch])
     30                 loss = self.loss_fn(data[1, current_index:current_index + batch_size, :], batch_output)
     31

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/base_layer.py in __call__(self, inputs, *args, **kwargs)
    889           with base_layer_utils.autocast_context_manager(
    890               self._compute_dtype):
--> 891             outputs = self.call(cast_inputs, *args, **kwargs)
    892           self._handle_activity_regularization(inputs, outputs)
    893           self._set_mask_metadata(inputs, outputs, input_masks)

<ipython-input-2-fe0e8431350e> in call(self, inputs)
     72
     73         decoder_output = self.sequence_decoder(self.embeddings(output_sequence[:, :-1]), initial_state=[state_h, state_c])
---> 74         output = self.time_distributed_dense(decoder_output)
     75         return output

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/base_layer.py in __call__(self, inputs, *args, **kwargs)
    889           with base_layer_utils.autocast_context_manager(
    890               self._compute_dtype):
--> 891             outputs = self.call(cast_inputs, *args, **kwargs)
    892           self._handle_activity_regularization(inputs, outputs)
    893           self._set_mask_metadata(inputs, outputs, input_masks)

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/layers/wrappers.py in call(self, inputs, training, mask)
    252         inner_mask_shape = self._get_shape_tuple((-1,), mask, 2)
    253         kwargs['mask'] = K.reshape(mask, inner_mask_shape)
--> 254       y = self.layer(inputs, **kwargs)
    255       # Shape: (num_samples, timesteps, ...)
    256       output_shape = self.compute_output_shape(input_shape).as_list()

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/base_layer.py in __call__(self, inputs, *args, **kwargs)
    889           with base_layer_utils.autocast_context_manager(
    890               self._compute_dtype):
--> 891             outputs = self.call(cast_inputs, *args, **kwargs)
    892           self._handle_activity_regularization(inputs, outputs)
    893           self._set_mask_metadata(inputs, outputs, input_masks)

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/layers/core.py in call(self, inputs)
   1056         outputs = gen_math_ops.mat_mul(inputs, self.kernel)
   1057     if self.use_bias:
-> 1058       outputs = nn.bias_add(outputs, self.bias)
   1059     if self.activation is not None:
   1060       return self.activation(outputs)  # pylint: disable=not-callable

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py in bias_add(value, bias, data_format, name)
   2716       value = ops.convert_to_tensor(value, name="input")
   2717       bias = ops.convert_to_tensor(bias, dtype=value.dtype, name="bias")
-> 2718     return gen_nn_ops.bias_add(value, bias, data_format=data_format, name=name)
   2719
   2720

/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/gen_nn_ops.py in bias_add(value, bias, data_format, name)
    753       else:
    754         message = e.message
--> 755       _six.raise_from(_core._status_to_exception(e.code, message), None)
    756   # Add nodes to the TensorFlow graph.
    757   if data_format is None:

/usr/local/lib/python3.6/dist-packages/six.py in raise_from(value, from_value)

ResourceExhaustedError: OOM when allocating tensor with shape[3136,50000] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc [Op:BiasAdd] name: model/time_distributed/dense/BiasAdd/

I could reproduce the issue with Tensorflow 2.0.0.rc1.
Please take a look at colab gist. Thanks!

@tocab Looks like shape of tensor is very big and consuming more memory. Can you try to optimize some parameters so that tensor size and memory requirements works well with your GPU? Also, can you try 2.0.0rc2? Thanks!

I get the same error also with 2.0.0rc2. How can I optimize tensor size and memory requirements? With not using the keras api in tensorflow 1, the training never got an oom after it startet and the batch size stayed the same.
Another question: Is it possible to finalize the graph with the keras api? Then I could test if more parameters are added during the training that leads to the oom.

I tested it with the final release 2.0.0 and got the same error

Hi,
Any news about this problem, because I have same issue. With 4x 2080Ti I have problem with simple unet model with input size 320x480

This is expected, and stems from the fact that you're running eagerly.
In graph mode, there are a number of optimizations to reuse of aggressively free memory based on an analysis of the overall dataflow graph. A good example to illustrate this is buffer forwarding:
k = 100000  # Just some large number
x = tf.ones((k, k))
y = x + 1.
z = y ** 2

In graph mode, the runtime can observe that y is the only consumer of x, and z is the only consumer of y. So it just allocates one chunk of memory and does all of the operations in place because it can prove that that is safe. On the other hand, if you run that code eagerly then the Python handles for x, y, and z would be alive at the same time, and you could subsequently use any or all of them; the runtime has no way of knowing what you'll do next. So it has to keep 3x as much data in memory as the graph versions since it can't prove that in place mutations are safe. (And there are a number of similar optimizations. See this presentation for a more thorough summary.)
So, back to your example. I doubled the batch size just to force an OOM in the first step (Note that you need to pass BATCH_SIZE to model_trainer.train_model in your colab to see the effect), and if instead of:
            with tf.GradientTape() as tape:
                batch_output = self.model([input_sequences_batch, output_sequences_batch])
                loss = self.loss_fn(data[1, current_index:current_index + batch_size, :], batch_output)

            gradients = tape.gradient(loss, self.model.trainable_variables)
            self.optimizer.apply_gradients(zip(gradients, self.model.trainable_variables))

you create a tf.function outside of the loop:
        @tf.function
        def train_step(features, labels):
          with tf.GradientTape() as tape:
                batch_output = self.model([input_sequences_batch, output_sequences_batch])
                loss = self.loss_fn(data[1, current_index:current_index + batch_size, :], batch_output)

          gradients = tape.gradient(loss, self.model.trainable_variables)
          self.optimizer.apply_gradients(zip(gradients, self.model.trainable_variables))
          return loss

And then call it inside the training loop:
    loss = train_step([input_sequences_batch, output_sequences_batch],
                               data[1, current_index:current_index + batch_size, :])

The model no longer OOMs. (Because the tf.function can apply all of the same tricks that TF 1.x uses to conserve memory.)
So why doesn't the model OOM immediately?  So what happens is that after most loops python's gc is clearing out Tensors in time for the memory to ready for the next batch, but it's not guaranteed. So if gc is ever late, the last batch worth of Tensors are still waiting to be collected and the GPU OOMs.
Hope this helps.


Slicing after map_overlap with asymmetric overlap gives unexpected result.

I'm seeing unexpected results from slicing after a map_overlap with an asymmetric overlap. For example:  (dask  == 2.5.0)
import dask.array as da
import numpy as np
arange = da.from_array(np.arange(20), chunks=(10,))
after_overlap = a.map_overlap(lambda x:x, depth={0:(0,5)}, boundary="none", trim=True)
print(after_overlap.compute())

[ 0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19]

As expected.
We then try to slice:
print(after_overlap[1:].compute())

[ 1  2  3  4 10 11 12 13 14 15 16 17 18 19]

There is a missing block of numbers (the same size as the overlap) in the middle.
Slicing from the other end:
print(after_overlap[:-1].compute())

[ 0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19]

Seems to have no effect. If you use depth=5 everything works as expected.
I will start to look into this, but thought I would write up first incase anyone has an idea.
Thanks for dask, been loving using it!

I think I have found the cause.
In https://github.com/dask/dask/blob/master/dask/array/overlap.py#L160 there is the following:
            left = [bds[0] + left_depth]
            right = [bds[-1] + right_depth]

This code is calculating the size of chunks at the edges of the array, so we need to add the chunk size to the boundary size, BUT, the left edge chunk has a right size overlap, not a left size overlap, so swapping these would seem to be correct:
            left = [bds[0] + right_depth]
            right = [bds[-1] + left_depth]

I'm pretty sure this is correct, but it is possible I have misunderstood the intent.
I'll write up a PR for this.

I am seeing the same thing.  Thanks for the report and the fix!

Fixed by #5449


Get-AccessToken is not using the proxy

When you configure a proxy because your server has no direct access to the internet, there's an issue as the Get-AccessToken method from Configuration.ps1 at the root of the project is not using it.
Due to that the access token can't be generated and the following rest calls fail with error : {"error":"JWT is required"}
Can you check why the proxy is not being used on that part and ensure it's used everywhere when it's set ?

Hello @patrice-adp,
Thank you for adding this into the SDK! Due to spacing issues I created a PR https://github.com/sailpoint-oss/powershell-sdk/pull/36 off of your code to fix this issue.


Can select children of instanced scene while it doesn't have editable children

Godot version:
3.2.4.rc.custom_build / 3.2.4.rc1 (both exhibit the same behaviour)
System
Linux (PopOS - most recent, up to date including drivers), GLES3, Nvidia 1060 - laptop
Issue description:
This is a really weird bug. It only affects projects created with previous versions of Godot.
As of rc1 i believe, the 3d editor unreliably alters between selecting the instanced scene or its children.
No errors whatsoever. In the screenshot below you can see:

instanced scene which doesnt have editable children
first click on the scene selected one of its children
understandably the node is not highlighted in the scene tree as it's not there at all.

Steps to reproduce:
Open a project created in 3.2.3 or lower
Minimal reproduction project:
Sadly I am not in possession of a minimal reproduction project, I've only got bigger ones, which I don't mind sharing if it'd help and you don't mind downloading a bigger project.

Might be related to physics picking changes @RandomShaper?

@akien-mga, maybe. I'll check it.
@lentsius-bark, yes, please share the project. That'll help me a lot.

@RandomShaper here you go. I stripped the project of unnecessary parts but the problem persists on my end.
If you navigate to a scene called LeGame.tscn and try selecting the "DeliveryBox", or parts of the character on the sword it exhibits the aforementioned behaviour.
SwordSurfers-picking-test.zip
Thanks for looking into this!

Bisected down to 6dbc08668b990ebb6518d37501c6d777b9a5d127.
It made this code section not work as expected:
https://github.com/godotengine/godot/blob/db8c2410a4ee6213f5b78d3e8fb9783d9d4f0edf/editor/plugins/spatial_editor_plugin.cpp#L537
I've unassigned myself. I'd gladly try to fix it, but I don't think I'll have time.

That said, if no one willing and able to fix it pops up soon, I'll try to find a spot to do it myself to help unblocking the release.

CC @hilfazer @KoBeWi

That said, if no one willing and able to fix it pops up soon, I'll try to find a spot to do it myself to help unblocking the release.

I'll give it a try once i'm back from work.

@hilfazer i can test it on Linux.

Minimal Reproduction Project:
https://github.com/hilfazer/Projects/tree/spatialEditorEditableChildrenSelection/Godot/EngineIssues/SpatialEditorSelectingHiddenNodes
Projects created in 3.2.4 are affected as well.
The bug is caused by the new way of storing Editable Children information. The code found by RandomShaper will need to change, tomorrow i'll try to figure it out.

@hilfazer Looking forward to the possible fix! Let me know if you need testing on Linux.

@lentsius-bark i'd welcome any help! PR for 3.2 is ready.

@hilfazer super sorry, I pulled your branch and went to build godot, sadly I got ALSA related errors that I had never met before. Not sure how to fix them either, meaning it looks like I wont be able to test your fix! :(
[100%] /usr/include/alsa/rawmidi.h:82: error: variable 'snd_rawmidi_open' redeclared as function
   82 | int snd_rawmidi_open(snd_rawmidi_t **in_rmidi, snd_rawmidi_t **out_rmidi,
      |
drivers/alsa/asound-so_wrap.c:3042: note: previously declared here
 3042 | int (*snd_rawmidi_open)( snd_rawmidi_t**, snd_rawmidi_t**,const char*, int);
      |
/usr/include/alsa/rawmidi.h:86: error: variable 'snd_rawmidi_close' redeclared as function
   86 | int snd_rawmidi_close(snd_rawmidi_t *rmidi);
      |
drivers/alsa/asound-so_wrap.c:3044: note: previously declared here
 3044 | int (*snd_rawmidi_close)( snd_rawmidi_t*);
...

These errors should be fixed in the latest 3.2 branch, does it work if you rebase on upstream/3.2?
git remote add upstream https://github.com/godotengine/godot
git pull --rebase upstream 3.2

@akien-mga Thank you, having done that, I could successfully build the engine!
@hilfazer I can confirm that your fix does indeed fix the issue without any other regressions or newly introduced issues my testing found. All projects which previously showcased the behaviour worked fine under the latest build. Awesome work.
I can't comment on the code itself as that beyond my abilities but from a pure user perspective, this does indeed fix the issue.

Fixed by #46141.

There's still a case where a node that's not visible in Scene dock can be selected in the editor - when it's a child of a node from an instanced scene.
So it's not the same as this issue, since the node in question is isntanced on the edited scene, but it's similar. I'm not sure if it's a bug or not.
A picture that's worth 1000 words:

@hilfazer Do you have reproduction project for that? I can't reproduce it.

I forgot to mention "Editable Children" checkbox needs to be unchecked before "ChildOfEditable".
Anyway, there were also problems with saving the scene so i've opened a new issue: https://github.com/godotengine/godot/issues/46726
Reproduction project can be found there.


Kodeco Reskin Iteration 2

Lots of fixing in CardViews (style borders, background/foreground colors, list style, padding, etc)
PRO badges in Kodeco orange
Removed RW era illustrations
Removed all right arrows from buttons

Still pending: Typography (Relative Book) fixes and clearing negative space.

Thanks! Please see PR #685 for fixes.


⚠ Mitsubishi has degraded performance

In a36024a, Mitsubishi (https://mitsubishimotorsid-mobileapp.com/app/login) experienced degraded performance:

HTTP code: 200
Response time: 7378 ms

Resolved: Mitsubishi performance has improved in da74a9f after 2 minutes.


Requesting blunderbuss feature to read aliases.

Turn on the aliases feature in the blunderbuss munger.

This change is

What is the alias feature? What will it be used for?

@apelisse It reads aliases in OWNERS files. The original PR which added the functionality is https://github.com/kubernetes/contrib/pull/1536

ping @apelisse

Shame on me for not LGTM'ing before ...


ANGULAR: View names on tabs are cut-off

The bottom portion of view names like the 'p of epi, the g of alignment etc. are cut off, likely due to the name not being centered in the tab space

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Updated sizing of space for text in the tabs so that characters are not cut off. Change deployed to mossy.


Feature/jcr checksum combined

I've been working with @andrewmkhoury to build out JCR Checksum Compare (lionshare of the credit here goes to andrew).
We've made a Web UI that builds on top of his JCR checksum comparison APIs that allows JCR trees on multiple systems to be easily compared.
Configure the JCR Check Comparison Parameters

Get the Checksum Comparison

Click on an entry to get the JSON diff

Download the full JSON dump based on the Configuration tab settings

JSON Dump file

This may seem like a dumb Q: but is this not more appropriate for ACS Tools instead of Commons?

@bstopp that was my initial thought, but the ~99% use case for this is troubleshooting Production and Tools is "intended for dev and qa" and generally cautioned against being installed on Production.
If Tools ever lifts that restraint, then i agree this would be better suited in Tools.
I actually made an issue in the Tools repo wrt to this feature and had a similar convo there.

Going through this: have you run a quick code analysis on this? without looking at all of the classes side-by-side, there appears to be duplication, but maybe i'm just seeing things.

@davidjgonzalez can you take a look at why the build is failing for this PR? looks like a failing test.

@justinedelson yup - havent had the time, maybe this weekend


Bug 2072891: Update to v1.5.1

From 1.3.4 that we have in 4.10.
Apart from the usual Dockerfile / OWNERS changes I noticed we still <carry> oauth update from this PR.
Diff to upstream v1.5.1: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/compare/v1.5.1...jsafrane:rebase-v1.5.1
Notable new features:

Enables volume cloning.
Add support for NVMe persistent disks
Add parameters to VolumeSnapshotClass for disk image config.

Full changelogs:
1.4 https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/release-1.4/CHANGELOG/CHANGELOG-1.4.md
1.5 https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/release-1.5/CHANGELOG/CHANGELOG-1.5.md
For NVMe support I added nvme-cli.rpm and /usr/bin/xxd (vim-common!) to the Dockerfile.openshift + copied deploy/kubernetes/udev to the image.
cc @openshift/storage

/hold
to get QA approval before merge

There seems to be a regression:
Apr  7 12:25:38.700: INFO: At 2022-04-07 12:22:58 +0000 UTC - event for pod-0be85581-5cb9-49be-acbe-7ac720e0f765: {kubelet ci-op-qhtmr1gl-713ae-xfx8d-worker-c-xjr8h} FailedMapVolume: MapVolume.SetUpDevice failed for volume "pvc-8ae6b1b0-0d86-4e21-becb-ffdd215be6bf" : rpc error: code = Internal desc = Error when getting device path: rpc error: code = Internal desc = error verifying GCE PD ("pvc-8ae6b1b0-0d86-4e21-becb-ffdd215be6bf") is attached: could not find tool at "/lib/udev_containerized/google_nvme_id", unable to verify device paths

For NVMe support I added nvme-cli.rpm and /usr/bin/xxd (vim-common!) to the Dockerfile.openshift + copied deploy/kubernetes/udev to the image.

Tested clone part here:
File bug for failed test case:
https://bugzilla.redhat.com/show_bug.cgi?id=2073959
failed: (3m28s) 2022-04-11T08:55:34 "[sig-storage] STORAGE Author:wduan-High-47224-[CSI Driver] [CSI Clone] [Filesystem] provisioning volume with pvc data source larger than original volume [Suite:openshift/conformance/parallel]"

passed: (5m28s) 2022-04-11T08:57:33 "[sig-storage] STORAGE Author:wduan-Critical-46813-[CSI Driver][CSI Clone] Clone a pvc with Raw Block VolumeMode [Suite:openshift/conformance/parallel]"

passed: (3m10s) 2022-04-11T08:58:26 "[sig-storage] STORAGE Author:wduan-Critical-46358-[CSI Driver] [CSI Clone] Clone a pvc with filesystem VolumeMode [Suite:openshift/conformance/parallel]"

Hello @jsafrane , when I create pvc( with storageclass standard-csi) /pod, found that provisioned pv is mounted with iscsi. Is there any parameter to let us use nvme?

I haven't found anything in GCP docs and upstream says NVMe is used only in confidential VMs, which I can't create in my GCP account.
I guess we can't really test them and thus we should not mention them in our docs.

/lgtm

/hold cancel


AAudio (Android) playback

Hi,
This library is great.
Is there any ETA to get  AAudio (Android) playback?
Thank you

There's no ETA, but this feature is important, and I will definitely start working on it at some point.

Added AAudio playback.


fix: deserialize EthNotification from params field

Closes #92

Thank you, I've added a test and done some cleanup of the nested conditionals :) Will merge when tests pass


[Usage] SGLang Launch: AttributeError: 'str' object has no attribute 'eos_token_id'

Describe the issue
Issue:
router init state: Traceback (most recent call last):
File "/home/a/miniconda3/envs/py310/lib/python3.10/site-packages/sglang/srt/managers/router/manager.py", line 68, in start_router_process
model_client = ModelRpcClient(server_args, port_args)
File "/home/a/miniconda3/envs/py310/lib/python3.10/site-packages/sglang/srt/managers/router/model_rpc.py", line 619, in init
self.model_server.exposed_init_model(0, server_args, port_args)
File "/home/a/miniconda3/envs/py310/lib/python3.10/site-packages/sglang/srt/managers/router/model_rpc.py", line 137, in exposed_init_model
self.regex_fsm_cache = FSMCache(
File "/home/a/miniconda3/envs/py310/lib/python3.10/site-packages/sglang/srt/constrained/fsm_cache.py", line 8, in init
self.outlines_tokenizer = TransformerTokenizer(
File "/home/a/miniconda3/envs/py310/lib/python3.10/site-packages/outlines/models/transformers.py", line 63, in init
self.eos_token_id = self.tokenizer.eos_token_id
AttributeError: 'str' object has no attribute 'eos_token_id'
Command:
CUDA_VISIBLE_DEVICES=0 python3 -m sglang.launch_server --model-path liuhaotian/llava-v1.5-7b --tokenizer-path llava-hf/llava-1.5-7b-hf --port 30000

Log:
PASTE THE LOGS HERE.

Screenshots:
You may attach screenshots if it better explains the issue.

https://github.com/sgl-project/sglang/issues/292 This has been raised and a temporary solution addressed in sglang project.

fyi https://github.com/haotian-liu/LLaVA/pull/1302 works around the issue


Potential data leakage issue due to wrong code logic

Hi, there! RepoCoder is a very motivating work for repository-level code completion using RAG. However, I noticed a technical bug (if it is not, I am sorry about that and please ignore this), which is shown as follows:
In search_code.py, you implemented an method named _is_context_after_hole, which determines whether a code fragment overlaps with the query (or the ground truth code you need to complete). However, in the subsequent prompt building phase, you invoke _make_an_extended_block which shifts down a few lines (as ReACC done) to better match the context with the completion target. There is no additional judgement about the aforementioned overlapping issue, and hence it ends up with retrieving ground truth and inevitably rises the performance.
Could you please explain this issue? Many thanks.

Hi, there! RepoCoder is a very motivating work for repository-level code completion using RAG. However, I noticed a technical bug (if it is not, I am sorry about that and please ignore this), which is shown as follows:
In search_code.py, you implemented an method named _is_context_after_hole, which determines whether a code fragment overlaps with the query (or the ground truth code you need to complete). However, in the subsequent prompt building phase, you invoke _make_an_extended_block which shifts down a few lines (as ReACC done) to better match the context with the completion target. There is no additional judgement about the aforementioned overlapping issue, and hence it ends up with retrieving ground truth and inevitably rises the performance.
Could you please explain this issue? Many thanks.

same question！

Thank you for bringing this up! This is indeed a potential issue, although it does not impact the outcomes of RepoCoder's experiments with the current hyperparameter settings.
To clarify, the variable context_start_lineno, as referenced below, plays a key role here. https://github.com/microsoft/CodeT/blob/35f54d60b152cc31d134b788e702878ad613d9f7/RepoCoder/search_code.py#L44
This variable context_start_lineno defines the start line number of the unfinished code preceding the completion target (or "hole"). Our prompt construction follows where half of the maximum allowed tokens in prompt (denoted $N$) are reserved for retrieved snippets, while the other half is allocated to the preceding unfinished code. The variable context_start_lineno is the line number $y$ where this unfinished preceding code begins.
To illustrate: if the target line number is $x$, with a sliding size $S_s$, and maximum prompt token limit $N$, then $N/2$ tokens are allocated to the retrieved snippets and the other $N/2$ tokens to the preceding code from line $y$ to line $x$. When the preceding code contains fewer than $N/2$ tokens, context_start_lineno is set to 0.
In retrieval, we filter out any code snippets whose ending lines exceed context_start_lineno $y$. The specific issue you described arises only when a retrieved snippet ends exactly at $y$ and spans $y + S_s \ge x$, potentially causing an overlap with the target code. However, given the hyperparameters used (with $S_s = 10$ and $N \ge 2,048$), this scenario is avoided: for instance, 10 lines of Python code would need at least 1,024 tokens to fit within the prompt window, which is unlikely given the dataset.
For reference, I examined the RepoEval dataset:

In datasets/api_level_completion_1k_context_codegen.test.jsonl ($N/2=1k$), the preceding code covers min($y - x$) = 48 lines, max($y - x$) = 144 lines, and a mean of 82.8 lines. (counted for the prompts with $y>0$)
Similarly, in datasets/line_level_completion_1k_context_codegen.test.jsonl($N/2=1k$), the preceding code spans min($y - x$) = 42 lines, max($y - x$) = 155 lines, with a mean of 85.3 lines.  (counted for the prompts with $y>0$)

In our jsonl data file, prompt represents the preceding unfinished code, metadata.context_start_lineno is $y$, and metadata.line_no is $x$.
In summary, while this bug does not impact the results of our experiments with the current settings, it could affect outcomes if different hyperparameters were applied. We appreciate you bringing this to our attention and will address this bug in an upcoming update.

fixed in https://github.com/microsoft/CodeT/commit/d1b55f698803b71462a47af76f40a220060b01e1


[RV Garage Page]  - Import content and render the page

https://www.hubblehomes.com/rv-garage

Will not be adding as per the discussion with the customer https://adobe-dx-support.slack.com/archives/C06P5NMBH6W/p1721160135071959


created a new Nrp Api version (2017-10-01) folder and updated all resources api-versions

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

please make sure Ajinkya's changes make it

@dsgouda  : updated the readme.md. please take a look now

Closing as duplicate of
https://github.com/Azure/azure-rest-api-specs/pull/1798


DebuggerThread: remove unused sortString()

Before anyone actually tries to use this broken implementation (comparing the toLowerCase functions instead of their return values).

Thanks!


Updated _getMimeType

Updated _getMimeType to use deprecated mime_content_type() for php version < 5.3
References Issue #39

Below 5.3, you might have the PECL finfo extension installed, so maybe just check if class_exists('finfo') instead of this PHP version check.

Good idea. I'll get that updated.
Using submodules when I didn't create a fork is a bit tricky. Still trying to figure this out so if there are a bunch of strange commits that is why.


chore(query): use dbrp v2 service in flux influx.v1 dependencies

Updating the DBRP Mapping Service to the v2 version within the flux v1 packages dependencies.
The interface is nearly identical, apart from taking the v2 struct types.
Moving to v2 will allow me to use the new DBRP mapping service client. Meaning the DBRP metadata can be retrieved from a remote service instead of directly from the kv store.

Hey @fchikwekwe ! I just tagged flux team as I am touching some transpiler code. Would you mind throwing your eyes over this for me 🙏
We've moved from dbrp mapping service v1 to v2 and some future work I am doing will benefit from this :)

Hey @jsternberg I hope it is ok I tagged you on this. Github recommended it for the part of the code and Faith is out this week.


Remove deprecated ioutil

Small change to replace the deprecated ioutil package with their direct equivalents.

@aaronhurt trying to avoid the YOLO badge can I ask for your view on this one?
P.S. also included testing.TempDir() in tests to replace ioutil.

Thanks, this was a tedious one, but something that needed to be done!


Add "Violet" by Mrjajkes to the Automatic Zombie Evacuation

About the PR

Adds "Violet" by mrjajkes to the automatic emergency shuttle call for Zombies.
Currently does not work for an unknown and completely mysterious reason. It spams the console with an error:
[ERRO] runtime: Caught exception in "entsys"
System.ArgumentException: Path must be rooted
   at Robust.Shared.Audio.Systems.SharedAudioSystem.SetupAudio(String fileName, Nullable`1 audioParams, Boolean initialize, Nullable`1 length) in C:\Users\admin\Documents\Programming\CS\Goob-Station\RobustToolbox\Robust.Shared\Audio\Systems\SharedAudioSystem.cs:line 311
   at Content.Server.Chat.Systems.ChatSystem.DispatchStationAnnouncement(EntityUid source, String message, String sender, Boolean playDefaultSound, SoundSpecifier announcementSound, Nullable`1 colorOverride) in C:\Users\admin\Documents\Programming\CS\Goob-Station\Content.Server\Chat\Systems\ChatSystem.cs:line 401
   at Content.Server.GameTicking.Rules.ZombieRuleSystem.CheckRoundEnd(ZombieRuleComponent zombieRuleComponent) in C:\Users\admin\Documents\Programming\CS\Goob-Station\Content.Server\GameTicking\Rules\ZombieRuleSystem.cs:line 135
   at Content.Server.GameTicking.Rules.ZombieRuleSystem.ActiveTick(EntityUid uid, ZombieRuleComponent component, GameRuleComponent gameRule,
Single frameTime) in C:\Users\admin\Documents\Programming\CS\Goob-Station\Content.Server\GameTicking\Rules\ZombieRuleSystem.cs:line 159
   at Content.Server.GameTicking.Rules.GameRuleSystem`1.Update(Single frameTime) in C:\Users\admin\Documents\Programming\CS\Goob-Station\Content.Server\GameTicking\Rules\GameRuleSystem.cs:line 142
   at Robust.Shared.GameObjects.EntitySystemManager.TickUpdate(Single frameTime, Boolean noPredictions) in C:\Users\admin\Documents\Programming\CS\Goob-Station\RobustToolbox\Robust.Shared\GameObjects\EntitySystemManager.cs:line 306

And spams the game with the text announcement in-game, but doesn't play the sound / song at all. This even occurs when the ogg path is taken from a working announcement, the one right above it in fact. Without the song added to the announcement, the announcement works perfectly fine and doesn't spam.
This PR also removes a duplicate of redsun.ogg.
Why / Balance

Technical details

Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl: Piras314, mrjajkes

add: The song "Violet" by mrjajkes now plays when the emergency shuttle is automatically called during Zombies.

Summary by CodeRabbit

New Features

Introduced a new sound announcement for the zombie shuttle call, enhancing gameplay feedback.
Added attribution details for the new audio file violet.ogg, including licensing and source information.

Bug Fixes

Improved clarity in the zombification process by ensuring associated actions are properly managed.

Documentation

Added comments to key methods for better understanding and context regarding their functionality.

discussion on wizden discord here, could not solve the issue.

tests are unrelated so... seems to be working on linux at least?

Should retry this now that we've merged upstream

The announcementSound part of DispatchStationAnnouncement is just broken, I can't find any place where it works, so I am making a new PR using PlayGlobal instead. It was completely unrelated to this PR though, it's broken on master.


Autosaving too often

Currently all rulesets are saved just before the dashboard is unloaded. This means that a lot of write operations are done every time the tab is closed, so the quota will be reached far quicker. Therefore, if an actual change was to be made to a ruleset, it would likely not be saved because the quota was probably already met.
Simply changing from autosaving on unload to saving on ruleset modification would solve this, so I'll work on that at some point soon.

Fixed in b7fe8793fa2b111a84bbda62bde2feb1cd1021bf


Alternative to the cache: no-cache in fetchClient

Hi, 04034e24787cf454cad662f77b9901de9de9cf8c has introduced using the cache: "no-cache" option when making fetch requests. This however, is unsupported by Cloudflare's Workers and Pages, and unfortunately isn't silently ignored, but throws an error. Is it possible to have an option to disable that parameter, or some alternate solution bypassing it?
It currently causes this error: Error: The 'cache' field on 'RequestInitializerDict' is not implemented.
Which is gone by downgrading to 1.0.0-rc.3, which didn't have that commit in.
See https://github.com/cloudflare/workerd/issues/698#issuecomment-2053681304

Please... our logs have been silently failing due to this for several weeks

Yup same issue here

Have been waiting for Cloudflare to address this issue in https://github.com/cloudflare/workerd/issues/698#issuecomment-2053681304 but there haven't been any updates for a while.
The reason I added this cache parameter is to prevent frameworks like Next.js from caching the requests. Will have to think about a different solution


Parse $refs in JSON

One can construct JSON pointers using $refs, e.g.
{
  "definitions": {
    "address": {
      "type": "object",
      "properties": {
        "street_address": { "type": "string" },
        "city":           { "type": "string" },
        "state":          { "type": "string" }
      },
      "required": ["street_address", "city", "state"]
    }
  }
}
{ "$ref": "#/definitions/address" }

Right now the package doesn't resolve those $refs, and will actually probably need a separate library (maybe jsonref).

jsonschema has a resolver class which can be used to resolve refs relative to schema, i.e. something like { "$ref": "#/definitions/$Thingy/.." } would resolve to an included Thingy schema items

@jenner yesssss thanks for the tip!

Would you accept a pull request adding this functionality?

@benhamill definitely

@benhamill thanks in advance :)

Being worked on via #19

addressed in #40


Migrate SQLFederationOptimizerRule to OptimizerRule::rewrite

DataFusion 40 changed the OptimizerRule format, ref apache/datafusion#9954. We'll need to migrate over.

We did the migration in this PR #64


Add support for multiple projects, fix linting when cross-compiling with cmake (The clean way)

This is basically a resubmit of PR #117 with clean-up and refactor as proposed by @Arcanemagus
(Yep, I finally got down to fixing this!)

@hebaishi @Arcanemagus ping


Change $MYTH token to use GIF instead of PNG for logoURI

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

@keone Could I get this manually reviewed please? <3333333333

this re-adds a duplicate block instead of modifying the existing one; see https://github.com/solana-labs/token-list/pull/17060/files

@keone sorry about that! Should be fixed now

added in https://github.com/solana-labs/token-list/commit/4718b3c204c90c1c23b6774814c30c59bd55b198


Replace proprietary licenes with Apache 2.0 or other compatible license, if possible

$ git clone https://github.com/p4lang/p4-dpdk-target

# cd p4-dpdk-target

$ git log -n 1 | head -n 3
commit 754c69683164465fed03c33ab0592cd75b8875b9
Author: b3n-l<EMAIL_ADDRESS>Date:   Fri Jun 28 18:27:17 2024 +0000

$ find . \! -type d | xargs grep -i confidential | head -n 5
./include/tdi_rt/tdi_rt_attributes.hpp: *  INTEL CONFIDENTIAL
./include/tdi_rt/c_frontend/tdi_rt_attributes.h: *  INTEL CONFIDENTIAL
./include/tdi_rt/c_frontend/tdi_rt_init.h: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY
./include/tdi_rt/tdi_rt_init.hpp: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY
./src/tdi_rt/tdi_common/tdi_context_info.hpp: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY

$ find . \! -type d | xargs grep -i proprietary | head -n 5
./include/tdi_rt/c_frontend/tdi_rt_init.h: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY
./include/tdi_rt/c_frontend/tdi_rt_init.h: * technical concepts contained herein are proprietary to Barefoot Networks,
./include/tdi_rt/tdi_rt_init.hpp: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY
./include/tdi_rt/tdi_rt_init.hpp: * technical concepts contained herein are proprietary to Barefoot Networks,
./src/tdi_rt/tdi_common/tdi_context_info.hpp: * BAREFOOT NETWORKS CONFIDENTIAL & PROPRIETARY

For these files, and ideally all source files in this repository that are released under and Apache 2.0 license, please add a comment line near the beginning of the file with exactly this text in it (plus any characters required to make it a comment):
SPDX-License-Identifier: Apache-2.0

@riyazahm22 Pinging you since you made at least one of the commits that added files with "CONFIDENTIAL" and/or "PROPRIETARY" in it.
@swaroopsarma @weiqiand Pinging you since you made many other commits to this repository, and hopefully know the answer, or can find out, about re-licensing these source files.


Discord OAuth url not working

So I am using the example zenora with flask example, but when I run it and press the login with discord button, it pops up a discord window that says "Invalid OAuth2 redirect_uri". My discord oauth link looks like this: https://discord.com/oauth2/authorize?client_id=1136642816597037161&redirect_uri=http%3A//localhost%3A5000/oauth/callback&response_type=code&scope=identify. Is there something wrong with it? Thanks!

I just forgot to add the correct redirect in the developer settings


@lepture  still getting this error

@lepture  Hi there! I've tried the 1.0.0 version just now, and it seems the issue persists with Google Oauth2.
oauth = OAuth()
oauth.register(
    name='google',
    server_metadata_url='https://accounts.google.com/.well-known/openid-configuration',
    client_kwargs={
        'scope': 'openid email profile'
    },
    client_id=GOOGLE_OAUTH2_CLIENT_ID,
    client_secret=GOOGLE_OAUTH2_CLIENT_SECRET
)

@app.route('/oauth2-login')
async def oauth2_login(request: Request):
    # absolute url for callback
    # we will define it below
    redirect_uri = request.url_for('oauth2_auth')
    return await oauth.google.authorize_redirect(request, redirect_uri)

@app.route('/oauth2-auth')
async def oauth2_auth(request: Request):
    token = await oauth.google.authorize_access_token(request)
    user = token['userinfo']
    return user

My stacktrace :
Traceback (most recent call last):
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/uvicorn/protocols/http/httptools_impl.py", line 376, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 75, in __call__
    return await self.app(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/fastapi/applications.py", line 208, in __call__
    await super().__call__(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/applications.py", line 112, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/middleware/cors.py", line 78, in __call__
    await self.app(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/middleware/sessions.py", line 75, in __call__
    await self.app(scope, receive, send_wrapper)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/asgi_correlation_id/middleware.py", line 60, in __call__
    await self.app(scope, receive, handle_outgoing_request)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 580, in __call__
    await route.handle(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 241, in handle
    await self.app(scope, receive, send)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 52, in app
    response = await func(request)
  File "/home/sorasful/dev/my_api_async/my_api/__main__.py", line 168, in oauth2_auth
    token = await oauth.google.authorize_access_token(request)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/authlib/integrations/starlette_client/apps.py", line 74, in authorize_access_token
    params = self._format_state_params(state_data, params)
  File "/home/sorasful/.cache/pypoetry/virtualenvs/my-api-5UH-8tMH-py3.10/lib/python3.10/site-packages/authlib/integrations/base_client/sync_app.py", line 234, in _format_state_params
    raise MismatchingStateError()
authlib.integrations.base_client.errors.MismatchingStateError: mismatching_state: CSRF Warning! State not equal in request and response.

Originally posted by @sorasful in https://github.com/lepture/authlib/issues/376#issuecomment-1073074610

Please test with https://github.com/authlib/demo-oauth-client


[python-package] ImportError: cannot import name 'log_evaluation' from 'lightgbm'

Description

ImportError: cannot import name 'log_evaluation' from 'lightgbm' (C:\Users\MASSAWE\Anaconda3\lib\site-packages\lightgbm_init_.py)

Reproducible example
from lightgbm import early_stopping, log_evaluation

Environment info
LightGBM version = 4.1.0:
Command(s) you used to install LightGBM
pip install lightgbm

Additional Comments

Thanks for using LightGBM.
I was not able to reproduce this.
docker run --rm -it python:3.11 /bin/bash
pip install 'lightgbm==4.1.0'
python -c "from lightgbm import log_evaluation"
echo $?
# 0

I suspect that one of the following is happening:

you are using a local file called lightgbm.py and that's conflicting with the installed LightGBM library

solution: rename such files to anything other than lightgbm.py

somewhere in your code, you've imported something else as the name lightgbm, like import sklearn as lightgbm

solution: do not do that

mixing pip with conda has resulted in some unexpected behavior

I noticed that you said you ran pip install, but that Python is looking in an Anaconda3/ directory
solution::

  pip uninstall --yes lightgbm
  conda uninstall --yes lightgbm
  conda install -c conda-forge lightgbm

something else

solution: provide us with more information, like the output of pip freeze and conda env export

I've reformatted your post to make the difference between your own statements, code, and output from code clearer. If you're unsure how I did that, please review https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax

Thanks for your explanation.
On Mon, 13 Nov 2023, 20:03 James Lamb, @.***> wrote:

Thanks for using LightGBM.
I was not able to reproduce this.
docker run --rm -it python:3.11 /bin/bash
pip install 'lightgbm==4.1.0'
python -c "from lightgbm import log_evaluation"echo $?# 0
I suspect that one of the following is happening:

you are using a local file called lightgbm.py and that's conflicting
with the installed LightGBM library

solution: rename such files to anything other than lightgbm.py

somewhere in your code, you've imported something else as the name
lightgbm, like import sklearn as lightgbm

solution: do not do that

mixing pip with conda has resulted in some unexpected behavior

I noticed that you said you ran pip install, but that Python is
looking in an Anaconda3/ directory
solution::

pip uninstall --yes lightgbm
conda uninstall --yes lightgbm
conda install -c conda-forge lightgbm

something else
solution: provide us with more information, like the output of
pip freeze and conda env export

I've reformatted your post to make the difference between your own
statements, code, and output from code clearer. If you're unsure how I did
that, please review
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/LightGBM/issues/6187#issuecomment-1808593884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALETT3LEAYEFJ5PAWBIZHDLYEJHF7AVCNFSM6AAAAAA7H27TGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYGU4TGOBYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Glad to hear it!
On Thu, 14 Dec 2023, 07:03 github-actions[bot], @.***>
wrote:

Closed #6187 https://github.com/microsoft/LightGBM/issues/6187 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/LightGBM/issues/6187#event-11243139796, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALETT3PIBGQRGTBRAP4JJRLYJJ3BXAVCNFSM6AAAAAA7H27TGCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGI2DGMJTHE3TSNQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks a lot.
On Thu, 14 Dec 2023, 07:50 github-actions[bot], @.***>
wrote:

Reopened #6187 https://github.com/microsoft/LightGBM/issues/6187.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/LightGBM/issues/6187#event-11243351820, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALETT3MDDAV2U57JZV5DAW3YJKATDAVCNFSM6AAAAAA7H27TGCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGI2DGMZVGE4DEMA
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix AutoComplete component declare in index.d.ts file

This PR is to fix issue #196 .
In the index.d.ts file has a code snippet:
...
export class AutoComplete extends React.Component<__MaterialUI.AutoCompleteProps, any> {}

while __MaterialUI.AutoCompleteProps<DataItem> is a Generic type  which need a type parameter .
I found in material-ui AutoComplete component , DataItem should be string or node , so i fix it to:
export class AutoComplete extends React.Component<__MaterialUI.AutoCompleteProps<string | React.ReactNode>, any> {}

Codecov Report

Merging #198 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #198   +/-   ##
=======================================
  Coverage   76.31%   76.31%
=======================================
  Files          11       11
  Lines          38       38
=======================================
  Hits           29       29
  Misses          9        9

Continue to review full report at Codecov.

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

travis-ci failed because npm install failed in node-8 environment.
The command "eval npm install  " failed. Retrying, 2 of 3.

Probably relate to this: https://github.com/npm/npm/issues/19019#issuecomment-345523411. Latest npm not compatible with latest nodejs version. ;p So probably will be solved soon.

I saw that this was merged into master, which is awesome. Do you have an idea of when a new release will get cut? Thanks so much for this!


Consolidate allocated hosts from all model versions

Activate the superset of hosts allocated from all model versions
Use the version of each host allocated by the newest model version

@hmusum or @freva please review.

(But note that due to the TODO I added in ModelsBuilder.versionsToBuild we will not actually discover model versions to build from nodes not requested by the latest model, so the only consequence of this for now is that we'll always use the node spec produced by the latest model version.)


Matching code cleanup

This is a followup to #3810 which:

removes the bidirectional matching code and IsNotMatch (still todo!) as the substitution produced by this code will always be a matching one
re-factor he list and map matching code adding comments describing the match cases in more detail

List matching looks good. One could argue that we should return larger chunks of the unmatched lists when we fail (to make it easier to identify the failed match in the given configuration). The Map matching is rather hard to understand IMHO.

I was thinking the exact opposite. If we have a bug/missing case in map/list matching, this returns the exact point of failure, making it (hopefully) easier to diagnose

List matching looks good. One could argue that we should return larger chunks of the unmatched lists when we fail (to make it easier to identify the failed match in the given configuration). The Map matching is rather hard to understand IMHO.

I was thinking the exact opposite. If we have a bug/missing case in map/list matching, this returns the exact point of failure, making it (hopefully) easier to diagnose

OK, that's of course true: if we return a larger chunk the reader of the error message needs to follow the algorithm to understand where it hit the actual problem. I just noticed that in many cases the error will involve an empty list on one side... We can leave the error messages as they are now and see how this turns out in practice

Whatever we do, make sure the list and match matching algorithms are as isolated as possible. Eventually we'll want ot reimplement them with standard algorithms based on Diophantine solvers from literature.