Can't extract ogg files with unityextract

Trying to extract ogg files with the unityextract script but it keeps giving that error:
Traceback (most recent call last):
  File "unityextract", line 159, in <module>
    main()
  File "unityextract", line 155, in main
    exit(app.run())
  File "unityextract", line 57, in run
    self.handle_asset(asset)
  File "unityextract", line 97, in handle_asset
    samples = extract_audioclip_samples(d)
  File "C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\lib\site-packages\unitypack\utils.py", line 37, in extract_audioclip_samples
    sample = af.rebuild_sample(sample)
  File "C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\lib\site-packages\fsb5\__init__.py", line 212, in rebuild_sample
    from . import vorbis
  File "C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\lib\site-packages\fsb5\vorbis.py", line 12, in <module>
    vorbis = load_lib('vorbis')
  File "C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\lib\site-packages\fsb5\utils.py", line 76, in load_lib
    raise LibraryNotFoundException('Could not load the library %r' % (names[0]))
fsb5.utils.LibraryNotFoundException: Could not load the library 'vorbis'

Windows 10 64 bit version 1803
unitypack and fsb5 installed with pip

I have tried putting the libvorbis and libogg libs given on the fsb5 github in multiple places, including:

C:\Windows\System32
Where the unityextract script is C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\Scripts
Where unitypack is installed C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\Lib\site-packages\unitypack
Where fsb5 is installed C:\Users\Lykrast\AppData\Local\Programs\Python\Python36-32\Lib\site-packages\fsb5

So far none of them worked and the error hasn't changed.

Just noticed that I got the issue duplicated at #83, probably something wonky happened with my internet connection when I wrote that.


[ChaCha20-Poly1305.json] Update spec link

ChaCha20-Poly1305 is now RFC7905. Also when will this feature be displayed on the website?

Thanks. Currently based on the caniuse search logs there's very little interest in this feature so it hasn't been a priority, but I'll get to it eventually.


Getting started Docker Desktop

Getting started for Docker Desktop tutorial. It would be good if someone could test this.

This change is

/ok-to-test

Fixes https://github.com/kubeflow/website/issues/754

@DanSanche Do you have bandwidth to review this PR?

/assign @DanSanche
Thanks Dan!

@sarahmaddox: GitHub didn't allow me to assign the following users: DanSanche.
Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Huh it seems that a review comment doesn't count as a comment.

ok, this is my real comment then!

/assign @DanSanche

Yaayyy that worked :)

Thanks for the work! However, this tutorial does not yet work for me on Windows 10.
The introduction should state that one needs to have ksonnet in the PATH and perhaps demonstrate how to download and add it.
Further, I need to run
cd ${KFAPP}
ks init ks_app
${KUBEFLOW_SRC}/scripts/kfctl.sh apply all

instead of the sequence given in the tutorial (just creating a folder ks_app is not sufficient).

Hi @sarahmaddox In my Fix ks_app issue commit I added the fix as per suggestions, however I also got stuck in a loop of 'resources not found'. If someone could help on this then that would be great as I just haven't had time to look at it since then. I'll reach out on the workspace today.

Hey, I just got this working on Docker Desktop on macos. I tried to follow the instructions here, but ended up getting similar errors to you. I ended up going with a modified version of the instructions here: https://tutorials.ubuntu.com/tutorial/get-started-kubeflow#3
The tutorial assumes microk8s, but I just moved forward with Kubernetes running on Docker Desktop. Things I had to adjust included needing to run kubectl create namespace kubeflow-anonymous and I ended up needing to to use the apply.sh script as I ended up with the same bug detailed in this issue (looks like it's being fixed with 0.7 so this is a temporary need): https://github.com/kubeflow/kubeflow/issues/3810#issuecomment-527687504
To run the apply.sh script I also had to brew install kustomize.
Possibly not as straightforward as the approach taken here, and definitely required a few hoops, but it works! Let me know if/how I can help get this written up! My company blocks virtual machines on our machines, so using multipass/microk8s won't work, but they do allow Docker Desktop so getting this working is a life saver!

@devenjarvis I ended up getting mine running with a similar method but no extra steps if you need to get others up and running on windows:

enable k8s in docker for desktop
deploy to existing cluster: https://www.kubeflow.org/docs/started/k8s/kfctl-k8s-istio/
at any time before executing the kfctl apply all step do the kubectl create namespace kubeflow-anonymous to avoid looping warning at end (apparently this occurs with kfctl on all non-gcp targets according to: https://github.com/kubeflow/kubeflow/issues/4090 )

Here's a blog post that gets Kubeflow v0.6.2 running on Docker Desktop for Mac or Windows:
https://www.docker.com/blog/depend-on-docker-for-kubeflow/

Hallo @josiemundi Thanks so much for all the work you've done on this pull request. Kubeflow has moved on to using kustomize instead of ksonnet, and it looks like the task has turned out to be a lot more complicated than we originally thought. I'm going to close this PR, but please do re-open it if you'd like to pick up the work again.
I've added a reference to this PR in the related issue https://github.com/kubeflow/website/issues/754 - please let me know if you'd like to pick up that issue and create a new PR for Kubeflow v1.0.
/close


Add Slurmrestd to Centos

We now have slurmrestd packaged for centos7. This PR adds the test code to check if it is working.
Depdensd on:

https://github.com/omnivector-solutions/slurm-ops-manager/pull/55
https://github.com/omnivector-solutions/slurm-bundles/pull/16

To be merged after #78

closing as this PR is very out of date. Will open a new one with a clean history soon


Add files via upload

I didn't find the business card designs here, so I added them

Great  🎉
In case you would like to show the logos in https://bewelcome.github.io/community-gallery/ you would need to convert a copy to jpg or png.


Enhancements to mayactl for Jiva volumes

This is a feature request to display the size (du -h) of each replica in the mayactl volume info/stats commands.
It will be good to implement this for both jiva and cstor.

Current implementation of mayactl is broken for snapshot related queries. I have tested following commands and it didn't work for me:
bash-4.3# mayactl snapshot create --volname=pvc-9babeb43-96aa-4da2-b8d4-e142b3a1efda --snapname=hello -n openebs
Executing volume snapshot create...
Snapshot creation failed: failed to create snapshot 'hello': missing volume name
bash-4.3# mayactl snapshot list
--volname is missing. Please specify an unique name
bash-4.3# mayactl snapshot list --volname=pvc-9babeb43-96aa-4da2-b8d4-e142b3a1efda
Error list available snapshot: Server status error: Bad Request

both commands failed with different errors. Further digging into the logs of maya-apiserver i found out that namespace related checks are not there for all the snapshots. I also tried to hit the endpoint using curl and this gave me different error:
bash-4.3# curl "<IP_ADDRESS>:5656/latest/snapshots/?volume=pvc-9babeb43-96aa-4da2-b8d4-e142b3a1efda&namespace=openebs"
unable to list snapshots: missing cas template for list snapshot

I quickly had a look at the code and i found that snapshot list related CAS Template is not there. As of now all the snapshot related commands have been commented out in the mayactl.
Since jiva already provides jivactl a command line tool to manage jiva volumes, snapshot related functionality is already there. One can run following command to query about the snapshot by execing into the controller.

jivactl ls
jivactl snapshot ls
jivactl snapshot info


Support AppGroup in ServiceStage Configuration and Deployment

Update plugin to enable deployment of resources with app group specification:

Update Config dialog UI with selection of optional field App Group.
Populate VPN and Subnet selection base on App Group selection input.
Add supporting changes in Token, Request Manager, Http Clients and Helper classes.
Update/Add test cases

Changes are under development in branches

https://github.com/ewcchan/servicestage-java-client/tree/config-deploy
https://github.com/ewcchan/servicestage-eclipse-plugin/tree/config-deploy

code delivered. mark close.


Add "sync-lockfile" command

My --bin project has CI which updates the version number in Cargo.toml, which it then commits. However, this means that any further cargo command (build, test, etc) will update the existing Cargo.lock file (updating the root version), causing some frustration for users. Furthermore, it breaks the publish command, which requires the repo to be current.
I've added a sync-lockfile command to simply update the root version in the Cargo.lock file to match the Cargo.toml in the same way that simple commands like fetch do. If no Cargo.lock file is present, and new one is generated based on the index.
This is a demo PR for Pre-RFC conversation at https://internals.rust-lang.org/t/pre-rfc-cargo-command-to-just-sync-lockfile/13119, but may become a real PR if it gets approval.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR!  The Cargo team talked about this, and we feel that this would probably be better to be part of cargo update. There is a pretty high bar to add a new top-level command, and this doesn't feel like it really needs a new command. Perhaps a --workspace flag to mirror other commands?  I'm not certain that it is 100% equivalent to pass workspace members to the avoid list, but I believe it should be roughly the same.

Thanks for the PR! The Cargo team talked about this, and we feel that this would probably be better to be part of cargo update. There is a pretty high bar to add a new top-level command, and this doesn't feel like it really needs a new command. Perhaps a --workspace flag to mirror other commands? I'm not certain that it is 100% equivalent to pass workspace members to the avoid list, but I believe it should be roughly the same.

Thanks, @ehuss. Discussion on the forums came to roughly the same conclusion. I'll change the PR so that update --workspace does what I want, instead of an entirely new command.
Are the Cargo Book descriptions auto-pulled from the source, or should I be updating that separately?

Are the Cargo Book descriptions auto-pulled from the source, or should I be updating that separately?

The documentation is written in markdown. The cargo-update documentation is here: https://github.com/rust-lang/cargo/blob/master/src/doc/man/cargo-update.md.  After updating the docs, you need to run build-man.sh to rebuild the man pages. There's more documentation on how this works at https://github.com/rust-lang/cargo/tree/master/src/doc.

@ehuss Sorry for the slow response: real life intervened. Anywho, I have moved the functionality to update --workspace as discussed, and have added the flag to the docs as well. Please let me know how that looks.

Thanks!
From an implementation standpoint, I was thinking that the --workspace flag would just add the set of member PackageIds to the to_avoid list. That would avoid needing a special code path. This current implementation seems to ignore additional -p flags, and doesn't report what was updated. Do you think there would be any particular problems with that approach, or were there other reasons to go with the current design?

Thanks, that does seem like a better approach. Will put that in.

@ehuss Just checked in the suggested changes: looks like the best way is just to keep the to_avoid array empty (-ish) if there's a --workspaces flag. That is much easier approach, and integrates better with existing behavior. Let me know what you think.

@rfcbot fcp merge
This adds a new stable flag --workspace (or -w) to cargo update which will cause it to update only the workspace members (or more specifically, it does an update equivalent to cargo build which updates any out-of-date path sources).  This can be useful when bumping the version in Cargo.toml, and you want to update Cargo.lock, but don't want to run some other command (like build or metadata), or don't want to explicitly list each workspace member like cargo update -p foo.

@rfcbot fcp merge

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 63d0fe43449adcb316d34d98a982b597faca4178 to master...


Support Negative Edge Flip-flop

Motivate of the pull request

[ ] To address an existing issue. If so, please provide a link to the issue:
[x] Breaking new feature. If so, please describe details in the description part.

Describe the technical details
What is currently done? (Provide issue link if applicable)

Currently, OpenFPGA has the following limitations:

No examples about how to use negative edge triggered flip-flops

What does this pull request change?

This PR improves in the following aspects:

[x] Added a new circuit design of multi-mode flip-flop which supports negative-edge and positive edge
[x] Added a regression test for compiling verilog files in cell library
[x] Added an architecture which supported both positive edge and negative edge triggered flip-flops
[x] Added a counter design which is triggered by negative edge
[x] Added a test case to validate the newly added benchmark and architecture

Which part of the code base require a change

[ ] VPR
[ ] Tileable routing architecture generator
[ ] OpenFPGA libraries
[ ] FPGA-Verilog
[ ] FPGA-Bitstream
[ ] FPGA-SDC
[ ] FPGA-SPICE
[ ] Flow scripts
[x] Architecture library
[x] Cell library
[ ] Documentation
[x] Regression tests
[x] Continous Integration (CI) scripts

Impact of the pull request

[ ] Require a change on Quality of Results (QoR)
[ ] Break back-compatibility. If so, please list who may be influenced.

Waveform of the test case:


How to make "navBar" not animated, for example as "tabBar".

Version

react-native-router-flux v4.0.0-beta.21
react-native v0.46.4

How to make "navBar" not animated, for example as "tabBar". That is, when switching between scenes, the transition animation was not applied to "navBar".

Use headerMode='screen' prop.

@aksonov it's not exactly what I want. How to make a 'navbar' a global component? That is, it did not redraw when switching between scenes


no .exe

Hello. I am very new to GitHub but I can't find the .exe?
I downloaded the very first one you released and it came with a .exe but now I cant find it.

Hi, you have 2 ways to run this project
Option 1: Use the stable release:
https://github.com/aeon0/botty/releases/tag/v0.3.0
This includes the .exe
And it's the easiest to use.
Option 2: Use the latest release: (What you have done I think)
https://github.com/aeon0/botty/archive/refs/heads/master.zip
But you need to:

Install miniconda (https://docs.conda.io/en/latest/miniconda.html). Note: You will have to check "Add conda to my PATH environment variable" in order to access the conda command in the cmd.
open cmd and do:

cd botty (Where you downloaded it)
conda env create environment.yml
conda activate botty
python src/run.py

Thanks! That's exactly what I did the first time I forgot I downloaded win7 to unzip the rar!
i have 1 more question. but i think im suppose to make a new "issue" right?
is there any way to get the bot to buy potions at the start of the game?

Issues are only for bugs, thus the template to fill out all needed questions. Please ask your questions in the discord server. Closing this.


SparkSession.builder() not working

Hi, I'm trying to use the library, I put the dependency on the gradle.
The import worked, but the Creating a SparkSession in Kotlin implementation doesn't work, it gives an error in the builder, did I do something wrong?

Hi there!
Do you still have this issue?
We also support Spark 3.2 now, if you're interested: kotlin-spark-api-3.2:1.0.3

Closing this, feel free to reopen if you still face the bug


Lua - onSpawnStrum function

This function activates when a strum is added (basically at the beginning of a song)
It's really useful despite the fact that some players make cutscenes in the beginning of a level
It has 3 parameters: position, player and id
position - index number of the strum in strumLineNotes
player - to which player does the strum belong to? (0 is the opponent while 1 is the player)
id - public strum's noteData (basically what strum is it, left down up or right)
Script example - Placing the notes just like in vanilla fnf:
function onSpawnStrum(position, player, id)
        if not middlescroll then
	        setPropertyFromGroup('strumLineNotes', position, 'x', getPropertyFromClass('Note', 'swagWidth') * id + 50 + (screenWidth / 2) * player)
        end
end

(haven't tested this script so I am not certain if this would work)

if i broke something by making the player variable global in strumnote.hx, i'll make another merge


?graded practise?

is this hack only for tests?
bc if so we should do a co-op for the graded practise flash cards
also me and my friend are willing to pay u if u make a hack for graded practise

Me to

💸🤑💰

Implemented.


full node - syncing stalls until restart

Celestia Node version
v0.11.0-rc6
OS
Ubuntu 22.04
Install tools
docker-compose
Others
celestia full start --core.ip http://consensus-full-arabica-9.celestia-arabica.com/ --gateway --gateway.deprecated-endpoints --gateway.addr da --gateway.port 26659 --p2p.network arabica --keyring.accname caldera
Node store mounted using:
volumes:
       - /home/ubuntu/.celestia-full-arabica-9/:/home/celestia/.celestia-full-arabica-9/

Steps to reproduce it
Let full node launch and sync for a while.
Expected result
The full node continues to sync and reaches the network head.
Actual result
The full node stalls during sync and resumes syncing after a restart.
Relevant log output
2023-07-02T00:49:49.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:50.430Z	INFO	header/store	store/store.go:353	new head	{"height": 9640, "hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD"}
2023-07-02T00:49:50.430Z	INFO	header/sync	sync/sync_head.go:116	new network head	{"height": 9640, "hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD"}
2023-07-02T00:49:50.430Z	INFO	das	das/worker.go:148	sampled header	{"type": "recent", "height": 9640, "hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD", "square width": 2, "data root": "3D96B7D238E7E0456F6AF8E7CDF0A67BD6CF9C2089ECB559C659DCAA1F880353", "finished (s)": 0.000015223}
2023-07-02T00:49:50.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:51.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:52.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:53.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:54.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:55.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:56.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:57.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:58.022Z	WARN	header/sync	sync/sync_head.go:140	received known network header	{"current_height": 9640, "header_height": 9640, "header_hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD"}
2023-07-02T00:49:58.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:49:59.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:00.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:00.866Z	WARN	header/sync	sync/sync_head.go:140	received known network header	{"current_height": 9640, "header_height": 9640, "header_hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD"}
2023-07-02T00:50:01.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:02.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:03.052Z	WARN	header/sync	sync/sync_head.go:140	received known network header	{"current_height": 9640, "header_height": 9640, "header_hash": "523E88FEAEBC98F374694544BEF68CBEB8E6EE05EE9612E5279C9861BF8CE7FD"}
2023-07-02T00:50:03.839Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:04.840Z	INFO	share/discovery	discovery/discovery.go:254	discovering peers	{"want": 1}
2023-07-02T00:50:05.429Z	INFO	header/store	store/store.go:353	new head	{"height": 9641, "hash": "94F5A98C00B069CB7AF12F2F013B39D34944764FFAB586A2AB65BAFAC8DA40BE"}
2023-07-02T00:50:05.430Z	INFO	das	das/worker.go:148	sampled header	{"type": "recent", "height": 9641, "hash": "94F5A98C00B069CB7AF12F2F013B39D34944764FFAB586A2AB65BAFAC8DA40BE", "square width": 2, "data root": "3D96B7D238E7E0456F6AF8E7CDF0A67BD6CF9C2089ECB559C659DCAA1F880353", "finished (s)": 0.000077669}

Full logs: https://drive.google.com/file/d/10Gp0O33lBHK0KhBJAJT0LZAvnbstSFq-/view?usp=sharing

### Notes

Originally reported by Caldera team

/cc @TheAppleTucker

When the sync paused around 9640, the client trying to submit blobs was being returned the following error:
header: given height is from the future: networkHeight: 9640, requestedHeight: 11437

Is this fixed, I thought it was fixed by a recent PR? If so we should link + close this

Has not been observed on recent RCs


feat: org v2 ListOrganizations

Which Problems Are Solved
Org v2 service does not have a ListOrganizations endpoint.
How the Problems Are Solved
Implement ListOrganizations endpoint.
Additional Changes

moved descriptions in the protos to comments
corrected the RemoveNoPermissions for the ListUsers, to get the correct TotalResults

Additional Context
For new typescript login

@stebenz looks like the service was never added to the docs. Could you please add it now


How to solve the error of executing rebuild.

oot@git askbend]# ./target/release/askbend -c conf/askbend.toml --rebuild
[2023-04-12T09:49:50Z INFO ] config: Config { log: LogConfig { level: "INFO", dir: "_logs" }, data: DataConfig { path: "data/", file_ext: "md", ignore_dirs: ["rfc"] }, database: DatabaseConfig { database: "askbend", table: "doc", answer_table: "", dsn: "******" }, server: ServerConfig { host: "<IP_ADDRESS>", port: 8081, rebuild: true }, query: QueryConfig { min_content_length: 50, max_content_length: 8000, top: 3, min_distance: "", prompt: "You are a dedicated Databend representative, eager to assist users with their inquiries. Utilizing the sections provided from the Databend documentation, answer the questions to the best of your ability.\nIf the answer is not explicitly available in the documentation or you are unsure, respond with, "Sorry, I dont know how to help with that."\nMake sure to keep the SQL syntax unchanged.\nAnswer in markdown, incorporate relevant code snippets, if available, and ensure that any URLs are converted to absolute URLs in the style of Docusaurus documentation.\nAvoid using relative URLs and images.\n\nDocumentation sections:\n{{context}}\n\nQuestion:\n{{query}}" }, config_file: "conf/askbend.toml" }
[2023-04-12T09:49:50Z INFO ] Step-1: begin parser all md files
[2023-04-12T09:49:50Z INFO ] Step-1: finish parser all md files:5, sections:9, tokens:177
[2023-04-12T09:49:50Z INFO ] Step-2: begin insert to table
Error: error sending request for url (https://test/v1/query): error trying to connect: dns error: failed to lookup address information: Name or service not known
Caused by:
0: error trying to connect: dns error: failed to lookup address information: Name or service not known
1: dns error: failed to lookup address information: Name or service not known
2: failed to lookup address information: Name or service not known

What's your DatabendCloud dsn address?

Thank you, it has been solved. The reason is that the Batabend DSN address is filled in incorrectly.


Fixed for compatibility with PostgreSQL-14 beta2

In PostgreSQL 14 Beta 2 was introduced new parameter readOnlyTree bool for function ProcessUtility.
I append new parameter to function signature, but I'm not sure, should it be true or false when called for create PGTT.
@darold , please, run tests if you have the time.

It seems deprecated.

Oh, sorry I have not seen this PR. I have fixed it urgently after Devrim report.

I have modified the release note https://github.com/darold/pgtt/releases/tag/v2.6 and the ChangeLog to acknowledge you about the patch on PG14.


Implement enableBackingStore method

Looking good, just run dart format . and you're golden

Nothing changes in these 3 files when I run dart format . 🙈


Allow to specify queue name for shoryuken

Allow to specify queue name for Shoryuken:
config.use_shoryuken :queue => 'my_queue'

Previous behaviour enforced "rollbar_#{Rollbar.configuration.environment}" queue name which is now the default name.
This PR actually includes changes introduced in different PR that fixes shoryuken undefined method call error since that's what makes Shoryuken work properly.

This PR is not passing Travis builds. I added shoryuken and aws-sdk-sqs to all gemfiles. Please sync with the latest master.  Can you investigate?

Thank you @herr-zimt for this PR. It looks great and passes tests. Merging now.


Update to Tableau Dashboard

Tableau Dashboard
Yuanyuan.

Rename pageviews column to views (Check with Niharika for the right naming convention)
Add ms or secs to pageview time (min,max,avg) columns
Re-arrange age-range based on Dr.Cleo recommendation
Size of groups for analytics
18-49
50-64
65 and older
Run a test on the CanbeWell test website and check for the data captured in the firebase for the session details.

Niharika.

Clean Dr. Cleo web activity footprints from the dashboard (Week 6 - 12 July)
Update the wiki page with color code to be used for the charts in the dashboard

Juveriya.
Check the dashboards created to make sure they meet the consistency criteria ( follow-up with Niharika or Yuanyuan for any doubts.

For dashboard update of July 13 to July 19:

Renamed "number of records" column to "Views".
Added "seconds" in the title of the page view time table.
Re-arrange age-range based on Dr.Cleo recommendation
Size of groups for analytics
18-49
50-64
65 and older
Done.
Tested according to test plan.
Updated workbook on tableau public.
Uploaded data and workbook files as records to google drive.
Yuanyuan


[SMALLFIX] Fix logging formats

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6904/
Test FAILed.

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6905/
Test PASSed.


RuntimeError: CUDA out of memory when training BioBERT NER model

I have tried to run the run_ner.py script on my local laptop and I had the following error:
Iteration:   0%|                                                                                | 0/189 [00:00<?, ?it/s]
Epoch:   0%|                                                                                | 0/5 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "run_ner.py", line 284, in <module>
    main()
  File "run_ner.py", line 206, in main
    model_path=model_args.model_name_or_path if os.path.isdir(model_args.model_name_or_path) else None
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/trainer.py", line 499, in train
    tr_loss += self._training_step(model, inputs, optimizer)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/trainer.py", line 622, in _training_step
    outputs = model(**inputs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 1446, in forward
    output_hidden_states=output_hidden_states,
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 762, in forward
    output_hidden_states=output_hidden_states,
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 439, in forward
    output_attentions,
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 371, in forward
    hidden_states, attention_mask, head_mask, output_attentions=output_attentions,
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 315, in forward
    hidden_states, attention_mask, head_mask, encoder_hidden_states, encoder_attention_mask, output_attentions,
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/xegulon/miniconda3/envs/ehr-re/lib/python3.7/site-packages/transformers/modeling_bert.py", line 256, in forward
    context_layer = torch.matmul(attention_probs, value_layer)
RuntimeError: CUDA out of memory. Tried to allocate 20.00 MiB (GPU 0; 5.80 GiB total capacity; 4.70 GiB already allocated; 18.19 MiB free; 4.85 GiB reserved in total by PyTorch)

Is there any easy workaround for that? Is it compulsory to run that on a cloud GPU?

The NER task requires a lot of memory for training, it's best to run it on a cloud GPU. However, if you want to run it locally, you can try to decrease the batch size and/or max token length,


Declare the license for this repository

See:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

Done, thanks
https://github.com/saveriofrancini/bap/blob/master/LICENSE.md
Saverio
Il giorno lun 10 ott 2022 alle ore 21:16 Tyler Erickson <
@.***> ha scritto:

See:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
—
Reply to this email directly, view it on GitHub
https://github.com/saveriofrancini/bap/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI744U3KHLLFYGZAPO4GXI3WCRTSVANCNFSM6AAAAAARBTP5IY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Update tomcat7 to 7.0.59 #648

I tried to update the version. I have no idea how to test this =)

Duplicate of https://github.com/Homebrew/homebrew-versions/pull/642

Close because dup of #642


Update adb extension

Description

Add display density to control display density (values from 0.5 to 3.0)
Add font size to control font sizes (vales from 0.5 to 3.0)
Add large display and font to set display density and font size to maximum
Add reset display and font to reset the values to default
Change extension name to include Android in order to improve discoverability of the extension

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer 👋  disabled 2 commands, thanks :)


Delete endpoint returns 201 created

Delete endpoints should not return 201 Created.
http://apidocs.cloudfoundry.org/225/blobstores/delete_all_blobs_in_the_buildpack_cache_blobstore.html

Fix pushed.  Please re-open if you have any further issues.
Thanks!

Thanks.


Typo fix @ Let's encrypt

Just a typo fix!

Thanks for the fix!
Added your name in contributors list


Network: Clustering state avoid duplicate global config when doing re-create

When doing a lxc network create for subsequent attempts after failed initial attempt, avoid creating duplicate global config by ignoring global config supplied on subsequent attempts.

@stgraber I'm wondering now if I should reject lxc network create subsequent attempts that specify global config, rather than ignore it.
E.g.
lxc network create ovn1 --type=ovn network=uplink # Partially fails on one node due to uplink issue for example.
# Fix issue with failed node uplink.
lxc network create ovn1 --type=ovn network=differentUplink # Reject or ignore global config supplied here?

@stgraber I think also this will need a patch to remove duplicated rows that have the same value, as for OVN networks the network property will have been duplicated due to https://github.com/lxc/lxd/pull/8244/commits/319053c314e310ef561c5de381d4ed5e118b0e86

Reject would be good I think, less of a surprise to the user who can then decide to either complete with current config or delete and do it again.

@stgraber fixed, and added a patch for removing duplicate network config rows that have exact same value.

@tomponline jenkins not happy

jenkins: test this please

Testsuite passed

Testsuite passed

Testsuite passed

Testsuite passed

Testsuite passed

Testsuite passed

Testsuite passed

Testsuite passed


The delete_global_graphs command does not work in a specific scenario

Describe the bug
The delete_global_graphs command fails (return false) to delete a graph context if any graph context later in the list was deleted before.
How are you accessing AGE (Command line, driver, etc.)?

What is the necessary configuration info needed?

AGE needs to be installed in the PG 11.17.

What is the command that caused the error?
-- delete age_global_graph_2's context
-- should return true (succeeded)
SELECT * FROM cypher('age_global_graph_2', $$ RETURN delete_global_graphs('age_global_graph_2') $$) AS (result agtype);

-- delete age_global_graph_1's context
-- should return true (succeed) because previous command should not delete the 1st graph's context
SELECT * FROM cypher('age_global_graph_1', $$ RETURN delete_global_graphs('age_global_graph_1') $$) AS (result agtype);

-- delete age_global_graph_3's context
-- should return true (succeed) because previous commands should not delete the 3rd graph's context
SELECT * FROM cypher('age_global_graph_3', $$ RETURN delete_global_graphs('age_global_graph_3') $$) AS (result agtype);

SELECT * FROM cypher('age_global_graph_2', $$ RETURN delete_global_graphs('age_global_graph_2') $$) AS (result agtype);
 result
--------
 true
(1 row)

SELECT * FROM cypher('age_global_graph_1', $$ RETURN delete_global_graphs('age_global_graph_1') $$) AS (result agtype);
 result
--------
 false
(1 row)

SELECT * FROM cypher('age_global_graph_3', $$ RETURN delete_global_graphs('age_global_graph_3') $$) AS (result agtype);
 result
--------
 true
(1 row)

Expected behavior
The second query should return true.
Environment (please complete the following information):

Version: PG 11.17

Additional context
If the queries are executed in this order, the output is correct:
-- delete age_global_graph_1's context
-- should return true (succeed) because previous command should not delete the 1st graph's context
SELECT * FROM cypher('age_global_graph_1', $$ RETURN delete_global_graphs('age_global_graph_1') $$) AS (result agtype);

-- delete age_global_graph_2's context
-- should return true (succeeded)
SELECT * FROM cypher('age_global_graph_2', $$ RETURN delete_global_graphs('age_global_graph_2') $$) AS (result agtype);

-- delete age_global_graph_3's context
-- should return true (succeed) because previous commands should not delete the 3rd graph's context
SELECT * FROM cypher('age_global_graph_3', $$ RETURN delete_global_graphs('age_global_graph_3') $$) AS (result agtype);

Output:
SELECT * FROM cypher('age_global_graph_1', $$ RETURN delete_global_graphs('age_global_graph_1') $$) AS (result agtype);
 result
--------
 true
(1 row)

SELECT * FROM cypher('age_global_graph_2', $$ RETURN delete_global_graphs('age_global_graph_2') $$) AS (result agtype);
 result
--------
 true
(1 row)

SELECT * FROM cypher('age_global_graph_3', $$ RETURN delete_global_graphs('age_global_graph_3') $$) AS (result agtype);
 result
--------
 true
(1 row)

Such a n00b mistake on my part, sigh. I will create a patch to fix this.

Once the patch is approved and applied, please verify your new regression tests. Then create the appropriate requests to add those regression tests as part of our suite of regression tests.

A patch to fix this bug has been applied to the master branch.


add disabled prop

Can one of the admins verify this patch?

test this please

Codecov Report

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

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          10     10
  Branches        1      1
=====================================
  Hits           10     10

Impacted Files
Coverage Δ

src/Checkbox.tsx
100% <ø> (ø)
:arrow_up:

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 b15f7ae...2651856. Read the comment docs.


RedisSinkCluster self.masters sometimes contains replicas

I have observed a random test failure https://github.com/shotover/shotover-proxy/runs/6290958118?check_suite_focus=true occur because a RoutingInfo::Slot command was routed to a replica and the command "CLUSTER REPLICAS" must be run against a master.
The only way for this to have occurred is for self.slots.masters to have contained a replica.

I took a look at this because it sounded dangerous but I am giving up for now.
just very confused how this could happen at all.
The self.slots.master generation seems sound.
The only remaining possibilities I can think of is either:

a master node failed and was swapped with a replica node - this cant be it because I'm sure we would hit other errors first in the case of such a failure
a redis cluster from a previous test is still partially running and the networking is sometimes hitting the old cluster :shrug: - seems to farfetched

This could likely occur due to a split brain in the cluster, or we havn't caught things up. I have seen this error during a failover in the redis cluster while running test suites.
I think for most queries, we generally expect either a mov or an ask as the response when this occurs. I guess SLOTS errors out differently. Without digging into the flow of CLUSTER REPLICAS and what it does, my gut would be to try rebuilding our slot list when we get this and then giving up if it still happens (that indicates the cluster would be in a weird state).

While investigating the intermittent failure, I discovered the true cause which I raised a PR for here https://github.com/shotover/shotover-proxy/pull/1792 , but its worth noting that the reasoning in my original comment is flawed and doesnt really make sense.
In that test case we arent running CLUSTER REPLICAS but CLUSTER REPLICAS $ID which has different routing requirements.


08/13/2018 05:57 : Create Pull Request for branch master -> prTesting1_2018081305

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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


Update service-gateway-deployment-guidance.md

fixed typo and bolded DirectQuery

@andikrueger : Thanks for your contribution! The author, @mgblythe, has been notified to review your proposed change.

Thanks @andikrueger
#sign-off


ops(dspy): adding docs previes to MRs CI/CD action

Adding automatic docs generation from the new branch (when docs are changed) so we can validate the new documentation before merging the PR.
Warning ⚠: This requires setting up the repos PAT (personal acess token) in the secrets of the repo.

Hi @piotrlaczkowski , closing for now as we've moved to hosting docs via Vercel and the dspy-docs subtree. Thanks!


Switching Update-ServiceStatus to use Runspaces + minor fixes

Type of Change

[x] Bug fix (non-breaking change)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Remove the usage of Start-Job cmdlet, which was slow and didn't work without having dbatools in $env:psmodulepath variable
Approach
Using runspaces instead
Commands to test

Screenshots

Learning

you rock 👨🎤  ! Wanna consolidate your tests into this PR? Then we can see if it all works together

re-opened PR #2268 for that (added commits from this branch to the tests branch)

awesome, thanks!


add changelog, bump version to 0.2

@bobmcwhirter Is this OK with you? Do you want to do the cargo publish or do you want to add me?

What's your crates.io username and I'll grant that power to you.

@bobmcwhirter same as here, jordens
Thanks!

Gimme an hour or so to get to my desk and will do.


Broadcast data and Listen for data at the same time (mesh)

Hi petzval, I am trying to make a mesh from 3 Raspberry Pis. One node will broadcast data to the two other nodes, this part works, but at the same time, I want them to also listen to the other Raspberry Pis for data. However, I am having a problem with the latter. For example, when the mesh server starts listening in raspi A, I tried to send data to other raspi but there is an error like this.
Initialising...
Bluez down failed
Bind failed
HCI socket ERROR - no Bluetooth?
Is it possible to make the node broadcast data and listen for data from the other nodes at the same time? If possible, How can I do it? I'm sorry I am a beginner at this topic. Thank you so much!
Another issue I am facing right now is I tried to code the MESH BROADCASTER but when I try to run it, I cannot receive the data that it sends to other nodes. This is my code:
#include <stdio.h>
#include <stdlib.h>
#include "btlib.h"

int main()
  {
  if(init_blue("devices.txt") == 0)
    return(0);

  char buf[4];

  buf[0] = 0x12;
  buf[1] = 0x34;
   // broadcast two-byte mesh packet
  write_mesh(buf,2);
   // broadcast D disconnect command
  write_mesh("D",1);
  return(0);
  }

If node 1 is the broadcasting Pi, and 2/3 are the receivers.

How is the broadcasting done - via node (or maybe classic)
client/server connections where 1 is a node client and 2/3 are connected
node servers, or via mesh packets where 2/3 are mesh servers and 1 uses
write_mesh.

In either case 2/3 are already listening to 1. Do you want 1 to
listen for data from 2/3, or 2 to listen for data from 3?

The sample.c example (section 3.9 in the documentation) might help.
If 2/3 are mesh servers, they listen to all other Pis, and only connect
temporarily 1:1 as node client/server when they get a mesh packet
requesting a data transfer. After the transfer, the node connection is
disconnected and the mesh server goes back to listening for write_mesh
packets from all the other devices.

The HCI socket ERROR is usually caused by not running with root
permissions, use sudo:
sudo ./mycode
The simple write_mesh() code fails because the program is terminating
and shutting down Bluetooth before the mesh packet can be sent. There
needs to be a delay after each write_mesh  to allow the packet to be
sent. The advertising repeat rate at which packets are sent is 1 second
or more. Also, good practice to call close_all() on exit. Thanks for
flagging this up, I see the documentation is not clear on this point.
|#include <stdio.h> #include <stdlib.h> #include <unistd.h> #include
"btlib.h" int main() { if(init_blue("devices.txt") == 0) return(0); char
buf[4]; buf[0] = 0x12; buf[1] = 0x34; // broadcast two-byte mesh packet
write_mesh(buf,2); sleep(5); // wait 5 seconds for packet to be sent //
broadcast D disconnect command write_mesh("D",1); sleep(5); // wait 5
seconds for packet to be sent close_all(); return(0); }|

I've checked the code and the mesh packet repeat rate should be about 3 per second, so a one second delay should be OK. For hackers, this rate is set in btlib.c - leadparam[32] around line 532. This sets the rate to 0200 (multiplied by 0.625ms = 320ms).

The broadcasting is done via mesh packets. So, Node 1 uses the mesh broadcasting code with write_mesh on it. Then, 2 and 3 were able to receive it since it is running the mesh server code.

Yes, I want node 1 to listen for data from 2 and 3. So, I tried running the mesh server code in node 1 and it runs without error. So, node 1,2 and 3 are listening for data.  But when I try to run the mesh broadcasting code with sudo in node 1 or in any node, the error above came out. Is this logic possible?

I saw sample.c code but do you think number 2 can be used instead? So every node (1&2&3) is listening (mesh server running). Then, if I want to send data from 1 to 2 and 3, or 2 to 1 and 3, or 3 to 1 and 2, I will just run the mesh broadcasting code to send the data. Is this likely to be achieved?

The other issue is now working! It needed the delay for it to work. Thank you so much for your assistance. I appreciate it.

If all devices are mesh servers, they are all listening for a mesh packet - so there is no way to initiate a process. Something
has to take charge and send an initial mesh packet. Node 1 could tell 2 and 3 to connect and exchange data for example. But you could construct your own mesh server using read_mesh - then because you have written the listening code it can now initiate a process and all devices can be servers, and any pair can decide to exchange data.
Here's how to return data from 2 to 1 (but 3 will also receive the reply). This same code runs on all devices.
#include <stdio.h>
#include <stdlib.h>
#include "btlib.h"
#include <unistd.h>
#include <string.h>

int callback(int clientnode,unsigned char *dat,int len);

int main()
  {
  int node;
  char buf[32];

  if(init_blue("devices.txt") == 0)
    {
    printf("FAIL\n");
    return(0);
    }

 if(localnode() == 1)
   {
    buf[0] = 0x12;
    buf[1] = 0x34;
    write_mesh(buf,2);
    sleep(1);
      // wait 3 seconds for reply
    if(read_mesh(&node,buf,32,EXIT_TIMEOUT,3000) != 0)
      printf("GOT reply from node %d = %s\n",node,buf);
    sleep(5);
    write_mesh("D",1);
    sleep(1);
    }
  else
   {
   mesh_server(callback);
   }

  close_all();

  return(0);
  }

int callback(int clientnode,unsigned char *dat,int len)
  {
  int n;
  char buf[32];

  if(dat[0] == 0x12)
    {
    sprintf(buf,"OK from %d",localnode());
    write_mesh(buf,strlen(buf));
    }
  if(dat[0] == 'D')
    return(SERVER_EXIT);
  return(SERVER_CONTINUE);
  }

Thank you for that and I will try that one. But what I did in my setup is I ran the mesh server code in the terminal of all the pis. Then, if I try to run the mesh broadcasting code in any of the pis while the mesh server code is listening, it won't run. Is there a fix for this or it cannot be done?

It sounds like you might be running init_blue twice - this will trigger those errors. It only needs to be run once on program entry.

I tried removing it on the mesh broadcasting code but it throws a segmentation fault error.

I haven't understood the set up. If all the Pis are running as mesh servers (mesh_server has been called and has not returned) how is it possible to run the mesh broadcaster code? - mesh_server has tied up all the devices waiting for packets.

I will implement this in python since I am not familiar with C and I am thinking that it could use multi threading so that it can run the mesh server thread and for example every 5 second the mesh broadcasting  thread will be executed. But I am not sure if that is possible.

OK, it is not possible to run two programs at the same time. The code monopolises the Bluetooth adapter and nothing else can use it - including another thread. It is easy to have a mesh server running and execute other code every 5 seconds. You just need your own custom version of mesh_server as follows.
void my_mesh_server(int(*callback)())
  {
  int nread,retval,clientnode;
  char buf[32];

  mesh_on();

  printf("Mesh server listening (x=stop)\n");
  do
    {
    nread = read_mesh(&clientnode,buf,32,EXIT_TIMEOUT | EXIT_KEY,5000);
    if(read_error() == ERROR_KEY)
      retval = SERVER_EXIT;
    else if(nread > 0)
      {
      retval = (*callback)(clientnode,buf,nread);
      }
    else
      {
      printf("5 seconds\n");
      // 5 second code here
      retval = SERVER_CONTINUE;
      }
    }
  while(retval == SERVER_CONTINUE);
  }

Thank you so much for that!

Hello Sir, I tried using multithreading with python and it worked! I can send and receive simultaneously. Thank you for your repository!

I'm surprised, but that's useful information. Thanks.


Fold "divert" into liferay-theme-tasks

As noted in:
https://github.com/liferay/liferay-themes-sdk/pull/163
This function was duplicated almost verbatim in two packages. Centralize it in "liferay-theme-tasks" as the first step towards unmonorepoization discussed in:
https://github.com/liferay/liferay-themes-sdk/issues/164
Eventually, we might only have two packages:

generator-liferay-theme (needs to be independent, so yeoman can find it).
liferay-theme-tasks (effectively the public "API" of the SDK).

Test plan: yarn test and yo ./packages/generator-liferay-theme (works, apart from expected failure due to us not having published liferay-theme-deps-7.2 to NPM yet).

Note: this one is built on top of https://github.com/liferay/liferay-themes-sdk/pull/163 so it starts with the same two commits. If we merge that one first, then I will rebase this one.

Just started reviewing :)


Mobile nav top spacing bug

The space for the L0 header navigation is still showing on mobile. 2rem of extra space needs to be removed.

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @andreancardona @jdharvey-ibm


Merge Strategy for the USEPA version and Feng's (cancelled) Pull Request

I have recently worked with the CMake files in Issue #7 (https://github.com/OpenWaterAnalytics/epanet-msx/issues/7) in order to compile and run the USEPA version of the repository which can be found on the epa-upstream-1.1.0 branch.
I then used the same strategy to compile and run the code found in Feng's cancelled pull request. In Feng's version of the code, the reports contain additional water quality information at the bottom of the reports. This information includes the water quality mass balance for different chemicals. It details the Initial Mass, Mass Inflow, Mass Outflow, Mass Reacted, Final Mass, and Mass Ratio.
After successfully running Feng's code, I merged it with the USEPA version and fixed all merge conflicts. I favored Feng's version of the code over the USEPA version with the conflicts to make sure not to mess up any of the additional features. I then made sure it could compile and successfully ran examples.
If wanted, I can create a pull request for this code, including the CMake files and I can create a document with compiling instructions specifically for Windows as I have not had the ability to compile this on Mac or Linux.

Sounds like a good approach. I've re-opened and merged the PR so that Feng's commits remain intact in the git history, so hopefully that doesn't throw a wrench in this plan. If you could open a PR into dev branch that adds CMake files any other diffs from the USEPA distributable code, we will be in good shape for getting community input. I think we will especially want to verify the build tooling on Mac and *nix to make sure the project is nice and clean for anyone who wants to pick it up.

given no other comments (thanks to @rjanke20 for the thumbs-up!), we will consider this resolved. All other comments and questions should go to the PR.


fixed method arguments in Q3d

Codecov Report
Attention: Patch coverage is 49.25373% with 34 lines in your changes are missing coverage. Please review.

Project coverage is 76.58%. Comparing base (85bd251) to head (5b11d6f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4544      +/-   ##
==========================================
- Coverage   81.50%   76.58%   -4.92%
==========================================
  Files         110      110
  Lines       53731    53723       -8
==========================================
- Hits        43791    41146    -2645
- Misses       9940    12577    +2637


Tagslong.cs

My BoxCollider Size = (1,1,1)
when MinimumHorizontalOverlap and MinimumVerticalOverlap both set 1f, My UI always shake.

I'd suggest using the Sphere Based Tagalong

closing this in favor of 111


Hakatime 400 Error on Sending Heartbeats

Hey @mujx, thanks for looking into #48. It however appears there's still issues. I am on VSCode 1.61.0:
Version: 1.61.0
Commit: ee8c7def80afc00dd6e593ef12f37756d8f504ea
Date: 2021-10-07T18:10:20.463Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.6.0

and Hakatime 1.6.2 but I am still getting errors. From my .wakatime.log file:
{
    "caller": "/Users/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/run.go:199",
    "func": "runCmd",
    "level": "error",
    "message": "failed to run command: today fetch failed: api error: failed fetching today from api: invalid response status from \"https://hakatime.mydomain.com/api/v1/users/current/statusbar/today\". got: 404, want: 200. body: \"File not found\"",
    "now": "2021-10-10T11:41:06-05:00",
    "version": "v1.27.0"
}
{
    "caller": "/Users/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/run.go:199",
    "func": "runCmd",
    "level": "error",
    "message": "failed to run command: sending heartbeat(s) later due to bad request: bad request at \"https://hakatime.mydomain.com/api/v1/users/current/heartbeats.bulk\"",
    "now": "2021-10-10T11:41:13-05:00",
    "version": "v1.27.0"
}
{
    "caller": "/Users/runner/work/wakatime-cli/wakatime-cli/cmd/legacy/run.go:199",
    "func": "runCmd",
    "level": "error",
    "message": "failed to run command: offline sync failed: bad request: bad request at \"https://hakatime.mydomain.com/api/v1/users/current/heartbeats.bulk\"",
    "now": "2021-10-10T11:44:02-05:00",
    "version": "v1.27.0"
}

And logs from my Hakatime container:

<IP_ADDRESS> - - [10/Oct/2021:11:48:21 -0500] "POST /api/v1/users/current/heartbeats.bulk HTTP/1.1" 400 - "" "wakatime/v1.27.0 (darwin-20.6.0-arm64) go1.17.1 vscode/1.61.0 vscode-wakatime/17.1.0",
<IP_ADDRESS> - - [10/Oct/2021:11:48:21 -0500] "POST /api/v1/plugins/errors HTTP/1.1" 400 - "" "wakatime/v1.27.0 (darwin-20.6.0-arm64) go1.17.1 vscode/1.61.0 vscode-wakatime/17.1.0",
<IP_ADDRESS> - - [10/Oct/2021:11:48:48 -0500] "POST /api/v1/users/current/heartbeats.bulk HTTP/1.1" 400 - "" "wakatime/v1.27.0 (darwin-20.6.0-arm64) go1.17.1 vscode/1.61.0 vscode-wakatime/17.1.0",
<IP_ADDRESS> - - [10/Oct/2021:11:48:48 -0500] "POST /api/v1/plugins/errors HTTP/1.1" 400 - "" "wakatime/v1.27.0 (darwin-20.6.0-arm64) go1.17.1 vscode/1.61.0 vscode-wakatime/17.1.0"

@jimmybrancaccio Are you using the latest wakatime plugin?

@mujx Looks like it. I have v17.1.0 and the Changelog is showing that is the latest version. Is it working for you (assuming you use VSCode and this extension)?

I'm not familiar with VS Code and on my testing I was using the open-source version where the Wakatime plugin is quite outdated. So I'll have to install the official version and debug this issue.

@jimmybrancaccio any news? I got the same error earlier and was curious about it

@vladiiancu This has been fixed. Do you still have this issue on the latest version?

Yes. I had an older version installed. Updated it today. Added the old token but I get the file not found error. Created a new token just in case, same. Gone through the settings, saw some new? ENV variables, made the updates there as well, but no luck

@jimmybrancaccio any news? I got the same error earlier and was curious about it

As @mujx mentioned this was fixed (7 months ago). I don't have the issue anymore. I would suggest creating a new issue in GitHub (you can reference this one if you'd like), and provide as much information as possible in it.


Undo/Redo may be crash

Please consider making a Pull Request if you are capable of doing so.
App Version:
2020.2.2 Develop branch, means all version has the bug.
Affected Device(s):
ViVo x27 with Android 10
Describe the bug
    java.lang.ArrayIndexOutOfBoundsException: length=10; index=-1
        at java.util.ArrayList.get(ArrayList.java:439)
        at com.lightteam.editorkit.feature.undoredo.UndoStack.pop(UndoStack.kt:37)
        at com.lightteam.editorkit.internal.UndoRedoEditText.redo(UndoRedoEditText.kt:119)
        at com.lightteam.modpeide.ui.editor.fragments.EditorFragment.onRedoButton(EditorFragment.kt:616)
        at com.lightteam.modpeide.ui.editor.utils.ToolbarManager$bind$5.onClick(ToolbarManager.kt:129)
        at android.view.View.performClick(View.java:7187)
        at android.view.View.performClickInternal(View.java:7164)
        at android.view.View.access$3500(View.java:813)
        at android.view.View$PerformClick.run(View.java:27649)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:230)
        at android.app.ActivityThread.main(ActivityThread.java:7742)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:508)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1034)

    fun pop(): TextChange {
        // TODO: size must >= 1
        val item = stack[size - 1]
        stack.removeAt(size - 1)
        currentSize -= item.newText.length + item.oldText.length
        return item
    }

To Reproduce
Steps to reproduce the behavior:

Change content of Editor.
Quick click undo or redo button.
May be crash.

Expected behavior
No crash.

It's important to call undoStack.canUndo() before calling this method. Does it really reproducible or you just removed all canUndo checks? 🤔 I've never seen this on my device

It's important to call undoStack.canUndo() before calling this method. Does it really reproducible or you just removed all canUndo checks? 🤔 I can't reproduce it on my device, everything works fine

I fork develop branch, nothing to modified, but when you quickly double click Redo or Undo, it will crash. normal single click, it works fine.

I can not found canRedo() or canUndo() in call strack:
EditorFragment.kt
    override fun onUndoButton() {
        // TODO: The below line not found `canUndo()`
        binding.editor.undo()
    }

    override fun onRedoButton() {
        binding.editor.redo()
    }

It's important to call undoStack.canUndo() before calling this method. Does it really reproducible or you just removed all canUndo checks? 🤔 I can't reproduce it on my device, everything works fine

Reproduce step:

Change text.
Duoble click Undo button *quickly.
Crash  on my device.

When I change the text many times, I want quickly undo, but it crashed.😂😂😂

@liyujiang-gzu Still cannot reproduce 😔
I really don't want to modify UndoStack.pop() because then it will have nullable return type.
Could you modify these methods and check it?
override fun onUndoButton() {
    if (binding.editor.canUndo()) {
        binding.editor.undo()
    }
}

override fun onRedoButton() {
    if (binding.editor.canRedo()) {
        binding.editor.redo()
    }
}

If everything will be fine, then I'll merge your PR into develop

@liyujiang-gzu Still cannot reproduce
I really don't want to modify UndoStack.pop() because then it will have nullable return type.
Could you modify these methods and check it?
override fun onUndoButton() {
    if (binding.editor.canUndo()) {
        binding.editor.undo()
    }
}

override fun onRedoButton() {
    if (binding.editor.canRedo()) {
        binding.editor.redo()
    }
}

If everything will be fine, then I'll merge your PR into develop

A great idea. I think the reason was:
If you click too fast<EMAIL_ADDRESS>was too late to change to false and then click again, so undo / redo cause crash.

I modified the above methods, It‘s works to fine, Clicking too fast will no longer cause a crash

Alright, I'll change it later, but if you want you can make pull request with these changes

I'll PR it later.


Throw an exception when alppaca is not reachable

Coverage decreased (-0.2%) to 72.303% when pulling d61ad959078bb77cd95b85048c016858422f5d91 on transacid:master into bcc3b5a5345807a00ed564b704ff0c896176d02f on ImmobilienScout24:master.

Pull-request number 42


Fix xcodeproj

Summary
This fixes the Xcode project. https://github.com/react-native-community/lottie-react-native/pull/486 broke it — it made this library work only via CocoaPods. This PR fixes it. Unfortunately the upgrade to Lottie iOS v3 also seems to mean iOS 12 is required if you're linking via Xcode project
Test Plan
Create app, link "traditionally" lottie-react-native and lottie-ios, see if compiles
What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅

Checklist

[ ] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

thanks @radex

@radex Could you please explain what is required to make it work on iOS 11 and lower?
Do we need to update readme to reflect it?

@enagorny

Apps that use static Xcode project linking need to set iOS deployment version to iOS 12 or switch to CocoaPods-based linking (using frameworks) or downgrade lottie-react-native to version 2.6.1.

iOS 12 requirement is from lottie-ios v3 when using static libraries -- you can take up the issue there


Fix: Validation does not accept empty string for "*string" property #274

Fix for issue #274. It helps in my case, but I do not know if it is safe for validation mechanics.

@alex.saskevich @asaskevich I have this issue too! Any chance we can get this merged?

I'm facing this issue as well

Hello guys!
I forked this package cause owner disappeared. Hope, he will be back, but it would be easier to merge these changes back if he is back
Link to my repo: create issue there and we'll discuss it.


Closes #1 and plotting script for vtstability

See 14cfab9.

Update the branch to CubicEoSDatabase v0.2.2, where no collisions between eos and physical source parameters.


Add SendGrid Email API Implementation

We currently have an SMTP implementation but need to implement SendGrid Email API as it tends to perform better and is generally excepted by the community.

I have done this before, maybe I can contribute ?


HDDS-3930. Fix OMKeyDeletesRequest.

What changes were proposed in this pull request?

The cache of the key should be updated in ValidateAndUpdateCache, as we return response once after adding to cache, and before DoubleBuffer flushes to disk using OmClientResponse#addToDBBatch.
Changed return type of DeleteKeysResponse, as anyway when success we are not returning delete list and also when failure, we fail complete batch. So we can just return status.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3930
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
Added tests

Thanks @bharatviswa504  for the update. LGTM, +1 from me.

Thank You @adoroszlai for the review.
I have addressed review comments.

Thank You @adoroszlai @xiaoyuyao and @smengcl for the review.


Improve how importing works in NextJS

How we import is overly-complicated and developers will probably be confused as why it's necessary. Lit does not compile correctly serverside so currently code like this is needed:
"use client"
import dynamic from 'next/dynamic';
const Button = dynamic(
  () => import('@getalby/bitcoin-connect-react').then((mod) => mod.Button),
  {
    ssr: false,
  }
);

// Render the Button normally

<Button />

// or to use the API:

<button
  onClick={async () => {
    const launchModal = await import('@getalby/bitcoin-connect-react').then(
      (mod) => mod.launchModal
    );
    launchModal();
  }}
>
  Launch modal
</button>

Referencing https://github.com/getAlby/bitcoin-connect/pull/153
Ideally Button and launchModal can be directly imported and just work.

Can https://lit.dev/docs/ssr/overview/ help?
The issue is "ReferenceError: HTMLElement is not defined" which I believe comes from code in the lit package which is incompatible with NextJS?

Thanks for this ticket! This was (and still is) definitely one of my major pain points when working with bitcoin-connect.


cannot load such file -- dotenv and unable to boot Celluloid during tests

In previous versions of Celluloid (0.16.2 as far back as I've seen it work), requiring celluloid/rspec worked in the following code for running rspec spec https://github.com/Tonkpils/celluloid-eventsource/blob/master/spec/spec_helper.rb#L5
With the latest release of Celluloid (0.17.2), it seems that changes were made to the celluloid/rspec file which caused it to require dotenv which is not part of the gems brought along during bundle install.
That's fine since I could not find documentation which stated that celluloid/rspec should be required for tests. I went on to require celluloid/test and ran into all my specs failing with the error Celluloid is not yet started; use Celluloid.boot
I tried adding a before hook on my spec_helper to run the commands suggested by https://github.com/celluloid/celluloid/wiki/Gotchas#testing with no luck. Is there new documentation which points to how to test with Celluloid?

Hmm, seems that requiring celluloid/test and adding an around hook with
config.around(:each) do |ex|
  Celluloid.boot
  ex.run
  Celluloid.shutdown

seemed to do the trick.

Ran into the same issues. It seems like the Testing wiki page is out of date, and there are surprisingly few google results for testing celluloid 😞
Your around hook didn't work for me, but it seems that you just have to have called Celluloid.boot before any require 'celluloid' calls. So if you do the "standard ruby" thing and requiring files at the top;
some_job.rb
require 'celluloid/current'

class SomeJob
  include Celluloid

  def run
  end
end

something.rb
require 'some_job'

SomeJob.run

something_spec.rb
require 'celluloid/test'
require 'something' # <-- exception here because not booted yet

describe 'something' do
  around(:each) do |ex|
    Celluloid.boot
    ex.run
    Celluloid.shutdown
  end
end

It ends up not working.
I had to boot celluloid momentarily just so it could be required
require 'celluloid/test'
Celluloid.boot # temporarily boot just so celluloid can be required
require 'something' # eventually requires 'celluloid/current' successfully
Celluloid.shutdown # the around hook will re-boot celluloid when needed

That gets my test running anyway... I run into other issues where I can't mock anything on the celluloid class under test, and anything that uses the DB seems to completely not work, only inside rspec but works when run "for real", but that is another fight....


Updates formatting of test doc...

Slight tweaks to Remix setup instructions for clarity.
Uses built-in nav IDs.
Standardizes numbered lists, indented lists.
Marks functions and arguments as code.
General proofreading.
Proper markdown header indentation levels.

See the preview of the rendered markdown on the incoming branch: https://github.com/brookr/nftdelegation/blob/tests-format/Documentation/Sample_Test_Cases.md


Implement patient search by WHO identifier

Fixes #481
Type
Choose one: Regression
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Pull Request Test Coverage Report for Build #298

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 91.456%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/org/smartregister/fhircore/util/Utils.kt
3
96.91%

src/main/java/org/smartregister/fhircore/viewmodel/CovaxListViewModel.kt
5
96.71%

Totals

Change from base Build #292:
0.1%

Covered Lines:
1627

Relevant Lines:
1779

💛  - Coveralls


Fix broken port regex

Fixes #1557.

I'll give it a shot, might take a couple of days.  If the next release will be sooner please let me know.

Closing this since the error was not in the format of the git url, in the end. See https://github.com/sdispater/poetry/pull/1576 for the actual fix.
Thanks for your contribution.


Fix #486 - restore binary compat for inline resource API

Bug number #486
Customer scenario

Internal error when consuming some F# 3.X libraries in F# 4.0 REPL, due to binary compat break.
Compat break was introduced in fix for loc issue #159.  Restoring compat means this bug is now re-introduced.

Fix description
Restore old code in the resource API with the compat break
Do best-effort at keeping localization fix intact where possible

Loc issue is now restricted only to inline functions. The busted resource API was intended for use only by inline functions, but it had crept in to non-inline functions, as well. This is now corrected, so original localization issue is minimized as much as possible.

Testing done Cross-version compiler tests added, covering functions that use these resource APIs

ping @dsyme @enricosada to review.  AFAICT switch to SR.GetString( ... ) in non-inline functions should be safe/correct and maintain localization fix where possible.

Yes, LGTM. Thanks to both of you for your diligence and efforts on this

good job @latkin , didn't think about other functions using old ErrorStrings, LGTM :shipit:

MoreInfo 6/12 by ML Shiproom. @latkin Rollback for next release, full fix for go-ahead repo.

Shiproom has requested that this be scoped purely to rollback of the binary compat issue.  I've removed the partial loc fixes.


Error after updating to 1.6.1

I am running Zwave-JS-ui 1.6.0.  When I updated to 1.6.1, the web ui for zwave JS would not load.
From there, when I went into the addon and restarted it, I got the following error:
Failed to restart add-on
Can't create container from addon_a0d7b954_zwavejs2mqtt: 409 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_a0d7b954_zwavejs2mqtt: Conflict ("Conflict. The container name "/addon_a0d7b954_zwavejs2mqtt" is already in use by container "d89bb24c3664f92612dfa237f5c993e29b78471954149c6f513c4e8a176d049d". You have to remove (or rename) that container to be able to reuse that name.")
I was able to restore 1.6.0 from backup and all is working well again.
Any ideas on how to keep this from happening when I upgrade?

I think the error is self explained but I dunno what could cause that as I don't maintain the addon, @frenck could you help here?

The Docker images for the add-on are hosted on the GitHub container registry. They had a service outage last night, causing these errors. GitHub has restored its services. Everything should be normal again.
../Frenck


Lambda Declare for realz

Still needs to wait for #34

[Current coverage][cc-pull] is 100%

Merging [#88][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #88   diff @@
===================================
  Files           0     0
  Lines           0     0
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits            0     0
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last updated by [ecb6585...f8c59f7][cc-compare]
[cc-base-branch]: https://codecov.io/gh/HighSchoolHacking/GLS/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/HighSchoolHacking/GLS/compare/ecb658571770f61ad7838864cd04f478864fb942...f8c59f75ddf7526a4e71036a88bd6b08cddfb892
[cc-pull]: https://codecov.io/gh/HighSchoolHacking/GLS/pull/88?src=pr

lambda declare :
or
lambda declaration :
?

Heh, good question. I declare is shorter.


Release archive path prefix changed in 1.11 Linux tarballs

curl -fL --silent "https://get.docker.com/builds/Linux/x86_64/docker-1.10.3.tgz" | tar -xvz
x usr/
x usr/local/
x usr/local/bin/
x usr/local/bin/docker

vs
curl -fL --silent "https://get.docker.com/builds/Linux/x86_64/docker-1.11.1.tgz" | tar -xvz
x docker/
x docker/docker
x docker/docker-containerd-shim
x docker/docker-containerd
x docker/docker-containerd-ctr
x docker/docker-runc

it seems it is not an issue. Please close it. It is docker 1.11.* new change

It seems like it's a bug to me. Docker 1.11 introduced new executables, I don't see why that should introduce a different directory prefix in the release archive.

Note the different prefixes: docker/ and usr/local/bin/.

This was intentional, not a bug. The new executables are not all designed to be installed into /usr/local/bin, not that that was ever where people necessarily installed them anyway.

Yes, this was a deliberate change indeed, for example, the install location using the deb / yum packages is /usr/bin, and the decision was made remove the prefix to more clearly leave it to the "consumer" of those packages to decide where to install the binaries. The "docker" wrapper directory was kept to prevent inadvertently polluting the location where the archive is extracted.


Update README.md

For the link to work correctly, you need to specify to which element it will lead

@Serega346 it is not a link though. It's a subheading in a markdown file, so it should be fine 👍


Document Validation on both Validator and FormRequest

When using Validation Rules that touches the databases like unique and exists, one should add the tenant. db connection to correctly check the correct tenant db connection respectively.

Hi! How can I implement this one? I'm confused and tried to put
=> 'unique:connection.tenant,coupons,code'
but this doesn't work. Any help?

@markandrewkato that's supposed to be unique:connection.table,column so in your case, you need to use unqiue.tenant.coupons,code

@bkintanar Got it working. Thank you very much!

@bkintanar can we prioritize a Validation section for the docs that states this behavior?

@luceos of course. 👍


babashka-unwrapped: 1.3.184 -> 1.3.185

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for babashka-unwrapped is: A Clojure babushka for the grey areas of Bash
meta.homepage for babashka-unwrapped is: https://github.com/babashka/babashka
meta.changelog for babashka-unwrapped is: https://github.com/babashka/babashka/blob/v1.3.185/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.185 with grep in /nix/store/xb71wk8gzkbi9japgq2vr1s5fh4x6xiq-babashka-unwrapped-1.3.185
found 1.3.185 in filename of file in /nix/store/xb71wk8gzkbi9japgq2vr1s5fh4x6xiq-babashka-unwrapped-1.3.185

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
babashka
babashka-unwrapped
bbin
neil

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xb71wk8gzkbi9japgq2vr1s5fh4x6xiq-babashka-unwrapped-1.3.185 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A babashka-unwrapped https://github.com/r-ryantm/nixpkgs/archive/c93589755b3ff7c24471ed96e3d08eb894b77315.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c93589755b3ff7c24471ed96e3d08eb894b77315#babashka-unwrapped

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xb71wk8gzkbi9japgq2vr1s5fh4x6xiq-babashka-unwrapped-1.3.185
ls -la /nix/store/xb71wk8gzkbi9japgq2vr1s5fh4x6xiq-babashka-unwrapped-1.3.185/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

babashka
babashka-unwrapped
bbin
neil

Maintainer pings
cc @bennyandresen @bhougland18 @DerGuteMoritz @jlesquembre @thiagokokada for testing.

Yay, glad to see the new updateScript works :tada:


add kmd_tools ros package

This ROS package is particularly useful for extrinsic calibrations.
This also provides code for publishing odometry and pose graphs from the output of past kimera multi experiments - the original purpose was to be able to benchmark new algorithms against previous runs of kimera multi / dpgo in a deterministic way.

fyi @yuluntian - there are many details which i am sure i am not remembering here and are unfortunately undocumented. Perhaps not all of this is useful. If there are specific questions i may be able to help.
Also, i recall that I (1) made the rosbags significantly smaller by replaying and recording the depth topic as compressed and (2) i had a specific data directory structure that may be assumed in some of this code and (3) i think i relied on the output of dpgo logs for some of the functionality in the c++ nodes.
re extrinsics - i think i would only trust acl_jackal and acl_jackal2 as it currently stands. It looks like i made some attempts on the ARL vehicles, but they may not be "high quality". I could not calibrate spark vehicles - something to do with how the data was recorded i think. It's probably worth inspecting the extrinsics using https://github.com/plusk01/lidar2camera

Hello guys! Thanks for the nice sharing.
However, recently, I found that the extrinsics of apis, sobek, and thoth might be wrong, especially lidar-to-camera extrinsics.
Because in cases of Outser OS1-64, the forward direction is -X (see https://static.ouster.dev/sensor-docs/image_route1/image_route2/sensor_data/sensor-data.html),
so each rotation matrix in the extrinsic should be similar to
[0 1 0
0 0 -1
-1 0 0].
However, those are set like
[0 -1 0
0 0 -1
1 0 0]
, which are mostly correct if the sensor is Velodyne types.
I was not here when you guys did experiments, so feel free to let me know what I'm supposed to do to fix the extrinsic issues.

And @plusk01 , I tried to fix this calibration issue, so follow the calibration github https://github.com/plusk01/lidar2camera. However, it did not show anything :(.
roslaunch lidar2camera manual_calib.launch camera:=/apis/forward/color points:=/apis/lidar_points
(in another cmd)
roslaunch lidar2camera projection.launch camera:=/apis/forward/color points:=/apis/lidar_points

The only message that I could see is as follows:
Warning: TF_OLD_DATA ignoring data from the past (Possible reasons are listed at http://wiki.ros.org/tf/Errors%20explained) for frame apis/base (parent apis/realsense_base) at time<PHONE_NUMBER>.067386 according to authority unknown_publisher
         at line 278 in /tmp/binarydeb/ros-noetic-tf2-0.7.7/src/buffer_core.cpp

I found that the extrinsics of apis, sobek, and thoth might be wrong, especially lidar-to-camera extrinsics.

yeah, this is because

I could not calibrate spark vehicles - something to do with how the data was recorded i think

regarding the rviz/tf errors, that is probably something to do with ros on your computer, maybe something related to timing / use_sim_time, or there are some frames not set up correctly - try looking at rqt tf tree visualizer


[AIRFLOW-1237] Fix IN-predicate sqlalchemy warning

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following

AIRFLOW-1237 Fix IN-predicate sqlalchemy warning

Description

[ ] Here are some details about my PR:
Getting rid of the following warning from sqlalchemy:

/home/travis/build/apache/incubator-airflow/.tox/py27-cdh-airflow_backend_mysql/lib/python2.7/site-packages/sqlalchemy/sql/default_comparator.py:161: SAWarning: The IN-predicate on "dag_stats.dag_id" was invoked with an empty sequence. This results in a contradiction, which nonetheless can be expensive to evaluate.  Consider alternative strategies for improved performance.

Tests

[ ] All existing tests pass.

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2320 into master will decrease coverage by 0.32%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2320      +/-   ##
==========================================
- Coverage   69.48%   69.15%   -0.33%
==========================================
  Files         144      144
  Lines       11028    11024       -4
==========================================
- Hits         7663     7624      -39
- Misses       3365     3400      +35

Impacted Files
Coverage Δ

airflow/models.py
86.98% <100%> (-0.13%)
:arrow_down:

airflow/executors/sequential_executor.py
50% <0%> (-50%)
:arrow_down:

airflow/executors/__init__.py
56.09% <0%> (-4.88%)
:arrow_down:

airflow/www/app.py
94.11% <0%> (-2.36%)
:arrow_down:

airflow/utils/dag_processing.py
85.36% <0%> (-1.22%)
:arrow_down:

airflow/jobs.py
73.49% <0%> (-1.02%)
:arrow_down:

airflow/configuration.py
83.33% <0%> (-0.48%)
:arrow_down:

airflow/www/views.py
67.82% <0%> (-0.29%)
:arrow_down:

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 d165377...f220ed6. Read the comment docs.


NTR sent to ENVO: transportation device

See:
https://github.com/EnvironmentOntology/envo/issues/230

Most request terms added


Allow to pass callables to EventHandler (not only Closure)

@dlondero please review

@tomaszdurka please apply CS

Hmm? Codestyles? I think they are fine.

@dlondero please take a look again, thanks.

@tomaszdurka lgtm


Docs: incorrect checkbox value check

It's not impossible I'm missing something, but isn't this code incomplete and thus broken?
https://github.com/vuejs/test-utils/blob/main/docs/api/index.md?plain=1#L1694
wrapper.find('div') will return a DOMWrapper, not a boolean, right?
Looks like it's been like that for years. It's the only reference for how to check the value of a checkbox, though.
There's also a reference to element.checked, but TS flags that the property doesn't exist on VueNode. Of course, it probably just needs to be casted. (The docs should probably say something about that, for those new to TS.) For me, I prefer to check with the docs for correctness before just forcing Typescript to be tautologically correct. The lack of actual docs on the expected way to check this value really slowed me down today.

Yeah, it doesn't look correct. It should probably be expect(wrapper.find('div').exists()).toBe(true).
Would you mind opening a PR to fix this? (it's probably the same in the french version of the docs).
To check if a checkbox is checked, you can use expect(wrapper.get('input').element.checked).toBe(true);. I don't think you need a cast to make it work though.

Hi, I've submitted a PR #2495 that addresses this issue. Could you please review it when you have a chance?
https://github.com/vuejs/test-utils/pull/2495


clicking outside modal(apart from gray area) closes the modal

We have a trigger for modal and it gets closed when we click somewhere apart from gray area in the page.

If you had followed the issue template, we would know what browser and operating system you're referring to, steps to reproduce, etc. The functionality you describe does not exist, the px-modal does not dismiss when a user clicks on the gray area, it can only be dismissed by clicking one of the buttons.

we have a left nav bar and top header, if we hover over there it closes. refer the screenshot

I still think this must be a customization of your application, as the only mechanism that px-modal has for hiding itself is if an element with class modal-trigger is tapped, or if the modalButtonClicked method is called on the px-modal. Does your application use app hub / pxh-chrome?


How use relationships

Hi!
How use relationships in admin panel?
For example: if I use model Projects and use Project_cats, How add project_cat in my project in field select?

Need some relation type

in Project_cats model:
public function project()
{
return $this->hasMany('App\Projects');
}
in Projects model:
public function categories()
{
return $this->belongsToMany('App\Project_cats');
}

@IvanBohonosiuk there is no way for now to use relationship unless you override the projects route and use your own controller:
on routes/web.php add this:
Route::resource('admin/projects', 'ProjectController');

Then create a new ProjectController.php to your app/Http/Controllers. You can copy VoyagerBreadController.php to your controller and edit it.
Don't forget to define VoyagerServiceProvider above AppServiceProvider so it will use web.php instead of voyager routes.php
on config/app.php:
        /*
         * Package Service Providers...
         */

        // Voyager Service Providers
		TCG\Voyager\VoyagerServiceProvider::class,
		Intervention\Image\ImageServiceProvider::class,

        /*
         * Application Service Providers...
         */
        App\Providers\AppServiceProvider::class,
        App\Providers\AuthServiceProvider::class,
        // App\Providers\BroadcastServiceProvider::class,
        App\Providers\EventServiceProvider::class,
        App\Providers\RouteServiceProvider::class,


Add CODEOWNER to smart contract tutorials

I want to make sure that this content is roughly correct anytime it gets updated.
If the changes are small feel free to merge without my approval, I don't want to be a
gatekeeper.
I can always open follow-up issues or PRs if I see that something is off.
@cmichi @SkymanOne let me know if you also want to be on here

Sure. I'm happy to keep an eye on it too.


Enhancement of Moksh Trademark

Before creating an issue, go through all open/closed issues to avoid getting your issue/suggestion marked as duplicate##
If we see the Trademark moksh icon it is getting slightly outside the blue area .
Issue and Steps to Reproduce:
If we see the second image ,I have given margin-bottom of 15 px, then it is getting inside the blue area
Screenshots:

Expected:

Actual:
Additional Details:

Hey @kumarankit999  I can Come Up With new Enhanced UI for the Moksh Trademark please Assign it to me Under GSSOC'23

Assigning @kumarankit999 Proceed

Please assign this issue to me under ssoc.

Please assign this issue to me .

Hello @Rakesh9100, I saw your complete website it delivers a great message and is beautifully designed. But as every art has some flaws your website do also have some of them... Here I can easily fix them and make them even good looking and functioning. I request you to assign this to me for one of the best results.
Thank You.

Is this issue still open? If so, then I can try to fix it


Check for p2p xp, not just p2p lvls in isF2p function

This function was returning true if a player had xp in a p2p skill but didn't have lvl 2, ex 50 thieving xp.

good call


Better Directory Input & Game Object based Lip Syncing

1. Enhanced Directory Wizard
The existing wizard has a significant limitation: It only reads the children of a specified directory without replicating that directory's structure in the output.
This oversight forces users to manually sort their baked data to match the hierarchy of the original audio clips, which is inefficient, prone to errors, and if your line count is high enough may lead to death from dehydration because of how long sorting them would take. My alternative wizard addresses this issue by cloning the directory hierarchy from input to output, ensuring that the structure of subfolders and their contents is preserved.
2. Game Object-based Lip Syncing for 2D Rigs
I noticed a very noticeable gap in the current toolset for 2D lipsyncing, particularly for rigs that aren't sprite sheet-based (Believe it or not that's every single rig I use). uLipSyncTexture falls short in this case. One of Unity's only features that actually "just works" is the PSB import pipeline, which automatically slices sprites based on their boundaries, resulting in varying origins and sizes that aren't easily swappable. It also mirrors the layer structure when dragging the imported PSB into the editor. Therefore, all of your phonemes will already exist as individual game objects. So I created uLipSyncGameObject which is functionally similar to uLipSyncTexture, but works by just enabling and disabling the objects instead.
I love this tool, so I hope these are useful additions.

Thank you for the fantastic PR! I aim to review and integrate it as soon as possible. However, I might not have time in the immediate future, so it could take up to a month. I appreciate your patience. Additionally, since there are two updates included, it would be smoother to review if you could separate them into individual PRs.


refactor — bash specific changes

adding - to EOF allows for quoting and ignores escape sequences; also changed to USAGE

$BASH_SOURCE is a BASH specific variable that reads absolute directory name

integers in BASH are better handled with == integer operator within (()) arithmetic expansion

[[]] double braces in BASH handles automatic quoting & more powerful options, like regex with the =~ operator

dropped a function, changed __fatal to __out — if x is specified as second argument, has the same behavior; if second argument is empy __out prints like [Pass]: <output>

changed some if statements to ternary for readability

broke some long lines & realignment

These changes are untested but I mostly made syntactical changes to wondeful bashisms

Hey, I appreciate the PR! That's quite a refactor, but I'm not sure I agree with many of the proposed changes.

adding - to EOF allows for quoting and ignores escape sequences; also changed to USAGE

Maybe I'm mistaken, but I thought the - sign made it ignore leading tabs, so you don't have to break indentation levels. Also, I personally prefer EOF as the heredoc marker.

$BASH_SOURCE is a BASH specific variable that reads absolute directory name

In this case, I specifically want $0. Reason being, if the script is installed the way I suggest in the readme and invoked with pac, $0 returns "pac", whereas $BASH_SOURCE would return the path to the symlink.

integers in BASH are better handled with == integer operator within (()) arithmetic expansion
[[]] double braces in BASH handles automatic quoting & more powerful options, like regex with the =~ operator

I know this is not obvious from the script, but I'm trying to avoid Bashisms unless necessary. I actually tried to write the script as POSIX sh-compatible at first, but got stuck with some things. I'm still keeping that in mind as goal, though. Should probably add a to-do list to the readme.

changed some if statements to ternary for readability

I'm not so sure readability is improved. Also, shellcheck flags those lines as problematic - apparently a && b || c is not the same as if a then b else c. See https://www.shellcheck.net/wiki/SC2015

That's alright. Those are quick changes I did on my phone without even testing. Personal prefrence is always a fine line.
Instead of a symlink, you could use an alias or just put the script in $PATH. I typically stick to BASH specifics just due to speed. Running subshells is extremely slow. I would not recommend using the BASH shebang if you are wanting to write in POSIX. Some users don't have BASH and that will cancel your script entirely. If that system just has plain sh, dash, zsh or whatever else, it will not run. BASH is meant to be very BASH and that's why dylanaraps rewrote Neofetch to pfetch
As you know, I am all about BASH. I think POSIX is a joke considering 90% of systems do have BASH, or they can get over it and install it, because it is the best modern shell.  I get compliments on the code all the time and it doesn't break as often as something like pfetch does. Also ternary operators are an and, or statement, instesd of an and, else. So it's really case specific

I like Bash too, but I wanted to challenge myself to try and keep portability in mind, and this script, being barely more than a bunch of aliases, seemed like a good project for that. If I do rewrite it in pure POSIX sh, I'll change the shebang; if it turns out to be more trouble than it's worth, then I won't :)

That's cool you're working to achieve a POSIX script anyway. BASH and POSIX have two different goals and I got a little confused when I saw the shebang, I shouldn't have assumed. I think the way your script is wrote currently is pure sh and you could likely benefit portability now since sh is just a symlink to the systems default shell or else bourne shell. It looks good though and I like the idea — like a reverse Pacapt. I apologize if I came off rude earlier, I did try shellcheck since you mentioned it and I think it did clean up my script a bit and provide some nice information

@IndrekHaav Just in case you made this for self-use, I've made a package manager wrapper for several different package managers/helpers, which is based on Debian's apt style. It's called pkg, so it runs like pkg on Termux and can replace that as well. Made it to take several different arguments, e.g. -d, delete, remove, uninstall just for removing a package. It will run yay over pacman if found and also works for winget on Windows as well


[VideoTranslation] Update client sample code readme.md.

Purpose

...

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

/azp run


KOGITO-5480 Reorganized seed jobs & trigger automatically

https://issues.redhat.com/browse/KOGITO-5480
Related PRs:

https://github.com/kiegroup/kogito-pipelines/pull/206
https://github.com/kiegroup/kogito-runtimes/pull/1429
https://github.com/kiegroup/optaplanner/pull/1416
https://github.com/kiegroup/kogito-apps/pull/928
https://github.com/kiegroup/kogito-examples/pull/778
https://github.com/kiegroup/kogito-images/pull/575
https://github.com/kiegroup/kogito-operator/pull/929
https://github.com/kiegroup/rhpam-kogito-operator/pull/53

Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've ran make before-pr and everything is working accordingly
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

@radtriste feel free to merge, I'll not merge it since I don't know if there is any dependency/pr that needs to be merged first (same for kogito-images).

@spolti this can be merged without dependency. It will be used later by https://github.com/kiegroup/kogito-pipelines/pull/206 once that one is ready ;)

ok :)