sendEvents Async

Signed-off-by: marius-patrascu<EMAIL_ADDRESS>Description
Send instance, types, registrations events async. Use the default threadPool to not spawn a lot of threads that do small work. Reworked the OMRSTopic interface to support async send, made minimal changes (sendInstance event is not checked, but it could be changed for consistency)
Testing
Build, UT, FVT, UI, manual

This change was functionally tested and validated. No functional regression found.

buidling-data-catalog lab on local dev environment
design lineage flows on private cloud environment


Remove layout property for logs

It is not user friendly for people with some type of colour blindness.
Please, let's try to avoid changing the default colours in the project. It's very personal and everybody is more than capable of customising the working environment if needed

Merged https://github.com/hibernate/hibernate-reactive/pull/372

Huh????
So IntelliJ and Eclipse shouldn't do syntax highlighting by default?
I'm sick to death of not being able to read the SQL in the Hibernate logs because there's no syntax highlighting. And it's amazing to me that in 20 years we did nothing about that, and made ourselves and our users suffer.

It is not user friendly for people with some type of colour blindness.

And that's perfectly fine, because people with accessibility needs are quite accustomed to having to make their own adjustments. Just like I have to increase the font size on my phone.

It's very personal and everybody is more than capable of customising the working environment if needed

So if it's so easy to customize, what's the problem with having a default?

So if it's so easy to customize, what's the problem with having a default?

I don't want to do it right now.
I can read pretty well the default log but the colour scheme you picked makes it hard for me to look at the log.
Also, the colour scheme of my ide is configured to work with a default log, if you start to add colours to it I need to start figuring out how to make the two works.

I'm sick to death of not being able to read the SQL in the Hibernate logs because there's no syntax highlighting. And it's amazing to me that in 20 years we did nothing about that, and made ourselves and our users suffer.

???
The pattern you picked only highlight the priority and the Class name, doesn't do anything for the SQL.
We can probably achieve the same effect without dealing with colours and using chars to separate them.
But if you really want to use colours, at least let's try to find some other combination.

So you haven't actually followed any of what I was working on the last few days, have you?
You just decided to arbitrarily roll back changes I made after quite a lot of thinking and experimentation.

(Run MutinyMain and you'll see why I wanted the log categories colorized.)

I didn't merge the PR.
I didn't touch the example.
The PR that you sent has only one commit saying:upgrade to log4j 2. I wouldn't expect to also change the colour scheme and among all the changes is something that could have been easily missed.
I also don't see the changes for the example in that PR.
I still think some of the colours need to change

But yes, I guess I shouldn't have merged the PR and have a better look at the commits.
I wasn't working on the SQL on the console and didn't realise the ultimate goal of that specific change in the core project.

I also don't see the changes for the example in that PR.

Sorry, I was wrong about it. The commit also contains the changes for the example.

You know what, nevermind, I'm going to revert my changes.

You know what, nevermind, I'm going to revert my changes.
Done


Crash with plustic 8.0.5

Custom modpack,
crash-2022-02-19_23.12.31-client (1).txt

I am getting a similar crash in java.lang.NoClassDefFoundError: landmaster/plustic/modifiers/armor/JetpackPancakeHippos

From a previous issue:
#43 setting "Add Simply Jetpacks as ConArm modifiers" to false seems to fix it.
However my config seems to reset back to having this true when I try to launch.

Okay third time is the charm for saving the config it seems haha. Finally got a successful launch with this config change. Maybe this should be false by default or if there is some deeper cause that needs investigated for why this crash is happening. I was running into this adding the mod to Project Ozone 3 3.4.6

A fixed build is now available on CF.


Modified to use angular-translate.

@lkysow @amoghsa @Jareechang Feel free to merge if you get to this before I do.

:+1: so how do the translators translate these strings now? Edit that config you were going to move to an external file?

Yes. There'd be another $translateProvider.translations('ar'). It'll be a copy-paste of the 'en_EN' version once we're ready to pass it to the translator, who would then replace all the right-hand strings.

nice!


Missing Preprocessing?

Hi,
would you mind sharing the preprocessing how you go from downloaded data that you reference in the README to the files "high_c1_source_tensor", "/high_c2_source_tensor",  "high_c3_source_tensor" which are specified in the default.yaml configurations?
Thanks!

Hello!
@AlexSauer
Did you understand how to preprocess the data?


Add multi-term support to Query#term

Previously a single term could be passed to the Query#term method,
additionally this term needed to be a string. No tokenization is
performed by this method. The API was a bit cumbersome when dealing
with user entered queries, tokenization had to be done manually, and
then the results manually iterated over and used with Query#term.
This change improves matters in two ways:

Lists of terms are supported
A term can be anything that responds to toString

Together these two changes make it possible to directly use the
lunr.tokenizer when passing strings to Query#term.

This has now been merged into master and is released in version 2.2.0


Limiters/queues rename/delete fix. Issue #3924

[X] Redmine Issue: https://redmine.pfsense.org/issues/3924
[X] Ready for review

This PR fixes limiters/queues deleting from the fw rules,
and automatically renames limiters/queues in the rules in case of renaming

since the queue/limiter can be successfully removed from fw rules using these functions, it seems that this code is no longer needed:
https://github.com/pfsense/pfsense/blob/d2abe7c919eaf0c40b911278b96f9bab4fa0be45/src/usr/local/www/firewall_shaper_vinterface.php#L99


Uncaught DOMException when using mongo-decimal and a client collection includes a document with a Decimal object.

image
I have a small Meteor project at https://github.com/gfbeqs/mongo-decimal-test that reproduces the issue
inject.js:1 Uncaught DOMException: Failed to execute postMessage on Window: function Decimal(v) {
      var e, i, t,
        x = this;

      // Decimal called without new.
      if ...<omitted>... } could not be cloned.
    at e.sendMessage (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:29403)
    at u (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:33872)
    at g (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24267)
    at m (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24542)
    at j (chrome-extension://ibniinmoafhgbifjojidlagmggecmpgf/build/inject.js:1:24432)```

Happening to me as well - have to disable the devtools when working with data that contains Decimal128.

Guys, my life has been very crazy at the moment, but now I think I will have some of my bandwidth back and I will certainly check this. Sorry about that.

I implemented a fix, now non-plain objects will be transformed into strings like so:

I will release it until the end of this week.

The fix has been released.


Fix reading/writing small buffers

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[x] My changes were added to the CHANGELOG.md in the proper section.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
Fixes #1728
Testing
See #1728 for a minimal repro

On ESP32 the interrupt triggered before reg_block.cmd().modify(|_, w| w.usr().set_bit()); and before tx.listen_eof() - so the interrupt cleared INT_ENA, then it gets set again making the future believe the transfer is still ongoing

I agree on clearing the interrupts before preparing DMA, but regarding reset_dma_before_usr_cmd the TRM says

Ahhh I see, okay those are probably fine then. I wish the TRM had more details about how these buffers worked.

The failed test test_symmetric_dma_transfer_huge_buffer could be a stack overflow, I've seen that defmt panic before when the global defmt flag gets trashed. Not sure why this has been induced from these changes though :thinking:

The failed test test_symmetric_dma_transfer_huge_buffer could be a stack overflow.

The test also fails with const DMA_BUFFER_SIZE: usize = 50

Since Bjoern is on vacation this week, I will convert this to a draft for the time being.

Turned out clearing the interrupts earlier (which seemed to make sense) caused problems for ESP32-S3 .... Very glad we have HIL-TESTs in place


Arm32 support

Patch of EDK2 for ARM32 support
Adaptation of list of BBR SCT

Hello @cpriouzeau and all,
Base on this P-R, i've created https://github.com/ARM-software/bbr-acs/pull/9 and  https://github.com/ARM-software/bbr-acs/pull/10, as proposals for discussions around 32bit architecture support in bbr-acs.
P-R #9 targets a common BBR_SCT.dsc file for AARCH64 and ARM.
P-R #10 targets a common build_bbr.sh script and prevents need for your commit "ARM32 support: EDK2: patch for ARM32 support".
Dear maintainers, do these changes make sense to you?
These 2 P-Rs do not cover all required changes in other build scripts (build-sct.sh, buildf-wts.sh, build-uefi-apps.sh) for toolchain/architecture selection. I think these could be factorized with related changes in https://github.com/ARM-software/arm-systemready/pull/25.

Can close this P-R as superseded by https://github.com/ARM-software/bbr-acs/pull/11.


List Renderer

Rendering Lists
Lip Gloss ships with a list rendering sub-package.
import "github.com/charmbracelet/lipgloss/list"

Define a new list.
l := list.New("A", "B", "C")

Print the list.
fmt.Println(l)

// • A
// • B
// • C

Nesting
Lists have the ability to nest.
l := list.New(
  "A", list.New("Artichoke"),
  "B", list.New("Baking Flour", "Bananas", "Barley", "Bean Sprouts"),
  "C", list.New("Cashew Apple", "Cashews", "Coconut Milk", "Curry Paste", "Currywurst"),
  "D", list.New("Dill", "Dragonfruit", "Dried Shrimp"),
  "E", list.New("Eggs"),
  "F", list.New("Fish Cake", "Furikake"),
  "J", list.New("Jicama"),
  "K", list.New("Kohlrabi"),
  "L", list.New("Leeks", "Lentils", "Licorice Root"),
)

Print the list.
fmt.Println(l)

Customization
Lists can be customized via their enumeration function as well as using
lipgloss.Styles.
enumeratorStyle := lipgloss.NewStyle().Foreground(lipgloss.Color("99")).MarginRight(1)
itemStyle := lipgloss.NewStyle().Foreground(lipgloss.Color("212")).MarginRight(1)

l := list.New(
  "Glossier",
  "Claire’s Boutique",
  "Nyx",
  "Mac",
  "Milk",
).
  Enumerator(list.Roman).
  EnumeratorStyle(enumeratorStyle).
  ItemStyle(itemStyle)

Print the list.

In addition to the predefined enumerators (Arabic, Alphabet, Roman, Bullet, Tree),
you may also define your own custom enumerator:
var DuckDuckGooseEnumerator Enumerator = func(l *List, i int) string {
    if l.At(i) == "Goose" {
        return "Honk →"
    }
    return ""
}

Use it in a list:
l := list.New("Duck", "Duck", "Duck", "Duck", "Goose", "Duck", "Duck")
l.Enumerator(DuckDuckGooseEnumerator)

Print the list:

Building
If you need, you can also build lists incrementally:
l := list.New()

for i := 0; i < repeat; i++ {
    l.Item("Lip Gloss")
}

Similar to our table implementation, I think it would be desirable to support custom data models.

Hello guys,
I'm in need for this. Can we expect a merge to master anytime soon?
Thanks

Need to add ItemStyleFunc and EnumeratorStyleFunc as well to allow more customization of the list.

ItemStyle and EnumeratorStyle should be aliases for these function.

Need to add ItemStyleFunc and EnumeratorStyleFunc as well to allow more customization of the list.
ItemStyle and EnumeratorStyle should be aliases for these function.

implemented in #264

superseeded by #264

closing in favor of https://github.com/charmbracelet/lipgloss/pull/264


vanilla-dmz: Expose themes under DMZ-{White,Black} names

Description of changes
Mir and maybe other applications down the Lomiri stack expect these themes to be called DMZ-White and DMZ-Black, which are also the names of the folders we enter & build these themes in. I don't know why they are called Vanilla-DMZ and Vanilla-DMZ-AA (I've checked repology, it's also not consistent across other distros) so I'm keeping the Vanilla names via symlinks.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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/1752


Flex wrapped items act unexpectedly ONLY in web view

React Native version:
Expo version 34.0.1 which uses react-native 0.59.8
Steps To Reproduce

See related snack - https://snack.expo.io/B13SVavQH

Describe what you expected to happen:
Items that are wrapped should be grouped closely together based on layout.
If you run the "Android" or "iOS" version you can see that what is shown there is the expected behavior. So this seems to only happen in the web version of the application.

React Native doesn't support Web, please report the issue to expo or react-native-web.


user docs: minimize references to the home view in /help/

Because the home view can be confusing to new users and excessive use of the home view early in one's Zulip career can hurt the development of stream/topic discipline (leading to (no topic) messages and messages sent to the srong stream), we are trying to de-emphasize the home view to new users.  We should make sure the user documentation does not encourage/imply that the home view is what people should use by default (and possibly document the home view as a "power user feature").
For example, https://chat.zulip.org/help/view-messages-from-a-stream gives the following steps as its first suggestion:

In your view, find a message sent to the stream.
Click on the message's stream to narrow your view to all messages sent to that particular stream.

(which basically only makes sense from the home view) rather than suggesting simply clicking on the stream name in the streams menu on the left-hand sidebar (which works from any narrow as well).

it would still be useful (& more productive) for people to be aware that they can eg. narrow if they are in the home view-- would changing the different docs into the simpler versions & adding a Tip for the home view version of things be a good compromise?

@zulipbot claim

@zulipbot claim

I am new to Zulip, can I take this ?
If yes can you elaborate how to proceed please

I am already working on this @visuvasi .

I am waiting for a review on my pull request.

@zulipbot claim

`@zulipbot abandon

@rishig is this actually already resolved?

yup, closing.


Fixes #1739 Analysis does not restart if Python is installed while VS is running

Fixes #1739 Analysis does not restart if Python is installed while VS is running
Fixes notifications when going from "no interpreters" to "global default" interpreter
Fixes analyzer not starting when no interpreters are available
Fixes errors being swallowed by analyzer
Fixes thread safety issues when loading the default interpreter
Excludes some logged events from telemetry collection
Excludes (slow) Event Log data from diagnostics when Shift is held

👍


More flexible API

Hi, thank you for the library!
I am trying to use select with Vec<Rc<serde_json::Value>>, but it seems that the only option I have now is to construct a new array-like serde_json::Value. What about adding (or even replacing existing select methods) new pub trait for navigating in json or some other more flexible API? F.e. wolker that can in-depth and in-width move across json could suit here.

Hi. The answer was very late.
It is understood as saying that it would be nice to have a walker for exploration. The purpose is to find a specific JSON value with "path expression" but I don't know why walker is needed.
If you explain the use case with pseudo code, it will be a little more understandable.
Thank you.


Bug/repair warnings game write step your mission comp moderation test src index

In this branch, I resolved three tickets that dealt with several defined but never used warnings through four files.
In this ticket, I resolved two warnings.
./src/components/pages/Gamemode/YourMissionComp.js
Line 61:11: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
./src/components/pages/ModerationTest/ModerationTest.js
Line 213:11: Headings must have content and the content must be accessible by a screen reader
The first warning was in the YourMissionComp component. There was a redundancy warning with the alt attribute in the img element. The word image was in the text; this is what caused the warning. I simply changed the text to "A boy" and it resolved the issue.
The second warning was an empty h1 element in the ModerationTest component. I checked the codebase to see if this element was potentially going to be used but found no use for this element. I deleted it and the warning was resolved.
 Screen-readers already announce img tags as an image. You don’t need to use the words image, photo, or picture (or any specified custom words) in the alt prop
We had three warnings about duplicates in the index.js file. I checked the codebase and as it turns out, there are no duplicates. The real issue was improper syntax with the ProtectedRoute components on lines 210-211-212. One ProtectedRoute tag was not closed and the other ProtectedRoute on line 212 didn't have a tag at all. I closed the first tag on line 210 and added the ProtectedRoute tag to the ProtectedRoute on line 212. That resolved the issues in this file.
In the GameWriteStep.js file, there was an img element on #112 that had the word "image" in the text of the alt attribute. I changed the text to "A boy" and that resolved the warning.
Trello card: https://trello.com/c/yecJDBnN/617-other-warnings-and-error-d

In this ticket, I resolved several defined but never used warnings:
./src/components/pages/Gamemode/YourMissionComp.js
Line 1:27: 'useEffect' is defined but never used
Line 5:20: 'Button' is defined but never used
Line 7:8: 'UploaderComp' is defined but never used
Line 8:10: 'tasks' is defined but never used
Line 9:10: 'Gamemode' is defined but never used
Line 10:10: 'Link' is defined but never used
Line 10:16: 'Route' is defined but never used
Line 11:10: 'render' is defined but never used
Line 14:11: 'push' is assigned a value but never used
Line 14:17: 'location' is assigned a value but never used
Line 15:15: 'setsRwd' is assigned a value but never used
In the YourMissionComp.js file, there were several imports that were imported that were never used.
From line 1-11, I deleted the imports that were triggering the warnings. Note: If we need a particular import in the future, we can import what we need when we are ready to implement. I deleted the push and location consts that were not being used on line 14.
On line 15 there was a state variable and its update function that was declared. The state variable "rwd" was being used throughout the codebase but the update function, setsRwd, was not being used. The individual who coded this component was trying to directly assign values to the properties of the state variable rather than use the update function to update those values properly. It didn't make sense when I saw this. In any case, I deleted the direct assignments on #20,#22,#24,#34#,36,and #38. I then made a call to the update function, setsRwd, and passed the values from props to the individual properties to update the state variable. I made a call on #25-29 and #39-43.
I understood what their intention was but the way the individual implemented wasn't correct. With setsRwd implemented, the warning was resolved.
Trello card: https://trello.com/c/0PLOlsOR/603-defined-but-never-used-f

PR submission walkthrough: https://drive.google.com/file/d/1Bu4ilCzA0krvrbMkG0IxlG4RgR_L3Qni/view?usp=sharing

Apologies to the reviewers. Qirhi you're correct about this PR. I've been a little bit obsessive about clearing out the warnings that I think I did too much for this PR. I promise that the next one isn't going to be as heavy.


Don't Merge! PR real time test for target branch full build

Docs Build status updates of commit 3d2f3e8:
:clock10: Full build: the average full build time is 5 min(s) 59 sec(s), this is based on the last 576 build(s) for this repository.

Docs Build status updates of commit 3d2f3e8:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/manage-azure-subscriptions-azure-cli.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

docs-ref-conceptual/manage-azure-subscriptions-azure-cli.md

[Warning] The call to the validation service timed out and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or continue to see this message, file an issue via https://SiteHelp. See https://aka.ms/validation-timeout

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


"Tag-level security"

Where is the section mentioned in this quote? I don't see anything like that on the NH security page, and search doesn't turn up a hit in any Azure docs.
> Since apps can be hacked, securing the registration to specific tags requires extra care, as explained in the section “Tag-level security.”
Page I checked
https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-security

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1fe12c8b-5f7b-be6f-9db0-1009a27ceef8
Version Independent ID: 5bb28d30-3240-7354-9f58-e9e51da7f3ae
Content: Registration Management
Content Source: articles/notification-hubs/notification-hubs-push-notification-registration-management.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@dcbrown16 , Thanks for raising the issue. We will investigate and update you.

@dcbrown16 Thank you for pointing this out! I'm not sure of what happened here, but for now I will link to the Security article. This should be live after 3 PM today PDT. Thanks again for the contribution! #please-close

@dcbrown16 , I spoke with @sethmanheim who is content write for this document. We have agreed to make the changes. Thanks for pointing this out.

Thanks everyone :)


Write heartbeat thread output to safe crash log

PR Description
https://github.com/RelationalAI/julia/pull/140 added the --safe-crash-log-file command line argument. When this is specified, and when in signal handler context, jl_safe_printf additionally writes whatever it is printing to the file in JSON format.
With this PR, jl_safe_printf writes to the file in JSON format from the heartbeat thread's context also.
This PR also refactors the JSON printing function to use a single write call rather than multiple, to reduce the possibility of output from multiple threads being interleaved.
Checklist
Requirements for merging:

[ ] I have opened an issue or PR upstream on JuliaLang/julia: <link to JuliaLang/julia>
[X] I have removed the port-to-* labels that don't apply.
[X] I have opened a PR on raicode to test these changes: https://github.com/RelationalAI/raicode/pull/19710

Improved the "JSONification" implementation based on @NHDaly's comments.
My first stab at this was to use alloca for a sufficiently large buffer, but that didn't work well. I then moved to using a large but fixed-size buffer and hoping it was big enough -- terrible approach. But I didn't want to add the overhead of a malloc and a free for every call, so I'm now following Nathan's suggestion of truncating the message if it is too big for the fixed-size buffer. I've also updated the buffer math to accommodate the JSON preamble, etc.

I've tested this locally, starting Julia with --safe-crash-log-file:

Sending a signal: the output is correctly duplicated into the safe crash log file as before.
Starting the heartbeat mechanism and forcing it to timeout: the heartbeat loss messages and the task backtraces are correctly duplicated into the safe crash log file.

So we're still going to get one json message per line in the safe printf in the julia task stacktraces? I was incorrectly believing this PR would also be combining the whole report into one json message, which would be nicer to consume, but I guess would be annoying to implement.

Yes, it's one JSON message per line. To do what you're thinking would require changing how jl_safe_printf is used in the stack trace collection code and I think that would be a lot more complicated.


Add tests for process-handlers.ts file

Background:
Currently we're missing tests for process-handlers.ts file.
Task Details:

please add some would to cover process-handlers.ts file.

Picking Up This Issue:

If you'd like to work on this, please comment "picking this up" below, and I'll assign the issue to you

Questions:

If you need assistance or clarification, feel free to comment below.
Feeling overwhelmed? Join our #hack-together channel and collaborate with a buddy.
New to open-source? Check out our Hacktober #getting-started channel.
Leaderboard: Check your ranking after finishing this task.

Resources:

Creating a Pull Request: If you're new to GitHub and unsure how to create a pull request, follow this step-by-step guide.

Remember, communication is key! If you have any questions or face any challenges, we're here to help so please don't hesitate to reach out.
Good Luck! 🍁

Linking related test issues https://github.com/TBD54566975/dwn-server/issues/50 & https://github.com/TBD54566975/dwn-server/issues/49

"picking this up"

picking this up

@captain-Akshay Yay another issue 🥳!
I'd also like to note that Hacktoberfest officially kicks off on October 1st. Contributions made before the event may not be eligible for the challenge. However, feel free to start working on it, but I'd recommend holding off on submitting your PR until the event begins.

to be eligible for Hacktoberfest's official prizes make sure you're registered, registration is now OPEN.

@VarnikaB Hey, thanks for your enthusiasm to contribute. 😊 Someone got in just a bit ahead of you on this issue, but don't worry! We have other open Hacktoberfest tagged issues that you might find interesting.

developer.tbd.website
web5-js
dwn-server
dwn-sdk-js

Also, we'll be adding more issues throughout the month of October, so there will be plenty of opportunities to jump in. If for any reason the current assignee can't proceed with this one, I'll definitely keep you both in mind and reach out. keep an eye on our events-and-updates channel in discord. Thanks for spending Hacktoberfest with us! 🍁

@captain-Akshay Hey, how are things going with this issue? Is this something you still want to work on?


Add clusterctl labels to CRDs to support clusterctl move

Towards https://github.com/giantswarm/giantswarm/issues/23855

Tested with CAPG.

I'll let you release this first before I release this one to upgrade CAPI.


Use Knuth's Algorithm D for 512-bit division

@ozie777 thanks for the review. What are your opinions? Have you reviewed similar numerically-intensive code before?

Sounds good


File I/O doesn't work inside a sub-module (-mexec-module=reactor)

I've been using MULTI_MODULE support and it appears for whatever reason file I/O no longer works when setting a wasm module with the following:
target_link_options(file PRIVATE -mexec-model=reactor)
I need to be able to create sub-modules and it seems I'm only successful with -mexec-model=reactor. If I don't use that flag I get this this when trying to load as a sub-module "WASM module load failed: a command (with _start function) can not be a sub-module".

May I take a look at the source code?

Actually basic I/O doesn't work at all if you use -mexec-module=reactor
    add_executable(file file.cpp)     target_link_options(file PRIVATE -mexec-model=reactor)
`
#include
#include
#include
#include <unistd.h>
#include <fcntl.h>
#include
extern "C" {
attribute((export_name("read_file"))) size_t read_file(const char *path, char *buf, int bufSize) {
printf("read_file: path=%s, bufSize=%d\n", path, bufSize);
auto in = open(path, O_RDONLY);
printf("read_file: open for path %s, errno=%d\n", path, errno);
if(in == -1){
fprintf(stderr, "read_file: open failed for path %s, errno=%d\n", path, errno);
return 0;
}
auto bytesRead = read(in, buf, bufSize);
close(in);
return bytesRead;
}
attribute((export_name("write_file"))) int write_file(char *data, int dataSize, char *path) {
printf("write_file: called for path %s data size=%d\n", path, dataSize);
auto fd = open(path, O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR);
printf("write_file: open for path %s, fd=%d, errno=%d\n", path, fd, errno);
if(fd == -1){
    fprintf(stderr, "write_file: open failed for path %s, err=%s, errno=%d\n", path, strerror(errno), errno);
    return 0;
}
auto bytesWritten = write(fd, data, dataSize);
printf("bytes written to path %s=%ldl bytes\n", path, bytesWritten);
close(fd);
return bytesWritten;

}
}
int main(int argc, char *argv[]) {
return 0;
}
`

Nice catch. It looks like an issue. We will track in #1814

Fixed in #1816.


Fix timezone conversion.

Fixes #24.
Commit timezone is kept, and then displayed to the user instead of UTC. I'm not opposed to displaying UTC but it should at least have a 'Z' suffix so that it's clear.
Travis timestamp is parsed as UTC and then compared with the commit datetime, since this is less error-prone: the previous comparison used strings, but the RHS had a space instead of 'T' between the date and time, causing it to yield an incorrect result.
Note: the utc object is used from git, since datetime.timezone.utc is Python 3 only.

Does this fix #24?

Yes

Codecov Report

Merging #25 into master will increase coverage by 0.2%.
The diff coverage is 33.33%.

@@           Coverage Diff            @@
##           master     #25     +/-   ##
========================================
+ Coverage    40.5%   40.7%   +0.2%
========================================
  Files           1       1
  Lines         200     199      -1
========================================
  Hits           81      81
+ Misses        119     118      -1

Impacted Files
Coverage Δ

trytravis.py
40.7% <33.33%> (+0.2%)
:arrow_up:

Continue to review full report at Codecov.

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

Sounds good to me, once tests pass I'll merge.

Thanks! :tada:


Add posibility to install go from source

Mainly added to install go on an arm machine.

Thanks! I'll merge it soon.


Introduce save/restore emulator state snapshots instead of the InitialChainState param

Area
[O] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[X] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[O] Marlowe Related to Marlowe
[O] Other Any other topic (Playgrounds, etc.)
Describe the feature you'd like
Introduce save/restore emulator state snapshots instead of the InitialChainState param.
When calling runEmulatorTrace, the user is expected to supply InitialChainState in EmulatorConfig. It is defined as:
type InitialChainState = Either InitialDistribution Block

where InitialDistribution is a synonym for Map Wallet Value. So the InitialChainState is basically serving as a genesis block for each EmulatorTrace run. It would be useful to be able to prerun some of the chain operations and supply a snapshot of EmulatorTrace to runEmulatorTrace instead of a single genesis block.
Prerunning parts of the operations is also required to be able to acquire "runtime" arguments and feed them as contract parameters, if necessary. Consider such an example: Contract B is expecting value returned by a Contract A as a parameter. The value is depending on a runtime argument such as UTxO. There is no easy/elegant way to acquire the value before running the EmulatorTrace. If one is using the Plutus.Contract.Test.ContractModel framework, it severely hurts the ability to run the tests:
handleSpec :: [ContractInstanceSpec MyModel]
handleSpec =
  [ ContractInstanceSpec (MyActionKeyA w1) w1 contractA ] ++
  [ ContractInstanceSpec (MyActionKeyB w) w (contractB aValue) | w <- knownWallets ] -- how to get the `aValue`?

Lack of the feature also slows down the testing performance, as one has to rerun in every test the same boilerplate initial operations that usually are irrelevant to a specific test suite.
Describe alternatives you've considered
In the plutus-use-cases code, there is  function, which basically preruns the first contract to acquire its state token, which later is given to the contract depending on it (cf. ). I have used the same trick (almost the same code) to acquire value from Contract A. The value then can be passed to Contract B:
handleSpec :: [ContractInstanceSpec MyModel]
handleSpec =
  let aValue = getValueFromA in
    [ ContractInstanceSpec (MyActionKeyB w) w (contractB aValue) | w <- knownWallets ]

This is all happening before running tests. Now, the problem is that we are assuming that the aValue will be a correct one because both prerun and the tests themselves would be run sharing the same genesis block. This assumption will fall apart if someone e.g. changes the order of contracts to be run in the "Initial Action".

That's a good idea, and we have been looking for a solution to the "runtime arguments" problem for a while. If you want to work on this it would be best to open a PR early so that we can talk about the design.


ValorantCC Isn't opening

I've installed the .net thingy and valorantcc but when i open valorant cc it comes with this

I've installed the .net thingy and valorantcc but when i open valorant cc it comes with this

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.2-windows-x64-installer

dotnet 6.0.8 didn't work for me, but 6.0.2 worked flawlessly


[ALLUXIO-2629] add final to PlainSaslServerCallbackHandlerTest

https://alluxio.atlassian.net/browse/ALLUXIO-2629
add final keyword to PlainSaslServerCallbackHandlerTest class

Merged build finished. Test PASSed.

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


Multiple api packages?

Add support for multiple api packages?
Reason: https://github.com/GTNewHorizons/BetterQuesting

Resolved with addon.gradle. Must be revisited when adding publish to maven


Add a script that enables running azurectl commands from the git project dir.

sorry guys that already exists.
look at
bin/azurectl
I'm going to revert it

On 10/02/2015 04:51 AM, Marcus Schäfer wrote:

sorry guys that already exists.
look at
bin/azurectl
I'm going to revert it

Thanks for catching that, I forgot about bin/azurectl. There was this
little voice in my head say "this is already done" but I couldn't put my
finger on it. :(

Reply to this email directly or view it on GitHub:
https://github.com/SUSE/azurectl/pull/56#issuecomment-144962345

--
Robert Schweikert                   MAY THE SOURCE BE WITH YOU
Public Cloud Architect                         LINUX
<EMAIL_ADDRESS>IRC: robjo

bin/azurectl doesn't work for me; presumably because of the path. If it did, I wouldn't add a script referencing it.


OpenLdap - There is no distinction in error messages between access denied or invalid password.

**Rancher versions: Build from master
Steps to Reproduce:
Enable openLDAP and set site access to "Allow any valid Users".
Try to log in with invalid password.
User is presented with following error message:
"Logging in failed: Your account may not be authorized to log in."
This is the same message that is presented when a user who has no access to rancher server tries to login.

Tested with latest build from master:
User is presented the following message when user (who has access / no access to rancher server) attempts to log in with invalid password.
Logging in failed: Check credentials, or your account may not be authorized to log in.
When user who does not have access to rancher server tries to log in with valid credentials , he is presented with following message:
Permission denied


Priority Selection On Filtered Connector Missing

The priority selection on the filtered cable connector is absent on Tom's Storage 1.18.2-1.4.4.
https://github.com/tom5454/Toms-Storage/issues/205 https://github.com/tom5454/Toms-Storage/issues/300 https://github.com/tom5454/Toms-Storage/issues/291 and https://github.com/tom5454/Toms-Storage/issues/285 indicate that this should be an option.

For this test, I am using the Forge 40.2.14 on Minecraft 1.18.2 with only Tom's Storage installed.

That's a 1.19+ feature, it doesn't exist on 1.18.2.


Watcher in JSON

Hi,
I am using formly that loads a JSON file from the server, but how can i use the watcher functionality?
Tried this:
            {
                "key": "FirstName",
                "type": "horizontalInput",
                "templateOptions": {
                    "label": "First name",
                    "required": true
                },
                "watcher": {
                    "listener": "function(field, newValue, oldValue, scope, stopWatching) { if(newValue) { console.log('String Expression: '+ newValue); } }"
                }
            }

but that didn't work. How can i get this to work?

Yeah, so if you're loading it from a server then you'll have to use the string version for your watcher and other expressions. In-lining functions as strings will not work (and would be a very bad idea). Here's an example that may be helpful to you: http://angular-formly.com/#/example/other/json-powered
P.S. I recommend avoiding using watcher if you can. It's better to try to use expressionProperties. Mostly from a performance standpoint.

Let me know if that is enough to get you going.

Thank you Kent. Can i use expressionProperties to filter a dropdown depending on what the user types in the FirstName?

Absolutely. Depending on the dropdown's templateOptions, you might do something like this: http://angular-formly.com/#/example/other/filter-select

Perfect, thank you very much.


Add possibility to add custom validation function for workload

Adds possibility to add custom validator for workload.
dpbench search for [workload name]_validate.py and for validate function. If not found uses default_validate.
Fix relative_error for case of reference data filled filled with zeros.
Fix valid flag not to reset for each output.

Good changes! I wanted to leave few comments, but ended up writing code. Sorry for that. Could you just review changes I've add in separate commit and if you like it, please squash them into one commit.
Idea behind changes was to separate configuration set up and use of it. As a bonus we get more compact code, more modular code and it gets more flexible control over validation functions, e.g:

We can provide multiple validation functions and use can chose between them
User can use validation functions from 3rd party libraries


[Build] update dependencies

Problem (Why?)
loosen the version of torch dependency to 1.10
Solution (What/How?)

[x] torch to ^1.10

Other changes (bug fixes, small refactors)

[x] Makefile, init recipe (add quite option to pip)

Notes
version to 1.1.4

Codecov Report

Merging #68 (db834c8) into main (959a944) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   95.90%   95.90%
=======================================
  Files          28       28
  Lines        2051     2051
=======================================
  Hits         1967     1967
  Misses         84       84

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add format and clippy checks to continuous integration

Pull Request Template
Checklist

[x] Confirm that run-checks script has been executed.

Changes
This PR:

Adds format and clippy checks on Linux directly on CI and uses actions to better show in PR clippy warnings
Adds ci option to scripts not to run format and clippy checks on Linux when scripts are used on CI
Updates binaries and shell scripts

TODO

[x] Find a better action to show formatting errors --> Any supported and easy-to-use action has been found to show format errors as PR annotations or comments
[ ] Write INFRASTRUCTURE.md documentation

@antimora and @nathanielsimard I think I've finished, so this PR is read to be reviewed

The goal of this PR consists of providing a way to better visualize clippy lints as annotations inside each PR without having to look for the problems within CI output. It's a PR oriented to help newcomers in detecting clippy lints in a simpler way since they are shown directly in their PR. But if there is no agreement on this aspect, this PR does not make sense at all. Separating clippy and format for optimizations reasons is quite useless since they are not computational heavy at all. I had already described this part in the #552
Providing a better clippy and `format output directly in the script is just a waste of time, we can simply use the output provided by the two binaries in that case.
Personally I think CI should be superior than scripts because a CI is the last  "judge" to evaluate a PR since:

Anyone can see the outcome, so it's not important if a developer has run locally the scripts. We can catch the issues related to the considered PR immediately.
You can have comments in it that helps you to fix some aspects such as code coverage or clippy lints annotations
You cannot do some things locally with scripts without forcing a developer to set his/her own machine according to our specifications. CI allows a more degree of freedom.

But I also understand that an action can be quickly unmaintained and not conform to the new GitHub Actions APIs. So use only the necessary ones can be a valid point.
Unfortunately I do not see a tradeoff for this PR, we can leave as it is now and create a new PR for the INFRASTRUCTURE books.

I couldn't understand initially what better output you were telling us about. So I dug in briefly about this clippy action. It appears from my limited research this action uses clippy and forwards output (or formats) to reviewdog service (that is why it requires git hub token in the code), which actually talks to the originating PR via comments. So it's clippy + clippy-action +  reviewdog.
Potentially we could enhance our PR workflow with the automated review tools like reviewdog, and I am open to this. I know little about current trend, so it'd be interesting to explore.
With this new information, I am not exact sure why you had to modify the current run-checks if you added action/clippy. Does the action take the output?

Waiting upstream https://github.com/giraffate/clippy-action/issues/82

@antimora
I have found another way to show clippy lints in PR, simpler than before, so this PR is no more blocked

@antimora and @nathanielsimard
I rebased this PR on top of main


Attribute differences

This is report is  an observation about the difference between the CUPS and cups-filters PPD generators rather than one about a bug in cupsfilters.
I have been working with a user at
https://ubuntuforums.org/showthread.php?t=2429221.
The most relevant recent post is at
https://ubuntuforums.org/showthread.php?t=2429221&page=2&p=13902908#post13902908
The wf1 queue was set up with the driverless model. The wf2 queue used the everywhere model.
I understand fully that the cupsfilters PPD generator is intended to be in sync with the CUPs one, while diverging from it when it sees it as necessary. However, why the differences in the cupsPrintQuality/Print Quality and PageSize/Media Size attributes (particularly in regard to borderless)?
Explaining this to a user is not the easiest of tasks.
--
Brian.

https://ubuntuforums.org/showthread.php?t=2429221&page=3&#23
Regards,
Brian.

This printer (EPSON WF-2630) seems to have the same problem as the Epson ET-7700 of Pull request #168, claiming to accept PWG Raster input but actually not printing it.
For some reason CUPS creates a PPD where the printer gets Apple Raster whereas the cups-filters PPD lets PWG Raster go to the printer.

The fact that some printers report to support PWG Raster but actually printing in this format does not work caused also the CUPS issue apple/cups#5238. Here a Canon Pixma Pro 10 showed this problem. So an actual fix for at least getting your printer working again is to modify the PPD generator to prioritize Apple Raster against PWG Raster if both are supported, as the fix of the CUPS issue does with the PPD generator in CUPS.
As a workaround until we have actually done this in cups-filters, you simply proceed as described in this comment in the CUPS issue. This will at least get you back printing.
The differences in the choices of the options are an independent issue which we will look into later.

I have fixed the Apple Raster/PWG Raster problrm now, following CUPS in preferring Apple Raster if both are supported, commit 80f87b0a.

Discrepancies in the option choices:

CUPS only gives standard page sizes, cups-filters has borderless sizes added.
CUPS has "draft" quality added, cups-filters has only "normal"
cups-filters gives "4" and not "normal" as print quality choice name.

The discrepancy in the page sizes is already solved. Current cups-filters is correct, listing also borderless sizes, CUPS has it correct at least from 2.3.x on, as I have tested with the 2.2.12 of Ubuntu 19.10 and also tested with an LD_PRELOAD of the libcups of 2.3.x from the CUPS GitHub. The latter also shows the borderless sizes, the former not.
You can easily see in the output of ipptool that a printer supports borderless printing, even if the "media-col-database" attribute is not listed. If you get margin info like
        media-left-margin-supported (1setOf integer) = 0,300
        media-right-margin-supported (1setOf integer) = 0,300
        media-top-margin-supported (1setOf integer) = 0,300
        media-bottom-margin-supported (1setOf integer) = 0,300

having zero and a non-zero value for each nargin, it means that the printer has a standard mode and a borderless mode and so at least for some page sizes borderless printing is supported. The actual page sizes which have a borderless version are found via the "media-col-database".

The fact that CUPS adds a "draft" print quality but cups-filters not is that CUPS not only adds "draft" if it is listed in the "print-quality-supported" attribute but also if the lowest resolution is even. in the latter case the "draft" mode is simply using half the lowest resolution. I am in doubt whether this always actually works and therefore I do not overtake it into cups-filters.

I have fixed the choice names of the "cupsPrintQuality" option now to be "Draft",  "Normal",  and "High", as CUPS also uses (commit 47b9adab6).
So now all differences should be fixed or explained and you should be able to print. So I am closing this issue.


[DPE-3501] make sure restoration works correct on all the shards

Issue
Solution

solved with #373


wifi not connected. waiting...

I have some questions for you
Run active_ AP, the AP named myssid cannot be found, the computer and mobile phone cannot be scanned, and then run
active_ STA, as shown below:
I (940) Active CSI collection (Station): connect to ap SSID:myssid password:mypassword
CSI will not be collected. Check idf.py menuconfig  # > ESP32 CSI Tool Config to enable CSIwifi not connected. waiting...
wifi not connected. waiting...
wifi not connected. waiting...
I (2990) Active CSI collection (Station): Retry connecting to the AP
wifi not connected. waiting...
wifi not connected. waiting..
idf：v4.3

Were there any steps that you took to solve this issue? It might help someone else in the future if you share your debugging steps and your solution. Thanks.

I wrong with some sitting of menuconfig


Add 'openddl-parser' package

github: https://github.com/kimkulling/openddl-parser
hunterized: https://github.com/hunter-packages/openddl-parser

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35010309-add-openddl-parser-package?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.549

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.561
https://travis-ci.org/ingenue/hunter/builds/138705632

Branch develop, binaries uploaded, new wiki page: https://github.com/ruslo/hunter/wiki/pkg.openddlparser


Create new dashboard for github project health and activity from bitergia

Integrate with bitergia for looking at github software contributions.


Create ability to define additional filters per stream in the HLSPlaylistExporter

As specified in title/commit message I needed the ability to add filters per format (scale/framerate).
For this purpose I added the option to add (multiple) filters to the addFormat function (these per stream filters work exactly the same as the addFilter method on the media object).
As more people might be interested I submit this pull request for you to review and/or merge (if wanted/needed).

Thanks for the PR! I like the feature but this would be a breaking change. I'll try to find some time to refactor this into a non-breaking change and then add it as a feature.

As of version 1.2.0 the addFormat method of the HLS exporter takes an optional second parameter which can be a callback method. This allows you to add different filters per format:
$lowBitrate = (new X264)->setKiloBitrate(250);
$highBitrate = (new X264)->setKiloBitrate(1000);

FFMpeg::open('steve_howe.mp4')
    ->exportForHLS()
    ->addFormat($lowBitrate, function($media) {
        $media->addFilter(function ($filters) {
            $filters->resize(new \FFMpeg\Coordinate\Dimension(640, 480));
        });
    })
    ->addFormat($highBitrate, function($media) {
        $media->addFilter(function ($filters) {
            $filters->resize(new \FFMpeg\Coordinate\Dimension(1280, 960));
        });
    })
    ->save('adaptive_steve.m3u8');


updated messages for french locale

@monlouisj I've merged. It's still missing draft-07 "if" keyword translation and also I think faux or even "false" can be better than incorrect here: https://github.com/epoberezkin/ajv-i18n/pull/81/files#diff-83a6b665cb4d1d32513534b482e2893aR50

And thank you :)

I think faux or even "false" can be better than incorrect here

I agree, "false" would be more precise than "incorrect".


[cli] add --sqlite param

There is a SQLiteDialect but it wasn't available as a cli parameter.
I'm running the following query cargo run --features json_example --example cli /tmp/some.sql --sqlite
on main:
david@hydra sqlparser-rs % cargo run --features json_example --example cli /tmp/some.sql --sqlite
   Compiling sqlparser v0.37.0 (/Users/david/code/sqlparser-rs)
    Finished dev [unoptimized + debuginfo] target(s) in 0.53s
     Running `target/debug/examples/cli /tmp/some.sql --sqlite`
thread 'main' panicked at 'Unexpected parameter: --sqlite', examples/cli.rs:51:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

on ddol--cli-add-sqlite:
david@hydra sqlparser-rs % cargo run --features json_example --example cli /tmp/some.sql --sqlite
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/examples/cli /tmp/some.sql --sqlite`
Parsing from file '/tmp/some.sql' using SQLiteDialect
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] Parsing sql 'select 1;'...
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] parsing expr
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] prefix: Value(Number("1", false))
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] get_next_precedence() TokenWithLocation { token: SemiColon, location: Location { line: 0, column: 0 } }
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] 0: ; 1: EOF 2: EOF
2023-08-25T03:58:26.462Z DEBUG [sqlparser::parser] next precedence: 0
Round-trip:
'SELECT 1'
Serialized as JSON:
[
  {
    "Query": {
      "with": null,
      "body": {
        "Select": {
          "distinct": null,
          "top": null,
          "projection": [
            {
              "UnnamedExpr": {
                "Value": {
                  "Number": [
                    "1",
                    false
                  ]
                }
              }
            }
          ],
          "into": null,
          "from": [],
          "lateral_views": [],
          "selection": null,
          "group_by": [],
          "cluster_by": [],
          "distribute_by": [],
          "sort_by": [],
          "having": null,
          "named_window": [],
          "qualify": null
        }
      },
      "order_by": [],
      "limit": null,
      "offset": null,
      "fetch": null,
      "locks": []
    }
  }
]
david@hydra sqlparser-rs %

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
56 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.1%) to 87.222%

Files with Coverage Reduction
New Missed Lines
%

src/ast/mod.rs
1
78.74%

tests/sqlparser_postgres.rs
1
98.0%

tests/sqlparser_mysql.rs
2
99.35%

tests/sqlparser_common.rs
16
96.79%

src/lib.rs
36
12.03%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
16198

Relevant Lines:
18571

💛  - Coveralls

I believe the clippy failure is due to a newer version of clippy and not anything related to this PR. I will fix it separately

Clippy fixes in https://github.com/sqlparser-rs/sqlparser-rs/pull/957
Thanks again for the contribution @ddol


Missing info about cache in doc

Upgraded to latest 0.6 and failing. Had to add nettrine/cache ext dependency
   Nette\DI\ServiceCreationException: Service 'dbal.configuration' (type of Doctrine\DBAL\Configuration): Service of type 'Doctrine\Common\Cache\Cache' not found.

Ok, this first touch was in testcase. But now i tested it on real app and had to import nettrine/cache extension to make it work. If it is required, it should be mentioned in doc

Fixed by https://github.com/nettrine/dbal/commit/0545b8b390350d57508a79a71e75d566959b8291

👍


fix: miscast of List to List?

Since stack is taking a non-null list of widgets. the provided child
Widget cannot be null
This is crashing my app. while running in full sound null safety

+1 Please merge

Thank you @abhinandval

please do a releases so i can replace the git version with pub


Some client issues/improvements

I've been writing things down as I notice them. I'm just going to throw them in one issue instead of making a bunch. These are all related to the client/simple browser...

[x] no inline code syntax highlighting
[ ] extra dash in titles
[x] test text get cut off on the right
[ ] could maybe use some sort of loader while the packages are being installed

I will leave the dash for you to decide on, because, the only reason it is there is to allow titles like:

Could you explain what sort of loader you imagine? As in, where and when does this show?

Not really sure on the loader, but when I run course, the simple browser opens with a white screen while everything installs - which can take a decent amount of time. I dunno, I would have to play with - could we somehow load a static index.html file with a css loader until the server starts? Then redirect to that or something. That's all that comes to mind at the moment.


Ultisnips stopped working

I do not remember changing anything in my config, but ultisnips just wont show any suggestions anymore.
Is it working ok for you guys?
I have all the basic setup done, nothing too fancy - but cmp just wont show any entry form ultisnips.  The only error I ever get - is if I try to edit snipped file and on save I get this:

Not sure if this is because I'm on daily nvim build?
UltisnipsEdit works ok though, so Ultisnip seems loaded ok. .

never mind.   Moving comp ultisnips outside of lay load fixed the issue.


Automate breaking large batches into smaller groups

For lage batches of input, provide the capability to break these into batches that respect the service's request size limitations.
Provide knobs for users to tune throughput vs. response time.  Add to ClientOptions?

Just curious, @kristapratico were you looking into this?

I dont believe we will be looking into this in library side.


Question

How does the font work?
I had font 4 in my cfg but it looked different the next day. And i had to use font 5 for the one i liked.

It uses vgui fonts - to view complete list type vgui_spew_fonts in console.

alright thanks


Update to Bot API 5.4

Updates grammY to Bot API 5.4.
Also updates the Deno std lib to 110. If someone knows where iter is in more recent versions, please let me know and we can update the dep to 113.

https://github.com/denoland/deno_std/pull/813 renamed iter to iterateReader.


Determine whether the task scheduler is execute by user or execute by schedule

I would like to know whether it is possible to determine whether there's a way to know the task scheduler is being triggered by schedule or triggered by user other than referring to the task's history?
Originally posted: 2016-10-30T08:56:15

Not that I'm aware of. The same engine launches both with the same process information. The only place I've seen any record of a User launched task is in the history.
Originally posted: 2016-10-31T08:05:13


asPointwise with n_jobs>1 does not progress

(This was tested after fixing another issue locally https://github.com/scikit-learn-contrib/scikit-dimension/issues/17)
https://github.com/scikit-learn-contrib/scikit-dimension/blob/bde433aba866eafdf4de3bf2c7b226f68a7dd1cf/skdim/_commonfuncs.py#L105
asPointwise works as intended when n_jobs=1. However, in my experience when n_jobs>1 the async call does not complete.
I can recommend using the joblib library instead of multiprocessing, for example:
from joblib import delayed, Parallel
if n_jobs > 1:
    with Parallel(n_jobs=n_jobs) as parallel:
        def fit_estimator(class_instance, data, idx):
            return class_instance.fit(data[idx, :]).dimension_
        results = parallel(
            delayed(fit_estimator)(
                class_instance, data, idx
            ) for idx in knn
        )
    return np.array(results)

Thanks, really appreciate you bringing up these issues and possible fix.
Would you have an example to reproduce this ? For example this completes with no problem for me:
import numpy as np
import skdim
X = np.random.random((1000, 10))
skdim.id.lPCA().fit_pw(X,n_jobs=4).dimension_pw_

Oh I was about to explain more but I see your edit. I was specifically using the ESS estimator which does not have a built-in fit_pw function, and asPointwise appeared to be the intended method for pointwise estimation of local intrinsic dimension.
import numpy as np
import skdim
import multiprocessing as mp

# Re-defining this function to fix bug in Issue 17
def asPointwise(data, class_instance, precomputed_knn=None, n_neighbors=100, n_jobs=1):
    """Use a global estimator as a pointwise one by creating kNN neighborhoods"""
    if precomputed_knn is not None:
        knn = precomputed_knn
    else:
        _, knn = skdim.get_nn(data, k=n_neighbors, n_jobs=n_jobs)

    if n_jobs > 1:
        with mp.Pool(n_jobs) as pool:
            # Asynchronously apply the `fit` function to each data point and collect the results
            results = [pool.apply_async(class_instance.fit, (data[i, :],)) for i in knn]
            # Retrieve the computed dimensions
        return np.array([r.get().dimension_ for r in results])
    else:
        return np.array([class_instance.fit(data[i, :]).dimension_ for i in knn])

X = np.random.random((100, 10))

# estimator = skdim.id.lPCA() # GlobalEstimator
estimator = skdim.id.ESS() # LocalEstimator

# n_jobs = 1 # single process
n_jobs = 2 # multi process

if isinstance(estimator, skdim._commonfuncs.LocalEstimator):
    lid = asPointwise(X, estimator, n_neighbors=10, n_jobs=n_jobs)
elif isinstance(estimator, skdim._commonfuncs.GlobalEstimator):
    lid = estimator.fit_pw(X, n_neighbors=10, n_jobs=n_jobs).dimension_pw_

print(lid)

This code completes quickly for LPCA with n_jobs=1 or 2, and for [ESS, MADA, MLE, MOM, TLE] with n_jobs=1.
It completely hangs for [ESS, MADA, MLE, MOM, TLE] with n_jobs=2. These are the GlobalEstimator classes.

Thanks for looking into this, and for the great library!
I had a question about terminology. Estimators like LPCA inherit from GlobalEstimator, and have the fit_pw function for pointwise (local) dimension estimation. Estimators like ESS inherit from LocalEstimator, and do not have the fit_pw function implemented, only fit which is for the whole dataset.
Based on these descriptions, it seems like the class names of GlobalEstimator and LocalEstimator are reversed. Local estimators should be the ones that operate pointwise, while global estimators only act on the whole dataset by default. Did you have a different interpretation?

You can use ESS pointwise like so:
import numpy as np import skdim X = np.random.random((1000, 10)) skdim.id.ESS().fit(X,n_jobs=4).dimension_pw_
LocalEstimator class is used for estimators that already computes and return ID estimates for each point neighborhood. So in principle there is no need for a fit_pw method - which would effectively treat each neighborhood as an entire dataset.
For lPCA I made an exception - most people are used to running PCA on the entire dataset to estimate ID,  so this is the default when using .fit() to prevent confusion. Accordingly it inherits from GlobalEstimator whose .fit method runs an estimator on the entire dataset.
However paper references associated with this class rather use local PCA estimates and aggregate them to obtain global ID. Indeed ID estimation using PCA applied to an entire dataset will fail for non-linear data. So conceptually, PCA is more of a local ID estimator that tries to obtain ID of the manifold tangent space. Hence the name lPCA (local PCA) for the class to point this out while keeping default use global.
I agree the terminology is very confusing so suggestions are very welcome. Overall I am trying to keep users from inadequately using estimators.  .fit()  always expects to receive an entire (possibly non-linear) dataset as input whether the estimator inherits from LocalEstimator  or GlobalEstimator. This is not the case in original R ESS implementation where ESS expects a single neighborhood as input. In Python this would be equivalent to calling ESS().fit_once

I see, that make much more sense and is simpler. I understand why Local and Global are used no. What threw me off was first seeing lPCA as a "global" estimator, since I think of using it in the local way, but it happens to be the exception to your naming scheme.
Here's a suggestion then - in the README you use DANCo as an example of a global estimator (fine), and lPCA as an example of a local estimator. Then when I look up their implementation I see they both inherit from GlobalEstimator. That's unexpected! Why not replace lPCA with ESS or another LocalEstimator in the first example that most users will see?

I'll put this one my to do list: the lPCA exception should probably be removed and the docs provide a clear example with a lPCA.fit_once method to apply PCA "as usual" a single time on the whole dataset

Can you give me access rights to make branches and push? I will make a PR switching this function joblib, and then another for adding parallelism internally for estimators like ESS.

I think I need to request for you to be added to the scikit-learn-contrib org. I don't see option to add you directly myself

Actually you should be able to PR even without being member

No, I have no option to make a PR or even a new branch on this repo. I tried pushing a branch directly but I get a permissions error.

Could you try again following the steps at https://github.com/firstcontributions/first-contributions ?

Closed by PR https://github.com/scikit-learn-contrib/scikit-dimension/pull/23


Loading indicator on account creation

Issue link
https://github.com/tasitlabs/tasit/issues/358

Auto-close the issue?

Closes #358
Types of changes

New feature (non-breaking change that adds functionality)
Notes
This PR closes issue #358 listed on Tasit's kanban. It introduces a better loading experience on account creation state.

@pedrobergamini This looks great, thanks!!


Training for wav to midi transcriper

I’m starting an experiment to train the model to converts music audio to MIDI. The approach involves freezing the encoder and continuing training on the decoder. Any suggestions or feedback before I begin?

I’m starting an experiment to train the model to converts music audio to MIDI. The approach involves freezing the encoder and continuing training on the decoder. Any suggestions or feedback before I begin?

The sampling rate of WavTokenizer for both audio and music is relatively low, at only 24k. I am unsure whether this might limit the generation of high-quality MIDI.


fix server_test TestRawDelete1 cannot be passed

kv/server/server_test.go
on test case "TestRawDelete1"
line187: val, err := Get(s, cf, []byte{99})
line188: assert.Equal(t, nil, err)
to
line188: assert.Equal(t, badger.ErrKeyNotFound, err)
Because GetCf try to take a non-existent key,it will return badger.ErrKeyNotFound
So i think its necessary to update its _test.go
ThankYou

please take a look at https://github.com/pingcap-incubator/tinykv/blob/course/kv/storage/storage.go#L18


feat: support configure envoyproxy image from env

When generate manifests, we can specify the envoyproxy image, this is used for release manager/release workflow or end-user to specify the envoyproxy version.
The current envoyproxy image is hardcode and it is the latest dev version of envoyproxy, if the release manager is going to release, he/she will need to change the default dev version to the compatible stable version of envoyproxy:
make generate-manifests IMAGE=envoyproxy/gateway TAG=v0.3.0 PROXY_IMAGE=envoyproxy/envoy:v1.23.3 OUTPUT_DIR=release-artifacts

When make kube-deploy, we can also specify the envoyproxy image to test or dev:
TAG=latest IMAGE=envoyproxy/gateway-dev PROXY_IMAGE=envoyproxy/envoy:v1.23.3 make kube-deploy

Signed-off-by: bitliu<EMAIL_ADDRESS>

@Xunzhuo can you please share motivation behind this ?
If there is enough +1s for this, this should probably be driven from https://github.com/envoyproxy/gateway/blob/89ae35388ec6e0134beb32efbba693d68c685ba8/api/config/v1alpha1/shared_types.go#L22 instead

based on the comments from https://github.com/envoyproxy/gateway/issues/672 it looks like the envoy version needs to be updated in the release branch right before cutting the release.
looks like 1.25 has not been released yet, my suggestion would be to raise a draft PR when it does to proactively catch any issue

my suggestion would be to raise a draft PR when it does to proactively catch any issue
Let's make sure this draft PR


ari 3.0 - SendDTMF needs Options

Options for Before/Between/Duration/After/etc. v2 has SendDTMFToChannelRequest.

Done via af98a69


lxml.etree.ParserError: Document is empty

I made a small script in order to try the scrapping process.
I have a case when If I use extruct as the CLI, I get lots of information about the schema extracted.
extruct [url]
However, if I use  for the same url schema = extruct.extract(html_content, base_url=url) , I get the error "lxml.etree.ParserError: Document is empty"
The url is valid and the content of html_content (response.text) is valid and full.
I tried also with a fresh python environment when I've installed only extruct and I still get the error.
import requests
import sys
import extruct

def get_html(url):
    response = requests.get(url)
    if response.status_code == 200:
        return response.text
    else:
        return None

# Check if URL is provided as a command-line argument
if len(sys.argv) < 2:
    print("Please provide a URL as a command-line argument.")
    sys.exit(1)

url = sys.argv[1]  # Get the URL from the command-line argument
html_content = get_html(url)
if html_content:
    #print(html_content)
    schema = extruct.extract(html_content, base_url=url)
    print(schema)
else:
    print("Failed to retrieve HTML.")

Any insights about why it failed by using the python code ?

I'm facing the same issue for cnn articles (e.g. https://edition.cnn.com/2023/08/09/politics/georgia-medicaid-eligibility-work-requirements/index.html). It seems that lxml.etree.fromstring(resp.text, parser=lxml.html.HTMLParser()) returns None for some reason. Haven't investigated it any further but it seems that this is an issue with the lxml.

I did some more analysis. It seems that for the same article goose3 works well while extruct crashes. Both libraries use lxml. The only difference is in goose3.utils.encoding.smart_str function being applied (https://github.com/goose3/goose3/blob/d3c404a79e0e15b7957355083bd5a7590d4103ba/goose3/parsers.py#L59). I've checked it manually and it seems to do the trick for me.
Additionally, there is a lxml.html.soupparser module that can also be used.
To summarize, either of the two worked for me:
from goose3.utils.encoding import smart_str

html = '...'
extruct.extract(smart_str(html), syntaxes=['json-ld'])

import io
from lxml.html import soupparser

html = '...'
extruct.extract(soupparser.parse(io.StringIO(html)), syntaxes=['json-ld'])

Another option is to parse the HTML on your end and pass an already parsed tree (in lxml.html format) to the extruct library, most syntaxes support that in the last release. For example we're internally using an HTML5 parser https://github.com/kovidgoyal/html5-parser/ passing treebuilder='lxml_html' (happy to share more details), which is more compatible compared to default lxml.html parser.

Hi everyone,
I believe this is fundamentally an encoding issue, as vasniktel suggested. Try to feed extruct directly with bytes instead of (mistakenly) utf-8 decoded strings to prevent it from happening.
Example:
import requests
import extruct

u = "https://edition.cnn.com/2023/08/09/politics/georgia-medicaid-eligibility-work-requirements/index.html"
r = requests.get(u) # note that r.content is a bytes object

# crashes
extruct.extract(r.content.decode("utf-8"))
# works
extruct.extract(r.content)


Detect trying to access non-existent files.

Falco doesn't log access/stat syscalls (https://falco.org/docs/rules/#ignored-system-calls), which means we may miss attempts to search for e.g. .ssh keys or other credentials.
We should try set '-A' as the documentation suggests, or if that causes performance issues (and dropped syscalls again), then we may need to set up fake credentials.

This should be fixed now.


add SAML provider OneLogin + Add vendors: Bridgecrew & Lacework

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

This one also fixes the following error:
Traceback (most recent call last):   File "cloudmapper.py", line 73, in <module>     main()   File "cloudmapper.py", line 67, in main     commands[command].run(arguments)   File "/Users/barak/Documents/dev/cloudmapper/commands/weboftrust.py", line 398, in run     cytoscape_json = weboftrust(args, accounts, config)   File "/Users/barak/Documents/dev/cloudmapper/commands/weboftrust.py", line 302, in weboftrust     get_nodes_and_connections(account, nodes, connections, args)   File "/Users/barak/Documents/dev/cloudmapper/commands/weboftrust.py", line 287, in get_nodes_and_connections     get_iam_trusts(account, nodes, connections, connections_to_get)   File "/Users/barak/Documents/dev/cloudmapper/commands/weboftrust.py", line 184, in get_iam_trusts     raise Exception('Unknown federation provider: {}'.format(principal['Federated']))
In cases where Onelogin is used as a SAML provider

Thanks @schosterbarak !


Optimization: send premultiplied alpha from vertex to fragment shader.

Note that this applies only to the builtin shaders - interface for Kage stays
unchanged for compatibility.
Minor compatibility delta: when interpolating alpha values, previous code has
created nonsense values, such as, when interpolating from
fully-transparent-black (0,0,0,0) to opaque-white (1,1,1,1), something like
half-transparent-grey (0.25,0.25,0.25,0.5) where half-transparent-white
(0.5,0.5,0.5,0.5) is used by the new code.
I assume this is a strict improvement, however this may warrant some testing.
Possible later improvement could be moving the premultiplication from fragment
shader to CPU. Did not do this as it makes the code rather inconsistent of Kage
vs built-in shader usage.
Helps with https://github.com/hajimehoshi/ebiten/issues/1772, achieved 23fps->27fps and 36fps->48fps on a Dell E6500.

Check failures were fun:

Could not connect to azure.archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]

Benchmark results of 01-start-to-hub.dem on Dell E6500 (the underpowered GPU with the large screen, shader exec time bound):

before 352fd76312fab3f11e369cb8ef26af333814c433: 171.7 seconds
before 352fd76312fab3f11e369cb8ef26af333814c433 + this change: 171.6 seconds (yes, basically no change)
main at 352fd76312fab3f11e369cb8ef26af333814c433: 119.3 seconds
main at 352fd76312fab3f11e369cb8ef26af333814c433 + this change:  92.9 seconds (22% faster!)

Why does this change only really take effect with the nearest shader? Because it's really about fillrate - my game runs at 640x360 and has about 2x overdraw at the settings used here, so it renders 461k pixels - however this gets scaled up to 1920x1080 -> 2M pixels. This final render pass really seems to be what matters.

I just found the condition under which a < 0 can break things, and added a comment as well as adapted the check.
The part I missed was that these colors are unpremultiplied, so my arguments failed epically - a sign flips when premultiplying which can wreak havoc.
The proper condition is r >= 0 && g >= 0 && b >= 0 && r <= 1 && g <= 1 && b <= 1 && a >= 0, and the only possible condition that allows even more requires analyzing the vertex colors.
OTOH, if this condition holds, then multiplying this with the vertex colors does not make the vertex colors any more pathological than they already might be, essentially meaning that the clamping can never kick in due to the vertex colors themselves being unpremultiplied too.
Negative matrix colors can combine with negative vertex colors to something positive, which can cause clamping. It might be possible that I actually just need r >= -1, etc. - did not analyze close enough, probably not worthwile.

I'm confused. Why don't we need the condition like r <= a?

Because colors in this layer (atlas.Image) are all unpremultiplied, and they previously got premultiplied in the fragment shader (now will in the vertex shader - this is what I primarily am moving here, as well as making the min() optional).

So a >= 0 and r <= 1 here implies r <= a in the fragment shader.

What about the scale (r, g, b, a) = (0.5, 0.5, 0.5, 0) for the color (1, 1, 1, 1)? Will the result be (0.5, 0.5, 0.5, 0)?
(For min, I want to be flexible about the compatibility, but I'd like to know what is kept and what is not exactly.)

If the scale is (r, g, b, a) = (0.5, 0.5, 0.5, 0), this

now: becomes (0, 0, 0, 0) in the vertex shader, and invariably makes the fully-transparent in the fragment shader
previously: stayed (0.5, 0.5, 0.5, 0) in the vertex shader, got turned into (0, 0, 0, 0) by the fragment shader, and invariably makes the output fully-transparent

This is what is to be expected about the unpremultiplied color (0.5, 0.5, 0.5, 0), which is "fully transparent grey". The fact that it is grey is entirely invisible, and should be irrelevant, when alpha is zero - and premultiplying like Ebiten does ensures precisely that.

Note that there is one real difference caused by changing the code to do color interpolation in domain of premultiplied rather than unpremultiplied colors - one can construct examples of vertex colorings that look rather different in the interpolated area.
However, in almost all cases the previous behavior would actually be considered a bug, as it makes the "color" of alpha-zero vertices visible.
As an example, change the "shapes" example as follows:
diff --git a/examples/shapes/main.go b/examples/shapes/main.go
index 57b0da4c..2854d07b 100644
--- a/examples/shapes/main.go
+++ b/examples/shapes/main.go
@@ -112,16 +112,21 @@ func rect(x, y, w, h float32, clr color.RGBA) ([]ebiten.Vertex, []uint16) {
        x1 := x + w
        y1 := y + h

+       r = 0
+       g = 0.25
+       b = 0
+       a = 1
+
        return []ebiten.Vertex{
                {
                        DstX:   x0,
                        DstY:   y0,
                        SrcX:   1,
                        SrcY:   1,
-                       ColorR: r,
-                       ColorG: g,
-                       ColorB: b,
-                       ColorA: a,
+                       ColorR: 1,
+                       ColorG: 0,
+                       ColorB: 0,
+                       ColorA: 0,
                },
                {
                        DstX:   x1,
@@ -157,8 +162,6 @@ func rect(x, y, w, h float32, clr color.RGBA) ([]ebiten.Vertex, []uint16) {
 }

 func (g *Game) Update() error {
-       g.count++
-       g.count %= 240
        return nil
 }

Note how I made one vertex of the quads "fully transparent bright red", and all other vertices "fully opaque dark green".
Before: http://www.rm.cloudns.org/img/uploaded/e4fcea908c3a22d0b32864343fbe42a0.png
After: http://www.rm.cloudns.org/img/uploaded/8c5d93a08ad1a36d1ad76d0f32668542.png
A human, asked to interpolate between these (a transparent piece of glass and a solid dark green piece of paper) would sure agree with then new rendering. That red tint that only occurs between vertices, but never at vertices, is the wellknown artifact that comes from interpolating unpremultiplied colors, and I assume it is why Ebiten usually thinks in premultiplied colors internally.

Should also mention that the common cases of vertex interpolation are unchanged by this:

Same color, different alpha - both ways of doing the math result in the same color tone at the same alpha slope.
Different color, sample alpha - both ways of doing the math result in the same alpha level with the same color slope.

now: becomes (0, 0, 0, 0) in the vertex shader, and invariably makes the fully-transparent in the fragment shader

OK acknowledged.

A human, asked to interpolate between these (a transparent piece of glass and a solid dark green piece of paper) would sure agree with then new rendering. That red tint that only occurs between vertices, but never at vertices, is the wellknown artifact that comes from interpolating unpremultiplied colors, and I assume it is why Ebiten usually thinks in premultiplied colors internally.

I agree. The new version is much better and makes sense. My understanding is that this is a very similar issue of wrong interpolation due to straight-alpha (non-premultiplied-alpha) colors.
(To be exact, interpolation might have to consider gamma correction, but this is a different issue)

Yes, it is precisely the same interpolation issue you also get with images in straight-alpha notation when scaling them component-wise without regard for the alpha channel. This can be fixed in a scaling algorithm, of course, however the ones commonly used on GPUs do not.
The only difference is that we had the same issue here in vertex domain rather than texel domain. But indeed - in general, colors should be premultiplied before interpolation.
This underlying issue also affects Kage shaders which I am not fixing here as the chance is higher to break underlying code - this requires further analysis. I do wonder if we are lucky enough to find that nobody uses Fragment()'s "color vec4" argument in Kage with alpha != 1 anyway and thus we can just change it to be premultiplied. Maybe worth tracking this related item as an issue?

This underlying issue also affects Kage shaders which I am not fixing here as the chance is higher to break underlying code - this requires further analysis. I do wonder if we are lucky enough to find that nobody uses Fragment()'s "color vec4" argument in Kage with alpha != 1 anyway and thus we can just change it to be premultiplied. Maybe worth tracking this related item as an issue?

Kage users can determine how to use the color values. Surprisingly, Tetra3D by @SolarRune uses these components for different purposes, so modifying this value would break compatibility unfortunately.
So this reminds me that we have to skip the color component modifying when a custom shader is used... Does your change do so?

So this reminds me that we have to skip the color component modifying when a custom shader is used... Does your change do so?

Yes, "accidentally" - no *Shader calls support a ColorM (unsurprisingly, given Kage also gives no access to it), so the ColorM is always identity when we get here.

Yes, "accidentally" - no *Shader calls support a ColorM (unsurprisingly, given Kage also gives no access to it), so the ColorM is always identity when we get here. In which case this code does nothing.

I see. I'd be happy if you could leave a comment about this (the color components must not be modified when a custom shader is used, and luckily when ColorM is used, a custom shader is not used)

As for Kage's use of colors, maybe it's worth stating explicitly in documentation that color values ColorR, ColorG, ColorB, ColorA are freely usable and get interpolated independently when using DrawTrianglesShader (as opposed to DrawTriangles, which treats them as a straight-alpha color)?

Yes, we need such comments at the APIs.

Would it be fine to ask you to add API comments?
And, it is optional but a test for the interpolation behavior would be nice. If this is difficult to you, I can do this later.

Added API comments about Vertex colors. Especially important as this means the interpretations differ.

As for a regression test, sorry, I do not have experience with that in Ebiten - especially as nothing is really guaranteed there (all depends on how the GPU does it internally). Can do so later, but I'd prefer to not have this be blocked.

As for a regression test, sorry, I do not have experience with that in Ebiten - especially as nothing is really guaranteed there (all depends on how the GPU does it internally). Can do so later, but I'd prefer to not have this be blocked.

Acknowledged!

Right now seeing if I can make a somewhat working test for this despite interpolation not clearly defined.

I'll go to bed soon so I'm happy to take a look at your progress tomorrow if there is :-)

Yeah, sending PR. I decided to make it an approximate test, allowing for quite some rounding errors. Should be good enough.


avl tree in c

Please assign this issue to me

Kindly assign me this task under Hacktoberfest2024, Thanku.

Please assign this issue to me


Article assumes install method was powershell

The "clean up" or uninstall document jumps straight into uninstall steps. If the user did the install with WAC, this document needs to have a section advising how to setup the variables used in the commands
$subscription, $resource_group, $vnetName, $customloc_name, $csv_path
the command line install document has these defined and how to set them
https://learn.microsoft.com/en-us/azure-stack/hci/manage/deploy-arc-resource-bridge-using-command-line?tabs=for-static-ip-address-1%2Cfor-static-ip-address-2

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7e049430-9bb9-ab66-b8bc-5fa0cc7b37e5
Version Independent ID: 387e8235-0668-18b5-fc98-e3af2e464636
Content: Uninstall Azure Arc VM management (preview) - Azure Stack HCI
Content Source: azure-stack/hci/manage/uninstall-arc-resource-bridge.md
Service: azure-stack
Sub-service: azure-stack-hci
GitHub Login: @ksurjan
Microsoft Alias: ksurjan

@peterLeathMSFT
Thanks for your feedback! We will investigate and update as appropriate.

@ksurjan
Can you please check and add your comments on this doc update request as applicable.

@ManikaDhiman on the Troubleshooting page, let's add a few lines to remind customers who deployed via WAC. We can direct them to the "Setup using command line" doc, specifically the input param section, for the input.

@ZmanKyle Thank you for quick response.
@peterLeathMSFT We will update the document, as of now we are closing this case, further questions please feel reach out me.

A blurb has been added for clarification with a link to the command-line setup article: https://learn.microsoft.com/en-us/azure-stack/hci/manage/uninstall-arc-resource-bridge#how-to-uninstall-azure-arc-vm-management
Thanks!


TTL in PubSub.

Description
Added TTL in PubSub.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR relates to: https://github.com/dapr/dapr/issues/2216
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[X] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

I am merging this as I need this change to merge my PR in the dapr/dapr repo. If there is any other comments, I can address in a separate PR. This change is aligned to what we discussed in our last maintainers meeting.


Fix bad import.

Closes #2904 with @Rishabh-Choudhry's fix.

@yasyf thank you for the PR. I added some questions in https://github.com/microsoft/DeepSpeed/issues/2904 since I am not able to reproduce the original issue. Just wanting to make sure other ops are working okay as well.

@yasyf please let us know if #2963 does not solve this issue for you, closing this PR for now.


TouchableNativeFeedback support for android

That will be nice to have.

Totally agree 😄 . Will look into adding it later this week

Will now use TouchableNativeFeedback on Android as of v3.0.0.


settings.ini modified in github actions

I am working on a project using nbdev. It worked flawlessy so far but now the following problem is happening:
Observed behavior

When pushing a certain branch, github actions are triggered properly but breaks on Check if all notebooks are cleaned with the error message git status is not clean. Now, I added some more logging to try and see what exactly is not clean.
It seems that the file settings.ini is modified when installing the library, leading to non-clean git status.
Here are the logs on what exactly is changed:

diff --git a/settings.ini b/settings.ini
index
--- a/settings.ini
+++ b/settings.ini
@@ -1,5 +1,4 @@
 [DEFAULT]
-# All sections below are required unless otherwise specified
 lib_name = my_lib_name
 user = fastai
 description = my_description
@@ -12,42 +11,16 @@ version = 0.0.1
 min_python = 3.6
 audience = Developers
 language = English
-# Set to True if you want to create a more fancy sidebar.json than the default
 custom_sidebar = False
-# Add licenses and see current list in `setup.py`
 license = apache2
-# From 1-7: Planning Pre-Alpha Alpha Beta Production Mature Inactive
 status = 2
-
-# Optional. Same format as setuptools requirements
 requirements = numpy pandas matplotlib requests tqdm pyarrow joblib fastai torch xlrd hyperopt scikit-optimize
-# Optional. Same format as setuptools console_scripts
-# console_scripts =
-
-###
-# You probably won't need to change anything under here,
-#   unless you have some special requirements
-###
-
-# Change to, e.g. "nbs", to put your notebooks in nbs dir instead of repo root
 nbs_path = nbs
 doc_path = docs
+doc_host = https://fastai.github.io
+doc_baseurl = /my_lib_name/
+git_url = https://github.com/fastai/my_lib_name/tree/master/
+lib_path = my_lib_name
+title = my_lib_name
+host = github

-# Anything shown as '%(...)s' is substituted with that setting automatically
-doc_host =  https://%(user)s.github.io
-doc_baseurl = /%(lib_name)s/
-git_url = https://github.com/%(user)s/%(lib_name)s/tree/%(branch)s/
-lib_path = %(lib_name)s
-title = %(lib_name)s
-
-#Optional advanced parameters
-#Monospace docstings: adds <pre> tags around the doc strings, preserving newlines/indentation.
-#monospace_docstrings = False
-#Test flags: introduce here the test flags you want to use separated by |
-#tst_flags =
-#Custom sidebar: customize sidebar.json yourself for advanced sidebars (False/True)
-#custom_sidebar =
-#Cell spacing: if you want cell blocks in code separated by more than one new line
-#cell_spacing =
-#Custom jekyll styles: if you want more jekyll styles than tip/important/warning, set them here
-#jekyll_styles = note,warning,tip,important

Expected behavior

No error in this step.

Additional context

This is the first time it happens. It does not happen for any other branch we have or had in the past.
I would say I have not changed anything related to all this, but I am not sure.

Note: Not sure if this a real issue with the library or I am doing something wrong. I would have posted this in the fastai forums but I could not find an nbdev category. If there is a place for this discussion there, I will happily move it.

The most recent of nbdev needs additional fields in settings.ini. To avoid breaking compatibility, those are added to your config file if not present with default values. The problem is that GitHub actions install the new nbdev and you have an older one, resulting in a mismatch between those files.
To fix:

save your old settings.ini just in case,
upgrade nbdev,
run something like nbdev_read_nbs in your repo,
checkout the changes in settings.ini and either keep this one or add the new fields in your old settings.ini.

Thank you very much, this solved the issue.
Maybe it would be helpful to add a suggestion on updating the library if this error pops up. Do you think it is a good idea? If so, I could do the PR.

Sure, a helpful error message can always help.


Compose.js Updates

Added easier to use prompt to compose.js, updated the readme and added handling of blank inputs. added package inquirer

sidenote : added prettier ignore because why would someone want to pretty everything including .next folder ( prettierignore works with gitignore content )

Hi @AryaveerSR, any reason you are closing this request? I thought it was a nice addition, just needs some cleaning up and it should be good to go. Let me know if you no longer want to work on it and I will copy over the changes. Thanks.


Prefer stateless function does not detect the use of redux.

For example when I have a component like this
class SomeComponent extends Component {

render() {
  const { someState1, someState2 } = this.props
  return( <View>
                  <Component1 prop1={someState1} />
                  <Component2 prop2 ={someState2}} />
            </View>
         );

      }
}

const mapStateToProps = state =>({
   someState1: state.action.someState1,
   someState2:state.action.someState2
});

export default connect(mapStateToProps)(SomeComponent);
Even though the rule says it detects the use of local states, constructors, or render returning something other than JSX before triggering the warning. For some reason it does not detect the use of redux and says it should be a pure function, especially  when the redux states are being passed down. I just want to know if this is a bug or if this is intentional. Thank you.

It should be a pure function - that you're calling your props "state" doesn't make them state, they're just props. redux has state, but SomeComponent does not.


feat: introduce a xr locomotion handler

Description
XR implementation of a XR Locomotion handler and XR Rig Manipulation handler to directly manipulate the position and rotation of the XR Rig. The is the Unity XR implementation of the base locomotion handler from Basic-Interaction (https://github.com/Innoactive/Basic-Interaction-Component/pull/46)
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Aditional Notes
Related PRs:
https://github.com/Innoactive/Basic-Interaction-Component/pull/46
https://github.com/Innoactive/Creator-Pro/pull/60

/azp run

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Basic problems with generated SQL for Postgres

I have a feeling that I'm missing something, but my experience with the PostgresCompiler is that it has several problems creating valid queries even for simple scenarios. There are things which seem so basic that I cannot be the first to run into them - hence the feeling that I am missing something. The queries were executed by manually taking the compiled sql and executing them with Dapper, if it makes any difference. I'm using version 2.4 of the library.

When using query.WhereContains, the query string itself is not surrounded with 's which it must be. I updated the CompileBasicStringCondition implementation to change the switch statement to the following:

switch (x.Operator)
{
    case "starts":
        text2 = "'" + text2 + "%'";
        break;
    case "ends":
        text2 = "'%" + text2 + "'";
        break;
    case "contains":
        text2 = "'%" + text2 + "%'";
        break;
}

When using query.WhereLike I had the same problem as in 1), but here the solution was just to prewrap my argument in single quotes at the call site. This is less of a big deal, but takes away from a feeling that the library "just works".

When selecting columns, they are wrapped in "s. This is not valid, so I had to do the following in my compiler.

public override string WrapValue(string value) =>
    value;

I'm not sure if this has any influence on 1) and 2), but I don't think so since the quotation character is " which is not what is needed in those cases.

How are you executing your query?,are you using the output of SqlResult.ToString() method?

@ahmad-moussawi I'm compiling like this and then executing the sql with Dapper. There may be one or more queries in the array.
var sql = compile.Compile(arrayOfQueries).Sql

Can you please confirm if you face the issue when using the Compile(Query) overload?

Yes, this makes no difference.

I started building a minimal repro, when I realized something. I used the search parameter expecting it to be inserted directly. However, the library actually treats it as a query parameter which I did not expect. As a query parameter, it makes sense that it would not be quoted I think (I'm not sure if SELECT * FROM Users WHERE Username LIKE %@p0% is valid or not, but I expect it is). It makes sense that it would not just inject the search query verbatim since that would facilitate injection attacks - I just didn't realize it. I'll have to look into why my code worked regardless which is a bit weird.
The third case still stands though. It can be reproduced with this xUnit test (which fails).
[Fact]
public void Scenario3__Columns_are_not_quoted()
{
    var query = new Query("users").Select("Name");

    var sql = new PostgresCompiler().Compile(query).Sql;

    Assert.Equal("SELECT Name FROM users", sql);
}

I should have made the repro before reporting the issue, so sorry to bother you with scenario 1 and 2.

no worries thanks for getting back, so I think we can close this ticket now,
feel free to reopen in case you find something else.


Add GEEST

Insert URLs to the project here: https://github.com/worldbank/GEEST

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All projects listed will be posted on our Mastodon channel

@andre-pegasys