Owls87234 create start/stop managing namespace events in operator namespace

In the operator namespace processing workflow, when NamespaceWatchingStarted/Stoped events are generated in the domain namespace, the operator also generate corresponding Start/StopManagingNamespace events in the operator namespace.
In order to aggregate same events into a single event with a count, operator creates a watcher for events in the operator namespace, which is similar to the event watcher that the operator creates for domain events. Note that in Dedicated mode, the operator does not create the watcher.
In addition, the operator will never generate a StopManagingNamespace event since the domain namespace is the same as the operator namespace.
Jenkins job with this branch: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/3898/.
Jenkins job with develop branch: https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/3899/.
Both jobs had the same exact failures.

"In addition, the operator will never generate a StopManagingNamespace event since the domain namespace is the same as the operator namespace."
What is the reason for this? Thanks.

@alai8 The operator generates a StopManagingNamespace event when a namespace is removed from the targetNamespace list, or does not have the required labels, or does not match the configured regular expression that specifies the namespaces that the operator is supposed to manage. In the dedicated mode, the operator only manages its own namespace, and therefore, as long as the operator is running, it manages the namespace.

@alai8 The operator generates a StopManagingNamespace event when a namespace is removed from the targetNamespace list, or does not have the required labels, or does not match the configured regular expression that specifies the namespaces that the operator is supposed to manage. In the dedicated mode, the operator only manages its own namespace, and therefore, as long as the operator is running, it manages the namespace.

So we are not generating the StopManagingNamespace event for operator's own namespace in dedicated mode, but we will in other modes?

@alai8 The operator generates a StopManagingNamespace event when a namespace is removed from the targetNamespace list, or does not have the required labels, or does not match the configured regular expression that specifies the namespaces that the operator is supposed to manage. In the dedicated mode, the operator only manages its own namespace, and therefore, as long as the operator is running, it manages the namespace.

So we are not generating the StopManagingNamespace event for operator's own namespace in dedicated mode, but we will in other modes?

yes.

@alai8 The operator generates a StopManagingNamespace event when a namespace is removed from the targetNamespace list, or does not have the required labels, or does not match the configured regular expression that specifies the namespaces that the operator is supposed to manage. In the dedicated mode, the operator only manages its own namespace, and therefore, as long as the operator is running, it manages the namespace.

So we are not generating the StopManagingNamespace event for operator's own namespace in dedicated mode, but we will in other modes?

yes.

Just to be clear. Only if operator manages domains in its own namespace as well in other modes.


[Storage] Emit spans for elastic storage backend

First draft, aims to fix #1043
Which problem is this PR solving?

Context is passed, but spans are not emitted for the ES backend.

Short description of the changes

Create spans in calls to ES backend.

I'm restarting the CI for this PR, but I suspect the failure might actually be related to this change.

@jpkrohling the CI test has passed, could you review the changes?

pleas ensure full test coverage

Patch updated. @yurishkuro

Thank you, @annanay25 !
If you are using Jaeger in your organization, please consider commenting on https://github.com/jaegertracing/jaeger/issues/207.

@yurishkuro thanks! I'll look into the survey soon.


Joining collaboration sessions is taking a really long time (2+ minutes)

Describe what happened:
Tried connecting to a few different Liveshare sessions today, and the plugin is really struggling. VScode started eating 200-400% of my CPU, fans kicking up like wailing banshees, and the actual window is just super slow to connect. Of the 5 different sessions attempted, 1 actually loaded fully but that took 2+ minutes just for that initial connect and load.
Previously I've had no issues with the plugin, so I'm not sure what changed but it is super recent. This was working fine as early as 2 weeks ago for me.
Attempted system restarts, VScode restarts, plugin reinstall, cache wiping, etc. No changes.
What was your system configuration?
VScode
MacOS 10.15.7
LiveShare v1.0.3303
Language: Twig + Javascript
Steps to Reproduce / Scenario:

Click shared link from code session initiator
Sit, wait, and watch activity monitors as CPU goes insane indefinitely, even post session load.

logs.zip

Thanks for reporting this! Has anything else changed in your setup, since you started seeing this connection issue? Are you working on the same projects (or projects of equivalent size), and with people in similar distance from you? Also, did you happen to update your version of macOS recently? I only ask in order to rule out some of the obvious (but possible) factors. Thanks!

The only other thing that changed in my setup would have been MacOS point release updates for Catalina, but from testing I have no reason to believe that is the issue as someone else with the older version is experiencing the same issues (I had them check as well to recreate).
Working on exact same projects (wise range of size), same editor configs, and with the same people from the same locations from when it previously worked.
In 1 instance only, it was able to connect completely and the files/tree showed up. But it was hovering around 450% CPU usage non-stop over 10 minutes. This stopped as soon as I ended session. Every other connection attempt showed me as joined/joining on the host side, but on my end it was still trying to load tree/files and never completed. But no errors show up as to indicate it hit any kind of problems.
The same symptoms happened to my partner when I was hosting and they tried to connect to me. High CPU usage, hanging with no errors, not loading completely, etc. As a side note, connecting to sessions through the web VScode beta thing went fine. Not sure the configs on those machines.

We’ve made improvements in this area since this issue was filed. We believe this may have improved your experience and are closing this issue. If this issue still persists for you, please reopen the issue and let us know. Thank you.


Istio stable-mesh test is broken

Please refer to https://testgrid.knative.dev/serving#istio-stable-mesh.
Almost all tests became Red :skull: after https://github.com/knative/serving/commit/09986741f0bc6e369ed99370728ad715054656d5.

cc @mattmoor

I am suspecting this Istio's issue https://github.com/istio/istio/issues/23463. The DestinationRule and some behavior were different whether we have the port or not.

@nak3 I think this is fixed in 1.6?

cc @ZhiminXiang @JRBANCEL @Cynocracy

It is still broken.
The webhook Container of webhook Pod never gets ready (example), because the probes defined here:
2020-10-02T01:16:54.849646Z	error	Request to probe app failed: Get "https://localhost:8443/": remote error: tls: internal error, original URL path = /app-health/webhook/readyz app URL path = /
2020-10-02T01:16:55.347043Z	error	Request to probe app failed: Get "https://localhost:8443/": remote error: tls: internal error, original URL path = /app-health/webhook/livez app URL path = /

It might be an Istio issue, see this similar issue.

What seems to be happening is that Kubelet does indeed call the modified probes (on Istio Proxy) and then the proxy calls the Webhook probes, but this fails with the not useful remote error: tls: internal error.
I suspect that it fails because this is endpoint uses a self-signed certificate.

Istio skips TLS validation: https://github.com/istio/istio/blob/master/pilot/cmd/pilot-agent/status/server.go#L421
So it is failing for another reason. In the webhook logs I see 2020/10/02 01:20:23 http: TLS handshake error from <IP_ADDRESS>:55830: server key missing.
Someone complained about this recently: https://github.com/knative/eventing/issues/4165

Closing. There are still some failures but they are tracked by https://github.com/knative-sandbox/net-istio/issues/340.


Email form isn't working?

According to @maxwofford, this form isn't working. This issue is to investigate and fix

The form itself works, but the data gets added to the old https://github.com/hackclub/api database which was deprecated in favor of Airtable.
Since new events are added to Airtable (not hackclub/api), the event notification email itself is also currently out of commission.

Thanks @exu3 I think that's actually what he said and I misremembered. I'll edit the issue to match your details

Closed by #163


Update jdk in pipeline to temurin

Hi,
just a minor thing I've noticed: According to the docs of the setup-java action, one should not use the 'adopt' distribution anymore.
Quote:

NOTE: AdoptOpenJDK got moved to Eclipse Temurin and won't be updated anymore. It is highly recommended to migrate workflows from adopt and adopt-openj9, to temurin and semeru respectively, to keep receiving software and security updates.

I assume this can be simply replaced without any issues.

I've taken the liberty to open PRs, I'm not sure how the branching model in this project works, it will probably be enough to merge into main-dev, I assume. Feel free to close irrelevant PRs.


Context is undefined

Are there any on-going work in this area?
https://github.com/cobraz/pubsub-http-handler/blob/27fc1e08ca66993720996f9edd7bae9efd91340b/src/__tests__/fastify-plugin.test.ts#L31

I commented on https://github.com/cobraz/pubsub-http-handler/pull/178 now, regarding context.
Are there any requirements you have that should be taken into account?


Jest Unit tests only emit events when intializing full AppModule

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
When I assemble aTestingModule which does not resemble the full AppModule, my event listeners don't get registered at the EventEmitter
With this code:
const module: TestingModule = await Test.createTestingModule({
      imports: [EventEmitterModule.forRoot()],
      providers: [RecipesService, EventEmitter2],
    }).compile()

const app = await module.createNestApplication();
await app.init();

the events don't work,
If I initialize the complete AppModule like this:
 const module: TestingModule = await Test.createTestingModule({
      imports: [AppModule],
    }).compile();

 const app = await module.createNestApplication();
 await app.init();

the events work fine.
this is my AppModule:
 @Module({
  imports: [
    EventEmitterModule.forRoot(),
    RecipesModule,
  ]
})
export class AppModule {}

Minimum reproduction code

Steps to reproduce
yarn test
Expected behavior
Events should be emitted and listened to in both scenarios
Package version
1.4.1
NestJS version
8.4.7
Node.js version
18.10.0
In which operating systems have you tested?

[ ] macOS
[ ] Windows
[ ] Linux

Other
No response

Token EventEmitter2 not initialized provider. EventEmitterModule.forRoot() initialize provider by token EventEmitter2 and return EventEmitter2 instance.

Please provide a minimum reproduction repository (Git repository/StackBlitz/CodeSandbox project).

@kamilmysliwiec
Its my bad.
The problem is that by putting EventEmitter2 in the providers list, the emitter provided by EventEmitterModule.forRoot() gets overwritten by a new EventEmitter2 instance without any listeners. Sorry for opening this as a bug.

@DanielMenke Thank you so much for following up on this. I did the exact same thing in my event service and it was driving me nuts for days

@DanielMenke if possible can provide a snippet on how I can use it. I'm trying to a scenario where once the event gets triggered I want to test if the functions registered with @OnEvent gets called. I'm kind of stuck it would be nice if you can provide some snippet on how do did it since my mocks are not emitting the events as well as they don't have any listeners attached to them.

@BruceWayneTheSupermanSlayer I did it as shown above, with the slight difference that I didn't list the EventEmitter2 class inside my TestingModules provider-Array.
const module: TestingModule = await Test.createTestingModule({
      imports: [EventEmitterModule.forRoot()],
      providers: [RecipesService],
    }).compile()

INSTEAD OF

const module: TestingModule = await Test.createTestingModule({
      imports: [EventEmitterModule.forRoot()],
      providers: [RecipesService, EventEmitter2],
    }).compile()

I simply use my actual implementation inside my test case and only mock the parts that I don't really care about in the test scenario. Do you mock the parts of your implementation which call the emit functions?


Cursor position changes when formatting

Hope:cursor stays in its original position before format.
I format my code frequently so I need to return to the previous position manually every time.
Thanks for your working.This extension helpful for me!

thanks @moshiwu -- this seems like a bug.  It's worth noting that the desired cursor position will change due to formatting changes, so this is something we'll want to keep in mind when fixing it

Here's the relevant line: https://github.com/yieldmo/uncrustifier/blob/master/Uncrustify/SourceEditorCommand.swift#L58


Add devfile and community documentation to /public

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind documentation
[skip ci]
What does does this PR do / why we need it:
This moves the "upstream" documentation that we have here:
https://github.com/openshift/odo/tree/gh-pages/chosen-docs/upstream to
our main master branch to we have one central place for documentation
changes.
Which issue(s) this PR fixes:
N/A
How to test changes / Special notes to the reviewer:
N/A
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

@boczkowska can you please take a look at this?

I'm going to merge this in for now in order for @GeekArthur to push further changes to the devfile documentation. Also because the doc team is a bit busy at the moment.
If @boczkowska or @Preeticp could have a look at this at a later date, that'd be great. But as of right now, let's merge so we can push further changes / updates to the site with no blockers.


Driver crashes when using prepared statement from subclass

Thanks for releasing the Early Technical Preview for PHP 7! I tried out the Non Thread Safe version on PHP 7.0.2, but unfortunately it's crashing when I try to use a prepared statement from a subclass. Strangely, the crash doesn't occur if I don't call the parent constructor, or if I comment out the throw new Exception lines.
This is based on real-world code in the PeachySQL library.
<?php

$connection = sqlsrv_connect('Computer-Name\SQLEXPRESS', ['Database' => 'MyDatabase']);

$sql = "UPDATE Users SET name = ? WHERE user_id = ?";
$id = $name = null;
$stmt = new Statement(sqlsrv_prepare($connection, $sql, [&$name, &$id]));

$names = [
    7 => 'Michael J. Fox',
    8 => 'Christopher A. Lloyd',
];

foreach ($names as $id => $name) {
    $stmt->execute();
}

$stmt->close();

class BaseStatement
{
    public function __construct() {}
}

class Statement extends BaseStatement
{
    private $stmt;

    public function __construct($stmt)
    {
        parent::__construct(); // neither execute() nor close() cause a crash if I comment out this line
        $this->stmt = $stmt;
    }

    public function execute()
    {
        if (!sqlsrv_execute($this->stmt)) {
            // calling execute() causes crash unless I comment out the below line
            throw new Exception('Failed to execute statement: ' . print_r(sqlsrv_errors(), true));
        }
    }

    public function close()
    {
        if (!sqlsrv_free_stmt($this->stmt)) {
            // calling close() causes crash unless I comment out the below line
            throw new Exception('Failed to close statement: ' . print_r(sqlsrv_errors(), true));
        }
    }
}

What type of crashing were you experiencing? I am having issues with sqlsrv_query only with specific queries. I get the following error message: C:\Program Files (x86)\PHP\v7.0\php-cgi.exe - The FastCGI process exited unexpectedly
My issue is NTS too, so I am thinking these may be related.

I'm running the above code in a test.php file from the command line, and it crashes with a "CLI has stopped working" message:

@theodorejb - this has been absolute madness for me. Spent 6-7 hours trying to figure out what was causing it, because SOME queries worked.
I reinstalled from php scratch 3 times. If you are using php 7 from IIS web installer x86 I have the fix. (Fyi I even went the long route and did a manual install at one point, which was failing too)
The download checks to make sure you have the visual c++ runtime 2012 for x86. I did. I reinstalled this package over 7 times today, including other versions. I read numerous posts about this resolving it for others to no available for me. Finally I did the opposite.
You need to uninstall Visual C++ runtime 2012 and reinstall x64 .. That's right, x64 for x86 php. Every single query works, without a single crash at this point. I was getting an insane about of 500 errors before, and they were very inconsistent. Sometimes the same query worked, and upon refresh I'd get a 500.
Here is the link: https://www.microsoft.com/en-us/download/details.aspx?id=30679
Not sure if this is something we can say is specific to this driver or if it's the php.net team-- because they've been compiling in x64. Real strange.

@nickmccally : thanks for the update. This is not idea behaviour. We will investigate this and let you know when we have something to share.
@theodorejb : Does @nickmccally's hack solve your issue for now?

@meet-bhagdev No, I tried uninstalling all the Visual C++ runtimes on my PC and reinstalling the version @nickmccally linked, but the crash is still occurring.

@theodorejb: Where did you get the PHP 7 for IIS from? Did you get it from the WebPI (https://www.microsoft.com/web/downloads/platform.aspx)?

@meet-bhagdev No, I downloaded it from http://windows.php.net/downloads/releases/php-7.0.2-nts-Win32-VC14-x86.zip. Unzipped in C:\php and added the directory to path.

Before testing my above script, create a Users table like this:
CREATE TABLE Users (
    user_id int IDENTITY PRIMARY KEY,
    name varchar(50) NOT NULL
)

INSERT INTO Users (name)
VALUES ('Martin'), ('Emmett')

If the script runs successfully, it should update "Martin" to "Michael J. Fox" and "Emmett" to "Christopher A. Lloyd." However, for me it crashes PHP unless I comment out the parent::__construct() call or throw new Exception lines.

@theodorejb The version I linked has an option to select type. Did you select x64 on the type to download? The x84 and x64 download names were the same. (I played with these quite a bit and redownloaded several times)

@nickmccally Yes, I selected the x64 version, but it didn't fix the crash. Have you tried running the above script yourself to see if you can reproduce it?

This crash is still occurring with today's driver update on PHP 7.0.3.

@theodorejb We are aware of this and will aim to fix it. Will share an update once we have concluded our investigation and have a fix.

Closing this as the #4.0.2 release fixed this issue of the driver crashing while using the script above.


Link feature to existing child

More of a question than a problem, but I'm looking for a way to replicate the option in QGIS, to link a new feature to a existing child in a Relation setting.
Even if I keep the option toggled in QGIS, I can't find a way to access the option in QField.
I'm guessing this is not supported, but I'm asking just in case.

More details:
I have a geometry layer with a Relation to a second form. I would like to link multiple geometries to a single child (form).

Sorry, realized I'm in QFieldCloud here


support for gtx 1050 ti gaming x

dont know if this is still an active project, but it still seems to be the only solution to led control without the gaming app.

This Project seems inactive. I can suggest you to try my solution on my repo

On 12 Sep 2017, at 16:35, SamDenton<EMAIL_ADDRESS>wrote:
dont know if this is still an active project, but it still seems to be the only solution to led control without the gaming app.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Added fastapi to wic

This PR includes the following:

added api (fastapi)
integrated auth
added Dockerfile.api

FYI I'm still trying to figure out a way to test this new code, if possible.

FYI I'm still trying to figure out a way to test this new code, if possible.

you can test it locally by running uvicorn api:app --reload --port 3000. You will need to add an access token to your auth headers when making a POST request to route /compile.

I should have clarified that I was asking about how to incorporate it into the automated CI. We can probably still merge without, but if there's a way to do it without too much effort that would be excellent.


Fails to parse the GraphiQL introspection query

GraphiQL 0.13 is trying to run the following query against the API:
  __schema {
    queryType {
      name
    }
    mutationType {
      name
    }
    subscriptionType {
      name
    }
    types {
      ...FullType
    }
    directives {
      name
      description
      locations
      args {
        ...InputValue
      }
    }
  }
}

fragment FullType on __Type {
  kind
  name
  description
  fields(includeDeprecated: true) {
    name
    description
    args {
      ...InputValue
    }
    type {
      ...TypeRef
    }
    isDeprecated
    deprecationReason
  }
  inputFields {
    ...InputValue
  }
  interfaces {
    ...TypeRef
  }
  enumValues(includeDeprecated: true) {
    name
    description
    isDeprecated
    deprecationReason
  }
  possibleTypes {
    ...TypeRef
  }
}

fragment InputValue on __InputValue {
  name
  description
  type {
    ...TypeRef
  }
  defaultValue
}

fragment TypeRef on __Type {
  kind
  name
  ofType {
    kind
    name
    ofType {
      kind
      name
      ofType {
        kind
        name
        ofType {
          kind
          name
          ofType {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
              }
            }
          }
        }
      }
    }
  }
}

Error is as following:
{
  "errors": [
    {
      "message": "syntax error: unexpected \"{\", expecting Ident",
      "locations": [
        {
          "line": 36,
          "column": 11
        }
      ]
    }
  ]
}

Line 36 is type {, I think this might be caused by the library treating it as a special keyword. Running commit 8f92f34fc59823d34fc08bfdc9fd266b854e2b50, didn't happen before.

I just ran this against an old commit that in theory supported this and it failed. Maybe it's a GraphiQL change?

Oops, my reader was injecting some random characters.


Is there any way to set multiple 'transport_socket' to one 'cluster'?

In [config.cluster.v3.Cluster proto] , one "cluster" can have one "transport_socket" struct.
In my project, "Proxy-Protocol" and "TLS" are both important feature to one upstream cluster.
 cluster:
    transport_socket:
      name: envoy.transport_sockets.upstream_proxy_protocol
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.proxy_protocol.v3.ProxyProtocolUpstreamTransport
        config:
          version: V1
        transport_socket:
          name: envoy.transport_sockets.raw_buffer
          typed_config:
            "@type": type.googleapis.com/envoy.extensions.transport_sockets.raw_buffer.v3.RawBuffer

cluster:
 transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
        common_tls_context:
          validation_context:
            trusted_ca:
              filename: SOME-PATH

It seems that one "cluster" can only support one "transport_socket", but I think some "transport_sockets" are not incompatible. Just link TLS and Proxy-Protocol, the connection can be established via TLS, and then send message encrypted in Proxy-Protocol.
Is there any way to config TLS and Proxy-Protocol "transport_socket" feature to one upstream cluster at same time?
Thanks for help : )

check this out -> transport_socket_matches
BR,
Stoyan

check this out -> transport_socket_matches
BR, Stoyan

Thanks for replying. I have tried but it seems not work. "transport_socket_matches" configuration can use different transport sockets for different endpoints, but only one transport_socket configuration works at one time.
cluster:
    transport_socket_matches:
    - name: "tls"
      transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
          common_tls_context:
            validation_context:
              trusted_ca:
                filename: /data/flowcontrol/adc-proxy-certs/adc-proxy-ca.crt
    - name: "proxy-protocol"
      transport_socket:
        name: envoy.transport_sockets.upstream_proxy_protocol
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.proxy_protocol.v3.ProxyProtocolUpstreamTransport
          config:
            version: V1
          transport_socket:
            name: envoy.transport_sockets.raw_buffer
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.transport_sockets.raw_buffer.v3.RawBuffer

I use tcpdump to inspect TCP packets, it seems only "tls" can work, and "proxy-protcol" not work.

you need to match the transport socket to the endpoint metadata - you need two endpoints in your cluster: ep1:
{
    "metadata": {
           "filter_metadata": {
            "envoy.transport_socket_match": {
             "ts": "proxyprotocol"}

           }
    }
}

ep2:
{
    "metadata": {
           "filter_metadata": {
            "envoy.transport_socket_match": {
             "ts": "tls"}

           }
    }
}

BR, Stoyan

I hope that I can have only one upstream endpoint (e.g <IP_ADDRESS>:8080), and use "tls" and "proxy-protocol" feature at same time. When connection established, client and server exchange certificates and do tls-handshake (tls). Then client sends data with "Proxy-Protocol" header. Is it possible for envoy?
Thanks !


All alarms in the rule are silenced

I only have one rule, I want to make each alarm only generate once, and the repeated alarm is silent for an hour, but each time it seems to silence the whole rule? Why is that?
{
"_index" : "elastalert_status_silence",
"_id" : "gDpZd5ABVEXVlDRlmDgv",
"_version" : 1,
"_seq_no" : 0,
"_primary_term" : 1,
"found" : true,
"_source" : {
"exponent" : 0,
"rule_name" : "Prod Rule._silence",
"@timestamp" : "2024-07-03T06:47:58.744077Z",
"until" : "2024-07-03T06:47:58.744067Z"
}
}
There will be multiple different alarms in a rule, but it seems that the whole rule is silent.
name: Prod Rule
type: any
index: k8slog*
num_events: 1
timeframe:
minutes: 5
realert:
hours: 1

Read #11 . Issues are for verified software bugs, not for asking for support. Open a discussion.


Add go.mod file

go.mod file which both defines projects requirements and locks
dependencies to their correct versions.
go mod init github.com/adzeitor/mediatr

Codecov Report

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

@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   98.36%   98.36%
=======================================
  Files           1        1
  Lines          61       61
=======================================
  Hits           60       60
  Misses          1        1

Continue to review full report at Codecov.

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


Web Export Feature

Instead of saving just recent changes, add a button which uploads everything to bytebin, probably as a recent change in entirety so that luckperms plays nicely with it. This would be very useful for exporting where FTP is unavailable etc and would allow people to restore their servers in an emergency rather easily with an editor link if backups unavailable.
Note: I've noticed that you're probably going to have to add the creation of the groups to the bytebin because simply marking everything in a standard bytebin as a change doesn't include the groups.
<3 Turbo

fixed in https://github.com/lucko/LuckPerms/commit/a766c0e9aa31789524abcc4e264eee76e9bee603


Update LongestCommonSubsequence.java

Hi Tushar,
First of all, i thank you very much for your noble effort.
In the previous file there was issue with the lcs function.
I have corrected it.
Can you please review this and update.
Thanks

I appreciate your effort. Can you tell me what was wrong before? Is there any example which was failing?


Use a MAX() aggregation when fetching current count during reconciliation

Fixes #253
On PostgreSQL, if the table where the counts are stored doesn't have a primary_key specified (in our case, because it's actually a view), reconciliation fails with an error:
PG::GroupingError:
   ERROR:  column "foo.users_count" must appear in the GROUP BY clause or be used in an aggregate function
   LINE 1: ...foo".id, COUNT("users".id)*1 AS count, "foo..

This is because, according to the Postgres docs:

When GROUP BY is present, or any aggregate functions are present, it is not valid for the SELECT list expressions to refer to ungrouped columns except within aggregate functions or when the ungrouped column is functionally dependent on the grouped columns, since there would otherwise be more than one possible value to return for an ungrouped column. A functional dependency exists if the grouped columns (or a subset thereof) are the primary key of the table containing the ungrouped column.

When there's no primary key index present, even though Rails knows what the primary key is, no functional dependency gets detected at the DB level.
This MAX agg should effectively be a no-op in every case, but it prevents PG from blowing up. An alternate fix to this same problem would be adding "#{relation_class_table_name}.#{column_name}" to the GROUP BY fields.
Note: the specs added in this commit will pass on SQLite even without these fixes — they work as expected when running the specs on a PostgreSQL DB. Running the tests on PG also reveals that the existing string ID specs (which also don't have a primary_key index) fail in the same way).

Any chance of getting this merged soon? Would it be helpful for me to set up PostgreSQL testing on Travis to demonstrate the issue?

Yes, this makes sense, thank you for this. Sorry, I didn't get a notification from Github when you opened this for some reason.
Released this as 2.2.2 right now.

Thinking about this some more: Do you think you could get this test running in PostgreSQL also? I think that would be really good to make sure I don't break this for you again in the future.


[Feature]: tensorflow on gfx1102 / RX7600

Suggestion Description
On Linux, RX7600 do not seems to be supported :
# docker run -it --network=host --device=/dev/kfd --device=/dev/dri \
                 --ipc=host --shm-size 16G --group-add video --cap-add=SYS_PTRACE \
                 --security-opt seccomp=unconfined rocm/tensorflow:latest
tf-docker / > python
Python 3.9.18 (main, Aug 25 2023, 13:20:04)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow
2024-03-06 07:00:40.549184: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
/usr/lib/python3/dist-packages/requests/__init__.py:89: RequestsDependencyWarning: urllib3 (1.26.18) or chardet (3.0.4) doesn't match a supported version!
  warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
>>> tensorflow.config.list_physical_devices('GPU')
2024-03-06 07:01:21.149888: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-06 07:01:26.856968: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-06 07:01:26.857151: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-06 07:01:26.857236: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2266] Ignoring visible gpu device (device: 0, name: AMD Radeon RX 7600, pci bus id: 0000:0d:00.0) with AMDGPU version : gfx1102. The supported AMDGPU versions are gfx1030gfx1100, gfx900, gfx906, gfx908, gfx90a, gfx940, gfx941, gfx942.
[]

(empty list of supported GPU)
Did I make a mistake ?
Is it planned ?
Operating System
Arch Linux
GPU
gfx1102
ROCm Component
No response

This looks like a bug in tensorflow library https://github.com/search?q=org%3AROCm+gfx1030gfx1100&type=issues#issue-2133438576

Indeed there looks like a bug with this typo "gfx1030gfx1100". But my card identify itself as gfx1102 not gfx1100. So it is not the same problem.
I suspect the list of compatible version of tensorflow to be here : https://github.com/ROCm/xla/blob/main/xla/stream_executor/device_description.h. gfx1102 is missing in its file.

I have the exact issue in Arch Linux. I have latest rocm tensorflow docker image
`Python 3.9.18 (main, Aug 25 2023, 13:20:04)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
2024-03-12 16:10:24.080485: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
/usr/lib/python3/dist-packages/requests/init.py:89: RequestsDependencyWarning: urllib3 (1.26.18) or chardet (3.0.4) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
tf.config.list_physical_devices('GPU')
2024-03-12 16:10:50.416352: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-12 16:10:50.565263: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-12 16:10:50.565317: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-12 16:10:50.565335: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2266] Ignoring visible gpu device (device: 0, name: AMD Radeon RX 7600, pci bus id: 0000:2b:00.0) with AMDGPU version : gfx1102. The supported AMDGPU versions are gfx1030gfx1100, gfx900, gfx906, gfx908, gfx90a, gfx940, gfx941, gfx942.
[]
`

Hi,
Since Tensorflow was not built targeting gfx1102, one thing you can try is export HSA_OVERRIDE_GFX_VERSION=11.0.0 in your environment to make ROCm report the device as a gfx1100.

>>> import tensorflow
2024-03-15 20:07:29.478342: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
/usr/lib/python3/dist-packages/requests/__init__.py:89: RequestsDependencyWarning: urllib3 (1.26.18) or chardet (3.0.4) doesn't match a supported version!
  warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
>>> tensorflow.config.list_physical_devices('GPU')
2024-03-15 20:07:53.778397: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-15 20:08:00.541001: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-15 20:08:00.541182: I tensorflow/compiler/xla/stream_executor/rocm/rocm_gpu_executor.cc:756] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2024-03-15 20:08:00.541250: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2266] Ignoring visible gpu device (device: 0, name: AMD Radeon RX 7600, pci bus id: 0000:0d:00.0) with AMDGPU version : gfx1100. The supported AMDGPU versions are gfx1030gfx1100, gfx900, gfx906, gfx908, gfx90a, gfx940, gfx941, gfx942.
[]

Good idea, but now it fall on the gfx1030gfx1100 bug.

http://ml-ci.amd.com:21096/job/tensorflow/job/release-rocmfork-r214-rocm-enhanced/job/release-build-whl/206/
I've downloaded the newest build from the CI system. Let's hope the updates make their way to PyPI soon.

Just to clarify the original question, Tensorflow comes built with a number of target AMD GPU architectures: gfx1030, gfx1100, gfx900 ..., etc.  If you want additional architectures, Tensorflow developers will need to add them or you will need to build Tensorflow yourself.
Alternatively you can use export HSA_OVERRIDE_GFX_VERSION=11.0.0 mentioned above, which makes ROCm report the GPU as gfx1100. This works because the 7600 XT (gfx1102) is just a cut-down gfx1100.

Closing this ticket as the issue is with Tensorflow, not ROCm.  Thanks.


BASE_AVATAR_URL path is not being resolved correctly

The BASE_AVATAR_URL path is not being resolved correctly. Missing brackets in four places in both the app_openai.py and app_sagemaker.py files. Results in the following error:
2023-08-05 12:32:23.290 Uncaught app exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/streamlit/elements/image.py", line 361, in image_to_url
    with open(image, "rb") as f:
         ^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'BASE_AVATAR_URL/bot-64px.png'

Issue resolved. Thank you, Antonio Martellotta.


✨ Refactor OnRefreshlistener to Kotlin Functional Interface

Refactoring OnRefreshlistener previously implemented as interface to functional interface

@shwetachauhan-simform @yashwantgowla-simform Is there anyone who can review this PR?

Thanks @l2hyunwoo for your contribution
We will review and let you know ASAP.

The changes are okay to merge, made the interface functional as there is only one method for now and it makes sense to do that. We can proceed with the PR and merge it


Virtualbox > Timeout waiting for WinRM error

Sorry I  need to help, How can I fix this "timeout waiting for WinRM" error
I use Virtualbox 5.2.10
I don't know How to fix...  so  have any link to me refer ?
very thanks !!

I would try debugging the build using: PACKER_LOG=1 packer build --only=virtualbox-iso windows_xx.json and see if you encounter any errors. Also, depending on your hardware, you might just try increasing the timeout in the windows_xx.json file as well (although it really shouldn't take that long).
If you want to skip the packer builds, you can use the build script and download pre-built boxes:
./build virtualbox --vagrant-only

Much Thank! I try increasing  the timeout in the windows_xx.json , it work!!
but... I met a new problem.. :(
Would like to ask how can I fix the problem?
Very Thanks !!

There should be a restart timeout option in the .json file as well. Try bumping up the time limit for that.

Closing due to inactivity


[Jira] No longer caches the last project you created a ticket in

Extension
https://www.raycast.com/raycast/jira
Description
When creating multiple tickets, you have to select the same project over and over again. In the past (previous, deprecated version of the extension), this project ID would be pre-selected when you triggered the Create Ticket command. We have hundreds of projects but I primarily work on only a few, I suspect this could be a similar situation for many people using the extension.
I think ideally this list would sort by last used instead of purely alphabetical like it is today.
Steps To Reproduce

Invoke the Create Issue command in Raycast
Observe that the project selection has been reset from the last time it was invoked

Current Behaviour
Project selection is reset for every invocation of the Create Issue command
Expected Behaviour
Retain the last selected project in the Create Issue command in the Jira extension

Thanks for bringing this up. It appears that this is a duplicate of issue #5988, so I'll mark it as such.

@thomaslombart this issue is still occurring, I don't think it is actually related to https://github.com/raycast/extensions/issues/5988. The selected project is always set to the first alphabetical project in the list, rather than last selected


How to add JSON with source?

I can run the example JSON .
and run the JSON without Image source export by AE
but can't run the JSON by use Image source export by AE
JSON  :
{"v":"4.5.9","fr":25,"ip":0,"op":750,"w":750,"h":1334,"ddd":0,"assets":[{"id":"image_0","w":154,"h":154,"u":"images/","p":"img_0.png"},{"id":"image_1","w":154,"h":154,"u":"images/","p":"img_1.png"},{"id":"image_2","w":154,"h":154,"u":"images/","p":"img_2.png"},{"id":"image_3","w":154,"h":154,"u":"images/","p":"img_3.png"}],"layers":[{"ddd":0,"ind":0,"ty":2,"nm":"img_0.png","cl":"png","refId":"image_0","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":0,"s":[159,1415,0],"e":[349,485,0],"to":[31.6666660308838,-155,0],"ti":[-279.666656494141,-620,0]},{"t":45}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":45}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":1,"ty":2,"nm":"img_0.png","cl":"png","refId":"image_0","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[285,1591,0],"e":[269,1131,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[-10.6666669845581,184.33332824707,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":11,"s":[269,1131,0],"e":[349,485,0],"to":[10.6666669845581,-184.33332824707,0],"ti":[-279.666656494141,-620,0]},{"t":56}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":11,"s":[100,100,100],"e":[86,86,100]},{"t":56}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":2,"ty":2,"nm":"img_1.png","cl":"png","refId":"image_1","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[493.863,1633.527,0],"e":[477.863,1173.527,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[24.1438236236572,191.421157836914,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":5,"s":[477.863,1173.527,0],"e":[349,485,0],"to":[-24.1438236236572,-191.421157836914,0],"ti":[232.33332824707,-272,0]},{"t":21}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":16}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":3,"ty":2,"nm":"img_1.png","cl":"png","refId":"image_1","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[184,1544,0],"e":[168,1084,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[-27.5,176.5,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":5,"s":[168,1084,0],"e":[349,485,0],"to":[27.5,-176.5,0],"ti":[-279.666656494141,-620,0]},{"t":50}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":45}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":4,"ty":2,"nm":"img_2.png","cl":"png","refId":"image_2","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[247,1522,0],"e":[231,1062,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[-17,172.83332824707,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":3,"s":[231,1062,0],"e":[349,485,0],"to":[17,-172.83332824707,0],"ti":[-279.666656494141,-620,0]},{"t":48}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":3,"s":[100,100,100],"e":[86,86,100]},{"t":48}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":5,"ty":2,"nm":"img_3.png","cl":"png","refId":"image_3","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[459,1653,0],"e":[443,1193,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[18.3333339691162,194.66667175293,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":6,"s":[443,1193,0],"e":[349,485,0],"to":[-18.3333339691162,-194.66667175293,0],"ti":[-55.6666679382324,76,0]},{"t":25}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":6,"s":[100,100,100],"e":[86,86,100]},{"t":25}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":6,"ty":2,"nm":"img_3.png","cl":"png","refId":"image_3","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[183,1577,0],"e":[167,1117,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[-27.6666660308838,182,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":16,"s":[167,1117,0],"e":[349,485,0],"to":[27.6666660308838,-182,0],"ti":[-279.666656494141,-620,0]},{"t":61}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":16,"s":[100,100,100],"e":[86,86,100]},{"t":61}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":7,"ty":2,"nm":"img_2.png","cl":"png","refId":"image_2","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":0,"s":[362,1591,0],"e":[349,485,0],"to":[-2.16666674613953,-184.33332824707,0],"ti":[-231.66667175293,-152,0]},{"t":45}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":45}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":8,"ty":2,"nm":"img_1.png","cl":"png","refId":"image_1","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":0,"s":[324,1522,0],"e":[349,485,0],"to":[4.16666650772095,-172.83332824707,0],"ti":[-71.6666641235352,-36,0]},{"t":25}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":45}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":9,"ty":2,"nm":"img_2.png","cl":"png","refId":"image_2","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[639,1583,0],"e":[623,1123,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[48.3333320617676,183,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":7,"s":[623,1123,0],"e":[349,485,0],"to":[-48.3333320617676,-183,0],"ti":[428.333343505859,-672,0]},{"t":31}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":7,"s":[100,100,100],"e":[86,86,100]},{"t":31}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":10,"ty":2,"nm":"img_3.png","cl":"png","refId":"image_3","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":0,"s":[578,1615,0],"e":[349,485,0],"to":[-38.1666679382324,-188.33332824707,0],"ti":[272.333343505859,-456,0]},{"t":45}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":0,"s":[100,100,100],"e":[86,86,100]},{"t":45}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1},{"ddd":0,"ind":11,"ty":2,"nm":"img_0.png","cl":"png","refId":"image_0","ks":{"o":{"a":0,"k":100},"r":{"a":0,"k":0},"p":{"a":1,"k":[{"i":{"x":0.833,"y":1},"o":{"x":0.333,"y":0},"n":"0p833_1_0p333_0","t":0,"s":[562,1583,0],"e":[546,1123,0],"to":[-2.66666674613953,-76.6666641235352,0],"ti":[35.5,183,0]},{"i":{"x":0,"y":1},"o":{"x":0.333,"y":0},"n":"0_1_0p333_0","t":4,"s":[546,1123,0],"e":[349,485,0],"to":[-35.5,-183,0],"ti":[224.33332824707,-108,0]},{"t":23}]},"a":{"a":0,"k":[77,77,0]},"s":{"a":1,"k":[{"i":{"x":[0.692,0.692,0.667],"y":[1,1,0.667]},"o":{"x":[0.662,0.662,0.333],"y":[0,0,0.333]},"n":["0p692_1_0p662_0","0p692_1_0p662_0","0p667_0p667_0p333_0p333"],"t":4,"s":[100,100,100],"e":[86,86,100]},{"t":23}]}},"ao":0,"ip":0,"op":750,"st":0,"bm":0,"sr":1}]}

The current version of lottie-react-native doesn't support images. Support was just added in lottie-android, however, so there's hope you'll be able to run JSON animations with images in RN soon

Any update on this ? :)

I think could be linked to #145.
Any updates?

@alexcanessa @ahanriat Unfortunately the owners of this project don't seem very active in answering issues, but there seems to now be a prop for defining an imageAssetsFolder, added in the docs.
I haven't yet been able to figure out how to use it, might have to add the animations to the android assets folder and define imageAssetsFolder as a relative path from there. Will update once I figure it out.

I agree with @alexcanessa, #145 is a duplicate - I can't get the image to get loaded on iOS, any update anyone? :/


ign -> gz : Remove redundant namespace references

Part of: https://github.com/gazebo-tooling/release-tools/issues/784

Seems this is good to go too!


PATH commands not working lonely.

Windows Terminal version
1.17.11461.0
Windows build number
10.0.19043.0
Other Software
No response
Steps to reproduce
I opened the terminal, typed "ping" command, then got this error:
PS C:\Windows\system32> ping
ping : The term 'ping' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ ping
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (ping:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command ping was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\ping". See "get-help about_Command_Precedence" for more details.

So, I have to use ".\ping" for it to work.
I've tested it with PowerShell and cmd.exe themselves and PATH commands are working fine, But they have issues in the windows terminal
Expected Behavior
The "ping" command itself (without dot and backslash) should work as a command too.
Actual Behavior
The error that I mentioned it earlier.

What does your $env variable in PowerShell contain? You can strip out anything that you consider private data.

This is an expected behavior. In powershell command execution has this priority:
Alias > Function > Script > Native program

In your case, the ping.ps1 script should be executed, since it has a higher priority than ping.exe, but according to the PowerShell rule, this cannot be done without an absolute or relative path to the script if its folder is not in $env:PATH.

Name                           Value
----                           -----
ACSetupSvcPort                 23210
ACSvcPort                      17532
ALLUSERSPROFILE                C:\ProgramData
APPDATA                        C:\Users\Raven\AppData\Roaming
CommonProgramFiles             C:\Program Files\Common Files
CommonProgramFiles(x86)        C:\Program Files (x86)\Common Files
CommonProgramW6432             C:\Program Files\Common Files
COMPUTERNAME                   DESKTOP-FAU54K4
ComSpec                        C:\Windows\system32\cmd.exe
DriverData                     C:\Windows\System32\Drivers\DriverData
HOMEDRIVE                      C:
HOMEPATH                       \Users\Raven
INTEL_DEV_REDIST               C:\Program Files (x86)\Common Files\Intel\Shared Libraries\
JAVA_HOME                      X:\Program Files\jdk-17.0.2
LOCALAPPDATA                   C:\Users\Raven\AppData\Local
LOGONSERVER                    \\DESKTOP-FAU54K4
MIC_LD_LIBRARY_PATH            C:\Program Files (x86)\Common Files\Intel\Shared Libraries\compiler\lib\mic
NUMBER_OF_PROCESSORS           8
OS                             Windows_NT
Path                           C:\Users\Raven\AppData\Local\Microsoft\WindowsApps;C:\Users\Raven\AppData\Local\GitHu...
PATHEXT                        .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW;.CPL
PROCESSOR_ARCHITECTURE         AMD64
PROCESSOR_IDENTIFIER           Intel64 Family 6 Model 165 Stepping 3, GenuineIntel
PROCESSOR_LEVEL                6
PROCESSOR_REVISION             a503
ProgramData                    C:\ProgramData
ProgramFiles                   C:\Program Files
ProgramFiles(x86)              C:\Program Files (x86)
ProgramW6432                   C:\Program Files
PSModulePath                   C:\Users\Raven\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell...
PUBLIC                         C:\Users\Public
RlsSvcPort                     22112
SystemDrive                    C:
SystemRoot                     C:\Windows
TEMP                           C:\Users\Raven\AppData\Local\Temp
TMP                            C:\Users\Raven\AppData\Local\Temp
USERDOMAIN                     DESKTOP-FAU54K4
USERDOMAIN_ROAMINGPROFILE      DESKTOP-FAU54K4
USERNAME                       Raven
USERPROFILE                    C:\Users\Raven
windir                         C:\Windows
WSLENV                         WT_SESSION::WT_PROFILE_ID
WT_PROFILE_ID                  {61c54bbd-c2c6-5271-96e7-009a87ff44bf}
WT_SESSION                     43d8e0e5-7679-43f3-9943-1654f11e5fc9

Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment

it's not working also

What does the output of $env:Path look like/? Weird that this works in pwsh in conhost but not Terminal. My only theory is that Terminal's launching with different env vars.
(but also if 1.18 doesn't work then that doesn't seem likely either.... hmm...)

Same here.
C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.18.1462.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
C:\Users\alexe>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\alexe\AppData\Roaming
ChocolateyInstall=C:\ProgramData\chocolatey
ChocolateyLastPathUpdate=133327802124098935
ChocolateyToolsLocation=C:\tools
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=ALERT_WHITE
ComSpec=C:\WINDOWS\system32\cmd.exe
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS;.MSC
PROMPT=$P$G

C:\Users\alexe>

In the meantime: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe displays the environment variables in full scale, correcty.

Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment

Yeah, It Works.
Thanks


ext_authz: support for buffering request body

This PR adds support to ext_authz filter for buffering the request data. This is useful when the authorization server needs to check the request body, e.g. HMAC validation.
Fixes https://github.com/envoyproxy/envoy/issues/5676
Risk Level: low
Testing: unit
Docs Changes: yes
Release Notes: yes

Please merge master to pick up https://github.com/envoyproxy/envoy/pull/5827.

@lizan Thank you for looking at the PR. I had to work on some other things, but I will work on this by next week.

Sorry, another busy week. I will take a look at this later today or Monday.

@lizan I've addressed all your comments.

I will try to get back to this one tomorrow. Thanks for reviewing it.

@lizan @dio I think I addressed all your comments. Thank you for reviewing it.

@gsagula Any update/ETA on this? Seems all comments were addressed.

Same! I would love for this to be merged, am also waiting on it as it will help me a lot, trying to do HMAC in ext-authz :)

@lizan No worries, I've been pretty busy lately too. I found a couple of issues with the partial message feature, but I need to fix the broken tests now. I will try to get it out tomorrow. Thanks!

Build failures seem unrelated. I will merge master and retry.

@lizan @dio I have addressed your concerns I believe. I also added a few tests for the logic around upgrade requests and did some manual testing. Feel free to take another look. Thanks!


Plugin Subrecord Parsing

The most critical and logically difficult problem for parsing plugins is determining the subrecord structure to use for parsing the subrecord. This is difficult due to how nested subrecord collections are allowed including the options to be optional and multiple.

[x] Handle flat subrecord structures
[x] Handle "optional" subrecord structures
[x] Handle "multiple" subrecord structures
[x] Handle infinitely nested subrecord collections
[x] Handle "optional" subrecord collections
[x] Handle "multiple" subrecord collections

A quickie post about the issue: http://stephen.bunn.io/blog/2018/07/02/parsing-subrecords/

Logic for proper plugin parsing is being developed in feature/plugin-parsing.


Issue creating device

I tried copy/pasting the script above into the Azure Cloud Shell and received an error when it created a device:
terry@Azure:~$
terry@Azure:~$ # Create the IoT device identity to be used for testing.
terry@Azure:~$ az iot hub device-identity create --device-id $iotDeviceName
>     --hub-name $iotHubName
No IoT Hub found with name ContosoTestHubMsgEn30256 in current subscription.
I checked the subscription and the IoT Hub does exist.  Perhaps it is a timing issue and newly created IoT Hub's are not yet visible?

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

ID: e2d11f9c-7b7f-fb19-acf9-24df508aec17
Version Independent ID: d9f44e50-4e97-79a5-fb53-261337f7de9f
Content: Tutorial - Using Azure IoT Hub message enrichments
Content Source: articles/iot-hub/tutorial-message-enrichments.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

I tried it again, and when the script is trying to add the device the IoT Hub is not yet provisioned.  Looking at it in the portal gives the following message, "IoT Hub ContosoTestHubMsgEn28370 may not function properly because it is not in an ACTIVE state."

Changing my default az resource group to the new group seems to have fixed the problem.  eg.
az configure --defaults group=ContosoTestHubMsgEn
I recommend adding the resource group name to the create of the device, and any az commands further down in the script.  ie.:
az iot hub device-identity create -g ContosoResourcesMsgEn --device-id $iotDeviceName --hub-name $iotHubName

Hi @terrymandin Thanks for trying IoT Hub and taking the time to provide feedback to make this document better for others. I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign v-gpettibone

Issue is a couple of years old. Can't reproduce so not a doc bug. One possibility is that it takes up to a few minutes to create a hub. If one tries creating a device before the hub is fully provisioned and active, the script doesn't work. Other than that, it may have been some kind of  transient error. Not sure at this point. Going to close the issue.

#please-close


Should @BodyParam default to required?

Taking a stab at rebuilding a Ruby/Grape API with Koa2 and this library, extremely happy that it exists. Thank you for your work!
Something I noticed is that that Params specified in a request function are not required by default. Reading this signature, I'd expect it to raise an error if any fields are missing in my POST:
@Post('/buzz')
createSession(@BodyParam('foo') foo: string, @BodyParam('bar') bar: string, @BodyParam('baz') baz: string) {
  // do something
}

I see I can add the { required: true } option, but I feel like the less surprising default would be a closer to match to what the TS function signature describes, which is "everything is required." As it stands, the default forces us to treat each param as optional, so the TS signature does not accurately describe the input. Changing the default would make things safer and more trustworthy by default, which is a better user experience, IMO.

Exactly this's what I feel, e.g. The current user decorator also requires to put required: true. What if we could just use TS signature.

@BruceHem there's no way to use the reflection metadata to determine whether a parameter is required or not. That information is not emitted by the TS compiler.

Unfortunately as @marshall007 told we cannot use that information because typescript does not emit this information. We should ask typescript team to improve their reflection mechanizm and emit more data about code.

No, that is not what I am suggesting, I know TypeScript won't allow it. What I am suggesting is a change to this line.
export function BodyParam(name: string, options?: ParamOptions): Function {
    return function (object: Object, methodName: string, index: number) {
        getMetadataArgsStorage().params.push({
            // ...
            required: options ? options.required : true, // default to true, not false
            // ...
        });
    };
}

This would make the method signature match the library's defaults.

New default option allows paramOptions to be required by default
useExpressServer(app, {

    defaults    : {
        paramOptions: {
            required: true // this means that all parameters (@BodyParam, @Param etc in Actions) are required by default
        }
    }
}

@IAMtheIAM, but it will be released in 0.7.3 so it cannot be used right now.

@NoNameProvided it is released in 0.7.2, I've checked it.

Yes confirmed, it is working in 0.7.2

Ahh ok, thanks for the correction, I must have mess up something during the update of my test project.


handle request errors for getFigure, getImage and stream

Resolves: https://github.com/plotly/plotly-nodejs/issues/31
@etpinard @bpostlethwaite
Solves the issue where we weren't properly handling request errors for getFigure, getImage and stream requests.
This passes the error back to the callback.

:dancer:


OSCI: Retry UI build flake

Description
The UI build has an odd flake under OpenShift CI build:
error /go/src/github.com/stackrox/stackrox/ui/node_modules/postinstall-postinstall: Command failed.
Exit code: 1
Command: node ./run.js
Arguments:
Directory: /go/src/github.com/stackrox/stackrox/ui/node_modules/postinstall-postinstall
Output:
/bin/real-bash: /tmp/yarn--1653614697147-0.110742682233689/yarn: Text file busy

This was see quite regularly in earlier development. This PR is a workaround adding a retry.
Checklist

[x] Investigated and inspected CI test results

Testing Performed
CI is sufficient

Another instance of this: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/branch-ci-stackrox-stackrox-master-stackrox_branding-images/1530194510192054272


wip

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2807  👈 (View in Graphite)
#2806
#2805
#2804
#2803
#2802
#2801
#2724
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


can double-clicking to hide ? for GitHub-table-of-contents Script

If easy to achieve, Can you add double-clicking to hide Toc ?
Please see the screenshot below ❸:

Hi @dnknn!
That's an easy enhancement to make. I'll make it available soon.

Hmm, weird. I just noticed that the double-click only works after you drag & drop.

Ok, fixed. There is a delay after the double-click before the window collapses; I haven't spent too much time investigating how to fix that while also trying to detect a drag & drop.

I tried it, and it was perfect, no problem.
Thanks you very much!


Enable scroll locking on the terminal

Fixes #1481

@2opremio could you give this a quick test please!

Sure, I'll do that before EOD.
On Tue, Oct 18, 2016 at 3:51 PM, Simon<EMAIL_ADDRESS>wrote:

@2opremio https://github.com/2opremio could you give this a quick test
please!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/pull/1932#issuecomment-254513545,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQOJAJ7WNxryAN62-AokQtKV42IIf2cks5q1M7GgaJpZM4KZ0Dv
.

If I run the following and try to scroll up, the screen goes all black (before the fix it would jump around but show output.
while true; do find /etc; done

Good one, that blows through the scroll back nice and quickly..

I am missing a side bar to indicate where am I in the history.

Also, I would expect scrolling to happen when selecting text and moving the mouse up. That is:

Scrollbars are a nice to have, mentioned in #1940.
Scrolling up as we drag up is an interesting one. I'll mention it in that issue too.

But you're looking for a way to export the contents of the terminal somehow. Other (less ideal but still) options:

Copy terminal contents to clipboard
Show terminal contents in some other mode that allows for better selection. (textarea/plain <p>s)

Issue w/ this: cannot make a selection after having scrolled up.

Scrolling up works well, and the position stays there. Selections dont work when scrolled up, but that's mentioned. Definitely an improvement. LGTM

Selections dont work when scrolled up, but that's mentioned

Is there an issue for this?


Changed condition for protocol node selection

Changed condition for protocol node selection

@sasikeda With the colocation of CES node, this condition will handle if CES nodes are subset of Storage node.
Let us know if you have any questions.


Update 2017_01_16_121747_add_markdown_and_lock_to_chatter_posts.php

HI
When I use sqlite DB or run tests in sqlite it give error for
SQLSTATE[HY000]: General error: 1 no such column: markdown
So by assigning an array in down method it starts working , and have no trouble. That's a fix for running tests and sqlite users.
I am attaching screen shot of before and after

TIA

According to the documentation:

Dropping or modifying multiple columns within a single migration while using a SQLite database is not supported.


Add new extra difficulty category

Details are secret for now. Will replace all CURSE skills.

Resolved via commit 1c9f1a31f2b1f8758e9064d8d4c88894fdbeaab8.


Update imports in gistCore to include all gist ontologies

An rdfs:comment on the gistCore ontology states: "gistCore convenience for including all of gist." However, not all the gist ontologies are directly imported. Are we relying on indirect imports, or is it just out of date? It would be better if gistCore explicitly imports all the ontologies in case recursive imports change; it also allows a reader to see all the gist ontologies rather than following a thread of imports.

There is a tradeoff here. Adding all ontologies is redundant given import is transitive, but it can be handy to have them all there. FIBO went back and forth on this and decided to have all of the imports in each ontology, not relying on import chains.

I was surprised to see this closed. I thought we agreed to NOT depend on transitive closure of imports. While gistCore lists all of the imports, other ontologies do not.   Why are we relying on transitive import in some cases but not others?

It was fixed in 9.2.0.

I just downloaded the 9.2.0 ontologies from our web site. Only gistCore imports all ontologies. Many of the others rely on transitive import.  Do you want me to open a separate issue on this, since technically this issue was only about gistCore?

If you think it should be done then go ahead and create a separate issue. If you look up at the top at the issue description and discussion, it was only meant to apply to gistCore.


improving _core_computation

Hello,
Was playing around with this last night and ran into memory issues. I was trying to get some confidence estimates for a forest with 1 million training examples and 300k testing examples. The line cov_hat = np.zeros((X_train.shape[0], X_test.shape[0])) was giving me Memory Errors since having this matrix in memory would take over 300GB.
I realized a couple things:

The function _core_computation was not fully vectorized. It was implemented by summing outer products instead of just one matrix multiplication. With my testing, doing this multiplication all at once is around 5-10x faster with no additional memory requirements.

If a matrix of shape (n_train_sample,n_test_sample) cannot fit in memory, this function did not work at all. However, this is easy to deal with since we can deal with chunks of the pred_centered matrix at a time. I implemented this by adding a couple arguments to _core_computation and random_forest_error that allow the user to specify if they have memory constraints and if so what is the maximum memory an intermediate matrix should take up in megabytes. To my surprise, if memory_limit is tuned decently, this method is actually even faster than the whole matrix at one time method by around 3x (even if it's unnecessary and the whole matrix can fit in memory).

In summary, these improvements can speedup the _core_computation function up to 15-30x if the user plays with the memory_limit arguments or 5-10x if he or she does not. It also allows the function to work when a matrix of shape (n_train_sample,n_test_sample) cannot fit into memory.
All tests currently in the repo pass on python 2 and 3. I can add tests for when memory_constrained=True if it is desired. Please let me know if you have any comments or questions.
Thanks

thanks @arokem. Added some lines to the test_core_computation function. Had to repeat test examples 1000 times so that matrix would be big enough to meaningfully use the memory_constrained functionality. Also fixed for PEP8. All tests seems to be passing. Thoughts?

LGTM - merging. Thanks!


Integration test failing after installing @glint/environment-ember-loose/

Is this related to my install for "ember-cli-typescript": "^4.2.1",?
---
    stack: >
        Error: Could not find module `@glint/environment-ember-loose/glimmer-component` imported from `@somePackageAddon/lms-date-ui/components/date-range`
            at missingModule (http://localhost:7357/assets/vendor.js:259:11)
            at findModule (http://localhost:7357/assets/vendor.js:270:7)
            at Module.findDeps (http://localhost:7357/assets/vendor.js:180:24)
            at findModule (http://localhost:7357/assets/vendor.js:274:11)
            at Module.findDeps (http://localhost:7357/assets/vendor.js:180:24)
            at findModule (http://localhost:7357/assets/vendor.js:274:11)
            at requireModule (http://localhost:7357/assets/vendor.js:36:15)
            at Class._extractDefaultExport (http://localhost:7357/assets/vendor.js:73921:20)
            at Class.resolveOther (http://localhost:7357/assets/vendor.js:73583:32)
            at Class.resolve (http://localhost:7357/assets/vendor.js:73644:25)

I yarn remove ember-cli-typescript and the test passed again.

or add ember-cli-typescript but remove @glint/environment-ember-loose the test passes but i can't have both isntalled.

TypeScript compiler crashes?

A few questions to hopefully get a better picture of what's happening here:

Does your app have ember-auto-import installed? What version?
Does the addon in question have ember-auto-import installed? What version?
Does the addon have a declared dependency on @glint/environment-ember-loose?
Is the integration test written in TS or JS?

Also one note: we intentionally haven't documented a path for published addons to use Glint yet, as the custom imports present some potentially thorny adoption issues for consumers. That doesn't mean it isn't possible, just that addon authors will be 'on their own' for the time being to make it work. If we can land the component signature RFC in Ember proper, we'll be able to eliminate the custom imports and the story gets a lots simpler.


ES7 decorator

I am really new to the JS world so this is me just thinking out loud.
From the start the connect()() really threw me for a loop.  Mix that with connect(mSTP, mDTP)(Radium(component)) etc... the uglyness continues.
Would it be possible to come up with something like this?
@Redux({
  mapStateToProps: (state) => {
  },
  mapDispatchToProps: (state) => {
  },
})
class App extends Component {
  ...
}

Where they were optional just like the connect?

You can use the connect as a decorator.
@connect(...)
class App extends Component...

In fact that is all class decorators are, functions that take in a class and return a class.

We don’t suggest using decorators though until the spec advances and Babel officially supports it.
Why not use compose for this?
import { compose } from 'redux'

class MyComponent extends Component {
  // ...
}

const enhance = compose(
  connect(mapStateToProps, mapDispatchToProps),
  Radium,
  // anything else
)

export default enhance(MyComponent)

Hi @gaearon, thank you for this library. +1 for your solution.
I am also new to redux and came across this similar problem.
I cant seem to find much about using connect with es6 classes in the docs, hence google brought me here.
Would like to check if decorators are ready to use?
And i realised that none of the examples were using es6 classes, is there a specific reason? Am i going in the wrong way with incorporating code that uses es6 classes?

I cant seem to find much about using connect with es6 classes in the docs, hence google brought me here.

You’d use connect() with ES6 classes exactly like you’d use it with functional components.
There is no difference.
Functions:
function Foo() {
  return

}

function mapStateToProps() {
  // ...
}

export default connect(
  mapStateToProps
)(Foo)

Classes:
class Foo extends React.Component {
  render() {
    return

  }
}

function mapStateToProps() {
  // ...
}

export default connect(
  mapStateToProps
)(Foo)

Use classes when you need this.setState() or lifecycle hooks like componentDidMount(). Use functions when you don’t need either. Example do use classes in such cases, for example RepoPage.
Neither approach has any relation to decorators. Decorators are an unstable feature that is not officially supported by Babel at the moment, and their specification is undergoing a change now. So I don’t recommend using them. In terms of connect, there is nothing you can do with decorators that you can’t do without them.

Thank you for the prompt reply.
However this begs the question, when do I use compose? Instead of using your latest solution?
Thank you.

compose is used to combine multiple wrappers together into a pipeline.  For example, with store enhancers, you'd do:
const composedStoreEnhancer = compose(
    applyMiddleware(thunk, saga),
    DevTools.instrument()
);

const store = createStore(rootReducer, composedStoreEnhancer);

Similarly, if I wanted to create a single wrapper that combined Redux setup and Redium setup, I could do:
const combinedWrapperComponents = compose(
    connect(mapState, mapDispatch),
    Radium(radiumArgs)
);

export default combinedWrapperComponents(MyComponent);

And, uh, that's basically what Dan wrote already :)


Fix Succesful to Successful.

Hi @bmzhao Can you please review this PR ? Thank you!

Hi @bmzhao Can you please review this PR ? Thank you!

Please fix more than just one single letter typos.

Brian does not work in TF for more than a year, removing assignment.


Switch PyPI deploy method to use trusted publisher

PyPI introduced Trusted Publishers last year (see the announcement and how trusted publishing works). This improves security, since you no longer rely on having long-lived API tokens to use with twine.
We recently added a PyPI deployment job to the release workflow in https://github.com/computational-cell-analytics/micro-sam/pull/606. That PR uploads to PyPI using twine (because I didn't know about the trusted publisher option then).
To switch to trusted publishing for micro-sam, we'd need to do two things:

Add a trusted publisher to our existing PyPI project (or you can create a new PyPI project with a trusted publisher).
Merge a PR updating .github/workflows/release_drafter.yml. The deploy job needs to be given id-token: write permissions, and changed to use the pypa/gh-action-pypi-publish action (see example here).
Delete the old PyPI API tokens, from both PyPI and the GitHub repository secrets settings.

Xref: https://github.com/napari/napari-animation/issues/211

I'd say this change is good to have, but not super urgent.
Maybe we should aim to get it done in the next 1-2 releases, or the next six months?
Sorry Contantin, I know I had you make those PyPI API tokens very recently. I didn't realise this was the better way to do it!

No worries and thanks for looking into it @GenevieveBuckley. I was a bit delayed with testing the PyPI upload anyways; I want to do this together with a new patch release but still need to work on a few minor things for this. I should be able to do this early next week. I will check this issue out then.

No worries. We could easily wait for this to happen in https://github.com/napari/napari-animation/issues/211 (I've opened https://github.com/napari/napari-animation/pull/212), and see how things go there first. There might be one or two hiccups we can learn from.

Ok! Let's wait for the PR in napari-animation and also figure out why our current deployment is not working before that, see #530.


Can’t archive App that uses a swift package with this xcframework

Hello,
thanks for this repo, it works like a charm.
I have a problem when adding xcframework inside a SPM Framework when archiving (works in the simulator).
Have you used the xcframework in a SPM Package?
Seems like a Apple Bug but maybe you found a workaround.
My workaround for the moment is to embed the xcframework in the App Target directly and not in the SPM Package.
Thanks in advance
My SPM Package with the xcframework:
import PackageDescription

let package = Package(
    name: "Data",
    platforms: [.iOS(.v13)],
    products: [
        .library(
            name: "Data",
            targets: ["Data"]),
    ],
    dependencies: [
    ],
    targets: [
        .binaryTarget(
            name: "GSignIn",
            url: "https://github.com/SyncServerII/GSignIn/raw/main/XCFrameworks/GSignIn-5.0.2.xcframework.zip",
            checksum: "b2b468ca98bcbe7d771726cd2a1ea6f9bee785957af8c9f4c75aa10e5c337a52"
        ),
        .target(
            name: "Data",
            dependencies: [
                "GSignIn"
            ]
        ),
        .testTarget(
            name: "DataTests",
            dependencies: ["Data"]),
    ]
)```

Hey-- Thanks for the report. I'm using it here:
https://github.com/SyncServerII/iOSGoogle.git
I definitely ran into a problem in archiving. I wrote up some notes here:
https://stackoverflow.com/questions/65469685/using-google-sign-in-for-ios-with-swift-package-manager/65469686#65469686
Not sure if that's enough to fix your issue. Happy to help a little later if not. Mid-work day for me. My app https://github.com/SyncServerII/Neebla (using https://github.com/SyncServerII/iOSGoogle.git) is archiving -- have been testing it on TestFlight.

The secret sauce was here:
https://github.com/SyncServerII/iOSGoogle/blob/38dee7730ab27ae54e28437ebc48e688a842c111/Package.swift#L26
Let me know if you have more questions.

Thanks for the quick reply.
I'll give a try during the next week to solve the error: no such module 'GSignIn' when archiving.
I made similar than you, maybe there's a missing subtility in my steps.
The steps:

In the Package.swift of the Module containing the GSignIn xcframework (aka Data). In my first attempt I didn't add the product library GSignIn, we'll see if this causes the problem.

let package = Package(     name: "Data",     platforms: [         .iOS(.v13),     ],     products: [         .library(             name: "Data",             targets: ["Data"]),             .library(             name: "GSignIn",             targets: ["GSignIn"]),     ],     dependencies: [],     targets: [         .binaryTarget(               name: "GSignIn",               url: "https://github.com/SyncServerII/GSignIn/raw/main/XCFrameworks/GSignIn-5.0.2.xcframework.zip",               checksum: "b2b468ca98bcbe7d771726cd2a1ea6f9bee785957af8c9f4c75aa10e5c337a52"         ),         .target(             name: "Data",             dependencies: [                 "GSignIn"             ],             resources: [                 .process("Resources/test.json")             ]         ),         .testTarget(             name: "DataTests",             dependencies: ["Data"])     ] )

I have added an Archive - Post Action script in the Data SPM Package with:

full_frameworks_path="${ARCHIVE_PRODUCTS_PATH}/Applications/${FRAMEWORKS_FOLDER_PATH}" echo "full_frameworks_path: ${full_frameworks_path}" rm -rf "${full_frameworks_path}/GSignIn.framework"
In your example, you're doing a similar approach with a build phase script with an Input file $(BUILT_PRODUCTS_DIR)/$(PLUGINS_FOLDER_PATH)/GSignIn.framework
and the script
`
See https://forums.swift.org/t/swift-package-binary-framework-issue/41922/2
COUNTER=0
while [ $COUNTER -lt "${SCRIPT_INPUT_FILE_COUNT}" ]; do
tmp="SCRIPT_INPUT_FILE_$COUNTER"
FILE=${!tmp}
echo "Removing $FILE"
rm -rf "$FILE"
let COUNTER=COUNTER+1

done
`
I'll try again with your approach to see if it's working.


Prefer lodash functions over native javascript

Just what I was looking for! Thanks!
Would be awesome to have rules to set lodash forEach/isArray/isObject/isString/isBoolean/etc over native javascript. Similar to what https://github.com/Gillespie59/eslint-plugin-angular did with typecheck-array/typecheck-date/typecheck-number/typecheck-object/etc.
Thanks and nice job!

Sounds good! We'll add it to our backlog. You're welcome to submit a PR yourself.

Implemented rules prefer-lodash-method and prefer-lodash-typecheck for your convenience!
Available from v0.1.8.

Thanks!


feat: tss-history

Description

Add add Tss History to crosschain store
Add tss pubkey to createCCTX
Closes: #1026 #1027

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

Is it ready for re-review @kingpinXD ?


Adding compatibility with DateTimeOffset values in MySQL

We are trying to add DateTimeOffset support in DBContext model. This type is mapped to a Timestamp in MySQL. The issue we have is that the types are no compatibles automatically in EF. Thus we need to add some extension method or something else so the user can perhaps create a custom conversion or we can provide maybe a generic.
Is there already any methods we can override or implement in the current EF Core infraestructure?
@rowanmiller
@divega
Any comments are highly appreciated.

@gmartinezsan Have you tried returning the appropriate type mapping in your implementation of RelationalTypeMapper?

hi @ajcvickers , thanks for the reply.
Yes I did. MySQL server do not have any DateTimeOffset equivalent type. So we use Timestamp. The issue is thrown when the DataReader tries to get the value. I'm getting an Invalid Cast Exception.
I was thinking about overriding the DataReader method. Not sure if that could work.
Here's the call stack
System.InvalidCastException was unhandled by user code
HResult=-2147467262
Message=Unable to cast object of type 'System.DateTime' to type 'System.DateTimeOffset'.
Source=System.Data.Common
StackTrace:
at System.Data.Common.DbDataReader.GetFieldValue[T](Int32 ordinal)
at lambda_method(Closure , DbDataReader )
at Microsoft.EntityFrameworkCore.Storage.Internal.TypedRelationalValueBufferFactory.Create(DbDataReader dataReader)
at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable.Enumerator.MoveNext()
at Microsoft.EntityFrameworkCore.Query.QueryMethodProvider.<_ShapedQuery>d__31.MoveNext()        at System.Linq.Enumerable.First[TSource](IEnumerable1 source)
at lambda_method(Closure , QueryContext )
at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass19_11.<CompileQuery>b__1(QueryContext qc)        at System.Linq.Queryable.First[TSource](IQueryable1 source)
at MySql.Data.EntityFrameworkCore.Tests.FluentAPITests.CanUseModelWithDateTimeOffset() in D:\Repository\Git\7.0\DEVELOPMENT\Tests\MySql.EntityFrameworkCore.Basic.Tests\FluentAPITests.cs:line 77
Thanks in advance for your time.

@gmartinezsan As of now, EF Core only supports types that can be read from the DbDataReader with a call to GetFieldValue<T>() where T is the type. The object returned from the call must be of type T. It looks like GetFieldValue<DateTimeOffset>() is throwing for MySQL. This means a type conversion is required after reading from the data reader. This is not yet supported--it is being tracked by issue #242.

Thanks for the information @ajcvickers .. I'm closing this issue and follow up with the #242
Regards,

@gmartinezsan It is possible to resolve your instances of DateTimeOffset by creating a custom implementation of EntityMaterializerSource. I've tackled something similar where I am getting EFCore to support custom type mapping from a string -> TagSet (a custom type which represents a list of tags).
The trick for me, was intercepting how the value is materialized from the value buffer.
Before:
Expression.Convert(CreateReadValueExpression(valueBuffer, index), type);

After:
Expression.Convert(
   Expression.Convert(CreateReadValueExpression(valueBuffer, index), type),
   typeof(TagSet));

This is possible because I had implemented custom explicit operators on my TagSet type:
public static explicit operator TagSet(string tags) => new TagSet(tags);
```
See the following gist:
https://gist.github.com/Antaris/ca0f271311fdb84ef3a8db95b149a307#file-customentitymaterializersource-cs

With trying to map `DateTimeOffset`, you may instead have to generate a delegate method expression whereby you can do the mapping from the `timestamp` type to a `DateTimeOffset`, because you can't apply those operators to the `DateTimeOffset` type.

Perhaps define a helper class

public static class DateTimeMapper
{
public DateTimeOffset Map(DateTime value)
=> new DateTimeOffset(
new DateTime(value.Year, value.Month, value.Day), TimeSpan.Zero);
}

And then generate the mapping expression:

var method = typeof(DateTimeMapper).GetMethod(nameof(DateTimeMapper.Map));
Expression.Call(
method,
Expression.Convert(
CreateReadValueExpression(valueBuffer, index), type));

Hopefully the work in #242 makes this somewhat easier.

Possible with Value Conversions
Define the Converter:
private ValueConverter GetDateTimeToDateTimeOffsetConverter()
{
    var converter = new ValueConverter<DateTimeOffset, DateTime>(
                                requestedWithOffset => requestedWithOffset.DateTime,
                                requested => new DateTimeOffset(requested, TimeSpan.Zero)
                                );

    return converter;
}

Then add it to the property:
entity.Property(e => e.date)
                    .HasColumnName("date")
                    .HasColumnType("timestamp")
                    .HasConversion(GetDateTimeToDateTimeOffsetConverter());


Rework EVP_CIPHER support, enhance existing functions

This adds missing support for providers in diverse EVP_CIPHER and EVP_CIPHER_CTX functions.  A few helper macros found in crypto/evp/evp_locl.h minimize the code duplication.
One bit may be controversial: I've change the proliferation of small functions return small bits of information, such as key length, iv length, that sort of things, into parameters fetchable and settable with get_params and set_params type functions.  My main reasoning is that it makes for a more consistent transfer of information data.  Others may disagree and I'm open for other points of view.
The cipher context IV was a bit interesting.  EVP_CIPHER_CTX_iv() returns a pointer to the live IV, while EVP_CIPHER_CTX_ctrl() with the type EVP_CTRL_GET_IV gets a copy of the live IV.  To support both, we support getting it with both the OSSL_PARAM_OCTET_STRING and OSSL_PARAM_OCTET_PTR datatypes.
This is a first, and a bit unexpected...  I hadn't foreseen this kind of use for OSSL_PARAM_OCTET_PTR, and this type of use may not always be very well supported, by providers who do not want to share their internals like this (I expect the FIPS provider to refuse this, since that constitutes an intermediate value that probably shouldn't get out).

NOTE: this PR includes the test change from #9324.
NOTE: this PR overlaps #9301 a bit.  I left all the AEAD, GCM and CCM stuff alone 'cause I knew it was there already.  But @slontis, we may have to discuss coding strategies, they differ a bit :wink:

Ok, I've reworked the ugly macros with a function and a set of callbacks.  Thanks for pushing me

git add ? :)

D'oh.  You're entirely correct

CIs are now happy

Just finish tests - proposed correction resolves issue #8895.

LGTM

Merged.
06c8331c51797f43881e5262b4c114aacc6d0ca0 Adapt the provider AES for more use of OSSL_PARAM
13273237a65d46186b6bea0b51aec90670d4598a Adapt diverse EVP_CIPHER functions to use get_params and set_params interfaces
80942379c9fc66076b784cba6318ed6ca85ca3ea Make more use of OSSL_PARAM for ciphers
48ebde226d4bd66556f25d0c4b3679478890974d test/evp_test.c: [ciphers] Test that we get back the same IV we gave


Reduces the amount of auth checks for allProblems query

This PR address a performance issue with the allProblems query GQL resolver by reducing the number of auth checks required to a per project basis, rather than per problem basis.
Checklist

[ ] Fixes a server timeout issue that was being thrown during a keycloak auth check for a large query

Closing issues
To add

@timclifford and @rocketeerbkw is there anything in this PR that would still be of use in the current performance work?


Support Python 3.11

[X] I have searched the [issues] of this repository and believe that this is not a duplicate.
[X] I have searched the [documentation] and believe that my question is not covered.

Is your feature request related to a problem? Please describe.
poetry-dotenv has an explicit upper bound version constraint against Python 3.11
Describe the solution you'd like
Support Python 3.11
Describe alternatives you've considered
"Forking locally" to remove the <3.11 constraint and see if it works.
Additional context
What's the reason for the upper bound? Does poetry-dotenv use Python features removed in 3.11?
If not, <3.11 is overly conservative, as Python will retain functionality for at least two minor versions, i.e. at least two years.

Done.


[SPARK-46681][CORE] Refactor ExecutorFailureTracker#maxNumExecutorFailures to avoid calculating defaultMaxNumExecutorFailures when MAX_EXECUTOR_FAILURES is configured

What changes were proposed in this pull request?
This pr aims to refactor ExecutorFailureTracker#maxNumExecutorFailures to avoid calculating defaultMaxNumExecutorFailures when MAX_EXECUTOR_FAILURES is configured.
Why are the changes needed?
Avoid unnecessary computations:
https://github.com/apache/spark/blob/bfaf9e47b35b96be01962cce0670949901e171c3/core/src/main/scala/org/apache/spark/deploy/ExecutorFailureTracker.scala#L86-L100
The result of defaultMaxNumExecutorFailures is calculated first, even if MAX_EXECUTOR_FAILURES is configured now.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

Merged to master. Thank you, @LuciferYang .


Consider supporting JSONPatch

http://jsonpatch.com/
as the format is "standard" and is widely supported on backend stacks

That could be done, but it would require a breaking change and might come at a bit of a performance cost because of the value handling (the value can be an array or object instead of just going a level deeper).

I am returning to this, as this is more possible than I initially thought.
Question to everyone: Would you be willing to go through a breaking change if it meant that everything was compatible with JSONPatch? This would mean you would have to update some of your code, but it shouldn't be much more than some find and replace since the formats are very related, and it would allow for more integration without a compatibility layer. Also, this would make patching much easier since the libraries already exist (although I still might fully release Micropatch for the same reason I made Microdiff, but for JSONPatch patching).

I am not an existing user but my frontend basically necessitate a diff library that output JSON-Patch given that libraries on the backend commonly expect (or generate) this format.

I am looking at doing this again. However, a feature some people rely on in Microdiff is the oldValue property, which does not exist in JSON Patch. I could add oldValue while otherwise keeping compatibility with JSON Patch. This would still be compatible with most things and would be simple enough to filter out if there is an incompatible library.
Another option would be to add a JSON Patch config option. This would allow for perfect  JSON Patch compatibility while  still making it possible to see the past value for those who need it and could even allow for no breaking change (although I would probably still release a new major version for other things). However, I try to minimize the configuration, as each config option increases size and decreases performance.
What do you think?

I would personally vote for the config but it's your codebase, do as you please :)

I am little confused about what you mean. I am not talking about adding patching functionality for Microdiff. What I am saying is that Microdiff would output JSON Patch statements. For example, if oldValue was included, the output could be:
[
  { "op": "replace", "path": "/baz", "value": "boo" , "oldValue": "qux"},
  { "op": "add", "path": "/hello", "value": ["world"] },
  { "op": "remove", "path": "/foo" , "oldValue": "bar"}
]

As for use cases, it is anything that needs the past value, as getting it from the path and the old object can be slow and annoying. For example, the old value would be helpful if you built a diff viewer.
About the config, I am leaning towards that, but the code would be made much larger and potentially slower.

Hello, I think keeping "oldValue" is reasonable if any other key is compatible with json-patch.
One other way would be to expose a patch and a reverse patch, so you can apply / reverse some diff changes.
Maybe making json-patch available through a new file to import might help to avoid config / breaking changes.
import { diff, patch, reversePatch } from "microdiff/json-patch"

I'm going to play with microdiff and json-patch soon by transforming the result to a patch.
Do you have a branch with json-patch? I might play with microdiff locally and try to implement something

@Julienng There is an implementation of patching functionality, although it is currently only on GitHub, not NPM (https://github.com/AsyncBanana/micropatch).
I could make it accessible through a subpath, although I could also just release a new major version with json-patch and continue maintaining v1 (although there is not much maintenance needed to do the library being compact and dependency-less).
Currently, I do not have a branch with json-patch, although it would be trivial to implement.

+1 for this! Love your micro library :)


Mongoid 5: NoMethodError: undefined method `merge' for "primary":String

Let's say I have a User model.
In the app or console, I can do User.all.first or User.all.count but if I do the same thing when running rspec, I get htis error:
NoMethodError:
       undefined method `merge' for "primary":String

I had a lingering read option in my mongoid.yml config.