Python Program for Difference between sums of odd and even digits

Problem:
Given a long integer, we need to find if the difference between sum of odd digits and sum of even digits is 0 or not. The indexes start from zero (0 index is for the leftmost digit).
Definition of done:

Clear code should be written.
Comments will be really appreciable.
Add minimum 2 test cases to test the code.
Add you code under Python/Data Structure and Algorithms/<ProgramName.py>
Make sure to add the Screenshot of Program Testing in the comment while merging the PR

Hey! Could I work on this? 😄

Sure. assigning to you

Just to clarify:
1234 -> (1 + 3) - (2 + 4) -> odd digits - even digits
1234 -> (2 + 4) - (1 + 3) -> digits on odd indexes - digits on even digits
Thank you

Yes. This is correct

Both of the options?

Sorry. Go with the indices one

I would like to work on this

@andrefpoliveira are you working on this


[Azure DevOps]:

Inputs
Provide the following required inputs:
Organization: ghes-demo
Project: ghes-migration
Available commands
The following commands can be executed by adding a comment to this issue:

/audit
/dry-run --pipeline-type pipeline|release --pipeline-id :pipeline-id
/migrate --pipeline-type pipeline|release --pipeline-id :pipeline-id --target-url :github-repository-url

Note: The pipeline-type option will default to pipeline if omitted. If any remaining options are missing, the command will not be successful.

/audit

/audit


wip: consolidate logic to useFetch

Summary of changes
I introduced useFetch in https://github.com/mbta/dotcom/pull/1658/commits/05fee508f836976ff48579b6f58bfedee94ddb5e, this is the attempt to use it across all our fetches in the stops page redesign.
I considered deleting all the hooks and using useFetch directly and repeatedly, which would produce code something like this
  const stopResult = useFetch<Stop>(`/api/stop/${stopId}`);
  const routesWithPolylinesResult = useFetch<
    (Route & { polylines: Polyline[] })[]
  >(`/api/routes/by-stop/${stopId}`);
  const alertsForStopResult = useFetch<Alert[]>(`/api/stops/${stopId}/alerts`);
  const facilities = useFetch<Facility[]>(`/api/stop/${stopId}/facilities`);
  const alertsForRoutesResult = useFetch<Alert[]>(`/api/alerts?route_ids=${
    (routesWithPolylinesResult.data || []).map(r => r.id).join(",")}`);

But it felt messy, would've made refactoring all the tests and hook mocking a heavy lift, and useSchedulesByStop had some additional logic (parsing the data before returning).
Welcome feedback, visions, comments.

General checks

[x] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
[x] Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
[x] Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

Can revisit later, it's a bit much for now


MSVC_RUNTIME_LIBRARY value 'MultiThreadedDLL' not known for this ASM

CMake Error in cmake-build-release/_deps/sdl3_mixer-src/external/wavpack/CMakeLists.txt:
  MSVC_RUNTIME_LIBRARY value 'MultiThreadedDLL' not known for this ASM
  compiler.

Windows 10
Visual Studio/2022/Community
Use the latest node: de0f62abbcb41c64e0cb1045a521e2deeb562fb7
include(FetchContent)

FetchContent_Declare(SDL3
        GIT_REPOSITORY https://github.com/libsdl-org/SDL.git
        GIT_TAG 3a219caf3da11df9feed819be6d2b08c10d44cfc
)
FetchContent_MakeAvailable(SDL3)

FetchContent_Declare(SDL3_mixer
        GIT_REPOSITORY https://github.com/libsdl-org/SDL_mixer.git
        GIT_TAG de0f62abbcb41c64e0cb1045a521e2deeb562fb7
)
FetchContent_MakeAvailable(SDL3_mixer)

add_executable(${PROJECT_NAME}
        src/main.cpp
)
target_link_libraries(${PROJECT_NAME} PRIVATE SDL3::SDL3)
target_link_libraries(${PROJECT_NAME} PRIVATE SDL3_mixer::SDL3_mixer)
target_compile_features(${PROJECT_NAME} PRIVATE cxx_std_23)

It seems to be related to the shared libraries build.
Use the following options will not generate errors. (it has also become a static link)
set(BUILD_SHARED_LIBS OFF)
set(SDL_SHARED OFF)
set(SDL_STATIC ON)
set(SDL3MIXER_VENDORED OFF)


Remove Provider

This removes the provider package.  It is no longer necessary and has been replaced by the provisioning system.
Refs #1190

Tested against VirtualBox, AmazonEC2 and DigitalOcean -- all work as expected.

+0 -121 :heart_eyes: :heart_eyes: :heart_eyes:
LGTM

Travis is blowing up with "no install location" errors though, not sure what's up with that.

@nathanleclaire fixed PTAL

Nice LGTM


chore: prepare v4.0.0

Sorry for all the confusion here.
I was originally going to implement the mock image for the upgrade tests, however this turned out to be slightly move involved than I thought.
I reverted back to the chore: remove mainnet id check commit.
Will implement mock image in follow up PR.


Add sponsorship to the navigation

Add a new item as "sponsorship" or "donation" to the navigation in the header. Use the link https://github.com/sponsors/graycoreio for the new menu item

@AnnieMi888 this request is quite vague, can you clarify what you mean?

We should add a donation menu item to navigation, see picture. The link should lead to https://github.com/sponsors/graycoreio


Inference helper class

I just wanted to share some code I'm using to help with type inference for higher-kinded effects.
cleff-plugin wasn't an option for me because I am x-compiling. See this GHC ticket.
The effects I was using were unique for my effect stack anyways, so I was able to use a helper type class with a fundep to get GHC to figure out the type parameter that the plugin would normally help with. I added a little more stuff to guarantee the effect is only used once (just like mtl fundeps ensure in that world).
Here's the code! https://gist.github.com/ramirez7/fab0ba053f27b73c2a50bafa69c26be4
theAsks
  :: forall r a es
   . The Reader es r
  => Reader r :> es
  => (r -> a)
  -> Eff es r
theAsks f = f <$> ask @r

^ theAsk will never run into inference issues even if the function you pass to it is highly parametric (e.g. optics and labels and such. Like theAsks $ view #player % #speed). The only downside is you can't have multiple Readers.

PS I love the library and it's working great for me so far! I'm using it for gamedev and it's really cleaned up my code compared to mtl style. And my small stuff is still humming at 60fps with plenty of headroom.
PPS I also have an alternative that uses implicit Proxy params in a similar way to nudge inference. That was mostly for fun, but it was cool nonetheless.

I'm glad that cleff works well for you! I had a look at your The class, it was neat. It seems that to use theAsk, the call site needs to have both The Reader es r and Reader r :> es - is it possible to make the latter a superclass of the former, i.e. class f e :> es => The f es e, so that only The is needed?

I was able to make it a superclass and it Just Worked! Very cool - I've never used superclasses for type-level computations like that. Thank for the code review 🤠

Closing for now - if you have any further suggestions/questions let me know!


[SPARK-7235] [SQL] Refactor the grouping sets

The logical plan Expand takes the output as constructor argument, which break the references chain. We need to refactor the code, as well as the column pruning.

Merged build triggered.

Merged build started.

Test build #31283 has started for   PR 5780 at commit c4395b4.

cc @viirya @marmbrus

Test build #31283 has finished for   PR 5780 at commit c4395b4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31283/
Test FAILed.

Merged build finished. Test FAILed.

The failure depends on #5798

Hey @chenghao-intel, per our offline discussion, we can fix the case sensitivity issue in a surgical way within this PR (by comparing attribute names in a case insensitivity way when necessary), so that #5798 doesn't bock this one.

Merged build triggered.

Merged build started.

Test build #35549 has started for   PR 5780 at commit 76e4aa4.

Test build #35549 has finished for   PR 5780 at commit 76e4aa4.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BroadcastHint(child: LogicalPlan) extends UnaryNode

Merged build finished. Test PASSed.

Thanks, this looks a lot cleaner.  Merging to master.


[test-only] ApiTest. deleteTag test. increase coverage

added test for deleting tags

:boom: Acceptance test localApiTests-apiSpaces-ocis failed. Further test are cancelled...


Ensure all asset output ids are filled in

If a test curator only provides an output name, I think we should send it through the Name Resolver on ingestion to the Tests repo. The Runners will need the output id and I don't think we should obtain it at run-time.

Hi @maximusunc, the most robust solution (@sierra-moxon correct me if I'm wrong) would be to annotate the TestAsset model slot for output_id as required: true.
Following this line of reasoning, it is tempting to ask what are all of the required slots of a TestAsset?  I would personally hazard to guess that the following list of TestAsset slots are such:

id - required by inheritance from the TestEntity parent class
input_id
predicate
output_id
expected_output

All the other fields of the TestAsset model are likely optional (again, @jh111, @sierra-moxon correct me if I'm wrong).
I will issue a PR to add required: true to all of the above slots which lack the directive.

Potentially enforced by PR https://github.com/TranslatorSRI/TranslatorTestingModel/pull/15.

One caveat I'd like to point out here. It's my understanding that the Data Harmonizer spreadsheet that Sierra created uses the model, so that would require these fields to be filled in, but I'm worried that a non-technical user might not know how to fill out the input and output ids (not to mention that it kind of needs to use the preferred curie from node normalizer). My opinion is that the best way to do this is to keep the Data Harmonizer a little less strict and then inside our Asset -> Test Case script, we name resolve and node normalize all the ids that are missing.

I agree we want non-technical people to be able to add assets. However, from a testing perspective, I think it will be best to have those cases fail. Test failures may be bugs in the product or bugs in the test. Have nice red failures will motivate SMuRFs like me to get my IDs done, and help SMEs who can't do it.

Are you saying the IDs should not be required, but the test should fail until one is provided?

Yes, I think that would be ideal longer term. If TAQA says a test is important, than it's a priority to get both the test and Translator working.

I said "Node Normalizer" above but I'm wondering if it's keyword searching on concept annotation.
As you mention to me on Slack, maybe such queries against the my-*-info resources?


Check if devise_ldap_authenticatable can bind as admin

Is there a way to check if devise_ldap_authenticatable can bind as admin? I provided all credentials, but the notorious get_ldap_param does not work.
Basically I just used the same dn and password I use with net-ldap. And it works there. But I get:
(byebug) Devise::LDAP::Adapter.get_ldap_param(self.email, "FirstName")
  LDAP: LDAP search for login<EMAIL_ADDRESS>  LDAP: LDAP search yielded 0 matches
  LDAP: Requested ldap entry does not exist
nil

Oh, I find a solution. One has to add
config.ldap_auth_username_builder = Proc.new() {|attribute, login, ldap| "#{login}" }

to config/initializers/device.rb. source


bug(forge script): duplicate vm.prompt display in script with external libs

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (a0a0020 2024-08-12T00:21:34.427762642Z)
What command(s) is the bug in?
forge script
Operating System
Linux
Describe the bug
Repro code: https://github.com/beeb/foundry-repro-prompt-lib
When a contract must be linked against external libraries, and a Foundry script deploys such contract, prompts are
shown twice.
Reproduction steps:

Launch an anvil instance: anvil -a 1
Launch script: forge script -f http://localhost:8545 --broadcast script/Counter.s.sol:CounterScript
Observe that a prompt shows up and paste the first anvil private key: 0xac0974bec3...
Observe that a second identical prompt is displayed

If the deployed contract does not have external libraries that must be linked, the problem does not happen.

I encountered the same issue. I believe there's a problem with the deployment of external libraries and the prompt sequence. When using a script where external libraries need to be deployed, this task is performed first, even before the run function starts executing. However when a prompt is included in the script, the deployment of these libraries is delayed, awaiting user input, which maybe conflicts with the deployment process.
The inputs from the second prompt overwrite those from the first.
Initially, I thought the duplicated prompt was related to the simulation of the script, but using the --skip-simulation option didn't change anything.

@klkvr Potentially related to https://github.com/foundry-rs/foundry/issues/8639?

This is happening because of the way scripts handle external libraries deployment when private key is not known before running the script. Forge needs to know which address to use to deploy external libraries, and if the only signer is being resolved dynamically in script (in this case, by prompting private key), then we need to run script second time with correctly calculated library addresses, deployed by the prompted private key

Thanks for the explanation! Could a fix potentially be to skip showing the prompts the second time around and reuse the values provided the first time?

Maybe it's simpler to invoke the script with -i 1 and not have the private key prompt in the script. Is there a way to detect if that argument is missing to e.g. revert inside the script if missing?

Thanks for the explanation! Could a fix potentially be to skip showing the prompts the second time around and reuse the values provided the first time?

This could work, though it might result in unexpected edge cases in situations where prompts order is not deterministic, so its hard to come up with a generally working approach here

Maybe it's simpler to invoke the script with -i 1 and not have the private key prompt in the script. Is there a way to detect if that argument is missing to e.g. revert inside the script if missing?

if it will be missing, then script will just dry-run with default sender, and once you try to broadcast it will throw a error saying that script is missing sender, do you need some different behavior for this case?

@klkvr never mind my suggestion, the problem is the same with -i 1 added to the script command. It prompts twice.

@klkvr never mind my suggestion, the problem is the same with -i 1 added to the script command. It prompts twice.

is the script still using vm.startBroadcast(vm.promptSecretUint("Enter the private key"))?

No I removed it since the -i 1 prompt does the same

Ok never mind I tried again and there is no double prompt. I must have done something wrong. So the workaround would work.


Fix git push error for protected CLA branch

The pull request is created from master636885396366517465 to master to fix git push error for protected CLA branch

@opbld17 : Thanks for your contribution! The author, @mikeblome, has been notified to review your proposed change.


add piglow to the projects list

Feel free to also submit this to maintained fork:
https://github.com/abandonware/node-i2c


BCO 2016: Schedule Section (1/2 built)

Building the Schedule section ACF
Styling text and tabular data
Removes prefab h6 styles

Looks great! Good work today! 👍


Issue #19 🎫: Refactor to migrate es6 FC to es5 FC - and - Fix 'LikeButton' UI FC non-persistend liked style

Pull Request Summary for Issue #19 Completion

Overview:

Issue #19.

As described in the issue overview, the changes made in this branch are related to refactoring all functional components from ES6 fat arrow functions to ES5 functions. This was done to ensure that the codebase is consistent and to make it easier for other developers to understand the code. Aditionally and more importantly, this changes was made to ensure a better debugging experience with the React DevTools, since all the components written in ES5 functions are named and can be easily identified in the DevTools.

Changes Made:
Added:

n/a.

Modified:

/package.json

/package-lock.json

Updated gh-pages version from 5.0.0 to 6.1.1.

The following components were refactored from ES6 fat arrow functions to ES5 functions:

/src/components/UI/*

ContactForm.tsx.

ExpertiseLinks.tsx.

FileTabsNavbar.tsx.

LineCount.tsx.

Navbar.tsx.

SplideCarousel.tsx.

SplideCarouselSlide.tsx.

LikeButton.tsx.

Additionally, I have address the issue with the like button not showing its liked style class when the user clicks on it.

/src/components/animations/*

AccessPageVideo.tsx.
Drone.tsx.
FloatingAstronaut.tsx.

/src/components/pages/*

AboutPage.tsx.
AccessPage.tsx.
ContactPage.tsx.
HomePage.tsx.
ExpertiseSummaryPage.tsx.
NotFoundPage.tsx.
ProjectsPage.tsx.

Deleted/Renamed

n/a.

Impact:

The changes made in this branch are not expected to have any impact on the functionality of the application. The changes are purely cosmetic and are meant to improve the readability of the codebase.
These changes will impact all UI, animations, and pages components in the application.

Testing:

n/a.

Related Issues:

Closes #19.

Dependencies:

n/a.

Additional Notes:

The changes made in this branch have just been deployed, check the new SemVer v2.3.1.

Commit fe85f13 message is wrong, the correct one is:
Chore: Update 'gh-pages' version from 5.0.0 to 6.1.1

✅ Good for merge.


WB-4045 - Adding BAC brand colour as an option to the hero

Modifying the hero colour picker to allow the user to select the brand colour for Bereavement Advice Centre. That colour already exists as a class after merging here: https://github.com/coopdigital/coop-frontend/pull/262

im not sure this is needed. you could delete the other colours and just use the ones you need for BAC and maybe add the extension folder into your gitlab repo?


Recursive copy or something?

When I run
npm install
npm run package:linux

in Arch Linux, the folder electron-packager contains linux-ia32 -> Google Play Music Desktop Player-linux-ia32 -> resources -> electron and then again electron-packager and this will continue until the filename is too long for ext4 to handle. My original electron-packager folder is now 5.7 GB big...

Sounds like your node / npm is borked.
What node version are you using?

I'll take a look at that later when I have my laptop on. Does running npm run package:deb have a similar result? It should produce usable binaries in dist/Google-....
Also, what about npm run make:linux? I have an idea of what the issue might be, but I can't look at it right now.

$ node --version
v5.7.1
$ npm --version
3.8.0
$ gulp --version
[06:37:16] CLI version 3.9.1

Can you try dropping to LTS node (4.3.1)

That isn't available for Arch Linux... :D

So with node version v4.3.2 running npm run package:linux works and finishes and I have contents in the dist folder.
But with this PKGBUILD file it doesn't work (again this "loop" which happens after
[07:33:11] Starting 'package:linux'...
Packaging app for platform linux ia32 using electron v0.36.10```

I have no idea how PKGBUILD works, I would assume it's buggered... :+1:

Closing as PKGBUILD is not supported internally (someone else made it) and the build process has been proven to work

@dylanlesko npm run make:linux returns that the command dpkg-deb was not found.


"cumsum" function in mutate

When I try to create a new variable that is the cumulative sum of another variable I get incorrect results:
`using DataFrames
using Tidier
df = DataFrame(a = 1:10)
df = @chain df begin
@mutate(
cum_a_tidier = cumsum(a)
)
end
df[!, :cumulative_a_base] = cumsum(df[!, :a])
`
This results in the tidier version returning an array containing only the value for "a" for that row, whereas the base version returns the correct result.

Can you check which version of TidierData you have installed?
You can go to the package console using ] and then type in status to check on package versions.
I believe we had fixed this issue quite a while ago. Thanks for checking.


recipientSuppliesTabs gets set to true on one recipient of my template

I have a template with 3 signers from which I create an envelope.
My issue is that with 1 recipient in particular, the field recipientSuppliesTabs gets set to true and this recipients gets a free form signing experience.
I have tried supplying recipientSuppliesTabs : false in the templateRoles when creating the envelope but this does not do anything. Does the api not support this field ?

hey @hgrubst yes this property is not yet supported


Air dash

Tasks

[x] dash directionality
[x] keyboard mapping
[ ] @d-roak & @0xMugen playtest to tune parameters

closing for archiving


"com.evvo" should be "io.evvo"

Describe the refactor you'd like.
All packages named "com.evvo" should be renamed to "io.evvo".
Why should the refactor happen?
We own evvo.io. We don't own evvvo.com. The current directory structure is incorrect and will cause issues with Maven.
Additional context

Closed by #117


Fix auth

Hey I fixed authentication and made some changes in auth.rs and conf.rs
In response to my issue  #109

@GuyL99 ,
I did not forget to implement the custom auth type.
Actually cherrybomb support for four  type of authentication:  basic, bearer, header, cookie.
You can see https://github.com/blst-security/cherrybomb/blob/fix_auth/cherrybomb-engine/src/scan/active/http_client/auth.rs
that the four type for authentication are implemented. ( see the "from_parts" function)

Why not include custom then?

Raz called it header type instead of custom, it is work the same way. User provide header and value

Custom can be delivered by query or payload as a parameter...

Custom can be delivered by query or payload as a parameter...

I get it.
So actually the new cherrybomb  CLI does not include custom authentication.
I implemented authentication in according to the new CLI.
maybe open an issue for it?

Merged with dev, will be added to main in 1.0.1


Integration Test - Release - 2019/02/21 09:09:24

Auto create for integration test. IssueCommandFlow

@adunndevster : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


workStart / workEnd should be null or undefined

Previously workStart & workEnd was 0 when work area wasn't specified, now it looks like it returns -1.
Best would be to set it to undefined or null when not defined so we can do
const start = animation.workStart ?? 0;
const end = animation.workEnd ?? animation.duration;

Maybe also add a comment in changelog, readme or in the d.ts :
/** Start of the work area. If no work area then -1 */
workStart: number;

The change happened on the cpp side and the js is being auto-generated. Our new default value for undefined uints is -1.
There is the enableWorkArea boolean flag in the cpp; I can expose that in Wasm so you can use it to work out if there's a work area for the animation.
Would that work?

That makes things clearer indeed. Thanks.


Arts 98

Adding Role to the trial config. The changed files in this commit will change again shortly as we remove authentication and retrieve the trial-config json file from git

Conflicts resolved


Uninstall Tweakster, jumplist stick

So i had some issue with my VS, and to search for the error i uninstalled all extensions (was unrelated thing).
I then noticed that the jumplist feature for tasks presentation mode and safe mode stuck there, and i wanted to show recent files instead. Alot of googling later i found out that i had to delete a file in  %AppData%\Roaming\Microsoft\Windows\Recent\CustomDestinations\ that contained visual studio presentation mode and safe mode - now i got my recent files list back again.
This is not a bug per se, but i wrote this if someone else have the same issue.
Perhaps i should add i don't use the standard windows start menu, i use Open-Shell if that matters.

I have the same problem, I installed the Tweaks 2022 extension, then found the "don't copy line" feature wasn't working and uninstalled, but it left the Presentation Mode and Safe Mode under Tasks when I right-click on the task bar for VS2022.
However I don't have the folder %AppData%\Roaming\Microsoft\Windows\Recent,  the closest thing is "Recent Items" under that Windows folder but that doesn't contain a CustomDestinations folder.  I searched the C: drive and didn't find "CustomDestinations" anywhere so I'm not sure how to manually remove those two tasks for Presentation/Safe mode.  Any ideas?


Clean markdown characters, leave only clean text.

I want to make an html element on my website that is responsible for displaying news articles.
I am only displaying title and sample of the article content as preview.If user wants to read full article he can switch mode to see all the content with markdown parsed as html.
Value of the article content is stored as markdown and is converted to HTML on the client side.
I would like to make sample of article content as simple as it can be, stripped of any special markdown characters.
Is there any simple solution to strip these characters and leave only simple text?

Is it worth to make an extension for such usecase?

it's indeed possible to make an extension to strip all markdown special characters. however, it might be hard to account for everything since stuff such as newlines count as markdown too.
Maybe it's easier to let showdown parse the text as HTML ad then strip the HTML tags


stop avatar aim legs influence

This is to fix the issue with aim walk being janky, now aim animation does not influence legs
https://user-images.githubusercontent.com/51108458/151588835-8b7db367-a2e1-4a49-b61e-121bb076bbf4.mp4

How well does this handle the couch case?

Looks like a frog during crouch, same as https://app.webaverse.com url

https://user-images.githubusercontent.com/51108458/151632701-f01baec0-8a80-4a65-a873-a4fd61a6a452.mp4
The face might be an animation change but should it not also just work the same as before, since the head should be controlled separately? or is it decided by hips forward?

Looks like a frog during crouch, same as https://app.webaverse.com url

Can't we use the same technique to keep  the legs stable when crouching?

The face might be an animation change but should it not also just work the same as before, since the head should be controlled separately? or is it decided by hips forward?

I think what is happening here (you are the expert on this code!) is the sword aim animation has a gradual torso twist and that is not being compensated for.

Looks like a frog during crouch, same as https://app.webaverse.com url

Can't we use the same technique to keep the legs stable when crouching?

I dont think I can do the same for the legs because there is no crouch locomotion.

The face might be an animation change but should it not also just work the same as before, since the head should be controlled separately? or is it decided by hips forward?

As far as I know the hips define the head, and identity twists along the route will result in the head being straight, which is how the rest of the walking works.
I think what is happening here (you are the expert on this code!) is the sword aim animation has a gradual torso twist and that is not being compensated for.

I will look at preventing the neck from updating.

https://user-images.githubusercontent.com/51108458/151640384-706e084c-ea2b-425c-867d-88df0b0e6129.mp4


[Chore] Improve unit testing architecture

Issue

While the API application has a decent amount of tests, the tests create records in the same local database as used for the development. Populating the database for each test also requires deleting the test records at the end of each test or test suite (each file). That's where I suspect the hanging issues come from. It also deletes all development data, i.e., if a dev creates a user locally to use the application and then runs the tests, the next time the developer uses the application locally, the newly created user will be gone  😅
Expected
First, when creating database-stored fixtures for tests, it is a best practice to have a local database dedicated to testing, e.g., e=using the database api_development for development and api_test for tests. Second, whenever possible, not creating records in the database should be preferred to ensure adding loads of tests (think hundreds) will not slow down too significantly the whole test suite. Prisma has support for using a DB mock, and the simplest is to mock the DB client: https://www.prisma.io/docs/guides/testing/unit-testing#mocking-the-prisma-client

Lol, I also face the same issue when I developed this application.
Sorry that you have to face the same experience 😅.
Yes, I agree that we should add another database specifically for testing purposes and config our application to automatically switch to use it when we run our test cases. I have never done this with Nest.js before so I decided to put this issue on my waitlist when I developed the application last week.
Regarding avoiding creating records in our database to reduce the testing time, I do agree that it would reduce the testing time, plus it would allow us to run the test case in parallel rather than in sequence (--runInBand)
However, I think It comes down to the level of assurance that the team would like to achieve from these test cases and the disadvantage of each approach that the team considers being tolerable.
In my opinion, the benefit of creating the records in the database is allowing us to discover even the bug that comes from Prisma. In my previous company, this approach allows me to discover the bug in our underlying ORM library and address it before we release the product to our end users. I admit though that it rarely happens.
Anyway, I don't mind mocking the Prisma client if it is the convention that the team is already settled on.
Just want to clarify that we are on the same page about the pros and cons of each approach. 😊

In general, we cannot bypass entirely creating records in the database. Think of UI tests and other integration tests. However, for unit tests, mocking the DB client is usually sufficient and even preferred as it makes the tests less brittle and have zero external dependency (which we want when unit testing ⚖  )


Fix batch of bugs found from static analysis

Godot version:
Current master branch (presumably).
Issue description:
Developers of commercial PVS-Studio static analysis tool posted a blog article with details on various bugs that their tool detected in Godot's source code: https://www.viva64.com/en/b/0594/
Most seem to be low hanging fruits and would be good to fix. A couple of those might already be fixed though (e.g. the v_scroll one - error 5 was fixed in #23735).

Superseded by #24014.


Firefox 41 large image displaced

In Firefox 41 the image of Napoleon's March is overlapping with the Rhino in the sidenote.

i think I fixed this by adding clear:both to .fullwidth see pull request #54

I used @crmackay fix and added my own, perhaps someone can review this.


Training---socket.gaierror: [Errno 11001] getaddrinfo failed-hostname = socket.gethostbyname(socket.getfqdn())

Hi, thank you again for sharing this code. I use only a single GPU, so I changed the node to 1 (it works with a CPU but not with a GPU). I got this error.
GPUS_PER_NODE = 1
SETUP_RETRY_COUNT = 3
python version 3.8
torch 1.9.0+cu111
torchvision 0.10.0+cu111
Windows
File "scripts/segmentation_train.py", line 89, in
main()
File "scripts/segmentation_train.py", line 25, in main
dist_util.setup_dist()
File ".\guided_diffusion\dist_util.py", line 34, in setup_dist
hostname = socket.gethostbyname(socket.getfqdn())
socket.gaierror: [Errno 11001] getaddrinfo failed

Hi
I am not sure the problem is GPUS_PER_NODE, since (in the version you get in this repo) we do not use MPI (please check out the original repo from openai, where they use mpi4py).
Rather check whether th.cuda.is_available(), since the error occurs in this line.


[Hostmetrics Receiver]: e2e testing- CW validator, Linux expectation template, Testcase, and ECS script

Description:
Added Hostmetrics Receiver e2e testing

CW validator
Linux expectation template
testcase
and ECS script

Link to tracking Issue:
https://github.com/aws-observability/aws-otel-ops/issues/137
Testing:
Manually testing on local box by running:
cd terraform/ecs
terraform init
terraform apply -auto-approve \
    -var="aoc_image_repo=public.ecr.aws/q1w6y6d0/hostmetricsamd" \
    -var="aoc_version=latest" \
    -var="testcase=../testcases/hostmetrics_receiver" \
    -var-file="../testcases/hostmetrics_receiver/parameters.tfvars"

Note - Requires Collector with hostmetrics_reciever component
Documentation:

[ ] Few metrics were not emitted through cloudwatch exporter. Details will be added. This is a todo item.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Created PR erroneously to terraform branch - meant it for dev branch.


Fix to remove python 2.7 specific syntax

Hi,
Subject says it all, really. Thanks!

Erik,
No problem with this, but could you re-submit against the dev branch?


runtime selector needs better colors

Due to the chosen colors, one needs to hoved them one by one to find them.

Looks like this now:

Much better!


[ISSUE-167] Support graph aggregation

What changes were proposed in this pull request?
图迭代计算中，如果满足迭代收敛或者迭代结束条件，则需要提前结束迭代。
需要新增api支持用户

搜集迭代信息，并支持局部聚合和全局聚合。
支持根据全局聚合值，判断是否提前终止

需要实现agg相关算法，以traversal为例，实现VertexCentricAggTraversal
和普通traversal(VertexCentricTraversal)不一样的是，接口getTraversalFunction返回对应VertexCentricAggTraversalFunction<K, VV, EV, M, R, I, GR>>，该function在普通function基础上多实现接口VertexCentricAggContextFunction<I, GR>, 其在traversal期间提供agg context和aggrete接口。
public interface VertexCentricAggTraversalFunction<K, VV, EV, M, R, I, GR>
    extends VertexCentricTraversalFunction<K, VV, EV, M, R>, VertexCentricAggContextFunction<I, GR> {
}

同时新增接口getAggregateFunction，该接口定义部分aggregate和全局aggregate具体实现。
VertexCentricAggTraversalFunction<K, VV, EV, M, R, I, GR>> getTraversalFunction();
VertexCentricAggregateFunction<I, PA, PR, GA, GR> getAggregateFunction();

How was this PR tested?

[ ] Tests have Added for the changes
[ ] Production environment verified

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: cbqiao:x: 参辰参辰 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[LDA] - (Mods) LuxImport Change to SkiaSharp instead of using SixLabors.ImageSharp

Describe the bug
When loading a bitmap using SixLabors.ImageSharp, the image is successfully loaded, but the library does not allow decoding or saving the bitmap in formats like PNG, JPEG, and others. This limitation impacts the ability to process or export images in common formats.
Expected behavior
The application should seamlessly load images in various formats using the SkiaSharp library. SkiaSharp provides robust features such as:

Compatibility with WinUI 3 components.
Advanced GPU-acceleration for improved performance.
Cross-platform support for rendering and manipulation.
Additionally, it should utilize SKBitmap to enable further image processing and exporting in formats like PNG, JPEG, etc., without restrictions.

Increment version of LuxImport from V1.0.0 to V1.0.1

:tada: This issue has been resolved in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Implement process scanning on AIX

There is a proc filesystem, but the layout differs from the Linux implementation, see https://www.ibm.com/support/knowledgecenter/ssw_aix_72/com.ibm.aix.files/proc.htm for details.
I'd be happy to give it a try, but I'm not sure for how long I'll keep access to an AIX virtual machine.

In that case I wouldn't bother about implementing process scanning for AIX. If someone actually needs this feature and will be able to support it in the long term I would include it, but if not, I don't think the demand for AIX is high enough to be worth the effort.


bug: inconsistent cursor blink interval

Recording a gif for this one would be tricky (because of fps)
Anyway, the problem is that the cursor blinks with a changing/inconsistent interval.
Win10, powershell, alpha34

Same for me in Linux, I guess after some last updates

Same for me. It doesn't happen on start, but after some time using it.

Running into this problem as well

not fixed yet

I am seeing this issue as well but only when using the WSL/Default distro shell.


Option to align Free Text

Would be great if there is an option to align Free Text automatically.
Something like this (screenshot from Photoshop):

Right now, there's the Caption feature, which has an aligned option.

Would be great if there is an option to align Free Text automatically.

There is pull request with text alignment for left, center, right and justification - #779 Possibility to align text within free text

Would be great if there is an option to align Free Text automatically.

There is pull request with text alignment for left, center, right and justification - #779 Possibility to align text within free text

Feature added by @mabakay.
The option to align vertically by bounding box will come after the editor get reworked to support layers.


animation after FlexLayoutManager.OnItemsMoved() works incorrectly

[ v ] I have searched existing issues and confirmed this is not a duplicate

Issues and steps to reproduce
i write a sample code using RecyclerView, ItemTouchHelper(for drag&drop),
using options are FlexWrap.WRAP, FlexDirection.ROW, JustifyContent.FLEX_START
in ItemTouchHelper.Callback.onMove(), i call FlexboxLayoutManager.onItemsMoved()
after that, views before target position are duplicated.
i see source code of this project. there is a need to fix determie 'dirtyPosition'
<FlexBoxLayoutManager.java>
...
private void updateDirtyPosition(int positionStart){
..
if (firstVisiblePosition <= positionStart && positionStart <= lastVisiblePosition) {
return;
}
}
'if statement' above may need fix
(i think the all positions greater than 'positionStart' should be dirty)
Expected behavior
Please describe what you expected would happen.
Version of the flexbox library
1.0.0
Link to code
Please link to the code we can use to reproduce this issue.
A complete project we can build/run is preferred, if you can't provide one, please show
us relevant code
you can see code
https://github.com/msju/FlexboxLayoutManagerIssue

@thagikura
https://github.com/msju/FlexboxLayoutManagerIssue
you can see codes. thanks :)


Enable specifying a directory to relativize resource paths against

This change is useful when the desired resources are not in either the working directory or at a constant path. The specific use case that lead to this is using Dexter in an Apache Spark job. Relativizing the paths in the dexter-conf file against wherever Spark downloads the resources greatly simplified my life. To give you an idea of what I mean, our calling code:
// Go download this file from S3 and distribute it to the executors
sparkContext.addFile("s3a://.../dexter-resources/", recursive = true)
// And each executor does:
val resourcePath = new File(SparkFiles.get("dexter-resources")).toPath
System.setProperty("conf", resourcePath.resolve("dexter-conf.xml").toString)
System.setProperty("dexter.resourceRoot", resourcePath.toString)
val params = DexterParams.getInstance()

Thank @dandersonw  I'll take a look over the weekend!

@dandersonw Looks good happy to merge in, could I just ask to invert the order of the arguments in the private constructor in order to be consistent with the File signature?
private DexterParams(String resourceRoot, String xmlConfig)

Thanks, I think something should change also in getInstance() no ?

Hah, looks like I'm not paying attention. One second...

Thanks @dandersonw


mmseqs result2repseq does not make a *_h file

I'm trying to get the abundance of gene clusters generated by linclust. My method involves mapping the post-QC Illumina reads to the post-linclust cluster representatives via mmseqs map. To get the representative sequence db, I'm using mmseqs result2repseq. I ran mmseqs map (actually mmseqs search --alignment-mode 4 due to Issue #144), but after many hours of processing, I got the error that no "*_h" file exists for the database, and the map job died.
Do I have to convert the rep-seq database to a fasta and then re-create the database with mmseqs createdb just so that I can generate the *_h file?  Is there a more efficient way?
Why doesn't mmseqs search check for the necessary files at the start of the job instead of in the middle of the run (possible after many hours of processing)?

@nick-youngblut yes this indeed not great default behavior. We will change it. Your computation time is not wasted. You can restart the job by just calling the same command again. But before you need to create the header file (_h') file by calling mmseqs createsubdb repSeqDb seqDb_h repSeqDb_h. Sorry for the inconvenience.

The restart behavior is quite nice. Thank you for explaining how to create the *_h file using mmseqs createsubdb. I didn't understand what createsubdb does, but I must have missed it in the wiki docs.


Hot module reload for tests

Have you given thought to writing a test runner or somehow extending mocha to only run tests for specs that have changed or whose dependencies have changed? It would be a very powerful thing for bigger projects.

This would be great. I'm not familiar with any of the code bases involved, so I'm not sure just how much I can contribute, but I've be mulling this over conceptually. I thought rather than just put it to one side, I'd write down my thoughts as a straw-man. If someone who is a bit more familiar with how this all works, and can refine this, that would be brilliant.
I'm not sure if "proper" HMR is required for achieve this, or if it is necessarily the easiest way to do it. (Would using HMR mean that jasmine was HMR aware? Or just karma runner?)
Aims

Only re-run tests which have changed or whose dependencies have changed
Don't require whoever is consuming test results to be aware of what we're doing. (ie. return the full result set every time, not just the subset which has changed).

Design constraints

Only support the "one entry per test file" style, as this will result in one chunk per test-file, which will make it much easier to work out which tests / dependencies have changed.

Description of what should happen

Start karma in watch mode with one entry per test file
webpack builds one output file per test file
All the tests are run as per usual
The test results are cached on an per test-file basis before being returned
webpack picks up changes to tests or dependencies & updates one or more test files
karma-webpack sends only these changed files off to karma-runner to be re-run
The new results are cached
The full result set is returned

Questions

Is it possible to access test results "per-file" from karma runner?
Where ought the test results be cached?
Is it possible to only re-run certain files with karma runner at present?
Where would we make the change to return cached results, rather than "fresh" results?

@studds thank you for your comments. For what it's worth, there's a version that implements this available https://www.npmjs.com/package/karma-webpack-with-fast-source-maps

@aaronjensen I like your documentation on sourcemaps it's more clear, it'd be worth considering to update the karma-webpack repo to match.

Feel free to take whichever bits of the docs you like and PR them to here.

@aaronjensen Seems that the version you linked is no longer supported and incompatible with latest depencies. Any chance this feature can be implemented in this repo?

@gnz00 I'm not using Karma anymore, so it's unlikely that I will, but anyone else is totally welcome to.

@gnz00 what are you using instead?

As karma is now deprecated and coming up on EOL, we are no longer planning on any significant enhancements to this project and are instead going to focus on security updates, stability, and a migration path forward as karma's lifecycle comes to an end.
Thank you for supporting and using this project!


refactor(useAuthModal): move the useAuthModal hook and render into account context

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR updates the Alchemy project by refactoring the AuthModal component, introducing a MissingUiConfigError class, and restructuring context and hook usage.
Detailed summary

Refactored useAuthModal to throw MissingUiConfigError
Updated context types to AuthContextType
Renamed useAuthModalContext to useAuthContext
Updated PasskeyAuth and EmailAuth components to use useAuthContext
Added uiConfig to AlchemyAccountProvider
Introduced MissingUiConfigError in errors.ts
Updated AlchemyAccountContext and AlchemyAccountProvider in context.tsx

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Or did I miss something?

ah nope you're right, this does deal with the remounts issue since the component is statically rendered as opposed to being dynamically defined within another component


macos platformview UI blinking

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

build the attached example (works in xcode)
run it
plays a little with windows resize and the scroll
at some moment the UI will start blinking

Expected results

no UI blinking

Actual results

UI blinking

I think it comes from ClipRRect() around the platform view, without it all seems working well
Code sample
Code sample
source code

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
too many logs, quarantine..

Flutter Doctor output
Doctor output
[✓] Flutter (Channel main, 3.17.0-3.0.pre.20, on macOS 14.1.1 23B81 darwin-arm64, locale en-FR)
    • Flutter version 3.17.0-3.0.pre.20 on channel main at /Users/renanyoy/code/sdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6007b91a37 (2 weeks ago), 2023-11-07 02:43:32 -0500
    • Engine revision 7f4d56a7f4
    • Dart version 3.3.0 (build 3.3.0-102.0.dev)
    • DevTools version 2.30.0-dev.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/renanyoy/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.84.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.76.0

[✓] Connected device (3 available)
    • IPhone10.renan (mobile) • 00008020-000640992209002E • ios            • iOS 17.1.1 21B91
    • macOS (desktop)         • macos                     • darwin-arm64   • macOS 14.1.1 23B81 darwin-arm64
    • Chrome (web)            • chrome                    • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Reproducible using the code sample provided above.
https://github.com/flutter/flutter/assets/88313112/8a007bb6-84df-4949-b757-d382cee5c4fc

flutter doctor -v
[✓] Flutter (Channel stable, 3.16.0, on macOS 14.1.1 23B81 darwin-arm64, locale en-GB)
    • Flutter version 3.16.0 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db7ef5bf9f (8 days ago), 2023-11-15 11:25:44 -0800
    • Engine revision 74d16627b9
    • Dart version 3.2.0
    • DevTools version 2.28.2

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc1)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0-rc1
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 76.3.4
    • Dart plugin version 232.10072.19

[✓] VS Code (version 1.84.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.76.0

[✓] Connected device (5 available)
    • Pixel 7 (mobile)     • 28291FDH2001SA            • android-arm64  • Android 14 (API 34)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.1.1 21B91
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.1 21B74
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 14.1.1 23B81 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.17.0-15.0.pre.13, on macOS 14.1.1 23B81 darwin-arm64, locale en-GB)
    • Flutter version 3.17.0-15.0.pre.13 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 106667eb4b (12 hours ago), 2023-11-22 22:15:57 +0000
    • Engine revision f331e0afaf
    • Dart version 3.3.0 (build 3.3.0-152.0.dev)
    • DevTools version 2.30.0-dev.4
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc1)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0-rc1
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 76.3.4
    • Dart plugin version 232.10072.19

[✓] VS Code (version 1.84.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.76.0

[✓] Connected device (5 available)
    • Pixel 7 (mobile)     • 28291FDH2001SA            • android-arm64  • Android 14 (API 34)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.1.1 21B91
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.1 21B74
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 14.1.1 23B81 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

This seems to happen because these CAMetalViews are thrashing the main thread, sometimes to the point where core animation does not manage to update the server with new flutter surface. This is not something our compositor on macOS expects to happen. We only have two surfaces that we're flipping in order to not allocate more memory than needed, but in pathological cases such as this one we end up drawing into front buffer.
When obtaining backbuffer surface we don't check if is used by compositor, because generally it's not a problem if compositor still holds it at the beginning of frame for a few milliseconds. It does become a problem if compositor is using it for another 2-3 frames like in this example.
I'm not entirely sure what the best solution here is. We may need to handle situation when jank is not caused by Flutter.

Btw, have you considered using external textures for this? Using this many CAMetalLayers on platform thread is likely not going to result in good performance, it's just too heavy, but you should be able to render most of the workload to external texture and render those in flutter.

@knopp  it's just a stressing example to be sure it happens quickly. In my app, I use max 10 small 190x80 at a time on screen. also I pause all rendering as soon as the window enter live resizing... but it still happens sometime..
if there is a way to share MTLTexture with flutter, and display them using the flutter renderer, would be faster for sure.. but I don't know how do it..

Look at FlutterTextureRegistry (it's same on macOS and iOS). The texture object that you register needs to provide a CVPixelBufferRef. You can create CVPixelBufferRef from IOSurface through CVPixelBufferCreateWithIOSurface. The same IOSurface can be backing a metal texture. This will not be entirely trivial and will need some housekeeping, but if you get it right it should be much cheaper than using metal views. Plus you can do all rendering on background thread.
I'm suggesting this because even when the issue here gets fixed, you'll still be dropping frames with your current approach (dropping CA frames not caused by Flutter is the underlying reason for the flicker).

@knopp thank you, I will look at it. For my app all the real rendering is done in background, so it's not too important if the UI drop some frame sometime.. but it still better if not and if can spare some cpu cycles..

This is possibly relevant: https://github.com/flutter/flutter/issues/49757
CADisplayLink / CVDisplayLink on main thread reflect dropped frames, which should prevent raster thread from more frames than the compositor can display.

Actually, I just noticed, that because every of these platform views has a flutter outline, there are 19 total surfaces on Flutter side. That is way, way too much, and perhaps even bigger reason why we're missing core animation deadline.
Good news here is, I have a PR in progress just for this: https://github.com/flutter/engine/pull/43301. I tested it, and it reduces the number of surfaces to 1 (2 when scrolling because of overlay). It seems to completely get rid of the issue.

@knopp I think I got the fix on master branch, seems better.. but it's still happening sometime when using lots of camera inputs.. they must hang a lil the main thread when they are starting.. I think would be nice to have a frame counter or something like that to sync the compositor thread and the renderer thread in flutter.. in case something hang... I'll try to avoid the camera start on main thread still ;)

I think a main thread display link would help here. It is on my TODO list. In any case, if you can provide another example that breaks, it would be quite helpful.

Reopening because with opacity set on large number of platform views, there is still flicker because we're pushing more frames than the compositor can flip. This still needs to be addressed.

There are two problems here:

With opacity = 1 all those CAMetalLayer will hog the platform thread preventing render server to take over front surface. After which we keep writing to the back buffer, which is still used by the render server. For this we should try to detect the situation and possibly switch to multiple buffers. Also I'd strongly suggest drawing to this many metal layers on platform thread.
With opacity < 1, raster threads gets blocked for several frame periods waiting in [commandBuffer waitUntilScheduled], after which it returns several frames in a burst. We could possibly try skipping rasterization of these frames, but the whole thing seems a bit pathological, I even had whole computer freezing when trying to profile this. Long story short, CAMetaLayer really doesn't seem to behave nicely when parent layer is not opaque (clip might also matter).

@knopp I confirm, I got multiple computer freezes lately when minimizing and reverting back the app window.

@knopp , little update, since one of the last sonoma update, apple has fixed the freezing.. it should be easier to debug this problem now..

I'm fairly confident that we're being too optimistic with single back buffer here. I really wanted it to work, but there's no way to know for sure that the compositor has picked up front surface. And when that happens (and compositor misses the frame), we end up drawing to the front surface while it is in use.
I think we're going to need similar logic to retrieve surface as FlutterMetalLayer is using.


Frame grammatical meaning in <>

Fixes #56

@rultor merge

@rultor merge

@suseika OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@suseika Done! FYI, the full log is here (took me 5min)


Add support for resolving container image digests by tag name

Docker tags are not immutable and the same tag can be assigned to the same image over and over.
However they are easier to deal with than, for instance, sha digests.
In an example scenario, say that you have a deployment with 4 replicas, all referencing "my_image:latest".
If you scale up the deployment, or delete a pod say, a month later, it is not possible to guarantee that the exact same version is running.
The idea is to be able to specify an image by tag (i.e. my_image:latest) but a compile time, turn that tag into an immutable reference (sha)
This way it will be easier to have the guarantee of running the same image consistently for all pods.

I've been exploring this topic lately, and am wondering about:

how we should identify whether the user actually means to write a docker tag in a file or not, that is, if any pieces of text that resembles foo:bar format may not necessarily refer to docker tag. Maybe we intend to limit this feature only to FROM line in Dockerfile?

How to get sha256 digest from docker tags. There are docker APIs v2 (run by Docker daemon), but I don't actually know if we can take it for granted that this service is locally/remotely available. Another way of course if to run some docker pull (or docker images --digests, if the tag was already used) command behind the scene and parse the digest, but I feel like pull is a bit of overkill. Am I missing a Docker feature that you have on mind to accomplish this task?

I have the impression that this could actually be easier to solve if #197 was done. Then you could get the latest digest with a custom command at compile time.

@uberspot
Agreed! That way we can support more commands, and let the user decide whether to use tags or digests to start with, as well as where to get the digest from. I'll look into #197 then.

ping ?

I can see what the problem is, but I don't think kapitan should be doing anything about it.
If a user really specified image:latest then I don't think kapitan should magically replace that with image:sha_of_latest_image_currently_available
The answer to that depends on each user deployment process and should probably be solved in CI/CD pipelines or with the image building process and appropriate tagging.
If we want to go ahead with this, then we should still continue to support all 3 use cases:

use label and never change it
use sha and never change it
use label and replace it with sha at compile time

we could use https://get-kbld.io/ instead


Add DPG: Pharmarun

Automatic addition of a new digital public good submitted through the online form available at https://digitalpublicgoods.net/submission

Linked to #878

Digital solutions that are no longer active, or do not provide the required documentation needed for review, will be moved into the archive hence moving Pharmarun to archives as per the archiving policy. Thanks.

Digital solutions that are no longer active, or do not provide the required documentation needed for review, will be moved into the archive hence moving Pharmarun to archives as per the archiving policy. Thanks.


operator project-quay (3.8.10)

Add 3.8.10 to community operators

/merge possible

/merge possible


correctly rounded divide test for half is not using a correctly rounded reference

The new correctly rounded divide test for half precision, located in binary_operator_half.cpp is using an fptr for its reference function and computing the reference like this:
    s[j] = HTF(p[j]);
    s2[j] = HTF(p2[j]);
    r[j] = HFF(func.f_ff(s[j], s2[j]));

Here func.f_ff works out to reference_divide().  So r[j] starts with the double precision rounded result of the divide, rounds it to single precision and then rounds that to half.  That's 3 roundings instead of the required single rounding.
Shouldn't this test be disabled until a correct reference is used?

The new correctly rounded divide test for half precision

Which reminds me, we should probably disable the correctly rounded tests for fp16 and fp64; see #1901 .
However, for fp16 I believe the divide_cr and divide tests are identical, since fp16 division must be correctly rounded (at least for the full profile).  So if I'm not mistaken this issue also affects the regular fp16 divide test?

When running the new fp16 divide test I get this kind of error:
ERROR: divide: 0.500000 ulp error at {0x1.428p-13 (0x090a), -0x1.ep+6 (0xd780)}
Expected: -0x1.6p-20  (half 0x8016)
Actual: -0x1.5p-20 (half 0x8015) at index: 61714

As the specs state that fp16 precision for divide is <= 1 ulp, I'm not sure if this is a real error, or a bug somewhere in the CTS.

Alright, it feels like the the half_ulp is set to 0.0f here. I'll open another issue and will make a PR for it.

~Alright, it feels like the the half_ulp is set to 0.0f here. I'll open another issue and will make a PR for it.~ My mistake, I was looking at the embedded profile. For the full profile, the division needs to be correctly rounded.

For the embedded profile we need to account for the <= 1 ulp, so we'll still need a separate issue I think.

@b-sumner are you seeing any failures related to the excess roundings?  If so, could you share some of the problematic input values?

I haven't studied it closely, but this suggests some theorems for safe double rounding that could be helpful: https://dl.acm.org/doi/abs/10.1145/221332.221334

I thought I saw another patch about dropping the correctly rounded tests for non-fp32 floating point types, so perhaps this should be closed.
But while I'm here I want to ask a related question about the max ulp error for half division.  What I see in function_list.cpp is:
412     { "divide",
413       "/",
414       { (void*)reference_divide },
415       { (void*)reference_dividel },
416       { (void*)reference_relaxed_divide },
417       2.5f,
418       0.0f,
419       0.0f,
420       3.0f,
421       2.5f,
422       INFINITY,
423       FTZ_OFF,
424       RELAXED_ON,
425       binaryOperatorF },
Line 419 sets the half_ulps to 0.0.  I would like to know where in the spec this requirement of correct rounding for half division appears or if the specified error is higher but simply not properly reflected in the test.

I would like to know where in the spec this requirement of correct rounding for half division appears

Table 69 in https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_C.html#relative-error-as-ulps

Thank you.

@b-sumner I just compared all reference values with equivalents divided with single precision - there are no differences. Could you share your error printout with problematic case ? Thanks


Update docs to use 'path()' routing rather than 'url()' routing.

Refs #7482. (Perhaps to be merged into there at a future date, but making these changes independently for now so we can get up and running on reviewing them)
This is an initial pass on the documentation for path() style routing.
Still need to:

Review if there are any sections discussing "named vs unnamed groups" and remove or alter those as appropriate (I assume we should only use named groups with the new style syntax, and only need to discuss unnamed groups in the context of `path_regex?)
Add docs for path_regex(). (Figure out where is most appropriate and how much depth we go into.)
Add docs for convertors, and discussion about the convertor syntax during eg. intro and tutorial sections.

Some things that the docs changes highlighted to me that may or may not already be addressed in #7482...

Ensure that character literals such as "." in a path expression are escaped when creating the URL regexs.
I think we should simply error if a leading ^ literal or a trailing $ literal is used in a path() expression. It's almost certain to be user error, rather than intended syntax. (The error message can suggest that a user to use an explicit path_regex() if they want complete control over the exact syntax.)
We're almost never using unnamed groups now. (and eg. view.args will almost never used). Not a problem but worth highlighting.

Preliminary reviews from anyone are very welcome.

I agree with not using args (unnamed groups). The new syntax compiles to named groups, and that is "necessary" for converters to work.
Escaping the non-parametrised segments already happens, though I should add a testcase for that as well.
We might want to deprecate support for unnamed capture groups all-together. Yes, named capture groups look less pretty, but with the new syntax it's beautiful again.
Leading/trailing ^$ can be warned on, although I highly prefer just warning in a check over erroring out...

@tomchristie would you mind if I take this over? or there are other takers?

I think it's best to wait for https://github.com/django/deps/pull/41 to be merged and for https://github.com/django/django/pull/7482 to move forwards before resuming efforts here.

Continued in https://github.com/django/django/pull/9072.


Ionic Cards on the Roadmap?

Was looking through the Ionic docs and saw the "Ionic Cards" components and wondered if there were on the roadmap for Meteoric:
http://ionicframework.com/docs/components/#cards

None of the components in the http://ionicframework.com/docs/components/ list require any Meteoric integration - they are just static CSS components and are all already included along with the https://github.com/meteoric/ionic-sass package.

Ah, that makes sense. Thanks!


Module 2 exercises [replace with your name]

Please "drag & drop" exercise 1 file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 2 and make sure to take
the post-training survey.
Uploading WS2_M2E2_Submission.docx…

Hi Afenya, could you reupload your submission? The document did not properly load into Github. Thank you!


pre trained models

thank you for your job
Can you upload the pre-trained models?
thank you

Hello @orydatadudes! Thanks for your feedback.
You can take the pretrained models from here.

Hello @orydatadudes! Thanks for your feedback.
You can take the pretrained models from here.


Small fixes

Cleaning up a few things I found when trying to run the evaluation demo on a fresh repo copy.
The only actual bugs were:

We needed to be creating the cache directory structure earlier; with ..., save_path.open("wb") as out_file otherwise errors on a fresh repository.
Use of the cache was being set to different default values in different places. I changed things to make the default to use it.

The other changes are a bit more stylistic and/or pedantic:

I replaced the contents of data/README.md with "see the help function" because we don't want to have multiple sources of truth (one is likely to end up out of sync otherwise).
I made the path to included-divisions.txt an argument in load_metadata with a default, rather than a strictly hard-coded value. In so doing, I decided the default place to call this from was the top level of the repo, rather than /data.
I changed the evaluation demo workflow slightly.

Great catches, thanks!


Cannot connect to server 'https://gpt.pawan.krd/'

Trying to join the server all day today:
Cannot connect to server 'https://gpt.pawan.krd/'

Have you blocked me by IP address? Why was I able to connect via VPN? If yes, then why?

dm me your IP in discord i will check if your IP is blocked or not

Can you please tell me where can I find your Discord?

This is the link to his Discord server: https://discord.com/invite/VCdWGREsmd which can also be found in the README.md of the repository.


Setting poller period to 0 doesn't disable poller mechanism

As per title.

Fixed in https://github.com/ilcato/homebridge-fibaro-home-center/pull/246


Carthage doesn't download Firebase binaries on Apple M1

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.2
Firebase SDK version: 7.1.0
Installation method: Carthage
Firebase Component:  All
macOS version: 11.0
Chip: Apple M1

[REQUIRED] Step 2: Describe the problem
Carthage doesn't download any firebase binaries on Apple M1 with Big Sur.
When running carthage update --no-use-binaries  --cache-builds --platform iOS, the empty json has downloaded.
*** Downloading binary-only framework FirebaseDynamicLinksBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseDynamicLinksBinary.json"
*** Downloading binary-only framework FirebaseRemoteConfigBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json"
*** Downloading binary-only framework FirebaseAuthBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAuthBinary.json"
*** Downloading binary-only framework FirebaseCrashlyticsBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseCrashlyticsBinary.json"
*** Downloading binary-only framework FirebasePerformanceBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json"
*** Downloading binary-only framework FirebaseProtobufBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseProtobufBinary.json"
*** Downloading binary-only framework FirebaseInAppMessagingBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseInAppMessagingBinary.json"
*** Downloading binary-only framework FirebaseMessagingBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json"
*** Downloading binary-only framework FirebaseAnalyticsBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
*** xcodebuild output can be found in /var/folders/74/lws4xlls7fg_m4pkl499hp6h0000gn/T/carthage-xcodebuild.SOqsl2.log
*** Downloading binary-only framework FirebaseAnalyticsBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
*** Downloading binary-only framework FirebaseAuthBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAuthBinary.json"
*** Downloading binary-only framework FirebaseCrashlyticsBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseCrashlyticsBinary.json"
*** Downloading binary-only framework FirebaseDynamicLinksBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseDynamicLinksBinary.json"
*** Downloading binary-only framework FirebaseInAppMessagingBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseInAppMessagingBinary.json"
*** Downloading binary-only framework FirebaseMessagingBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json"
*** Downloading binary-only framework FirebasePerformanceBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json"
*** Downloading binary-only framework FirebaseProtobufBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseProtobufBinary.json"
*** Downloading binary-only framework FirebaseRemoteConfigBinary at "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json"

{
  "Mac" : [

  ],
  "watchOS" : [

  ],
  "tvOS" : [

  ],
  "commitish" : "7.1.0",
  "iOS" : [

  ]
}

Steps to reproduce:
Relevant Code:

Hi @d-date - hope you're doing well.
I'm not sure about the --no-use-binaries bit since Firebase only offers a binary distribution of Carthage, but right now Carthage won't work well with Apple silicon Macs using the M1 chip due to Carthage's lack of support for XCFrameworks: https://github.com/Carthage/Carthage/issues/2799
We can't include the simulator slice for arm64 as well as the arm64 device slice, they simply can't be put into a .framework together. It's unfortunate, but until Carthage can support XCFrameworks it's going to be a poor experience for Carthage since you can't work on the simulator. You may be able to still pull the frameworks down if you run on device only, and potentially get rid of the --no-use-binaries flag, I'll try it out on my Mac mini later today.
Sorry about that!

Hi @ryanwilson
I'm doing well, thank you🙂
You can ignore no-use-binaries option since binary hasn't effected.
I see your points and it's hard to continue to use Carthage until XCFramework be supported.
I think the workaround to make us to use them in Carthage is Firebase team prepares binary for Apple M1, and prepare other jsons for versioning.
(Looks so hard to do maintenance)
Since SwiftPM is also not work for us now(#6472), it seems the only way to use Firebase in M1 now is use CocoaPods with Rosetta and ffi gem.
Thank you for your help!

@d-date FYI, the Firebase does also support a binary zip packaging that as of 7.2.0 is comprised of xcframeworks for everything except FirebaseML. See the download at https://github.com/firebase/firebase-ios-sdk/releases/tag/CocoaPods-7.2.0

@paulb777 Thank you for your suggestion. It's also good way to introduce as pre-build binary (except versioning).

Carthage update on plans for binary xcframework support at https://github.com/Carthage/Carthage/pull/3071#issuecomment-747085975

Latest "master" branch of carthage compile xcframework correctly.
Can we have a release version with the right firebase .xcframework that work on M1 macs please ?

Latest "master" branch of carthage compile xcframework correctly.
Can we have a release version with the right firebase .xcframework that work on M1 macs please ?

@mmdumi thanks for pointing out that Carthage has merged support. However, it's still not in a release so we can't break all existing Carthage users until at the very least there's a release.

@mmdumi thanks for pointing out that Carthage has merged support. However, it's still not in a release so we can't break all existing Carthage users until at the very least there's a release.

Actually, I haven't seen evidence that binary support for xcframeworks has yet merged. The PR that added support for source xcframeworks explicitly says it will be addressed in a subsequent PR.

Actually, I haven't seen evidence that binary support for xcframeworks has yet merged. The PR that added support for source xcframeworks explicitly says it will be addressed in a subsequent PR.

As I understand it, no-use-binaries is useless on M1 Macs because there are no arm64 binaries. Which seems kind of silly but I think I read you must build each dependency.

As I understand it, no-use-binaries is useless on M1 Macs because there are no arm64 binaries. Which seems kind of silly but I think I read you must build each dependency.

It's there now. After getting 0.37.0, it suggested I rerun with a switch to build an XCFramework, which worked, but then a dependency I am getting from SPM is failing on running in the sim because it can't find the x86 binary. Which makes no sense as I am on M1 and Xcode is not running in Rosetta?

Carthage PR in progress at https://github.com/Carthage/Carthage/pull/3123

Any update on this? The PR was merged

I'm planning to investigate this week.

@d-date FYI, the Firebase does also support a binary zip packaging that as of 7.2.0 is comprised of xcframeworks for everything except FirebaseML. See the download at https://github.com/firebase/firebase-ios-sdk/releases/tag/CocoaPods-7.2.0

I think the download link you provided doesn't include FirebaseFirestoreSwift.

Correct the Swift packages are so far only available via CocoaPods and SPM.

On further investigation, the Carthage release PR with the fix is open and not yet released.  I'll follow up when 0.38.0 is available.
In the meantime, if anyone wants to validate that the Firebase xcframeworks work with the pre-release, it would be appreciated.

if anyone wants to validate that the Firebase xcframeworks work with the pre-release, it would be appreciated.

@paulb777 Just validated, works for me 👍

Thanks @dmhts!  In that case we should be able to publish a Carthage xcframeworks update soon after 0.38.0 is available.


(python) Fix error related to having an ending double quote in the docstring

Before:

The error is

Missing closing quote ["]

After:

Fixes #2247

Thanks! One small change suggested.

Thanks @dvdsgl ! I will update it once the suggestion is available. I didn't see any, maybe it is still in the review queue?


How is Context.del being called?

I have an issue where my program is hanging consistently at a certain point. Oddly, If I ctrl-c, it just prints out a zmq error and continues happily after that. It's hanging in Context.__del__, but what I can't figure out is how/why Context.__del__ is being called. My code isn't calling it explicitly, and I haven't closed the context. I inserted a called to traceback.print_stack() in sugar/context.py inside the method __del__ and I get the following traceback:
  File "client.py", line 289, in _parse_packet_header_v10
    for name, p in zip(names1, params1):
  File "venv//lib/python3.6/site-packages/zmq/sugar/context.py", line 65, in __del__
    traceback.print_stack()

where names1 and params1 are lists of strings, so I don't see how zip or for loop based iteration would lead to calling __del__. Is this garbage collection or something else? Any ideas?
Based on a previous issue I've set LINGER=0 for all sockets I open anywhere in my code, so even given that __del__ is called I'm confused about why it is hanging.

Object.__del__ is called when an object is deleted by the interpreter. Usually this happens when a variable goes out of scope, but can occur at very different times when there are cyclical references or other things that prevent that. Most often, it's called either when:

a function returns, if the context is defined only within the function
a parent object is deleted, if the context is an attribute on the parent
interpreter shutdown, if not cleaned up elsewhere

For contexts in particular, __del__ calls term() if term has not already been called. Per libzmq's specification, this will block until:

all associated sockets have been closed, and
all pending messages have been delivered (OR expired due to non-negative LINGER)

The most common cause of term hanging is failure to close sockets. Usually this is resolved by Python deleting dereferenced objects in topological order (sockets hold a reference to the context, context holds only weak references to sockets), but creating reference cycles in other objects can result in out-of-order deletion.
The fix is ~always to explicitly close sockets and contexts when you are done with them.


Workflow for running ttbar analysis from AGC on REANA

The files for running ttbar analysis at REANA:

READ.ME
Snakefile
prepare_workspace.py
Changed ttbar analysis notebook
Additional merging notebooks.

I'm not sure if the environment section is explained properly in README file.
Close #2


Ladybug in Ibis4Example not loading properly (Docker related)

Describe the issue
Ladybug does not load in Ibis4Example. According to Niels this has to do with the docker deployment.
Reporter
Daniel Langeveld

To Reproduce
Steps to reproduce the behavior:

Go to: https://frank4example.frankframework.org/iaf/gui/#!/testing/ladybug
Observe

Screenshots

Environment
FF! 7.7-20211222.121243: Ibis4Example
Running on 5e7f472cb95a using Apache Tomcat/8.5.60
Java Version: OpenJDK Runtime Environment (1.8.0_275-b01)
Heap size: 314M, total JVM memory: 1768M
Free disk space: 5GB, total disk space: 50GB
Up since: 2021-12-22 15:59:00 (1h)
Additional Context
Ladybug report

issue appears to be caused by removal of context root by reverse proxy

This has been fixed ;)


Can I run it directly?

Can I run it directly? With or without changing things

Hi, this is a maven project, and you will need JDK13 and Apache Maven installed and configured. The program should work exactly like the original version FSD if everything works as expected.
Have fun!


Investigate status of metadata-only submissions

[x] Create a submission
[x] Validate metadata
[x] Validate graph
[ ] Export

@gabsie should we prioritise investigation for export of metadata-only submissions?
this is probably going to be a problem downstream
discuss again the aim of this export with Will?

at the moment metadata only submissions are non exportable
discuss priority of making metadatata only submission exportable
@idazucchi add to wrangler agenda