Flaky ReactivePulsarListenerTombstoneTests$SingleComplexPayload causing random CI PR failures

The ReactivePulsarListenerTombstoneTests$SingleComplexPayload fails randomly from time/time.
Example: https://github.com/spring-projects/spring-pulsar/actions/runs/7735972858/job/21092530057#step:4:7079
This needs to be fixed.

Hi @onobc, can i work on this?

Hi @KartikShrivastava ,
That would be great. The trick will be to reproduce it. I have not had luck doing so locally. Let me know if you have any questions.

Hi @onobc,
I too couldn't reproduce it locally. I have two hypothesis tho:

Messages are received in order different then the test expects
assertMessagesReceivedWithHeaders is called before latchWithHeaders is finished executing?

wdyt?
P.S.:
Linking the CI PRs failures I found associated with this flakiness [1] [2]

Hi @KartikShrivastava ,
Thanks for digging into this!
Those are very plausible theories. I am not opposed to adding temporary code in tests or main (logging etc..) that may help prove the points. Do you see anything (and anywhere) we can instrument to see if we can get some more info during the CI run?

Hi @KartikShrivastava ,
If you do not want to continue looking into this issue I totally understand. The issues currently in the backlog are rather coarse grained and if you are looking something small to work on there is not a lot to choose from. We have been meaning to put some smaller issues in and mark them accordingly. I will try to get to that this week but in the meantime if you want me to find you something else just let me know. And there is no obligation to do anything - I just wanted to offer this in case.
Thanks

Hi @onobc, apologies for not raising that small PR yet, I was planning to do it in coming weekend. My weekdays availability is most of the time very less.
P.S: Please feel free to assign any other small and low priority task you have in mind, I find this project quite interesting to explore and learn from

Absolutely no worries @KartikShrivastava . No need to apologize. I just thought about the issue and that it is not the most fun thing to work on and thought you might enjoy something else. I will ping you when we have added some low priority issues.
Thanks 👍🏻

Hi @onobc, I've created a PR adding one info log, please review as per your availability. Thanks!

Looks like this flaky test failed in a recent build, here's the stack trace (it failed after executing logger.info(message.toString()); statement once):
ReactivePulsarListenerTombstoneTests > SingleComplexPayload > shouldReceiveMessagesWithTombstone() STANDARD_OUT
    17:24:20.410 [Test worker] INFO  org.springframework.pulsar.reactive.listener.ReactivePulsarListenerTombstoneTests$SingleComplexPayload - ReceivedMessage[payload=Foo[value=foo], keyHeader=key:foo]

ReactivePulsarListenerTombstoneTests > SingleComplexPayload > shouldReceiveMessagesWithTombstone() FAILED
    java.util.ConcurrentModificationException
        at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1013)
        at java.base/java.util.ArrayList$Itr.next(ArrayList.java:967)
        at org.springframework.pulsar.reactive.listener.ReactivePulsarListenerTombstoneTests$SingleComplexPayload.shouldReceiveMessagesWithTombstone(ReactivePulsarListenerTombstoneTests.java:249)

What could be the reason of ConcurrentModificationException?


BLD: make scipy build warning-free with LTO enabled

Much fortran code is not LTO-safe, and would require modernizing that fortran code, probably. We cannot actually solve this trivially. What we can do, is mark each of these targets as LTO-unsafe so that meson with -Db_lto=true refrains from compiling these specific targets with LTO.
Reproduce by compiling SciPy with:

compile/link flags (CFLAGS, CXXFLAGS, FFLAGS, LDFLAGS): -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing

meson setup -Db_lto=true

and keep adding override_options to various targets until the build succeeds.
Bug: #16098

I noticed this when I tried reinstalling SciPy on Gentoo with -flto in /etc/portage/make.conf.
@rgommers commented in the linked ticket:

It's mostly old Fortran code. Example:
scipy/stats/statlib/spearman.f:75:72: warning: type of ‘alnorm’ does not match original declaration [-Wlto-type-mismatch]
   75 |       prho = u / exp(y / two) + alnorm(x, .true.)
      |                                                                        ^
scipy/stats/statlib/swilk.f:217:38: note: return value type mismatch
  217 |       DOUBLE PRECISION FUNCTION ALNORM(X, UPPER)

It's pretty tedious (but not hard) to fix.

Since it's been a while and it doesn't appear to be getting fixed? I think the pragmatic approach is to carefully disable LTO for those targets. Also, this makes it easier to grep for "known trouble spots" without doing a full build. If a target is suppressing LTO, that can be analyzed as a red flag.

That looks more like somehow it is mixing AppleClang together with generic Clang compilers.

That looks more like somehow it is mixing AppleClang together with generic Clang compilers.

Yes indeed, that is happening with conda-forge compilers; the compilers are built within conda-forge, but the system linker may be used (sometimes with a shim, platform-dependent). I have LLVM 16.0.6 from conda-forge, and LLVM 15.0.0 from macOS.
On Linux I get similar issues with conda-forge compilers:
[1361/1537] Linking static target scipy/optimize/_highs/libbasiclu.a
/home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-ar: scipy/optimize/_highs/libbasiclu.a.p/.._..__lib_highs_src_ipm_basiclu_src_basiclu_factorize.c.o: plugin needed to handle lto object

xref https://github.com/conda-forge/clangdev-feedstock/issues/155; conda-forge can't enable LTO. However, Linux distros can - and they do ensure to build all their packages with the same compilers.
Since this is an improvement and will help Linux distros, let's get this in. A lot of the problematic Fortran code is in the process of being rewritten in another language, so the problem will gradually shrink / go away.

The 1.13.0 release isn't too far off anymore (~1 month or so I hope), and 1.12.0 is already at RC2, so I'll not mark this for backporting.

Sure, no problem. For now I can add filter-lto to the SciPy ebuilds, which will delete -flto completely from the user's *FLAGS. That way other users won't hit this footgun.


Remove evidence-data index

We should evaluate usage of this index, and move to generating a file that can be read within data_pipeline and separately loaded into elasticsearch if necessary for rest_api

This is used by the API

As part of opentargets/data_pipeline#364 this can be written to file. We still need to investigate how the association step of the data pipeline read it (from the file or from elasticsearch) and how the API reads it from Elasticsearch, and if any further changes are required.

Decision taken to close based on low priority and value at this point in platform refactor.


Bot triggers GuildCreate event again for all the servers it was previously in.

I need to do a database operation for the servers that bot has just joined, but when I use the discordgo.GuildCreate event, bot triggers the event again for the servers it was previously in.
Here is my code:
package events

import (
	"github.com/barbarbar338/emojibot/utils"
	"github.com/bwmarrin/discordgo"
)

func GuildCreate(session *discordgo.Session, event *discordgo.GuildCreate) {
	utils.Logger.Println("I joined server", event.Name)
}

// in main
// discord.AddHandler(events.GuildCreate)

and this is my output:
PS C:\Users\demir\Desktop\emoji-go> go run .
✔ - 2021/06/19 11:51:28 main.go:34: Logged in as Emojicord BETA
☄ - 2021/06/19 11:51:28 ready.go:10: Ready!
✎ - 2021/06/19 11:51:28 guildCreate.go:9: I joined server Merloss's emojis << these shouldn't be here
✎ - 2021/06/19 11:51:28 guildCreate.go:9: I joined server Hammer Sunucusu << these shouldn't be here
☄ - 2021/06/19 11:51:31 main.go:45: Closing bot...
PS C:\Users\demir\Desktop\emoji-go>

This is fully expected behavior. Looking at the Discord docs, we see:

This event can be sent in three different scenarios:

When a user is initially connecting, to lazily load and backfill information for all unavailable guilds sent in the Ready event. Guilds that are unavailable due to an outage will send a Guild Delete event.
When a Guild becomes available again to the client.
When the current user joins a new Guild.

This event more closely means "this guild is now available to your current running instance" to "this guild is now available to your bot at all". If you'd like to detect guild joins, you should keep some sort of external long-running storage, or could perhaps try using the JoinedAt time in your bot's member object in the guild to approximate it.

Thanks for your reply :)


Publish failed after upgrading to 2.0 RTM

In my projects, modules are dynamically loaded at runtime, and I need to turn off PrecompiledViews by adding
    <EnableDefaultContentItems>false</EnableDefaultContentItems>
    <PreserveCompilationContext>false</PreserveCompilationContext>

I worked fine, but after upgrading to 2.0 RTM. I got the following error
Severity	Code	Description	Project	File	Line	Suppression State
Error The command ""dotnet" exec --runtimeconfig "C:\WebApplication15\bin\Release\netcoreapp2.0\WebApplication15.deps.json" "C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.mvc.razor.viewcompilation\2.0.0\build\netstandard2.0\Microsoft.AspNetCore.Mvc.Razor.ViewCompilation.dll" @"obj\Release\netcoreapp2.0\microsoft.aspnetcore.mvc.razor.viewcompilation.rsp"" exited with code 1.	WebApplication15		0

Add:
    <MvcRazorCompileOnPublish>false</MvcRazorCompileOnPublish>

It works, thanks

Where do you add that? Which file?


blt_add_test learned NUM_OMP_THREADS

#2
#231

@white238 -- would it make sense to provide a blt option to set the default number of threads for blt tests?
(Alternatively, one could argue that this would add too much magic to the build system..)
Obviously, this could be in a separate PR.


Support for configuring layers in server function

We have a requirement to configure a layer for monitoring in our deployment. From what I could see in the variables , there is no option for configuring a layer. Is this the case?
Describe the solution you'd like
Ability to configure a layer for our deployment
copy and paste an example terraform configuration here

  server_function = {
    additional_environment_variables = {
      ... my envs
    }

    layers = ["MY_LAYERS"]
  }

Hi @tom-sanderson-bt,
Thanks for using the module.
Looking at the code, it appears layer support was missed. I am adding this now and will create a new version shortly.


Installation for python2 fails due to mypy

$ pip install<EMAIL_ADDRESS>Collecting cirq from<EMAIL_ADDRESS>  Cloning<EMAIL_ADDRESS>to /tmp/pip-build-XAtp9i/cirq
Password for<EMAIL_ADDRESS>
Collecting 3to2 (from cirq)
Collecting absl-py (from cirq)
Collecting mypy (from cirq)
  Downloading mypy-0.580.tar.gz (1.4MB)
    100% |████████████████████████████████| 1.4MB 1.2MB/s
    Complete output from command python setup.py egg_info:
    ERROR: You need Python 3.4 or later to use mypy.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-XAtp9i/mypy/

This is fixed now, due to the introduction of separated requirements files.


add unrar license and use

Description of changes
Continuation of #328698
Based on the fedora comment I don't think the license allows us to redistribute the binaries.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Based on the fedora comment I don't think the license allows us to redistribute the binaries.

It just means that the use restriction is incompatible with Fedora’s licence policy. I think it is still compatible with our lenient definition of unfreeRedistributable, which in any case does not cause us to redistribute binaries (and never should; cf. my standard spiel about how we would need a specific list of permitted unfree licences).

Thanks for picking this up!
Thinking more on the discussion in #328698, I do think that there's actually a matryoshka of two licenses here:

The full license, which is the one that the original UnRAR source code comes with, and which includes the problematic "you must remove UnRAR files from your storage devices" clause;
Just the 2nd paragraph, which is less burdened.

Some projects have elected to include the code only along with the 2nd paragraph, which does not reference the rest of the license, so it wouldn't be quite correct to lump them together.
Notably, the "2nd paragraph only" variation does look like it should allow redistribution without issues.

The docs say that we would distribute it then https://github.com/SuperSandro2000/nixpkgs/blob/a1ddda46fa838b99460ae4594e3e382231ac1e8b/doc/stdenv/meta.chapter.md#liblicensesunfreeredistributable-unfree-redistributable-liblicensesunfreeredistributable-unfree-redistributable

Weird. The docs lie, I guess.

Some projects have elected to include the code only along with the 2nd paragraph, which does not reference the rest of the license, so it wouldn't be quite correct to lump them together.

IIRC it’s actually that the licence changed to become more burdensome later on (otherwise any project cutting out parts of the licence would be committing a copyright violation and be less redistributable), but I forget the exact details.

Weird. The docs lie, I guess.

I think it is intentional. Some programs are unfree (as in open source free) but we are allowed to distribute them.

I think it is intentional. Some programs are unfree (as in open source free) but we are allowed to distribute them.

We don’t do it. See https://github.com/NixOS/nixpkgs/issues/83884, and https://github.com/NixOS/nixpkgs/issues/83884#issuecomment-2241222950 for why we shouldn’t do it as a blanket policy separate to any ideological concerns.

Then we should update the docs to be correct. Since I seem to lack some knowledge here I leave it up to the people that are more familiar with licenses.


sslv3 issue in production

Hi, everything works fine locally, but when I run on remote host in production I get the following:
{:error,
{:options, {:sslv3, {:versions, [:"tlsv1.2", :"tlsv1.1", :tlsv1, :sslv3]}}}}
How to fix this?

Which provider? Are you on OTP23?

Yes otp 23, elixir compiled on 21

This could be caused by your provider not doing their job, or OTP 23 removing old SSL encryption options. Try passing [ssl_options: [versions: [:"tlsv1.2"]]] as hackney_options in %Email{}'s private field.
# somewhere in your pipeline that constructs the email
|> put_private(:hackney_options, [ssl_options: [versions: [:"tlsv1.2"]]])`

If this doesn't work, you probably have to remind your provider to upgrade their infrastructure... Not very likely though, the OTP issue is a lot more likely and I've had it before.

Thank you very much. This solved it.

Thanks for the confirmation!


Allow adding a unit term for serves

Description
As per #36, I added the field "servesUnit" and a method called "getServes" which is just concatenating the serves with its unit when it's not empty. This gets added to json-ld microdatas as well to be in line with the spec which allows specifying different kinds of serves depending on the recipe (yields 4 pizza slices, yields 12 donuts, etc.)
Also, sidenote: I'm hungry.
Related issues
#36

Thx!


Fixed #26643 -- Prevent unnecessary AlterModelManagers operations caused by the manager inheritance refactor.

https://code.djangoproject.com/ticket/26643

Prevented*
Looks okay to me although I haven't worked in this area much.

Thanks Tim, I incorporated all the suggestions.


Hello, I found that after denying the storage permission, the screenshot will call the onScreenCapturedWithDeniedPermission method twice.

Hello, I found that after denying the storage permission, the screenshot will call the onScreenCapturedWithDeniedPermission method twice. After the permission is granted, the onScreenCaptured method is called only once.
sorry for my pool english

Refer to #5, onScreenCapturedWithDeniedPermission method not suitable in that case. Remove it might be the solution. So I will remove it in next version.


adding controller for user

added updateuser controller,getAllUsers controllers,getUserByRole,getUserById and delete user account controllers and their routes with swagger documentation

added new thing for users


Literal argument aliases are ignored by cloud-brigadier

Steps to reproduce
Here's an example command:
manager.command(
    manager
        .commandBuilder("reputation", Description.of("Change player's reputation"))
        .permission("example-plugin.command.reputation.good")
        .senderType(Player.class)
        .required("player", offlinePlayerParser())
        .literal("good", "potato", "tomato")
        .handler(new AsyncHandler<>(ctx -> handleAddRemove(ctx.sender(), ctx.get("player"), ReputationAction.UPVOTE)))
);

Expected behavior
Expected command tree:
literal "reputation"
    offline player "player"
        literal "good"
        literal "potato"
        literal "tomato"

Observed behavior
However, the resulting Brigadier command tree looks like this:
literal "reputation"
    offline player "player"
        literal "good"

Other
I might be wrong, but I think this happens because o.i.c.brigadier.node.LiteralBrigadierNodeFactory#constructCommandNode(CommandNode<C>, BrigadierPermissionChecker<C>, com.mojang.brigadier.Command<S>) creates a literal node for the component name only, ignoring its aliases:
final ArgumentBuilder<S, ?> argumentBuilder;
if (root.component().type() == CommandComponent.ComponentType.LITERAL) {
    argumentBuilder = this.createLiteralArgumentBuilder(root.component(), root, permissionChecker);
} else {
    argumentBuilder = this.createVariableArgumentBuilder(root.component(), root, permissionChecker);
}
this.updateExecutes(argumentBuilder, root, executor);

And then in LiteralBrigadierNodeFactory#createLiteralArgumentBuilder(CommandComponent<C>, CommandNode<C>, BrigadierPermissionChecker<C>):
private @NonNull ArgumentBuilder<S, ?> createLiteralArgumentBuilder(
        final @NonNull CommandComponent<C> component,
        final @NonNull CommandNode<C> root,
        final @NonNull BrigadierPermissionChecker<C> permissionChecker
) {
    return LiteralArgumentBuilder.<S>literal(component.name()) // <--- aliases not used
            .requires(this.requirement(root, permissionChecker));
}

One possible fix would be making constructCommandNode(...) return a list of ArgumentBuilders which would work well with Brigadier node's then(...) method
But I might be completely wrong about why this happens, so ¯\_(ツ)_/¯
It could also be related to #5

Duplicate #5


Problem in updating the operation-key until a new application is regarded to OperationKeyManagement application

As per the new embedding procedure , a new application will be embedded in the following order to the TinyApplicationControllers,

ALT
OKM
EATL
AA
OL

As a part of the /v1/regard-application procedure in ALT ,
ALT will ,

create link between the "/v1/redirect-topology-change-information" of the client application(ALT) and the serving application(NewApplication),
notify the created link to OKM

Further , OKM will try to set the operation-key in both the involved end-points.
OKM will ,

set the operation-key to ALT
fail to set the operation-key in the serving application(NewApp).
Reason : The new application is not yet regarded to OKM and OKM will not know the TCP/IP information about the new Application.

Possible proposals :
Proposal#1 :
After getting the ControlConstruct from the new Application , ALT shall regard the new application to OKM.(by Thorsten)
Proposal#2 :
ALT will send the details of the link-id to OKM using the /v2/regard-updated-link API.
A sample of the requestBody is as below ,
{
  "link-uuid": "11bf5b37-e0b8-42e0-8dcf-dc8c4aefc000",
  "link-end-point-list": [
    {
      "application-name": "RegistryOffice",
      "release-number": "2.0.1",
      "operation-uuid": "ro-2-1-0-op-c-im-alt-1-0-0-000",
+     "ltp-direction": "core-model-1-4:TERMINATION_DIRECTION_SINK"
    },
    {
      "application-name": "ApplicationLayerTopology",
      "release-number": "2.0.1",
      "operation-uuid": "alt-2-0-1-op-s-bm-001",
+     "ltp-direction": "core-model-1-4:TERMINATION_DIRECTION_SOURCE"
    }
  ]
}

On receiving a /v2/regard-updated-link ,
OKM shall look for the "ltp-direction": "core-model-1-4:TERMINATION_DIRECTION_SOURCE"
If the "application-name" + "release-number" client stack is not available in its configuration
then
OKM shall set the default operation key "Operation key not yet provided" to the consuming application.
So , an "update-operation-key" call will be triggered to the consuming application( In our case ALT will receive trigger to respond back to RegistryOffice )

Proposal #2 seems to be really good idea.

Changed as proposed.


Removing gh-pages from Circle CI

What does this PR do? (please provide any background)

UI-Toolkit has docs which get published to gh-pages branch of GitHub
CircleCi currently runs tests on that branch, but the branch is a static generated site therefore has no tests.
This PR stops CircleCI running on that branch.

What tests does this PR have?
None, thats kinda the point :)
How can this be tested?

This is going to be a hard one to test, we will need to do (or wait for) a release of the UI Toolkit to see if this runs against the branch.
It should have no problems going live as it doesn't affect the site, just the CI.

Screenshots / Screencast

What gif best describes how you feel about this work?

[x] I have checked the contributing document and I'm happy for this to be reviewed.

Reviewers
Review 1

[ ] :+1:

Review 2 *

[x] :+1:

Review 3 (optional)

[ ] :+1:

By adding a +1 you are confirming you have...

Witnessed the work behaving as expected (this could be on the author's machine or screencast).
Checked for coding anti-patterns.
Checked for appropriate test coverage.
Checked all the tests are passing.

*  for HX this review must be completed by an SE, SA or Project Guru

:+1:

dev

:+1:


Cloud graal native support be considered?

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
use unirest in cli application and publish as native image.
Describe alternatives you've considered
apache hc
Additional context
no
whom use graal native:
tocmat
https://tomcat.apache.org/tomcat-9.0-doc/graal.html
micronaut
https://micronaut.io/
quarkus
https://quarkus.io

Tomcat, Micronaut and Quarkus are all application stacks. That is, they are containers for running an application. Most likely Unirest would be included in one of these stacks and compiled natively as a dependent library.
It's not clear to me what Unirest as a library that is not executable self would need to do? It looks like any application should be able to include Unirest itself in order to create a native image.

yeah, for example: unirest + picoli

So you want a CLI interface for Unirest? That would be a pretty major undertaking. We have a big backlog of functionality that would be ahead of such a thing (http2 for example). If you have a command line available, I don't see why you wouldn't use cURL. anything we made for unirest would eventually just look a lot like cURL and  would probably never catch it in terms of features.

i plan to use unirest and picoli to build a cli tool for my web product, and build it to native image for publishing to customer.  security and no depend to jre.

well, you sure could do that, and it would be great to see that open sourced, I'm not sure it belongs in this project by itself, possibly as a extension module, but I suspect you have a far smaller use case than "all of unirest". If there is anything about Unirest which is incompatible with graalvm let us know


feat: Add type hint on Quote

Description

Add type hint on Quote

Checklist

[x] My code follows the existing style, code structure, and naming taxonomy
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my own code and included any verifying manual calculations
[x] I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage.  New and existing unit tests pass locally and in the build (below) with my changes
[x] My changes generate no new warnings and running code analysis does not produce any issues
[x] I have added or run the performance tests that depict optimal execution times
[x] I have made corresponding changes to the documentation

need to rebase


Refresh Object not working

Whenever I try to refresh object from VS Code, the following message pop ups:

Have you taken this object using the "Get Object" command or it's some
existing xml file on the disk?
The Refresh Object is only applicable to those objects that you obtained
from your remote server using "Get Object" command.
On Fri, Sep 16, 2022 at 3:42 AM Roberto @.***> wrote:

Whenever I try to refresh object from VS Code, the following message pop
ups:
[image: image]
https://user-images.githubusercontent.com/34972093/190584112-6c54ffb3-210f-4b10-8c81-9677fa227a21.png
—
Reply to this email directly, view it on GitHub
https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/30,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZB3VTHCNSQN5CKKMFMLV6QQGTANCNFSM6AAAAAAQOCKWEE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I get it with "Get Object".
I'm checking now that there is a problem with the name of the file... if I change the name and path when I save the XML after doing the "Get Object", then the "Refresh Object" won't work...
When I do "GetObject", the file suggests being saved on a temp location on my computer that is outside my project path, so that's why I'm moving it...

I attach a pic about where the file appears after GetObject

Does it work if you don't save it under your project folder?
The original idea for refresh was to get an object in a temp folder and get
a refreshed (new version) from the server and compare them.
From your picture it looks like your file is in a temporary location, so it
should work properly, the only thing I can think of is that this temp
folder is part of your IIQ project folder, otherwise the error that you get
doesn't make sense to me.
Also to deal with saved object there is a "Compare Local with Deployed"
command, see if that works for you.
Yes, there is a bit of redundancy there, maybe I can combine them together
so that I disregard whether the current object is in the project or in a
temp folder.
On Fri, Sep 16, 2022 at 3:01 PM Roberto @.***> wrote:

I attach a pic about where the file appears after GetObject
[image: image]
https://user-images.githubusercontent.com/34972093/190712137-fe6b381a-5b3d-4187-9552-53a19eeafa5d.png
—
Reply to this email directly, view it on GitHub
https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/30#issuecomment-1249706494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZBYHZB2RFDU6KWCTE5DV6S7YFANCNFSM6AAAAAAQOCKWEE
.
You are receiving this because you commented.Message ID:
@.***>

Yes, if I save it on the temp default folder everything works fine.
The problem is that the path doesn't make any sense... my project is under "/Users/myuser/Downloads/ssb/" so I don't understand why it's going outside.
Also, I don't why it fails even if I name the object by -.xml

Hey, have u been able to check this lately? I was wondering maybe I can give it a look and try to make the GetObject to ask for a folder to place the retrieved object place it there with "ClassName-ObjectName.xml" format.
Tell me if you have anything else in mind, so I can try to help with it.
Happy new year, by the way! :)

Happy New Year, Roberto, thanks for checking in!
Please check out the latest 1.0.42 where I put a fix for "Refresh
object", see if it works for you.
On Mon, Jan 9, 2023 at 7:32 PM Roberto @.***> wrote:

Hey, have u been able to check this lately? I was wondering maybe I can
give it a look and try to make the GetObject to ask for a folder to place
the retrieved object place it there with "ClassName-ObjectName.xml" format.
Tell me if you have anything else in mind, so I can try to help with it.
Happy new year, by the way! :)
—
Reply to this email directly, view it on GitHub
https://github.com/lispercat/sailpoint-iiq-dev-accelerator/issues/30#issuecomment-1376545932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCZB7XZGIPT7UH7UHD3ADWRSUYJANCNFSM6AAAAAAQOCKWEE
.
You are receiving this because you commented.Message ID:
@.***>


Add typedef for ssize_t under windows

This fix allows the library to be compiled under windows as well.
I have only tested this under clang, not using msvc or any other windows-targetted compiler.

Thanks!


3.0.83 Is Newer Than 3.0.9

That's a bit of a mess for versioning...

Where are you seeing this?

Bower will install it if i ask for ~3.0.8 rather than the latest. The behaviour is the same for ~3.0.9 too.

Interesting... that's bower's faulty semver parser :(

No its not. It's correct. Your versioning is incorrect. 83 is a larger patch version than 9...

I see what's going on.

I have been also slightly confused.
Please just release another v3.1.0 or change 3.0.9 to 3.0.90, after more then 10 years this awesome script really deserves a higher number :)
Oh, and please be so kind to Update the Download Page:
http://alexgorbatchev.com/SyntaxHighlighter/download/
There are still many outdated confusing links on your website.

https://github.com/syntaxhighlighter/syntaxhighlighter/releases/tag/v3.0.90
Thank you very much everyone for taking time to flag this issues!

I am new to github and using files from git. I am trying to use syntax highlighter and I am not sure how to include it in my html file. It would be wonderful if you can help me with it


Restore jellybeans colors (for real) (closes #24)

Also has low-color-terminal compatibility, in theory. (Not completely
faithful: I added some more grayscales to the inactive palette. Also did
not touch CtrlP colors, since I'm not sure when they're used.)

By the way, I noticed when testing this that normal_modified and company don't seem to do anything in low-color mode. Anybody know why?

what is the difference between #29?

I think I tried harder to copy all the colors from the old jellybeans airline theme. This also preserves the modified palette colors (where the status turns orange when the file has been modified). Finally, it tries to be compatible with terminals that don't have 256 colors like the original jellybeans is, but I don't know if anybody still cares about that nowadays.
But overall, yeah, these PRs are trying to do the same thing.

Okay, I am closing this for now. If you still think,some colors need to be fixed, please update according your work. Thanks!


Fixes flakiness in TimestampTrackerIT

I was building Fluo locally in a VM and the test TimestampTrackerIT was failing a lot of the builds.  I investigated and found the problems was the test would make a change that kicked of an action in a background thread, sleep, and then check for the action.  Sometimes the background action was not done and the test would fail.  I replaced the sleeps w/ loops that check a condition and sleep.  With the changes I was able to run the test 15 times w/o failure.

Some other ITs failed during the build, so I restarted it and it passed.  May be some other flaky ITs that need attention.

Some other ITs failed during the build, so I restarted it and it passed.  May be some other flaky ITs that need attention.

Some other ITs failed during the build, so I restarted it and it passed. May be some other flaky ITs that need attention.

There are several open bugs about flaky ITs already. I wouldn't be surprised if what you saw included one of those already identified. If you see any others, please feel free to create a new issue for them.

Some other ITs failed during the build, so I restarted it and it passed. May be some other flaky ITs that need attention.

There are several open bugs about flaky ITs already. I wouldn't be surprised if what you saw included one of those already identified. If you see any others, please feel free to create a new issue for them.


[GuestConfiguration] minor fix for SDK publish job failure

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[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.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

specs are here:
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/guestconfiguration/resource-manager/Microsoft.GuestConfiguration/preview/2018-06-30-preview/guestconfiguration.json

Tests need to be fixed


[zh] sync topology-aware-routing.md

Add zh text to this page:
content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md

@windsonsea,
Please Rebase PR to get success checks.

/approve


fix(onText): reset state of global regexp after search

[x] All tests pass
[x] I have run npm run gen-doc (no changes)

Description
Regex matching in onText: Resets the search index to start each regex match at the beginning again .
Note: I usually add test cases to code I add/modif, but in this case it seems rather difficult to do that without modifying the onText function itself. I want to count the number of times the callback is executed. Any Ideas?
References
Issue #325

How about something like this:
const regexp = /ab*/g;

bot.onText(regexp, function() {
    // the 'lastIndex' property should be reset by now!
    assert.equal(regexp.lastIndex, 0);
});

:+1: Good idea. Thanks!
I added the test to my commit.

Thanks @Sirius-A for this awesome PR! :+1:


chore: bdd-spring-1577665603 to 0.0.1

chore: Promote bdd-spring-1577665603 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Cannot login - is app hacked?

After login:

Hi, there is no indication that the app got hacked or anything but we have seeing this issue too. I wonder if some weird routing at AWS was happening :/ Either way, if you still have this issue remove the service worker for djangopeople.net and clear your cache.


Overflow in information displayed when cloning large repositories

Although this is not a big problem, when the cloned repositories is too large, the current progress displayed in real time in the log will overflow, like this:
[-] 10:59 - Clone - https://github.com/JetBrains/intellij-community.git
     remote: Enumerating objects: 7876335, done.
     remote: Counting objects: 100% (12111/12111), done.
     remote: Compressing objects: 100% (4794/4794), done.
     Receiving objects: 48% (3855387/7876335), -2113079880 bytes | 941.75 KiB/s.

Sorry, it seems like that it is a bug of git, I close this issue.

No, you've been right - this is a problem with Gittyup: We're currently building that message ouself (it's just meant to resemble the standard GIT's messages)


[Testing On iOS 18.1 Simulator] Swift Compiler Error (Xcode): Cannot find 'dateToMillis'/'imageToBase64' in scope

Version
4.7.1
Steps to Reproduce

Upgrade Posthog Flutter SDK to version 4.7.1
On VSCode, F5 Launch on iOS 18.1 simulator (I was running on iPhone 16)

Expected Result
The app should run without any hitches.
Actual Result
Getting the following error in VSCode debug console:
Swift Compiler Error (Xcode): Cannot find 'dateToMillis' in scope
/Users/username/.pub-cache/hosted/pub.dev/posthog_flutter-4.7.1/ios/Classes/PosthogFlutterPlugin.swift:182:28

Swift Compiler Error (Xcode): Cannot find 'dateToMillis' in scope
/Users/username/.pub-cache/hosted/pub.dev/posthog_flutter-4.7.1/ios/Classes/PosthogFlutterPlugin.swift:217:28

Swift Compiler Error (Xcode): Cannot find 'imageToBase64' in scope
/Users/username/.pub-cache/hosted/pub.dev/posthog_flutter-4.7.1/ios/Classes/PosthogFlutterPlugin.swift:235:39

Dupe https://github.com/PostHog/posthog-flutter/issues/125
Please upgrade your Pods


Follow redirects

Fixes #775
What's Changing and Why
Automatically follow http redirects instead of erroring out.
What else might be affected
Tasks

[ ] Add tests
[ ] Update Documentation
[ ] Update jimp.d.ts
[ ] Add SemVer Label

Published PR with canary version: 0.8.1-canary.789.301.0

@SaWey please fix lint and add a test if you can

I installed version with this changing and that solve my problem.
Byffer error happen only if I try to read a file that is only partially downloaded.
I think it's good results.

I'd still like a test so we don't break it in the future. Good to know that it solved the problem though!

I can't seem to get the test environment setup on my windows machine.
Keep bothering mee about not finding '@jimp/test-utils' module when running the tests.
How would you see this test being setup? Start a custom server to send a 301 response when loading an image?
Because if we were to use an internet link, we're not sure it's going to stay online.

Hi, I'm having an issue that probably will get fixed with this.   My url redirects to the actual image but Jimp/phin is reading as XML so it fails.  If I test with curl url it shows the xml if I test curl -L url it works like a charm, so please if this gets into Jimp would be awesome

I was able to add a test with a local server to mock a 301 redirect.

@hipstersmoothie any idea how I should tackle this testcase?
I don't know how to differentiate between browser and node running the test.

@hipstersmoothie
Can this patch be applied?

:rocket: PR was released in v0.9.3 :rocket:


Warn for overlays with different dimensions?

Right now, overlays seem to use the name of the first object's dimensions, but happily combine dimensions with different names:

This behavior is a bit surprising to me; I'd have expected a warning or else the axis label to list all the dimensions that apply to this plot (i.e. "horiz, h" here).  Not sure how widespread such overlaying is, i.e. how many existing usages adding such a warning would affect, but it seems like people must already have to deal with this because whether the displayed axis label is the one they wanted seems like only a matter of chance.

I'm open to a issuing a warning when overlaying non-matching dimensions. @philippjfr?

I'm open to a issuing a warning when overlaying non-matching dimensions. @philippjfr?

On the one hand this would force people to give their objects proper kdims on the other hand I think this happens all the time and could in some cases be quite annoying. In theory we could also add parallel axes eventually. I'll have to think about it and maybe try the warning out for a bit.

The warning can be a config option so we can try it and then decided whether it should be on or off by default.

If it happens all the time, it means that people's plots are being labeled with some arbitrary dimension, and they probably just don't notice that it's only the name of one of the things they are plotting, not all of them.  So I'd vote for either having a warning, or showing all the dimensions in a list, so that it's not silently being misleading.

I almost never give annotations or annotation-like things proper kdims. My compromise would be to warn for non-default dimensions.

I agree, for annotations; I'm talking about actual overlaid data.  Sure, if there's more than one non-default dimension (as above), then it's a clear case for warning.

An Overlay's x and y axes have Dimensions that seem be created ONLY through inference on it contained Elements. In jbednars case, the inference picks the first contained Element and does not detect conflicts between other elements. I think a warning would be useful in this case.
But also, there does not seem to be a way to explicitly set the Dimensions of Overlay axes. Allowing the user to override how the inferences implemented, would be a more general solution.
Making inferences a first class object would be even a better solution.

I still don't get it; how is the behavior of arbitrarily choosing "horiz" in the above case, instead of "h", more convenient?  To me it is simply surprising and confusing, and hard to remember. Even if this were to be a general rule, why should the label be taken from the first item in the overlay, given that Overlays generally leave the last thing on top of the plot?  I think the current behavior is just a bug, for anything with specified (non-default) dimensions; I really can't see any justification for it.

I think I would be ok with issuing warnings as long as you can disable them to allow the old behavior without the warnings. @philippjfr ?

Warnings for non-default dimensions are probably okay, but I think it would have to be coupled with detailed documentation about working with wide datasets and how to make your data tidy. I'd also be okay with using the name of the first layer with a non-default dimension for the axis.

I'd also be okay with using the name of the first layer with a non-default dimension for the axis.

I would also be happy with that policy.


Built outline components for Ratings and Reviews

Built out my components and added my section to app.jsx
Also added the tiniest amount of layout styling to my section for visibility

Nice work! I like it.
A couple of notes/questions.
Top-Level Div
This is the current structure in ratings.jsx:

Ratings and Reviews

    <Breakdown />
    <ReviewList />

Is there a reason for the outer
? If not, you might want to remove it, make the ratings-reviews
 the top level, and move the
 inside it.
I mention this because it seems like we should aim for a final rendered DOM where all the top-level component divs are siblings just one level below app like this:

...
   <-- overview

...
   <-- related products

...
   <-- questions and answers

...
   <-- ratings and reviews

React styles
A minor thing, but I noticed the filename ratings.jsx is lower case and the rest are Pascal case. I've been using all lower case but realized that's probably weird, so I googled and found that React has no opinion on it, but it's more common to Pascal, and AirBnB does in their style guide:
https://airbnb.io/javascript/react/
If everyone else is cool with it, we could conform to ^this guide to keep everything looking like one team wrote it. If so, all our JSX filenames will need to be Pascal case.

Is there a reason for the outer
? If not, you might want to remove it, make the ratings-reviews
 the top level, and move the
 inside it.

I wrote my divs like that as a quick way to keep my title separate from my content layout. I just made a div to wrap it all together because initially my styling was putting everything on the same row.

I agree that's how our layout should be in app and I refactored my code. Hopefully it looks a little bit cleaner!

A minor thing, but I noticed the filename ratings.jsx is lower case and the rest are Pascal case. I've been using all lower case but realized that's probably weird, so I googled and found that React has no opinion on it, but it's more common to Pascal, and AirBnB does in their style guide:

I'm cool with following the AirBnB style guide. I went ahead and changed ratings.jsx to Reviews.jsx to be more consistent with how this widget is named in our deliverables tracker. I was keeping that file lowercase in order to avoid merge conflicts, but it did look a little weird the way it was. There is also an ESLint config for the AirBnB styling if we want to go that route - https://www.npmjs.com/package/eslint-config-airbnb


deno^2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

11 of 11 (100.0%)  changed or added relevant lines in 6 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.3%) to 91.741%

Files with Coverage Reduction
New Missed Lines
%

src/utils/execve.ts
1
85.63%

src/modes/integrate.ts
2
95.56%

src/modes/shellcode.ts
2
86.36%

Totals

Change from base Build<PHONE_NUMBER>1:
0.3%

Covered Lines:
1474

Relevant Lines:
1606

💛  - Coveralls


add blog post for face blinder

blog for face blinder

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


Qiskit wrapper

This is the same modification as in https://github.com/pyRiemann/pyRiemann-qiskit/pull/2, but with the commit history.
Blocker:
https://github.com/pyRiemann/pyRiemann-qiskit/pull/1
Reference Issue:
pyRiemann/pyRiemann#141

Since pyRiemann-qiskit uses pyRiemann as dependency, IMO, it is better to do not inherit the long commit history of pyRiemann.
So, I prefer #2. @gcattan, are you ok to close this PR?

Sure, I understand :)


Fixed old releases not being cleaned up when keep_releases reduced by than half.

Q
A

Bug fix?
Yes

New feature?
No

BC breaks?
No

Deprecations?
No

Fixed tickets
Side effect noticed after fixing #1004 #1036

If as a user reduced their keep_releases by more than half of the number of releases they have on their server, the oldest would be ignored and not cleaned up.
For example, if you have 100 releases on your server and reduce keep_releases to 20, only the most recent 45 releases would be read from the CSV. This would cause the oldest 55 releases to be ignored and not cleaned up.
The simple fix was to make sure it always reads as many lines from the CSV as there are release directories.

Nice solution 👍🏻


core-decorators broken with react-native 0.57.1 and babel 7.0.0.

I'm attempting to upgrade my project to react-native 0.57.1, due to a multitude of reasons and issues with the current versions of packages.
Seems core-decorators are broken by Babel 7 or something else is amiss.
I ran
react-native run-android

Same issue with run-ios on mac.
Essentially we only use @autobind on methods and these decorators seem not to work.
E.g.
import { autobind } from 'core-decorators';
export class MainScreen extends Component {
//...
  @autobind
  handleHardwareBackPress() {
  // ... doing stuff
  }
}

So this happens during runtime (i.e. the metro bundler finishes ok).

BTW, I tried using the replacement autobind-decorator package, but also get an error, seems Babel 7 isn't welcoming these decorators...
Any input would be appreciated.
My package.json
{
  "name": "my-project",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "@babel/core": "^7.0.0",
    "@babel/plugin-proposal-class-properties": "^7.0.0",
    "@babel/plugin-proposal-decorators": "^7.0.0",
    "@babel/plugin-proposal-export-namespace-from": "^7.0.0",
    "@babel/plugin-proposal-function-sent": "^7.0.0",
    "@babel/plugin-proposal-json-strings": "^7.0.0",
    "@babel/plugin-proposal-numeric-separator": "^7.0.0",
    "@babel/plugin-proposal-throw-expressions": "^7.0.0",
    "@babel/plugin-syntax-dynamic-import": "^7.0.0",
    "@babel/plugin-syntax-import-meta": "^7.0.0",
    "@babel/preset-env": "^7.1.0",
    "@babel/preset-react": "^7.0.0",
    "@babel/runtime": "7.1.2",
    "color": "3.0.0",
    "core-decorators": "0.20.0",
    "jwt-decode": "2.2.0",
    "lodash": "4.17.10",
    "lottie-react-native": "2.3.2",
    "moment": "2.22.2",
    "prop-types": "15.6.2",
    "react": "16.5.0",
    "react-native": "0.57.1",
    "react-native-bluetooth-status": "1.3.0",
    "react-native-fast-image": "4.0.14",
    "react-native-fcm": "github:evollu/react-native-fcm#e7f0ad935b79acf9e729da8d707807356ff1e178",
    "react-native-firebase": "3.3.1",
    "react-native-input-scroll-view": "1.7.0",
    "react-native-keyboard-aware-scroll-view": "0.5.0",
    "react-native-permissions": "1.1.1",
    "react-native-render-html": "3.9.2",
    "react-native-splash-screen": "3.1.1",
    "react-navigation": "1.5.11",
    "react-navigation-redux-helpers": "1.1.2",
    "react-proxy": "1.1.8",
    "react-redux": "5.0.7",
    "redux": "3.7.2",
    "redux-freeze": "0.1.5",
    "redux-logger": "3.0.6",
    "redux-persist": "5.10.0",
    "redux-thunk": "2.3.0",
    "reselect": "^3.0.1",
    "urbanairship-react-native": "^1.6.2",
    "urijs": "^1.19.1",
    "validator": "^9.4.1"
  },
  "devDependencies": {
    "@babel/core": "^7.0.0",
    "@babel/preset-flow": "^7.0.0",
    "babel-core": "^7.0.0-bridge.0",
    "babel-jest": "23.6.0",
    "babel-plugin-transform-decorators-legacy": "1.3.4",
    "jest": "23.6.0",
    "metro-react-native-babel-preset": "0.47.1",
    "react-test-renderer": "16.5.0",
    "redux-devtools-extension": "2.13.2",
    "redux-mock-store": "1.5.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

My .babelrc
{
  "presets": [
      "module:metro-react-native-babel-preset",
  ],
  "plugins": [
    ["@babel/plugin-proposal-decorators", {"legacy": true}],
    "@babel/plugin-proposal-class-properties"
  ]
}

BTW, this works just fine with old react-native, see my OLD package.json:
{
  "name": "my-project",
  "version": "2.0.6",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "./node_modules/.bin/jest --silent",
    "test:debug": "./node_modules/.bin/jest --debug",
    "test:watch": "npm test -- --watch --silent",
    "test:debug:watch": "npm test -- --watch",
    "test:e2e:init": "detox test -c ios.sim.release",
    "test:e2e:init:debug": "detox test -c ios.sim.debug --loglevel verbose",
    "test:e2e:build": "detox build -c ios.sim.release",
    "test:e2e:build:debug": "detox build -c ios.sim.debug",
    "test:e2e": "npm run test:e2e:build && npm run test:e2e:init",
    "test:e2e:debug": "npm run test:e2e:build:debug && npm run test:e2e:init:debug",
    "lint": "node_modules/.bin/eslint src/**/*.js",
    "setup-api": "node ./scripts/setup-api.js",
    "setup-meridian": "node ./scripts/setup-meridian.js",
    "setup-urbanairship": "node ./scripts/setup-urbanairship.js",
    "setup-e2e": "node ./scripts/setup-e2e.js",
    "setup-firebase": "node ./scripts/setup-firebase.js",
    "setup-push": "node ./scripts/setup-push.js",
    "setup": "npm run setup-api && npm run setup-meridian && npm run setup-urbanairship && npm run setup-e2e && npm run setup-firebase && npm run setup-push"
  },
  "dependencies": {
    "color": "^3.0.0",
    "core-decorators": "^0.20.0",
    "jwt-decode": "^2.2.0",
    "lodash": "^4.17.10",
    "lottie-react-native": "^2.3.2",
    "moment": "^2.22.2",
    "prop-types": "^15.6.2",
    "react": "^16.3.1",
    "react-native": "^0.55.3",
    "react-native-bluetooth-status": "^1.3.0",
    "react-native-fast-image": "^4.0.14",
    "react-native-fcm": "github:evollu/react-native-fcm#e7f0ad935b79acf9e729da8d707807356ff1e178",
    "react-native-firebase": "^3.3.1",
    "react-native-input-scroll-view": "^1.7.0",
    "react-native-keyboard-aware-scroll-view": "^0.5.0",
    "react-native-permissions": "^1.1.1",
    "react-native-render-html": "^3.9.2",
    "react-native-splash-screen": "^3.1.1",
    "react-navigation": "^1.5.11",
    "react-navigation-redux-helpers": "^1.1.2",
    "react-proxy": "^1.1.8",
    "react-redux": "^5.0.7",
    "redux": "^3.7.2",
    "redux-freeze": "^0.1.5",
    "redux-logger": "^3.0.6",
    "redux-persist": "^5.10.0",
    "redux-thunk": "^2.3.0",
    "reselect": "^3.0.1",
    "urbanairship-react-native": "^1.6.2",
    "urijs": "^1.19.1",
    "validator": "^9.4.1"
  },
  "devDependencies": {
    "babel-eslint": "^8.2.1",
    "babel-jest": "22.2.2",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-preset-es2015": "^6.24.1",
    "babel-preset-react-native": "4.0.0",
    "detox": "7.3.5",
    "eslint": "^4.18.0",
    "eslint-config-airbnb": "^16.1.0",
    "eslint-plugin-import": "^2.8.0",
    "eslint-plugin-jsx-a11y": "^6.0.3",
    "eslint-plugin-react": "^7.6.1",
    "expect": "^22.3.0",
    "jest": "22.4.4",
    "jest-fetch-mock": "^1.4.2",
    "react-test-renderer": "16.2.0",
    "redux-devtools-extension": "^2.13.2",
    "redux-mock-store": "^1.5.1"
  },
  "detox": {
    "specs": "e2e",
    "test-runner": "jest",
    "runner-config": "tests/e2e/config.js",
    "configurations": {
      "ios.sim.debug": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/my-project.app",
        "build": "xcodebuild -workspace ios/my-project.xcworkspace -scheme my-project -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build",
        "type": "ios.simulator",
        "name": "iPhone 8 Plus"
      },
      "ios.sim.release": {
        "binaryPath": "ios/build/Build/Products/Release-iphonesimulator/my-project.app",
        "build": "xcodebuild -workspace ios/my-project.xcworkspace -scheme my-project -configuration Release -sdk iphonesimulator -derivedDataPath ios/build",
        "type": "ios.simulator",
        "name": "iPhone 7"
      }
    }
  },
  "rnpm": {
    "assets": [
      "src/modules/ui/assets/fonts/"
    ]
  }
}

Please let me know if you had and resolved the issue or have a suggestion on how to approach this.

any solution for this ?

It's been a while since I've worked with react-native and babel. As I recall, I fixed my problem by removing all autobind annotations and binding all the methods in the constructor manually.
I used a python script and some regex magic to do most of the replacements.

Thank you!
I am using RN 0.61.5, react 16.9.0, and I solve the problem by adding this line to babel.config.js
"plugins": [
["@babel/plugin-proposal-decorators", {"legacy": true}]
}
Actually I got a clue from your babel.rc file configuration @kburnik posted here. (y)

Glad it helped. :-)
P.S. I think I had tinkered around with what you suggested but that didn't work out. That's why after a few hours, I decided to remove autobind.


Update with PPC/MIPS/ARM-musl new targets

Adds a few more bits and pieces
Compiler builds for these platforms:

powerpc-unknown-linux-gnu
powerpc64-unknown-linux-gnu
powerpc64le-unknown-linux-gnu
mips-unknown-linux-gnu
mipsel-unknown-linux-gnu
s390x-unknown-linux-gnu

New target libraries for these platforms

arm-unknown-linux-musleabi
arm-unknown-linux-musleabihf
armv7-unknown-linux-musleabihf

I had to update the linux-cross image a bit to fix some errors, I'll be pushing that up to the docker hub soon. I... am praying this works for beta, not entirely sure that it does.

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

Needs to also update the triples in build-rust-manifest.py

Great work, @alexcrichton !


feat(aggregator): Add support for multiple signers in input

Lets the aggregator accept receipts or input RAVs that are signed with other keys.
Helpful with dealing with the transition when rotating keys, or making sure that we can accept receipts signed by other signing keys belonging to the same Sender (multiple locations with different keys for example).
Fixes #205

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-11 of 52 (78.85%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 73.81%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tap_aggregator/src/server.rs
18
19
94.74%

tap_aggregator/src/aggregator.rs
23
26
88.46%

tap_aggregator/src/main.rs
0
7
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1364

Relevant Lines:
1848

💛  - Coveralls


Adding the photo--editor folder in the repo

Description
photo --editor is a Photo editor where one can flip(both horizontally and vertically),resize ,gray scale images
Checklist

[ ] I've been assigned an issue related to this PR.
[ ] I've used beautifiers.
[ ] I've made a README.md file for my Project.
[ ] The README.md file of my projrct contains Project title, Description, Use of project, Set up, Stack used and Output (Screenshots).

Related Issues or Pull Requests number
#230

@chicken-biryani  Please look into this pr

Your readme file should have the following details -

Introduction
Use of the project
Steps to use it locally
Screenshots (your screenshots doesn't seem to work)

Also, please add your project details to index.md file.

I've asked you to add your project details to index.md file as well. Please do that! Thanks.

@harshita2216 @chicken-biryani  I have made the fequired changes
Can u plz merge now

@harshita2216 @chicken-biryani  I have made the required changes
Can u plz merge now

I will merge it tomorrow after I resolve the conflicts. Don't worry!

Okay thanks

Okay thanks

It is difficult to resolve conflicts on the phone, hence I have only approved it for now.
It will be merged tomorrow morning positively. :)


Wrong category while suppressing message

I am working with visual studio for project building and warning resolution.
And for deployment purpose i am using azure pipelines.
suppression logic works in visual studio
but the azure pipeline does not recognize suppression in global suppression.
upon investigation i found that azure recognizes
[assembly: System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Performance", "CA1822:MarkMembersAsStatic", Scope = "member", Target = "

But when i am use visual studio suppression then it generates below code
[assembly: System.Diagnostics.CodeAnalysis.SuppressMessage("Performance", "CA1822:Mark members as static", Justification = "<Pending>", Scope = "member", Target = "

I am not able to figure out what to do and how to resolve this.
I am using visual studio version 4.8.03752
and for code analysis i am using VSIX extension named "Microsoft Code Analysis 2019"
Please provide some solution as i was not able to find any article related to this online.

@Kelvin-K -- thank you for your feedback.  It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.

https://developercommunity.visualstudio.com/content/problem/1027180/wrong-category-while-suppressing-message.html

@Kelvin-K -- Kelvin, thank you for posting that.


get the item Im over on before dropping on it

I want to know if there is a way to know over which item Im on (when ever the css dndDragover is on).
Or even better, is there a solution to change the ghost css when Im over a 'not-allowed' item?
Im trying to change my ghost div when Im over a not-allowed item but I dont know how to get the item Im over on

One basic thing to keep in mind is that your not dropping over a list item, but instead between two list items. The dnd-dragover callback does have a index variable you can use. However, the normal UX for native drag and drop is that disallowed target elements don't change at all.


feat:  total number of v3 stakers

Adds the total number of v3 stakers to the api

The total number of stakers shows sum of stakers per dApp, which is not correct since one person can stake on multiple dApps. Maybe I wasn't clear before and I am sorry. We are looking unique number of stakers.

It is now distinct stakers, fixed upstream https://github.com/AstarNetwork/dapps-staking-indexer-v3/pull/14


[GRADLE-3573] Gradle 3.1 jansi ClassDefNotFound

https://discuss.gradle.org/t/gradle-3-1-jansi-classdefnotfound/19978
Gradle Version: 3.1
Operating System and JVM version: Linux primarily any JVM
Is this a regression? If yes, which version of Gradle do you know it last worked for? Yes, worked in 3.0
With the upgrade to jansi 1.13 a native library now is attempted to be extracted from the bundled jar and then loaded into memory. Unfortunately, this can fail with Could not initialize class org.fusesource.jansi.internal.CLibrary if there is any issue loading that library.
By default this library attempts to extract itself to java.io.tmpdir, which can often be mounted under linux as noexec, and under those conditions it will fail with the "Could not initialize class org.fusesource.jansi.internal.CLibrary" error.
This error can be simulated on windows or linux by simply modifying the DEFAULT_JVM_ARGS for the gradle or gradle.bat scripts and setting -Djava.io.tmpdir=somedirectory-that-does-not-exist
Fortunately, there is also a -Dlibrary.jansi.path that can be set, as altering java.io.tmpdir is only the fallback if that isn't explicitly set to something.
The failure occurs in ConsoleConfigureAction.java as all other references to jansi classes do not trigger any native library loading. Ideally the library.jansi.path system property would be assigned just before the AnsiConsole.wrapOutputStream() calls. It seems that setting it to gradleUserHome makes sense, unfortunately the two existing classes that provide that lookup capability are not visible to the logging component at present (and they probably shouldn't be either).
Unfortunately, attempting to pass in system properties via gradle.properties doesn't work, and attempting to simulate with commandLine argument settings for system properties forces a daemon to start and the actual failure is not displayed other than the daemon failing to start.

Closing as delivered


Publish to Zen's theme store

There is already a Catppuccin theme on the theme store, though unofficial. I saw @IAmJafeth that you made https://github.com/zen-browser/theme-store/pull/626, curious why it was closed?

Hi @uncenter !
Thanks for bringing this matter to the table, updating the Catppuccin theme in the Zen Browser mod store it is definitely in my plans and I will use this issue to track the progress.
That first PR I created was kind of rushed and I did not took in consideration the maintainability of the theme, as it will require a separate Whisker template that will required maintenance along with the template of this repo.
I will require some time to re-structure it in a more straight forward workflow as the current Zen Mod structure only allows me to modify the userChrome.css and not the userContent.css.
May be submitting the Official Catppuccin theme in the store and having the userContent.css and modified Zen Browser logo as optional steps listed on the repository will be the way to go.
Currently I am busy writing a User Guide for the Zen Browser docs, but once I am done with it this issue will be my next objective in the list.
I will be adding some documentation and what I have done so far below in case someone would like to contribute to this:
Zen Browser Theme Preferences Documentation (Basically how to add settings to you theme)
My current implementation of the Catppuccin Theme for the Zen Browser's Mod Store


Update schema

add local git hooks
add commit analyze github action
fix backtick problems
update schema

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


Kitchen Sink: Development of  Quiz Website with API Integration

Describe the feature
I'd like to propose an issue for the development of a  quiz website that integrates with an API.
Pls assign this issue to me.
Additional information

[ ] Would you be willing to help implement this feature?

Hmm, sure thing!

Make sure to use Million.js though 😁

Hey there @BikramNarayan; any updates on this?

Hey there @BikramNarayan, any updates on this? I might need to close this soon.


Switch to dynamic js nodes

To current infrastructure uses a web server and opens a web browser.
With dynamic js node extension KNIME can be configured to open js/css files using it's bundled web browser.
This would make the nodes much simpler.

For example see https://github.com/knime/knime-plotly


Running Error

Hi, @tinghuiz ,
Thanks for releasing this package.
However, when I run through the following cell, I got this error
saver = tf.train.Saver([var for var in tf.trainable_variables()])
with tf.Session() as sess:
    saver.restore(sess, ckpt_file)
    pred = sfm.inference(I[None,:,:,:], sess, mode=mode)

My system is ubuntu 14.04, tensorflow 1.0 and python 3.5.
Any suggestion to fix this issue?
THX!

Reason found!
After reinstall the tensorflow 1.0, all the cells could run successfully


pandas.io.data doesn't work with hyphenated ticker names

Noticed that the pandas.io.data doesn't return the Data Frame on tickers having a '-' in the ticker name , for example: HINDUNILVR-EQ.NS, TATA-MOTORS.NS .
Any ideas ?

pls refere to pandas-datareader package


Partner skill level become 0

Reproduce:

Convert Save to Json - Level.sav
Save Changes - Level.sav.json (without modifying any pal data)
Convert Json to Save - Level.sav.json

All pals I have become Partner skill Level 0.
For reference,
"Level_before.sav" is the original save file.
"Level_after.sav" is the modified save file by PalEdit.
BF53333A4EADE7B865FBAE86F9024E8E.zip

same

Same here.
Anyone know where that value is storing in the file, so I can quickly fix my save?

Should be fixed with #0.431

Should be fixed with #0.431

Would this repair any saves done with the previous version?

Should be fixed with #0.431

Would this repair any saves done with the previous version?
You can already repair it. Just set rank to 1 and back to 0 for each corrupted pal.

@therysin alright. I changed something, so all your pals get auto fixed with the v0.44

If someone wants to give v.044 a try. Download current source and overwrite it with:
PalEdit.py
PalInfo.py

Thanks much <3

Thanks much <3

Welcome, drop some feedback please about your issues.

Doesn't change. Rank up cost is still 8. and partner skill change 0.
Current source / overwrite PalEdit.py, Pallinfo.py

can you upload your level.sav and name me one pal with this issue? If you got multiple of the same species, please add a nickname like Buggedpal or smh.

Confirming it works to change the partner skill to level 1, however the rank is 1 star (the partner skill is level 1 at zero stars). Also confirming that the partner skill works as it's supposed to (pals drop stuff when assigned to ranch).

Confirming it works to change the partner skill to level 1, however the rank is 1 star (the partner skill is level 1 at zero stars). Also confirming that the partner skill works as it's supposed to (pals drop stuff when assigned to ranch).

Don't quite understand that.

Also, in the previous version just want to point out that every pal was corrupted, not just ones that you edit.

Yh, that makes sense. Its a technical thingy. But v0.44 should fix every single pal. Did that work?

Confirming it works to change the partner skill to level 1, however the rank is 1 star (the partner skill is level 1 at zero stars). Also confirming that the partner skill works as it's supposed to (pals drop stuff when assigned to ranch).

Don't quite understand that.

Also, in the previous version just want to point out that every pal was corrupted, not just ones that you edit.

Yh, that makes sense. Its a technical thingy. But v0.44 should fix every single pal. Did that work?

Hopefully you can see what I mean in the image above. The star rank of the pal is zero, but the partner skill is at level 1. Your fix assigns a star rank of 1 to every pal(when the star rank should remain at zero but the partner skill should be at level 1).
Yeah the fix was applied to every pal.

Deleted my previous post, mistakes were made on my end.
Confirming that the partner skill rank restored to level 1 for all pals.
Thanks.

Backup Sav.zip
Two file. Original and PalEdit.
The pal I fixed(only edit 1 pal) add a nickname Buggedpal. but all creature rank up cost 8 and partner skill change to 0.

Backup Sav.zip
Two file. Original and PalEdit.
The pal I fixed(edit 1 pal only) add a nickname Buggedpal. but all creature rank up cost 8 and partner skill change to 0. oh, and I use preset worker.

Sorry was busy with another issue, join this discord pls. https://discord.gg/tqH8NE293C

Deleted my previous post, mistakes were made on my end.
Confirming that the partner skill rank was restored to level 1 for all pals.
Thanks.

great to hear, I can't delete your post. I have no mod permissions.

came to comment this about the pals partners skills and star level not only taking double but also not increasing. is there a way to get a notification when the fix is live?

came to comment this about the pals partners skills and star level not only taking double but also not increasing. is there a way to get a notification when the fix is live?

if you want, join https://discord.gg/tqH8NE293C and test v0.45


If no valid, up to date, price feed then....

No new shorts No forced settling No margin calls.
TODO: create test.

Let me see what I can do.

This issue was moved to bitshares/bitshares-2#27


[cli] key sync does not update the generated IDL type

the anchor keys sync command does does not update the generated typescript type file located in the target/types/program-name.ts
so in order to sync the key, users must run:

anchor keys sync to update the declare_id value
then rebuild the program via anchor build in order to regenerate the type

proposed solution
since anchor keys sync is already performing a regex replacement for the previous program id, this command should also replace other instances of the program id (including the generated type file)

We can easily implement this, but I don't think it would solve the problem because the user has to rebuild the program to update the program binary regardless, otherwise interacting with the program will fail with the DeclaredProgramIdMismatch error.

keys sync command's documentation mentions that it only changes the declare_id! pubkeys (can also be seen from the help message).
Making changes to the source code naturally requires everything that was generated from that source code to be re-generated, so I think informing the user to rebuild the program should be enough to resolve this issue.
FYI, program ids are synced automatically if Anchor.toml doesn't have localnet entries during the initial build (https://github.com/coral-xyz/anchor/pull/3023).

Making changes to the source code naturally requires everything that was generated from that source code to be re-generated, so I think informing the user to rebuild the program should be enough to resolve this issue.

Works for me :)


Witness all intermediate states before switching to new ledger builder

What does this mean? It's not relevant anymore?

Right


Windows based collection fails due to kubectl issue

Need to remove the C: part of the path otherwise the colon char is being trated like a namespace / pod according to
https://github.com/kubernetes/kubernetes/issues/77310

I'm still finding this doesn't work with kubectl cp
https://github.com/kubernetes/kubernetes/issues/77310#issuecomment-1530142017


Add new function support

Enhancement

LAST_DAY

LAST_DAY in month, like LAST_DAY("2022-09-10") -> "2022-09-30"
LAST_DAY("2022-02-19") -> "2022-02-28"
LAST_DAY("2024-02-19") -> "2022-02-29"

CALENDAR_WEEK

PATINDEX

Here's some more info on CALENDAR_WEEK -- the SQL function we need is the same as Vertica's WEEK_ISO.
The following 2 examples shows the difference between WEEK_ISO and Starrock's current WEEK function. The left column consists of unix-timestamps corresponding to the date range from 1/1/2001 to 1/1/2002, incrementing by 1 day. Most datapoints are off by one, but roughly once a week it exactly matches, so it's not a consistent addition.
 That gets closer but still see a number of diffs. For example:
WEEK_ISO
"1009324800000","52"
"1009411200000","52"
"1009497600000","52"
"1009584000000","52"
"1009670400000","52"

WEEK(TIMESTAMPADD(DAY,6,col))
"1009324800000","0"
"1009411200000","0"
"1009497600000","0"
"1009584000000","0"
"1009670400000","0"


Sum of a field in mongodb using php yii2 ex

I am using for yii2 mongodb extension. I want to get the sum of a field total from mongodb collection.
$query = new Query;
$rows = $query->select(['total'])->from('invoices')->where(['status' => 'Unpaid'])->sum('total');
But, I am getting zero every time, even though it is greater than zero. Is there any issue with my query?

Hello. I am wondering if this is bug, could you please offer advise.
Using the following command in Yii2
        $collection = Yii::$app->mongodb->getCollection('stats');
        $count = $collection->aggregate(
            ['$match' => [
                'unit_id' => 'c4c8'
            ]],
            ['$unwind' => '$value'],
            ['$group' => [
                '_id' => '$_id',
                'sum' => [ '$sum' => 1 ]
            ]]
        );

Getting this as an error msg...
"message": "'pipeline' option must be specified as an array",
When i do the following query in mongodb directly it is successful...
db.stats.aggregate(
	{$match : {
    		'unit_id' : 'c4c8'
    }},
	{$unwind : "$value" },
  	{$group: {_id: '$_id', 'sum': { $sum: 1}}},
  	{$group: {_id: null, total_sum: {'$sum': '$sum'}}}
)

Am i missing something or is there a bug?
Thanks
Regards
Dennis

@drawlusyk I have no idea what your code does but I can clearly see that you invoke the aggregate method incorrectly. It takes two arguments each of which is an array. You provide three arguments instead.


Tests/connection module within media package

Codecov Report

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

@@           Coverage Diff           @@
##             main      #47   +/-   ##
=======================================
  Coverage        ?   33.20%
=======================================
  Files           ?       10
  Lines           ?      798
  Branches        ?        0
=======================================
  Hits            ?      265
  Misses          ?      504
  Partials        ?       29

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 457a37f...d07d644. Read the comment docs.


Contested advisory: GHSA-rwqr-c348-m5wr / CVE-2022-33124

This hasn't landed in the PyPA advisory database yet, but we should probably either manually purge it or mark it as contested (if possible) when it does.
Context: upstream does not believe that this advisory corresponds to a meaningful weakness or exploitable state (and I agree): https://github.com/aio-libs/aiohttp/issues/6801
GHSA: https://github.com/advisories/GHSA-rwqr-c348-m5wr
CVE: CVE-2022-33124 (already marked as disputed)

I guess that's because the PyPI service is pulling from other sources as well?

FYI I think I've seen some mentions of the CVE database while translating Warehouse.

CVE: CVE-2022-33124 (already marked as disputed)

I believe you meant to link https://nvd.nist.gov/vuln/detail/CVE-2022-33124 and not the same GH Advisory as in the previous line.

We should also document how reverts and contested advisories should work within this repo.
PyPI only gets it's data from OSV, but OSV may be pulling from other data sources including GHSA.

I believe you meant to link https://nvd.nist.gov/vuln/detail/CVE-2022-33124 and not the same GH Advisory as in the previous line.

Ugh, that looks like GitHub being too clever: I actually didn't link to the CVE at all, but GitHub auto-linked to their own advisory. I'll fix that now.

I think we should just be able to populate the withdrawn date?  I believe we did it in the past for a loguru one.  I can try to find it a bit later

I think we should just be able to populate the withdrawn date? I believe we did it in the past for a loguru one. I can try to find it a bit later

+1. withdrawn is intended for cases like this. Perhaps adding a line to the README.md would suffice?

Looks like this "vuln" has finally made its way in: https://github.com/pypa/advisory-database/commit/596fad27a24cb2fa855dbd1236628f6262177015
I'll look at marking it as withdrawn.
CC @Julian

https://github.com/pypa/advisory-database/pull/169 should withdraw this on the PYSEC side. I still haven't heard anything from MITRE (and I suspect we never will).


nn/Sequential.lua:29: bad argument #1 (field padW does not exist) on Arch Linux

I've installed Torch7 with torch/distro, which also installed lots of luarocks including cutorch, cunn, and graphicsmagick. The compilation and installation went well with proper dependencies. The installation directory is /home/vbchunguk/torch/install/.
With previous version(the cuDNN version), it exited with error because I don't have cuDNN-compatible GPU. Now waifu2x doesn't need cuDNN anymore, so I tried to run waifu2x again, with hope. But the error occured:
$ primusrun th waifu2x.lua
/home/vbchunguk/torch/install/bin/luajit: .../vbchunguk/torch/install/share/lua/5.1/nn/Sequential.lua:29: bad argument #1 (field padW does not exist)
stack traceback:
    [C]: in function 'updateOutput'
    .../vbchunguk/torch/install/share/lua/5.1/nn/Sequential.lua:29: in function 'forward'
    /home/vbchunguk/waifu2x/lib/reconstruct.lua:19: in function 'reconstruct_layer'
    /home/vbchunguk/waifu2x/lib/reconstruct.lua:45: in function 'image'
    waifu2x.lua:36: in function 'convert_image'
    waifu2x.lua:116: in function 'waifu2x'
    waifu2x.lua:121: in main chunk
    [C]: in function 'dofile'
    ...nguk/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:131: in main chunk
    [C]: at 0x00405be0

I'm using GeForce GT 520M(CUDA compute capability 2.1) on laptop, and I used primusrun because the laptop is using Optimus. Is there a problem with not using Ubuntu?

Try update nn and cunn package.
This could be caused by version mismatch between cunn and nn.

I've updated cunn, but not nn. I updated nn and it worked well. Thanks!


Feat/gamma oauth2

This should only add production integration, It is possible to build in development mode, but gamma does not automatically add hubbIT as a Oauth2 client, this should be added once version 1.1 of gamma is released which will fix this.

The issue above has been fixed in #9a86bab


WIP: Always store primary email address into email_address table and also the state

This PR will always store primary email address into email_address table and also add is_primary column on that table.
Replace #13296 and fix #11251 and #10279
TODO: (next PRs)

[ ] Remove column email from user table

Codecov Report

Merging #15956 (9c57920) into main (7979c36) will decrease coverage by 0.00%.
The diff coverage is 55.07%.

@@            Coverage Diff             @@
##             main   #15956      +/-   ##
==========================================
- Coverage   44.06%   44.06%   -0.01%
==========================================
  Files         682      682
  Lines       82460    82417      -43
==========================================
- Hits        36338    36313      -25
+ Misses      40205    40190      -15
+ Partials     5917     5914       -3

Impacted Files
Coverage Δ

models/error.go
39.53% <0.00%> (-0.32%)
:arrow_down:

models/user_mail.go
50.23% <56.36%> (-0.15%)
:arrow_down:

models/user.go
53.39% <75.00%> (+0.23%)
:arrow_up:

models/gpg_key.go
51.42% <100.00%> (-2.09%)
:arrow_down:

modules/git/command.go
87.96% <0.00%> (-1.86%)
:arrow_down:

services/pull/pull.go
43.83% <0.00%> (+0.45%)
:arrow_up:

modules/log/event.go
61.79% <0.00%> (+1.88%)
:arrow_up:

modules/process/manager.go
75.30% <0.00%> (+2.46%)
:arrow_up:

models/list_options.go
43.47% <0.00%> (+8.69%)
:arrow_up:

Continue to review full report at Codecov.

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


DS - Checkbox - Add to linting pkg

Update the linting package to issue deprecation notices for the VASelector component.
Note: This ticket should be completed after all other essential tickets for creation of the component.
Acceptance Criteria

[ ] Update linting package to throw deprecation warnings for the following flagship component(s):
[ ] Create an alpha build to test in flagship it'll behave correctly
[ ] Update linting package version locally to be one minor version lower than the components package version that released the component (so on publish in main it'll align versions correctly)

@kellylein Since Checkbox and RadioButton are both covered by the VASelector component, the linting ticket for them need to be done at the same time. I'm going to close this ticket and modify #527 to cover them both once RadioButton is complete.


PEG VirtualBox does not assign CPUs

We pass the number of CPUs in
https://github.com/kairos-io/kairos/blob/9398bae848b0dcfb795e5e3f689244562fc7b648/tests/tests_suite_test.go#L125-129
But this does not propagate. It does work with qemu ...

Actually bug in the test suite of kairos, fixed in:
https://github.com/kairos-io/kairos/pull/692/commits/8b4d7e3234d2630b8c9f33425c24f3498444505f


W-12190419-DWv23PropertyFixes-duke

Writer's Quality Checklist
Before merging your PR, did you:

[ ] Run spell checker
[ ] Run link checker to check for broken xrefs
[ ] Check for orphan files
[ ] Perform a local build and do a final visual check of your content, including checking for:

Broken images
Dead links
Correct rendering of partials if they are used in your content
Formatting issues, such as:

Misnumbered ordered lists (steps) or incorrectly nested unordered lists
Messed up tables
Proper indentation
Correct header levels

[ ] Receive final review and signoff from:

Technical SME
Product Manager
Editor or peer reviewer
Reporter, if this content is in response to a reported issue (internal or external feedback)

[ ] If applicable, verify that the software actually got released

wrong repo, file was moved to dw 2.3


Infer blocks clang's stdout

Infer v0.12.0.
Some build systems (like Eclipse CDT's indexer or Waf) do something like clang -dM -E - to get a list of the compiler's implicit #defines.  The output goes to stdout.
But if one tries to do that with infer capture -- clang -dM -E -, the only output is
Capturing in make/cc mode...

A maybe interesting detail is that around v0.8 infer did print clang's stdout when given that command line, AFAIR. In fact, I used that way of working to use infer with my build system (waf), as seen in #316 .
So, is this a regression? Is there any way to get clang's stdout?
(The reason I'm going back to using the CC environment variable is because my build system now hides waf under a layer of scripting, so using infer run -- buildscript only gets me a ERROR: (Invalid_argument "Unsupported build command buildscript"). So I don't know whether the waf support that got introduced in #316 is still working. I suspect not, given that waf inspects the compiler's output to the mentioned command line)

For me clang -dM -E - on its own also blocks (waiting for stdin?). Is that the exact command you are using? Which version of clang is it? I tried with 3.8.1 and 4.0.0.

Sorry, I should have specified that you have to close stdin (with ^D) for clang to continue.
Clang on its own prints to stdout, but infer only prints its line.


Temporary change CREDENTIALS->CONFIGURATION

Due to lack of support of CREDENTIALS feature in the sandbox frame, this feature breaks Sandbox operation.
To work around this issue, the CREDENTIALS feature has been temporarily changed to CONFIGURATION.
This should be rolled back after CREDENTIALS feature support added to the sandbox frame.

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

The CREDENTIALS feature is now added to SandboxFrame and merged. Closing PR.


Add option for sorting imports in formatter

Partially fixes #3729

This change is

@orizi This is the simplest solution I could come up with from the current implementation. It looks like comments on top of use clauses are also associated with the SyntaxNode and moved togheter. Any suggestion for improving the sorting function, or if you think there's a better direction for tackling this, that would be helpful. Also, this simple solution is not addressing merging.


Finish Pipeline

This story may already be mostly complete, this story is to verify it. In order for this story to be complete the following must be true.
-The pipeline takes in a SQL query from portal for fresh data
-The pipeline must immediately act on this query and get the fresh data
-The pipeline must automatically analyze and flag the data, storing the flags in the database

I handled creating the query to select a service date's data, as there was some overlap with Issue #3 . Date range selection is performed via command line arguments, which will likely be revised when we have a better understanding of how Docker will interact with pipeline initiation.

Regarding the third point, #51 could probably taken care of here as well, if you want.

its done


PR: Make QtWebEngine Optional

Description of Changes
I've been involved with packaging on conda-forge for the last few years and unfortunately the situation for packaging QtWebEngine hasn't really improved.
I think Spyder is a REALLY important tool for those starting off with python and being able to co-install it in modern environments is also a really great asset.
However, ensuring that qt-webengine is updated is a constant challenge and we are having a hard time keeping up especially on windows and OSX.
I would really like to continue to recommend Spyder to users, but if there isn't a clear path toward compatibility with qt6 (for which we don't have the webengine plugin) it makes it a really hard sell.
The following patch would effectively silently disable the plugins that require WebEngine.
One modification I would like to propose is the addition of a flag for each plugin like:
REQUIRES_WEBENGINE

That way, plugins beyond help could declare themselves as requiring webengine and the main application would be able to disable them intelligently

[ ] ~Wrote at least one-line docstrings (for any new functions)~
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

The main visual difference is that by default the help tab no longer shows up:

Example showing matplotlib still working:

Issue(s) Resolved

Xref: https://github.com/conda-forge/qt-main-feedstock/issues/49#issuecomment-2148423663
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Mark Harfouche

One thing I would like to do, is to run the tests to ensure that this continues working. I'm not sure if it would be appropriate to add an other CI job, but I can look into it if you want.

Hey @hmaarrfk, nice to see you here and thanks for all your contributions during the last days! You said:

I think Spyder is a REALLY important tool for those starting off with python and being able to co-install it in modern environments is also a really great asset.

First of all, thanks a lot for your kind words. In what feels to be a Jupyter monoculture of GUIs to do scientific programming in Python, we really value them. And second, thanks for helping us to move forward to support Qt6.

However, ensuring that qt-webengine is updated is a constant challenge and we are having a hard time keeping up especially on windows and OSX.

Is this also a problem for Qt5?

I would really like to continue to recommend Spyder to users, but if there isn't a clear path toward compatibility with qt6 (for which we don't have the webengine plugin) it makes it a really hard sell.

That's a very good point and I agree with you.

One modification I would like to propose is the addition of a flag for each plugin like:
REQUIRES_WEBENGINE
That way, plugins beyond help could declare themselves as requiring webengine and the main application would be able to disable them intelligently

I really like this idea. Would you be ok with implementing it as part of this PR? If not, this is (of course) the right first step in that direction, so we'd merge it first and implement your suggestion in a follow up PR.

However, ensuring that qt-webengine is updated is a constant challenge and we are having a hard time keeping up especially on windows and OSX.

Is this also a problem for Qt5?

Generally yes.... the only reason that things have been "prompt" to update on the qt-webengine side is that Qt vendors so many of the dependencies. Its also what parts of webengine engine are depended on for users of conda-forge. Building "everything" is not a feasible target.

One modification I would like to propose is the addition of a flag for each plugin like:

REQUIRES_WEBENGINE

I really like this idea. Would you be ok with implementing it as part of this PR? If not, this is (of course) the right first step in that direction, so we'd merge it first and implement your suggestion in a follow up PR.

If you can choose the name of the attribute, then I can implement it this weekend.
Thank you for the rest of the review, I'll take a look at it "soon"

If you can choose the name of the attribute, then I can implement it this weekend.

I prefer REQUIRE_WEB_WIDGETS to make it easier to understand for people not familiar with Qt.

I feel like the plugin code should be more resilient in general to missing dependencies:

pygithub not installed
asyncssh
yarl: /home/mark/git/spyder/spyder/plugins/remoteclient/api/jupyterhub/init.py
aiohttp /home/mark/git/spyder/spyder/plugins/remoteclient/api/jupyterhub/init.py

I mostly bring this up because maybe you don't that added property?

Hello @hmaarrfk! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/app/mainwindow.py:

Line 772:80: E501 line too long (85 > 79 characters)

@ccordoba12, would the help plugin require qt-webengine if it only rendered plain text? I'm wondering if there could be some fallback solution in the absence of qt-webengine that could still leave the help plugin operable.

I mostly bring this up because maybe you don't that added property?

@hmaarrfk, we did. You can check our lastet setup.py (or meta.yaml in Conda-forge) and you'll see them declared there.
I think this problem only happens in development mode because in that case Spyder is not installed properly. So, you can run it in an env that doesn't contain all dependencies required in master.
A possible fix would be to do a required (not optional) deps check at startup in development mode and inform users if some are missing. @mrclary, do you have a bit of free time to implement that?

would the help plugin require qt-webengine if it only rendered plain text? I'm wondering if there could be some fallback solution in the absence of qt-webengine that could still leave the help plugin operable.

@mrclary, no, it doesn't. But I think the Help's UI would look like a bug if we'd only display its plain text mode. However, we can talk about that in a follow-up issue and decide what to do about that.

I think this problem only happens in development mode because in that case Spyder is not installed properly. So, you can run it in an env that doesn't contain all dependencies required in master.

yeah i get it.
I mostly was surprised to see the new features!!!! congrats!

A possible fix would be to do a required (not optional) deps check at startup in development mode and inform users if some are missing. @mrclary, do you have a bit of free time to implement that?

Shouldn't that already be reported on startup, regardless of DEV?
https://github.com/spyder-ide/spyder/blob/01140e19b96fd54648c4f6db0a3807c4d9697893/spyder/plugins/application/plugin.py#L134

Is there anything else that is required for this to be merged. I believe all the comments pertaining to this Ii mprovement have been addressed. Sorry I derailed the conversation bringing up other dependencies.

Shouldn't that already be reported on startup, regardless of DEV?

Sorry, I forgot about your comment @mrclary. That's right: we check for dependencies even in development mode. But that happens after the application starts. If there's a new dependency which is not part of the current env, and that dependency is imported before the app is instantiated, then Spyder will crash.
So, my idea is to run the dependencies check in spyder/app/start.py when in DEV and before creating the main window. If it fails, then we'd print a message to the console alerting users of the missing deps.


sbt 1.3.3

Codecov Report

Merging #211 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #211      +/-   ##
==========================================
+ Coverage   92.88%   92.96%   +0.08%
==========================================
  Files         135      135
  Lines        2403     2403
  Branches      128      128
==========================================
+ Hits         2232     2234       +2
+ Misses        171      169       -2

Impacted Files
Coverage Δ

...ala/hydra/kafka/services/TopicBootstrapActor.scala
100% <0%> (+0.99%)
:arrow_up:

...scala/hydra/kafka/ingestors/KafkaTopicsActor.scala
100% <0%> (+4%)
:arrow_up:

Continue to review full report at Codecov.

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

I just updated this to SBT 1.3.4