Swift LLDB cannot launch application in 5.6-centos7 docker image

Swift LLDB fails to launch application in 5.6-centos7 docker image.
It prints
error: 'A' packet returned an error: 8

I found this while running inside a devcontainer in Visual Studio Code. The lldb extension in VSCode returns a slightly different error message
/root/.vscode-server/extensions/vadimcn.vscode-lldb-1.7.0/adapter/codelldb: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /root/.vscode-server/extensions/vadimcn.vscode-lldb-1.7.0/adapter/codelldb)
Debug adapter exit code=1, signal=null.

You're actually raising two different problems here.
The Swift LLDB failure is caused by missing capability in Docker environment. The guidance on https://hub.docker.com/_/swift?tab=tags is out of date, and you should refer to the README from this repo:

If you want to run the Swift REPL you will need to run the container with additional privileges:
# If running Docker on Linux:
docker run --security-opt seccomp=unconfined -it swift

# If running Docker on macOS:
docker run --privileged -it swift

The CodeLLDB failure is another one: that plugin is incompatible with CentOS 7 itself, because Glibc 2.16/2.17 shipped by CentOS 7 doesn't meet its requirement of Glibc 2.18.
There's no officially prebuilt Glibc 2.18 for CentOS 7, and I think shipping a custom Glibc causes more trouble than benefits.

Going to close this as a we don't support Centos7


Report signature mismatch when overridden method doesn't return reference.

See https://3v4l.org/k7UBK
class C16 {
    public function &j() {}
}

class C17 extends C16 {
    public function j() {}
}

This code produce warning on php7 and strict error on php5.6:
Warning: Declaration of C17::j() should be compatible with & C16::j() in /in/k7UBK on line 9

We should report it as method signature mismatch

Thanks again, @alex-vlasov!


Improved footer dark 4 and made it responsive

For Issue #791
Full Screen View

Tab View

Mobile View

Great work @RavindraP04


config file change doesn't trigger re-run in workspace

Describe the bug
In the reproduction, changing neither vitest.workspace.ts nor packages/*/vite.config.ts doesn't trigger rerun. I thought this is a part of forceRerunTriggers https://vitest.dev/config/#forcereruntriggers, but it doesn't see the case.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-tkdqry?file=packages%2Flib2%2Fvite.config.ts
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 1.3.1
    vite: latest => 5.1.4
    vitest: latest => 1.3.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The change of the config should restart the Vite server first, not just rerun the tests. Otherwise, the config won't be resolved correctly.


[yaml] Fix YAML join with upstream ReadFromPubSub

Fixes #33272
This should now allow Join to be used (and validate) against incoming Rows using BeamSchema and Row schema

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @robertwb


Fix "working?" of PostAgent

Bug fix as suggested in issue #2194.

Thanks you, can you fix the specs by setting @checker.last_received_at = Time.zone.now after this line?

I added a new test.
By the way, what does interpolated do? I looked at the specs of different agents and the usage seems to be inconsistent.

By the way, what does interpolated do? I looked at the specs of different agents and the usage seems to be inconsistent.

interpolated is taking the Agents options and evaluates all Liquid templates. In the working? method one could use credentials. In most receive methods the interpolate method gets the event contents as context. That allows the configuration to be dynamic based on the incoming events.

Thanks again, now I understand. Should I make any more changes?

Thanks again, now I understand. Should I make any more changes?

Yes, can you please change the "checks if events have been received within expected receive period" spec to the way it was before? I am pretty sure it will work and then makes it clear that your change does not affect this test.

Thanks you for working on this!

Unfortunately, there is another problem. Validation won't let me unset expected_receive_period_in_days. With the new logic of working?, would it be okay to make expected_receive_period_in_days optional?

Yeah, that makes sene.

See #2333


Seed words:UI changes.

This ui is for entering, display is a little different. Doesn't have two columns and no space at the bottom.

@cakesoft-swati  & @summikhan11  can you please explain UI changes here.

Verified this issue on dev app v2.0.80(485)


All2All precision always in fp32

This example shows how to use TutelMoE with Torch autocast amp.
Q: Is the All2All precision still meant to be done in FP32?
In general torch autocast amp keeps network master weights in FP32 and downcasts weights before a layers fwd pass.
So within an autocast context (as suggested here) the matmul here will be autocast to fp16
(Note torch.add is done in fp32; list of ops which are autocast; by default ops upcast to the input with highest precision; since batched_fc1_bias is fp32, the add will be done in fp32 and will output an fp32 answer)
So far everything is just standard torch.
My question is about these few lines of code. Since expert weights are in fp32, this will upcast input x to type fp32.
As a result the All2All communication is done using fp32 inputs.
Is this correct or am I missing some other cast?
(Note: in the cast at the end of this line, x has already been case to fp32).
It looks like the all2all is ALWAYS done using fp32 precision even if we are using an amp autocast context manager. Was this done deliberately or is this a bug? It seems like if the all2all is done using 16 bits we'd save 2x the BW.
Final note: as mentioned, if in the autocast context manager, although the all2all is done using fp32, autocast is still on and therefore the matmul's here are done using fp16.
Potential Bug: I'm not sure this does anything... That layer should already be in fp32 and when its run here autocast should still run it in fp16...
I THINK the right way to do this is something like this:
    def forward(self, x):
        if self.fp32_gate:
            x = x.float()
        with torch.autocast(device_type=x.device.type, enabled=not self.fp32_gate):
            out = self.wg(x)
            return out

In general it seems as though if the input is not explicitly cast here (ie we comment out those lines)
and the input to the MoE layer is in fp16, then the the all2all input is fp16 (and I'm assuming the all2all will be done in fp16); if the input to the MoE is in fp32 then the input to the all2all is in fp32 (and I'm assuming the all2all will be done in fp16)


fix bash code-block type and add others

Summary
README Code block syntax highlighting fixes
Description
README Code block syntax highlighting fixes

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Paginator (abstraction for backend plus UI)

https://stackoverflow.com/questions/50928891/how-to-implement-pagination-in-asp-net-core-razor-pages

https://www.mikesdotnetting.com/article/328/simple-paging-in-asp-net-core-razor-pages


mkdocsBuild fails when sourcesDir is ''

Hi, when I run
./gradlew mkdocsBuild

with the mkdocs configuration sourcesDir = '' (because I want to keep my docs in the /docs dir in the root of the repo.
I get the following error:
10:56:20.518 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
10:56:20.518 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
10:56:20.518 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
10:56:20.518 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Could not determine the dependencies of task ':mkdocsBuild'.
10:56:20.518 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > path may not be null or empty string. path=''

Here is my configuration in the repo used: https://github.com/commercetools/commercetools-sync-java/blob/create-doc-pages/gradle-scripts/mkdocs.gradle

Use sourcesDir = '.' (dot instead of empty string) and it will work.


Library status update 📢

Hi,
I'm the guy who coded angular-split and who didn't touch it since like 10 months.. 😳
Sorry about that for people who filled issues and made pull requests.
One of the reason I stopped working on was the total mess it was to manage an angular library with all packaging/bundling/import issues; the way I was coding it and testing pull requests was really bad too.
Adding to that a bit of laziness and many others things to do at home/work and you got a dead repo!
But i'm back on it, I've tested the new 'official' way to manage a library using angular-cli and that's totally awesome and painless compared to the way I was doing it before.
Currently, one of the main need is an upgrade to rxjs ^6.0.0 to make it works without rxjs-compat.
This is how I will move on first:

first I will check pull requests, merge some of them (like #119) if I'm ok with what it does and confident it doesn't break anything and refuse others.
set new project organisation using an angular cli configuration managing 2 projects: the library and the app demonstrating its use.
Upgrade dependencies to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Commit all of this to github
Publish an 1.0.0 version on npm

Next:

a lot of people ask for pixel sizes (#101), and there are 3 pull requests on it, the one from mrothauer (https://github.com/bertrandg/angular-split/pull/32) is really interesting but I need to test each case I see to be sure it doesn't break anything.
there is a mess with devicePixelRatio I need to resolve (#81 & #85) to make it works properly on desktop / mobiles / retina display.
check all issues..

I would like to set cypress tests to back it too (I've played with it lately at work and you can simulate drag and drop easily!).
So you will get a 1.0.0 really soon! 😉

That's a great news!
looking forward for the updated version

Hey @bertrandg, awesome to hear you're picking up work on this library again! 👍

Great news. Thanks for your efforts, it's a really useful lib!

Thanks for that. Will be included in our project when ready!

Check #131 for what's coming.

Sorry if this is not the place to ask, but is there a version that is supported with Angular 6.x.x?
I'm running into brick walls, so if you have any tips I'd appreciate them.
Upgrading to 7.x is not an option at this time.

FYI to others, I found this branched version someone did that I can use: https://www.pika.dev/packages/angular-split-ng6


Add --scalapy-version option

Allowing users to change the ScalaPy version when --python is passed.

Maybe we could add some simple test?
otherwise, LGTM

Maybe we could add some simple test?

Yeah. Initially I had integration tests in mind for that, but I was a bit reluctant to add ITs just for that. I just added some more unitary tests (along with an extra commit tweaking the ScalaPy organization).

Maybe we could add some simple test?

Yeah. Initially I had integration tests in mind for that, but I was a bit reluctant to add ITs just for that. I just went for some more unitary tests (along with an extra commit tweaking the ScalaPy organization).

Yeah, that works


[bug 1173763] Tweak error logging code

Still can't figure out why we're posting "https://" to GA. Trying this
out to see if it sheds light on the situation.
Quick r?

r+

Thank you! This is so weird.


TweetInvi causing application failure on test servers

We have an application that is running fine on a dev box but when installed on two test servers fails as soon as it encounters any code accessing the TweetInvi library (4.0.1).  The following line causes an exception:
ExceptionHandler.SwallowWebExceptions = false;
This is odd as ExceptionHandler is a static class.  We tried commenting out this line but then hit the same issue with this one (again a static class):
RateLimit.RateLimitTrackerMode = RateLimitTrackerMode.TrackOnly;
Can anyone explain what might be causing this issue?  Thanks in advance.

This seems to be some oddity with our continuous integration build server.  Builds fine on other machines.  Closing this issue.

@mpm01  Do you know what was the oddity with your continuous integration build server? I am having same issue.


Uses delayed notification, so we only restart td-agent once.

Isn't :delayed the default behaviour?

Really? I just read the doc and it seems so.
But why in my usages it's restarted multiple times :confused:
Here is partial log:
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] created file /etc/td-agent/conf.d/application_log.conf
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] updated file contents /etc/td-agent/conf.d/application_log.conf
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] owner changed to 0
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] group changed to 0
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] mode changed to 644
[2015-07-30T16:20:35+07:00] INFO: template[/etc/td-agent/conf.d/application_log.conf] sending restart action to service[td-agent] (delayed)
[2015-07-30T16:20:35+07:00] INFO: Processing service[td-agent] action restart (my_cookbook_common::none line 27)
[2015-07-30T16:20:39+07:00] INFO: service[td-agent] restarted
[2015-07-30T16:20:39+07:00] INFO: Processing td-agent_source[nginx_access_log] action create (my_cookbook_common::none line 35)
[2015-07-30T16:20:39+07:00] INFO: Processing service[td-agent] action nothing (my_cookbook_common::none line 27)
[2015-07-30T16:20:39+07:00] INFO: Processing template[/etc/td-agent/conf.d/nginx_access_log.conf] action create (my_cookbook_common::none line 31)
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] created file /etc/td-agent/conf.d/nginx_access_log.conf
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] updated file contents /etc/td-agent/conf.d/nginx_access_log.conf
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] owner changed to 0
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] group changed to 0
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] mode changed to 644
[2015-07-30T16:20:39+07:00] INFO: template[/etc/td-agent/conf.d/nginx_access_log.conf] sending restart action to service[td-agent] (delayed)
[2015-07-30T16:20:39+07:00] INFO: Processing service[td-agent] action restart (my_cookbook_common::none line 27)
[2015-07-30T16:21:11+07:00] INFO: service[td-agent] restarted

By default, notifications are :delayed, that is they are queued up as they are triggered, and then executed at the very end of a chef-client run. To run an action immediately, use :immediately:
https://docs.chef.io/resource_common.html#notifies-syntax

Explicitly specify notification method as :delayed won't help. Anyway there's something need to be fixed. Now I'm preparing another patch for the problem.


Failing spec for #3671

Did we ever make any progress on fixing this?

Not yet...
On Mon, Aug 17, 2015 at 9:59 PM, Samuel E. Giddins
<EMAIL_ADDRESS>wrote:

Did we ever make any progress on fixing this?
Reply to this email directly or view it on GitHub:
https://github.com/bundler/bundler/pull/3696#issuecomment-132071900

I made a failed attempt a while back... it's a bug whack-a-mole. I managed to fix this spec but broke several others :sob:

This PR will be auto-closed once 2-0-dev is merged to master


⚠ Bofrost.at has degraded performance

In aa82e7d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2497 ms

Resolved: Bofrost.at performance has improved in f2e6367 after 58 minutes.


Server is returning errors under "errors" key, not "error"

This is to fix #25

I'm pretty new to Python so if there is a better, more idiomatic way to do this that you'd like to see just let me know.

@nehresma this looks good to me, all good @hmarr ?

Looks great, other than minor comments.

I've ported the error message handling from the Ruby client.

Thanks - added a couple of minor style points but :+1: otherwise.

Style changes added.  Thanks for considering this for merging.

Cheers, this is looking great. Looks like there's a conflict between this and master, so could you rebase on top of current master? Will merge and release new version as soon as the conflict is resolved.

Sorry for the build failures.  I live in a mostly Python 2.7 world at the moment.  The tests are no longer dependent upon a particular ordering of dict keys, or on 2.7's map functionality.

Thanks! Merged and pushed to PyPI as v0.5.1.


Build with alabaster

DO NOT MERGE it's just a test (see #1138)

Can this be closed now?

Yes, thanks for the ping @Blendify!


Extend Hub retirement

@Jann-Skotdal : Thanks for your contribution! The author, @v-pawal, has been notified to review your proposed change.

#sign-off

@ktoliver : I work for the Translator team but off network. The date change referenced in this PR should go live as soon as possible. Are there any more approvals needed to make sure it goes live this afternoon?

@Jann-Skotdal The publishing schedule through 5/6 is altered to support Build starting this morning. Can you email me -<EMAIL_ADDRESS>- or tell me who your Microsoft manager is so I can get you the information about requesting approval to merge your content?

@tfosmark : Thanks for your contribution! The author, @v-pawal, has been notified to review your proposed change.


bugfix: selectForUpdate lockQuery exception in file mode

Ⅰ. Describe what this PR did
file mode rm selectForUpdate lockQuery exception
Ⅱ. Does this pull request fix one issue?

fixes #1586
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1646 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #1646      +/-   ##
=============================================
+ Coverage      47.23%   47.23%   +<.01%
  Complexity      1764     1764
=============================================
  Files            359      359
  Lines          12999    13000       +1
  Branches        1617     1617
=============================================
+ Hits            6140     6141       +1
  Misses          6193     6193
  Partials         666      666

Impacted Files
Coverage Δ
Complexity Δ

.../java/io/seata/server/lock/DefaultLockManager.java
53.33% <100%> (+1.06%)
12 <1> (ø)
:arrow_down:

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 186baf3...35e3c95. Read the comment docs.

LGTM

LGTM

你好大佬 我想深入的研究一下 可以给我发一份seata的时序图和详细的流程图吗。非常感谢<EMAIL_ADDRESS> 或者<EMAIL_ADDRESS>

You may find these images on the site seata.io.

You may find these images on the site seata.io.

看到了 谢谢


Create Lightning v0.30.0 RC branch

Before submitting
Please complete the following checklist when submitting a PR:

[ ] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[ ] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[ ] Ensure that the test suite passes, by running make test.

[ ] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[ ] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:

Forked as v0.30.0_release and released with tag v0.30.0. All changes to merge will master will be included in PR #446. Closing.


Add disabled-picker property to enable a full disabled state on component

The property disabled-picker has been added to enable a full component disabled state.
The property is of type Boolean and has a default of false, when ser to true the input field inside the component get disabled, and as a consecuense of that the mouse click stops working, so the component get into a read only mode, until the property gets back to true, that reenables the input field and the date can be changed angain.
Hope this simple functionality can be merged soon, since it has been comented by some others and is very usefull for read only situations.

Coverage remained the same at 99.324% when pulling b6ad35da602f4e8a666d16e341115a977c64f0fb on pflirae:master into 2ba83816fdf0580f2cea7350081d576e9134e00e on charliekassel:master.

Hey thanks for the PR!
I believe not having the disabled attribute at all is preferable to disabled=false
Not sure what the best way to achieve that is?

Since the disabled attribute is conditioned to a property of the vue component, if the propertie has false value, when the final html is rendered the attribute disabled is not present on the html generated. The disabled attribute only shows up on the final html when the property is true. Doing this ways the disabled condition gets a reactive behavior, that is what I expect from a Vue component.

This does indeed work as expected.
Can you please document this behaviour in the available props section in the readme? Then I'm happy to merge and release this.

Coverage increased (+0.009%) to 99.333% when pulling dde6b267b3abc0110d3a6abc2c9d934bdf15c8f7 on pflirae:master into 2ba83816fdf0580f2cea7350081d576e9134e00e on charliekassel:master.

Props section updated on readme.

Available from<EMAIL_ADDRESS>


Updating the README

Fixing verb tense and whitespace

LGTM

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


import and recipes order

The interaction between the import statement and the overriding of recipes doesn't seems intuitive to me, because imported recipes take the precedence over the ones in the importing file. I'd expect the other way around, in order to be able to override "defaults".
The following example  shows the problem. With the two files:
# justfile

set allow-duplicate-recipes

import 'lib.just'

_default: hello

# lib.just

_default:
    @just --list

hello:
    echo "hello world"

I get the following:
$ just --version
just 1.19.0
$ just
error: Justfile contains no default recipe.
$ just _default
Available recipes:
    hello

While I'd expect that the default recipe exists, and should be the _default defined in ./justfile. If I move set allow-duplicate-recipes in ./lib.just, or move the _default definition before the import, I get the same results.

Nice catch! I agree, recipes in parent modules should override recipes in imports. Fixed in #1790.


Missing the Set-SPOTenant -UsePersistentCookiesForExplorerView $True   setting

This document is missing the additional required setting Set-SPOTenant -UsePersistentCookiesForExplorerView $True thats needed at the SPO tenant level in order for File Explorer view to work in Edge

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

ID: 2c3f9bb0-43af-b544-3fd7-71eed410cbec
Version Independent ID: 250786b4-90f1-0eab-c15d-2f0182d69e5e
Content: View SharePoint files with File Explorer in Microsoft Edge - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/sharepoint-view-in-edge.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hello @Jvasil
Please see this note

This setting is not used anymore with Internet Explorer (IE) retired and the parameter would be removed soon. Users need to select "Yes" when prompted for "Stay signed in?" at the time of sign-in for "View in File Explorer" to work with Microsoft Edge.

here https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps

@scanum


Unexpected calculation behavior

I have a very odd case, the Kapacitor if clause comparison is failing at a very specific spot
System OSX 10.11.6
Homebrew install
Kapacitor v1.2.0 (git:  5408057e5a3493d3b5bd38d5d535ea45b587f8ff)
Connected to http://localhost:8086 version 1.2.2
InfluxDB shell version: v1.2.2
Input for the task
influx -database 'example' -execute 'select time, bay_utilization from bay_utilization' -format 'column' -precision 'rfc3339'

name: bay_utilization
time                 bay_utilization

2017-03-31T12:05:00Z 30
2017-03-31T12:06:00Z 30
2017-03-31T12:07:00Z 30
2017-03-31T12:08:00Z 30
2017-03-31T12:09:00Z 30
2017-03-31T12:10:00Z 30
2017-03-31T12:11:00Z 30
2017-03-31T12:12:00Z 30
2017-03-31T12:13:00Z 30
2017-03-31T12:14:00Z 30
2017-03-31T12:15:00Z 30
2017-03-31T12:16:00Z 30
2017-03-31T12:17:00Z 30
2017-03-31T12:18:00Z 30
2017-03-31T12:19:00Z 30
2017-03-31T12:20:00Z 90
2017-03-31T12:21:00Z 90
2017-03-31T12:22:00Z 90
2017-03-31T12:23:00Z 90
2017-03-31T12:24:00Z 90
2017-03-31T12:25:00Z 90
2017-03-31T12:26:00Z 90
2017-03-31T12:27:00Z 90
2017-03-31T12:28:00Z 90
2017-03-31T12:29:00Z 90
2017-03-31T12:30:00Z 90
2017-03-31T12:31:00Z 90
2017-03-31T12:32:00Z 90
2017-03-31T12:33:00Z 90
2017-03-31T12:34:00Z 90

Task Definition:
// Get batch data
var views = batch
    |query('SELECT mean(bay_utilization) FROM "example"."autogen".bay_utilization')
        .period(15m)
        .every(15m)
        .groupBy(time(1m), *)
        .fill(0)

views
//  |log()
//     .prefix('Debugging TICK')
    |eval(lambda: if ("mean">40, 1, 0))
    .as('value')
    |influxDBOut()
    .database('example')
    .measurement('Bay')

execution:
## clear output table
influx -database 'example' -execute 'delete from Bay'
## define task, refresh task definition
kapacitor define bay_state \
    -type batch \
    -tick BayState.tick \
    -dbrp example.autogen
## generate recording
rid=$(kapacitor record batch -task bay_state -start 2017-03-30T12:03:25.472999936Z -stop 2017-04-01T12:03:25.472999936Z)
## test task definition with recoding
kapacitor replay -task bay_state -recording $rid -rec-time
## remove recording after done
kapacitor delete recordings $rid
## verify output
influx -database 'example' -execute 'select * from Bay' -format 'csv' -precision 'rfc3339'

Output

ef6979b0-b455-40a4-872d-c44084eb5131
name,time,bay_number,value,work_zone

Bay,2017-03-31T12:10:00Z,6,0,NW
Bay,2017-03-31T12:11:00Z,6,0,NW
Bay,2017-03-31T12:12:00Z,6,0,NW
Bay,2017-03-31T12:13:00Z,6,0,NW
Bay,2017-03-31T12:14:00Z,6,0,NW
Bay,2017-03-31T12:15:00Z,6,0,NW
Bay,2017-03-31T12:16:00Z,6,0,NW
Bay,2017-03-31T12:17:00Z,6,0,NW
Bay,2017-03-31T12:18:00Z,6,0,NW
Bay,2017-03-31T12:19:00Z,6,0,NW
Bay,2017-03-31T12:20:00Z,6,1,NW
Bay,2017-03-31T12:21:00Z,6,1,NW
Bay,2017-03-31T12:22:00Z,6,1,NW
Bay,2017-03-31T12:23:00Z,6,1,NW
Bay,2017-03-31T12:24:00Z,6,1,NW
Bay,2017-03-31T12:25:00Z,6,1,NW
Bay,2017-03-31T12:26:00Z,6,1,NW
Bay,2017-03-31T12:27:00Z,6,1,NW
Bay,2017-03-31T12:28:00Z,6,1,NW
Bay,2017-03-31T12:29:00Z,6,1,NW
Bay,2017-03-31T12:30:00Z,6,1,NW
Bay,2017-03-31T12:31:00Z,6,1,NW
Bay,2017-03-31T12:32:00Z,6,1,NW
Bay,2017-03-31T12:33:00Z,6,0,NW
Bay,2017-03-31T12:34:00Z,6,1,NW
Bay,2017-03-31T12:35:00Z,6,0,NW
Bay,2017-03-31T12:36:00Z,6,0,NW
Bay,2017-03-31T12:37:00Z,6,0,NW
Bay,2017-03-31T12:38:00Z,6,0,NW

The issue is 2017-03-31T12:33:00Z for the output will always be 0. I have tried to adjust the threshold.
Trying to debug Kapacitor task input:
influx -database 'example' -execute "select mean(bay_utilization) from bay_utilization where time>'2017-03-31T12:03:25.472999936Z' and time<'2017-03-31T12:50:25.472999936Z' group by time(1m)" -format 'csv' -precision 'rfc3339'

name,time,mean

bay_utilization,2017-03-31T12:03:00Z,
bay_utilization,2017-03-31T12:04:00Z,
bay_utilization,2017-03-31T12:05:00Z,30
bay_utilization,2017-03-31T12:06:00Z,30
bay_utilization,2017-03-31T12:07:00Z,30
bay_utilization,2017-03-31T12:08:00Z,30
bay_utilization,2017-03-31T12:09:00Z,30
bay_utilization,2017-03-31T12:10:00Z,30
bay_utilization,2017-03-31T12:11:00Z,30
bay_utilization,2017-03-31T12:12:00Z,30
bay_utilization,2017-03-31T12:13:00Z,30
bay_utilization,2017-03-31T12:14:00Z,30
bay_utilization,2017-03-31T12:15:00Z,30
bay_utilization,2017-03-31T12:16:00Z,30
bay_utilization,2017-03-31T12:17:00Z,30
bay_utilization,2017-03-31T12:18:00Z,30
bay_utilization,2017-03-31T12:19:00Z,30
bay_utilization,2017-03-31T12:20:00Z,90
bay_utilization,2017-03-31T12:21:00Z,90
bay_utilization,2017-03-31T12:22:00Z,90
bay_utilization,2017-03-31T12:23:00Z,90
bay_utilization,2017-03-31T12:24:00Z,90
bay_utilization,2017-03-31T12:25:00Z,90
bay_utilization,2017-03-31T12:26:00Z,90
bay_utilization,2017-03-31T12:27:00Z,90
bay_utilization,2017-03-31T12:28:00Z,90
bay_utilization,2017-03-31T12:29:00Z,90
bay_utilization,2017-03-31T12:30:00Z,90
bay_utilization,2017-03-31T12:31:00Z,90
bay_utilization,2017-03-31T12:32:00Z,90
bay_utilization,2017-03-31T12:33:00Z,90
bay_utilization,2017-03-31T12:34:00Z,90
bay_utilization,2017-03-31T12:35:00Z,
bay_utilization,2017-03-31T12:36:00Z,
bay_utilization,2017-03-31T12:37:00Z,
bay_utilization,2017-03-31T12:38:00Z,
bay_utilization,2017-03-31T12:39:00Z,
bay_utilization,2017-03-31T12:40:00Z,
bay_utilization,2017-03-31T12:41:00Z,

After further debugging with Kapacitor logging, 2017-03-31T12:33 is the end of first batch, and the beginning of the second batch. 2017-03-31T12:33 in the batch 1 has mean of 90, in the batch 2 has mean of 0. It seems Kapacitor batch slicing is using (start-time, end-time]. So endtime is included in the previous batch, not in the next batch, and all of my events are stamped at the exact 0 second.

fill(0) will result in above behavior
fill('previous') will handle is properly
is there any way to fill a fixed value properly?

Does adding a .align() to the batch query fix the issue as well?

adding .align() resolved the problem. may i know the reason behind this?


Drop docker build/push/pull steps

Currently we push all builds to DockerHub, and tag all deployed builds. This takes a fair amount of time, and hasn’t proved to be that useful.

@slorek so I realised after pushing this commit that currently our tests pull ALL the docker images from docker-compose.yml from dockerhub in order to run the tests. 3e4f23a613fb1db44efebe5f39b5acfbac8b1f31 switches this to build them instead, which should work, but is way slower – because DockerHub is acting as a sort-of cache for the keycloak and antivirus docker images which rarely change.
We could switch the tests to use a shared long-running keycloak service, in the short term? Antivirus could be disabled for tests, as I don’t think it’s really needed?

17 minutes to build all the docker images from scratch... at least the review app was deployed in parallel though.

👍 We're working on running a Keycloak instance for tests separately.


option to turn off animation

What feature or improvement do you think would benefit Files?
There should be an option to disable animation in the application
as you can see when you open the application it takes some time to load because of the animation | preview.
my windows animation is turned off completely | preview.
Requirements

we just need an option for turning out animation completely in the app

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19044.2130
Windows Version
Edition	Windows 10 Pro Version	21H2 Installed on	10/9/2022 OS build	19044.2130 Experience	Windows Feature Experience Pack 120.2212.4180.0
Comments
No response

Animations can be turned off from the settings app in Windows.

https://imgur.com/a/5eXhA1l
mine is tuned off but the application still shows the animation!


Anvil freezes in sub-process

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (0c61e40 2022-11-08T16:46:49.405733Z)
What command(s) is the bug in?
anvil
Operating System
macOS (Apple Silicon)
Describe the bug
When running Anvil in a sub process (for example spawned by a Go process), calling evm_mine makes Anvil freeze for 5 to 9 seconds. I'm trying to mine a block with about 20 transactions.
A similar issue was reported here: https://github.com/foundry-rs/foundry/issues/2652

hmm interesting.
you're calling evm_mine as rpc call from the program that spawned the anvil process?

I'll try and get an example, but basically I'm grabbing 20 signed transactions from 20 different signers, stacking them onto a forked chain (forked server is 200ms away) and mining a block.

@mattsse here is a single go script to reproduce the issue (it mines the current block).
package main

import (
	"context"
	"fmt"
	"os/exec"
	"strconv"
	"time"

	"github.com/ethereum/go-ethereum/ethclient"
	"github.com/ethereum/go-ethereum/rpc"
	log "github.com/sirupsen/logrus"
)

// put your fork url here
const FORK_URL = "http://xxxxx"

func main() {
	// Create an IPC based RPC connection to a remote node
	conn, err := ethclient.Dial(FORK_URL)
	if err != nil {
		log.Fatalf("Failed to connect to the Ethereum client: %v", err)
	}

	// get the latest block
	block, err := conn.BlockByNumber(context.TODO(), nil)

	if err != nil {
		log.Fatalf("Failed to get latest block: %v", err)
	}

	port := 21000

	forkBlockNumber := block.Number().Uint64() - 1

	// fork anvil at the previous block
	args := []string{
		"-a", "0", "--no-mining", "--fork-block-number", strconv.Itoa(int(forkBlockNumber - 1)), "-p", strconv.Itoa(port), "--chain-id", "137", "-f", FORK_URL,
	}

	ganacheCmd := exec.Command("anvil", args[:]...)

	log.WithField("command", ganacheCmd.String()).Info("starting ganache")

	// kill ganache when done
	defer func() {
		log.WithFields(log.Fields{
			"pid": ganacheCmd.Process.Pid,
		}).Info("killing ganache")

		err := ganacheCmd.Process.Kill()

		if err != nil {
			log.WithError(err).Error("failed to kill ganache")
		}
	}()

	err = ganacheCmd.Start()

	log.WithFields(log.Fields{
		"pid":  ganacheCmd.Process.Pid,
		"fork": FORK_URL,
	}).Debug("Started ganache")

	// wait a bit
	time.Sleep(1 * time.Second)

	// connect to anvil
	rpc, _ := rpc.Dial(fmt.Sprintf("http://localhost:%d", port))
	anvil := ethclient.NewClient(rpc)

	startTxSend := time.Now()

	// pass the current block's transaction to anvil
	for _, tx := range block.Transactions() {
		err := anvil.SendTransaction(context.Background(), tx)

		if err != nil {
			log.WithError(err).Error("failed to send transaction")
		}
	}

	log.WithFields(log.Fields{
		"in":  time.Since(startTxSend),
		"txs": len(block.Transactions()),
	}).Info("Sent transactions to anvil")

	startTime := time.Now()

	// mine the next block
	err = rpc.Call(nil, "evm_mine", nil)

	log.WithFields(log.Fields{
		"in":  time.Since(startTime),
		"err": err,
	}).Info("anvil block mined")
}

Here is the output is:
INFO[0000] starting ganache                              command="/anvil -a 0 --no-mining --fork-block-number 35416266 -p 21000 --chain-id 137 -f http://FORK_URL"
INFO[0001] Sent transactions to anvil                    in=809.475708ms txs=59
INFO[0016] anvil block mined                             err="<nil>" in=14.887776333s

It's also quite slow to send all txs to the anvil instance, considering it's on the same machine. In this case mining the block took 14s+

can confirm that the first run takes ~14s
that's because we have to fetch the necessary state from the fork endpoint. However,
consecutive runs against the same block are much faster because the state is cached.
So the freeze is actually just the amount of time it takes to fetch all the touched slots.
If you have a fork API key with a higher tier then you can set a custom CUPS value, see
anvil --help for --compute-units-per-second which we use to budget requests

If is possible to make --compute-units-per-second unlimited? I run my own node

is the fork url localhost?

I put the script on the node, and cranked up the cpu limit, now blocks mine in < 100ms. Thanks!

A non-local node that is not operated by a provider is probably more of an unconventional niche setup overall.
However, this should be better supported.
There should be a flag to opt out of ratelimit prevention I think, will add this


WordPress Node: Strip trailing slash in _actor_uri_to_userid.

At least in my WordPress installation the URI is required to have a trailing slash and that ends up being included in the userid with the current Wordpress method override.
Related: #275

Suggest we make this work this way first, and once we have something running, we think again.

Suggest we make this work this way first, and once we have something running, we think again.

I'm not sure what you mean. We can't make the URL work with WordPress without the trailing slash.
Are you referring to the hard-coded URL structures rather than specifically to the trailing slash?

I typed this comment into the wrong issue, was intended for #275. Too many windows open.

This does not seem to be an issue any more based on looking at the code.


Remove PyTorch requirement in documentation

Description
As mentioned in the linked issue, the installation page currently says that the user needs to have PyTorch == 1.5.0. However, this requirement is not necessary for the user to install, as it is included in requirements.txt and is installed with the ivadomed package. This pull request removes that line in the documentation.
Linked issues
Resolves https://github.com/ivadomed/ivadomed/issues/655

Pull Request Test Coverage Report for Build 512677744

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

Totals

Change from base Build 510201240:
0.0%

Covered Lines:
5261

Relevant Lines:
6987

💛  - Coveralls

Pull Request Test Coverage Report for Build 512677744

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

Totals

Change from base Build 510201240:
0.0%

Covered Lines:
5261

Relevant Lines:
6987

💛  - Coveralls


RSS Feed Watcher

A module that watches, or perhaps only queries, RSS feeds. From this one could implement generic watch functionality many things. One could easily make halibot watch a github feed and it would then inform you whenever a new commit has been pushed, for example.

Sounds similar to the reddit watcher idea that I attempted and failed: would be interesting to have live RSS info dumped to chat rooms as they are updated.


Fix some trivial typos in readme.

Some typo fixes - should be totally unexciting. This file has a mix of DOS and UNIX line endings, which I have NOT fixed in this checkin (but seem to show up in some diffs).


zsh: 5.4.2 -> 5.5

Motivation for this change
New stable release of ZSH: https://sourceforge.net/p/zsh/code/ci/master/tree/
Things done
Using it on my NixOS setup now without any obvious problems.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build zsh

Success on x86_64-linux (full log)
Attempted: zsh
Partial log (click to expand)
shrinking /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/lib/zsh/5.5/zsh/pcre.so
shrinking /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/lib/zsh/5.5/zsh/system.so
shrinking /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/lib/zsh/5.5/zsh/compctl.so
gzipping man pages under /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/lib  /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/bin
patching script interpreter paths in /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5
/nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5/share/zsh/5.5/functions/harden: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
checking for references to /tmp/nix-build-zsh-5.5.drv-0 in /nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5...
/nix/store/k3zg9hm6w0xwj5rgkcmpjv9767f34qmd-zsh-5.5

Success on x86_64-darwin (full log)
Attempted: zsh
Partial log (click to expand)
fi
mkdir -m 755 -p -- /nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5/share/zsh/5.5/help
make[1]: Leaving directory '/private/tmp/nix-build-zsh-5.5.drv-0/zsh-5.5/Doc'
post-installation fixup
gzipping man pages under /nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5/share/man/
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5/lib  /nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5/bin
patching script interpreter paths in /nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5
/nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5/share/zsh/5.5/functions/harden: interpreter directive changed from "/bin/sh" to "/nix/store/x030a63qdilnv02pkivfjg44pdxsh5km-bash-4.4-p19/bin/sh"
/nix/store/nxrbq21fvlpma1ii614a02hwza88ffp0-zsh-5.5

Changes from 5.4.2 to 5.5
-------------------------

The effect of the NO_INTERACTIVE_COMMENTS option extends into $(...) and
`...` command substitutions when used on the command line.  Previously,
comments were always recognized within command substitutions unless the
comment character "#" was disabled via reset of $histchars.

An alternative assignment syntax for indicating indices for arrays
and keys for associative arrays:

typeset -a array=([1]=first [2]=second)
typeset -A assoc=([key1]=val1 [key2]=val2)

is allowed for compatibility with other shells.  In the case of normal
arrays the new syntax can be mixed with the old.

Success on aarch64-linux (full log)
Attempted: zsh
Partial log (click to expand)
shrinking /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/lib/zsh/5.5/zsh/rlimits.so
shrinking /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/bin/zsh
shrinking /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/bin/zsh-5.5
gzipping man pages under /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/lib  /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/bin
patching script interpreter paths in /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5
/nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5/share/zsh/5.5/functions/harden: interpreter directive changed from "/bin/sh" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5...
/nix/store/49lpizw250qhj5yrxr4kkc48z2mfk4n3-zsh-5.5


Responsiveness improvements

If there is no JS support the user will get a classic input box where he/she can enter a string. If there is JS support, there will be additional features but the input field that is submitted will always be empty and you need to use javascript to collect the values. I think this requires unnecessary extra-work. Why not create a new hidden field that is populated/updated whenever the tags change? Or at least create an event that can be used to do that when the module is instanciated.
Or maybe the functionality is already there but the documentation is not clear for this scenario. Or I wasn't paying attention :)

I revert the form back to the original value before submissions. It involves less work than creating a hidden field and making sure it stays in sync


Network Policies third party OSS projects support

regarding Network Policies third party OSS projects support , could you add on this page at
https://docs.microsoft.com/en-us/azure/aks/support-policies#aks-support-coverage a reference to the page https://docs.microsoft.com/en-us/azure/aks/use-network-policies#differences-between-azure-and-calico-policies-and-their-capabilities which states that KubeNet+Calico is not supported by Azure support Teams, but by Calico community support.

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

ID: 36ecef62-68f2-9e81-f4b6-da2b49d1a653
Version Independent ID: a6c2c35a-8a12-a9de-0a4e-669cf8506892
Content: Support policies for Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/support-policies.md
Service: container-service
GitHub Login: @jnoller
Microsoft Alias: jenoller

@ezYakaEagle442
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@jnoller
Can you please check and add your comments on this doc update request as applicable.


Update Quality Level 1

Related:

[x] https://github.com/eProsima/Micro-CDR/pull/61

TODO:

[x] uncrustify
[x] check Synopsis
[x] CodeQL

When merged update the version to v1.2.2 and create a release.

Build status:

Linux
Windows

Build status:

Linux
Windows


How to use pre-trained model and where is post-processing codes?

Hello, Sir. First of all, many thanks for your nice codes!
Because there were so many errors while using original-LaneNet code, I was looking for other version of same network.
And I found your codes, and I saw it works well!
By the way, I have some questions.

I want to use pre-trained model (such as trained LaneNet model which was trained with tuSimple datasets), may I ask you direction how to use it in your codes?

I was to use post processing codes. Because I want to count the number of lanes from the image. But I cannot find this code... Where can I revise this codes?

Also, I want to classify multi-class lane detection.. Is there any config file in your codes? And do I have to revise some parts of the code for multi-class detection?

Thank you again for your codes! I will wait for your reply :)

Hi, landkwon94:

You can use my pre-trained model here: https://github.com/IrohXu/lanenet-lane-detection-pytorch/blob/main/log/best_model.pth
The model is ENet version and trained with Tusimple dataset. For using the other model trained by yourself,  please change the --model of test.py.

You can add your code inside the test.py.

Tusimple will not helpful for multi-class lane detection & classification, as it do not label the type of the lane marking. My group is researching for this topic these days and we will submit a new dataset and new transformer-based lane detection model to ECCV.

Thank you so much for your kind reply! I will carefully do that, and I will wait for your new paper! Thanks again :)


⚠ Bofrost.at has degraded performance

In 5e1edb7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1321 ms

Resolved: Bofrost.at performance has improved in 73ec0f1 after 8 minutes.


I have a very basic question

I want to ask why I report an error when I use vs2022 for packaging

Working  on my side with VS2022 17.4:
Rebuild started...
1>------ Rebuild All started: Project: Installer, Configuration: Debug Any CPU ------
2>------ Rebuild All started: Project: NLog.EFT.Trainer, Configuration: Debug Any CPU ------
Restored C:\dev\EscapeFromTarkov-Trainer\Installer\Installer.csproj (in 170 ms).
Restored C:\dev\EscapeFromTarkov-Trainer\NLog.EFT.Trainer.csproj (in 170 ms).
1>  Installer -> C:\dev\EscapeFromTarkov-Trainer\Installer\bin\Debug\Installer.exe
2>  NLog.EFT.Trainer -> C:\dev\EscapeFromTarkov-Trainer\bin\Debug\NLog.EFT.Trainer.dll
2>          1 file(s) copied.
========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ==========
========== Elapsed 00:03.331 ==========

Double check that the property EFTBasePath is properly set in your NLog.EFT.Trainer.csproj.
See:
https://github.com/sailro/EscapeFromTarkov-Trainer/blob/master/NLog.EFT.Trainer.csproj#L17

感谢，我去检查一下
Thank you. I'll check it


Size filter in accordion

This PR is not to be merged, its sole purpose is to document and delete the associated branch

Closing PR as per comment


How to get the "data-bin/multi30k.en-de.mmt_vqa/train.imgname"

Hi
Thank you for your great work. I found No such file or directory when trying to run your code: 'data-bin/multi30k.en-de.mmt_vqa/train.imgname'.I'd like to know what code was executed to generate this file?

Apologies for omitting a description of the source of this file.
'data-bin/multi30k.en-de.mmt_vqa/train.imgname' indicates image file name of  multi30k, you can get it from here: https://github.com/multi30k/dataset/blob/master/data/task1/image_splits/train.txt.
Note: You can post-process this file based on the paths of the Flickr images you downloaded.

Thank you for your reply. But now I have another problem, I have no problem running English to German translation, but my English to French translation is very bad, I only changed the target language, the other hyperparameters are the same as in German, can I ask what went wrong?
Generate test with beam=5: BLEU4 = 3.32, 30.5/6.2/1.7/0.5 (BP=0.951, ratio=0.952, syslen=13553, reflen=14229)
VizSeqScore(corpus_score=0.207, sent_scores=None, group_scores=None)


-1.2k LOC in s_mpi_sendrecv_variables_buffers

Description
s_mpi_sendrecv_variables_buffers has too much repetition and is therefore very hard to read and maintain. This PR refactors it, removing 1.2k LOC.
Scope

[x] This PR comprises a set of related changes with a common goal

How Has This Been Tested?

[x] Test Suite
[ ] Example Cases (QBMM + Bubbles)

When this works it will be my favorite PR to date, second to the Frontier merge and my LAPACK commit.

@sbryngelson I modified the 1D_qbmm example case to run on 8 A100s in 3D with different BCs. I compared the results against master using the ./mfc.sh packer and the results are EXACTLY the same:
 Comparing test/master.txt to test/master.txt:

   OK: The two packs are within tolerance (abs: 1.00E-12, rel: 1.00E-12).
   Average error: abs: 0.00E+00, rel: 0.00E+00.

This test was important because halo-exchange buffers are different when qbmm .and. .not. polytropic evaluates to true.

wonderful. I think the Frontier case will run before maintenance and then I will merge. I won't merge anything else in the meantime anyway since all other PRs will also be waiting on Frontier CI.


Duplicate Entries enlisted sometimes

Sometimes duplicate entries are seen. One record is seen . Twice.

Hi Mukul,
Thanks for reporting this issue. Can I have some information to reproduce the issue? JSON file & Core Data model or sample project would help.

Closing for lack of response.


Setting_menus: Correct hover on actions column in tables(dark theme)

Ingored hover behavior for actions column in tables,
using hover:not(.class_name).
Fixes: #21137

Testing plan: Manually tested in both themes.
GIFs or screenshots:

@yogesh-sirsat , can you please fix the typo of word 'ingored' in your description of the PR as well as the commit message for this PR.

Rest, lgtm.
@timabbott , can have a look at this.

Hey @jai2201, it's done.

Merged after tweaking the commit message to explain the problem more clearly, thanks @yogesh-sirsat!


Miscellaneous Improvement to azure-core

Description
Adds miscellaneous performance and reliability improvements to azure-core.

Updated AddDatePolicy to use optimized RFC1123 string creation. Falls back to previous functionality if an error occurs (unlikely).
Updated HTTP request and response body logging to use low-copy APIs introduced recently.
Added cache for previously used HttpResponseException constructors instead of looking it up each time the exception occurs. Additionally, added specific checks for HttpResponseException types that exist in azure-core to reduce the usage of reflection when constructing exceptions.
Added properties to SwaggerMethodParser to track the index of Context and RequestOptions in the parameters array passed instead of looking it up on each call.

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

@alzimmermsft: Do you think any of the performance improvements are large enough to be measured by our end-to-end perf tests?

@alzimmermsft: Do you think any of the performance improvements are large enough to be measured by our end-to-end perf tests?

Maybe, I know the RFC1123 datetime handling was changed in the past and made a moderate performance difference and this PR updates the DatePolicy to use that logic so this may be an improvement. But, the other improvement cases are mainly in error paths which we don't normally tests.
I'll add a few micro benchmarks instead and post the numbers, and from there we can determine whether it's worthwhile calling this out in a larger end-to-end performance test.

Could you share results from benchmarks ?

RestProxyResponseConstructionBenchmark
Code path is called at least once per service client method.

Benchmark
Mode
Cnt
Score
Error
Units

directConstruction
avgt
15
4.443
± 0.128
ns/op

reflectionConstruction
avgt
15
179.818
± 41.468
ns/op

RestProxySpecialParametersBenchmark
Code path is called at least twice per service client method.

Benchmark
Mode
Cnt
Score
Error
Units

directArrayAccessForSpecialParameters
avgt
15
2.303
± 0.018
ns/op

iterativeCheckForSpecialParameters
avgt
15
9.854
± 0.054
ns/op

AddDatePolicyBenchmark
Code path is called at least once per service client method.

Benchmark
Mode
Cnt
Score
Error
Units

dateTimeFormatter
avgt
15
835.178
± 19.411
ns/op

dateTimeRfc1123
avgt
15
543.192
± 6.362
ns/op

@alzimmermsft, @kasobol-msft: I ran the storage tests before/after this PR, and perf was the same:
DownloadBlob(10KB)
Before: 14,601
After: 14,545
UploadBlob(10KB)
Before: 11,405
After: 11,341
ListBlobs(5)
Before: 14,793
After: 14,872

Thanks @mikeharder! That's no surprise to me as the number of times these methods are called is low on a per-request basis and the improvements are much smaller than any network noise.

Thanks @alzimmermsft for going through and ensuring azure-core is clean and always improving. It's always great to see these tidy-up's happening!


RootsWallet DIDDoc Viewer

We need a modal that provides a visual representation of a DIDDocument

will be in roots-react-native


Lucy testing um scripts

There is a plan to move towards using GitHub and this ticket acts as a proof of concept for using rose-stem or code-styling scripts from GitHub. This PR focuses on enabling rose-stem to use an up-to-date version of umdp3_checker scripts from GitHub, but also contains two admin scripts that can be pulled and manually run.
This is linked to a UM ticket #7266
The script_updater.sh script has been added to this project code, so it can be updated on GitHub, and can be manually run. However there is also a copy on the UM, which will be automatically run by rose-stem.
The code in the scripts indentation.py and styling.py has not been modified and is just a copy of the scripts in the UM admin/bin
N.B. The nature of this change means that users will have to have a GitHub account with Met Office permissions to run this script from the UM branch.
Currently this is under the Simulation-Systems project on GitHub, but may do better in its own project.

Closing this PR as it's been duplicated in the SimSys_Scripts repo. Cheers


Feature/ng update 10

Story
Exploring an upgrade of Angular to version 10 for use with another project. Direct Message me for information.
Changes

Ran through the angular upgrade checklist
Updated the version to 0.10.0
Modified some code in demo2 -- which does not seem to work

Tests

Ran demo1.
Attempted to recover demo2, but it has issues that remain

Jeremy,
Can you please bump version to 0.11.0 in package.json ?


Added method to apply multiple named aberrations to a model PSF

Sorted! It may be worth adding black==19.10b0 to the requirements file, as the latest version of black fails to format identically to the CI's specs.


Fix test cases hanging due to missing await keywords

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tablet mode detected, but no commands issued.

Hi
I am using a yoga 6 (13abr8) and I am to the point of creating the configuration file, but other than detecting the tablet mode switch it doesn't seem to issue any commands.
I have not posted an issue on here before, so I'll wait to hear from you before posting any output.
Thanks

First, are you sure that commands are actually not issued or that they don't do anything? Because for example on Wayland they won't do anything. Commands part is kinda up to users, that's why they are in the config, because only you know what you want to happen during mode transitions and how to make it happen in your particular desktop environment.


Add upstream maintainer as the project collaborator

Upstream has indicated interest in helping with the snap maintenance.

Done:


[Database] Feature request: import selected field's rows from an external database

I understand that currently LocoKit uses its own database and has no way to import data from an external database.
In my use case, I would like to allow users to import some fields from an external source in order to help filling some fields in the rows, but it should stay optional.
Here is a suggestion of this feature story:

The source SQL database would be predefined by admins (URL, username, password,etc.)
In the Database > Schema tab, a field would be added and set as "fillable with an external source: MyPreviouslyDefinedDB"
In this added field we map it to the corresponding column in MyPreviouslyDefinedDB, let's call it column description in table events
While adding data to the LocoKit app, the user may choose to fill the field manually, or by choosing to automatically import from MyPreviouslyDefinedDB by setting the corresponding row's event ID.

That's an interesting feature !
Actually, we know the way LocoKit store/fill the data is a bit limited, and we are implementing an API over SQL feature, to allow the user retrieve data from other data source.
This is a big feature, but I think it could help in this feature, as the user would be able to "link" data.
Could you tell me if this story would be enough for you :

The source SQL database MyDefinedDB is predefined by admins
In the Database > Schema tab, the user see tables from the database MyDefinedDB (because he has access to this db, in this workspace)
The user add a new table specific_events
The user create a relation between table field named related event between specific_events and events
The user create another lookup field event_description in the table specific_events, pointing to events.description
When filling a new specific_events record, the user is able to fill the related_event by choosing an event from the events table, and the field event_description is automatically filled with the matching description

When you say the user may choose to fill the field manually, do you mean this field could be not linked to an event ?

Thank you for your suggestion.

When you say the user may choose to fill the field manually, do you mean this field could be not linked to an event ?

Yes, I mean the user may optionally choose to automatically fill in the field with the content of a field from an external database. But there is not link created between the newly added field and the field from the external database. At the end, the user has the final word on the raw content of the field.
Taking this into consideration, maybe your suggested story may be too constrained. I imagine that, in order to fulfill the needs of everybody, a lock option would be interesting. If the lock option is enabled, than your story seems okay, and the user can only fill it's field with the content from the external database. If the lock option is disabled, than the user should be able to see the content of the external database as suggestion but still be able to add its own content. In that case, maybe the field should not be a lookup field, but something else.

I understand better.
The field you want to create could take suggestions from another data source (as you define it, or may be an external API too, maybe) and just inject the retrieved data, with no particular link / constraint.
The lock feature is interesting.
I don't know if this need to be a new field type, or just a new option for an existing field type.
If this is a new option, I think it could be related to the RELATION_BETWEEN_TABLE (RBT) field type. We could define a field related to a table, to have the autocompletion feature, without storing the link between records.
We could also think as an option of number, string, date fields (maybe others), named suggestions from.
This new option could be configured by defining a suggestion table (as we already do for RBT fields), or an external API, and the foreign fields we want to retrieve ?
Thus, the user could choose what he wants to retrieve, without linking to the record/data.
@Alketta what do you think about it ?
Do you have an opinion on which way could be better ?
@KillianKemps do you think the idea of a suggestions option would be "better" as it could cover more use cases ?
Or would you prefer a new field type ?
Do you have already seen this feature in other tools you know / use ?


Preview in Editor doesn't preview properly

Category
Bug in gitbook.com Editor
What is the current behavior?

Breaks are omitted in Preview pane.

What is the desired behavior?
In this example, preview pane should show some space where I've put breaks.
Additional information

Thank you for the feedback.
The latest editor is using our new markdown parser. We'll fix this issue and release a fix soon.
BTW, do you know that you don't have to use
 to do soft newline. In markdown, in a paragraph, if the line ends with two spaces, it'll insert a soft newline.
Removing the
 will switch the editor to Document mode, (which has a much better UX). In Document mode, pressing Shift+Enter will insert a newline in the paragraph (no need to type the two spaces), and Enter will split the paragraph.
Markdown source
Interval (period)  [[[ THIS LINE ENDS WITH TWO SPACES ]]
options are Auto, Weekly, Monthly, Quarterly and Yearly

Result
Interval (period)
options are Auto, Weekly, Monthly, Quarterly and Yearly

I didn't know about the two spaces. Very handy. However my Preview pane doesn't bring up the right results although it may draw a break in the actual html page once I publish.


contractcourt: increase the default deadline for anchor sweeping

This commit changes the default anchor sweeping deadline from 1 week to 10 weeks so they won't be grouped with other inputs, which mitigates the pinning issue.

Concept ACK.  Not a fix, but it helps a little.

Hmm what about a slightly different approach:
We currently use the Short_Chan_ID as the exlusive group id:
https://github.com/lightningnetwork/lnd/blob/747abb4a0eb0aa7c7a59f4c15475760143ce7ab6/contractcourt/channel_arbitrator.go#L1306
So we know from the definition of the Short_Chan_Id that every blockheight before the Segwit Activation can basically used as an exclusive group in particular for anchor outputs.
https://github.com/lightning/bolts/blob/master/07-routing-gossip.md#definition-of-short_channel_id
Why not use a particular exlusive Group for anchors for the non-cpfp purpose, by this would would also group the anchors which comes quite handy.
We maybe need to be careful that we don't use ZeroConf_Short_Chan_IDs but they use something very high for the blockheight, so we will not have any conflict there.
wdyt ?

I think the current state of the PR improves the situation because anchors will not likely be grouped with HTLCs (at least not with HTLCs of the same commitment tx) however I think we accomplished it in a more difficult way that it actually necessary.
I think the current implementation is in its actual effect equal to not sweeping anchors in the non-cpfp case at all (see my comment above). Which is even a more safer solution because we would not run into the issue where we sweep the anchor when its deadline is below 2 weeks with another potential Force-Close.
The best solution would probably be to mark the anchors with a special exclusive group or introduce a group ID as mentioned in the TODO.
But I would favour the case where we don't sweep the anchors at all, rather then introducing this artificial large deadline.

@ziggie1984 Currently anything marked with an exclusive group has batching disabled completely, which is probably not how we want to handle dangling anchors.
https://github.com/lightningnetwork/lnd/blob/a449a5d1323f89f2873d57cbaa201d0e3d1d1a39/sweep/aggregator.go#L67-L71
For a true fix we need a special "dangling anchor" cluster that only contains dangling anchors.

But I would favour the case where we don't sweep the anchors at all, rather then introducing this artificial large deadline.

Yeah, we don't gain much from sweeping the anchors, and regardless of what we change the deadline to there will be a some pinning vulnerability.
You convinced me -- let's rip out anchor sweeping!

I am also in the 'lets not sweep anchors' camp

I don't think we should give up anchors completely - we just need to find a way to handle it safely and economically. A proper fix is to introduce GroupID when making sweep requests, and only inputs sharing the same group ID will be put in the same tx. This will also fix other weird scenarios such as bumping a specific input accidentally ends up bumping a whole input set. This GroupID gives users another option to group inputs beyond just using the deadline, which is planned for 0.19.0, as part of the finalizing sweeper series #8680.
Think this PR can be closed for now, as this hack seems to bring more issues than anticipated. I also tried out the ExclusiveGroup approach here, it didn't work well as,

using the same ExclusiveGroup for all the anchors means, when one of them gets swept, the rest will be canceled.
using the short channel ID for the anchors means, after the FC tx is confirmed, the old anchor sharing the same short channel ID won't be canceled.

We can def add some counter to this ExclusiveGroup to make it work, but it's more like a hack now as that's not what the exclusive group is designed for. Will go for the GroupID approach instead.


rerun the benchmark of fbopt for diva

git clean -df
git checkout fbopt
git pull
./run_benchmark_slurm.sh examples/benchmark/pacs_diva_fbopt_and_baselines.yaml

Running

done?

if yes, maybe post it here @DanScarc

slurm_errors.txt

i checked the results, so the error is due to time-out which means we have too many random seeds.

temp_results.txt


cephfs: log error message if clone fails

During CreateVolume from snapshot/volume, it's difficult to identify if the clone is failed and a new clone is created. In case
of clone failure logging the error message for better debugging.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@mergifyio rebase

@mergifyio refresh

@Mergifyio refresh


After hook throwing forbidden error for get only conditional rules

Hello :
Thank you for this great tool!!. I'm migrating my older application that was working well with feathers and CASL from feathers v3 (js) to v4 with ts using feathers-casl.
The rules are saved in DB and all of them are working well but one which has get only permission with conditional clause. To reproduce the problem, If I statically define the rule  can('get', 'users', { id: user.id }) instead of 'read' because I don't want to allow find, the after kook throws forbidden error. As soon as I remove the after hook it works fine.
This is because the forOneEl function tests for 'read' and if not allowed returns undefined causing the forbidden error .

Thank you.

Hey, thanks for your feedback and your report.
Are you capable of doing a pull request for this issue?

I don't get it, shouldn't you define an alias for "get" in that case ? @vigalo

@J3m5 did you define the 'read' alias?
I think @vigalo is right with this one. feathers-casl should work with the default methods out of the box. Defining an read alias just for get method when you don't want to allow find seems like a weird workaround.
read should only be sugar for people who want same behavior for find and get and don't want to define ["find", "get"] every time.

Ah, ok I see now, thanks.

@J3m5, I defined the read alias to ["find", "get"] and using it in other rules. As @fratzinger says, I can't re-define the alias to only get and I don't want to allow find.
@fratzinger, I can do a PR for this issue but not at this moment. As a workaround, I modified the rule to read and when the migration is done will do the PR.
Thanks

by the way @vigalo. Do you also use casl on the client side? And if so, which framework (angular, react, vue) do you use?

yes @fratzinger, I use casl on the client side with angular.

Ah nice. Do you use the authentication -after-hook approach or "just" the hooks?
Since feathers-casl is at an early stage and I'm not using angular, I'm searching for someone who could add some hints here: https://feathers-casl.netlify.app/client-side.html#angular  for how to get started with feathers-casl and angular. Would you mind sharing some snippets with us, that we can add to the docs to help others?
I would highly appreciate it 😄

Yes, I use the authentication after hook to load the abilities to use server side and previously I use a custom authentication service to send the abilities to client side in JWT payload .
If I can help, let me know. I'm really busy at the moment but when I finish this tasks I will be glad to help others.
Thanks

This should be fixed in version ^0.1.8-0.
Please try it again with npm i<EMAIL_ADDRESS>and give feedback. It's a pre-release. but it's more stable than the current version. Hopefully I will bring this to v1 soon.
Please also notice that this is major upgrade from casl@4 to casl@5. You might come across errors, which should be fixable by following this: https://github.com/stalniy/casl/releases/tag/%40casl%2Fangular%405.0.0

Hello @fratzinger. I installed ^0.1.8-0 and it seems to work well. The only problem I had was with  @casl/angular, but it is not related with your library. There is a problem with webpack and angular 11  with .mjs and required a postinstall hook:  https://github.com/stalniy/casl/issues/427#issuecomment-758026538. I'll do further tests and report here if necessary.
Thanks a lot with your support.

Such mixed feelings 😄 Let me know, if I can do something about it. Unfortunately I know nothing about angular nor .mjs files.
Should this be a note in the docs? Is this an issue all angular users will come across?

released as stable with ^0.2.0. See release notes: https://github.com/fratzinger/feathers-casl/releases/tag/v0.2.0


I can't download your dataset

I downloaded your dataset through GitHub, but encountered an error when decompressing it, and it cannot be used normally.
I tried to download through the Google link again, but when I downloaded to more than two gigabytes, it displayed "Forbidden". Can you help me? Thank you very much!

I've just download correctly, try using other compress software.

I made many attempts but failed.
Can you share me the address? Thank you very much!

Use gdown to download files from google drive instead of wget
pip install gdown
gdown https://drive.google.com/uc?id=1Szc920DAh5kU8Qk38Doq0znEVR1QmTZS


SecureTextEntry doesn't work on Android

I set secureTextEntry as {true} on property
<Fumi style={{flex: 1}}
                              label={'비밀번호'}
                              iconClass={FontAwesomeIcon}
                              iconName={'lock'}
                              iconColor={'#f95a25'}
                              onChangeText={(password) => this.setState({password})}
                              keyboardType="email-address"
                              autoCapltialize={"none"}
                              autoComplete="none"
                              secureTextEntry={true}
                        />

It works on IOS but not on Android
How can I fix it?

It works for me on Android 5.1 and 6 using Kohana :
<Kohana    style={{width: 300, height:50, backgroundColor:"rgba(255,255,255,0)"}}    label={'Password'}    iconClass={FontAwesomeIcon}    iconName={"key"}    iconColor={'rgb(228, 4, 32)'}    iconSize={20}    secureTextEntry={true}    onChangeText={(password) => this.setPassword(password)}    autoCapitalize={'none'}    autoCorrect={false}    returnKeyType='go'    labelStyle={{color:"#5a5959"}}    />
You can try it and if it works, then it's a problem with the Fumi implementation

This problem didn't occur on other components like Kohana.
Maybe there's a problem with the Fumi. You're right.

I just tried secureTextEntry on Android 4.4 and it worked fine for Fumi. I used the example project that's in the repository.
Could you deploy the example app to your device and try it out @2hyjun?

I am using Fumi and having no issue with secureTextEntry={true} on Android.

Closing for inactivity.


Strange behavior with ul/ol tags in RichTextLabel

Godot version
v4.0.alpha6.official [e4f0fc50f] v4.0.alpha.custom_build [6cd730ea9]
System information
Linux Mint 20.3, Vulkan, NVIDIA GeForce GTX 1050 Ti
Issue description

Strange behavior near ul/ol close tags;
Strange behavior with empty ul/ol tags;
Strange behavior with nested ul/ol tags.

The first 2 points, they might be essentially the same one. Seems to be related to close tags.

Steps to reproduce

Add a RichTextLabel
Check Bbcode Enable
Resize it to make it big enough
In the Text field, enter the following text.

[ol]
two
three[ul]a
b
c[/ul]four
[/ol]end
test 1
a
[ul][/ul]b
c
a
[ol][/ol]b
c

Minimal reproduction project
No response

Do these issues occur on 3.4.4/3.5rc2?

Do these issues occur on 3.4.4/3.5rc2?

No, as list tags (ul, ol) are not supported in 3.x, see #49914.

For the reference, the first two points were resolved by the linked PR.


ci: disable e2e integration tests

This PR disables e2e Cypress integrations tests due to this error:

You've exceeded the limit of private test recordings under your free plan this month. The limit is 500 private test recordings.
To continue recording tests this month you must upgrade your account. Please visit your billing to upgrade to another billing plan.

For stop block automatic PR's from Dependabot, I'm planning to disable this for some investigation.

Opened #2451 to track this, merges to unblock Dependabot PR's.


Mismatched tensor shapes

Thanks a lot for making this repo.  I have been using it with my own dataset using python3.  I have resolved a few version compatibility issues, but now I'm stuck on an issue which I don't think is related to the python version or library versions.
I'm trying to train YOLO on my own dataset with 54 classes, and I'm getting the error:
Traceback (most recent call last):
  File "train.py", line 135, in <module>
    _main_(args)
  File "train.py", line 131, in _main_
    debug              = config['train']['debug'])
  File "/home/aschoen/git/basic-yolo-keras/frontend.py", line 444, in train
    max_queue_size   = 8)
  File "/home/aschoen/.local/lib/python3.5/site-packages/keras/legacy/interfaces.py", line 87, in wrapper
    return func(*args, **kwargs)
  File "/home/aschoen/.local/lib/python3.5/site-packages/keras/engine/training.py", line 2114, in fit_generator
    class_weight=class_weight)
  File "/home/aschoen/.local/lib/python3.5/site-packages/keras/engine/training.py", line 1826, in train_on_batch
    check_batch_axis=True)
  File "/home/aschoen/.local/lib/python3.5/site-packages/keras/engine/training.py", line 1411, in _standardize_user_data
    exception_prefix='target')
  File "/home/aschoen/.local/lib/python3.5/site-packages/keras/engine/training.py", line 153, in _standardize_input_data
    str(array.shape))
ValueError: Error when checking target: expected lambda_2 to have shape (None, 13, 13, 5, 59) but got array with shape (16, 13, 13, 5, 6)

I'm getting the same error regardless of whether I use the train.py script or the Yolo Step-by-Step notebook.
I notice that the raccoon example has one category, so the last dimension of each tensor seems to correspond to number of classes + 5.  So I assume this problem is arising because some part of the train function does not know the correct number of classes.
I set the LABELS variable, and so it seems that the model is getting the correct output dimension via output = Reshape((GRID_H, GRID_W, BOX, 4 + 1 + CLASS))(x), so I think the model is the correct size and it's some other operand that has the wrong size, but it's hard for me to tell where the error is coming from, so I haven't been able to tell what the other tensor is so I can fix the size.

I have a small update.  I found this line in the getitem class of the BatchGenerator class:
y_batch = np.zeros((r_bound - l_bound, self.config['GRID_H'],  self.config['GRID_W'], self.config['BOX'], 4+1+1))

And I think this means that the number of classes in y is fixed to 1

@alanjschoen I use 4+1+1 but not 4+1+CLASS as we only need to pass the index of the object, instead of the one-hot encoding. Says, to signal that the class of the object is the fifth class, I only need to pass index 4, instead of vector [0, 0, 0, 0, 1]. It saves some memory transfer between CPU and GPU this way.
You may further notice that I use tf.nn.sparse_softmax_cross_entropy_with_logits (line 216 in frontend.py) to compute the classification loss. I only need the index of the class, not the full one-hot encoding.
Another user has this same problem (https://github.com/experiencor/basic-yolo-keras/issues/43). It turns out that Keras > 2.0.8 does not allow this mismatched shape. He installed Keras 2.0.8 and the issue disappear. You may give it a try.

I just want to confirm that I changed my keras version and that fixed the problem.


SQL Blacklist bug

Hi, I try to set the SQL Blacklist on the Starrocks but it seems to be not work. My criteria is blocking the query that start with "with". Below command that I try but no one the can match to my query. So I also test with the regex pattern and it's correct.
SQLBlacklist that I applies
ADD SQLBLACKLIST "^with .+";
ADD SQLBLACKLIST "\^with\s.+";
ADD SQLBLACKLIST "\\^with .+";
ADD SQLBLACKLIST "\^with .+";
ADD SQLBLACKLIST "\\^with\\s.+";
ADD SQLBLACKLIST "^with\\s.*(\\n.*)*";
ADD SQLBLACKLIST "\^with\\s.*(\\n.*)*";
ADD SQLBLACKLIST "^with\s.*(\n.*)*";
ADD SQLBLACKLIST "\^with\s.*(\n.*)*";

My Query that I tested
with four_years as (
SELECT cus_id,
   cast(count(b_id) as int) as t
FROM hc.ac.a AS b
WHERE b.date_month  >= 202208
AND DATEDIFF(now(), bdate) <= 90
AND cus_id > 0
AND cus_id <> 27344988
AND b_status not like '%Cxl%'
GROUP BY 1)
select * from four_years limit 10;

Here when I tested on the Regex pattern and it's correct

So the starrocks should apply my regex pattern but it can't prevent my query.
So it might be related to how complex is it on regex Or is it the bug on Starrocks?
StarRocks version (Required)
Starrocks version: 3.2.6
OS: K8s

However, I already tested with the simple one and this one is could block the query.
Here is the simple that I try
ADD SQLBLACKLIST "select count\(\*\) from .+";

I will close the case as I investigated for more information the ADMIN config didn't enable so we have enabled and it work for me


Cannot get VM running in 1.8

Following https://preliminary.istio.io/latest/docs/setup/install/virtual-machine/ or https://deploy-preview-8418--preliminary-istio.netlify.app/latest/docs/setup/install/virtual-machine/, I cannot get the VM running.
The problem is the XDS proxy is expecting certs in OUTPUT_CERTs. However, we do not write them there until envoy requests them (see https://github.com/istio/istio/issues/28099 and https://github.com/istio/istio/issues/28712)
Even if we turn xDS proxy off, somehow still get authentication failures. Not sure why for that one.
cc @stevenctl @christian-posta @bianpengyuan

Marked this as release blocker.

ISTIO_SERVICE_CIDR=*
ISTIO_INBOUND_PORTS=*
*PROV_CERT=*
ISTIO_LOCAL_EXCLUDE_PORTS=15090,15021,15020
PROXY_XDS_VIA_AGENT=true
ISTIO_META_DNS_CAPTURE=true
ISTIO_PILOT_PORT=15012
ISTIO_NAMESPACE=vm-ns

Seems to do the trick for me:
landow@instance-1:~$ tail /var/log/istio/istio.log
2020-11-12T19:44:02.485631Z     info    sds     resource:ROOTCA new connection
2020-11-12T19:44:02.485711Z     info    sds     Skipping waiting for gateway secret
2020-11-12T19:44:02.485737Z     info    sds     resource:default new connection
2020-11-12T19:44:02.485770Z     info    sds     Skipping waiting for gateway secret
2020-11-12T19:44:02.485941Z     info    cache   adding watcher for file ./etc/certs/root-cert.pem
2020-11-12T19:44:02.485993Z     info    cache   adding watcher for file ./etc/certs/cert-chain.pem
2020-11-12T19:44:02.486045Z     info    cache   GenerateSecret from file ROOTCA
2020-11-12T19:44:02.486280Z     info    cache   GenerateSecret from file default
2020-11-12T19:44:02.487004Z     info    sds     resource:ROOTCA pushed root cert to proxy
2020-11-12T19:44:02.487108Z     info    sds     resource:default pushed key/cert pair to proxy
landow@instance-1:~$ ls /etc/certs/
cert-chain.pem  key.pem  root-cert.pem
landow@instance-1:~$

Retesting the istioctl x workload based doc.. seems like that generates everything in a way that would work and I've been repeatedly testing it over the past couple weeks. In that flow, we don't set PROV_CERTS or OUTPUT_CERTS.

Seems like explicitly adding PROV_CERT= to cluster.env is required, omitting it doesn't work.

John pointed out that this will just make us use JWT forever – and it will eventually expire. We likely need a code fix to either use JWT for the first request/until the certs in the specified "PROV_CERTS" dir are ready.
https://github.com/istio/istio/blob/6f04042f382168fced34b519600ebce9ee974792/pkg/istio-agent/xds_proxy.go#L449-L451

the prov_cert and output_certs should be set and  .
output_certs : the path where sds agent store the when sds agent get the cert
prov_cert: the path where sds agent extract the cert the build mtls connection
they should be set the same

Right. In our current integration tests, we have PROV_CERT="" so we only ever use the token.
In our manual testing we set PROV_CERT and OUTPUT_CERT to the same value, and we get continuous failures due to the cert and key never getting fetched.

This should block the 1.8 release, but I don't see it on the triage spreadsheet?

Going to leave this open till we land the 1.8 cherry-pick and manually confirm.


beter background

PR Title/Tagline
fixes images on background screen
How to Test

Please add or build upon a testing card to the Notion page and link it here

Important Changes

Database change / migration to run
Environment config change
Breaking API change

Related Github Issues

#[Number of Issue]
Or, remember to link to an issue on the sidebar

Related PRs

#PRNUMBER

Checklist

[ ]  Database schema docs have been updated or are not necessary
[ ]  Code follows design and style guidelines
[ ]  Code is commented with doc blocks
[ ]  Tests have been written and executed or are not necessary
[ ]  Latest code has been rebased from base branch (usually develop)
[ ]  Commits follow guidelines (concise, squashed, etc)
[ ]  Github issues have been linked in relevant commits
[ ]  Relevant reviewers (Senior Dev/EM/Designers) have been assigned to this PR

I'm going to ask Dr. Evans for his feedback on the appearance of the background page so we can hopefully close out the user story


adjust the e2e scan job tests to fit with new navigation changes

:nut_and_bolt: Description
with recent changes to the navigation, we need to update e2e tests

merging this so we can stop failing the deploy/dev jobs


now the backend is running perfectly

i have resolved the issues

Please accept my pull Request @PARKHI277  #6

This Branch has conflicts. Try again to push your changes

All pull the main branch again as there are some changes in it


Implementation of a Levenberg–Marquardt algorithm

Implementation of a Levenberg–Marquardt algorithm #119, according to the paper Improvements to the Levenberg-Marquardt algorithm for nonlinear least-squares minimization.
The solver in raphson.jl was used as a template for this solver.
I didn't include this algorithm in precompile_algs in NonlinearSolve.jl because then it increased the loading time from 13 to 20 sec, see #128. (I also removed TrustRegion from precompile_args, which reduced the loading time from 13 to 0.387 sec).

Edit:
I will include this algorithm in precompile_algs. I naively thought I would have the same loading time as the 13 sec stated in #128, and when I got 20 sec for all three algorithms I thought the last 7 sec was due to the newly added LevenbergMarquardt.
And when I removed both LevenbergMarquardt and TrustRegion the loading time vanished.
But I now tested with only LevenbergMarquardt and NewtonRaphson and the loading time was good. While for TrustRegion and NewtonRaphson Is was 20 sec. Therefore I'll now include LevenbergMarquardt in the precompile_algs.

Testing to remove the precompilation of LevenbergMarquardt to see if it fixes the error in the check "IntegrationTest / ModelingToolkit.jl/All/1 (pull_request)"

Think I've found the issue from #128.
Have to go now, unfortunately, but I'll be back in 12h again.

This looks good for a first pass. More to be done, but we should split correctness from improvements.


Increasing the precision for Naive Bayes models

Closes #352

Codecov Report

Merging #360 (d53ffe7) into main (50f1f5c) will decrease coverage by 4.88%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #360      +/-   ##
==========================================
- Coverage   90.98%   86.09%   -4.89%
==========================================
  Files          58       58
  Lines        3373     3374       +1
  Branches      675      675
==========================================
- Hits         3069     2905     -164
- Misses        163      326     +163
- Partials      141      143       +2

Flag
Coverage Δ

unittests
86.09% <100.00%> (-4.80%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...bird/ml/operator_converters/_nb_implementations.py
100.00% <100.00%> (ø)

...mmingbird/ml/operator_converters/sparkml/linear.py
42.85% <0.00%> (-57.15%)
:arrow_down:

...bird/ml/operator_converters/sparkml/discretizer.py
47.36% <0.00%> (-42.11%)
:arrow_down:

hummingbird/ml/_topology.py
67.68% <0.00%> (-17.50%)
:arrow_down:

hummingbird/ml/convert.py
67.36% <0.00%> (-16.85%)
:arrow_down:

hummingbird/ml/_container.py
77.55% <0.00%> (-12.60%)
:arrow_down:

hummingbird/ml/_parse.py
76.11% <0.00%> (-10.20%)
:arrow_down:

...ml/operator_converters/sparkml/vector_assembler.py
90.00% <0.00%> (-10.00%)
:arrow_down:

...rd/ml/operator_converters/sklearn/decomposition.py
81.81% <0.00%> (-6.07%)
:arrow_down:

...l/operator_converters/_pipeline_implementations.py
73.68% <0.00%> (-5.27%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


Cancel save file dialog, will crash the application

https://github.com/tryphotino/photino.Native/blob/94a9adace478eee339f305ebe42bf931c94529af/Photino.Native/Photino.Linux.Dialog.cpp#L104C11-L104C11
Cancel save file dialog, the method returns NULL, the above code will cause Segmentation fault.

Good catch. thank you. We have just checked in a change that fixes this. It will be in the next version.


Panic when getting empty response from server

As noted in this other (closed) issue: https://github.com/hyperium/hyper/issues/365
When receiving empty response data, hyper consistently panics with:
thread '<unnamed>' panicked at 'thread '<unnamed>Http11Message lost its underlying stream somehow.', /home/jneves/.cargo/registry/src/github.com-0a35038f75765ae4/hyper-0.6.10/src/http/h1.rs:270

Yep, try updating hyper, this was fixed in a patch.
On Fri, Sep 4, 2015, 12:26 AM João Neves<EMAIL_ADDRESS>wrote:

As noted in this other (closed) issue: #365
https://github.com/hyperium/hyper/issues/365
When receiving empty response data, hyper consistently panics with:
thread '' panicked at 'thread 'Http11Message lost its underlying stream somehow.', /home/jneves/.cargo/registry/src/github.com-0a35038f75765ae4/hyper-0.6.10/src/http/h1.rs:270
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/issues/646.

Actually, I think this can happen, but not because the response is empty, but because the Content-Length header is invalid.
For example, try accessing a server that gives Content-Length: asdf or even Content-Length:  (i.e. empty) and you'll reproduce this.
It's because the get_incoming method definitely drops the stream here and returns an Err, but then Response tries closing it in the error match arm here.
Adding a line to save the stream before returning the Err in get_incoming fixes it, though...


Update test-infra

Major changes:

Use regional clusters for E2E tests
Allow specifying the E2E test cluster min/max size using environment variables
Use the already setup service account when running E2E tests
Block tests using the release/nightly GCRs
Remove all code deleting images from GCR
Use go-junit-report for go test summaries (bye bazel)
Georeplicate GCR releases
Add support to weekly "dot" releases

Fixes #160.

/lgtm
/approve


Fixed nil String bug (issue #2), can select "ALL" the data

I fixed issue #2 and @Flox06 added the ability to call "ALL" as a string, to select all the network data.

Merci beaucoup, guys, you rock!
Merged and a new version is pushed to rubygems: https://rubygems.org/gems/vatsim_online
I appreciate the contribution! Take care!


Missing method process_as_bytes

It would be cool to have a method process_as_bytes where input type is byted JSON.
import requests
from kaiba.process import process_as_bytes

config = {
...
}

resp = requests.get('https://example.com')
process_as_bytes(resp.content, config)

It removes a need to cast to json to transform for me as a customer and makes code cleaner for me.

I like this idea.


FINERACT-1910: Added pagination & sorting support in datatables/query

Description
Describe the changes made and why they were made.
requires some review by maintainers, please tell if there is room for improvements, thanks
Ignore if these details are present on the associated Apache Fineract JIRA ticket(https://github.com/apache/fineract/pull/1284).
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[x] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[x] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@shyam1s15 Please check your commit, because it is not compiling...


sourcemap: posscss-loader loses information about source file from the previous sourcemap

Details

posscss-loader loses information about source file from the previous map.
links to a single app.scss file generated by sass-loader
with postcss-loader

without postcss-loader

Reproduction [Code]

          {

              test: /\.scss$/,
              use: [{
                  loader: "style-loader",
                  options: { sourceMap: true }
                },
                {

                  loader: require.resolve('css-loader'),
                  options: {
                    importLoaders: 2,
                    sourceMap: true
                  },

                },
                {
                  loader: require.resolve('postcss-loader'),
                  options: {
                    sourceMap: true,
                    // Necessary for external CSS imports to work
                    // https://github.com/facebookincubator/create-react-app/issues/2677
                    ident: 'postcss',
                    plugins: () => [
                      require('postcss-flexbugs-fixes'),
                      autoprefixer({
                        browsers: [
                          '>1%',
                          'last 4 versions',
                          'Firefox ESR',
                          'not ie < 9', // React doesn't support IE8 anyway
                        ],
                        flexbox: 'no-2009',
                      }),
                    ],
                  },
                },
                {
                  loader: "sass-loader",
                  options: {
                      sourceMap: true,
                      includePaths: ["node_modules"]
                  }
              }]

          },

/cc @ai Problem in postcss? We send file https://github.com/postcss/postcss-loader/blob/master/lib/index.js#L108
@PawelGIX Can you create minimum reproducible test repo?

The problem is between Sass, source-map and PostCSS :D

@ai can you provide link on issue or some other stuff?

Nope. The best way to understand what happens https://sokra.github.io/source-map-visualization/

@PawelGIX I need a (minimal) reproduction to debug this please

Closing due to inactivity for now, if you can provide a concrete repo for reproduction feel free to reopen :)