Revert "ace: mm: tlb: Check tlb translation enabled before flushing cache"

This reverts commit 311ddf90e297631c640aea2616fa501486399614. That commit breaks firmware boot on both MTL and LNL.

https://sof-ci.01.org/sofpr/PR9455/build8033/devicetest/index.html
https://sof-ci.01.org/sofpr/PR9455/build8034/devicetest/index.html

I have checked on our mtl fpga test platforms and the firmware boots successfully using sof/main + zephyr/main. Is there any overlay being used? In particular the debugging options like:
CONFIG_ZTEST, CONFIG_SOF_BOOT_TEST, CONFIG_DEBUG or CONFIG_ASSERT? I will check on rvp tomorrow.

ACK. Activating the CONFIG_ASSERT option actually break firmware loading. It seems that somewhere we trying to unmap an memory address that is not mapped. After my fix the function returns an appropriate error code. In my opinion we should look for the cause and not treat the effect by reverting my commit.

testing with https://github.com/thesofproject/sof/pull/9455

ACK. Activating the CONFIG_ASSERT option actually break firmware loading. It seems that somewhere we trying to unmap an memory address that is not mapped. After my fix the function returns an appropriate error code. In my opinion we should look for the cause and not treat the effect by reverting my commit.

@softwarecki sorry, which your fix? I don't see any open PRs from you for Zephyr ATM?

@lyakh The one you're trying to revert in this PR. It causes the sys_mm_drv_unmap_page_wflush function to return an error code when trying to unmap a memory page that is not mapped. This error is probably detected by unmap_locked or sys_mm_drv_unmap_region_initial and the firmware stops at assert. I think we should stop trying to unmap an unmapped memory instead of throwing the error checking code away.

@softwarecki Ack a fix is preferred, but time is of essence here as well. Let's go with standard procedure. If you can fix the MTL/LNL boot assert issue quickly, please submit ASAP, or if not, let's merge this revert PR and @softwarecki you submit the original patch again later with the updates to avoid panics with asserts. This is currently blocking all Zephyr updates to SOF mainline, so we need to address this quickly to not block other developers why this issue is addressed for Intel.

@kv2019i I will create a PR with the fix right away.

I will block it as fix is proposed in #78612

@softwarecki have you also submitted a SOF PR to test your fix?


Added the captured exception to retry_context

Codecov Report

Merging #376 into dev will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev     #376      +/-   ##
==========================================
+ Coverage   86.04%   86.05%   +<.01%
==========================================
  Files          56       56
  Lines        4343     4346       +3
  Branches      464      464
==========================================
+ Hits         3737     3740       +3
  Misses        460      460
  Partials      146      146

Impacted Files
Coverage Δ

...orage-common/azure/storage/common/storageclient.py
91.24% <100%> (+0.12%)
:arrow_up:

...zure-storage-common/azure/storage/common/models.py
90.74% <100%> (+0.05%)
: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 769868f...6a6bcda. Read the comment docs.

Codecov Report

Merging #376 into dev will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev     #376      +/-   ##
==========================================
+ Coverage   86.04%   86.05%   +<.01%
==========================================
  Files          56       56
  Lines        4343     4346       +3
  Branches      464      464
==========================================
+ Hits         3737     3740       +3
  Misses        460      460
  Partials      146      146

Impacted Files
Coverage Δ

...orage-common/azure/storage/common/storageclient.py
91.24% <100%> (+0.12%)
:arrow_up:

...zure-storage-common/azure/storage/common/models.py
90.74% <100%> (+0.05%)
: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 769868f...6a6bcda. Read the comment docs.


docs: add esp-hal

I can also add some examples if you think that is a good idea, but I don't want to add any maintenance burden in doing so; of course, I am more than happy to maintain the examples myself.

bors r+

Adding a "dummy" embassy-esp directory feels a bit strange. I think the note in the top-level README should be enough.

Thanks!


Use paketo

Thanks for submitting this PR!
When trying your branch, I get the following error, any thoughts?
spring-cds-demo (use-paketo =)$ ./gradlew bootBuildImage
Starting a Gradle Daemon (subsequent builds will be faster)

> Task :bootBuildImage
Building image 'docker.io/library/spring-cds-demo:1.0.0-SNAPSHOT'

 > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' ..................................................
 > Pulled builder image 'paketobuildpacks/builder-jammy-base@sha256:3607951929167c3f76294ca29ef8cb3a5b4141eca72834e889c10ffe294f0d2a'
 > Pulling run image 'docker.io/paketobuildpacks/run-jammy-base:latest' ..................................................
 > Pulled run image 'paketobuildpacks/run-jammy-base@sha256:50e96b1e8ae6ac02afd38d8e9285b5344d1f8a37698cf3442857bcf8849133ef'
 > Pulling buildpack image 'docker.io/anthonydahanne/java:app-cds' ..................................................
 > Pulled buildpack image 'anthonydahanne/java@sha256:ae2b1d3e3f440f03624e3482894278be15d4ca7f2c17701cfc51d2b7c0b5459c'
 > Executing lifecycle version v0.18.4
 > Using build cache volume 'pack-cache-a11332224717.build'

 > Running creator
    [creator]     ===> ANALYZING
    [creator]     Image with name "docker.io/library/spring-cds-demo:1.0.0-SNAPSHOT" not found
    [creator]     ===> DETECTING
    [creator]     ERROR: failed to initialize detector: open /cnb/buildpacks/paketo-buildpacks_java/{{.version}}/buildpack.toml: no such file or directory

> Task :bootBuildImage FAILED

FAILURE: Build failed with an exception.

The error is due to https://github.com/spring-projects/spring-boot/issues/39323. For people like me using Docker engine 25 (Docker Desktop latest Mac version uses it), it is fixed by using Spring Boot 3.2.3-SNAPSHOT.

Superseded by 736c60dfb7f1ca3ffe8d4d5f1018475513770eba.


Rank up on Extra Channels doesn't let me get the 10th rank

Small problem - for some reason, Extra Channel (and possibly other feats) are restricted to 9 ranks in the party editor when it's possible for it to reach up to 10 ranks. Might be best to switch to the system in Bag of Tricks where you could keep clicking to add ranks to the features, to be honest, rather than the current 'Add/Remove' system.

This is fixed in 1.1.3


7+ Taskbar Tweaker v5.9.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

PR fails because the rename deleted the old file..

think the new PR will fix the issue


System.IndexOutOfRangeException: Index was outside the bounds of the array. (in v3.0.272)

Go to load the save file 5 as instructed and the error pops up

3.0.272 is very old. Please try with the latest version
On Sun, Dec 19, 2021, 11:56 AM rintongci @.***> wrote:

Assigned #123 https://github.com/mburbea/koar-item-editor/issues/123 to
@mburbea https://github.com/mburbea.
—
Reply to this email directly, view it on GitHub
https://github.com/mburbea/koar-item-editor/issues/123#event-5789330485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUB4K7ZUZ2URSZDNAU72LURYFFVANCNFSM5KMCHRVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***>

Just to let you know I thought it was the latest version I was using. I
downloaded it on Nexus primarily
On Mon, 20 Dec 2021, 20:12 Michael Burbea, @.***> wrote:

Closed #123 https://github.com/mburbea/koar-item-editor/issues/123.
—
Reply to this email directly, view it on GitHub
https://github.com/mburbea/koar-item-editor/issues/123#event-5795016069,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW7MAT2M46WPY5HDZ3ZQTFLUR6E37ANCNFSM5KMCHRVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, I updated the one for the remaster. That link is for the original game. The remaster nexus link is here:
https://www.nexusmods.com/kingdomsofamalurrereckoning/mods/8
I don't test any more with the original game, so I don't know if my changes work in the OG game anymore.


Missing module "ext"

Hi. I pulled the development version tonight. Is this the right way to get the latest quokka? I don't mind if it's broken sometimes, that's how I hope to help you. I am just wondering if that's the best way to do it. Obviously I dont want python3 do I? what about master? Comparing the three none look very active lately. Anyway my googling isn't helping me with the following error I am getting because python and ext come up with too many results. I pulled the latest development version like I said, started new. Then replaced "static" "themes" local_settings.py" "settings.py" and "mediafiles" with my backup ones. But quokka wouldnt start. I was getting the error module "ext" not found. Like I said googling wasn't helping so I figured out on my own the "ext" folder was missing from inside "/home/mike/quokkaenv/quokka/quokka" after comparing the new quokka files with my backups. Why was that folder missing? How do I get it, is it a package? Lastly whats the best command to run using manage to upgrade?   Thanks!

I don't know what happened but I pulled it again and the ext folder is there. I must have deleted it fumbling at the command line moving my backups into it. Probably wasn't paying attention and deleted a folder, but also that one. the ext problem is fixed but ill leave this issue open so hopefully I can get an answer to those few questions I had.


connect leaks Coroutine on subsequent reconnects (Android)

Characteristic changes are forwarded from the Callback to the Observers via launchIn(scope) but the Coroutine is never cancelled.
https://github.com/JuulLabs/kable/blob/d9ff2cef685cf2a9bd2b1584c58398bcdd0537c5/core/src/androidMain/kotlin/Peripheral.kt#L175-L178

I may have misunderstood overlooked that upstream the Channel is closed, and thus: this launched Coroutine should terminate when the upstream Channel closes (which is triggered via a disconnect event in the Android Callback).
tl;dr this may not be a bug at all.

Confirmed that this is not a bug. In #193 the completion of this flow is relied on for observation handling. Testing of SNAPSHOTs produced from #193 confirmed that (as identified in https://github.com/JuulLabs/kable/issues/139#issuecomment-975004651), the flow is terminated upon disconnected signal in Android's BluetoothGattCallback.


[UNDERTOW-1546] Upgrade jboss-parent pom version to 35

Jira: https://issues.jboss.org/browse/UNDERTOW-1546

This is ok to test

Retest this please

Retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please


Assign account per folder

It would be nice if we could assign different accounts to different directories for dealing with different projects where each is on a different account.

FYI, i added the following lines to my .zshrv:
`set-heroku-account() {
local heroku_account_setting_path=".heroku_account"
if [ -f "${heroku_account_setting_path}" ]; then
local heroku_account="$(cat "${heroku_account_setting_path}")"
echo "Using heroku account ${heroku_account}"
heroku accounts:set $heroku_account

fi
}
add-zsh-hook chpwd set-heroku-account
set-heroku-account`
Now, adding a '.heroku_account' in a folder, containing the account I want to use, makes my bash switch automatically


✨ feat: exposed .getGraphemeLength (#972)

Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for new/updated/fixed functionality.
[ ] I have updated/added dartdoc comments with ///.

Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Related Issues

Codecov Report

Merging #972 (831e3af) into main (7bd1d02) will increase coverage by 5.88%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #972      +/-   ##
==========================================
+ Coverage   79.35%   85.24%   +5.88%
==========================================
  Files         282        5     -277
  Lines        3551      122    -3429
==========================================
- Hits         2818      104    -2714
+ Misses        733       18     -715

see 277 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature request: Automatic spider

Hi, thanks for this great tool!
It would be great if ezXSS can automatically spider an entire app after the XSS is triggered. This works adding a hidden iframe and scanning the target page for all hyperlinks with the same domain. Then for each found URL, fetch it via XHR in the iframe and extract all response data / screenshot it like a usual target page.
The advantage of this is that an attacker can gain immediate insight in all URL's and pages that are available in for example an admin panel.
If this is something to consider including, I have working code available from our own tooling.

Hey Dick,
Thanks for the feature request. This for sure sounds like something we can add. I would love for you to share the working code and possibly some ideas how to implement this in ezXSS.
I can then look myself what would be the best way to implement this in the current system.

@ssl great, I'll get back with some example code after my holidays!

Hey @dicksnel! Hope you had a good holiday. Is this FR still something you would like to see in ezXSS? Let me know so I can implement it :)


release: 0.13.0

Do not merge
TODO:

[ ] Pull lua-resty-healthcheck version bump
[ ] Changelog
[ ] Upgrade path
[ ] Meta bumps

Two hotfixes cherry-picked from master since 0.13.0rc2: 0.13.0rc2...release/0.13.0
Rebase on top of next before merging into next.

@hishamhm It seems like a16537c2e8cb63482e562c2c8e917284c68ecf35 forgot to update the spec-old-api version of the test

It seems like a16537c forgot to update the spec-old-api version of the test

@thibaultcha fixed!

For now, waiting on #3324 for the CI to pass on this branch.

:tada:


Home gihub/master

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

hello, these are some small compatible changes for Yocto Project 3.2 release, code-named gatesgarth. This is build-only tested.

Acked-by: Martin Jansa<EMAIL_ADDRESS>

Thank you for prodding me on the new compat.  And I will need to remove zeus on master since python versioning changed. much housekeeping to do.


Bot will not launch or update correctly.

The update.bat keeps coming up with this 'Command "python setup.py egg_info" failed with error code 1 in C:\Users\grend\AppData\Local\Temp\pip-build-luvbgq14\cffi'

Please provide a full traceback

Alright here you go.

Please install python to path


Fs 1122 discovery bug

Fixed a bug - a function was accidentally returning local data...

@SentientHousePlant Looks like a test is failing, looks like the unit tests are trying to reach the remote host?


Setting up xdebug for PHP.

Hi.
I've been using docker for mac, but found it way too slow for development. It's been a revelation using dinghy! Straightforward to use. I can't seem to find documentation on how to setup xdebug though. It works when I use docker for mac but when I switch to dinghy it does not. Maybe some proxy professional can help me out. :)
Any help, much appreciated. Thanks.
JJ

Nevermind. It's a mac osx issue.


[Doc]: BNB 8 bit quantization is undocumented

📚 The doc issue
BNB 8 bit quantization is apparently supported as of https://github.com/vllm-project/vllm/pull/7445, but there is no detail on how to load in 8 bit on the BNB documentation page
Suggest a potential alternative/fix
Give an example of using load_in_4bit/load_in_8bit on the documentation page
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Indeed, please feel free to contribute this. Thank you very much!

@jeejeelee I actually am unsure about the usage myself. I was hoping someone could help me out with that. I've seen the PR where 8 bit was introduced,but wasn't able to which arguments I must change while calling LLM().

I did request the author of the PR for clarification https://github.com/vllm-project/vllm/pull/7445#issuecomment-2504063814

IIUC,  you don't need to set the specific argument (see:https://github.com/vllm-project/vllm/blob/main/tests/quantization/test_bitsandbytes.py#L24),  like :
llm = LLM(
    model=model_name,
    trust_remote_code=True,
    load_format="bitsandbytes",
    quantization="bitsandbytes",
)

@jeejeelee the code you shared works to give an 8-bit quantized BNB model when the model_name (model ID or path) corresponds to a 8 bit already BNB-quantized checkpoint.
But, as described in the docs, vLLM supports in-flight quantization, which takes the base full precision model ID and returns the 4-bit BNB quantized model. To achieve this you run the same code from your comment but give a full precision model path.
This is also supported in HuggingFace, which on the other hand, does the in-flight BNB quantization using load_in_4bit/load_in_bit arguments (see here) from the base checkpoint.
vLLM's own BitsAndBytesConfig class  has load_in_4bit/load_in_8bit flags present, but it is unclear how we pass these in while calling LLM().
The definition of the LLM class has no such information. It only takes one-related argument (quantization).

Currently, vLLM only supports 4-bit  for in-flight quantization, see: https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/model_loader/loader.py#L997.
vLLM's load_in_4bit/load_in_8bit arg are used for pre-quantization(at least for now). In general, they are obtained from the model's configuration file,see: https://huggingface.co/openbmb/MiniCPM-V-2_6-int4/blob/main/config.json#L28

Should I close this then?

Could you please  submit a PR to clarify in the documentation that inflight quantization only supports 4-bit quantization? thanks very much

The documentation does say that.

There is currently no support for Inflight 8bit quantization.


Add missing images for bar chart tests

I noticed that there was missing images for 64 bit @3x and 32 bit @2x causing the tests to fail when I would run them.

From looking at generated images testHideLeftAxis, testHideLeftAxisGridlines, testHideRightAxis, testHideRightAxisGridlines I wonder if those tests are actually work as expected? Those images seem to be equivalent to me while I was expecting some changes on them. Or am I missing some details?

No they are correct it is just the names that are confusing. testHideLeftAxis for example just hides the line that borders the graph. I'll update the tests to make more logical sense.

OIC. Thanks!


MSID: 92805 Version: 1 DOI: 2<IP_ADDRESS>3835

"msas": "Neuroscience"
"msid": "92805"
"preprintDoi": "10.1101/2<IP_ADDRESS>3835"
"Reviewed Preprint posted": "2023-12-18"
"Sent for peer review": "2023-10-24"
"Posted to bioRxiv": "2023-10-29" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>3835v1/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92805)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/92805/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3835)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/92805/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/92805)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/92805

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/92805

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/92805/v1/92805-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/92805)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

elocations missing from the references


Version 2 examples are needless complex

 Issue by ramondeklein
Monday Jan 02, 2017 at 11:01 GMT
Originally opened as https://github.com/gsscoder/commandline/issues/389

This module was a great module in v1 to deal with commandline options. The new version doesn't have any documentation and the examples are so complex that it's easier to deal with commandline options the old-fashioned way. Please provide some form of documentation, add comment to the examples or make the API more logical again. Why do we need such a complex way to deal with commandline options?

 Comment by nemec
Tuesday Jan 03, 2017 at 03:38 GMT

Have you seen this documentation from the wiki? https://github.com/gsscoder/commandline/wiki/Latest-Version

 Comment by ghost
Saturday Jan 28, 2017 at 17:24 GMT

Not a single example is complete.


Support for mongo transactions

Check please support for mongo transactions. Related to feature request #706
import Post from './post'
import User from './user'
import { MongoInternals } from 'meteor/mongo';

let post = Post.find(postQuery);
let user = User.find(userQuery);

post.userId = user._id;
user.posts.push(post);

const { client } = MongoInternals.defaultRemoteCollectionDriver().mongo;
const session = await client.startSession();
await session.startTransaction();
try {
  post.save({session});
  user.save({session});
  await session.commitTransaction();
} catch (e) {
  await session.abortTransaction();
} finally {
  session.endSession();
}

This feature would be great!!! Is there any ETA for this?

Hey, unfortunately I no longer actively develop this package. I only do bug fixes. Nowadays, there is less need for packages like this. Feel free to fork Astronomy or use custom local build with this feature merged.
Imho Meteor is not a nice option anymore, and soon it will be dead in terms of the new projects picking it as the main technology. It looks like even MDG focused their full power on Apollo. At work, I've stopped using Meteor a few years ago and I don't regret. As application grew the reactive nature of it caused more and more trouble and I feel more comfortable creating my own stack where I control every aspect of it. Also the development of Meteor stagnated. Even the 2.0 release doesn't introduce any deal breaker changes (at least from what I know).


[tlul] Correct width for secded encoder in tlul_adapter_reg.sv

I think this was missed from commit 4a7399f (and causes lint errors).

thanks! i had this in one of my other PRs also, but let's get this merged first.


Add xIMX: Staked IMX

[X] I understand that token listing is not required to use the Polygon Wallet with a token.

Please provide the following information for your token.
Token Name: Staked IMX
Token Symbol: xIMX
Decimals: 18
Polygon Address: 0xff52775de813d060aa5854657055fb19b3a3dda5
Ethereum Address: 0x363b2deac84f0100d63c7427335f8350f596bf59
Logo URI:
Project Name: Impermax
Project Summary: Leveraged yield farming protocol
Project Contact: https://twitter.com/ImpermaxFinance
Project Website: https://www.impermax.finance/
Mainnet/Testnet: Mainnet
Additional Notes:

Please provide the logoURI.


Unable to open Drop-in of Adyen

Adyen libraries dependency throwing error in react native
Steps to reproduce the behavior:

Go to Login
Click on adyen button
Scroll down to Adyen screen,click on Drop in Button
See error

Expected behavior
Adyen Drop-in page should be opened.
Screenshots
Error:
Attribute data@scheme at AndroidManifest.xml:45:51-85 requires a placeholder substitution but no value for  is provided.
ERROR  TypeError: Cannot read property 'config' of undefined.
ERROR  TypeError: start is not a function (it is undefined), js engine: hermes
Desktop (please complete the following information):

OS: ios

Additional context
Add any other context about the problem here.

Hey @rahulystl

Go to Login ... Click on adyen button

I am not sure what is this description.

Attribute data@scheme at AndroidManifest.xml:45:51-85 requires a placeholder substitution but no value for is provided.

OS: ios

Is it iOS or Android?
Why do you believe this error related to our SDK?


Bug: TinyProxy is refusing connections

What VPN service provider are you using?

[X ] PIA
[ ] Mullvad
[ ] Windscribe

What's the version of the program?

Latest

What are you using to run the container?

[ ] Docker run
[x ] Docker Compose
[ ] Kubernetes
[ ] Docker stack
[ ] Docker swarm
[ ] Podman
[ ] Other:

What's wrong? (please share some of your logs, and maybe configuration)

TinyProxy is refusing connections.  I went back to the release tagged as rename-encryption and it worked again: Running version rename-encryption built on 2020-03-26T11:58:15Z (commit 38fb859).  I don't really see anything in the logs to provide an explanation.

Is this urgent?

[ ] Yes
[X ] No

log with older release looks like this:
2020-03-30T01:47:14.971Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Initializing tinyproxy ... pia         | 2020-03-30T01:47:14.972Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Reloading config file pia         | 2020-03-30T01:47:14.972Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Added basic auth user : bcjacob pia         | 2020-03-30T01:47:14.973Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Disabling transmission of the "Via" header. pia         | 2020-03-30T01:47:14.973Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: listen_sock called with addr = '(NULL)' pia         | 2020-03-30T01:47:14.973Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: trying to listen on host[<IP_ADDRESS>], family[2], socktype[1], proto[6] pia         | 2020-03-30T01:47:14.974Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: listening on fd [4] pia         | 2020-03-30T01:47:14.974Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: trying to listen on host[::], family[10], socktype[1], proto[6] pia         | 2020-03-30T01:47:14.974Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: listening on fd [5] pia         | 2020-03-30T01:47:14.975Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Now running as group "tinyproxy". pia         | 2020-03-30T01:47:14.975Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Now running as user "nonrootuser". pia         | 2020-03-30T01:47:14.976Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 1 of 10 ... pia         | 2020-03-30T01:47:14.976Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 2 of 10 ... pia         | 2020-03-30T01:47:14.977Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 3 of 10 ... pia         | 2020-03-30T01:47:14.977Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 4 of 10 ... pia         | 2020-03-30T01:47:14.978Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 5 of 10 ... pia         | 2020-03-30T01:47:14.978Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 6 of 10 ... pia         | 2020-03-30T01:47:14.979Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 7 of 10 ... pia         | 2020-03-30T01:47:14.980Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 8 of 10 ... pia         | 2020-03-30T01:47:14.982Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 9 of 10 ... pia         | 2020-03-30T01:47:14.983Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Creating child number 10 of 10 ... pia         | 2020-03-30T01:47:14.983Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Finished creating all children. pia         | 2020-03-30T01:47:14.984Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Setting the various signals. pia         | 2020-03-30T01:47:14.984Z  INFO    tinyproxy: INFO      Mar 30 01:47:14 [54]: Starting main loop. Accepting connections.
Current release:
2020-03-30T01:55:43.263Z  INFO    tinyproxy configurator: generating tinyproxy configuration file pia         | 2020-03-30T01:55:43.263Z  INFO    firewall configurator: accepting any input traffic on port 8888 pia         | 2020-03-30T01:55:43.270Z  INFO    tinyproxy configurator: starting tinyproxy server

I found the bug (but in bed on my phone :smile:), I just need to remove the line deluser tinyproxy from the Dockerfile as it also removes the group tinyproxy precised in the generated tinyproxy config file, hence preventing tinyproxy to start. I'll do that tomorrow morning (EST timezone).
Thanks for creating the issue anyway!


[Feature] Add StarRocks Connector for Trino

What type of PR is this：

[x] Feature

Problem Summary(Required) ：

Optimization of StarRocks write performance by using stream load api instead of jdbc connector

join the support for openlookup?

join the support for openlookeng?

Any progress on this PR?

license header should include Copyright 2021-present StarRocks, Inc. All rights reserved.. You can refer to other files.

What's the data type mapping between trino and starrocks?

@banmoy The above points have been modified. PTAL

Just a question: Why don't we submit this PR to Trino repo? https://github.com/trinodb/trino

Just a question: Why don't we submit this PR to Trino repo? https://github.com/trinodb/trino

I think both are fine, but first I contacted a colleague in the starrocks community.


Allow ptr of time.Time as SoftDelete filed

And we still does not allow delete with nil pointer model, such as :
-       _, err = db.NewDelete().Model(video1).Where("id = ?", video1.ID).Exec(ctx)
+       _, err = db.NewDelete().Model((*Video)(nil)).Where("id = ?", video1.ID).Exec(ctx)

Will we support this?

Will we support this?

I guess we should. We probably should start adding tests for such features :)


Requires.io has been sunset

Remove the badge, because of http://shiningpanda.com/requires-io-clap-de-fin/.

This PR was branched off main and then rebased against rel1.4 branch, hence the force-push.


feat: Add 'MemoryStore'

Features:

Add MemoryStore

I submitted a pull request for MemoryStore to oras-credentials-go a week ago. However, the repository has since been deprecated. I've created an identical PR to this one.
Reference Issue: Here

Codecov Report

Merging #602 (7dc9201) into main (577bffe) will increase coverage by 0.06%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #602      +/-   ##
==========================================
+ Coverage   74.58%   74.64%   +0.06%
==========================================
  Files          58       59       +1
  Lines        5252     5266      +14
==========================================
+ Hits         3917     3931      +14
  Misses        983      983
  Partials      352      352

Files Changed
Coverage Δ

registry/remote/credentials/memory_store.go
100.00% <100.00%> (ø)


Should rename columns tx_in_id and tx_out_id in tx_in and collateral_tx_in table to in_tx_id and out_tx_id

As per the title, I think these columns should be renamed, because it can be confusing in documentation or when first learning to navigate the database.

In the "tx_in" table, the "tx_in_id" column may be mistaken as the primary key, but there's also a "id" column, so that may cause some confusion.
In the "tx_in", "collateral_tx_in" and "ma_tx_out" table, there are the same column names "tx_out_id" but they are referring to different things. The "tx_out_id" in "tx_in" and "collateral_tx_in" tables actually references the pk of "tx" table, meanwhile the "tx_out_id" in "ma_tx_out" is actually referencing the pk of "tx_out" table.
Renaming it to "in_tx_id" and "out_tx_id" enables us to immediately identify that the data in this column are in fact "tx_ids", referencing the "tx" table, but they are input or output transactions denoted by the "in" and "out" prepend. This is also in line with the "registered_tx_id" columns in other tables such as "stake_address" where the prepend is further describing the transaction.

I understand this will cause a lot of regression issues, devs will need to take note and make changes to their code referencing these columns. But I think it's necessary to reduce the amount of questions and difficulty in learning for the in-flux of new developers coming on board Cardano.

This is basically a duplicate of #1138 . It would make more sense for you to add a comment there and close this issue.

Sorry, was not aware of #1138. Thanks for pointing that out!


WIP: Add metrics api for poseidon

fix： #94
1, we will collect metrics like scheduling latency/binding latency ..
2, port for metrics will be configurable, default as port  9292 or can we multiplex other ports?
3, need to provide capability like health check(like :/healthz) for poseidon?
@m1093782566

/ok-to-test

@jiaxuanzhou
Thanks for your PR. You need to

Sign the CLA.

Add your vendors to the Gopkg.lock.

@jiaxuanzhou
Is that ready for reviewing?

/assign

@m1093782566 i will submit the code soon

@jiaxuanzhou Please remove the WIP once this PR is ready for reviewing.

@m1093782566 plse help review

@m1093782566 please hold, will add the service of metrics port later

/test pull-poseidon-verify

@m1093782566 please help review, healthz funcs  will multiplex the port of metrics.

@jiaxuanzhou
Can you please clean up the commits history? e.g. squeeze some similar changes but keep the commit for vendor.

@m1093782566 sure

@m1093782566 rebased the commits

/test ci-poseidon-e2e-gce

/approve except some nits.
@shivramsrivastava any chance to take a look at this PR?

/lgtm


⚠ Spryr has degraded performance

In 78ee14b, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4481 ms

Resolved: Spryr performance has improved in fed9ae1 after 8 minutes.


Added permissions attribute e to app

Some people also need to get the permissions the app requires.
I've added this attribute to the app class.
Enjoy!

Coverage decreased (-28.5%) to 70.952% when pulling 8b0db1fdcdd09617ea73bb06574fe72767e0a74d on Prutheus:master into 7ce53640bcbdfd85b0fa5d9b1933962b1b90df69 on chadrem:master.

@Prutheus Thank you for the pull request! I can't merge this as is, but with some work we can get it there. Here's are some of the changes needed to get this merged:

Make a new branch off my master branch with the bare minimum number of changes needed to add this feature. I review all changes manually and this will help me keep the commit log simple and clean.
Put changes in a single commit so that it is easy to review and merge. In theory the only changes needed are in app.rb and app_spec.rb. This also helps me with reviewing and keeping a clean commit history.
Avoid adding the Mechanized gem. This project depends on Typhoeus and I want to avoid additional HTTP gems.
Avoid adding the package argument to the parse class method if possible. Can't this be auto detected from the html?
Make sure all existing tests pass and add good tests for your feature.
Make sure code coverage never goes down. It appears to have dropped by 28.5%.
Make this feature optional (enabled by default) since it impacts performance (double the HTTP requests). You'll see an example of this with :skip_reviews in app.rb. This is especially beneficial to users who scrape millions of apps a day.

Let me know if you have time to work on the above and I'll provide any assistance I can. Just shoot me another pull request if you are able to take care of these things.

I am closing this pull request due to inactivity. I’m happy to revisit it in the future.


Configure @pep8speaks

Closes #359

@nespinoza Could you review?  Unfortunately I don't think we will be able to see @pep8speaks in action until this PR is merged (and a new exoctk PR is opened).

Hey @bourque --- is Travis failing on this normal?

Looks like 2 of the 6 builds got stuck and timed out.  I just spawned a new build, hopefully it works!

These builds keep getting stuck, and it's not clear to me why 🤷♂ .  I'll try again on Monday.

All right, no worries! Let me know when you figure this out :-).

For some reason Travis has stopped working.  I will investigate.

After logging into the Travis account, it does appear that PRs are triggering Travis builds, for example, this PR: https://travis-ci.org/github/ExoCTK/exoctk/builds/670187171
I'm not sure why this information is not getting back to GitHub though.

I pushed the "restart build" button on Travis and now GitHub appears to recognize that a Travis build is happening.

@nespinoza I finally got the Travis build to run and pass successfully on this, so it should be ready to go!


Add new color turtlenecks in WinterDrobe

About the PR

Adds color turtlenecks in WinterDrobe.
Why / Balance

Passengers have little opportunity to express themselves. Also i love turtlenecks UwU
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl: Ko4erga

add: Added new color turtlenecks in WinterDrobe.

coloring machine soon tm

coloring machine soon tm

I got clothes dyeing working, I just need to finish the UI, which is a pain to do 😭

I hope we don't have to wait for this and I'll get my cutie turtlenecks


feat: Added support for AVIF image thumbnails [CCS-1240]

Purpose
Customers have asked for AVIF thumbnail support in the cloudinary app CCS-1240
Approach
It's already supported on Cloudinary, just needed to update the list of allowed files

@whitelisab can you take care of releasing when you merge the chore: release main please, I see there are other changes packed into that and don't think I should be touching that 😄


Remove util.rmrf in favor of rimraf

LMK If you want to go for commander.js :+1:
I didn't bump the version, as I am not sure what the most correct workflow would be. Let me know if you want me to bump it up and I will squash and rebase.

@bucaran Great work, I'll land this. Thanks for your contribute.

I've shipped as v1.3.2. Thanks :smiley_cat:

Writing a roadmap or at least a todo list like:

[ ] This
[ ] That
[ ] That too.

Would help future contributions.


Merge Swift Package Directory urls with Swift PM Library

Closes #87
I was surprised to see fewer overlaps than expected. ~Only about 50 repositories in common.~ 187 in common actually - I realized I've been using all lowercase and your packages are mixed so I lowercased everything to do matching.
This is the result of scanning github from 2014 onward for packages meeting these criteria:

Must have a Package.swift manifest file
Must have at least 1 semver release tag i.e. "1.0.0"
Must NOT contain a .podspec or Cartfile in the root (I was focused on SPM-first packages)
Must have at least 1 star

My crawler had some issues at some point this year that I didnt fix so I'm not sure if it's captured some of the past few months. If I have some more time later and you think the quality-level is high enough on these packages I can look into making sure the crawler has captured everything to date that follows these rules.
There's also the possibility of opening it up to include repos that have .podspec or Cartfiles

I might need a little help interpreting how to fix the test that failed in CI too

There's also the possibility of opening it up to include repos that have .podspec or Cartfiles

I for one would welcome that a lot, since there's many packages out there doing their best to support all package managers so as to let users use whatever they already have included in their project. I realize that many packages also eagerly added a package manifest in 2014 without ever maintaining it, especially those packages where it just didn't make sense (iOS only packages for example), but that's changed now/soon with the release of SwiftPM support in Xcode 11.

I might need a little help interpreting how to fix the test that failed in CI too

There's a missing newline at the end.

Hmm added a new line but that didn't seem to do it

Better than editing, launch the jq command to sort
I take your fork in my fork, launch the command, push and my travis is ok

For the PR, I know URL do not care about case, but it easier to read for humain
This project SwiftPMLibrary have case on GitHub...
Less work to do, just copy it from Github which propose it with case, etc...
So I am against if it is not an automatic process, or a submission form or command line (like cocoapods)

I can definitely review my merging code so the final result doesn’t affect
the case of any existing repo
Another thing I just realized is that the readme says Swift 4.0 and greater
but I don’t think these repos are necessarily Swift 4.0, so there’s some
more filtering to be done.
On Sat, Aug 24, 2019 at 6:01 AM Eric Marchand<EMAIL_ADDRESS>wrote:

For the PR, I know URL do not care about case, but it easier to read for
humain
This project SwiftPMLibrary have case on GitHub...
Less work to do, just copy it from Github which propose it with case,
etc...
So I am against if it is not an automatic process, or a submission form or
command line (like cocoapods)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/daveverwer/SwiftPMLibrary/pull/104?email_source=notifications&email_token=AAFMXM5LZRVQWYXDCMISGFDQGEBJLA5CNFSM4IPEJ6NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5B5CHQ#issuecomment-524538142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFMXM74K7QAOXK56OT7RJ3QGEBJLANCNFSM4IPEJ6NA
.

Fixed the lowercasing problem so all existing entries are undisturbed and ranjq locally. Looks like everything passes.
Up for discussion is whether my crawler could be of any use now or in the future. If i rerun it from the beginning and changed rules to include podspec and cartfile packages and omit packages < 4.0 (i guess by checking the swift-tools-version?), i wouldn't surprise me if it took a week to run, given the API rate limitations. I think i get about 500 calls per hour and each package analysis takes 3-4 calls each.
For reference this is the crawler code, currently dependent on Cloudant because I used IBM Serverless to run it: https://github.com/bitwit/swift-package-directory/blob/master/Sources/SPDCore/Services/PackageCrawler.swift

This is fantastic, thank you Kyle!
I think some of the reason that there isn't a lot of overlap is that my original crawl had a lot of these packages in, but I removed them when they were causing my parser to fail. You can see some of that work here.
A couple of examples, just from loading a few random repositories here.

https://github.com/a2/passcards-swift - Has a Package.swift but doesn't declare any libraries or executables.
https://github.com/aktowns/csdl - Not really a Swift package.

That said, my has got much more reliable since then and so I think with a couple of simple changes this could be good to merge because the vast majority of packages added here are fantastic, and completely legitimate to be in the directory.
I'm going to hold off on merging just for now though. I'm in the middle of a huge change to the back end code and I have no doubt that when I add these packages it'll find plenty of edge cases in my parser. I'd rather be working with a stable codebase when that happens.
I should merge my big change in either today or tomorrow, so I'll look at this again towards the end of the week.

Just one more thing on this, I think I'll include a new rule in the search that only packages that define at least one library or executable should be eligible for searching. I have this data already so it will be easy to do. Tracking this as #106.

https://github.com/aktowns/csdl - Not really a Swift package.

Isn't it though? That specific package uses an old manifest format, but it's still a Swift package nonetheless that others might want to include as a dependency.

Isn't it though? That specific package uses an old manifest format, but it's still a Swift package nonetheless that others might want to include as a dependency.

You're right, of course, but the majority of packages in this state would include Swift code, and that Swift code would be so out of date that its usefulness would be questionable.
The other issue with this package, and many others, is that they won't process using dump-package with the Swift 5/5.1 tools.
I currently get the package name from that generated JSON manifest. Of course, I could keep a copy of Swift 3 around for these packages, and then fall back to trying that when 5.x fails, but I'm just not sure it's worth the work to support these packages that are multiple years old.

Oh if it's about the old manifest format, I'm totally with you. If a package fails to be to analyzed with current tooling it shouldn't be included (or not updated if it's already being indexed). I thought this was about the package only being a modulemap. If dump-package doesn't work on that then that's probably a bug worth filing a JIRA for.

I thought this was about the package only being a modulemap.

It kinda was, but you convinced me on that one straight away. I think this package is a bit of a special case where it hasn't been updated in 4 years, but is still potentially relevant and useful as it includes no actual Swift code. An edge case for sure, but a valid one. 👍

If dump-package doesn't work on that then that's probably a bug worth filing a JIRA for.

This is the practical side of it though, running dump-package gives:
$ swift package dump-package
/Users/dave/Desktop/CSDL: error: package at '/Users/dave/Desktop/CSDL' is using Swift tools version 3.1.0 which is no longer supported; consider using '// swift-tools-version:5.1' to specify the current tools version

Apologies for the very long delay on getting this merged, I've had a few other things that needed attention first. I just merged it and the server is starting to chew through the packages now… Fingers crossed!
Thank you so much for your efforts on this @bitwit, I really appreciate them.

As expected, this uncovered all sorts of edge cases in my code 😂 The final run through these packages just finished though. It's now tracking 3429 packages with over 42,000 package versions as of right now.

This is great news. Super psyched to have been able to contribute to this project and extract more value out of past experiments. If there's anything I can do with the crawler code to assist you in the future, please let me know.


chore/toggle-tests: adding unit tests to toggle components

Closes #
📝 Description

Add a brief description

Adding as prop and tests to toggle components (Checkbox, Radio, RadioGroup and Switch).
Screenshots

Please provide screenshots for any visual changes

Merge checklist

[x] Added/updated tests
[ ] Added changeset

Talked with @Ashley-p44 IRL, going to work on a more robust class creation util for easier composition on testing!


KOGITO-855 - [Jobs Service] improve persisted jobs loading

Schedule and load jobs in chunks, expressed in a period of time that can be configured, for instance, next 10 minutes, 30 minutes,  60 minutes...
The scheduler just handles the jobs in the current chunk in this way it is not necessary to schedule jobs that are supposed to be executed in a long time in the future.
Besides, it was added the jobs load prioritization.

@MarianMacik would you like to take a look at this PR?

PR updated it was added KOGITO-532 to handle jobs prioritization on loading.

Jenkins retest this

Jenkins retest this please

@tiagodolphine @cristianonicolai  guys sorry being a PITA, but when you add a new feature to the services, could you please talk to us so we can open JIRAs on our side to support them? Or at least have a discussion with you about implementation details on operator side? Thanks!!

@ricardozanini this was discussed when we met here in Krakow so I thought you were up to date with the details. Plus does this actually have impact on the operator? Is this about new properties or...

@ricardozanini as @mswiderski pointed out, this feature was already discussed during the krakow f2f and on the planning, IMHO this is the place we should discuss what will be implemented on the feature and if it is necessary some new JIRAs be handled on the operator or any other component, maybe we missed this point, and besides I'm not sure these configurations should be mandatory to be on the operator since they are fine-tuning for the application runtime, or we can expose them with some pre-defined values or some limitations, for instance from 1 to 100, WDYT guys?

Do you know how to retest the PR? it seems to be failed on a test with the integration test with infinispan, but locally it is running well. The "Jenkins retest this please" thing seems not to be working here.

@tiagodolphine you need to retriever it manually in Jenkins console - there is a sort of refresh button next to login/logout button in right hand side top corner, just triggered it ...

@ricardozanini this was discussed when we met here in Krakow so I thought you were up to date with the details. Plus does this actually have impact on the operator? Is this about new properties or...

I’m not talking about only about this feature, but any implantation in general. For this one we have now a JIRA.
@tiagodolphine any property that will reflect the behavior of the service in runtime should be reflected in the operator deployment. I’ll change that behavior though to have a config map mounted instead with default values, so we won’t need to take care about properties in the future (or not so much).
Plus would be nice if you start giving a chance to the operator. I’ll think on something to make your life easier or at least a tutorial of how to rebuild the images and test them with the operator. :)

not talking only about this feature, but any implantation in general. For this one we have now a JIRA.
@tiagodolphine any property that will reflect the behavior of the service in runtime should be reflected in the operator deployment. I’ll change that behavior though to have a config map mounted instead with

Sure +1, and the default values would be nice to have.

I think we are ok to merge the PR.


Target configuration and configurations

New Issue Checklist

[x] Updated struct to the latest version
[x] I have read the documentation to make sure my issue isn't covered already

Struct version
[2.1.1]
Spec version
[2.1.1]
Which type of spec are you using?

[x] project.yml
[ ] project.json
[ ] Specfile

Context
When specifying a target it's not possible to have both configuration and configurations.
Both should be able to be set for the same target.
Reproduction steps
iOS:
    sources: iOS
    platform: ios
    type: ":application"
    configuration:
      INFOPLIST_FILE: iOS/Info.plist
    configurations:
      debug: iOS/configurations/test_debug_iOS.xcconfig
      staging debug: iOS/configurations/staging_debug_iOS.xcconfig
      production debug: iOS/configurations/production_debug_iOS.xcconfig
      test release: iOS/configurations/test_release_iOS.xcconfig
      staging release: iOS/configurations/staging_release_iOS.xcconfig
      production release: iOS/configurations/production_release_iOS.xcconfig
    references:

Expected result
Target gets INFOPLIST_FILE  set and also has project configurations set
Actual result
Only the project configurations are set. If the configurations is removed, INFOPLIST_FILE gets set correctly

Hi @yonaskolb, that's correct, if you're using xcconfig references, you need to specify your INFOPLIST_FILE inside the xcconfig file. Currently, you can either use xcconfig references, or overrides, but not both.
This is currently described in the documentation:

Please note that when specifying xcconfig references, any overrides are ignored.

Yes, but xcode configuration references are set on a project level. While specific overrides are set on a target. There should be no reason to not allow both of them right?

If it's just limited to xcodeconfig files, then variants lose a lot of their power as you can't set specific build settings on them while still having fallback project configurations

In struct, you can set configuration references on a project level, and an individual target level. From the above example you've posted, it appears you're setting them on a target level. If you wish to achieve the behaviour you describe, you can do as follows:
configurations:
  debug:
    source: iOS/configurations/test_debug_iOS.xcconfig
  staging debug:
    type: debug
    source: iOS/configurations/staging_debug_iOS.xcconfig
  production debug:
    type: debug
    source: iOS/configurations/production_debug_iOS.xcconfig
  release:
    source: iOS/configurations/test_release_iOS.xcconfig
  staging release:
    type: release
    source: iOS/configurations/staging_release_iOS.xcconfig
  production release:
    type: release
    source: iOS/configurations/production_release_iOS.xcconfig
targets:
  iOS:
    configuration:
      INFOPLIST_FILE: iOS/Info.plist

Well I actually have different targets that all point to different xcode config files

In this scenario, your individual targets' xcconfig files would need to specify the INFOPLIST_FILE within them. Currently Struct does not support combining xcconfig references with configuration overrides.

It wouldn't need to combine xcconfig references.
Whenever a target has a xcconfig file set for a special project configuration, those build settings sit above a target's build settings. All I'm asking for is to change a target's build settings while also still referencing an xcodeconfig file for the project config. Then the target has these levels of build settings viewable in Xcode as level:
Target, Config File, Project, Platform Default

Yes, I believe we're talking about the same thing. Currently Struct does not support specifying build settings in addition to an xcconfig file. I'll mark this as a feature request for 2.2.0.

Ok cool. Is it just a case of removing a check that limits it to one? Because both features work independently at the moment, just not together.

The configurations and configuration block behaviour would need to remain the same. configuration is shorthand for specifying a full configurations block when all of your configuration settings are identical. This is why you can only specify one or the other.
Behind the scenes when specifying a configuration block, Struct will generate a target configuration entry based on that block for every build configuration in your project.
In your particular use case, we would need to add support for specifying a more detailed variant of the configurations block, for example, something like this:
    configurations:
      debug:
        source: iOS/configurations/test_debug_iOS.xcconfig
        overrides:
          INFOPLIST_FILE: iOS/Info.plist

Ok got it. If adding that extra functionality to configurations then it would be good to have some way of specifying a build setting once if it's the same for each configuration. Maybe a $base config?

Hi @yonaskolb, we actually added this to 2.0.0, but it hasn't been documented yet. You can use it like this:
targets:
  my-target:
    configurations:
      $base:
        IPHONEOS_DEPLOYMENT_TARGET: 10.2
      debug:
        INFOPLIST_FILE: Info.plist
      release:
        INFOPLIST_FILE: Info-Release.plist

This may actually solve your issue in the short term too, I don't believe we restrict adding build settings from $base to configurations using xcconfig references. If my theory is correct, you should be able to do something like this:
targets:
  my-target:
    configurations:
      $base:
        IPHONEOS_DEPLOYMENT_TARGET: 10.2
      debug: path/to/config.xcconfig
      release: path/to/config.xcconfig

Oh cool! Yeah there are a few things that don't seem to be documented, notable schemes
https://github.com/workshop/struct/wiki/Spec-format%3A-v2.0

Yes, that works using $base, thanks!

Yes documentation for 2.0.0 is being improved gradually. If you find anything that's missing or doesn't appear to work as described, feel free to file an issue!


Option to reverse layers order

It would be nice to have an option to see the latest layer on top of the layer view. This is useful when dealing with base images and a number of layer are always the same so one can quickly see what has changed.

I could add an option to reverse the order, though I think it makes more sense to leave the order as is (the same order as the Dockerfile) and add a page-down/page-up ability on the layer view. In this way you could very quickly jump to the last layer. I could also make the view "circular" such that when you arrow up on the top layer, it jumps to the last layer (possibly disorienting, but I feel that would be better than reversing the order).

Both are fine with me

Added pgup/pgdown key options in 184d3a2b0c82d149f17e17c6494d3a4e4a1f93c8 , should be in the v0.7.0 release


tag-recon

Thanks for your PR it looks promising, I made some changes and cleanings that maybe can help with the failing test on your PR, can you please rebase it onto the last master commit?
Also I've noticed fsevents as dependency, when trying to install your branch on a windows it raise an error because win platform is not supported, I see is not used anywhere in the code, can you please remove it?
This will retrigger the tests and hopefully avoid the yarn eval error shown and run them correctly.

Thank you will resubmit after rebase on those changes.

You can keep this open and resubmit here, since there is nothing wrong with this PR itself, it was the package very outdated and it had few errors and potential vulnerabilities in the dependencies.


Use decorators for icon names in conf. provider objects

This would allow us to get rid of if(ModelName) ... switches in views and controllers.
Also, it will fix some errors occuring when switching between GTL views.
https://bugzilla.redhat.com/show_bug.cgi?id=1330288
@himdel :-)

@miq-bot remove_label wip

I think this looks great! Except I'd put image_name in the decorators too, unless some of the models really have it in the db..


i use require.js to include the needed file jquery jquery.terminal-2.8.0.min.js jquery.mousewheel-min.js to some page but when i view the page it tell me need wcwidth.js

Expected behavior
Actual behavior
Steps to reproduce
Browser and OS

when i serach wcwidth i found that in  jquery.terminal-2.8.0.min.js  whether the jquery.terminal-2.8.0.min.js grammar conflict with the require.js

If you use requirejs you need to have wcwidth because its dependency. I should document it.

Do you have actual, real code I can test? If you copied the files you need to get wcwidth as well, jQuery.Terminal don't have jQuery as well. Both jQuery and wcwidth are dependencies you need to download them if you don't use npm but directory with files and you've downloaded.

I should document it

ok, thank you i will try

Do you have actual, real code I can test? If you copied the files you need to get wcwidth as well, jQuery.Terminal don't have jQuery as well. Both jQuery and wcwidth are dependencies you need to download them if you don't use npm but directory with files and you've downloaded.

i am sorry i can not give you real code ,by the way thank you so much to answer my question i will  download wcwidth to try


Add Support for KVD21 Gateway

Refer to documented information in https://github.com/highvolt-dev/tmo-monitor/issues/22
Need to add support for the Arcadyan KVD21 Gateway.

Released in https://github.com/highvolt-dev/tmo-live-graph/releases/tag/v0.0.3


Initial example async process plugin

I am not sure if this should be in master, but I am getting tired of rebasing it.
Comments?

Looks reasonable, why do you think it should not be in master?


"Cannot instance script because the associated class could not be found." error when loading C# assembly + .pck

Godot version
4.0.2.stable.mono.official [7a0977ce2]
System information
Windows 10 21H2
Issue description
I'm trying to implement modding support in a game I'm working on, but scenes from my test mod are unable to be loaded correctly. When I load a scene, the scene loads but Godot fails to create the script attached to the scene and prints the following error:
E 0:00:00:0724   Godot.NativeInterop.NativeFuncs.generated.cs:332 @ void Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_ptrcall(IntPtr , IntPtr , System.Void** , System.Void* ): Cannot instance script because the associated class could not be found. Script: 'res://Foo.cs'. Make sure the script exists and contains a class definition with a name that matches the filename of the script exactly (it's case-sensitive).
  <C++ Error>    Method/function failed. Returning: false
  <C++ Source>   modules/mono/csharp_script.cpp:2301 @ can_instantiate()
  <Stack Trace>  Godot.NativeInterop.NativeFuncs.generated.cs:332 @ void Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_ptrcall(IntPtr , IntPtr , System.Void** , System.Void* )
                 NativeCalls.cs:3435 @ Godot.GodotObject Godot.NativeCalls.godot_icall_1_371(IntPtr , IntPtr , Int32 )
                 PackedScene.cs:126 @ Godot.Node Godot.PackedScene.Instantiate(Godot.PackedScene+GenEditState )
                 Game.cs:77 @ void Game._Process(Double )
                 Node.cs:1795 @ Boolean Godot.Node.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 CanvasItem.cs:1371 @ Boolean Godot.CanvasItem.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 Node2D.cs:516 @ Boolean Godot.Node2D.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 Game_ScriptMethods.generated.cs:31 @ Boolean Game.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 CSharpInstanceBridge.cs:24 @ Godot.NativeInterop.godot_bool Godot.Bridge.CSharpInstanceBridge.Call(IntPtr , Godot.NativeInterop.godot_string_name* , Godot.NativeInterop.godot_variant** , Int32 , Godot.NativeInterop.godot_variant_call_error* , Godot.NativeInterop.godot_variant* )

I was able to replicate this behavior in an MCVE, linked below (and where the above error message is from).
Steps for reproducing the issue can be found in the MCVE repo's readme. I've verified that I can clone the repository, follow those steps, and repro the issue. I can repro the issue in my game on both Windows (Win10 21H2) and Linux (Ubuntu 22.04), and on Windows (Win10 21H2) with the MCVE. I did not test the MCVE project on Linux.
There are a few GitHub issues that are related:

https://github.com/godotengine/godot/issues/74146

This issue appears to be an exact match, but it was closed with no fix.

https://github.com/godotengine/godot/issues/73932

This issue does not apply in my case as my project does not have any of the invalid characters in its path
For my MVCE, I verified the behavior with the repo at C:\GodotMcve and again with the repo cloned to C:\mcve

https://github.com/godotengine/godot/issues/36828

I believe this issue is not relevant as it's old enough that it's from before the move away from Mono

Steps to reproduce
Steps to reproduce the issue can be found in this repository's README:
https://github.com/MYTX-Wildfire/godot-pck-mcve
Minimal reproduction project
mcve.zip

Thanks for the report. This was already reported in https://github.com/godotengine/godot/issues/75352, so closing to consolidate the issue tracking there.

are there any play to fix this bug??
now has publish 4.02 version
but this bug is very serious for .net developers.


Use biopython

https://github.com/pierrepo/grodecoder/blob/e4e072758297926ea5a6a04b1ae9050a66e31b92/fasta_seq_into_PDBID.py#L6
Could you use biopython to read the fasta file?

@pierrepo yes I read a fasta file to collect all the sequence, and re-write a fasta file to put the PDB ID in the line begin with ">" for each sequence

ok @KarinDuong
No need to revrite the fasta with the PDB ID.

@pierrepo so how to store these PDB ID ? and how we going to known to which sequence it's related ?

As discuss last time, we might have multiple PDB structures that match the target sequence. So it's better to just output in the terminal something like this:

FASTA sequence 1: <20-first-amino-acids>
Putative structure:
Putative PDB IDs: <5 or 10 best PDB IDs with best match>


NullPointerException when playing Mixer streams

Playing a mixer stream returns
Version: jda4-SNAPSHOT
JDA Version: 4.0.0_41
java.lang.NullPointerException: null
	at lavalink.client.player.LavalinkPlayer.playTrack(LavalinkPlayer.java:83)

I think it's fair to say we can close this due to Mixer no longer being a thing


Utilising the underlying dask machinery

It looks like that many of the computationally intensive tasks (blocking mechanisms, feature value extraction) are reimplemented using dask (in submodule: dask), but they're not installed when installing the package via pip. Have they been omitted purposefully due to the lack of testing on them (as suggested by the docstrings of the functions) or is there a way (for instance setting some installation flags) to install the dask utilities?

At the moment, these functions have not been properly tested and that is the reason they are not directly callable in the current version of the code. Unfortunately, none of these command are imported in the __init__.py file and therefore cannot be called directly.
However, there is a workaround to this problem if you install the code from the source distribution. This can be done by first cloning the repository. I'd recommend cloning the latest release branch, called rel_0_3_2. Then, you can add the desired commands to be imported by the __init__.py file by adding lines for each command you want to be able to use. The example below allows you to use the dask attribute equivalence blocker and the dask decision tree matcher:
# dask functions
from py_entitymatching.dask.dask_attr_equiv_blocker import DaskAttrEquivalenceBlocker
from py_entitymatching.dask.dask_dtmatcher import DaskDTMatcher

Once these lines have been added to the __init__.py file, you can install the code from the source distribution you have edited. Go to the main directory where the setup.py file is located. I'd recommend first installing the requirements using the requirements.txt file. Note that there are some dependency packages in the dask command code that are not included as a requirement so you will also need to install them. Additionally, to build the package you will need cython:
pip install -r requirements.txt
pip install dask cython toolz

After this is done, you can install the package. The first line below builds the cython files and the second line actually install py_entitymatching.
python setup.py build_ext --inplace
python setup.py install

Now that everything is installed, you should be able to use the dask commands that you imported in the __init__.py file earlier. For example, the use the dask attribute equivalence blocker:
import py_entitymatching as em
A = em.read_csv_metadata('./py_entitymatching/tests/test_datasets/A.csv', key='ID')
B = em.read_csv_metadata('./py_entitymatching/tests/test_datasets/B.csv', key='ID')
dask_ab = em.DaskAttrEquivalenceBlocker()
C = dask_ab.block_tables(A, B, 'zipcode', 'zipcode')

I hope this helps. If anything here is unclear or you have any remaining questions, please ask and I will try to clear things up as best that I can.

Thank you,
I followed your instructions and finally managed to install the dask modules. Although, you said already that those dask modules haven't been properly tested yet (and you might be well aware of what I am about to say), but I didn't see any performance improvements relative to the  original modules when testing the dask versions of the same modules.

Hi, I just wanted to follow up on this to provide a little more explanation about the dask version of commands. They generally require specific arguments to be properly set in order to actually use the dask aspects of the command.
For example, take the dask version of the attribute equivalence blocker (DaskAttrEquivalenceBlocker). When calling the block_tables command, you must set the arguments n_ltable_chunks and n_rtable_chunks because the default value for each is 1, which behaves exactly like the regular attribute equivalence blocker. If you set these commands to something else, say 4, then the command will split each table into 4 chunks and the command will run the blocker on each pair of chunks in parallel using dask. The other dask commands generally have similar arguments that specify how the task should be split up to run in parallel.
Another import aspect regarding the effectiveness of the dask commands is that they only begin to have any use when the tables get large enough to warrant the extra overhead required to split the tables and run tasks in parallel. When using smaller tables, the regular versions of commands will be faster than the task versions, even when setting the arguments properly.
You may already be fully aware of all this, but due to the lack of documentation about these commands, we thought it would be best to provide some extra explanation about how they work here in case you or others find it helpful.


feat: Make Reanimated optional (disable Frame Processors if REA v2 is not installed)

What
This PR adds support for using VisionCamera without Reanimated v2. A lot of people didn't migrate to v2 yet, but they should also be able to use VisionCamera - they just can't use Frame Processors.
Implemented:

[x] iOS
[ ] Android

Blockers
I don't really know how to make a dependency/library optional in CMake/build.gradle....
Related issues

Fixes https://github.com/mrousavy/react-native-vision-camera/issues/411
Fixes #660

This is awesome!
Is anything here relevant: https://docs.gradle.org/current/userguide/feature_variants.html?

Any luck with this?

Not yet, don't understand Gradle well enough yet.

Thanks for the update. I'll take a look as well.

The good news is that react-native-reanimated will actually support v8 quite soon. I just got it working after a lot of help from the maintainer of react-native-v8, who was awesome enough to share a couple of patches.
So I think this might not be urgent anymore, now that react-native-reanimated should support JSC, Hermes, and v8.

@mrousavy Just in case we can't yet update to reanimated-v2 (in our case because we are using react-native-draggable-flatlist which is not yet compatible with v2 (https://github.com/computerjazz/react-native-draggable-flatlist/pull/335)), and we need the react-native-vision-camera but without frame-processors, Is there any workaround?

the workaround is to delete all of the C++ files and CMake setup 😅

Do you think that making frame processors a separate repo from the vision camera and have it as an add-on (which would entirely need anIimated-V2), would be a solution?

No, because that is way more complex than simply allowing Frame Processors to be disabled if REA is not installed

@mrousavy Just in case we can't yet update to reanimated-v2 (in our case because we are using react-native-draggable-flatlist which is not yet compatible with v2 (computerjazz/react-native-draggable-flatlist#335)), and we need the react-native-vision-camera but without frame-processors, Is there any workaround?

I believe react-native-draggable-flatlist is compatible with REA v2. It just doesn't uses the new REA v2 API, but the old one still works with V2.
@computerjazz knows better

@nelsonprsousa yep that's correct. react-native-draggable-flatlist uses the v1 api because performance is better with v1 when rendering an arbitrarily-long list where each item has complex animated value interactions (largely thanks to the proc node). This is only an implementation detail, the package works just fine with reanimated 2, and I actually have reanimated 2 as a peer dep just to allow me to transition to the new api whenever the perf issues are fixed.
Would love to get your take on this @mrousavy but I won't hijack this thread :). I know some performance issues have landed in reanimated recently but last I checked the v2 api still resulted in low fps.

@jzxchiang1 can you test if it works for you now?

It works! Just tested both on Android and iOS, Reanimated is no longer required! And if you don't use Frame Processors, compile time is faster! :)

Sorry just saw this. Thank you! I ended up getting reanimated to work either way, but this is helpful as well.


[mssql-linux] Added feature to enable HADR

Adding feature to enable SQL Server deployment with HADR (Availability Groups)

/cc @unguiculus

Fixed merge conflicts #5291

/cc @unguiculus - could you merge this

/cc @timstoop

/assign

/ok-to-test

/lgtm


Capture compiler plugin failure information with the diagnostics

Description:
Currently, in the diagnostics generated for the compiler plugin failures does not include information to isolate the particular plugin which failed.
Affected Versions:
slalpha at least

This issue was created for the old compiler plugin implementation. However, we have added this with
https://github.com/ballerina-platform/ballerina-lang/pull/29148 for the new implementation. Hence closing this issue.


Bump Kotlin to 2.0.0-Beta3

Does it run languageVersion=2.0? 👀

Does it run languageVersion=2.0? 👀

No :(  I think that's a new one, I'll try a small reproducer/open an issue.


Normalize FUNCTION_URI directory

Each function invoker places the function to execute in a different location.
Java: /functions
Node: /functions
Python: /
Shell: /
We should always place functions into an empty directory since it's possible the function name could collide with a legitimate file path.

maybe /riff?

This issue was moved to projectriff/riff#312


Templating for git hooks

Currently, pre-receive hook is fixed: https://github.com/hasura/gitkube/blob/master/build/gitkubed/pre_receive.sh
We want to make it scriptable to enable : https://github.com/hasura/gitkube/issues/20
Each hook probably needs variables from the remote like DEPLOYMENTS, REGISTRY_PREFIX.
For pre-receive, we are currently doing a moustache render during startup.
For giving same variables to each hook, we need to run a moustache render on each hook and then place it in the correct directory.

Would this also allow something like using a secret as a Docker build argument? For example, now I need to pass a Github token to a Dockerfile for fetching Github repos during the build. I can get the secret into Gitkubed's environment, but I see there is no way to pass a build argument currently.

@jsierles Yep. You can then load the build argument from the kubernetes environment
kubectl --context=accrue51 get secrets hasura-secrets -o json | jq -r '.data."auth.secretKey"' | base64 --decode

and then pass that as a build-arg to the docker build command.
@tirumaraiselvan Does that make sense?

Yes, this issue is to make available arbitrary params to the build environment which can then be used in custom hooks. Custom hooks is in a WIP branch although I haven't gotten around to parameterization part yet. For now, the easiest way is to keep in the Dockerfile. The harder way is to fork from master and build your own version of Gitkube.

@jsierles docker build args support is here https://github.com/hasura/gitkube/pull/64


Show overflow indicators for Wrap widget

Fixes https://github.com/flutter/flutter/issues/47085

I was gonna comment that I am not really excited about having non-fatal exceptions and would like to avoid the complexity that this brings. Somehow I forgot to actually post that comment, though...
Anyways, closing this and marking it was wountfix sounds good to me.


Fixed link that was 404

Heads up, I think the npm page still has the broken link: https://www.npmjs.com/package/@supabase/supabase-js


nextFocusDown, nextFocusLeft and nextFocusUp not working

Description
In tvOS nextFocusDown, nextFocusLeft and nextFocusUp not working only nextFocusRight is working but in android all are working.
Version
<EMAIL_ADDRESS>Output of npx react-native info
System:
OS: macOS 12.3.1
CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
Memory: 675.79 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.15.0 - /usr/local/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 8.5.5 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.14 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: Not Found
react-native-macos: Not Found
react-native-tvos:  0.68.1-1
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
.
Snack, code example, screenshot, or link to a repository
No response

This has to do with the way this feature is implemented in tvOS; nextFocusLeft only works if there is already a focusable view to the left (similarly for the other nextFocus methods). Android TV does not have this limitation, it is directly using the corresponding native APIs.
I have an idea about how to make this work as intended on tvOS and will take a look this week.


Create Containers with multiple known children

I have a vec of n Elements I've built from server JSON. I'd like to push these all into a Column. I tried to do a for loop and push onto an existing Column, but I think because push captures self not &self I can't do this because of the borrow checker (I'm new to Rust, please correct me).
I have a local fork with a new instantiation method. It seems to hold true to the spirit of immutability.
    /// Creates an full [`Column`].
    ///
    /// [`Column`]: struct.Column.html
    pub fn new_with_children(
        children: Vec<Element<'a, Message, Renderer>>,
    ) -> Self {
        Column {
            spacing: 0,
            padding: 0,
            width: Length::Shrink,
            height: Length::Shrink,
            max_width: u32::MAX,
            max_height: u32::MAX,
            align_items: Align::Start,
            children,
        }
    }

Is that a welcome PR, or is there a better way?

I do something like what you want with Airshipper, check out https://github.com/Songtronix/Airshipper/blob/master/client/src/gui/mod.rs
You probably are interested in the news part but sadly can't explain more right now but if needed I can sure help you tomorrow.

@rowungiles You should be able to fold an iterator. The todos example does this to generate the list of tasks: https://github.com/hecrj/iced/blob/master/examples/todos/src/main.rs#L174
That said, I agree Column::with_children and Row::with_children would be nice additions. By all means, feel free to open a PR!

Super, I'll do that. Thank you.
And yes, of course you were both correct. fold did exactly what I wanted.

Closed by #220. Thank you! :tada:


Option for directory first

Is there an option to make the results have the directories first, then the files, like most file browsers?
I tried nosort but it's not enough.
Or an option to get an object tree structure instead of a list of paths.

There's no option to get an object tree structure, but there are plenty of modules on npm that do give you folder trees.
You could do something like this in the meantime, using mark:true to mark directories with a / and then sorting them yourself
const matches = glob.sync('test/fixtures/a/**', { mark: true })
const sorted = matches.sort((a, b) => {
  const adir = a.substring(a.length - 1) === '/'
  const bdir = b.substring(b.length - 1) === '/'
  return adir === bdir ? a.localeCompare(b, 'en') : adir ? -1 : 1
})
console.log(sorted)
/*
[
  'abcdef/',
  'abcdef/g/',
  'abcfed/',
  'abcfed/g/',
  'b/',
  'b/c/',
  'bc/',
  'bc/e/',
  'c/',
  'c/d/',
  'c/d/c/',
  'cb/',
  'cb/e/',
  'symlink/',
  'symlink/a/',
  'symlink/a/b/',
  'x/',
  'z/',
  'abcdef/g/h',
  'abcfed/g/h',
  'b/c/d',
  'bc/e/f',
  'c/d/c/b',
  'cb/e/f',
  'symlink/a/b/c'
]
*/


webpack build over 1MB?

before i import it
> webpack  --progress --profile --colors --production

3115ms build modules
11ms seal
18ms optimize
16ms hashing
52ms create chunk assets
5749ms additional chunk assets
1ms optimize chunk assets
1ms optimize assets
17ms emit
Hash: 52be11111c7829c756b7
Version: webpack 1.12.14
Time: 9010ms
  Asset    Size  Chunks             Chunk Names
main.js  *253 kB*       0  [emitted]  main
   [0] multi main 52 bytes {0} [built]
       factory:0ms building:3ms = 3ms
    + 286 hidden modules

after i import it
> webpack  --progress --profile --colors --production

6446ms build modules
18ms seal
22ms optimize
32ms hashing
74ms create chunk assets
22070ms additional chunk assets
1ms optimize chunk assets
1ms optimize assets
86ms emit
Hash: ec8fa799601ba0b5d3a3
Version: webpack 1.12.14
Time: 28784ms
  Asset     Size  Chunks             Chunk Names
main.js  *1.26 MB*       0  [emitted]  main
   [0] multi main 52 bytes {0} [built]
       factory:1ms building:2ms = 3ms
    + 584 hidden modules

That is because https://github.com/Daniel15/babel-standalone


PayPal Express Recurring Support

This single file commit adds PayPal Express Recurring Support.
This was originally written by rayvinly, but his repo is out of date.

See #142 for discussion.


[cube] remove multiple refresh worker configuration

Remove the ability to define multiple workers.
Discussion on cube's slack :
https://cube-js.slack.com/archives/C0442JL3GGP/p1682950291320629
Cube architecture summary :

N cube-api
1 cube-worker
1 cube-store-router
N cube-store-worker
1 remote-storage-bucket

Schema :

LGTM

Hi lvauvillier ,
What you mention the above diagram, our application is same.. what cube-api pods is getting error like
{
"error": "Continue wait",
"requestId": "00-000000000000000056430cbeca9546c9-7347bc60b75a3386-01"
}
can you please solve this issues, and provide proper documentation and solution


TypeError: this._router.init is not a function

Version
3.0.1
Reproduction link
https://codesandbox.io/s/w26279rw0l
Steps to reproduce
Open the code sandbox and inspect the console.
What is expected?
No errors in the console.
What is actually happening?
There is an error saying this._router.init is not a function.

While the app itself is rendering fine, I am not sure what consequences this might have once the app gets complicated. I just wanted to bring this to your attention.

It's due to the router field in your Home component… vue-router uses this field to inject the VueRouter instance, so you are not expected to put any arbitrary data into it.

That fixed it. I'll close the issue. Thank you!!

In router.js file used this
export default router


Manual ww data exclusion

This PR adds functionality to manually exclude specific wastewater forecast dates and locations from the analysis. I have applied this to MN in January/early February which is when we saw the jump in values in the time stamped datasets, likely due to a reporting error.
I also caught some issues with how we were doing the Hub analysis. These were:

needed to filter to include only the forecast dates and locations that we "would have submitted" based on presence of sufficient wastewater data and model convergence (same as in the head to head analysis, as described in manuscript)
needed to filter scores when we used the scoringutils function to log transform observations and predictions, since this returns scores both in natural and log scale

I can change it here, perhaps just ww_forecast_date_locs_to_exclude  since we don't want to imply we are excluding the entire forecast date, just the entire forecast date-location combination? Agree it is too similar to the hospital admissions one which is specific data points

ww_forecast_date_locs_to_exclude
Sounds good.


Update golangci-lint version to 1.50.1

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?
This PR updates golangci-lint to version 1.50.1 (latest at this time).
Checklist

[x] Implementation tested

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Were there no static analysis breakings with the upgrade?

Not when I ran make lint on my machine.

Were there no static analysis breakings with the upgrade?


Evaluation using Glue Lorahub Modules

Hi! I am trying to use the lorahub modules trained on Glue cola dataset, but it seems like it is not producing the correct output? Running the following code gives an output of "The next one is more accurate." rather than the expected label "1".
model = AutoModelForSeq2SeqLM.from_pretrained("google/flan-t5-large")
model = PeftModel.from_pretrained(model, "lorahub/flan_t5_large-glue_cola")
tokenizer = AutoTokenizer.from_pretrained("google/flan-t5-large")

input_text = "Our friends won't buy this analysis, let alone the next one we propose."
input_ids = tokenizer(input_text, truncation=True, padding=True,return_tensors="pt").input_ids
outputs = model.generate(inputs=input_ids)
print(tokenizer.decode(outputs[0]))

@raywang4 Thanks for your interest on our work! May I know if your problem has been solved?

Hi there! Thanks for the reply! I tried with the FLAN 2022 dataset but it still seems like my evaluations are quite off. Would you mind specifying what part of the dataset was used for fine-tuning the lora modules? I read from other issues that a min(10k, data size) samples are selected. Can you let me know which template type was used? Thanks a lot!

@raywang4 Hello! We do not specify the template types, and just try to sample from these datasets using the following code:
from datasets import load_dataset
import os

dataset_folder = "flan_task"

def download_flan():
    dataset = load_dataset("conceptofmind/FLAN_2022", split="train")
    # filter some examples from the dataset
    dataset = dataset.filter(lambda example: example['template_type'] == "zs_noopt", num_proc=32)
    # group the dataset using the task_name
    task_names = dataset.unique("task_name")
    for task_name in task_names:
        print("Processing task: ", task_name)
        # filter the dataset for the current task
        task_dataset = dataset.filter(lambda example: example['task_name'] == task_name, num_proc=32)
        # if the dataset is too large, we randomly sample 5000 examples for the training
        if len(task_dataset) > 10000:
            task_dataset = task_dataset.shuffle()
            task_dataset = task_dataset.select(range(10000))
        # save it into the task file
        task_name = task_name.replace("/", "_")
        task_dataset.to_json(os.path.join(dataset_folder, task_name + ".json"))

if __name__ == "__main__":
    download_flan()

Thanks for the code! It's very helpful!


Adding NetflixOSS lifecycle badge to README

Coverage increased (+0.03%) to 89.092% when pulling 93810fa7f44fa6969c405fcd4b16fba4fe30e4c6 on tgianos:master into 5b8c5c2bb30152067f02d35686c3dd53148f691e on Netflix:master.


Add TG16/PCE roms

Hi,
Could you add the TurboGrafx16/PCEngine roms please?
There are some great SHMUPs and plateformers.
Anyway, awesome work and beautifull launcher, thanks for your great work !

Thanks, I'll look into it

I've released a new version with resolves the issue:
https://github.com/jimbob4000/RetroFlow-Launcher/releases/tag/v3.0


Stratux with Air Navigation Pro

Stratux version: 1.2r1

Stratux config: 9ee46170
SDR

[ ] single
[X ] dual

GPS

[X ] yes
[ ] no
type: VK162

AHRS

[ ] yes
[X ] no

power source: Battery full charge
usb cable:

EFB app and version: Air Navigation Pro last version
EFB platform: IOS 10.2.1
EFB hardware: iPhone 6 +

Description of your issue:

Before any congratulation for your software. Anti-collision finally accessible
I want use Air Navigation Pro with Stratux ads-b but the software requires of me to configure connection with Stratux.
I inform address IP and port TCP but I cannot what bring to the level of the passcode.
 Adresse Ip : <IP_ADDRESS>
 Port : 4000
 PassCode : ?????     (Which value is necessary it to put)

Can you give me the configuration necessary to make function the whole. I do not manage to find in documentation which passcode I must put
Excuse-me for my poor language. French pilot.
If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://<IP_ADDRESS>/logs/stratux/ and http://<IP_ADDRESS>/logs/stratux.log.

You have the IP and port correct. There is no passcode. Is it working without?

Not that does not go. I very tested. The raspberry walk well and via the address <IP_ADDRESS> one recovers the traffic well.
That goes with the applications WingX Pro7 and AvPlan EFB.
On Air Navigation Pro with this param :
<IP_ADDRESS>, Port 4000 and NULL or 0 or 6000 in the Pin Code
it doesnt walk

@ecsaulnier -
"Passcode" implies that Air Navigation Pro uses the FLARM network format, which is used by devices such as AIR Connect. This is different that the GDL90 network format used by most American EFB applications (and Stratux).
I developed a branch of the Stratux software that emulates the FLARM  output, but it hasn't been tested extensively. If you'd like to try it, read this comment, then download and install the linked .sh update file.
Once it reboots, you should be able to connect to Port 2000, and use any value in the PIN code.

Thank you for your answer.
I want to test your new version well
Do you have a procedure to install this new version on the raspberry?

I thank you for all this help.
I succeeded in installing the update 1b17cb4 and now on Air Navigation Pro with the TCP port the 2000 led concerning the traffic passes well to the green.
A new question: This is the real traffic which passes by the port 2000 or the traffic DEMO because it has there nothing which appears on the cartography Air Nav Pro
Thank you in advance for all that you do.
Pilot French Autogiro

I have just installed the version 1.2r2-dev version, can-you indicate to me how to put over the version which manages protocol FLARM on the port 2000 for the application Air VOR Pro.
Thank for your response
French Pilot.


Minor fixes to admonition.

There still seem to be some things wrong with how they are rendered, but this may be the version of myst-js we use ?

Here is http://<IP_ADDRESS>:1234/p/papyri/0.0.8/docs/index that renders wrong with 2 titles every time.

This is not really relevant anymore, closing for now


Can't disable stale state

I want to disable displaying of gray circle when location is not changing. As I understood it is called "stale state". I tried calling enableStaleState(true) and enableStaleState(true), but the gray circle was appearing after some time in any case. I also tried to call staleStateTimeout(Long.MAX_VALUE), but this didn't help either.

By the way I was referring to Location Layer Plugin

I think you are looking to set LocationLayerOptions.enableStaleState(false) which should do the trick. It also sounds like once the options objects built you aren't passing it into the Location Layer Plugin through either its constructor or method applyStyle.
cc: @zugaldia

Oh, sorry, I made a typo. I meant trying to call either enableStaleState(true) or enableStaleState(false).
I'm passing options through constructor, and all options except enableStaleState are applied properly. The gray circle appears no matter what I trye.
        val locationLayerOptions = LocationLayerOptions.builder(this)
                .foregroundDrawable(R.drawable.location)
                .backgroundTintColor(Color.TRANSPARENT)  // hide the default icon
                .elevation(0f)  // hide the shadow
                .enableStaleState(false)  // do not show gray circle
                .build()
        locationPlugin = LocationLayerPlugin(mapView, mapboxMap, locationEngine, locationLayerOptions).apply {
            setLocationLayerEnabled(true)
        }

Awesome find, thanks for the code snippet. I've fixed the issue in #525.


can make it work on iOS

What do you mean? It already works in ios

First of all need enable Settings - Face ID & Passcode