Speed improvements for files in UI

This PR removes the call to get the file header when listing the files for an organization to speed up the performance of the UI.
Changes

Removes the call to get the file header in order to speed up the listing of downloadable files in the UI

Checklist
Testing

[ ] Tested locally?
[ ] Ran quickTest all?
[ ] Ran ./prime test against local Docker ReportStream container?
[ ] Downloaded a file from http://localhost:7071/api/download?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes
List GitHub issues this PR fixes

#issue

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

What's the status of this?


HOSTEDCP-1469: Set GOMEMLIMIT annotation based on request serving node label

What this PR does / why we need it:
If a label of hypershift.openshift.io/request-serving-gomemlimit is found in the request serving nodes for a given HostedCluster, the HostedCluster will get an annotation of
hypershift.openshift.io/kube-apiserver-gomemlimit with the same value.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #HOSTEDCP-1469
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

/test verify
/test unit
/test e2e-aws

/lgtm


Add Dockerfile

Add a Dockerfile to make it easier to build in all environments.
(NOTE: To actually use this Dockerfile, you'll need to change localhost:8234 to <IP_ADDRESS>:8234 in main.go.)

Thanks for your PR (｀･ω･´)🙌
I'll add a port option (or env variable) in future(｀･ω･´)


chore(main): release 2.116.1

:robot: I have created a release beep boop
2.116.1 (2024-05-21)
Bug Fixes

versioning: fix cloning environments using v2 versioning (#3999) (eef02fb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Flagsmith/flagsmith/releases/tag/v2.116.1 :sunflower:


[Release] sdk/resourcemanager/authorization/armauthorization/2.0.0

This release help to fix two issues:

https://github.com/Azure/azure-sdk-for-go/issues/18811
https://github.com/Azure/azure-sdk-for-go/issues/18674

Wait for .Net authorization GA.

v2 releases are painful for customers. We want to keep this on the v1.x path.

The breakings contain required param removal, property ref change and operation removal from swagger. I don't think it is possible to make it 1.x.

Any progress here? Is there a way to get this merged in the next days?

@RickWinter, I've use directive to mitigate most of the breakings. Only one orphan model not used is left. I think it could be ignored. You could see the new generated SDK here and directive here. @JeffreyRichter Could you help to confirm whether we could release it with 1.1.0?

Joel & I spoke about this today. Here's where we're at...
It is a reality today that swaggers have bugs, we generate a client and then the swagger gets fixed causing a breaking change in the client (even though the service itself has not changed).
So, if we ship a client V1.0.0 and then the swagger gets fixed, we ship a new client V1.0.1.
Now, let's say an app uses V1.0.1 and also uses another package that depends on V1.0.0 - the app can't build now because V1.0.0 & V1.0.1 can't be compiled together into a single app - this is a very bad place for a customer to be and so we can't do this and put them there.
So, any client library break must be done in a new major version so that the new major and old major can be compiled together into a single app.
Obviously, the best thing for us (service team and SDK teams) to do is to better validate our swaggers and fix bugs before we create and ship client libraries.

Any progress here?

Any progress here?

We are double confirming with service team and will release the new version soon.

@RickWinter Please sign off. .NET has released package-2022-04-01 as stable and we also got confirmation from service team to release Go SDK.

Release request: https://github.com/Azure/sdk-release-request/issues/3207

All the breaking changes is from this PR and approved in this PR.

Function *RoleAssignmentsClient.NewListForResourcePager parameter(s) have been changed from (string, string, string, string, string, *RoleAssignmentsClientListForResourceOptions) to (string, string, string, string, *RoleAssignmentsClientListForResourceOptions)
New swagger here. This operation's path params have been changed. Old version here.
Type of RoleAssignment.Properties has been changed from *RoleAssignmentPropertiesWithScope to *RoleAssignmentProperties
Struct RoleAssignmentPropertiesWithScope has been removed
Properties of RoleAssignment model has been changed. Old one here. New one here.
Function *RoleAssignmentsClient.NewListPager has been removed
Struct RoleAssignmentsClientListOptions has been removed
Struct RoleAssignmentsClientListResponse has been removed
An operation has been renamed. Old swagger here. New one here.
Struct PermissionAutoGenerated has been removed
Permission model has been changed to align with other Permission definition. Old one here. New one here.

@jhendrixMSFT @RickWinter @JeffreyRichter I list all the breakings and please help to review.


Preemptively create issues with answers to common errors / warnings

As folks build out their Keystone app, they're inevitably going to run into error outputs or warnings, which they'll then drop into Google to find an answer for.
It would be great if we could preemptively create issues for those and answer them so when Googler's Google, they land on our issue with the answer in the first comment and they can continue being awesome 🎉
NOTE: This is not in exclusion to our docs, just solving for the case where GitHub has excellent SEO. Could also make sense to do it on StackOverflow too.

Here's a great example: https://github.com/expressjs/session/issues/556

The 16 emoji responses here show that folks have landed on this issue, probably without reading the docs, and have been helped and on their way asap 👍

We've got a big task to change\update our error messages. Once this is done let's grab all the console logs from the main packages and see what issues we can create for each of them. That's a better starting point.


Mutating props: attempted to assign to readonly property

Trying to use the Swiper component in react-native 0.26.2 in my iOS 9.3 simulator gives the error attempted to assign to readonly property

Which is tracked down to this line where you mutate this.props - something that probably shouldn't be done.

Fixed in #169


rename pv containers recipes to remove ambiguity.

There is already a recipe named 'connman' which creates a conflict. It would make sense that there could be many single-app containers that would similarly conflict.

ok cool. could we name the containers maybe pv-XXXX ? e.g. pv-connman etc.? all same prefix and short at best....

or you feel for yocto having -suffix would feel moreg natural?


Update README.md

cd first-based does not exit.
Hence updated to cd-first-and-based which opens the directory post git clone


New package: Microsoft.Sysinternals.MoveFile version 1.02

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #181426

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

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

Microsoft Reviewers: Open in CodeFlow

Verify:


chore: drop temp_card table and all associated items

Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[x] Refactoring
[ ] Dependency updates

Description

This PR removes the temp_card table and all associated queries, functions, etc.
Additional Changes

[x] This PR modifies the database schema
[x] This PR modifies application configuration/environment variables

Database Changes:

The temp_card table has been dropped. The up.sql and down.sql files just have queries related to the temp_card table from the down.sql and up.sql files in the 2022-09-29-084920_create_initial_tables directory, respectively.

Configuration Changes:

The aws_key_id, aws_region and temp_card_key fields have been removed from the Keys struct ([keys] table in the TOML files).
The keys field([keys] table) has been renamed to secrets, since it no longer holds any keys.

Motivation and Context

Cleaning up unused code.
How did you test it?

N/A
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

By the way, services::encrypt() and services::decrypt() seem to be unused. Should we keep them for now?

No , keep these in case we want to keep data that needs to encrypted and kept in the database

LGTM


Handle SSO or User Already logged in

Currently we expect user to click on Login on the Header however as a step towards getting SSO ready we need some provisions.

We need to be able to support an already logged in scenario. Our application sits behinde WebSEAL, which handles the login page. We are using Angular's APP_INITIALIZER to run a check before application is bootstrapped, so I'd like to be able to display the users name right off the bat, not the Login message.

Fixed by PR#44 version 2.1.3
Try something like this in your app.module.ts
https://github.com/US-CBP/ngx-cbp-theme/blob/c533d6ed36d980513056f9563a039db9d83f0504/src/demo/app/demo.module.ts#L54-L57


sh/rc-cgroup.sh: add openrc. prefix the cgroupv2 path

Some services, like docker, creates and manages /sys/fs/cgroup/ themselves. Avoid conflict with the openrc created cgroup path by adding a openrc. prefix.
Fixes: https://github.com/OpenRC/openrc/issues/680

It seems that it needs more changes for be fully coherent.

Perhaps add a rc.conf variable for the openrc. prefix?

Hi,
I just applied this patch locally to test it and restarted a service.
I found that the old group for the service existed along side the new group after the restart.
e.g. /sys/fs/cgroup/ and /sys/fs/cgroup/openrc. both existed.
I was able to remove the old cgroup successfully.
Should we add something to this pr to removeit?

Hi,
I just applied this patch locally to test it and restarted a service. I found that the old group for the service existed along side the new group after the restart. e.g. /sys/fs/cgroup/ and /sys/fs/cgroup/openrc. both existed. I was able to remove the old cgroup successfully. Should we add something to this pr to removeit?

Not sure its worth it. Its only a one time problem during upgrade that a reboot will "fix".


Add property to suppress error from GetReferenceAssemblyPaths when the path can't be found

This should allow the .NET SDK to check if a given targeting pack is installed, and if not, fall back to referencing a NuGet package with the reference assemblies.
The full proposal is here: https://github.com/dotnet/designs/pull/33

Code looks fine, just not clear on what targets are changing to use this?

@AndyGerlicher The targets to use it would be in dotnet/sdk, and would implicitly add a PackageReference for reference assembly packages if the targeting pack wasn't found on the machine.  My work-in-progress branch is here, currently by default it only references the reference assembly packages on non-Windows OS's.

@AndyGerlicher Are there some flaky tests?  One of the CI legs timed out, and I see this in the other one:

Unhandled Exception: Xunit.Sdk.TrueException: Expected Directory.GetCurrentDirectory to be 'D:\j\w\innerloop_Win---c5dcd6be\artifacts\2\Debug\bin\Microsoft.Build.Tasks.UnitTests\netcoreapp2.0', but it was 'D:\j\w\innerloop_Win---c5dcd6be\artifacts\2\Debug\bin\Microsoft.Build.Tasks.UnitTests\netcoreapp2.0\TestTemp\d03111684be84ca08b8820a453603a7f'

@dotnet-bot test OSX10.13 Build for CoreCLR
test Windows_NT Build for Full


Examples: update forwarded prop item -> value

the basic and sementic-ui examples had the old item prop in the forwardProps

Codecov Report

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

@@           Coverage Diff            @@
##             master     #33   +/-   ##
========================================
  Coverage          ?   18.8%
========================================
  Files             ?       8
  Lines             ?     218
  Branches          ?      44
========================================
  Hits              ?      41
  Misses            ?     139
  Partials          ?      38

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 a0df855...d36c654. Read the comment docs.

Thanks! We are going to be deleting this folder in favor of this (see #1)
But I'll merge this for now :smile:


Param reset when POST, PATCH or DELETE

Hi! I'm not sure if this is a non expected behavior but it is very annoying one. Also, maybe it is a particular behavior from the project I'm in and not a particular bug of Constance.
The steps I do are:

Go to the panel admin -> Constance
Change any parameter (e.g: Default X: 0 -> Default X: 1)
Make a POST, DELETE or PATCH request to the server
Look at the Constance panel again and find "Default X: 0"

When I do GET requests I do not have any problem it is only with POST, PATCH or DELETE when the config values are reset (It resets all the params, not just the last I've changed)
System configuration

Django version: 1.11.15
Python version: 3.5

This are the other Django plugins I have installed, just in case:
django-app-namespace-template-loader==0.4
django-appconf==1.0.2
django-braces==1.8.1
django-compressor==2.0
django-constance==2.3.1
django-cors-headers==1.1.0
django-dbarray==0.2
django-extensions==1.6.1
django-filter==1.0.2
django-ipware==1.1.1
django-jenkins==0.18.1
django-material==0.9.2
django-nose==1.4.5
django-oauth-toolkit==0.11.0
django-picklefield==0.3.2
django-redis==4.4.4
django-static-precompiler==1.1
django-storages==1.1.8
djangorestframework==3.6.3
djangorestframework-camel-case==0.2.0

Looks like this behaviour belongs to the django admin and not from constance.

Neither Constance nor Admin was the problem, I found out that for some reason someone decided that reset redis parameters when doing a POST, PATCH or DELETE request was a good idea... :/


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3357

Questions ?
Please refer to the Backport tool documentation


Firebase can not able to remove

Firebase plugin show error on executing the cordova plugin rm cordova-plugin-firebase command. It shows the following error.
Uninstalling cordova-plugin-firebase from android
Android Studio project detected
missing file :: app/src/main
Error during processing of action! Attempting to revert...
Uh oh!
ENOENT: no such file or directory, open 'D:\cordova projects\HTMLCodePlay\platforms\android\AndroidManifest.xml'

Same problem:
cordova plugin rm cordova-plugin-firebase
Uninstalling cordova-plugin-firebase from android
Android Studio project detected
missing file :: app/src/main
Error during processing of action! Attempting to revert...

I was able to remove the plugin by running
cordova platform rm android

and then
cordova plugin rm cordova-plugin-firebase

and then re-adding the android platform

I've have just started to get this problem as well.
I believe the plugin need to be updated to support cordova-android 7.1.4.

I'm having this bug now. I need to reinstall the plugin and this error appears when I try to uninstall it. If the problem is that this plugin is not compatible with version 7.1.x of cordova-android, should I expect any more problems in the future?


sdk list doesn't work in SDKMAN 3.3.1

In SDKMAN 3.3.1, sdk list will not work for any candidate names that previously worked:
sdk list grails
Stop! grails is not a valid candidate

sdk list gradle
Stop! gradle is not a valid candidate.

...

As you can see on the release build, all the tests passed which means that the list command definitely works. Also, when I enter sdk list grails, I get the following:
================================================================================
Available Grails Versions
================================================================================
     3.1.0.RC1            3.0.0                2.3.5                2.1.4
     3.1.0.M3             2.5.3                2.3.4                2.1.3
     3.1.0.M2           * 2.5.2                2.3.3                2.1.2
   * 3.1.0.M1             2.5.1                2.3.2                2.1.1
     3.0.9                2.5.0              * 2.3.11               2.1.0
   * 3.0.8                2.4.5                2.3.10               2.0.4
     3.0.7                2.4.4                2.3.1                2.0.3
     3.0.6                2.4.3                2.3.0                2.0.2
     3.0.5                2.4.2                2.2.5                2.0.1
     3.0.4                2.4.1                2.2.4                2.0.0
     3.0.3                2.4.0                2.2.3                1.3.9
     3.0.2                2.3.9                2.2.2                1.3.8
 > * 3.0.11               2.3.8                2.2.1                1.3.7
     3.0.10               2.3.7                2.2.0                1.3.6
     3.0.1                2.3.6                2.1.5                1.3.5

================================================================================
+ - local version
* - installed
> - currently in use
================================================================================

Could I ask you to try flushing your candidates with sdk flush candidates, then opening a new terminal?

That fixed it.  Thanks.

:+1:

I run sdk flush candidates but it cannot resolve the issue. Any suggestion?

Did you open a new terminal?

sdk ls | list not working
sdk ls grails works fine

You will need to use your package manager to install less.

I verified less is working fine.

I suggest moving this to the correct channel. We have a gitter user-issues channel for this sort of thing.


Update futures preview 0.3.0-alpha.17 to 0.3.0-alpha.18

The futures-rs 0.3.0-alpha.18 is released. futures-preview

This is blocked on tokio upgrading.

Tokio 0.2.0-alpha.2 is now using futures-rs 0.3.0-alpha.18

Is there actual need to bump version? cargo update should pick up latest automatically

@DoumanAsh during these alphas there is no guarantee of semver compatibility, so crates that are willing to track the unstable edge should all be aggressively bumping their versions up to the latest release to provide the highest chance of interoperability.


Bad matcher cause completion to hang

Minimal example:

Do edit:-matcher[''] = { bad command }
In a directory with sufficiently many files, do echo

The editor hangs.

I think we could close this issue now.

FWIW, if you wrote "fix #503" or "fixes #503" this issue will be auto-closed: https://help.github.com/articles/closing-issues-using-keywords/


detect script doesn't check multiple services

when checking VCAP_SERVICES the script only looks at the first service

Fixed by 3caf8532aba6d7fac586724ead97eeaddc7d2198


Try using new UnrolledUtilities branch

This PR tries out CliMA/UnrolledUtilities.jl#13. Hopefully compilation won't hang for the non-orographic gravity wave parametrization's unit tests.

Looks like CliMA/UnrolledUtilities.jl#13 didn't help with the compilation hanging issue. I will now try out CliMA/UnrolledUtilities.jl#15 instead.

CliMA/UnrolledUtilities.jl#15 also didn't fix the issue. Now trying out CliMA/UnrolledUtilities.jl#16. We might need to combine these two PRs before we have a solution, but maybe this will work on its own.


[Key Vault] Prepare for strict-sphinx

Description
Resolves https://github.com/Azure/azure-sdk-for-python/issues/33553 and https://github.com/Azure/azure-sdk-for-python/issues/33555.
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.

API change check
API changes are not detected in this pull request.

Validating run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3431860&view=results
(strict-sphinx tests passing in this pipeline led to the SDK bot automatically closing the issues linked to this PR)


Recommend combining Figures 38.6-1 and 38.6-2

Figures 38.6-1 and 38.6-2 show the same thing in slightly different ways. The first makes the facade of the PDQm Patient Demographics Supplier and PDQ patient demographics consumer more clear, while the second makes the transaction flow in this scenario more clear. I think it would be better to combine them into a single figure.

seems good idea


Cannot build tcod-rs on OS X 10.11 - SDL include failure

Homebrew sets up the SDL include files differently than the standard, it seems:
➜  tcod-rs git:(master) cargo build
   Compiling bitflags v0.1.1
   Compiling libc v0.1.10
   Compiling lazy_static v0.1.15
   Compiling tcod-sys v3.0.0 (file:///Users/ysgard/Dropbox/Rust/tcod-rs)
failed to run custom build command for `tcod-sys v3.0.0 (file:///Users/ysgard/Dropbox/Rust/tcod-rs)`
Process didn't exit successfully: `/Users/ysgard/Dropbox/Rust/tcod-rs/target/debug/build/tcod-sys-cb640d538f93be78/build-script-build` (exit code: 101)
--- stdout
STDOUT: \rm -f /tmp/libtcod/release/bresenham_c.o /tmp/libtcod/release/bsp_c.o /tmp/libtcod/release/color_c.o /tmp/libtcod/release/console_c.o /tmp/libtcod/release/fov_c.o /tmp/libtcod/release/fov_circular_raycasting.o /tmp/libtcod/release/fov_diamond_raycasting.o /tmp/libtcod/release/fov_recursive_shadowcasting.o /tmp/libtcod/release/fov_permissive2.o /tmp/libtcod/release/fov_restrictive.o /tmp/libtcod/release/heightmap_c.o /tmp/libtcod/release/image_c.o /tmp/libtcod/release/lex_c.o /tmp/libtcod/release/list_c.o /tmp/libtcod/release/mersenne_c.o /tmp/libtcod/release/noise_c.o /tmp/libtcod/release/parser_c.o /tmp/libtcod/release/pat
...<snip>...
_debug.dylib libtcodpy.pyc
Compiling debug src/bresenham_c.c

STDERR: In file included from src/bresenham_c.c:28:
include/libtcod.h:109:10: fatal error: 'SDL/SDL.h' file not found
#include "SDL/SDL.h"
         ^
1 error generated.
make: *** [/tmp/libtcod/debug/bresenham_c.o] Error 1

--- stderr
thread '<main>' panicked at '`make` returned: exit code: 2', tcod_sys/build.rs:39

This comes because homebrew sets up pkg-config like so:
➜  tcod-rs git:(master) pkg-config --cflags sdl
-D_GNU_SOURCE=1 -D_THREAD_SAFE -I/usr/local/include/SDL

The workaround is to create a link for SDL within the include dir specified by pkg-config.
ln -s /usr/local/include/SDL /usr/local/include/SDL/SDL

There was a similar issue (#203). Are you sure that the steps mentioned there don't solve your issue as well?

It does :dizzy_face:  My bad, I'll close this.


Add withTheme definition

See #483

How it going, @patrick91 ? Do you need any help?

I'm pretty busy these days! I'll try to find some time soon :)

@Igorbek I don't see any way to remove the theme prop any than using rest. Also we need to specify the theme prop in the component interface, otherwise we won't be able to use use it (see: http://s.patrick.wtf/FSirCmZ9dz) so I was thinking to require the them prop on the component. What do you think?

I can't mark the theme prop as required, it will complain when using the component.
Let me know if you have any other feedbacks :)

Yup!
On Wed, 1 Mar 2017 at 07:38, Max Stoiber<EMAIL_ADDRESS>wrote:

@mxstbr approved this pull request.
LGTM, let's shipit?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/pull/521#pullrequestreview-24416120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAotlaZH5qPGmH6s-rrK5-UipKRTtPJMks5rhSB9gaJpZM4MGM5u
.

--
Patrick


Need help on GKE deploy

Hi there,
I'm trying to deploy on GKE by use Helm
My config with yaml file
key: KEY_VALUE
salt: MORE PEPPER
maxSrcResolution: 12
maxSrcFileSize: 10485760
quality: 80
useGcs: true
gcsKey: |
  {
    "type": "service_account",
    "project_id": <value>,
    "private_key_id": <value>,
    "private_key": <value>,
    "client_email": <value>,
    "client_id": <value>,
    "auth_uri": <value>,
    "token_uri": <value>,
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": <value>
  }
enableWebpDetection: true
enforceWebp: true
fallbackImageUrl: gs://<bucket>/default.svg

And deploy successful with my ingress setting
After that, I try to use https://progapandist.github.io/imgproxy-form to get generated URL
But result is Invalid URL
I don't know what I missed, hope someone help me out.
Thank you!

Sorry, I know what it is, forgot to set height to 0.


[BUG] Version 1.2.16 does infinite calls when people join causing huge stutter

On version 1.2.16 the log shows infinite RPC handler messages anytime someone joins, the more people joining the worse it gets until it's unplayable. I also noticed the modded moons were not loading.
I tested it on different versions and all of this works fine on 1.2.15
LogOutput.log

On version 1.2.16 the log shows infinite RPC handler messages anytime someone joins, the more people joining the worse it gets until it's unplayable. I also noticed the modded moons were not loading. I tested it on different versions and all of this works fine on 1.2.15
LogOutput.log

You have 57 errors, i can't support an issue with a modpack burried of errors

Reinstaled everything from a mod manager and most of the issues got solved included this one. Sorry about that.


Notification web / email for flagged post

Feature Request
Is your feature request related to a problem? Please describe.
This extension resolve the issue to report by email when a new post is created or queued for the moderation.
I miss the possibility to be emailed when a post is reported for moderation.
Describe the solution you'd like
Add the possibility to be emailed on the case a post is flagged.
Currently there is no way on Flarum to be alerted by email if a post is flagged.
This great extension help to be informed when there is a new post, a new user, a queue for moderation post but not when moderators need take actions on a flagged post for abuse or spam.

I installed on flarum 1.2 but no notification came at all condititions.

@murdocklawless have you activated notification in your user settings profile?

oh no because there no info about this in description. I activate it and it's ok. thank you very much.


MM-40934 - Playbook metrics dashboard view - frontend

Summary

This is using dev data, and not ready for merging the master, but I wanted to get reviews started since we're getting close to the code complete date.
I didn't realize that we're not actually sending metrics data with the GET /runs endpoint, so I need to add that next. :)
@abhijit-singh I decided to add an error-text colored N/A if the run was finished but the retro/metrics had not be published yet. This will highlight the lack of metrics and encourage people to fill them out (it's better than hiding them, I think).

Ticket Link

https://mattermost.atlassian.net/browse/MM-40926

Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[ ] Unit tests updated

Okay, looks like we're ready for this PR -- added metrics to the GET /runs and added sorting by metric -- the column headers are now clickable. But they won't work if a second (or more) page of the infinite scroll has been loaded (https://mattermost.atlassian.net/browse/MM-41862)

Improved the look of the graphs:


[DATA CONTRIBUTION] CAMELS-ES

Basin prefix
es
Zenodo DOI
10.5281/zenodo.8373021
Number of catchments
269
Location of catchments
Spain
For which periods are streamflow records available in your dataset?
1st October 1991 to 30th September 2020
Please list any sources of the data you contributed.
The discharge records are taken from the "Anuario de Aforos" (https://ceh.cedex.es/anuarioaforos/default.asp),
a public repository of hydrological records in Spain curated by CEDEX (Centro de Estudios y Experimentación
de Obras Públicas) and supported by the gauging networks of the several water agencies in the country.
The European Flood Awareness System (EFAS) version 5.0 is part of the Copernicus Emergency Management Services (https://emergency.copernicus.eu/)

EFASv5 simulated discharge is publicly available in the Copernicus Climate Data Store (https://cds.climate.copernicus.eu)
EFAS static maps are publicly available in the Joint Research Centre data catalog (https://data.jrc.ec.europa.eu/dataset/f572c443-7466-4adf-87aa-c0847a169f23)
The EMO1 dataset is publicly available in the Joint Research Centre data catalog (http://data.europa.eu/89h/0bd84be4-cec8-4180-97a6-8b3adaac4d26 )

HydroATLAS is licensed under a Creative Commons Attribution (CC-BY) 4.0 International Licence (https://www.hydrosheds.org)
ERA5-Land hourly data is publicly available in the Copernicus Climate Data Store (https://cds.climate.copernicus.eu/cdsapp#!/dataset/reanalysis-era5-land?tab=overview)
The processing of HydroATLAS and ERA5 data was done using the Caravan GitHub repository (https://github.com/kratzert/Caravan.
License
CC BY 4.0
Additional context
The official network of gauging stations contains 1074 points. A selection has been made to remove stations with less than 8 years of data in the period 1991-2020, and those whose records show a clear alteration caused by the presence of reservoirs upstream. Unfortunately, after filtering, the distribution of catchments around the country is uneven, representing mostly the central and northern Spain. In the future I will explore the data sets from the water agencies, both to cover a larger part of the country and to explore if it would be possible to increase the temporal resolution of the time series.

Distribution of the selected and discarded gauging stations
In addition to the usual attributes and time series that the Caravan notebooks generate, I have added new attributes and the simulated discharge from the recently released EFAS version 5 (European Flood Awareness System).
Checklist

[X] I have uploaded my dataset on Zenodo, where it is accessible under the DOI provided above.
[X] I used a basin prefix that is not yet used by any other Caravan sub-dataset (you can check this via the Data Contributions discussion thread, where all accepted Caravan contributions are listed).
[X] Permissive License: My data is available under a license that is compatible with the Caravan CC-BY-4.0 license (the easiest way to be sure about this is if your data uses CC-BY-4.0, too).

Hi Jesús,
thanks for contributing data to Caravan, much appreciated. I downloaded the data from Zenodo and had a quick look at it and here are a few things that I noticed.

Naming of the extension: On Zenodo the dataset is named CAMELS-ES, but all extension folders are named es (rather than e.g. camelses. No problem from our side, just something I witnessed.
No matter which extension name you pick, one thing that needs to be changed is that all gauge_ids in e.g. the attribute files and the shape files, but also the timeseries files, should always be {extension_name}_{national_id}. In your case, these are currently just what I assume is the national station id. This is important, because these national ids are not unique across the glob and otherwise it could happen that you have the same gauge_id for a gauge in Spain and e.g. Austria. So it would be great if you could rename the time series files and also make sure that all the gauge_ids in the attribute files and shape files are renamed. Depending on your choice in the previous point, this would e.g. be es_1103.nc, instead of 1103.nc as of now.
Regarding compatibility with the rest of Caravan, can you maybe remove all but the gauge_id field from the shape file? And strictly speaking, also the station shape file is not required, as this could be loaded from the attributes_other_es.csv file (which would also include the river name, country etc.
The name of the basin shape file does not match the pattern we usually use in Caravan. Could you maybe rename the file to {extension}_basin_shapes.shp ({extension} depends on point 1).

Let me know what you think and/or once you updated the Zenodo repository.

Hi Frederik,
I have created a version 1.0.1 with all the changes you suggested. I have chosen the extension camelses.
Let me know if I need to do any further change.
Regards.

Hi,
checked the data again and all looks good. There is only one minor thing: The attribute files and the license file still end with _es instead of _camelses. We use to have the convention that we use the same short name of an extension everywhere (e.g. the gauge id has the same extension str added to the beginning as is used for folder names or in the attribute/license/shapefile file names.)
So if you could rename those files that would be great. Everything else looks fine.

Hi,
Sorry for the delay. The issue with the file names is fixed in the version 1.0.2 of the Zenodo data set.
Regards.


Bump elixir to v1.6.5

✌

Thanks for the PR @cetinajero!

Thank you for your script @onlurking! 👍


'Fetch All' not fetching all updated feeds

 Issue by landonreed
Friday Sep 15, 2017 at 12:33 GMT
Originally opened as https://github.com/catalogueglobal/datatools-server/issues/35

@demory experienced this behavior when fetching feeds for the DC area.  Only three out of 4 or 5 feeds were fetched after clicking 'Fetch All'.

 Comment by landonreed
Tuesday Nov 13, 2018 at 17:07 GMT

No longer an issue.


2 Garage Doors Not Registering.

I have 2 garage doors w 2 ZWave sensors via Smartthings. I've gone thru adding in the MyQLite to my SmartApps and when I go to register my 2 doors, only 1 actually shows up in the My Home. If I go in and do just 1, it is fine. If i remove that one and then add the other, it shows up. However, it seems to not be able to get both to register under My Home at the same time. Any thoughts on how to fix this?? When there is 1, it is totally functional via ST by the way.
Thanks in advance.

I figured it out. had to add a second momentary button tile.


Your site's DNS settings are using a custom subdomain, docs.modcluster.io, that's set up as an A record

The page build completed successfully, but returned the following warning for the gh-pages branch:
Your site's DNS settings are using a custom subdomain, docs.modcluster.io, that's set up as an A record. We recommend you change this to a CNAME record pointing at modcluster.github.io. For more information, see https://help.github.com/articles/using-a-custom-domain-with-github-pages/.
For information on troubleshooting Jekyll see:
https://help.github.com/articles/troubleshooting-jekyll-builds
If you have any questions you can contact us by replying to this email.

@rhusar The registrator's web app works again so I changed that:
- docs.modcluster.io.    A        <IP_ADDRESS>
+ docs.modcluster.io.    CNAME    modcluster.github.io

:crossed_fingers:

I ll testibthe morning.

Works.
$ dig docs.modcluster.io

docs.modcluster.io.	3586	IN	CNAME	modcluster.github.io.
modcluster.github.io.	3586	IN	A	<IP_ADDRESS>
modcluster.github.io.	3586	IN	A	<IP_ADDRESS>
modcluster.github.io.	3586	IN	A	<IP_ADDRESS>
modcluster.github.io.	3586	IN	A	<IP_ADDRESS>


Fix indentation of groups yaml example

Why:
When I saw this example, I assumed this meant you could have groups defined outside of updates to apply to all package types. Doing so, however, causes the dependabot file check to fail with the following error:

Your .github/dependabot.yml contained invalid details
Dependabot encountered the following error when parsing your .github/dependabot.yml:
The property '#/' contains additional properties ["groups"] outside of the schema when none are allowed

Please update the config file to conform with Dependabot's specification.

Closes #27987
What's being changed (if available, include any code snippets, screenshots, or gifs):

This example shows groups at the top level of a dependabot.yml. This PR corrects it to have the groups indented within the npm updates settings since it otherwise fails.
# `dependabot.yml` file using the `update-types` option to group updates.
# Any packages matching the pattern @angular* where the highest resolvable
# version is minor or patch will be grouped together.
version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
groups:
  angular:
    patterns:
    - "@angular*"
    update-types:
    - "minor"
    - "patch"

# `dependabot.yml` file using the `update-types` option to group updates.
# Any packages matching the pattern @angular* where the highest resolvable
# version is minor or patch will be grouped together.
version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      angular:
        patterns:
        - "@angular*"
        update-types:
        - "minor"
        - "patch"

Relevent docs links:

Live - https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#groups
Preview deployment - https://docs-28056-0123c9.preview.ghdocs.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#groups

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@DenverCoder1 Thanks so much for submitting a PR! I'll get this triaged for review :zap:

ATM.NET

HOME


Bold & Italics in MarkDown Editor?

I'm wondering if there is a way to get the MD editor to display bold & italics in, respectively, heavier font-weight and slanted font-style -- like, say TextMate? I simply don't recall, from before installing this plugin, whether this is something Joplin's MD editor even does in the first place.

Hi @MrPoetry , take a look at this Rich Markdown-plugin. With Tools -> Options -> Rich Markdown -> Add additional CSS classes for enhanced customization with some user styles you should be able to make this work. The Extra CSS-part in the README has info about the classnames you can target.
If you need any help, drop a line!

I installed Rich Markdown, which seemed to have no option for MD-editor display of bold & italics, so I opened an issue on that plugin's github page, asking if I was missing something. Here is that dev's reply:

Am I missing something?

Just that italics and bold styling is not a feature of this plugin. That's actually a feature of the base application (below is a screenshot from a clean version of Joplin without any plugins).

The macos-native-theme plugin overrides the Joplin css. You'll need to ask that plugin developer to add the styles you want back in…. [emphasis added by me]

I'm not sure how to approach the issue now. In case it's playing a role in the problem, I do use a userchrome.css, which only consists of:
.ace_content {
font-size: 20px;
/* changes the font size of the ACE editor body text */
}
span[role="presentation"] {
font-size: 20px;
/* changes the font colour for the editor text */
}
Do you have any thoughts about what might be going on?

NEVER MIND: Ignore previous comment! Suddenly bold and italics are rendering in the MD editor. I swear it wasn't working an hour ago.

@MrPoetry Ha no worries! Glad to hear it's working. 👍


Instrument AWS Swift Modules

[x] Remove dependency on aws-sdk-swift
[ ] Instrument AWS Swift Modules

[ ] extend HTTP client API to pass BaggageContext?
[ ] extend their API to pass BaggageContext?

[ ] Update AWSXRaySDKExampleAWS

see proof of the concept HTTP client https://github.com/slashmo/gsoc-swift-tracing/issues/95 created as part of https://github.com/pokryfka/aws-xray-sdk-swift/pull/16

PoC here https://github.com/swift-aws/aws-sdk-swift-core/pull/348
uses AHC https://github.com/swift-server/async-http-client/pull/289
will need to wait for swift-tracing to be released


get 50% “Bad Gateway” http responses in kubernetes

docker version:17.09.0
system version: CentOS Linux release 7.2.1511 (Core)
kubernetes version : 1.6.2
traefik version: v1.4.1
What did you do?
when I run command "while true; do curl test.traefik.io ; done"
What did you see ?
<!DOCTYPE html>

<title>Welcome to node1!</title>

Welcome to node1

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Bad Gateway

<!DOCTYPE html>

<title>Welcome to node1!</title>

Welcome to node1

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Bad Gateway

<!DOCTYPE html>

<title>Welcome to node1!</title>

Welcome to node1

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Bad Gateway

For the client , I have 50% “200” http responses, 50% “Bad Gateway” http responses.
what is problem?

Thanks for your interest in Traefik !
Every question asked in issues means less features 😉.
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following:

Stack Overflow using the "traefik" tag
the Traefik community Slack channel

sorry,I do not understand what you say. you mean this is a bug and it had reporting to you?

@samlyhuang what @ldez is saying is that this is probably rather a user / configuration problem than a bug in Traefik. We encourage people to join us on Slack or open questions on StackOverflow for user-related problems and reserve the issue tracker for feature requests and clear defect reports.
Thanks for your  understanding.


az group list broken

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az group list
Errors:
CLIInternalError: The command failed with an unexpected error. Here is the traceback:
cannot import name 'raise_subdivision_deployment_error' from 'azure.cli.core.commands.arm' (/usr/lib/python3/dist-packages/azure/cli/core/commands/arm.py)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 558, in execute
    self.commands_loader.load_arguments(command)
  File "/usr/lib/python3/dist-packages/azure/cli/core/__init__.py", line 480, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 315, in load_arguments
    super(AzCliCommand, self).load_arguments()
  File "/usr/lib/python3/dist-packages/knack/commands.py", line 106, in load_arguments
    cmd_args = self.arguments_loader()
  File "/usr/lib/python3/dist-packages/azure/cli/core/__init__.py", line 789, in default_arguments_loader
    op = handler or self.get_op_handler(operation, operation_group=kwargs.get('operation_group'))
  File "/usr/lib/python3/dist-packages/azure/cli/core/__init__.py", line 829, in get_op_handler
    op = import_module(mod_to_import)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/azure/cli/command_modules/resource/custom.py", line 31, in <module>
    from azure.cli.core.commands.arm import raise_subdivision_deployment_error
ImportError: cannot import name 'raise_subdivision_deployment_error' from 'azure.cli.core.commands.arm' (/usr/lib/python3/dist-packages/azure/cli/core/commands/arm.py)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az group list

Expected Behavior
Environment Summary
Linux-5.9.0-kali1-amd64-x86_64-with-glibc2.31, Kali GNU/Linux Rolling
Python 3.9.1
Installer: DEB

azure-cli 2.18.0 *

Extensions:
azure-devops 0.19.0

Additional Context

This is a legacy issue of CLI in the old version 2.18.0. This issue in the latest version of CLI should have been resolved. You can use az upgrade --y to update CLI to the latest version, then please have a try again


Clean up warnings in tests

Current coverage is 79.10%

Merging #232 into master will increase coverage by +0.18% as of 143b224

Powered by Codecov. Updated on successful CI builds.


bug: typed-enum is incorrectly returning warnings about type

For this doc: https://raw.githubusercontent.com/speakeasy-api/openapi-directory/main/APIs/twitter.com/current/2.21/openapi.yaml
It has an enum at line 1563 that looks like:
enum:
  - media_key
  - duration_ms
  - height
  - preview_image_url
  - type
  - url
  - width
  - public_metrics
  - non_public_metrics
  - organic_metrics
  - promoted_metrics
  - alt_text
type: string

which produces the below errors complaining about "string" defined as "type"
(1563:13)     | warning  | enum type mismatch: enum value 'height' is a string, but it's defined as a 'type'                 | $
(1563:13)     | warning  | enum type mismatch: enum value 'duration_ms' is a string, but it's defined as a 'type'            | $
(1563:13)     | warning  | enum type mismatch: enum value 'type' is a string, but it's defined as a 'type'                   | $
(1563:13)     | warning  | enum type mismatch: enum value 'public_metrics' is a string, but it's defined as a 'type'         | $
(1563:13)     | warning  | enum type mismatch: enum value 'url' is a string, but it's defined as a 'type'                    | $
(1563:13)     | warning  | enum type mismatch: enum value 'promoted_metrics' is a string, but it's defined as a 'type'       | $
(1563:13)     | warning  | enum type mismatch: enum value 'preview_image_url' is a string, but it's defined as a 'type'      | $
(1563:13)     | warning  | enum type mismatch: enum value 'alt_text' is a string, but it's defined as a 'type'               | $
(1563:13)     | warning  | enum type mismatch: enum value 'media_key' is a string, but it's defined as a 'type'              | $
(1563:13)     | warning  | enum type mismatch: enum value 'organic_metrics' is a string, but it's defined as a 'type'        | $
(1563:13)     | warning  | enum type mismatch: enum value 'width' is a string, but it's defined as a 'type'                  | $
(1563:13)     | warning  | enum type mismatch: enum value 'non_public_metrics' is a string, but it's defined as a 'type'     | $

Interesting! working on a fix.

This should be fixed in v0.0.44

can confirm it is fixed


Remove App.js Filename

Similar to #169, the codebase has many App.js filenames. This can become confusing when it comes to importing the files.
examples: [here](https://github.com/SCE-Development/Core-v4/blob/dev/src/Pages/3DPrinting/app3DPrintForm.js, here and here
Find and replace all filenames. A good new name can be derived from the class in the file or the name of the directory that the file is in.

@nanarboursal before I close this, can you also rename app3DPrintForm.js and app3DPrintForm.css?

Closed by #185 and #205


Allow selected ApprovedInvoices to be printed

The frontend needs to be able to render selected invoices and trigger print. This gets interesting with multiple documents since you need to deal with page breaks.

Going to deal with this by returning a pdf from backend instead.


Improvement suggestion for sel

If I have a xarray DataArray, that has x-coordinates in descending order, and I try to crop the DataArray using
da.sel(x=slice(10,50)), it gives me empty DataArray. If I use
da.sel(x=slice(50,10)), it finds everything it is supposed to find.
I think it would be useful to be able to use this feature without knowing the exact order of the DataArray. Is this intentional?

This was actually intentional, though you are certainly not the first person to complain about this.
Xarray's behavior mirrors pandas. The justification for this logic is that sel/loc would work like normal indexing [] on a Python list, and if you supply slice limits in the opposite order on a Python list, you get an empty result.
Probably the cleanest solution possible would be a separate selection object for xarray that doesn't care about order, e.g., da.sel(x=xarray.Between(10, 50)).

The justification for this logic is that sel/loc would work like normal indexing [] on a Python list, and if you supply slice limits in the opposite order on a Python list, you get an empty result.

Given that sel is label/value-based, I don't see how the analogy with positional list-based indexing applies. This behavior looks like a functional bug. If you have decided to keep it as is, I'd suggest at the very least to add a warning if an empty dataset is returned because values in an attribute are ordered high...low.

To clarify: xarray behavior doesn't just mirror pandas here -- it actually directly uses pandas to figure out the mapping from labeled slices to integer slices.
So I'm not opposed to changing this (I agree this trips people up often) but we should try to change it upstream if possible.

Ah okay, that makes sense. I'm sure there's a related pandas issue (or many), will try to find that later.

The only related issues I can find are:

https://github.com/pandas-dev/pandas/issues/14316
https://github.com/pandas-dev/pandas/issues/7860

They don't look identical though. Don't really have the time to dive into that further now.

In case it helps anyone else, I ended up doing:
    # Note that xarray is fiddly with indexing - if x or y values are ordered
    # high to low, then the slice bounds need to be reversed.  So check that
    x_ordered_low2high = data.x.values[-1] - data.x.values[0] > 0
    y_ordered_low2high = data.y.values[-1] - data.y.values[0] > 0

    if x_ordered_low2high:
        x_index = slice(lower_lon, upper_lon)
    else:
        x_index = slice(upper_lon, lower_lon)

    if y_ordered_low2high:
        y_index = slice(lower_lat, upper_lat)
    else:
        y_index = slice(upper_lat, lower_lat)

    subset = data.sel(x=x_index, y=y_index)

Consider using index.is_monotonic_ascending and index.is_monotonic_descending instead of subtracting the first few values -- those are exactly the checks that pandas uses.
I also did a little more searching and found that this has come up in the xarray issue tracker before: https://github.com/pydata/xarray/issues/1465

Thinking about this a little more, I'm remembering the reasoning for pandas working this way:

Integer slicing by position and by label with positive integers should work the same for an index with values given by range(N).
Positional indexing in Python x[a:b] returns all values between a and b in order. Indexing like x[high:low] with high > low returns an empty list.
Label based indexing in pandas has df.loc[df.index[i] : df.index[j]] equivalent to df.iloc[i : j+1] (arguably this is a mistake; e.g., https://github.com/pydata/xarray/issues/1492 and other discussion that I can't find right now :) ).
Indexing a monotonic decreasing index therefore should work for decreasing labels.
If slicing a monotonic increasing index only works for increasing but not decreasing labels, then it would be weird if indexing a monotonic decreasing index works for both increasing and decreasing labels.

Consider using index.is_monotonic_ascending and index.is_monotonic_descending instead of subtracting the first few values -- those are exactly the checks that pandas uses.

Thanks, that's nicer, will do. And thanks for digging up the background/rationales.

(1)Integer slicing by position and by label with positive integers should work the same for an index with values given by range(N).

This I don't think I agree with. Slicing by position and by label are semantically very different operations.
(2) is correct, but irrelevant to label-based indexing.
(3) yes, agree that's a mistake
(4) indeed
(5) I'd say that it's in practice less important, because users normally won't do slice(high, low), but for consistency I agree that there should be symmetry in behaviour. Making slice(high, low) return the same as slice(low, high) on a monotonic increasing index seems reasonable.
Additionally: arguably monotonicity should not be required. When one uses labels, the semantics are clear without monotonicity. This doesn't have a position-based equivalent.

Additionally: arguably monotonicity should not be required. When one uses labels, the semantics are clear without monotonicity.

Requiring monotonicity lets us guarantee that the result is a NumPy view rather than possibly being a copy.

Requiring monotonicity lets us guarantee that the result is a NumPy view rather than possibly being a copy.

Sure, but if a users happens to have non-monotonic data it just requires her to then make that copy first anyway. Still a good thing overall for performance, but there'll be cases where it's just an extra thing to understand for the user without any performance gain.
Anyway, the non-monotonic case is less relevant, because it's harder to run into in practice. The decreasing case however is easy - there is standard geo software (looking at you ArcGIS) that can write geoTiff's with monotonic decreasing indices. That's how I ran into this. Rewriting multi-GB source data that I didn't produce is not an option, so I'm left with the manual monotonicity checks and juggling label-based slices.

there is standard geo software (looking at you ArcGIS) that can write geoTiff's with monotonic decreasing indices

This is very frequent for climate models also (lat arrays are frequently upside down). An xarray (or upstream) solution would be very useful indeed, but possibly there are other things to consider, like being "too magical".
xarray makes a very good job at handling decreasing coordinates (i.e. when plotting), but soon or late users might need to know how they data is ordered, and indexing might be the right time to warn them about it when they do something wrong: usually an empty array is unlikely to be left unnoticed, so that the current behavior might help to find bugs in user code.

Making slice(high, low) return the same as slice(low, high) on a monotonic increasing index seems reasonable.

Agreed, I don't think many pandas users would object to this.

This is probably worth fixing if possible in a straightforward way. I don't think anyone is well served by matching the behavior of Python list indexing here -- it's a strange edge that case that indexing a list like x[5:0] returns an empty list.

What would be a good solution?

Make sel implicitly ignore order  for slice objects.
Add a option to sel for explicitly ignoring slice order.

add a new kwarg
Add a new xr.Between object

How about: add one code line at the top of slice that properly orders the exactly two arguments (in other words, reverses the order if necessary).

One complication with using sel() with slice objects is that you can do selection over non-monotonic indexes, merely based on matching bounds:
>>> data = xarray.DataArray([1, 2, 3, 4, 5], dims=['x'], coords=[[5, 1, 4, 3, 2]])
>>> data
<xarray.DataArray (x: 5)>
array([1, 2, 3, 4, 5])
Coordinates:
  * x        (x) int64 5 1 4 3 2
>>> data.sel(x=slice(1, 3)))
<xarray.DataArray (x: 3)>
array([2, 3, 4])
Coordinates:
  * x        (x) int64 1 4 3

If we change the semantics of slice in sel() to do filtering rather than be concerned about order (which does seem much less useful), we should probably deprecate the handling of non-monotonic ascending or descending indexes.
Alternatively, we could either do the dedicated indexing object like xarray.Between(lower, upper) or have a dedicated method for selecting between values, e.g.,  perhaps data.sel_between(x=(1, 3)) or data.sel_bounds(x=(1, 3)).

@shoyer, selection over non-monotonic indexes, merely based on matching bounds is a case I never considered... probably a rare one, which I for one would happily sacrifice.
New syntax like your first suggestion, .Between instead of .slice if I understand correctly, could be appealing too:  The word 'slice' has never seemed terribly intuitive to this user, and 'between' is high in an alphabetical list of tips/suggestions a good IDE might bring up with the tab key or whatever.

How about an informative warning when returning an empty set, as a minimal change? What's the path to an action item here?

Agreed, new rather than redefine existing meanings.
Who has the chops and the cred to implement it? Not quite me...

Alternatively, we could either do the dedicated indexing object like xarray.Between(lower, upper) or have a dedicated method for selecting between values, e.g., perhaps data.sel_between(x=(1, 3)) or data.sel_bounds(x=(1, 3)).

xref #7099 about generic API for indexing objects.


Claims - printingLocation

    printingLocation:
      description: Printing place information
      type: object
      properties:
        id:
          type: integer
        name:
          type: string

What is this? What purpose does this have? How is this to be used? This is only relevant for those banks which use RB for printing so remove or make optional.

Skv. RB
Sjá https://github.com/stadlar/IST-FUT-FMTH/blob/master/Vinnusvæði/Verkþáttur 4/Examples/claimTemplateDetail.xml


Cannot create repo, validation of git repo url does not pass

Browser: Chrome 46.0.2490.86
dogpro version: 8b45cad82d5a3913d41c2fd7827eac03ba05c1df
Tried:

ssh://git@bitbucket.org:mn7z/demo.git
git@bitbucket.org:mn7z/demo.git
git@github.com:dogdep/dogpro.git

Getting Please match the requested format
I have actually been able to enter the value ssh:/.git as a valid one.
The format (?:git|ssh|https?|git@[\w\.]+):(?:\/\/)?[\w\.@:\/~_-]+\.git\/? which can be found at public/templates/repo seems working great while testing in regex online, however the browser renders the field:
<input class="form-control ng-dirty ng-valid-parse ng-valid-required ng-touched ng-valid ng-valid-pattern"     type="text"   id="url" placeholder="GIT URL..." ng-model="repo.url" required="" title="This must be a valid GIT URL" pattern="(?:git|ssh|https?|git@[w.]+):(?://)?[w.@:/~_-]+.git/?">

Check removed completely in 5a8e060ea3aa856b3d7d3015e087c548c9021c1e


[FIXED - Implemented][Feature Request] Add 51 Miss Fail [FIXED] [BUG] Default fail type are not saved properly [Pump] [Infinitesimal]

Game Mode
pump
Give an example of what is wrong
I am running <IP_ADDRESS> with Pump mode and the theme Infinitesimal
"Default Fail Type" settings are not working properly.
For instance, setting it to off, should result in a pass, even if the lifebar has been depleted
Give an example of what it should look like
This might be contested, but IMO the options should work like this
Immediate should fail and quit back to eval when life bar depletes
Delayed should fail and quit back to to eval after 51 miss combo
End Of Song should result in a fail at the end of the song, if the life bar was depleted at any point in the song.
Off should make it impossible for a fail to happen

These are implemented and solved in Alpha V. A backport is not possible, so I've moved this as solved due to the new fixes we've done working with the pump bros these past few weeks. :)

fixed in 042


Large notebook trigger very many leak warnings

Testing #210961
slow.ipynb.txt

open dev tools console
open the notebook from above
😱 notice leak warnings from various places

This is critical: REFUSES to accept new listeners because it exceeded its threshold by far because it means a listener will never be used, meaning a feature is likely not working.
This seems to be a widespread misconception and it seems each cell listens by itself. So, more cells,  more listener, leak warning and refusal to accept more listeners. Generally, listener should be used sparingly, e.g instead of each cell being a listener there should be one per notebook which dispatches onto cell.

One such case is for the new cellDiagnostics that I added (off by default).
https://insiders.vscode.dev/github/microsoft/vscode/blob/aamunger/focusEditor/src/vs/workbench/contrib/notebook/browser/contrib/cellDiagnostics/cellDiagnostics.ts#L62

need to check if these are still happening, I think I've taken care of most cases

Just came across the notebook and there is still plenty of leak. Just scrolling in the notebook prints tons for leak warnings. This issue should really be prioritised because it can slow down all of vscode. Also, note that there is much related error telemetry like https://github.com/microsoft/vscode/issues/226057

I think we can see if this is the same as https://github.com/microsoft/vscode/issues/211105 which renders too many toolbars.


Be smart about changes to OWNERS files

The bot could be smart about changing OWNERS files and request review from those added/removed.
Example:  https://github.com/w3c/web-platform-tests/pull/10508#issuecomment-382043566

This would become a security vulnerability if ever there was a merge bot added to the project.

I think we can remove the OWNERS code from the bot when the lint has landed. This issue is also sort of moot now that almost everything has OWNERS.

Forgot about this issue and filed https://github.com/web-platform-tests/wpt-pr-bot/issues/32
@tobie so, we'd need to exclude review requests from bot accounts?


Implement QpsWorker for Python

go/grpc-performance-testing-setup

CC @vjpai

Anything new?

@nathanielmanistaatgoogle
I'm taking a look at this.  I'm working on creating a worker for a SYNC server/client to begin with.

@kpayson64 I really need this.

@hsaliak is working on this but I don't know the eta

First Pass of the python qps worker in #6208

QPS Tests merged.


I can user in my project without a licence?

I can user in my project without a licence?

No, in order to use the editor you would have to purchase a license.


Automate process for converting mp3 to proper file

r @sandlerben @roornelas
-Given a file name, creates a new file with the proper audio format for transcription
Question: should the function be taking in a string file name or a path/something else?

TODO: I have ffmpeg, but need to figure out how ppl in project can use

I'll give this a look after Rodrigo

Looks good to me

Was having this problem for a while, tried looking up but not sure how to resolve:

Looks like complaints went away when I ran go get github.com/qur/withmock/mocktest, can you remind me how to add that to /vendor instead of only to /Godeps?

Also: make test didn't start to work until I ran go get github.com/qur/withmock/mocktest, can you remind me how to add that library to /vendor?

That makes sense. I'll make sure that installing mocktest is included in the README.
You can add libraries to vendor with godep save ./....

@sandlerben how does this look?

@yoninachmany can you make a new PR off of master? I'll give it a final look and then you can merge.


Sampling values directly on GPU, instead of copying from CPU to GPU. …

…7 times faster.

Hi @sarahdoerr
Makes sense. I am incorporating these changes and will test. Thanks.


Feature Request - request confirmation when deleting Notification Hubs/Service Buses etc

Would it be possible to have request confirmation when deleting Notification Hubs, or Queues, Topics, Service Buses etc?
A simple "Are you sure? Okay/Cancel" would be great.

You can do this by checking the following check box in the Options dialog window.

Thanks

We have not for the 3rd time (by a mistake) deleted a queue that was in production. Would it make sense to introduce a field that you need to type in the queue / topic name, when deleting it?


lf/issue-49  compare all columns macro for testing

Description & motivation
This PR creates a macro compare_all_columns which can be included in a dbt test suite to test whether any values in any columns have changed.
The output of compare_all_columns allows for various testing configurations, including but not limited to:

Flagging only direct conflicts as test failures.
Ignoring very recent values.
Filtering and grouping of test results based on model attributes.

issue this PR is meant to address: https://github.com/dbt-labs/dbt-audit-helper/issues/49
Checklist

[x] I have verified that these changes work locally
[x] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)

I've run into this error when trying to build a test for compare_all_columns. It's not surprising to me that dbt won't allow me to have two seeds with the same name. However, this would be a perfect solution for what I'm trying to test: comparing the same table between two targets (dev and prod). Is there a recommended approach for this kind of thing?
dbt.exceptions.CompilationException: Compilation Error
  dbt found two seeds with the name "data_compare_relations__a_relation".

  Since these resources have the same name, dbt will be unable to find the correct resource
  when looking for ref("data_compare_relations__a_relation").

  To fix this, change the name of one of these resources:
  - seed.audit_helper_integration_tests.data_compare_relations__a_relation (seeds/prod_schema/data_compare_relations__a_relation.csv)
  - seed.audit_helper_integration_tests.data_compare_relations__a_relation (seeds/data_compare_relations__a_relation.csv)
13:38:31  Encountered an error:
Compilation Error
  dbt found two seeds with the name "data_compare_relations__a_relation".

  Since these resources have the same name, dbt will be unable to find the correct resource
  when looking for ref("data_compare_relations__a_relation").

  To fix this, change the name of one of these resources:
  - seed.audit_helper_integration_tests.data_compare_relations__a_relation (seeds/prod_schema/data_compare_relations__a_relation.csv)
  - seed.audit_helper_integration_tests.data_compare_relations__a_relation (seeds/data_compare_relations__a_relation.csv)

Exited with code exit status 2

Need to update README to explain additional arguments: exclude_columns, updated_at_column, exclude_recent_hours, direct_conflicts_only.
{{
  audit_helper.compare_all_columns(
    model_name='stg_vendr__deals',
    primary_key='id',
    prod_schema='warehouse',
    exclude_columns=['updated_at'],
    updated_at_column='updated_at',
    exclude_recent_hours=2,
    direct_conflicts_only=true
  )
}}

@joellabes I think I've addressed everything you raised--would appreciate another look when you have a chance! I held off on additional attempts at test-writing until the proposed code has hardened somewhat.

Without looking at the code itself, it looks like the CI tests are failing - can you access Circle CI? I had mixed success when outside of the Labs organisation, but it looks like it's public (I could get in from incognito).
If you can't, the error is

00:49:16  Running with dbt=1.3.0-b1
00:49:16  Installing ../
00:49:16    Installed from <local @ ../>
00:49:16  Installing dbt-labs/dbt_utils
00:49:16    Installed from version 0.8.6
00:49:16    Up to date!
00:49:19  Running with dbt=1.3.0-b1
00:49:19  Partial parse save file not found. Starting full parse.
00:49:20  Encountered an error:
Compilation Error in model compare_relations_with_exclude (models/compare_relations_with_exclude.sql)
  The name argument to ref() must be a string, got <class 'dbt.adapters.postgres.relation.PostgresRelation'>

which looks like you're passing in a whole ref instead of the name of the ref.
Will probably have a look at the rest of the code early next week!

I think the tests are failing because of this! Tomorrow a.m. (PST) I'll remove the offending test, see if I can get CI to pass, and then we can revisit what tests should be written and how to go about that. Thanks!

@joellabes scratch my comment above, that's a new issue that I hadn't noticed, I'll look tomorrow morning!

@joellabes tests passing! 🥳 see the hacky workaround for bigquery ... maybe there's a better approach, I can look into that

wondering why you're still collecting the prod schema and model name instead of

@joellabes honestly, I think I was having a mental block on why this wouldn't work just fine. I've made the update!

got one strange test error to sort out and a few more tests / error states to write.


Fix package name & instructions

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues
#5

Fixed the package name & updated instructions.
Closes #5

Thank you!


HCRC-78 | Article carousel show all links

Description
Implemented showAllLink fetching from the CMS for article carousels. Event carousels don't have show all links at least for now.
Also updated README about yarn generate:graphql not working with Node.js v16 or greater.
Issues
Closes
HCRC-78: As a content manager I can add a show all -link in the carousel

Please set a new version number and make a release with yarn publish-stable


iOS:   APIError: The HTTP response status code is [401].

Describe the bug
I am getting 401 API error when I try to fetch data. Can anybody help me with this issue or guide me the right way to solve this error?
Error:
"APIError: The HTTP response status code is [401].
Recovery suggestion: The metadata associated with the response is contained in the HTTPURLResponse.
For more information on HTTP status codes, take a look at"
Steps To Reproduce
- document : "query ListMessages($limit: Int) {\n  listMessages(limit: $limit) {\n    items {\n      id\n      body\n      createdAt\n      creationDate\n      groupId\n      mediaType\n      poll\n      reaction\n      reply\n      senderId\n      updatedAt\n      __typename\n    }\n    nextToken\n  }\n}"
  ▿ variables : Optional<Dictionary<String, Any>>
    ▿ some : 1 element
      ▿ 0 : 2 elements
        - key : "limit"
        - value : 1000
  - responseType : Swift.Array<NeonatalChat.Message>
  ▿ decodePath : Optional<String>
    - some : "listMessages.items"

Expected behavior
Should get the data
Amplify Framework Version
1.28.3
Amplify Categories
API, DataStore, Storage
Dependency manager
Swift PM
Swift version
5
CLI version
1.28.3
Xcode version
14.2
Relevant log output
<details>
<summary>Log Messages</summary>

INSERT LOG MESSAGES HERE

```
Is this a regression?
Yes
Regression additional context
No response
Device
iPhone 13
iOS Version
16.2
Specific to simulators
No response
Additional context
No response

Hello Guys, It is solved. It was because of my API KEY was expired.


Should #[storage(read)] be required when the bal opcode is used?

Example: Do we need #[storage(read)] added to test_function() given that this_balance() actually reads from storage?
contract;

use std::context::*;

abi MyContract {
    fn test_function() -> bool;
}

impl MyContract for Contract {
    fn test_function() -> bool {
        let x = this_balance(~ContractId::from(0x0000000000000000000000000000000000000000000000000000000000000000));
        true
    }
}

This depends on what specifically storage refers to: just contract storage, or any state?

In the CEI pattern analysis we differentiate between contract storage and balance tree state. I think it would make sense to do the same and require something like #[balance_tree(read)] annotation here.

It might also be a good idea to add analysis for anything non-pure. E.g. calling a contract doesn't touch the current contract's storage or balance (or balance of another contract), assuming no base-asset is sent with the call. But calling a contract makes that function not pure.


ipv6nat stop working after docker update

Hi,
I have got this error since my docker upgrade:
ipv6nat_1              | Try `iptables -h' or 'iptables --help' for more information.
ipv6nat_1              | 2019/05/25 21:20:31 running [/sbin/iptables -t nat -C OUTPUT -m addrtype --dst-type LOCAL -j DOCKER --wait]: exit status 2: iptables v1.6.2: Couldn't load target `DOCKER':No such file or directory

My docker version:
docker version
Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        481bc77
 Built:             Sat May  4 02:36:01 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.6
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       481bc77
  Built:            Sat May  4 01:59:36 2019
  OS/Arch:          linux/amd64
  Experimental:     false

My nat table:
sudo iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination
DOCKER     all  --  anywhere             anywhere             ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE *** (all my rules here)

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
DOCKER     all  --  anywhere            !<IP_ADDRESS>/8          ADDRTYPE match dst-type LOCAL

Chain DOCKER (2 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere
DNAT *** (all my ipv4 dnat here)
# Warning: iptables-legacy tables present, use iptables-legacy to see them

I have disabled ipv6 for now. Can I do something to fix this?
thanks

I'm not sure where those errors come from, ipv6nat runs ip6tables, not iptables. It seems something else is going on here.
 Or did it exit at this time? I'm asking because you're using --cleanup which removes all the rules on exit.
Can you do a docker-compose up -d --force-recreate ipv6nat and after that send me the docker logs?

I have removed the command section and run the recreate:
ipv6nat_1              | 2019/05/26 11:25:07 running [/sbin/iptables -t nat -C OUTPUT -m addrtype --dst-type LOCAL -j DOCKER --wait]: exit status 2: iptables v1.6.2: Couldn't load target `DOCKER':No such file or directory
ipv6nat_1              |
ipv6nat_1              | Try `iptables -h' or 'iptables --help' for more information.

The ipv6nat wasn't running because it fails at the start with that log.

OK, it craps out trying to detect hairpin mode in the IPv4 firewall. Could you try:
docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro --net=host --cap-add=NET_ADMIN --cap-add=SYS_MODULE --entrypoint iptables-save robbertkl/ipv6nat

sudo docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro --net=host --cap-add=NET_ADMIN --cap-add=SYS_MODULE --entrypoint iptables-save robbertkl/ipv6nat
# Generated by iptables-save v1.6.2 on Sun May 26 12:14:56 2019
*nat
:PREROUTING ACCEPT [8392:426047]
:INPUT ACCEPT [2635:96038]
:OUTPUT ACCEPT [3987:318688]
:POSTROUTING ACCEPT [9744:648697]
COMMIT
# Completed on Sun May 26 12:14:56 2019

Can you try the same but with --privileged instead?
docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro --net=host --privileged --entrypoint iptables-save robbertkl/ipv6nat

The output is empty.
When I run docker-ipv6nat again:
/ # ./docker-ipv6nat
2019/05/26 15:50:19 running [/sbin/iptables -t nat -C OUTPUT -m addrtype --dst-type LOCAL -j DOCKER --wait]: exit status 2: iptables v1.6.2: Couldn't load target `DOCKER':No such file or directory

So when you're running iptables-save from within a privileged, net=host ipv6nat container it shows no IPv4 rules, but when you run iptables-save on the host it does show IPv4 rules?
I've just tried the same on a test host running Docker 19.03.0-beta3, and I still see the IPv4 rules from within the container, so no way to reproduce it on my end.

Sorry I run the ip6tables command.
Here the output:
# Generated by iptables-save v1.6.2 on Sun May 26 16:20:42 2019
*nat
:PREROUTING ACCEPT [3580:160229]
:INPUT ACCEPT [562:19464]
:OUTPUT ACCEPT [792:64734]
:POSTROUTING ACCEPT [1927:130179]
COMMIT
# Completed on Sun May 26 16:20:42 2019
# Generated by iptables-save v1.6.2 on Sun May 26 16:20:42 2019
*filter
:INPUT ACCEPT [3180:338688]
:FORWARD ACCEPT [50554:39971344]
:OUTPUT ACCEPT [3327:460405]
COMMIT
# Completed on Sun May 26 16:20:42 2019

Sorry, I'm a bit confused, this output is different than before again. Can you please post all 3 outputs:

iptables-save (on the host)
docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro --net=host --cap-add=NET_ADMIN --cap-add=SYS_MODULE --entrypoint iptables-save robbertkl/ipv6nat
docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock:ro -v /lib/modules:/lib/modules:ro --net=host --privileged --entrypoint iptables-save robbertkl/ipv6nat

All commands use iptables, not ip6tables. The problem is your ipv6nat instance seems not to see the IPv4 rules, even though they're available on the host. I cannot reproduce this myself, however.

Despite my provider give me only a /128 block, it seems I can have a /64 block anyway.
They are not limiting the ipv6 assignation on my /64 block.
I have reconfigured my docker to handle ipv6 block /80.
All my containers have a public IP address now, and it seems to connect to the host with ipv6 on a container port (SMTP for example) redirect properly but in a weird way.
HOST ipv6 -> Host docker ipv4 -> Container IPV4
Also, an issue is that they are no ipv6 isolation of the container. If I have a port listing (80) on a container but I don't open it on the host (don't have the "ports"), I can't reach it with ipv4, but I can with ipv6.
Also, ports redirect doesn't work well: ports: 2222:22, give ipv4: 2222, ipv6: 22
The ipv6 nat is far easier to configure.
Here the output I have (sorry for the change):
1.
 I will disable ipv6 on my host. It is not really useful.
If that evolves, I may reenable it.
Or I may look out for an alternative.

 However, I've been running it with ipv6nat for years without any issues. Not sure what your issue is; your container not being able to reach the (IPv4) firewall rules seems to be the cause of ipv6nat crashing, but why this is happening I don't know. Are you by any chance using SELinux? I can't reproduce it myself, so it's hard to debug.

I'm on debian/buster, the latest kernel on this system.
I also have the latest (non-beta) version of docker/docker-compose.
It seems to hide iptables rules indeed inside the container which cause the issue here.

Yeah, I'm curious to know what's causing it. Even on 19.03.0-beta3 I could not reproduce it, so it must not be a Docker thing. Perhaps it's something kernel-related.

Can you test it with debian/buster ?

Maybe it would be possible and safer to run your companion on the host directly? Something like a service that starts with docker?

The kernel:
Linux ns363135 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux

Running on the host is a great idea, that should work since it should be able to access the firewall there.
I'll try to do some tests with buster / later kernels soon.

OK @celogeek, just did 2 clean Debian VM installs (1 stretch @ 4.9.0-9, 1 buster @ 4.19.0-5) and installed Docker stable (18.09.6).
Then tried reading iptables from within a (privileged, net=host) container on both:

on stretch it worked
on buster it did not (no rules)

It seems the problem is buster using nftables (see https://wiki.debian.org/nftables). I managed to get it working by switching to legacy version by running:
update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
update-alternatives --set arptables /usr/sbin/arptables-legacy
update-alternatives --set ebtables /usr/sbin/ebtables-legacy
reboot

After the reboot, I can see the rules from inside the container again.

Nice catch!
Did you try directly on the host? without a container?

Yes, you can either switch to legacy iptables like above, or run ipv6nat directly on the host. On the host it will use the iptables/ip6tables commands that are linked to the special nftables compatibility versions.
This same approach would also work from within the container (auto translating iptables to nftables), so I'm working on a fix for the Docker image to support this. I just need to figure out how to reliably detect which is used. After I'm done with this fix, you should be able to run it again as a container, without any changes.

Hi @celogeek , just released a new version of the docker images with support for nftables, so it should work again with your previous setup, unchanged. Could you test this?

Yes of course.
I will need to reactivate ipv6 on my server.
I do that as soon as possible.
I guess you have try in debian/buster/nfptables condition ?

Yep, tried it and as far as I could see it starts just fine.

test done
it doesn't work.
here the error I got:
ipv6nat_1              | 2019/05/28 18:50:57 running [/usr/local/bin/ip6tables -t filter -I DOCKER 1 -d fd00:dead:beef::2 ! -i br-f016aef740c8 -o br-f016aef740c8 -p tcp -m tcp --dport 22 -j ACCEPT --wait]: exit status 1: iptables: Invalid argument. Run `dmesg' for more information.

in dmesg:
[  557.022382] x_tables: ip6_tables: tcp match: only valid for protocol 6

Yeah, I'm seeing this same error now. Seems like a bug in the compat scripts, because we're obviously using protocol 6. Doing an ip6tables-translate did not generate an error.
You're right about ip6tables-nft, this is what I wanted to use, however I'm using Alpine Linux as a base image and their iptables is running behind.

Wait, this is great, there's a Alpine ip6tables 1.8.2-r1 package in edge now, built just YESTERDAY 😄
I'll go check it out.

I got a bit further by using 1.8.1-r1 and ip6tables-nft, but now I ran into an issue with go-iptables, I reported it here: https://github.com/coreos/go-iptables/issues/59
There's not really a workaround with the current version, so I'll fix the issue to get it working. Should be done soon, I'll let you know. I'll reopen this issue.

@celogeek Could you please test again with the latest release? Thanks!

yes sure. testing it right now.

It works !!! congrat.
Everything is back to normal now.
I will take a vps with ipv6 connectivity and play with real ipv6 config (no nat).
It seems to be not so easy to do a firewall with docker / ufw / ipv6.
This would be a good challenge ;)
A very great companion for docker would be something like this tools, that disable incoming connection and redirect port to the one inside but with real ipv6 ip addr.
As I said before if I have a real ipv6 on a docker, it is accessible directly without following the rules of dockers (port open/close or redirected).

Good to hear it's working! I'll close the issue now.


what is the validation set?

In formula_detection.py, the annotation file is under Ts01, but the images are under Tr01. Also, the training set contains Va00, Va01. Shouldn't they belong to the validation set?
    val=dict(
        type=dataset_type,
        ann_file=data_root + 'Ts01/train_coco_sdk4.json',
        img_prefix=data_root + 'Tr01/img/',
        classes=classes,
        pipeline=test_pipeline),
    test=dict(
        type=dataset_type,
        ann_file=data_root + 'Ts10/train_coco_sdk4.json',
        img_prefix=data_root + 'Tr10/img/',
        classes=classes,
        pipeline=test_pipeline))

Hi @cpwan , I'm sorry for my carelessness. Images must be as same as their annotations, 'Tr' should change to 'Ts' here, and the latest code has been fixed this error.
This config is my final version which gets the result of the unlabeled data Ts10. If you only want to reimplement the result on README.md quickly, train on Tr00, Tr01, Va00 and Va01, validate on Ts00, and test on Ts01.


+[PFConfig currentConfig] warning on long-running operation is being executed on the main thread

Hey Parsers!
In my app, I'm calling +[PFConfig currentConfig], expecting to get the currentConfig. I received the warning long-running operation is being executed on the main thread, and when adding the symbolic breakpoint, I got the following:

What is strange is, that I call getConfigInBackgroundWithBlock, and in the completion block, other method tries to access currentConfig, triggering the warning.
My question is: is it ok to ask for the currentConfig in the main thread, right? If so, why am I getting the warning? If not, what am I doing wrong?

Yes, it's absolutely fine, this warning is actually coming from Bolts.framework which warns you that you are executing PFConfig.currentConfig() on the main thread. This operation is basically free if you currentConfig was loaded into memory, otherwise it might be slightly expensive (based on the size of your config).
It's strange that you see this warning, since it should have been fixed in v1.8.0.
Any chance you can confirm the version of the SDK that you are using?

Oh, good to hear.
I'm using the one earlier than 1.8.0, due to the localization bug in 1.8.0. So I'll just update to 1.8.0 using pointing to Master here in my Podfile (or when is 1.8.1 being released?)

BTW, is there any place (or twitter feed) where we can be notified of new SDK versions?

You can start watching the repo on GitHub - it will notify you (I hope).
Our official Twitter is @parseit, but so far we didn't announce new releases, but there have been talks to actually do it, so I think it's definetly coming now.

I guess that watching will notify me about more than only releases, no?
That will be great to have on Twitter, even if in a new Twitter account just for that.


Old pip version is still present

Although pip 8.1.2 is installed in the docker image python:3.5, pip 7.1.2 is still present.
pip 8.1.2 is installed and used:
$ docker run --rm -it python:3.5 pip --version
pip 8.1.2 from /usr/local/lib/python3.5/site-packages (python 3.5)

pip lists an old version of itself as outdated:
$ docker run --rm -it python:3.5 pip list --outdated
pip (7.1.2) - Latest: 8.1.2 [wheel]
setuptools (18.2) - Latest: 23.0.0 [wheel]
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

It sill lies around in site-packages:
$ docker run --rm -it python:3.5 ls /usr/local/lib/python3.5/site-packages/
README	__pycache__  _markerlib  easy_install.py  pip  pip-7.1.2.dist-info  pip-8.1.2.dist-info  pkg_resources	setuptools  setuptools-18.2.dist-info

Regards pypa/pip#3538

Interesting -- I'm not sure this is really pypa/pip#3538, since our official image is built on AUFS (not overlay), and since we do the pip upgrade directly in the same layer that it was originally installed (specifically to avoid issues like this), but I could be mistaken.  Is there a flag we're missing on our pip line to make sure it cleans up older artifacts completely?

I'm not sure this is really pypa/pip#3538

It is, just not because of overlay.

Is there a flag we're missing on our pip line to make sure it cleans up older artifacts completely?

Good idea, it happens due to --ignore-installed
https://github.com/docker-library/python/blob/9383f7d4d2f96068e8957651aa3588fee8b48f71/3.5/Dockerfile#L34
I removed it locally, built the image and ran the commands again.  The errors are gone.

PR docker-library/python#100 fixes this.

I don't remember why we added --ignore-installed :disappointed:
If it currently works without, that sounds great, and we can cross the bridge of why we added it previously if the problem it solved resurfaces. :+1:
Do you know of a simple one-liner we could use to test for the failure case, so that we can embed it directly in the Dockerfile and avoid this issue resurfacing? (it's OK if there's not a simple one -- I'd rather have asked and the answer be "not really" than not have asked at all :smile:)

Here are two tests that work:
RUN test $(ls -1 /usr/local/lib/python3.5/site-packages/ | grep "pip.*dist-info" | wc -l) -eq 1

RUN test $(pip list | grep -o -P '(?<=pip \().*(?=\))') = $PYTHON_PIP_VERSION

I like the second one better.


Can not reproduce the finetuning results of Qwen and Seeclick on Mind2web.

The data format is like:
'Picture 1: /root/data/Mind2Web_related/qwen_image/013781df-4391-4533-bcb1-15f6819064f6-79c4a963-4aa9-49c1-9257-6b0d5069c551.jpg\n
Please generate the next move according to the ui screenshot, instruction and previous actions.
Instruction: What are the romantic reggae musics from BCD Studio that can be used in tik tok series in andorra. Previous actions:'
For images in Mind2web, i tried using the raw size and cropped size(the raw sizes are very large).
I didn't modify the code of finetuning, but the final results are not good. Can you provide me some advices for solving this problem? Thx

Hi,
Did you follow the fine-tuning steps provided in our readme_agent?
I'm not sure about your training script, but in our fine-tuned code (actually the official Qwen-VL code), the path of the image should be surrounded by <img> </img>, as in https://github.com/njucckevin/SeeClick/blob/5067f6bcde12e507cff7dab676b0df6b71d23b79/agent_tasks/mind2web_process.py#L101

I followed the fine-tuning steps, The image icon may have been mistakenly replaced by github. It's in correct format.

I tried using the released checkpoint in huggingface, but still cannot produce the test results, so So I think it’s a data processing problem.😂
How do you deal with the large size of mind2web image, or just use the raw image.

The processing details for mind2web images are in the paper's appendix C.4. We kept the 1920*1080 resolution for the screenshots. And we provided these screenshots in this repo.

Really thanks for sharing, i will try it.


Python source editor's bug

This issue has been moved from a ticket on Developer Community.

[severity:It bothers me. A fix would be nice]
In the Python source, if you add a name to a variable or function with a Japanese kanji kana or an English kanji mix,
Double-clicking the mouse does not allow you to select the entire name. (Only part is selected)
It seems that you can select it properly in C++ and C# editors.

Original Comments
Feedback Bot on 8/2/2024, 11:00 AM:
(private comment, text removed)

Original Solutions
(no solutions)

A gif demonstrates the issue. This does not repro in VS Code, might be a VS editor issue?


Console warning in /contents view

Warning: Failed prop type: Invalid prop `size` of value `none` supplied to `Confirm`, expected one of ["mini","tiny","small","large","fullscreen"].
    in Confirm (at Contents.jsx:977)

This should be easy to fix.

Solved in the PR #1702.

Thanks @silviubogan


Pass LogsLocation as a method param in Knowledge.hanndle

RIght now it is specified in the ctor and it's dangerous, since a different LogsLocation could be used by each Knowledge, when in fact there should be a single location for all.

done


Do we need RazorLanguageServer-PlatformAgnostic?

We currently publish this package as a build artifact on every build, and don't use it when inserting into VS Code. Perhaps we should get rid of it? Or switch to using it instead of the runtime specific packages?
/cc @allisonchou as you're the expert here

Following up here: Roslyn builds their platform-specific language servers with ReadyToRun which makes it faster compared to the language agnostic server. I don't think Razor uses ReadyToRun today so there's not much benefit for us, but it could be an optimization that we implement in the future.
Also, today we don't actually publish the platform agnostic extension in the marketplace, so having the platform agnostic language server is future proofing in case users start requesting it.

Thank you for the info. I'm going to close this with no action required.


support nested params

I know that nested params tends to usually happen when dealing with model-back resources, and that in those cases you're supposed to rely on your model validations.
However, that pattern doesn't work for me.  I can't just stick the data into my model and call .validate!, because I'm validating far more than basic data types and values.  I'm also validating complex inter-model relationships with the help of a Service object, and I need to type-and-value sanitize the params in the Controller before passing them to the Service object.
rails_param looks awesome, and would be of great help with this, except it only takes param names as a symbol, and therefore there's no way to handle nested params such as params[:user][:name].

We had the same issue.  Check the docs now, rails_param takes a block for nested attributes and also handles arrays.

That is fantastic -- thanks!
PS-It annoys me that this gem is more popular, especially since it affects my decision of whether to use it.  I think it's because it goes against the Rails way passing the data straight to a model build and letting the validations deal with them.  But that way is so limited to the most basic, text-book case...

@odigity : even if I've accepted a PR to support nested params, I still does not understand why you don't use ActiveModel::Model virtual classes to validate nested params. This feature is already included in Rails and support all the classical Rails validations out of the box.
I still think that if you need to validate nested params inside a controller you are already too far from the first goal of this gem and may break the "thin controller" rule.

@nicolasblanco -- Why do you assume that all controller params always map to the concept of a model?  And why do you assume ActiveModel validators is always the right way to validate input?

Closing this as main question as been addressed 👍 !


x1034 React 18 , Cypress, react-testing-library, react-dom, react-table update

Hello could you give a description of the issue you are facing?


Disable single-quote autopairs in rust files

Rust syntax is a bit unusual in the sense that single quotes (') don't come in pairs, as they are used as a single prefix to indicate lifetime annotation.
This rule should be pretty universal, so it seems that the most elegant solution is to disable "'" completion in the rust filetype by default for all users.

Provided a PR #143 that seems to work for me, would appreciate review.


Keboola.KeboolaCLI version 2.9.0

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

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

Closing due to merge conflicts.


GPU linear solver + implicit timestepper

Check that linear solvers and implicit timesteppers work on GPUs.
For now, we only care about the Wfact case.

I saw a similar issue in ClimaAtmos. Should we close this?