Question about the meaning of "automatic assertion" evidence

Sorry, can of worms opening.....
Some of  our protein modification annotations, which are  experimental, but high-throughput use the ECO code
"tryptic phosphopeptide mapping assay evidence used in automatic assertion"
I was wondering exactly what this meant because, to me, automatic assertion is non-experimental and tryptic phosphopeptide mapping assay is clearly experimental  (we were importing some UniProt annotations which happen to use a different evidence code for the same paper "experimental evidence used in manual assertion" so they are not recognised as identical annotations)
I thought I would begin where I am familiar and so I looked up the definition of automatic assertion. This did not help me because
evidence used in automatic assertion
is defined as
A type of evidence that is used in an automatic assertion.
author cjm @cmungall  ;)
This has the synonym (not sure of the scope) Synonym IEA inferred from electronic annotation
in GO IEA is defined
Electronic annotation evidence code
‘Electronic’ (IEA) annotation are not manually reviewed (although the method itself is usually subjected to various quality assessments). IEA-supported annotations are ultimately based on either homology and/or other experimental or sequence information, but cannot generally be traced to an experimental source. Three methods make up the bulk of these annotations. The first, and most comprehensive, method is InterPro2GO, which is based on the curated association of a GO term with a generalized sequence model (‘signature’) of a group of homologous proteins. Protein sequences with a statistically significant match to a signature are assigned the GO terms associated with the signature, a form of homology inference. A second method is the computational conversion of UniProt controlled vocabulary terms (including Enzyme Commission numbers describing enzymatic activities, and UniProt keywords describing subcellular locations), to associated GO terms. Lastly, annotations are made based on 1:1 orthologs inferred from Ensembl gene trees, an approach which automatically transfers annotations found experimentally in one gene, to its 1:1 orthologs in the same taxonomic clade (e.g. those within the vertebrate clade, and separately, those within the plant clade).
This  definition of automatic assertion doesn't really fit a tryptic phosphopeptide mapping assay
but it seems that the ECO meaning of "automatic assertion" is not really equivalent to the GO
"automatic assertion" in ECO is poorly defined, and  is used very loosely, this probably means that most descendants  might need to be revisited?
Thoughts? @cmungall   @mgiglio99

For my reference. Consequences
every annotation from this dataset is duplicated :

(we would filter if they were parent-child in the hierarchy, but these are in different parts. of the graph)
https://www.pombase.org/reference/PMID:18257517

This is the relevant definition:
ECO:0000203 ! automatic assertion "An assertion method that does not involve human review."
This doesn't precisely align with the GO definition "but cannot generally be traced to an experimental source", but I don't know what the GO text means. We propagate EC2GO as IEA but these are clearly traceable to an experimental source. IMO IEA is just some legacy thing that is hard to formalize, convenient for GO, but also that confuses users.
The term in question here has 2 subtypes for automated and manual (but both tracing to experimental)

I'm not sure if this triad pattern is the most meaningful or useful or intuitive but it's how ECO has worked for a while....

The way I understand it, "automatic assertion" is a type of assertion (the other one being manual), which generate cross products with evidence terms via the "used in" relationship. An automatic assertion is an assertion that is made by a machine, without human involvement. This can be "classic" algorithm (e.g. BLAST search), where the algorithm determines what are relevant hits for a sequence query. But it can also be an experimental setup where the apparatus makes calls on what is relevant or significant. For instance, in a phosphopeptide mapping assay, the mass spectrometry setup may make automatic assertions based on attributes of the spectra. If that is what is reported (e.g. in a table) that would be an automatic assertion. Same for up- or downregulated genes at some pre-defined log-value cutoff in RNA-seq. If the researchers interpret some of their findings and conclude that some residues are clearly phosphorylated (or some genes most certainly induced) that would be a manual assertion on the same ECO evidence. That is, at least, how I have always interpreted it, which means that it is not necessarily true that "automatic assertion" is "non-experimental".

OK, got it!
So most  high throughput datasets would be "automatic assertions"

Hi all, sorry to be late coming to the thread.
Thanks Chris and Ivan for jumping in.
Indeed 'automatic assertion' in ECO is not equivalent to "not experimental".
And Val, as for high-throughput datasets,  you are right that most will likely be automatic, but some could definitely be manual - it will come down to whether a human reviewed the output or not.
Best,
Michelle

Thanks all.
It seems that the GO evidence codes for HDA maps to the manual assertion evidence code (most are certainly automatic).
https://www.ebi.ac.uk/ols4/ontologies/eco/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FECO_0007005?lang=en
There may be some confusion here about what constitutes "manual". Just because a curator is happy with the method, and the threshold, and has done spot check validation, doesn't make it "manual"
and IEA is a synonym of high throughput direct assay evidence used in automatic assertion
which also doesn't seem quite right.
I'll open a ticket on the GO tracker about this (the correct usage isn't totally clear from the guidelines).

Hi @ValWood HDA should be manual as the data should have been reviewed by a curator and added by 'hand' not by automatic propagation.

I don't understand :)
I looked at the HTP paper, and it wasn't clear what the curator's role would be. It only describes reviewing the threshold, method and spot checking? It doesn't say that they need to "manually apply each annotation". What  would the curator be doing in these cases that a computer wasn't doing?

You might add the IDs for the genes 'in bulk' but there will be checking and verification that does not happen with electronic annotation. You could add in bulk for IDAs, if the experiment didn't meet a HTP threshold.
We can also remove individual HTPs annotations if they conflict with other knowledge.
Note IBAs are classed as manual.

OK got it.

Hi @ValWood
Regarding this comment above:  "and IEA is a synonym of high throughput direct assay evidence used in automatic assertion which also doesn't seem quite right."
In fact, IEA is not a synonym of 'high throughput direct assay evidence used in automatic assertion' ECO:0007589, rather, it is the value in the "has GO evidence code" property. Term ECO:0007589 has no synonyms. We realize that the name of this property is confusing - we are working on changing it - what is should be is "maps to GO evidence code". The ECO:0007589 term should map to IEA if one was "rolling-up" annotations on more granular terms up to more general terms. IEA is a synonym for only one ECO term - that is ECO:0000501 'evidence used in automatic assertion'.
But many ECO terms that are more granular than GO evidence codes would map to IEA.
We described the process we adopted a few years ago for mapping GO evidence codes to ECO terms in the 2022 ECO NAR paper in the "New ECO-to-GO evidence code mapping process" section. Also talked about it at a GO meeting a few years ago. Happy to delve into that more if you wish.
And clearly we need to change the name of that property since many people are getting confused by it.

Thanks Michelle, that's clear now. I don't look at ECO often as we tend to use a limited set of evidence codes.
My issue will be resolved by UniProt  changing the evidence code they used from
ECO:0001265 tryptic peptide phosphopeptide mapping assay used in manual assertion
to match our
ECO:0007464 tryptic peptide phosphopeptide mapping assay used in automatic assertion
to suppress the duplication
so this one can close

Ok, Thanks Val


Rename error messages

Contributes to #2363.

Improve the discoverability of Visual Basic error topics in both GitHub and on docs.microsoft.com by renaming the files to have only the Visual Basic error/warning number rather than the message string. This also requires that we create redirects for the 203 existing files in the language reference directory.

I've renamed 10 files only in this PR for easier review. I didn't made the redirects for those yet. Wanted to make sure if entries in .openpublishing.redirection are ordered in some specific way ?

In general the * .openpublishing.redirection* is ordered alphabetically.

This looks really good, @Youssef1313. Thank you so much for doing it.
Once you add the redirects, we can merge. As @Thraka indicated, redirects should be in alphabetical order.
Renaming just a handful of files (10-20 is a good number) in a single PR would be useful -- it enormously simplifies the review process.

As I was about to reply, I noticed the last entry wasn't added in alphabetical order, so created PR #15071.

GitHub shows merge conflicts that I can't see locally, and not allowing to resolve them using web interface. I'll try to fix it and add the redirections, if I couldn't I will open a new PR with the current changes and the redirection.

Did you try to pull --rebase from master?

I've rebased your PR @Youssef1313.

@mairaw, Thanks for fixing the conflicts for me :)
I've updated the redirections.


How is this related to Sysinternals WinObj?

It looks like the same app to me. Did Sysinternals copy this app originally? Or is this a copy of the Sysinternals app?

It's heavily inspired by, but isn't the SAME app.

It is unrelated. Originally this was an extended version of WinObj called WinObjEx and created by Four-F in 2003 year because SysInternals WinObj was (and is up to current date) a feature restricted trash. WinObjEx was close source and wasn't updated since 2005. This one was created on top of it features specially for x64.


Create setup.py

Currently when I try to install runner using python -m pip install git+https://github.com/monarch-initiative/runner.git , it gives me the error attached.

I'm guessing it is the absence of a 'setup.py' file in the project?

commit https://github.com/monarch-initiative/runner/commit/88e17788a6703e4e0473808f146ce045ec3b6bd9


Fix Slick mouse cursor bug.

The bug:

SlickBatchRenderBackendFactory is creating a BatchRenderBackendInternal,
which simply calls MouseCursor#enable in
BatchRenderBackendInternal#enableMouseCursor for custom mouse cursors.
This works for every backend except for Slick because MouseCursor must
be cast to a SlickMouseCursor, and then
SlickMouseCursor#enable(GameContainer container) must be called, NOT
MouseCursor#enable, which throws an UnsupportedOperationException after
extensive refactoring of the custom mouse cursor system in Nifty (see
commit 2c4b5d0 for details).

The fix:

Get rid of SlickMouseCursor#enable(GameContainer container) &
SlickMouseCursor#disable(GameContainer container), as they violate the
encapsulation of the newer MouseCursor#enable & MouseCursor#disable
methods, respectively.

Remove AbstractNativeSlickMouseCursor#enable &
AbstractNativeSlickMouseCursor#disable implementations, as they only
throw UnsupportedOperationException's (due to a leaky abstraction).

Add LwjglCursorSlickMouseCursor#enable &
LwjglCursorSlickMouseCursor#disable methods, that implement
MouseCursor#enable & MouseCursor#disable, respectively. Delete
LwjglCursorSlickMouseCursor#enable(GameContainer container) &
LwjglCursorSlickMouseCursor#disable(GameContainer container), as they
are removed from the implemented SlickMouseCursor interface.

Require a GameContainer to be passed into the
LwjglCursorSlickMouseCursor constructor, that can be used to enable &
disable the mouse cursor via #enable & #disable, respectively. This
removes the need for #enable(GameContainer container) &
can be treated as a MouseCursor instead of a SlickMouseCursor when
enabling & disabling, just like every other backend's mouse cursors
(patching the leaky abstraction).

Create SlickBatchRenderBackend, which delegates every single method to a
BatchRenderBackendInternal, EXCEPT for the rendering of non-native
SlickMouseCursor's. Require a GameContainer in the
SlickBatchRenderBackend constructor, as it must be passed to the
SlickMouseCursor#render in #endFrame. This is the still-leaky part of
the MouseCursor abstraction, as MouseCursor does not have a #render
method, but non-native SlickMouseCursor's must have #render called every
frame, so cast MouseCursor to SlickMouseCursor (if possible) and render
it in #endFrame.

Create a SlickBatchRenderBackend in SlickBatchRenderBackendFactory
instead of a BatchRenderBackendInternal, to get special mouse rendering
support for SlickMouseCursor's.

Require a GameContainer in SlickBatchRenderBackendFactory#create, which
gets passed to SlickBatchRenderBackend & SlickMouseCursorFactory.

Update all internal uses of SlickBatchRenderBackendFactory#create by
passing in the GameContainer.

Require SlickMouseCursorLoader#loadCursor &
LwjglCursorSlickMouseCursorLoader#loadCursor to take a GameContainer, as
it must be passed to the returned LwjglCursorSlickMouseCursor, so that
it can be enabled & disabled.

Require SlickMouseCursorLoaders#loadCursor to take a GameContainer, as
it must be passed to the returned LwjglCursorSlickMouseCursor, so that
it can be enabled & disabled.

Fix SlickRenderDevice (deprecated) mouse cursor support to work with
the aforementioned changes.

API Changes:

All users of the Slick batch rendering backend must pass a
GameContainer to SlickBatchRenderBackendFactory#create when
instantiating Nifty, i.e.:
new Nifty(new BatchRenderDevice(SlickBatchRenderBackendFactory.create(gameContainer)), ...);

If users of the Slick backend uses a convenience class such as
NiftyGameState or NiftyOverlayGameState, this will be done
automatically.

GitHub Issue References:
Fixes #324
Fixes #355

Thanks for another EPIC pull request with another über EPIC commit comment! :smile:


Paypal Integration: Break on success & failure

The Heroku link breaks and is redirected to http://localhost:8080/api/paypal/success?paymentId=PAY-1ND280637A326803CLLZ6EOA&token=EC-2NR76106M86837311&PayerID=9PP8UJ4DYAYHA

By Heroku, do you mean the demo site that is listed on this repo?

Yes

Unfortunately the demo site currently is more less just to give you a feel of the project, and doesn't have valid credential or modified call back registration. In other words currently the demo deployment is literally a deployment of the git repo, which means it is using the API credentials and callback configs that are in the .env.example.  As far as the credentials go, most of the credentials in the .env.example are invalid since publishing valid keys publicly have a high chance of them being abused.
You can use your own copy of the project with your own valid API keys from Paypal or the other API providers and based on your development system or deployemnt location adjust the Paypal call back URLs through environment variables listed at https://github.com/sahat/hackathon-starter/blob/master/.env.example#L53 .
At some point, we may adjust the demo deployment with custom env variables, but right now it is going to be the defaults in the .env.example.


Point to SnarkVM derives crate

This PR is meant as a follow up to AleoHQ/SnarkVm#13 and updates the metrics crate to use the derives crate in SnarkVM as a dependency.
Note, this will need to be updated with the new commit hash once the SnarkVM PR is merged, and the build is expected to fail until this is the case.
Update: this also deletes the derives crate from SnarkOS in favour of the SnarkVM version.

LGTM :+1:

LGTM :+1:


Upgraded to latest netty to avoid memory leak

Netty recommends upgrading due to a memory leak, so I'll get this out there.

When can we expect release with this changes?

@artkoshelev - Today! It's out.


QUESTION:: When the stable version comes?

When the stable version comes?
Is there any information when we can use it in production wihtout issues)))))?

v1.0 does not have a release date yet.


win9 low on disk space in Temp directory.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
win9 low on disk space in Temp directory.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Removing old files and directories in Temp directory to free up disk space.


Resolve the disk space issues

Merged https://github.com/hibernate/ci.hibernate.org/pull/20

Do we keep track of issues related to the maintainance of CI somewhere?
Should we use the WEBSITE tag on JIRA?

'WEBSITE' has a 'ci.hibernate.org' component for us to use, but we didn't use it much so far.
We could start to track further TODOs


Travel only with Lego Gyro

How can I only travel with a Lego Gyro?

Sorry, this repo not maintained


Authentication not working with azure repositories

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pip
Package manager version
No response
Language version
python 3.12
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
registries:
  python-azure:
    type: python-index
    url: https://pkgs.dev.azure.com/ORG_NAME/_packaging/ArtifactRepository/pypi/simple/
    username: ORG_NAME
    password: ${{secrets.PYTHON_REGISTRY_PKGS_DEV_AZURE_COM_ORG_NAME_PACKAGING_ARTIFACTR_PASSWORD}}
updates:
  - package-ecosystem: "pip" # See documentation for possible values
    directory: "/"
    insecure-external-code-execution: allow
    registries:
      - python-azure
    schedule:
      interval: "weekly"
    labels:
      - "patch"
      - "dependencies"
    reviewers:
      - TEAM_NAME
    target-branch: "main"

Updated dependency
No response
What you expected to see, versus what you actually saw
What I expect to see
updater | 2024/02/07 16:00:10 INFO <job_784227778> Checking if fastapi  needs updating
  proxy | 2024/02/07 16:00:10 [015] GET https://pypi.org:443/simple/fastapi/
  proxy | 2024/02/07 16:00:10 [015] 200 https://pypi.org:443/simple/fastapi/
  proxy | 2024/02/07 16:00:11 [019] GET https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/ArtifactRepository/pypi/simple/fastapi/
  proxy | 2024/02/07 16:00:11 [019] * authenticating python index request (host: pkgs.dev.azure.com)
  proxy | 2024/02/07 16:00:11 [019] 200 https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/ArtifactRepository/pypi/simple/fastapi/
updater | 2024/02/07 16:00:11 INFO <job_784227778> Latest version is 0.109.2

Instead I get a 401 error saying it's not able to access the repository. I have verified that the tokens themselves work, and Dependabot itself is working on some repositories and not on others.
 proxy | 2024/02/12 03:53:49 [047] GET https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/ArtifactRepository/pypi/simple/PACKAGE_NAME/
  proxy | 2024/02/12 03:53:49 [047] * authenticating python index request (host: pkgs.dev.azure.com)
  proxy | 2024/02/12 03:53:49 [047] 200 https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/ArtifactRepository/pypi/simple/PACKAGE_NAME/
  proxy | 2024/02/12 03:53:49 [049] GET https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/UPSTREAM_REPO/pypi/download/PACKAGE_NAME/0.0.1/PACKAGE_NAME-0.0.1-py3-none-any.whl
  proxy | 2024/02/12 03:53:49 [049] 401 https://pkgs.dev.azure.com:443/ORG_NAME/_packaging/UPSTREAM_REPO/pypi/download/PACKAGE_NAME/0.0.1/PACKAGE_NAME-0.0.1-py3-none-any.whl
  proxy | 2024/02/12 03:53:49 [049] Remote response: {"$id":"1","innerException":null,"message":"TF400813: The user 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' is not authorized to access this resource.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000}

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
Additional Info
It is basically this same issue, but for Python

We're seeing exactly the same thing, have tried configuring Dependabot to use registries.python-azure.token as well as username + password, same results. We use this token with pip, poetry and it works fine so this appears to be unique to dependabot.


Cannot enable Tweak Injection - continuous Watchdog errors

Hi there,
I was directed here from my post on r/jailbreak (link). I'm currently using an iPhone 12 running iOS 15.3.1 and jailbroken with Dopamine 2.0.11. Despite only having a few tweaks installed (iCleaner Pro, Watusi, Bioprotect, and Legizmo), I'm experiencing frequent crashes with Dopamine, often without warning.
I've attempted to resolve the issue by re-jailbreaking multiple times over the past few days, but unfortunately, I've had no success. Each attempt seems to result in a different outcome, which is incredibly frustrating.
Initially, I tried removing the jailbreak entirely and reinstalling it from scratch. While this appeared to work initially, as soon as I installed iCleaner, the device froze and eventually rebooted with a userpanic error. Subsequent attempts yielded varying results, sometimes freezing during the "Patchfinding" stage, and other times rebooting with the same error.
In another attempt, after successfully jailbreaking, I installed PreferenceLoader and ElleKit. However, upon rebooting as prompted, the device again encountered the panic error and Sileo disappeared. Restarting Springboard brought Sileo back, but attempting to enable Tweak Injection caused the device to crash repeatedly.
Even after uninstalling all tweaks and starting fresh, I'm still unable to enable Tweak Injection. I was advised to delete the udid folder in /private/preboot/ using Filza, but unfortunately, the delete option is greyed out, preventing me from doing so.
Do you have any suggestions on how to resolve this issue? Any help would be greatly appreciated.

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Hey @opa334 thanks for responding. I've eventually gotten around the issue by erasing and restoring my phone. Everything now works the way it should do. Hopefully that'll be the last of my problems with it.

Hey @opa334 thanks for responding. I've eventually gotten around the issue by erasing and restoring my phone. Everything now works the way it should do. Hopefully that'll be the last of my problems with it.

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem.
Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

After activating Tweak inject, I get such a Watchdog error. After I press OK, the device hangs. When should I make a sysdiagnose? After I do a hard reboot?

And the question is, what exactly is the name of the .ips file in analytics? I tried to find him, but it didn't work out.

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

can you check?

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

can you check?

I have not received a sysdiagnose

After activating Tweak inject, I get such a Watchdog error. After I press OK, the device hangs. When should I make a sysdiagnose? After I do a hard reboot?

After activating Tweak inject, I get such a Watchdog error. After I press OK, the device hangs. When should I make a sysdiagnose? After I do a hard reboot?

u here?

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

can you check?

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

can you check?

I have not received a sysdiagnose

i send you sysdiagnose, but im upload it to dropmefiles

iconservicesagent gets stuck which caused SpringBoard to get stuck aswell, leading to the watchdog timeout.

can you fix it?

Regarding the issue you're reporting, it is known but I have no clue what causes it or anything. Never been able to reproduce it either. It's something to do with the icon cache, but the thing that doesn't really make sense is that it works when tweak injection is disabled. Maybe produce a sysdiagnose right after the watchdog timeout and send it to me via email at<EMAIL_ADDRESS>https://it-training.apple.com/tutorials/support/sup075.

Can I send you a sysdiagnose? I have the same problem. I wrote to you earlier about her

sure

can you check?

I have not received a sysdiagnose

i send you sysdiagnose, but im upload it to dropmefiles

iconservicesagent gets stuck which caused SpringBoard to get stuck aswell, leading to the watchdog timeout.

can you fix it?

since I have no clue what causes this, no

I think I know the reason for this error. Recently, after installing a large number of applications from GBox, my device started hanging again, I found the folder where this cache is stored, I cleared this folder and magically the device installed the application from GBox without any freezes.
Here is the path to the cache folder that I found: /var/containers/Shared/SystemGroup/systemgroup.com.apple.lsd.iconscache/Library/Caches

After installing one application through GBox, there were 4 files. But after reactivating Dopamine, there were 1394 files

That's a stock bug, but TrollStores "Reload Icon Cache" option should wipe that folder aswell, no?

I started the process, waited, and the device went into respring.  There are 435 files left

I found a "fix" for it that's pretty dumb in my opinion (that miraculously worked "instantly"), so after the watchdog timeout, go on dopamine, turn on tweak injection, ⚠REBOOT LATER⚠, go back to the main menu of dopamine & click on "restart environment (or springboard, try both cause I don't remember well lol)

I found a "fix" for it that's pretty dumb in my opinion (that miraculously worked "instantly"), so after the watchdog timeout, go on dopamine, turn on tweak injection, ⚠REBOOT LATER⚠, go back to the main menu of dopamine & click on "restart environment (or springboard, try both cause I don't remember well lol)
EDIT: do this only if rebuilding icon cache doesn't work ;)

That doesn't fix anything.

Really ? That works for me... every time I jailbreak, watchdogs removes inject tweaks toggle, then I re-enable them, click on reboot later & reboot springboard... but I also noticed that by doing this, CraneSupport.dylib isn't getting loaded in the springboard... so I can't use Crane at all :(, is there any other way that can fix the watchdog timeout ? I tried rebuilding Icon cache too, but that didn't help

It is very unlikely the icon cache is even the cause for these issues. If it was then it makes no sense why booting with no tweaks works, that should crash the same way, disabling tweaks does not change anything about the icon cache.

 No more need for all that annoying extra steps... but I feel kinda idiot now lmfao, so what I did to "fix it" was to disable custom tweak injection in springboard (I had denied Autotouch & satella for some reason), & also just straight up deleted Autotouch. So now I'm happy lol, sorry if I wasted your time

Im back, I still have that issue and found it quite peculiar that by opening Filza & going to the jb directory & just wandering there a few seconds (and in the settings app too), re-enabling the tweaks (without rebooting now) & reloading environment works to successfully jailbreak... (I know I've explained it shittyfully, would sharing my watchdog sysdiagnose help ?)


Feat: Add Gen3/Arborist authorization check

This adds a missing authorization check to ensure that the user is indeed authorized to access the requested "team project".

@rkboyce FYI - once merged and deployed, this change will require an extra installation of Gen3/Arborist.


[web] Pointer Binding Tests fail when DPI > 1 in Chrome >= 108

It seems that a change in behavior in Chrome 108 has started scaling synthetic mouse events' offset position by the DPI of the screen. Our engine CI breaks when attempting to update the version of Chrome to anything greater than the current 107 version.
Here's the related Chromium bug:

https://bugs.chromium.org/p/chromium/issues/detail?id=1407034

Accidentally discovered by @eyebrowsoffire when he ran the tests in a high DPI display in an unrelated change.

Some notes:

This doesn't seem to affect our CI directly, because tests there must be always be running in DPI=1 (and we fake higher DPIs through code, not actual browser configuration)
It seems that Chrome has always done (or attempted to do) something like this?

https://github.com/chromium/chromium/commit/81a26910b2b492523ef8970a135a07459fa53d8b#diff-b5f8f49500a102020d3ab688dd91e6d42d5fc249ba7f80829f8fbd1994e16c62L463-R461

This was fixed by explicitly specifying the DPR of the screen when launching Chrome in test mode.


Favicon Added

IMPORTANT: When creating your Pull Request, please use the following format for the title: Category - Resource Name & Section
PR Title samples:

Web development - CSS Portal & Tools
Web development - Leetcode & Challenges

Closes #587
Description:

Provide a brief description of the pull request
The favicon icon is not on the website that icon is now added
Screenshot :

Resource URL:

Insert the URL of the resource you're proposing

#587

Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[x] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[x] I followed the prescribed PR title template. (Check this if you're adding a resource)

fill the bracket with x. Something like this [x]

@jfmartinz  kindly tell me why the checks failed

@jfmartinz
Kindly review the PR and merge adding suitable labels
Thank you


Info: Which is a good ReactJS panel to add to manange models and CRUD?

Info: Which is a good ReactJS panel to add to manange models and CRUD that would be added to this project?

Any suggestion?


CENC support

https://www.w3.org/TR/eme-stream-mp4/

@89z
https://github.com/abema/go-mp4/issues/13
go-mp4 already supports pssh box and tenc box.
Can you tell me in more detail about your request?

Can you tell me in more detail about your request?

If I have an encrypted MP4 and the Key, I want to be able to decrypt it.

go-mp4 has no encryption/decryption feature yet.
At the moment, I don't decided whether to add the feature.

@sunfish-shogi If you want to close this issue, it may be good to know that the same issue was raised by the same person in in github.com/edgeware/mp4ff  and as a result I improved and implemented decryption of both cenc and cbcs. The latest PR on this matter is mp4ff PR 157.

Nothing wrong with multiple packages having support. Owner here may discover an improved method for decrypting, which is faster or less memory, or less lines of code.
Please don't discourage that.

@sunfish-shogi @89z I don't discourage multiple implementations.
For me, go-mp4 is an excellent tool to manipulate and extract boxes.
But, I think it is good if a software does one thing well instead of doing a little of everything. Media handling including encryption apparently has low priority, which I think is a good decision.
go-mp4 is an active and well-maintained project, with a relatively small number of open issues. Still, in my view, it is always good to close issues where no progress is expected, so my suggestion would be to give this issue an "out-of-scope" label and close it.

you're directly contradicting yourself. In the same breath, you say "I don't discourage multiple implementations" and "close it".
You've made your opinion known. You aren't the owner here, or even a contributor apparently. Please allow the maintainer to make up their own mind. From my understanding, only one Go package currently can do CENC, so its a poor idea for someone to go around killing other potential implementations are you are doing.
Please stop.


Move Azure functions documentation to Azure repository

:warning: Validation status: warnings

File
Status
Preview URL
Details

sandbox/functions-recipes/functions-basics.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/functions-basics.md

Line 21: [Warning] Illegal link: [Configuring timeout](hostjson.md#configuring-timeout) -- missing bookmark. The file functions-recipes/hostjson.md doesn't contain a bookmark named configuring-timeout.
Line 22: [Warning] Illegal link: [Configuring queues](hostjson.md#configuring-queues) -- missing bookmark. The file functions-recipes/hostjson.md doesn't contain a bookmark named configuring-queues.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Hi @priyamohanram. Do you mind providing some context for this PR?

I'm working on moving all the conceptual/reference content for Azure functions from the Sandbox to the main Azure repo. It isn't ready yet, and I created the PR to view the incremental changes in staging. I'll mark the PR with a sign off tag when it is ready for review.

:warning: Validation status: warnings

File
Status
Preview URL
Details

sandbox/TOC.yml
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

sandbox/functions-recipes/development-environment.md
:white_check_mark:Succeeded

sandbox/functions-recipes/functions-basics.md
:white_check_mark:Succeeded

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/triggers-bindings.md
:white_check_mark:Succeeded

sandbox/TOC.yml

[Warning] Invalid file link:(~/functions-recipes/triggers-bindings.md).
[Warning] Invalid file link:(~/functions-recipes/functions-basics.md).
[Warning] Invalid file link:(~/functions-recipes/development-environment.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

sandbox/TOC.yml
:white_check_mark:Succeeded
View

sandbox/functions-recipes/development-environment.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/functions-basics.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/triggers-bindings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

sandbox/TOC.yml
:white_check_mark:Succeeded
View

sandbox/functions-recipes/development-environment.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/functions-basics.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/triggers-bindings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@rloutlaw

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/sandbox, working directory: W:\hbsf-s, target branch: master, target branch commit: dd21a637bf9f273cd289a30c1bae9256029ddad1, source branch: 3afd1aa36f6c0c254b415acead9704d7/AzureFunctions, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

sandbox/TOC.yml
:white_check_mark:Succeeded
View

sandbox/functions-recipes/development-environment.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/functions-basics.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/includes/routes-azureportal.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-infunction.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-optionalparameters.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-prefixes.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-routeparameters.md
:white_check_mark:Succeeded

sandbox/functions-recipes/media/integratepage.png
:white_check_mark:Succeeded

sandbox/functions-recipes/media/integratetab.png
:white_check_mark:Succeeded

sandbox/functions-recipes/routes.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/triggers-bindings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Is it possible to leave the example here and cross-post to the main Azure repo?

:warning: Validation status: warnings

File
Status
Preview URL
Details

.openpublishing.redirection.json
:warning:Warning

Details

sandbox/TOC.yml
:white_check_mark:Succeeded
View

sandbox/functions-recipes/development-environment.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/functions-basics.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/hostjson.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/includes/routes-azureportal.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-infunction.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-optionalparameters.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-prefixes.md
:white_check_mark:Succeeded

sandbox/functions-recipes/includes/routes-routeparameters.md
:white_check_mark:Succeeded

sandbox/functions-recipes/media/integratepage.png
:white_check_mark:Succeeded

sandbox/functions-recipes/media/integratetab.png
:white_check_mark:Succeeded

sandbox/functions-recipes/routes.md
:white_check_mark:Succeeded
View

sandbox/functions-recipes/triggers-bindings.md
:white_check_mark:Succeeded
View

.openpublishing.redirection.json

[Warning] 'W:\kr3a-s\sandbox/functions-recipes/logging.md' would be overwritten by redirection rule configured in master redirection file .openpublishing.redirection.json. Please remove the original file to resolve this warning.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Permission denied error to reconfigure/uninstall the extension

[READ] Step 1: Are you in the right place?
Yes, I tried raising this issue firebase support and got redirected to me github issue after making necessary checks from their end.
[REQUIRED] Step 2: Describe your configuration

Extension name: firebase/firestore-send-email
Extension version: 0.1.6-rc.1 / 0.1.12
Configuration values (redact info where appropriate):

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
We tried updating the configuration and the update started throwing error. So we tried uninstalling the extension it didn't work. So we tried installing new version of the extension, neither did it work. Now the extension is completely not working.
Today i managed to update the extension to latest version 0.1.12
Getting the following error while trying to reconfigure:
; RESOURCE_ERROR at /deployments/firebase-ext-firestore-send-email-6ns1/resources/mods-api-enable-iam: {"ResourceType":"deploymentmanager.v2.virtual.enableService","ResourceErrorCode":"403","ResourceErrorMessage":{"code":403,"message":"Permission denied to enable service [iam.googleapis.com]\nHelp Token: <token>","status":"PERMISSION_DENIED","details":[{"@type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"googleapis.com","subject":"110002"}]},{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"AUTH_PERMISSION_DENIED","domain":"serviceusage.googleapis.com"}],"statusMessage":"Forbidden","requestPath":"https://serviceusage.googleapis.com/v1/projects/prot-4dc6e/services/iam.googleapis.com:enable","httpMethod":"POST"}}; RESOURCE_ERROR at /deployments/firebase-ext-firestore-send-email-6ns1/resources/mods-api-enable-cloudfunctions: {"ResourceType":"deploymentmanager.v2.virtual.enableService","ResourceErrorCode":"403","ResourceErrorMessage":{"code":403,"message":"Permission denied to enable service [cloudfunctions.googleapis.com]\nHelp Token: <token>","status":"PERMISSION_DENIED","details":[{"@type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"googleapis.com","subject":"110002"}]},{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"AUTH_PERMISSION_DENIED","domain":"serviceusage.googleapis.com"}],"statusMessage":"Forbidden","requestPath":"https://serviceusage.googleapis.com/v1/projects/prot-4dc6e/services/cloudfunctions.googleapis.com:enable","httpMethod":"POST"}}; RESOURCE_ERROR at /deployments/firebase-ext-firestore-send-email-6ns1/resources/mods-api-enable-cloudbuild: {"ResourceType":"deploymentmanager.v2.virtual.enableService","ResourceErrorCode":"403","ResourceErrorMessage":{"code":403,"message":"Permission denied to enable service [cloudbuild.googleapis.com]\nHelp Token: <token>","status":"PERMISSION_DENIED","details":[{"@type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"googleapis.com","subject":"110002"}]},{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"AUTH_PERMISSION_DENIED","domain":"serviceusage.googleapis.com"}],"statusMessage":"Forbidden","requestPath":"https://serviceusage.googleapis.com/v1/projects/prot-4dc6e/services/cloudbuild.googleapis.com:enable","httpMethod":"POST"}}; RESOURCE_ERROR at /deployments/firebase-ext-firestore-send-email-6ns1/resources/mods-api-enable-firebase: {"ResourceType":"deploymentmanager.v2.virtual.enableService","ResourceErrorCode":"403","ResourceErrorMessage":{"code":403,"message":"Permission denied to enable service [firebase.googleapis.com]\nHelp Token: <token>","status":"PERMISSION_DENIED","details":[{"@type":"type.googleapis.com/google.rpc.PreconditionFailure","violations":[{"type":"googleapis.com","subject":"110002"}]},{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"AUTH_PERMISSION_DENIED","domain":"serviceusage.googleapis.com"}],"statusMessage":"Forbidden","requestPath":"https://serviceusage.googleapis.com/v1/projects/prot-4dc6e/services/firebase.googleapis.com:enable","httpMethod":"POST"}}
Uninstallation error from the other version(0.1.6-rc.1):
; RESOURCE_ERROR at /deployments/firebase-ext-firestore-send-email/resources/processQueue: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"403","ResourceErrorMessage":{"code":403,"message":"Permission 'cloudfunctions.functions.get' denied on resource 'projects/prot-4dc6e/locations/europe-west1/functions/ext-firestore-send-email-processQueue' (or resource may not exist).","status":"PERMISSION_DENIED","statusMessage":"Forbidden","requestPath":"https://cloudfunctions.googleapis.com/v1/projects/prot-4dc6e/locations/europe-west1/functions/ext-firestore-send-email-processQueue","httpMethod":"GET"}}
The cloud function ext-firestore-send-email-processQueue already got deleted. I think this could be one reason for un-installation failure.
The extension service account has the following permission in IAM

Cloud Datastore User
Cloud Run Service Agent

I even tried adding Cloud Function Admin permission, but still didn't work.
Tried both both firebase console as well as cli, getting the same error.
Expected result
Possible to reconfigure/uninstall the extension.
Actual result

Unable to reconfigure the extension.
Unable to uninstall the extension.

Hi @binoyudayan
I have tried to replicate the issue to confirm this is an issue with a new version release.
The installation installed successfully for me.
Using the cli, can you try the following...
firebase ext:update {ext-name} . --project={project-name} from the firestore-send-email directory

Hi @dackers86,
Thank you for the quick reply. I have tried and updated the extension from 0.1.11 to 0.1.12. The problem is I'm unable to reconfigure the updated extension and uninstall the old version of the extension. I have pasted the error from console/cli: there are some permission error being thrown. As per the firebase support, the user has all the permission needed. Actual issue started on version 0.1.6-rc.1 while we were trying to update the configuration. Now i'm stuck because i can not update the configure and delete the old version of the extension.

Can you try deploying a basic function with the same name as ext-firestore-send-email-processQueue and then re-triggering the re-installation?

Still same errors for both configuration update and uninstall :(

I couldn't find any version older than the one I deployed yesterday. Version 2 & 3 is from yesterday.

okay. The user has Editor has permission as i mentioned before. So shall I contact firebase support again?

@binoyudayan I think that although this was a firebase installation issue, the solution may be something Firebase support could potentially provide a solution for.
I'm not sure which permission is required to uninstall, I could take a long time when trying to replicate.
Can you contact Firebase support and include the response here?

@dackers86 Sure, thank you for the support. :+1:

Closing until further feedback provided.

Did you get any updates on this issue? I'm having the same thing on 0.1.13 here. It is infuriating. My production email notifications are down because of this issue!

Did you get any updates on this issue? I'm having the same thing on 0.1.13 here. It is infuriating. My production email notifications are down because of this issue!

Complete reinstall solved the issue for me

In my case the cloud service account had not enough permissions anymore. Seems like they got somehow lost on the way...
Double check that your Google Cloud API Service Agent<EMAIL_ADDRESS>has all required roles. By default it should have "Editor" (roles/editor)

H, Finally this worked after adding Project IAM Admin and Security Admin  roles for the user. The user already has Editor permission. Something happened on the way as @rbedemann mentioned.
I wanted to update it here as it might help someone.

@rbedemann Thanks so much, your comment here solved the issue for me.

Heads up!
Be sure to check if you are changing Google APIs Service Agent
It should look something like this:
<EMAIL_ADDRESS>then add Basic -> Editor permission. That's it.


serpl: init at 0.1.26

Description of changes
Adds Serpl package, a simple terminal UI for search and replace, ala VS Code.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.
[ ]

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

I found about it today via the neovim reddit, found it pretty cool and I am just curious and if it's the same for you :) ?

No, someone I follow on github starred it and I decided to check it out. The project description seemed intriguing.


Add in name mappings to Marketo script

Needed to properly populate values in Marketo

@nicholassewitz - would you mind running the JSON code through https://jsonformatter.org/ (and pasting back in) so that the formatting is correct and we can be sure there are no errors?

(Also, apologies, I've been OOO the past few days and am just now seeing this.)

np. I added in formatting and tested on my local


fix wrong result of group_concat with order by or null args

Proposed changes
Issue Number: close #xxx
Problem summary

signatures without order element are wrong
signature with one arg is miss
group_concat should be NullableAggregateFunction
fold constant on fe should not fold NullableAggregateFunction with null arg

Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 36.66 seconds
load time: 488 seconds
storage size:<PHONE_NUMBER>5 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230118205028_clickbench_pr_83716.html


Gravity vector override of Area3D doesn't override fully the project's default gravity vector

Godot version
v4.1.1.stable.official [bd6af8e0e]
System information
Godot v4.1.1.stable - Pop!_OS 22.04 LTS - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 970 (nvidia; 535.98) - Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 Threads)
Issue description
When putting a RigidBody3D inside an Area3D set to override (mode = "Replace") the gravity vector to a null vector, we still see the rigid body falling.
The fall speed is slower than the default one, still it's falling.
The fall seems to stop after a little while.
Setting the "can_sleep" property to false seems to extend the fall asymptotically.
Setting the default gravity vector (project settings) to 0 seems to fix this behavior.
Steps to reproduce
From the minimal reproduction project:
Minimal scene setup  with:
An Area3D

gravity_space_override set to Replace
gravity_direction set to (0,0,0)

A default RigidBody3D
Test1:

Run the scene and observe the capsule falling and stopping few moments later

Test2:

Set the property "can_sleep" to false on the RigidBody3D
Run the scene and observe the capsule falling slower and slower

Test3:

Set the project setting "physics/3d/default_gravity_vector" to (0,0,0)
Run the scene and observe the capsule falling no more

Minimal reproduction project
Area3dOverridePbDemo.zip

It seems godot will step the physics world first with area size equals zero, which means it will accumulate the default gravity and  damping vaue and give it a velocity.

After this the area will be inserted and it can correctly calculate the physics using the area override value.

I could reproduce, i'll try and fix it!


Venv "doesnt exist". However, it does.

Every time I try to switch to an interpreter, it says it does not exit.

Going to need more info than that.. Can you list the venvs on the file system that the plugin thinks doesn't exist? Are they symlinks or ordinary files? Which venvs are detected and which are not?

Hi again.
I realized now that you are using the old version of VenvSelect. Its not being updated anymore and a new version has been rewritten from scratch that works in a very different way. Please try that one instead. You have a link to it at the top of the readme.
I think it will work a lot better for you.


Add some built-in app information so that users can see the icon and names without downloading the apps first.

The previous logic uses package manager to read info about apps from phone, which is not friendly to those who have not installed all the apps. I extract all the pics and names from the apks and put them in the app so that the user could see all the information even without installing all the apps. The installation would be delayed until user clicks any deeplink. Also fix some bugs and some UI components to make app look better.
fixes #21, fixes #22, fixes #20, fixes #11
resolve #18,

All bugs fixed, thanks for pointing out!


I dont even know

I followed everything as best as i could but its still not working would someone be able to walk me through this to understand

certainly what is your discord?

Lasky Kirito#9619


Added Triplewise operator

This is basically a clone of Pairwise, modified for iterating over triplets instead of pairs.
It probably wouldn't take much to generalise Pairwise and Triplewise as a method that overloads on the number of arguments to the resultSelector such that the following is valid:
source.Tuplewise((a, b) => a + b);
source.Tuplewise((a, b, c) => a + b + c);
source.Tuplewise((a, b, c, d) => a + b + c + d);

Maybe this could be overloads for Batch ?

You can do this today with Window + Fold except window allocation might be expensive for simple cases. Also, the window size and Fold arity can be redundant and error prone to maintain.

It probably wouldn't take much to generalise Pairwise and Triplewise

I like Tuplewise as the more general name and solution so why not just start with that? Pairwise would then just delegate to Tuplewise of 2.

A .tt template looks appropriate here.

Because I only thought of it while submitting the PR :)

Happens to me all the time. 😆

A .tt template looks appropriate here.

Seems reasonable. I've not played with .tt templates much but I'll see what I come up with.

Awesome and an occasion to learn and there are plenty of examples in MoreLINQ.

It probably wouldn't take much to generalise Pairwise and Triplewise
I like Tuplewise as the more general name and solution so why not just start with that? Pairwise would then just delegate to Tuplewise of 2.
Because I only thought of it while submitting the PR :)
In light of this, I vote to abandon this PR in favour of a new one that adds Tuplewise with its overloads.

That's fair, will do.

That's fair, will do.

Thanks @jonasdmentia! Closing this meanwhile.


Forestry doors showing unlocalized name

Cherry Door
Teak Door

Versions please?

TOP 1.1x-1.4.2
Forestry <IP_ADDRESS>2
MC 1.10.2

@mezz, any idea what I could be doing wrong? I do the localization on the client now and from the server I sent over unlocalized names for the itemstack

Forestry has complex localization that often involve multiple localization keys and grammar, it needs more than just the localization string. I think you will have to serialize the ItemStack so that it can localize itself on the client.
I override Item#getItemStackDisplayName here:
https://github.com/ForestryMC/ForestryMC/blob/mc-1.11/src/main/java/forestry/arboriculture/items/ItemBlockWood.java
And this is the localization code:
https://github.com/ForestryMC/ForestryMC/blob/mc-1.11/src/main/java/forestry/arboriculture/WoodHelper.java#L24

Hmm, transmitting ItemStacks could potentially give big network overhead. Especially if getPickBlock for some block returns a very heavy itemstack. I was hoping for a lighter solution but I guess it will not be easy

It will definitely be more overhead than before, but one ItemStack per player per tick (worst case?) is still not very much is it? It may be the only way to be fully-compatible with mods that override getItemStackDisplayName. If you want to test a very heavy block, try Forestry saplings because they have NBT stored on them for genetics and it is preserved by getPickBlock.

Fixed next version


JsonCodecWrapper defeats CODECS LRUCacheMap cache

When using a high number (eg hundreds of thousands/millions) of RedissonJsonBucket instances, I found that the use of the JsonCodecWrapper generates an enormous number of values being entered into org.redisson.command.RedisExecutor#CODECS .
This is because a copy of the codec is created for every bucket, which then appears to the executor as a new codec for every single bucket.
I'm unclear on what the wrapper is achieving, especially the org.redisson.codec.JsonCodecWrapper#JsonCodecWrapper(org.redisson.codec.JsonCodec<?>) variant that simply presents the underlying codec unchanged, but perhaps it could implement hashCode/equals.

Is contextClassLoader is different per call? You can simply set useThreadClassLoader = false.

No it's not - I'll use that to workaround the issue, however I believe the issue still remains if left at the default true configuration.

Fixed. Thanks for report.


Checkpointing issues

I had a quick test with Checkpointing feature. I see the following issues

When epochs_between_checkpoints is set,  evaluation is skipped in the same epoch where checkpointing happens.
when steps_between_checkpoints is set,  error occurs during checkpointing of second block

Traceback (most recent call last):
  File "dlio_benchmark/src/dlio_benchmark.py", line 354, in main
    benchmark.run()
  File "dlio_benchmark/src/dlio_benchmark.py", line 295, in run
    steps = self._train(epoch)
  File "dlio_benchmark/src/dlio_benchmark.py", line 236, in _train
    self.stats.end_block(epoch, block, block_step)
  File "/home/ubuntu/storage/dlio_benchmark/src/utils/statscounter.py", line 103, in end_block
    if 'end' in self.per_epoch_stats[epoch][f'block{block}']:
KeyError: 'block2'

Thanks for testing. I'll fix that later today.

@johnugeorge I fixed issue for 2, please check it again.
For 1, evaluation is independent of checkpointing, please double check and confirm again whether you still have that issue. It didn't show on my side.

Thanks @zhenghh04 I tried it and I didn't see any issues


Incremental and hierarchical fallback

This supports three levels of fallback. The requested locale, falling back to the fallback locale and then the default. This allows incremental localisation files, so, for example, you can have de-CH as a swiss localisation with just a few Swiss phrases, over-riding de-DE for the main German language localisation, and then the fallback of en-US for anything not in these files.
This builds the hierarchical locale list in the setLocale method then it loads all files when they are first requested to avoid any issues later.
This PR also includes #38 which adds locale names to the configuration list.
(#30)

I've updated this PR to merge your latest changes and resolve the conflicts. I've also fixed a small bug in the fallback routine associated with resolving all the promises as the deferred path previously didn't include the locale which meant that resolving the promise didn't work correctly.
I've also fixed the fallback tests and added some new test cases.

+1


Add v1.48.x and v1.49.x to the support map

Which problem is this PR solving?
Resolves: https://github.com/jaegertracing/jaeger-operator/issues/2331
Description of the changes
Adds the latest 2 releases of jaeger-operator to the COMPATIBILITY.md file
How was this change tested?
The information is taken by first checking out to the tags and then for each tag:

Kubernetes: Kind .yamls present in the root dir indicating the tested K8s versions
Strimzi Operator: Strimzi Operator version being pulled in the Makefile

Cert-Manager: From the CERTMANAGER_VERSION variable defined in the Makefile

Checklist

[ ] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[ ] I have signed all commits
[ ] I have added unit tests for the new functionality
[ ] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

Hi @ishaqkhattana, thanks for your contribution!
Could you check the DCO job from the CI?

Hi @ishaqkhattana, thanks for your contribution! Could you check the DCO job from the CI?

Hey, it's my pleasure. Also, just checked my signature on the commit and I was using my secondary email. Pushed a small fix and it seems to be good now


Version Bump for Neuroc

Neuroc version is already 0.6, so this bumps it for when we pull it.

probably needs to be rebased on master


should we group command for easy read?

if we can group command like kubectl,it will easy to read,like this
Release Commands:
  get         download extended information of a named release
  history     fetch release history
  install     install a chart
  list        list releases
  test        run tests for a release
  rollback    roll back a release to a previous revision
  status      displays the status of the named release
  template    locally render templates
  uninstall   uninstall a release
  upgrade     upgrade a release

Chart Commands:
  create      create a new chart with the given name
  dependency  manage a chart's dependencies
  pull        download a chart from a repository and (optionally) unpack it in local directory
  show        show information of a chart
  lint        examines a chart for possible issues
  package     package a chart directory into a chart archive
  repo        add, list, remove, update, and index chart repositories
  search      search for a keyword in charts
  verify      verify that a chart at the given path has been signed and is valid

Other Commands:
  completion  Generate autocompletions script for the specified shell (bash or zsh)
  env         Helm client environment information
  plugin      install, list, or uninstall Helm plugins
  version     print the client version information

Use "helm <command> --help" for more information about a given command.

@zgfh This is a good proposition. Currently there is a issue open with Cobra for this https://github.com/spf13/cobra/issues/836
Helm uses Cobra for it's cli, it would be nice to support this after Cobra releases support themseleves.

@waveywaves  if you allow use package: k8s.io/kubectl/pkg/util/templates for now, I like to make  a PR。 Then when cobra release we can replace it

@zgfh Please do so if you can.

@waveywaves  done

re-opening as #7917 was reverted in #8153.

Hi, @zgfh - thanks again for starting this work. As you may have seen, #7917 was reverted in #8153. To move forward now, the next step would be to address those concerns.
I'll resolve this issue now due to inactivity. If you or someone else would like to start a broader discussion about command grouping and get buy-in from the community on the approach, you could file a Helm Improvement Proposal: https://github.com/helm/community/blob/master/hips/hip-0001.md


Activate for all Python file types

Vim's filetype detection determines if a file is Python by:

extension: *.py,*.pyw,.pythonstartup,.pythonrc,*.ptl,*.pyi
shebang

See #219.

@jansorg The tests pass when I run them locally; I don't know why they fail in the Travis build.

@airblade Tests with latest vim seem to fail on Travis, *.pyi should be ignored but all other python files should be accepted

I upgraded my Vim to 8.1.2234, the same as the Travis build is using, and all the tests pass for me locally.

@airblade Let me check this on Linux with this particular version, perhaps it's not occurring on macOS.

How can I display the currently detected filetype for the current buffer in vim?

@jansorg :echo &filetype or :echo &ft.

@airblade I'm seeing these errors when the tests are run on my machine. These errors are later removed from the screen and replaced with the test runner messages.
This is a snippet taken from the stream of error messages:
Error detected while processing function RunTest[14]..Step[1]..<SNR>2_expect_request[37]..LogRequestHistory:
line    3:
E714: List required
"~/.vim/pack/kite/start/vim-plugin-git/editors-json-tests/data/whitelisted/file.js" 0L, 0C
Error detected while processing function RunTest[14]..Step[1]..<SNR>2_expect_request_count:
line    6:
E714: List required
E714: List required
E714: List required
E714: List required
"~/.vim/pack/kite/start/vim-plugin-git/editors-json-tests/data/whitelisted/too-large.py" 93601L, 1123277C
Error detected while processing function RunTest[14]..Step[1]..<SNR>2_expect_request:
line   16:
E714: List required
Error detected while processing function RunTest[14]..Step[1]..<SNR>2_expect_request[37]..LogRequestHistory:

@jansorg Those errors were all caused by the /testapi/request-history endpoint not returning a JSON list.  I can't tell what it was actually returning but I'll make the code more robust.

@jansorg Oh, the tests pass now.

Rebased and merged in bde4e93...09b0eb2.


[n4biasCorrection] remove std::endl warnings

COMMIT https://github.com/Inria-Asclepios/medInria-public/commit/4bbbf71d0483da39c90bfdd5bdc9976782776a3d
Based on https://github.com/Inria-Asclepios/medInria-public/pull/847
This PR removes endl at end of qDebug to avoid compilation warning.
:m:

The original PR is not merged, so why not fix it there?

Oh it is not related to that PR (this PR shouldn't be based on it then)

I need the ubuntu 22 PR to work. So either i do a PR with the ubuntu 22 commits + new ones on a specific topic, or i do a complicated technique where i work on ubuntu22 commits + my new ones, then i commit and through steps i manage to remove the ubuntu 22 commits on a new branch (cherry-pick) to create PRs.
It's easier to create PR and rebase

This is very easy to do with git rebase -i <commit-id> (where commit-id is the last commit that was merged). This allows  you to remove commits that are not related to your PR. I use it all the time.

(when editing the file during the interactive rebase you simply replace pick with drop in front of the commits that are not related)

This PR has been rebased (and switched to 4.1, it was wrongly on master)


Fix deleting expressions

When ustx is loaded, expressions that have been deleted from the project are also deleted from the note (because a null expression descriptor in the note causes an error): UNote
Some expressions that was getting directly from the project are now getting via track (Supplement to #1017)
When expressions are deleted in ExpressionsDialog, the default required expressions are added again: ProjectCommand
Pending as I don't have a solution for duplicate flags.

A solution was made in #1118 for when a required expression is deleted in the Expressions dialog.


Memory Leak

There seems to be a memory leak somewhere... Urg... Will investigate.

So there wasn't a memory leak after all. However since there are a lot of byte[] arrays created and destroyed in this class, it's very hard to figure out what is going on elsewhere.
Will create a pull request with significant memory usage improvements.

Background: I'm using this to stream many terabyte of zipped data from and to gzip in parallel. This change has made a huge difference in memory performance. @shevek

Closing in favour of #5  , which has a review comment now. If we can pass the test suite and a reasonable argument of correctness, I very much want this patch.


refactor(go): move child process handling to dedicated package

Isolate the subprocess handling to a dedicated sub-package, to ensure it
has a better defined API. Also implemented the version check part of the
handshake logic.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 8afff7b122f873df16345a29ef27c008a24f234d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 4188feb01fe03be8d5e1a3592673b9472a338057
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 5c5e844c69432fe73562bcfb7284bd3cfffd9287
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: db74113968af235ece550b93d845cfb0ac83bbe9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: e788ef7637cc46026d3fc39d56ed31fc4f32985f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 771034a54eb461e21afff9634d37a7ac8bf43a02
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Checksum failure during pacmak go build but otherwise lgtm

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 707ceed3993d723774f5bfb3ef74e65f9bffffd9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 252d6cb08936cba8fef9b3b38b88785ae71aa78e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID:<PHONE_NUMBER>ab989e21a98075c4202c3d5ac29ddf
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 40b6ba264a62ea2e5bfae9fdbac41308c8b81128
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 4c3117970ddd13b60e7a0709904ed7b7074e51d1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 5bbe62c21736025727f463a4034aa928562a78a2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Dedup display functions for view commands

Deduplicates functions like display_account_info and display_access_key_list, and puts them into common.rs.
This is just one part of the cleanup process, and there will be more after this one. Don't want to snowball all of these into one giant PR, since that wouldn't be good for anyone looking at it, nor would it increase the chance of it being looked at. So let's go with integrating cleanups often

is it failing because I need to increment the version number?
  with:
    tag_name: 0.1.14
    release_name: 0.1.14
    draft: false
    prerelease: false
  env:
    NEAR_CLI_VERSION: 0.1.14
    GITHUB_TOKEN: ***
Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}


Oddity with JSON response to next

I'm sending next events as x-prolog with body
next

and getting back this strange beastie when it goes to destroy:
{
  "data": {
    "data": [{"X": "c"}],
    "event": "success",
    "id": "4c53430f-9570-4e05-9036f6b5fc63dd8c",
    "more": false,
    "time": 3.951999999999992e-05
  },
  "event": "destroy",
  "id": "4c53430f-9570-4e05-9036-f6b5fc63dd8c"
}

I'd count this as an oddity.

This is fine.  Create and destroy events may embed the first and last answer.  The first happens if
you include the ask option in the create and the latter if auto destruction is enabled (default).  Both
can be combined, which may give you a single response that consists of a create, embedded destroy and embedded first-and-only answer.   This is done to reduce round trips.

its the field naming - data field with data field


PackageManager: Skip empty files

Skip pathologic cases of empty files like ORT's own synthetic package
manager files in the "all-managers" directory.
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests? If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests? If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests? If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

I'd be fine with the proposed removal.

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests? If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

I'd be fine with the proposed removal.

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests?

Are there any package manager specific tests that test the code to detect definition files?

If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

What is the actual reason for this change?

@fviernau @mnonnenmacher This chnages renders the "findManagedFiles" test in PackageManagerTest more or less useless. Would you be fine with simply removing the test and the "src/funTest/assets/projects/synthetic/all-managers" directory then, and rely only on the package-manager-specific tests?

Are there any package manager specific tests that test the code to detect definition files?

If so, that would actually make this change unnecessary (at least for the case of scanning ORT itself)... but I'd probably still keep it, for real-world pathologic cases.

What is the actual reason for this change?

Are there any package manager specific tests that test the code to detect definition files?

You're right; the package-manager-specific tests are already pointed to the definition file, they do not need to find it. So how about then rewriting the "findManagedFiles" test to not use the empty files in the "all-managers" directory, but simply the files below "analyzer/src/funTest/assets/projects/synthetic"?

What is the actual reason for this change?

See the commit message, to avoid bogus findings when scanning ORT with ORT due to the empty package manager files in the "all-managers" directory.

Are there any package manager specific tests that test the code to detect definition files?

You're right; the package-manager-specific tests are already pointed to the definition file, they do not need to find it. So how about then rewriting the "findManagedFiles" test to not use the empty files in the "all-managers" directory, but simply the files below "analyzer/src/funTest/assets/projects/synthetic"?

What is the actual reason for this change?

See the commit message, to avoid bogus findings when scanning ORT with ORT due to the empty package manager files in the "all-managers" directory.

Are there any package manager specific tests that test the code to detect definition files?

You're right; the package-manager-specific tests are already pointed to the definition file, they do not need to find it. So how about then rewriting the "findManagedFiles" test to not use the empty files in the "all-managers" directory, but simply the files below "analyzer/src/funTest/assets/projects/synthetic"?

I thought about this as well, but it's more tedious to maintain because these change more often.

What is the actual reason for this change?

See the commit message, to avoid bogus findings when scanning ORT with ORT due to the empty package manager files in the "all-managers" directory.

But are they that bad? At least this path is excluded which should also be shown in the reports. I was just wondering, if you scan an arbitrary project, would you want to know that there are empty definition files or not?

Are there any package manager specific tests that test the code to detect definition files?

You're right; the package-manager-specific tests are already pointed to the definition file, they do not need to find it. So how about then rewriting the "findManagedFiles" test to not use the empty files in the "all-managers" directory, but simply the files below "analyzer/src/funTest/assets/projects/synthetic"?

I thought about this as well, but it's more tedious to maintain because these change more often.

What is the actual reason for this change?

See the commit message, to avoid bogus findings when scanning ORT with ORT due to the empty package manager files in the "all-managers" directory.

But are they that bad? At least this path is excluded which should also be shown in the reports. I was just wondering, if you scan an arbitrary project, would you want to know that there are empty definition files or not?

But are they that bad?

They clutter up the console output a lot, esp. for package managers that call external tools, as those complain about the invalid syntax in those empty files.

I was just wondering, if you scan an arbitrary project, would you want to know that there are empty definition files or not?

I guess not, as they would also have no influence on the build / distribution.

But are they that bad?

They clutter up the console output a lot, esp. for package managers that call external tools, as those complain about the invalid syntax in those empty files.

I was just wondering, if you scan an arbitrary project, would you want to know that there are empty definition files or not?

I guess not, as they would also have no influence on the build / distribution.

I thought about this as well, but it's more tedious to maintain because these change more often.

Well, the directory structure of those tests does not really change that often, or? Because for this test only the location of the definition files would matter.

I thought about this as well, but it's more tedious to maintain because these change more often.

Well, the directory structure of those tests does not really change that often, or? Because for this test only the location of the definition files would matter.

I thought about this as well, but it's more tedious to maintain because these change more often.

Well, the directory structure of those tests does not really change that often, or? Because for this test only the location of the definition files would matter.

Ok, then let's use this approach.

I thought about this as well, but it's more tedious to maintain because these change more often.

Well, the directory structure of those tests does not really change that often, or? Because for this test only the location of the definition files would matter.

Ok, then let's use this approach.

I'll replace this with another PR shortly.


Update index.html

i made correction in the spelling of programming in line 655 of ;

tock/docs/en-dark/api/index.html

Thanks @Astrodevil for raising this!
HTML is actually generated by MkDocs from the Markdown sources (.md files) in docs-mk folder. You can use etc/serve-docsite-xxx.sh scripts to test/run (localhost:8000) and etc/regen-docsite.shto regenerate all sites versions to docs folder (provided you have Python and mkdocs-material up and running, see docs-mk/README.md).
I just fixed the spelling error in Markdown sources and regenerated HTML: https://github.com/theopenconversationkit/tock/commit/13c32d025dc57c2a56b954d984d6634f2a1d9610
Sorry for not pulling your commit as-is this time, but don't hesitate to fix the Markdown sources directly next time and we will pull the fix!

Thanks @Astrodevil for raising this!
HTML is actually generated by MkDocs from the Markdown sources (.md files) in docs-mk folder. You can use etc/serve-docsite-xxx.sh scripts to test/run (localhost:8000) and etc/regen-docsite.shto regenerate all sites versions to docs folder (provided you have Python and mkdocs-material up and running, see docs-mk/README.md).
I just fixed the spelling error in Markdown sources and regenerated HTML: https://github.com/theopenconversationkit/tock/commit/13c32d025dc57c2a56b954d984d6634f2a1d9610
Sorry for not pulling your commit as-is this time, but don't hesitate to fix the Markdown sources directly next time and we will pull the fix!


Error packaging PCF Sample : Project Reference with output path 0, is not a valid PowerApps Component Type

I'm getting an error on the last step of packaging the samples - on the 'msbuild' step I'm getting:
....\microsoft.powerapps.msbuild.solution\1.1.6\build\Microsoft.PowerApps.MSBuild.
Solution.targets(98,5): error : Project Reference with output path 0, is not a valid PowerApps Component Type  [...\TS_MapControl\solutions\solutions.cdsproj]
Tried on MapControl, IframeControl & ImageUploadControl, both on msbuild 15.* and 16.* tool chain

I am getting the same issue.
After following the instructions here:
https://github.com/microsoft/PowerApps-Samples/blob/master/component-framework/README.md
I successfully run msbuild /t:restore, and then when running msbuild again, i get 2 fails both with the same message as shown in the post above.

I am getting the same issue but specific only for TS_ReactStandardControl. The app works on local but when packaging the solution, it seems to be having some trouble with Whole.None type. Other type seems to be OK.

Got it!

For some reason when solution folder is initialized, the [SolutionName].cdsproj default version is not  1.. Just modify that to 1. then do a msbuild /t:build /restore.

@cyus Thanks for the help solving the issue. Closing the issue.
@radupasol Please re-open the issue, if you feel you need more information.


zoom set programmatically disappears when draggin or resizing

Hi All,
in my application, after calling c3.generate, I call zoom([a,b]) to set an initial zoom.
This works fine, but as soon as the user clicks and drags the mouse on the chart, the zoom disappears.
The initial zoom disappears also when chart.resize() is called (and in my specific case this happens very often, since users can change the size of the chart container, and resize() is the only way to adapt the chart size to its container)
Here's an attached jfiddle : https://jsfiddle.net/ydh162kf/2/

C3 version: 0.7.0
D3 version: 5.9.2
Browser: Chrome 73.0.3683.103
OS: Windows 10

Seems to not happen when the subchart is shown: https://jsfiddle.net/y8aw3j14/

I'm having a similar issue and would like to offer an imperfect workaround:
Save the zoom before the resize then restore it afterwards.
I'm hoping this might provide some insight as to how to fix the problem.
The modified jsfiddle code below:
var chart = c3.generate({
    data: {
        columns: [
            ['sample', 30, 200, 100, 400, 150, 250, 150, 200, 170, 240, 350, 150, 100, 400]
        ]
    },
    zoom: {
        enabled: true,
        type : 'scroll'
    }
});

chart.zoom([-0.1,4.1])

document.getElementById('btn').onclick = function(){
	var zoomSave = chart.zoom();  // save zoom
	chart.resize();
	// chart.load({ });           // using load instead of resize eliminates the extra chart movement
	chart.zoom(zoomSave);         // restore zoom
}


Remove bootstrap from the genome position search box

Description

What was changed in this pull request?

Removed React bootstrap from the genome position search box

Why is it necessary?

React bootstrap is a pain to include and clobbers all styles. It would be better if we got rid of it.

Before:

After:

Fixes #___
Checklist

[ ] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[ ] Unit tests added or updated
[ ] Documentation added or updated
[ ] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[x] Screenshot for visual changes (e.g. new tracks or UI changes)
[ ] Updated CHANGELOG.md

One small thing I found during testing: the search icon doesn't look consistent with the other icons:

It's darker than the other icons
On hover it's not changing to white

My guess is that it's fill property isn't set to currentColor.
Apart from that I would like to test the tileset adding modal but higlass.io is currently down so I can't load any tilesets. Before merging I'd recommend testing that modal once higlass.io is back online.

Updated the normal color to the standard grey and the mouseover color to white 👍 Thanks for the suggestion!


images: clean old and un-used code

since they not in use anymore removing them

Verified with https://jenkins.scylladb.com/job/scylla-master/job/releng-testing/job/next-machine-image/275/


kedro pandera coverage

Description
The more I think about the importance of data contracts ensuring coverage checks as part of a team's workflow feels like a natural evolution of this pattern.
Context
The way I see this, there are two standards a user should aim for:

A "gold standard 🥇" pattern where every dataset in your project has pandera schemas attached (all parameter inputs also have pandera/pydantic definitions too)
A "silver standard 🥈" pattern where just the free-inputs/outputs of a pipeline are properly validated and the rest is treated a closed box.

Possible Implementation

Build an AST introspection utility which uses an instantiated KedroSession object to validate state

Possible Alternatives

Look at building a Pylint plugin to do the same thing

I like the idea, but why would we need AST introspection? Couldn't just we if all the dataset in a pipeline have a schema attached in their metadata? Is it related to the decorator way to trigger  data checks?

So I was thinking about supporting the Python annotations (as well as the catalog metadata), but we don't actually have to do that using static analysis we can actually just inspect the live objects at pipeline creation time.


can't download captcha image - 403 error

Problem:
[2016-04-12 12:26:41,818] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - GET https://www.google.pl/search?q=SEARCH&num=100 via proxy:direct try 3 [2016-04-12 12:26:42,404] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - captcha form detected via proxy:direct [2016-04-12 12:26:42,687] [google-0] DEBUG c.s.s.s.g.s.GoogleScraper - can't download captcha image https://ipv4.google.com/sorry/image?id=12625432490275182982&q=CGMSBFMfRGUY3ZqzuAUiGQDxp4NLawzX2Xk3s7gTst6cuP5RAwbnzCY&hl=en&continue=https://www.google.pl/search?q=SEARCH&num=100 (status code = 403)
[2016-04-12 12:26:42,691] [Thread-23] WARN  c.s.s.t.g.GoogleTask - 261 searches have not been checked
Someone know what is wrong?

Yes it looks like there is an issue now. But not sure it is related to serposcope. I did a lot of search with my own browser to encounter a captcha, and I got the same 403 using my browser.... Now on twitter, people are complaining having 403 on Google too, so maybe there is an issue on Google side. I ll wait tomorrow before investigating further.

That was only google brainless joke. Everything works good :)
@serphacker Thanks for quick response.


Equivalent to TensorArray for while_loop

A large class of algorithms require maintaining an arbitrary length list of arrays over loops.
What is the flow for collecting a list of tensors (all of the same shape and dtype) in a while_loop?
This should be the same notion as TensorArray in tensorflow.
One obvious way is to use python while loops, but what I'm looking for is while_loop support.
Is there a way to do it without unrolling the graph?
Also, if it can only be done with python while loops what are the constraints and performance effects? Is it still jittable? Is it feasible for really long loops?

Most likely, you're looking for jax.lax.scan:
https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.scan.html#jax.lax.scan
e.g., if you were writing, say, an RNN, that's what you would want to use.
Does that help?

TensorArray lets your grow tensors in each loop iteration, but that isn't possible to in XLA (i.e., under jit).
Instead, you should preallocate the full sized arrays you need, and update them using primitives such as while_loop and scan. This may seem extremely inefficient, but is actually only a 2x cost in memory (the difference between the upper triangular half of a matrix and the full matrix).

Thanks for the pointer to lax.scan. Solves the problem for most problems except those with a dynamic length. Thanks for the info about XLA too.

@shoyer re-opening this thread to ask another related question. Is there a way to have both a dynamic halting condition and a dynamically allocated result. Basically, I need scan-like behaviour in that it collects results, but the termination condition is dynamic as in a while_loop. I was wondering how you would implement scan under the hood, and noted that in TF it's with a while_loop. In JAX are you essentially just preallocating a result array tree and then using dynamic_update_slice?

Looks like the _scan_impl in JAX also uses a while_loop using dynamic_update_index_in_dim. Makes sense. So I'm guessing the answer to my problem is to do a similar thing.

Clear

Extending on the question, I wonder: Without sth like TensorArray, how can that be efficient with backprop? Wouldn't it keep a copy of ys of each iteration for backprop? StackOverflow question with more details.


Queue based on Linked List

Title: Queue based on Linked List
Name: NanthaKumar
Label: Feature Request
Assignee: ''

Define You:

[x] DevIncept Participant
[ ] Contributor

Is your feature request related to a problem? Please describe.
No. It's a new feature.

Describe the solution you'd like...
A Queue implemented by linked list from scratch. It will contains methods like enqueue(), dequeue(), peek() and etc.
By implementing with linked list, it'll give enqueue() and dequeue() operations in O(1) time.

You can proceed. Issue assigned. @nknantha


Update version

There's probably a small omission in the last release, with the pom.xml still being in the 0.1.2 version 😉

Codecov Report

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

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   91.39%   91.39%
=======================================
  Files           2        2
  Lines          93       93
  Branches       17       17
=======================================
  Hits           85       85
  Misses          6        6
  Partials        2        2

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 5a2ff1f...cd8c36c. Read the comment docs.

Oops! I replaced the release. I hope JitPack recognizes this. Thank you!


SourceFileReader with wrong path to BarCode

Hi guys. I think I found bug but please validate my findings described below:
SourceFileReader uses private method pathForBarcode in order to get path for BarCode. However,
SourceFileWriter delegates it to pathResolver.
The bug which above causes is: FileSystemImpl:getRecordState returns RecordState.MISSING all the time as path which was saved by SourceFileWriter is different than path used by SourceFileReader. We talk about the case when BarCode is a key.
Does above make sense?

Hey @phajduk I understand what you're saying and I'm looking into it now.
Do you have any code samples that will help by any chance? Maybe an example of the bug?

Hey @KevCron
OK so I have following configuration of my Store:
    private val constructionForUpload = FluentStoreBuilder.parsedWithKey<BarCode, BufferedSource, ConstructionsResponse>(
            Fetcher {
                api.getConstructions().map { it.source() }
            }) {
        parsers = listOf(GsonParserFactory.createSourceParser(gson, ConstructionsResponse::class.java))
        persister = RecordPersisterFactory.create(FileSystemFactory.create(context.cacheDir), 10L, TimeUnit.SECONDS)
        memoryPolicy = MemoryPolicy.builder().setExpireAfterWrite(5).setExpireAfterTimeUnit(TimeUnit.SECONDS).build()
        stalePolicy = StalePolicy.REFRESH_ON_STALE
    }

If I understood Store lib properly following statements are true:

treat cached data in memory data as up-to-date for 5s
treat cached data in File System as up-to-date for 10s

So after 10 secs data is treat as STALE and fetch call should be performed.
As an addition to bug description I can see that StoreUtil.persisterIsStale always returns true because RecordState recordState = provider.getRecordState(key); is always RecordState.MISSING.