purge release artefacts from repo

I'm working on getting your library onto conda-forge and these release/build artefacts are causing a bit of grief.

Sorry this took so long for me to see. It looks good to me, got it merged in.
Will future updates be taken care of as well or is this just for the current version?

Hi @a-urq , no need to apologize.  In general, you want to try to keep binary / complied stuff out of your source code repository and especially the source tree, so that it does not get bundled into releases.  I think cutting a new release would fix my issue upstream with conda-forge.  Up to you.

Done https://github.com/a-urq/ecape-parcel-py/releases/tag/v<IP_ADDRESS>

Thanks @a-urq , please upload the release to pypi

https://pypi.org/project/ecape-parcel/<IP_ADDRESS>/


Stack unwinds incorrectly  when jumping from if block to the outermost block using a br_if

Given the following code:
(module
  (type $t0 (func (param i32) (result i32)))

  (func $innerFunc (type $t0) (param $arg0 i32) (result i32)
    (local $resultCode i32)
    block $outerBlock
      i32.const -1 ;; These values must be dropped from the stack
      i32.const -2 ;; when the br_if jump is triggered

      i32.const -3
      if (result i32)
        local.get $arg0
        local.tee $resultCode
        br_if $outerBlock
        i32.const 100
      else
        i32.const 200
      end
      local.set $resultCode

      drop
      drop
    end
    local.get $resultCode)

  (func $main (export "main") (type $t0) (param $arg0 i32) (result i32)
    i32.const 0
    local.get $arg0
    call $innerFunc
    i32.add)

  (memory $M0 1))

When executing 'main' on Chicory with the argument '5', the function returns the incorrect result of 3.
In the "innerFunc", the  br_if jump  to the outer block is triggered and after its execution the values -1 and -2 remain on the stack:
stack = {ArrayDeque@2296}  size = 4
 0 = {Value@2311} "5@i32"
 1 = {Value@2312} "-2@i32"
 2 = {Value@2313} "-1@i32"
 3 = {Value@2314} "0@i32"

When executed on wasm-interp the result is correct:
$ wasm-interp test.wasm -r "main" -a "i32:5"
main(i32:5) => i32:5

Thanks a lot @illarionov for the detailed report and the minimal reproducer!
Are you willing to look into this issue?
Also @mariofusco might be interested :slightly_smiling_face:

I've been trying to look into this, but I think this issue should be looked up by someone who originally implemented the control flow instructions in the project or know how they should work.

Thanks for getting back, I'm a bit busy but I'll try to have a look by the end of the week.

Finally managed to get to this, sorry for the delay!

NP, Thank you for the quick resolution!

Thank you once again for the fix. I checked the changes in #301 and found that the problem with br_if has been resolved. However, I quickly ran into a similar issue with the br and br_table instructions. Perhaps these instructions should also be marked as control frames.
It can be reproduced using the following examples:
br
(module
  (func $main (export "main") (result i32)
    i32.const 1
    i32.const 3
    block $outerBlock
      i32.const 5
      i32.const 7
      if
        br $outerBlock
      end
      drop
    end
    i32.add))

br_table
(module
  (func $main (export "main") (result i32)
    i32.const 1
    i32.const 3
    block $outerBlock
      i32.const 5
      i32.const 7
      if
        i32.const 0
        br_table $outerBlock
      end
      drop
    end
    i32.add))

Thanks for the update @illarionov , I updated my PR to take into account the additional cases reported.
Thanks a lot for the help and the great reproducers!


[Feature request] Ability to open PDFs through URLs

From what I know, only the inbuilt PDF Viewer in the Google Drive app and Librera can open PDFs through a link shared from the browser/another app.
Is that something that is feasible to add to this app? It would allow the user to view the PDF without having to download it.

I can work on implementing this feature

Just did some testing and it appears it already works in Android 6, but something changed in Android 7 that prevents it from working

Conspiracy theory: Google broke things so only their Drive app could have this functionality. 👀

Actually that functionality work, I implemented it some months ago... Well maybe it doesn't work for everything, can you tell us from which app the link come from ?
To test I use an Android 9 phone and open a link to a PDF from Firefox to PdfViewer and it work perfectly...
Is there only a problem on Android 7 ? :(

Ah. A little more testing done.
I was using Fenix to try and share a link to PDF Viewer, but it doesn't show up in the Share Sheet. That threw me off, since Librera does show up. Could that be added?
Using Firefox for Android's 'Open in App' feature does indeed work, but it downloads the file permanently. I was hoping for it to be cached, and deleted upon closing PDF Viewer. Is that feasible?
(Google Drive's PDF Viewer also has an option to permanently save a cached PDF if you feel like it, though that might amount to feature creep, since it can be downloaded separately anyway. Still would be nice to have. ^_^ )

I was testing Google chrome and it didn't work, perhaps there's no fix since there's no way on android 7+ to get the os to detect that it can open files without download

If it works for Google Drive, there must be a way, mustn't there?

Google Drive is a file explorer app (which the open with feature already works with), Google Drive likely downloads the file and then opens it in the app you choose

Sure. The file cannot be shown without being downloaded, even for desktop browsers. But they store it in a temp directory and then either delete it or it gets cleaned up with a restart.
Google Drive has an inbuilt PDF viewer (see OP) which directly downloads the PDF (temporarily) and shows it. The main app has no role (unless you choose to save the PDF to Drive) and you can use this PDF Viewer activity as a standalone.

Wait, I just discovered that the print button has a Save to PDF option. All I need now is for the PDF to be temporarily cached instead of downloaded for viewing.


chore: issue templates

What:

Adds the new GitHub templates
Why:

How:

Checklist:

[x] Documentation
[x] ~Tests~
[x] Ready to be merged
[x] Added myself to contributors table

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


size mismatch.My num_classes is 4, and I want to use dino's checkpoint, which causes an error.

RuntimeError: Error(s) in loading state_dict for DINO:
size mismatch for transformer.decoder.class_embed.0.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.0.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.decoder.class_embed.1.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.1.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.decoder.class_embed.2.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.2.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.decoder.class_embed.3.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.3.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.decoder.class_embed.4.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.4.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.decoder.class_embed.5.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the s
hape in current model is torch.Size([5, 256]).
size mismatch for transformer.decoder.class_embed.5.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in
current model is torch.Size([5]).
size mismatch for transformer.enc_out_class_embed.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the sha
pe in current model is torch.Size([5, 256]).
size mismatch for transformer.enc_out_class_embed.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in c
urrent model is torch.Size([5]).
size mismatch for label_enc.weight: copying a param with shape torch.Size([92, 256]) from checkpoint, the shape in current model is
torch.Size([6, 256]).
size mismatch for class_embed.0.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.0.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).
size mismatch for class_embed.1.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.1.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).
size mismatch for class_embed.2.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.2.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).
size mismatch for class_embed.3.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.3.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).
size mismatch for class_embed.4.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.4.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).
size mismatch for class_embed.5.weight: copying a param with shape torch.Size([91, 256]) from checkpoint, the shape in current mode
l is torch.Size([5, 256]).
size mismatch for class_embed.5.bias: copying a param with shape torch.Size([91]) from checkpoint, the shape in current model is to
rch.Size([5]).

请问你的问题解决了吗

have you solved it i am facing the same issue though i have used finetune ignore to ignore class embed weight

不知道怎么回事，我第一次按照readme微调的时候工作得很好，第二次出现你的错误，而后我又试了两三次，又可以正常工作了，真是玄学。


Improve macos tray removal code

This factors duplicated code by reusing existing launchd helpers, and rewords a bit the messages.

/retest

CI seems to be failing because the cluster is too slow to start:
     Given checking that CRC is running           # crcsuite.go:271 -> github.com/code-ready/crc/test/e2e/crcsuite.CheckCRCStatus
    output did not match. Expected: '.*OpenShift: .*Running \(v\d+\.\d+\.\d+.*\).*', Actual: 'CRC VM:          Running
OpenShift:       Starting (v4.10.3)


Abandoning logseq-dynamic-lookup, update to a fork?

Dear all,
I've not been using logseq for a while now and I'm abandoning my logseq-dynamic-lookup plugin. Without using it, I can't ensure that the version bumps make it keep working.
There is a fork by @jjaychen1e. Maybe they want to take over?
If not, I will add a PR to remove the plugin from the marketplace.

Sorry, I have not been using Logseq personally for a while.


Environment Package shows up in Mixed Reality Feature Tool

The MRTK3 environment package was removed in pre12, but still shows up in the Mixed Reality Feature Tool under MRTK3.  Maybe there should be a Warning in Project Validation to show that its depreciated, and should be removed from Project.
MRTK3 Pre12 Changelog
We've removed the environment package. We recommend using Unity's built-in support for playspace boundary queries instead, as well as ARFoundation's ARMeshManager for scene reconstruction.

i can deprecate the package on the feed. that will hide it from the MRFT UI by default (customers who need it can unhide deprecated packages in settings)

That's perfect! Thank you so much.


How to make multiple groups and multiple clients restricted-access name

Hello
how can I make restricted-access multiple clients?
I saw the #92
but where to put the role
the client or authentication?
I tested 1 client 1 group
example (Zabbix)
in it has a roles called (restricted-access) and in
Groups (group role mappings) (client role) selected (restricted-access) for the Zabbix client
it's working but how to rename each client have different names like
(zabbix01.restricted-access)
(kibana03.restricted-access)
Zabbix01
(roles)=(zabbix01.restricted-access)
and in
(group role mappings)->(client role) selected (zabbix01.restricted-access) for the (Zabbix01 client)

Hello @awsmaythem,
I am not sure if I really understand what you are trying to achieve here.
Do you want roles to have different names per client? That is currently not possible and I do not think I will support this in the future.
The role restricted-access must be defined per client. Therefore, the role name is the same for all clients that you want to restrict. The client works like a namespace or "scope" for the role. In #92 I used the notation <client_name>.<role_name> (e.g. zabbix01.restricted-access) only to distinguish roles from different clients. I did not want to imply that there is a role with that exact name.
If you want to assign roles from multiple clients to the same group, simply switch the client in the dropdown field and assign the roles as needed.
Best regards
Sven-Torben

you mean i can set (zabbix01.restricted-access) in roles in client and select a group or user assigen a client role to it (zabbix01.restricted-access)

You do not need the prefix with the role name. The name must be the same for every client. It has to be restricted-access.
For every client that has this role defined, the authenticator will check access permissions.
To allow a user access to multiple clients, you simply need to assign all defined roles (one for every client) to the user.
I currently do not have my notebook with me. I can send some detailed pictures the next days, if that helps.

please show some detailed pictures

The Problem am having is I have 3 client services (Zabbix and Kibana and ticket system) and have groups like (team zabbix)(team logs)(team ticket)
in (zabbix client) have role (restricted-access) and (team zabbix) but (kibana client) and (team kibana) if it have (restricted-access) in role and group the (team zabbix) can access (kibana client and team kibana) can access zabbix
i need a way to separate the role on client and group or users...

Sorry for the late reply, I was off for a few days.
Let's say you have your three clients.

Add a role restricted-access to every client.

With your three groups, you can now assign the roles to your groups as needed.

Let's take team logs as an example. Open the team and assign role:

As you can see (in the new admin console at least) there are three roles, one per client.

You can now assign a combination of these roles as needed.
In the old admin console it is not that intuitive. You will need to switch clients via the dropdown box:

that explained alot thanks alot


pkg/errors.Gatherer: Add DoneOrFailed() or similar.

Currently, it's impossible to perform a "Wait for completion of all goroutines or until the first goroutine fails" trivially. We need that behavior in the erdstall project. Please either add a function DoneOrFailed() <-chan error (or <-chan struct{}, I don't really care), or a WaitDoneOrFailed() function. While you're at it, it might also be an appropriate time to add context support for the Gatherer, but that's optional.

To stick with the interface i would do DoneOrFailed <-chan struct{} since the error can be accessed with Err(), just like in the Failed() <-chan struct{} case.
@RmbRT

Can we please start moving that generic pkg functionality to a separate repo? I think now would be a good time.

Can we please start moving that generic pkg functionality to a separate repo? I think now would be a good time.

Sure. But without an issue and a prioritization i would not like to do it in this MR.


Admin me please🙏

My user is: Symon...
Include the dots

I need password please

user: Symon...  Password: Create0629
On Wed, Nov 6, 2024 at 7:00 PM bbrraaddeenn44 @.***>
wrote:

I need password please
—
Reply to this email directly, view it on GitHub
https://github.com/mrmojololo/blooket-admin-hack/issues/1053#issuecomment-2461106258,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMWYG3NR752SURDS2CYHDSDZ7K3RXAVCNFSM6AAAAABRJAYFWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRRGEYDMMRVHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok will be done in 5 hours ok
On Thu, Nov 7, 2024 at 8:45 AM Sk-ERROR-mon @.***>
wrote:

user: Symon... Password: Create0629   On Wed, Nov 6, 2024 at
7:00 PM bbrraaddeenn44 @.>  wrote:   > I need
password please  >  > —  > Reply to this email
directly, view it on GitHub  > <
https://github.com/mrmojololo/blooket-admin-hack/issues/1053#issuecomment-2461106258>,
 > or unsubscribe  > <
https://github.com/notifications/unsubscribe-auth/BMWYG3NR752SURDS2CYHDSDZ7K3RXAVCNFSM6AAAAABRJAYFWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRRGEYDMMRVHA>
 > .  > You are receiving this because you authored the
thread.Message ID:  > @.>  >
—
Reply to this email directly, view it on GitHub
https://github.com/mrmojololo/blooket-admin-hack/issues/1053#issuecomment-2462278745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMXDLM45XNJG2V2I5URXBRLZ7NVHJAVCNFSM6AAAAABRJAYFWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRSGI3TQNZUGU
.
You are receiving this because you commented.Message ID:
@.***>


Add a test suite

I'd like to help out with this project, but I don't really know the domain. Maybe one way I could be helpful is to set up unit and end-to-end/acceptance testing?

First of all, I'm flattered you're even interested enough to check the project out.
Setting up unit and end-to-end/acceptance testing would be invaluable, since it's one of the most obvious missing pieces right now. It's also something that's not present because I don't really have the know-how, yet. (My testing experience is limited to using mocha on simple npm packages.) Getting proper testing in place would also help a lot now that the project's past initial launch and I need to make sure that ongoing bug fixes and feature additions don't cause regressions.

I am excited for this!


Pdf issues I found

Hi thanks for the great work!
Here are some issues I found when reading the pdf version of this excellent book:

Low resolution Figure 5.5, The roofline performance model has low resolution and thus a little blur, see the screenshot of the official pdf:

This link in Chap11 PGO is outdated: https://github.com/google/llvm-propeller/blob/plo-dev/Propeller_RFC.pdf
This Image covered the line above as shown below:

The link https://sites.google.com/site/intelptmicrotutorial/ is outdated, but web archive has it saved.

Thanks for reporting! I fixed them. Will add them to the errata and push it to the printed version as well. There are a few other low-res images I fixed.


How to do sparql query on Ontop

I'm doing a benchmark on Ontop. But I got below error. My question is how to configure the query?
2021-03-12 10:06:15,633 [main] ERROR [org.aksw.iguana.cc.query.impl.InstancesQueryHandler] -
My configuration:
queriesFile: "queries.txt"
PREFIX : http://example.org/voc#
PREFIX foaf: http://xmlns.com/foaf/0.1/
select ?sensorData ?siid ?val WHERE {
?sensorData a foaf:SensorData .
?sensorData :Siid ?siid FILTER(?siid = 5045).
?sensorData :value ?val .
}
Official query command:
POST http://localhost:8080/sparql
Content-Type: application/sparql-query
Accept: application/json
PREFIX : http://example.org/voc#
SELECT DISTINCT ?teacher {
?teacher a :Teacher .
}
My configuration:
datasets:

name: "DoesNotMatter"
connections:
name: "benchmark"
endpoint: "http://<IP_ADDRESS>:8080/sparql"
updateEndpoint: "http://<IP_ADDRESS>:8080/sparql"
tasks:
className: "Stresstest"
configuration:
#timeLimit is in ms
timeLimit: 3600000
queryHandler:
className: "InstancesQueryHandler"
workers:
- threads: 2
className: "SPARQLWorker"
queriesFile: "queries.txt"
timeOut: 180000
metrics:

- className: "QMPH"

className: "QPS"

- className: "NoQPH"
- className: "AvgQPS"
- className: "NoQ"
#optional otherwise an nt file will be used
storages:

className: "NTFileStorage"
#configuration:
#fileName: YOUR_RESULT_FILE_NAME.nt

Hey,
Thanks for using Iguana :)
The StackTrace of the error is cut off, Could you send the complete StackTrace of the error :)
I guess the queries file isn't loaded properly
the queries.txt file has to have one query per line. so
queriesFile: "queries.txt"
PREFIX : <http://example.org/voc#> PREFIX foaf: <http://xmlns.com/foaf/0.1/> select ?sensorData ?siid ?val WHERE { ?sensorData a foaf:SensorData . ?sensorData :Siid ?siid FILTER(?siid = 5045). ?sensorData :value ?val . }

Other than that:

Thanks for so quickly response, I tried your suggestions, but it still has errors. Please help me to figure out.
benchmark.txt
StackTrace.txt

  workers:
    - threads: 2
      className: "HttpPostWorker"
      contentType: "application/sparql-query"
      responseType: "application/json"
      queriesFile: "/home/program/workspace/iguana/queries.txt"
      timeOut: 180000

Now Server doesn't report error, but when I run IGuana, the log shows that
<Starting Worker[{HttpGetWorker} : {1}].>
What I configured is HttpPostWorker

<Starting Worker[{HttpGetWorker} : {1}].>
Ah that is a logging issue.
THe HttpPostWorker extends the HttpGetWorker but apperently doesn't override the LOGGER.
So you can ignore that there stands HttpGetWorker
Regarding:  org.springframework.web.bind.MissingRequestHeaderException: Missing request header 'Accept' for method parameter of type String
I will look into that and keep you updated. Normally it should send the Post request correctly.
The queryResults will be saved into an ntriple file located in your folder.
For more details on how to read them: http://iguana-benchmark.eu/docs/3.2/usage/results/

Thanks for you support. fixed.


I don't have "admin" interface inside my package

Hi! I have installed this package on my server and I have updated the dependencies, checked the config files, etc.
The problem is that I don't have admin interface and also the php script that sends the request to the admins.
Thank you in advance

Hi,
Any errors? did you follow the instillation steps?

Yes, but inside the package there's no admin folder or file...
Inviato da iPhone

Il giorno 14/nov/2016, alle ore 18:26, Ahmed Alaa<EMAIL_ADDRESS>ha scritto:
Hi,
Any errors? did you follow the instillation steps?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

its MVC based there is no folders for every Route/URL

I don't understand, when I upload the .zip package to the web server, there is no admin interface included (as you say in the guide), so I get a 404 error. I uploaded all the files, gave permissions, imported dependencies and imported database file.., What's wrong?

there is no actual files for every URL its MVC ... the code takes care of the URL so you wont see files for every URL
check your .htaccess file and see...
i cant help you without providing an actual error or trace

cause there are no errors... i link you my page
http://vps336178.ovh.net/ts3chan

looks like there is something wrong with your redirects most likely you have issue with your .htaccess or mod_rewrite

My path is /ts3chan/Publio
Can you send me an example? Thanks
Inviato da iPhone

Il giorno 14/nov/2016, alle ore 21:28, Ahmed Alaa<EMAIL_ADDRESS>ha scritto:
looks like there is something wrong with your redirects most likely you have issue with your .htaccess or mod_rewrite
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm trying but no results.... can we get in contact with ts3?

same error... please help us...

sorry kinda busy 😢  ..
try open yoursite.com/ts3chan/debug dose it show a hash??
if this doesn't work then its 100% .htaccess or modrewrite issue

Nothing, error 404 not found :/

then its server side.. the redirects/modrewrite is not working cant help you with that atm soz :(

Can we speak on a teamspeak (if u want even the TeamSpeak Public server is good)? I think that if we can talk in about 10/15 min we can fix/solve the problem. Please.

i would be happy to join your TS and even help via teamviewer... but currently am working on huge project with very strict timeline
this script is a sideproject :(
i will inform you as soon as i have some free time sorry


Running npx prisma introspect throws access denied error

Bug description and reproduction
This is pretty basic example I used to experiment with Prisma introspect feature and to test it with existing DB. I'm running Postgres database inside Docker container with already defined schema. Existing model just creates one table like:
(
    id SERIAL,
    name VARCHAR(80) NOT NULL,
    PRIMARY KEY(id)
);

My docker compose looks like:
version: "3"

services:
  pg:
    image: postgres:13
    restart: "always"
    expose:
      - "5432"
    ports:
      - "5432:5432"
    environment:
      - POSTGRES_DB=prisma
      - POSTGRES_HOST_AUTH_METHOD=trust
    volumes:
      - "./db/data:/var/lib/postgresql/data"
      - "./db/init:/docker-entrypoint-initdb.d"

After you run docker compose up you will have running DB in a container locally ready to accept connections.
Run npx prisma introspect
You will get following output:
Prisma schema loaded from prisma/schema.prisma

Introspecting based on datasource defined in prisma/schema.prisma …
Error: P1010

User `postgres` was denied access on the database `postgres.public`

I tried also granting permissions to user postgres, no luck.
schema.prisma file
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider = "postgresql"
  url      = "postgresql://postgres@localhost:5432/prisma"
}

generator client {
  provider = "prisma-client-js"
}

Running npx prisma validate is returning ok result.
Expected behavior
It should run introspection and populate schema.prisma file. This is pretty basic example and should be pretty much covered inside the official docs.

Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: 14
Prisma version: 2.21.2

This really look like the user postgres does not have access to the database postgres.public.
Which is weird, as you defined the database as prisma. Hmmm...
What is the schema of that database called? If it is not public, maybe add it as ?schema=foo to your connection string please (https://www.prisma.io/docs/concepts/database-connectors/postgresql#arguments)
Can you try setting a password for the user and adding that to your connection string as well - maybe we have a bug around password less users.

I tried also with adding ?schema=public, same result. .
I even tried with adding user and password so it's not related to passwordless users.

You can try setting basic postgres docker container with one table and try to introspect.

@enoent4400 I think if you try to connect via peer authentication, then you will need to provide a unix domain socket in the connection string.
Can you try setting a password instead and try this? I use the following postgres docker config:
version: '3'
services:
  postgres:
    image: postgres
    ports:
      - 5432:5432
    restart: always
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
    volumes:
      - postgres:/var/lib/postgresql/data
volumes:
  postgres: ~
``

Internal reproduction note: Just try to introspect a database with the original Docker file.

For me it was my other local running instance of postgres. Previously I had installed postgres.app and pgadmin for another project and had it running in the background. So if you're running postgres inside docker, be sure to quit any other local postgres instances. Soon as I did that the issue went away.

Thanks @richardanewman! After trying to debug my config, permissions, etc. all it took was
brew services stop postgresql


Automate the creation of PRs updating image-build-base when image-build-base releases

When image-build-base releases a new version, all the rancher/image-build-xxxx projects [1] should update their Dockerfiles. We are talking about ~24 projects. This process is not automated but manual and the consequence is that most of them are outdated.
It'd be so great that a PR would be created for each of them updating that parameter (e.g https://github.com/rancher/image-build-calico/blob/master/Dockerfile#L4) every time there is a new release of image-build-base.
Ideally, we should trigger this from drone/github_actions/etc in the image-build-base github project as soon as there is a new release. However, as we are still unsure what will be our CI at the end of the year, I think it would be great to start having the functionality here.
[1] https://github.com/orgs/rancher/repositories?language=&q=image-build-&sort=&type=all

Check out https://github.com/rancher/ecm-distro-tools/blob/master/bin/update_go

Check out https://github.com/rancher/ecm-distro-tools/blob/master/bin/update_go

Nice! I did not know this :). Closing!


Cluster Provisioning v2: LKE - Create

We need the option in Dashboard to create Linode clusters.

Closing this for now since there's an iFrame that's sufficient. Once the hosted providers are using the CAPI framework, we can look at this then.


Support OUD enviroments on Windows

OUDBase currently does depend on bash. Bash is missing on Windows ;-)

Basically just bash has to be available on the server. But did not yet test this.

currently no request to test / develop this


Add missing namespace nfl to FastGaussianNoise & aligned_allocator

The FastGaussianNoise class and other random generation functions were not encapsulated in the nfl namespace.
I did some minimal cleanup also.

Oops thx for fixing this I did not think about it.
+1 for merging this PR.

Thanks for the comments, I did some modifications. I think the prng files will eventually need to be revamped, but that is a future work to do.

The instructions in this function are compatible with AMD and Intel 64 bit processors. It won't work for 32 bit architectures. You think we should include 32-bit support ?

If it works for both 64-bit processors it should be ok. Sorry for the confusion.

Ok for me. @serge-sans-paille merge when you think it is ok.

Np, thank you for being picky.

@serge-sans-paille you can merge this pr whenever it is ok for you


VulcanAC vs mineflayer pathfinding

flags bad packets when trying to build

I will put this under enhancements as pathfinder is not designed or made to work with every anti cheat that exists. If you want to try and fix this yourself you are free to open a pull request.

Its pretty easy ngl as u just have to correctly set the stuff in the place block thing


add swiping from child

adds a swipeChild which allows swiping scaffold from left/right child.
#21

This is a great feature, waiting to be merged. :+1:

hmm, a feature that is quite interesting, I hope it quickly merged.

i'm actually waiting for this merge, need this feature so much.


[Bug] oops 1774 broke soca

Description
Guessing oops PR 1774 is the culprit for:
[...]
/work/noaa/da/gvernier/sandboxes/GDASApp/soca/src/mains/GridGen.cc(16): error: object of abstract class type "soca::GridGen" is not allowed:
            pure virtual function "oops::Application::execute" has no overrider
    soca::GridGen makegrid;
[...]

.... oops, forgot to check the existing issues ...


Autocompletion suddently not working anymore.

ST build 3126
Linux Ubuntu 16.04
I have an angular2 project which I moved to angular4. Since the upgrade, the autocompletion in typescript files stopped working. As far as I remember it was working properly before. I'm running un linux ubuntu 16.04.
On a different computer, running a linux VM running on a windows host, it's still working properly, even after the angular upgrade.
Here is the sublime console log, looks like,  at the end, there is an error on a python file.  Project is compiling fine with angular-cli.
Looked at both issues : #574 and #452 and couldn't find any working fix there.

Tried the computer running the ubuntu VM where Typescript autocomplete is working properly and the console shows more or less the exact same output except the last 7 lines :
Exception in thread Thread-2:
Traceback (most recent call last):
  File "./python3.3/threading.py", line 901, in _bootstrap_inner
  File "./python3.3/threading.py", line 858, in run
  File "/home/jp/.config/sublime-text-3/Packages/TypeScript/typescript/libs/node_client.py", line 146, in monitorPostQueue
    self.server_proc.stdin.flush()
BrokenPipeError: [Errno 32] Broken pipe

Btw, on that computer, the sublime settings files doesn't seems to contain any reference to typescript_tsdk setting. So I removed it from my setting file in the non working computer and now everything is working again. Don't know what changed and why it suddenly broke everything (I remember adding it on purpose when I started working with typescript and angular2 to make autocomplete work) but it solved the problem for me.

Hi, just reiterating that I had a typo in the path for the typescript_tsdk setting which caused this issue so this will likely be your issue if you find yourself here.


change Julia LS to use the new dedicated neovim LS wrapper LSPNeovim.jl

This change is to make nvim-lsp use the package LSPNeovim.jl by default.  This simplifies the interface and resolves some issues, see discussion here.
From conversations with others from the Julia community involved with LanguageServer.jl (@kdheepak , @davidanthoff, @non-Jedi), it seems there is consensus we should do this.  If you are involved with LanguageServer.jl please thumbs up/down this PR.

I can't opine on this, I'm not familiar enough with the details of how nvim is integrated with the Julia language server, sorry :)

what is https://github.com/ExpandingMan/LSPNeovim.jl doing that can't be done here instead (in Lua)? Then users can avoid an extra step.
we need to get out of the auto-install business here ( https://github.com/neovim/nvim-lspconfig/issues/334 ) so is there a different way users could install LSPNeovim.jl (a julia package manager or whatever), that can be mentioned in the docs here instead of :LSPInstall ?

I've updated the Julia start commands and it seems to work well now, I would recommend creating an nvim-julia plugin if you'd like to add more advanced configuration or use wrappers around julials

I've updated the Julia start commands and it seems to work well now, I would recommend creating an nvim-julia plugin if you'd like to add more advanced configuration or use wrappers around julials


chore: update comments in ReactiveCommand

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Tidies up more comments.
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
More renaming of This parameter...
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines: https://github.com/reactiveui/reactiveui#contribute
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:

Coverage remained the same at 66.835% when pulling 581eba7cacec7f53a66cbd8f4d94064d2b4b498b on olevett:new-reactive-command-comments into b6209cdd1dfcea809449d6736c79c8b34f11c21d on reactiveui:develop.


Logos

Created Logos in .svg and .png

Hey @nancu,
thanks for the logo!
I appreciate the creativity. I especially like how the gear is split in half; makes the logo more dynamic and a bit playful.
Using the initials in the logo is a clever idea that I hadn't considered.
I'd kind of want to stay closer to the original logo and keep it clean and simple. Maybe we can combine the gear and the "analysis tools" text into one entity and omit the initials? Perhaps we can play a bit with ligatures to spice up the text or emphasize the "y" letter.
Hope that makes any sense. I'm not good at reviewing designs apparently. 😆

Hi @mre,
No problem! I can try thinking of other ideas for the logo.


Custom Logger

Hi!
Nice work on this lib and pluggin!
Do you think it could be a good addition to be able to add a custom logger?
Let's say instead of Log I want to use Timber. Or change the tag. Or priority (info, debug, warn, ...) Of the log tag.
What do you think? Maybe I can open a PR with some guidance from your part.

Great addition!
That was my idea for a second iteration of logger!


HIVE-26990 - Upgrade Iceberg from 1.0.0 to 1.1.0

Iceberg released 1.1.0. Hive currently uses 1.0.0
What changes were proposed in this pull request?
Upgrading the iceberg/pom.xml maven dependency and porting/fixing necessary changes to be able to make all tests green.
Some comments about the changes:

There were some qfile changes as the output contains more detailed information when describing tables.
There were issues about altering partition specs. Had to patch BaseUpdatePartitionSpec.java. After the iceberg fix is merged and released, we can remove that patch: https://github.com/apache/iceberg/pull/6653
Had to port some old changes that haven't ported yet. See the commits.

Why are the changes needed?
To make sure the code compiles and all tests are green.
Does this PR introduce any user-facing change?
There will be some changes in describe metadata tables. See https://github.com/apache/hive/commit/c13294b4c63c457c5b152919c64629960f12a8ea
How was this patch tested?
Ran all the existing tests.

Looks like https://github.com/apache/iceberg/pull/5670 was included only downstream, I guess we can disregard it for now, but it might bite us eventually.


Add Ability to Edit Display Name

Not sure if this is on the roadmap but it would be nice to have the ability to edit the name next to the (@name) section of the profile.

Yep, we call it "slug editing" internally. It's super high on my list, but
its the thing that keeps getting put aside for other stuff that seems more
important in the moment. Definitely on our radar though. 😁
On Tue., Aug. 14, 2018, 02:25 Daryl Yeo<EMAIL_ADDRESS>wrote:

Not sure if this is on the roadmap but it would be nice to have the
ability to edit the name next to the (@name) section of the profile.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1722, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABf2CVq1mMGY9nfAVlLW40mNBq4l_O5Eks5uQm08gaJpZM4V7224
.

@mikekasprzak Any updates on "slug editing"?


Fix typos in README

Fixed a few typos and fixed spacing in README to render Markdown correctly. GitHub renders links OK on docker/community but when you view README individually, the links are broken.

LGTM


BUG: componentWillReceiveProps() state.layout doesn't update

Hi,
I have a scenario where after a layout change, I re-render RGL while changing the item's keys-order only. (Meaning that I have the same keys, but they "sit" different children order) The layout of the props stays the same, but at this point the RGL's state.layout differs from the props.layout
React does an update, and calls RGL's componentWillReceiveProps().
It is clear that the state.layout need to be updated, but it doesn't.
There are 2 points in the function where is fails:

childrenEqual() doesn't recognize the children have changed. As it says in the comment:

/**
 * Comparing React `children` is a bit difficult. This is a good way to compare them.
 * This will catch differences in keys, order, and length.
 */

Also if it did recognize that the children have changed, the new layout from props is not used ! instead it keeps the layout from the stale state.

// If children change, also regenerate the layout. Use our state
    // as the base in case because it may be more up to date than
    // what is in props.
    else if (!childrenEqual(this.props.children, nextProps.children)) {
      newLayoutBase = this.state.layout;
    }

This is the issue.
I'll think about a solution, and post it separately.
Cheers,
Erez

I think maybe the solution should actually come from the first layout comparison in componentWillReceiveProps():
    // Allow parent to set layout directly.
    if (!isEqual(nextProps.layout, this.props.layout)) {
      newLayoutBase = nextProps.layout;
    }

why isn't the comparison done on the this.state.layout?
    if (!isEqual(nextProps.layout, this.state.layout)) {
      newLayoutBase = nextProps.layout;
    }

My guess is that, if someone updates a different prop that doesn't affect the layout (such as margin,...), then maybe you want to keep the state.layout, as stated in another comment in componentWillReceiveProps():
    // ... Use our state
    // as the base in case because it may be more up to date than
    // what is in props.

But I think this is wrong, and it is the responsibility of the user to update his own layout state, so that when re-rendering RGL, it will show the changes. If I got it right, then the rule of thumb with React is that any internal state should always be updated from props in case of an update, e.g in componentWillReceiveProps(). It kind of annoys me that React decided wether to create a new component, or to update a component, and I couldn't find a way to avoid update, and force creation of a new component (thus re-initializing any internal state).


alphabetically order apiFiles before PUT

Corresponds to bug #371. All revisions should be deployed.
Currently, the APIs are deployed in random order, so revision 2 can be deployed before revision 1, which causes rev 1 to be missed.
Alphabetically ordering the API files prior to the PUT requests ensures that the list of files fed to .ForEachParallel is set in the correct order - v3 will come after v2 and v1/original, and rev3 will come after rev2 and rev1, so on and so forth.
I deployed the SampleArtifacts with an additional Swagger Petstore API to demonstrate the initial issue:

The same APIs have all revisions deployed after the change, with correct isCurrent and isOnline properties:

@waelkdouh and @guythetechie
The .ForEachParallel on line 387 of Api.cs in the publisher means that the APIs can still be deployed in incorrect order. While the list itself that is fed to .ForEachParallel is in now in the correct order, the parallel nature of the executions may result in order issues. In the deployment logs below, you can see that the PUT request for myversionedapi-v2 occurred before the PUT for myversionedapi.
Updating the .ForEachParallel to a .ForEach ensures the PUT requests are made in the correct order. I have deployed using .ForEachParallel many times and have not been able to actually cause an error or any deployment issues, though the version order can be incorrect, so I haven't made any updates here.
The logs before the change were as follows:
info: Publisher[0]
      Putting apiVersionSet 6286439d9a310d01468c083c...
Publisher: Information: Putting apiVersionSet 6286439d9a310d01468c083c...
info: Publisher[0]
      Putting API myversionedapi...
Publisher: Information: Putting API myversionedapi...
Publisher: Information: Putting API testapi;rev=2...
info: Publisher[0]
      Putting API testapi;rev=2...
info: Publisher[0]
      Putting API myversionedapi-v2;rev=2...
Publisher: Information: Putting API myversionedapi-v2;rev=2...
info: Publisher[0]
      Putting API myversionedapi-v2...
Publisher: Information: Putting API myversionedapi-v2...
info: Publisher[0]
      Putting API unversioned-petstore;rev=2...
Publisher: Information: Putting API unversioned-petstore;rev=2...
Publisher: Information: Putting API testapi...
info: Publisher[0]
      Putting API testapi...
info: Publisher[0]
      Putting API unversioned-petstore...
Publisher: Information: Putting API unversioned-petstore...
info: Publisher[0]
      Execution complete.
Publisher: Information: Execution complete.
info: Microsoft.Hosting.Lifetime[0]
      Application is shutting down...
Microsoft.Hosting.Lifetime: Information: Application is shutting down...

The logs after the change were as follows:
info: Publisher[0]
      Putting apiVersionSet 6286439d9a310d01468c083c...
Publisher: Information: Putting apiVersionSet 6286439d9a310d01468c083c...
Publisher: Information: Putting API myversionedapi-v2...
info: Publisher[0]
      Putting API myversionedapi-v2...
info: Publisher[0]
      Putting API myversionedapi...
Publisher: Information: Putting API myversionedapi...
info: Publisher[0]
      Putting API myversionedapi-v2;rev=2...
Publisher: Information: Putting API myversionedapi-v2;rev=2...
info: Publisher[0]
      Putting API testapi...
Publisher: Information: Putting API testapi...
info: Publisher[0]
      Putting API testapi;rev=2...
Publisher: Information: Putting API testapi;rev=2...
info: Publisher[0]
      Putting API unversioned-petstore...
Publisher: Information: Putting API unversioned-petstore...
Publisher: Information: Putting API unversioned-petstore;rev=2...
info: Publisher[0]
      Putting API unversioned-petstore;rev=2...
info: Publisher[0]
      Execution complete.
Publisher: Information: Execution complete.
info: Microsoft.Hosting.Lifetime[0]
      Application is shutting down...

If I change .ForEachParallel to .ForEach:
info: Publisher[0]
      Putting apiVersionSet 6286439d9a310d01468c083c...
Publisher: Information: Putting apiVersionSet 6286439d9a310d01468c083c...
info: Publisher[0]
      Putting API myversionedapi...
Publisher: Information: Putting API myversionedapi...
info: Publisher[0]
      Putting API myversionedapi-v2...
Publisher: Information: Putting API myversionedapi-v2...
info: Publisher[0]
      Putting API myversionedapi-v2;rev=2...
Publisher: Information: Putting API myversionedapi-v2;rev=2...
info: Publisher[0]
      Putting API testapi...
Publisher: Information: Putting API testapi...
Publisher: Information: Putting API testapi;rev=2...
info: Publisher[0]
      Putting API testapi;rev=2...
info: Publisher[0]
      Putting API unversioned-petstore...
Publisher: Information: Putting API unversioned-petstore...
info: Publisher[0]
      Putting API unversioned-petstore;rev=2...
Publisher: Information: Putting API unversioned-petstore;rev=2...
info: Publisher[0]
      Execution complete.
Publisher: Information: Execution complete.
info: Microsoft.Hosting.Lifetime[0]
      Application is shutting down...
Microsoft.Hosting.Lifetime: Information: Application is shutting down...

@waelkdouh @guythetechie moving back to draft as I am still able to trigger errors by making certain revisions current

The changes do allow all revisions to be deployed and appear in API Management successfully, but it introduces a bug - if any revision other than rev1 is current, the PUT request fails with the message:
[{"code":"ValidationError","target":"IsCurrent","message":"Can't set new revision as current."}]
I then updated the list order so current revisions are deployed before non-current revisions. In the case where revN is current and rev 1 is not, if revN is deployed before rev1, the error disappears but we're back to the original issue, where only revN deploys successfully and rev1 is missing.
I then reverted my changes back to what is currently in main and paused the execution of the publisher after each API is deployed, examining how the exported template from Azure changes. When rev2 is deployed before rev1, the following occurs regardless of which API revision is current (using testapi and testapi;rev=2 as an example):

PUT for testapi;rev=2 is made. A "Microsoft.ApiManagement/service/apis" resource is with "name": "..../testapi" and "apiRevision": "2"
PUT for testapi is made, but the URL that corresponds to a now existing API ^. After the PUT, there is still only one resource.

When I deploy in alphabetical order so rev2 is deployed after rev1 and pause execution the same way, the following occurs (using testapi and testapi;rev=2 as an example again):

PUT for testapi is made. A "Microsoft.ApiManagement/service/apis" resource is with "name": "..../testapi" and "apiRevision": "1"
PUT for testapi;rev=2 is made. A  "Microsoft.ApiManagement/service/apis" resource is with "name": "..../testapi;rev-2" and "apiRevision": "2". Two "Microsoft.ApiManagement/service/apis" resources now exist.

Essentially, when revision N is PUT first, it creates an API resource with the API version's base name and sets the revision number to N. When revision 1 is then PUT, it updates an existing API.
On the other hand, when revision 1 is PUT first, it creates an API resource with the API version's base name and sets the revision number to 1. When another revision is then PUT, the url the PUT request is sent to does not correspond to an existing API, and thus creates a new API. If that revision is current, however, an error is thrown.
I am closing this PR as alphabetically ordering the APIs before their PUT requests introduces an error if revN is current.

@guythetechie thoughts on this?

@waelkdouh @guythetechie API Release support would potentially fix/alleviate the issue the ordering introduces as it would enable making other revisions current.


Request: Use dual icons like System -> Hotkey Switch

Is it possible to set dual-icons on a static button? Or have a seperate "input" called Static Switch?
That functions like the hotkey switch with has 2 icons available? 1 for pushed down, 1 when it's not?
Examples i could think of are:
Landing gear = up, icon = green. Landing gear = down, icon = red
Cruise control = on, icon = green. Cruise control = off, icon = red.

The game does not provide feedback on the status. So this is not possible

It's not so for having status feedback, but it's for when it's pressed or not pressed. So if you press the button it takes the color. So basicly the request is to have the option to assign 2 icons, like on the System -> Hotkey Switch

No
I will not make landing gear up/ down image until he game tells me if the gear is currently up or down
See GitHub description where is described how to use multi action switch to set up toggle function with 2 images


Fix generation of type forwarder metadata

We were not setting the public key/token for the reference.

@dotnet-bot test this please


v0.12.0: Separate SplitAndMergeTag into SplitTag/MergeTag for compile-time safety

This is the follow-up for #137 to avoid unexpected/undefined behavior at runtime.
Finally, the typestate pattern is in place. Separation into 2 traits was the missing link.

Finished. Only marked as Draft because it is based on #137 which has not been merged yet and might still change.
Merging this PR instead of #137 would also be an option.

This looks good after a rebase. Thanks!


💡 Those exported modules that are being used within the current file should not be tagged as unused exports.

Suggest an idea for Knip
In a file, there are two methods being exported, which are export A and export B. Here, A is imported by app.tsx, and B is being referenced by A. In such a scenario, B would also be identified as an unused export. Can we possibly optimize for such situations? In other words, if the exported module is being referenced within the current file, then it should not be tagged as an unused export.
For example
test.tsx

App.tsx

B is recognized as an unused module.

While I think Knip is behaving as expected and tries to optimize what's flagged or not, it does provide this option: https://knip.dev/reference/configuration#ignoreexportsusedinfile. Would that work for you

I really appreciate it, this is quite helpful for me.

Excellent, let's close this ticket then.


Error Validation: use .accessibilityValue matching the visible error message text for each invalid input

IMO, .accessibilityValue is another valid technique to expose an input's helper text and error message. Unlike .accessibilityHint, I don't think users can disable the announcement of an element's .accessibilityValue. This is why I think using .accessibilityValue may be a more robust approach.
My recommendation is to update the Error Validation coding technique (and associated documentation page) to include a "good" example that demonstrates how to use .accessibilityValue.

Thanks for the feedback! I've added that second good example using .accessibilityValue.
Will be out it in the App Store sometime today likely.

Closing because value property should only be used for the value the user types into the input.


chore: use latest math package

I think that the runtime version needs to be bumped.

yes, that's the thing i have problem with. Previous merged PR bumped the runtime version but that was not released yet. So the same runtime version can be used with this change too.
@jak-pan am i right ?
I know that this is something we already talked about but i am still not happy bumping runtime version with every PR.

Always bump the runtime if needed, it's not because of release but because the developers that will be running this and our own infrastructure that will be testing compatiility between commits. If you don't bump it someone might run this successfully for a while and then it will crash for him because the runtime will be incompatible at given function call. We want to avoid these errors.


Move compile-time configuration into a runtime configuration

Addresses issue #4.
To make this work as a runtime configuration, we have to store the heap limit, split threshold, max blocks, and alignment somewhere. I naturally would have put them in the Heap struct, but I didn't want to mess up the nice graphic you made in the README, so I made them static. Thoughts?
Previously the TA_HEAP_START could be configured separately from the control structure. I changed it to (size_t)base + sizeof(Heap) + heap_blocks * sizeof(Block) like we discussed, but if that's not acceptable I'll can add that configuration back in if you can provide a little guidance on your ideal scenario.

Hi @winduptoy - sorry for the delay, I've been held up w/ other projects. Will try to review & merge this over the next few days... THANKS already in advance!

Finally merged! Sorry about the delay - and THANK YOU! 🎉


Downloads number of package

Just curious to know which is used most but I didn't see anything on deno.land/x

For starters, adding number of stars might help people to choose.

I don't see how this would be possible, because deno.land/x is just serving files from GitHub/etc., not from a dedicated registry like npm. Perhaps on the CDN side, number of file requests can be tracked?

This is possible, but will probably be difficult.

How about adding stars badge like this.
https://img.shields.io/github/stars/oakserver/oak.svg?style=social&label=Star&maxAge=2592000

Something like this.

The registry is still in early stages (lacks lots of features, etc.), may be too young to add an analytics.
Showing GitHub stars is both simple and effective.

Sorry for being late, I got busy. I created the pull request. Feedback and suggestions are appreciated.

I believe we can close this issue, PR is merged for the badge and database.json is temporary so once we have solution for that then this can be done.

Closing in favour of #2358


Multi-assignment syntactic sugar - apply to multiple with only one value

If I want to assign multiple variables to the same value, I have to do this:
local Var1, Var2, Var3 = 0, 0, 0

It would be nice if specifying one implicitly meant you wanted it to apply to all of them:
-- All of them are assigned `0` instead Var2 and Var3 being assigned `nil`
local Var1, Var2, Var3 = 0

I would understand any potential compatibility issues, but it would be nice instead of having to repeat the variable multiple times.

This is already possible with local x, y, z = nil.
This is not backward compatible, and in some cases can be confusing. For example, what does this do?
local t1, t2 = {}

print(t1 == t2)

One can argue that t1 and t2 has the same table, but one can also argue that t1 and t2 should not have the same table. This means the above snippet is semantically ambiguous, and that's awful from a debugging point of view.


Flash attention

hi, thanks for documenting this.
i'm curious if you were able to train successfully with peft + flash attention?
i keep seeing loss spikes after a few iterations

i tried on another machine and it works fine there, so something else is going on. i will continue investigation in https://github.com/Dao-AILab/flash-attention/issues/311

@tmm1 what machine have you used where it is not working?

it is a local machine with 3090. I got it working by starting with a fresh CUDA 11.8 conda environment. the flash-attn tests were failing in the broken env.


Worked like a charm - thank you!

Just wanted to report back that I had success using your tool with Diablo 2 and it has been great. No Actual issue, just wanted to say thanks.
For anyone reading this unfamiliar with software, here’s what I did to get it working:

Download the release (the zip file Containing the compiled executable program, found here: https://github.com/woroniecki/Joypad-To-Keyboard/releases/tag/release) and extract it to a folder locally.
Download his Diablo2 config file (the JSON text file linked in another issue here https://github.com/woroniecki/Joypad-To-Keyboard/tree/master/MapController/Assets/Binds) and save it locally.
Launch the executable and use the ‘load’ button to select the config JSON you downloaded.  (I need to use run as administrator or it can’t interact with my Diablo 2 window which is also run as administrator)
Launch Diablo 2 (I use the PlugY mod to play in a large centered borderless windowed, but it shouldn’t be required)
If your cursor isn’t centered when using the left stick, you’ll need to adjust the center pixel values in the tool. In the tool, click on the left stick and adjust the screen center locations so it centers on your character when Diablo 2 is running. I also increased the center distance value to get it working a bit better.
Set the in-game ‘show items’ Alternate hotkey to X In the menu.

And that’s it!   This tool allows me to play the game much longer before my arms get sore from the repetitive clicking, and in fact I find it works even better than the default mouse control scheme for some characters. Thanks again!

Thanks, Is it okay if I will add this instruction to promo video on youtube?

Thanks for the guide and thanks woroniecki for making this tool. This is super cool!! So much better than anything that just maps the mouse to a joystick. I mostly play D2 but I can see it being useful for other games too. Great work.


Should spinlock 31 be exposed to end users via the spinlock API?

VictorKoenders: I wonder if spinlock 31 should be removed here as it's used internally. I can't imagine people needing more than 30 spinlocks
Originally posted by @VictorKoenders in https://github.com/rp-rs/rp-hal/pull/270#discussion_r790711369

I thought about this for a while.
On the one hand, in theory the same spinlock could be used by both user software and the HAL at the same time, if done carefully. And a bug would at worst cause a deadlock, so even without unsafe, there would not be a source of unsoundness.
But on the other hand, I don't see a good reason why one would want to do this, there are more then enough other spinlocks available. And in case some special use case really needs to access the same spinlock as the HAL, one could still write some unsafe code to access the register directly.
TL;DR: I agree with https://github.com/rp-rs/rp-hal/commit/4a540d041abf60c61ec93180946be995f2cfecac

Why not document that and expose in a way that would require using unsafe function?

My rationale is quite selfish: I do not want to deal with bugs related to "action at a distance" when people use this spinlock and it dead-locks their critical_section. Unsafe+documentation is insufficient deterrent sometimes.
That, and I'm happy to delay dealing with problems of insufficient spinlocks until someone actually has a use-case that requires all 32.

I think it was open long enough, and can be reopened if anyone comes up with a good reason to do so.
Closing this now.


Clarify rules/concepts re number of Providers/StateNotifiers can be used across app data without missing updates

When designing an App with multiple tables (e.g. say including depth in parent/child arrangement, e.g. TodosDataSet => TodoLists => TodoItems) documentation to understand how many Providers and StateNotifiers there can be without "missing updates".
Some items/questions within this:
[A] Application with no persistance to database say

By "missing updates" I am thinking if you had a separate StateNotifier with a Provider for each "table" on it's own then this may be indepentant islands of state, so updating a parent StateNotifier may not trigger updates to children StateNotifiers?
For example in my example (TodosDataSet => TodoLists => TodoItems) would the "rules" be:

only one (1) state notifier that covers all these "tables" so they are one "set" of data? (e.g. one state notifier that has within it's state all levels of data, so TodosDataSet, TodoLists and TodoItems)
can have as many StateNotifierProvider's as you wish that refernce the single StateNotifier? As the actual state all comes from the single StateNotifier?

[B] Application with data persisted somewhere (e.g. local SQLite database say)

I am assuming you may need to decide whether your app is really going to use StateNotifier data, with the underlying persistance layer just being there to "save" when the used decided to "save" data.
Assuming for the purpose of this item however you assume the concept is to automatically "persist" data as changes occur.  What would be the rules around how many StateNotifiers and StateProviders could be used here to ensure no "update notifications" are missed?
For example should there be only one StateNotifier for the whole database, I'm hoping no. But if you have multiple StateNotifiers for each section of the application/database schema, how do ensure that an update to StateNotifier_A triggers an update to StateNotifier_B?
Example:  Say in the app (represented in the database tables) there is a ability to indicate what categories for todo lists a user can see in the UserStateNotifier, but then how does it trigger the TodoDatasetStateNotifier to ensure the scope of Todolist to be shown is correctly changed.

Hope this makes sense.

so updating a parent StateNotifier may not trigger updates to children StateNotifiers?

What does this mean exactly? There should never be a situation where you'll obtain outdated data in Riverpod. If a parent updates, the children will too

Perhaps a bit of Newbie question so apologies of so. One way to cast it is, if you have an app to build with say 20 or so database tables, then you are then deciding how to map these to StateNotifiers and Providers, how would you decide how many to have?  For example one state notifier to cover whole app?  (Say using freezed to represent all data)

There's no real answer to that. It depends on so many things
But I'd heavily advise against having everything in a single provider.
In general it is better to split your code is numerous providers. This separate responsibilities

ok - If that's ok I'll try to think of a sample app and post back here with a couple of specific questions....that highlight the principles questions in my head...

:wave:
This issue seems stale. In the lack of an answer, I'll close it. If you still want something to be covered, please open a new issue while making sure you clarified the questions :smile:


Hyperlink pipeline changes

Required items, please complete
Change(s):

Add support to check hyperlink validation for mainTemplate and CreateUiDefinition files.
When there is any change in Data connector azuredeploy file then it should check if "Website_run_from_package" attribute value is having correct hyperlink or not.

Reason for Change(s):

Add support to check hyperlink validation for mainTemplate and CreateUiDefinition files.
When there is any change in Data connector azuredeploy file then it should check if "Website_run_from_package" attribute value is having correct hyperlink or not.

Version Updated:

NA

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Testing result:
When links are invalid in maintemplate:

When all changes are good in azuredeploy file in data connector

When Website Run from Package property link is invalid:

When all links in Data connector azuredeploy file is correct:

Closing this as rishikesh is working on this.


Fixed a glitch in DatePickerRange

This PR is for fixing a glitch in DatePickerRange where the gray part was still shown when both start- and enddate were on the same date.
Sample page
What was happening

The gray part was still shown on the left side of the selected date range when both start- and enddate were on the same date

What was done

Added a rule to the SCSS code to separate the date ranges where both the startRange and endRange classes were on the same day from the existing date ranges where both classes are on different days.

Test Steps

Open a DateRangePicker
Select the same day twice to get a range of 1 day.
Open the DateRangePicker again.
The gray part on the left should be gone after the fix is implemented.

Screenshots
Before the fix:

After the fix:

Checklist

[X] tested locally
[ ] documented the code - the code speaks for itself.
[X] clean all warnings and errors of eslint
[ ] requires changes in OutSystems (if so, provide a module with changes)
[ ] requires new sample page in OutSystems (if so, provide a module with changes)

Hello dekkinga :wave:
Thanks for your Pull Request. It looks like this may be your first contribution to an OutSystems Open Source project.
Before we look into your contribution, we need you to accept the :memo: OutSystems Contributors License Agreement.
After you read and accept the terms of the agreement, reply to this message saying I read, understood and accept the OutSystems CLA.
After this step, we'll review your Pull Request and provide any feedback if needed.
Thank you and feel free to keep contributing! 🚀

I read, understood and accept the OutSystems CLA.
From: Gonçalo M. @.>
Sent: Wednesday, 19 April 2023 16:35
To: OutSystems/outsystems-ui @.>
Cc: Remco Dekkinga @.>; Author @.>
Subject: Re: [OutSystems/outsystems-ui] Fixed a glitch in DatePickerRange (PR #727)
Hello dekkingahttps://github.com/dekkinga 👋
Thanks for your Pull Request. It looks like this may be your first contribution to an OutSystems Open Source project.
Before we look into your contribution, we need you to accept the 📝 OutSystems Contributors License Agreementhttps://outsystems-public-dl.s3-eu-west-1.amazonaws.com/opensource/cla/OutSystems-Contributor-License-Agreement-2020-03-23.pdf.
After you read and accept the terms of the agreement, reply to this message saying I read, understood and accept the OutSystems CLA.
After this step, we'll review your Pull Request and provide any feedback if needed.
Thank you and feel free to keep contributing! 🚀
—
Reply to this email directly, view it on GitHubhttps://github.com/OutSystems/outsystems-ui/pull/727#issuecomment-1514850604, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH57OYPA4KP53LSLGRVTSM3XB7Z2HANCNFSM6AAAAAAXEE5RAY.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
DISCLAIMER:
Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te informeren. Wij adviseren u om bij twijfel over de juistheid of de volledigheid van de e-mail contact met de afzender op te nemen.
Nothing in this email shall bind LINKIT in any contract or obligation. This e-mail is for the intended addressee only. If you have received it in error then please delete it and notify the sender by return e-mail. In case of doubt about correctness or completeness of this e-mail please contact the sender.

Hello dekkinga 👋
Thank you for your contribution and we are glad to inform the PR was merged after our validation.
With this, you'll also receive our OutSystems community badge for "OS Component Contributor".
Cheers!


LE Audio: Callbacks as singletons or lists?

Is your enhancement proposal related to a problem? Please describe.
Typically the callback structs used by LE Audio are currently singletons, but most of them are not defined as const. For these we should either add const or we should allow multiple users to register it.
Describe the solution you'd like
Add const to callback structs for LE Audio profiles
Describe alternatives you've considered
Allow multiple users of the callbacks, which is done by adding a slist node and storing the callbacks in a list similar to e.g. the bt_conn_cbs.
Additional context
We may want to decide this based on each profile.

Zephyr-bt F2F: Decide for each profile, open issues when needed.  Closing.


fix get user transactions, allow to pass body options

According to paddle api docs https://developer.paddle.com/api-reference/product-api/transactions/listtransactions#request-parameters
the correct entity to retrieve transactions of a user is user instead of users that is currently used:
https://github.com/avaly/paddle-sdk/blob/461a9909ac351982d1de7e2e2d1a367c096bcac9/sdk.js#L215
I've fixed the typo and added the option to pass the body to _getTransactions that will allow to pass the page parameter.

Hello @avaly
Can you please take a look at these changes?
Thanks

For anyone that needs this bug fix I've released a<EMAIL_ADDRESS>package with these changes

I've been offline for a while, so I didn't see your PR.
Please add some unit tests for the changes you made and I'll merge the PR afterwards.

Closed in #40 and #41


Prevent loading of assets from non-asset-folders

By throwing a newly created NotInAssetPathException.
Problems:

How do we correctly determine that we are outside of the asset folder?
Everyone using the Asset Manager needs to wrap that Exception and show the appropriate dialogue. We can't do that for all at once.

https://github.com/jMonkeyEngine/sdk/blob/5be6123ca8f7f8ea4d57c23d52e61fe6713bb8e5/jme3-core/src/com/jme3/gde/core/assets/AssetDataObject.java#L182 should already be in place.


Adding AUC and F1 score to collection of evaluation metrics

@rachelyangzhou

Keshav just directed me to his very helpful code that computes these metrics: https://github.com/gsbDBI/Learning_Tools_Competition/blob/master/src/notebook/simulated_data/evaluation.py

Thank you for linking me to this code, I am adding them to the BEMB package.

I have added the support for a couple more metrics (see the screenshot below), hope this provides more insights on model tunning.


Allow for editing context

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

#302  👈
#301
#299
#298
main

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

Join @acco and the rest of your teammates on  Graphite


User feedback reporting

We should have a "feedback" or "contact us" form where users can enter feedback about new features that they might want, or enter in a bug report.
These reports should then be able to reviewed / triaged by an admin.

@epicfaace - can you go into a little more detail on what you meant by this?

Just added -- thanks.

The UI/UX long-term roadmap (18 mths+) includes the creation of an Online Community and Feature Request panel for data consumer engagement.


Remove Typescript code from core repo

Fixes https://github.com/trustwallet/wallet-core/issues/1427

removed from release repo too


PaCMAP is stochastic with sparse data even if random seed is set

Hi all,
I noticed that (the current version) of PaCMAP seems to give stochastic results on sparse binary data even if random seed is set. Below is an example of code with randomly generated data -- in the first case, the data is sparse and the result is stochastic on my machine; in the second case the data is not sparse and the result is deterministic.
I have not given deeper thought to whether it is reasonable to run PaCMAP on sparse data, but it would still be nice if it was deterministic when random seed is set.
Could you have a look into this?
Many thanks!
import pacmap
import numpy as np

###----
### Stochastic when there's sparsity
###----
print('\n\nBinary data with high proportion of zeros')

# Create a binary dataset with low frequency of 1s
rng = np.random.default_rng(seed=42)
d = rng.binomial(n=1,p=0.01,size=(1000,100))

# Just in case - if any columns are all zeros, remove these
mask = d.sum(axis=0) > 0
d = d[:,mask]
print('Shape of data: \n{}'.format(d.shape))
print('Number of nonzero elements in each column: \n{}'.format(d.sum(axis=0)))
print('Snapshot of data: \n{}'.format(d[:10,:10]))

# Pacmap
e = pacmap.PaCMAP(n_components=2, n_neighbors=None, MN_ratio=0.5, FP_ratio=2.0, random_state=42)
t = e.fit_transform(d, init="pca")

e2 = pacmap.PaCMAP(n_components=2, n_neighbors=None, MN_ratio=0.5, FP_ratio=2.0, random_state=42)
t2 = e2.fit_transform(d, init="pca")

# Test
print(t[:3, :3])
print(t2[:3, :3])
test = np.sum(np.abs(t-t2)) < 1e-8
print('Difference between values of two runs is less than 1e-8? {}'.format(test))
test2 = (t == t2).all()
print('Values between two runs are equal? {}'.format(test2))

###----
### Deterministic when there's less sparsity
###----
print('\n\nBinary data with roughly equal proportion of zeros and ones')

# Create a binary dataset with low frequency of 1s
rng = np.random.default_rng(seed=42)
d = rng.binomial(n=1,p=0.5,size=(1000,100))

# Just in case - if any columns are all zeros, remove these
mask = d.sum(axis=0) > 0
d = d[:,mask]
print('Shape of data: \n{}'.format(d.shape))
print('Number of nonzero elements in each column: \n{}'.format(d.sum(axis=0)))
print('Snapshot of data: \n{}'.format(d[:10,:10]))

# Pacmap
e = pacmap.PaCMAP(n_components=2, n_neighbors=None, MN_ratio=0.5, FP_ratio=2.0, random_state=42)
t = e.fit_transform(d, init="pca")

e2 = pacmap.PaCMAP(n_components=2, n_neighbors=None, MN_ratio=0.5, FP_ratio=2.0, random_state=42)
t2 = e2.fit_transform(d, init="pca")

# Test
print(t[:3, :3])
print(t2[:3, :3])
test = np.sum(np.abs(t-t2)) < 1e-8
print('Difference between values of two runs is less than 1e-8? {}'.format(test))
test2 = (t == t2).all()
print('Values between two runs are equal? {}'.format(test2))

##
print('PaCMAP version: {}, numpy version: {}'.format(pacmap.__version__, np.__version__))

The output I get is:
Binary data with high proportion of zeros
Shape of data:
(1000, 100)
Number of nonzero elements in each column:
[12 16 11 11 11 14  7  6  8 11  8 10 11  9  8 13 10 11  5 10  9 11  9  9
 11 21 14 11 13 12 15  8 11  7 10 11  6  8  6 10  7  9  9 12  6 15  5  9
  8  7  9  8 11  9 15  5  6  8 11 14 12 13  7  9  8  6 12  8  6 12 12 14
 17  7 14 12 12  8 10 13  6 13 15 12  6  7 10 13  9 13  8  7  7 17  9 12
  9 10 15  7]
Snapshot of data:
[[0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 1 0 0 0 0 1]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 0]
 [0 0 0 0 0 0 0 0 0 1]
 [0 0 0 0 0 0 0 0 0 0]]
C:\Users\andres.tamm\Anaconda3\lib\site-packages\pacmap\pacmap.py:774: UserWarning: Warning: random state is set to 42
  warnings.warn(f'Warning: random state is set to {_RANDOM_STATE}')
C:\Users\andres.tamm\Anaconda3\lib\site-packages\pacmap\pacmap.py:774: UserWarning: Warning: random state is set to 42
  warnings.warn(f'Warning: random state is set to {_RANDOM_STATE}')
[[ 0.8841729   2.0089896 ]
 [-0.5350942   0.95636046]
 [ 1.7903003   2.135278  ]]
[[ 0.73095715 -2.7870746 ]
 [ 0.6337722  -0.6057222 ]
 [ 1.952701   -2.0199978 ]]
Difference between values of two runs is less than 1e-8? False
Values between two runs are equal? False

Binary data with roughly equal proportion of zeros and ones
Shape of data:
(1000, 100)
Number of nonzero elements in each column:
[506 519 499 509 499 526 520 492 500 511 520 512 510 526 532 489 503 496
 502 487 491 508 509 518 496 467 488 510 498 516 488 520 516 509 495 511
 485 498 528 520 514 472 481 522 488 513 491 520 499 507 468 513 515 510
 493 489 496 508 480 523 494 518 489 491 514 507 489 507 489 520 501 487
 502 505 498 476 503 517 507 474 502 498 513 492 518 493 502 491 511 494
 504 508 472 500 505 534 478 497 533 493]
Snapshot of data:
[[1 0 1 1 0 1 1 1 0 0]
 [1 1 0 1 1 1 0 0 0 1]
 [1 1 1 0 0 0 0 1 0 1]
 [1 0 1 1 1 0 0 1 0 0]
 [0 1 1 0 1 1 0 1 0 1]
 [1 1 1 1 1 1 0 1 0 0]
 [0 1 1 1 1 1 1 0 1 0]
 [0 0 0 1 0 1 1 1 0 0]
 [1 0 1 1 0 0 1 0 1 1]
 [0 0 0 0 1 1 0 0 0 0]]
C:\Users\andres.tamm\Anaconda3\lib\site-packages\pacmap\pacmap.py:774: UserWarning: Warning: random state is set to 42
  warnings.warn(f'Warning: random state is set to {_RANDOM_STATE}')
C:\Users\andres.tamm\Anaconda3\lib\site-packages\pacmap\pacmap.py:774: UserWarning: Warning: random state is set to 42
  warnings.warn(f'Warning: random state is set to {_RANDOM_STATE}')
[[ 1.0503646 -2.2979746]
 [ 1.6191299  2.3795164]
 [-3.1472695 -1.3276936]]
[[ 1.0503646 -2.2979746]
 [ 1.6191299  2.3795164]
 [-3.1472695 -1.3276936]]
Difference between values of two runs is less than 1e-8? True
Values between two runs are equal? True
PaCMAP version: 0.6.3, numpy version: 1.21.1

Thank you for bringing this up -- this issue is very well written! In release notes of 0.5.0, we have noticed such edge case that the user may get slightly different results even if the random_state parameter is set to be the same, due to some numba parallelization issue. It seems like this is not the case here in the first snippet. I will try to replicate the problem locally and look into this.

Thank you! It would be interesting to know what the solution will be. I hope the issue is reproducible (and not a typo in my code). Please let me know if I can be of help somehow.
Out of curiosity, I also ran the first part of my code 10 times and computed the correlation between embeddings from two runs. They were similar, but sometimes quite different -- [0.68,  0.75,  0.85, -0.15,  0.69,  0.81,  0.71,  0.49,  0.73, 0.81].

… due to some numba parallelization issue.

I think it would be useful to be able to turn this parallelisation off, so that the output is deterministic with the same random seed.

Hi @hyhuang00, thank you for looking into this! I found a workaround that I believe is satisfactory for me -- I replaced all zeros with small random numbers (in [-2e-5, 2e-5]), which then led to stable sorting.
Thanks!

Thank you for sharing your solution! I will close this issue.

Thank you for sharing your solution! Closing the issue for now.


[Bug]: Accuracy of crossplane_managed_resource metric counters

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)
All group version kind.
Resource MRs required to reproduce the bug
Any, but a DynamoDB table may suffice.
Steps to Reproduce
git clone git@github.com:upbound/configuration-observability-oss.git
cd configuration-observability-oss
make
make e2e
kubectl apply -f examples/oss.yaml
kubectl apply -f examples/folder-grafana.yaml
kubectl apply -f examples/dashboard-grafana-crossplane-sli-2-metrics.yaml

Update the namespace variable to upbound-system if providers are not running in crossplane-system namespace.
Load provider secrets and establish AWS providerConfig as shown at https://github.com/upbound/platform-ref-aws
Create an example table MR per https://marketplace.upbound.io/providers/upbound/provider-aws-dynamodb/v1.12.0/resources/dynamodb.aws.upbound.io/Table/v1beta1
Observe duration from sync to ready and compare with crossplane_managed_resource_first_time_to_readiness_seconds_bucket metrics and related metrics. See below under what happened bug description for the list.
kubectl -n <PROVIDER_NAMESPACE> port-forward <PROVIDER_DYNAMODB_POD> 8080
curl http://localhost:8080/metrics | grep Table

What happened?
When creating a Dynamo table the observed max for crossplane_managed_resource_first_time_to_readiness_seconds_bucket was 3 seconds for dynamodb.aws.upbound.io/v1beta1, Kind=Table.
However, the rady minus sync timestamp was 25 seconds.
conditions:

lastTransitionTime: "2024-08-23T18:54:22Z"
reason: Available
status: "True"
type: Ready
lastTransitionTime: "2024-08-23T18:53:57Z"
reason: ReconcileSuccess
status: "True"
type: Synced
lastTransitionTime: "2024-08-23T18:54:20Z"
reason: Success
status: "True"
type: LastAsyncOperation

Relevant Error Output Snippet
There is no error. Just the metric counter values do not seem to line up with the calculations derived from the timestamps of the transitions to sync true and ready true.

Based on the following time stamps, it took 15 seconds to create a dynamo table from sync to ready.

  - lastTransitionTime: "2024-08-26T19:45:47Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2024-08-26T19:46:02Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-08-26T19:46:00Z"
    reason: Success
    status: "True"
    type: LastAsyncOperation

But that does not seem to line up with the following metrics counters.
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="5"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="10"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="15"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="30"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="60"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="120"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="300"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="600"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1800"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="3600"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="+Inf"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_sum{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"}<PHONE_NUMBER>94
crossplane_managed_resource_first_time_to_readiness_seconds_count{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 1
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1e-08"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1e-07"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1e-06"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="9.999999999999999e-06"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="9.999999999999999e-05"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="0.001"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="0.01"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="0.1"} 0
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1"} 1
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="10"} 1
crossplane_managed_resource_first_time_to_reconcile_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="+Inf"} 1
crossplane_managed_resource_first_time_to_reconcile_seconds_sum{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 0.395364009
crossplane_managed_resource_first_time_to_reconcile_seconds_count{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 1
crossplane_managed_resource_ready{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=GlobalTable"} 0
crossplane_managed_resource_ready{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 1
crossplane_managed_resource_ready{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=TableItem"} 0
crossplane_managed_resource_ready{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=TableReplica"} 0
crossplane_managed_resource_synced{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=GlobalTable"} 0
crossplane_managed_resource_synced{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 1
crossplane_managed_resource_synced{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=TableItem"} 0
crossplane_managed_resource_synced{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=TableReplica"} 0
upjet_resource_external_api_calls_total{operation="CreateTable",service="DynamoDB"} 1
upjet_resource_external_api_calls_total{operation="DescribeTable",service="DynamoDB"} 13
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1"} 1
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="5"} 1
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="10"} 1
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="15"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="30"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="60"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="120"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="300"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="600"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1800"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="3600"} 2
upjet_resource_reconcile_delay_seconds_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="+Inf"} 2
upjet_resource_reconcile_delay_seconds_sum{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"} 12.809876446
upjet_resource_reconcile_delay_seconds_count{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="5"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="10"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="15"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="30"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="60"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="120"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="300"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="600"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1800"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="3600"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="+Inf"} 2
upjet_resource_ttr_sum{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"}<PHONE_NUMBER>3
upjet_resource_ttr_count{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"} 2

### Crossplane Version

1.16.0

### Provider Version

1.11.0

### Kubernetes Version

1.29, 1.30

### Kubernetes Distribution

Kind

### Additional Info

- Please confirm that crossplane_managed_resource_first_time_to_readiness_seconds_bucket measures the duration from MR sync true to MR ready true.
- Please also examine the following counters for accuracy:
    - crossplane_managed_resource_deletion_seconds
       The time it took for a managed resource to be deleted.
    - crossplane_managed_resource_drift_seconds_bucket
       Measures drift caused by external sources mutating resource state, such as a person or third party system adding tags to cloud resources.
    - crossplane_managed_resource_first_time_to_readiness_seconds
       The time it took for a managed resource to become ready for the first time after creation.
    - crossplane_managed_resource_first_time_to_reconcile_seconds
      The time it took for a managed resource to be detected by the controller.
    - upjet_resource_ext_api_duration
      Measures in seconds how long it takes a Cloud SDK call to complete.
    - upjet_resource_external_api_calls_total
      The number of external API calls.
    - upjet_resource_ttr
      Measures in seconds the time-to-readiness (TTR) for managed resources.
    - upjet_resource_reconcile_delay_seconds
      Measures in seconds how long the reconciles for a resource have been delayed from the configured poll periods.

@humoflife I wasn't able to reproduce the issue, neither in a kind cluster I created nor in one created by configuration-observability-oss after following your instructions above. Both methods seemed equivalent to me, by the way.
I'll list my results below, but first, I would like to clarify what metrics measure. Both crossplane_managed_resource_first_time_to_readiness_seconds and upjet_resource_ttr measure the time from resource creation (not synced condition) to ready condition (reference to source code for the former and for the latter). So we should compare the measured values to the time difference between status.condition Ready's lastTransitionTime and metadata.creationTimestamp.
In my tests, the time it took from metadata.creationTimestamp to status.condition Synced was around 3 seconds. So, the difference in what you observe (Synced to Ready) and what the metrics measure (creationTimestamp to Ready) should be small, unless you applied the resource manifest before the provider was ready. In that case metrics would also include the time it took provider to become ready, which seems to be the case in your reported results above, as the following line implies:
crossplane_managed_resource_first_time_to_readiness_seconds_sum{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"}<PHONE_NUMBER>94

Because there was a single resource, the sum of the metric is the time it took from resource creation to readiness. In my tests, DynamoDB Tables were ready in around 20 seconds.
Can you make sure to apply the manifest when the pod is ready? Then I would expect you to get similar results to the ones I got:
# HELP crossplane_managed_resource_first_time_to_readiness_seconds The time it took for a managed resource to become ready first time after creation
# TYPE crossplane_managed_resource_first_time_to_readiness_seconds histogram
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="5"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="10"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="15"} 0
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="30"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="60"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="120"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="300"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="600"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1800"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="3600"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="+Inf"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_sum{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 22.793627546
crossplane_managed_resource_first_time_to_readiness_seconds_count{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table"} 1

# HELP upjet_resource_ttr Measures in seconds the time-to-readiness (TTR) for managed resources
# TYPE upjet_resource_ttr histogram
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="5"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="10"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="15"} 0
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="30"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="60"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="120"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="300"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="600"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="1800"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="3600"} 2
upjet_resource_ttr_bucket{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1",le="+Inf"} 2
upjet_resource_ttr_sum{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"} 44.038504133
upjet_resource_ttr_count{group="dynamodb.aws.upbound.io",kind="Table",version="v1beta1"} 2

metadata:
  creationTimestamp: "2024-08-29T07:38:15Z"
status:
  conditions:
  - lastTransitionTime: "2024-08-29T07:38:37Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-08-29T07:38:18Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2024-08-29T07:38:34Z"
    reason: Success
    status: "True"
    type: LastAsyncOperation

PS: There could be differences in crossplane_managed_resource_first_time_to_readiness_seconds and upjet_resource_ttr, as noted in release notes of v1.4.0, because of crossplane-runtime not being async-aware. The difference is negligible for fast-provisioning resources, such as DynamoDB Table. For resources that take a long time to be created, such as creating an RDS Instance from a backup, upjet_resource_ttr_bucket is more accurate.
PPS: Thanks to your report, I discovered a potential bug that records upjet_resource_ttr_bucket multiple times, instead of once, for a resource. I'll open an issue in Upjet repository.

PPS: Thanks to your report, I discovered a potential bug that records upjet_resource_ttr_bucket multiple times, instead of once, for a resource. I'll open an issue in Upjet repository.

Sort of related here @mergenci, but could you also help me understand the crossplane_managed_resource_first_time_to_readiness_seconds_bucket better too? If you were reconciling a single resource, why would there be an entry in multiple buckets? Wouldn't that one resource fall into a single bucket corresponding for how long it took to first become ready? 🤔
Example below, why is the one dynamodb resource in more than 1 bucket? Thanks!
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="1800"} 1
crossplane_managed_resource_first_time_to_readiness_seconds_bucket{gvk="dynamodb.aws.upbound.io/v1beta1, Kind=Table",le="3600"} 1

@jbw976, Prometheus buckets are cumulative. The label le stands for “less than or equal to”, so the bucket le="3600" includes le="1800", as well as anything in between. All in all, there's a single DynamoDB resource counted in the metric.

Verified that the respective sum counter divided by the count counter are accurately showing the average time to create a particular group version kind resource.
Closing this issue.