feat: Color scheme update

This PR gives our restake frontend a custom WhisperNode dark theme! Please go through all pages and give me any feedback on things you want to change :)

Hey @gh0stdotexe! I have updated the logo and link colors with the pushes I added this morning, I also changed the operated by ghost section to just have the whispernode logo at the moment, I think once we have all our services themed and named we can update the footer to link to all our different websites (WhisperBlocks, whisperStake, etc)


Fixed links to classes in docstrings

@zezha-msft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #354 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev    #354   +/-   ##
=====================================
  Coverage   86.2%   86.2%
=====================================
  Files         61      61
  Lines       5133    5133
  Branches     554     554
=====================================
  Hits        4425    4425
  Misses       555     555
  Partials     153     153

Impacted Files
Coverage Δ

...common/azure/storage/common/cloudstorageaccount.py
70% <ø> (ø)
:arrow_up:

...zure-storage-common/azure/storage/common/models.py
90.79% <ø> (ø)
:arrow_up:

...orage-common/azure/storage/common/storageclient.py
90.83% <ø> (ø)
:arrow_up:

azure-storage-blob/azure/storage/blob/models.py
95.38% <ø> (ø)
:arrow_up:

azure-storage-file/azure/storage/file/models.py
93.61% <ø> (ø)
:arrow_up:

...-storage-table/azure/storage/table/tableservice.py
95.39% <ø> (ø)
:arrow_up:

...storage-blob/azure/storage/blob/pageblobservice.py
91.12% <ø> (ø)
:arrow_up:

...storage-blob/azure/storage/blob/baseblobservice.py
94.46% <ø> (ø)
:arrow_up:

...orage-blob/azure/storage/blob/appendblobservice.py
94.38% <ø> (ø)
:arrow_up:

...mmon/azure/storage/common/sharedaccesssignature.py
63.69% <ø> (ø)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


Some Initial Predefined Metrics

Partially Fixes #309

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

In the file src/einsteinpy/symbolic/predef/de_sitter.py:

Line 42:1: W293 blank line contains whitespace


WebUI not Connecting to server

after updating ollama webui i can no longer connect to my ollama instance. All settings are the same the only thing i changed is adding a volume for database. it says my server cant be connected. running latest image for ollama everything worked perfect until current build...

just noticed when going to ollama url with /api i get 404. How do i ensure ollama api is being exposed

Hi, Thanks for creating this issue! Could you make sure that the ollama api url is set to /ollama/api in the webui settings? Also, try this alternative command: https://github.com/ollama-webui/ollama-webui/blob/main/TROUBLESHOOTING.md#ollama-webui-server-connection-error, Keep us updated, Thanks!

Ollama is served through a reverse proxy since the instance runs on my servers not localhost. I was one of the original people to start using this and issue number 2 or 3 was helping me resolve my original issue. Ollama api is served from https://ollamaapi.mydomain.co/api. Before the update with the auth and account creation everything worked fine...

OLLAMA_API_BASE_URL=https://example.com/api
I have this set as a build argument and in my webui settings it is indeed correct.
Offcourse the url is that of my personal domain but the variable i did pass through.

Hmm, You're using docker run -d -p 3000:8080 -e OLLAMA_API_BASE_URL=https://ollama.jryng.com/api -v ollama-webui:/app/backend/data --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main command, and ollama api url is set to /ollama/api in the webui settings, correct?

yes sir i will post my docker compose.
Docker-Compose.txt

Assuming both ollama and ollama-webui containers are running on the same machine, try this:
version: '3.9'

volumes:
  ollama-data:
    driver: local
    driver_opts:
      type: "nfs"
      o: "addr=<IP_ADDRESS>,soft,rw"
      device: ":/mnt/marsSSD/Docker-Volumes/Ollama/ollama-data/_data/"
  ollamaui-data:
    driver: local
    driver_opts:
      type: "nfs"
      o: "addr=<IP_ADDRESS>,soft,rw"
      device: ":/mnt/marsSSD/Docker-Volumes/Ollama/ollamaui-data/_data/"

services:
  app:
    image: ollama/ollama:latest
    volumes:
      - type: volume
        source: ollama-data
        target: /root/.ollama
        # volume:
          # nocopy: true
    ports:
      - "11434:11434"
    environment:
      OLLAMA_ORIGINS: "*"
      NVIDIA_VISIBLE_DEVICES: all
    deploy:
      resources:
        reservations:
          generic_resources:
            - discrete_resource_spec:
                kind: "NVIDIA-GPU"
                value: 1
      mode: replicated
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.labels.nas == true

  web:
    image: registry.lab.awptechnologies.co/ollama-webui:latest
    environment:
          - "OLLAMA_API_BASE_URL=http://app:11434/api"
    volumes:
      - type: volume
        source: ollamaui-data
        target: /app/backend/data
        # volume:
          # nocopy: true
    depends_on:
      - app
    ports:
      - "8040:8080"
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
        condition: on-failure
      placement:
        constraints:
          - node.labels.nas == true

so maybe try to rebuild with no arguments and add the environment variable?

still didnt work...

Hmm, let's try replacing registry.lab.awptechnologies.co/ollama-webui:latest with ghcr.io/ollama-webui/ollama-webui:main

do you think that it will make a difference i cloned and built from main. the reason it has that domain is because i have a private registry

but i will try. Could it be bacause im on ollama 1.17 which is the latest instead of 1.16

It should work fine with 0.1.17 as well, I'm a bit puzzled on why it won't work for you. I believe the docker logs from the webui container will probably help us with the troubleshooting.

using ghcr.io/ollama-webui/ollama-webui:main still failed...
I reverted to an older build in my registry one before the auth stuff and it still works fine...
I dont believe it is the settings. not sure what it could be

ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     Started server process [7]
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     Waiting for application startup.
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     Application startup complete.
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64535 - "GET / HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64536 - "GET /_app/immutable/chunks/scheduler.0545783f.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64535 - "GET /_app/immutable/entry/start.6ae36a3b.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64538 - "GET /_app/immutable/entry/app.48aa6f73.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64537 - "GET /_app/immutable/chunks/singletons.c585103f.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64537 - "GET /_app/immutable/chunks/navigation.34e880ce.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64536 - "GET /_app/immutable/nodes/0.79bc6ad9.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64538 - "GET /_app/immutable/chunks/constants.2c7fe818.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64535 - "GET /_app/immutable/chunks/index.e2fa35e3.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64540 - "GET /_app/immutable/chunks/stores.d79df05d.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64541 - "GET /_app/immutable/chunks/index.fbad1410.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64536 - "GET /_app/immutable/chunks/FileSaver.min.ace3aac6.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64545 - "GET /_app/immutable/chunks/Navbar.2d4a2d36.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64538 - "GET /_app/immutable/chunks/index.1021f11b.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64543 - "GET /_app/immutable/chunks/index.13820637.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64542 - "GET /_app/immutable/chunks/index.a4e3af26.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64544 - "GET /_app/immutable/nodes/3.39b25d92.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64546 - "GET /_app/immutable/assets/Navbar.e3b04202.css HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64539 - "GET /_app/immutable/nodes/1.c7d43fa0.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64537 - "GET /_app/immutable/nodes/2.5d2f8931.js HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64541 - "GET / HTTP/1.1" 200 OK
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64540 - "GET /auths/ HTTP/1.1" 200 OK
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64545 - "GET /modelfiles/ HTTP/1.1" 200 OK
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64543 - "GET /assets/fonts/Arimo-Variable.ttf HTTP/1.1" 304 Not Modified
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64546 - "GET /chats/ HTTP/1.1" 200 OK
ollama_web.1.d2cf8w5cb6fr@net1server    | INFO:     <IP_ADDRESS>:64542 - "GET /ollama.png HTTP/1.1" 304 Not Modified

so i made leway....
i went to the raw address my ip :8040 and it works so its something to do with serveing the webui over reverse proxy.

lol i figured it out
had to clear browser cache

Nice, feel free to reach out if you encounter any issues in the future!


Skew extension pls

Is it possible to have a skew extension, like penguinmod?

penguinmod has a skew extension?

penguinmod has a skew extension?

It does, and SA will in 1.35 (though TurboWarp is multiple SA versions behind, so I don't know when it will be added).

penguinmod has a skew extension?

It does, and SA will in 1.35 (though TurboWarp is multiple SA versions behind, so I don't know when it will be added).

They're not referring to the costume editor

Oh, I just kinda assumed they meant addon by "extension" because the other user did

Oh, I just kinda assumed they meant addon by "extension" because the other user did

We're in the extensions repo, so it's safe to assume no one here is referring to addons

Is it possible to have a skew extension, like penguinmod?

Image Effects has a skew block, its a bit funky though...

Trying it out, why does it skew like that???

Trying it out, why does it skew like that???

Cuz the viewbox gets messed up. I don’t know how to fix it, yet….

check the pm source,

From: SharkPool-SP @.>
Sent: Tuesday, October 3, 2023 1:27 PM
To: TurboWarp/extensions @.>
Cc: Subscribed @.***>
Subject: Re: [TurboWarp/extensions] Skew extension pls (Issue #1070)
Trying it out, why does it skew like that???
Cuz the viewbox gets messed up. I don’t know how to fix it, yet….
—
Reply to this email directly, view it on GitHubhttps://github.com/TurboWarp/extensions/issues/1070#issuecomment-1745417031, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAGGRICUBAEV4NB6MWD6RELX5RDHXAVCNFSM6AAAAAA5OMMAROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGQYTOMBTGE.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

check the pm source,
…

that one doesnt work either last time I checked

hm

From: SharkPool-SP @.>
Sent: Tuesday, October 3, 2023 2:52 PM
To: TurboWarp/extensions @.>
Cc: Surv @.>; Comment @.>
Subject: Re: [TurboWarp/extensions] Skew extension pls (Issue #1070)
check the pm source,
…
that one doesnt work either last time I checked
—
Reply to this email directly, view it on GitHubhttps://github.com/TurboWarp/extensions/issues/1070#issuecomment-1745539553, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAGGRIHIJ6TW5K3IMHAYXMLX5RNG7AVCNFSM6AAAAAA5OMMAROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGUZTSNJVGM.
You are receiving this because you commented.Message ID: @.***>


[Docs] Support same client Id for applications over different tenants

Is your suggestion related to a missing or misleading document? Please describe.

Currently in IS client ID is considered to be unique across the server and as a result the same client ID cannot be used in two different tenants. However when there are specific terms like CONSOLE, MYACCOUNT, etc, organization bound client ID is a valid requirement and should provide this capability.
Same client ID should be able to use across different tenants. This improvement will be done with https://github.com/wso2/product-is/issues/16370. Need to document this properly.

Optional Fields
Additional context

Related Issues:

@ThaminduDilshan is this deliver with the IS 7.0.0. If not, shall we move this to  new dashboard. https://github.com/orgs/wso2/projects/97/views/1

This is a doc issue. Should we add it to new dashboard?

This needs to be completed when related sections are added to the documentation.
Related PR: https://github.com/wso2/docs-is/pull/3987


Anonymous GDPR consent

See RAY-214 and RAY-222 (might be duplicates). We asked how to set consent for anonymous users. Pawel says it's very complex but maybe it can be done in Spartacus. Accelerator used a cookie. We can work with Team Argos as they are developing the CDS portion.

@Xymmer I'm not sure about why it's complex, but I might something. I've created an umbrella ticket for token-consent-management, see #1323

dupe of #2124


ALMS1 Protein Structure and Oncoplot Variant Classifications

Hi,
1- When I run the lollipopPlot function for ALMS1, I get the error message, "Structure for protein ALMS1 not found."
Will you please add it to maftools?
2- By default the oncoplot function does not show all variant types. Specifically, 3'UTR. 3'Flanking, Translation_Start_Site, Splice_Region, Intron and a few others are not shown when the plot is generated. Why is that?
THANKS!
Code-----------
lollipopPlot(
maf = Nigerian_Tumor.maf,
gene = 'ALMS1',
AACol = "HGVSp",
showMutationRate = TRUE,
showDomainLabel = FALSE,
roundedRect = TRUE,
domainBorderCol = NA,
legendTxtSize = 1.25,
colors = test_pal_2,
labelPos = 27,
axisTextSize = c(1.5, 1.5),
pointSize = 2
)
oncoplot(maf = Nigerian_Tumor.maf,
top = 30,
clinicalFeatures = c('Gsum'),
colors = test_pal_2,
annotationColor = GScolors
)

Hi,

I have added the ALMS1 to the database. Please install from GitHub for the update.
By default only non-synonymous variants are plotted. You can define your own list of variant classifications to be considered as non-syn. See vc_nonSyn in ?read.maf for details.

Thanks for the quick assist.
One last thing, how does maftools distinguish non-synonymous and synonymous mutations?

It stores non-syn and syn variants in two separate slots of MAF object. See ?MAF-class for details.


file name too long

IOError: [Errno 36] File name too long: u'azurerm_network_security_group.citrix-xd-0feb107a-80db-493a-8ea0-3da8bca85a47-kebbz__Citrix-Deny-All-a3pgu-0feb107a-80db-493a-8ea0-3da8bca85a47.tf'
IOError: [Errno 36] File name too long: u'azurerm_network_security_group.citrix-xd-0feb107a-80db-493a-8ea0-3da8bca85a47-kebbz__Citrix-Deny-All-a3pgu-0feb107a-80db-493a-8ea0-3da8bca85a47.tf'
Error in az2tf.py
Any reasonable way to bypass this? thank you.

Can you post the debug output please:
./az2tf.py -s yoursub -d yes -v yes -r network_security_group
maybe add -g citrix-xd-0feb107a-80db-493a-8ea0-3da8bca85a47-kebbz
if that's the name of the resource group ?

I think I will just skip this resource group since I don't care about it; but perhaps this is useful to report it to you anyway.

Project archived with the release of the 2.0 azurerm providers


Allow restapi=false

Just a quick PR to allow specifying restapi=false in Ansible to skip the tasks in ceph-restapi role.

Why don't you simply remove this line?
https://github.com/ceph/ceph-ansible/blob/master/site.yml#L17

@leseb I could (and I did, at first), but this way I figured one can choose to enable/disable ceph-restapi at deploy-time, without having to modify the ceph-ansible sources.

Hum I don't like adding a lot of when statements, can you do something like this instead?

{ role: ceph-restapi, when: not restapi }

The restapi var exists here: https://github.com/ceph/ceph-ansible/blob/master/group_vars/all#L116
This will also disable the section in the ceph.conf

Sorry, you're right. That's what I should've done in the first place. Fixed.

Thanks!


Missing key/explanation for the colour scale on the CE90 plot indicate

My colleagues and I have been unable to work out what the colour scale on the CE90 plot represents - see e.g. this example from the readme, the bottom left plot:

It doesn't appear to be the absolute displacement of the points, nor the percentile. Density of points is a possibility, but I'm unsure of how to interpret the values if so.
Could a label be added to the plot to explain its meaning?

Hi Daniel,
Thank you for your feeback. It is the density of key points in relation to their displacement.
We will consider your proposal about adding a label.


WIP: Support deploying and publishing plugins

This PR is outdated.
One thing blocking this to proceed is that when multiple client is connected to the same plugin worker, we don't know which client initiated the plugin api call. We need to think a bit more on how to do this.


Code compiled with error-prone 2.0.15 is compiled against Guava 20

We have code which is using older version of Guava library (17). We use error-prone to compile it. Since updating to error-prone 2.0.15, we are running into this exception: java.lang.NoSuchMethodError: com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
It turns out that this method has been added in Guava 20: https://github.com/google/guava/blob/master/guava/src/com/google/common/collect/Sets.java#L667 (iterator method has been there before but has been inherited from super-class, with different return type)
While our project doesn't use Guava 20, latest error-prone does, which leads us to believe that our code has been compiled against this version. :-(
Expected: compile against jar files provided in our code, not against internal error-prone dependency.

Are you seeing the crash in Error Prone, or when you run code that was compiled by Error Prone?
And do you have a repro?

I see the crash in the code compiled by error-prone, when running it with old Guava on the classpath. This very same code with same guava jar works fine when compiled with error-prone 2.0.14. I will try to make a small self-contained example tomorrow if needed.
-peter

On 7 Dec 2016, at 18.22, Liam Miller-Cushon<EMAIL_ADDRESS>wrote:
Are you seeing the crash in Error Prone, or when you run code that was compiled by Error Prone?
And do you have a repro?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Which build system are you using?

Ant, and error-prone javac task for ant.

On 7 Dec 2016, at 18.50, Liam Miller-Cushon<EMAIL_ADDRESS>wrote:
Which build system are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I've created small test case in https://github.com/pstibrany/error-prone-issue-492.git

I can confirm this issue with gradle.

Version 2.0.15 will cause some guava related type interference errors when to project is compiled with a older guava version. Switching to 2.0.14 will solve most of them, but the created bytecode differs from artifacts compiled without the ant adapter.


acquireTokenSilent fails when identity server is on localhost

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.32.1
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.5.1
Public or Confidential Client?
Public
Description
Our authority is Duende Identity Server running on https://localhost:5000 (for development).  When I updated our project dependencies to include the latest version of msal-common, acquireTokenSilent began throwing errors.  It looks like it is failing to retrieve the access token.  It doesn't appear to actually be making any network calls to our IDP (except to retrieve the openid configuration object).
Upon investigating the msal-common library, there is a regex that was recently added to /lib/msal-common/src/cache/entities/CredentialEntity.ts.  This regex fails to recognize localhost:5000 as the domain.  The method is called getCredentialType().
Error Message
Uncaught (in promise) InteractionRequiredAuthError: no_tokens_found: No refresh token found in the cache. Please sign-in.
at InteractionRequiredAuthError.AuthError [as constructor] (AuthError.ts:49:1)
at new InteractionRequiredAuthError (InteractionRequiredAuthError.ts:44:1)
at InteractionRequiredAuthError.createNoTokensFoundError (InteractionRequiredAuthError.ts:71:1)
at RefreshTokenClient.
Identity Provider
Other
Browsers Affected (Select all that apply)
Chrome
Regression
@azure/msal-common 9.0.1
Source
External (Customer)

@konstantin-msft Is this related to the recent push? Can you please verify?

We are also hitting this issue.
Did you find a work-around or do you know which version's do work ?

@konstantin-msft Is this related to the recent push? Can you please verify?

Yes, this one is related to the recent push. Working on a fix.

I was able to workaround by manually adding "@azure/msal-common" version 9.0.1 as a dependency in my package.json.

I've been experiencing this error too.

Can you please try upgrading to @azure/msal-browser-2.33.0?

Can you please try upgrading to @azure/msal-browser-2.33.0?

I was already using v2.33.0
what worked for me was deleting the node_modules folder and the package lock file, and running npm install
seems to be working fine since then

Could be old node-modules pointing to older msal-browser. Closing.


Current release doesn't work with DeepVariant 1.6.0

Describe the bug
I understand that current default version of DeepVariant in the suggested input JSON 1.5.0.
I have replaced it with 1.6.0 because it has now been available for a while.
HiFi-human-WGS-WDL with 1.6.0 now hangs (idles, doing nothing) without quitting in the deepvariant.deepvariant_call_variants phase.
Last line in log:
BackgroundConfigAsyncJobExecutionActor [6784f40cdeepvariant.deepvariant_call_variants:NA:1]: Status change from - to WaitingForReturnCode
Last lines in subtask tree subfolder stderr
tensorflow.python.framework.errors_impl.NotFoundError: Unsuccessful TensorSliceReader constructor: Failed to find any matching files for /opt/models/pacbio/model.ckpt
Details

Release Version = 1.1.0
Backend = Cromwell on HPC with Docker actors
Inputs = singleton sequenced to 30x on Revio
Failing task(s) = deepvariant.deepvariant_call_variants

Expected behavior
Expected DeepVariant 1.6.0 to be a drop-in replacement by configuring "1.6.0" in the input JSON.
Additional context
Novice user. Used all default parameters as given, only with 1.6.0 for DeepVariant.

After replacing 1.6.0 back to 1.5.0 - the workflow appear to work fine. (the result aligned.BAM of course is the same; "samples" for tensorflow are ~ the same, and all stages finished normally

Hi Sergey,
We break up DeepVariant into three different tasks to balance cost/time and use resources efficiently.  While the run_deepvariant.py command typically doesn't change much from version to version, the parameters for "internals" like make_examples, call_variants and postprocess_variants can change a lot from version to version.  There were a few significant changes from DeepVariant v1.5.0 to v1.6.0, including how model files are stored.  Unfortunately, that means it's more complicated than just changing the version number.
Our develop branch (https://github.com/PacificBiosciences/HiFi-human-WGS-WDL/pull/103) has been updated to use DeepVariant v1.6.0, but we aren't ready to merge this into main and cut a new release yet (so use at your own risk). In the documentation for the next release, we'll make it clearer that we typically only support one version of DeepVariant per release, and I'll likely remove the optional deepvariant_version and custom model inputs (they'll still be implemented, just not in the templates or examples) to avoid confusion.  These inputs are really useful if I want to test a new unreleased model, but confusing to end users.
Billy

Addressing this with better documentation in the next release.

Will current release work down-compatible? (e.g. if version is set to "1.4.0"?

I intend to run HG002-rep1 (and maybe all five exemplar datasets) from PBCLOUD store to see identical results, for validation)

There have been API differences for each of the last few releases that make it difficult to maintain backwards compatibility.  The next release will only support DeepVariant v1.6.0.


Simplify the codebase by avoiding metaprogramming

Following on from https://github.com/mpmath/mpmath/issues/683#issuecomment-1537412261 concerning the speed of creating a context object and see the past discussions in gh-178.
The mpmath codebase uses a number of metaprogramming features that increase complexity for what I suspect is relatively little benefit (mostly DRY and micro-optimisation). These make the codebase hard to follow and also defeat static code analysis which is increasingly integrated in modern Python editors. I propose to remove these and move towards ordinary Python code with plain functions, methods and attributes.
Specifically I suggest:

Eliminate dynamic class generation. Make e.g. mpf a simple type that just has _mpf_ and ctx attributes.
Write methods in ordinary Python code rather than generating them dynamically either with exec or by attaching them from decorators.
Use more traditional methods for reducing boilerplate like reusable functions.

One example of this is dynamically created classes like:
https://github.com/mpmath/mpmath/blob/29b47ce9af262287c7dd00f537eded49a74e3885/mpmath/ctx_mp_python.py#L584-L596
There are also functions and methods created from code strings at runtime:
https://github.com/mpmath/mpmath/blob/29b47ce9af262287c7dd00f537eded49a74e3885/mpmath/ctx_mp_python.py#L280-L293
We also have methods that are dynamically added to classes:
https://github.com/mpmath/mpmath/blob/29b47ce9af262287c7dd00f537eded49a74e3885/mpmath/functions/functions.py#L16-L20
Some of these happen at import time and others happen when a context object is created and add measurable overhead to the cost of creating a context:
In [9]: from mpmath import MPContext, mp

In [10]: %timeit MPContext()
538 µs ± 16.6 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

In [11]: %timeit mp.clone()
561 µs ± 27.3 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

In [12]: %timeit mp.cos(1)
10.9 µs ± 253 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

In [18]: %prun -s cumulative [mp.clone() for _ in range(1000)]
         863004 function calls in 1.736 seconds

   Ordered by: cumulative time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    1.736    1.736 {built-in method builtins.exec}
        1    0.000    0.000    1.736    1.736 <string>:1(<module>)
        1    0.002    0.002    1.736    1.736 <string>:1(<listcomp>)
     1000    0.005    0.000    1.734    0.002 ctx_mp.py:297(clone)
     1000    0.022    0.000    1.718    0.002 ctx_mp.py:63(__init__)
     1000    0.007    0.000    0.831    0.001 ctx_base.py:42(__init__)
     1000    0.364    0.000    0.783    0.001 functions.py:18(__init__)
     1000    0.355    0.000    0.775    0.001 ctx_mp.py:96(init_builtins)
   213000    0.270    0.000    0.378    0.000 ctx_mp_python.py:1014(_wrap_specfun)
    43000    0.356    0.000    0.372    0.000 ctx_mp_python.py:979(_wrap_libmp_function)
   220000    0.080    0.000    0.080    0.000 {built-in method builtins.setattr}
     1000    0.073    0.000    0.073    0.000 ctx_mp_python.py:585(__init__)
   256000    0.048    0.000    0.048    0.000 {method 'get' of 'dict' objects}
    17000    0.020    0.000    0.038    0.000 rational.py:31(__new__)
    14000    0.017    0.000    0.037    0.000 ctx_mp_python.py:336(__new__)
     1000    0.023    0.000    0.023    0.000 matrices.py:749(__init__)
    26000    0.020    0.000    0.020    0.000 {built-in method builtins.getattr}
    17000    0.016    0.000    0.018    0.000 rational.py:7(create_reduced)
     1000    0.008    0.000    0.015    0.000 ctx_base.py:52(_init_aliases)
    24000    0.011    0.000    0.011    0.000 {built-in method __new__ of type object at 0x7f2bc4270a40}
     1000    0.005    0.000    0.010    0.000 ctx_mp_python.py:612(_set_prec)
     1000    0.008    0.000    0.010    0.000 inverselaplace.py:668(__init__)
     1000    0.004    0.000    0.006    0.000 quadrature.py:461(__init__)
     5000    0.003    0.000    0.006    0.000 ctx_mp_python.py:597(make_mpf)
     1000    0.003    0.000    0.004    0.000 libmpf.py:59(prec_to_dps)
     1000    0.002    0.000    0.002    0.000 ctx_base.py:458(memoize)
     1000    0.002    0.000    0.002    0.000 rszeta.py:54(__init__)
     2000    0.002    0.000    0.002    0.000 quadrature.py:21(__init__)
     2000    0.002    0.000    0.002    0.000 {built-in method builtins.max}
     1000    0.001    0.000    0.001    0.000 ctx_mp_python.py:602(make_mpc)
     1000    0.001    0.000    0.001    0.000 {built-in method builtins.round}
     4000    0.001    0.000    0.001    0.000 inverselaplace.py:17(__init__)
     1000    0.001    0.000    0.001    0.000 ctx_mp_python.py:620(<lambda>)
     1000    0.001    0.000    0.001    0.000 ctx_mp_python.py:607(default)
     1000    0.001    0.000    0.001    0.000 {method 'update' of 'dict' objects}
     1000    0.000    0.000    0.000    0.000 {method 'items' of 'dict' objects}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

Ideally the cost of creating a new context object would be small enough that it could be worthwhile to create one just for the purposes of a single function call. The context object only has a handful of genuine attributes so it should not be this expensive to create:
In [29]: class Context:
    ...:     __slots__ = ('prec',)
    ...:     def __init__(self, prec=53):
    ...:         self.prec = prec
    ...:

In [30]: %timeit Context()
235 ns ± 25.1 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

I think that it would be better to rewrite these things using ordinary Python code with a primary emphasis on keeping the code simple and easy to understand and maintain. Future versions of CPython will also boost the performance of much Python code but mpmath will potentially not be able to benefit as much from these optimisations because they are generally targeted at simple straight-forward code.
With a simpler codebase it would also be easier to aim for bigger performance improvements by making it easier to swap different backends in and out and to leverage e.g. python_flint if available. The small performance benefits that are achieved by this metaprogramming could be made a lot greater just by having an optional C/Cython backend at least for basic types like mpf but it any such backend in a non dynamically typed language would not be able to replicate the metaprogramming. The python_flint module could house a faster version of mpf and MPContext if it was to be used as an optional backend for mpmath.

That seems reasonable.  However,

Make e.g. mpf a simple type that just has mpf and ctx attributes.

Are you suggest ctx attribute as an instance property?
I think we could use contextvars.ContextVar to store the current context and provide an API to get/set one.  Then we could make the ctx.mpf to be a simple type and the mpf.context will just run query to get the current context.  I believe this could be a relatively simple change.
(Another issue with _mpf is that we have the libmpf.py, that implements floating-point arithmetic in a functional style.  Not sure if this layer simplify the codebase or add a significant performance bonus.)

Write methods in ordinary Python code rather than generating them dynamically either with exec or by attaching them from decorators.

I doubt that the second is something wrong.  Why do you think so?

There are also functions and methods created from code strings at runtime

See #702.
Remaining cases are make_hyp_summator() and identify().

Are you suggest ctx attribute as an instance property?

Effectively it already is an instance attribute but it is implemented by having a dynamically created class with a class attribute. I'm suggesting not to have the dynamically generated class and just have ctx as an instance attribute.
Currently it is like this:
class _mpf:
    def __init__(self, value):
        self.value = value

    def __repr__(self):
        return "mpf(%s) (%s)" % (self.value, self.ctx)

class Context:
    def __init__(self, name):
        self.name = name
        self.mpf_type = type("mpf", (_mpf,), {})
        self.mpf_type.ctx = self

    def mpf(self, value):
        return self.mpf_type(value)

    def __repr__(self):
        return "Context(%s)" % self.name

ctx1 = Context("default")
ctx2 = Context("other")

a = ctx1.mpf(1)
b = ctx2.mpf(2)
print("a =", a)
print("b =", b)

I would instead write it like:
class mpf:
    def __init__(self, value, ctx):
        self.value = value
        self.ctx = ctx

    def __repr__(self):
        return "mpf(%s) (%s)" % (self.value, self.ctx)

class Context:
    def __init__(self, name):
        self.name = name

    def mpf(self, value):
        return mpf(value, self)

    def __repr__(self):
        return "Context(%s)" % self.name

ctx1 = Context("default")
ctx2 = Context("other")

a = ctx1.mpf(1)
b = ctx2.mpf(2)
print("a =", a)
print("b =", b)

Write methods in ordinary Python code rather than generating them dynamically either with exec or by attaching them from decorators.

I doubt that the second is something wrong. Why do you think so?

One problem with the decorator approach as currently implemented is that it is slow when creating a context object (see the profile above).
Another problem is just that it makes the codebase complicated to navigate and understand. Many different files and functions need to be inspected just to understand exactly how one function calls another. Usually I would follow things like that by jumping from one function to another in my editor using "go to definition" (gd in vim) but that fails as does all static analysis like type checking code completion etc when the methods are assigned dynamically.

I agree with this. I often find it hard to figure out where stuff is because of this. Especially if the only point of the metaprogramming is to avoid some code duplication, it would be better to either use standard methods of avoiding duplication (like factoring things into functions or subclasses), or to just duplicate the code.

Another example is multiple pickling issues with the current code base.

Effectively it already is an instance attribute but it is implemented by having a dynamically created class with a class attribute.

On another hand, this is a huge change in semantics: right now we have different mpf types per context.  You suggest instead something like gmpy2.mpfr.
I did some experiments in https://github.com/skirpichev/mpmath/tree/simple-mpf branch.  Not sure it worth a draft pr, let me know.  But I'm surprised there are only ~20 test failures with a decent part of this - broken isinstance(foo, mp.mpf) checks.  All changes are in the ctx_mp_python.py so far - the rest is things like type(m)(-1)->-ctx.one change in the elliptic.py, can be accepted in the master branch.

On another hand, this is a huge change in semantics: right now we have different mpf types per context.

Is that a huge change in semantics? Do you think that code outside of mpmath really relies on these dynamic types?
Probably something in SymPy would break but that is just because SymPy reaches into the internals of mpmath too much.

I did some experiments in https://github.com/skirpichev/mpmath/tree/simple-mpf branch. Not sure it worth a draft pr, let me know

The commit looks good to me.

But I'm surprised there are only ~20 test failures with a decent part of this - broken isinstance(foo, mp.mpf) checks.

I'm not so surprised because the dynamically created classes do not really achieve anything in terms of behaviour.

Do you think that code outside of mpmath really relies on these dynamic types?

Maybe.  Don't get me wrong, I like this idea.  In a long term, with this, probably we even could use (optionally) gmpy's mpfr/mpc instead of mpmath's mpf/mpc.
But this will be not a backward compatible change.

Probably something in SymPy would break but that is just because SymPy reaches into the internals of mpmath too much.

Lets test that: https://github.com/diofant/diofant/pull/1356 (I think the situation will be more or less same for the SymPy).
UPD: And yes, it does.

The commit looks good to me.

WIP: https://github.com/mpmath/mpmath/pull/719

I'm not so surprised because the dynamically created classes do not really achieve anything in terms of behaviour.

There are other issues (e.g. pickling), which aren't simple to fix.

Ok, now there are only pickling-related failures.

Now pickling works.


Add command line tool for adding multiple office users

Description
Right now, a manually generated migration is required to add new office users. When there are many new users to add writing these migrations by hand can be tedious and error prone. Eventually, the admin interface will replace this process, but in the meantime it'd be nice to have a script that could help generate these migrations.
Note:
I wasn't completely sure that there was a real need here (feel free reject if not), but last week we'd added 13 new office users and writing the SQL by hand involved a lot of copying and pasting from the spreadsheet we were sent. It seemed like a script would simplify this a bit.
Setup
Generate a sample list of fake test users and save in a csv file formatted like below.
| First Name | Last Name | Email                    | Phone          | Transport Office (UUID)              |
|------------|-----------|--------------------------|----------------|--------------------------------------|
| Robert     | Sanders   |<EMAIL_ADDRESS> |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Jennifer   | Jackson   |<EMAIL_ADDRESS>|<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Robert     | Diaz      |<EMAIL_ADDRESS>    |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| John       | Cooper    |<EMAIL_ADDRESS>    |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Robert     | Thompson  |<EMAIL_ADDRESS>|<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Lisa       | Morgan    |<EMAIL_ADDRESS>    |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Richard    | Ellis     |<EMAIL_ADDRESS>  |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| David      | Gonzalez  |<EMAIL_ADDRESS> |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Richard    | Collins   |<EMAIL_ADDRESS>|<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |
| Barbara    | Howard    |<EMAIL_ADDRESS> |<PHONE_NUMBER> | 313db258-d067-41d1-bbc2-91023d62f9a3 |

make build_tools
./bin/make_office_users_migration -f test_office_users.csv
# a new file add_office_users.sql will be created containing the sql to add the new users

Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] Request review from a member of a different team.

References

Pivotal story template for generating new office users.

This is great! Perhaps we could create a csv template for product so the data just comes in the format we need?

@tinyels makes sense. how should i make the template available to product?

Nice job!
Could you add to the ticket an example of a migration and its corresponding CSV? Also, I'd love to see you add a "How To" document on how to use this. I imagine the next one of these we'll see is a script to generate TSP users and I'd love for them to have some usage info to work from.

@chrisgilmerproj Added an example to the How-To. Will update the pivotal ticket as well to link to that section as well.

This is great! Perhaps we could create a csv template for product so the data just comes in the format we need?

@tinyels makes sense. how should i make the template available to product? I think you could create a stub in g-drive and let them know about it.

@chrisgilmerproj most recent commit 86bedfb8f81016901bcbb732645effbfb3d717cd I think should address the comments from discussion that we had over slack.

I tested this locally and it worked as intended.
I did run into an issue with either the command line library or how we're using it, which is that when you try to run a command that doesn't exist, you get an error about a flag instead of a command:

This seems to be an issue with all subcommands + Cobra Consistency in handling unknown commands/Expose findSuggestions(). I wasn't following the quick fix the user was suggesting, so I might defer on this. I'm subscribed to that issue now, so hopefully someone will reply with how this should be handled in Cobra and if not can revisit if ok.


[Issue 7711][pulsar-broker] Use original role instead of proxy role to check permissions

Fixes #7711
Motivation
A client can have more permissions than its original role allows and it is a security violation.
Modifications
Use the original role (if available) instead of the proxy role to check if a client is allowed to consume or produce messages.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@vzhikserg Thanks for the help.  Would you please help check whether the failed ci is related?
[ERROR] org.apache.pulsar.broker.admin.TopicBacklogQuotaTest.testRemoveBacklogQuota(org.apache.pulsar.broker.admin.TopicBacklogQuotaTest)
[INFO]   Run 1: PASS
[ERROR]   Run 2: TopicBacklogQuotaTest.testRemoveBacklogQuota:113 ? ServerSideError HTTP 500 In...
[INFO]
[ERROR] org.apache.pulsar.broker.admin.TopicBacklogQuotaTest.testSetBacklogQuota(org.apache.pulsar.broker.admin.TopicBacklogQuotaTest)
[INFO]   Run 1: PASS
[ERROR]   Run 2: TopicBacklogQuotaTest.testSetBacklogQuota:92 ? ServerSideError HTTP 500 Intern...

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Add pt_BR generic name in poedit.desktop

Brazilian Portuguese translation to the desktop entry "GenericName"

Thanks!


DataTaster: MVP Features

@benlangfeld this is haunting us, can we permit this in [oss-guide][https://raw.githubusercontent.com/powerhome/oss-guide/master/license_rules.yml] like this?

lol same issue, different solutions. at the very least, we should check before we merge https://github.com/powerhome/power-tools/pull/219 to see whether we need to add any data_taster-specific code

@benlangfeld this is haunting us, can we permit this in oss-guide like this?

Yep, feel free to open a PR there.


Does not Exist Error

I have done all the steps in the installation guide. I made all the settings, but when I run the application, android studio gives such an error

I looks like your project is not able to read Kotlin. Have you followed that step?

Yes I followed all steps

same here, have you solved this issue?

same here, have you solved this issue?

No I haven't figured it out yet

I got this issue and found the solution after inspecting the node_modules folder:
Change
import com.dooboolab.RNAudioRecorderPlayerPackage;

to
import com.dooboolab.audiorecorderplayer.RNAudioRecorderPlayerPackage;

Oops, just fixed the readme in https://github.com/hyochan/react-native-audio-recorder-player/commit/3913e6a9418677e54ebf8cffe23cf61ef9f8d1bb.
Sorry for inconvenience 🙏


Memoize PayPalButtons component

Experiment with the idea of using memo to prevent side-effects from triggering a re-render and breaking the iframe.

https://stackoverflow.com/a/52874606
https://reactjs.org/docs/react-api.html#reactmemo

This is not necessary, but it can fix a problem that we don't have yet, and it doesn't make it worse. I think this is a good catch

@pedroapfilho I think being very careful with re-renders is a good thing and we will continue to do that with this library. I'm going to close out this draft PR for now since it isn't solving any particular bug. We can re-visit this in the future if more re-render issues arise.


can't reach this page.Check if there is a typo in ngblhofnpockbiaghoejgicnmbkejkcg.chromiumapp.org.

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.30.0
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
Problem: The redirect URL is giving the error message "can't reach this page. Check if there is a typo in ngblhofnpockbiaghoejgicnmbkejkcg.chromiumapp.org."
It all looks good initially.

Until it gives this message.

I do have the below redirect URI given in the AAD registration.
https://ngblhofnpockbiaghoejgicnmbkejkcg.chromiumapp.org/

Help Needed:  Am I doing something incorrectly? Any help to resolve this issue OR a code example where this is successfully implemented in "manifest version 3" is appreciated.
Scenario: I am trying to develop a browser extension in manifest version 3. Need to make an API call within this extension. This API call needs a bearer token using AAD for authentication. That's how I reached trying MSAL.js. Below is how I am using it inside popup.js file of my extension.
popup.js
const clientId = "";
const authority = "https://login.microsoftonline.com/microsoft.onmicrosoft.com";
const scope = ["user.read"];
const redirectUri = chrome.identity.getRedirectURL();
console.log('getRedirectURL=',redirectUri);
const pca = new msal.PublicClientApplication({
auth: {
clientId: clientId,
authority: authority,
redirectUri: redirectUri
}
});
async function getToken() {
try {
const accounts = pca.getAllAccounts();
const silentRequest = {
scopes: scope,
account: accounts[0]
};
const result = await pca.acquireTokenSilent(silentRequest);
console.log('accessToken=', result.accessToken)
return result.accessToken;
} catch (error) {
console.log(error);
return null;
}
}
const escalateNowBtn=document.getElementById("escalateNow-btn")
escalateNowBtn.addEventListener("click",async ()=>{
console.log('Hello from escalate button');
const redirectUri = typeof chrome !== "undefined" && chrome.identity ?
chrome.identity.getRedirectURL() :
${window.location.origin}/popup.html;
console.log('redirectUri=',redirectUri);
try {
// Login the user and get an access token
const loginRequest = {
scopes: scope
};
await pca.loginPopup(loginRequest);
  // Get the access token
  const accessToken = await getToken();
  console.log(accessToken);
} catch (error){
  console.log(error);
}

})
MSAL Configuration
popup.js
--------------------
const clientId = "<ClientID>";
const authority = "https://login.microsoftonline.com/microsoft.onmicrosoft.com";
const scope = ["user.read"];

const redirectUri = chrome.identity.getRedirectURL();
console.log('getRedirectURL=',redirectUri);

const pca = new msal.PublicClientApplication({
  auth: {
    clientId: clientId,
    authority: authority,
    redirectUri: redirectUri
  }
});

async function getToken() {
  try {
    const accounts = pca.getAllAccounts();
    const silentRequest = {
      scopes: scope,
      account: accounts[0]
    };
    const result = await pca.acquireTokenSilent(silentRequest);
    console.log('accessToken=', result.accessToken)
    return result.accessToken;
  } catch (error) {
    console.log(error);
    return null;
  }
}

const escalateNowBtn=document.getElementById("escalateNow-btn")
escalateNowBtn.addEventListener("click",async ()=>{
    console.log('Hello from escalate button');
    const redirectUri = typeof chrome !== "undefined" && chrome.identity ?
    chrome.identity.getRedirectURL() :
    `${window.location.origin}/popup.html`;
    console.log('redirectUri=',redirectUri);
    try {
      // Login the user and get an access token
      const loginRequest = {
        scopes: scope
      };
      await pca.loginPopup(loginRequest);

      // Get the access token
      const accessToken = await getToken();
      console.log(accessToken);
    } catch (error){
      console.log(error);
    }
})

Relevant Code Snippets
Manifest.json
--------------------
{
    "manifest_version": 3,
    "name": "Extension_22ndMarch",
    "description": "Extension_22ndMarch",
    "version": "1.0",
    "icons": {
      "16": "icon.png",
      "48": "icon.png",
      "128": "icon.png"
    },
    "action": {
      "default_icon": {
        "16": "icon.png",
        "48": "icon.png",
        "128": "icon.png"
      },
      "default_title": "Extension_22ndMarch",
      "default_popup": "popup.html"
    },

    "permissions":["storage","search","tabs","contextMenus","activeTab", "scripting","identity"],
    "oauth2": {
      "client_id": "<clientID>",
      "scopes": ["user.read"],
      "redirect_uri": "https://ngblhofnpockbiaghoejgicnmbkejkcg.chromiumapp.org"
    },
    "background":{
      "service_worker":"background.js"
    },
    "content_scripts":[
      {
        "matches":["https://onesupport.crm.dynamics.com/*"],
        "exclude_matches":["https://www.google.com/*"],
        "js":["contentScript.js"]
      }
    ],
    "web_accessible_resources": [
      {
        "resources": [
          "popup.html"

        ],
        "matches": [
          "<all_urls>"
        ]
      }
    ]
  }

popup.html
--------------------------
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />

    <link rel="stylesheet" href="popup.css" />
    <title>Extension_22ndMarch</title>

Extension_22ndMarch!

        <button id="escalateNow-btn">TriggerAPICall</button>

Identity Provider
Azure AD / MSA
Source
Internal (Microsoft)

Hi @jinsonbits , based on your description it seems like MSAL and AAD are correctly handling the redirect. The issue is the browser can't find the page that your redirect URI points to, which is unrelated to MSAL/AAD. Could it be that the extension isn't properly installed or running on your browser?

Hi AzureAD/microsoft-authentication-library-for-js,
No way. The extension is properly installed. Other functionalities are
working fine. See a screenshot below. I have tried this in edge and chrome.
[image: image.png]
Still if you want to verify, feel free to  use the poup.html,
manifest.json, popup.js files which I have included in this issue.
I think I am doing something wrong in the way of obtaining the
authentication from AAD. But not sure what. Any help to resolve or a a code
example where this is successfully implemented in "manifest version 3" is
appreciated.
Thank you
Jinson.
On Mon, Mar 27, 2023 at 5:12 PM Hector Morales @.***>
wrote:

Hi @jinsonbits https://github.com/jinsonbits , based on your
description it seems like MSAL and AAD are correctly handling the redirect.
The issue is the browser can't find the page that your redirect URI points
to, which is unrelated to MSAL/AAD. Could it be that the extension isn't
properly installed or running on your browser?
—
Reply to this email directly, view it on GitHub
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5820#issuecomment-1485423885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS7WLSFUO5XOOSMGXQG6ELTW6G35ZANCNFSM6AAAAAAWGZ5KRE
.
You are receiving this because you were mentioned.Message ID:
<AzureAD/microsoft-authentication-library-for-js/issues/5820/1485423885@
github.com>

--
The information contained in this electronic communication is intended
solely for the individual(s) or entity to which it is addressed. It may
contain proprietary, confidential and/or legally privileged information.
Any review, retransmission, dissemination, printing, copying or other use
of, or taking any action in reliance on the contents of this information by
person(s) or entities other than the intended recipient is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us by responding to this email or telephone and
immediately and permanently delete all copies of this message and any
attachments from your system(s). The contents of this message do not
necessarily represent the views or policies of BITS Pilani.

@jinsonbits it has come to my attention that we don't support manifest v3 yet. @EmLauber could you take a look at this as a feature request?

@jinsonbits it has come to my attention that we don't support manifest v3 yet. @EmLauber could you take a look at this as a feature request?

Seriously ? That is news to me. Please confirm. Based on that I will see if I need to go back to version 2. Meanwhile, please do share if you have a code example where this is accomplished in version 2.

Yes, manifest v3 is on our backlog but I don't have a timeline yet. A related issue for tracking is #3923. We are monitoring the deprecation of manifest v2 as Chrome reviews their timelines.

Thanks for the confirmation @EmLauber .  Note that I am facing the same problem in the Chrome browser as well. So, I don't think this issue is due to version 3.

Also on manifest version v2, I am facing another problem.

Clicking on the button doesn't do anything apart from closing the window.

@jinsonbits have you tried a different account? There may be some permission restrictions you're unaware of on your @microsoft account.
I'll add that the screenshots and places where your demo is getting errors are actually outside MSAL control and happen between redirects, so I don't believe this is an issue related to MSAL. MSAL will create the initial auth request, but what happens after the initial redirect and before you redirect back to the original app calling MSAL is all on the authorization service side.

Hi @hectormmg -- Yes, you are right. I am able to get the token successfully in a personal domain.  of course with V2 only.  Unfortunately, I have to generate the token with the "microsoft.onmicrosoft.com" domain as the APIs which I am trying to leverage inside the browser extension are authenticated within this domain. Do you have some POC for browser extension support?

@jinsonbits here's our only ChromiumExtensionSample as a POC. Unfortunately, this doesn't deal with restricted permissions for corporate accounts since that I believe is managed by whoever manages the tenant.


Add Crowd methods for fixed steps, fixed time stepping with interpolation

https://github.com/isaac-mason/recast-navigation-js/commit/a128ee1b7883245996285ea70511def91df33275

Released as part of 0.29.0 - https://github.com/isaac-mason/recast-navigation-js/blob/main/packages/recast-navigation/CHANGELOG.md


Ollama working with llama3

Hi recently i made a introduction course about llama2/3:https://learn.deeplearning.ai/courses/prompt-engineering-with-llama-2/lesson/1/introduction
The teacher was one of the CEO of Llama3: https://www.linkedin.com/in/amitsangani?trk=public_post_feed-actor-name
So they teach that for using Llama you have to format prompts in multiturn conversation. Some kind of   to mark every pair question user-answer from system, and add [inst] [/inst] in every prompt ( user question). An image of the idea:

Or perhaps cleaner:

The question is when you use ollama JS library to communicate to llama2/llama3 model via localhost... All this work is done in the background ? ( transforming prompts and responses in the format explained above)?
I was think of using some kind to build a promptchat with prompts and responses. As you can see i save prompts an array of the used or past prompts. And in responses the array with passed responses ( only the response message no all the response object).
But my question is this done automatically by ollama JS, is it useless to do it, would i increase speed or whatever using this fomat ?
Thanks in advance
export function get_prompt_chatv2(prompts, responses, verbose = false) {
    let prompt_chat = "";
    if (verbose) {
        console.log(`Longitud prompts:\n${prompts.length}\n`);
        console.log(`Longitud repuestas:\n${responses.length}\n`);
    }

    if (prompts.length !== responses.length + 1) {
        console.log("\n Error: Numero de prompts debe ser numero de responses + 1.");
        return prompt_chat;
    }

    let size = 0;
    for (let responseActual of responses) {
        prompt_chat += `<s>[INST] \n${prompts[size]}\n [/INST] \n${responseActual}\n </s>`;
        size = size + 1;
    }

    // Añadimos el ultimo prompt
    prompt_chat += `<s>[INST] \n${prompts[prompts.length - 1]}\n [/INST] \n`;

    return prompt_chat;
}

Any response or idea ??

This isn't something handled by ollama-js, but instead by ollama itself using "templates". Whenever you create (or pull) a model using ollama, you provide a Modelfile which basically just describes all the defaults for that model. Part of that Modelfile is the template, which is exactly what you are describing. So, chances are that you are already using the correct template. However, as I mentioned, this is just a default, so you can override it if you wish. In ollama-js, you do this by setting the value of template when using ollama.generate({...}).


block incoming messages from accounts not in roster

I am getting quite some spam lately, so this would be a nice little feature.

(via a configuration option, do not block subscription requests (neither group messages) -- might conflict with #22, but that's why this should be an option)

since 30 seconds, network events (presence or messages) will never (ever) create new contact items, but instead warnings are added to the status log... pls report if this is a fine solution for you, or you'd like additional massaging (such as a config option to silently drop all messages from unknown people)


local.adguard.org certificate is not re-issued when it expire

@DBotThePony commented on Wed Sep 23 2020
Screenshots:

Your environment

Environment name and version: Any browser (this one: Chromium based Yandex browser, issue appear in Firefox and all other chromium based browsers)
Operating system and version: Windows 10 build 2004
Adguard Version:

To resolve this issue you have to manually press reinstall certificate in network settings of adguard. After this, local.adguard.org will get new certificate

@adbuker commented on Wed Sep 23 2020
@DBotThePony, could you please restart the protection and check the issue?

@adbuker i did restart it sometimes, and of course system is online for only a few hours, so protection was restarted obviously because of power off.

Most likely the problem is that we re-issue expired certs on protection startup OR reload.
So if it's expires, there's an extra restart/reload needed to re-issue the certs.
We should change this logic and make sure that certs are re-issued a couple of days before their actual expiration date.

Or, even better, we should simply check that the cert is expired real-time when it's received from the cache.


[SQL] az sql mi server-configuration-option: New command group to manage server configuration options

Related command
az sql mi
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

SQL


VideoGallery Calling Participant tests

What

Add tests for hermetic testing the video gallery
Why

Allows us to run new tests for the video gallery to verify that the participant state is reflected properly in their video tile

https://skype.visualstudio.com/SPOOL/_workitems/edit/2919178
How Tested

Ran locally
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Let's get those updated snapshots. I have nitty comments, overall looks good.

Please also stress test these new tests by running node scripts/runBrowserTests.mjs -s 10 before merging.
It is much harder to fix flaky tests once they're in and they have an outsized (negative) impact on eng productivity. So I'm pushing for all of us to work harder to deflake before we add tests.


Incorrect app icon used after app is installed on GNOME

Describe the bug
After a GUI application is installed via configuration.nix, GNOME uses an incorrect icon for the application -- in fact it uses the default place holder icon, refer to the below:

Steps To Reproduce
Steps to reproduce the behavior:

Add a GUI application to configuration.nix while running GNOME and save file.
Execute sudo nixos-rebuild switch
Press WIN key and search the application.  If the app is launch, the default place holder icon will be displayed in the dock/dash as well.

Expected behavior
The correct icon should be used.
Screenshots
Incorrect icon used within dock/dash:

Incorrect icon used within the apps menu:

Additional context
The correct icons will be loaded once user log out of GNOME and logs back in.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.39, NixOS, 24.05 (Uakari), 24.05.2933.c716603a63ac`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"home-manager-24.05.tar.gz, nixos-24.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

duplicate of #12757


unpin setuptools

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.727%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5045

Relevant Lines:
5686

💛  - Coveralls


Feedback for “Memgraph direct download links”

Downloading memgraph_2.22.0-1_amd64.deb to install on Ubuntu 24.04.1 LTS.
I try to install as follows, but this deb file wants an older version of libpython
sudo apt install ./memgraph_2.22.0-1_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'memgraph' instead of './memgraph_2.22.0-1_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
memgraph : Depends: libpython3.9 (>= 3.9.1) but it is not installable
Depends: libssl1.1 (>= 1.1.0) but it is not installable
E: Unable to correct problems, you have held broken packages.

Can you try downloading here as well and let me know if it works as expected?

Yes that works fine - it is just too big for my edge application.
What I am trying to accomplish is the creation of a docker container image built from a debian slim image where I simply do a apt install <memgraph.deb> in the docker build.
I can do that without any problem
I also need MAGE in the image. That is where I am stuck. I tried simply copying the query_modules folder from the memgraph-platform container image into my custom docker image at container build time but that didn't work. memgraph didn't recognize the existence of the additional modules.
I have a number of open issues in memgraph and memgraph-mage related to this.
Sent with Proton Mail secure email.
On Tuesday, December 10th, 2024 at 2:54 AM, Katarina Supe @.***> wrote:

Can you try downloading here as well and let me know if it works as expected?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Can you please link the issues you created here as well?


Use const array for unrolled Huffman table

Motivation
We've spent a long time with an unrolled Huffman-table to optimize the
Huffman decoding of HPACK headers. This works well, but because of some
limitations in Swift it's been impossible to embed this structure in the
binary directly: we've always had to alloc-and-copy on startup.
Additionally, due to type checker performance limitations, we've been
Base64 decoding it on startup, which isn't great either.
The introduction of const allows us to embed the knowledge of the fact
that this structure is compile-time constant in to the binary, improving
performance.
Modifications
Revert to the old layout, constify, and remove anything that blocks
that.

This is a bit of a WIP. In particular, we have a few issues to resolve. The biggest one is that this still drastically slows down compiles due to the type checker overhead. The type checking here takes 25s on my machine to check this one statement, which is simply not practical for something shipped as source code.

@swift-nio-bot test perf please

Huh, no comparison there. Weird. I don't expect substantial performance improvements regardless: this only cleans up the dirty memory situation and our benchmark doesn't really test memory pressure.


In Fabric 2.2.3, when approve chaincode with different packege id, commit still can be success

I found when different organization approve chaincode by "peer lifecycle chaincode approveformyorg", the "--collections-config" file content and the "--signature-policy" string must be strict equals to the one in "peer lifecycle chaincode commit".
But why there is no "--package-id" in commit command? If two organization install and approve different chaincode with same version, sequence, collection-config and signature-policy, then they can run different chaincode if endorse policy is 1 of n?

If I'm not mistaken, packageId should be unique only in the context of an organization. It's ok to have different IDs of the same chaincode in different organizations. When you approve, you agree that at the specified sequence you trust your installed chaincode.
From Fabric doc:
The chaincode definition also includes the Package Identifier. This is a required parameter for each organization that wants to use the chaincode. The package ID does not need to be the same for all organizations. An organization can approve a chaincode definition without installing a chaincode package or including the identifier in the definition.

But in my testing, the package id is generated with format "_:", I'm not sure how the  is calculated, but I found the same java chaincode jar generated the same value in all organizations. So from my understanding, for different organizations on a channel, they should install the same chaincode with same name and version, and approved with same sequence. And commited command can check package id to make sure they use the same chaincode.


[Bug] PaypalButtons component errors out in debug mode

🐞 Describe the Bug
When using the PaypalButtons component in a React app created using the create-react-app CLI, an error occurs while running the app in debug mode (which starts a new instance/window of Chrome). More explicitly:

PaypalButtons do not work correctly while using the Chrome debugger for Visual Studio Code's default debug configuration.
PaypalButtons do work correctly while using the app from a normal Chrome window (as opposed to the Chrome window that pops up for VS Code's default debug configuration)

🔬 Minimal Reproduction
Reproduction repository here. The readme in the repository has instructions for starting the app and reproducing the issue.
😕 Actual Behavior
When running the app in the Chrome window opened by the debug configuration, clicking the "PayPal" button results in no "overlay" appearing while the PayPal window tries to load, and then the PayPal window fails to load, accompanied by the following error message (which we chose to display in a window.alert():
Error: Unable to delegate rendering. Possibly the component is not loaded in the target window.
Error: No ack for postMessage zoid_delegate_paypal_checkout in https://www.sandbox.paypal.com in 10000ms

And then an additional error message:
Error: No ack for postMessage createOrder() in https://www.sandbox.paypal.com in 10000ms

Screenshots of this behavior:

🤔 Expected Behavior
After clicking the PayPal button, a dark overlay should cover the page, and the PayPal window should successfully load. The following screenshot was taken while running the app normally rather than in debug mode.

🌍 Environment

Software
Version(s)

react-paypal-js
7.3.3

React
17.0.2

Browser - Chrome
Version 93.0.4577.82 (Official Build) (64-bit)

Operating System
Windows 10 Enterprise 10.0.18363 Build 18363

NodeJS
10.22.0

Visual Studio Code
1.60.1

➕ Additional Context
We're obviously able to work around this by just not using debug mode when developing/testing the PayPal functionality in the project we're working on, but not being able to set breakpoints can be pretty rough so it'd be nice if this library worked with our debug configuration.
Create React App and Visual Studio Code are both incredibly popular, so I'm probably not the only developer who's run into problems using react-paypal-js. Obviously, if there's a tweak we can make to our debug configuration to make this work, I'd be more than happy to try that out.

Hey folks! I'm another PayPal engineer on our DevRel team. We have this error reproduced and we are actively working with a team here to try to figure out exactly what the root cause is. No concrete updates yet on exactly what the issue is, but we will keep this thread updated with whatever we figure out!

@mkirlin any updates here?

We talked to the teams that build these components; they took a look at it and it appears that what’s happening here is that whatever process VS Code is using under the hood to connect to the browser in the debugger session is dropping certain messages sent from the button to the parent page, and vice-versa. Based on that, we’re going to close this issue, as the problem does not appear to be in our code. I’m sorry for what I’m sure is a frustrating answer. I would recommend opening a ticket with the VS Code debugger
@sgarg17, I'm a little unclear on the issue you're seeing, and whether it's also related to whatever this problem is the the VS Code debugger. If you can get reliably reproduced and it's not the same problem, would you mind opening a new issue here with your info and tagging me? Thanks!


new attribute needed to detail exact physical dimensions corresponding to display window

Various packages that reconstruct camera position and orientation from image sequences require their users to enter the position and dimensions of the rectangle on the sensor or film plane that corresponds to the display window. Alternatively the dimensional specification is in pixels and the package requires the user to enter a pixel dimension (almost always a single pixel dimension, although OpenEXR is so old that it makes provision for non-square pixels).
Several camera systems provide enough metadata in their output to determine the dimensions and offset from optical sensor of this rectangle, or provide enough that when combined with static pixel dimensions from the manufacturer allow both dimensions and offset to be computed. Depending on the sophistication of the VFX artist or facility this can be easy or very tedious.
Defining a standard optional attribute to carry this rectangle's position and dimensions would encourage camera vendors and vendors of systems transcoding camera output to OpenEXR to properly populate it.
Note that this corresponds to the ActiveSensorPhysicalDimensions metadatum defined in SMPTE's camdkit.

Apologies to OpenEXR, my comment about it being "so old that it makes provision for non-square pixels" was out of line. The provision is for anamorphic acquisition and isn't some pre-digital-television non-square pixel thing.
Nick's comment in the TSC meeting yesterday about "just divorce yourself from the existing coordinate systems" [paraphrased] is correct, or at least mostly so. I think we want to retain the data window / display window convention of how you move when you increase either x or y when we talk about centering offset and about what part of the sensor is being used.
Proposal:
sensorPhotositePitch, µm, as a float
sensorOverallDimensions, mm, v2f
sensorCenterOffset, mm, v2f
sensorAcquisitionRectangle, photosites, Box2i
Will start work on a PR.

Mr Edge Case here again: would the sensorCenterOffset be relative to the optical center of the lens or is just the relationship between the camera body lens mount and which part of the sensor contributes to the final image? So if a shift lens  is used (or just a badly aligned one), the sensorCenterOffset should change? Or is there already sufficient additional metadata that describes the lens properties relative to the lens mount?
Most digital cameras offer a choice of aspect ratios and resolutions. I believe some cameras do resolution changes on the sensor itself using something like hardware pixel binning which might make the term 'photosite' ambiguous. Should those cameras adjust the sensorAcquisitionRectangle and sensorPhotositePitch accordingly if they aren't capturing the full sensor at full resolution? Also, what happens to all of these if there's a post-process "optical" effect, such as an aspect ratio change, or a pan or zoom? Should these parameters refer to the values "at capture time" or is image processing software expected to update these accordingly? With the philosophy that wrong metadata is worse than no metadata, I wonder if those attributes could be tagged as "not safe to preserve if the image geometry is modified" via some new API, so software that reads/modifies/writes OpenEXR images knows to drop them.
(I think all of these parameters are a good idea, and wouldn't suggest adding any more to handle the above cases, but I think a certain amount of pedantry may be required in defining them to ensure they are interpreted consistently)

Echoing Peter's comment, Is the term "photosite" right? I think of hardware sensors when I think of photosite, but maybe I'm thinking about that wrong. Is photopitch vs a Bayer green, red or blue? Or does "photosite" mean the resampled/regularized data we've got in the EXR file? Pedantically is it correct in both cases? I guess I'm unclear if photosite refers to final sampled output, or if it refers to a hardware characteristic. Since the term is being used with respect to the sensor I'm unable to work out what's right.
My understanding is that sensorCenterOffset is relative to the lens optical center, otherwise how are we to understand the direction light was coming from when it hit the sensor?
With regards sensorAcquisitionRectangle, I assume the box itself is in the coordinate system defined by the with an origin of sensorCenterOffset and the euclidean metric is defined by sensorPhotositePitch. With that information, and an unambiguous definition for sensorPhotositePitch, for any pixel I can work out any interesting fact I can think of that doesn't involve further knowledge about the lens.

I will try and take these comments in order. But before I do that I should say that I am copying concepts from SMPTE RDD 55, "Material Exchange Format — Carriage of ARRI Camera System Metadata", because I worked on that document with some very smart people and mostly I think we got things right. Mostly (see below).
sensorCenterOffset is relative to the optical center of the camera's lens mount. I have asked (and have a couple more people to ask) but have yet to find anyone tracking an offset between the optical axis of a lens relative to the center of the lens mount on the lens side, nor any sort of provision for a too-heavy lens mounted on a camera with a weak lens mount and too-weak support rods.
Regarding tilt lenses, I would not say they are never used, but as far as I know, they are almost never used for motion picture or television work. Moreover, looking at the lenses on the Wikipedia page to which you linked, the weirdness is solely on the lens side. I don't believe any of those cameras had their film gate or their sensor displaced in any way. Thus I think that if the industry cried out for metadata supporting tilt or shift lenses, we would support them by adding additional metadata beyond what is proposed here, with no need to change what this proposal provides.
I do need to come up with an exact definition relating signs of the offset components to the contents of the data window, e.g. positive x and y offsets would shift the contents of the data window up and to the left.
sensorAcquisitionRectangle refers, roughly speaking, to those photosites that contribute to the image, even if the image that is recorded does not comprise an image where the number of image rows and image columns match the number of photosite rows and photosite array columns. For example, when shooting for HD delivery on the original ALEXA EV, a 2880 x 1620 photosite array contributed sensel data [the read-out-contents of photosites] to a debayer algorithm that simultaneously downsized to a recorded 1920 x 1080 array of RGB pixel data.
In light of Nick's comments it's worth my explicitly adding a comment block saying that photosites are the rectangular (typically square) sites where the photon-induced charge is registered; sensels are the data read out of those sites; and pixels are the data that are stored in OpenEXR files. In the RGB case, the pixels result from feeding sensel data and a description of the color filter array into a demosaicing algorithm and possibly linearly scaling and/or converting an integer image to float; in the monochrome case, there is only the possible linear scaling and/or conversion from image to float.
Here is the wording from SMPTE RDD 55: "...the rectangular region of the sensor containing the photosites from which the captured image is read".
Guess what? That's incorrect. It's incorrect because most debayering algorithms work by examining adjacent pixels on either side of the pixel being reconstructed. When the debayer is working with a 5x5 array of sensel data, in the example above, technically, the examined region is 2884 x 1624.
Therefore in the next revision of RDD 55 we are going to change the language to be something like this: "...representing the rectangular region of the sensor containing photosites the contents of which are in one-to-one correspondence with the captured senseless, fora. monochrome sensor, or with the reconstructed pixels, for an RGB sensor." Thought I might change "RGB sensor" to "sensor covered with an RGB color filter array arranged in a Bayer pattern".
(The Sony F65 has the duck-billed platypus of CFA-covered sensors in that it is tilted at a 45º angle)
What RDD 55 calls SensorPixelPitch I propose to call sensorPhotositePitch. The definition is "Distances between centers of sensor photosites, in microns".
What RDD 55 calls OverallSensorDimensions I propose to call sensorOverallDimensions. The description can be almost copied one-for-one; I would go with "Dimensions of the light-sensitive area of the sensor, in mm, independent of the subset of that region from which image data are obtained."
If I maintain the order of attributes in the file to be as it was in the original message here, then I would add just above the center offset wording to the effect that for the purposes of center offset, the origin of the coordinate system in which the offsets are given is, as with the data and display windows, in the upper left; and that the directions in which the row and column indices of that same coordinate system increase are the same directions as those found in the data and display windows.
In re: pedantry, apologies if I've used this setup before; It really should be on my gravestone:
DEVIL: ...and this is the lake of lava you will be spending eternity in
ME: Actually, since we're underground, it would be magma
DEVIL: You do understand this is why you're here, right?

Submitted as PR #1489 .
n.b. running locally, the added standard attribute tests passed, but two compression tests failed when I ran make test on my late-2021 MacBook Pro (i.e. Apple Silicon, if that matters) — OpenEXRCore.testDWAACompression and OpenEXRCore.testDWABCompression.

Thanks for all the explanatory notes, very much appreciated.
The test failures are unrelated to adding attributes ~ Kimball has a separate fix up for that.


Is it possible to retrieve the parameters for a given ssrs report?

Is it possible to retrieve the required parameters for a given ssrs report?

If you call loadReport() you should get back lots of information on the report, including the parameters. Each parameter should have a required flag on it.
Something like this:
<?php
require(__DIR__ . '/../vendor/autoload.php');

$options = array(
    'username' => 'testing',
    'password' => 'password'
);

$ssrs = new \SSRS\Report('http://localhost/reportserver/', $options);
$result = $ssrs->loadReport('/Reports/Reference_Report');

$parameters = $result->getReportParameters();

How do you retrieve conditional parameters? For example: based on the parameter chosen in one field, it updates the available params in another field. I'd prefer to default this value if I can before loading the list of parameters the first time.
Is this possible?

IIRC you have to update the parameters, then grab the 'updated' conditional parameters from SSRS. I don't think you can get a list of everything right off the bat.
It has been a while, but we did something like this, where $knownValues are the default values or the previously submitted values:
$executionParameters = new SSRS_Object_ExecutionParameters($knownValues);
$newExecutionInfo = $ssrs->setExecutionParameters($executionParameters);

$ssrs->setSessionId($newExecutionInfo->ExecutionID);
$newParameters = $newExecutionInfo->getReportParameters();

// here we had a form generator, eventually populating a HTML form based off the available parameters and values
$formGenerator->generate($newParameters);

$output = $ssrs->render('HTML4.0'); // PDF | XML | CSV

Thanks for the response. Unfortunately this code doesn't work. Here's the full snippet of what I tried:
This code fails with "Session ID not set"
// You need to connect to the server and load your report
$ssrs = new \SSRS\Report('http://myserver/ReportServer', array('username' => 'user', 'password' => 'password'));
$report = $ssrs->loadReport('/Folder/Report');

// Add execution parameters from submission
$execution_params = new \SSRS\Object\ExecutionParameters($requestedFilters);
$new_report = $ssrs->setExecutionParameters($execution_params);

$ssrs->setSessionId($new_report->ExecutionID);

// Params to send to the form view
$available_params = $new_report->getReportParameters();

Your other examples in the wiki indicate that the session id has to be set in the same statement as the setExecutionParameters but if I use that session ID, the parameters I get at the end are just the defaults, not reflective of the data I sent for the report.
// If I instead use the previous session ID:
$new_report = $ssrs->setSessionId($report->ExecutionID)->setExecutionParameters($execution_params);

// Do not reflect the values submitted
$available_params = $new_report->getReportParameters();

// Just for giggles and grins
$new_report->executionInfo->Parameters; // this is null

Here's an example -- you can see value is null even though I am sending a value and the report executes as if a value has been sent.
array:9 [▼
  0 => ReportParameter {#1181 ▼
    +name: "parForecastDate"
    +value: null
    +data: array:13 [▶]
  }
  1 => ReportParameter {#1555 ▼
    +name: "parMonths"
    +value: null
    +data: array:13 [▶]
  }
  2 => ReportParameter {#1561 ▼
    +name: "parType"
    +value: null
    +data: array:13 [▶]
  }
]

The issue with this is that sending these available parameters to our form builder, and one of them has no options available because it's not showing a value for a dependency.
At this point I'm stumped and I might have to build the form filters manually and just send the data to get the report.

If the execution ID isn't updated any subsequent requests won't reflect your submission. The execution ID from SSRS is like a state marker.
In your example, where you keep the old session ID, you'll get back the state before you submitted anything.
Unfortunately I don't have access to an SSRS server at the moment to run some tests, but the code should work. Here is a fuller example from the snippet I sent, you'll see we keep updating the session ID to the latest execution ID:
$ssrs = new SSRS_Report('http://testing/reportserver/', $options);
$executionInfo = $ssrs->loadReport($reportName);
$ssrs->setSessionId($executionInfo->ExecutionID);

$executionParameters = new SSRS_Object_ExecutionParameters($knownValues);
$newExecutionInfo = $ssrs->setExecutionParameters($executionParameters);

$ssrs->setSessionId($newExecutionInfo->ExecutionID);
$newParameters = $newExecutionInfo->getReportParameters();

// here we had a form generator, eventually populating a HTML form based off the available parameters and values
$formGenerator->generate($newParameters);

$output = $ssrs->render('HTML4.0'); // PDF | XML | CSV

Hopefully that helps a bit? Sounds like its almost there...

Hey that works! Gotta love Microsoft and their exacting requirements.
Thank you for your help!
Elanor Riley
Dynamic Web Application DeveloperGraphic Designer
On Fri, Dec 8, 2017 at 12:56 PM, rb-cohen<EMAIL_ADDRESS>wrote:

If the execution ID isn't updated any subsequent requests won't reflect
your submission. The execution ID from SSRS is like a state marker.
In your example, where you keep the old session ID, you'll get back the
state before you submitted anything.
Unfortunately I don't have access to an SSRS server at the moment to run
some tests, but the code should work. Here is a fuller example from the
snippet I sent, you'll see we keep updating the session ID to the latest
execution ID:
$ssrs = new SSRS_Report('http://testing/reportserver/', $options);$executionInfo = $ssrs->loadReport($reportName);$ssrs->setSessionId($executionInfo->ExecutionID);$executionParameters = new SSRS_Object_ExecutionParameters($knownValues);$newExecutionInfo = $ssrs->setExecutionParameters($executionParameters);$ssrs->setSessionId($newExecutionInfo->ExecutionID);$newParameters = $newExecutionInfo->getReportParameters();// here we had a form generator, eventually populating a HTML form based off the available parameters and values$formGenerator->generate($newParameters);$output = $ssrs->render('HTML4.0'); // PDF | XML | CSV
Hopefully that helps a bit? Sounds like its almost there...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ChartBlocks/php-ssrs/issues/25#issuecomment-350329035,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFpvEte-_6XXSZn_3PYUWD_CTTf195ks5s-Xg6gaJpZM4J3bBi
.

Phew, good to hear! :)


[6.0 🍒] Apply the @_alwaysEmitConformanceMetadata semantics to conformances originating from macro-expanded declarations and extensions

Cherry-pick of https://github.com/apple/swift/pull/73680/files
Existing code does not visit such declarations and does not mark them to be preserved in the binary even if not public and used.
Explanation: The attribute added in https://github.com/apple/swift/pull/60367 causes the compiler to ensure that conformances to protocols annotated with the @_alwaysEmitConformanceMetadata attribute are in the resulting binaries even if the conformance itself is not public or even used elsewhere in the code. The current implementation (https://github.com/apple/swift/pull/69609) of this attribute does not account that such conformances may originate from macro-expansions. This change fixes that by causing the detection logic to consider macro-expanded contexts.
Risk: Low. This change extends the existing declaration walker by causing it to also walk macro-expanded declarations in order to find conformances to attribute annotated protocols. For code not annotated with this attribute this will not result in any changes. And for code that is annotated, the produced binaries will contain the expected results, whereas they did not before.
Testing: Automated test added to the compiler test suite.
Resolves rdar://127903662

@swift-ci test


refactor: remove deprecated debug command

Removed "debug" as it's been replaced by print (which works at all debug levels)
Fixed issue where print didn't interpolate the globals in the text in all instances
Updated the debug console to use print over debug. Compared output in the debug window when using print vs debug and the 11 debug output lines are identical (repacing everywhere that says "debug" with "print")
Deduplicated the replace_globals function

Fixes : https://github.com/godot-escoria/escoria-issues/issues/221

Fixes https://github.com/godot-escoria/escoria-issues/issues/204
Fixes https://github.com/godot-escoria/escoria-issues/issues/221


Is it possible to passe a custume bevy image

Hi, thank you for the hard work, this library is exactly what i was looking for.
I'm rendering moving objects to a texture and i want to display the my render inside the user interface.
Is it possible to passe a custume bevy image to the img component in stead of a file?

Not now, but it looks pretty easy to implement. Will do it shortly.

Thank you for your responsiveness 👍👍👍

@bekraoui it is now possible to pass the handle to  as well as path to asset:
let img0 = "icon.png";
let img1: Handle<Image> = asset_server.load("bevy_logo_light.png");
let img2: Handle<Image> = asset_server.load("bevy_logo_dark.png");
commands.add(eml! {

});

There is example: https://github.com/jkb0o/belly/blob/main/examples/image-sources.rs


training alignment

Thanks for your great works! I am trying to train the model on laion2B datasets.
My training details are:  base_size=4096, learning_rate=1e-4, AdamW optimizer.
After 130000 iterations, the loss curve is as follows, it seems to flatten...

And the visualized images are:

prompts are:
A tiger in a lab coat with a 1980s Miami vibe, turning a well oiled science content machine, digital art
A group photo
a fish on a bike
star citizen aurora
Are you in a similar situation during training, what is the lowest loss you can achieve during training?? Hope to get your suggestions!

How many gpu are you used?

@PanXiebit


Only access ControlInteractivity through the projection

Summary of the Pull Request
This forces the TermControl to only use ControlCore and ControlInteractivity via their WinRT projections. We want this, because WinRT projections can be used across process boundaries. In the future, ControlCore and ControlInteractivity are going to be living in a different process entirely from TermControl. By enforcing this boundary now, we can make sure that they will work seamlessly in the future.
References

Tear-out: #1256
Megathread: #5000
Project: https://github.com/microsoft/terminal/projects/5

PR Checklist

[x] Closes https://github.com/microsoft/terminal/projects/5#card-50760270
[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments
Most all this was just converting pure c++ types to winrt types when possible. I've added a couple helper projections with til converters, which made most of this really easy.
The "MouseButtonState needs to be composed of Int32s instead of bools" is MENTAL. I have no idea why this is, but when I had the control OOP in the sample, that would crash when trying to de-marshal the bools. BODGY.
The biggest changes are in the way the UIA stuff is hooked up. The UiaEngine needs to be attached directly to the Renderer, and it can't be easily projected, so it needs to live next to the ControlCore. But the TermControlAutomationPeer needed the UiaEngine to help implement some interfaces.
Now, there's a new layer we've introduced. InteractivityAutomationPeer does the ITextProvider, IControlAccessibilityInfo and the IUiaEventDispatcher thing. TermControlAutomationPeer now has a
InteractivityAutomationPeer stashed inside itself, so that it can ask the interactivity layer to do the real work. We still need the TermControlAutomationPeer though, to be able to attach to the real UI tree.
Validation Steps Performed
The terminal behaves basically the same as before.
Most importantly, I whipped out Accessibility Insights, and the Terminal looks the same as before.

Crap I broke something in the merge, I think the automationPeer is getting torn down in the wrong order. It's crashing on close again. 💩

specific crash was:

open terminal
open SUI
change defterm
save
close window with the X

this would crash consistently on this branch, not in preview.

Okay, crash on exit fixed in latest push


Keywords should be valid metric names

Currently an expression such as if is invalid due to it being a keyword. As we won't limit metric not to clash with keywords, we should allow any valid metric name to be used in promql.

I don't see the practical necessity of this considering the implementation complexity it ships with. This will be absolutely nasty to parse for alerting rules.

I don't think this will ever happen and nor do I consider it necessary.
I would like to close issues that are not going to be tackled. Our keywords are mostly single-worded while metrics are generally multi-worded, so the conflict-potential is minimal. There is always the workaround through __name__ should there actually ever be a conflict.
Thoughts?

:+1: for closing for now and potentially reopening in the distant future if the need really ever becomes apparent.


feat: Add --with-source flag to bicep publish command

This pull request primarily focuses on the enhancement of the module publishing process in the GitHub workflows and PowerShell scripts. The main change is the addition of the --with-source flag in the bicep publish command to include the source code while publishing the module.
Changes in GitHub workflows:

.github/workflows/publish-module.yml: Added --with-source flag in the bicep publish command under the Publish module job. This flag ensures that the source code is included when the module is published.

Changes in PowerShell scripts:

avm/utilities/pipelines/platform/Publish-ModuleFromTagToPBR.ps1: Included --with-source flag in the bicep publish command in the Publish-ModuleFromTagToPBR function. This change ensures that the source code is included when the module is published from a tag to PBR.
avm/utilities/pipelines/publish/Publish-ModuleFromPathToPBR.ps1: Added --with-source flag in the bicep publish command in the Publish-ModuleFromPathToPBR function. This ensures that the source code is included when the module is published from a path to PBR.

This PR cannot be merged until v0.25 is released of bicep is released (hence draft initially)

@jtracey93 - is the do not merge status still applicable?


[QA] Requesting shares with "shared_with_me=true" retrieves shares with incorrect path

oCIS is saving shared content in the folder \Shares. Then, when requesting "shared with me" content:
ocs/v2.php/apps/files_sharing/api/v1/shares?state=all&shared_with_me=true
the response must include in the <path> and <file_target> the \Shares folder
F ex: in oC10's config.php, the following instruction is added to set the same behaviour as oCIS:
'share_folder' => '/Shares'
So, sending the request above, the response...
oC10:
<path>/Shares/Speech.ogg</path> ... <file_target>/Shares/Speech.ogg</file_target>
oCIS:
<path>/Speech.ogg</path> ... <file_target>/Speech.ogg</file_target>
this makes the mobile clients not to show that the item is shared by others in the actions card:

oC10
oCIS

Backend: EOS storage via via https://github.com/owncloud-docker/compose-playground/blob/master/examples/hetzner-deploy/make_ocis_eos_compose_test.sh
Version: v1.0.0-rc1
Client: iOS App v11.4 over iOS13

Similar bug report here: https://github.com/owncloud/product/issues/203

@jesmrec this still an issue?

Not reproducible anymore with ocis-2.0.0. Any way to check with EOS storage?

Please open again if the ticket is still relevant