Ability to retrieve mean elements of any pair of bodies

While working on the circular restricted three-body problem, @DhruvJ22 realized that he needs the mean distance between 2 primaries, for example sun-earth, earth-moon, sun-mars, sun-jupiter, saturn-titan, etc.
Assuming a Keplerian orbit of one primary around the other, we could use poliastro.mean_elements.get_mean_elements(), which uses low precision ephemerides from erfa.plan94:
https://github.com/poliastro/poliastro/blob/70f37e7f7239c4c5b0bd2fbcb61b36c1c0a27372/src/poliastro/twobody/mean_elements.py#L10-L44
However, we need to generalize this function to other primaries. At the moment, "Approximate heliocentric position and velocity" values are given:
https://github.com/liberfa/erfa/blob/eb4c95dfc128fc893987330b5bf3c6413065eb53/src/plan94.c#L4-L14
Notice that this topic has been discussed in the past, see gh-864 and most especially gh-790.
Options:

Add an "attractor=Sun" parameter that could be changed to any other body. The problem with this approach is that we'd need to check if body.parent is attractor and otherwise give an error.
Allow the function to receive more bodies, and always retrieve the mean elements with respect to body.parent. We keep the signature unchanged, and we just allow more bodies. The problem is that erfa/plan94 does not have them, so we'd need to add some more logic based on Simon et al "Numerical expressions for precession formulae and mean elements for the Moon and the planets" (1994).

https://github.com/astropy/astropy/blob/3fc010a49d3257ab7fb78963f3dfbc030a4c4622/astropy/coordinates/solar_system.py#L47-L57

Read data from high-precision ephemerides, that have fewer limitations on the bodies that are available. This has the disadvantage that requires network access, and it might be overkill.
Hardcode some constants. Feels a bit hacky but it's also the simplest ones. I believe we'd either need (a) some authoritative sources to back our data up, or (b) if we invent some procedure ourselves, document it well.

Also, notice that before attempting any of this, it would be nice to have some extra bodies like the Jupyter and Saturn moons in poliastro.bodies.

I learned from informal sources that NASA GSFC uses the mean distance of two primaries by propagating them in an ephemeris model from 1900 AD to 2100 AD for some of their analysis using CR3BP and Bi-Circular Restricted 4BP.
It is important to remember that the results from CR3BP are dependent on the mean distance of the primaries. However, the results are not realistic as the gravitational effects of other planets/bodies, besides the two primaries, are not included. The model serves to design orbits or trajectories with some specific characteristics and with the hope that when they are differentially corrected in an ephemeris model the characteristics will be preserved. Thus, it doesn't really matter much if the mean distances are low or high precision values as for more realistic mission design the CR3BP results are used as initial guesses and then numerically corrected in an ephemeris model.
I think the best idea is to use Spicypy, or something similar, to propagate the systems of interest in ephemeris from 1900 AD to 2100 AD and get their mean distances. We ideally need to only do this once and then hardcode those values.
For now, I would rather just stick to having the Sun, planets, and the Moon. Include instructions that the users can use their own mean distance and mass ratio values with the CR3BP model. We can work on adding the other planet-moon systems in the future.

Thanks a lot for the explanation @DhruvJ22. I like the idea you propose, with a twist:
Our current get_mean_elements function is used in quite a few places, see:
https://github.com/poliastro/poliastro/blob/70f37e7f7239c4c5b0bd2fbcb61b36c1c0a27372/src/poliastro/threebody/soi.py#L51-L52
https://github.com/poliastro/poliastro/blob/70f37e7f7239c4c5b0bd2fbcb61b36c1c0a27372/src/poliastro/plotting/tisserand.py#L77-L78
https://github.com/poliastro/poliastro/blob/70f37e7f7239c4c5b0bd2fbcb61b36c1c0a27372/src/poliastro/plotting/_base.py#L266
https://github.com/poliastro/poliastro/blob/70f37e7f7239c4c5b0bd2fbcb61b36c1c0a27372/src/poliastro/twobody/orbit/creation.py#L485-L490
So, I think it's good that we keep that API. We can use it for the upcoming CR3BP code as well.
Then the question is: how do we generate a mean orbit from a set of observations coming from some propagation? And the answer is orbitdeterminator. @hornig I think it is not yet available on PyPI, correct? (shouldn't stop us from using it, but just checking)
So, the plan is to

Add a /contrib/compute_mean_elements.py script (outside of src since users are not expected to run it anyway) that reads the positions of several bodies (configurable) from 1900 AD to 2100 AD (configurable), fits an orbit using orbitdeterminator.kep_determination.ellipse_fit.determine_kep, and spits a simple CSV file containing (body_name, p [km], ecc, inc [rad], raan [rad], argp [rad], nu at J2000 [rad]) for each body.

Note that the true anomaly requires an epoch! Let's default to J2000

Run the script once locally for various bodies, and ship the resulting CSV file with the library.
Have poliastro.mean_elements.get_mean_elements(body, epoch) read the CSV file to produce a ClassicalState object.

How does that sound?

@astrojuanlu I think I understand your idea. I am not sure about where we should get the initial positions of the several bodies. Do we use spicypy to generate the 200 years of data and then use ellipse_fit.determine_kep to get a representative orbit?

I found an easy solution. Take a look at: https://ssd.jpl.nasa.gov/sats/elem/sep.html
We can just create a CSV using the 'a' of common systems and read from that. I think it is a solid source that we can rely on and does not require any further processing.
Also, see: https://ssd.jpl.nasa.gov/tools/periodic_orbits.html#/intro
It is a great tool built by one of the alumna of my research group that we can use to verify and list as an alternative to Poliastro. The Poliastro's version will be more helpful than the NASA tool as it will give the user more control and allow them to investigate the general dynamics and not just Periodic Orbits.

After discussing this in more depth, we realized that

All the use cases can be served just with the semimajor axis, and
Computing these mean elements ourselves is probably overkill

So we decided to create poliastro.constants.mean_elements and add the mean semimajor axis of all the major bodies and some satellites. Then I'll take care of replacing the uses of get_mean_elements() by that.

gh-1567 is merged, so we can proceed by replacing get_mean_elements() 👍🏽


Null coalescing operator (??) with string.Join is translated incorrectly

The following code should return a string by joining the string array values with semi-colon separators (ie. "1;2;3") -
public class Program
{
    public static void Main()
    {
        Console.WriteLine(Combine(new[] { "1", "2", "3" }));
    }

    private static string Combine(string[] ids) => string.Join(";", ids ?? new string[0]);
}

.. but the emitted JS for the method looks like this:
Combine: function (ids) {
    return ids || System.Array.init(0, null, System.String).join(";");
}

.. and so, for a non-null "ids" value. it returns the array straight back out.
It looks like there are some brackets missing, if it was translated into the following then it would work:
Combine: function (ids) {
    return (ids || System.Array.init(0, null, System.String)).join(";");
}

See deck.net/205005881530f3ed2881cb3b75fa2b83
I can work around the issue by replacing ?? operator with a null check but this could be a nasty bug for someone else to run into if something similar happens for other translations of that operator.

Fix merged upstream and available upon next Bridge release!


Ad support page

Feature Request: Add Support Us Page
Description:
We need to add a "Support Us" page to the website or project. This page will allow users to understand how they can contribute to the project, either financially or through other means (e.g., starring the repo, contributing to the code, etc.).
Proposed Solution:
Create a new page with the following sections:

Why Your Support Matters
Ways to Support Us:

Star the Project on GitHub
Contribute to the Code
Share the Project with Others
Donate or Sponsor the Project (if applicable)

Acceptance Criteria:

[ ] Page layout and content structure finalized.
[ ] Sections on how to support us, including links to GitHub, contribution guidelines, and donation options.
[ ] Styling consistent with the rest of the website (or project).
[ ] Page accessible through the main navigation or footer.

Additional Context:
Include links to the GitHub repo, contribution guide, and any donation/sponsorship platforms.

@jahnvisahni31 please assign this to me

GO AHEAD @Rizvi-Faiz


Network security group rules require a priority

In Microsoft.Network, the definition of SecurityRule does not list the priority property as required, but the Azure portal does and it seems to be actually required.

@thomas11 Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@thomas11 I am sharing the 2 examples here for the NSG creation:

Create network security group without custom Security rule

Create network security group with custom SecurityRule and priority

The latter, makes use of:

properties.securityRules
SecurityRule[]
A collection of security rules of the network security group.

Please let me know if this helps.

Hi @navba-MSFT, your reply unfortunately does not address my issue. You give one example without security rules, and one with security rules with priorities. But my question is about rules without priorities. I don't think that's allowed but according to the schema it is because the priority property is not marked as required. That should be fixed.

@thomas11 Thanks for clarifying. I tried to create a NSG security rule without the priorities and it failed as expected. So that means that the priority is a required field.  This is the API I invoked:
Sending you my Request body ( without the priority field):
{
  "properties": {
    "securityRules": [
      {
        "name": "rule1",
        "properties": {
          "protocol": "*",
          "sourceAddressPrefix": "*",
          "destinationAddressPrefix": "*",
          "access": "Allow",
          "destinationPortRange": "80",
          "sourcePortRange": "*",
          "direction": "Inbound"
        }
      }
    ]
  },
  "location": "eastus"
}

As expected, it failed with 400 Bad Request error with below expected error message:
{
  "error": {
    "code": "SecurityRuleInvalidPriority",
    "message": "Security rule has invalid Priority. Value provided: 0 Allowed range 100-4096.",
    "details": []
  }
}

Hi @navba-MSFT, thank you for reproducing. This is what I expected. Therefore, the priority should be marked as "required" in the API spec as I pointed out above. Unfortunately, I pasted a wrong link initially, apologies. This is now fixed. To reiterate, I think priority needs to be added here.

@thomas11 It seems like we have a check implemented at the service side for the priority field and if its missing the below error is being thrown. So irrespective of making it required or not, the check is happening.
{
  "error": {
    "code": "SecurityRuleInvalidPriority",
    "message": "Security rule has invalid Priority. Value provided: 0 Allowed range 100-4096.",
    "details": []
  }
}

Hi @navba-MSFT, I know the check is happening. But this is an issue on the azure-rest-api-specs repository, and it is about the specs, not the service. The field should be marked as required in the spec to match the reality of the service.

@thomas11 Thanks for your reply. I have created the above PR and it is currently under review.


Fix for issue 'unexpected end of input' and updated error handling

Hi,
When is this fix going to be merged into the master?

Hi SalvoLunar,
A similar bug fix for index.js has already been merged with #6, so you might be good to go...
But I also like this one, because it fixes not only stdout (like #6) but also stderr.
Plus, it displays a more verbose message in launch.R.
Br, Dr. MMu


how to update electron version to the new version

who can help me? update electron version to the Latest release v5.0.4

hey @heronggen check the answer here https://github.com/SimulatedGREG/electron-vue/issues/855 and especially the last comment https://github.com/SimulatedGREG/electron-vue/issues/855#issuecomment-503002257
and be sure to close this ticket if you got the answer you need

@linuxjuggler  Thanks very much


Avalonia.Controls.ToolBar.Demo Build Failure

Hello,
I've encountered a build issue with the Avalonia.Controls.ToolBar.Demo project and would like to seek assistance in resolving it. Below are the details of the issues I faced, along with the environment setup and steps I've taken to troubleshoot.
Issue Description
Initially, I received the following error when trying to build the project:
"Microsoft.PackageDependencyResolution.targets(266, 5): [NETSDK1004]"
I attempted a dotnet restore, which led to another error. It seems the issue might be related to MSBuild.

@seoyhaein I fix MSBuild issue, you can update main branch


Inscription metadata in rune deploy.

What if there was a way to do a inscription when a rune is deployed. You could inscribe the rune logo and additional metadata when a rune is created.

I think part of the goal with RUNE is to offload token related inscriptions.
This might encourage additional JSON metadata so if this is supported, maybe force a "rune" protocol specifier.

That’s too complicated to start IMO, we should wait and see how the community would handle metadata with existing ordinals infra first before considering another inscription envelope type. Simple and not over engineering is best especially for a fungible payment protocol.

Simple and not over engineering is best
Concept ACK :laughing:

Kidding aside, keeping the protocol tight is definitely a priority, but allowing for future protocol development without colliding with application specific or user-driven development would be a definite nice to have

User data push would be unstructured and purposefully not validated by Runestone (except in so much as Runestone allows it to exist without invalidating the protocol message as a whole).

I like this approach, and probably in the future when we do want to support a protocol push, the first varint in the protocol represent the protocol version starting with 0, so that we can continuously update protocol extensions (similar to segwit versions). Also, we can allow for skipping over the issuance push with a 0x00 op, so that protocol and/or user data push can be accessed without the need for issuance.

That’s too complicated to start IMO, we should wait and see how the community would handle metadata with existing ordinals infra first before considering another inscription envelope type. Simple and not over engineering is best especially for a fungible payment protocol.

Not a new envelope type, simply don't use "ord" otherwise we will just see prob JSON metadata inscriptions flood ord in addition to BRC-20, which is not ideal imo.

User data push would be unstructured and purposefully not validated by Runestone (except in so much as Runestone allows it to exist without invalidating the protocol message as a whole).
This let's us kick the can down the road without creating the same collision of concerns as we have in ord due to having a strict list of allowed values for protocol pushes and not caring about the content of the user data push.

I'm in favor of the idea of users pushing optional data. One suggestion is to push an inscription ID that references a JSON, like:
json
Copy code
{
"p": "runestone",
"symbol": "RUNE",
"logo": "<inscription_id>",
...
}
This would be purely for clients and indexers to easily retrieve metadata.

I'm in favor of the idea of users pushing optional data. One suggestion is to push an inscription ID that references a JSON, like:

Not a new envelope type, simply don't use "ord" otherwise we will just see prob JSON metadata inscriptions flood ord in addition to BRC-20, which is not ideal imo.

It would make more sense to use an inscription image reference that ID for the logo and then add metadata fields to that once metadata gets merged in ord for all the rest of the stuff.
https://github.com/ordinals/ord/pull/2421

I am strongly opposed to creating strong interconnections at the protocol level between runes and ord as they do not use any shared underlying tech (other than Bitcoin itself). One is UTXO-based with OP_RETURNs, the other is Ordinal-based with witness data.
If we are referencing the inscription(s) in user-data pushes whose content is not explicitly defined in the spec/protocol, then I very much like these ideas (especially eloc's comments about using metadata in envelope). This facilitates users to develop their own meta-protocol layer of interconnections to various other services (ord in this case), without the need for the protocol directly weighing in on what should be heavily-opinionated application-specific decisions.

I think Non-transferrable Artifacts (NTA) aka soul-bound tokens should be considered as contextually relevant here.
Ideally, a RUNE deploy pointing to some inscription(s) should not be inherently movable as per Ordinal Theory.
This is why I mention using a different protocol identifier if an inscription is part of a RUNE deploy TX. If not and point to existing inscription (within ord) then it is more acceptable since repurposes content such as a so-called ticker or logo. Still would be odd to be able to sell part of a RUNE object due to ord reference. Could always send ord inscription to burn address though. Overthinking perhaps. It's all wonky eod.

Why? What's the issue in transferring a RUNE deploy metadata? As long as inscription ID is constant, we should be good.

"Ideally" because it is wonky. Just something to think about at minimum. Normally, the metadata assets a token points to are not themselves tradable assets independent from the tokens. It is why BRC-20 inscriptions don't need Ordinal Theory except in cases where total supply is reserved and token never used (token deploy inscription + all tokens can be sold to new owner).
RUNEs does not need Ordinal Theory, but it still could make use of inscription envelopes, which are not inherently Ord specific.
This is more of a devil's advocate remark, since I have also suggested leveraging Ord inscriptions for tickers and metadata as well. There is nothing stopping people to add an inscription pointer (reveal TXID) if there is space allocated for it. But combining RUNE deploy with an Ord inscription in same TX would encourage Ord namespace use when it could just as easy be a new envelope protocol specifier (as a NTA envelope).
Either way, nobody will lose sleep over it. Just a fellow technologist injecting broad view design opinions.

This is done. When you etch a rune, if the same transaction reveals an inscription, the inscription is displayed on the /rune page. The meaning of such an inscription, e.g., if it is just metadata, or if the inscription itself represents the issuer and its transfer has meaning, is an open question.


 Needs to change the binary name.

Description

Fixes # (issue)
Type of change

[ ] Bug fix :bug:
[ ] New feature :sparkles:
[ ] This change requires a documentation update :book:
[ ] Breaking changes :warning:

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist:

[ ] I have :tophat: my changes (A 🎩 specifically includes pulling down changes, setting them up, and manually testing the changed features and potential side effects to make sure nothing is broken)
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] The test coverage did not decrease
[ ] I have signed the appropriate Contributor License Agreement

hi, @lobuhi ! Thank you for contribution. Can you please sign the CLA?

CLA completed!


[Impeller] Opacity peephole stops a bit too early on Impeller

import 'package:flutter/material.dart';

void main() {
  runApp(const MaterialApp(home: Example()));
}

class Example extends StatefulWidget {
  const Example({super.key});

  @override
  State<Example> createState() => _ExampleState();
}

class _ExampleState extends State<Example> {
  @override
  Widget build(BuildContext context) {
    // This does not require a subpass.
    // return ListView(
    //   children: <Widget>[
    //     for (int i = 0; i < 100; i++)
    //       Image.asset('assets/Tile.png', opacity: const AlwaysStoppedAnimation(0.5))
    //   ],
    // );

   // This does.
    return ListView(
      children: [
        for (int i = 0; i < 100; i++)
          Opacity(opacity: 0.5, child: Image.asset('assets/some_image.png'))
      ],
    );
  }
}

The listview isn't important, that just makes it easier to pump frames for the metal frame capture.

Given the following application, I'd expect that we could apply the opacity directly to the image. However, we stop a bit short and end up applying the opacity via a save layer that requires a subpass. Skia does not appear to use a subpass for this.

actually, I'm not sure if this is entirely wired up yet. If not, we should really do so now...

Fixed with a basic opacity peephole implementation


Net Neutrality Day of Action

July 12, shut down 5he site in tandem with the rest of the internet. See https://www.battleforthenet.com/july12/ for info. Be sure to register

Signed up, tools will be emailed.


Resolve Artifacts Fails on Windows

Describe the bug
resolveArtifacts for windows fails due to the failure of privilege's that are required to create a symbolic link.
Files.kt
 Exception in thread "main" java.nio.file.FileSystemException:  A required privilege is not held by the client.
        at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
        at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
        at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
        at sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(WindowsFileSystemProvider.java:585)
        at java.nio.file.Files.createSymbolicLink(Files.java:1043)
        at flank.common.FilesKt.createSymbolicLink(Files.kt:17)

To Reproduce
It was tested on two different windows 10 machines. Windows 10 Home(2004) & Pro(1903).
Both fail.
Reproduce by running it on Windows 10 native. Not a virtual machine.
Details (please complete the following information):
Tested on commit - a7380ff0f3f2a71251593932daefdbbd53291917
Activating developer mode on Windows 10 Pro does not alleviate the problem.
We may need to elevate the privilege's of the java process or investigate a way around this issue.
Ideas.

Do an actual File copy for windows instead of a symbolic link
Checkout the conditions of this flag SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE and which OpenJDK supports this
Elevate the user process so it can complete successfully for windows. (Maybe execute a separate bat file or some other way.)

It is possible to bypass the failure by simply copying the files from:
..\flank\test_artifacts\<unpacked artifacts>
to
..\flank\test_runner\src\test\kotlin\ftl\fixtures\tmp

I tried to reproduce on win 10 pro native machine and Win 10 pro on parallels but without effect. Did you try run resolveArtifacts from IntelliJ with admin privileges?


Load Testing

General Load testing, no clear specification at the onset of what is needed for this ticket, just generally known that we need so produce some sort of results for our potential users to show how much traffic this site can potentially handle under certain conditions and servers.

Re: from @astrosnat , Discord
Using pre- v0.0.3, deployed on Digital Ocean.

FYI https://docs.digitalocean.com/products/droplets/how-to/graphs/

Then...

Created +10 markets, for a total of 11 on https://openprediction.xyz/

This is running on Digital Ocean.
Specs for the box it's running on?
Suggest running a load test again, see where we are at, and then based upon the results of that test, increase the markets up to the point that is significant but perhaps doesn't break it yet, repeat until able to break the website.

Graphs & specs pre load test - 4GB RAM 80 GB basic hard drive Ubuntu 22.04 LTS
Thank you so much for doing this, load testing starts after coffee
Do you have an idea of what will be significant @pwdel? Like say a rough % of CPU usage or something?

Load testing with 10 markets: requests start to fail at around 100k requests total with a concurrency of 1000 (think 1000 users trying to access the site at the same time)
20240728_LoadTest3.csv
20240728_LoadTest2.csv
20240728_LoadTest1.csv
20240728_LoadTest3_logs.txt
20240728_LoadTest4_logs.txt
20240728_LoadTest4.csv
Here is how CPU usage etc. got affected:

OK so this means that there is a huge potential for improvement in serving static files.
That being said ... I wonder how geometric this would be. So if the markets/ page displayed 10X more markets, would that be the equivalent of 100 users accessing the site at the same time?
E.g., so does this mean we're only rated for displaying around say 200 markets on the front page, with 50 users simultaneously right now?
Or, the equivalent of 400 markets on the front page, 25 users (not that we would need 400 markets, but something equivalent, processing wise).
I don't necessarily see us needing to support 25 users with that much activity by say, September, but I could ask more from @jg-you and his class as a hypothetical. There could be a safety factor that we build in.
Just trying to think about project planning and whether it's worth it to build in, "serve static files for prod," right away now or keep it more as a dev product.

Well, I can create 90 dummy markets and see what happens. My feeling is that it makes sense to build in "serve static files for prod". I would be targeting ~100 scientists to use this - for example I could talk to the UK Reproducibility Network (a group of scientists focused on improving reproducibility) and the University of Sheffield metascience department. It also fits in pretty nicely with UKRI's new pivot to metascience. (UKRI is the umbrella research funder for the UK.)
Wonder if we could share the SocialPredict software with the Open Science Foundation too. I'm sure some OSF folks would be really into it.

So I didn't manage to create 90 extra dummy markets...I got up to about 50 and ran out of extra credits. And then when I tried to create a new account, this happened when trying to change its password:

Load testing today:
20240730_LoadTest2_logs.txt
20240730_LoadTest2.csv
20240730_LoadTest1_logs.txt
20240730_LoadTest1.csv

hey, I had already commented this on Discord but putting it here for posterity.
Get the logs from the various containers, probably frontend first, to see where that error came from. Post the error here when you can and we'll generate a ticket based off of that.
https://github.com/openpredictionmarkets/socialpredict/blob/main/README/LOCAL_SETUP.md#getting-logs-from-different-containers

20240802_ErrorLogs.txt
logs from frontend + backend

Load testing on openprediction.xyz after QoL fix to leverage vite build (PR #341)
1GB RAM | 25GB Disk
20240930_LoadTest5_logs.txt

20240930_DOMetrics.txt
(I'll make the metrics into a nice graph later)
20240930_LoadTest5.csv
10000 requests, 1000 requests at a time
Note: we are already at 32.1% disk usage, which might imply needing to resize the droplet at some point in time

Looks like less memory usage as well... down to ~55% of RAM from the previous 70%.

From Discord:

BrierFoxForecast ... using old version of master from late August:
Disk:

Memory:

CPU:

Just a quick update after having updated again, working on BrierFoxForecast, with SSL.


Health checks have not been running for helm

With a previous change from APP_URL to HELM_APP_URL in the pipeline, this caused health checks to silently not run. These changes should allow for APP_URL to be set for these tasks and get the required health check
See bottom of: https://cloud.ibm.com/devops/pipelines/tekton/5e8ca235-673d-47df-a0ca-79942bcdb07c/runs/1dce97a9-eb16-4689-bb52-fdc8d1ee612d/check-health/execute?env_id=ibm:yp:us-south

A successful run with a health check: https://cloud.ibm.com/devops/pipelines/tekton/5e8ca235-673d-47df-a0ca-79942bcdb07c/runs/be0de097-b7d5-40d1-88f9-389c98f761b3/check-health/execute?env_id=ibm:yp:us-south


Breaks on Swift 2.2 because it relies on non-existing private protocol _Strideable

In Sections.swift:
public prefix func == <T : _Strideable>(y : T) -> T -> Bool {
	return { x in x == y }
}

public postfix func == <T : _Strideable>(x : T) -> T -> Bool {
	return { y in x == y }
}

We are not 2.2 compliant yet (have to put out Swiftx's 2.2 support first).
This issue and #295 are related nonetheless.


fix: DEV-3341: selected=true  attribute is not supported for Taxonomy

/git merge master

/git merge master

fixed in https://github.com/HumanSignal/label-studio-frontend/pull/1239 with tests for cypress


Exclude temp tables from read-only access trigger

What
The trigger make_readable is executed on a number of CREATE commands and grants SELECT on all tables and sequences as well as USAGE on all schemata.
If a table is created within a stored procedure, this trigger does not return and keeps an AccessExlusiveLock on all tables. This is effectively globally locking the entire database for the runtime of the stored procedure, which may be substantial (The billing update_resources function runs for 2h+ in London).
This modification evaluates the schema_name of the pg_event_trigger_ddl_commands() to prevent the trigger from being
executed if a temporary table is created. As we are using temporary tables in the stored procedures this will prevent locking the database for their runtime.
We do not envision this change to impact the read-only functionality for tenants and read-only users should not need to access temporary tables - TBD.
pair: @whpearson @schmie
How to review

Code review
Change is deployed to dev env schmie: connect to a postgres db via conduit and see that create temporary table test_1 (idx int); does not output the chatter of the trigger, i.e. WARNING:  no privileges were granted for "sql_packages" etc.

Huh I didn't realize temp tables weren't excluded. Seems like a bit of a facepalm.

Also here's a tricky question: do you have a plan for updating the trigger in existing databases?

Also here's a tricky question: do you have a plan for updating the trigger in existing databases?
The trigger is updated on execCreateUser which in turn is called during any "Bind" - so restaging/re-binding the service would do it (or connecting via conduit, which is a little bit of a "surprise", but may be good enough?!).

Also here's a tricky question: do you have a plan for updating the trigger in existing databases?

It will create or update the trigger every time a user binds to the

I wonder if it would be good to consider doing it proactively to tenant databases. Many tenants don't do any of those things that would trigger its reintroduction frequently, and it's not as though we take many legacy considerations into account in the broker's test suite.
The case I'm worrying about is us rolling out a future change after this that appears a-ok according to our tests because our tests only test against fresh databases. But when applied to a database that has a legacy version of the trigger function... badness.

I wonder if it would be good to consider doing it proactively to tenant databases. Many tenants don't do any of those things that would trigger its reintroduction frequently, and it's not as though we take many legacy considerations into account in the broker's test suite.
The case I'm worrying about is us rolling out a future change after this that appears a-ok according to our tests because our tests only test against fresh databases. But when applied to a database that has a legacy version of the trigger function... badness.

Made a story to track this, #180633196

Yes yes please merge away

Whatever happened to this? I thought the only thing we were unsure about was how/whether to backfill the old DBs' sql?

Just waiting on the change freeze to thaw, it dropped off our radar.


Add Tiny JS

https://github.com/thoughtspile/awesome-tiny-js#readme
This is a list of small frontend libraries — mostly under 2Kb, with exceptions for select categories. Smaller frontend libraries help you build smaller apps, resulting in better user experience and fewer wasted resources. Apart from production usage:

A well-organized list of small libraries helps open-source developers focus their efforts on fields that are not already well-covered.
The cruft-free code of small libraries is an excellent learning material to understand how a class of libraries works — e.g. hyperapp source is a great overview of virtual DOM.
Many people put considerable effort into engineering size-conscious libraries, and deserve recognition for that.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

[x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
[x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[x] You have to review at least 2 other open pull requests.

https://github.com/sindresorhus/awesome/pull/2569#issuecomment-1493308363
https://github.com/sindresorhus/awesome/pull/2565#issuecomment-1493303277

[x] You have read and understood the instructions for creating a list.
[x] This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
[x] Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
[x] Your entry should be added at the bottom of the appropriate category.
[x] The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

[x] The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[x] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[x] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
[x] The default branch should be named main, not master.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)
[x] It's the result of hard work and the best I could possibly produce.
[x] The repo name of your list should be in lowercase slug format: awesome-name-of-list.
[x] The heading title of your list should be in title case format: # Awesome Name of List.
[x] Non-generated Markdown file in a GitHub repo.
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate. Please search for existing submissions.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
[x] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

[x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[x] Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

[x] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

[x] Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

[x] Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

[x] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
[x] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Does not use hard-wrapping.
[x] Does not include a CI (e.g. GitHub Actions) badge.You can still use a CI for linting, but the badge has no value in the readme.
[x] Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

unicorn

Wow

My first investment with Charlotte give me profits of over $7,000 and ever since then she has never failed to deliver and I can even say she's the must sincere broker I have ever known'' communicate with her to be a successful investor. On WhatsApp:+𝟭𝟰𝟳𝟱𝟮𝟰𝟮𝟲𝟯𝟯𝟴

It's really nice and clean list.
I just have a minor suggestion about the file names in the repo.
The casing is inconsistent where:

Some files are in uppercase, like: README.md.
Some files are in lowercase, like contributing.md .

You can use any, but my suggestion is to keep them consistent.

It's really nice and clean list.

Thanks, that's good to hear!

You can use any, but my suggestion is to keep them consistent.

Done, all lowercase now (casing changes are tricky in git)

Hey @sindresorhus, is there anything else I could fix or improve here? Otherwise, maybe it's time to merge.

Tweet: https://twitter.com/awesome__re/status/1659508021482127361

Thanks, and have a nice weekend y'all ❤


Assets folder

Hello.
It's my first time here. I don't seem to have an Assets folder in the bin\Max2016 folder

Hello
I make dir h2max in any dsk and it contains dirs:

x:\h2max:

assets
otl
tx

then set up them in h2max settinngs

hello,
please consider i am not a specialist. i don't understand what you are saying.

Yes, any name(which 3dsmax support) for dir to store assets and maxscript plugins

Please refer to "Houdini Engine Plugin Path (assets folder)" and "PATH environment variable" on InstallGuide_en.docx.
Thank you for help, ilayshp.


Unable to run cells when opening existing notebooks (even after running it before a reload)

Install Jupyter extension
Open a notebook, select Kernel A
Run a cell & confirm execution order changes to 1
Next Select kernel B
Run a cell & confirm execution order changes to 1
Close this notebook
Reload VS Code.
Open the same notebook.
Confirm Kernel B is selected on the bottom
Run a cell, it looks like (progress UI displayed) the cell ran.
But there are errors in the error log indicating that it could not.

Upstream https://github.com/microsoft/vscode/issues/123700
Users running into this https://github.com/microsoft/vscode-jupyter/issues/4941#issuecomment-839948482
@joyceerhl /cc

Isn't this the same as https://github.com/microsoft/vscode-jupyter/issues/5848?

Duplicate of #5848,


Export OSM file to shapefile

Hello Jochen, I installed osm-gis-export for exporting .osm.pbf files to shapefiles. Could you provide an example on how to do this? I have osm_gis_export_overview, osmium_toogr, osmium_toogr2 and osmium_toogr2_exp under the /osm-gis-export/build/src folder. Which one should I use? Thanks!

Sorry, currently you have to look at the source code and change it according to your needs. This software can be used as basis for your own experiments, but you need to understand C++ for that. There is no one-size-fits-all solution here. Use  osmium_toogr as a basis if you only need nodes or ways, no (multi)polygons. Use osmium_toogr2 as basis if you also need multipolygon support.


Exception on exporting to Excel with aggregation data when grouped column is numeric

When we run export with aggregation turned on and our grouping column is numeric, the exporter throws an exception because we try to add something like "1 Total (17)" to an Excel cell marked as "numeric".
We need to make that group footers cells for for grouping columns always textual.

Resolved in 1.4.2


Jenkins CPE found in empty project (With edited manifest)

Describe the bug
When jenkins and release strings are in Manifest file, jekins CPE for release plugin is found.
Version of dependency-check used
Tested with 6.1.1 and 6.5.3
To Reproduce
Steps to reproduce the behavior:

Create simple java project without any dependencies
Build it
Edit Manifest in jar file and add: Build-Tag: jenkins-test release-1
cpe:2.3:a:jenkins:release: is present in report

Expected behavior
I would expect jenkins CPE to not be present. Or have I misunderstood how this works?
Additional context
If instead of release, snapshot string is present, no cpe is found (I suppose snapshot plugin does not have vulnerabilities in jenkins, have not checked that)

The behaviour you describe is expected given how DependencyCheck works
The contents of the Build-Tag from your manifest get added as evidences (alongside other metadata) to try and derive the vendor/product that the jar represents. Upon searching for known CPEs it (wrongly) finds the jenkins release plugin as the best match for the evidences encountered in your project. (the full list of evidences encountered and considered you can find in the report)

@aikebah I wonder if we should allow the configuration of manifest entries to skip?

@jeremylong Might be good to allow users to set additional entries not-yet excluded by default.
Think such an additional skip would be more manageable than having to repeat all the already coded exclusions of manifest entries when all you need is one (or a few) more.

Thanks for the information. Such a skip indeed would be welcome. I suppose this can be closed.


Be able to execute shell commands

Summary
Being able to execute shell commands for example using child_process would be very useful.
Basic Example

const { exec } = require("child_process");

...
          exec("ls -la", (error, stdout, stderr) => {
            if (error) {
                console.log(`error: ${error.message}`);
                return;
            }
            if (stderr) {
                console.log(`stderr: ${stderr}`);
                return;
            }
            console.log(`stdout: ${stdout}`);
        });

Simple native implementation and binding
https://github.com/ospfranco/sol/blob/1b638b1facf61520c13cd47dfa62544363a078d6/macos/sol-macOS/lib/SolNative.swift#L92
https://github.com/ospfranco/sol/blob/1b638b1facf61520c13cd47dfa62544363a078d6/macos/sol-macOS/lib/ShellHelper.swift
Probably won't work with Sandboxing enabled though. So no, React Native probably shouldn't/can't implement this, also huge security vunerability for bad actors.

@ospfranco: Do shell commands work on sol?
It seems to me that you have done something with JSI, do you think it is possible?
@Saadnajmi : How come this command works /sbin/ping:

import {spawn, kill} from 'react-native-childprocess'

  useEffect(() => {

    const fetchData = async () => {

      cmdID = await spawn('/sbin/ping', ['google.com'], {

          pwd: "/",

          stdout: (output) => {

              console.log('>>>', output)

          }

      });

      console.log(cmdID)

    }

    fetchData()

      .catch(console.error);

  }, [])

However, any different command does not work.
Like ls or pwd don't work.
Maybe a set of commands found in /sbin work.

react-native-childprocess seems to be a rewrite of child_process as a react native module is why it works


[Bug]: Cannot submit new form

What happened?
Visit form page shows error:
Property type not supported in Livewire for property: [{"attributes":{},"request":{},"query":{},"server":{},"files":{},"cookies":{},"headers":{}}]

I also checked a demo form and got error https://demo.larazeus.com/bolt/diego
How to reproduce the bug
Create new form
Visit the form view page
Error thrown:
Property type not supported in Livewire for property: [{"attributes":{},"request":{},"query":{},"server":{},"files":{},"cookies":{},"headers":{}}]

Package Version
v2.0.1
PHP Version
8.2.8
Laravel Version
v10.20.0
Which operating systems does with happen with?
Linux
Notes

thank you for the report
I released a new version addressing this and will update the demo soon.
https://github.com/lara-zeus/bolt/releases/tag/v2.0.2
the issue is the HTML ID is required so I added a validation
but:
The error message is not shown since the field is on the inactive tab.
I will submit a bug report to Filament.
Thank you again

the demo is fixed now, feel free to reopen or create a  new issue if you still having issues :)

Can you provide a link to the bug report you submitted on Filament so I can follow it please?

I didn't have a chance to create a reproducing repo and submit a new issue, but there is one the same thing: #7474.

I think the errors are different. The error I reported is specifically a livewire error:
Property type not supported in Livewire for property: [{"attributes":{},"request":{},"query":{},"server":{},"files":{},"cookies":{},"headers":{}}]

it's not the same issue but related
The issue you mentioned is fixed here
The reason for the livewire issue is that I have:
$component->id($zeusField->options['htmlId'])

the htmlId is always required but there was no validation for it.
do you still having the same issue? tried the demo and the LW issue is fixed.

I created a reproduction repo that will help fix the bug: https://github.com/damms005/example-app-bolt
Login:
Username<EMAIL_ADDRESS>Password: password
Please go through the https://github.com/damms005/example-app-bolt#readme for steps on how to set up

thank you for doing this
I did clone and test
you need to go to /admin
http://<IP_ADDRESS>:8000/admin/forms/jupeb/edit
in the Contact Information section, the field Email doesn't have an htmlID:

if you write any random string, and save the form, then access it in the URL:
http://<IP_ADDRESS>:8000/custom-forms/jupeb
it will work

I think there's a better way to communicate this. You know you may not be able to address this issue for every single person that has this error. Maybe throw a descriptive exception? Thoughts?

I did address this issue, I made a fix: https://github.com/lara-zeus/bolt/releases/tag/v2.0.2
and the issue of not been able to see the error message is related to this: https://github.com/filamentphp/filament/issues/7474

Got ya. This is an awesome package. Thanks my man.


centralize submission methods in core

call_jenkins
argparser construction
retrieval of (new) models and benchmarks
sending user email

@kvfairchild another question: why do we catch all exceptions and just print them here? Why not let them be raised?


[Bug]: Cannot set default values with RESTful API create_table

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Version or Commit ID
v0.3.0-dev6
Other environment information
No response
Actual behavior and How to reproduce it
show_table_columns returns default values of each column. But I cannot set default column value with create_table:
 curl --request POST      --url http://localhost:23820/databases/default_db/tables/table_with_default      --header 'accept: application/json'      --header 'content-type: application/json'      --data ' {
       "create_option": "ignore_if_exists",
       "fields": [
           {
               "name": "name",
               "type": "varchar"
           },
           {
               "name": "score",
               "type": "float",
               "default": 5.0
           }
        ]
     } '

server=oatpp/1.3.0
code=500
description=Internal Server Error
message=[json.exception.type_error.305] cannot use operator[] with a string argument with number/string

Expected behavior
No response
Additional information
No response

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Is this bug fixed now?


[options] add an add flag for each embed flag

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[ ] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[ ] Covered the code with tests (note that PRs without tests will be REJECTED)
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
I sometimes download some songs with this program and, like with bash primitives, I forget which flag is embed and which is add for metadata and thumbnail. This PR just add an alias for --embed-subs and --embed-thumbnail replacing the embed word to add to solve this problem. Now if you want you can use all add instead of some add and some embed.

If doing this, probably also make --embed-metadata an alias for --add-metadata. However I am not particularly enthusiastic about these changes in general. Maybe make them but don't advertise them, as with deprecated options?

IDK for real, there is no conflict AFAIK to keep both.
Would even help because it could avoid confusion.
A deprecation may cause breakage and the cost of keeping both flags seems cheap.

Basically the more options we have, the fewer people will make it through to the part of the manual they actually need. So my suggestion was to make these secret aliases that you can use if you know them, but not to advertise them in the documentation.

Perfect
If someone got confused then the program will just magically accept it and carry on xD

The only --add... option that currently exists is --add-metadata. So why not just deprecate it in favor of --embed-metadata

Which would also match yt-dlp!
Given that, I'm happy to align the options.
However the yt-dlp manual hasn't been consistently updated to use --embed-metadata.


Quieter ouput on check-status

What enhancement would you like to see?
I would like to disable all warnings when using --check-status together with --quiet (that is the behaviour prior to issue #1026 ). It can be implemented as another flag (--quieter or --no-warnings)
What problem does it solve?
I am using a script with some failing scenarios being handled by the return code and I prefer a cleaner output, without the warnings.
Provide any additional information, screenshots, or code examples below:

Is this something that we want to implement? I know I would like this and I can work on it.


Command with Cucumber Tag and PAT Authentication

Hello,
I have already implemented a Cypress Cucumber Test Automation Framework running with all test scenarios each of them have one or more tags. Some Scenarios have the same Ticket Tag because I test them on different languages. On Bamboo I had solved this issue with a language Tag, so therefore I had 2 separate builds running one for each tag/language. Now I want to do the same with the cypress-xray-plugin, but I get a fail when running the command npx cypress run --env tags="@EN" JIRA_API_TOKEN="PATToken"  with the error: Error: Failed to configure Xray uploader: no viable Xray configuration was found or the configuration you provided is not supported.
What did I do wrong?
If I leave the tag out I get an error that I have multiple tests with same tag. Also I have an issue with another plugin cy-verify-downloads  which works perfectly in open mode.

Hey @alexviz7,
thanks for creating the issue. I don't think I fully understand it yet. Would you mind providing a minimal reproducible example containing your tag configuration?  You don't have to include step definitions or your real steps. I'm just a little bit confused still, especially about the tags="@EN" parameter. I assume this is a custom thing for choosing the subset of tags to include in a run? Without the example it's difficult for me to deduce why the plugin would be complaining about identical tags.

Error: Failed to configure Xray uploader: no viable Xray configuration was found or the configuration you provided is not supported

This error indicates that Xray wasn't properly configured. You seem to be using a server instance, which requires the JIRA_API_TOKEN environment variable (which you've set up) and the jira.url (see here). Can you double check if you've set up the URL?

Yes, thank you very much for the detailed example! I managed to set up a corresponding project myself.

[npx cypress run --env tags="@EN" JIRA_API_TOKEN="token"] has the following error:
Error: Failed to configure Xray uploader: no viable Xray configuration was found or the configuration you provided is not supported.

You've really set up everything properly. I think the issue is that you're separating the environment variables with a space, not a comma: https://docs.cypress.io/guides/guides/environment-variables#Option-4---env

[npx cypress run --env JIRA_API_TOKEN="token"] has the following error:
Multiple issue keys found in tags of scenario "View page footer and header": PRJ-2441, PRJ-2747

Multiple tags are pretty problematic, true. But what should the plugin do? Right now there's no way to tell it which tag to use. In such a situation, the plugin is facing a difficult choice:

upload the results to the issue of the first tag?
upload the results to the issue of the last tag?
upload the results to issues of both tags?

Simply throwing the above error is currently the user-friendliest way, I think. But maybe you've got an alternative solution/proposal? I'm definitely open for it.
Regarding the errors of cy-verify-downloads: I'm not quite firm in bundling topics, but have you tried adding nodepolyfills() to this bundler as well?
on('file:preprocessor', async (file) => {
  await syncFeatureFile(file);
  const cucumberPlugin = createBundler({
    plugins: [nodepolyfills(), createEsbuildPlugin(config)],
    //        ^^^^^^^^^^^^^^^
  });
  return cucumberPlugin(file);
});

This fixed the error for me, although I used a different polyfill package I think (I could not figure out which one you're using).

Wow, thank you it solved the issues with the cy-verify-downloads and the run command with the comma.
I still get the error of the multiple tags but the test run nevertheless.
However I get another issue now after the first feature tested the run stops with status code 405, most likely because i still have the cypress cucumber reporter configured:
`Running:  downloadUploadFiles.feature                                                    (1 of 42)
| Cypress Xray Plugin | INFO    | Synchronizing upstream Cucumber tests (cypress\e2e\features\downloadUploadFiles.feature)
| Cypress Xray Plugin | INFO    | Importing cucumber feature files...
| Cypress Xray Plugin | ERROR   | Feature file "[object Object]" invalid, skipping synchronization: AxiosError: Request failed with status code 405

  Download & Upload Files
    √ Download Effective Root Certificate (7801ms)

  1 passing (8s)

[mochawesome] Report JSON saved to C:\Projects\cypress\results\mochawesome_003.json

An error was thrown in your plugins file while executing the handler for the after:spec event.

The error we received was:

Error: ENOENT: no such file or directory, open 'C:\Projects\cypress\cucumber-json\cucumber-messages.ndjson'

Yeah, the multiple tags found error is not going to disappear, I'm afraid. The plugin just can't decide for you which tag to use.
The only thing I could think of right now is to provide a tag prefix in the configuration. Something like this:
await configureXrayPlugin({
cucumber: {
  featureFileExtension: '.feature',
  uploadFeatures: true,
  tagPrefix: "PRJ"
},

Would this help you? After changing your tags, you would then be able to provide prefixes through npx run --env CUCUMBER_TAG_PREFIX="PRJ-EN".

Regarding the upload: I cannot reproduce the error, unfortunately. I don't think the reporter is at fault, it should not influence the plugin. The 405 response is interesting, Xray's documentation states that it only returns the following codes on import:

400 BAD_REQUEST
401 UNAUTHORIZED
500 INTERNAL SERVER ERROR

Can you set plugin.debug to true in the configuration? This should create JSON files containing request data, such as the URL that was used to import the Cucumber file. It should look something like this in your setting:
https://devstack.jira.com/rest/raven/latest/import/feature?projectKey=PRJ

If this is correct, can you try replacing latest with 1.0 in the plugin's source code?
https://devstack.jira.com/rest/raven/1.0/import/feature?projectKey=PRJ

You can do it directly in the node_modules folder. Just change it in the following line in
node_modules/cypress-xray-plugin/src/client/xray/xrayClientServer.js:

Maybe this helps already. Otherwise I would need to add better debugging/logging output, I think.

⚠ Do not simply copy and paste entire debug payloads here for further analysis, as they will contain your credentials! ⚠

Hi I didnt try the debugging( maybe you can explain me where to set it),
however i managed to fix the issue of the stopping test run by removing the cypress-cucumber json creation from the package.json:

Now all test scenarios run even if they have same tags.
After the test execution is finished i see following info:
| Cypress Xray Plugin | INFO    | Uploading test results to https://devstack.com/jira/projects/PRJ/...
| Cypress Xray Plugin | DEBUG   | Writing POST request data to POST_https_devstack.com_jira_projects_PRJ_rest_raven_latest_api_import_execution_1687507965699_request.json.
| Cypress Xray Plugin | ERROR   | Failed to upload results to Xray: "AxiosError: Request failed with status code 405"
| Cypress Xray Plugin | ERROR   | Complete error logs have been written to "importExecutionResultsError.json"
| Cypress Xray Plugin | WARNING | Execution results import failed. Skipping remaining tasks.

Another issue i found out, that when I run the test with tag=EN I have new test tickets created even though all the scenarios have ticket numbers taged on them. Now i have to delete the doublicates from jira.

I'm glad to hear it was just the URL that required changing.

Also I found out if a ticket is closed then no result is shown. So I had some old tests that i had closed, now I had to reopen them.

Would you mind elaborating on this problem? I've never had to reopen issues before. Ideally, please provide steps to reproduce the problem.

Another issue i found out, that when I run the test with tag=EN I have new test tickets created even though all the scenarios have ticket numbers taged on them. Now i have to delete duzen dublicates from jira.

Yes, this is what I was trying to explain earlier in the comments (https://github.com/Qytera-Gmbh/cypress-xray-plugin/issues/79#issuecomment-1603005048, https://github.com/Qytera-Gmbh/cypress-xray-plugin/issues/79#issuecomment-1603281133). There's just no way currently for the plugin to know which issue you would like to reuse when providing multiple tags. Please consider the proposal I made in the last comment and if it would be an adequate solution for you.

Could you please check why the cypress cucumber json creation has to be deleted in order that the test run does not stop?

I investigated it. The situation is as follows:

the cypress-cucumber-preprocessor hooks into Cypress's before:run event: https://github.com/badeball/cypress-cucumber-preprocessor/blob/c6b40d3397899c75a41be71556f47d41a648f543/lib/add-cucumber-preprocessor-plugin.ts#L90

the hook then creates the folders where the report will be written to: https://github.com/badeball/cypress-cucumber-preprocessor/blob/c6b40d3397899c75a41be71556f47d41a648f543/lib/plugin-event-handlers.ts#L178

the cypress-xray-plugin hooks into Cypress's before:run event: https://github.com/Qytera-Gmbh/cypress-xray-plugin/blob/c2808fb4893a9152d5c5c54d31ed13587ae65c76/plugin.ts#L10

The big issue is that Cypress does not allow multiple hooks. The last function that hooks into the event will replace all the other ones: https://github.com/cypress-io/cypress/issues/22428. In your case, the cypress-xray-plugin hook won, preventing the cypress-cucumber-preprocessor from creating the output directory, resulting in your
Error: ENOENT: no such file or directory: 'C:\Projects\cypress\cucumber-json\cucumber-messages.ndjson' error.
Unless I (or Cypress) come up with a solution to this problem, you will need to decide between:

the JSON report of the cypress-cucumber-preprocessor
the upload of the cypress-xray-plugin

Both at the sime time is not possible. If you want to keep using the cypress-xray-plugin without having to delete your JSON configuration, make sure to omit the cucumber-preprocessor-plugin event handlers as described here: https://qytera-gmbh.github.io/projects/cypress-xray-plugin/section/setup/installation/#cucumber-support

This is also an issue for the scenarios with examples (Scenario Outline). When I have 5 examples 5 tickets are created. Can the ticket generation not be stopped in the xray or jira configuration?

This problem was fixed in v3.3.1. If exactly one tag is configured for a scenario, the examples won't result in superfluous Jira issue creation. However, the plugin does not yet support combining examples into a single data-driven test execution issue (as described here). I currently don't have the time for such a big undertaking, unfortunately. But it's definitely a necessary feature which will be included in a future version.
Can you check if you're on v3.3.1 or above?

The big issue is that Cypress does not allow multiple hooks. The last function that hooks into the event will replace all the other ones: cypress-io/cypress#22428. In your case, the cypress-xray-plugin hook won, preventing the cypress-cucumber-preprocessor from creating the output directory, resulting in your Error: ENOENT: no such file or directory: 'C:\Projects\cypress\cucumber-json\cucumber-messages.ndjson' error.
Unless I (or Cypress) come up with a solution to this problem, you will need to decide between:
* the JSON report of the `cypress-cucumber-preprocessor`

* the upload of the `cypress-xray-plugin`

Ok thanks, I ll take it in consideration which is more useful for reporting.

This problem was fixed in v3.3.1. If exactly one tag is configured for a scenario, the examples won't result in superfluous Jira issue creation. However, the plugin does not yet support combining examples into a single data-driven test execution issue (as described here). I currently don't have the time for such a big undertaking, unfortunately. But it's definitely a necessary feature which will be included in a future version.
Can you check if you're on v3.3.1 or above?

Yes i have this installed:  "cypress-xray-plugin": "^3.3.1",

Also the tagPrefix is not recognized.

Also the tagPrefix is not recognized.

Yes, the option does not exist yet. It was just something I came up with to discuss with you if that would be a solution to your problem.

The plugin does not retrieve Cucumber step information as of now, unfortunately. It will only upload screenshots/videos and set the corresponding status in Xray.

Thank you for the link, I actually did not know about that. This is very useful and highly interesting. I will report my findings in #87.
I will leave this PR open for some time, so that you can provide more examples whenever you find the time.
Apart from that, I'm sorry that the Cucumber integration isn't as fleshed out as the other parts of the plugin. The plugin was created more or less out of necessity, and Cucumber has not really been the main focus of that project.

Unless I (or Cypress) come up with a solution to this problem, you will need to decide between:

This is not true and can be achieved using cypress-on-fix.

If you don't want to keep using the cypress-xray-plugin without running into errors or deleting your JSON configuration, make sure to omit the cucumber-preprocessor-plugin event handlers as described here: https://qytera-gmbh.github.io/projects/cypress-xray-plugin/section/setup/installation/#cucumber-support. This will reduce the cucumber-preprocessor-plugin to running Cucumber tests only. No reports whatsoever will be generated anymore.

This documentation is misleading, for reason mention above.

Thank you @badeball, I did not know about cypress-on-fix. I will try it out and adapt the documentation accordingly! Sorry for any inconveniences or headaches the current setup has caused.

Sorry for any inconveniences or headaches the current setup has caused.

No inconvenience at all, I just want everyone to have the best experience.

This is not true and can be achieved using cypress-on-fix.

So according to this plugin it is possible to create a cucumber report and work with the xray plugin.
I haven't managed to make it work though.

@alexviz7 I think I'm going to close this issue, things like handling multiple Cucumber tags are out of this plugin's scope. If you (or future readers) still have issues, you should try to handle multiple tags manually as you see fit, for example by writing custom feature file parsers/preprocessors: https://github.com/Qytera-Gmbh/cypress-xray-plugin/issues/86#issuecomment-1620794137


Add Parallel_Attention_Blocks (3 of 3)

Summary:
This PR adds the main and final part for upstreaming Parallel Attention Blocks, specifically the actual Parallel Attn Blocks class itself.
This supports both MHA, MQA and GQA attention head setups.
RMSNorm has already landed and so can be used.
Cross Attention has been removed as requested.
Test plan:
Added 3 unit tests - one each for Parallel Attn Blocks using MHA, MQA and GQA.
Within each test, the number of query heads and number of KV heads are tested to ensure appropriate head counts (i.e. for GQA, num_KV heads is set to 2 and then verified.
From there, a Parallel Attn Layer runs a forward pass on a fixed single input tensor and the first row of the output is checked as is the attn_output shape.

Codecov Report
Patch coverage: 95.12% and project coverage change: +0.33% :tada:

Comparison is base (eed8716) 70.09% compared to head (7972d4d) 70.43%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #457      +/-   ##
==========================================
+ Coverage   70.09%   70.43%   +0.33%
==========================================
  Files         174      176       +2
  Lines       11940    12104     +164
==========================================
+ Hits         8369     8525     +156
- Misses       3571     3579       +8

Files Changed
Coverage Δ

...rchmultimodal/modules/layers/parallel_attention.py
91.66% <91.66%> (ø)

tests/modules/layers/test_parallel_attention.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Option to use router.replace in Link

This is especially handy if you only need to update the query in a link.
I try to keep as much state as possible in the url, I want to do this too for a small image gallery. Except it is quite inconvenient if you have to press back 7 times to go to the previous page after you watched 7 images.

This is intentionally not supported – <Link> shouldn't replace the location, just as <a> cannot.

Ah, ok. Thanks for the headup!

See https://github.com/ReactTraining/react-router/issues/3776


Fix Safari compatibility

We are very eager to get Safari browser support back in this library. This is an attempt at contributing a fix. Please let us know if there is something we can do, or do differently.
Fixes #142

<3 thank you!

In readme:

If you need to use this in the browser, use version 4: npm i normalize-url@4

Whether new version@^4 published?


Check fails when submodule path differs from submodule name

Currently the check at https://github.com/jtmullen/submodule-branch-check-action/blob/6c6f99f42640ce5247e478880be431940ad3c515/entrypoint.sh#L94-L95
and
https://github.com/jtmullen/submodule-branch-check-action/blob/6c6f99f42640ce5247e478880be431940ad3c515/entrypoint.sh#L119-L120
is incorrect---instead of checking if the path given to the action is the path of a submodule this checks if the path given is in the name of the key corresponding to the path. This happens to work in the event that the submodule is named the same (which is a common case), but breaks when it is not.
For instance, this can be reproduces with a structure like the following:
repo-root
├── .gitmodules
├── main-repo-content
└── submodule-dir
   ├── .git
   └── submodule-content

where .gitmodules is as follows:
[submodule "submodule"]
	path = submodule-dir
	url = <arbitrary>

which can be replicated by adding the submodule like so: git submodule add --name submodule -- $URL submodule-dir
Then a workflow like
  check-submodules:
    name: check submodule branches
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - name: Check submodules
        uses: jtmullen/submodule-branch-check-action@v1
        with:
          path: submodule-dir
          branch: master

results in an error like
Error: path "submodule-dir" is not a submodule on $COMMIT

Huh, yes this is definitely a bug. I thought that git config --file .gitmodules --name-only --get-regexp path was outputting the path but it would appear I never verified that.  I will have to get this fixed, quick test shows that the seemingly undocumented command git submodule--helper list actually gives out the path. So I will try to use that for a fix, or worst case just parse .gitmodules directly.

I believe you should be able to get the path with
git config --file .gitmodules --get-regexp path | awk '{ print $2 }'

without relying on undocumented features.

This should now be fixed in the latest release and on the v1 tag


Having troubles using ffjson on Windows

Hi,
I have set GOPATH=c:\ttt
And my project lives in c:\ttt\src\myproject\monitoring_event.go
When I'm trying to generate the encoder with the following command:
(current directory c:\ttt\src )  ffjson myproject\monitoring_event.go
I'm getting
Error: error=Rel: can't make \ttt\src\myproject relative to \ttt path="":
Same error message is my directory c:\ttt, or c:\ttt\src\myproject and the file is src\myproject\monitoring_event.go and monitoring_event.go respectively.
What am I missing/doing wrong?
Thank you very much!

I'm closing this. It seems it does not work from the windows cmd.
I ended up using git bash.


Proxy and client methods should return the response type when headers are present

today it simply returns SimpleResponse<BodyType>.

Already fixed


Add gather facts function

Gather sysconfig, and use that for the python location.
This allows for more future checks based on the jsonar sysconfig file (like based on current version, or current data dir)

Hi Chris, I think it is a good idea. I had few comments on the code and the test, please take a look on the main code comments before the tests comments.

Hi Everyone, @jsonar-cpapke @sivan-hajbi-imperva - what's left to be done for this PR before it gets approved/merged?

I approved it.
בתאריך 22 בפבר׳ 2024 15:57, Darya Abdollahzadeh @.***> כתב:
CAUTION: This message was sent from outside the company. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Everyone, @jsonar-cpapkehttps://github.com/jsonar-cpapke @sivan-hajbi-impervahttps://github.com/sivan-hajbi-imperva - what's left to be done for this PR before it gets approved/merged?
—
Reply to this email directly, view it on GitHubhttps://github.com/imperva/dsfkit/pull/383#issuecomment-1959503786, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4C5U2275U3FTEF44M4ZFH3YU5FFBAVCNFSM6AAAAABDFP43PWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGUYDGNZYGY.
You are receiving this because you were mentioned.Message ID: @.***>

This message is confidential. If you believe you received this message in error, please inform the sender and delete this message and all attachments.


Loading the FSAverageDataset causes a requests.exceptions.ConnectionError

Found while trying to solve #323.
The error arrises with this simple working example:
from kymata.datasets.fsaverage import FSAverageDataset

FSAverageDataset().download()

Temporary workaround is use a browser to download the files listed in the URLs in the error message, and move them into place manually.


Allow reuse of the functionality that checks for skaffold dependencies

How to categorize this PR?

/area dev-productivity
/kind enhancement
What this PR does / why we need it:
In the registry-cache extension we also had to specify ko dependencies in the skaffold file to workaround https://github.com/GoogleContainerTools/skaffold/issues/7836. See https://github.com/gardener/gardener-extension-registry-cache/pull/57.
We also forked the hack/check-skaffold-deps.sh script and adapted it for us.
This PR makes possible reuse of the core logic so that other extensions using skaffold (such as shoot-rsyslog-relp extension, cc @plkokanov) can easily reuse the logic for checking skaffold deps.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener-extension-registry-cache/issues/3
Special notes for your reviewer:
See example usage in https://github.com/ialidzhikov/gardener-extension-registry-cache/commit/7f47b4b822e98da2c4635ba82b1e5a3e896f5e02
Release note:

There is now a new script (`hack/check-skaffold-deps-for-binary.sh`) that can be used by gardener extensions to validate their skaffold ko dependencies.

/test pull-gardener-e2e-kind

/lgtm

/lgtm
/approve


Release steps to be automated in github action

Target
Automate the steps from https://github.com/SAP/xsk/wiki/Release-Process in a GitHub action.
Inputs should be:

Dropdown with options major, minor, micro

While studying github workflows, release process and corresponding git log, I've noticed few things that need improvement.
Docker images and buildpacks build and release process
currently, docker images are built based on separate artifact definitions described in POM files, even for slightly different versions.
Because of that, if some change is made to POM, all POM files have to be altered.
For myself I hit that rock while making standalone runtime server version, intended for testing and debugging deployment pipeline.
Issue created for that: #1644
Change a way of defining version
Currently version is hardcoded across POM files and is replaced all in one for each release making one big and quite irrelevant diff in commit. This approach have two downsides:

irrelevant entries in file change history makes it harder to manage code
every single build on forked or branched version have same version as on it is was forked/branched from, making it harder to understand what version of system is being used/deployed/tested/etc.

My proposal on it is described in issue #1645

As discussed yesterday, idea on release automation is to make it happen from github interface with options.
I checked up if it is possible to modify repo from within action.
It seems to be quite possible to add repo tag within action and to trigger release build action.

github registered release tag can be fetched with
curl --silent "https://api.github.com/repos/SAP/xsk/releases/latest" | jq -r .tag_name
v0.16.1

I believe there should be more handy way to do that from within github action, will look into it.

As I digged into the issue, I found several already existing solutions for github actions for that.
I'm currently hecking them out to see how it is actually working.

This issue is closed as the project is no longer maintained


Mixtral Instruct AWQ Quantization

System Info

CPU x86_64
GPU x4 A100 80GB
CUDA 12.1
TensorRT-LLM 0.8.0

Who can help?
@Tracin
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
I am using:
python3 ./quantization/quantize.py --model_dir /home/training/TensorRT-LLM/examples/mixtral/mixtral \
                                  --output_dir /home/training/TensorRT-LLM/examples/mixtral/mixtral-int4-awq \
                                  --dtype bfloat16 \
                                  --qformat int4_awq \
                                  --awq_block_size 128 \
                                  --kv_cache_dtype int8 \
                                  --calib_size 32

Expected behavior
Its supposed to create the config.json file and the tensor files
actual behavior
It give me a warning of unknown format .npz When I check the directory after it finished. Only two files present a .json and .npz that is only 3GB and doesn't match an AWQ quant size.
additional notes
I can replicate the logs but I would have to provision another x4 A100 and run the full quant to finish to be able to get them. Just let me know.

@christian-ci Thank you for the report. Currently, Mixtral does not support AWQ yet.


Set rel attribute when linkTarget is specified

This closes a potential security vulnerability. See the below for references.
https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-no-target-blank.md
https://mathiasbynens.github.io/rel-noopener/
Note that this isn't checking whether linkTarget returns "_blank" in the case that it's a function. Might be worthwhile to check though.

You might want to take a look at #350 which adds support for what you want to do.

Same answer as what this is a duplicate of: https://github.com/remarkjs/react-markdown/pull/350#issuecomment-705571004


feature: Add CoreRPC.Testing

So in the unit tests we can write:
public sealed class SecureRpcList : RpcListBase
{
    public SecureRpcList(string uri) : base(uri, new Dictionary<string, string> {["X-Auth"] = "foobar"}) { }

    public IRpcExec<SecureComputeRpc> Compute => Get<SecureComputeRpc>();
}

And then call the RPCs without explicit interfaces (e.g. exposed to TypeScript) like this (with FluentAssertions):
var secure = new SecureRpcList(address);
secure.Compute.Call(api => api.Sum(2, 2)).Should().Be(4);
secure.Compute.Call(api => api.Multiply(2, 2)).Should().Be(4);

ping @kekekeks


Tile Painting UI Icon not highlighted

Godot version:
3.1.1
Issue description:
When I flip the tile, there is no indicator that the tile is already flipped.
This is shown be default

This is shown when I flipped

I guess the flip icon should be highlighted like 3.0

CC @groud @YeldhamDev

I disagree, those icons are "actions" now, not "states" anymore.
In fact, those 4 action buttons change 3 different booleans behind the scenes, flipped_h, flipped_v and transposed. When transposed is true, the flipped_h and flipped_v impact the opposite axis, and since there is no way to display the transposed status here, displaying a status would be more confusing than helping. Also, I think the "clean transform" button, as enabled or not, does provide enough information.


Blacklist apps from GCM

See https://github.com/WhisperSystems/Signal-Android/issues/6895

The only way to test for the presence of GCM is to make the framework call that we're making, which MicroG is apparently returning true for. You can re-enable MicroG after registration and Signal will not attempt to use GCM.

Could this be implemented?

There's already this option in MicroG (I'm running 0.2.4-105):

Open the "microG Settings" app
Go to "Google Cloud Messaging"
Open Advanced settings (hidden behind three vertical dots)
Select confirm new apps
or you can unregister and/or disallow registration for existing (registered) applications

Tried that, but Signal still won't register. There's no GCM confirmation, no app added to microG's GCM list.
GCM off
10-20 20:50:22.427 16910 16957 W PushServiceSocket: Push service URL: https://textsecure-service.whispersystems.org
10-20 20:50:22.428 16910 16957 W PushServiceSocket: Opening URL: https://textsecure-service.whispersystems.org/v2/keys/
10-20 20:50:22.703  4066 26811 D GmsGcmRegisterSvc: onHandleIntent: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms (has extras) }
10-20 20:50:22.704  4066 26811 D GmsGcmRegisterSvc: registration not allowed
10-20 20:50:22.713 16910 16957 W RegistrationService:
10-20 20:50:22.713 16910 16957 W RegistrationService: java.io.IOException: SERVICE_NOT_AVAILABLE
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at com.google.android.gms.gcm.GoogleCloudMessaging.zza(Unknown Source)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at com.google.android.gms.gcm.GoogleCloudMessaging.register(Unknown Source)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.handleCommonRegistration(RegistrationService.java:249)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.handleSmsRegistrationIntent(RegistrationService.java:210)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.access$000(RegistrationService.java:60)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService$1.run(RegistrationService.java:97)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
10-20 20:50:22.713 16910 16957 W RegistrationService: 	at java.lang.Thread.run(Thread.java:761)

GCM on, confirmation enabled
10-20 20:52:27.790 16910 16957 W PushServiceSocket: Push service URL: https://textsecure-service.whispersystems.org
10-20 20:52:27.790 16910 16957 W PushServiceSocket: Opening URL: https://textsecure-service.whispersystems.org/v2/keys/
10-20 20:52:28.073  4066 26883 D GmsGcmRegisterSvc: onHandleIntent: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms (has extras) }
10-20 20:52:28.074  4066 26883 D GmsGcmRegisterSvc: No checkin yet, trying to checkin
10-20 20:52:58.071 16910 16957 W RegistrationService:
10-20 20:52:58.071 16910 16957 W RegistrationService: java.io.IOException: SERVICE_NOT_AVAILABLE
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at com.google.android.gms.gcm.GoogleCloudMessaging.zza(Unknown Source)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at com.google.android.gms.gcm.GoogleCloudMessaging.register(Unknown Source)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.handleCommonRegistration(RegistrationService.java:249)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.handleSmsRegistrationIntent(RegistrationService.java:210)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService.access$000(RegistrationService.java:60)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at org.thoughtcrime.securesms.service.RegistrationService$1.run(RegistrationService.java:97)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
10-20 20:52:58.071 16910 16957 W RegistrationService: 	at java.lang.Thread.run(Thread.java:761)

The "Registering with server..." part in Signal takes much longer to fail in the second case.

I was also facing this problem a few times. For now, the suggested workaround with completely disabling microG Services Core and reenabling it after Signal registration does the job.
But the fact that other apps like whatsapp and telegram manage to register even though GCM is present but disabled shows that there must be another solution test for working GCM... Maybe with Signal connection both with and without GCM to the server and checking what did work? I can only think of something like that, but I am not a dev

@amo13 How do you completely disable microG Services Core?  I'm using LineageOS + microG, so it's installed from the beginning.


extract-i18n doesn't  work when $localize is used server side

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[x ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
in AppServerModule (universal) I have  the following service provided
{       provide: MetadataService,       useClass: MetadataServiceServer     }
Using $ localize in that file does not produce any translation units.
🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.1200.5
@angular-devkit/build-angular     12.0.5
@angular-devkit/build-optimizer   0.1200.5
@angular-devkit/core              12.0.1
@angular-devkit/schematics        12.0.1
@angular/flex-layout              12.0.0-beta.34
@angular/localize                 12.0.5
@nguniversal/builders             12.1.3
@nguniversal/common               12.0.0
@nguniversal/express-engine       12.0.0
@schematics/angular               12.0.1
rxjs                              7.4.0
typescript                        4.2.4

Anything else relevant?

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.

running extract-i18n will extract message from BrowserServiceService, but not from ServerServiceService.
[https://github.com/manzonif/ng-extract-i18n-server](repro app)


Add option to support window padding

In cases where the window has areas that the dropdown menu should not cover - for instance a fixed header - it would be useful to have support for window "padding" to offset the selectOffset* calculations.
JSFiddle of problem.
Image of problem:

Implemented it in a fork. Discussion takes place in #1503.


Use LIBVIRT_DEFAULT_URI instead of VIRSH_DEFAULT_CONNECT_URI

VIRSH_DEFAULT_CONNECT_URI is deprecated and LIBVIRT_DEFAULT_URI should be used. [1]
[1] https://libvirt.org/uri.html#specifying-uris-to-virsh-virt-manager-and-virt-install

on my host the virt-copy-out fails not finding the vm as it was not using the VIRSH_DEFAULT_CONNECTION_URI. it works when setting LIBVIRT_DEFAULT_URI.

/lgtm
Meh... of course, we'd need to use multiple env vars, why only one that will be known by everyone? :)
That said, virt-copy-out is weird by itself, and may be replaced by some other command iirc. Anyway.

I'm not sure this was needed as it was fixed already in #158 by using -c, instead of relying on implicit env vars. If you were testing PR156 and saw this issue, you probably hadn't rebased it on master.
In fact, does this fix still work? Because now it looks like it will try and use -c with an unset env var:
https://github.com/openstack-k8s-operators/install_yamls/blob/master/devsetup/scripts/gen-edpm-compute-node.sh#L198

you are right, I missed to rebase. follow up PR in https://github.com/openstack-k8s-operators/install_yamls/pull/164


cert-manager: bump version to v0.10.1 for pending TOS.

Please provide a description for what this PR is for.
This is a version bump for cert manager to head off the impending termination of service for clients below v0.8.0.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ x] Configuration Infrastructure
[ ] Docs
[x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @Kampe. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I signed it!

We unfortunately don't really have any automated testing for certmanager. Have you done testing if this locally?
Because we aren't great at testing or maintaining our certmanager install here and we don't really do anything different we are planning on directing folks to the upstream installation. However, I think it's probably a good idea to upgrade now for the short term as people transition over.

I see! Well, I must admit it's not the most thorough testing, but can confirm it's working for my use case using istio-1.3.0.

Looking at release notes+latest changes I am not sure if just changing the image is sufficient. We may need to update CRDs https://github.com/jetstack/cert-manager/commit/71ccc0e72c0296a3297ee249e54393748bfbef7c#diff-078f40fa23e0672777adc7c05d4773dd RBAC rules https://github.com/jetstack/cert-manager/commit/d8d7d8fd0b1ebbd2611f0546e77e8b41d588b520#diff-078f40fa23e0672777adc7c05d4773dd and new features https://github.com/jetstack/cert-manager/commit/ec8df6d6df5dcd9ec0698820e4e33e51144902c7#diff-078f40fa23e0672777adc7c05d4773dd and probably many more

Those commits you linked are tied to the v0.11 tag.  I believe those changes are absent in v0.10.1.

I didn't get through all the commits back to 0.6. But it does look like
there are some backwards incompatible changes - see
https://docs.cert-manager.io/en/latest/tasks/upgrading/upgrading-0.8-0.9.html
On Sun, Sep 29, 2019, 4:09 PM Nick Kampe<EMAIL_ADDRESS>wrote:

Those commits you linked are tied to the v0.11 tag. I believe those
changes are absent in v0.10.1.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/17462?email_source=notifications&email_token=AAEYGXNHO4BS3MOHX7V4DQTQMEYRNA5CNFSM4I3NLCXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD74A7IA#issuecomment-536350624,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEYGXJVCAQMMMMCI7CBWBDQMEYRNANCNFSM4I3NLCXA
.

Maybe for time being v0.8 is a better candidate then


Task 757-760: msr_sqa dataset

Task 747-750: msr_sqa dataset
Given a passage in tabular format, generate a question | Question generation
Given a passage in tabular format and a question, generate a correct answer | Answer generation
Given a passage in tabular format, generate an incorrect answer | Incorrect answer generation
Given a passage in tabular format, generate a long text passage | Long text passage generation

Thanks for creating the PR. I have renamed it to task 757-760 as task numbers till 756 are taken in this PR https://github.com/allenai/natural-instructions-expansion/pull/307

@sarnshreya, tests are failing because of some formatting issue, can you fix?

Thanks for creating the PR. I have renamed it to task 757-760 as task numbers till 756 are taken in this PR #307

Oh, okay let me push the changes.

@sarnshreya, tests are failing because of some formatting issue, can you fix?

Done! Can you please review now?

@sarnshreya, tests are failing because of some formatting issue, can you fix?

Done! Can you please review now?

Yes, tests are passing now. Thanks!

Reviews: https://github.com/swarooprm/CSE576HW/pull/121

I have updated a bit of definition and explanation. These tasks look good to me @danyaljj

I am still not sure why we're using "passage" to refer to the input knowledge. If it's always a "table", why don't we use this term to refer to it?

I am still not sure why we're using "passage" to refer to the input knowledge. If it's always a "table", why don't we use this term to refer to it?

The given examples were in this format. So I thought to keep the structure uniform to comply with the code standards everyone else is using. However, I can push the changes as posted by you.

A couple of suggestions; leaving it here for @swarooprm to give it a 2nd look before merging.

@sarnshreya, any update?

@swarooprm, I will do it in a couple of days. I did some code changes for including the headers from the csv file, but it altogether disturbed the entire format of the input Passage. So, need just a couple fo days to fix it.