On browser reload claimable XP isn't showing correctly

Testing on https://xp-testing--taho-development.netlify.app/ and trying some non-happy path scenarios. This is one I tried:

Connected wallet for account '0x50f5f766db5b6ce04f4eacede11e1bf96d6d986e'
Can see that there are 6 XP to claim
Click to claim the first drop but then reject it and leave the modal
Reload the page and check the realm again and it shows 0
Disconnect and reconnect and now the 6 shows again

Video: https://drive.google.com/file/d/11L4Yl6hrf6YTI_wHt01PtX_wM3PvP9-K/view?usp=sharing
It seems like if you reject but then come back, those 6 XP should still have shown without having to disconnect/reconnect the wallet. It's worth nothing that if you don't refresh then it does still show the 6 XP and you can go through the claim flow again. So this seems very much like an edge case to me.

I can't reproduce it with other accounts that have XP there right now. Looking at the video and knowing how it is working I'm 99% sure that the request asking for unclaimed XP just didn't had enough time to resolve and update the UI, sometimes I see that on the xp-testing env it takes up to 5s to load the xp data 😞 This request is not cached in any way so when the web page is reloaded we are starting with clear state and it shouldn't matter if the transaction was rejected. Unless you are able to reproduce it every time so we can sync and debug I think we can close it.


Add more sample data

Codecov Report

Merging #133 (82fe33c) into master (5a51cd0) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #133      +/-   ##
============================================
- Coverage     55.59%   55.52%   -0.07%
  Complexity      785      785
============================================
  Files           167      167
  Lines          3272     3276       +4
  Branches        381      381
============================================
  Hits           1819     1819
- Misses         1351     1355       +4
  Partials        102      102

Impacted Files
Coverage Δ

.../java/seedu/address/model/util/SampleDataUtil.java
8.57% <0.00%> (-1.11%)
:arrow_down:

Continue to review full report at Codecov.

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


Atom 1.52 beta requires CXXABI_1.3.9 which is not available in some distro releases

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
apm fails due to library API mismatch; atom also fails to start, but without obvious error logged
Steps to Reproduce
apm-beta upgrade
Expected behavior:
check for pkgs to upgrade
Actual behavior:
$ apm-beta upgrade
internal/modules/cjs/loader.js:815
return process.dlopen(module, path.toNamespacedPath(filename));
^
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/share/atom-beta/resources/app/apm/node_modules/git-utils/build/Release/git.node)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:815:18)
at Module.load (internal/modules/cjs/loader.js:641:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Module.require (internal/modules/cjs/loader.js:681:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (/usr/share/atom-beta/resources/app/apm/node_modules/git-utils/src/git.js:3:22)
at Module._compile (internal/modules/cjs/loader.js:774:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:785:10)
at Module.load (internal/modules/cjs/loader.js:641:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
Reproduces how often:
100%
Versions
OK 1.51.0.beta0-0.1
BAD 1.52.0.beta0-0.1
Additional Information
Oracle Linux Server release 7.8 (based on RHEL 7.8)
/usr/lib64/libstdc++.so.6.0.19
Name        : libstdc++
Arch        : x86_64
Version     : 4.8.5
Release     : 39.0.5.el7
$ strings /usr/lib64/libstdc++.so.6 | grep ^CXXABI
CXXABI_1.3
CXXABI_1.3.1
CXXABI_1.3.2
CXXABI_1.3.3
CXXABI_1.3.4
CXXABI_1.3.5
CXXABI_1.3.6
CXXABI_1.3.7

Same problem

i am having this problem as well what was the solution to fix this?

i am having this problem as well what was the solution to fix this?

No solution or workaround known, as far as I'm aware.

No solution or workaround known, as far as I'm aware.

Does this still happen on the latest stable release? I mean, I guess they can bundle this...

Does this still happen on the latest stable release? I mean, I guess they can bundle this...

I am getting this error on atom version 1.54.0

I am getting this error on atom version 1.54.0

I'm not understanding any of it as a novice to the set up of it ALL can't help sorry but don't fink I'm right 4 it I told just click watch get dollars lol click watch bank nnnaarr lol
I

I'm not understanding any of it as a novice to the set up of it ALL can't help sorry but don't fink I'm right 4 it I told just click watch get dollars lol click watch bank nnnaarr lol
I

workaround as here:
https://github.com/atom/language-shellscript/issues/142#issuecomment-709820884


user-generated character

after #18 we will have a db schema for characters
we can use non-LLM approach to randomly roll a character using this approach, basically a randomized data approach
we can do template-based images. notably, users should not be able to roll a unique or ultra-rare character this way
in the future after #10 we can do GPT-4 bc users can pay and also we can let users buy these souls and have me manually roll and store them as well
so, these will be basic characters and there is only one per account
in a new issue subsequently, people can buy bronze, silver, gold, and platinum souls manually ie by paying on Ladderly
in a further subsequent issue, people can buy here (with true GPT integration)
in a further subsequent issue, people can buy and sell on a marketplace
in a semi-related issue, owning a character will also generate a card
in another subsequent issue, characters can roll non-character encyclopedia things like places, etc
in a further issue, we will have decks of cards that can be bought together with the art, and maybe if you buy a deck you get a book for free? meh that sounds like a special deal we can do on occassion not the norm but we will see, depends on audience preference/willing to pay

this would be great to plugin to the GPT marketplace and could also be bound to crypto.


Problem with pip install python-binance

Hi, I installed Microsoft Visual Studio 2015, then 2017, and problem is still here.
I see red text with "Twisted" ending in the cmd.
binance.client doesn't exist for python..
Windows 10, 64 bit, python 3.6.4
Thank you!

I got this same issue. Look harder in the return.
You're missing a dependency.
I'm 75% sure its this:
http://landinghub.visualstudio.com/visual-cpp-build-tools
but like i said, it's in the return of "pip install python-binance" in powershell (admin)

I have istalled Visual Studio 17

can you post the entire return of "pip install python-binance"?

Command "c:\users\vishniakov\appdata\local\programs\python\python36\python.exe -u -c "import setuptools, tokenize;file='C:\Users\VISHNI~1\AppData\Local\Temp\pip-build-o6uovkfi\Twisted\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Users\VISHNI~1\AppData\Local\Temp\pip-7g7f27qe-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\VISHNI~1\AppData\Local\Temp\pip-build-o6uovkfi\Twisted\

If you are developing on Windows like me. That you should install Twisted by wheel

Hey I am trying to install in on vscode but it always gives me this error. no matter what I try to install it gives me the same error:
Fatal error in launcher: Unable to create process using '"c:\users\roi\appdata\local\programs\python\python38-32\python.exe"  "C:\Users\Roi\AppData\Local\Programs\Python\Python38-32\Scripts\pip.exe" install python-binance': The system cannot find the file specified.
how can I fix this?

Hey I am trying to install in on vscode but it always gives me this error. no matter what I try to install it gives me the same error:
Fatal error in launcher: Unable to create process using '"c:\users\roi\appdata\local\programs\python\python38-32\python.exe"  "C:\Users\Roi\AppData\Local\Programs\Python\Python38-32\Scripts\pip.exe" install python-binance': The system cannot find the file specified.
how can I fix this?

pip install python-binance was not working because of twisted
tried to install twisted alone using pip dind't worked as well
so I used  conda install twisted and then pip install python-binance
and it installed sucessfully

pip install python-binance was not working because of twisted
tried to install twisted alone using pip dind't worked as well
so I used  conda install twisted and then pip install python-binance
and it installed sucessfully

Yay thanks!!!

Yay thanks!!!

Thanks @arlucio !

@arlucio Thanks helped a lot was stuck for 2 days..

@cryptokcmo lol I was stuck for a week


Code Release

@Cc-Hy  thanks for sharing ur wonderful work , can u please share the code base and pre trained models
THanks in advance

Look forward to code + 1

Thank you for your work. Do you have any plans for when to open the source code？

Thanks for your great work! The results seem really nice. Is there any time schedule of code release? Thanks!


Sumo

Title and your branch says sumo and still the pull request is created for master branch.

@leimaohui I fixed the base branch and the PR includes a single commit on top of our current sumo.
Does this patch has been applied onto master? If so, please note the commit hash you are backporting or submit to master before.

Sorry，I made a mistake. I have closed this PR.


Simplify F.separate test

Simplifies test_separate using testing.FunctionTestCase
Refer to #6071

LGTM. Jenkins, test this please.

Jenkins CI test (for commit e6857aecaca43b8e30c7518febcec0822f31c4a7, target branch master) succeeded!

Merging.


Updating renovate config

Looks like renovate was never configured here, which is why file is empty. Do we need renovate configured here? https://github.com/hmcts/azure-devops-agent/pull/10

Looks like renovate was never configured here, which is why file is empty. Do we need renovate configured here? #10

yeah should be

Closing PR for renovate to be configured via a modified version of https://github.com/hmcts/azure-devops-agent/pull/10


GDB Plugin Upgrade part4: net related tools

Note: Please adhere to Contributing Guidelines.
Summary
Add network related tool, contributed by @wengzhe
netstat: networks statistics.
Impact
New feature.
Testing
Tested with qemu.

Compile:

 tools/configure.sh lm3s6965-ek:qemu-flat

Make sure +CONFIG_DEBUG_SYMBOLS_LEVEL="-g3" is changed to level3.

Run

qemu-system-arm -semihosting \
        -M lm3s6965evb \
        -device loader,file=nuttx.bin,addr=0x00000000 \
        -nic user,id=user0,hostfwd=tcp::10023-:23 \
        -serial mon:stdio -nographic -s

Connect from GDB

gdb-multiarch nuttx -ex "tar rem:1234" -ex "source tools/gdb/__init__.py"

Test
Connect to telnetd in qemu from host: telnet localhost 10023.

Here's a breakdown of what's good and what needs improvement:
Strengths:

Clear Summary: The summary concisely describes the change (adding a netstat tool).  Attribution to the contributor is also good.
Testing Section:  Provides steps to reproduce the test, including build instructions and how to use the new tool. The inclusion of example output is excellent.

Weaknesses:

Incomplete Summary:  While the what is clear, the why and how are missing.  Why is this tool needed? How does it gather and display the information? What specific files were changed?
Insufficient Impact Assessment:  Simply stating "New feature" is not enough. While there might not be changes to the build process or hardware,  considerations for documentation, security, compatibility, and other potential impacts should be explicitly addressed.  Even if the answer is "NO," stating it explicitly is important.
Limited Testing: Testing on QEMU is a good start, but ideally, testing should be performed on real hardware if possible. More importantly, the "before change" log is missing.  Without this, it's impossible to verify that the new tool is actually providing new information. The testing also focuses only on one specific scenario.  More diverse testing scenarios would strengthen the PR.
Missing Issue References:  If this addresses a specific issue in either the NuttX or NuttX Apps repositories, those issues should be linked.
Build Host Information Missing:  The testing section mentions QEMU, but doesn't detail the build host OS, CPU, or compiler used.
No Discussion of Error Handling: How does the tool handle errors? What happens if a network interface is down?  This should be tested and documented.

Specific Recommendations for Improvement:

Expand the Summary: Explain the motivation for the tool. Briefly describe the implementation details (e.g., which system calls or data structures are used).  List the affected files.
Thoroughly Address all Impact Points:  Even if the answer is "NO," explicitly state it for each impact category.  For example: "Impact on build: NO."  For documentation, specify whether documentation updates are included in the PR or will be added later.
Improve Testing: Provide "before change" logs. Test with different network configurations (e.g., multiple interfaces, different protocols). Test error conditions.  If possible, test on real hardware.  Provide details about the build host environment.
Add Issue References: Link any related issues.
Document Error Handling:  Explain how the tool handles errors and unexpected situations.  Include tests that demonstrate this behavior.

By addressing these points, the PR will be much stronger and more likely to be accepted.  A more complete and well-tested PR demonstrates care and attention to detail, making it easier for reviewers to understand and approve the changes.


feat: Enable user to choose their preferred package manager

Enable users to choose their preferred package manager (npm, yarn, pnpm). Preview of how this looks:

Other .
Checklist:

[x] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[x] manually checked my feature / checking not applicable
[x] wrote tests / testing not applicable
[x] attached screenshots / screenshot not applicable

Hey @JohannesMogashoa 👋
Thanks for the contribution ❤  Can you give a brief rationale of why this change is necessary / helpful? Users can already invoke create-sidebase with npm, yarn, ... and it will "just work TM". What is the use-case for allowing the user to invoke the CLI with npm and then choosing pnpm?

Hi there @BracketJohn 👋🏽
Much appreciated. So you are correct in saying that it is not a necessary or much-needed change but I feel it to be to an extent somewhat a "nice-to-have".
If the individual chooses to install the tool globally and not execute npm create-sidebase at every project creation, npm will become default. I say this because I have all three package managers and on occasion, I like switching them so I thought it to be an advantage if I can select whichever package manager I want even if I decide to init this using npm or yarn or pnpm.

Thanks for the thoughful response @JohannesMogashoa and sorry for taking some time to get back to you here.
I get your point, but I do not think that this use-case is frequent enough to warrant an extra step in the CLI:

the recommended way to use this CLI is not by installing it globally but by running {npm, yarn, pnpm} create sidebase@latest
that means that for >95% of users the package manager they use for invocation will be the one the want to work with

In addition even if setting it up with npm but then wanting to switch to pnpm is easy:

Remove package-lock.json / pnpm-lock.yaml
Run {pnpm, yarn, npm} install

So the use-case only applies to <5% of users PLUS the mitigation that these 5% of users can apply is quite straight forward.
Based on this, I do not want to land this PR at the moment. Sorry for that and sorry for the time you invested on something that now will not fully be used. I very very very much appreaciate you taking the initiative and opening a PR - it was really a great moment for us.
In the future, you can open an issue first or ping us on discord (https://discord.gg/9MUHR8WT9B) to ask: "Hey, do you think X is a good idea?" and get earlier feedback this way.
Hope that all makes sense to you, have an amazing day & week,
BracketJohn


Fix ecma_op_array_object_define_own_property

JerryScript-DCO-1.0-Signed-off-by: Kristof Kosztyo<EMAIL_ADDRESS>

Check the ecma standard here: http://ecma-international.org/ecma-262/5.1/#sec-<IP_ADDRESS>
It also fixes the following test262 tests:
ch15/15.2/15.2.3/<IP_ADDRESS>/<IP_ADDRESS>-4-339-3
ch15/15.2/15.2.3/<IP_ADDRESS>/<IP_ADDRESS>-4-34
ch15/15.2/15.2.3/<IP_ADDRESS>/<IP_ADDRESS>-4-547-3

Looks good to me.

Great. make push

lgtm


add support for ExecDomain

ExecDomains should be supported

I found this comment by Wez helpful when I was researching domains https://github.com/wez/wezterm/discussions/4324#discussioncomment-7076398
I confess that I still don't fully grasp how domains work under the hood. I think that Exec domain is almost like the class instance for domain types.
I plan to test connecting to a docker instance because I think it will use the UNIX domain.

I found this comment by Wez helpful when I was researching domains wez/wezterm#4324 (comment)
I confess that I still don't fully grasp how domains work under the hood. I think that Exec domain is almost like the class instance for domain types.
I plan to test connecting to a docker instance because I think it will use the UNIX domain.

Thanks for sharing!


Install Error

After downloading the zip file and extracting all the folders it always gives me this error when I try to run the setup,
Application download did not succeed.
Check your network connection or contact your system provider.
[Full error removed. Issue is pending resolved.]

For now, until it is uncomfirmed I am closing and marking this resolved.


Runtime settings support

Adding entyrpoint so we can have runtime settings modifying the configuration.
Ideally that should address the concern pointed out on #41

You can test it on : quay.io/jrottenberg/fluent2es:runtime-aws-es-user-passwd

+1 @jrottenberg thanks for the patch. Exactly what I needed.

@edsiper Can we merge this or do you have any concern?

@edsiper / @repeatedly - What else might need to be done before merging this in?

@edsiper how about adding more maintainers to this repository?
We are sometimes busy for supporting new features and adapting new k8s features.
Adding more active maintainers is good for users and community.


multilingual website xhtml ?

Hi,
would it be possible to add the functionality for multilingual website ?
=>
with

http://www.example.com/cool
daily
<xhtml:link
rel="alternate"
hreflang="en"
href="http://www.example.com/en/cool"
/>
<xhtml:link
rel="alternate"
hreflang="de"
href="http://www.example.com/de/cool/"
/>

Shouldn't be too hard to implement. I will look into it the next days.

@lgraubner  thanks it would be really amazing for SEO :)

I dived into that feature and actually it's not as easy as I expected. The problem is, that the generator has to skip links which are already handled by a link rel="alternate". But unfortunately the generator is not keeping track on which items were already added as it just streams the pieces to a file. Also a lookahead would be required to not add those site before the "main" language site was added with it's links.

Thanks, I will have a look.


ECC Keys in JWKS Response cause Error

Currently if a JWKS Set contains both an RSA and a ECC key, jwks-client produces an error due to the missing e and n fields in the ECC key.
Using the #[serde(default)] tag in both fields solves the issue; as the library doesn't verify P256 keys, those will still fail but R256 keys continue to function, so it doesn't matter that the P256 key isn't a valid RSA key.

Hey Tim,
Thanks for opening the issue. Is there any chance you could provide a sample keyset (json or url) to help me look at the issue?

{
  "keys": Array[3][
    {
      "kid": "OuLjiRkq<<redacted>>",
      "kty": "RSA",
      "alg": "RS256",
      "use": "sig",
      "n": "<<redacted>>",
      "e": "AQAB",
      "x5c": Array[1][
        "<<redacted>>"
      ],
      "x5t": "<<redacted>>",
      "x5t#S256": "<<redacted>>"
    },
    {
      "kid": "bjFH5u9T<<redacted>>",
      "kty": "RSA",
      "alg": "RS256",
      "use": "sig",
      "n": "<<redacted>>",
      "e": "AQAB",
      "x5c": Array[1][
        "<<redacted>>"
      ],
      "x5t": "<<redacted>>",
      "x5t#S256": "<<redacted>>"
    },
    {
      "kid": "keZwNXPO<<redacted>>",
      "kty": "EC",
      "alg": "ES256",
      "use": "sig",
      "crv": "P-256",
      "x": "<<redacted>>",
      "y": "<<redacted>>"
    }
  ]
}

I do have to redact the actual key material for various reasons so sadly this won't enable you to test the verification itself. The JWKS Data is generated by Keycloak.

That's perfect Tim. Much appreciated.

Hey Tim, an updated version of jwks_client should be available in crate.io (0.1.8). If you could test and let me know if that fixes the error for you that would be greatly appreciated. Thanks again for your help.

Thanks, I won't be able to test the code until early January since we are closed over christmas but I appreciate the quick fix!

Thank. I'm make the issue as closed, but feel free to re-open should there be a problem. Have a great holiday!

Hi, just a closing remark; I was able to test the patch and it works like a charm! Thank you very much!

Thank you for helping me improve jwks-client!


Add instructions for adding users to the render group

Fixes #11

No worries, thanks for merging this!


[In-Person Event] Phony badge application for GSOC 2022 badging bot microtask by Ayush Tamra

In-Person Event Submission
Requirements

Event Name: Phony badge application for GSOC 2022 badging bot microtask by Ayush Tamra
Link to the Event Website:
Are you an organizer of this event? Yes, Ayush Tamra - Chaotic!

Event Demographics

[x] This event commits to Event Diversity and Inclusion.

Q Detail the process for measuring Event Demographics.
A Asking them demographic related questions which are completely optional
Q Provide an example of an opt-out option on the Event registration page if available.
A All demographic related questions are completely optional
Q Provide an example of a demographics text input box on the Event registration page if available.
A Not available

Inclusive Experience at Event

[x] This event commits to the Code of Conduct at Event.

Q Provide an example of the Event Feedback page if available.
A https://example.com/event-feedback-form
Q Is the event team using feedback from previous event's attendees, speakers, and volunteers to improve DEI at this event?
A The feedback is taken from the attendees, speakers and volunteers and shared with the core team to improve the DEI experience
Q Does the event team plan to use feedback from this event's attendees, speakers, and volunteers to improve DEI at future events?
A Yes they do
Q How can attendees learn more about accessibility at the event?
A https://example.com/DEI/resources
Q Does the event platform allow attendees to suggest future accomodations for the event?
A yes it does
Q Will the event platform be accessible to attendees and speakers after the event?
A yes it does

Code of Conduct at Event

[x] This event commits to the Code of Conduct at Event.

Q Is the code of conduct posted at Event venue?
A Yes
Q Provide a link for the Event Code of Conduct.
A https://example.com/Code-of-conduct

Diversity Access Tickets

[x] This event commits to the Diversity Access Tickets.

Q How many different types of diversity access tickets are available for the event?
A one type- travel tickets which are fully funded
Q What are the criteria for qualifying for a diversity access ticket?
A Funding applicants who are from underrepresented groups, and the applicants who are interested in attending but attending the event is not financially feasible for them
Q Provide a link to the page containing information about Diversity Access Tickets.
A https://example.com/Diversity-Access-Tickets

Family Friendliness

[x] This event commits to Family Friendliness.

Q Does the Event provide childcare facilities for its attendees and speakers?
A Yes
Q What are the other ways that a family-friendly environment is being created in the Event?
A We are planning to organize subevents that family memebers including kids can participate example: games, subevents which include some learning and fun!
Q Provide relevant links related to family friendliness at the Event.
A https://example.com/event/family

/result

/end

Working! :smile:


Show instructions explaining hot to view and mark a feedback as done

We're not explaining how you should view a feedback, thus there are users who have no clue and abort the process.
Let's add an explainer at the top of the <SolveExercise> component.

Done!


neovide: 0.13.0 -> 0.13.1

Description of changes
Bump neovide to v0.13.1
https://github.com/neovide/neovide/releases/tag/0.13.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 315136 run on x86_64-linux 1

1 package built:

neovide

@PriceHiller since you did #312630, can you give a look at this one, please?

Works as expected for me. Shouldn't be a breaking change either -- so should be ok.
Hashes match tags.
I'm going to guess that the Darwin x86_64 builds are still broken. (Which #312936 set out to remove -- seems to have stalled though)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4001

commit message should be neovide: update to 0.13.1 also update PR title

Addressed

@andrevmatos consider adding link to changelog / diff to commit message something like d54c554d1487a03f6b2b32825c0428bca23a2501

Addressed


Implement password lookup from the downloaded data

Add a class to lookup password using hash or plain text password.

Resolved in version 1.0.0


⚠ Bofrost.es has degraded performance

In 4ea48fd, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1571 ms

Resolved: Bofrost.es performance has improved in fdd2949 after 6 minutes.


[docs] update list of winning solutions

This project's documentation includes a list of winning solutions for machine learning competitions which used LightGBM.
https://github.com/microsoft/LightGBM/tree/master/examples#machine-learning-challenge-winning-solutions
With one exception (), this has not been updated since December 2019.
How to close this issue
Look through "completed" competitions (from December 2019 to now) at https://www.kaggle.com/competitions.

For each competition, look through the message boards to find posts about the 1st, 2nd, or 3rd place solutions. If these used LightGBM (even as part of an ensemble), create a pull request which adds them to https://github.com/microsoft/LightGBM/blob/master/examples/README.md.

Hi, I can help with the above. I need a quick clarification, from my understanding the above issue requires me to check for the usage of LightGBM in the solution description/discussions of the first three winning entries?

@Juniper-23
yeah, you can review the shared winning solutions in Kaggle/KDD, etc.

Can we close this issue? I think the majority of solutions from Kaggle are covered right now.

yeah I think so


Installation instructions unclear; please clarify

I tried installing as follows:
npm install -g jingo
cd /code/jingo
jingo -s > config.yaml
jingo -c /code/jingo/config.yaml

but get this error:
Bad repository path (not exists):

I am using the full path to the config file, and it does exist at the location:
less /code/jingo/config.yaml | wc -l
      62

Have you modified config.yaml to point to the correct repository ?
  repository: ABSOLUTE_PATH_TO_YOUR_REPO

@jeremypatrickdahan is right.


make Python API on carla 0.9.13 generates .egg file for 0.9.14

Discussed in https://github.com/carla-simulator/carla/discussions/6185

Originally posted by RDB-bit February  6, 2023
Ubuntu 18.04
Python 3.6.9
carla version - 0.9.13
unreal engine - 4.26
This is second time that I noticed that after I run make PythonAPI in carla root folder, .egg and .whl files generated in dist folder are for carla 0.9.14
My make launch command fails here ..
BuildLibCarla.sh: Success!
BuildCarlaUE4.sh: ERROR: UE4_ROOT is not defined, or points to a non-existant directory, please set this environment variable.
Util/BuildTools/Linux.mk:7: recipe for target 'launch' failed
make: *** [launch] Error 2
I believe this is due to version mismatch above. Please advise.

This has been resolved but not happy with how it was resolved
Note : 0.9.14 .egg files did not conflict with 0.9.13 version
Resolution : added UE4_ROOT = ~/UnrealEngine_4.26 at the end of bashrc
I did create a if fi section in bashrc to say if variable = 0.9.13 then UE4_ROOT = ~/UnrealEngine_4.26 and set the variable the variable as 0.9.13. I am not sure why that assignment did not work.


Use satsense for Sentinel 2 tif

As a user,
I want to run satsense over a few sentinel-2 tiles, and osm shapefile as my ground label
because I want to do landcover classification.

@bouweandela any idea?

Hi @prakharcode,
I have used satsense to extract features from a sentinel2 image, so this should in principle be possible. Sentinel2 has the same band structure as quickbird so if you specify that when loading the image it should work.
Something like this should work:
import matplotlib.pyplot as plt

from satsense import Image
from satsense.generators import FullGenerator
from satsense.features import NirNDVI
from satsense import extract_features

# URI to the image
imagefile = 'path/to/your/sentinel2_image.tif'

# Loading the file
image = Image(imagefile, 'quickbird')
image.precompute_normalization()

# Define the step from one window to the next
step_size = [10, 10]
# Define one or more window sizes
windows=[(10, 10)]

# Define the features to calculate
features = [
  NirNDVI(windows)
]
generator = FullGenerator(image, step_size)

# Extract the features (using 1 cpu)
# extract_features is a generator, therefore use the next() function
feature_vector = next(extract_features(features, generator, n_jobs=1))

plt.imshow(feature_vector.vector[:, :, 0, 0])

@prakharcode Have you been able to resolve your issue? If so I can close this issue.


ftrace: Separate top_buffer_size from buffer_size

Since we now set the top buffer size to be the same as the devlib buffer size, this effectively halves the maximum available buffer size that can be set while using devlib. Whatever size is passed as buffer_size will be allocated twice, even if the top buffer is hardly used at all.
This commit separates them into buffer_size and top_buffer_size. If the latter is not passed, the behaviour will not change compared to now.
Fixes: e0c53d09990b5501e493d048a5dce067d8990281

LGTM, if we end up supporting reentrant collectors with alternative buffers then we will still have a single non-top-level buffer per collector, so the parameter will  not need to be generalized to a dict.


investigate replacing R plotting with javascript plotting

Our R dependency is primarily for producing plots.  It could be possible to create plots using javascript instead.  Javascript plots have several potential advantages but also several major downsides.  The biggest and most obvious drawback is that we don't have any code to produce them yet, and they are likely harder to generate and experiment with than R scripts.
The advantage would be that we could avoid requiring an R installation to run hellbender scripts, we could potentially also include interactive plotting or other neat tricks to make the plots more useful.
I see 2 possible routes to replacing Rscripts with javascript.  The first would be for tools that require graphs to perform some html generation and produce html reports with embedded javascript.  The user could then open these in their browser and view the plots ( much like how our test suite report and jacoco is done).
A different option would be to use javascript plotting libraries directly within the jvm to generate SVG.  Java 8 has a new javascript engine which is supposed to be reasonably fast and offers access to java objects from within it.  Unfortunately it doesn't offer a full DOM like a browser does, so most existing javascript libraries will fall over.  It seems like it would take a lot of hacking to get something like d3 to run directly on the jvm.  (someone has done something of the kind here: http://jazdw.net/content/server-side-svg-generation-using-d3js)
Other options would be to use the javafx web panes to display a browser directly, or to plot directly on a canvas.  Either of these options seem like they would be painful and awful.

i'm going to close this. we're not going to implement it.


fix: use correct workspace for online validation

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

Project coverage is 21.69%. Comparing base (dea9a3a) to head (d9e74a8).

Files
Patch %
Lines

cmd/gateway_validate.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1243   +/-   ##
=======================================
  Coverage   21.69%   21.69%
=======================================
  Files          53       53
  Lines        5453     5453
=======================================
  Hits         1183     1183
  Misses       4177     4177
  Partials       93       93

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Addition of prerequisite for helm in website docs

Under the installation process in docs, the section of Choose access options does contain the helm repo add information but directly contains the next step of helm charts installation.
A prerequisite can be added to add the helm keptn repo first before going for helm installation as discussed in today's community meeting.
The command could be: helm repo add keptn https://charts.keptn.sh
For more information visit here: https://artifacthub.io/packages/helm/keptn/keptn
cc- @DavidPHirsch @agardnerIT @bradmccoydev

I would like to work on this!!

Before starting to make changes I wanted to gather some thoughts regarding these two pages:

Choose access options
Install Keptn using the Helm chart

I feel that these two pages contain pretty much the same information and content and can be merged to make a single page 🤔. Please let me know your thoughts on this and also if something else can be done.
OR
We can maybe swap the two pages which can also be a solution.
cc- @agardnerIT @DavidPHirsch

I would be in favor of merging

/assign @agardnerIT

I agree that both these pages are conceptually very close to one another and can probably be merged.

@SuperAayush
If merged, let's close this issue 😄

Hey @ashutosh887!!
There is still some work left on this issue, I am in the middle of my exams and would work on it after they are finished.
I still have some changes to make as per the suggestion of Meg and Adam.
Thank you for giving me a reminder.

Yeah please take your time @SuperAayush
Best of luck to you!

Keptn V1 has reached EOL on December 22nd, 2023, so this issue has been closed.


48272 Create CloudantSyncEncryption.h

What:
Move to a new header file the imports specific for encryption.
Why:
Originally, CloudantSync.h imported the classes and methods to encrypt a datastore if macro ENCRYPT_DATABASE was defined, in other case these classes and methods were not visible in Xcode. However, this macro is never set if the developer is working on a Swift app. More exactly, if a developer creates the bridging header file and includes: import <CloudantSync.h>, when he tries to type the methods to create encrypted datastores, Xcode does not recognise the selector because those methods were never imported.
How:

Edit CloudantSync.h. Create CloudantSyncEncryption.h
In every place where CloudantSync.h is imported, also imports CloudantSyncEncryption.h

Tests:
No tests required.
reviewer @emlaver
reviewer @mikerhodes

+1.

+1


multi: reliable hand-off from htlcswitch to contractcourt

This is achieved by changing the 1-way handoff to a 2-way handoff with a done channel. This is a more ideal pattern for subsystem handoff than the existing way and is ideally how all of our existing 1-way handoffs should be. This is done, for example, in the breacharbiter & chain_watcher handoff.

This doesn't fix #2998 as that is the other way around (contractcourt -> htlcswitch)

Meanwhile the unit test builds seem to fail badly. Do you think they are flakes?

Meanwhile the unit test builds seem to fail badly. Do you think they are flakes?

The main one I see failing is: https://github.com/lightningnetwork/lnd/issues/5437


select variable from different files in the same vim session

the idea is from AngularJS Brackets, will vim-multiple-cursors support this ??

Sorry, I didn't followup this thread.
What I mean is that will vim-multiple-cursors support cross-files selection and replacement as that it does in that video?

No problem! No this plugin does not cross-files

will this feature be listed on future plan or wish list? it looks cool!


chore(dcos-ui): bump DC/OS UI v3.0.7

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

DCOS-ID JIRA title / short description.

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot sync

@mesosphere-mergebot bump-ee

@mesosphere-mergebot sync


Introduce unit and functional testing in pre-commit hooks

We need automated testing to make it easier to ensure core functionality is maintained with re-factoring and addition/modification of code.   Ideally development starts with and remains led by tests, but the world isn't ideal, and hence we need to work this in after the fact.  The issue #181 provides a good opportunity to introduce our first formal test, that the _project_setup.py script, which is core to almost the entire workflow functions.   In that particular instance, the encoding of a text file wasn't correct resulting in the _project_setup.py script not to finish successfully.   An automated test to verify that it does load issued prior to git commit would have picked up this failure.  That particular bug slipped through because the encoding of the template wasn't updated, while the local instance of the configuration file was modified; this was my error and highlights why testing is required.
So! Let's get this sorted.

update
A folder for tests containing a file tests.py that can be run to launch unittests was incorporated in #184 .
The tests implemented to date are to verify successful import of the project setup module, and that the global-indicators.sh file has unix-style line endings (or doesn't have any non-unix style line endings), respectively guarding against issues like #181 and #183.    Both of these tests are run-able both from within the Docker image container environment, and external to it.
However, I can envisage that the running of some tests will depend on project dependencies for running and so will only be able to run within the Docker container.  Those kinds of tests perhaps won't be able to be run from a pre-commit hook for testing if we had one; or, thought needs to be put in to how that would work to make sure it does.

Global Healthy Liveable Cities Indicator Study Collaboration, version 1.2

Processing: Testtest (Manchester) (test_sm_manchester)

test_global_indicators_shell (tests.tests.tests)
Unix shell script should only have unix-style line endings. ... ok
test_project_setup (tests.tests.tests)
Check if _project_setup.py imported successfully. ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.001s

OK

I'm going to close this issue, as unit and functional testing has been introduced now (much work to get coverage up; but a start has been done and the practice can now be continued!)


Avoid opening idxfile to early for writing. Especially as it might ge…

…t truncated due to error handling later on.
Instead just open the file when you need to write it. It does not happen that often to warrant keeping it open all the time.
@toregge PR

LGTM


PII toggle state between request detail page and privacy request manager page are not maintained as expected.

Bug Description
The PII toggle state between the request detail page and the privacy request manager page is not maintained as expected.
Steps to Reproduce

Go to privacy requests page and click to reveal PII.
Now go to a detail page for any privacy request. PII toggle is disabled but the PII is visible.
Click to enable and go back to the privacy requests page. PII is visible for all the requests and the toggle is off.

Expected behavior

PII toggle for the privacy requests page and request detail page should be independent and the default state should have no PII visible.

Screenshots

Note that this was previously reported here: https://github.com/ethyca/fides/issues/1926, but we'll keep this issue as it has screenshots! 😄


Invalid noqa warning should give the file name

I am running ruff via pre-commit and this over multiple files. I just upgraded to v0.0.278 and got the following warning:
warning: Invalid `# noqa` directive on line 867: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`).
warning: Invalid `# noqa` directive on line 869: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`).
warning: Invalid `# noqa` directive on line 871: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`).
warning: Invalid `# noqa` directive on line 873: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`).

Here it would be helpful to also be told the file so that i can have a look and fix this.

Working on it :)

Please note this is a duplicate of https://github.com/astral-sh/ruff/issues/5729


Core: Adding ability to not show validation messages when calling valid().

This feature is very usefull for when you want to check if a field is valid without showing the user he/she has done something wrong.

+1
I created a function with some fields. In onChange event, I test those fields, and if is valid, it call other  function.
I searched and I found issue  #1220. I think is a good idea.
I don't like @staabm suggestion. I think is function the library give information, if is valid or not.

It's a bit of a pain that valid() applies a call to validate(), meaning there's no way to easily check whether the form is valid after it has already been validated. I guess the only way to accomplish that right now is to access the validator.invalid object on the jQuery data attached to the form?
My use case: I'm hooking onto the submit event from some other script on a form that's being validated through jQuery validation. Now, I want to know within that code whether the form that's being submitted is valid or not.
If I call form.valid(), it will redo the validation that just happened due to the submit event, so it's doing the validation logic twice in a row just to check if it's valid...
I guess I would have to hook up a submitHandler to this instance of the form, but can I set that after the validate-setup has already been run? Hmm.

I guess the only way to accomplish that right now is to access the validator.invalid object on the jQuery data attached to the form?

You shouldn't use internal variables, those may change from version to another which will cause your code to break. As an alternative, there are some internal methods that you can use:

validator.numberOfInvalids(): return the count of invalid elements in your form (only the validated ones).
validator.invalidElements(): returns a jQuery array that contains the invalid elements (only the validated ones).

I guess I would have to hook up a submitHandler to this instance of the form, but can I set that after the validate-setup has already been run? Hmm.

From submitHandler's docs:
submitHandler (default: native form submit)
   Type: Function()
   Callback for handling the actual submit when the form is valid. Gets the form as the
   only argument. Replaces the default submit. The right place to submit a form via
   Ajax after it is validated.

Yes, but can you set up a new submitHandler after the form has already been set up with a call to .validate()? Will .validate(options: { submitHandler: function() { new submithandler } }) only overwrite the previous submitHandler, or will it set all the other options back to default also?
For now I've solved this by setting a data attribute on the form and checking if it exists when I first set up the form with .validate() to provide the correct submitHandler, but that's not very flexible.

Yes, but can you set up a new submitHandler after the form has already been set up with a call to .validate()? Will .validate(options: { submitHandler: function() { new submithandler } }) only overwrite the previous submitHandler, or will it set all the other options back to default also?

The second call of .validate( {} ) will be ignored by the plugin.
But I guess you can overwrite the submitHandler this way:
var validator = $( "yourForm" ).data( "validator" );
validator.settings.submitHandler = function() {
    // new submitHandler
};


fix: karma configuration in ng2 blueprint updated, allowing unit testing on travis.

The original karma configuration contained a custom launcher for travis (for more details, please check out karma.conf.js), but it was not used anywhere.
By extending the configuration, it is now automatically applied if travis is detected, and also enabled single run mode for the CI tool, otherwise karma wouldn't exit at the end of the tests.
I am not sure however, if adding an out-of-box travis support directly to the blueprint was the original intention behind the custom launcher.

I signed it!

We currently allow doing single run via the ng test --watch=false. I understand how it would be helpful for the user to have that configuration directly in karma, but I think ultimately the config should "special-case" Travis since there are plenty of other CI's out there in general.
I appreciate you taking the time to do the PR, but that is my reasoning for not accepting it.

Thank you for the answer and the quick decision - you are absolutely right, I also don't think favoring one CI tool over the others would be a good direction for a general tool.
The PR was about extending the current travis-specific configuration of karma.conf.js, since there is already a custom launcher, called Chrome_travis_ci.
From the user's perspective, right now if you want to run your application against a CI tool, you will either have to edit your package.json or your karma.conf.js [you probably want to run your tests on your local machine as well sometimes, this is why adding the commands just to your CI tool's descriptor file (travis.yml for example) would not be enough probably], and there is nothing wrong with that.
But when the user generates the application, scans through the generated files, he will see, that there's already a Chrome_travis_ci launcher, which may lead to a false assumption (just as in my personal case), that this particular CI tool is supported. But this is not the case, which leads to frustration.
@filipesilva  What do you think, would it make sense to remove the Chrome_travis_ci launcher from karma.conf.js, so that the split-brain situation would be solved completely? Travis users must edit files anyway, it would not make such a huge difference them to copy-paste 3 more lines, and it would make it clear, that there is no built-in support favoring one CI tool above any others.
If it does, I would be happy to give a PR for the change!

You know, it completely slipped my mind that we already had the Chrome_travis_ci in customLaunchers. That changes things a bit.
I'd be interested in a PR that removes that from the Karma config, yes. If you are available to do it, I'd point you towards our .travis.yml file that already adds some specific code to make Protractor work in travis by 'faking' chrome: - if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then export CHROME_BIN=chromium-browser; fi.
Maybe there's a good way to do something similar for Karma as well, and we could fully bypass custom Karma config for Travis.

https://github.com/karma-runner/karma/issues/1144#issuecomment-53633076 seems to have had success doing something similar.

Hmm, sure, removing the custom runner is not a big deal, I would love to give a PR for that. :)
So, as I understand it currently, in order to be able to run karma on any CI tools, there are two requirements that needs to be met:

we must run karma with singleRun: true
(for travis at least) we must be able to pass a --no-sandbox flag to chrome.

I can experiment with CHROME_BIN env var, maybe it can use the flag, and then the second option is solved out-of-the-box.
The other one is more interesting here. Since the karma binary is not called directly, we can't pass --single-run to it. The test.ts could however inject the proper singleRun value to the options object, based on an environment variable (SINGLE_RUN?). It already does some preprocessing with the browsers array before creates the server.
This way, no travis specific code has to exist in the codebase, and the behavior could be controlled through environment variables (for example in .travis.yml).
@filipesilva What do you think about it? Isn't it too hacky?

In ./tests/e2e/e2e_workflow.spec.js we are setting test args to run travis in single run mode, so no need to change that.
var testArgs = ['test', '--watch', 'false'];

The --no-sandbox arg might be a bit more complicated though... Not really sure how to do that one without changing karma config tbh.

Maybe it's possible to change the CHROME_BIN=chromium-browser to CHROME_BIN="chromium-browser --no-sandbox" or something?

Okay, so here are my findings: [ng init-ed repository with the new karma.conf.js]
(https://github.com/andyskw/ng_cli_generated_project_for_travis_test) and it's Travis builds.
Looks like CHROME_BIN does not work, but - echo "--no-sandbox" > ~/.config/chrome-flags.conf works flawlessly in .travis.yml. Also works with chromium for those, who prefer that one. You can check out the .travis.yml of the test project for all the settings I am using now.

Oh that's nice! Your technique allows all Travis specific config to be ONLY on .travis.yml, which is just perfect.
For the CLI tests themselves I prefer chromium because it's already installed so it takes less CI time.


Memory leak

I notice that memory use keeps growing till there is nothing left and the process is killed. (takes about 1 hour)
I observe this behaviour on my own tests and the demos
Fresh raspbian sept 2014, node 10.25, mem-split 256/256

Are you still having memory leak issues?

I have not tested the refectored version. I hope to find the time next week.

no more reports so updating.


ezSegmentation

If you haven't already, please read through our contributing guidelines before opening your PR
What is the purpose of this PR?
Adds ezSegmentation functionality. This PR will add many of the backend features.
The notebook and interactive Jupyter components will come in a separate PR.
How did you implement your changes
Currently added the following files:

ez_object_segmentation
ez_object_segmentation_test

Remaining issues
Need to add the rest of the stuff in #847, #907.

Mostly general formatting stuff in the new ezSegmenter notebook. Main points to keep in mind are to:

Combine certain cells into one
Documentation should be done in markdown cells, not code comments
Remove cell outputs, other than example images.

@srivarra looks like the tests for ez_object_segmentation.py are still failing. Can you look into this?


remove setup_requires from setup.py

Hello please consider removing setup_requires=['flake8'] from setup.py
making that work with a simple pip install -r requirements.txt gets very difficult within a corporate intranet.

hey thanks for the issue.
this project is opensource, anybody could propose changes, you could just send a PR :)

see PR, no activity despite the feedback provided, closing :(


Cleanup external tests dockerfile directory

Each external test has the dockerfile directory, which originally set as the location of docker related files( dockefile, shell script). For example https://github.com/adoptium/aqa-tests/tree/master/external/elasticsearch/dockerfile . External tests story has been updated to dynamically generate dockefile there is no need to keep the directory.
We'd like to remove the dockefile directory in external tests and move the shell script file to be the same level of all other files.

print_test_files() will be affected. The line https://github.com/adoptium/aqa-tests/blob/master/external/dockerfile_functions.sh#L423 and https://github.com/adoptium/aqa-tests/blob/master/external/dockerfile_functions.sh#L427 will need to update.

Hey, Can I work on this?

@sophia-guo Except test.sh Can we delete other related files in dockerfile directory (eg: dockerfile) or we have to move those to  external test directories

For the subdirectories that still have static dockerfiles in that directory (system-test and functional-test), we have to check that they will work if we switch them over to use the autogenerated dockerfiles.  If they do, we can remove the static dockerfiles.  Handling these 2 cases can be done under a separate issue / PR.

Thankyou @smlambert , So I will keep those 2 dockerfile directory(inside system-test and functional-test) as it is. And just move test.sh script in both subdirectories to external test directories

Yes, thanks @abhijeetjejurkar

Yes, thanks @abhijeetjejurkar

Welcome😊


Update scala3-library, ... to 3.1.0

Updates

org.scala-lang:scala3-library
org.scala-lang:scala3-library_sjs1

from 3.0.2 to 3.1.0.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-minor

Good point, I didn't know about it. I guess it won't be a problem until we do a next release?


Error says the following:

Error occurred: Error: ENOENT: no such file or directory, scandir '///e%3A/Data%20folder/Code%202023/MERN/React/firebase_auth_and_crud'

Kindly provide more context to the issue. What version of the extension are you using?

VERSION
Released on
3/17/2020, 13:16:33
Last updated
6/10/2022, 13:37:14
I don't know there is some kind of path you are reading using vscode electron node js engine and it is giving me this error. It occurs in every project I open. The path in the error becomes according to the name of the project!
For example:

Error occurred: Error: ENOENT: no such file or directory, scandir '///e%3A/Data%20folder/Code%202023/Firebase/customActionHandler/custom_action_handler'
There is no custom setting mentioned for the extension that could help me!

Thanks. I will look into it this evening and get back to you.

Fixed 🎉


[VS Code] Joining collaboration session: Could not join the collaboration session as it has already reached the maximum of 5 participants.

Error:
Joining collaboration session: Could not join the collaboration session as it has already reached the maximum of 5 participants.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.1326

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.32.3

platformName
MacOS

platformVersion
18.2.0

Hey! You can increase the maximum number of collaborators to 30 by changing the following setting:
 "liveshare.increasedGuestLimit": true
Please re-open the issue if this does not fix your problem. Thanks!


Add depreaction annotations to variables

Enhancement: Add deprecation annotation
We have added the ability to annotate variables in case of deprecations:
refs #3917
Example code for testing:
services/nats/pkg/config/config.go
Host string `yaml:"host" env:"NATS_HOST_ADDRESS,NATS_NATS_HOST" desc:"Bind address." deprecationVersion:"1.6.2" removalVersion:"1.7.5" deprecationInfo:"the name is ugly" deprecationReplacement:"NATS_HOST_ADDRESS"`

Huston, we have a problem...
I updated the adoc.tmpl file so it has no general rendering issues - this is ok now, see the outcome (beside other improvements for readbility)
a|`NATS_HOST_ADDRESS` +
`NATS_NATS_HOST` +
:is-deprecated: true
ifeval::[{is-deprecated} == true]
xref:deprecation-note[Deprecation Note]
endif::[]

BUT
our attempt to define the attribute inside the table does not work. I have tested for hours and post a chat with Antora dev I have the answer why its not working. Note that ifeval is working fine if you have defined the attribute outside the table. You just cant set the attribute inside.

The preprocessor directives are applied on a table before the lines are processed (that's because before we parse the table, we don't know where AsciiDoc table cells are in the table). Therefore, the preprocessor directives will not see the outcome of the attribute entries in the table cell.

As it is merged now, some documentation needs to be added to the dev docs...


[PORT] Replace UseState() with UseBotState()

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3862

Fixes #3859
and use untyped params so that order and type are not fixed.
Tweak RegisterMiddlewareClass so you can provide the key for the turnstate.
Changed projects

Microsoft.Bot.Builder.Dialogs.Adaptive.Testing
Microsoft.Bot.Builder
Microsoft.Bot.Builder.AI.QnA.Tests
Microsoft.Bot.Builder.Dialogs.Adaptive.Templates.Tests
Microsoft.Bot.Builder.Dialogs.Adaptive.Tests
Microsoft.Bot.Builder.Dialogs.Declarative.Tests
Microsoft.Bot.Builder.Dialogs.Tests
Microsoft.Bot.Builder.TestBot.Json

I'll start working on this after #2382 being merged.

Pushing this out as the core change in #2504 adds surface area for a pattern that isn't normally used in JS.
Additionally, between this (RegisterClassMiddleware) and DialogManager.InitialTurnState, I think there might be some room for cleanup around the concept of initializing a TurnContext.TurnState.


Deleting Global Areas

In the dashboard /dashboard/blocks/stacks/view_global_areas there is no option to delete global areas.  I have removed some areas from a theme but they still display in the dashboard list.  We delete button before.

Yes, I want it to be deleted, too.


Issue with k8s.io/docs/concepts/storage/persistent-volumes/

Docs state:

If the admission plugin is turned off, there is no notion of a default StorageClass. All PVCs that have no storageClassName can be bound only to PVs that have no class. In this case, the PVCs that have no storageClassName are treated the same way as PVCs that have their storageClassName set to "".

I don't think this is true. The following storageClassName-less PVC successfully binds to the storageClassName-ful PV:
apiVersion: v1
kind: PersistentVolume
metadata:
  name: local-pv-1
  labels:
    name: local-pv-1
spec:
  capacity:
    storage: 2Gi
  volumeMode: Filesystem
  accessModes:
  - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain #
  storageClassName: local-storage
    path: /mnt/pv1
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: kubernetes.io/hostname
          operator: In
          values:
          - minikube
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: local-storage
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Retain
---
apiVersion: v1
kind: Pod
metadata:
  name: busybox1
  labels:
    name: busybox
spec:
  hostname: busybox1
  subdomain: default-subdomain
  containers:
    - name: busybox
      image: busybox:latest
      command:
        - sleep
        - "3600"
       - mountPath: /mnt/local
         name: local-storage-1
  volumes:
    - name: local-storage-1
      persistentVolumeClaim:
        claimName: my-claim
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-claim
spec:
  accessModes: [ "ReadWriteOnce" ]
  resources:
    requests:
      storage: 1Gi
  selector:
    matchLabels:
      name: local-pv-1

Update: Actually I was wrong. Was testing with minikube. Turns out minikube installs a DefaultStorageClass and a dynamic PV was being created. The selector.matchLabels is being ignored in this case for some reason.


Shadows (and other paintBounds-exceeding paints) are dropped by lazy lists

 Issue by Hixie
Thursday Sep 24, 2015 at 19:07 GMT
Originally opened as https://github.com/flutter/engine/issues/1323

Suppose you have a widget whose position & size happens to place it so that its bottom is just off the top of a vertically scrolling list. Its shadow, if any, will vanish.
We should base these widgets on the children's paintBounds, not their sizes.

Paint bounds isn't a thing anymore.  Maybe the solution here is to pad the viewport by one item?  It's hard to know how far a shadow will extend from beyond the viewport...

https://github.com/flutter/flutter/issues/5467 would provide a real fix for this, but we should probably do the padding thing.

A bunch of bugs about scrolling laziness claim that this is the fix, but actually a better fix for this is pad the viewport by one on each side. We'll also need that to fix https://github.com/flutter/flutter/issues/1714.


Refactor travis build for testing on lowest/highest sf version

[ ] Update the README

I use the same configuration on my projects.
See https://github.com/Spomky-Labs/jose-bundle/blob/master/.travis.yml for example.

Finally I think it's legit to keep at least one build per main symfony version on our lowest supported PHP version (5.5), and build on lowest/highest for other. See #280, let me know wdyt :)


Unable to use keyboard shortcut when modal UI is open

Hello @ECuiDev,
using the plugin I have noticed that it makes it impossible to use keyboard shortcuts when the modal UI is open (in my case, I have 'ctrl+s' to lint the file with the “linter” plugin, when the UI is open I can't, as well as other shortcuts), or, the “Hover” plugin doesn't even work in a second open Obisdian window when the UI is active in another window. Also, it would be very convenient if the UI did not prevent interacting with the file but could behave like the “Hover” plugin windows.
lastly (I didn't want to open another issue for this), on Android, the UI's “answer box” fails to include “short-answers” that are too long and cuts out some text, also preventing scrolling to continue reading.
Thank you very much for this plugin, I use it every day ! hope I was helpful.

Hi,
Regarding the keyboard shortcuts and the Hover plugin not working in a second Obsidian window, I'm pretty sure this is a consequence of Obsidian's Modal class, but I'll see what I can do.
As for the UI not preventing interaction with the file, what do you mean by interaction? Do you mean being able to move the modal around like in this demo video from the Hover Editor plugin?
Lastly, are you using any themes on Android? Certain themes seem to interfere with text overflow which I'm already working on a fix for. If you could attach a screenshot of what you're seeing that would be greatly appreciated.

Hi,
I'm closing this issue as the keyboard shortcut and mobile text cutoff issues have been fixed and will be included in the next release.
Making the UI behave like the Hover plugin turns out to be pretty complex so I've marked it as a feature to be included in a future update.


Add props.validateOnChange check to cDU

Should NOT run validateForm on cDU while props.validateOnChange in FieldArray is set to false

I would like to see this merged as well. This is a major performace issue in Formik. The whole <FieldArray validateOnChange={false}> is broken because it is not used in this comparison!


Adds crash, throwException (iOS only)

Ended up implementing this since I needed it. Not doing Android at the moment so I didn't want to risk messing up the Android code. Thanks!

This is great, thanks!


qtbitcointrader: 1.40.40 -> 1.40.41

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/qtbitcointrader/versions.
meta.description for qtbitcointrader is: '"Bitcoin trading client"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
directory tree listing: https://gist.github.com/ae20974aae82a64b52bae75521882a49
du listing: https://gist.github.com/b1eacd7b070c270a422476afb645bb60

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
qtbitcointrader

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9i8kdlnr3722rs7682wqpwi4xn9g333g-qtbitcointrader-1.40.41 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A qtbitcointrader https://github.com/r-ryantm/nixpkgs/archive/b09108eace2246993cbfaa45c4e0670696e1d1ff.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9i8kdlnr3722rs7682wqpwi4xn9g333g-qtbitcointrader-1.40.41
ls -la /nix/store/9i8kdlnr3722rs7682wqpwi4xn9g333g-qtbitcointrader-1.40.41/bin

@GrahamcOfBorg eval


fix(shipper): added Walmart delivering sensor. Added new subject to Walmart delivered.

Added Walmart Delivering Sensor
Updated Walmart Delivered Sensor subject array.
Updated Walmart Delivered tracking pattern.
Proposed change

Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[x] Update existing shipper

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:

Just the recommendation and then formatting with black should check all the boxes :+1:

I didn't change the version at all. I'm not sure how that happened. I've pushed a new commit with the suggested version change. I also used Microsoft's black extension. I hope that's the right extension.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.13%. Comparing base (3506995) to head (0133e97).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #884   +/-   ##
=======================================
  Coverage   95.13%   95.13%
=======================================
  Files           8        8
  Lines        1481     1481
=======================================
  Hits         1409     1409
  Misses         72       72

Files
Coverage Δ

custom_components/mail_and_packages/const.py
100.00% <ø> (ø)

Thanks!


feat: add button to clear/reset dialog filters

Adds button to clear filters.
If you manually added a filter or implicitly added by coming from an action this helps to clera the filters.
Before you would have to manually select the dropdown and scroll to select the "All *" option. This does it one click and is also a visual indicator if the filter is set.  For examplle if you enter a search term it might be only showing 9 of the total 10 dialogs and you could think you're looking at the complete set but you are not.

Update: Temporarily disregard the amount of files and changes in the PR. I had to rebase on another PR to get the models change and that PR is stuck.  Will fix this when that PR is fixed.

:tada: This PR is included in version 0.361.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed typo as suggested in RT #132764.

Hi @davorg
Please review the PR.
This address the RT #132764 (minor typo in pod) as raised by @gsullivan.
https://rt.cpan.org/Public/Bug/Display.html?id=132764
Many Thanks.
Best Regards,
Mohammad S Anwar

Coverage remained the same at 100.0% when pulling 65f3ccf65622b251d130e56b02749381570df3f9 on manwar:pullrequest-for-rt-132764 into f8f5eefd6e244f4d44d6545952264dc4a196f40a on davorg:master.


Performance compared to MEF 2

There is a comparison library for several IoC implementations. Comparing VS MEF to MEF 2 shows that VS MEF is only better in startup performance, but significantly slower in other benchmarks:
https://github.com/danielpalme/IocPerformance
Compared versions (this is the nuget package version - the screenshot displays the assembly version):

VS MEF: 16.1.8
MEF2: 1.2.0

Do you think it is still justifiable in some cases to use VS MEF over MEF 2? Or could be there a conceptual problem why these benchmark values are worse? Do you maybe have other benchmarks that shows a different picture?

It doesn't look like you linked to a repository containing a VS MEF benchmark, I only found danielpalme/IocPerformance#120. Maybe you can share your implementation instead of just showing some numbers?

I will when I find the time. Do you also have some performance comparison that I could check?

No I don't have measurements, but I'm using VS MEF in a few projects and could check if there's anything obviously wrong. It sounds surprising that VS MEF should be that much slower considering that everything is precalculated.

VS MEF was merged to the main repository of this benchmark:
https://github.com/danielpalme/IocPerformance
If you want to take a look at the comparison using the AppHost package (running the console app will give the result only for Mef 2 and VS Mef):
https://github.com/BalintPogatsa/IocPerformance

I just ported a super large MEF application to Vs-Mef (targeting .NET 4.5.2). My conclusions so far:

Startup is slightly faster if and only if you read the graph from a serialized cache.
Performance overall was not affected.

I suppose the async APIs can be used to further improve performance. Still, I would expect a significant performance gain compared to the old CompositionContainer.

Could the performance discrepancies have anything to do with jitting? I.e. MEF2 is already jitted when the benchmark is performed, whereas vs-mef is not.

That might explain a startup cost, but not a throughput perf difference.
The throughput perf difference I would guess is because MEFv2 creates dynamic methods for every export (IIRC) whereas VS-MEF's execution path to create an export includes evaluating conditions, etc.
Also: vs-mef is thread-safe and MEFv1 and MEFv2 have known thread-safety bugs. Being thread-safe in a MEF engine requires very careful planning, and it's quite possible that in being truly thread-safe, we have a state machine system that is fundamentally slower than the non-thread-safe one that MEFv2 uses.

Not to mention that latest release requires reflection to call GetExportedValue<>(). When can we expect an updated Nuget package?

16.3.4-alpha was just pushed to nuget.org. It should be available in less than an hour and includes the new API.

@AArnott, I just realized that verifying the assembly timestamps is dead slow. So I need to change my conclusion. vs-mef with a cache is definitely faster than MEF.

@AArnott, did you drop support for .NET 4.5.2 in this 16.3.4-alpha version? When updating the nuget package, the package manager tells me this:

Could not install package 'Microsoft.VisualStudio.Composition 16.3.4-alpha'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Yes. 16.3 targets net472 and netstandard2.0.
I believe systems with net452 are no longer in the Microsoft support lifecycle, so we're cutting support for it too.


inccorrect logo color

Bug:
logo of youtube in top left is incorrect:

however if i go to some video and open side bar logo looks correct:

Additional Information
tested on mocha style

Have noticed this for a week or two - I assumed it was due to Youtube rolling out a short-lived logo variation. It appears to no longer be the case for the Basic and Premium logo.


Rasterizing & vectorizing with rasterio

Proposed changes
A notebook demonstrating the use of rasterio for rasterizing vectors and vectorising rasters
Checklist (replace [ ] with [x] to check off)

[x] Notebook created using the DEA-notebooks template
[x] Remove any unused Python packages from Load packages
[x] Remove any unused/empty code cells
[x] Remove any guidance cells (e.g. General advice)
[x] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[x] Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
[x] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
[ ] Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed)
[ ] If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with

accidentally created this PR to merge with master instead of develop


Settings page

Added a settings page option to profile button in navbar. In this page the user can now change home office and put a default value that updates in the db. The user can now also hard delete his account. In the future we can add more functionality to the settings page according to client needs. One example would be password change.

Looks good!


Add Create Sources Flow

Part of the v0 MVP should allow the creation of sources, since that's sort of the whole point. A "source" in this context refers to an entity with at least the following properties:

Title - the display title that will appear in each row.
URL/source href - the actual URL where this source lives.
Creation Date - time/date source was added.
Description - Any additional notes or info to include.
Tags - a one-to-many relationship to tag entities (shape tbd)
Authors - a one-to-many relationship to author entities (shape tbd)

@domisidion - here's a basic issue outline for a feature.
This one specifically goes over what I expect a "source" would actually include, let me know if that lines up to what you were thinking or if you have any suggestions/feedback.

@domisidion follow up question, what do you think about adding empty fields for authors and tags? Should a source be allowed to be created if it has no tags and/or authors?


[Event Request] Codeunit 99000830 OnAfterCopyFromInsertReservEntry

Please add a new Parameter to OnAfterCopyFromInsertReservEntry. As the existing parameterrecord InsertReservEntry2 does only contain the sourcetype fields, but not the quantity and other content, the record ReservEntry is needed to fill the fields correctly:
old:
LOCAL [IntegrationEvent] OnAfterCopyFromInsertReservEntry(VAR InsertReservEntry : Record "Reservation Entry";VAR ReservEntry : Record "Reservation Entry")
New:
LOCAL [IntegrationEvent] OnAfterCopyFromInsertReservEntry(VAR InsertReservEntry : Record "Reservation Entry";VAR ReservEntry : Record "Reservation Entry"; VAR FromReservEntry : Record "Reservation Entry")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Coursier not using SFTP resolver

Added coursier to SBT as a plugin. Immediately resolving does not work for 3 libraries, which are supposed to be taken from an SFTP resolver. That resolver is not even tried.
Does Coursier support SFTP resolvers, or is this to be added?

These aren't supported for now. coursier supports custom protocols via java.net.URL. E.g. fm-sbt-s3-resolver adds support for s3 this way (see https://github.com/frugalmechanic/fm-sbt-s3-resolver/blob/1aa10983e3ba70eefef014fbdd57fb6a66c0a47f/src/main/scala/fm/sbt/s3/Handler.scala).

Closing this for now. Feel free to open a PR with support for that, or to discuss that further here.


Regarding the identification of elements with a high contribution rate in the inspection vector.

Is it possible to add a program that can identify which elements of the vector being inspected contribute significantly to the increase in distance?

I am not sure I understand. Can you provide more details?

I believe the distance is calculated as the Euclidean distance. The Euclidean distance is determined as the square root of the sum of the squares of the differences between the query vector and the training vector. The question becomes, which difference contributes the most to the increase in distance? Can an algorithm be added to determine this?

This logic ranks the squared differences between the query vector parameters and the learned vector parameters used in Euclidean distance calculations. If this logic is customized and added to the HNSW algorithm, it could enable the calculation of the contribution of each feature to the detection of outliers.
#include
#include
#include
#include
// Function to calculate the sum of squared differences between vectors
std::vector computeSquaredDifferences(const std::vector& v1, const std::vector& v2) {
std::vector differences(v1.size());
for (size_t i = 0; i < v1.size(); i++) {
differences[i] = pow(v1[i] - v2[i], 2);
}
return differences;
}
// Function to rank contributions from the sum of squared differences
std::vector<size_t> rankContributions(const std::vector& squaredDifferences) {
std::vector<size_t> indices(squaredDifferences.size());
for (size_t i = 0; i < indices.size(); i++) indices[i] = i;
// Sort in descending order
std::sort(indices.begin(), indices.end(), [&](size_t a, size_t b) {
    return squaredDifferences[a] > squaredDifferences[b];
});

return indices;

}
int main() {
// Example vectors
std::vector learnedVector = {1.0, 2.0, 3.0};
std::vector queryVector = {1.1, 2.1, 3.5};
// Calculate squared differences
auto squaredDifferences = computeSquaredDifferences(learnedVector, queryVector);

// Get ranking of contributions
auto rankings = rankContributions(squaredDifferences);

// Output rankings
for (auto idx : rankings) {
    std::cout << "Feature " << idx << " Contribution: " << squaredDifferences[idx] << std::endl;
}

return 0;

}


Borland ILINK support not possible (order dependency)

I'm looking to add borland's compiler toolset to Tundra but there's a few things that's not too clear to me.
I'm using tundra\scripts\tundra\tools\* as a template starting point replacing the env variables as I go. The borland toolchain makes a distinction between different builds and options. For example, console app vs window GUI app vs dll. Another is single-threaded app vs multi-threaded app. And yet another aspect is static-linking vs dynamic-linking to the runtime library.
What's the best way to encapsulate these options in the toolset lua file? Keep in mind certain options must be used together to get a working executable so this needs to be enforced somehow. For example, if I'm building a multi-threaded app that's linked dynamically to the runtime lib then -tWM -tWR must be passed during compiling and cw32mti.lib must be included when linking. If I'm creating a console app, c0x32.obj needs to be linked. For a Win32 GUI app, c0w32.obj must be linked. Those 2 aspects are mutually exclusive. These various options must be combined together in the right way to produce a working executable.
What's the recommended way to create this abstraction toolset layer for Tundra so it's easy to use and configure?

Closing out old issues that have no traction for now. If you'd like to work on this issue, we can just re-open.

This is fine, given that Borland/Embarcadero's 32-bit toolchain doesn't support C++11, modern C++ programming can't really be done with it.


Drop necessary usage of Exit Stack

Sorry for spam, at the first attempt i encountered many problem and i left this change in the end.
Tests passes and enjoy it.
Remember always bypass the exc_info tuple for wrapped context manager.

Nice, thanks 👍


Bytes over string

[x] Remove unused code
[x] Support Encode for byte[]

Important Note

The transition of parameters from string to bytes[] has been challenging due to our extensive use of Runes. It seems more practical to switch from strings to Runes instead of bytes. Subsequently, we can offer public APIs/methods that accept byte[] and internally convert them to Runes for essential processing.

Reference: https://learn.microsoft.com/en-us/dotnet/fundamentals/runtime-libraries/system-text-rune#convert-a-rune-to-utf-8-or-utf-16

While converting the core processing to UTF-8 bytes, I encountered a more significant issue.
The code style and structure, which closely aligns with Rust conventions, relies heavily on mutable tokens—passing Token references around and modifying them in-place. Some functions merely alter the text property, which eventually results in the token object not reflecting its original state.
Therefore, implementing an Immutable Token Record/Class would address this issue and eliminate much of the back-and-forth conversion between bytes and strings.
So, I'm seeking confirmation: should we implement this before undertaking such an extensive refactor? What are your thoughts?
@vermorel @ClementLokad

It seems there are too many operations on a Token to switch to a byte[] implementation, sorry for that. Using a Span<char> would still be a better fit for our usage to reduce the memory allocation (we can still overload with a string usage), could you try this way please? (there is an equivalent of EnumerateRunes https://github.com/dotnet/runtime/blob/5535e31a712343a63f5d7d796cd874e563e5ac14/src/libraries/System.Private.CoreLib/src/System/Text/Rune.cs#L307).
This Span<char> can be updated when tokenizing.
There are some normalization methods that can only be called on a string, it would be great to have a parameter set by the user to avoid it (NFKC normalization for example) if he knows it's unnecessary, otherwise, cast the Span<char> to a string. We also still want to remove some back and forth conversions like in TokenizationUtils.SubstringByByteOffset. Ideally we would only want to work with the Span<char> and only a string if it's really needed.

@EslaMx7 let's revert the last commit and only keep public TokenizedInput Encode(String inputText, String? additionalInputText, int maxLen, TruncationStrategy truncationStrategy int stride) (removing the one with byte[] parameters, so that we remove the byte attempt and restart from the string version) and I will merge the PR


Adds support for automatically updating the chart when the type changes

I found myself needing this for a project in which I'm using the ember-cli-chart library. It's great when you can create a chart using:
{{ember-chart type=chartType data=chartData}}
And have it automatically update when chartData changes. (Either due to an auto-update loop, or in response to user actions.) However, if one set of data is best viewed as a line chart and another set is better as a bar chart, it follows that changes to chartType should also trigger chart updates.
See it in action: https://vid.me/3ab0

Hi @aomran - would it be possible to have this reviewed? Thanks

Do you know if the latest version of chartjs can update a chart with a type change? I'm working on the next major release of this addon here: https://github.com/aomran/ember-cli-chart/pull/54

I'm not sure - I just thought this would be a good addition to the 2.0.x branch of the addon for any folks who don't want to upgrade to ChartJS version 2 yet.

ok i'll push one more minor version to 2.0.x and then see if I can port this to v3

Does the graph look vertically squished when going from a pie chart to a bar chart? This is the behavior i'm seeing on my branch (https://github.com/busybusy/ember-cli-chartjs/pull/2).

Updating type option isn't working in latest ember-cli-chartjs release. Trying to do so throws many deprectations: https://ember-twiddle.com/e2d9c2b794a64d18201e5bcc03480387


Support the new custom media directory feature for publications media

Tracked in https://github.com/hydephp/develop/pull/685

Fixed in https://github.com/hydephp/develop/pull/938


pdf.js Key bindings will not go away

Hello, in the project I am testing we use pdf.js inside an Angular web app to view PDFs.
After a pdf is viewed, and the user navigates to another view in the app which does not have pdfjs embedded, all key bindings seem to be still going to pdfjs even though it is not visible. For example, arrow keys and backspace do nothing in rich text (trix) input fields, but they do work in regular input fields.
Can someone please help me understand what we have done wrong here?  How can we correctly disable pdf.js' key binding events when the view containing it is not visible?
Any help is greatly appreciated.

This is for the default viewer, but perhaps you are using it too/something similar: see https://github.com/mozilla/pdf.js/blob/059e826e20518a00e4bdcb72a6b7a37bb849a5bb/web/viewer.js#L2016. PDF.js adds the key bindings to window, which might explain why you can use them in another view if you do not refresh the page. You can decide to remove the key bindings when you change views, or refresh the page when you change views, or rewrite the key binding code a bit to not attach them to the window object. Closing as answered.

Thank you very much for your assistance @timvandermeij .