question about consumer group.

in the kakfa document said, only one conusmer can consume one partition in the same consumer group. but I test kafka-node, it seems allow doing this.
doese the kafka-node support this feature? or I have some mistake? Thanks~!

Hi haio,
As @geoffrey-young pointed out, in Kafka, message distribution is load balanced across all the consumers of the same consumer group and hence should not receive the same message.
Currently with kafka-node, all the consumers under a consumer group, listening to the same topic, receive the same set of messages. Would there be a fix for this in kafka-node?
I'm building a Node.js + Socket.io cluster for server-side push using Kafka as the event-driven messaging system. The kafka-node consumers in all the nodes in my cluster is listening to the same topic and gets duplicate messages, and hence I end up pushing the same message to the browser multiple times(the same number as the number of Kafka consumers).
Thanks & Regards,
Karthic

+1

@karthic891 Did you actually resolve this issue?

@dmtrs No, the issue is still open as I couldn't find any alternative way(hack) to achieve the desired behaviour.

@haio Can we reopen this issue please. It seems that they have result issue in python client

+1
Let's try to see how this can be fixed, if possible, I am willing to contribute with some help

Are you using the ConsumerGroup? This is not still an issue afaik.


Update redis Docker tag to v18.19.4

This PR contains the following updates:

Package
Update
Change

redis (source)
patch
18.19.2 -> 18.19.4

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.


Implement std::error::Error for winrt::Error

Thoughts on implementing the primary Rust error trait for winrt's error type?

I think I haven't done that so far because std::error::Error has some deficiencies (which is why https://github.com/rust-lang-nursery/failure is a thing). I'm not sure if we are able to support both. Maybe with a feature flag?

I think I haven't done that so far because std::error::Error has some deficiencies (which is why https://github.com/rust-lang-nursery/failure is a thing)

It has some deficiencies, yeah, but this RFC was approved which plans to improve it.


Fix domain_template scripts

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
Fixes #2009.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Looks like GAN fix(#2019) is already merged. But the same problem is in imagenet.py which is fixed here.


Convert Less to Sass

Changes

Convert Less files to Sass and bring in Sass files from https://github.com/cfpb/design-system/pull/1993

How to test this PR

yarn install && yarn build and site should be unchanged.

I've noticed that some of our apps (TCCP, find a housing counselor) are prioritizing system-ui over Avenir Next

This seems like it's because Avenir is only defined in cfpb-typography, vs. system-ui being defined in cfpb-core and both of those apps import core but not typography.
I imagine that sass is choking on it in a way that a less reference import isn't

Updated to v3 DS. Try it now. Thanks!

Erp I'll need to fix the jest tests so they don't try to scoop up the scss files, but the site can still be checked locally.


update installer in quick start guide

update installer links in the quick guide as it is not up to date anymore

#138


Slide deck template

[x] POC
[x] support sub-sections (vertical slides)
[x] tests
[x] Pretty CSS
[x] Fullscreen mode (=> presentation mode)
[x] Fix template select box
[x] Customize Reveal theme (WIP)
[x] Add doc

Features

Write slides in Markdown
Code, FontAwesome, KaTeX (Math symbols), Emoji are supported
Transitions are configurable (in YAML front matter)
New presentation mode (for all templates, not only slide deck)
Convert any Markdown text into a slide deck (use --- for horizontal slides, and ---- for vertical ones)
Fragments are supported

Editing mode

Fullscreen mode

Presentation mode

This is a brilliant idea!
One small improvement could be to add a full screen "presentation mode" (hiding Monod's header & footer).

Could you take care of it? because there are weird css rules for the current layout. Also, I would only remove the header.

Could you take care of it?

Yes!

Also, I would only remove the header.

Why?

Why?

I think we could add more useful information to this "bottom bar", could be useful to keep it.

Actually, nevermind.
Note for myself:

try not to modify Reveal.js base CSS
review current theme

Ready to be shipped Captain.

I have deployed this branch to production, which is means it is available to everyone for testing: https://monod.lelab.tailordev.fr/. Cheers!

Yaaaay! 🔥 🔥 🔥


Model matrix is broken the same variable is present on both sides of ~.

This was not tested here but in the statsquiz.jl in StatsBase.
julia> ModelMatrix(ModelFrame(x~x, nasty))
ERROR: BoundsError: attempt to access 0-element Array{Array{Float64,2},1} at index [1]
 in expandcols(::Array{Array{Float64,2},1}) at /Users/andreasnoack/.julia/v0.6/DataFrames/src/statsmodels/formula.jl:377
 in DataFrames.ModelMatrix{T<:Union{Float32,Float64}}(::DataFrames.ModelFrame) at /Users/andreasnoack/.julia/v0.6/DataFrames/src/statsmodels/formula.jl:472

It broke during 90f700e1c988c3e228cf56bee43f02538d8be542

Hah, I was just about to file an issue for this. Thanks for correctly bisecting, sorry for misidentifying the offending commit before.

cc @dmbates

I know I submitted a PR to fix this, but now I'm wondering if it's behavior that we want to allow. Or, rather, how opinionated the formula DSL should be about what is a well-formed formula. Is there any situation where the response variable would also appear on the RHS?

@kleinschmidt I agree that it would be unusual to have the same variable on the right and left-hand sides if the purpose is to create a model matrix.
I think the general approach of model terms and evaluation terms and the role of the response should be revisited.  Unfortunately I say this just as I am starting vacation and will be without internet access for about 10 days.  Anyway, the current way of storing information on the response is copied from the R formulation and is not a very Julian approach.  It seems to make more sense to store a symbol or expression for the response and evaluate it with respect to the model frame when needed.  It doesn't really need to be mixed with the model terms for the model matrix.


Add tests for cpu/gpu relaxation inference

Tests are quite slow; is there a way to choose just one surface (like 111) in the configs? @KirbyBroderick

Tests are quite slow; is there a way to choose just one surface (like 111) in the configs? @KirbyBroderick

I know of a way to pretty easily do this. Can implement some changes


Thêm api lấy dữ liệu Tiếng Việt từ Concept5

Tham khảo: http://conceptnet.io/
ConceptNet is a freely-available semantic network, designed to help computers understand the meanings of words that people use.
ConceptNet is used to create word embeddings -- representations of word meanings as vectors, similar to word2vec, GloVe, or fastText, but better. https://github.com/commonsense/conceptnet-numberbatch

Not necessarily! Feel free to re-open with more attractive reason.


List/Edit Bug with Image Thumbnails in 0.9.4-beta.18

Describe the bug
In views (type list) images work fine if it's set to "show image".
If the image is set to a specified size, that size is ignored.
If the image is set to "Click to Expand", the click to expand function is ignored.
This has been a bug for a long time.   My workaround has been to set the properties I wanted for the thumbnail and click Next, at this point the preview would be correct. If I exited out of the Configure there, then my thumbnails would be correct. (If I clicked Next again instead, it would break.)
Starting with 0.9.4-beta.18 (docker image bdde9744b3e02625fb62df7a9609800b58f621ea1b4168c5ef4f583899f1dfb9) the workaround no longer works if I edit the list.  (If I do not edit the list, it works okay.)
This means that now I cannot edit any of my List Views that have thumbnails because they will break.

fixed in #2336

fixed in #2336. Thumbnails should be working fully, no need for workarounds

Awesome! I look forward to trying it out whenever it gets pushed as the docker image.

Tested, works great now thank you very much!


Simplify environment yamls

Description
Remove old duplicate environments and add new ones
Todos

[ ] related to: #41
[ ] go through different modules / scripts and make compartmentalized environments.

Questions
Status

[ ] Ready to go

Codecov Report

Merging #128 (4f727af) into main (ec18d42) will increase coverage by 0.00%.
The diff coverage is n/a.


ZeroDivisionError: integer division or modulo by zero

Hello author, I have completed FTR.train. When doing BATCH TEST, I used my own TEST and MASK data sets of 100 each.Input code: python FTR_inference.py --path ./ckpt/zits_mural --config_file ./config_list/config_ZITS_places2.yml --GPU_ids '0'

yml:

After that I changed TEST_MASK_FLIST to /home/liu/WH/ZITS_inpainting-main/mural_datasets/mask_10/Test_mask_10

Hi, TEST_MASK_FLIST should be a directory of masks. And we define 'self.log_file' during training, you can modify the codes if you want to save the test results to a file:
https://github.com/DQiaole/ZITS_inpainting/blob/208fe52e62c3c126aec0823cadc11081f32d90cb/src/FTR_trainer.py#L287


Enable saving weights to the Database

We should use GridFS to save big numpy arrays to the database. That would enable saving the weights of the network alongside the experiment.

This is possible with the new add_artifact call


How to do partials with other engines

Specifically HAML
how does one render a partial?

Since this is more of a support question, would you mind opening your question on stack overflow? Feel free to use the metalsmith tag, I'd be more than happy to help you there.
Closing now, but feel free to link to your question on SO, or reopen if this is a bug report.

My thinking for putting on here was that one established it might be suitable to put in a pr for the readme

I understand. Problem is that there are a lot of supported engines, and putting engine specific instructions in the readme would make the readme way too large. Which is why I recommend SO, as I'm monitoring the metalsmith tag there and can help you there just as easily.
Also that way other people will be able to weigh in and your question can be easily found through google.


test: use T.Setenv to set env vars in tests

Description
This PR replaces os.Setenv with t.Setenv. Starting from Go 1.17, we can use t.Setenv to set environment variable in test. The environment variable is automatically restored to its original value when the test and all its subtests complete. This ensures that each test does not start with leftover environment variables from previous completed tests.
References

Reference: https://pkg.go.dev/testing#T.Setenv
Review Checklist

[ ] I have added documentation for new/changed functionality in this PR or in openfga.dev
[x] The correct base branch is being used, if not main

 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.


Generate alarms in firmware for sensor disconnection and low battery power

This PR adds:

alarms for sfm drivers connection loss
Low battery alarm for battery power less than 30%
Critical battery alarm for battery power less than 5%

Observations from testing:

Sensor disconnection/connection alarm is triggered only once and the backend/frontend needs to be restarted for the change to take place.

The battery alarms look good in testing, for both the firmware and the backend. Right now our implementation assumes that activation of a new alarm event will not cause alarms to be automatically unmuted - I believe that's what we decided to do, so this assumption is reasonable. If one day we decide to make generation of a new alarm event automatically unmute alarms, then when we're charging the battery from wall power and it goes from 5% to 6%, alarms will be unmuted - which is undesirable. I don't think we need to worry about this.
For how the frontend displays the sensor disconnection events, I'd suggest that the event text should be "Internal sensor failed", and then the Details text should say which sensor was lost, e.g. "O2 sensor connection lost". Otherwise, everything looks good to merge. For records-keeping:

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too?
Were any of these contributions also part of work you did for an employer or a client?
Does this work include, or is it based on, any third-party work which you did not create?

Added change for label and detail

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too? Yes.
Were any of these contributions also part of work you did for an employer or a client? No.
Does this work include, or is it based on, any third-party work which you did not create? No.


Integrating Slack

https://hawkins.gitbook.io/dispatch/administration-guide/incident/plugins/configuring-slack
Following the above documentation, I have set the required env vars in my .env file :
SLACK_APP_USER_SLUG
SLACK_API_BOT_TOKEN
SLACK_SIGNING_SECRET
SLACK_WORKSPACE_NAME
However, I am having issue getting Slack integrated with dispatch.
When I try to enable events with this endpoint : https://[REDACTED]/api/v1/events/slack/event, I get the following message.

Is that endpoint available publically? If you're behind a firewall or VPC I would recommend using socket mode instead: https://hawkins.gitbook.io/dispatch/administration-guide/incident/plugins/configuring-slack#socket-mode

@sumansid is https://[REDACTED]/api/v1/events/slack/event publicly facing? Slack needs to be able to reach out to it.

right, the endpoint isn't publicly facing. I will use the socket mode.


Could not access sufficient Git history

Summary
Receive error "Could not access sufficient Git history. Add 'fetch-depth: 0' as a parameter to the 'actions/checkout' action." ever after adding fetch-depth parameter.
Reproduction Steps
Create workflow yaml file as per below. Execute workflow as part of PR status check.
name: PR Metrics
on:
  issues:
    types:
      - opened
      - edited
      - closed
      - reopened
  pull_request_target:
    types:
      - opened
      - edited
      - closed
      - reopened
      - synchronize
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout
      uses<EMAIL_ADDRESS>      with:
        fetch-depth: 0
    - name: PR Metrics
      uses<EMAIL_ADDRESS>      env:
        PR_METRICS_ACCESS_TOKEN: ${{ secrets.PR_METRICS_ACCESS_TOKEN }}
      continue-on-error: true

Additional Information
Repository is private if that has any implications.

Hi @philcart, thanks for trying out PR Metrics.
I don't believe the private repo should be a problem, as long as all branch history is available to PR Metrics. The issue appears to indicate that is not the case – the message you're receiving is a wrapper around the underlying Git response that it couldn't get the branch diff against main (or your custom target branch).
To help debug further, could you:

Tell me which branch your PR was created on and the branch you intend to merge it into.
Tell me if the branch you're merging into is your main branch.
Provide me with the debug output for the execution. You should be able to activate this by following the instructions at https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.

@muiriswoulfe debug output logs are attached. Noticed that unlike Azure DevOps it doesn't include the actual workflow file, so I've added that into the zip.
The PR is merging a feature branch into our main branch.

logs_6827.zip

@muiriswoulfe changing the trigger to pull_request has done the job. Cheers


Adding a video preview/stream method?

Description
In video mode, how could we re-activate the preview, after a record.stop()?
It could be useful in case of a countdown before a new recording.
Steps to reproduce

player.recorder.getDevice() -> camera preview
player.recorder.start() -> camera preview
player.recorder.stop() -> recorded video cover (fixed)
player.recorder.start() -> camera preview

Expected result

player.recorder.getDevice() -> camera preview
player.recorder.start() -> camera preview
player.recorder.stop() -> recorded video cover (fixed)

4. player.recorder.preview() -> camera preview

player.recorder.start() -> camera preview

Actual
Using recorder.stopDevice() then recorder.getDevice() works, but the browser will ask for camera access again, which is annoying.

Using recorder.stopDevice() then recorder.getDevice() works, but the browser will ask for camera access again, which is annoying.

I believe this isn't the case in Chrome, once you give permission you don't have to do it again. Can you confirm this?

I believe this isn't the case in Chrome, once you give permission you don't have to do it again. Can you confirm this? <

That is correct, Chrome doesnt ask twice. But firefox does, and probably others, I have to try.

what do you mean with "recorded video cover (fixed)"? <

The player replaced the camera feed by a still image (the first image of the recorded video).

But firefox does, and probably others, I have to try.

There is a Firefox pref (media.navigator.permission.disabled) to disable the permission check, but this is probably not an option for you?

Any feedback @jipema?

@jipema you can use player.record().startVideoPreview() (for audio-video or video-only mode) to show the video preview window. The state of the play/pause/record etc will be the same. Does that work for you?
In videojs-record < v2.0.0 it's player.recorder.startVideoPreview().


[Q] Search always returns "Nothing matched your query"

Hi,
My new graphite setup is working quite well EXCEPT the search button. Whatever I enter, I get "Nothing matched your query". No errors in apache or wsgi logs.
Any ideas?
Thanks!!

Sorry, search functionality is broken long time ago. Usually, people just
browsing metric tree.
On Thu, 13 Feb 2020 at 00:51, gerases<EMAIL_ADDRESS>wrote:

Hi,
My new graphite setup is working quite well EXCEPT the search button.
Whatever I enter, I get "Nothing matched your query". No errors in apache
or wsgi logs.
Any ideas?
Thanks!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/2540?email_source=notifications&email_token=AAJLTVWT5EKJDX4JUVO5PELRCSDPVA5CNFSM4KUGWCI2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4INDKKUQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJLTVQQ3POBEWDIJ7AFGU3RCSDPVANCNFSM4KUGWCIQ
.

Hi Denis,
In which version did it stop working?
We're using graphite-web-0.9.16 everywhere and the search is working everywhere except on the new cluster I set up. Can I increase logging level somewhere to see where it's failing?
Thanks!

Ah, maybe I wrong. Never used that before. Please note that /opt/graphite/bin/build-index.sh exists and running periodically. This should update metric index (located somewhere in /tmp/graphite-test-xxxx/index)

Yep, found that by looking at metrics/search.py. It turns out that the index builder hard codes the whisper directory to /var/lib/carbon/whisper
...
WHISPER_DIR="/var/lib/carbon/whisper"
...

In my case it's in a completely different location. I created a symlink from /var/lib/carbon/whisper to ACTUAL_PATH and it did the trick :)
I'm not sure if the newer version of that script is smarter and actually relates the directory to local_settings.py somehow.
Anyway, I'm glad I see why it was not working. On my other systems the default locations are used for whisper data and so the index is correctly built.


✨ Feature Suggestion | Explain anti-recommendations too

Description
When I view a page such as https://www.privacytools.io/software/passwords/ I read the text:

If you are currently using a password manager software like 1Password, LastPass, Roboform, or iCloud Keychain, you should pick an alternative here.

The immediate question raised is "what is wrong with 1Password, LastPass, etc?".
So, I think it would be good if there was a section on each page, underneath Worth Mentioning and Related Information, which would namecheck a few pieces of software or services and explain why each is not recommended. This would better help people understand why they should use one of the recommended items.
Having such a list of anti-recommendations would reassure readers that you have evaluated the alternatives. Also it would mean that when something such as Startpage or Wire is delisted, users don't think that you just are unaware of them and use them anyway, or suggest them to be added to your list.

While this is a good idea, it's worth waiting until the comprehensive criteria sections are completed for each page. (I think the team were working on something like that, but cannot remember where I
read it?) They will state clearly what sort of requirements the software/service needed to meet, after which you could easily infer why certain services did not measure up.

Thank you. Yes, I would welcome documented criteria for inclusion on each page/category, and I look forward to that. That would definitely help with understanding and transparency.

Thing is though, we generaly want to be sure that what we list is up to date, which is already hard enough as is with us only recommending stuff. have an anti recommendation means that we also have keep an eye on in the case that anything changes there.

Thanks for the replies. To be clear, I wasn't proposing a list that would be very long or detailed. Just a sentence or two about the most popular non-private alternatives.

If there are services being widely used by people whom believes it helps their sec. and or privacy bit actually doesn't or has multiple contra-indications.
If that is clear as day for, and there is a consensus on that issue.
A disclaimer about 2-3 apps per category with a real short rundown on, why not to use it.
I don't see that hurting but I haven't been running any such site so these are just my two cents.

I agree with @GintokiHub that it would help explain problems with commonly used services that have are not recommended. Similar to @JohnVeness I too wonder what is "wrong" with these common password managers. The only reference to any 1Password or LastPass issues I found in this repo is that they don't play nice with Linux: https://github.com/privacytools/privacytools.io/issues/722#issuecomment-454478537
Specifically, I've reviewed the security design of 1Password (https://1password.com/files/1Password-White-Paper.pdf) as well as iCloud Keychain (https://support.apple.com/guide/security/icloud-keychain-overview-sec1c89c6f3b/web) and both seem fairly well thought out and secure. 1Password has been designed so the company cannot access passwords either due to insider risk or government compulsion. Apple iCloud Keychain is similarly designed, as long as users have a strong recovery key set. Neither are open source though, so all of the claims cannot be completely verified (as may be the case with Bitwarden).
Simply because the encrypted data is in the hands of another entity, and that the tools are not open source, shouldn't be reason enough to recommend against their use. However, if there are specific, known, and documented reasons against recommending these commonly used tools, especially password managers, I feel it would help the site make a more compelling case for better tools, and help people choose better tools if those reasons are explained.


Add Vala

https://github.com/desiderantes/awesome-vala
A curated list of libraries and resources for the Vala programming language
PRs reviewed: #1630, #1609
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Great! Was you the creator of that awesome list? Congratulations!

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

@vinibeloni - as with the F# awesome list PR, please add a project image as stipulated in the guidelines. Thanks! 😄

That's the issue. Vala has no official artwork, so any image I add would be pretty useless since it would probably not represent the language. Guidelines said add a project image whenever possible, but in this case I don't think it makes sense to have one.

What about this one? https://en.wikipedia.org/wiki/Vala_(programming_language)#/media/File:Vala_Logo.svg
No need for it to be official - it just makes it easier to distinguish the document from other READMEs, at least.

Looks good:
⠙ Linting(node:55103) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
✔ Linting`

Not sure if you forgot or missed it but just needed to point out this particular item:

To verify that you've read all the guidelines, please add comment with just the word unicorn.
🙂

Updated the list, now it has a proper image

@sindresorhus please review it again

Tweet: https://twitter.com/awesome__re/status/1197933315577090048

Also note: https://github.com/sindresorhus/awesome/commit/b9338ca9226bf2dabacb46a847dd5f9db1856821


[node][cypress] wsjson read error

{
  "service": "node",
  "timestamp": "2024-08-09T06:05:44Z",
  "level": 3,
  "message": "wsjson read error",
  "fields": {
    "error": "failed to read JSON message: failed to get reader: received close frame: status = StatusNormalClosure and reason = \"\""
  },
  "occurrence_count": 1567
}

should be probably fixed through
https://github.com/Bisonai/orakl/pull/2062/files


feat: Kakarot Rpc method "eth_getTransactionReceipt"

eth_getTransactionReceipt
Metadata

name: getTransactionReceipt
prefix: eth
state: ⚠
specification

Specification Description
Describe the method
Parameters

Address : address
Block : BlockTag

Returns

BlockCount : uint

Kakarot Logic
Describe the interaction with Kakarot and/or Starknet.
e.g. "this method does not interact with the kakarot contract or any other starknet contract."
Kakarot methods
Which Kakarot methods are called?
Starknet methods
Which Starknet RPC methods are called? e.g. "Would be calling the corresponding starknet_getTransactionReceipt https://github.com/starkware-libs/starknet-specs/blob/master/starknet_vs_ethereum_node_apis.md"

Is someone on this issue?

Yes


Constantly getting Offset is outside the bounds of the DataView error

Hello,
I've just downloaded the latest version of cropper. I've got a div and inside that I've got an img object that I want to crop. When I try to initialize cropper:
     `$(image).cropper({
                    aspectRatio: 1,
                    crop: function(e){
                        debugger;
                    }
                });`

I'm getting Uncaught RangeError: Offset is outside the bounds of the DataView in my browser's console (latest Chrome). My image displays normally, with no cropping support as if there's no cropper.
How can I solve it?

Nevermind, it was an error at my side. Fixed it.

hi @canpoyrazoglu , how were you able to fix this issue? I ran into a similar issue. I'm using the latest Firefox. It works great in Chrome though.

hi @canpoyrazoglu , how were you able to fix this issue? I ran into a similar issue. I'm using the latest Firefox. It works great in Chrome though.

@ricpumanes I've quit that project long ago, but as far as I remember I ended up changing many things with the CSS, as the cropper area was breaking very easily.

Recommands to use jquery-cropper which may have not this problem.


Fix #1122 Added concurrent structures to ThriftTransportPool

Also contains suggestions for removing syncrhonized blocks
Syncrhronized blocks of text are commented out in the diffs below.  These may not be necessary if the object constructs handle write/delete concurrency. But maybe they are not that costly.
Additionally - I have a question on the section of code below.  The connections are closed specifically after the sync block.  It seems that since the "unreserved" is read and not deleted from then someone could use one that is designated to close by the sync blck.
    synchronized (pool) {
         for (CachedConnections cachedConns : pool.getCache().values()) {
           Iterator<CachedConnection> iter = cachedConns.unreserved.iterator();
           while (iter.hasNext()) {
             CachedConnection cachedConnection = iter.next();

             if (System.currentTimeMillis() - cachedConnection.lastReturnTime > pool.killTime) {
               connectionsToClose.add(cachedConnection);
               iter.remove();
             }
           }

           for (CachedConnection cachedConnection : cachedConns.reserved.values()) {
             cachedConnection.transport.checkForStuckIO(STUCK_THRESHOLD);
           }
         }

         Iterator<Entry<ThriftTransportKey,Long>> iter = pool.errorTime.entrySet().iterator();
         while (iter.hasNext()) {
           Entry<ThriftTransportKey,Long> entry = iter.next();
           long delta = System.currentTimeMillis() - entry.getValue();
           if (delta >= STUCK_THRESHOLD) {
             pool.errorCount.remove(entry.getKey());
             iter.remove();
           }
         }
       }

       // close connections outside of sync block
       for (CachedConnection cachedConnection : connectionsToClose) {
         cachedConnection.transport.close();
       }

Wrong branch was submitted.  I am closing this and resubmitting.


Blobs: nested folder support

creating a blob with the uri : Windows/7/Python/python.exe should create the folders Windows, 7, and Python .

It does (in the sense that blob folders in Azure are completely virtual) - we just display them in a flat list.

Closing pending customer feedback.


Fixed requests_get_timeout and added schemata fields.

client.py:
Fixed missing token and query_id in requests_get_timeout, and the calls from send_request and get_statement.
schemata.py:
Added missing fields to EquitySummaryByReportDateInBase and TradeConfirmation.

Thanks.


Move clippy to linux tests

Going to close this: clippy gives different errors on stable vs nightly, and we don't want to deal w/that yet.


Event broadcasting is broken as of 0.3.17

For example: adding listener in \ias\applications\example\init\event.js so it will work in all instances after emit in any. But events are not broadcasting and on fires just in save server instance.
application.backend.on('test', function(data) {
  console.log('Event "test" received by: ' + application.nodeId);
  console.log('  data: ' + api.json.stringify(data));
});

if (application.nodeId == 'S1N1') {
    api.timers.setInterval(function() {
      application.backend.emit('test', { sender: application.nodeId, data: 'data' });
    }, 5000);
}

Console output:
  JSTP listen on <IP_ADDRESS>:250 by Master(30166/S1N0) Cloud Controller
  HTTP listen on <IP_ADDRESS>:38881 by Worker(30179/S1N1)
  HTTP listen on <IP_ADDRESS>:38882 by Worker(30180/S1N2)
Event "test" received by: S1N1
  data: {"sender":"S1N1","data":"data"}
Event "test" received by: S1N1
  data: {"sender":"S1N1","data":"data"}
...
Event "test" received by: S1N1
  data: {"sender":"S1N1","data":"data"}

While expected:
> Event "test" received by: S1N1
>   data: {"sender":"S1N1","data":"data"}
> Event "test" received by: **S1N2**
>   data: {"sender":"S1N1","data":"data"}

@dmitrystas now IPC (interprocess communication) is broken because moving from Impress RPC (with JSON serialization) to JSTP. I'll close this issue when it will work again.

Fixed via bb427730dbd730b1adaf35c7c81c65ab8cb6845e.


Fix broken anchor links to troubleshooting section

The Vagrant environment setup tutorial anchor links for the Troubleshooting & Common Errors section don't work in GitHub flavored markdown because the ampersand in the heading gets removed and the resulting space is filled with a hyphen. (See here: https://gist.github.com/asabaylus/3071099#gistcomment-1593627)
To make anchor links work with ReadTheDocs as well as with GitHub markdown for the time being, this commit changes ampersand in the heading to 'and.'
This fixes #7056

Merged, after line-wrapping the long lines in the commit message.  Thanks @aklap!


Add ULID Data Type.

Please add support for ULID data type https://github.com/ulid/spec
( It's a much more practical version of UUID. )
Thank you.

Feel free to add support for it. I'll review the Pull Request when it's done.


I'd like to join this project's community

Your public repo
https://github.com/jevinifer/gov4git-identity-public.git
Your public branch
main

Have you contributed to the project yet?

Hi Glen, I have not yet git pushed the chapters I translated into Germen (chapters 0, 1, 5, 7).

Didn't realize it was you!

Approved

 Follow up
On Wednesday, 29-May-24 03:42:11 UTC by Gov4Git dev
@jevinifer was added to the community.


style="background-image[...] becoming style=background:[...]

Hello, I'm using zola for a project, and I'm running into an issue with its minify, which I think uses minify-html.
The issue I was having came when using CSS and style attributes simultaneously, specifically style=background-image: url('[...]'), while using other CSS to control the other aspects of the background image (like position, size, etc...). I think minify-html (or is it lightningcss?) changes background-image to background, but in this case it's not just minifying but changing the meaning, since the style attribute will override the CSS, and the background property is short hand for all background properties expressed together.
For now I have a workaround by just turning of minification, but I wanted to come here and ask if there's any advice? Maybe there's a setting or something that I can submit upstream to Zola? Thank you.

The quotes cause this issue. Need an option to disable removing quotes for attributes on the minify HTML end.
But also as explained https://github.com/wilsonzlin/minify-html#spec-compliance here. Minify HTML will respect the spec. Seems Zola's parser isn't playing well with the standard

Hi @SettingDust , thank you for responding.
I included a slight typo when I originally posted, which I've now corrected to make the situation more clear, but I don't think it changes anything. So, thank you for your patience, and please bear with me while I try to elaborate.
This is a real example, taken from the issue that I'm seeing:

When minify is off this works as expected

But when minify is on this does not work as expected

I read the README you sent, but with my typo corrected I don't think that is applicable here. However, just to be safe, I tried thing with the typo still in place (and removing the quotes like you said), and the problem is still there. Furthermore, I ran the code through the recommended validator and there was no issue like that brought up.
However, I do see a potential cause of my issue in the README:
### Attributes

Any entities in attribute values are decoded, and then the shortest representation of the value is calculated and used:

- Double quoted, with any `"` encoded.
- Single quoted, with any `'` encoded.
- Unquoted, with `"`/`'` first character (if applicable), any `>`, and any whitespace encoded.

According to this minify-html takes "any entities in attribute values" and then the "shortest representation of the value" is calculated and used. Therefore it appears that minify-html is taking background-image as a value and calculating that some space can be saved by converting that to a background CSS rule. This is confirmed in the resulting HTML:

In this particular example, this change results not merely in a syntactic different but an actual semantic difference.  background is not the same thing as background-image, because background will override any CSS rules that were meant to go in addition to background-image. In this case, those rules were set by the CSS classes bg-cover and bg-center, which are classes that set background-size: cover and background-position: center, respectively.
I believe the correct minifcation would be to leave the same semantic meaning in place, which is to do nothing since there is no way to make background-image shorter without knowing what other rules are being used alongside it.
Now that I've explained that does that make the issue more clear? Sorry for the typo earlier,  style="background-image:url('{{ slide.thumb.src }}')" !=  style=background-image:url('{{ slide.thumb.src }}'). However, with all of that out of the way, does your point about the quotes remain the underlying cause or could it be there is a mistake with the minifcation?
Thanks for taking the time to read this.


Where does initialState come from?

I stared at this for quite a while now but I can't figure out two things:

Where does the initialState come from? I can see in that server render-routes middleware that the compiled server entrypoint is called via yield runRouter but only location is passed in. In the server entry point I can see that Router.run is called and has a function as a parameter that takes initialState but how does thisnvariable ever get set to anything?

All other starter-kits that I found do something like de-hydrating and re-hydrating the initialState by dumping the state that was used by the server as a variable into the global document scope so that the client render can pick it up again. Why is this not necessary in this starter-kit?

Bonus question: Usually my routes would need to fetch data from APIs onEnter, how would I do this here so that it still works with server sode rendering (needs to wait until everything is fetched).

Hey, you're right - there is no way to provide initial state like this at the moment. It's something I've been meaning to get around to but just haven't; the server implementation could use quite a bit of love. So it's not that it's not necessary in this starter kit for some reason, I just haven't done it yet.
Sorry for the inconvenience; I'll make this a bigger priority and try to take a look at it early next week and see what can be done.

Thanks for the quick answer!  If you ever get around that de/re-hydration problem, I think this would be one of the best starter kits around.

Hey @mbrochh, I added the ability to inject initial state; it's currently on the master branch: https://github.com/davezuko/react-redux-starter-kit/blob/master/server/index.js#L25-L32. There's still some improvements I'd like to make to it, but one of the things holding me up is the current structure of the app, where the server doesn't have direct access to the source code (it just consumes some convenience methods compiled from ~/client/entry-points/server).
Given this setup, I'm not sure how to go about solving your bonus question (in fact I've never even done this, so it's entirely new to me). I'll try to check out some other universal apps and see how they solve the issue, but this server configuration was intentional. In fact, one of the reasons I even built this starter kit was because I wanted to be able to use more of what Webpack has to offer (sass imports, for example), which is something that a lot of boilerplates just avoid altogether. So far the easiest solution is to just join that group and refactor the starter kit to only allow JS imports, but I'm not yet convinced it has to come to that, even though a better solution eludes me.

Deferring to https://github.com/davezuko/react-redux-starter-kit/issues/71.


forwardedRef prop doesn't drill through styled(Wrapper)

Please see https://github.com/styled-components/styled-components/pull/2223 for an explanation and an attempted patch. Thank you!

Closing this issue as there is a better resolution in store.


Proposed: Log HTTP responses

Summarizing our slack discussion here, re. using zap.Binary() to effectively base64-encode the response body in the logs:

Matthew: "if the server is sending an error, I think it’ll be more ergonomic to see the error directly in the log." (for example, this makes searching for error generically more effective")
Proposal: check if all response bytes are between ‘ ‘ and ‘~’ and if so, log the body using a zap.String, otherwise using zap.Binary

Problem: makes automation impossible, since the format of the message (the value for "body") is undefined.

Proposal: changing key could address some of that —”body” if cleartext, ”bodyB64” if not

Problem: someone writing an analysis needs to know that this ("body") is a "oneof" type field, which they can only determine by reading the code.  So if customer-eng is writing something to look for known issues, and they aren't aware that the body key can be different depending on the content of the http response, then their analyzer will just miss half of the issues.

Proposal: encode body as base-64 always, and include errorBodyText (encoded as plaintext) with the body encoded as cleartext only if the response code is an error?

Accepted
An alternative would be to combine the other two proposals, and log the body with errorBodyText as base-64-encoded text if the response is not an errork, and body as paintext if not.

Noting the post-review changes,

the low-level changes (factoring out the user-agent == Envoy check into a boolean, pre-allocating bodyBuf, etc) are all done
We log the body even for non-error requests (and additionally log the body in cleartext for error-ed requests, as noted above). We log the response headers, but do not log them before responding with the entire body; slow requests will delay the response log
We don't handle multi-part responses


Statically typed look aheads

In juniper-from-schema we have a feature called QueryTrail. That is basically a type safe look ahead that guarantees that you only check for valid fields. I've been thinking if something like that would make sense to have in juniper. I've also thought of a way to implement it.
How QueryTrail works in juniper-from-schema
The current look ahead API looks something like this:
let lh = executor.look_ahead();

let lh = lh.select_child("user")
  .and_then(|lh| lh.select_child("city"))
  .and_then(|lh| lh.select_child("country"));

if let Some(_) = lh {
  // user.city.country was part of the query
}

This works well but has two downsides

Because select_child returns an Option you have to chain with and_then or ?. That isn't very ergonomic.
The keys are strings so you risk making typos or otherwise checking for fields that don't even exist.

In juniper-from-schema I solve these issues with an abstraction I call QueryTrail. It is basically a wrapper around a LookAheadSelection with a PhantomData for the particular type in the schema the LookAheadSelection corresponds to. The definition is:
pub struct QueryTrail<'a, T, K> {
  pub look_ahead: Option<&'a LookAheadSelection<'a, DefaultScalarValue>>,
  pub node_type: PhantomData<T>,
  pub walked: K,
}

walked: K is to know statically whether the look ahead path you've built up has been checked against the query. K will always be one of two types:
struct Walked;
struct NotWalked;

Imagine we have a schema like this:
type Query {
  user: User
}

type User {
  city: City
}

type City {
  country: Country
}

type Country {
  id: ID
}

At compile juniper-from-schema walks over your schema and adds methods to QueryTrail for the fields of each type. Something like:
impl<'a, K> QueryTrail<'a, Query, K> {
    pub fn user(self) -> QueryTrail<'a, User, NotWalked> {}
}

impl<'a, K> QueryTrail<'a, User, K> {
    pub fn city(self) -> QueryTrail<'a, City, NotWalked> {}
}

impl<'a, K> QueryTrail<'a, City, K> {
    pub fn country(self) -> QueryTrail<'a, Country, NotWalked> {}
}

impl<'a, K> QueryTrail<'a, Country, K> {
    pub fn id(self) -> bool;
}

For each resolver you then get a QueryTrail where T is the type the resolver returns:
impl QueryFields for Query {
    fn field_user<'a>(
        &self,
        _: &Executor<'a, Context>,
        trail: &QueryTrail<'a, User, Walked>,
    ) -> FieldResult<User> {
        // ...
    }
}

This QueryTrail is constructed using MakeQueryTrail.
Since we get a QueryTrail<'a, User, Walked> we're only allowed to call .city(). That is the only method we generated for QueryTrail<'a, User, K>. For example we cannot call .country() because the requires a QueryTrail<'a, City, K>, which we don't have. This is how we're guaranteed to not look for fields that don't exist on the current type.
There is one more important method on QueryTrail:
impl<'a, T> QueryTrail<'a, T, NotWalked> {
    pub fn walk(self) -> Option<QueryTrail<'a, T, Walked>> {}
}

Notice that .user(), .city(), etc, all return QueryTrail<'a, T, NotWalked>. To turn this into a QueryTrail<'a, T, Walked> we have to call .walk(), which returns an Option<QueryTrail<'a, T, Walked>>. That means we're also forced to check that we get a Some back.
The implementation of .walk() just to check that the look_ahead inside self is a Some and if so return a QueryTrail<T, Walked>.
All this put together means we can write code like this:
fn eager_load_countries<'a>(
    country_ids: &[i32],
    trail: &QueryTrail<'a, Country, Walked>,
    ctx: &Context,
) -> Vec<Country> {
    // ...
}

if let Some(country_trail) = trail.user().city().country().walk() {
    eager_load_countries(&country_ids, &country_trail, ctx);
}

By taking QueryTrail<'a, Country, Walked> we're guaranteed that country is part of the query, because the only way to get a Walked is to call .walk() which performs the check an Option.
This means we're guaranteed that we don't eager load unnecessary data. This is exactly what juniper-eager-loading does.
We also generate code for looking at arguments. You can read about that here.
Aside about inherent impls
Actually we don't generate the methods directly on an impl QueryTrail block like shown above. That isn't possible because QueryTrail is defined in juniper-from-schema itself. It is defined there such that juniper-eager-loading can depend on it. If QueryTrail was put directly into the user's code that wouldn't be possible.
So the way we actually add the methods is through extension traits. For each type we generate a trait called something like QueryTrailUserExtension which has methods for each field. All those traits are put in the same module so users can import them with use query_trail::*.
Adding QueryTrail to juniper
The fact that the methods are added to QueryTrail via extension traits technically means that we don't need to know the whole schema up front. #[juniper::object] could also generate these traits.
There is an issue of making it easy for the users to import the traits so they can call the methods. I'm not quite sure how to solve it. I would imagine the compiler would be good at suggesting what to import however. Since we don't generate all the traits all at once we can't easily put all of them in the same module.
I see there is a fair of type "magic" going on but I think the guarantees you get are very useful.
What do you think? Is this something that makes sense to add to juniper? If so I'll cook up a PR.

This definitely makes sense, and I have very much wanted type safe look-ahead myself previously.
When thinking about this I came up with a slightly different design approach that doesn't require traits.
Basically it involves generating a lookahead struct for each object type and having an extra type Lookahead on GraphQLType.
It has the benefit of working without importing extension traits and not requiring a walk() method.
trait GraphQLType {
...
  type Lookahead;
}

Example:
struct User;

#[object]
impl User {
  fn best_friend(&self) -> Option<User> { ... }
}

impl GrahQLType for User {
  ...
  type Lookahead = UserLookahead;
}

// GENERATED code:

struct UserLookahead<'a> {
  selection: &'a juniper::LookaheadSelection,
}

impl UserLookahead {
    fn best_friend(&self) -> Option<<Friend as GraphQLType>::Lookahead> { ... }
}

Ah, I just noticed that this has a problem: it would require GAT (generic associated types) to be implemented, since the lookahead type contains a lifetime...

Hm true. I wonder what the implications would be to add that lifetime to GraphQLType so
impl<'a> GrahQLType<'a> for User {
    type Lookahead = UserLookahead<'a>;

    fn resolve_field(
        &self,
        info: &(),
        field_name: &str,
        args: &Arguments,
        executor: &Executor<'a, Database>,
    ) -> ExecutionResult {
        // ...
    }

    // ...
}

Having UserLookahead::best_friend return an Option is also a minor inconvenience if you want to look for deeply nested fields. Something like user_look_ahead.best_friend().city().country(). Then you end up chaining either with and_then or ?.
Whether this actually comes up in practice I don't know. In my experience I mostly look "one level down" and in that case it isn't an issue.

Having UserLookahead::best_friend return an Option is also a minor inconvenience

True. I actually think your approach is better. We can always return the lookahead type and add a walk() or resolve() method to get an actual value out at the end.
Makes more sense.

I wonder what the implications would be to add that lifetime to GraphQLType so

Sadly not possible since the lifetime is not related to the type implementing the trait.
The lifetime would have to be stored in a PhantomData, which is not possible here.
Actually we could remove the lifetime requirement by cloning the data in the lookahead. It's a tree of selected fields and arguments , so it's not terribly expensive to clone.
We would need to clone again though at every nested step. (Or put the tree in a Arc to the top level selection and have the lookahead types keep track of the nested path in a Vec<String> )
Note that this design would actually also require:
trait LookaheadBuild {
  fn build(sel: &LookaheadSelection) -> Self;
}

trait GraphQLType {
  type Lookahead: LookaheadBuild;
}

I actually think your approach is way more elegant, especially the type machine style of Walked/NotWalked.
The downside is the need to import the various traits. juniper-from-schema could generate a prelude module that contains all this, but with regular juniper the compiler messages could be a bit confusing and importing a trait that doesn't exist in your code would feel a little bit weird. (eg use users::UserLookaheadExt)
The downside to the alternative is potential cloning of the selection tree.
I'll think a bit more about which approach is better, and I'm happy to hear your thoughts (and others).

Sadly not possible since the lifetime is not related to the type implementing the trait.

Are you sure? I do something similar in juniper_eager_loading::EagerLoadChildrenOfType. That trait has a lifetime which is only used in the QueryTrail argument of one method.
trait EagerLoadChildrenOfType<'a, ...> {
    fn eager_load_children(
        nodes: &mut [Self],
        models: &[Self::Model],
        db: &Self::Connection,
        trail: &QueryTrail<'a, Child, Walked>,
        field_args: &Self::FieldArguments
    ) -> Result<(), Self::Error> { ... }
}

Making implementations like
impl<'a>
    EagerLoadChildrenOfType<
        'a,
        Country,
        EagerLoadingContextUserForCountry,
    > for User
{
    type FieldArguments = CountryUsersArgs<'a>;
    ...
}

works fine. There is a complete example here.
There might be some subtleties I'm missing.

One thing we should keep in mind though is that it must be possible to build libraries that depend on these look ahead types. That might influence the design. However both
fn eager_load_countries(
    country_ids: &[i32],
    trail: &QueryTrail<'_, Country, Walked>,
    ctx: &Context,
) -> Vec<Country> {
    // ...
}

or
fn eager_load_countries(
    country_ids: &[i32],
    trail: &<Country as juniper::GraphQLType>::LookAhead,
    ctx: &Context,
) -> Vec<Country> {
    // ...
}

would probably work fine.

but with regular juniper the compiler messages could be a bit confusing and importing a trait that doesn't exist in your code would feel a little bit weird

Yes that is pretty awkward 😕 If only Rust had a "all proc-macros are done" sorta callback 😜


Support calling a local heroku-api

When trying to use a local heroku api host like
HEROKU_HOST="http://localhost:5001", the api client fails for a number
of reasons. First, protocol is not set, so it defaults to https. Second,
the port is not split out from the hostname so it attempts to lookup the
host using the portname. Third, the port is not passed in to the http
client. This patch fixes all of these issues.

Fix included in #74


DSEV: adjust recommendations according to content in cfg files

While working on a bug related to RPM and DSEV, I discovered that it uses ASET Avionics props, and most of the IVAs have been converted to use MAS to drive them (the RPM versions are still there but renamed to .txt)

@Angel-125 this look OK?


[FEATURE REQUEST] Enable passing Headers from a file

Is your feature request related to a problem? Please describe.
I often encounter frustration when required to specify multiple headers, especially lengthy ones like the Authorization header, directly through the CLI. Updating these headers involves manually removing and re-pasting them each time, which is time-consuming and error-prone. A more efficient approach would allow headers to be passed directly from a file.
Describe the solution you'd like
I’d like the ability to pass headers from a file, with each header specified on a separate line. The tool would read and apply each header listed in the file, simplifying the process of updating or adding headers without requiring direct CLI input for each one.
Describe alternatives you've considered
I've considered no alternative solutions that achieve the same convenience as file-based header loading.
Additional context
N/A

howdy!
it's not exactly what you're asking for, but version 2.11.0 added the ability to scan from a raw http request file e.g. from burp.

closing this one since the requested functionality exists in the linked feature. Please fee free to reopen/continue discussion if needed.


rootston: default meta key

Sensible defaults are here:
https://github.com/swaywm/wlroots/blob/master/rootston/config.c#L300
Maybe we want to move that piece there?

Sensible defaults are here:

Those only get applied if no config file is found.

If you provide a config file it's your responsibility to make sure it's good.

On the same note, there's a config->xwayland = true; right after, if we don't want a default meta key we may not want to enable xwayland by default too (but enable it if no config file is specified).

I could go either way on that change.


add kubernetes documentation links to avoid confusion

There are Kubernetes objects (Deployment and Service) and general ones (as in microservices).
Since both are here, to avoid confusion whether it's a general concept or a Kubernetes one, during Architect Review Board on last Thursday (December 1st), we decided to put Kubernetes link for the Deployment and Service related to Kubernetes.

@EdPrice-MSFT
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Update default SPs

Branching Reminders
X For core code changes, create a branch off develop

For product documentation changes, create a branch off main
Always name your branch in a way that clearly describes your proposed changes

Description

Consolidate google, tweak tags, switch to single Web PSE, update names & defaults
Related Issue(s)

DS-1816
Testing and Validation

Tested preloaded
Type of Change

[X] Bug fix or other non-breaking change that addresses an issue
[ ] New Feature / Enhancement (non-breaking change that add or improves functionality)
[ ] New Feature (breaking change that is not backwards compatible and/or alters current functionality)
[ ] Documentation (change to product documentation or README.md only)

Added db.sqlite3.dist


configure theme_style as dark

I'm wondering which file may configure theme_style as dark?
Thanks!

@elvawyf
Add theme_style: dark in ./Hexo/_config.yml

@elvawyf @asd7227600
In your blog's main _config.yml.
Just put it under your theme config so that you have them together in one place. That would be easier to manage if you want to modify them in the future.
Thought the question was answered. Checked this morning and found the bug in my README.md. :P
Sorry for the late reply.


WIP: Remoteworkitem TrackerQuery Refactor

Remoteworkitem: TrackerQuery Refactor
fixes issue #1681

@DhritiShikhar snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1777-2

@DhritiShikhar snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1777-3

@DhritiShikhar snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1777-4

@DhritiShikhar snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1777-6

[test]

Codecov Report

Merging #1777 into master will decrease coverage by 0.21%.
The diff coverage is 62.25%.

@@            Coverage Diff             @@
##           master    #1777      +/-   ##
==========================================
- Coverage   63.46%   63.25%   -0.22%
==========================================
  Files         127      127
  Lines       11669    11656      -13
==========================================
- Hits         7406     7373      -33
- Misses       3588     3605      +17
- Partials      675      678       +3

Impacted Files
Coverage Δ

remoteworkitem/tracker_repository.go
64.28% <ø> (ø)
:arrow_up:

migration/migration.go
72.1% <100%> (+0.05%)
:arrow_up:

remoteworkitem/trackerquery_repository.go
67.9% <60%> (-16.05%)
:arrow_down:

controller/trackerquery.go
66.4% <63.33%> (+13.38%)
:arrow_up:

remoteworkitem/errors.go
0% <0%> (-33.34%)
:arrow_down:

remoteworkitem/jira.go
75% <0%> (-25%)
:arrow_down:

controller/tracker.go
53.27% <0%> (-13.94%)
:arrow_down:

remoteworkitem/scheduler.go
63.41% <0%> (+2.43%)
:arrow_up:

models/transaction.go
66.66% <0%> (+22.22%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@DhritiShikhar snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1777-8

@baijum @pranavgore09 can you please review this pr?


lazy blocking for final results

I was going over an example of yours where you and the scikit-image team showed that it was hard to get good performance from scikit-image algorithms and dask.
I decided to jump down the rabbit hole and found that there were probably 2 places that could probably be optimized:

Serialization/serialization of numpy arrays. You seem to have identified this one, and might come in later versions of numpy.
The final blocking of the result.

I think it many cases, making the final result a C_continguous numpy array is probably not necessary.
For the example here: (i7-7700HQ, 16GB of RAM, 4 cores + hyperthreading)
https://gist.github.com/hmaarrfk/ea6d364c2ce097f249b5c23a93214f31
Passing the arrays 4 arrays 50MB each, of around a threaded scheduler takes a few ms. while blocking the final result (200 MB) in a contiguous array takes 100ms+.
Have you considered returned a result as a blocked matrix that is not c-contiguous? Is this possible at the moment? I don't think I saw the option in the docs, but maybe I'm blind.
I don't know if getting rid of blocking might help map_overlaped as well.
CC: @jni

Have you considered returned a result as a blocked matrix that is not c-contiguous? Is this possible at the moment? I don't think I saw the option in the docs, but maybe I'm blind.

Did you have a target data structure in mind?  The way I would represent such a blocked matrix in Python is probably with a dask array.  You might consider looking at timings that use dask.persist, which returns a dask array rather than dask.compute, which returns a numpy array

Serialization shouldn't be a problem if you use a threaded scheduler

Thanks you for the info. Persist does mostly what is needed for the question I had. I guess I wrote off persist when I first read through the docs a few months back.
I was talking with @jni about parallelizing the computation of a Gaussian filter using Dask and the question of blocked operations came up. It made use of map_overlap which seems to a convenience function that calls overlap, map_blocks and trim.
Going a step further, it seems that trim returns blocks that are C-contiguous.

Any chance of returning memory views of the original arrays? (See benchmark below)
Any chance of having dask arrays with more transparent overlaps, ie. they would hold extra memory for the overlapping regions, but a call to np.asarray would omit copies of the overlapped parts?

from dask import array as da
import numpy as np

from skimage.filters import gaussian as gaussian_filter

shape=(150, 1024, 1024)
chunks=(-1, 512, 512)
dtype='float32'
z = da.zeros(shape=shape, chunks=chunks, dtype=dtype)
# This takes time 407 ms
%time _ = z.compute()
# This is fast. (24 ms) Thank you for hint!
%time _ = z.persist()

z_overlaped = da.overlap.overlap(z, 10, boundary='none')
# This is slow (450 ms)
%time _ = z_overlaped.compute()
# This is kinda slow (160 ms) but I understand why a memory copy is necessary.
%time z_overalaped_persisted = z_overlaped.persist()

# convenience function, inverse of da.overlap.overlap
# logic taken from map_overlap
def trim(x, depth, boundary=None):
    from dask.array.overlap import coerce_boundary, coerce_depth, trim_internal, add_dummy_padding
    boundary2 = coerce_boundary(x.ndim, boundary)
    depth2 = coerce_depth(x.ndim, depth)

    x2 = add_dummy_padding(x, depth2, boundary2)
    return trim_internal(x2, depth2)

# This takes 775 ms
%time trim(z_overalaped_persisted, 10, boundary='none').compute()
# This takes 488 ms, I wish it returned a memory view so as to return in 1ms.
%time trim(z_overalaped_persisted, 10, boundary='none').persist(scheduler='threads')

Is there a particular copy within one of the dask.array functions that you
believe might be safely removed?
On Tue, Sep 4, 2018 at 3:59 PM, Mark Harfouche<EMAIL_ADDRESS>wrote:

Thanks you for the info. Persist does mostly what is needed for the
question I had. I guess I wrote off persist when I first read through the
docs a few months back.
I was talking with @jni https://github.com/jni about parallelizing the
computation of a Gaussian filter using Dask and the question of blocked
operations came up. It made use of map_overlap which seems to a
convenience function that calls overlap, map_blocks and trim.
Going a step further, it seems that trim returns blocks that are
C-contiguous.

Any chance of returning memory views of the original arrays? (See
benchmark below)
Any chance of having dask arrays with more transparent overlaps,
ie. they would hold extra memory for the overlapping regions, but a call to
np.asarray would omit copies of the overlapped parts?

from dask import array as daimport numpy as np
from skimage.filters import gaussian as gaussian_filter
shape=(150, 1024, 1024)
chunks=(-1, 512, 512)
dtype='float32'
z = da.zeros(shape=shape, chunks=chunks, dtype=dtype)# This takes time 407 ms%time _ = z.compute()# This is fast. (24 ms) Thank you for hint!%time _ = z.persist()
z_overlaped = da.overlap.overlap(z, 10, boundary='none')# This is slow (450 ms)%time _ = z_overlaped.compute()# This is kinda slow (160 ms) but I understand why a memory copy is necessary.%time z_overalaped_persisted = z_overlaped.persist()
convenience function, inverse of da.overlap.overlap# logic taken from map_overlapdef trim(x, depth, boundary=None):
from dask.array.overlap import coerce_boundary, coerce_depth, trim_internal, add_dummy_padding
boundary2 = coerce_boundary(x.ndim, boundary)
depth2 = coerce_depth(x.ndim, depth)

x2 = add_dummy_padding(x, depth2, boundary2)
return trim_internal(x2, depth2)

This takes 775 ms%time trim(z_overalaped_persisted, 10, boundary='none').compute()# This takes 488 ms, I wish it returned a memory view so as to return in 1ms.%time trim(z_overalaped_persisted, 10, boundary='none').persist(scheduler='threads')
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3938#issuecomment-418498368, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszB1Wn8qZhG6n-vlvfCH3d4yho7p8ks5uXtuUgaJpZM4WYItL
.

@mrocklin thank you for replying so quickly. Benchmarking on the plane kept me busy.
I think I need to rerun benchmarks with a hacked up version of dask that doesn't hash every call to from_array. See Issue #3946

@mrocklin I'm mostly convinced that it is the issue outlined #3947
from dask import array as da

from dask.array.overlap import (coerce_boundary,
                                coerce_depth,
                                trim_internal,
                                add_dummy_padding)

shape=(50, 1024, 1024)
chunks=(-1, 512, 512)
dtype='float32'

def trim(x, depth, boundary=None):
    boundary2 = coerce_boundary(x.ndim, boundary)
    depth2 = coerce_depth(x.ndim, depth)

    x2 = add_dummy_padding(x, depth2, boundary2)
    return trim_internal(x2, depth2)

a00 = da.ones(shape=shape, chunks=-1, dtype=dtype).persist()
a01 = da.ones(shape=shape, chunks=-1, dtype=dtype).persist()
a10 = da.ones(shape=shape, chunks=-1, dtype=dtype).persist()
a11 = da.ones(shape=shape, chunks=-1, dtype=dtype).persist()

b = da.block([[a00, a01], [a10, a11]]).persist()
c = da.block([[a00[10:-10, 10:-10], a01[10:-10, 10:-10]], [a10[10:-10, 10:-10], a11[10:-10, 10:-10]]]).persist()
d = trim(b, 10, boundary='nearest').persist()
%timeit b = da.block([[a00, a01], [a10, a11]]).persist()
%timeit c = da.block([[a00[10:-10, 10:-10], a01[10:-10, 10:-10]], [a10[10:-10, 10:-10], a11[10:-10, 10:-10]]]).persist()
%timeit d = trim(b, 10, boundary='nearest').persist()

returns
2.25 ms ± 47.9 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
3.83 ms ± 46.4 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
1.72 ms ± 24.7 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

meaning that the cost of trim_internal approximately the same as just calling persist on a dask array, but the call to add_dummy_padding should be removed, instead the slicing logic should probably be moved to trim_internal.


Rewrite header recipes for hyper 0.12

Apparently, changes have been made to hyper 0.12 that breaks the header! implementation.  Those changes should be reviewed and implemented into the recipes.  Documentation is being moved to doc.servo.org until the recipes have been revamped.
Check out the changelog

Currently two examples using custom headers are broken:

trivial single custom headder
three typed headders for github rate limmiting

As there are several ways to approach the implementation I'd like to pick @seanmonstar 's brain for suggestion on what would be the most idiomatic approach for custom header definition for our readers to learn from.
cc https://github.com/seanmonstar/reqwest/issues/312

Thanks a lot for the info @seanmonstar!
I guess that we will hide the examples (https://github.com/rust-lang-nursery/rust-cookbook/pull/430) and revert them once the custom header story is sorted out on hyper side. What are your thoughts @AndyGauge ?

Sounds like a plan of action.  We can leave this open as a reminder once headers lands.


[Feature]: Implement Contact Us Page

Is your feature request related to a problem? Please describe.
I propose adding a Contact Us page to the project's website. Currently, the "Contact Us" hyperlink in the footer redirects to the same page as the "About Us" hyperlink, with the link /about or /contact. However, I suggest creating a separate page where users can fill in their information, including their email address and a message they want to send to the team. Additionally, we can also add a link to join discord if it is the prefered way to contact.
Describe the solution you'd like
The Contact Us will be an accessible way to communicate with the project team. It serves as a platform for users to submit their inquiries, feedback, or any other messages they wish to convey.
Key components of new Page:
Header: The page will have a header section consistent with the overall design of the website.
Contact Form: The main component of the Contact Us page is the contact form. The form will include the following fields for users to fill out:

Name: Users can input their name.
Email Address: Users are required to provide their email address for the team to respond.
Message: A text area where users can write their message or inquiry.
Discord link(Optional): Including link to Digitomize discord page as a way to contact the team.
Submit Button: A submit button at the bottom of the form allows users to send their message to the project team.
Footer: Similar to other pages on the website, the Contact Us page will have a footer section containing links to various resources, including links to the project's social media profiles, privacy policy, and terms of service.

Alternatives
No response
Additional Context

Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

For functionality, once they submit then send that message along with details to<EMAIL_ADDRESS>and also on discord webhook. (Check discord folder for webhook implementation, use similar functions)

Hey @namnoum, any updates?

Hey @namnoum, any updates?

Im working on the submit the form part! Ill get back to you by the end of the day i have some questions

Ohk np, you can text on discord for better conversation

Update: with guidance from @pranshugupta54 , I was able to implement the contact page containing a contact form with the same styling as the login/signup page, with a specific format of an email sent to<EMAIL_ADDRESS>


error message when trying to update reply-url with az ad app update

When I try to use az cli to update a reply url i get the following:
az ad app update --id f1aec2f5-090e-4994-be10-a9ab7e23c705 --reply-urls "http://localhost:8233"
Update to existing credential with KeyId 'd0e6649d-d546-4b64-86b2-ec64b46adf66' is not allowed.

The KeyId mentioned matches the id on the passwordCredentials property on the ad app.
This seems like a bug, because if I manually do a http PATCH to "https://graph.windows.net/$($tenant)/applications/$($objectId)?api-version=1.6" with the same credentials and just {"replyUrls":["https://localhost:4503"]} as payload the update works fine.

I apologize for being late in response, but we have fixed a few bugs in app update command recently.
Please migrate to a newer version and run the command again.
I tried already and it worked; hence I am closing this issue.


add an example for finding specific disassembled instructions

great example according to reox ‘s suggestion

Codecov Report

Merging #759 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #759      +/-   ##
==========================================
+ Coverage   76.76%   76.79%   +0.03%
==========================================
  Files          51       51
  Lines       16201    16235      +34
==========================================
+ Hits        12436    12467      +31
- Misses       3765     3768       +3

Impacted Files
Coverage Δ

androguard/core/__init__.py
90.06% <0%> (+0.32%)
: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 6d9f09b...dd752f5. Read the comment docs.


Fix : prevent crashing when views are disabled

This is actually a hotfix for a problem we encountered. We started using sails to act only as a REST API (please don't ask why). When we ripped out the views, tasks and disabled the grunt + views hooks, things stopped working.
When calling a route, we would always get this error:
api/responses/ok.js:44
  else return res.guessView({ data: data }, function couldNotGuessView () {
                  ^

TypeError: res.guessView is not a function

The hotfix makes sure that if views are disabled, data is immediately returned in JSON and will not make the server crash by attempting to load a view.

Thanks @fed135 @konstantinzolotarev!


add school cqepc

add school cqepc

@Bellatriix I have to close this request without merging, because you requested to add a non-existent domain to this repository: ;; connection timed out; no servers could be reached Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


remove ">" in link output

This typo causes syntax errors when inputting cursor links into curl.

Why:
In testing for an addition to other areas of documentation. The original instructions I submitted included a typo ">" in several example links. This extra addition will throw a syntax issue if inputted into curl. Removing this from the example will correct the issue.

What's being changed (if available, include any code snippets, screenshots, or gifs):
Removing ">" from several of the provide links to prevent syntax errors

Check off the following:

[X] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[X] For content changes, I have completed the self-review checklist.

Submitting pull request #22153 to remove inlink output that creates errors


Sourcing a shell script and using it in another script

Node version (or tell us if you're using electron or some other framework):
v14.16.0
ShellJS version (the most recent version/Github branch you see the bug on):
0.8.4
Operating system:
MacOS Catalina
Description of the bug:
Imagine this contrived scenario:
./main.sh
source ./config.sh
./output.sh

./config.sh
export SOME_CONFIG='foo'

./output.sh
echo "Config is: ${SOME_CONFIG}"

I am trying to replace ./main.sh with a ShellJS powered ./main.js WITHOUT replacing the other shell files for now.
But the problem is exec() I think spawns a new child_process every time so the previous command is lost.
How can I achieve this with ShellJS without some sort of hacky && to run multiple commands in the same child_process?
I notice that running ShellJS's cd just works throughout the script. So I am looking for something similar.
Ideally something like so:
./main.js
const shell = require('shelljs')

shell.execInline('source ./config.sh')
shell.execInline('./output.sh')

This isn't something we can reasonably support, unfortunately. There's no way to "exec in-line" on the node platform, so the only way to implement this would be transpile shell script ➡ JavaScript on the fly and require() it. This isn't really a goal of this project, although you could look at https://github.com/nfischer/shelljs-transpiler as a tool which can handle a limited subset of shell scripts. https://github.com/dthree/cash is another project which executes (limited) shell syntax.
You would probably have an easier time transpiling your script by hand.

I managed to solve this by the way! Here's the Stack Overflow with my answer on it: https://stackoverflow.com/questions/66512620/create-a-persistent-bash-shell-session-in-node-js-know-when-commands-finish-an
I would have much rather used ShellJS though, so am wondering if you would consider adding a way to pass an object of environment variables to ShellJS exec-like commands?


After new update issue for the writing in card on IOS

After the new update there is an Issue on IOS for writing/reading the NFC tags.
flutter: error PlatformException(104, Tag is not connected, null, null)

I have the same issue - Anyone has a solution for this please? Only the Android side is working.

Move this code to end of onDiscovered callback function.
await NfcManager.instance.stopSession(alertMessage: "scanned.");
Don't stop nfc session before write to tag.


Zapping from alby to mutiny shows double

client initiating action
Alby via Amethyst
client receiving or observing action (or lack thereof)
Sending to mutiny
timestamp
https://njump.me/nevent1qqspv8pvsp5j9mmlpjwxcals42cc2j8w2g4fe0dnu6em8hq5u38350qpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q3vamnwvaz7tmndpshwm3wdehhxarjxyhxxmmdqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx292cch2

what happens
A single zap shows as double
suggestion
@kiwiidb @benthecarman

I know the cause of this, thanks for the report

Thanks - I think you should be able to close this issue when you push the fix.
cc @utxo-one


[CH] stop is called before write finished in CelebornHashBasedCHColumnarShuffleWriter

Backend
CH (ClickHouse)
Bug description
[Expected behavior] and [actual behavior].
stop is called before write finished in CelebornHashBasedCHColumnarShuffleWriter, and cause exceptions.
Spark version
Spark-3.3.x
Spark configurations
No response
System information
No response
Relevant logs
2023-09-06 12:13:30.326 <Error> CelebornPartitionWriter: xxx CelebornPartitionWriter::~CelebornPartitionWriter.<PHONE_NUMBER>07648
23/09/06 12:13:30.326 INFO [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskMemoryManager: Memory used in task 15305
23/09/06 12:13:30.327 INFO [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskMemoryManager: Acquired by GlutenMemoryConsumer/CelebornShuffleWriter: 1.0 B
23/09/06 12:13:30.327 INFO [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskMemoryManager: Acquired by GlutenMemoryConsumer/ContextInstance: 42.9 MiB
23/09/06 12:13:30.327 INFO [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskMemoryManager: 0 bytes of memory were used by task 15305 but are not associated with specific consumers
23/09/06 12:13:30.327 INFO [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskMemoryManager: 44978440 bytes of memory are used for execution and 70688 bytes of memory are used for storage
23/09/06 12:13:30.327 WARN [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] InFlightRequestTracker: Clear InFlightRequestTracker
23/09/06 12:13:30.328 ERROR [Executor task launch worker for task 305.0 in stage 1.0 (TID 15305)] TaskResources: Task 15305 failed by error:
io.glutenproject.exception.GlutenException: Block is empty
0. ./build1/../contrib/llvm-project/libcxx/include/exception:134: Poco::Exception::Exception(String const&, int) @ 0x0000000013510db9 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
1. ./build1/../src/Common/Exception.cpp:98: DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x0000000006cfb677 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
2. DB::Exception::Exception<char const (&) [15]>(int, char const (&) [15]) @ 0x000000000e332c98 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
3. ./build1/../src/Core/Block.cpp:280: DB::Block::safeGetByPosition(unsigned long) const @ 0x000000000f6811d6 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
4. ./build1/../contrib/boost/boost/smart_ptr/intrusive_ptr.hpp:93: DB::NativeWriter::write(DB::Block const&) @ 0x000000001124084f in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
5. ./build1/../utils/extern-local-engine/Shuffle/PartitionWriter.cpp:0: local_engine::CelebornPartitionWriter::evictPartitions(bool)::$_0::operator()() const @ 0x000000000732c6a0 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
6. ./build1/../utils/extern-local-engine/Shuffle/PartitionWriter.cpp:0: local_engine::CelebornPartitionWriter::evictPartitions(bool) @ 0x000000000732b635 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
7. ./build1/../utils/extern-local-engine/Shuffle/PartitionWriter.cpp:339: local_engine::CelebornPartitionWriter::stop() @ 0x000000000732d610 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
8. ./build1/../utils/extern-local-engine/Shuffle/CachedShuffleWriter.cpp:144: local_engine::CachedShuffleWriter::stop() @ 0x000000000731c8f7 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so
9. ./build1/../contrib/llvm-project/libcxx/include/vector:537: Java_io_glutenproject_vectorized_CHShuffleSplitterJniWrapper_stop @ 0x0000000006bd0c80 in /data5/hadoop/yarn/local/usercache/liangjiabiao/filecache/83271/libch.so

        at io.glutenproject.vectorized.CHShuffleSplitterJniWrapper.stop(Native Method)
        at org.apache.spark.shuffle.gluten.celeborn.CelebornHashBasedCHColumnarShuffleWriter.internalWrite(CelebornHashBasedCHColumnarShuffleWriter.scala:145)
        at org.apache.spark.shuffle.gluten.celeborn.CelebornHashBasedCHColumnarShuffleWriter.write(CelebornHashBasedCHColumnarShuffleWriter.scala:88)
        at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:60)
        at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
        at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
        at org.apache.spark.scheduler.Task.run(Task.scala:136)
        at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:548)
        at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1504)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:551)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

find an OOM exception, maybe that is why this happen
23/09/06 15:14:13.926 ERROR [Thread-6] SparkUncaughtExceptionHandler: Uncaught exception in thread Thread[Thread-6,5,main]
java.lang.OutOfMemoryError: Java heap space
	at org.apache.celeborn.client.ShuffleClientImpl.pushOrMergeData(ShuffleClientImpl.java:855)
	at org.apache.celeborn.client.ShuffleClientImpl.pushData(ShuffleClientImpl.java:1157)
	at org.apache.spark.shuffle.gluten.celeborn.CelebornCHPartitionPusher.pushPartitionData(CelebornCHPartitionPusher.scala:50)
23/09/06 15:14:13.926 ERROR [SIGTERM handler] CoarseGrainedExecutorBackend: RECEIVED SIGNAL TERM

Maybe the same reason in #3016

trace the memory consumption in partition writer.
2023-09-06 16:53:41.276 <Error> PartitionWriter: xxx PartitionWriter::write. cache bytes. total_partition_buffer_size=1.51 GiB/1.52 GiB, total_partition_buffer_allocated_size=2.16 GiB/2.18 GiB, current mem usage:4.70 GiB


Put "our project library" at top of front page options

This idea came from Brad D. as a way to further encourage new users to try this out.

Part of #342


integration with Compose via Requires

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          30     31    +1
=====================================
+ Hits           30     31    +1

Impacted Files
Coverage Δ

src/BlinkPOMDPSimulator.jl
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Hability to select objects and move / remove them altogether

From<EMAIL_ADDRESS>on March 14, 2010 13:36:56
(new feature request)
The idea is to get a selection rectangle displayed when keeping the mouse
button down.

Selected tables shall be removable
Selected tables shall be movable

Might extends to Issue 66
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=73

From ondrej.zara on March 14, 2010 12:39:29
This feature is already present: just try to drag a rectangle around multiple tables...
Status: Invalid

From<EMAIL_ADDRESS>on March 14, 2010 14:12:31
nice ! i am now with the trunk version... ^^


Update urls

Update src to reflect hosting moved to github.  Codeplex closing down at the end of 2017.

@slestak,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@slestak, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


SSL verification is disabled

Steps:

Attempt to do some canonical libssl / certificate loading on a per-OS basis (targeting windows, mac, linux)
Add cert to the gem environment, and load as a failsafe if #1 does not pan out.

Also: Investigate whether things work for david on his mac lappy if we turn the ignore HTTPS line off. Just for investigative purposes.

Just out of curiosity (and the fact that I dont know much about SSL), why do we need to worry about this issue?

ignoring invalid certificates is a poor practice and could lead to users of the library passing their credentials to malicious endpoints.


fixed issue of destroying exisint clusters

This is to fix a minor issue that the hostedcluster doesn't exist.

/test pipeline-service-upgrade-test

cool yep I saw this in a few runs yesterday


Add Library: Team Topologies

Added Primitives to create Team Topologies Diagrams, as per Matthew Skelton and Manuel Pais.

It allows to create diagrams that looks like this

And the primitives are these:

Nice, I've already started using your library.
I'd prefer the other models for the interaction-modes though:

Hey 👋
How is this different from the one @VLecrubier built

@ferminrp I am @VLecrubier, same person 🖖
But @nikordaris an improved version since ( https://github.com/excalidraw/excalidraw-libraries/pull/105 ), which conforms better to the Team Topologies website, as @YouriTjang mentioned, so all good.