text:
Update README.md

Change Description
This PR is about EOSIO installation issue through Homebrew. It is noticed that on a fresh MacOS 10.15 Homebrew throws this error Reinstalling 1 broken dependent from source: eosio/eosio/eosio which prevents successful installation of EOSIO. The cause of this issue is still unknown, and this PR provides workaround for it in the ReadMe file.
Change Type
Select ONE:

[ ] Documentation

[ ] Stability bug fix

[x] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[ ] New Tests

[ ] Existing Tests

[ ] Test Framework

[ ] CI System

[x] Other

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[x] Documentation Additions
It should be mentioned that on MacOS 10.15, EOSIO installation via Home brew might face this error Reinstalling 1 broken dependent from source: eosio/eosio/eosio. Workaround for this issue is to use the following Homebrew commands: brew cleanup eosio && brew link eosio.

Has this error been seen since we fixed the tap syntax on June 22?

Has this error been seen since we fixed the tap syntax on June 22?

Yes. See homebrew-eosio build 18 and this thread on IM.

We've got to remember to remove this once it is fixed. These changes should also probably be added to the release/2.2.x and release/2.1.x branches. The v2.1.0 release is the currently published version exhibiting this error.
Also consider looping in @lparisc on these changes.

Good timing @kj4ezj. I need to fix a few links in the release/2.x READMEs and a hotfix on master. I'll bring in @shahabi8 edits too.


text:
add Deroceras lasithionense/xgDerLasi

Assembly review request

ToLID: xgDerLasi
Species:Deroceras lasithionense
Project: ERGA-BGE
Affiliation: Genoscope

Hi @CaroB-M, thanks for sending the EAR of Deroceras lasithionense.
I added the corresponding tag to the PR and will contact a supervisor and a reviewer ASAP.

Hi @tbrown91, do you agree to supervise this assembly?
Please reply to this message only with OK to give acknowledge.

ok

*****
EAR Reviewer Selection Process
Date: 2024-07-25 15:11

All Eligible Candidates:

Github ID  | Full Name     | Institution | Total Reviews | Last Review | Active | Busy | Calling Score | Adjusted Score
-----------------------------------------------------------------------------------------------------------------------
gitcruz    | Fernando Cruz | CNAG        | 1             | 2024-07-15  | Y      | N    | 1007          | 1057
DomAbsolon | Dom Absolon   | Sanger      | 1             | 2024-04-22  | Y      | N    | 1001          | 1051
tommathers | Tom Mathers   | Sanger      | 2             | 2024-07-08  | Y      | N    | 1000          | 1050
additive3  | Jo Wood       | Sanger      | 2             | 2024-06-15  | Y      | N    | 999           | 1049
tbrown91   | Tom Brown     | IZW         | 9             | 2024-07-05  | Y      | N    | 999           | 999

Selected reviewer: Fernando Cruz (gitcruz)
The decision was based on:
- different institution ('CNAG')
- active ('Y')
- not busy ('N')
- highest adjusted calling score in this particular selection (1057)
- Highest adjusted calling score.

Hi @gitcruz, do you agree to review this assembly?
Please reply to this message only with Yes or No by 01-AUG-2024 at 15:12 CET.

Time is out! I will look for another reviewer :)

Hi Diego,
I am on holidays right now. I will be back in business on August 19th.
Cheers,
Fernando
El jue., 1 ago. 2024 15:16, Diego De Panis @.***>
escribió:

Hi @tommathers https://github.com/tommathers, do you agree to review
this assembly?
Please reply to this message only with Yes or No by 08-AUG-2024 at
15:15 CET.
—
Reply to this email directly, view it on GitHub
https://github.com/ERGA-consortium/EARs/pull/50#issuecomment-2263016321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB34KVILX3PBFI4PPJ7YLEDZPIYJ5AVCNFSM6AAAAABLOQOY3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGAYTMMZSGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes
From: Diego De Panis @.>
Reply to: ERGA-consortium/EARs @.>
Date: Thursday 1 August 2024 at 14:16
To: ERGA-consortium/EARs @.>
Cc: Thomas Mathers @.>, Mention @.***>
Subject: Re: [ERGA-consortium/EARs] add Deroceras lasithionense/xgDerLasi (PR #50) [EXT]
Hi @tommathers [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tommathers&d=DwMCaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=MigC00eCez0AYiD8Bi3uR5vUblihAN7OJ3KK8sbnotw&m=mW2bfmbVmC2icLgejm6U7wkjSl6VN5TR35P5HLQSaSYn1zWaVUc2nmh-3ivmAmA4&s=fYMDiQy2TCWUu7nS6zQiZGgOCAZPGGRdapEQhMgjZCs&e=, do you agree to review this assembly?
Please reply to this message only with Yes or No by 08-AUG-2024 at 15:15 CET.
—
Reply to this email directly, view it on GitHub [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ERGA-2Dconsortium_EARs_pull_50-23issuecomment-2D2263016321&d=DwMCaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=MigC00eCez0AYiD8Bi3uR5vUblihAN7OJ3KK8sbnotw&m=mW2bfmbVmC2icLgejm6U7wkjSl6VN5TR35P5HLQSaSYn1zWaVUc2nmh-3ivmAmA4&s=A9SLEkNtJXqFAKyuGqDccUIHvfegkJK1gt0AkevmLoU&e=, or unsubscribe [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABVP3G5J52SML7L566M65GDZPIYJ5AVCNFSM6AAAAABLOQOY3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGAYTMMZSGE&d=DwMCaQ&c=D7ByGjS34AllFgecYw0iC6Zq7qlm8uclZFI0SqQnqBo&r=MigC00eCez0AYiD8Bi3uR5vUblihAN7OJ3KK8sbnotw&m=mW2bfmbVmC2icLgejm6U7wkjSl6VN5TR35P5HLQSaSYn1zWaVUc2nmh-3ivmAmA4&s=UxbcAFOmIny0shQy2gn6eTgEjV6kzt6JUPMjvvAhzdU&e=.
You are receiving this because you were mentioned.Message ID: @.***>

The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is Wellcome Sanger Institute, Wellcome Genome Campus, Hinxton, CB10 1SA.

Thanks for agreeing :D
I appointed you as the EAR reviewer.
I will change your status to Busy until you finish this review.
Please check the Wiki if you need to refresh something (and remember that you must download the EAR PDF to be able to click on the link to the contact map file!).
Contact the PR assignee for any issues.

Hi @CaroB-M
Have you had a chance to look at the suggested changes from @tommathers and recreate the EAR? It would be great to have another assembly finished

Hello, I'm back from vacation. I'm now generating the files, having taken into account the changes suggested by @tommathers.  I'll upload the files as soon as possible.

Hello, I added the new EAR report.  I made the changes suggested by @tommathers. For the little contigs, I placed just some of them in larger scaffolds.

Hi @CaroB-M
Welcome back and thank you for re-uploading the EAR. @tommathers can I ask you to give the map one last look-through? Hopefully we can finish this assembly off soon and publish it to ENA

@tommathers ping

Hi @CaroB-M
I looked through the map and can see two potential mis-scaffolds:
xgDerLasi_30:14.37Mb-14.54Mb this should be placed at 21.21Mb - same orientation
xgDerLasi_18:21.81Mb-21.91Mb this should be placed at the end ~36Mb - reverse orientation
In your TAPAS plot there are two bacterial sequences. Have you already removed these, or do you have evidence that they are false positives?
If you make these changes and remove the contaminants I think it is ready to upload.
Any further thoughts, @tommathers ?

Hi. Sorry for the delay. Just had a look through. I agree with Tom's suggestions re chrom 18 and 30. Also, the haplotig in chrom 1 at 48.7 i flagged before needs removing and I just noticed there is another small one i missed before at 48.1 Mb.

Thanks @CaroB-M
Hopefully just one more quick look-through please @tommathers

Hello, I added the new EAR report. I made the changes suggested. The bacterial contigs were already removed. Thanks!

Hi just wanted to check if the corrext ear has been uploaded? I can still see the haplotigs on chr. 1 that were flagged above when I downloaded the map from the latest report. See attached pic of region of chr. 1 at ~48 Mb.

Hello @tommathers. You're rigth. There was a mistake. I have changed the pretext map link so can you try to download the pdf file and the pretext map? Sorry for the inconvenience

Thanks @tommathers
Congrats @CaroB-M please go forward with the upload to ENA

source: gharchive/pull-request

authors: CaroB-M diegomics gitcruz tbrown91 tommathers

repo: ERGA-consortium/EARs

license: MIT

license_type: permissive

license_source: github-api


text:
rewrite the polling / recursive setTimeout code to be more managable

Perhaps look into new block events via: https://github.com/MetaMask/eth-block-tracker

Finished in #788

source: gharchive/issue

repo: ETCDEVTeam/emerald-wallet


text:
What is the purpose of last else block in the screen below.

Check the code here

Please direct the question to the etheriumproject/go-etherium repo

repo: ETCDEVTeam/sputnikvm


text:
plans to implement depth, limit, page parameter in hrls servlet.

Hi,
At the moment I can do:
'''
curl -u username:password https://fqdn:port/hrls/handles?URL=*
["1000/E255C48C-4A62-11E6-BF9E-B8E8561BDBEC","1000/TEST","1000/TEST1","1000/TEST2"]
'''
Are there plans to implement a depth parameter? So you can do:
'''
curl -u username:password https://fqdn:port/hrls/handles?URL=*%depth=infinity
'''
This so handles are right away shown complete and you don't have to retrieve them one by one.
If I now add %depth the return value is '[]'

The same goes for:

limit
page

"limit" was already implemented.
The "page" parameter has been implemented in #4aceac as well as "retrieverecords" parameter for single field search.
On retrieval of full records:
I consider the ability to retrieve full handle records a convenience function only. The purpose of the HRLS is to provide reverse lookups, not retrieve Handle records. For that, the Handle REST interface / B2HANDLE should be used.
Nonetheless, the servlet now provides such a convenience function, but only if you search over a single field (e.g. URL only).
To retrieve record functionality for searches over multiple fields (e.g. "URL=*&FOO=bar"), the already complex SQL statements with multiple inner joins would have to be extended, and the limit/page implementation is also not easy to solve as it should refer to the selected Handles, not the returned values. I consider this to be too far out of scope for the HRLS.

Hi Tobias,
I was just thinking out loud. Thanks for the answers..

Hi Tobias,
Can you add an example with the "retrieverecords" parameter to the README.md?


text:
前端代码生成器中加入了校验规则，后端代码中增加了几个正则校验

hello

不错不错


text:
Upgrade to php7.0

Attempt to upgrade from php5.6 to php-7.0

@gcnonato
Thanks for the pull request !! we will update on this soon :)

No problem, I hope it helps.
Cheers!

Hello @gcnonato ,
Thanks for pull request. We are going to adding PHP 7.0 and PHP5.6 both support, so that user can run either PHP7.0, PHP 5.6, or both.
So for now I am closing this pull request.

+1 to both. Thanks for your work, @gcnonato

thank you I just updated to 3.5
how to update php version to 7?

repo: EasyEngine/easyengine

license: mit

license_source: bigquery


text:
Obsidian 1.74 breaks functionality

Pretty simple. As far as I can tell it's 100% repro. 1.74 breaks main functionality.

Please delete. It was user error.

repo: Ebonsignori/obsidian-at-symbol-linking


text:
Adding marathi translation for # How-To at a glance

एका दृष्टीक्षेपात कसे करावे

हे इतर भाषांमध्ये वाचा

Free-Programming-Books मध्ये तुमचे स्वागत आहे!
आम्ही नवीन योगदानकर्त्यांचे स्वागत करतो; ज्यांनी GitHub वर त्यांचे पहिले Pull Request (PR) सादर केले आहे. जर तुम्ही त्यापैकी एक असाल, तर इथे काही संसाधने आहेत जी तुम्हाला मदत करतील:

Pull requests बद्दल माहिती
Pull request तयार करणे
GitHub Hello World
YouTube - नवशिक्यांसाठी GitHub ट्युटोरियल
YouTube - GitHub Repo कसे Fork करावे आणि Pull Request कसे सादर करावे
YouTube - Markdown क्रॅश कोर्स

प्रश्न विचारण्यास अजिबात संकोच करू नका; प्रत्येक योगदानकर्त्याने पहिले PR केले आहे. म्हणून... का नाही आमच्या मोठ्या, वाढत्या समुदायामध्ये सामील व्हा.

वापरकर्ते विरुद्ध वेळ ग्राफ पाहण्यासाठी क्लिक करा.

जर तुम्ही अनुभवी ओपन सोर्स योगदानकर्ता असाल, तरीही काही गोष्टी तुम्हाला गोंधळात टाकू शकतात. तुमचा PR सादर केल्यावर, GitHub Actions एक linter चालवेल, आणि सहसा जागा किंवा अक्षरमालेतील चुका शोधेल. जर तुम्हाला हिरवा बटण मिळाला, तर सर्व काही पुनरावलोकनासाठी तयार आहे; पण जर नाही, तर फेल झालेल्या चेकखाली "Details" वर क्लिक करा आणि linter ला काय आवडलं नाही ते शोधा, आणि समस्या सोडवण्यासाठी PR उघडलेल्या शाखेत एक नवीन कमिट जोडा.
शेवटी, तुम्हाला खात्री नसेल की तुम्ही जोडू इच्छित असलेले संसाधन Free-Programming-Books साठी योग्य आहे का, तर CONTRIBUTING मार्गदर्शक तत्वे वाचा (अनुवाद देखील उपलब्ध आहेत).

Let me know if you need any adjustments!

@rohit223 May I solve this issue?

repo: EbookFoundation/free-programming-books


text:
Add 'Algorithm Notes for Professional' Book PDF

This book provides a detailed explanation of algorithms from the start for beginners to understand in a better way.

Are you talking about https://goalkicker.com/AlgorithmsBook/AlgorithmsNotesForProfessionals.pdf?

Are you talking about https://goalkicker.com/AlgorithmsBook/AlgorithmsNotesForProfessionals.pdf? Go ahead then!

Yes sir!

authors: davorpa keerthanasathya


text:
[FIF-213] Fix to add ETLProject to Kotlin to create subproject

Need to add ETL as subproject.

@stephenfuqua I fixed a lint issue that arose from the TeamCity runs. I also noticed that the service was failing to properly monitor postgres because the service's XML had an improper Postgres protocol URL for the connection string ENVVAR. Those changes make the ETL build for regular branches and PRs.

Looks good, I think it is ready to go.

authors: kurtjohnson-HS stephenfuqua

repo: Ed-Fi-Exchange-OSS/EdFi-Project-Buzz


text:
Gemfury fingerprint is very prone to false positiver

Service name
Gemfury
Proof

Documentation
I wish I could be a little more precise

Yes, you are right

repo: EdOverflow/can-i-take-over-xyz


text:
[FEATURE]

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
When editing the event ticket, ensure that changes are instantly visible without the need to manually scroll up after each adjustment. It's essential for the ticket to remain visible at all times while scrolling for a seamless user experience.
Proposed Solution
By making the ticket follow the page scrolling, users can conveniently view changes directly without interruption.
Screenshots
this is a video before and after the changes
https://streamable.com/tngbd6
Do you want to work on this issue?
Yes
If "yes" to above, please explain how you would technically implement this
CSS Class:  In the return function of the EventCard.js I add The div element with the CSS classes sticky, top-0. These classes ensure that the component sticks to the top of the viewport and the event card is synchronized with scrolling.

This is a great idea 👍  but as the project is being archived in a few days, I do not recommend working on it now

repo: EddieHubCommunity/BioDrop


text:
Add new features

Description
Hi, @eddiejaoude I think the previous milestones cards UI was far better than the present card UI.
Screenshots

Additional information
No response

Thank you for the feedback. The whole card was clickable before, now it is a specific icon. We can keep improving the design as we go along
I will close this issue and feel free to raise specific improvements.
Note: please don't write it is like you are shouting

authors: eddiejaoude priyankarpal

repo: EddieHubCommunity/LinkFree


text:
data:Anjuli08

I want to add my profile to the linkFree.

I've removed the comma. How can I move my profile to data directory?

If you are editing on GitHub, there is a box at the top with the filename.
Type data/ in the box before your filename & it should be moved.

I've removed the comma. How can I move my profile to data directory?

If you are editing on GitHub, there is a box at the top with the filename. Type data/ in the box before your filename & it should be moved.

done! please review if it's alright


text:
data:saidurrahmanmisket

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

wonderful

awaiting approval -_-

a

@saidurrahmanmisket why so many open / close and comment with just an a?

authors: eddiejaoude saidurrahmanmisket


text:
fix: add Abhishek Kushwaha

Changes proposed

Added my own developer profile on LinkFree

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Done with requested Changes 😁

LGTM!

I didn't get it ?
LGTM means?

Looks Good To Me

Could you resolve the linting errors? -
public/data/Abbhiishek.json
Error:   24:49  error  Trailing comma  json/*
Error:   31:72  error  Trailing comma  json/*
Error:   38:46  error  Trailing comma  json/*
Error:   45:44  error  Trailing comma  json/*

authors: Abbhiishek Vyvy-vi


text:
REST-API-Design-Guideline

We could think about using a Rest-Api-Design-Guideline like this for designing out endpoints consistently

I really like this 👍 , we can get out of it from the recommendations from NestJS docs, as I like to keep this vanilla to the recommendations of the framework, so that it is easier to onboard new people

authors: Cahllagerfeld eddiejaoude

repo: EddieHubCommunity/api


text:
[Bug]: Testing labels for issues

Just a test, please don't mind.

Test successful.

repo: EddieJaoudeCommunity/support


text:
Members in Discord don't have permissions to tag Moderators

Description

Oh this is so important, thank you 👍

Oh this is so important, thank you 👍

Fixed...

Fixed...

authors: HannWeb eddiejaoude


text:
Is it possible to use the plugin as a non-scheduled?

I see the functionality is exactly what i need, but.
Is it possible to fire a non-scheduled notification i.e. when listening to pusher?
const channel = socket.subscribe('newUser-channel');
channel.bind('newuser', data => {
alert({
title: "Your title",
})
})
instead of alert i want to have a notification of your plugin. Is it possible?
Thank in advance

Sorry for silly Q. If someone is also inattentive as me - you should pass an empty "at" and the notification will fire immidiately - great!


text:
🛑 Portal Preguntas Frecuentes is down

In 9908ac3, Portal Preguntas Frecuentes (https://www.preguntasfrecuentes.una.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal Preguntas Frecuentes is back up in 1968455.

repo: EdgardoRamosRoque/status


text:
Update suggested tools from jakub-onderka to php-parallel-lint

Composer complaints about jakub-onderka/* packages being abandoned:
Package jakub-onderka/php-parallel-lint is abandoned, you should avoid using it. Use php-parallel-lint/php-parallel-lint instead.
Package jakub-onderka/php-console-color is abandoned, you should avoid using it. Use php-parallel-lint/php-console-color instead.
Package jakub-onderka/php-console-highlighter is abandoned, you should avoid using it. Use php-parallel-lint/php-console-highlighter instead.

This PR should fix it.

It's going to be fixed in https://github.com/EdgedesignCZ/phpqa/pull/218/commits/f7ac2372399acc5f7153c12b8fbcd225cad2c7fe

authors: NITEMAN zdenekdrahos

repo: EdgedesignCZ/phpqa


text:
addPageRequestListener always fetching page even no scrolling

class DashboardWidget extends StatefulWidget {
  const DashboardWidget({
    super.key,
  });

  @override
  State<DashboardWidget> createState() => _DashboardWidgetState();
}

class _DashboardWidgetState extends State<DashboardWidget> {
  dynamic leads = null;
  dynamic creditBalance = null;
  dynamic managers;

  @override
  void initState() {
    initData();

    super.initState();
  }

  Future<void> initData() async {
    final token = Application.preferences?.getString('api_token') ?? "";
    final response = await Api.getLeads(token: token);
    dynamic managerIds;
    if (isUserManager()) {
      var managers = await Api.getUserSettings(
        token: token,
        params: {"manager": Application.preferences?.getString('id')},
      );

      managers = jsonDecode(managers.data)['data'];
      managerIds = managers.map((e) => e['id']).toList();
    }

    final partner =
        jsonDecode(Application.preferences?.getString('partner') ?? "");

    final managersData = await Api.getUserSettings(
      token: token,
    );
    if (mounted) {
      setState(() {
        creditBalance = partner['partner_credit_balance'].replaceAllMapped(
          RegExp(r'(\d{1,3})(?=(\d{3})+(?!\d))'),
          (Match match) => '${match[1]},',
        );
        leads = jsonDecode(response.data);

        if (isUserDesigner() ||
            (isUserDirector() &&
                Application.preferences!.getBool('company_view') == false)) {
          leads = leads
              .where(
                (lead) =>
                    lead['manager_id'] ==
                    int.parse(Application.preferences?.getString('id') ?? ''),
              )
              .toList();
        } else if (isUserManager()) {
          leads = leads
              .where((lead) => managerIds.contains(lead['manager_id']) as bool)
              .toList();
        }

        leads = leads
            .where(
              (lead) => [
                'Follow up (uncontactable)',
                'Follow up (discussion)',
                'New',
              ].contains(lead['heat_type_name']),
            )
            .toList();

        leads = groupBy(
          leads,
          (obj) => (obj! as Map<String, dynamic>)['grouped_lead_won_date'],
        );

        managers = jsonDecode(managersData.data)['data'].where((e) {
          if (isUserManager()) {
            return e['manager_id'] ==
                    Application.preferences?.getString('id') ||
                e['id'].toString() == Application.preferences?.getString('id');
          } else {
            return true;
          }
        }).toList();
      });
    }
  }

  @override
  Widget build(BuildContext context) {
    return RefreshIndicator(
      color: dangerColor,
      onRefresh: () async {
        if (mounted) {
          setState(() {
            leads = null;
            creditBalance = null;
            initData();
          });
        }
      },
      child: CustomScrollView(
        slivers: [
          SliverToBoxAdapter(
            child: Container(
              padding: const EdgeInsets.all(20),
              child: Column(
                children: [
                  IntrinsicHeight(
                    child: Row(
                      children: [
                        FollowupLeads(
                          counter:
                              leads != null ? leads.length.toString() : "0",
                        ),
                        TotalRewards(
                          counter:
                              leads != null ? creditBalance.toString() : "0",
                        ),
                      ],
                    ),
                  ),
                  const SizedBox(
                    height: 30,
                  ),
                  const SizedBox(height: 20),
                ],
              ),
            ),
          ),
          SliverList(
            delegate: SliverChildListDelegate([
              Center(
                child: LeadsTable(leads: leads, managers: managers),
              ),
            ]),
          )
        ],
      ),
    );
  }
}

class LeadsTable extends StatefulWidget {
  const LeadsTable({super.key, required this.leads, required this.managers});
  final dynamic leads;
  final dynamic managers;

  @override
  State<LeadsTable> createState() => _LeadsTableState();
}

class _LeadsTableState extends State<LeadsTable> {
  static const _pageSize = 2;

  final PagingController<int, dynamic> _pagingController =
      PagingController(firstPageKey: 0);

  @override
  void initState() {
    _pagingController.addPageRequestListener((pageKey) {
      _fetchPage(pageKey);
    });

    super.initState();
  }

  Future<void> _fetchPage(int pageKey) async {
    try {
      if (pageKey < 30) {
        final token = Application.preferences?.getString('api_token') ?? "";
        var newItems = await Api.getLeads(token: token, params: {
          "pageKey": pageKey,
          "pageLimit": _pageSize,
          "status": {"0": 3, "1": 4, "2": 42}
        });

        newItems = groupBy(
          jsonDecode(newItems.data),
          (obj) => (obj! as Map<String, dynamic>)['grouped_lead_won_date'],
        );
        var list = [];
        var length = 0;
        newItems.forEach((k, v) => {
              list.add(LeadModel(k, v)),
              length += v.length as int,
            });

        final isLastPage = length < _pageSize;
        if (isLastPage) {
          _pagingController.appendLastPage(list);
        } else {
          final nextPageKey = pageKey + length;
          _pagingController.appendPage(list, nextPageKey as int?);
        }
      }
    } catch (error) {
      _pagingController.error = error;
    }
  }

  @override
  Widget build(BuildContext context) {
    return Container(
      width: double.infinity,
      decoration: BoxDecoration(
        color: Colors.white,
        borderRadius: BorderRadius.circular(20),
      ),
      child: Column(
        children: [
          PagedListView<int, dynamic>(
            // physics: const NeverScrollableScrollPhysics(),
            scrollDirection: Axis.vertical,
            primary: false,
            shrinkWrap: true,
            pagingController: _pagingController,
            builderDelegate: PagedChildBuilderDelegate<dynamic>(
              itemBuilder: (context, index, item) {
                String key = index.date;
                return Column(
                  children: [
                    Container(
                      alignment: Alignment.centerLeft,
                      padding: const EdgeInsets.symmetric(
                        horizontal: 20,
                        vertical: 15,
                      ),
                      decoration: const BoxDecoration(
                        border: Border(
                          bottom: BorderSide(
                            width: 1,
                            color: Color(0xffE5E5E5),
                          ),
                        ),
                      ),
                      child: Helvetica(
                        text: DateFormat('dd LLLL yyyy')
                            .format(DateTime.parse(key)),
                        color: const Color(0xff546889),
                      ),
                    ),
                  ],
                );
              },
            ),
          )
        ],
      ),
    );
  }

  @override
  void dispose() {
    _pagingController.dispose();
    super.dispose();
  }
}

i've tried to add customscrollview but it's still loading even i'm not doing scrolling or load more action on the screen
can anyone help me please i've been stuck for so long

@EdsonBueno @clragon can help to solve my issue please

Yeah I'm also looking for solution to this issue. Please kindly share if you see any.

I've tried to replicate your problem with this code:
`class MainApp extends StatelessWidget {
const MainApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
body: Center(
child: CustomScrollView(
slivers: [
SliverList(
delegate: SliverChildListDelegate([
const Center(
child: Column(
children: [
MyPagedListView(),
],
),
),
]),
)
],
),
),
),
);
}
}
class MyPagedListView extends StatefulWidget {
const MyPagedListView({
super.key,
});
@override
State createState() => _MyPagedListViewState();
}
class _MyPagedListViewState extends State {
late final PagingController<int, int> _pagingController;
@override
void initState() {
_pagingController = PagingController(firstPageKey: 0);
_pagingController.addPageRequestListener((pageKey) {
  print('fetch');
  _fetchPage(pageKey);
});

super.initState();

}
Future _fetchPage(int pageKey) async {
const pageSize = 20;
List newItems = [];
for (int i = pageSize * pageKey; i < pageSize; i++) {
newItems.add(i);
}
_pagingController.appendPage(newItems, pageKey++);

}
@override
Widget build(BuildContext context) {
return PagedSliverList(
pagingController: _pagingController,
builderDelegate: PagedChildBuilderDelegate(
itemBuilder: (context, data, index) => Container(
height: 100.0,
color: Colors.red,
child: Text('Child $index'),
),
),
);
}
}`

Hi @AndersonArvando. I tried to replicate your issue using this piece of code:
class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: CustomScrollView(
            slivers: [
              SliverList(
                delegate: SliverChildListDelegate([
                  const Center(
                    child: Column(
                      children: [
                        MyPagedListView(),
                      ],
                    ),
                  ),
                ]),
              )
            ],
          ),
        ),
      ),
    );
  }
}

class MyPagedListView extends StatefulWidget {
  const MyPagedListView({
    super.key,
  });

  @override
  State<MyPagedListView> createState() => _MyPagedListViewState();
}

class _MyPagedListViewState extends State<MyPagedListView> {
  late final PagingController<int, int> _pagingController;

  @override
  void initState() {
    _pagingController = PagingController(firstPageKey: 0);

    _pagingController.addPageRequestListener((pageKey) {
      print('fetch');
      _fetchPage(pageKey);
    });

    super.initState();
  }

  Future<void> _fetchPage(int pageKey) async {
    const pageSize = 20;
    List<int> newItems = [];
    for (int i = pageSize * pageKey; i < pageSize; i++) {
      newItems.add(i);
    }

    _pagingController.appendPage(newItems, pageKey++);
  }

  @override
  Widget build(BuildContext context) {
    return PagedListView(
      shrinkWrap: true,
      pagingController: _pagingController,
      builderDelegate: PagedChildBuilderDelegate(
        itemBuilder: (context, data, index) => Container(
          height: 100.0,
          color: Colors.red,
          child: Text('Child $index'),
        ),
      ),
    );
  }
}

The widget tree is currently represented as:
CustomScrollView -> SliverList -> Column -> PagedListView
However, when using CustomScrollViews, it's recommended to use PagedSliverList instead.
So, it would be like:
class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: Center(
          child: CustomScrollView(
            slivers: [
              MyPagedListView(),
            ],
          ),
        ),
      ),
    );
  }
}

class MyPagedListView extends StatefulWidget {
  const MyPagedListView({
    super.key,
  });

  @override
  State<MyPagedListView> createState() => _MyPagedListViewState();
}

class _MyPagedListViewState extends State<MyPagedListView> {
  late final PagingController<int, int> _pagingController;

  @override
  void initState() {
    _pagingController = PagingController(firstPageKey: 0);

    _pagingController.addPageRequestListener((pageKey) {
      print('fetch');
      _fetchPage(pageKey);
    });

    super.initState();
  }

  Future<void> _fetchPage(int pageKey) async {
    const pageSize = 20;
    List<int> newItems = [];
    for (int i = pageSize * pageKey; i < pageSize; i++) {
      newItems.add(i);
    }

    _pagingController.appendPage(newItems, pageKey++);
  }

  @override
  Widget build(BuildContext context) {
    return PagedSliverList(
      pagingController: _pagingController,
      builderDelegate: PagedChildBuilderDelegate(
        itemBuilder: (context, data, index) => Container(
          height: 100.0,
          color: Colors.red,
          child: Text('Child $index'),
        ),
      ),
    );
  }
}

Now, the widget tree is like this:
CustomScrollView -> PagedSliverList

Hi @Israel001. From what I can see, you are using a sliver PagedSliverList within a Column.
Flutter follows two protocols for drawing widgets: Sliver and Box protocols.
A Column expects its children to adhere to the Box protocol. However, in the case of a PagedSliverList, it uses the Sliver protocol.
If you want to use a paged list inside a Column, I would recommend using a PagedListView wrapped in an Expanded widget (to avoid an unbounded height), and make sure to turn off shrinkWrap.
Let me know if it doesn't work.

@caiombueno God bless you bro ❤
It works!!!
Turning off the shrinkWrap is what did it for me 'cause I was already using Column and Expanded before but shrinkWrap was on.
Thank you very much bro.
I hope the original issue poster will also get his issue resolved.

@caiombueno Hello,
Sorry to disturb you again (:
After replicating the pagination logic as you explained for another scenario, it didn't work. I am getting the same issue as before, where the new pages are fetched before i even scroll.
I am using column inside a IndexedStack Widget. Here is an overview of my widget flow from scaffold to the pagination widget:
Scaffold -> IndexedStack -> Column -> Expanded -> Padding -> PagedListView -> Container -> Column
The Scaffold and IndexedStack is in a different file which imports the 1st Column Widget from another file.
Here is the code for the file that contains the PagedListView widget:
class CollectionHistoryViewState extends State<CollectionHistoryView> {
  final PagingController<int, UpcomingCollectionRequest>
      _upcomingCollectionsController = PagingController(firstPageKey: 1);
  final PagingController<int, CollectionRequest> _collectionsTodayController =
      PagingController(firstPageKey: 1);

  @override
  void dispose() {
    _upcomingCollectionsController.dispose();
    _collectionsTodayController.dispose();
    super.dispose();
  }

  fetchUpcomingCollections(Pagination pagination, int nextPageKey) async {
    try {
      String? accessToken = await getIt<StorageService>().getFromDisk(
        Constants.accessToken,
      );
      Response response = await getIt<Dio>().get(
        ServerRoutes.getUpcomingCollections(pagination),
        options: Options(
          headers: {"Authorization": "Bearer $accessToken"},
        ),
      );
      bool isLastPage = response.data['pagination']['page'] ==
          response.data['pagination']['pages'];
      List<UpcomingCollectionRequest> upcomingCollections =
          (response.data['data'] as List)
              .map((value) => UpcomingCollectionRequest.fromJson(value))
              .toList();
      if (isLastPage) {
        _upcomingCollectionsController.appendLastPage(upcomingCollections);
      } else {
        _upcomingCollectionsController.appendPage(
          upcomingCollections,
          nextPageKey,
        );
      }
    } on DioException catch (e) {
      if (context.mounted) handleDioException(e, context);
    }
  }

  fetchCollectionsToday(Pagination pagination, int nextPageKey) async {
    try {
      String? accessToken = await getIt<StorageService>().getFromDisk(
        Constants.accessToken,
      );
      Response response = await getIt<Dio>().get(
        ServerRoutes.getCollectionsToday(pagination),
        options: Options(
          headers: {"Authorization": "Bearer $accessToken"},
        ),
      );
      bool isLastPage = response.data['pagination']['page'] ==
          response.data['pagination']['pages'];
      List<CollectionRequest> collectionsToday = (response.data['data'] as List)
          .map((value) => CollectionRequest.fromJson(value))
          .toList();
      if (isLastPage) {
        _collectionsTodayController.appendLastPage(collectionsToday);
      } else {
        _collectionsTodayController.appendPage(
          collectionsToday,
          nextPageKey,
        );
      }
    } on DioException catch (e) {
      if (context.mounted) handleDioException(e, context);
    }
  }

  @override
  void initState() {
    widget.totalUpcomingCollections > widget.upcomingCollections.length
        ? _upcomingCollectionsController.appendPage(
            widget.upcomingCollections,
            2,
          )
        : _upcomingCollectionsController
            .appendLastPage(widget.upcomingCollections);

    widget.totalCollectionsToday > widget.collectionsToday.length
        ? _collectionsTodayController.appendPage(widget.collectionsToday, 2)
        : _collectionsTodayController.appendLastPage(widget.collectionsToday);

    _collectionsTodayController.addPageRequestListener((pageKey) {
      fetchCollectionsToday(Pagination(limit: 5, page: pageKey), pageKey);
    });
    _upcomingCollectionsController.addPageRequestListener((pageKey) {
      print("here???");
      fetchUpcomingCollections(Pagination(limit: 5, page: pageKey), pageKey);
    });
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    final model = context.watch<ProfileViewModel>();

    int listCount = model.collectionState == "Collections"
        ? model.collectionState2 == 'Collections Today'
            ? model.collectionsToday.length
            : model.upcomingCollectionReqs.length
        : 0;
    String listInUse = "";
    String collectionListInUse =
        model.collectionState2 == 'Collections Today' ? "list" : "upcomingList";
    Map baseList = {};
    if (listCount < 1) {
      switch (model.collectionState) {
        case "Collections":
          listCount = model.collectionState2 == 'Collections Today'
              ? model.collectionsToday.length
              : model.upcomingCollectionReqs.length;
          collectionListInUse = model.collectionState2 == 'Collections Today'
              ? "list"
              : "upcomingList";
          break;
        case "Missed":
          listCount = model.collectionState2 == 'This Week'
              ? model.missedCollectionReqs.length
              : model.missedCollectionHistory.entries.length;
          listInUse = model.collectionState2 == 'This Week'
              ? "missedThisWeek"
              : "historyList";
          if (listInUse == 'historyList') {
            baseList = model.missedCollectionHistory;
          }
          break;
        case "Completed":
          listCount = model.collectionState2 == 'This Week'
              ? model.completedCollectionThisWeek.entries.length
              : model.completedCollectionHistory.entries.length;
          baseList = model.collectionState2 == "This Week"
              ? model.completedCollectionThisWeek
              : model.completedCollectionHistory;
          break;
        case "Unavailable":
          listCount = model.collectionState2 == 'This Week'
              ? model.unavailableCollectionThisWeek.entries.length
              : model.unavailableCollectionHistory.entries.length;
          baseList = model.collectionState2 == "This Week"
              ? model.unavailableCollectionThisWeek
              : model.unavailableCollectionHistory;
          break;
      }
    }

    Widget renderUpcomingCollections() {
      return PagedListView<int, UpcomingCollectionRequest>(
        shrinkWrap: false,
        pagingController: _upcomingCollectionsController,
        builderDelegate: PagedChildBuilderDelegate<UpcomingCollectionRequest>(
          itemBuilder: (context, item, index) {
            return CollectionCard(
              date: item.date!,
              areaOfOperation: item.street!['areaOfOperation']['name'],
              street:
                  '${item.street!['name']}, ${item.street!['area']}, ${item.street!['lga']['name']}, ${item.street!['state']['name']}',
              streetId: item.street!['id'],
              status: "missed",
              daysLeft: item.daysLeft,
            );
          },
        ),
      );
    }

    Widget renderCollectionsToday() {
      return PagedListView<int, CollectionRequest>(
        shrinkWrap: false,
        pagingController: _collectionsTodayController,
        builderDelegate: PagedChildBuilderDelegate<CollectionRequest>(
          itemBuilder: (context, item, index) {
            return CollectionCard(
              date: item.createdAt!,
              areaOfOperation: item.adminStreet!['areaOfOperation']['name'],
              street:
                  '${item.adminStreet!['name']}, ${item.adminStreet!['area']}, ${item.adminStreet!['lga']['name']}, ${item.adminStreet!['state']['name']}',
              streetId: item.id!,
              status: "missed",
            );
          },
        ),
      );
    }

    Widget renderWidget() {
      switch (model.collectionState) {
        default:
          if (collectionListInUse == "upcomingList") {
            return renderUpcomingCollections();
          }
          return renderCollectionsToday();
      }
    }

    return Column(
      crossAxisAlignment: CrossAxisAlignment.start,
      children: [
        Container(
          width: 100.w,
          decoration: BoxDecoration(
            color: const Color(0xffE9EBFF),
            borderRadius: BorderRadius.all(
              Radius.circular(10.sp),
            ),
          ),
          child: WasteNgLinearTab(
            tabItems: const [
              'Collections',
              'Missed',
              'Completed',
              'Unavailable',
            ],
            onItemSelected: (i, s) {
              model.collectionState = s;
              model.collectionState2 =
                  s != 'Collections' ? 'This Week' : 'Collections Today';
              switch (s) {
                case 'Collections':
                  // model.collectionStatusCount = model.collectionsToday.length;
                  break;
                case 'Missed':
                  // to be revisited
                  // model.collectionStatusCount =
                  //     model.missedCollectionReqs.length;
                  break;
              }
            },
            value: model.collectionState,
          ).paddingSymmetric(horizontal: 0.w, vertical: 2.h),
        ).paddingSymmetric(horizontal: 5.w, vertical: 0.h),
        WasteNgMaterialTab(
          statusCount: const <int?>[null, null],
          tabItems: model.collectionState == 'Missed' ||
                  model.collectionState == 'Completed' ||
                  model.collectionState == 'Unavailable'
              ? const ['This Week', 'History']
              : const ['Collections Today', 'Upcoming Collections'],
          onItemSelected: (i, s) {
            model.collectionState2 = s;
          },
          value: model.collectionState2,
        ).paddingSymmetric(horizontal: 5.w, vertical: 1.h).paddingTop((1.5).h),
        Expanded(
          flex: 1,
          child: listCount < 1
              ? const Center(child: Text("No Collection Requests"))
              : renderWidget().paddingSymmetric(
                  horizontal: 5.w,
                  vertical: 0.h,
                ),
        ),
      ],
    );
  }
}

Thanks in advance ❤

authors: AndersonArvando Israel001 caiombueno


text:
Missing PR template

Addition of Pull Request Template to improve clarity and to make it easier for new contributors.
Please assign this issue to me under GSSoC'23 @SahityaRoy

Yup go ahead

what is the update

@SahityaRoy Sir, i will complete it by tomorrow. Sorry for the delay. My exams are going on right now.


text:
Problems with "Ladies & Crooners" frech jazz webradio

This works with VLAN in my laptop:
http://icepe4.infomaniak.ch:80/jazzladiescrooners-high
but not with esp-radio.
Please help

Looks like your link is being forwarded.
Try http://jazzladiescrooners.ice.infomaniak.ch/jazzladiescrooners-high.mp3

Right!  jazzladiescrooners.ice.infomaniak.ch/jazzladiescrooners-high.mp3 works.

YES! it did
Thank you for very fast help

authors: Edzelf dagisr perlix

repo: Edzelf/Esp-radio


text:
fix System.NullReferenceException when disconnecting Handler

Besides, disconnecting the Handler is a workaround for memory leaks:
https://github.com/dotnet/maui/issues/20283#issuecomment-2218729505

Thanks @sferhah , I'll work on merging this.
I plan to eventually re-work all the code in this repo to be based on what's shipping in .NET MAUI, and the logic for cleanup/preventing memory leaks is a lot better in that code base. But for now I think this is good!

authors: Eilon sferhah

repo: Eilon/MauiHybridWebView


text:
Error if no email account on device

Just tested with an iPhone with iOS 15 and no email account.
To Native ->  EmailComposer open 126488619 2021-10-02 18:44:50.261700+0200 App[434:10379] [MFMailComposeViewController] Unable to initialize due to + [MFMailComposeViewController canSendMail] returns NO. 2021-10-02 18:44:50.263913+0200 App[434:10379] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Application tried to present a nil modal view controller on target <Capacitor.CAPBridgeViewController: 0x10540b540>.' *** First throw call stack: (0x181f0b05c 0x19a425f54 0x1847f237c 0x1845dc9b4 0x184578dfc 0x1846ef638 0x184601de0 0x104cce438 0x104cce4dc 0x105124a20 0x105126700 0x105136a90 0x181ec3ce4 0x181e7debc 0x181e913c8 0x19d6a238c 0x1848370bc 0x1845b4be8 0x104b60ddc 0x104df5a24) libc++abi: terminating with uncaught exception of type NSException dyld4 config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Application tried to present a nil modal view controller on target <Capacitor.CAPBridgeViewController: 0x10540b540>.' terminating with uncaught exception of type NSException

You should check this with the hasAccount function before

authors: EinfachHans vogloblinsky

repo: EinfachHans/capacitor-email-composer


text:
Pathfinding Improvements

Fixed issues with pathfinding which causes mobs to walk into walls and get stuck. Seems to be working a lot better now with the A* and theta pathfinding at least (I've not touched the neighbors or obstacle_avoidance methods).
Pathfinding Improvements
mob_meta.get_node_height:
Moved to pathfinding, and made public (creatura.get_node_height).
Now uses collision box rather than node box, if available, unless flag specifies not to.
Fix for getting node height for nodes with connected node boxes
pathfinding.get_ground_level:
We now have one copy between pathfinding and mob_meta.
Can check a larger range of nodes at different heights.
Takes into account node height of both target node, and the height of the node we're coming from.
pathfinding.get_neighbors:
Get maximum distance mob can travel up/down from mob stepheight.
Improved checking diagonals are clear.
Improved checking vertical clearance, takes into account height of current and target node.
Vertical clearance can cope with nodes that have a different collision and node boxes, like snow.
Vertical clearance has a tiny height adjustment so a 2 node heigh entity can fit through a 2 node gap.
Fixed bug where it was assumed a node was reachable if it's the end goal.
methods.movement_theta_pathfind and movement_pathfind:
Fixed bug that raised goal pos by 0.5 nodes.
Movement Improvements
Pathfinding movement functions for A* and theta have been combined into one generic function.
Ensure next goal is always set if there is a valid path.
Checking if mob has reached the next goal improved - now works no matter the mob height, and the height of the node below the goal.
Mobs now won't overshoot their goal, if they're very close to it (less than mob width) their speed reduces.
The more a mob is turning, the less forward velocity it has. This should fix spinning a lot.
mob:pos_in_box now can take a size param that is a table, containing the separate width and height.
pathfinding.moveable no longer pads an extra 0.2 around the width of mob when checking if there is sufficient space for the mob.
pathfinding.get_neighbors now uses max_fall for the maximum distance we can go down, instead of stepheight.

Did some testing and found that it breaks mob following behavior in Animalia. Spawn in some cows and hold wheat, they just walk in somewhat of a circle. Pretty sure this has to do with the changes to pathfinding movement methods.

Fixed, the vertical check on the pos_in_box should be correct now, no matter the node its standing on too.
Also the movement should be better in general, at least less susceptible to spinning. The more the mob has to turn, the less forward velocity it has. If it has to turn at full turning speed, the forward velocity drops to zero. This means it won't circle the position it's aiming for.

First issue I've found is that pathfinding.moveable padding by 0.2 isn't a bug. It does so because of an issue with indexing positions without the padding. Sorry for not getting to this sooner btw, been busy with some visual assets.

I can add it back in, but would you mind explaining what you mean by indexing positions and the issue without the padding?

Best explained through screenshots.
The particle represent the indexed positions of a Dragons hitbox with the + 0.2 padding

and this is without the padding.

I have no idea why this happens, but not having the padding is definitely a potential issue for bigger mobs.

Is this to do with index_box_border in mob_meta.lua?

Nope, index_box_border just grabs each node around the based of a mobs collisionbox but doesn't modify anything. I encountered this same issue with mobkit as well, so I don't think any lua-side tampering is to blame.

Odd, as far as I can see, pathfinder.moveable is only used in pathfinder.get_neighbors.

It is, but it's very important because it checks if the mobs entire collisionbox can fit at each neighboring position.

I'll add it back, also found an issue with dragons pathfinding around snow, will fix that too.

I've increased the mob's collision box vertically when we're checking if the next pathfinding goal is inside the box, this helps dragons. The fire dragon seems to have trouble pathfinding around its own fire, although that seems to be an existing issue (shouldn't fire be seen as non-walkable?).

repo: ElCeejo/creatura


text:
[Bug Report] upload file component: the role of on-preview method is inconsistent with the document.

Element UI version
2.3.7
OS/Browsers version
Windows 7
Vue version
2.3.3
Reproduction Link
https://jsfiddle.net/api/post/library/pure/
Steps to reproduce
用vue-cli本地构建一个新项目，
制作一个简单的上传文件demo，
需求：上传文件后拿到服务器端返回的数据，
根据文档：http://element.eleme.io/#/zh-CN/component/upload
on-preview的功能是：
点击已上传的文件链接时的钩子, 可以通过 file.response 拿到服务端返回数据
但是实际上执行的时候发现， :on-preview="handlePreview"这个方法根本没有被执行
如果这是个bug，请你们修复
如果这个方法是别的作用，也请你们更新文档说明
谢谢。
PS：最后我用 on-success解决了问题。
What is Expected?
请你们判断以上问题是bug还是文档说明有误，
如果是bug，请修复bug
如果是文档说明错误，请更新文档。
What is actually happening?
请你们判断以上问题是bug还是文档说明有误，
如果是bug，请修复bug
如果是文档说明错误，请更新文档。

文档有误，应该是 file.url。我改一下。

我也遇到了这个问题，后面解决了吗

authors: Leopoldthecoder gitspringcould ykl124

repo: ElemeFE/element


text:
[Feature Request] select中的clearable触发

Existing Component
是
Component Name
select
Description
select中的clearable 能否作为一个方法调用？？

比如在选择地区的时候，在国家，省份，城市三个select中进行筛选，能否在切换国家的时候动态去清空省份以及城市的select??而在进行省份的切换时清空城市的select？
https://jsfiddle.net/fp8mtkwb/

监听国家的 change 事件，然后给省份和城市的绑定值赋值为空即可。

authors: Leopoldthecoder kukujbb


text:
[Feature Request] wants to open input new properties

Existing Component
是
Component Name
el-input
Description
希望添加键盘属性。输入框通过enter键实现提交功能。

Please read the FAQ before submitting an issue.

authors: Leopoldthecoder qianqWang


text:
Pagination:  input bug

currentValue in input component's data object didn't refresh when changeHandle emited

Please write a demo of the bug you're trying to fix.

Pagination bug repro by gif

@Leopoldthecoder
 a demo with code and repro step

authors: Leopoldthecoder mengro


text:
InputNumber: event on typed changes

When people are typing into number input, they need to receive change notification
Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

Not handling 'input' event is intentional. This is to allow partial inputs such as '0.', which is emitted as 'input' event. If handleInputChange is called, such inputs will be truncated, and user will not able to input decimal numbers.

I think it can work if we update on input and format on change

Well. It won't. Input-number's input emits a number. There is no way to distinguish "0." and "0" which are both represented as Number(0).
When input is emitted, component's value gets updated, which resets the value of native input.


text:
项目跑不起来

直接clone项目然后npm install完了之后example里的项目跑不起来，报错
如下：
SkeletonPlugin.prototype.outputSkeletonScreen = async function () { // eslint-disable-line func-names

百般折腾卸载Node和npm更新神奇般的好了

repo: ElemeFE/page-skeleton-webpack-plugin


text:
Reference implementation of CT descriptors

I'm aware that there are already a basic form of CT descriptors in this library, and this does not remove them, it just adds a new module which should act as a reference implementation for https://github.com/ElementsProject/ELIPs/pull/1
WIP because it needs a new rust-elements release to get tagged hashes in bitcoin_hashes.

Oops, missed some files. Added and force-pushed. I squashed everything because the individual commits weren't split out right; let me know if I should split them up again.

@sanket1729 regarding "should we remove the Blinded descriptors now", yes, and re "should this be called Descriptor, I think yes, the goal is to use it as confidential::Descirptor. We can also re-export it under a new name.

@apoelstra, agreed on both things

Addressed all comments. Remaning todo:

Update reference impl to use hash_to_private (and address comments on that PR)
Generate test vectors from the reference impl
Add a note forbidding uncompressed keys

So, where I'm at with this is that I need

a way to encode internal descriptors without checksums, which requires
https://github.com/rust-bitcoin/rust-miniscript/issues/477 and then
a new rust-miniscript release, whose use requires
an update of the rust-miniscript dependency here, which requires
an update of the rust-bitcoin and rust-elements dependencies here, which require
https://github.com/ElementsProject/rust-elements/pull/152

Thanks for the enumerated list. Left some feedback on elements repo.

@apoelstra, what is the status of this project/PR?

@sanket1729 I intend to finish this and merge it. I think I've got everything I need now? Will try to do it over the weekend or early next week.

Rebase only.

cc @sanket1729 I have finally finished this PR, with test vectors and everything.
No rush, but ready for review.

It would be nice to have elements_miniscript::confidential::Descriptor::parse_descriptor implemented so we can use descriptors strings with (extended) private keys. Now with from_str we can only parse descriptors with public keys. It would allow to create test vectors with private keys.

On @LeoComandini out-of-band advice we may modify this scheme so that the "bare pubkey" variant p2c-commits to the scriptpubkey. Conveniently, even when the scriptpubkey is exposed alongside the resulting key, nobody can "undo" the p2c and learn the original public key. So we get very good on-chain privacy here, even when one participant in a multiparty setup is reusing keys.
Will update after some more thought. Writing here so I don't forget.

Can now be rebased

Nice. I need to add some xpub-based test vectors but this is otherwise ready for review.

cc @sanket1729 ready for review

Checked against the spec. Any reason why don't have wildcards in BlindedKey?

There isn't a type called BlindedKey, but I guess you mean, "why not have wildcards in the blinding key". The reason is a bit dumb -- it's because we have a generic keytype for the main descriptor, but for the blinding key we have either (a) a generic type, or (b) a DescriptorSecretKey.
Generic key types don't, in general, have wildcards. Normally, wildcards are handled by people taking a generic descriptor, using DescriptorPublicKey with it, and then using some convenience methods around Descriptor::translate_pk to map every pubkey to a DefiniteDescriptorKey at a particular index. The descriptor itself doesn't understand anything about indices.
So, when the descriptor has an extra "blinding key" which needs to be updated in tandem with the the rest of the keys, our generic-key model breaks down. I think the right way to handle this would be to link DescriptorPublicKey and DescriptorSecretKey somehow, so that we could say that CT view descriptors had a blinding key which was Pk::SecretKey or something rather than a concrete key type. Then for the specific case of DescriptorPublicKey, we could support deriving public and secret keys at the same time.
Does this make sense? Basically the issue is that we're mixing a generic keytype and a concrete one, and our API does not handle this gracefully.

@apoelstra, I get the issues with DescriptorSecretKey. One of the main benefits of decsriptors is backing up and recovery.
Perhaps, I am misunderstanding something here, if ct(xpub/*,wsh(ms)), would the backups not grow linearly instead of just a single copy?

@sanket1729 I don't understand what you're saying. The spec allows wildcards. The reference implementation just doesn't support it because I didn't want to do the rearchitecture work required for it.

Going to merge this; can address comment nits in a followup PR.

authors: LeoComandini apoelstra sanket1729

repo: ElementsProject/elements-miniscript


text:
Fix sim speed benchmark

The benchmark is out of date with the new reset and data loading changes. This PR fixes it.

cool, will run this and check new perf soon!

@jsuarez5341 I dont think you would see any perf changes. I am only bringing the benchmark script up to date with a couple of API changes.

repo: Emerge-Lab/gpudrive


text:
Adicione outras modalidades

Adicione outras modalidades

Não precisa

8sso


text:
Preproceesing eICU issue

I got the following error while running the pre-processing scripts by python3 -m eICU_preprocessing.run_all_preprocessing
File "/anaconda3/envs/TPC_Proj/lib/python3.8/runpy.py", line 194, in_run_module_as_main
return _run_code(code, main_globals, None,
File "/anaconda3/envs/TPC_Proj/lib/python3.8/runpy.py", line 87, in_run_code
exec(code, run_globals)
File "/eICU/TPC-LoS-prediction/eICU_preprocessing/run_all_preprocessing.py", line 18, in
timeseries_main(eICU_path, test=False)
File "/eICU/TPC-LoS-prediction/eICU_preprocessing/timeseries.py", line 228, in timeseries_main
gen_timeseries_file(eICU_path, test)
File "/eICU/TPC-LoS-prediction/eICU_preprocessing/timeseries.py", line 166, in gen_timeseries_file
merged = timeseries_lab.loc[patient_chunk].append(timeseries_resp.loc[patien                                                                             t_chunk], sort=False)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexing.py", line 967, in getitem
return self._getitem_axis(maybe_callable, axis=axis)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexing.py", line 1194, in _getitem_axis
return self._getitem_iterable(key, axis=axis)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexing.py", line 1132, in _getitem_iterable
keyarr, indexer = self._get_listlike_indexer(key, axis)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexing.py", line 1330, in _get_listlike_indexer
keyarr, indexer = ax._get_indexer_strict(key, axis_name)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexes/multi.py", line 2587, in _get_indexer_strict
self._raise_if_missing(key, indexer, axis_name)
File "/anaconda3/envs/TPC_Proj/lib/python3.8/site-packages/pandas/co                                                                             re/indexes/multi.py", line 2605, in _raise_if_missing
raise KeyError(f"{keyarr[cmask]} not in index")
KeyError: '[141939 142056 142476 142521 142560 146391 147447 149039 149606 15300                                                                             6\n 160529 162431 166572 166709 167391 167417 171174 175528 177651 178069\n 1788                                                                             58 179142 179554] not in index'

@hanyin88 I have downgraded my Python version but getting errors around installing torch=1.5.0. Can you share the final package versions that you have used to fix this issue please? Thanks.

Ok, these versions of packages worked for me(atleast for pre-processing):
requirements.txt:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
absl-py=1.4.0=pypi_0
aiohttp=3.8.6=pypi_0
aiosignal=1.2.0=pypi_0
apscheduler=3.6.3=pypi_0
async-timeout=4.0.2=pypi_0
asynctest=0.13.0=pypi_0
attrs=22.2.0=pypi_0
backports-zoneinfo=0.2.1=pypi_0
cachetools=4.2.2=pypi_0
captum=0.2.0=pypi_0
certifi=2024.2.2=pypi_0
charset-normalizer=2.0.12=pypi_0
click=8.0.4=pypi_0
cloudpickle=3.0.0=pypi_0
colorama=0.4.6=pypi_0
colorlover=0.3.0=pypi_0
contourpy=1.1.1=pypi_0
cycler=0.10.0=pypi_0
dataclasses=0.8=pypi_0
decorator=4.4.2=pypi_0
dill=0.3.4=pypi_0
flask=2.0.3=pypi_0
fonttools=4.51.0=pypi_0
frozenlist=1.2.0=pypi_0
grpcio=1.48.2=pypi_0
idna=3.6=pypi_0
idna-ssl=1.1.0=pypi_0
imageio=2.15.0=pypi_0
importlib-metadata=7.1.0=pypi_0
importlib-resources=6.4.0=pypi_0
itsdangerous=2.0.1=pypi_0
jinja2=3.0.3=pypi_0
joblib=1.4.0=pypi_0
jsonpatch=1.32=pypi_0
jsonpointer=2.3=pypi_0
kiwisolver=1.4.5=pypi_0
llvmlite=0.36.0=pypi_0
markdown=3.3.7=pypi_0
markupsafe=2.0.1=pypi_0
matplotlib=3.2.2=pypi_0
multidict=5.2.0=pypi_0
multiprocess=0.70.12.2=pypi_0
networkx=2.5.1=pypi_0
numba=0.53.1=pypi_0
numpy=1.18.1=pypi_0
packaging=24.0=pypi_0
pandas=0.24.2=pypi_0
pathos=0.2.8=pypi_0
pillow=10.3.0=pypi_0
pip=21.3.1=pyhd8ed1ab_0
plotly=5.18.0=pypi_0
portalocker=2.7.0=pypi_0
pox=0.3.0=pypi_0
ppft=1.6.6.4=pypi_0
protobuf=3.19.6=pypi_0
pyparsing=3.1.2=pypi_0
python=3.6.15=h39d44d4_0_cpython
python-dateutil=2.9.0.post0=pypi_0
python-graphviz=0.19.1=pypi_0
python-telegram-bot=13.12=pypi_0
python_abi=3.6=2_cp36m
pytz=2024.1=pypi_0
pytz-deprecation-shim=0.1.0.post0=pypi_0
pywin32=305=pypi_0
requests=2.27.1=pypi_0
scikit-learn=0.20.2=pypi_0
scipy=1.4.1=pypi_0
seaborn=0.11.2=pypi_0
setuptools=58.0.4=py36ha15d459_2
shap=0.35.0=pypi_0
six=1.16.0=pypi_0
slackclient=2.9.4=pypi_0
slicer=0.0.7=pypi_0
tb-nightly=1.14.0a20190523=pypi_0
tenacity=8.2.2=pypi_0
threadpoolctl=3.4.0=pypi_0
torch=1.10.2=pypi_0
torchvision=0.11.3=pypi_0
tornado=6.1=pypi_0
tqdm=4.66.2=pypi_0
trixi=0.1.2.2=pypi_0
typing-extensions=4.11.0=pypi_0
tzdata=2024.1=pypi_0
tzlocal=4.2=pypi_0
ucrt=10.0.22621.0=h57928b3_0
umap-learn=0.4.6=pypi_0
urllib3=1.26.18=pypi_0
vc=14.3=hcf57466_18
vc14_runtime=14.38.33130=h82b7239_18
visdom=0.2.4=pypi_0
vs2015_runtime=14.38.33130=hcb4865c_18
websocket-client=1.3.1=pypi_0
werkzeug=2.0.3=pypi_0
wheel=0.37.1=pyhd8ed1ab_0
yarl=1.7.2=pypi_0
zipp=3.18.1=pypi_0

authors: Seham-Nasr SpeedRanger

repo: EmmaRocheteau/TPC-LoS-prediction


text:
Skill node highlighting ambiguity

There is ambiguity in node highlighting when right-clicking the attribute name in Attributes sidebar and right-clicking a node in Skill tree.
It is confusing to have green and blue circle highlighting with same meaning, but different way of access. Not to mention that you can have green circle with red cross together on same node.
Is it possible to have just one type of highlighting for node inclusion?
Using only green circle (easier to spot than blue one) should be sufficient.
For attribute name clicking to act as "all or nothing" toggle as it's current behaviour, the check for existance of corresponding highlighted node should be done first.
If such node exists, then unhighlight all highlighted corresponding nodes.
If no such node exists, then highlight all corresponding nodes.

Uh, my intention was to have RGB coding for the different ways. As in, right click node = blue, right click attribute = adds green (now turqiose), right click node again = remove blue (now green).
I mean, my primary intention with this method would've been that you can right click your life attribute in the list, therefore see all life nodes, then manually (blue) highlight the ones you want, then remove the attribute-based highlights.
With your suggestion (at least how I understand it) rightclicking the wrong attribute could result in having half your manual highlights erased (because you probably don't want to find a tree that encompasses all life nodes).

There are so many ways to screw stuff within a split of second, if you do something you should not :)
I understand it, you understand it. Question is, if rest of common folks will understand it.
I won't be the one writing manual explaining all those color combinations :p
Hope color blind people won't have trouble with it.
If you think that this protection is worth of raised complexity. I'm fine with it.

Another thing here is that it might not even be screwing up stuff by mistake.
For example you manually highlight some notable that has life for also having life regen, then you attribute highlight all life nodes to see what you could also highlight (with your suggestion you actually need to rightlick attributes twice, first the notable will be erased). After that you unhighlight that attribute again.
Well your manual highlight is now gone, you'd need to remember everything you previously highlighted to be able to restore it after another type of highlight overlaps with it.
Since search also has another highlight color, I think it would not be too difficult too understand that different ways of highlighting have different colors. You don't need to actually remember which color comes from which combination imo.

Think i found where i wasn't clear enough and got carried away.
I think optimizer should ignore yellow and also red circles. Those should be only informational.
You search for node, you find it and then you decide what to do with it manually. Only blue circles should be the ones used by optimizer.
Just right-click "maximum Mana" attribute or type "life" into search box. Good luck running optimizer with all those nodes :)
I think It should work like this:

search (attribute name clicking, search box, other sources)
decide (select for optimizer)
run optimizer

Think adding cross sign gave us good opportunity to make clear distinction between types of highlighting. As it's hard to call it as form of highlighting.
For the purpose of optimizer term "tag" sould be introduced. Blue circle should be replaced with green checked sign (like in checkbox input). Both green checked symbyl and red cross symbol should be called "tags".
Thus process of highlighting the nodes (placing a colored circle) would be purely result of search methods (clicking on attribute name, typing text into seach box).
While process of tagging would be result of decision whether found (highlighted) nodes should be considered by optimizer to either included them (checked) or exclude them (crossed).
New menu item "Remove All Tags" could be added to clear all node tags, while Unhighlight nodes would clear only highligting (colored circles) resulted from search.
This would make completely clear distinction between highliting as searching for nodes and tagging  as marking the nodes with tags for purpose of optimization.

That sounds way better. I like that idea.
Also with an additional menu entry like "Check-tag all highlighted nodes" (and maybe also "Cross-tag all highlighted nodes") for the cases where it would make sense, there won't be any functionality lost compared to what it is now.

I too like the idea of separating highlighting stuff from using it for the optimizer. It might also help with #106.
I was initially thinking about letting the full tree optimizer UI be accessed by choosing constraints based on nodes (or attributes) you click in a particular manner (e.g. Ctrl + RMB). This would be doable with the proposed distinction (or even use an exclamation mark instead of the check mark), but I'm not sure if it's user friendly enough. Having one UI for the full optimizer might be better in the end.
The question still remains if there should be an interaction between nodes and full optimizer.

For the skill highlighted nodes thing some kind of highlighting/tagging is obviously necessary. So I would say it would not hurt to have the option to also use it for the full optimizer, at least for the highlighting/tagging currently in place. It could also be made accessible in the settings UI, so it could be done in both (updating each other).
Changing constraints like you thought of could then also be done as an additional way to the settings UI if ithat feels intuitive.

Since it seems like no one has started this yet, I'll start working on this later today (and will probably finish it, doesn't look like much work).
The menu entry icons need to be done by someone else though.

Might want to hold off until I get the jewel stuff merged. I am waiting on
the item editor guy to merge all of his stuff too
On Jul 11, 2015 6:39 AM, "brather1ng" notifications@github.com wrote:

Since it seems like no one has started this yet, I'll start working on
this later today (and will probably finish it, doesn't look like much work).
The menu entry icons need to be done by someone else though.
—
Reply to this email directly or view it on GitHub
https://github.com/EmmittJ/PoESkillTree/issues/149#issuecomment-120619783
.

repo: EmmittJ/PoESkillTree


text:
[Bug]: Observation form incorrectly resets when user navigates away from page

Problem:
If the user starts an observation, navigates away from the page, then navigates back, they cannot stop the batch of observations they started. The observation form resets and the "Stop" button becomes unavailable. See the GIF below.
Expected Behavior:
The form state should be maintained despite navigation, including to other pages in our application as well as to external sites.

See #106

repo: Empyrean-Capstone/Empyrean


text:
Purge feature does not work when installing EnMasse using OLM

Describe the bug
When installing EnMasse using OLM, the purge feature does not work.
This is due to missing permissions for the agent service account to create tokenreviews.

I note that the code with this defect has not been released, so was not part of release-0.31.

authors: k-wall lulf

repo: EnMasseProject/enmasse


text:
Support for 1.19x,1.20x and more options

Translate by Google
Update support for 1.19x, 1.20x versions;
Support to customize which blocks belong to log, which blocks belong to leaves, and which tools can be used for mining.

Supplement: It has been tested and available on the 1.20.1 Paper side.

不懂就问，作者还活着吗

authors: Muska-Ami XiaMoHuaHuo-CN

repo: Enaium-SpigotMC/TreeCutter


text:
ファイルからバイナリを読み出してRGBA情報を取得

ファイルパスは今のところ決めうちでいいです FileManager.default でも使ってくだしあ
Dataからすんなり変換できればいいんだけどね…
Pixelクラス作ってRGBA丸ごと保持できたら面白そう(UInt8で保持してCIColorRepresentorとか用意して)

ピクセルフォーマットに変換するとこまでできた Pixel構造体は別ファイルに起こしたほうがいいね
DataはstartIndexベースで評価する　忘れてはいけない(戒め


text:
feature/add-config-option-to-pin-member-to-assignment

Added config option and variable to pin specific members to assignments

Iterate pack version and change log.


text:
Aw Snap window

We occasionally see an "Aw Snap" window within Peruse web browser.

We either need to have Peruse recognize this and handle it, or we need screenshot_analyzer to recognize and handle this.

@ezekiel can you provide some instructions on how to record crash dumps?
@jausborne please save the list of windows names when you see that error - crashed windows are likely to have a special title that you can put into forbidden windows names

@wzin how do we get the list of window names?

@jausborne I'm surprised that you are asking :) http://d.pr/i/1aNV7 < this is included on every montage site.

authors: jausborne wzin

repo: EndPointCorp/lg-peruse-a-rue


text:
Documentation and release notes for the Nuget package

Synopsis
As Energinet/Datahub we need to document how to use the package.
Notes
Are there any expectations from the art / SA?
Acceptance criteria

release notes are published with the NuGet package.
documentation is released with the NuGet package.

Testing:
To test the story the nuget-gallary was used to make sure that the needed information was available for people without knowing the location of our source code.
Our nuget looks like this in the gallery:

1) release notes are published with the NuGet package - PASSED
The page has a link to our release notes, https://github.com/Energinet-DataHub/geh-charges/tree/main/source/Energinet.Charges.Libraries/source/Energinet.DataHub.Charges.Clients/documents/release-notes/release-notes.md

2) documentation is released with the NuGet package - PASSED
The page has a link to the documentation.
https://github.com/Energinet-DataHub/geh-charges/tree/main/source/Energinet.Charges.Libraries/source/Energinet.DataHub.Charges.Clients/documents/documentation.md

authors: bemwen lasrinnil

repo: Energinet-DataHub/geh-charges


text:
Include actor name in ActorUpdatedIntegrationEvent

Charges domain needs to display the actor name in several charge related frontend pages.
In order to do so, we need the actor name published as part of the ActorUpdatedIntegrationEvent
It's the actor name, not the organization name, we need.
Database: ActorInfo.New.Name
Acceptance criteria

[ ] 1 Given an ActorUpdatedIntegrationEvent is published
When inspecting that event
Then actor name is included

Team Volt has initiated the transition to the micro market participants integration events and thus this story becomes obsolete.

repo: Energinet-DataHub/geh-post-office


text:
API design: EndianReader<Read> and EndianWriter<Write> abstractions?

This issue is to discuss whether read/write methods should stay in the Endianness enum alone or we should also provide a monadic abstraction EndianReader/EndianWriter which would contain a source T and the intended byte order, so that one could write code like this:
let src = EndianReader::new(src, Endianness::Little);
let x = src.read_u32()?;

It's already in, under the name ByteOrdered. It supports both static and dynamic endianness, and implements Read and Write depending on the wrapped value.


text:
Update the columns and the content of the columns so the render of the t...

...ables will be neater in the Ensembl mobile website

There seems to be code repetition for Alleles and Genotypes. Can this be split out as a subroutine? Also please avoid using inline styles. Add any styles to an appropriate .css file in htdocs/components.

What Harpreet said. There’s documentation on where to find the pertinent styles here:
https://www.ebi.ac.uk/seqdb/confluence/display/ENS/Ensembl+web+development https://www.ebi.ac.uk/seqdb/confluence/display/ENS/Ensembl+web+development
Cheers
Anne

On 30 Apr 2015, at 15:21, Harpreet Riat notifications@github.com wrote:
There seems to be code repetition for Alleles and Genotypes. Can this be split out as a subroutine? Also please avoid using inline styles. Add any styles to an appropriate .css file in htdocs/components.
—
Reply to this email directly or view it on GitHub https://github.com/Ensembl/ensembl-webcode/pull/223#issuecomment-97815423.

I moved the inline styles into the htdocs/components/85_spreadsheet_table.css file.

authors: ens-ap5 ens-hsr ens-lgil

repo: Ensembl/ensembl-webcode


text:
Multiple-alignment stats

The most important change is that we store the alignment statistics in a different object. This fixes the stats page: http://staging.ensembl.org/info/genome/compara/mlss.html?mlss=1142
See: http://http://ves-hx2-77.ebi.ac.uk:5083/info/genome/compara/mlss.html?mlss=1142
The other change is to use the pre-built species-tree rather than creating a new one

I can't verify this on my sandbox, but that's probably because of my confusion over MLSSids vs release versions. I'll accept the PR anyway and we can check it on staging as it only affects doc pages.

Thanks @ens-ds23 . I can show you on my sandbox if you want


text:
Real-time preview doesn't work properly

I am using Typst Preview v0.3.2 on Windows 10 , which the preview updates only when I save the file instead of changing content in the editor.And the inital preview got complete blank, it previews after the first save.

Preview on type is not enabled by default. You need to manually switch to OnType mode in settings.

authors: Enter-tainer Putinspudding

repo: Enter-tainer/typst-preview-vscode


text:
this repo should be English only

content can stay German, but readme and all of the source code is best to be kept in English to facilitate collaboration

main todo: English readme as default

done

repo: Entkenntnis/htw


text:
[Feature]Methods of refreshing GUI

Hi there, I'm using this API to develop platform independent forge mod and it works well.
The problem is that I have no idea how to refresh gui after click since I need to remove sth from the gui after click.
Have seen that your bingo mod used GuiFactory.guiBuilder() and GuiFactory.paneBuilder(), there're clickHandler()s in every elements which are used to execute some commands, wonder if I can add sth in this code block to implement "remove then refresh" logic.

Have figured out in WonderTrade that it just need to open the GUI again to refresh it.
Another question, do I have to interact with Threads to wait util the database updating finished? Since db accessing is a sole thread, it'll cause asynchronize issue when I write like this:
result=dataRemoveMethods(); openGUI(result);
the GUI will show first and it doesn't wait for the result.

Try to use CountDownLatch to block the code util db accessing finished but it seems not work.

Have figured out in WonderTrade that it just need to open the GUI again to refresh it.
Another question, do I have to interact with Threads to wait util the database updating finished? Since db accessing is a sole thread, it'll cause asynchronize issue when I write like this:
result=dataRemoveMethods(); openGUI(result);
the GUI will show first and it doesn't wait for the result.

I'm sorry I don't understand your question here. You're trying to wait for the database query to have finished executing before updating the GUI? If so, why?

Have figured out in WonderTrade that it just need to open the GUI again to refresh it.
Another question, do I have to interact with Threads to wait util the database updating finished? Since db accessing is a sole thread, it'll cause asynchronize issue when I write like this:
result=dataRemoveMethods(); openGUI(result);
the GUI will show first and it doesn't wait for the result.

I'm sorry I don't understand your question here. You're trying to wait for the database query to have finished executing before updating the GUI? If so, why?

Yep, that's it. It's because I wanna update sth before GUI is refreshed. e.g., I have a db which collects pixelmon data. I wanna get one and then delete it from db. I use GUI to display Pixelmons in the database, so I need to update the GUI after deletion. Therefore, the GUI should be updated after the query is executed.

Then you need to cache your database values because waiting for the database will be potentially too slow for the UI.

Then you need to cache your database values because waiting for the database will be potentially too slow for the UI.

Ah, that's it. I'll have a try and close it, thx for answering! :)

Btw, is there a way to close the GUI in a click handler?

No worries, you're welcome to DM on Discord or ask in my discord server if you've got any other questions :))
And yeah use Player#closeScreen (I think have some examples in the GTS and Bungo repos)

No worries, you're welcome to DM on Discord or ask in my discord server if you've got any other questions :))
And yeah use Player#closeScreen (I think have some examples in the GTS and Bungo repos)

Got it, it works. XD
Just have joined ur discord today, wish I could make cool projects and benefit others one day.

repo: EnvyWare/API


text:
Change ::Int64 to ::Int

This PR is a simple find-replace of ::Int64 with ::Int.
The restriction to ::Int64 breaks support for 32bit systems: https://github.com/TuringLang/Turing.jl/actions/runs/4687453137/jobs/8306774283?pr=1887#step:6:478

@devmotion this is sadly still broken per an Int64 used in an allocation function (see CI).

@devmotion here https://github.com/EnzymeAD/Enzyme.jl/blob/02cefb14b5ad4c57a7d4f7f57750030f71068dc7/src/compiler.jl#L371 can you add:
if value_type(Size) != T_size_t
  Size = trunc!(B, Size, T_size_t
end

Codecov Report
Patch coverage: 100.00% and project coverage change: -1.46 :warning:

Comparison is base (feffac2) 77.13% compared to head (02cefb1) 75.67%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #728      +/-   ##
==========================================
- Coverage   77.13%   75.67%   -1.46%
==========================================
  Files          18       18
  Lines        7182     7158      -24
==========================================
- Hits         5540     5417     -123
- Misses       1642     1741      +99

Impacted Files
Coverage Δ

src/compiler/reflection.jl
84.78% <ø> (ø)

src/compiler.jl
77.71% <100.00%> (-0.08%)
:arrow_down:

... and 7 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@devmotion this still fails in an abi.jl test, but the fix isn't obvious from the CI log. If you have an X86 machine, would you be able to isolate the test which fails (and possibly add a Enzyme.API.printall!(true))

authors: codecov-commenter devmotion wsmoses


text:
[NF] new object to store both time and freq data

In some particular cases, it could be handy to store both time and frequential data, to avoid computing many fft for example. Such an object would contain a DataTime and a DataFreq, and have the same get_along methods which would pick the data in the most appropriate object (DataFreq in case of fft for example). The same logic would be applied to VectorField objects.
Such an object could be named "DataTimeFreq", "DataDual", or "DataBoth". Any other suggestion?

DataTimeFreq 👍

We should keep in mind that sooner or later, we will probably have to define a new Data object to play with short-time fourrier transform. We should be carrefull not to introduce a confusion between your object and this future object (in terms of name in particular).

I close this issue since DataDual has been implemented.

authors: EmileDvs SebGue helene-t mglesser

repo: Eomys/SciDataTool


text:
REQUIREMENTS FOR USING DATETIMEPICKER

The documentation is just saying to use this and that script and css but it doesn't specify what version exactly. Can anyone help?
It doesn't show the form at the current version I am using.
Jquery 2.2.3
Bootstrap 3.3.6
bootstrap-datetimepicker 4.17.*

Me too, it doesn't show the form at the current version I am using.
In addition, I tried to install via Bower, but Bootstrap folder doesn't come...
Anyway, I'll revert to https://github.com/smalot/bootstrap-datetimepicker for now. It seems to be OK with Bootstrap 4.
Another question... I am not sure if it is even possible to install Bootstrap 3 alongside Bootstrap 4... Or Bootstrap 4 only?

This a specifically BS3  version and it does work with jQuery 2.2.3+ that includes jQuery 3.3.1
You can get files from CDNJS

Another question... I am not sure if it is even possible to install Bootstrap 3 alongside Bootstrap 4... Or Bootstrap 4 only?

Most people would say that you shouldn't do it, you don't want things breaking here and there.
For a version of BS4 of this project rewrite from scratch look at https://tempusdominus.github.io/bootstrap-4/

authors: William-H-M patarapolw programmerchibi

repo: Eonasdan/bootstrap-datetimepicker


text:
cargo build step fails with "invalid serialized PackageId" error

Followed the build steps for the epic-miner and it fails on the cargo build step with this error
$ cargo build
error: failed to parse lock file at: /usr/local/src/epic-miner/Cargo.lock

Caused by:
  invalid serialized PackageId for key `package.dependencies`

Tried removing the epic-miner directory, and re-cloning and rerunning, same error.
Environment:
PureOS 10 Byzantium  (debian based distro)
$ rustc --version rustc 1.35.0 (3c235d560 2019-05-20)

I removed the Cargo.lock file and the build appears to be proceeding normally.

Build fails at a different point now
$ cargo build
    Updating crates.io index
  Downloaded byteorder v0.5.3
  Downloaded rand v0.3.23
  Downloaded bufstream v0.1.4
  Downloaded blake2-rfc v0.2.18
  Downloaded native-tls v0.2.11
  Downloaded time v0.1.45
  Downloaded slog v2.1.1
  Downloaded dirs v1.0.5
  Downloaded libloading v0.4.3
  Downloaded bigint v4.4.3
  Downloaded cmake v0.1.50
error: failed to parse manifest at `/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.50/Cargo.toml`

Caused by:
  failed to parse the `edition` key

Caused by:
  supported edition values are `2015` or `2018`, but `2021` is unknown

Started from scratch with a new Ubuntu 24.04 LTS server. Cargo build step fails again with failed to parse lock file error.
$ cargo build --features opencl
error: failed to parse lock file at: /usr/local/src/epic-miner/Cargo.lock

Caused by:
  invalid serialized PackageId for key `package.dependencies`

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04 LTS
Release:        24.04
Codename:       noble

$ rustc --version
rustc 1.35.0 (3c235d560 2019-05-20)

Discovered that this is due to outdated documentation. Rust 1.60 or newer is needed to get past failed to parse error.

repo: EpicCash/epic-miner


text:
BitNet support

BitNet: https://arxiv.org/abs/2310.11453
@JoseCarlosGarcia95, I saw some of your work through PRs in Candle and found it very interesting - in particular, the PR supporting creating quantized BitLinear layers. If you would be willing to collaborate to add these to mistral.rs, it would be great!

Of course, I’d be happy to take a look! :)


text:
Garbled output on very long prompts

Describe the bug
Models seam to produce garbled output on very long prompts.
If i use the following script:
import openai
from transformers import AutoTokenizer

if __name__ == "__main__":
    client = openai.Client(api_key="foobar", base_url=MISTRAL)
    tok = AutoTokenizer.from_pretrained("meta-llama/Meta-Llama-3-8B-Instruct")
    with open("prompt.txt", "r", encoding="UTF-8") as f:
        content = f.read()

    print(len(tok.encode(content)))

    response = client.chat.completions.create(
        model="llama3",
        messages=[
            {
                "role": "user",
                "content": content,
            }
        ],
        max_tokens=256,
        temperature=0.0,
    )
    print(response.choices[0])

To send a 7368 token long prompt to a mistralrs server i recieve the following output:
Choice(finish_reason='length', index=0, logprobs=None, message=ChatCompletionMessage(content='!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!', role='assistant', function_call=None, tool_calls=None))

Meaning , that the server just filled the rest of the context length with !.
If i send the same prompt to an ollama server i get the following result:
Choice(finish_reason='stop', index=0, logprobs=None, message=ChatCompletionMessage(content='One mile is approximately equal to 1.6093 kilometers.', role='assistant', function_call=None, tool_calls=None))

Which is the correct answer for the given prompt.
The prompt i used:
prompt.txt
The server parameters:
--isq Q4K plain -m meta-llama/Meta-Llama-3-8B-Instruct -a llama
Latest commit
Release 0.1.9

Thank you for reporting this.
Can you reproduce the problem with mistral? I think that this may be a problem with needing llama cache shifting.

I think this is an issue with the sliding window. I have reproduced it with Mistral.

@LLukas22, I think I figured it out. It looks like it works when not using ISQ, but if ISQ is used then it breaks. This is probably because we quantize slightly differently than the GGUF implementation?

Perhaps #377 will help this


text:
command line diff and filter error if colon punctuation mark is in the run name

In CodeChecker v6.9.1 filtering and getting the results for run names with colon punctuation mark does not work properly.
If there is a timestamp in the run name we want to filter "myrun-12:23:12" the punctuation mark will be used as a delimiter of multiple run names even if this is not the case.
CodeChecker cmd results myrun-12:23:12

Changes were done in #2201

repo: Ericsson/codechecker


text:
It seems like SSL support issue for IOS?

Dear Stefan:
I deployed sipml5 on a nginx webserver. Then I visit https://nginx webserver url/sipml5/call.htm# on smart phone's browser and tried to make call.
The result is odd. When use android phone with chrome, everything is OK. When use iphone with safari/chrome, I can not even login. Once I press "Login" button, it fails.
It seems not a webrtc supporting issue. I also tested bowser (https://github.com/EricssonResearch/bowser) which claims it has support for audio, video and data on IOS, but it failed to login either.
I visited https://nginx webserver url/sipml5/call.htm with bowser and press "Login" button, the browser suggest "Failed to connect to the server" just the same as safari/chrome, error log from webrtc2sip server is pasted below.
It seems like SSL support issue for IOS? I used signed certs from startssl (https://www.startssl.com/) and everything works fine on android chrome and windows 10 chrome.
Could you please help me to solve this problem ?
Any suggestion would be appreciated !
[root@iZ23a928efdZ sbin]# ./webrtc2sip --config=/opt/webrtc2sip/sbin/config.xml

Copyright (C) 2012-2015 Doubango Telecom http://www.doubango.org
PRODUCT: webrtc2sip
HOME PAGE: http://webrtc2sip.org
LICENCE: GPLv3 or proprietary
VERSION: 2.7.0
'quit' to quit the application.

SSL is enabled :)
DTLS supported: yes
DTLS-SRTP supported: yes
[DOUBANGO INFO]: transport = udp://:10060
[DOUBANGO INFO]: transport = ws://:10060
[DOUBANGO INFO]: transport = wss://:10062
[DOUBANGO INFO]: transport = tcp://:10063
[DOUBANGO INFO]: transport = tls://:10064
*[DOUBANGO INFO]: enable-rtp-symetric = yes
*[DOUBANGO INFO]: enable-100rel = no
*[DOUBANGO INFO]: enable-media-coder = yes
*[DOUBANGO INFO]: enable-videojb = yes
*[DOUBANGO INFO]: video-size-pref = vga
*[DOUBANGO INFO]: rtp-buffsize = 65535
*[DOUBANGO INFO]: avpf-tail-length = [100-400]
*[DOUBANGO INFO]: srtp-mode = optional
*[DOUBANGO INFO]: srtp-type = sdes;dtls
*[DOUBANGO INFO]: dtmf-type = rfc4733
*[DOUBANGO INFO]: codecs = opus;pcma;pcmu;g729;gsm;vp8;h264-bp;h264-mp;h263;h263+
*[DOUBANGO INFO]: UnRegister codec: PCMA, G.711a codec (native)
*[DOUBANGO INFO]: UnRegister codec: PCMU, G.711u codec (native)
*[DOUBANGO INFO]: UnRegister codec: GSM, GSM Full Rate (libgsm)
*[DOUBANGO INFO]: UnRegister codec: VP8, VP8 codec (libvpx)
*[DOUBANGO INFO]: 'h264-bp' codec enabled but not supported
*[DOUBANGO INFO]: 'h264-mp' codec enabled but not supported
*[DOUBANGO INFO]: UnRegister codec: H263, H263-1996 codec (FFmpeg)
*[DOUBANGO INFO]: UnRegister codec: H263-1998, H263-1998 codec (FFmpeg)
*[DOUBANGO INFO]: codec-opus-maxrates = 48000;48000
*[DOUBANGO INFO]: enable-icestun = no
*[DOUBANGO INFO]: max-fds = -1
*[DOUBANGO INFO]: ssl-certificates =
/etc/ssl/private/xphone_online.key;
/etc/ssl/private/xphone.online.pem;
*;
no
[DOUBANGO INFO]: transport = c2c://:10070
[DOUBANGO INFO]: transport = c2cs://:10072
[DOUBANGO INFO]: database = sqlite;
*[DOUBANGO INFO]: sqlite3_threadsafe = 1
*[DOUBANGO INFO]: Database opened = TRUE
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=8, pipeW=9
*[DOUBANGO INFO]: Socket added[TCP/IPv4 transport]: fd=8, tail.count=1
*[DOUBANGO INFO]: master fd=3
*[DOUBANGO INFO]: Socket added[TCP/IPv4 transport]: fd=3, tail.count=2
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=10, pipeW=11
*[DOUBANGO INFO]: Socket added[TLS/IPv4 transport]: fd=10, tail.count=1
*[DOUBANGO INFO]: master fd=4
*[DOUBANGO INFO]: Socket added[TLS/IPv4 transport]: fd=4, tail.count=2
*[DOUBANGO INFO]: Stack running in SERVER mode
*[DOUBANGO INFO]: tsk_timer_manager_start
*[DOUBANGO INFO]: Best source at 0: 121.40.147.38
*[DOUBANGO INFO]: Best source at 2: 121.40.147.38
*[DOUBANGO INFO]: Best source at 3: 121.40.147.38
*[DOUBANGO INFO]: Best source at 4: 121.40.147.38
*[DOUBANGO INFO]: Best source at 5: 121.40.147.38
*[DOUBANGO INFO]: Timer manager run()::enter
*[DOUBANGO INFO]: SIP STACK::run -- START
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=17, pipeW=18
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=17, tail.count=1
*[DOUBANGO INFO]: master fd=12
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=12, tail.count=2
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=19, pipeW=20
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=19, tail.count=1
*[DOUBANGO INFO]: master fd=13
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=13, tail.count=2
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=21, pipeW=22
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=21, tail.count=1
*[DOUBANGO INFO]: master fd=14
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=14, tail.count=2
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=23, pipeW=24
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=23, tail.count=1
*[DOUBANGO INFO]: master fd=15
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=15, tail.count=2
*[DOUBANGO INFO]: tnet_transport_prepare()
*[DOUBANGO INFO]: pipeR fd=25, pipeW=26
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=25, tail.count=1
*[DOUBANGO INFO]: master fd=16
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=16, tail.count=2
*[DOUBANGO INFO]: SIP STACK -- START
*[DOUBANGO INFO]: Transport::run(TLS/IPv4 transport) - enter
*[DOUBANGO INFO]: Transport::run(TCP/IPv4 transport) - enter
*[DOUBANGO INFO]: TIMER MANAGER -- START
*[DOUBANGO INFO]: Transport::run(SIP transport) - enter
*[DOUBANGO INFO]: Starting [TLS/IPv4 transport] server with IP {0.0.0.0} on port {10072} using fd {4} with type {17}...
*[DOUBANGO INFO]: Starting [TCP/IPv4 transport] server with IP {0.0.0.0} on port {10070} using fd {3} with type {9}...
*[DOUBANGO INFO]: Transport::run(SIP transport) - enter
*[DOUBANGO INFO]: Transport::run(SIP transport) - enter
*[DOUBANGO INFO]: Transport::run(SIP transport) - enter
*[DOUBANGO INFO]: Transport::run(SIP transport) - enter
*[DOUBANGO INFO]: Starting [SIP transport] server with IP {121.40.147.38} on port {10062} using fd {16} with type {128}...
*[DOUBANGO INFO]: Starting [SIP transport] server with IP {121.40.147.38} on port {10063} using fd {13} with type {8}...
*[DOUBANGO INFO]: Starting [SIP transport] server with IP {121.40.147.38} on port {10060} using fd {15} with type {64}...
*[DOUBANGO INFO]: Starting [SIP transport] server with IP {121.40.147.38} on port {10064} using fd {14} with type {16}...
*[DOUBANGO INFO]: Starting [SIP transport] server with IP {121.40.147.38} on port {10060} using fd {12} with type {2}...
*[DOUBANGO INFO]: ioctlt(16), len=0 returned zero or failed
*[DOUBANGO INFO]: NETWORK EVENT FOR SERVER [SIP transport] -- FD_ACCEPT(fd=27)
*[DOUBANGO INFO]: Socket added[SIP transport]: fd=27, tail.count=3
*[DOUBANGO INFO]: WebSocket Peer accepted/connected with fd = 27
*[DOUBANGO INFO]: #1 peers in the 'SIP transport' transport
***[DOUBANGO ERROR]: function: "tnet_tls_socket_accept()"
file: "src/tls/tnet_tls.c"
line: "168"
MSG: SSL_accept() failed with error code [5, error:00000000:lib(0):func(0):reason(0)]
*[DOUBANGO INFO]: Removing socket 27
*[DOUBANGO INFO]: Socket to remove: fd=27, index=2, tail.count=3
*[DOUBANGO INFO]: CloseSocket(27)
***[DOUBANGO ERROR]: function: "tnet_transport_mainthread()"
file: "src/tnet_transport_poll.c"
line: "726"
MSG: SSL_accept() failed
***[DOUBANGO ERROR]: function: "tnet_transport_mainthread()"
file: "src/tnet_transport_poll.c"
line: "726"
MSG: (SYSTEM)NETWORK ERROR ==>Success
*[DOUBANGO INFO]: PipeR event = 1
*[DOUBANGO INFO]: WebSocket Peer closed with fd = 27
*[DOUBANGO INFO]: #0 peers in the 'SIP transport' transport
*[DOUBANGO INFO]: *** Stream Peer destroyed ***
*[DOUBANGO INFO]: WebSocket Peer closed with fd = 27

Some additional information.
The networking diagram is sipml5 client----webrtc2sip server--------IMS---------mobile phone.
Sipml5 webpage is visited via web browser on PC/android/IOS.

repo: EricssonResearch/bowser


text:
small /pay issue

When we were testing things out on one of out other plugins, I used the /pay command on myself (no one else was online at the time)
The issue is that it does allow you to /pay yourself  - it says you paid , then you received $ from , but it actually only takes the money from you.
Would a check be able to be added to make it so that you're unable to /pay yourself?

Interesting. I'll test it out and see if I can recreate it.

authors: Erigitic OzarkDragon

repo: Erigitic/TotalEconomy