Add S3FileSystem Write support

TODO: Compare performance against Presto Java at scale.
Resolves: https://github.com/facebookincubator/velox/issues/4805

CC: @akashsha1, @paul-amonson, @tigrux for early feedback.
I need to run some performance tests to wrap up this. I will share them.

@tigrux @akashsha1 @paul-amonson I did some tests at scale and had to fix the semantics a bit.
I observed that the query would fail after writing a 5GB file. The issue was the difference
between 5 GiB (code limit) vs. GB (AWS limit) upper part limit.
This made me realize that the current TableWriter uses only append() and never a flush() call.
So each part would have been 5GB big and was being buffered in memory before upload which is bad.
I looked at the latest Arrow S3FS implementation and saw that they use a fixed-size part to upload.
I changed the semantics to match this. This made more sense as the write memory is now fixed.
The multi-part upload API also does not match the append() + flush() APIs as it has the min and max part limitations.
Making the append() manage the uploads and flush() a no-op matches the multi-part upload semantics well.
I added some comments to reflect this change.

With the new semantics, I verified that we can now write files larger than 5GiB.

I also looked at the gcs::ObjectWriteStream documentation and it does something similar.
https://cloud.google.com/cpp/docs/reference/storage/latest/classgoogle_1_1cloud_1_1storage_1_1ObjectWriteStream

@pedroerp, @kgpai can you please help merge this? Thanks.

The linux-build failure is unrelated.


refactor: bitwise kernel right and left shifts

Which issue does this PR close?

Follow on to https://github.com/apache/arrow-rs/pull/4159, https://github.com/apache/arrow-rs/pull/4148, https://github.com/apache/arrow-datafusion/pull/6098 and https://github.com/apache/arrow-datafusion/pull/5476
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @izveigor


Application not loading due to lack of Bean

Receiving the message:
Consider defining a bean of type 'com.github.JanLoebel.jsonschemavalidation.provider.JsonSchemaProvider' in your configuration.
Application fails to start and basic context loading test fails.
Using @ComponentScan or @EntityScan pointing to the package doesn't fix the issue.
Using:
'org.springframework.boot' version '2.7.12'
'com.networknt:json-schema-validator:1.0.82'
'com.github.JanLoebel:json-schema-validation-starter:2.3.0'

Fixed by adding to application.class:
@Bean
	public JsonSchemaProvider JsonSchemaProviderBean(){
		return new DefaultJsonSchemaProvider();
	}

Consider adding to the example. Leaving here for future people to find out.


Usage in Super Groups

Tried using the bot by adding it on a group yet it doesn't respond to any commands other than Private Chats
`

An exception was raised while handling an update
update = {
"update_id": 329041365,
"message": {
"chat": {
"id": -1001479127404,
"type": "supergroup",
"username": "daboyclub",
"title": "The Boy's🕺&💃Girl's Club"
},
"text": "/new@clubwaifubot",
"group_chat_created": false,
"entities": [
{
"length": 17,
"type": "bot_command",
"offset": 0
}
],
"new_chat_members": [],
"reply_to_message": {
"chat": {
"id": -1001479127404,
"type": "supergroup",
"username": "daboyclub",
"title": "The Boy's🕺&💃Girl's Club"
},
"group_chat_created": false,
"entities": [],
"new_chat_members": [],
"new_chat_photo": [],
"message_id": 53913,
"delete_chat_photo": false,
"caption_entities": [],
"date":<PHONE_NUMBER>,
"supergroup_chat_created": false,
"photo": [],
"channel_chat_created": false,
"from": {
"is_bot": false,
"username": "AaronOmoriChan",
"first_name": "Aaron",
"last_name": "Chan",
"id": 836019393,
"language_code": "en"
}
},
"new_chat_photo": [],
"message_id": 62391,
"delete_chat_photo": false,
"caption_entities": [],
"date":<PHONE_NUMBER>,
"supergroup_chat_created": false,
"photo": [],
"channel_chat_created": false,
"from": {
"is_bot": false,
"username": "AaronOmoriChan",
"first_name": "Aaron",
"last_name": "Chan",
"id": 836019393,
"language_code": "en"
}
}
}
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/telegram/ext/_application.py", line 945, in process_update
await coroutine
File "/usr/local/lib/python3.8/site-packages/telegram/ext/_handler.py", line 135, in handle_update
return await self.callback(update, context)
File "bot/bot.py", line 149, in new_dialog_handle
await update.message.reply_text(f"{chatgpt.CHAT_MODES[chat_mode]['welcome_message']}", parse_mode=ParseMode.HTML)
File "/usr/local/lib/python3.8/site-packages/telegram/_message.py", line 784, in reply_text
return await self.get_bot().send_message(
File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 238, in decorator
result = await func(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 637, in send_message
return await self._send_message(  # type: ignore[return-value]
File "/usr/local/lib/python3.8/site-packages/telegram/ext/_extbot.py", line 253, in _send_message
result = await super()._send_message(
File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 346, in _send_message
result = await self._post(
File "/usr/local/lib/python3.8/site-packages/telegram/_bot.py", line 310, in _post
return await request.post(
File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 160, in post
result = await self._request_wrapper(
File "/usr/local/lib/python3.8/site-packages/telegram/request/_baserequest.py", line 319, in _request_wrapper
raise BadRequest(message)
telegram.error.BadRequest: Replied message not found

`
The messaging worked for a while on the groupchat while I mentioned with the command on a particular Group

It's originally designed to be used in 1-to-1 chat, not in groups.


Upcoming changes to authorization starting May 1, 2020

Starting May 1, 2020 Bearer Tokens become mandatory.
Requests using only Client IDs will be dropped.
https://discuss.dev.twitch.tv/t/requiring-oauth-for-helix-twitch-api-endpoints/23916
I would appreciate a support for automatic requests of app access token, when no token is provided.

I'll take a look at this. Do you know any other packages that already follow a similar behavior?

I've filed draft, see #52

Looks good, I'll test the new feature.
Thanks.


Update README.md

add missing spacy install step

Thanks for contributing to Nesta's Skills Extractor Library 🙏!
If you have suggested changes to code anywhere outside of the ExtractSkills class, please consult the checklist below.
Checklist ✔🐍:

[ ] I have refactored my code out from notebooks/
[ ] I have checked the code runs
[ ] I have tested the code
[ ] I have run pre-commit and addressed any issues not automatically fixed
[ ] I have merged any new changes from dev
[ ] I have documented the code

[ ] Major functions have docstrings
[ ] Appropriate information has been added to READMEs

[ ] I have explained the feature in this PR or (better) in output/reports/
[ ] I have requested a code review

If you have suggested changes to documentation (and/or the ExtractSkills class), please ALSO consult the checklist below.
Documentation Checklist ✔📚:

[ ] I have run make html in docs
[ ] I have manually reviewed the docs/build/*.html files locally to ensure they have formatted correctly
[ ] I have pushed both relevant files AND their corresponding docs/build/*.html files

Thanks for this @ichbinakanksha - I'm going to close this since after the refactor it isn't needed.


Some more usage of the FetchApi

Also introduced a MockFetchApi to make testing easier.

Oh and one more thing. The default fetch api implementation does have protocol translation enabled now. Should I actually remove that one, even in this very PR, and instead explicitly add it in the client as suggested above?

@freben let's allocate some more time next week and discuss this a bit more in depth all of us x)


[Bug Report] pip mamujoco install error

Describe the bug
I tried installing the mamujoco environement and pip reports that the extra "mamujoco" is not provided by gymnasium-robotics
Code example
pip install gymnasium-robotics[mamujoco]
WARNING: gymnasium-robotics 1.2.0 does not provide the extra 'mamujoco'
System Info
Describe the characteristic of your environment:

gymnasium was installed with pip
OS Version: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Python 3.10

Additional context
Add any other context about the problem here.
Checklist

[x] I have checked that there is no similar issue in the repo

Hi! We haven't included mamujoco environments in the current 1.2.0 release. We are waiting to perform some evaluation test before making a new release. Other than that, the documentation has to also be updated and remove the custom dependency installation for mamujoco. In the future the dependencies will be included with a normal pip installation pip install gymnasium-robotics.
For now the environments have to be installed from source:
git clone https://github.com/Farama-Foundation/Gymnasium-Robotics.git
cd Gymnasium-Robotics
pip install -e.

I'll make a PR with a documentation update and leave this thread open until the next release is made.

@rodrigodelazcano close


Blog page can be improvised

What's the style idea?
We need to improve blog page like nav bar and ,categories and recent post.
and i would like to add more blogs in this.
can u assign this issue?
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSoC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@somaakash So many Issues are opened already regarding this work on them


Lombok Fails with Gradle v4.9 (working with Gradle v4.8)

The Lombok annotation processor  get build error with Gradle v4.9 after upgrading from Gradle v4.8, e.g.:

lombok.javac.apt.LombokProcessor could not be initialized. Lombok will not run during this compilation: java.lang.ClassCastException

I didn't find any comments in the 4.9 release notes, so it seems to me that the fault lies with some change between  Gradle 4.8.1 (also works) and Gradle 4.8
Expected Behaviour
A simple Java  build should work with Lombok (example below)
 gradle build

With simple Java compile.
This small Java program compiles and run without problems using Gradle v4.8.
Current Behaviour
Witth Gradle v4.9 working code fails with compilation errors after upgrading from Gradle v4.8:

lombok.javac.apt.LombokProcessor could not be initialized. Lombok will not run during this compilation: java.lang.ClassCastException

This Error using Lombok with Gradle from a Linux command line.  I rolled back my project to a stable version of: Monday (today being Friday).  The build still failed with Gradle 4.9.
Context
A small java build is sufficient (see below).
Everything is the same except the Gradle version, I backed out Gradle to Gradle v4.8 and ran the  build.
 gradle build

That  works!!

Steps to Reproduce (for bugs)
Sample  program
package app.cmd;

import lombok.extern.slf4j.Slf4j;
import org.apache.log4j.BasicConfigurator;
/**
 *  Main Class
 *
 *    - lombok trail
 *
 *  @author aplatypus
 */
@Slf4j
public class LombokExample
{

    /**
     *  Main
     *
     *  @param args the command line arguments
     */
    public static void main(String... args)
    {
        try
        {
            BasicConfigurator.configure();

            log.info("starting up");
        }
        catch( Exception  ex )
        {
            log.error("Exception within  runMain()... ", ex );
        }

    }

}//LombokExample main class

Your Environment
O/S name:       Linux
Gradle version: 4.9 .... Fail
Gradle version: 4.8 .... GOOD
Groovy version: 2.4.12
Java version:   1.8.0_172-b11 (vendor: Oracle Corporation)

Root project:   'root project 'foundation''
  JAVA_HOME   = '/usr/lib/java/jre/home'
  target...
    JRE_HOME  = '/usr/lib/java/jre/home'
    JDK_HOME  = '/usr/lib/java/jdk/home'

net.ltgt.apt = v0.17
Lombok       = v18.0

Duplicate of https://github.com/rzwitserloot/lombok/pull/1718


Am I supposed to fork dpc/crev-proofs repository to bootstrap crev?

Either way it should be mentioned in README of this repository (i.e. "fork this repository before cargo crev new id" or "don't fork this repository, create your own source").

I am not sure if we should modify proof repos README's automatically. In a sense it would be nice, but:

users give an existing repo url, which typically will have an autogenerated README.
we don't want accidentally overwrite user's README
what if we change anything in crev UI, and the instructions will become stale everywhere.

It asks an  "URL to a repository", not a "URL to an empty repository". I assumed that repository must be specially prepared.
Also if repositories are connected with fork/source relationship on Github, it may be easier to discover reviewers that just review things and don't advertise the fact explicitly.

I've got an idea. I'll auto-generate README_USING_THIS_REPO.md in every proof repo. See https://github.com/dpc/crev-proofs-test .

It asks "URL to a repository", not "URL to an empty repository". I assumed that repository must be specially prepared.

Every user is supposed to create an empty repository for themselves. But this is a good feedback. I'll see into wording of it.

Sorry, but I can't write down every single way new users can get confused about what to do. Most people will not read it anyway, and I am putting gitter link everywhere, so users can just ask for help.

https://github.com/dpc/crev/wiki/Proof-Repository

This link should be displayed by cargo crev new id, in "enter your username or URL" prompt.

c2b1c48f588ff7d0c0761eae1b7334db798aa021

I've published a new version on crates.io to help new users. Thanks!

I have started writing integration tests which create a new folder temporarily  using a crate called ephemeral I wrote for the same purpose. We can abstract it out or use it as part of a command so you can generate a project on the fly to test it.

Yeah, some integration tests would be great to have @Dylan-DPC . Let's move this to a different issue / discuss on gitter.


Error communicating with a desired service!

Description
The SP crashes while running a scenario.
Expected Behavior
Shouldn't crash
Logs:
scenario-player-run_ms1_simple_monitoring_2019-09-18T12:42:17.log

https://gist.github.com/palango/27de6fccecedafca282e2bcd4c56ab19

It looks like the JSONRPCCLient in raiden is doing some invalid concatenation:
File \"/Users/paul/Projects/brainbot/scenario-player/scenario_player/services/rpc/blueprints/tokens.py\", line 111, in deploy_token
    constructor_parameters=(1, decimals, name, symbol),\n  File \"/Users/paul/Projects/brainbot/scenario-player/venv/lib/python3.7/site-packages/raiden/network/rpc/client.py\", line 574, in deploy_single_contract\
   receipt = self.poll(transaction_hash)\n  File \"/Users/paul/Projects/brainbot/scenario-player/venv/lib/python3.7/site-packages/raiden/network/rpc/client.py\", line 663, in poll
    tx_receipt[\"blockNumber\"] + self.default_block_num_confirmations
TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'"}

After updating raiden this works now.


Problem of PV attachment with VM located in two differents zones

/kind bug
Hello
What happened?
We declare some Vm in the cloudgouv-eu-west-1a. We declare a StorageClass and installed the csi driver. It works well, PVC declare PV that was created on Outscale.
Recently, we declare a new VM but in the cloudgouv-eu-west-1b. But PVC still create PV on the zone A. Due to the system of label on node and nodeAffinity on pv, pv cannot be attached to the VM.
But this will not solve another issues, all our PV will be on the zone A so if we want some replication on different zone, it is currently impossible.
What you expected to happen?
PV created by a PVC are on the same zone as the node where the PVC is attached.
How to reproduce it (as minimally and precisely as possible)?

Deploy a cluster with worker on zone A
Configure the StorageClass and the CSI driver
Create PVC attached on a pod running on a VM in zone A
Add a VM located in zone B inside the cluster
Create PVC attached on a pod running on the VM located in zone B

Anything else we need to know?:
Environment

Kubernetes version (use kubectl version):
Client Version: v1.26.10
Kustomize Version: v4.5.7
Server Version: v1.24.8+rke2r1

Driver version:
annotations:
meta.helm.sh/release-name: osc-bsu-csi-driver
meta.helm.sh/release-namespace: kube-system
labels:
app.kubernetes.io/instance: osc-bsu-csi-driver
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: osc-bsu-csi-driver
app.kubernetes.io/version: v1.2.4
helm.sh/chart: osc-bsu-csi-driver-1.5.0

Hello
you need to ensure that PVCs are dynamically provisioned in the same zone as the VM (node) requesting the storage.
1- Use allowedTopologies in Your StorageClass:
You can configure your StorageClass to support provisioning PVs in different zones by defining topology constraints. This allows the storage to be provisioned in a zone that matches the requesting node. Specifically, adding allowedTopologies will ensure that the PV is provisioned in a specific zone that matches the zone of the pod.
2- Set volumeBindingMode to WaitForFirstConsumer:
Setting volumeBindingMode to WaitForFirstConsumer ensures that the PV is not created until a pod requests it. This means k8s will know which zone the pod is scheduled in, and it will then provision the volume in the appropriate zone.
Example:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: bsu-sc
provisioner: bsu.csi.outscale.com
volumeBindingMode: WaitForFirstConsumer
allowedTopologies:

matchLabelExpressions:

key: topology.bsu.csi.outscale.com/zone
values:
- cloudgouv-eu-west-1a
- cloudgouv-eu-west-1b
So,  if you list both zones (cloudgouv-eu-west-1a and cloudgouv-eu-west-1b) under allowedTopologies in your StorageClass and set the volumeBindingMode to WaitForFirstConsumer, Kubernetes will create the Persistent Volume (PV) in the same zone as the requesting pod.

Feel free to reach out if you still have any issues or need more help.

I will close this issue for now, feel free to reopen it if the problem is still remaining


[NEW] ASMO

Contact person name
Abril Azocar Guzman
Contact person email.
<EMAIL_ADDRESS>Overview in the README.md
Artifact name
Atomistic Simulation Methods Ontology
Overview
ASMO is an ontology that aims to define the concepts needed to describe commonly used atomic scale simulation methods.
Reach out
https://github.com/OCDO
What is your artifact prefix?
asmo
Where is the artifact located on the Web (i.e. the URL)?
https://raw.githubusercontent.com/OCDO/asmo/main/asmo.owl
Do you want to enable content negotiation?

[ ] enable content negotiation

artifact type
OWL

Hi, I need to change ASMO from https://purls.helmholtz-metadaten.de/mmss/asmo to https://purls.helmholtz-metadaten.de/asmo
see here
I can also make a PR with the proposed changes to the htaccess file, if that's better. Please let me know, thx!

Hi Abril, it should work now. Therefore, I will close this issue.

Thanks a lot!!


Re-add some APIs to MTRCertificates, but deprecate them.

Some of the 1.0-targeted API changes did not happen soon enough.

Not happening in this form, after the API revert.


Coverage

Changes Unknown when pulling 1a4ab0f48b1f0eb07d40102eedbf957512035df1 on coverage into ** on master**.

Changes Unknown when pulling cc22126c7269ec23296ef7c65d8f88a3c55b4fd2 on coverage into ** on master**.

Changes Unknown when pulling 69e574536ff38922ac382c1b50f7239884931841 on coverage into ** on master**.


chore: copy used code from @celo/utils into the repo and remove @celo/utils dependency

Description
The following functions were migrated from @celo/utils:
No Equivalents:

hexToBuffer from @celo/utils/lib/address
ensureLeading0x from @celo/utils/lib/address
normalizeAddress from @celo/utils/lib/address
normalizeAddressWith0x from @celo/utils/lib/address
stringToBoolean from @celo/utils/lib/parsing
parseInputAmount from @celo/utils/lib/parsing
AddressType from @celo/utils/lib/io
appendPath from @celo/utils/lib/string
getErrorMessage from @celo/utils/lib/displayFormatting
Encrypt from @celo/utils/lib/ecies (only used in KeychainWallet.test.ts)

Address functions

privateKeyToAddress from @celo/utils/lib/address
There is a direct equivalent privateKeyToAddress function in viem/accounts but previous implementation covered string argument both including and excluding 0x while viems alternative requires 0x to always be present. Created abstraction to use viems but ensuring the leading 0x.

privateKeyToPublicKey from @celo/utils/lib/address
There is a potential equivalent privateKeyToAccount function in viem/accounts which returns object with publicKey field but it doesn't match the results of existing function

isValidAddress from @celo/utils/lib/address
There is a direct equivalent isAddress function in viem but it doesn't consider uppercase addresses valid.
Created abstraction that will pass lowercased input to isAddress.

isValidChecksumAddress from @celo/utils/lib/address
This function was a re-export from @ethereumjs/util

Various functions

ValidatorKind from @celo/utils/lib/inputValidation
Already present at src/utils/inputValidation.ts as a copy-paste from @celo/phone-utils

EIP712TypedData from @celo/utils/lib/sign-typed-data-utils
There is a direct equivalent EIP712Domain type at viem/zksync but at places where the EIP712TypedData is used - it is dependant on other functions from @celo/wallet-base that accept only this type. Not migrating to viem equivalent for now.

sleep from @celo/utils/lib/async
Replaced with existing function from src/utils/sleep.ts

verifySignature from @celo/utils/lib/signatureUtils
Replaced with viem equivalent verifyMessage function

levenshteinDistance from @celo/utils/lib/levenshtein
Replaced with equivalent from fast-levenshtein

New dependencies:

@ethereumjs/util (used: 8.0.5, latest: 9.1.0)
@noble/ciphers ^0.6.0
@noble/curves ^1.5.0
@noble/hashes ^1.5.0

Test plan
Added existing tests from @celo/utils repo for the used functions
Related issues

Relates to RET-1187

Backwards compatibility
Yes
Network scalability
If a new NetworkId and/or Network are added in the future, the changes in this PR will:

[x] Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

@jeanregisser I'll address all the things in the follow-up PR!


Support parsing the Metadata field in html using the XML parser

We want to be able to parse HTML using the XML parse, this change will enable us to parse the meta table tags

There are a number of "void" elements in HTML which do not have a closing element. We should probably be able to handle them all alike:
https://html.spec.whatwg.org/multipage/syntax.html#void-elements

There are a number of "void" elements in HTML which do not have a closing element. We should probably be able to handle them all alike:

If we decide to go forward and support all HTML, let make this more tag agnostic. For now lets just support the "meta" tag


reference to ZPM gets lost during update in OEX

when I update a package in OEX I see
ZPM installation: zpm "install iris-internal-websocket-client"
status "on approval"
ONCE it is approved the pointer to ZPM is gone.
Except at the 1st approval.

Checked all my candidates. OK, Fixed


Intermittent hang / lock-up when remote host reboots or shuts down while connected

SpiritVNC will very infrequently become unresponsive / hang / lock-up when the remote host reboots or shuts down while still connected.  Seems to happen on both straight VNC as well as VNC-through-SSH.
This issue happens approx. one in fifteen sessions.

I'm thinking this is an issue with libvncserver or libvncclient at the WaitForMessage or HandleRFBServerMessage methods.  Still investigating.

Latest freeze backtrace
Program received signal SIGINT, Interrupt.
[Switching to Thread 805416000 (LWP 100763/spiritvnc-fltk)]
0x0000000802fe373a in _select () from /lib/libc.so.7
(gdb) bt full
#0  0x0000000802fe373a in _select () from /lib/libc.so.7
No symbol table info available.
#1  0x00000008008cd872 in pthread_suspend_all_np () from /lib/libthr.so.3
No symbol table info available.
#2  0x00000008021083e0 in WaitForMessage () from /usr/local/lib/libvncclient.so.0
No symbol table info available.
#3  0x000000080210805f in ReadFromRFBServer () from /usr/local/lib/libvncclient.so.0
No symbol table info available.
#4  0x00000008020fd9cd in HandleRFBServerMessage () from /usr/local/lib/libvncclient.so.0
No symbol table info available.
#5  0x0000000000431ad2 in VncObject::vncMessageTimer (vnc=0x807392a40) at src/vnc.cxx:306
        i = 1
        v = (VncObject *) 0x807392a40
        itm = (HostItem *) 0x80554f900
#6  0x0000000000434b78 in Fl::wait ()
No symbol table info available.
#7  0x0000000000434d93 in Fl::run ()
No symbol table info available.
#8  0x000000000042f38c in main (argc=1, argv=0x7fffffffe6c0) at src/spiritvnc.cxx:98
No locals.


No such filter: 'drawtext'

also mentioned here: https://github.com/jrottenberg/ffmpeg/pull/408#issuecomment-2447624435

Lets See
Trying to understand the scope of the issue:
Lets start peeking at the versions and understanding the issue.

ffmpeg versions: 7.1, 7.02, 6.1.2, and 5.1.6
Os flavors:

<ffmpeg-ver>-ubuntu2404
<ffmpeg-ver>-ubuntu2404-edge
<ffmpeg-ver>-vaapi2404
<ffmpeg-ver>-nvidia2404
<ffmpeg-ver>-alpine320
<ffmpeg-ver>-scratch320

Example run
This is the run that @Gwemox  did here: https://github.com/jrottenberg/ffmpeg/pull/408#issuecomment-2456482992

jrottenberg/ffmpeg:7.1-ubuntu2404

docker run --rm -v $(pwd):$(pwd) -w $(pwd) --platform="linux/amd64" jrottenberg/ffmpeg:7.1-ubuntu2404 -i sample-5s_1.mp4 -vf "drawtext=text='Stack Overflow':fontcolor=white:fontsize=24:box=1:boxcolor=black@0.5:boxborderw=5:x=(w-text_w)/2:y=(h-text_h)/2" outfile/sample-5s_1_with_text.mp4

...
[AVFilterGraph @ 0x555555600a80] No such filter: 'drawtext'
Error opening output files: Filter not found

drawtext is missing
docker run -it --rm --platform="linux/amd64" jrottenberg/ffmpeg:7.1-ubuntu2404 -filters |grep draw
 T.C drawbox           V->V       (null)
 ... drawgraph         V->V       (null)
 T.C drawgrid          V->V       (null)
 ... drawbox_vaapi     V->V       (null)
 ... adrawgraph        A->V       (null)

Summary of current problems

Image
Current state

jrottenberg/ffmpeg:7.1-ubuntu2404
Filter not found

jrottenberg/ffmpeg:7.1-ubuntu2404-edge
Filter not found

jrottenberg/ffmpeg:6.1.2-ubuntu2404
Filter not found

jrottenberg/ffmpeg:6.1.2-ubuntu2404-edge
Filter not found

jrottenberg/ffmpeg-7.1-nvidi2404
Cannot find a valid font for the family Sans

This issue comment is a work in progress and will be updated in the future.


Implement a method TryConvert and fix two tiny bugs

Implemented as suggested in https://github.com/Giorgi/DuckDB.NET/pull/114#issuecomment-1609293876

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 11 (90.91%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 86.423%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

DuckDB.NET/DuckDBNativeObjects.cs
10
11
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
763

Relevant Lines:
879

💛  - Coveralls


Fixed types of properties of contextual filtering mapped types

This is based on the contextualPropertyOfGenericMappedType test case - just with the added filtering .nameType

@typescript-bot test this
@typescript-bot test top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot test tsserver top100
@typescript-bot run dt
@typescript-bot perf test this
@typescript-bot pack this

This also makes me wonder if this is also a bug:
- const keysRemapped = !!target.declaration.nameType;
+ const keysRemapped = getMappedTypeNameTypeKind(target) === MappedTypeNameTypeKind.Remapping;

(Or maybe other places where nameType is used)


serviceAccount.create ignores serviceAccount.name

if you set
serviceAccount.create: true
serviceAccount.name: somename

it will ignore the set name and create a service account using
name: {{ template "nexus.fullname" . }}

Offending Code:
https://github.com/Oteemo/charts/blob/master/charts/sonatype-nexus/templates/serviceaccount.yaml#L5
https://github.com/Oteemo/charts/blob/master/charts/sonatype-nexus/templates/deployment-statefulset.yaml#L63

PR with suggested fix: https://github.com/Oteemo/charts/pull/156


How to use Cycle to loop a sound?

Sorry to add this as an issue, I did not find another way to ask. I'm adding audio support for notan and I am doing some research and tests with oddio.
I'll implement audio using oddio+symphonia, this combo does all that I need. I was just wondering how to use Cycle to repeat audio I tried to use it as a part of the AudioHandle type but without success, I am not sure how can I chain this type and how to control it later.
Any hint or example will be awesome. Thanks!

Use Cycle<Sample> just like you would FramesSignal<Sample>. Note that it's not a filter (so you can't wrap it around another signal), and it doesn't expose any controls.
If you still have trouble, please post exact code and errors.

Got it, it works like a charm! Thanks
I would like to ask you one last question, there is a way to check if a sound is stopped or paused without a mutable reference? I'm doing this using control, and while I don't have any issue with the method been mutable I think that it makes sense to be immutable if possible. But the control method is mutable.

oddio is designed to allow controllable signals to employ SPSC inter-thread communications, which allow various things to be much cheaper and simpler than they might otherwise be, particularly due to the requirement that the real-time audio thread never make a call that might yield control like an alloc, free, or mutex-guarded operation. There's no special case for exemptions to this pattern, but I'd be willing to review design proposals to handle this.

Alternatively, you could just put your handle inside a RefCell or similar.

As a side note, you could avoid a lot of redundant matching with a pattern like
impl AudioHandle {
    fn as_stop(&mut self) -> &mut Stop<dyn Any> { match self { ... } }
}

There's no special case for exemptions to this pattern, but I'd be willing to review design proposals to handle this.

I don't have enough expertise (as you can imagine with my simple questions) about how this lib works yet. So I don't feel qualified to do any change on it. But I have a lot of plans to keep extending the use of the oddio backend in my lib, like spatial emitters, or creating music/sounds with it, I hope to learn enough about oddio to be able to contribute it back soon.
I'll keep the mutable reference for now. Also thanks for your "side note" change made.
Btw, I would like to say thank you for your work. I'm also using hecs for a game. I checked quinn, and now oddio. Any crate that comes from you seems to be a high-quality work. And I learn a lot reading internals of them (even though sometimes I don't understand quite well how they do things).
Thank you so much for sharing.

No problem! I'm glad my libs have been helpful.


[Refactor] Extract JobInformation

Relates to #27846.
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 208 / 419 (49.64%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
0
2
00.00%
[841, 842]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
2
00.00%
[1534, 1535]

:large_blue_circle:
com/starrocks/common/Status.java
0
4
00.00%
[59, 63, 67, 101]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
0
1
00.00%
[640]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
7
00.00%
[170, 172, 173, 174, 175, 177, 179]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
3
16
18.75%
[243, 522, 543, 544, 612, 700, 741, 747, 748, 763, 848, 894, 1083]

:large_blue_circle:
com/starrocks/load/ExportJob.java
2
10
20.00%
[441, 442, 444, 460, 486, 487, 489, 800]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
42
91
46.15%
[212, 213, 215, 220, 221, 223, 228, 229, 238, 239, 240, 241, 242, 243, 245, 249, 259, 260, 264, 270, 271, 272, 274, 294, 319, 324, 364, 369, 432, 434, 435, 437, 439, 440, 443, 457, 472, 534, 713, 824, 1015, 1345, 1423, 1508, 1563, 1570, 1897, 2049, 2050]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobInformation.java
110
217
50.69%
[90, 92, 113, 121, 122, 141, 157, 161, 162, 177, 178, 220, 237, 239, 241, 242, 243, 244, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 262, 263, 264, 275, 276, 277, 279, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 304, 305, 306, 314, 315, 317, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 334, 335, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 359, 377, 378, 380, 381, 382, 383, 386, 387, 388, 389, 392, 394, 399, 400, 403, 404, 405, 406, 407, 410, 411, 412, 414, 447, 448]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
25
32
78.12%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
5
6
83.33%
[97]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
11
13
84.62%
[798, 1127]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 211 / 419 (50.36%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
0
2
00.00%
[841, 842]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
2
00.00%
[1534, 1535]

:large_blue_circle:
com/starrocks/common/Status.java
0
4
00.00%
[59, 63, 67, 101]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
0
1
00.00%
[640]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
7
00.00%
[170, 172, 173, 174, 175, 177, 179]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
3
16
18.75%
[243, 522, 543, 544, 612, 700, 741, 747, 748, 763, 848, 894, 1083]

:large_blue_circle:
com/starrocks/load/ExportJob.java
2
10
20.00%
[441, 442, 444, 460, 486, 487, 489, 800]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
44
91
48.35%
[212, 213, 215, 220, 221, 223, 228, 229, 238, 239, 240, 241, 242, 243, 245, 249, 259, 260, 264, 270, 271, 272, 274, 294, 319, 324, 364, 369, 432, 434, 435, 437, 439, 440, 443, 457, 472, 534, 713, 824, 1015, 1423, 1508, 1570, 1897, 2049, 2050]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobInformation.java
110
217
50.69%
[90, 92, 113, 121, 122, 141, 157, 161, 162, 177, 178, 220, 237, 239, 241, 242, 243, 244, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 262, 263, 264, 275, 276, 277, 279, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 304, 305, 306, 314, 315, 317, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 334, 335, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 359, 377, 378, 380, 381, 382, 383, 386, 387, 388, 389, 392, 394, 399, 400, 403, 404, 405, 406, 407, 410, 411, 412, 414, 447, 448]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
25
32
78.12%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
11
13
84.62%
[798, 1127]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 352 / 439 (80.18%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
0
1
00.00%
[841]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
1
00.00%
[1534]

:large_blue_circle:
com/starrocks/common/Status.java
0
4
00.00%
[59, 63, 67, 101]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
7
00.00%
[170, 172, 173, 174, 175, 177, 179]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/ExportJob.java
2
10
20.00%
[441, 442, 444, 460, 486, 487, 489, 800]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
4
19
21.05%
[424, 506, 522, 543, 544, 608, 612, 630, 718, 722, 741, 744, 747, 763, 1083]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
10
13
76.92%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
84
105
80.00%
[320, 325, 365, 374, 449, 451, 452, 454, 456, 457, 460, 474, 489, 551, 730, 841, 1032, 1440, 1536, 1598, 1925]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobInformation.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 353 / 439 (80.41%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
0
1
00.00%
[841]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
1
00.00%
[1534]

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
7
00.00%
[170, 172, 173, 174, 175, 177, 179]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/ExportJob.java
2
10
20.00%
[441, 442, 444, 460, 486, 487, 489, 800]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
4
19
21.05%
[424, 506, 522, 543, 544, 608, 612, 630, 718, 722, 741, 744, 747, 763, 1083]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
10
13
76.92%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
84
105
80.00%
[320, 325, 365, 374, 449, 451, 452, 454, 456, 457, 460, 474, 489, 551, 730, 841, 1032, 1440, 1536, 1598, 1925]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobInformation.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 353 / 441 (80.05%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
6
00.00%
[170, 173, 175, 177, 179, 181]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
1
19
05.26%
[424, 506, 522, 543, 544, 608, 612, 630, 718, 722, 733, 734, 735, 744, 747, 765, 1085, 1303]

:large_blue_circle:
com/starrocks/load/ExportJob.java
4
12
33.33%
[438, 445, 447, 462, 463, 489, 491, 802]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
1
2
50.00%
[845]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
3
66.67%
[1491]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
10
13
76.92%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
82
103
79.61%
[318, 323, 363, 372, 447, 449, 450, 452, 454, 455, 458, 472, 487, 549, 728, 839, 1030, 1438, 1534, 1596, 1923]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobSpec.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 353 / 441 (80.05%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
6
00.00%
[170, 173, 175, 177, 179, 181]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
1
19
05.26%
[424, 506, 522, 543, 544, 608, 612, 630, 718, 722, 733, 734, 735, 744, 747, 765, 1085, 1303]

:large_blue_circle:
com/starrocks/load/ExportJob.java
4
12
33.33%
[438, 445, 447, 462, 463, 489, 491, 802]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
1
2
50.00%
[845]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
3
66.67%
[1491]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
10
13
76.92%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
82
103
79.61%
[318, 323, 363, 372, 447, 449, 450, 452, 454, 455, 458, 472, 487, 549, 728, 839, 1030, 1438, 1534, 1596, 1923]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobSpec.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 343 / 422 (81.28%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
6
00.00%
[170, 173, 175, 177, 179, 181]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
8
00.00%
[80, 113, 117, 300, 339, 352, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
1
22
04.55%
[342, 423, 489, 505, 521, 529, 543, 607, 611, 612, 629, 717, 721, 733, 734, 735, 744, 747, 765, 1085, 1303]

:large_blue_circle:
com/starrocks/load/ExportJob.java
4
12
33.33%
[438, 445, 447, 462, 463, 489, 491, 802]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
1
2
50.00%
[845]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
3
66.67%
[1491]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
10
13
76.92%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/Coordinator.java
72
81
88.89%
[383, 453, 454, 458, 487, 843, 1485, 1684, 1924]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobSpec.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/ICoordinator.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/qe/CoordinatorMonitor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/loadv2/LoadJob.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 260 / 321 (81.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
5
00.00%
[170, 175, 177, 179, 181]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
4
00.00%
[80, 339, 356, 398]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
1
21
04.76%
[342, 423, 489, 505, 521, 529, 543, 607, 611, 612, 629, 717, 721, 733, 734, 735, 744, 747, 765, 1085]

:large_blue_circle:
com/starrocks/load/ExportJob.java
3
8
37.50%
[438, 445, 447, 489, 491]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
1
2
50.00%
[845]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
3
66.67%
[1491]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
8
11
72.73%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobSpec.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/QueryQueueManager.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 350 / 432 (81.02%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/Status.java
0
3
00.00%
[59, 63, 96]

:large_blue_circle:
com/starrocks/load/loadv2/LoadLoadingTask.java
0
7
00.00%
[168, 175, 176, 177, 179, 181, 183]

:large_blue_circle:
com/starrocks/task/ExportExportingTask.java
0
4
00.00%
[80, 339, 356, 398]

:large_blue_circle:
com/starrocks/load/ExportJob.java
1
6
16.67%
[436, 445, 447, 489, 491]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadTask.java
4
18
22.22%
[423, 505, 521, 542, 543, 607, 611, 629, 717, 721, 732, 733, 734, 1085]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadJob.java
1
2
50.00%
[845]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
4
50.00%
[1491, 1538]

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
8
11
72.73%
[813, 1127, 1907]

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
84
108
77.78%
[319, 324, 364, 373, 448, 450, 451, 453, 455, 456, 459, 473, 488, 550, 729, 840, 1031, 1070, 1439, 1535, 1597, 1622, 1660, 1924]

:large_blue_circle:
com/starrocks/qe/CoordinatorPreprocessor.java
26
33
78.79%
[181, 221, 225, 253, 296, 1126, 1133]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/JobSpec.java
205
217
94.47%
[253, 294, 331, 333, 354, 362, 363, 398, 402, 403, 418, 419]

:large_blue_circle:
com/starrocks/qe/QueryQueueManager.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/qe/NormalBackendSelector.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/mv/MVMaintenanceJob.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/qe/scheduler/Coordinator.java
5
5
100.00%
[]

@mergify backport branch-3.1


Sync v0.4.8 into master

Overview
Sync changes from v0.4.8 into master
Changes
See commits
Testing
N/A

Ugh forgot I should create a new branch, not use v0.4

Closed in favor of #1531


Add the compatible Redis version to the info command

Add redis_version into the info command
this closes https://github.com/apache/incubator-kvrocks/issues/1157

@PragmaTwice @ShooterIT Does it look good to you?

Thanks all, merging...


datadog_tracking_http_client requires http < 1.0.0

The datadog_tracking_http_client package has http package version ^0.13.5 as an explicit dependency.  Now that the Dart team have released 1.x versions of the http package, we get conflicts when using other packages (such as google_fonts) that have specified ^1.0.0 as the version.
Adding a dependency override to set http explicitly to ^1.0.0 seems to work OK.
Steps to reproduce the issue:
Create a project with both datadog_tracking_http_client 1.3.1 and google_fonts 5.1.0.
Describe what you expected:
A later version of datadog_tracking_http_client that works with http 1.x versions.
Additional context

Dart/Flutter version: 3.10.6

This is fixed and deployed as datadog_tracking_http_client 1.4.0


Update index.js

Spam?

Hey @raunaqkalra it'd be great if you can open or pick relevant issues from the issues tracker.


Fuse linear chains of subgraphs

Adds fuse_subgraphs, a function to fuse linear chains of non-fusable-with-fuse subgraphs together into a single task. The intention is that this is called somewhere in __dask_optimize__ after fuse.
It's currently a separate function because some collections (e.g. fusing getitem in dask array) have addtional steps after fuse that require access to the graph, and tasks wrapped in SubgraphCallable wouldn't be available to those optimization routines.
Fixes #3807.
Todo:

[ ] Figure out how to handle renaming keys
[x] Add tests for SubgraphCallable
[ ] Add tests for fuse_subgraphs

Benchmark
from timeit import default_timer

import pandas as pd
import dask.dataframe as dd
import dask

# Simple computation with many fast tasks to emphasize compute overhead.
df = pd.DataFrame({'x': range(10000)})
ddf = dd.from_pandas(df, npartitions=2000)

ddf = ddf.map_partitions(lambda x: x)
ddf['x'] = ddf['x'].astype('int8')
ddf = ddf.map_partitions(lambda x: x)
ddf['x'] = ddf['x'].astype('int8')

def bench(ddf, filename):
    n_before = len(ddf.dask)

    t1 = default_timer()
    (ddf2,) = dask.optimize(ddf)
    t2 = default_timer()

    n_after = len(ddf2.dask)

    # Optimize graph for a single partition and output to file
    ddf.get_partition(0).visualize(filename=filename, optimize_graph=True)

    t3 = default_timer()
    out = ddf2.compute(optimize=False)
    t4 = default_timer()

    print("ntasks: %d" % n_before)
    print("ntasks after optimization: %d" % n_after)
    print("optimization time: %.2f" % (t2 - t1))
    print("compute time: %.2f" % (t4 - t3))
    return out

print('Without fuse_subgraph')
print('---------------------')
with dask.config.set(fuse_ave_width=5):
    out1 = bench(ddf, 'baseline.png')

print('')
print('With fuse_subgraph')
print('------------------')
with dask.config.set(fuse_ave_width=5, fuse_subgraphs=True):
    out2 = bench(ddf, 'with-fuse-subgraph.png')

# Check equal results
pd.util.testing.assert_frame_equal(out1, out2)

Output
$ python bench.py
Without fuse_subgraph
---------------------
ntasks: 18000
ntasks after optimization: 12000
optimization time: 0.65
compute time: 4.51

With fuse_subgraph
------------------
ntasks: 18000
ntasks after optimization: 4000
optimization time: 0.70
compute time: 2.82

Graph of a single partition without fuse_subgraphs

Graph of a single partition with fuse_subgraphs

Analysis

The additional optimization step adds minimal overhead, but can substantially reduces the number of tasks.

The current fused task names from fuse_subgraphs results in some oddly named tasks (partly but not exclusively due to fusing keys that were created by a prior pass of fuse). I'm not sure what to do about this (if anything). This may (unsure) be better handled if this was a part of fuse, but then we'd need to make certain optimization routines (e.g. fuse_selections) traverse into SubgraphCallables as they process. Alternatively, we could potentially change the key-renamer to better handle these situations.

cc @mrocklin, @eriknw.

Cool!  I'll take a look and may add some tests.

cc @kkraus14 this should help with fusing long chains of dataframe operations together.

I would expect fuse_subgraphs to be able to fuse this graph into a single task, but it currently does not.

We don't currently fuse static data, but we could. If you replace 'a' with a task, then this fuses fine:
import dask
from dask.optimization import fuse, fuse_subgraphs
from dask.utils_test import inc

dsk = {
    'a': (inc, 2),
    'b': (sum, ['a', 'a']),
    'c': (sum, ['a', 'b']),
    'd': (sum, ['a', 'c']),
    'e': (sum, ['a', 'd']),
}

dsk2, deps = fuse(dsk, ['e'])
dsk3, _ = fuse_subgraphs(dsk2, ['e'])

dask.visualize(dsk3, filename='subgraphs.png')

Here is another graph that I think fuse_subgraphs should be able to fuse into a single task:

The algorithm and design implemented here cannot fuse this, but I'm not sure if that's bad. I'm not sure how common graphs like the above are, or how important fusing would be for them. In contrast, diamond patterns (which this fuses) are quite common in dask.dataframe or dask.array.
For the algorithm here, we take the following approach:

Use fuse with its myriad of tuning parameters to collapse together reducible tasks between non-reducible points.
Use fuse_subgraphs to find linear chains of these collapsed tasks to then collapse into a SubgraphCallable. This is nice because:

fuse_subgraphs only has to look for linear chains, which is cheap
fuse still fuses multiple tasks into a single task, which our downstream optimizations expect (e.g. fuse_slices). The approach in https://github.com/dask/dask/pull/1979#issuecomment-281230317 doesn't do this, making downstream optimizations that rely on fused tasks difficult.
We don't need to add more configuration parameters.
Having a two-step process means that we can apply the initial fuse, apply the other optimizations, and then apply fuse_subgraphs, without modifying any of that code.

I see a few options moving forward:

Keep things as is (two functions). This means we'd need to figure out how to improve naming the fused tasks, but everything else is good to go.

Put the existing algorithm in fuse, but don't change anything else. This means we can cleanup the naming, and do things a bit more efficiently. Downside is things like fuse_slices would need to traverse SubgraphCallable objects as well, which complicates things.

Do everything in a single pass within fuse. This would be the most difficult, but with lots of work and bookkeeping we could fuse things in a single pass, resulting in SubgraphCallable objects whose internal tasks are also fused using the existing subbing-in-tasks method (e.g. in the form that fuse_slices expects). This also has the same downside as 2, but could handle fusing more graph topologies (not sure how common/useful that is).

I'm not sure what's best here. Right now I'm more for 1 or 2, as I expect 3 to be fairly complicated (I may be wrong though). 2 might be best, because it keeps things open for 3. to happen sometime in terms of api.

I'm comfortable going with a two-pass approach, so we can move forward with option 1 from your previous post.  Thank you for your thoughtful analysis.
I'm still curious about writing this specific optimization algorithm in the style of the new fuse instead of the old fuse_linear.  I have begun to do this, and I think the algorithm will simplify nicely.  This shouldn't stop you from moving forward with this PR though.  And, yeah, key renaming is always annoying!

I found a way to fix the key renaming problem by optionally returning more information from fuse to be used later by fuse_subgraphs. After doing that though, I think from an api perspective that my option 2 as described above makes more sense. For dask array we'd need to cleanup two additional optimization passes, and same with dask bag, but I don't expect that to be too bad. On the plus side, I think we can be more efficient with respect to avoiding a bit of repeated work, and it leaves an opening for more efficiency improvements later on as seen fit.

Ok, new timings:
Current Master (no fuse by default)
-----------------------------------
ntasks: 18000
ntasks after optimization: 18000
optimization time: 0.35
compute time: 4.97

With fusion but no subgraph fusion
----------------------------------
ntasks: 18000
ntasks after optimization: 12000
optimization time: 0.79
compute time: 4.38

With fusion and subgraph fusion
-------------------------------
ntasks: 18000
ntasks after optimization: 4000
optimization time: 0.63
compute time: 2.81

One interesting thing above is that turning on fusion, but leaving subgraph fusion off is actually slower to optimize than just turning on both fusion & subgraph fusion. This is because with subgraph fusion we do fewer key renaming steps, as things are bundled into one application.
The most recent commit merges the subgraph fusion into fuse (written as an inplace subfunction, so as not to make fuse longer than it already is). I have another idea for how to speed things up even more (faster way to find linear chains given the work fuse already did), but first I'm going to add tests.

Seems like a nice win :)

Ok, this is ready for review. I'm pretty sure there's ways to speed up the algorithm, but overall I'm happy with the current performance. The most recent numbers posted above are still accurate.
A few questions:

[ ] Should the default settings for fuse be changed in dask.dataframe.optimize? I think we can change the ave_width to 1 and make fuse_subgraphs True by default, but it would be good to benchmark average code first. In all my trials things are ~equal/slightly faster with this PR, but I may have missed some edge cases.
[ ] Should fuse look for fuse_subgraphs in config internally, as the other parameters do?
[ ] Should we turn this on for any of the other collections? Doing so will require some modification to other optimization passes (e.g. optimize_slices), but may also be useful.

A few more notes:

Turning on fuse_subgraphs now passes for all collections, but certain optimizations (e.g. optimize_slices) won't be applied inside any fused subgraphs. Fixing that would require changing those optimization passes to also traverse subgraphs.
fuse_subgraphs is most effective when there are "diamond-pattern" subgraphs where each subgraph is successfully fused by fuse. This happens more for larger values of fuse_ave_width. For dask dataframe, a value of 1 or 2 seems to catch some cases, for dask.array larger values seem necessary to really have a large effect. This of course depends on what computations you're doing.
After doing a few benchmarks for dask dataframe, the effectiveness of this optimization is situation dependent. At worst a setting of fuse_ave_width=1, fuse_subgraphs=True results in a mild slowdown of optimization time. At best it results in some level of speedup. The effect of this speedup can be more noticeable in a distributed environment where serializing intermediate values may occur.

Given the above, my current thoughts are to:

Leave this optimization off by default for dask.array and dask.bag.
Maybe modify optimize_slices and other passes to allow traversing subgraphs. I think atop fusion (#3998) will be more effective for dask.array, but dask.bag would most likely get some speedups from this pass. I think I'd prefer to add support for other collections in subsequent PRs.
Maybe modify the default values for dask.dataframe to something like fuse_ave_width=1, fuse_subgraphs=True (or even fuse_ave_width=2). My benchmarks show a slowdown in the us - ms in optimization time, but the compute speedup can be much larger for non-negligible compute (depending on graph topology).

What is the difference between 0 and 1? Naively I'm sort of assuming that these are the same.

0 means don't fuse at all. I believe this was chosen for dask.dataframe as your benchmarks found that fusing dataframes wasn't worth it. The other collections use the global default of 1.

Maybe modify the default values for dask.dataframe to something like fuse_ave_width=1, fuse_subgraphs=True (or even fuse_ave_width=2)

I've forgotten most of the configuraiton around fuse_ave_width. I notice that the current default value is 0. What is the difference between 0 and 1? Naively I'm sort of assuming that these are the same.

fuse_ave_width of 0 disables fusing (there's a hot path for this).  1 fuses linear chains.

In the latest commit I've:

Turned on subgraph fusion by default for dask dataframe
Changed the default ave_width back to the global default of 1.

I think the latter should definitely be done, but the former I'm not 100% set on.

Ok, this took some time to track down, but I've diagnosed the error on travis. This is a periodic error, but it points out a real issue that existed before this PR, but wasn't triggered due to less rigorous optimization:
We're seeing "ValueError: seek of closed file" in the set_index tests. The reason for this is two-fold:

Optimization differs between collections. The set_index code mixes delayed and dataframe objects, and passes both to compute. The dataframe objects are fused, while the delayed objects are not. This results in some tasks (specifically the reads) being fused together and done twice.

The OpenFile contextmanagers are generally unsafe in the presence of threads (the stateful contextmanager doesn't play well if __enter__ and __exit__ blocks interleave. I think for read_bytes at least these should be reworked to a more functional model.

For this specific issue, I think the read_bytes code can be refactored to avoid this. However, the "optimizations can result in duplicate work" issue still stands, and perhaps indicates that our default settings should be more minimal (i.e. keep fuse_subgraphs off by default). cc @mrocklin for thoughts.

I was sort of aware of the OpenFile issue, and have used copy.copy() in some places to make sure it doesn't happen (the objects are small and simple).

The latest commit does two things:

Is more precise with when and how optimizations are applied in set_index, preventing duplicate work being done even in the presence of fusing. A test is added for this. There may be other points where this is needed as well, not sure.
Adds a cheap copy operation in read_bytes, to ensure consistent threadsafe behavior. Ideally situations where this is necessary would never arise (since it means duplicate work is being done), but those objects really should be threadsafe anyway.

@TomAugspurger, not sure if you saw this PR, but comment sort of reminds me of the incremental use case in particular. Might be a useful optimization to explore in that context.


hat and cap blocks should start a new stack

This is not clear from the grammer, but should be handled by the visitor.

already works for define blocks in the current version on develop & gh-pages

To methods are related to this

visitor.interruptStack(); Indicates the previous start has ended, should be called before creating a hat block xml, after cap block xml.
´visitor.startStack();` before building the new stack, after creation of the hat block xml. This will be called by the stack(ctx) method when the stack was interrupted.


Fixed broken couchbase-cluster link

the link for couchbase-cluster was pointing to load-balancer

The test is failing due to the fact that our test account has multiple hosted zones with the same domain name. Fix is here: https://github.com/gruntwork-io/terraform-aws-couchbase/pull/31

OK, #31 is merged. Please rebase and feel free to merge this PR in too!


Is support for higher unity versions coming?

A few days ago I ran into a problem where AssetStudio could not properly parse MB files of a game which was made with Unity version 2022.2.12
The game is called "I am Dave", and it's free to download and play so just in case you want to take a look, below is the link to the game.
https://dnsatan.itch.io/i-am-dave
With that said, I was wondering if support for higher unity versions, such as 2022.2, are coming/planned/being considered in the future.
Or will the support versions permanently be fixed to 3.4 - 2022.1, as is at the moment?

Hi
Sadly, most likely the last one
I can't continue Perfare's work and keep AssetStudio up to date or fix some internal bugs
I just lack of knowledge to do that
This fork is mainly focused on UI modifications and functionality enhancements
Of course, there's a small chance that someone will make a PR that adds support for new Unity versions.. or maybe I'll find a solution somewhere on github one day..
But yeah, you shouldn't expect support for higher unity versions from this fork
There are other programs that can work with new Unity versions, such as AssetRipper, UABEA,..
You can try them

Fully understandable- but I thank you very much anyways for updating AssetStudio and maintaining it even to this point. I've been able to load a lot of games without errors in your fork of AssetStudio, unlike how they popped up 50 error windows in the original AS and it was such a tedious labor just to try and load one game by closing those error windows everytime they pop up.
As for other programs, I am already using UABEA very well. It's just that AssetStudio is kind of the beginnig point of my workflow. I usually try to understand the general approach I should be taking by looking in AS, then work with UABEA for working with specific assets/files :)

@enarkay


fix: updateUserAttributeSetting during add/update/push flows

Description of changes

adds attr during amplify add / amplify update flows
adds this attr during amplify pull / push / build workflow
for console and studio builds , this will work fine as contents are pushed with force
for cli Cx , if Cx doesn't update the auth category , it needs a force push to update the userPool with this attribute.

Issue #10561

Description of how you validated changes

updated unit tests
Manually tested

Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

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

Closing in favour of #10773


URIs of SO properties do not resolve

For example:
has_part -> http://purl.obolibrary.org/obo/so-xp.obo#has_part does not resolve
Moreover, the SO classes use different (and shorter) URI path to resolve e.g.,
SO:0000704 (gene) -> http://purl.obolibrary.org/obo/SO_0000704
Using the @prefix obo: http://purl.obolibrary.org/obo/ one would like to do the following:
obo:SO_has_part
obo:SO_0000704
OR
so:has_part
so:0000704
using @prefix so: http://purl.obolibrary.org/obo/so.owl#

We should use RO URIs such as http://purl.obolibrary.org/obo/BFO_0000051

Thank you so much for replying back, am I asking too much if I ask for your
assistance with this? I will try on my own first and if I run into a
problem...(which I will) is okay for me to email you back?
On Thu, Aug 11, 2016 at 10:02 AM, Chris Mungall<EMAIL_ADDRESS>wrote:

We should use RO URIs such as http://purl.obolibrary.org/obo/BFO_0000051
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/367#issuecomment-239169800,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT6dbkgQjn5sAtho3yScyesNv8SgpnOYks5qeytngaJpZM4Jf2nm
.

You can email me but I prefer to keep on the tracker.
Note that I would argue the fix should be made upstream in SO itself. But you can make a local copy and fix it yourself by searching and replacing on IRIs.
You can find more such relations in the OBO Relations Ontology. See also the sequence branch of RO visualized within OLS

That is fine by me. I could be wrong but I can't tell the difference
between the two.
On Thu, Aug 11, 2016 at 1:53 PM, Chris Mungall<EMAIL_ADDRESS>wrote:

You can email me but I prefer to keep on the tracker.
Note that I would argue the fix should be made upstream in SO itself. But
you can make a local copy and fix it yourself by searching and replacing on
IRIs.
You can find more such relations in the OBO Relations Ontology
https://github.com/oborel/obo-relations. See also the sequence branch
of RO visualized within OLS
http://www.ebi.ac.uk/ols/ontologies/ro/properties?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FRO_0002514
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/367#issuecomment-239238323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT6dbqUV0lvHPdqaldWWZyho4yWl1rOOks5qe2GCgaJpZM4Jf2nm
.

Thank you, Chris for taking care of this one. It looks like you have answered the questions. Feel free to reopen this if you have any more questions.
Thanks,
Dave Sant


Proposed Change: *.pylit

Docbuilder is only really appropriate for Literate-Style programs.
CoffeeScript accomplishes this by only parsing files with the .coffeelit extension.
A similar .pylit extension would also make sense, and wouldn't break python functionality as it stands.

Using a *.pylit extension may be confusing for some users, particularly Windows users, however it offers an easy way for:

Python Literates to be seperated logically from other projects that may exist within
Bash scripting (e.g. docbuilder.py *.pylit *.md -d docs)

As it may or may not end up breaking some compatibility, it has been delayed until 1.0.

Adopted.


Fix some warnings & deprecations on 0.6

Hi Joel!
I was looking for a way to write a MIDI file from Julia and found your package – great work, and it'll save me some time. :-)
I just went through and fixed some things so that they run on the latest Julia (0.6) without warnings. Let me know if this looks good to you, or if any additional changes are needed.

Hi Yuri!
Glad it's useful to you. I'm happy to merge it in once the CI build passes.

Ah, looks like I broke it on 0.5. I think this is what Compat (https://github.com/JuliaLang/Compat.jl) is for... I can look into it if you'd like to keep 0.5 compatibility.

@Datseris Do you have any thoughts? I haven't done anything with Julia in some time, so I think you might be better able to answer this question.

That last commit should address the issue. I just tested it locally on 0.5 on OS X and all tests pass:

Do you know how to restart the CI build? It seems that build #89 should have picked up the changes but didn't?

Last commit looks good, although it looks like the build is failing again.
ERROR: LoadError: LoadError: LoadError: syntax: invalid type signature
 in include_from_node1(::String) at ./loading.jl:488 (repeats 2 times)
 in eval(::Module, ::Any) at ./boot.jl:234
 in require(::Symbol) at ./loading.jl:415
 in include_from_node1(::String) at ./loading.jl:488
 in process_options(::Base.JLOptions) at ./client.jl:265
 in _start() at ./client.jl:321
while loading /home/travis/.julia/v0.5/MIDI/src/trackevent.jl, in expression starting on line 3
while loading /home/travis/.julia/v0.5/MIDI/src/MIDI.jl, in expression starting on line 6
while loading /home/travis/.julia/v0.5/MIDI/test/runtests.jl, in expression starting on line 1

I guess it doesn't like compat. I wonder if the travis.yml file needs to be updated with something? Sorry I can't be of more help.

So weird; it looks like it now passes on macOS but not Linux?

Hi Yurivish. Happy that the package has helped you like it has helped me as well :D
First things first: My humble opinion is that there is no reason to support 0.5. In fact, I see no reason to support any older version of Julia prior to 1.0. We don't want to have the same story as Python, do we? But this is just my opinion... In the packages I have develop I Do not support older versions and this saves a lot of unecessary complications.
I say unecessary because 0.6 is stricktly superiod to 0.5. There is no reason to still be using 0.5 besides "I am too bored to change"...
Now, I am curious about something: Why aren't the appveyor tests initialized? Hm.. I added a AppVeyor config file long ago. I recall that the 32-bit tests weren't passing. But we left it there in case there is any Windows 32-bit user that will ever use the package.
Seems like all failing builds are due to 0.5. I vote to drop support :D @JoelHobson it is your call now.

I updated the branch based on @Datseris' latest comment – Compat is gone, dropping support for Julia 0.5; any 0.5 failures are now to be expected. :-)

@yurivish Looks good. I dropped support for v0.5 in the main branch. Can you merge that into yours and push it again? That should get the build to complete this time.

@JoelHobson Done. Not sure why the OS X build isn't starting – it's been in limbo for a half-hour or so.

@yurivish OS X builds freeze many times on Travis. Sometimes they may take hours to start... :D So do not worry.
But everything passed now. @JoelHobson I will leave the merge of this one to you to be sure that we have both seen the changes. (I approve of course).

Thanks!

@yurivish @Datseris Done!


Changes required on each apply

Hi - This module is great, but each time I run terraform apply it looks like it wants to set and then remove a certificate - just wondering if you know why?
viewer_certificate.111111111.cloudfront_default_certificate: "" => "true"
viewer_certificate.111111111.iam_certificate_id:             "" => ""
viewer_certificate.111111111.minimum_protocol_version:       "" => "TLSv1"
viewer_certificate.111111111.ssl_support_method:             "" => "sni-only"
viewer_certificate.222222222.acm_certificate_arn:             "arn:aws:acm:us-east-1:12121212:certificate/1111111-222222-3333-4444-4444" => ""
viewer_certificate.222222222.cloudfront_default_certificate:  "false" => "false"
viewer_certificate.222222222.iam_certificate_id:              "" => ""
viewer_certificate.222222222.minimum_protocol_version:        "TLSv1" => ""
viewer_certificate.222222222.ssl_support_method:              "sni-only" => ""```

In my experience, I've seen this happen if the format of your ARN doesn't match the normalized version that AWS or Terraform uses. Can you share the complete plan?

I have a website module that I use to create a prod, staging and dev version of the a static website.
This website module calls the terraform-aws-cloudfront-s3-cdn module 3 times, once for each environment.
website.tf file:
data "aws_acm_certificate" "my_domain_com" {
  domain   = "*.my_domain.com"
  statuses = ["ISSUED"]
}

module "frog_website" {
  source              = "../modules/website"
  subdomain           = "frog"
  domain              = "my_domain.com"
  acm_certificate_arn = "${data.aws_acm_certificate.my_domain_com.arn}"
}

website module:
locals {
  name         = "${var.subdomain}.${var.domain}"
  prod_fqdn    = "${local.name}"
  staging_fqdn = "${var.subdomain}-staging.${var.domain}"
  dev_fqdn     = "${var.subdomain}-test.${var.domain}"
}

module "development_website" {
  source              = "git::https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn.git?ref=master"
  namespace           = "my-name-space"
  stage               = "dev"
  name                = "${local.name}"
  aliases             = ["${local.dev_fqdn}"]
  parent_zone_name    = "${var.domain}"
  acm_certificate_arn = "${var.acm_certificate_arn}"
}

module "staging_website" { .......
# same as above
}

module "production_website" { .......
# same as above
}

Yes, that looks good so far.
One thing to note: this could return random arns if you have more than one cert issued for *.my_domain.com. It is possible to have multiple certs issued for same domain. Have you confirmed you have exactly one?
data "aws_acm_certificate" "my_domain_com" {
  domain   = "*.my_domain.com"
  statuses = ["ISSUED"]
}

Thanks - you're correct we have multiple certs for that domain, but in different region.
However I'm sure the identifier I saw (for the certificate) when running terraform plan was the same. I'll have to test and see.

OK - I've confirmed, the certificate ARNs are the same, I solved this problem by doing this:
For the cloudfront_default_certificate parameter the Terraform documentation says

Specify this, acm_certificate_arn, or iam_certificate_id.

Which I presume means you can only specify one and not both together.

Oh - just found this: https://www.terraform.io/docs/configuration/interpolation.html#conditionals

#9 for review - could you do a merge/squash please.

That's great! Thanks for submitting the PR. Makes sense. I'll have @aknysh review and if it looks good, merge & tag a new release.

@cliveza
we merged your changes
https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/releases/tag/0.1.5
thanks again for the contribution


allow keyboard shortcut creation for 1) copying last command and 2) copying last command and its output

There should be a way to add keyboard shortcuts for

copying the last command
copying the last command's output (this already exists), and
copying the last command and its output.

I'm not sure if this was what https://github.com/microsoft/vscode/issues/178154 was getting at.

Current behavior
There's a way to create a keyboard shortcut for getting the last command's output, but not a way to get the last command, or the last command with its output.

cc @meganrogge @Tyriar likely the best for this

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I'm actually not sure if this is a bug-fix or a feature.
Were the

copy last terminal command and
copy last terminal command and its output

VSCode commands supposed to be keyboard-shortcut-mappable from the start, or was it always the intention to optionally add shortcuts for these VSCode commands later?


Worked unexpected in go rountine?

Wrote some test codes but got fatal error
	bt := btree.New(32)
	var wg sync.WaitGroup
	//var lock sync.Mutex
	for i:=1;i<10000;i++ {
		wg.Add(1)
		go func(n int) {
			//lock.Lock()
			bt.ReplaceOrInsert(btree.Int(n))
			bt.Delete(btree.Int(n))
			//lock.Unlock()
			wg.Done()
		}(i)
	}
	wg.Wait()
	t.Log(bt.Len())
	bt.Clear(true)

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5264b1]
goroutine 94 [running]:
github.com/google/btree.items.find(0xc000050010, 0x1, 0x1, 0x7a6820, 0xc00008e1e0, 0x0, 0x0)
/mnt/d/develop/go/pkg/mod/github.com/google/btree@v1.0.0/btree.go:191 +0xc1

Well i see it's threadunsafe


dockerclient: fix COPYing an archive to a new location

When COPYing an archive to a location which doesn't exist, don't force the destination to be treated as a directory that we might have to create.  We have to do that for ADD in order to be able to extract the archive's contents, but not for COPY.
Document that the Decompress field from dockerclient.CopyInfo is both never set and ignored.
Should fix #230.

/lgtm


How to get additional parameter when i use RESTFul Api

I follow this (http://jasig.github.io/cas/development/protocol/REST-Protocol.html) tutorial done, and all through. But I would like to submit additional arguments, and save the parameters submitted to a user table.(Because I see this "POST / cas / v1 / tickets HTTP / 1.0 username = battags & password = password & additionalParam1 = paramvalue ")
I want to save the mobile device ID, and do push notifications with MQTT.
We hope to get everyone's help
THX!

Please use the CAS mailing lists for any questions: http://jasig.github.io/cas/Mailing-Lists.html. Thanks.


Create predefined design-time roles for BPM

Environment

Platform version: 7.2-SNAPSHOT
Related issue: https://github.com/cuba-platform/cuba/issues/2172

Description of the bug or enhancement
Create two roles:

First Role should allow user to manage bpm processes. All screens should be available.
Second Role should allow user to work with processes tasks assigned for this user

Roles will appear in the project after adding BPM add-on to the project.

Two roles added:

bpm-process-admin - gives access to all BPM screens and entities
bpm-process-actor - gives access to BPM entities that is required to start the process and complete tasks. Process tasks screen is not available, if it is required then it must be added by another role.

QA: you can test roles using the https://github.com/cuba-labs/bpm-samples sample. It was migrated to CUBA 7.2-SNAPSHOT


Integrate metrics into the dashboard

[x] Create a daemon plugin that uses the lustre collector to read filesystem metrics
[x] Inject lustre metric output into influxdb

Integrate metrics into dashboard charts:
Filesystem View:

[ ] Read/Write Heatmap
[ ] OST Balance

This is a series based chart and requires the data to be stacked. Unfortunately, grafana does not support rendering data in this way at this time. I'm putting this off until we can discuss a solution.

[ ] Metadata Operations
[ ] Read/Write Bandwidth
[x] File Usage
[x] Space Usage
[ ] Metadata Servers

needs data

[ ] Object Storage Servers (needs data)

needs data

Filesystem Target View (MDT):

[x] Metadata Operations
[x] File Usage
[x] Space Usage

Filesystem Target View (OST):

[x] Read/Write Bandwidth
[x] Object Usage
[x] Space Usage

MDS View:

[ ] Read/Write Bandwidth
[ ] CPU Usage

needs data

[ ] Memory Usage

needs data

OSS View:

[ ] Read/Write Bandwidth
[ ] CPU Usage

needs data

[ ] Memory Usage

needs data


Staging to main: New Release 1.1.0

Description

Related Issues

Checklist:

[x] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[x] I have updated the documentation accordingly.
[ ] This PR is being made to staging branch and not to main branch.

docstrings are failing: https://readthedocs.org/projects/microsoft-recommenders/builds/ I can check tomorrow

Codecov Report

Merging #1687 (82a4d34) into main (6987858) will increase coverage by 23.19%.
The diff coverage is 100.00%.

:exclamation: Current head 82a4d34 differs from pull request most recent head 8e632dd. Consider uploading reports for the commit 8e632dd to get more accurate results

@@            Coverage Diff             @@
##            main    #1687       +/-   ##
==========================================
+ Coverage   0.00%   23.19%   +23.19%
==========================================
  Files         88       88
  Lines       9120     9120
==========================================
+ Hits           0     2115     +2115
- Misses         0     7005     +7005

Flag
Coverage Δ

nightly
?

pr-gate
23.19% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

recommenders/__init__.py
100.00% <100.00%> (+100.00%)
:arrow_up:

recommenders/datasets/mind.py
0.00% <0.00%> (ø)

recommenders/datasets/movielens.py
66.37% <0.00%> (+66.37%)
:arrow_up:

recommenders/datasets/download_utils.py
90.00% <0.00%> (+90.00%)
:arrow_up:

recommenders/models/newsrec/io/mind_iterator.py
0.00% <0.00%> (ø)

recommenders/models/newsrec/models/base_model.py
0.00% <0.00%> (ø)

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 6987858...8e632dd. Read the comment docs.


Support of different policies per project

Hi, I initially read the Policies documentation as meaning that you could supply a policies.yml as a file in the root of the codebase being scanned, after some experimenting and then re-reading I realised that policies.yml is globally applied.
It would be useful to be able to either pass the policies.yml along with the project to be scanned.
Or support having multiple policy files that the server knows about (probably specified based on outgoing license), and allow specifying which one applies for the project.
This is to allow for the use case where an organisation has multiple types of project which are distributed under different licenses where a single blanket policy will not work.
The first option is likely easiest to manage and would allow small teams to manage the policy checking for their project as and when they come across new licences.
The 2nd option would allow the organisation to centrally manage the policy and would allow it to be pre-populated so that new projects get the benefit without having to create the files from the start.
An expanded approach might be to combine those so that there is both an ability to select the outgoing license, or provide a project specific policy file. Pehaps the policy file could be provided in the file hierarchy such that the policy applies to files that are in the same folder or below and are overridden by policy files below them.
Paul

This is to allow for the use case where an organisation has multiple types of project which are distributed under different licenses where a single blanket policy will not work.

This makes perfect sense. In particular it would be typical to have a very different policy for a web-based, externally facing app, an embedded device firmware, a mobile app, some desktop app, or some internally used app.

An expanded approach might be to combine those so that there is both an ability to select the outgoing license, or provide a project specific policy file. Pehaps the policy file could be provided in the file hierarchy such that the policy applies to files that are in the same folder or below and are overridden by policy files below them.

I like the idea. We could likely expand it not only to license policies but also to other scan settings, I am thinking about for instance skipping some directories or files entirely or pointing to some pre-concluded definitive license determination that would override scanning... and the ability to optionally ignore this entirely and/or applying another policy not stored in the code.
Let's work out the design here!

Agree,
Could supply .scan_ignorefiles using the .gitignore format
Aboutfiles could be treated like a 'concluded license'
So my thinking in python inspired pseudocode
# default license policy read from existing policies
proj_policy = server_policy

# select a policy from pre-configured policy per outgoing license
....
if proj_outgoing_license is not None
    if proj_outgoing_license in license_policies:
        proj_policy = license_policies
    else
       alert user chose license not handled

for each folder in folders:
    file_policy = proj_policy
    local_policy_file = find_nearest_policy(folder)
    if local_policy_file is not None:
        file_policy = local_policy_file
    for each file in folder
        apply_policy(file,file_policy)

If we prescanned the tree to locate policy.yml files then sort it by length then the policy.yml to apply would be the one that has the longest string match with the folder path

We are slowly and surely implementing parts to support this:

We now support scancode_config.yml file that can be added to the scan inputs (or in the new project settings) to selectively ignore some files
In one of the pipelines (the new/WIP deploy_to_devel), we have a new pipe/step that uses ABOUT files for origin and license as some curation file

We should add policy to this next.

Right, we now have the structure in place to implement per-project policies.

Support for project-specific license policies and compliance alerts added in https://github.com/aboutcode-org/scancode.io/pull/1440
See https://scancodeio.readthedocs.io/en/latest/policies.html and https://scancodeio.readthedocs.io/en/latest/tutorial_license_policies.html


setOptions - homeDomain is empty string instead of None type after clear it.

Description
When typing something in Input block then clear it. After submit that field It's change to empty string instead of None type.
If I would like to change to None after type something. I have to refresh a page or create new operation and remove the old operation.
Expected behavior

After clear input field it should be None type.
Add some button to set None type. same as Memo.

Step to reproduce

Create operation type set_options
typing something in field Home Domain
clear all text in that field

In the following example for None type and empty string.
None type
AAAAALpDZVagspfAMfLgaw/esPlpWUf5zy+WM1bLWkvgm7S1AAAAZACOL/AAAAAEAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Empty string
AAAAALpDZVagspfAMfLgaw/esPlpWUf5zy+WM1bLWkvgm7S1AAAAZACOL/AAAAAEAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAA

Thanks for the description @obbaeiei , I was able to reproduce.


Indicator for ability duration

There should be something to show that an active ability has stopped taking effect while recharging.

Resolved via commit 879c31915f32a0b1e80fe2b124c0b1005b65115a.


added event hooks before and after koa routes have loaded

I don't have the required access to merge this PR.


Scraping with authentication

Use this

Hmm... it's difficult for me (basic authentication fails, should I use headless browser?)


List documentation

Some commits from #30 were changed, therefore, the only additions are in the file List.sim and Number.sim. The List module has been documented thoroughly, more blocks will be added as we progress..

Yeah. That would be the right way

It can be tough handling a lot of things 😂. I'll just close this PR and
fix my remote repo. Btw, your Map module seems to be buggy, have you tested
it lately ?
On Sep 16, 2018 10:44, "Steve Akinyemi"<EMAIL_ADDRESS>wrote:

Yeah. That would be the right way
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/simple-lang/simple/pull/32#issuecomment-421733492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Adkrj8ImLnn4hH8UDarzwjjbjIP69Hfpks5ubh1rgaJpZM4Wqkic
.


chore: Add changelog for new 4.0.0 release

New version 4.0.0 has been released
📝 You can modify the changelog template online here
Jira issues
See all Jira issues for 4.0.0 version

I'm not able to know if features are missing or not and I didn"t follow the potential Breaking Changes applied on AM so I can't jugde this PR but should we create a CHANGELOG-v4.adoc ? Maybe not now as I don't know the impact specially on the documentation side but maybe something to improve before the next 4.x release. thinking

Agree, I just decide to not do the move now as it need a dedicated task regarding the impact (documentation, automation process update). Same for the documentation part.


Remove Sprinkles from display updates

Fix a random issue where occasionally invalid data flashes on screen due to the DMA timing mismatch

Simplified logic for DMA Ack check at end of line and removed unused variable.


Fix for #557: check BTC/PTS addresses on balance import

This patch simple makes the cli_wallet check sharedrop addresses based on BTC/PTS keys in addition to BTS addresses.

Looks good.  I've created a branch corresponding to the issue number, and will merge it from there, so I'm going to close this.  (Additionally, I squashed these two commits into a single one.)


Expose Section from CustomUI

@sebjulliand How do you think we should go about doing this? Just another export on CodeForIBMi?

Is it necessary though, since CustomUI extends Section?


num_samples arg in runner_af2advanced.py should be int

At line 46, it should be:
parser.add_argument("--num_samples", default=1, type=int, help="number of random_seeds to try. Default is 1.")

Thanks, @maxbonomi. I added it!


Second learning rate

After 1 epoch, learning rate was set to 0.000006.
How do I fix it?

I don't know the reason why second learning rate was set to 0.000006 after 1 epoch, but I resolve this problem when I reinstall python, pytorch and other packages. However, this error message, "SRFBB\lib\site-packages\torch\optm\torch\lr_scheduler.py143: UserWarning: The epoch parameter in 'scheduler.step()' was not necessary and is being deprecated where possible. Please use 'scheduler.step()' to step the scheduler. During the deprecation, if epoch is different from None, the closed form is used instead of the new chainable form, where available."
This message is just warning message, so training goes without any problems.

OK, thank you.


Sor10874/readmes/41 45

this PR covers
MapReferenceScale
MapRotation
MapSpatialReference (android set-map-spatial-reference)
MinMaxScale (android set-min-max-scale)
MobileMapSearchAndRoute

ok pinging @Rachael-E for 2nd review!

over to @hud10837

@Rachael-E @hud10837 I believe it's all sorted on my end.

@hud10837 is it ok to merge this one?


Respect -Djava.net.preferIPv4Stack when using epoll transport

Motivation:
On a system where ipv4 and ipv6 are supported a user may want to use -Djava.net.preferIPv4Stack=true to restrict it to use ipv4 only.
This is currently ignored with the epoll transport.
Modifications:
Respect java.net.preferIPv4Stack system property.
Result:
-Djava.net.preferIPv4Stack=true will have the effect the user is looking for.

@trustin please review

@tjake this is what you need as far as I know

@Scottmitch also please review if you have time... nothing fancy though :)

Thanks @normanmaurer

@trustin addressed your comments ... please check again.

@normanmaurer - LGTM.

LGTM. Please merge.

Cherry-picked into 4.0 (9a755364a0dc197e89853b3ca4a449a8eba37d5d) , 4.1 (3df7b4dac746c2af2d65528bf85495eb530aba41) and master (88954c022c2d1dfa2ab7bde1e60eafe405d31551)


New project with TRPC throws CORS error

Please provide the environment you discovered this bug in.
https://codesandbox.io/p/sandbox/strange-elbakyan-f4m9k2
Which area/package is the issue in?
trpc
Description
I created a new project with npx create-nx-workspace --preset=@analogjs/platform enabling the TRPC option. When I serve the application and try to add a new note on the sample page I get CORS errors in the console.
Please provide the exception or error you saw
Access to fetch at 'http://<IP_ADDRESS>:4200/api/trpc/note.create?batch=1' from origin 'https://f4m9k2-4200.csb.app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
<IP_ADDRESS>:4200/api/trpc/note.create?batch=1:1     Failed to load resource: net::ERR_FAILED
chunk-YKBZPBB4.js?v=31d7cea3:5618 ERROR TRPCClientError: Failed to fetch
    at _TRPCClientError.from (@analogjs_trpc.js?v=31d7cea3:702:12)
    at @analogjs_trpc.js?v=31d7cea3:1005:30
    at _ZoneDelegate.invoke (zone__js.js?v=31d7cea3:294:158)
    at Object.onInvoke (chunk-YKBZPBB4.js?v=31d7cea3:14392:25)
    at _ZoneDelegate.invoke (zone__js.js?v=31d7cea3:294:46)
    at _Zone.run (zone__js.js?v=31d7cea3:100:35)
    at zone__js.js?v=31d7cea3:1028:28
    at _ZoneDelegate.invokeTask (zone__js.js?v=31d7cea3:320:171)
    at chunk-YKBZPBB4.js?v=31d7cea3:14222:49
    at AsyncStackTaggingZoneSpec.onInvokeTask (chunk-YKBZPBB4.js?v=31d7cea3:14222:30)
h

Other information
No response
I would be willing to submit a PR to fix this issue

[X] Yes
[ ] No

Most likely need to update the url in the tRPC client to match the Codesandbox environment
https://codesandbox.io/p/sandbox/strange-elbakyan-f4m9k2?file=%2Fsample%2Fsrc%2Ftrpc-client.ts%3A1%2C1

Ah, you are correct, I was accessing it locally on localhost:4200, works fine on <IP_ADDRESS>:4200. Thank you!