[server fabric 1.19.2] the mod is not considering my changes in the config file

On my server im using the following settings on home/container/config/AMETHYST_IMBRUEMENT/ENCHANTMENTS_V1.JSON, but it's not working:
{
  "disableIncreaseMaxLevels": true,
  "enabledEnchants": {
    "amethyst_imbuement:bulwark": true,
    "amethyst_imbuement:cleaving": true,
    "amethyst_imbuement:heroic": true,
    "amethyst_imbuement:wasting": true,
    "amethyst_imbuement:deadly_shot": true,
    "amethyst_imbuement:puncturing": true,
    "amethyst_imbuement:insight": true,
    "amethyst_imbuement:lifesteal": true,
    "amethyst_imbuement:decayed": true,
    "amethyst_imbuement:contaminated": true,
    "amethyst_imbuement:multi_jump": true,
    "amethyst_imbuement:night_vision": true,
    "amethyst_imbuement:steadfast": true,
    "amethyst_imbuement:rain_of_thorns": true,
    "amethyst_imbuement:vein_miner": true
  },
  "aiEnchantMaxLevels": {
    "amethyst_imbuement:bulwark": 1,
    "amethyst_imbuement:cleaving": 3,
    "amethyst_imbuement:contaminated": 1,
    "amethyst_imbuement:deadly_shot": 3,
    "amethyst_imbuement:decayed": 1,
    "amethyst_imbuement:heroic": 7,
    "amethyst_imbuement:insight": 3,
    "amethyst_imbuement:lifesteal": 3,
    "amethyst_imbuement:multi_jump": 1,
    "amethyst_imbuement:night_vision": 1,
    "amethyst_imbuement:puncturing": 6,
    "amethyst_imbuement:rain_of_thorns": 3,
    "amethyst_imbuement:steadfast": 3,
    "amethyst_imbuement:vein_miner": 2,
    "amethyst_imbuement:wasting": 4
  },
  "vanillaEnchantMaxLevels": {
    "minecraft:bane_of_arthropods": 6,
    "minecraft:blast_protection": 4,
    "minecraft:efficiency": 6,
    "minecraft:feather_falling": 5,
    "minecraft:fire_aspect": 3,
    "minecraft:fire_protection": 4,
    "minecraft:fortune": 4,
    "minecraft:knockback": 4,
    "minecraft:looting": 3,
    "minecraft:loyalty": 4,
    "minecraft:lure": 4,
    "minecraft:piercing": 5,
    "minecraft:power": 5,
    "minecraft:protection": 4,
    "minecraft:quick_charge": 4,
    "minecraft:respiration": 4,
    "minecraft:sharpness": 5,
    "minecraft:smite": 5,
    "minecraft:sweeping": 4,
    "minecraft:thorns": 3,
    "minecraft:unbreaking": 3
  }
}

1.19.2
fabric 0.15.11

Newest version 1.19-41 fixes this


Use .yml suffix consistently

Summary
We use .yaml for ~half of our YAML files, and .yml for the other half. This PR standardizes on .yml. I don't have a strong preference between the two, but cargo-dist prefers .yml, so seems easier to fall on that side of the argument.

Pre commit doesn't agree 🤣

Heavy sigh

😭

fwiw I have the smallest of preferences for yaml.

Yeah me too. I'm probably going to change it anyway though, since cargo-dist requires it and it's not a strong enough preference for me to change my mind on a bigger tooling decision based on the suffix alone.

Yeah me too. I'm probably going to change it anyway though, since cargo-dist requires it and it's not a strong enough preference for me to change my mind on a bigger tooling decision based on the suffix alone.

For which files does cargo-dist require .yml? Could we only change these files (yml is impossible to pronounce)

release.yml (which is auto-generated), and then the files that are automatically referenced as sub-steps (e.g., publish-to-pypi.yml).

I'll just close this then and bundle it with the cargo-dist PR. I figured it'd be easier to stage it separately, but seems not.


Create a macro for generating TestJSON trees.

Currently, Sapling has two datatypes for JSON trees (JSON is analogous to &str whereas TestJSON is analogous to String).  As the name suggests, TestJSON is used primarily for easily creating test cases, but is most of the time more verbose than JSON because of its long name.  If we could create a macro for this then it would be very epic.
Something like:
test_json!([true, false, {"key" => "value"}])

should expand to:
TestJSON::Array(vec![
  TestJSON::True,
  TestJSON::False,
  TestJSON::Object(vec![
    (
      TestJSON::String("key".to_string()),
      TestJSON::String("value.to_string())
    )
  ])
]);

anyone who wants to have some fun with macros and knows what they're doing is welcome to do this :grin:.

I think this can be replaced by converting serde_json value, right?

I think this can be replaced by converting serde_json value, right?

I think it can - the only issue is that serde_json::Value stores objects as an unordered (hash)maps, whereas TestJson and Json both keep the ordering of the fields.  I think it's fine - I've been refactoring the tests and this hasn't yet been a problem.
I've also got a new record of most compiler errors generated in one go (332 errors and 1 warning) :tada:.  Doing the refactoring is also taking forever - I'm down to 145 errors now but I've spent nearly 2 hours and it's now nearly 1am.  I need some sleep.

I think it can - the only issue is that serde_json::Value stores objects as an unordered (hash)maps, whereas TestJson and Json both keep the ordering of the fields.  I think it's fine - I've been refactoring the tests and this hasn't yet been a problem.
I've also got a new record of most compiler errors generated in one go (332 errors and 1 warning) :tada:.  Doing the refactoring is also taking forever - I'm down to 145 errors now but I've spent nearly 2 hours and it's now nearly 1am.  I need some sleep.

https://docs.serde.rs/serde_json/enum.Value.html#variant.Object

By default the map is backed by a BTreeMap. Enable the preserve_order feature of serde_json to use IndexMap instead, which preserves entries in the order they are inserted into the map.

https://docs.serde.rs/serde_json/enum.Value.html#variant.Object

By default the map is backed by a BTreeMap. Enable the preserve_order feature of serde_json to use IndexMap instead, which preserves entries in the order they are inserted into the map.

Oooooh!  I got round the issue by forcing the JSON to have the keys in alphabetical order but this is a much better solution :laughing:.

Oooooh!  I got round the issue by forcing the JSON to have the keys in alphabetical order but this is a much better solution :laughing:.


[ETFE-3574] added consignee-trader-identification page

As discussed:

Missing Error: prefix on page title when in error
Form automatically fills with valid value when an invalid value is submitted


Update instructions for OneVersion environments and local development vhd environments

Some parts of the article do not seem the current update process for OneVersion platform updates and/or local development vhd environments. For example, in the current platform update 25 installer package, there is no PlatformUpdatePackages.Config file as mentioned in section "Apply a platform update to environments that are not connected to LCS".

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

ID: 058d220b-d85d-eabd-abfb-8fadb3b8bf47
Version Independent ID: c25f2d4d-dfef-7736-311f-8c1f25ddc696
Content: Apply the latest platform update to environments - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/migration-upgrade/upgrade-latest-platform-update.md
Service: dynamics-ax-platform
GitHub Login: @tariqbell
Microsoft Alias: tabell

@FH-Inway, thanks for posting this!
@manalidongre, please review and update the topic as needed.

Bug 316728 has been logged to track this issue.

In addressing this, please could you consider updating step 4 in "Install the deployable package" so that it reads:
"Follow the instructions for installing a deployable package and ensure that the DefaultTopologyData.xml file is updated for your environment. See ... [etc]"
It is possible for the reader to skip over the updates to DefaultTopologyData.xml in the next page as they are enclosed with a section that refers to LCS environments again (this section is about non LCS environments).
There a lot of issues on Yammer that seem to be caused by this (I came a cropper the first time as well and didn't think it necessary to update DefaultTopologyData.xml...)

@noakesey I created a similar issue 1137 for another article, maybe bug 313995 created there could also be used for your feedback.


l3-149: union and stil nested objeection rather than one of (descriminated union) which did not work with mutable arrays.

What

Updated to unsure that operator is being passed along also left temporary old stepValidation as it's being used somewhere else, will remove if no objections
Unfortunately, one of or using union along with Discriminated unions which should allow to have an array of objects and say. One of is good enough.

Closed in favour of #121


Recipe

Changes made on this pull request :

[ ] Added interface skeleton for recipe
[ ] Setup controller for recipe

okay if that so lets merge it to dev @kosher9


Backups never finish because filesystem scan starts

I've been running the Docker-ized Crashplan fine since it was put into docker, but here of late my backups never complete.
They run for about 3 hours then stop.  THe history says "Reason for stopping backup: Full filesystem scan started".
I checked the web console and the verification scan is set every day at 3AM, so I'm clueless why the scans are starting and stopping the backups.
Anyone have any ideas?  I'm pretty sure Crashplan won't offer support for this.

That seems to be an issue on CrashPlan site.  Why do you say they won't offer support ?

Just looked a bit more into it.
Looks like there is no way to change the verification scan period on a an old/active device.
So the change set in web console only affect devices added after the change.
I ended up having to create a completely new device, which is now running backup.
Still have to see if it will work in the long run, cause it's gonna be doing backup for many days now.
8tb+ of data that has to be re-uploaded.
But i can see that this "new" device now has a 8 day full scan verification period.
Not a great work around, but hopefully a working one.
And i agree, this could seem to be a crashplan issue, and not a docker issue.
It might just be that large arrays just take too long, and full scans keep happening.
But i will be asking Crashplan support.

@jlesage : Crashplan does not support a headless configuration.  It's been this way as far back as I can recall.
I opened a case with Crashplan anyway in the hopes that possibly they've changed the policy.
This is the initial response from CP Support:
"We will need to begin by learning about your computing environment. What I see within our monitoring for the device is very strange to me, and I am unfamiliar with a lot of what I am seeing.
What type of setup are you running, from a hardware perspective? How does CrashPlan connect from the host device to the drives? What distro of Linux is this running, and what version number is this distro?
The behavior you are reporting sounds strange, and we'll need to know what type of environment CrashPlan is running in, in order to be able to know how this issue can be approached."
So at this point, they were "on to me".  I fessed up, and:
"the problem is that CrashPlan was never designed to run in a container, and that type of setup has been fully unsupported since day one. We don't design the software for that use case, but we of course don't enforce preventing users from creating whichever unsupported setup they feel confident in managing themselves."
@TheBekker : mine is 12TB as well, and here's what they recommended:
"You have 5 different backup sets set to send data all to the same destinations. Each of them are set to run for once per day, and each of them are scheduled to run a scan every 3 hours. I would generally recommend that you condense each of these backup sets back down to one backup set, as you're not actually using the backup sets feature in any meaningful way, unless there's something unique about how they would function in an unsupported environment which I am not aware of. Backup sets are intended to be used in order to send data to different destinations. When you configure them to all send to the same destinations, it all gets dumped into the exact same archive(s), so they just function as scheduling brackets. 5 schedules can get in the way during the best of times, but is going to be especially problematic in this scenario.
My recommendation is that you condense all of your backup sets into the "Homes" backup set, by adding their file selections to the "Homes" backup set", and then deleting each of those now-redundant extra 4 backup sets. Once you have done so, a verification scan schedule of once every 2 or 3 days should reduce the amount of time CrashPlan is stuck in scans, and greatly improve your uptime for the backup. "
So I actually ended up deleting all archives and starting over with the above recommendations with the exception that the verification scans were set to 7 days (reduce the # of times that occurred until it completed).  After about a month, I had a completed 12TB backup to CP and I set my scan time to 2 days and it seems to be fine now.

It's true that running CP in Docker container is not officially supported.  But if you don't tell the support team about it, or if your setup doesn't provide clear indication that CP is running in container (e.g. by naming your backup set Synology), the support team would help most of the time.

@TheBekker
By web console do you mean using the web interface connected to your Synology instance? If so, that's correct but there's a way to change it. You need to login to your Crashplan account on Crashplan's website to do it. At the top go to Device Backup and then under "Preferred time for verification scan" set it to how many days you want it to be. After you save that setting, here's the important part, you need to hit the button on the right side that says "Push settings to device". There's no text on that icon until you hover on it, but the changes won't take effect on the Synology instance until you do that.
I was having the same problem where since it was defaulted for every day, it could never finish the backup because it would hit the scan. Once I changed it to like 5 days through Crashplan's site, it gave it enough breathing room and I was able to finish the backup before the next scan. I even went to the restore section to verify if the files were showing up there now and they were.
The one problem I have now though is it seems like when it does a full scan, it has to do some extra validating on anything over 2TB. While it doesn't have to upload that data, it does seem to be doing something that takes way longer than the first 2TB. The only hope I have right now is that because this is the first time I've been able to complete my backup after this change, that this additional part of the scan is just happening for this one instance and it'll be fine after the next but my guess is that won't be the case.

@Darknight016
With Web Console i mean the Crashplan's own website, that what they call it.
Didn't notice the "Push settings to device", i might look into that.
I'm currently testing a Borg setup instead combined with a Hetzner storragebox.

@TheBekker : mine is 12TB as well, and here's what they recommended:
"You have 5 different backup sets set to send data all to the same destinations. Each of them are set to run for once per day, and each of them are scheduled to run a scan every 3 hours. I would generally recommend that you condense each of these backup sets back down to one backup set, as you're not actually using the backup sets feature in any meaningful way, unless there's something unique about how they would function in an unsupported environment which I am not aware of. Backup sets are intended to be used in order to send data to different destinations. When you configure them to all send to the same destinations, it all gets dumped into the exact same archive(s), so they just function as scheduling brackets. 5 schedules can get in the way during the best of times, but is going to be especially problematic in this scenario. My recommendation is that you condense all of your backup sets into the "Homes" backup set, by adding their file selections to the "Homes" backup set", and then deleting each of those now-redundant extra 4 backup sets. Once you have done so, a verification scan schedule of once every 2 or 3 days should reduce the amount of time CrashPlan is stuck in scans, and greatly improve your uptime for the backup. "

This is funny cuz it's EXACTLY the same thing they told me. Word for word except my "Homes backup set" is named different. I was actually using multiple backup sets to organize what I was backing up. I never remember reading anything that said "the purpose of multiple backup sets is to backup to different destinations".

So I actually ended up deleting all archives and starting over with the above recommendations with the exception that the verification scans were set to 7 days (reduce the # of times that occurred until it completed). After about a month, I had a completed 12TB backup to CP and I set my scan time to 2 days and it seems to be fine now.

So far I've "deleted" one of the additional sets by FIRST adding the files to the original backup (in essence duping things) and then once that backup was complete, THEN removing the set. That way not to lose anything/MAYBE quicker backup.
However, I still have issues with my setup since November. It still tells me after a full scan 3TB to backup out of 7TB EVEN THOUGH it has already backed up the 3TB. it runs through (sometimes) all data, gets to 0 to backup and then the next scan resets it right back to 3TB. All the backup sets I have do the same thing. to make it so bad one keeps restarting at "247 bytes to back up". COME ON GUYS!
Also have issue where I can only change settings of the original backup set via the web. None of the other backup sets allow changes. Can't "save" only "cancel".
I just want to know what they broke (on purpose?) beginning after the announcement of "no more forever backups". I do have a LARGE backup (I admit it) but NEVER had a single problem in the years since I first began sending them my data. Now I can't get correct unless I "delete and start over"? How can this "not backed up" pointer get reset? They release "fixes" for everything but this. Can't just be a "headless" issue (or is it?)... Somebody reverse engineer their bogus java app (memory eater!) and tell me what bomb they put in there (grin).

Personally, I suspect the "Scanning backup selection" step is there to throttle traffic/disk space usage for Code42. Intentionally showing down the backup benefits them when it comes to new, large backup sets.


Can`t update datetime in studio

Oriento: 2.0.11

Simliar issue here https://github.com/orientechnologies/orientdb-studio/issues/34

hi @StarpTech
how can i reproduce it?

Look at the picture above. Try to pick up a date in the studio and save. You can see the error also in the picture at the bottom.


Decide on OWD Q3 projects

We met last Wednesday (June 9th, 2021) to go through current OWD project proposals and ideas.
This issue summarizes them so we can discuss which projects to take on in Q3 2021 (the months July, August, September).
Continued projects
These project have been started and it makes sense to continue them in Q3.

Markdown conversation for more of MDN (CSS docs)
Finish mixin work (for workers, events, etc.)

Proposed projects
Proposed projects are defined ideas that are clear in scope. They are ready to be worked on.

WebXR Browser Compatibility
Fix how MDN distributes Polyfills
WebView information on MDN
ARIA roles reference docs
Modernizing the Learning Area JavaScript modules
Use webref as the source for CSS formal syntax, instead of mdn/data
Documenting HTTP/2 and HTTP/3 (discussion)

Ideas
These ideas aren't proposals yet as more details are needed.

Documenting WebDriver (needs scope, rough outline)
Web Testing strategies (needs scope, rough outline)
Fixing MDN page titles (needs decision)
Fixing how MDN documents dictionaries (needs decision, issue, list of pages affected)

Submit ideas
You can still submit ideas until the end of June and we will take a look!

Finish mixin work (for workers)

Should this also include events? See https://github.com/mdn/browser-compat-data/issues/8929#issuecomment-859545693 for everything that remains to be done to eliminate mixins.

Yes, ideally, we fix all issues related to mixins.

What's the right place to discuss WebView? @tomayac was enthusiastic about WebView, but there's no issue for it, just https://github.com/mdn/content/pull/3918 which added the linked RFC.

"Enthusiastic" as in "good to have this documented". The best browser still is an actual browser, and not a WebView :-)  Just to set this straight.

Sorry to overstate your love of WebViews :)

What's the right place to discuss WebView? @tomayac was enthusiastic about WebView, but there's no issue for it, just mdn/content#3918 which added the linked RFC.

I think we should open a new issue here so we can discuss this project some mor, outline a plan, and scope the work that we want to do.
(As soon as the vacations are over and new OWD employees have been onboarded, I plan to go over all projects, too, but it doesn't hurt to get into some of this stuff beforehand already).

Forgot to post this here: Results from the stack ranking we did in June:

WebXR Browser Compatibility
Fix how MDN distributes Polyfills
Documenting HTTP/2 and HTTP/3
WebView information on MDN
Modernizing the Learning Area JavaScript modules
Use webref as the source for CSS formal syntax, instead of mdn/data
ARIA roles reference docs

We talked about this ranking in the last SC call and I did not hear any reservations, so this order should be a guiding principle when assigning work in our team. We're planning to onboard two new folks soon and we will then get together and look at these to determine what is achievable in the quarter. In the meantime, we're trying to finish continued projects.

https://github.com/openwebdocs/project/issues/42#issuecomment-879679064

We had a planning check-in call yesterday and here's a summary of where we are with Q3 projects:
WIP with the goal to finish

Markdown conversation for more of MDN (CSS docs) (Will)
WebXR Browser Compatibility (Florian)
Documenting HTTP/2 and HTTP/3 (Jean-Yves)

Aiming to make progress (at least)

Mixin work (for workers, events, etc.) (help to unstuck, Florian)
Fix how MDN distributes Polyfills (start discussions/ make plan that can be executed in Q4, Jean-Yves)
Use webref as the source for CSS formal syntax, instead of mdn/data (exploration, Will)

@Elchi3 do you consider representing support of events in score for Q3, or just the bits that get entangled with mixins? From my work on API data with @vinyldarkscratch, I would say that events are the most problematic part of the data, and while the model we have makes it possible to represent support for different facets of events, I don't think the result is very clear to web developers.
Spending some cycles on events would be great, if OWD could :)

Predicting that the answer is "no not yet" my follow-up question would be where I can park the suggestion for Q4 review.

I'm still busy with WebXR docs, but unblocking mixins when I can is in scope. The top of my to-list includes https://github.com/mdn/browser-compat-data/pull/11518. Let me know what other things are pressingly needed and I will try to get to it.
https://github.com/mdn/browser-compat-data/issues/7545 looks like a larger effort, though (and maybe it is separate enough from mixins?). So, it would be really great if you could file that as new project for OWD to consider for Q4. You can file an issue on this repo and we can flesh it out this quarter, so it is ready to be considered in the next planning call (September 8).


Macedonia Partial country update

http://app.gdi.mk/arcgis/rest/services/MKT/Address_Model/MapServer/1

pulling in new resource - lets do this! Will update link and upload geojson file asap

full dump is in the same shared folder for skopje. We may want to remove the skopje one and have just the full dump? Let me know. Thanks!!
https://drive.google.com/open?id=10TAEmchP29RtUE9vhZMeCVRWj5i8fQSj


[Diagnostics] Fix errors on the developer console for the Entity Framework Database Middleware

Removes the content-length and connection headers as they shouldn't be setup by the AJAX request

@natemcmaster @javiercn Okay, I assume this is the real PR. :-)

@ajcvickers Yes. The other one was in diagnostics which got moved here.

Description
As part of the first-time experience ASP.NET Core apps will show a "database error page" if the application is run without first creating the database. This page has a button to create the database, which does what it says, but then shows an error leading first-time users to believe that things are really broken.
Customer Impact
Impacts the first-time experience for people trying ASP.NET Core with EF Core.
Regression?
Yes, from 2.1.
Risk
Very low--fix is isolated to removing two lines that were setting inappropriate headers. This page is also only enabled in the "Developer" environment--it's not used for "Production".

Approved for 2.2.1
Confirm if the 3rd error is also removed.

@javiercn Question from @DamianEdwards in shiproom: is the third error shown in the repro *(The HTTP 1.1 error) also fixed by this PR?

@ajcvickers I didn't see that error in my repro and the changes fix the other two.

@javiercn Thanks.
@DamianEdwards Since @javiercn can't repro the third error and we know the PR as it is fixes some known errors, I suggest we merge this and then re-test end-to-end after it gets in a patch build. If that still results in errors then we create a second fix, which may or may not be in time for the first patch, but can at least go in the second.

I'd like to have @javiercn (or someone) try to repro the 3rd error ASAP, though I'm OK with checking in what we have for now.

@Eilon I've already sent an email on friday about this. I believe the 3rd error is unrelated and due to a change in how VS launches EF under IIS Express. I'll add you to the thread.

As per Damian, while these changes don't fix the third issue (which was already identified) he also wants this to be patched, so merging.


mwc-textfield: cannot set background colour for outlined textfield

As the title states, we cannot override the default transparent background for an outlined mwc-textfield.
The --mdc-text-field-fill-color (see #544) only works for non outlined textfields

Can you give an example use case of when you'd want to use a colored background? Outlined textfields are supposed to show the background behind them according to spec.

Closing this for now due to inactivity. Outlined textfields should always be transparent per design spec.
Feel free to comment with your use case and we'll bring it up with our design team!


Resolve #135: Added dropup on dropdown

Description
Added the dropup feature on the dropdon.
Resolve: #135

Coverage remained the same at 100.0% when pulling 9160f21060d08707c63ef9c17017e78f21d91a9b on Olyno:135 into b9af8271840c9a52ecf493f3b1f919d8cd3e5fc1 on AlgusDark:master.


Coverity fixes

[x] tests are added or updated

I think that's everything covered.

Current again I think.

Thanks, will merge after the thawing of the repo.

Merged, thanks.


Firestore updateData([hashable], completion) not invoking completion handler

Environment

Xcode version: 9.3
Firebase SDK version: 4.13.0
Firebase Component: Firestore
Component version: 4.13.0

Description
I attempted to update a document that should have been created, using the updateData() with a completion handler included. The completion handler was never invoked (with or without an error).
The Firebase documents state that the updateData() method will fail if the document doesn't exist, so I wen't to check through the Firebase console whether the document had in fact been successfully created. It didn't show in the collection that it should have been in.
It then showed up about 10 minutes later, and subsequent update methods worked. But, in the interim, other clients trying to access this document could not find it - even though it had clearly been created? I'm wondering if this is some kind of multi-region syncing latency?
Steps to reproduce:
Call updateData([hashable], completion) on a document reference that has been created, but not showing in the Firestore database yet.
Relevant Code:
documentRef.updateData(dbDataUpdate) { (error) in
     if error != nil {
         // This didn't fire not firing
     }

     // Nor did this
}

That sounds like a perfectly reasonable explanation given my understanding of the offline behaviour of the client SDK. We have intermittent internet down here in Africa. Thank you for your help and speed of response.
--> Closing the issue. No need for action :)


Added Budget Tracker ("Track your spending, set goals, and stay on budget with our easy-to-use Budget Tracker!")

Pull Request Description
Title: Added Budget Tracker 📝
Author: Abhisek Panda
GitHub ID: abhisek2004
Email ID<EMAIL_ADDRESS>
Summary of Changes
I have implemented a new feature for the Budget Tracker in our web application. This feature allows users to easily track their spending and income, set financial goals, and maintain an organized view of their budget. Below are the specific changes made:

New Section in Main Page: 🗂

Added a "Budget Tracker" card in the main index page. This card serves as a gateway to the Budget Tracker functionality.
The card includes an image and a brief description that reads:

"Track your spending, set goals, and stay on budget with our easy-to-use Budget Tracker!"

Here is the added code for reference:

Budget Tracker

            "Track your spending, set goals, and stay on budget with our easy-to-use Budget Tracker!"

Budget Tracker Functionality: 💰

Implemented a form that allows users to add new transactions (both income and expenses).
Each transaction captures the type, name, and amount, which are stored in the browser's localStorage for persistence.
Added functionality to display transactions in a table format, allowing users to see their financial activity at a glance.
Users can delete transactions, and the balance updates automatically based on the entered data.

User Interface Enhancements: 🎨

Designed a user-friendly interface with a clean layout, ensuring that the Budget Tracker is easy to navigate and visually appealing.
Styled the balance display to make it prominent, incorporating a blinking effect for visibility.

Here is the code for the main page of the Budget Tracker:
<!DOCTYPE html>

    <title>Budget Tracker</title>
    <link rel="stylesheet" href="style.css">

Your Current Balance

                ₹

Add a new transaction:

            <form id="expForm">

                    Type:
                    <select id="type">
                        <option value="chooseOne">Choose one...</option>
                        <option value="income">Income</option>
                        <option value="expense">Expense</option>
                    </select>

                    Name:
                    <input type="text" id="name">

                    Amount:
                    <input type="text" id="amount">

                <button type="submit" class="buttonSave">Add to transactions</button>
            </form>

                    Type
                    Name
                    Amount
                    Options

        @ Created and Design By Abhisek Panda

Conclusion
These changes enhance the functionality and user experience of our application, making it easier for users to manage their finances. I believe this feature will be a valuable addition to our project.
Please considering my pull request! 🙏
My work Screen Shot ------

mention isssue no and resolve the conflict


How to get rid of Micronaut processor

Micronaut-inject generates a ton extra $Introspection and $Definition classes that bloat the binary and seem to produce some problems with ProGuard obfuscation.
Making the fxml fields/methods public generates byte code that doesn't depend on Micronaut introspection, but the classes still get generated. Is there a way to run only the fxml annotation processor? I tried removing the micronaut-inject-java annotation processor, but that results in the fxml files not being generated either.
Fwiw, I did a quick test yesterday to automatically generate GraalVM reflect-config files for annotated fields (see ConfigGenerator) and it turned out to be pretty straight forward. It might make sense to have a low-dependency mode that uses public access and falls back to reflection w/ generated config files.

Yes, it's a great idea, but not quite straightforward to implement. compiler-core can mark fields and methods that require reflections with special annotation, and then compiler.micronaut can skip generating introspection for controllers that does not require reflections. The only show stopper now is controller construction logic. If you do not have custom controller factory, controllers are created using Micronaut's introspector. To work-around this, new factory method that constructs controller or throws if there is no accessible no-args constructor can be added to CompiledFXMLLoader.
Reflective implementation is also possible, but I haven't implemented it because it's not clear to me how to deal with Jigsaw modules. Should this implementation be in automatic module, or should there be compiled module-info patcher? To implement MLFXLoaderDelegate there should be some kind of cache of available loaders at runtime. This cache can be implemented using ServiceLoader, but that would require tonns of provides io.github.paullo612.mlfx.api.CompiledFXMLLoader with ... in your module-info.
For the reference: there is reflection based accessor implementation on Groovy for tests.

About $Definition files: Looks like you're using some sort of DI in your app. I found no way to stop Micronaut's annotation processor from generating bean definitions for now. Looks like I should ask Micronaut guys to provide one. For now, you can just delete those $Definition files with maven-clean-plugin on package phase. The only required files are ...$Introspection and ...$IntrospectionRef.
micronaut-inject-java cannot be removed from annotation processors classpath, because it provides AST abstraction  implementation for Java.

Right, I didn't consider the module-info. I rarely use reflection and usually create a shaded/obfuscated/shrunk jar that gets rid of the individual jigsaw modules, so I'm not familiar with how it works across modules. I think some amount of one-time user setup would be reasonable as long as it gets rid of the grunt work of running the agent on updates.
After looking at the setup a bit more, my understanding is that this project has 3 different annotation processors:

CompileFXMLVisitor (compiler-core): looks for @CompileFXML and generates $CompiledFXMLLoader classes
FXMLMicronautVisitor (micronaut): looks for @FXML and marks classes as @Introspected for Micronaut
CompileFXMLMicronautVisitor (micronaut): looks for @GeneratedByMLFX and generates META-INF/services/io.github.paullo612.mlfx.api.CompiledFXMLLoader

All of them get called by the annotation processor service in micronaut-inject-java, which also calls the micronaut processors for generating $Introspection and $Definition. I tried using only the compiler-core processor, but that still generates the definition classes. Unless there is some micronaut flag to disable it this looks harder to get rid of than I initially thought.
The ProGuard issue I ran into seems to come from the $CompiledFXMLLoader classes, but I can't say anything specific because the error is absolutely useless... I'll create an issue if I manage to reproduce it in a smaller example.
 [proguard] ProGuard, version 7.2.0
 [proguard] Unexpected error
 [proguard] java.lang.StringIndexOutOfBoundsException: String index out of range: 93
 [proguard]     at java.lang.StringLatin1.charAt(StringLatin1.java:48) ~[?:?]
 [proguard]     at java.lang.String.charAt(String.java:1512) ~[?:?]
 [proguard]     at proguard.classfile.util.DescriptorClassEnumeration.nextFluff(DescriptorClassEnumeration.java:171) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.DescriptorClassEnumeration.classCount(DescriptorClassEnumeration.java:66) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.findReferencedClasses(ClassReferenceInitializer.java:1320) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.visitLocalVariableTypeInfo(ClassReferenceInitializer.java:718) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.attribute.LocalVariableTypeTableAttribute.localVariablesAccept(LocalVariableTypeTableAttribute.java:73) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.visitLocalVariableTypeTableAttribute(ClassReferenceInitializer.java:609) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.attribute.LocalVariableTypeTableAttribute.accept(LocalVariableTypeTableAttribute.java:60) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.attribute.CodeAttribute.attributesAccept(CodeAttribute.java:236) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.visitCodeAttribute(ClassReferenceInitializer.java:595) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.attribute.CodeAttribute.accept(CodeAttribute.java:138) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.ProgramMethod.attributesAccept(ProgramMethod.java:148) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.visitProgramMethod(ClassReferenceInitializer.java:309) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.ProgramMethod.accept(ProgramMethod.java:140) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.ProgramClass.methodsAccept(ProgramClass.java:695) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.util.ClassReferenceInitializer.visitProgramClass(ClassReferenceInitializer.java:266) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.ProgramClass.accept(ProgramClass.java:544) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.classfile.ClassPool.classesAccept(ClassPool.java:291) ~[proguard-core-9.0.8.jar:9.0.8]
 [proguard]     at proguard.Initializer.execute(Initializer.java:187) ~[proguard-base-7.2.0.jar:7.2.0]
 [proguard]     at proguard.ProGuard.initialize(ProGuard.java:324) ~[proguard-base-7.2.0.jar:7.2.0]
 [proguard]     at proguard.ProGuard.execute(ProGuard.java:138) ~[proguard-base-7.2.0.jar:7.2.0]
 [proguard]     at proguard.ProGuard.main(ProGuard.java:675) [proguard-base-7.2.0.jar:7.2.0]

Thanks for looking into it. My answer took too long to write, so I didn't see your comment until after.
I'm currently using Afterburner.fx for DI. It's very minimal and works quite well with JavaFX.


Add hints for types export

Exporting types is hard when you have multiple entrypoints. If the consumer's TypeScript configuration supports node16, the types condition should work splendidly. If not, there's a couple ways around it.
1. Map export path to actual files
If you have an export like my-lib/subpath, make sure you have a /subpath.d.ts file. Likewise for my-lib/really/deep/subpath, create a /really/deep/subpath.d.ts file.
2. Declare module
If your package has an ambient file, you can use declare module to achieve the same without needing to create new files. The downside though is that all types are in a single file, and the user needs to understand how ambient types work.
declare module 'my-lib/subpath' {
  export const hello: string
}

Because it's an ambient file, you will need the user to do /// <reference types="my-lib" /> in their own ambient file.
// src/global.d.ts (common names: env, ambient)
/// <reference types="my-lib" />`

It's not recommended to add to compilerOptions.types as that overrides types search. (TODO: needs more explanation)

Ambient files must also be script files, not module files. https://www.typescriptlang.org/docs/handbook/modules.html

In TypeScript, just as in ECMAScript 2015, any file containing a top-level import or export is considered a module. Conversely, a file without any top-level import or export declarations is treated as a script whose contents are available in the global scope (and therefore to modules as well).

Ideally we want to make sure types work in either node16 or not, and we give a hint on the first approach. The second approach is valid and publint needs to check patterns like these to not incorrectly give the hint.

Actually we should not do no1, https://github.com/andrewbranch/example-subpath-exports-ts-compat has some great examples of what to do instead. I'm leaning towards typesVersion instead.

This is really hard to lint, so I'm closing this for now. Maybe it'll be easier to tackle this once we have more TS specific rules in place.


⚠ Bofrost.be has degraded performance

In 226f0d7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1883 ms

Resolved: Bofrost.be performance has improved in d45dc80 after 1 hour, 14 minutes.


BW-1422 - Remove unused POST runs endpoint

I think you should be able to remove CromwellServerConfiguration cromwellConfig; from the RunsApiController now too.


manifest.yml is currently configured for lab-bluemix-cf, but instead needs to be configured for our specific application

Describe the problem
manifest.yml is configured for the lab-bluemix-cf set up during the lecture demo.
Expected behavior
Name and route in the .yml file need to be changed.
Name should be nyu-customer-service-fall2101
Route should be nyu-customer-service-fall2101.ussouth.cf.appdomain.cloud

Should it be nyu-customer-service-fall2021?

Just noticed that I forgot to change the name of the service


[sw, dif_kmac] Add implementation of SHA-3 (blocking only)

Add support for SHA-3 operations to the KMAC DIF. These operations
do not support returning partial results (i.e. they block until the
operation is complete). Support for non-blocking operations will be
added in a future PR.
Note that some aspects of the implementation will need to be
modified when support for XOF operations, such as SHAKE, are added.
I have marked these with 'TODO: XOF:' for now.
Signed-off-by: Michael Munday<EMAIL_ADDRESS>

@tjaychen, @eunchan: I know that we had a discussion about error handling when the SW was racing with the key manager. I think that it got flagged up with Garrett when he was still involved with the project, but I'm not sure that anything else came of it. Do we have any notes about the design decisions we took? (To avoid Michael wasting his time figuring it all out again!)

Finally, do you have any guidance over when kmac.CFG.entropy_ready should be set? Should it be set unconditionally as part of software initialization?

That CSR field was added to let entropy controller inside KMAC prepare the random values used in KMAC operations. Unless this bit is set, KMAC won't send requests to EDN HWIP nor generating pseudo-randon values from internal LFSR.
Wait... I think, This blocks rom_ctrl operations, as no SW loaded at the time. Ah.. I will deal with this in the separate issue ticket.

@tjaychen, @eunchan: I know that we had a discussion about error handling when the SW was racing with the key manager. I think that it got flagged up with Garrett when he was still involved with the project, but I'm not sure that anything else came of it. Do we have any notes about the design decisions we took? (To avoid Michael wasting his time figuring it all out again!)

@moidx @cfrantz
at the time we discussed this, we basically said that software would need to place an exclusive lock over the whole key manager / associated kmac collection.
so for example, if software wants to make use of the key manager (thus knowing this would involved kmac), but kmac is actually being used by something else, it would need to wait on the operation.  I think the kmac documentation also has a section that touches on this.. about how the keymagr / kmac operation is atomic, and while the hardware has control over the hardware, software control of kmac would be rejected / error'd.
Does this answer your question?


Mangatoon chapters aren't loading

Source information
Mangatoon
Source language
English
Steps to reproduce

Select source 'mangatoon'.
Open a comic

Expected behavior
All chapters of the manga should have loaded.
Actual behavior
Only the first few and last chapters are loaded

Mihon/Tachiyomi version
0.17.0
Android version
10
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

The hidden chapters are not free to read. Try signing in into WebView, if that does not work you should create a feature request for reading paid chapters.

Well, taking example of the screenshot I've shared (school hunk is a girl). The free chapters are much more than 6.
It shows only 9 chapters for EVERY series (first 6 and last 3). Just a couple of months back, it showed the entire chapter list just fine..
I've tried logging in to see if the issue is cleared, but it still remains same. Unfortunately, I haven't bought any paid chapters so, I can't check that.

Currently it shows chapter 1-9 in the extension. Since the extension is not using the same interface as the official app it is limited to what you can see from a regular browser. From WebView you can see chapter 10 and onwards are not viewable (see screenshot below).
I suspect the changing amount of visible chapters is due to various promotions or events going around.
After logging into the WebView make sure you refresh the chapter list and compare with what you have access to in the WebView. They should be the same. If additional chapters do show up, some sort of login prompt could be added to the extension. If they still don't work after logging in, the extension would need to be changed so it acts like the official app, if possible. Either way, this would be a feature request. Please open one or the other after investigating.


Download image has height zero in Firefox

@forivall I'm in the middle of fixing this right now. Thanks! ❤

Thanks again!


SWDEV-314867 - Fix clang missing issue in cuda docker

Cuda dockers doesn't contain clang. The dependence on clang
will fail catch2 building. Catch2 building actually doesn't
need clang. Remove clang dependence from catch2 cmake file.
Change-Id: I8fd76e99d27ce4f5769baffae0608dd1cf0f4188

!psdb

!hip


 But it looks like the problem is inside the Go compiler. Nevertheless I'll try to investigate. Could you recommend an instruction how to run a PPC64LE Ubuntu image in KVM?

You should be able to able to use the 21.04 ISO and run it with
qemu-system-ppc64le -M pseries -m 4G -hda ubuntu-21.04-live-server-ppc64el.iso

Yeah, I also saw similar command on stack overflow, but it does not work for 21.04 (qemu just unexpectedly exits while the boot) on my machine. Meanwhile will try 20.04, instead.

@paulmenzel : Which exactly tool are you trying to build?

I am testing the coreboot toolchain on ppc64le. The sample configuration for cbnt config/config.ocp_deltalake_cbnt fails to build.
To reproduce, I just changed to the repository, and executed the lines from .circleci/config.yml.
$ go version
go version go1.16.2 linux/ppc64le
$ apt-cache policy golang-go
golang-go:
  Installed: 2:1.16~0ubuntu1
  Candidate: 2:1.16~0ubuntu1
  Version table:
 *** 2:1.16~0ubuntu1 500
        500 http://de.ports.ubuntu.com/ubuntu-ports hirsute/main ppc64el Packages
        100 /var/lib/dpkg/status

@paulmenzel : Unfortunately, it takes too much time to reproduce the problem (because 21.04 does not work, and on other versions the problem seems to be non-reproducible). Can we wait until https://github.com/golang/go/issues/46858 fix will be merged? (I guess it will be in Go1.16.7)

Yes, we can definitely wait. Thank you very much for looking into this so quickly.

Also fixed by Michael’s Linux patch.
As the problem is not in the converged-security-suite, I am closing the issue.


KYLIN-4634 Fail to specify cube in model of low priority to query

Proposed changes
bug fix of KYLIN-4634, add model force choosing logic.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[x] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

LGTM


feat: [WIP] Delete Operation

Description
This is a full implementation of the Delta Delete Command
The overall functionality is implemented however it's not fully production ready.
TODO

#1175 Prevents pruning when only partition columns are specified in the predicate
I want to clean up the find_files implementation. Maybe ExecutionPlanVisitor can help achieve this.
Allow users to provide a WriterConfig

Related Issue(s)

Provides Delete for Datafusion #832

Documentation

I want to continue to push this forward to have a MVP for deletion. My biggest issue with the current implementation is  the find_files function since it has iterate through each file in series to determine if it contains a record.
If Datafusion supported a method like input_file_name then the multiple scans can be performed in parallel and would speed up the operation.
Requires further changes when #1303 is merged.
Currently there is an optimization for when the columns in the expression are only partitions columns. I may disable it until all pruning issues are resolved.

Hi @wjones127 @roeap
I've made the requested changes. Let me know if it is good to merge or any additional concerns.


NIFI-13496 Fix SNMP Integration Test Failures

Summary
NIFI-13946 Fixes SNMP integration tests that failed following upgrades from SNMP4J version 2 to version 3.
Changes include setting <IP_ADDRESS> as the listen address for ListenTrapSNMP, aligning with existing behavior. Additional changes include removing SHA and MD5 protocols from the integration test class for SNMP Version 3.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for the test fixes @exceptionfactory!
I suggest also removing the unsupported MD5 and SHA items from the allowable values of SNMP Authentication Protocol property. It can be done in a separate jira/PR if the current scope is the test fixes only.

Thanks for the test fixes @exceptionfactory!
I suggest also removing the unsupported MD5 and SHA items from the allowable values of SNMP Authentication Protocol property. It can be done in a separate jira/PR if the current scope is the test fixes only.

Thanks @turcsanyip, addressing those in a separate Jira issue would be good.


Suggestion: automatic type conversion on tags

For example, this fails:
            [BosunTag]
            public readonly int Response;

but this works fine:
            [BosunTag]
            public readonly string Response;

It seems like the library could perform the string conversion itself?

+1 for this

I can't allow arbitrary types because it's hard to enforce that the way values serialize won't change over time, which violates the strict immutability requirements the library enforces. It could work for primitives, but I'm hesitant to encourage people to use numeric types for tag values because I feel like it encourages an unbounded list of possible values.
However, what I really do want to encourage people to use are enums. So I've added support for enum fields being marked with the BosunTag attribute.
You can now do this:
    public enum SomeEnum
    {
        One = 1,
        Two = 2,
        Three = 3,
        Four = 4,
    }

    public class EnumCounter : Counter
    {
        [BosunTag] public readonly SomeEnum Value;

        public EnumCounter(SomeEnum val)
        {
            Value = val;
        }
    }

If you really want to use an int, there's nothing stopping you from calling .ToString() on it. I just don't want to encourage using numbers without it giving you some pause. This seems like a fair compromise to me.


chore: update deps

if #136 is landed then I can add the deps for the argument parsing tests to ./test/deps.ts


Build binary with ledger support

Description/Reasoning
We need GCC support in the container builds to support ledger, this is complex because we need a separate linker for each OS.
Current Behaviour
We don't support ledger
Expected Behaviour
Steps to reproduce (for bugs)
Relevant Logs or Files

Linking #1126


Add new raw parser

Read multiple registers and pass them through as array without
processing. Useful when you need to read multiple registers atomically.
For my usecase, I wanted to extract the inverter date time as a single
register to parse later using a jinja2 template.

I integrated your changes into my integration overhaul. Hope you don't mind. 🥂

@davidrapan No problem. I'll play around with your integration later in the week.
Looks very interesting. Good to see you using the async version of pysolarmanv5 too. I'm open to PRs too if you want to upstream your modifications too.

@jmccrohan Since your last update (i.e. where there was added resending last request) I'm adjusting only really two minor things:

omitting exception raise from the 'reconnect' method and just log it (as it is then risen in the task and not really catched properly)
adding except for TimeoutError inside '_send_receive_v5_frame' method before it logs it as an exception. Cause I view this behavior as somewhat expected given the fact how is the Stick Logger implemented.


[plugin-api-docs] Support OpenAPI 3.1

Feature Suggestion
Support rendering openapi: 3.1.x API definitions in Backstage. OpenAPI 3.1.0 was released as stable in the beginning of the year.
Possible Implementation
This likely depends on swagger-ui supporting OpenAPI 3.1, which it doesn't yet https://github.com/swagger-api/swagger-ui/issues/5891, but it might be a good preparation to update to swagger-ui v4 already as only v4 will get OpenAPI 3.1 support.
Context
Current backstage view when looking at an OpenAPI 3.1 schema:

Makes sense! Is this something you might be able to work on?

I see that we depend on "swagger-ui-react": "^4.0.0-rc.3" in the API plugin. Latest version of that as of this time is 4.1.0.

Yep, would make sense to update to the latest stable release. Opening that up to contributions in case anyone wants to beat us to it :grin:

So,
Hey  - since it'd be rather important to me (and the company) to get some movement on the OAS 3.1 front going, I've spent some time looking into this. The news is a bit bleak though:

Backstage depends on swagger-ui-react (see here
swagger-ui-react currently does not support OAS 3.1, hence we get no API explorer for specs using that scheme version
The swagger authors decided to work on a new version of their editor first, which will resolve the issue

This unfortunately means either one of two things:

Sit and wait.
Replace the dependency with something like OpenAPI Explorer. I've no opinion on this package myself (and I am not associated).

Anyway, this issue therefore should probably no be a good first contribution :wink:.
Cheers :heart:

(I also should've realized that @johanneswuerbach mentioned most of this in the original issue description, mea culpa :facepalm:)

In an effort to provide a tiny bit more substance, here is a branch where I switched out swagger-ui-react with openapi-explorer.
The result needs styling, obviously, but works rather nice, even with OAS 3.1:

Still relevant 👍

not actively, as I don't really have time myself. Switching out the OpenAPI Explorer is easy, but I am no CSS magician, so it'd look like :hankey:.

Personal opinion: Tests in Backstage are intended for React components making openapi-explorer hard to test since it is a 'Lit' component (Google.) I was able to integrate it and make it look good but I was unable to fiddle with it enough to get all tests passing. Swagger.io intends to have OpenAPI3.1 compatibility in swagger-ui this Quarter. I think we should wait a few weeks and implement the upcoming version of swagger-ui.
https://swagger.io/blog/swagger-support-for-openapi-3-0-and-openapi-3-1/

Swagger UI and Swagger Client
Rendering for OpenAPI 3.1 will soon follow as part of our [Swagger UI](https://github.com/swagger-api/swagger-ui) enhancements. In a nutshell, the ability to process and render OpenAPI 3.1 definitions/documents within Swagger UI will be enabled by the integration of [ApiDOM](https://github.com/swagger-api/apidom) with [Swagger Client](https://github.com/swagger-api/swagger-js).

We’re expecting to have this completed in Q1 2023 which will bring the rendering capability also into our Swagger Editor tool.

My implementation is here if anyone would like to do something with it:
https://github.com/backstage/backstage/blob/88443dca751eacf7ba49c64a753908afd5c8fd7c/plugins/api-docs/src/components/OpenApiDefinitionWidget/OpenApiDefinition.tsx#L27

nudging to appease the stalebot

https://github.com/swagger-api/swagger-ui/labels/version%3A 5.x
and https://github.com/swagger-api/swagger-ui/issues/8684 to watch for beta

FYI: swagger-ui v5.0.0 was released 2h ago.

In case you didn't see it yet, the linked PR will resolve this issue. It contains two 3.1.0 examples as well. A release of the type package was not necessary, they are still compatible.
If reviews go through, it should be part of next week's main release.


Added note for those installing Windows 11 to bypass internet connection screen

Currently, to bypass windows 11's "Let's connect you to a network" screen, you'll need to run the command within the note.

It is documented here with other windows specific tips https://github.com/utmapp/mac.getutm.app/blob/main/_virtual_machines/windows-11-arm.md


Confirm how this library handles 404 from FCM

Describe the feature you would like to see
Email sent from Firebase today:

We're writing to inform you that we will be garbage collecting all expired Firebase Cloud Messaging registration tokens and topic subscriptions starting May 15, 2024.
What you need to know
Starting May 15, 2024, the stale tokens and topic subscriptions for devices, which have not been connected to FCM in over 270 days, will be considered as expired and invalid. If a request is sent to an invalid token, it will be rejected with a 404 (UNREGISTERED) error.
Regarding topic sends or notification campaigns, it is possible that you may observe a decrease in the time taken for fanouts to complete. This could be attributed to the removal of expired subscriptions and a reduction in the number of messages sent.
This process will help improve fanout performance for your campaigns and identify the undeliverable registration tokens.
What you need to do
We recommend you to confirm that your service handles 404 error codes from FCM correctly. Please delete your record of any tokens with a 404 response code because they will not be valid again.

I'm currently catching the NotFound errors to detect invalid tokens:
try {
    $this->messaging->send($message);
} catch (\Kreait\Firebase\Exception\Messaging\NotFound $e) {
    // Purge these push tokens from the DB
}

Can someone please confirm if this will be impacted by the just announced Firebase change? Or will a change be needed to handle these new 404 errors?

I don't know what you mean with "this", but I am confident that the new 404s will be indistinguishable from the old ones 🤞🏻


Set scalac and javac source version for all sbt subprojects

Description
Some of the sbt subprojects are built using the source version of the java version used to compile the project.
This creates class files with versions greater than 52.0, which will fail to run on JVM 1.8, which is typically used to run Spark.
We fix this by setting the scalac and javac source version explicitly in each subproject.

How was this patch tested?
I've tested that the updated configuration works by running
delta$ build/sbt clean package
delta$ find . -type f -name "*class" | xargs file -b | sort | uniq
compiled Java class data, version 52.0 (Java 1.8)

Does this PR introduce any user-facing changes?
No

Thank you @jkylling for the PR. Could you please look at the failures in doc generation?

Looks like this issue https://github.com/sbt/sbt/issues/355

Hi @jkylling, can you email me or dm me on delta-users slack your public email address as a Delta Lake contributor?
<EMAIL_ADDRESS>


ColliderInstance transforms don't affect normals and triangle data

ColliderInstances' transforms only take the intersection point into account but not the normals since it's not implemented yet. Triangle data comes directly from Colliders, so either a new or static array should be used.

Normals are now transformed as of 09b8202


Remove usage of deprecated skimage.filter module

Pretty self explanatory...

Coverage remained the same at 49.8% when pulling 0e105d17555994b33abdda806a1d09fbd4f1efab on jni:remove-skimage-filter into cbb3ac64638b04904686232edf3adc1cab6de03f on microscopium:master.


Need help in extracting parameters using CPH extension

I am having an internal application where I am trying to automate the testing using CPH extension. It handles few parameters dynamically.
From first request,  we are extracting few parameters and use those in the subsequent request.
The hurdle we are facing is, we couldn't extract the values of the parameters. And also some help on how to calculate the regex would help.
Attached the demo request for reference as uploading was not allowed.
your help is highly appreciated.

![MicrosoftTeams-image (2)](https://user-images.githubusercontent.com/99052624/191356588-cfe2ea01-bbd2-4cbd-879e-008ac277e047.png)
![MicrosoftTeams-image (3)](https://user-images.githubusercontent.com/99052624/191356596-c9ae494c-0d78-4cc3-98d8-62fe133966db.png)

Hello,
I'll see if I can have a closer look soon - meanwhile, are you able to share the regular expressions that you're trying to use?
On Tue, Sep 20, 2022, at 15:19, pavithraasok wrote:

I am having an internal application where I am trying to automate the testing using CPH extension. It handles few parameters dynamically.
From first request, we are extracting few parameters and use those in the subsequent request.
The hurdle we are facing is, we couldn't extract the values of the parameters. And also some help on how to calculate the regex would help.
Attached the demo request for reference as uploading was not allowed.
your help is highly appreciated.
CPH1 https://user-images.githubusercontent.com/99052624/191356577-2d92d281-3696-4ff3-8987-66b26d154d5b.png
CPH2 https://user-images.githubusercontent.com/99052624/191356582-47f52749-97db-4083-ac62-7c087b5af429.png

—
Reply to this email directly, view it on GitHub https://github.com/elespike/burp-cph/issues/53, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADSG6H2RUKKNC3MNUW3ZV6TV7IL5VANCNFSM6AAAAAAQRNO47E.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


sphinx-autobuild can't find the correct resources directory

Background: I'm working on an RTFM project and was able to run sphinx-autobuild until just recently.
Specific issue: When running make livehtml on Mac OS X 10.11.1, I now throw the following error:
-bash: /usr/local/bin/sphinx-autobuild: /usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/Resour: bad interpreter: No such file or directory
Which is likely the result of my upgrading to python 2.7.10 and running brew clean a few days ago in an attempt to reclaim some disk space. As far as I can tell, sphinx-autobuild is the only program that's been affected.
I've tried reinstalling sphinx, as well as the version of python I manage with brew but to no avail. I've also done a decent amount of searching online but I can't seem to pinpoint where the old and incomplete variable is being held.
Any help would be appreciated.
thx

Update...
I restored the python 2.7.6 install from a TimeMachine backup and am able to build again. Seems like the issue is indeed related to the python upgrade + brew clean operation.


docs: contributing: editors: vscode: Explain how to venv

https://intel.github.io/dffml/main/contributing/editors/vscode.html

what I understand from this request is that we have to add automative venv initialization in the json file.
Is this correct and shall I proceed with it?

@pdxjohnny please provide some insights to the issue here

sir I have made changes for the same but I am not able to find where the lint is failing in github actions

@pdxjohnny please provide some extra information over this

@pdxjohnny Cqn you please assign this to me.


RenderManager: Replace None by Zero.

None is a reserved keyword in X11.

@Armada651 Do you have a citation for this? Is None defined as a macro somewhere in X11? Thanks!

Here you go, you can find it on this page:
https://refspecs.linuxfoundation.org/LSB_1.3.0/gLSB/gLSB/libx11-ddefs.html

Thanks!
Unfortunately, it's not possible for us to defend against every possible macro definition in the world.
If you're including X11/X.h and also osvr/RenderKit/RenderManager.h in your code, you can work around the X11 None definition with the following code:
#include <X11/X.h> // defines None = 0L

// Temporarily undefine the None macro so it doesn't conflict with
// osvr::RenderKit::ConstructionParameters::Display_Rotation::None
#pragma push_macro("None")
#undef None

#include <osvr/RenderKit/RenderManager.h>

// Restore X11's definition of None macro
#pragma push_macro("None")

// Anywhere after this point, None == 0L again.

The #pragma push_macro("None") works in GCC, Clang, and MSVC.

I understand you cannot defend against every macro definition, but I think it's useful to take into account macros in major headers for the operating systems you support. This is a small change that will save Linux developers a lot of headaches.

Also the problem is that I need to include RenderManager.h in the header of my class, which causes it to be included everywhere and ultimately it's going to get included somewhere together with X.h.
The reason I'm including RenderManager.h in my class header is because I can't forward declare the typedef structs like RenderInfo, because they're anonymous. If we don't want to defend against major operating system headers, then the only proper solution is to give all your structs full names so we can forward declare them.

This is the sort of thing I thought that namespaces were supposed to fix.  It looks like the pull request does all the work needed to avoid the problem and it doesn't seem to cause any other problems, so I'm going to say "thank you for submitting a fix" and merge it.  It makes me wonder if we should make an issue to find a better way to hide all of this that doesn't make clients forward-declare things in their code.


Can't build 0.5.4 release or git master due to error in ice module

Building older releases works without issues but I am unable to build the 0.5.4 release or git master:
CC [M]  build-x86_64/modules/ice/ice.o modules/ice/ice.c: In function 'call_gather_handler': modules/ice/ice.c:104:2: warning: implicit declaration of function 'icem_cand_redund_elim'; did you mean 'ice_cand_encode'? [-Wimplicit-function-declaratio ]   icem_cand_redund_elim(m->icem);   ^~~~~~~~~~~~~~~~~~~~~   ice_cand_encode modules/ice/ice.c:104:2: warning: nested extern declaration of 'icem_cand_redund_elim' [-Wnested-externs] modules/ice/ice.c:106:8: warning: implicit declaration of function 'icem_comps_set_default_cand'; did you mean 'icem_lite_set_default_candidates'? [-Wimplicit-function-declaration]   err = icem_comps_set_default_cand(m->icem);         ^~~~~~~~~~~~~~~~~~~~~~~~~~~         icem_lite_set_default_candidates modules/ice/ice.c:106:8: warning: nested extern declaration of 'icem_comps_set_default_cand' [-Wnested-externs] modules/ice/ice.c: In function 'stun_resp_handler': modules/ice/ice.c:135:10: warning: implicit declaration of function 'icem_cand_find'; did you mean 'icem_cand_add'? [-Wimplicit-function-declaration]   lcand = icem_cand_find(icem_lcandl(m->icem), comp->id, NULL);           ^~~~~~~~~~~~~~           icem_cand_add modules/ice/ice.c:135:10: warning: nested extern declaration of 'icem_cand_find' [-Wnested-externs] modules/ice/ice.c:135:8: warning: assignment makes pointer from integer without a cast [-Wint-conversion]   lcand = icem_cand_find(icem_lcandl(m->icem), comp->id, NULL);         ^ modules/ice/ice.c:148:8: warning: implicit declaration of function 'icem_lcand_add'; did you mean 'icem_cand_add'? [-Wimplicit-function-declaration]   err = icem_lcand_add(m->icem, icem_lcand_base(lcand),         ^~~~~~~~~~~~~~         icem_cand_add modules/ice/ice.c:148:8: warning: nested extern declaration of 'icem_lcand_ad ' [-Wnested-externs] modules/ice/ice.c:148:32: warning: implicit declaration of function 'icem_lcand_base'; did you mean 'icem_cand_add'? [-Wimplicit-function-declaration]   err = icem_lcand_add(m->icem, icem_lcand_base(lcand),                                 ^~~~~~~~~~~~~~~                                 icem_cand_add modules/ice/ice.c:148:32: warning: nested extern declaration of 'icem_lcand_base' [-Wnested-externs] modules/ice/ice.c: In function 'send_binding_request': modules/ice/ice.c:167:37: warning: implicit declaration of function 'icem_stu '; did you mean 'inet_pton'? [-Wimplicit-function-declaration]   err = stun_request(&comp->ct_gath, icem_stun(m->icem), IPPROTO_UDP,                                      ^~~~~~~~~                                      inet_pton modules/ice/ice.c:167:37: warning: nested extern declaration of 'icem_stun' [-Wnested-externs] modules/ice/ice.c:167:37: warning: passing argument 2 of 'stun_request' makes pointer from integer without a cast [-Wint-conversion] In file included from /usr/include/re/re.h:51:0,                  from modules/ice/ice.c:10: /usr/include/re/re_stun.h:187:6: note: expected 'struct stun *' but argument is of type 'int'  int  stun_request(struct stun_ctrans **ctp, struct stun *stun, int proto,       ^~~~~~~~~~~~ modules/ice/ice.c: In function 'turnc_handler': modules/ice/ice.c:195:3: warning: implicit declaration of function 'icem_set_turn_client'; did you mean 'video_set_orient'? [-Wimplicit-function-declaratio ]    icem_set_turn_client(m->icem, comp->id, NULL);    ^~~~~~~~~~~~~~~~~~~~    video_set_orient modules/ice/ice.c:195:3: warning: nested extern declaration of 'icem_set_turn_client' [-Wnested-externs] modules/ice/ice.c:216:8: warning: assignment makes pointer from integer without a cast [-Wint-conversion]   lcand = icem_cand_find(icem_lcandl(m->icem), comp->id, NULL);         ^ modules/ice/ice.c:220:21: warning: implicit declaration of function 'icem_lcand_addr'; did you mean 'icem_cand_add'? [-Wimplicit-function-declaration]   if (!sa_cmp(relay, icem_lcand_addr(icem_lcand_base(lcand)), SA_ALL)) {                      ^~~~~~~~~~~~~~~                      icem_cand_add modules/ice/ice.c:220:21: warning: nested extern declaration of 'icem_lcand_addr' [-Wnested-externs] modules/ice/ice.c:220:21: warning: passing argument 2 of 'sa_cmp' makes pointer from integer without a cast [-Wint-conversion] In file included from /usr/include/re/re.h:20:0,                  from modules/ice/ice.c:10: /usr/include/re/re_sa.h:56:10: note: expected 'const struct sa *' but argument is of type 'int'  bool     sa_cmp(const struct sa *l, const struct sa *r, int flag);           ^~~~~~ modules/ice/ice.c: In function 'cand_gather_relayed': modules/ice/ice.c:245:38: warning: passing argument 1 of 'stun_conf' makes pointer from integer without a cast [-Wint-conversion]   err = turnc_alloc(&turnc, stun_conf(icem_stun(m->icem)),                                       ^~~~~~~~~ In file included from /usr/include/re/re.h:51:0,                  from modules/ice/ice.c:10: /usr/include/re/re_stun.h:179:19: note: expected 'struct stun *' but argument is of type 'int'  struct stun_conf *stun_conf(struct stun *stun);                    ^~~~~~~~~ modules/ice/ice.c: At top level: modules/ice/ice.c:293:12: error: conflicting types for 'icem_gather_srflx'  static int icem_gather_srflx(struct mnat_media *m)             ^~~~~~~~~~~~~~~~~ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:77:6: note: previous declaration of 'icem_gather_srflx' was here  int  icem_gather_srflx(struct icem *icem, const struct sa *stun_srv);       ^~~~~~~~~~~~~~~~~ modules/ice/ice.c:302:12: error: conflicting types for 'icem_gather_relay'  static int icem_gather_relay(struct mnat_media *m,             ^~~~~~~~~~~~~~~~~ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:78:6: note: previous declaration of 'icem_gather_relay' was here  int  icem_gather_relay(struct icem *icem, const struct sa *stun_srv,       ^~~~~~~~~~~~~~~~~ modules/ice/ice.c: In function 'ice_start': modules/ice/ice.c:763:6: warning: implicit declaration of function 'ice_candpair_set_states'; did you mean 'ice_cand_attr_decode'? [-Wimplicit-function-declaration]       ice_candpair_set_states(m->icem);       ^~~~~~~~~~~~~~~~~~~~~~~       ice_cand_attr_decode modules/ice/ice.c:763:6: warning: nested extern declaration of 'ice_candpair_set_states' [-Wnested-externs] modules/ice/ice.c: In function 'media_alloc': modules/ice/ice.c:799:29: error: incompatible type for argument 2 of 'icem_alloc'   err = icem_alloc(&m->icem, ice.mode, sess->offerer,                              ^~~ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:71:6: note: expected 'struct ice *' but argument is of type 'enum ice_mode'  int  icem_alloc(struct icem **icemp, struct ice *ice, int proto, int layer,       ^~~~~~~~~~ modules/ice/ice.c:801:5: warning: passing argument 6 of 'icem_alloc' makes pointer from integer without a cast [-Wint-conversion]      sess->tiebrk, sess->lufrag, sess->lpwd,      ^~~~ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:71:6: note: expected 'void (*)(int,  _Bool,  void *)' but argument is of type 'uint64_t {aka long unsigned int}'  int  icem_alloc(struct icem **icemp, struct ice *ice, int proto, int layer,       ^~~~~~~~~~ modules/ice/ice.c:799:8: error: too many arguments to function 'icem_alloc'   err = icem_alloc(&m->icem, ice.mode, sess->offerer,         ^~~~~~~~~~ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:71:6: note: declared here  int  icem_alloc(struct icem **icemp, struct ice *ice, int proto, int layer,       ^~~~~~~~~~ modules/ice/ice.c:806:2: warning: implicit declaration of function 'icem_conf'; did you mean 'ice_conf'? [-Wimplicit-function-declaration]   icem_conf(m->icem)->nom   = ice.nom;   ^~~~~~~~~   ice_conf modules/ice/ice.c:806:2: warning: nested extern declaration of 'icem_conf' [-Wnested-externs] modules/ice/ice.c:806:20: error: invalid type argument of '->' (have 'int')   icem_conf(m->icem)->nom   = ice.nom;                     ^~ modules/ice/ice.c:807:20: error: invalid type argument of '->' (have 'int')   icem_conf(m->icem)->debug = ice.debug;                     ^~ modules/ice/ice.c: In function 'sdp_attr_handler': modules/ice/ice.c:841:24: warning: passing argument 1 of 'ice_sdp_decode' from incompatible pointer type [-Wincompatible-pointer-types]    (void)ice_sdp_decode(m->icem, name, value);                         ^ In file included from /usr/include/re/re.h:33:0,                  from modules/ice/ice.c:10: /usr/include/re/re_ice.h:62:6: note: expected 'struct ice *' but argument is of type 'struct icem *'  int  ice_sdp_decode(struct ice *ice, const char *name, const char *value);       ^~~~~~~~~~~~~~ make: *** [mk/mod.mk:44: build-x86_64/modules/ice/ice.o] Error 1

unfortunately I had to break the ICE api for some refactoring.
baresip 0.5.4 -> need libre 0.5.4
baresip git -> need libre git
/Alfred

Ah, ok - thanks!


IZE-592 start ecs task

Change:
added ize start <app_name> command
Test:

Codecov Report

Merging #499 (3a84297) into main (73b6f12) will decrease coverage by 0.40%.
The diff coverage is 13.29%.

@@            Coverage Diff             @@
##             main     #499      +/-   ##
==========================================
- Coverage   31.86%   31.45%   -0.41%
==========================================
  Files          60       61       +1
  Lines        7727     7897     +170
==========================================
+ Hits         2462     2484      +22
- Misses       5028     5175     +147
- Partials      237      238       +1

Impacted Files
Coverage Δ

internal/config/config.go
1.37% <0.00%> (ø)

internal/commands/start.go
10.30% <10.30%> (ø)

internal/commands/ize.go
67.76% <100.00%> (+0.26%)
:arrow_up:

internal/commands/logs.go
70.70% <100.00%> (+1.23%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Don't swallow unexpected exceptions in basic transport

The twisted transport is required to handle exceptions with a callback, but
baseic is just urllib and we can expose decent errors to users.

Per #12 I should be able to review and provide feedback shortly.  Thanks for the PR!

Reviewed this with the team and we all agree with the direction here.  This change will definitely make bugs easier to catch for users in the future.
I left some feedback with a couple of minor changes for you to review when you get a chance.

Done, mostly. I couldn't help using a chained comparison even though it looks a little weird with the not -- I usually find the fact that the comparison looks like a range to make it easier to understand the logic.
Happy to change it to make it use your requested or instead of not.

Wouldn't have thought to write it that way, but I like it!  Tested with both HTTP and non-HTTP exceptions and I think this is ready to merge.
Tagging @cpg1111 for +1

I'll submit a new PR to bump the version of the package so pip can take advantage of these fixes. Thanks again for the PRs @quodlibetor!


Fix compilation errors that occurs using Foundry

Motivation
forge test shows up the following errors because of the Foundry update https://github.com/foundry-rs/foundry/pull/3007
Failing tests:
Encountered 1 failing test in test/foundry/FulfillAdvancedOrder.t.sol:FulfillAdvancedOrder
[FAIL. Reason: Setup failed: The path "optimized-out/ConduitController.sol/ConduitController.json" is not allowed to be accessed for read operations.] setUp() (gas: 0)

Encountered 1 failing test in test/foundry/FulfillAdvancedOrderCriteria.t.sol:FulfillAdvancedOrderCriteria
[FAIL. Reason: Setup failed: The path "optimized-out/ConduitController.sol/ConduitController.json" is not allowed to be accessed for read operations.] setUp() (gas: 0)

...

It also shows up the following warnings
warning: Unknown section [default] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run `forge config --fix`.
warning: Unknown section [lite] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.lite] instead or run `forge config --fix`.

...

Solution

Add fs_permission to allow file access
Run forge config --fix

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (102a157) compared to base (dfce06d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##              main      #648    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           45        25    -20
  Lines         1917       929   -988
  Branches       322       147   -175
==========================================
- Hits          1917       929   -988

Flag
Coverage Δ

production
100.00% <ø> (ø)

reference
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

reference/lib/ReferenceTokenTransferrer.sol

reference/lib/ReferenceConsiderationBase.sol

reference/lib/ReferenceZoneInteraction.sol

reference/conduit/ReferenceConduit.sol

reference/ReferenceConsideration.sol

reference/lib/ReferenceExecutor.sol

reference/lib/ReferenceAssertions.sol

reference/lib/ReferenceOrderValidator.sol

reference/lib/ReferenceAmountDeriver.sol

reference/lib/ReferenceOrderFulfiller.sol

... and 10 more

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

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

Added additional commits to resolve the following CI fail:
[FAIL. Reason: Chain ID must be less than 2^64 Counterexample: calldata=0xf25832fb0000000000000000000000000000000000000000000000010000000000000000, args=[18446744073709551616]]

See also about this fail: https://github.com/foundry-rs/foundry/pull/3109

Just seeing this thanks! Fixing as part of https://github.com/ProjectOpenSea/seaport/pull/654

@Slokh Okay, but your PR does not include all the changes in my PR: forge config —fix

Hm yeah you're right, sorry focused on the chain id fix.


sails.io injection error

There are some problem in the frontend injection.
These are the errors showed in the browser's console:
Uncaught Error: [$injector:modulerr] Failed to instantiate module frontend due to:
Error: [$injector:modulerr] Failed to instantiate module frontend.core due to:
Error: [$injector:modulerr] Failed to instantiate module frontend.core.dependencies due to:
Error: [$injector:modulerr] Failed to instantiate module sails.io due to:
Error: [$injector:nomod] Module 'sails.io' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

seems related to sails.io.
Manually running bower install won't help

I met this issue also,

Hmm, that's weird. Do you see that sails.io.js file is included to sources?

@tarlepp thank for your answer, I think it link to a ngSails issue:
https://github.com/balderdashy/angularSails/issues/63

Same problem here, is there any workaround ?

Hi,
For a quick and temp fix, replace the last line of bower_components/angularSails/dist/ngsails.io.js
})( window, angular );
by
}));

Main reason is that I'm using master version of angularSails https://github.com/tarlepp/angular-sailsjs-boilerplate/blob/master/frontend%2Fbower.json#L41
So the proper fix is to change that to latest stable.


Confusion about heads of graphs

In srlSentence of CluProcessors there's a line roots ++= predicateIndexes and afterwards, the edges are calculated.  There is an example sentence in which the predicateIndexes are 1, 5, 6 and the edges are
1 -> 0
5 -> 4
6 -> 7
6 -> 5

Is 5 still supposed to be a root?  Maybe it is a predicate, but it is also the destination of an edge.  If it is a root, it messes up Eidos serialization because the roots aren't tracked separately and it otherwise looks like it's in the middle of a something, the source of an edge.  We wouldn't know that it's a root unless perhaps all sources were roots.
@MihaiSurdeanu, can you clarify the semantics?

Good find @kwalcock !
No, in this example 5 is not supposed to be a root. Roots are nodes that never appear on the right hand side of these edges.

A PR is on the way.  It sure seems like roots = edges.sources -- edges.destinations, which could be calculated in the constructor (or provided optionally) rather than passed to it.  I'll avoid changing the interface, though.

See #523.  However, there may be an additional problem.

I merged that PR. What additional problem?

Now I'm not sure where I wrote it down.  In DirectedGraphIndex.toDirectedGraph, the old roots shouldn't be used with the new edges.  I added a check in the DirectedGraph constructor and several things are creating directed graphs that don't fit this definition of roots.
  {
    val sources = edges.map(_.source).toSet
    val destinations = edges.map(_.destination).toSet
    val actualRoots = sources -- destinations

    if (actualRoots != roots)
      println("It went wrong!")
  }

I think I remember seeing this in some syntactic trees as well.
I think we should be lenient and adjust the actual roots in the created DG
to be correct ones.
On Wed, Jul 7, 2021 at 6:08 PM Keith Alcock @.***>
wrote:

Now I'm not sure where I wrote it down. In
DirectedGraphIndex.toDirectedGraph, the old roots shouldn't be used with
the new edges. I added a check in the DirectedGraph constructor and several
things are creating directed graphs that don't fit this definition of roots.
{
val sources = edges.map(.source).toSet
val destinations = edges.map(.destination).toSet
val actualRoots = sources -- destinations
if (actualRoots != roots)
  println("It went wrong!")

}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/522#issuecomment-875685935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TXOXXWXJFAPFX3U4LDTWRUYLANCNFSM473G5NDQ
.

Regarding my comment above, I've got an open window from yesterday where I had written it down and will press the comment button.
If the roots need to be double checked each time anyway, should they just be removed from the DirectedGraph case class constructor?  I'm not sure whose code that would break.  I've turned them into a var and am replacing them with the calculated value to see what breaks or fixes.

Fair point. I think they can be calculated on the fly, which should make
the constructor more robust.
On Wed, Jul 7, 2021 at 6:50 PM Keith Alcock @.***>
wrote:

Regarding my comment above, I've got an open window from yesterday where I
had written it down and will press the comment button.
If the roots need to be double checked each time anyway, should they just
be removed from the DirectedGraph case class constructor? I'm not sure
whose code that would break. I've turned them into a var and am replacing
them with the calculated value to see what breaks or fixes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/522#issuecomment-875719620,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TR5ICCQKEOCRYYNK53TWRZVXANCNFSM473G5NDQ
.

So far, fixing it in DirectedGraphIndex has solved the problems in Eidos.  It looks like DirectedGraphIndex.removeEdge and addEdge are being called without either of them updating the roots.  I should probably change those so that the class is consistent.  The DirectedGraph could probably stay the same then unless performance should be sacrificed for the correctness guarantee.  I can't judge that well.

Thanks! And good catches!
On July 7, 2021 at 7:40:38 PM, Keith Alcock @.***)
wrote:
So far, fixing it in DirectedGraphIndex has solved the problems in Eidos.
It looks like DirectedGraphIndex.removeEdge and addEdge are being called
without either of them updating the roots. I should probably change those
so that the class is consistent. The DirectedGraph could probably stay the
same then unless performance should be sacrificed for the correctness
guarantee. I can't judge that well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/522#issuecomment-875757449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TSUS2MBYGOHLR7XEBLTWR7QNANCNFSM473G5NDQ
.

The code above, in which a root cannot be a destination of an edge, does not especially address loops.  In one test document so far, FastNLPProcessor.parseWithStanford produces an edge 6 -> 6 with root of 6 for a GraphMap.UNIVERSAL_ENHANCED.  Luckily, this one isn't causing a problem with Eidos.  Now I observe other files are turning up additional loops.  One has a graph which no edges, but one root of 0.  I've made some minimal changes in a PR and am making sure that they at least solve the Eidos problem.  It doesn't unnecessarily "correct" these other situations.

Thanks!
Note that cycles are legal for both SRL and syntactic dependencies...

Can the cycles still include a root?

Yes...

For srlSentence at least, "Roots are nodes that never appear on the right hand side of these edges."  In a loop, all nodes appear on the right hand side.  A cycle cannot include a root then.
The problem with Eidos is that roots are not serialized, so they need to be recalculated.  That doesn't seem possible.  Maybe the serialization needs to be changed.  The compositional grounding makes use of the roots and they need to be preserved across serialization somehow.  Maybe it can be cleared up at the meeting today.

Does a root have to be a source of an edge?  Some code above says that it does:
val actualRoots = sources -- destinations

but there are places in the code where it isn't the case.  In a sentence with one word and no edges, is there a root, for instance?

It needs to be either a source, or to be a standalone node that is not part of any edge.

Hopefully last question: are all standalone nodes roots or just some of them?

Standalone nodes have to be roots because they are not reachable otherwise.


RTL with NavigatorIOS

Are RTL navigator transitions supported for NavigatorIOS?
I have followed the steps here but have been unable to reverse the navigation stack.
Thanks!

This issue looks like a question that would be best asked on StackOverflow.
StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
Will close this as this is really a question that should be asked on StackOverflow.


Add warning that requires SBT 0.13.13+

0.13.13 actually.

Hmm, still not working:
vagrant@cranberry:/vagrant/foo$ sbt --version
sbt launcher version 0.13.8
vagrant@cranberry:/vagrant/foo$ sbt new snowplow/snowplow-scala-app.g8
[info] Set current project to foo (in build file:/vagrant/foo/)
[error] Not a valid command: new (similar: set)
[error] Not a valid project ID: new
[error] Expected ':' (if selecting a configuration)
[error] Not a valid key: new (similar: name, run, runner)
[error] new
[error]    ^

sbt launcher version 0.13.8 should be 0.13.13.

I'd recommend this launched https://github.com/paulp/sbt-extras

So it doesn't work with 0.13.4+? We only have 0.13.2 and 0.13.8 in ansible-playbooks, so I don't really understand how I'm meant to use this.

No, it works only with 0.13.13+. I didn't consider to use it in conjunction with ansible-playbooks as this is something bootstrapped from host, not from Vagrant box.


utils: correct function name for PS style

The functions should be named [verb]-[noun], remove the extraneous - in the name. Also homogenise the call to avoid the parenthesis.

@swift-ci please smoke test


Home Page: JS Error

I added some JS to the static.js file that is throwing an error on the home page.  I need some help getting that resolved, please.
Uncaught TypeError: Cannot read property 'top' of undefined
This is coming from: https://github.com/donejs/donejs/blob/master/docs/theme/static/static.js#L501
@James0x57 or @moschel - I get by with a little help from my friends :)

As an added note, that JS is needed for somewhere within either Features, or guides, once the matrix design data is complete. Which, @moschel and @julia-allyce are working on.


ATMEGA32U4 has SRAM size incorrect on website

The ATMEGA32U4 has RAM size listed at 4K on the website. That's incorrect. It is 2.5K
http://www.atmel.com/devices/atmega32u4.aspx?tab=parameters

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26547364-atmega32u4-has-sram-size-incorrect-on-website?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

Thanks, fixed http://platformio.org/#!/boards


Implement Remote scraping

Is your feature request related to a problem? Please describe.
Currently we do not scrape Remote field for Indeed or Monster, which are providing many jobs.
Indeed provides this fairly visibly, it's just a bit buried in tags.
Glassdoor has this implemented already (tags as well)
Monster does not seem to have this capability, but it may be worth looking into if we can infer it.
Describe the solution you'd like
We should  scrape Remote = True if a job is fully-remote on Indeed. Temporarily remote doesn't count, sorry!
Describe alternatives you've considered
n/a
Additional context

Gonna see if I can get a PR up for this TN.

Completed the feature.


Add a link to intensity remap ref

Fixes #50.

Codecov Report

Merging #51 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #51   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines        1322   1322
=====================================
  Hits         1322   1322

Impacted Files
Coverage Δ

solt/transforms/_transforms.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Sort ref bug

@dvargas92495 for Sort References Bug
getPageTitleValueByHtmlElement(sortContainer) is still required for Daily Notes Page
getCurrentPageUid() returns today's date on DNP which is what /^([0-9]{2}-){2}[0-9]{4}$/.test(currentPageUID) is looking for.
I feel like this isn't ideal, and it gives a false positive for any day page, but that code still works regardless on those pages.
also npm version patch errored, but still went to 1.1.8

Not super happy with the "Check if sidebar" and "Find pageUID if sidebar" methods, but I didn't see anything helpful for this with roamAlphAPI.ui.rightSidebar, nor in roamjs-components
(other than maybe modifying getPageTitleByHtmlElement to include this functionality)


”Sarmizegetusa” is listed in  the drop-down menu

Description:
"Sarmizegetusa" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Sarmizegetusa" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Sarmizegetusa, HUNEDOARA".


Revert "Update docker image names in ci"

This reverts commit 648cdac73ab608dc56fa3ed3faf0f514fdf8b348.

@mestery is this reversion you mentioned in #77 ?

Yes, this is it!


RangeError: Invalid array length

Bug description
Adding the container inside a div with flex throws an error.
Environment

Browser: Chrome

Minimal code snippet
`"use client"
import { useWavesurfer } from '@wavesurfer/react';
import { RotateCcw, PauseIcon, PlayIcon, RotateCw, LoaderCircle, CircleX } from 'lucide-react';
import { useCallback, useRef, useMemo, useEffect } from 'react';
import { cn } from "@/lib/utils"
import { Skeleton } from '@/components/ui/skeleton';
interface WaveFormProps
{
url: string;
}
export default function WaveForm ( { url }: WaveFormProps )
{
const containerRef = useRef<HTMLDivElement | null>( null )
const { wavesurfer, isReady, isPlaying } = useWavesurfer( {
    url: url,
    container: containerRef,
    waveColor: '#dddddd',
    progressColor: '#6d28d9',
    height: 100,
    barWidth: 3,
    barGap: 2,
    barRadius: 4,
    autoplay: false,
} );

wavesurfer?.on( 'error', ( error ) =>
{
    console.error( 'Wavesurfer error:', error );
} );

const onPlayPause = useCallback( () =>
{
    if ( !isReady )
    {
        return;
    }
    wavesurfer?.playPause();
}, [ wavesurfer, isReady ] );

const onClickSkipSeconds = useCallback( ( number: number ) =>
{
    if ( !isReady )
    {
        return;
    }
    wavesurfer?.skip( number );
}, [ wavesurfer, isReady ] );

useEffect( () =>
{
    console.log( 'remove the flex from the classname and everything works' );
}, [] );

return (

)

}`
Expected result
It should always be displayed.
P.S. I discovered this behaviour as my production environment waveform is triggering "Container not found" and while trying to debug one functionality at a time, I discovered this weird case. I will lodge a ticket as soon as I can replicate "Container not found" in a logical way, as for now, it's triggered randomly.
Obtained result
Error
Screenshots

If you change it like this:

everything works fine.

Works fine using :

Seems to be a duplicate of https://github.com/katspaugh/wavesurfer.js/issues/3923