ReactQueryCacheProvider may loose queryCache

Describe the bug
ReactQueryCacheProvider creates queryCache when it's not defined by developer.   It means React may forget previous results and call the factory again, the factory will create a new query-cache instance.
From: https://github.com/tannerlinsley/react-query/blob/master/src/react/ReactQueryCacheProvider.js
 const resolvedQueryCache = React.useMemo(
    () => queryCache || makeQueryCache(),
    [queryCache]
  )

Expected behavior
ReactQueryCacheProvider should either to not create anything and notify developer when the property is not defined, or create in safe manner.
const resolvedQueryCacheRef = useRef(null)
const previousQueryCacheRef = useRef(queryCache)

if (previousQueryCacheRef.current !== queryCache) {
  previousQueryCacheRef.current = queryCache
  resolvedQueryCacheRef.current = null
}

if (resolvedQueryCacheRef.current === null) {
   resolvedQueryCacheRef.value = queryCache || makeQueryCache()
}

or
let [resolvedQueryCache, setResolvedQueryCache] = useState(() => queryCache || makeQueryCache())
let [previousQueryCache, setPreviousQueryCache] = useState(queryCache)

if (previousQueryCache !== queryCache) {
   resolvedQueryCache = queryCache || makeQueryCache()
   previousQueryCache = queryCache
   setPreviousQueryCache(queryCache)
   setResolvedQueryCache(resolvedQueryCache)
}

or
const [resolvedQueryCache, setResolvedQueryCache] = useState(() => queryCache || makeQueryCache())
const previousQueryCacheRef = useRef(queryCache)

useEffect(() => {
   const hasChanged = previousQueryCacheRef.current !== queryCache
   if (!hasChanged) return
   previousQueryCacheRef.current = queryCache
   setResolvedQueryCache(queryCache || makeQueryCache())
}, [queryCache])

Depending on your preference, side-effects, number of renders.

Great issue! This is definitely a problem. With the global queryCache becoming deprecated in v3 (#772) ReactQueryCacheProvider will become required, which makes this issue even more important to get right.

As of the latest react release I don't believe there is any useMemo garbage collection in place, so this isn't a super urgent bug right now, just something that should be fixed to avoid potential issues at some point in the future. (Yes I did contribute to this bug :disappointed: )

My coworkers actually ran into this problem today. I introduced the <ReactQueryCacheProvider> for server side pre-fetching with NextJS and they saw their useQuery hooks no longer reacting to setQueryData() calls. An easy work-around is creating your own queryCache instance with makeQueryCache() and passing it to <ReactQueryCacheProvider>. I thought this comment might be useful for people running into the same issue.

Looks like good workarounds for this issue are here for those using it in SSR and also with new plans to move to separate client and cache instances (and respective new providers), this should no longer be an issue in the next major version. That said, going to close this issue.


Add Delta Lake and Iceberg testing support

Overview
Support delta lake and iceberg in tests.
Checklist

[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] README.md updated and added information about my change
[ ] CHANGELOG.md updated and added information about my change

Currently minio, hive metastore versions are set to latest. This is probably not desirable as it might induce flakyness.

Please resolve the conflitcts with master.


Whitelisting pages

It would be useful to be able to whitelist pages. In other words, choose which pages get published, rather than having to exclude them.

I agree with the above, but I'd also like to do that from the meta section in the page itself.

Will look into this sometime this week! @nateritter, do you mean having a potential publish flag in the front matter of the Markdown? So something like
---
title: Example Post
publish: true
---

Content here...

Exactly!

You could do it the other way around (if you're using templates).
If your note-template looks something like the following, all notes would by default be excluded (I'm using templater instead of Obsidians default template-plugin btw):
---
title: "<% tp.file.title %>"
creation date: <% tp.file.creation_date() %>
draft: true
---
# <% tp.file.title %>
<% tp.file.cursor() %>

The above template workaround works for new notes but not large imported vaults (if you don't want mass changes to notes). Another workaround would be to add an ignoreFile RegEx in config.toml that ignores all files without some string in the file name (say, an emoji) which you can then add to the file name to whitelist the note.

My current workaround is by setting draft: true as a default frontmatter using cascade.
# config.toml
# make draft by default
[[cascade]]
draft = true
[cascade._target]
  path = '/notes/**'

This unpublishes all markdown files under '/content/notes/' unless I write draft: false individually in the frontmatter. Example:
---
# markdown file in /content/notes/
title: Example Post
draft: false
---

(I'm not sure why it doesn't seem to work if I try to do it for everything under '/content/' though)

This issue should be fixed in Quartz 4. I'll be closing it for now but please reopen this issue if this persists in the new version.


Update esy.json for recent esy

This updates esy.json for recent esy.

@andreypopp Thanks! Did you mean to commit esy.lock.json? I'm still not sure what to do with that file :)

@aantron yes! the idea is that if someone clones the repo they will get exactly the same versions as defined in esy.lock.json so they won't need to run solver and get into some state which isn't buildable (well, tbh it's rare with opam but happens too).
On CI it might makes sense to test from time to time that dependencies are solvable (by removing esyi.lock.json and running esy install && esy build).

Btw: I was able to try out repromise_lwt with just:
{
  "name": "repromise_lwt",
  "version": "1.0.0",
  "esy": {
    "build": "dune build -p repromise_lwt"
  },
  "dependencies": {
    "@opam/base-unix": "*",
    "@opam/lwt": "*",
    "@opam/repromise": "aantron/repromise",
    "@opam/result": "*",
    "@opam/dune": "*",
    "@esy-ocaml/reason": "*"
  },
  "devDependencies": {
    "@opam/merlin": "^3.0.5",
    "ocaml": "4.6.x"
  }
}

Fetching yet to be released repromise from github!

Thanks! I'll try restoring the Travis esy build as a follow-on to this PR. Would you mind PRing the esy.json to repromise_lwt? I'd be quite happy to merge it :)

@andreypopp BTW Repromise is released, it is @aantron/repromise in NPM :) https://www.npmjs.com/package/@aantron/repromise

Never mind, that's the JS one, you're using native, and that's not released indeed..!


AWS Stencils Become Brighter Than Before

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Before 14.9.9, which is the latest update related to AWS stencils update, the stencils was for light background.
After the update, the stencils replaced to the one for bark background.
To Reproduce
Steps to reproduce the behavior:

Go to 'Search Shapes'
Search for any AWS resource stencils
Click the stencil
See error

Expected behavior
Maintain the original stencils set with light background.
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version: After (including) 14.9.9

Desktop (please complete the following information):

OS: Windows and macOS
Browser: Firefox and Chrome

Additional context
AWS provides 2 sets of stencils, one for light background and the other for dark background.

Having a consistency in draw.io would be great because lots of diagrams are created before 14.9.9.

Edit (10/28): Update inline typo.

Will be fixed in next release


A proposed extension to CCF_AS_CT.owl

STATUS: Draft.  Discussion required prior to implementation.
In cases where tables do not validate well, CCF_AS_CT.owl can have too few relationships to be useful.  Even in cases that do validate, some terms may float free from the graph, even if they are well connected in Uberon & CL. The proposal aims to take advantage of that connectedness.
Proposal:
For every orphan term (one with no existential restrictions), find all relationships by permitted relation types in the redundant graph to other terms the table.  Then use standard redundancy stripping (robot reduce) to remove any redundancy.   (I'm not sure of the best way to find orphan terms)
Note:  we need to ensure CCF.owl has fully axiomatised RO object properties for this to work - but we should make sure of that anyway.

I can take the orphan terms from the class_{organ}_log files and double-check in the validated cases.
Are there any restrictions on only checking CT-CT or AS-AS, or CT-AS?

Initial spec is a bit sketchy
If we assume single inheritance - which I think holds for most or all the tables, then I think it would be safely to take the subject terms of all non-validating edges and add relations for all of those.  Also all this should be added to separate files and merged into the final product, as I think it would be very confusing for these term to show up in the graphs.
new Spec
Generate a new file for each table, containing the following:

For each nonvalidating pair ASn+1-ASn, add all subclassof/part_of* relationships between ASn+1 and every other AS term in the table.
For each nonvalidating pair AS-CL, add all part_of** relationships between CL and every AS term in the table.
For each nonvalidating pair CL-CL, add all subclassof relationships between CL and every other CL term in the table

Merge all of the new files into the final release file, making sure there is a REDUCE step after the merge to strip redundancy.
* We could consider connected_to here too, but need to test that redundancy stripping is sufficient. Leave out for now.
** We could consider overlaps here too, but need to test that redundancy stripping is sufficient. Leave out for now.
** We could consider develops_from here too. Leave out for now.

Request for Josef - make additional merged artefacts for each organ/table.


Added solution for Merge Sorted Arrays

Merge sorted Arrays is not an algorithm kindly look into it

I have added it in the correct section. Please have a look


adding spades

This should be ready after reviewing/merging: https://github.com/qiita-spots/qtp-sequencing/pull/37

Thanks so much @antgonza


PHP 7 support?

This may just be a case of lack of documentation.
The README only mentions PHP5. Does this software work with PHP 7? More specifically 7.3 and the upcoming PHP 7.4?

i tried on php7.3,is ok

Thanks


X-RateLimit-Reset incompatible with Github

Rule 153:  defines three headers for rate limiting (apart from Retry-After):

X-RateLimit-Limit
X-RateLimit-Remaining
X-RateLimit-Reset

I believe they are borrowed from Github's API, but they differ in how they interpret the X-RateLimit-Reset header:

The time at which the current rate limit window resets in UTC epoch seconds.
https://developer.github.com/v3/#rate-limiting

The relative time in seconds when the rate limit window will be reset.
http://zalando.github.io/restful-api-guidelines/#153

Github does define an example:
HTTP/1.1 200 OK
Date: Mon, 01 Jul 2013 17:27:06 GMT
Status: 200 OK
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 56
X-RateLimit-Reset:<PHONE_NUMBER>

Zalando doesn't define an example in the guidelines, but I'd expect this:
HTTP/1.1 200 OK
Date: Mon, 01 Jul 2013 17:27:06 GMT
Status: 200 OK
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 56
X-RateLimit-Reset: 2513

Is it intentional that we differ from Github here?

Other Companies/APIs that use the same approach as Github:

Twitter (note additional - in Rate-Limit)
Vimeo
Hipchat

I found some that use relative seconds, but none of the big players.

Reddit seems to use seconds.

Good point and good investigation.
@whiskeysierra Wasn't it you writing the initial rule ;).
I think we should discuss this in the next guild meeting. Having a difference to a common understanding is a problem, but changing the rule isn't optimal too.

Nope, not that I know of.
On Mon, Apr 16, 2018, 10:44 Tronje Krop<EMAIL_ADDRESS>wrote:

Good point and good investigation.
@whiskeysierra https://github.com/whiskeysierra Wasn't it you writing
the initial rule ;).
I think we should discuss this in the next guild meeting. Having a
difference to a common understanding is a problem, but changing the rule
isn't optimal too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zalando/restful-api-guidelines/issues/379#issuecomment-381524992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaPnSOgKIHWKcR8_SfaJ3P9jnoBR2cPks5tpFoBgaJpZM4TVN6N
.

I prefer to stick with the current implementation:

The current implementation follows the same specs of Retry-After;
X-RateLimit-Reset and Retry-After are better to be aligned;

imho

X-RateLimit-Reset:<PHONE_NUMBER> is potentially broken because it relies on client-server ntp synchronization and on jitter added to the date by the server
in my spec I advertise the server to only expose seconds, the client to support both (seconds and unix timestamp)

@whiskeysierra @tkrop I'm preparing a draft RFC proposal on throttling headers,
using the same semantic provided here.

https://github.com/ioggstream/draft-polli-ratelimit-headers
https://ioggstream.github.io/draft-polli-ratelimit-headers/draft-polli-ratelimit-headers.html

Are you interested in contributing?

Answered on twitter: https://twitter.com/whiskeysierra84/status/1151464580855599104


Feature request: add "copy address to clipboard" button in the wallet

The Issue
Almost all wallets have "copy address to clipboard" button. It is just more convenient and safer (if you miss selecting the entire address while copying)
Expected behaviour
Just a simple button that copies current address to clipboard
Anything Else
@liamcardenas and @lavradis could work on this

@LavRadis is working on this

This should be really easy to add. There is a copybutton prop (called
something different) that I added for the shapeshift deposit address.
On Dec 15, 2017 12:38 PM, "Liam Cardenas"<EMAIL_ADDRESS>wrote:

@LavRadis https://github.com/lavradis is working on this
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/875#issuecomment-352066330,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQGcjp9HBaoolYCZap1VJgIt9aYZPHECks5tAq51gaJpZM4RDwgr
.

I was curious how easy this was, and I found it was so simple that I just did it.

Way to steal @LavRadis 's thunder... :p

@LavRadis you should look at https://github.com/lbryio/lbry-app/issues/702 next - @seanyesmunt recently added this to the Shapeshift process so maybe it's not too difficult :)


Add Group Skipping to A11Y Test Docs

Group Skipping is not a part of writing A11Y Tests where it should be included. Need to add info about it to: https://wiki.hybris.com/display/spar/How+to+implement+accessibility+tests+and+fixes

Group skipping section added to wiki


Document that shortcut I use to create a test document

(Requires use of common|mdemo.md which is used by the gallery site)

{{ inc "common|mdemo.md" }}


Epic/ai summary

Related issue
Result
Work list
Discussion

@choisohyun 님~ draft 남은 것 close 부탁드릴께요!!


Remove Event.INIT; move Event.TRAINING_START to before the DDP

Once #43 is merged in, then Event.INIT can be removed.
Event.TRAINING_START can be moved up to the line right before ddp.prepare_module(). All existing algorithms that currently run on training start would be compatible with this change.

Augmix: :heavy_check_mark:
Colout: :heavy_check_mark:
Curriculum Learning: @moinnadeem what is being done on training start? I do not see any inputs or outputs being preserved.
Randaugment: :heavy_check_mark:
Sam: :heavy_check_mark:. In fact, it might be broken as it currently runs on training_start, after optimizers have been moved onto the device
Scale Schedule: :heavy_check_mark:
Seq Length Warmup: @moinnadeem what is being done on training start? I do not see any inputs or outputs being preserved.
SWA: :heavy_check_mark: This change would simplify this algorithm, as it would apply before the model is moved onto the device (and it wouldn't need to take that into account anymore)

TODO:

[ ] Implement and merge #43
[ ] Fix algorithms as described above
[ ] Refactor the training loop to support this change.
[ ] Update documentation. We frequently refer to TRAINING_START happening after the DDP fork and all DDP madness. This changes that. Will need to take a throughout read through the docs/ folder.

I'm not sure how I feel about removing INIT. I definitely agree it's hacky how Event.INIT currently needs to exist between model initialization and optimizer initialization to accommodate surgery, but #43 will allow us to fix those issues without just removing the entire event. I think INIT should be called at the end of Trainer initialization, and TRAINING_START should be called after Trainer.fit() is called. Note also that prepare_ddp_module() is now called within Trainer.__init__(), not Trainer.fit()

Surgery is fixed in #249, so we can now address this issue.

Addressed in #263. Kept Event.INIT; renamed Event.TRAINING_START to Event.FIT_START


Border gradient effect, for mobs reaching the bottom gate

Lights up a gradient at the bottom of the window, with either a blue or red gradient depending on if defense was healed or damaged.

I couldnt really notice this effect when I tested it (wasm). Maybe one of the for loops is over an empty eventReader? Maybe a component query isnt quite right?

I couldnt really notice this effect when I tested it (wasm). Maybe one of the for loops is over an empty eventReader? Maybe a component query isnt quite right?

The asset isn't uploaded yet. After we merge in #163 I am going to change them to be loaded with the UiAssets and upload them to s3.


feat: add validate workflow

Description
Runs integration tests in CD.
Towards #13
How Has This Been Tested?
Rand tests
Due Diligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

Also can you change the environment name in ci_terraform.yml to just staging so that we don't have 2 staging environments? Or can we remove an environment from the terraform ci as we don't really need one?

Also can you change the environment name in ci_terraform.yml to just staging so that we don't have 2 staging environments? Or can we remove an environment from the terraform ci as we don't really need one? We can also just make an issue to do this later.

Out of scope for this PR but sure I've updated it.


Upgrading to the latest version of CDK / Adjusted examples with new constructor signature

adjusting constructor parameter

Issue #, if available:
Description of changes:

Upgrading to the latest version of CDK
Adjusted examples with new constructor signature

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Waiting for this to be resolved before merging: https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci/pull/72


why does the image format is in jpeg and not in jpg ?

I just wanted to know, that's all.

Mostly to line up with this API (https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toDataURL) since that's what we're using to generate the image.
Good question though.


Default 'AutoUpdate' TAG name needs changing

Just tested this and it looks to me like line 28:
'AutoUpdate': os.environ.get('TagAutoUpdate', 'AutoUpdateTag'),
Needs changing to:
'AutoUpdate': os.environ.get('TagAutoUpdate', 'AutoUpdate'),
As then it works as per:
https://aws.amazon.com/blogs/security/how-to-automatically-update-your-security-groups-for-amazon-cloudfront-and-aws-waf-by-using-aws-lambda/
....apart from the fact that the article above mentions Python 2.7, and not 3.7, which is required.

experienced same ^^^

Experienced the same issue as well, please correct the function.
in the documentation it recommends to use Python 2.7 which is incorrect.

Just wasted 4 hours to find it out.

Got caught by the same issue today!
https://github.com/aws-samples/aws-cloudfront-samples/pull/26

Resolved


fix: container

Description
changed container height to min-height so it doesn't have a fix value of 100vh and can adapt to content that needs more space
fixes #188
Screenshots
If applicable, add screenshots about your changes
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)

How to test it
If applicable, describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Go to /confirm/20
set device width o 820px and height to 375px for example.

Checklist:

[ ] Doesn't break the current code.
[ ] Passes linters and test, also is building.
[ ] Doesn't have spelling or grammatical problems.
[ ] Doesn't have unnecessary comments or debugging code.
[ ] The branch is updated with the last dev branch changes.

I checked the issue described and I notice the layout is OK

The how to test guide is not working to me :(. I will pull the change on my local to test this


DO NOT MERGE

I will use this PR to check some issues with fix:format etc. do not merge

/fix:format

patch-1 branch on opentelemetry.io upstream got created by the last run of fix:format

https://github.com/open-telemetry/opentelemetry.io/actions/runs/6958843371/job/18934723020?pr=3588 was successful but didn't add any commit to my fork's patch-1 branch

/fix:format

https://github.com/open-telemetry/opentelemetry.io/actions/runs/6958897097?pr=3588+(comment) failed

worked


fix(button): Support anchor and button HTML attributes (#679)

I've chosen to extend React.AnchorHTMLAttributes<T> and React.ButtonHTMLAttributes<T> since these are the possible element types that can be rendered. However looking through the other components you seem to use HTMLProps<T> a lot as well. There doesn't seem to be any clear reason why this is used in some places and not in others.
I'm happy to change this to use HTMLProps<T> instead if that is the pattern you want to follow. It would make button consistent with icon-button.

Codecov Report

Merging #680 into rc0.10.0 will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           rc0.10.0     #680   +/-   ##
=========================================
  Coverage     94.88%   94.88%
=========================================
  Files            68       68
  Lines          2852     2852
  Branches        432      432
=========================================
  Hits           2706     2706
  Misses           50       50
  Partials         96       96

Impacted Files
Coverage Δ

packages/button/index.tsx
96.66% <ø> (ø)
: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 02da75c...838fbae. Read the comment docs.

I signed it!

CLA was not passing, but signed in https://github.com/material-components/material-components-web-react/pull/680#issuecomment-464043832


More improvements to template.

See commits one by one for reviewing and details.
reviewers: @kriskowal @malandrew @Matt-Esch
cc: @sh1mmer

Can you add a test to complain if the README isn't updated?

@sh1mmer I've considered adding a readme linter.
I searched for available packages to lint either readmes or markdown. I could only find readme-good which doesn't solve our need.
I would like to write a README linter, however it's non-trivial. I think adding it is out of scope for this PR, but if I have time I'll come back to it late next week.

@Raynos I think there is a difference between something applying a heuristic on the "goodness" of a README vs. something that just checks it's been updated from what was scaffolded.
E.g. I'd like to make the project with a failing test because the README needs to be updated to make it pass (and then you would delete the test one assumes).

@sh1mmer That's an interesting idea.
I'm worried about the user experience for that approach. Having a failing test automatically in your project that you have to delete feels a bit weird. It would also be hard to communicate what fails with a test.
The user experience would be better if we have a linter that checks your README, for a few reasons

People tend to write code & tests before the README, they want their tests to pass
The linter can output warnings or errors.
The linter is seperate from the test suite, people can write code & tests without fixing linting errors.

If we add checks I want to make sure it does not get in the way. I'd rather do it with a good user experience rather then bolt something on.

I think the linter could do the warning for sure. I'd be happy to put a "UPDATE THE README TO REMOVE THIS LINE TO MAKE THE LINTER PASS" or something in the README.md to make that trivial.
It would be nice to have a universal solution to this that isn't dependent on Uber internal tools for enforcement and works I equally well for open source. I figure a failing test is just TDD style and would work universally well for anything.
If the linter is part of the test suite I think that's very acceptable for this criteria.

Actually one thought that just occurs is that if we can assume git could have a test/lint that checks you updated the README if you update a version. That would work universally for new or existing projects. It's probably out of scope for this diff though, so I'd prefer to start with a simple solution.

Other than my one comment LGTM.

Noted, we need a README linter.
We can write a simple one that checks there are no TODOs in the README itself.
I don't want to block this particular PR to wait for that module though, so I'll circle back to it later this week if I have time.

I agree we shouldn't block on a README linter.


Enable Hiera 5

This commit enables the control repo to use Hiera 5 environment-level
hiera hierarchy. This means adding a hiera.yaml to the repo, and moving
hieradata/ => data/.
We should do this to the control-repo template new customers base off of
because in a Hiera 5 world, the global hiera.yaml should be very minimal
(possibly even ONLY having the console level), and everything else
(nodes, common) belongs in the environment hiera.yaml.
This control-repo template is how people start using Puppet. It should
reflect using our most modern technologies.

Seems good to me. I'll merge later on unless anyone disagrees. 👍

Approved 👍

Like it +1

The future is now. I'm gonna merge this.


Added ImageViewer Control to display full screen Image with Zoom, Pan & paging

A ImageViewer displays a full screen Image that allows Zoom, Pan, and paging through multipe images.
The image src can be a single image path String or a List of image strings to page through.
Example:
import flet as ft
def main(page):
    def show_image_viewer_click(e):
        img = e.control.data
        page.dialog = ft.ImageViewer(src=img, swipe_dismissable=False)
        page.dialog.open = True
        page.update()
    images = ft.GridView(expand=1, runs_count=5)
    for i in range(0, 60):
        images.controls.append(
            ft.GestureDetector(
                content=ft.Image(
                    src=f"https://picsum.photos/150/150?{i}",
                    fit=ft.ImageFit.NONE,
                ),
                data=f"https://picsum.photos/150/150?{i}",
                on_tap=show_image_viewer_click,
            )
        )

    page.add(images)
ft.app(target=main)

Sorry for the delay with reply... I honestly believe widgets like ImageViewer should be implemented as "out-of-band" Flet controls in separate libraries, that user can optionally add to the app (via flet build command).
We will create guidelines (there is an item on roadmap) on how to create a Python part (Python adapter) for a custom control and how to create and publish Flutter/Dart part of the control.
I think some of the existing or future Flet "core" controls could be implemented as optional "extensions", e.g. audioplayer, video, webview - they add a certain weight into the resulting app, but not all users need them.

I'm leaving this PR open as a possible candidate for testing OOB control extensions.

Aw, but it seemed like a simple, useful, general use UI function that so many apps use when you click on an image. I've used a full-screen Image Zoom feature in every Flutter app I've done, seemed like it should be a core feature, but it is up to you.
I hope I'll be able to use your OOB extension framework when deploying on Google Colab since that's my apps primary platform, I'm a bit confused how it's going to install a personal build of Flet there but will have to figure it out then. My Diffusion Deluxe app would be using the Image Viewer everywhere since the whole purpose of it is to generate high-resolution upscaled AI images that everyone wants to zoom into.. Check my progress at https://DiffusionDeluxe.com/screenshots and see what I mean, the project got really elaborate last year, way too many fun ways to use the Python AI code to make complex images..
Anyways, let me know when there's any updates, I look forward to expanding more features this year, thanks Feodor...

🤓 OK, could you please update this PR from main and fix the conflicts?

Looks like merging gone wrong - CI is failing: https://ci.appveyor.com/project/flet-dev/flet/builds/48927108/job/bb574ivys2ifw3d3#L145
shake is no longer required: https://github.com/flet-dev/flet/blob/main/package/pubspec.yaml#L23-L43

Thanks Feodor, I fixed those minor issues and got the changes merged.  Hopefully it's all good now, let me know if there's anything else I can do. Appreciate your hard work, trying to make it as easy as possible for ya..

Wondering how this control is going...

We need to make it in a separate package.

Wondering how this control is going...

Wondering how this control is going...

I had it all done, even though the commit might need to be redone because main was updated where I couldn't update my PR.  However Feodore then said it should be a separate package rather than core, which I have no idea how to do where I can still use it in my install without having to rebuild the package which I don't think would work for me in my Colab launcher.  I had it done almost a year ago and it sat, but for me this was still a much needed feature that I've been living without... So I don't know what the next step would be if we have any hope of a standard full screen image viewer.


Add BIP-49 support

It appears that for BIP-49 (which is used for TREZOR segwit addresses for litecoin) the address derivation is different. It would be nice to have an option for that.

See https://github.com/iancoleman/bip39/commit/6c08f364b30e711feac698546041388325a11834 which is included in the latest release (v0.2.0)


[FLINK-21069][table-planner-blink] Configuration "parallelism.default" doesn't take effect for TableEnvironment#explainSql

What is the purpose of the change
The configuration parallelism.default for table environment doesn't take effect for TableEnvironment#explain. Because PlannerBase#translateToRel doesn't invoke overrideEnvParallelism which configures the configuration into underlying StreamExecutionEnvironment and is invoked in translate. Method overrideEnvParallelism should be invoked in translateToRel and removed from translate.
Brief change log

PlannerBase#translateToRel invokes the method overrideEnvParallelism which configures the configuration into underlying StreamExecutionEnvironment.

Verifying this change

Modify testStreamTableEnvironmentExecutionExplain of TableEnvironmentTest to verify the test case whether the configuration parallelism.default takes effect in TableEnvironment#explainSql or not.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Compile is failed.

Compile is failed.

@wuchong sorry for the failure of scala style compile. I have updated the violation of TableEnvironmentTest. You could help to review.

@wuchong sorry for the failure of scala style compile. I have updated the violation of TableEnvironmentTest. You could help to review.


Bluetooth: ISO: Add check for pending ISO connections

Per the HCI spec it is not possible to send the
HCI_LE_Create_CIS command while an outstanding request
is pending. Since multiple ISO channels can be connected
in a single request, the solution implemented was
to iterate over all ISO connections and see if there was
any unicast ISO channels in the connecting state.
It also checks for the encryption pending state, which
is an additional check to make it simpler to handle in
the ISO layer, as once security have changed we would
not want to have to check for other pending ISO connections.
This adds a new return value to bt_iso_chan_connect,
and decided to properly document the return values the
function can return.
Signed-off-by: Emil Gydesen<EMAIL_ADDRESS>

I don't have the necessary understanding of ISO to review this PR in its current form. If you would like to me to, you will have to make the description more accessible.

Than you for the explanation. But I still don't understand what the purpose of this change is. AFAIU, without this change, the controller will just deny the HCI command. Isn't that ok?

Technically it is OK, but we would much rather avoid sending the HCI command if we know it will fail. We do that for almost all HCI commands in the host (and this is the primary issue that is being solved).

You are skirting around the "(or encrypting)"-bit like it's not important, but I suspect that this is the real reason behind this change.

To some extend, it is true that this is one of the reasons behind this change, i.e. there's no reason to start encryption if we know the next procedure (i.e. actually sending the HCI command) will fail, but this is not the main reason.

The commit message / PR description needs some love. Please rewrite it so it's obvious what motivates this change.

The motivation of this change is that we don't want to send an HCI command that we know will fail. I think this is already covered by the commit message by

Per the HCI spec it is not possible to send the HCI_LE_Create_CIS command while an outstanding request is pending. Since multiple ISO channels can be connected in a single request, the solution implemented was to iterate over all ISO connections and see if there was any unicast ISO channels in the connecting state.

Per the HCI spec it is not possible to send the HCI_LE_Create_CIS command while an outstanding request is pending.

I found this sentence in the spec: "If the Host issues this command before all the HCI_LE_CIS_Established events from the previous use of the command have been generated, the Controller shall return the error code Command Disallowed (0x0C)." Is that all you are referring to?

Yes

Since multiple ISO channels can be connected in a single request, the solution implemented was to iterate over all ISO connections and see if there was any unicast ISO channels in the connecting state.

Non sequitur. What was the problem that needed a solution? The fact that 'multiple ISO channels can be connected in a single request' does not describe a problem, nor does it motivate the solution.

That part describes the solution, and not the problem. The problem is stated earlier in the commit message.

It also checks for the encryption pending state, which is an additional check to make it simpler to handle in the ISO layer, as once security have changed we would not want to have to check for other pending ISO connections.

The construction of this sentence is really awkward. It should be split up and reworded. What is the ISO layer? The whole change is in iso.c, so I assume you have something more specific in mind. Please explain the problem carefully and why the solution works. What security change? (I actually don't know.) Why do we need to care if there are other "pending" ISO connections when security changes? How messy would it be if we did the check? Why do we not need the check with the change in PR?

I can rewrite this paragraph, and add additional information - I do, however, not want to explain how the entire ISO architecture is designed and how it works as part of a commit that doesn't change any behavior except returning an error earlier by not sending a command that is known to fail to the controller.
In this context iso.c is the ISO layer, and I used that term because ISO is implemented as a layer on top of conn.c (sort of as an extension of conn.c for a specific type of connection), but it may have been the wrong term to use :)

@alwa-nordic Maybe it will be simpler to understand, and be a simpler implementation, if we just added a another BT_DEV_ flag (e.g. BT_DEV_ISO_INITIATING), and simplified the check to be
if (atomic_test_bit(bt_dev.flags, BT_DEV_ISO_INITIATING)) {
	return -EALREADY;
}

So that it will have the exact same behavior as the check we have for ACL?

I also updated the commit message slightly


Contract Agreement IDs are not being size validated

Bug Report
Describe the Bug
The Database column related to the Contract Agreement ID has type character varying(255). Since the Contract Agreement ID is computed like:
 :  :
A large enough Contract Agreement ID, composed of a large contract definition id and a large asset id, will break the transfer process.
Expected Behavior
Either allow bigger Contract Agreement IDs to be registered, or restrict the size of the Contract Definitions ID and Asset IDs
Observed Behavior
Snippet of the stack trace:
org.eclipse.edc.spi.persistence.EdcPersistenceException: ERROR: value too long for type character varying(255)
at org.eclipse.edc.sql.SqlQueryExecutor.execute(SqlQueryExecutor.java:66)
at org.eclipse.edc.connector.store.sql.transferprocess.store.SqlTransferProcessStore.insertDataRequest(SqlTransferProcessStore.java:324)
at org.eclipse.edc.connector.store.sql.transferprocess.store.SqlTransferProcessStore.insert(SqlTransferProcessStore.java:318)
Steps to Reproduce
Steps to reproduce the behavior:

Register an Asset with a large ID (~100 chars)
Register a Contract Definition for that Asset also with a large ID (~100 chars)
Fetch the catalog for that EDC
Verify if the Offer ID has more than 255 chars (Offer ID and Contract Agreement ID are computed in the same manner, and have the same number of chars)
Negotiate the offer
Transfer the Offer

Context Information

Used version EDC v0.2.1

the EDC does not define a strict schema, you can find examples in the sql related modules but in fact how to define the schema is up to the specific connector implementation.
Anyway, the example schema for transfer process does not define length for the contract_id (in postgresql that should equal to define a field of length of 10,485,760)
https://github.com/eclipse-edc/Connector/blob/df48c3e0d3cf2daf00355215653210c3cd9e00e4/extensions/control-plane/store/sql/transfer-process-store-sql/docs/schema.sql#L60-L75

Thanks for the quick reply.
Closing this issue as it only applies to the EDC implementation I'm using


Parsing error if the username contains slash

ZNC uses "username/network" for usernames.
When this is parsed back the server address becomes the username.

Can you give further details? I don't follow.

Where are you, which fields do you fill in?
Do you get an error message?
Any other details..?

url parameter in connection.json
Further testing shows it's a Mojo::URL issue.
my $url = Mojo::URL->new('irc://username/network:password@example.com:3000);
$url->host is now "username"

Ah! Thank you. Wanna make a PR? I'm not sure if I have time to look at this today.
I guess this line need to be changed: https://github.com/Nordaaker/convos/blob/master/assets/vue/convos-connection-settings.vue#L102
Into something like this.
var userinfo = [this.username, this.password].map(function(str) {
  return encodeURIComponent(str);
}).join(":");

If you want to try it out, you might need to install the developer deps:
./script/convos install --develop
MOJO_ASSETPACK_LAZY=1 ./script/convos dev

MOJO_ASSETPACK_LAZY is used so you can make changes in to the files in assets/ and see the changes in your browser without restarting the server.
Ask in #convos, if you need a test IRC server.

As pointed out by @ksmadsen on IRC, the slash should be encoded. Which means the error is in Convos when parsing/storing user input.
The suggested solution did not work, but I ran out of time to debug further. Might do so later if still open.

"suggested solution did not work": The solution I posted above?

I need to look at when I have better time. When testing the websocket staeted acting up, even a git reset --hard has the same issue. I have to refresh the page after I add a server - it doesn't update.
Even running directly without the reverse proxy breaks, but I don't have time right now.
And now my VPN went down, so the box I worked on is not accessible. I'll have to revisit this later.

The result was quite a big commit, but I hope it's fixed in aa0daa3. Please let me know if you can try out the "master" branch.
The reason for so many changes is simply that username/password was not tested and seems to have been completely broken to me, not just related to the encodeURIComponent() bug

@tyldum have confirmed that this is fixed in https://github.com/Nordaaker/convos/commit/aa0daa345433b604899cb7f9affc7904820e505a


Normality of the countable box products of Reals

Hello, I was browsing the site when I noticed it said the countable box product of reals was a normal space (https://topology.pi-base.org/spaces/S000107/properties/P000013)
It struck me as odd for, as far as I knew, this hadn't been proven.
In fact, I found a math stackexchange answer which quotes from the 5th exercise, section 3.2, of Munkres' "Topology" as follows:

It is not known whether R^ω is normal in the box topology. Mary-Ellen Rudin has shown that the answer is affirmative if one assumes the continuum hypothesis [RM]. In fact, she shows it satisfies a stronger condition called paracompactness.
[RM] M. E. Rudin. The box product of countably many compact metric spaces. General Topology and Its Applications , 2:293-298, 1972.

Pi-base seems to have jumped to this conclusion based on the premise that it is T5 (https://topology.pi-base.org/spaces/S000107/properties/P000008).

Thanks for reporting this error.

See item #2 for space #109 in DOI 10.1007/978-1-4612-6290-9_6.

I checked this, and it's asserting that the space is T3.5, not T5. So it should assert P000006, not P000008.

Not at all, I'm happy to help.
While we're at it, I found a typo in the space's description. It seemed straightforward to fix, so I've submitted a pull request.
Keep up the good work!

T_4 is not known for the countable box product of reals.  But the answer in https://math.stackexchange.com/questions/3039316/is-mathbbr-omega-endowed-with-the-box-topology-completely-normal-or-hered gives a link to an article by Erik van Douwen (Fund. Math. 88 (1975), 127-132) http://matwbn.icm.edu.pl/ksiazki/fm/fm88/fm88113.pdf showing that the space is definitely not T_5.
So if someone wants to add the T_3.5 property, it would be good to change the T_5 property to false at the same time.


Investigate porting json UI documentation over

Here is the link: https://github.com/bleonard252/mc-addon-resources
Please note the CC-BY license. We will need to make a note of this when porting over.
Should we even port over? Can somebody look into this?

Although the JSON UI system is currently how you would modify UI and thus probably something you would want some documentation on, with some of the sneak peeks we got into scripting this UI system is going to be faded out in favor of a new HTML UI system. When this happens I wouldn't know and I'm not saying to NOT document this older system, but if we do I think it should include some kind of warning that this entire JSON UI system is considered deprecated.
I might just write something of my own. I know the system decently well and I feel just doing it from scratch is going to take me less time than trying to adapt Bleonard's guide. Bit low priority for me though, as I don't advise anyone to use this old system unless they really can't wait to modify UI.

@PepijnMC I am a fan of the iterative process. If you wanted to tackle a "2 minute explanation + disclaimer" doc, with a link perhaps to Bleonards guide, that could be good enough.
Especially like you said if the UI stuff is being phased out for a newer system.

This has been done. See page here: https://wiki.bedrock.dev/concepts/json-ui


[Post ROS2 Porting] Unify usage of tf library

We have packages using different syntax to obtain required tfs (lookupTransform, waitForTransform).
We should look through all the packages and make sure they use same functions for the same purpose.

Besides the two packages above, there is only one usage in pointcloud_preprocessor where I think it makes sense to keep waitForTransform.


Improve ParserGenerator readability

I'm not sure why you wrote it this way, but adding a few empty lines, early continues and inverting conditions to handle simple cases first seems to me like it makes this code much more readable.

Hey @alex, any more feedback?

@alex this still applies after 3 years and was also useful when I was adding some debugging to the parser generator code. Please consider for merging or just close it if you think it's not an improvement.


Develop Published toggle

This pen might help you. There is a basic technique but we might need something different.
I would use input + label and then work around label's before and after pseudo-elements to style both states.


Move patterns content-template from Drive to GitHub

What
Move our patterns content-template from Drive to GitHub.
Why
This Drive-hosted content has only had a few viewers in 2.5 years. If we move it to GitHub, our contributors would be able to use it when drafting their own patterns.
Who needs to know about this
Content Designer, Delivery Manager, Developers, Senior Product Manager, Technical Writer
Done when

[ ] Technical Writer confirms location of content with team
[ ] Content Designer reviews to see if content matches Design System patterns
[ ] Content Designer and / or Technical Writer make any updates
[ ] Content gets 2i'd, if needed
[ ] Content published on GitHub

To discuss:

What repo could this content live in?
Would it be in a new / existing folder?

We need to see if this content matches the pattern of Design System patterns pages (double pattern) before we move it.


How to implete suggestion and then type a space with typing the "space" key(like in Visual Studio)?

yes i have a question,but noone answer me on stackoverflow

I'm sorry, but I don't understand the question.


Don't tag as devel by default

Instead, we should set the tag to the branch name that's being merged
to, in accordance with the stable release policy.
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

We should probably rename master to devel prior to merging this

We should probably rename master to devel prior to merging this

This was backported in https://github.com/submariner-io/shipyard/pull/436.


ARROW-6853: [Java] Support vector and dictionary encoder use different hasher for calculating hashCode

Related to ARROW-6853.
Hasher interface was introduce in ARROW-5898 and now have two different implementations (MurmurHasher and SimpleHasher) and it could be more in the future.
And currently ValueVector#hashCode and DictionaryHashTable only use SimpleHasher for calculating hashCode. This issue enables them to use different hasher or even user-defined hasher for their own use cases.

I have restarted your build. Looks like there is a problem with all recent Java travis CI builds.

I have restarted your build. Looks like there is a problem with all recent Java travis CI builds.

Yes, it's strange, i also noticed, but seems its due to 10 minute timeout and no other error messages, and not only Java related. The recent 10 hours only a Rust related PR passed (https://travis-ci.org/apache/arrow/builds/596978648).

@siddharthteotia build passed, i think we could get this merged

Codecov Report

Merging #5625 into master will increase coverage by 6.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5625      +/-   ##
==========================================
+ Coverage    83.2%   89.94%   +6.74%
==========================================
  Files         251      737     +486
  Lines       20072   114177   +94105
  Branches     1501        0    -1501
==========================================
+ Hits        16700   102692   +85992
- Misses       3007    11485    +8478
+ Partials      365        0     -365

Impacted Files
Coverage Δ

r/src/recordbatch.cpp

js/src/util/fn.ts

r/R/filesystem.R

r/R/list.R

r/src/symbols.cpp

r/src/array_to_vector.cpp

go/arrow/ipc/file_reader.go

js/src/builder/index.ts

r/src/arrow_types.h

js/src/enum.ts

... and 978 more

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 8621a5c...2e0e4c9. Read the comment docs.

@emkornfield just passed the build, could we get this one merged?

merging.


Allow to set multiple folders for PEX_ROOT

It will be helpful to set multiple folders for PEX_ROOT in case one folder is not writable due to permission or disk full.

Can you explain a bit more? Do you have situations where building the PEX file with --runtime-pex-root X is not enough? If so, can you provide more details about your deployment targets that lead to this need?

On our cluster, we usually have two disks on a node and we won't decommission the node if only one disk is full or unhealthy. Say the two disks are mounted at /disk1 and /disk2, it will be great if we can set PEX_ROOT to /disk1,/disk2 and pex will find the first writable folder.

Aha, ok. So the PEX runtime tries os.mkdir on /disk1 which nets an OSError (or IOError) due to a disk full condition and then falls back to /disk2. That makes sense to me. This is all self contained in pex.pex-info.PexInfo class except for the --runtime-pex-root plumbing which is in pex/bin/pex.py.
@manuzhang are you willing to contribute this feature?

@jsirois thanks, I've submitted https://github.com/pantsbuild/pex/pull/1965. Please help approve to run workflow and review.

@jsirois Our usage is for PySpark applications(https://spark.apache.org/docs/3.1.1/api/python/user_guide/python_packaging.html#using-pex) and pex root is set like spark.executorEnv.PEX_ROOT=/disk1/pex. /disk1 is shared by many applications besides pex and can become full. For other applications, the node is managed by YARN, which has a health checker monitoring the disk state. It's configured with two disks and won't assign application to the node when both disks are unhealthy.
I'm thinking about adding similar feature to pex.

OK, thanks for the background. The health checker approach is the right approach! You need a daemon or a cron job for that. Pex is neither, it's a one-shot job. Its very hard to solve this with a one-shot job is what I'm trying to point out. That's not the right layer to solve this problem. The best way I can think of to solve this problem for a one shot job is to make sure it uses a wrapper that does something like (psuedo code - this could be a bash wrapper or even a python wrapper):
pex_roots = [...]
for pex_root in pex_roots:
  export PEX_ROOT=pex_root
  try:
    sys.exit(run_job())
  except Exception as e:
    if not is_disk_full_condition(e):
      raise e

Maybe this makes things clearer. Pex can restart itself if needed since it knows what its constraints are. It cannot, however restart user code - that might be disastrous. Who knows what that user code does. Maybe it withdraws money from a bank. As such, the best you can ever hope for here is that some form of new code / logic in Pex ensures user code never runs unless the PEX boot has probed all possible pex roots to find one it can use to get fully booted. Now, the handoff happens to user code and it tries to write some tempfile and hits disk full and everything crashes anyhow, outside the control of the PEX boot code. It really does seem to me that if your environment runs into problems like this frequently enough to want to solve the issue, you need to do it at ahigher system layer.

@jsirois thanks for everything you've said. The error pex would throw is like this
dagster.pex/.bootstrap/pex/common.py", line 221, in _extract_member
    File "/usr/share/anaconda3/python3.7/lib/python3.7/zipfile.py", line 1690, in _extract_member
      open(targetpath, "wb") as target:
  OSError: [Errno 28] No space left on device:

The higher layer, in our case, is Spark which has no idea what's going on at the Python side and YARN which handles disk health but doesn't integrate with pex. Another idea is that pex can randomly choose from the list of PEX_ROOT, and Spark could retry task (restart pex) on failure and eventually we can hit the healthy disk.

Ok, well hopefully you've taken in everything to consider and can come up with a reasonable design. I'm not seeing that design myself.
Make sure you address at least these questions:

Why its not feasible to implement a wrapper that does the retrying as sketched above.
Pex runs on MacOS and Linux (and soon Windows) and Python 2.7 through 3.11 - how does Pex detect disk full robustly on all these systems. It seems like you have a way to detect this on Linux. Perhaps Errno 28 is https://docs.python.org/3/library/errno.html#errno.ENOSPC. The trick is making sure you have a solid means of detection for all Pex use cases, not just yours.
Pex uses PexInfo.pex_root in several places - how will you address detecting disk full robustly in all these places?:$ git grep "\.pex_root" pex/
pex/bin/pex.py:    pex_info.pex_root = options.runtime_pex_root
pex/bin/pex.py:        pex_root = pex_info.pex_root
pex/commands/command.py:                if options.pex_root and options.cache_dir != options.pex_root:
pex/commands/command.py:                elif options.pex_root:
pex/commands/command.py:                pex_root = options.cache_dir or options.pex_root or ENV.PEX_ROOT
pex/environment.py:            pex_root = pex_info.pex_root
pex/pex_bootstrapper.py:                short_venv_dir = os.path.join(pex_info.pex_root, "venvs", "s", entropy)
pex/pex_bootstrapper.py:                                pex_root=pex_info.pex_root,
pex/pex_bootstrapper.py:    with ENV.patch(PEX_ROOT=pex_info.pex_root):
pex/pex_builder.py:            os.path.join(pex_info.pex_root, "bootstrap_zips", bootstrap_hash)
pex/pex_builder.py:                    os.path.join(pex_info.pex_root, "installed_wheel_zips", fingerprint)
pex/pex_info.py:        return self._venv_dir(self.pex_root, pex_file, interpreter)
pex/pex_info.py:        return os.path.join(self.pex_root, self.BOOTSTRAP_CACHE, self.bootstrap_hash)
pex/pex_info.py:        return os.path.join(self.pex_root, self.INSTALL_CACHE)
pex/pex_info.py:        return os.path.join(self.pex_root, "user_code")
pex/tools/commands/venv.py:                safe_rmtree(pex.pex_info().pex_root)

If you don't want to tackle 3 above but instead just try to detect disk full once in the PexInfo.pex_root property like the perm check is done today, how will you test for disk full and will that check be performant enough that it can be done for all Pex use cases without ~any performance impact? Remember that in your case you may be willing to burn 50ms to determne the correct pex_root to use, but other users will not be happy about this perf regression.

@jsirois thanks again for the thorough reply. I understand now it's not feasible to detect disk full in pex. Hence, I'm not going down that road anymore.
Spark runs Python code as a blackbox so it has no idea what's running inside. It could be a virtual environment like pex, anaconda or Python lib on the system. Hence, my last idea is a wrapper at higher level.

Another idea is that pex can randomly choose from the list of PEX_ROOT, and Spark could retry task (restart pex) on failure and eventually we can hit the healthy disk.

@manuzhang it sounds like you accepted solving the disk full condition with a higher level wrapper. As such, I'll close this issue and the associated PR.


Batch download

Is there a way to add more than 1 file to download (in a queue)?

Yes i write script where you can download 2 file in a queue. See here https://github.com/Sperhak323/ulozto-downloader-script

I will reopen this issue as feature request. This should be implemented easily in the ulozto-downloader itself when you give it multiple URLs.

Thanks. I made a fork and I'm running few instances in parallel (manually), which is simpler because I fill out all the captchas at start. I added support for manual restart using batch files (windows). I also added name of the download to the captcha window so I know which captcha belongs to which download (I'm too lazy to downgrade Python for ml detection). If you find use for any of those changes, they're in my fork.

Specifying multiple files when using Ulož.to downloader version 3.3.0 or newer is now possible. Just add multiple URLs as arguments and they will be downloaded sequentially.


 It's related to the Automatic Type Acquisition not working on 1.94. I rolled back to 1.93.1 and everything is back to normal.

@Sov3rain same here dude intellisense isn't working

I wasted the past 6 hours trying to figure out why IntelliSense stopped working. I installed 1.94 a few days ago and it was working fine. I installed some Windows updates and restarted and it hasn't worked since. I pulled my hair out for 6 hours before coming across this issue. Rolling back to 1.93.1 fixed the issue for me.
FYI, 1.94.1 has the same issue.

/duplicate of #230596
Needs TS release and then VS Code recovery built to include fixed TS version. But current workarounds posted in linked issue.


[Afya Yangu/Quest] - Family Registration

Is your feature request related to a problem? Please describe.
Afya Yangu is the new name for Boresha Afya project that is being transitioned to FHIR. This ticket forms the first of a couple of modules that need to be built in the realisation of the Afya Yangu CHW App.
Describe the solution you'd like
As a Community Health Worker (CHW) I need to register households and add household members while at the community conducting visits. Household and household members registrations are made once and they are then referenced while providing the different services at the community. Household members can either be children under 5 years of age or older people. One household can contain multiple household members.

[ ] I would like to view all my registered households, under a common section “All Families”.
[ ] Each of the listed households should provide a summary with family name, the village where the family is located, icons to show the number of household members of programmatic interest. These include children under 5, women under ANC, PNC or FP, and individuals with a Malaria diagnosis.
[ ] Each of the families should provide a count of all the services that are due (coded in blue) or overdue (coded in red).
[ ] I would also like to have an option to add a new household whenever I need to. Once a new household is added, it should immediately be available under the “All Families” listing.
[ ] I would like to have an option for searching for the families/households by their name or system ID.
[ ] I would like to have the ability to filter the household listing by those that have due services

The household registration questionnaire can be accessed here.
When I select a family:

[ ] I should see the listing of all the existing family members.
[ ] For each of the listed family members I should see a summary of the person’s full name, sex, age and whether that person is the head of the household or the primary care giver.
[ ] From the household members listing I should be able to know family members who have pending services or who I have already provided with the services due to them. Services include home visits for under 5 and PNC mothers among others. This can be through a coloured bubble next to the household member (blue where services are given and red where the services are due).
[ ] I should be able to select a household member from the household members listing and view their information in detail. i.e. Name, Age, Sex, Village, ID and a listing of the services that are due to the person or to his/her family.
[ ] The household member listing should have capability to divide the listing into pages where there are many household member.
[ ] I should have the option to change who is the household head or the primary care giver.

From within a household:

[ ] I should have the option to add a new household member.
[ ] At the point of adding a new household member, I want separate options for adding a child under 5 and for adding an older child or person. This is because part of the information collected between the two groups of people differs.
[ ] I should have an option to initiate a call to the household member marked as the head of the household.
[ ] I should be able to remove a household member from the family when such a person moves away, dies or is no longer part of the household for any reason. The App should provide me with the listing of all the members in the selected household.
[ ] I should then have the capability to select the household member to be removed and provide the reason for removal.
[ ] The removed person's record should not be accessible after removal. No other step needs to be taken after the removal from a household.
[ ] I should be able to remove a household. Removal of a household will also result in the removal of all the household members associated with it.
[ ] The removed household should not be listed under the "All Families" list and should not return results from a search by the family name or ID.

Below are the links to additional questionnaires used in the family registration.

Adding children under 5
Adding HH members above 5 years of age
Removing HH Member
Removing Family Record

Describe alternatives you've considered
N/A
Additional context
Add any other context or screenshots about the feature request here.

What in this is not already supported?

@pld A majority of the functionality is already available just a few edge cases such as

At the point of adding a new household member, I want separate options for adding a child under 5 and for adding an older child or person. This is because part of the information collected between the two groups of people differs.
Addition of linked StructureMaps for the authored questionnaires

Acceptance criteria for QA  - TBD @samkanga to add

We can  keep this ticket to track both code  and non-code items for configurability
CC @samkanga

Cool, I'm closing this ticket, we can use the closed ticket as a reference. Even for (1) I think a Questionnaire can handle that.
We can open a new ticket when any missing functionality arises that requires code and clear describes the code that must be written to close it.
For the content issues, we can track those elsewhere, not tickets in this code repo.

@samkanga and @Gental-Giant to update the ticket accordingly

@f-odhiambo cc: @Gental-Giant @ageryck  See the updates below:

We merged the under 5 and over 5 registration forms and have since removed the questions that are not related to the family member registration such as whether there was a delivery registered in the last 1 year or if a child has a growth booklet.
The request to provide a separation of the registration forms is no-longer needed and has been crossed out.
See additional detail below:

Updated Afya Yangu (AY) questionnaires on server as below;
Household - Updated
Family Member Registration - Updated
Remove House Hold - No Changes
Remove Family Member - Updated
Child U5 - To discard, no longer in use

For the Questionnaire will need to have the following subsequent changes

change the subject type to Group from Patient.
add group definition and extension in Family Name QuetionnaireItem.
add household ID in the questionnaire.

@f-odhiambo changes above done. Is Group.identifier a requirement too ?

@pld A majority of the functionality is already available just a few edge cases such as

At the point of adding a new household member, I want separate options for adding a child under 5 and for adding an older child or person. This is because part of the information collected between the two groups of people differs.
Addition of linked StructureMaps for the authored questionnaires
Acceptance criteria for QA  - TBD @samkanga to add

We can keep this ticket to track both code and non-code items for configurability
CC @samkanga

Did we already create a ticket for the seperation? Can we use the enableWhen logic on the forms to show and hide the questions based on who is being registered?

Have the first question be What type of client do you want to register? This question can have the option of under 5 and over 5. We then hide or show the other questions based on this.

@dubdabasoduba that would be our last resort(we discussed this already) should we be unable to use runtime calculated age  variable from DOB  to implement the skip logic. However even in this option we would still need to restrict DOB entry values based on responded value i.e. for U5 the calendar must not allow any entry above 5 years.

@dubdabasoduba that would be our last resort(we discussed this already) should we be unable to use runtime calculated age  variable from DOB  to implement the skip logic. However, even in this option, we would still need to restrict DOB entry values based on responded value i.e. for U5 the calendar must not allow any entry above 5 years.

I don't think we have a function to calculate DOB at runtime. FHIRPath which is used for extraction doesn't have runtime support for such calculations.
I think the date restrictions can be added by the min & max settings on the date field. We can test that to see if it works well.

Just sharing some related tickets on the date issue

https://github.com/google/android-fhir/issues/881
https://github.com/google/android-fhir/issues/1040

Also, related items shared by @ageryck  - Support simple calculation of patient age in fhirpath #1014
CC @ageryck @samkanga @dubdabasoduba

@ageryck @samkanga I just went through the issue again. Could we update this to different issues? Some of the points are more about scheduling and tasking and not registration. We can have a call to do this.

@dubdabasoduba Sure we can do that.

Reviewing some items here

Do we need Is family head? choice? where will this be used

The following items seem to be extensions of the patient

Is the primary caregiver
Physical disabilities
Type of physical disabilities? if the Patient has Physical disabilities?
Occupation
Leadership role in the community

These seem like things that will need to be discussed as they may or may not be available as Patient extensions else the data captured can be left stored in the QuestionnaireResponse
CC @samkanga @ageryck @dubdabasoduba

@f-odhiambo Can we try to review whether we can use the encounters for this? This will mean the product needs to address the following things.

Pre-populating a Questionnaire from 2 resources.
Make sure that every Questionnaire filled up has a corresponding encounter generated for it.

@dubdabasoduba that would be our last resort(we discussed this already) should we be unable to use runtime calculated age  variable from DOB  to implement the skip logic. However, even in this option, we would still need to restrict DOB entry values based on responded value i.e. for U5 the calendar must not allow any entry above 5 years.

I don't think we have a function to calculate DOB at runtime. FHIRPath which is used for extraction doesn't have runtime support for such calculations.
I think the date restrictions can be added by the min & max settings on the date field. We can test that to see if it works well.

Won't this issue address this? google/android-fhir#1040

@pld I don't this issue address the AGE  from DOB and vice versa on runtime. This is more on adding the min/max restrictions on the date field.

True, but, if I'm reading this correctly the only reason we care about calculating the age in the form is so we can have skip logic for if the person if <5, if 1040 is closed we can should be able to use today() to do that calculation, like today()-5 years > dob

My understanding is this is to allow restrictions like making sure that someone's DOB can only be <= today() and not in the future. I don't think it adds the ability to evaluate today() - 5 years > dob
More context on the issue is found here https://github.com/opensrp/fhircore/issues/845

Yea good point, that issue is only relevant for the validation. I guess I was figuring that if that issue shows that today() is support in FHIRPath, and we know that FHIRPath already supports date arithmetic for adding and subtracting durations to a date, https://hl7.org/fhirpath/#datetime-arithmetic, we could use that elsewhere in a Questionnaire to evaluate today() - 5 years > dob

Yea good point, that issue is only relevant for the validation. I guess I was figuring that if that issue shows that today() is support in FHIRPath, and we know that FHIRPath already supports date arithmetic for adding and subtracting durations to a date, https://hl7.org/fhirpath/#datetime-arithmetic, we could use that elsewhere in a Questionnaire to evaluate today() - 5 years > dob

I don't think it would during runtime though. We need to test it better. it could work during extraction I think we have tested a couple of date calculations.

Does the validation execute during run-time?

The following fields are left that needs to be mapped from family/household registration questionnaire. I am unable to find fields in the group resource that can be used.

Village: string
Landmark/ description of house location:  string
Nearest health facility:  string

CC: @f-odhiambo @shoaibmushtaq25 @maimoonak


ONEM-20048: removed unregister

It causes problems (crashes) in another scenario:
(1) Activate FMP
(2) Start playback
(3) Deactivate FMP through controller

Latest version of FireboltMediaPlayer.cpp on sprint/2105 already contain (or better say does not contain problematic Unregister operations, that was a topic of that pull request: reference: https://github.com/rdkcentral/rdkservices/commits/sprint/2105/FireboltMediaPlayer/FireboltMediaPlayer.cpp


stix2.exceptions.InvalidValueError

Traceback (most recent call last):
  File "/usr/local/bin/stix2_slider", line 11, in <module>
    load_entry_point('stix2-slider==1.0.1', 'console_scripts', 'stix2_slider')()
  File "/usr/local/lib/python2.7/dist-packages/stix2slider/cli.py", line 132, in main
    result = slide_file(slider_args.file_)
  File "/usr/local/lib/python2.7/dist-packages/stix2slider/__init__.py", line 27, in slide_file
    obj = stix2.parse(json_content)
  File "/usr/local/lib/python2.7/dist-packages/stix2/core.py", line 100, in parse
    obj = dict_to_stix2(obj, allow_custom, version)
  File "/usr/local/lib/python2.7/dist-packages/stix2/core.py", line 147, in dict_to_stix2
    return obj_class(allow_custom=allow_custom, **stix_dict)
  File "/usr/local/lib/python2.7/dist-packages/stix2/core.py", line 68, in __init__
    super(Bundle, self).__init__(**kwargs)
  File "/usr/local/lib/python2.7/dist-packages/stix2/base.py", line 160, in __init__
    self._check_property(prop_name, prop_metadata, setting_kwargs)
  File "/usr/local/lib/python2.7/dist-packages/stix2/base.py", line 93, in _check_property
    raise InvalidValueError(self.__class__, prop_name, reason=str(exc))
stix2.exceptions.InvalidValueError: Invalid value for Bundle 'objects': Invalid value for Indicator 'pattern': FAIL: Error found at line 1:1. extraneous input '"' expecting {IdentifierWithoutHyphen, IdentifierWithHyphen, '('}

Hi @sgmnt-qzh
Is it possible to get more detail on this error.  Maybe send us the file which caused the problem??
Thanks!!

Thanks for answer! This 2 files in archive for example.
Reports_Fin.zip

Hi @sgmnt-qzh
I ran Report.json, and notice that there were several typos that is causing the slider to fail.

in the patterns, you have the following text: "[\"domain-name:value = 'mail.ru'\"]".  The escaped double quotes are causing a problem.  They are not necessary, and make the pattern invalid.    This is the case with most of the patterns in the file
in other patterns, you specify the hash algorithm using values that are slightly wrong due to case issues and missing hyphens (-).  See the correct literals for hash algorithms in section 7.3 of Part 1 of the STIX specification.  This gets a little tricky, because if the hash algorithm name included a hyphen (-), it must be (single) quoted, but otherwise it shouldn't be. So where you had md5 you should have MD5, but there you had sha1 you should have 'SHA-1'

It looks like the other file has similar issues.
Please correct the typos and see if that fixes the problems.

Please reopen if this is still an issue


fix: consistent error rendering

https://github.com/omisego/elixir-omg/issues/938
Overview
If an exception happens in a lower stack then controller, this propagates to renderer without information about the template.
Changes

Render server errors

Testing
/

Coverage remained the same at ?% when pulling bab0936089babb19013ac510f00b51689bc49cf2 on 938-render500 into 819e9f858ae344d1f8493b5341015289eb64bcd7 on master.


1485 executed by unspecified fails

Modifications to the ModelInstance App.

fixed error when setting ExecutedBy to "Unspecified"
fixed error when initializing the ExecutedBy drop list
fixed ModelInstance versioning
Addresses issues #1485 and #1140

@zhiyuli Can you review this?

@Castronova  I did further test for the specific model instance resource types: SWAT and MODFLOW that are inherited from the generic model instance resource type. Everything works fine except the drop list. Still for these resource types the drop list turn back to Unspecified if I exit the edit mode then go to the edit mode again. Is this something we need to change in their JS?

This has been deployed on park.hydroshare.org and everything is working fine. I think this is ready now for reviewing.

@Castronova What's the status of this PR?

@Castronova
Thanks for clarifying this. Then I would like give a +1.

@pkdash @zhiyuli is this branch ready now to be merged?

@mohamedmorsy Yes. I gave a +1 already.


Bump kfp-tekton to 1.5.8

Bump kfp-tekton to 1.5.8

rhods-ci-pr-test/1993/TestReport/

I see more changes rather than only bumping the kfp version. Are these changes caused by the library change? Could you please extend the PR name/description?

I see more changes rather than only bumping the kfp version. Are these changes caused by the library change? Could you please extend the PR name/description?

all related

Diego, kfp_tekton 1.5.9 was released on Sep 12. Should we use that one instead?


Some issues with display of rendering, etc.

I have briefly tested the new FastPathology version. More stable. but some issues:

crashes when I try to load small tiff files, but not large ones. When I test prediction for mitoses they become invisible at "overview" ca. 4x magnification and thus it becomes almost pointless to run the algorithm when you have to look for all green dots. In Qupath, small annotations are magnified when you zoom out so they are still visible. Is this possible to get into FastPathology (that all annotations have a given line thickness regardless of magnification?)

The NoCodeSeg import script does not work on the tiff file I got out in the results folder. Correct size, but too large for the import script (this was a standard WSI, but large about 60k x 100k pixels, and MIB/DeepMIB/Matlab struggles with these as well at 40x resolution).

The import script for direct import from fast pathology at the NoCodeSeg page probably does not work either as it is a new folder structure with lots of subfolders. I would have dropped all these subfolders in results, or at least had a little less of them.

It is difficult to know whether the algorithm is actually running or not - no progress bar and no time indication for estimated finished prediction. For mitoses, I waited 15 minutes and it was finished, but could just as easily have been nothing that happened - I did not know that as a user.

Great suggestions, @SahPet!
Some of these suggestions, there already exists issues for. For 1) see https://github.com/AICAN-Research/FAST-Pathology/issues/33, and 2) see https://github.com/AICAN-Research/FAST-Pathology/issues/35, which I just created an issue for after discussing this with you on Teams.
Next time it is better to split sets of issues into individual issues on github.
That makes it easier for us to track, and we can more easily distribute the workload.
But great suggestions, we will try to solve all of them within a reasonable amount of time :)

So, here is a visual demo of what the point:
Segmentation networks for small rare objects, such as mitoses, rare cell types, etc. are not visible on the overview, which makes its really hard to use FastPathology for this purpose:

.... even though there are quite a few there:

In QuPath for example, small objects are clearly visible at full overview as well as on full zoom, so should be possible, by keeping the border line thickness rendering independent on zoom level for example.

Some of the points here has been adressed already. Whereas for those that remains, new targeted Issues have been created. Hence, this is now a duplicate. Closing this issue for now.


Revert "csv2kdi enhancements and doc cleanup"

Reverts KennaSecurity/toolkit#411

Reverting change due to customer issue investigation


maas_target_alias is already the default

This override don't need to exist:

Its value is already the group default
It's not overriden by any other mechanism
It's not re-use outside the role scope.

Connected https://github.com/rcbops/u-suk-dev/issues/1620

the CIT/ceph job got an issue with rpc_support role, not rpc_maas role. I'll dig deeper into this to see what needs fixing.

how this https://github.com/rcbops/rpc-openstack/commit/d49c4a266fb00f853ace69051a3a6e526d605c68 get through the door, that's a good question.

Instead of continuing to cherry pick all what's wrong in rpc-o, I'll just wait for the other patches to merge, this one should be auto-rebased on top.
i.e.: read this message as a "Don't workflow this unless the rest is merged".

recheck_cit_xenial

@hughsaunders This can wait for other patches to merge before rechecking.

recheck_cit_ceph
recheck_cit_swift
recheck_cit_xenial


can't save a file in new created folder (Permission denied )

New created folder gets  drw-r--r-- permissions
Creating a file inside the folder via filemanager results in an permission denied error.
Changing permissions manually to drwxr--r-- resolvs the error.

Folders are created with 0666 permissions... you can see the source here. I can't see where the problem is now... I'll try to reproduce this.

note: i've tested it on a freshl downloaded caddy with filemanager as a plugin today  and got the error.
Me too doesn't sees the reason why the caddy filemanager plugin uses 644 as permission

+1
For my condition new created folder gets drw-rw-r--.

I have 0666 for the default permissions now. What do you think I should change it for? 0766?

Hmm, the default permissions set for folders created by mkdir on my machine is 776. This should be fine.

I pushed a fix for this (changed to 0776) and it will be out when 1.2.0 is released (today or tomorrow).


Running a Second Node

Hey man.
Thanks for this great repo.
I'm pretty good with docker.
Only thing is. I'm getting stuck with the build command:
docker build -t gala-node:latest .
What I did was, I created 2 directories - one for each node.
but when I try to build node-2.
It's the same image in both nodes.
Is that ok?
How do I differentiate between the 2?
Would that be in the .configure?
If so, then I'm all good.
Please advise.
Thanks.
Ken

To run the second node you don't need to re-build a second container or even use another directory.
If the second node is on the same Gala account you just use the same docker start command but add -e NODE_SPECIFIER=2. You can verify that is working properly when you docker attach and see the :2 at the end of the machine ID.
If the second node is on another Gala account, you should copy/modify the .env file as second.env and then use that for your --envFile second.env arg when starting the second node.

I don't know the syntax re: the -e NODE_SPECIFIER=2
Could you post an example of a full Node 2 start up syntax,
where a Node 1 is hypothetically already running?
In other words, how do you alter this line of code to include (specify)
the second node?:
$ docker run -itd --name "gala-node-1"
--restart=unless-stopped
--env-file .env
-v /etc/machine-id:/etc/machine-id
gala-node:latest
That would help.
Thanks.

$ docker run -itd --name "gala-node-2"
-e NODE_SPECIFIER=2
--restart=unless-stopped
--env-file .env
-v /etc/machine-id:/etc/machine-id
gala-node:latest

Great!
Thank you, Erik.


Split KaTeX rendering into an optional separate service

Fixes: #17425.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I think in theory this would be the sort of thing that would be totally reasonable to enable by default on systems with 8GB+ of RAM, but I don't think the current settings framework makes that easy, and it's not important, so I think this is a fine path forward.

@andersk probably it makes sense for you to do a review on this PR at this point. I think https://github.com/zulip/zulip/pull/29198#discussion_r1519148457 is the only open concern from my review.

I believe I've addressed all of the comments.

This looks great, merged, thanks @alexmv!
I'm super excited to finally have this fixed.


Add weight property to items

Allowing the administrator to specify the order of items

Closed accidentally (trying out PHP Storms integration with GitHub's issue tracker)


DPL-986 - As developers we need to create an aliquot entity which can be used to create aliquots of samples and libraries for multiplexing and sequencing runs

User story
As developers we need to create an aliquot entity which can be used to create aliquots of samples and libraries for multiplexing and sequencing runs
Who are the primary contacts for this story
James / Steve
Who is the nominated tester for UAT
PSD
Acceptance criteria
To be considered successful the solution must allow:

[ ] an aliquot to have a model with volume, concentration, insert size and template prep kit box barcode
[ ] an aliquot to have a tag (optional)
[ ] an aliquot to have a source which is a sample, library or pool
[ ] a source to have multiple aliquots
[ ] a pacbio well to have many aliquots for sequencing
[ ] an aliquot to have a single parent aliquot
[ ] an aliquot to have many child aliquots

Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

#<issue_no.>
sanger/#<issue_no.>

Additional context
Add any other context or screenshots about the feature request here.

Just comparing to the ERD.
The acceptance criteria here specifies "an aliquot to have a source which is a sample, library or pool".
On the ERD aliquot connects to sample through a request entity, or via a library to request to sample relationship .
Is it worth clarifying what combinations are allowed, or a formal definition of source? Or have I got something backwards?


Update flopoco to latest

The newest version of flopoco has DSP inference, so we are updating to it in order to possibly improve some of our results.

Let's disable the arm build stuff for now, at least for the gen stuff, while we work on the deadline.


Optimizations

Coverage increased (+0.007%) to 21.921% when pulling cb57606586d61265e2f9edf84dacd5ae1c10056e on optimizations into ffcb1c720391e429c29bc4c2255618efaecc1077 on master.


Language editor: searches sometimes fail

Certain searches cause a continuable unhandled exception error. Examples include:

ONCOMING:
HUDMESSAGE_STUNT_RUN
BURNOUT_SKILLS_G

All of these have a pretty clear pattern where part of the string, but not all, matches an existing key. This should be pretty easy to debug and fix but I'm busy with other things so here's an issue for it for now.

Resolved by #49.


Bad line move indentation adjustment

Have the following TypeScript code:
function something() {
	const x = 3;
	// if (true) {
	// }
}

Move the line const x = 3; down two times. Observe the result:
function something() {
	// if (true) {
		// }
		const x = 3;
}

https://github.com/user-attachments/assets/84f6b38d-ca63-4852-8b17-070cedb4688e

I have seen this happened before as a regression that got fixed. Looks like the regression is back again. I also had the same issue.
Specs
Version: 1.96.2 (user setup)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
How to Reproduce
Using JavaScript, type:
switch (period) {
  case 'a':
    return '1';
  case 'b':
    return '2';
  case 'c':
    return '3';
  case 'd':
    return '4';
  default:
    return '2';
}

I'm trying to move case 'b': line to before default:  line. Here's what happens afterward. From line 4, press ALT down 5 times results in:
switch (period) {
  case 'a':
    return '1';
    return '2';
    case 'c':
      return '3';
      case 'd':
        return '4';
        case 'b':
  default:
    return '2';
}

Expected
I expected the indentation for case d to be unchanged.


Does anyone know how to fix a "(no such file), '/System/Library/Carbon.framework/Carbon' (no such file, not in dyld cache)" error?

This happens on a M1 macOS 14.0.
test.py
import rumps

class BarApp(rumps.App):
    @rumps.clicked("Test")
    def test(self, _):
        rumps.alert("Now click BarApp twice, then click OK.\nResult: segfault")

BarApp("BarApp").run()

setup.py
from setuptools import setup

APP = ['test.py']
DATA_FILES = []
OPTIONS = {
    'argv_emulation': True,
    'plist': {
        'LSUIElement': True,
    },
    'packages': ['rumps'],
}

setup(
    app=APP,
    data_files=DATA_FILES,
    options={'py2app': OPTIONS},
    setup_requires=['py2app'],
)

The error
~/rumps test/dist/test.app/Contents/MacOS $ ./test

Traceback (most recent call last):
  File "/Users/dima/rumps test/dist/test.app/Contents/Resources/__boot__.py", line 321, in <module>
    _argv_emulation()
  File "/Users/dima/rumps test/dist/test.app/Contents/Resources/__boot__.py", line 318, in _argv_emulation
    _run_argvemulator()
  File "/Users/dima/rumps test/dist/test.app/Contents/Resources/__boot__.py", line 127, in _run_argvemulator
    carbon = _ctypes_setup()
             ^^^^^^^^^^^^^^^
  File "/Users/dima/rumps test/dist/test.app/Contents/Resources/__boot__.py", line 51, in _ctypes_setup
    carbon = ctypes.CDLL("/System/Library/Carbon.framework/Carbon")
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "ctypes/__init__.pyc", line 376, in __init__
OSError: dlopen(/System/Library/Carbon.framework/Carbon, 0x0006): tried: '/System/Library/Carbon.framework/Carbon' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/Carbon.framework/Carbon' (no such file), '/System/Library/Carbon.framework/Carbon' (no such file, not in dyld cache)
2023-10-11 21:16:10.885 test[81802:3058374] Launch error
2023-10-11 21:16:10.885 test[81802:3058374] Launch error
See the py2app website for debugging launch issues

Same problem

Same here.

@Dima-369 @jksmx I fixed the issue. Here is my setup.py. Please make sure that 'argv_emulation' is False as shown below and DATA_FILES must be list[tuple[str, list[str]]].
This is my Hamster project. Hope I saved your day :)
APP = ['hamster/__main__.py']
APP_NAME = 'Hamster'
DATA_FILES = [('', ['hamster/app.properties']), ('img', ['hamster/img/hamster.png'])]
OPTIONS = {
    'argv_emulation': False,
    'iconfile': 'hamster/img/hamster.png',
    'plist': {
        'LSUIElement': True,
    },
    'packages': ['rumps', 'configparser', 'plistlib', 'os', 're', 'pathlib', 'psutil'],
}

Please make sure that 'argv_emulation' is False

Cool, this also works for me. Thanks 🙂

this worked for me too, thanks!


[Feature Request] Every flag for minute pacing?

We have —request-increase-rate and --max-rps which is great. But I wonder if we add another command line flag --every.
So, I have an example that would increase by 10 messages (SQS) every X number of minutes.
E.g. —request-increase-rate 10 —every 5m
That will go on until I either manually stop the test through the GUI or use the new Locust time duration flag.
Willing to pay bounty.

I prefer to change --request-increase-rate and add support like this.
E.g. --request-increase-rate 10/5m
The default interval is 1s, --request-increase-rate 1 is equal to --request-increase-rate 1/s.
What do you think?

More elegant than what I proposed.

Please give it a try.
https://github.com/myzhan/boomer/commit/e3065b9fe689e9c393ce949aa5aa3c6d49dcfec5

Testing on minutes and looks OK to me.
./a.out --request-increase-rate 10\1m --master-host=<IP_ADDRESS> --master-port=5557 --rpc=zeromq

// go run server.go

2018/07/13 11:09:04 Rate: 1
2018/07/13 11:09:05 Rate: 11
2018/07/13 11:09:06 Rate: 10
2018/07/13 11:09:07 Rate: 10
2018/07/13 11:09:08 Rate: 10
2018/07/13 11:10:03 Rate: 10
2018/07/13 11:10:04 Rate: 20
2018/07/13 11:10:05 Rate: 20
2018/07/13 11:10:06 Rate: 20
2018/07/13 11:10:07 Rate: 20
2018/07/13 11:10:08 Rate: 20
Thanks

Unfortunately, the pacing doesn't seem to working using SQS:
// Usage: ./a.out --request-increase-rate 10/1m --master-host=<IP_ADDRESS> --master-port=5557 --rpc=zeromq

package main

import (
    "github.com/aws/aws-sdk-go/aws"
    "github.com/aws/aws-sdk-go/aws/session"
    "github.com/aws/aws-sdk-go/service/sqs"
    "github.com/myzhan/boomer"
)

func sender() {
    sess := session.Must(session.NewSessionWithOptions(session.Options{
        SharedConfigState: session.SharedConfigEnable,
    }))

    svc := sqs.New(sess)

    start := boomer.Now()

    qURL := "<queueUrl>"

    // we probably need to do something with this result tuple
    _, err := svc.SendMessage(&sqs.SendMessageInput{
        MessageBody: aws.String("Aidy Lewis: Message body Test"),
        QueueUrl:    &qURL,
    })

    elapsed := boomer.Now() - start

    if err != nil {
        boomer.Events.Publish("request_failure", "sqs", "send_message", elapsed, err)
        return
    }

    // we need a base int type for the last parameter
    boomer.Events.Publish("request_success", "sqs", "send_message", elapsed, int64(10))
}

func main() {
    task := &boomer.Task{
        Name: "sender",
        Fn:   sender,
    }

    boomer.Run(task)
}

Having a holiday without computer, and not familiar with the sdk of sqs. I will look into this ASAP. And before that, please make sure you have run go get -u github.com/myzhan/boomer.

Thanks. I will try to debug it through delve. I've used go get on this project to include dependencies. Tried unsuccessfully to set requestIncreaseInterval = time.Minute

Hi, any progress?

Sorry, just looked at this. Didn't manage to achieve a slower request rate than seconds (for some reason).

What does the chart look like when you run test with sqs and set request-increase-rate to 10/1m?


Make tables with many columns responsive

There are different options like in this example for bootstrap:
http://elvery.net/demo/responsive-tables/

Added in de4bc0c7055d85859cd6fee16bac106ab3b623ee
Thanks a bunch for the link. It was very useful!

That was fast! Awesome!
Can you please also look at this new ticket I started:
https://github.com/Dogfalo/materialize/issues/427
Lucas Geiger
On Thu, Jan 8, 2015 at 4:33 PM, Alan Chang<EMAIL_ADDRESS>wrote:

Closed #424 https://github.com/Dogfalo/materialize/issues/424.
—
Reply to this email directly or view it on GitHub
https://github.com/Dogfalo/materialize/issues/424#event-216177425.


#771 - Update Turkish translations

Updates tr.yml according to the current changes.

Awesome. Thank you.

Also, if you have a minute, do you mind doing translation for this: https://github.com/comfy/comfy-blog/issues/48 (it's tiny)

Oh, I forgot this one! Will do it now :)


Write Pulsar message-generator client for testing

Leveraging the data definitions and interface methods in internal/armada/server/submit_to_log.go, write a simple Pulsar command-line client to:

submit an Armada job to Pulsar (perhaps by fashioning a api.JobSubmitRequest from a specified YAML file)
cancel an Armada job
cancel a JobSet
reprioritize one or more jobs
create one or more queues
delete a queue
get a queue's info

Implementation Notes per discussions with Albin Severinson and Chris Martin:

~use PulsarSubmitServer struct and associated methods from internal/armada/submit_to_log.go to create a client, using a JobRequest object for the submission.~
rename from 'pulsarctl' to 'pulsar-test' or some such (there is an existing  'pulsarctl' distributed with Pulsar).
read input yaml file as specified as command argument - the format should be   marshalable to an armadaevents.EventSequence object -see pkg/armadaevents/events.pb.go
do not directly use the PulsarSubmitServer struct and methods in  internal/armada/server - we want to publish directly to Pulsar using the EventMessage structs, not the api.JobSubmitRequest struct or any JobSubmitRequestItem
~borrow code from internal/armada/server/submit_to_log.go publishToPulsar(...) to  compact the event sequences, then~ send to Pulsar with code derived from  pulsarutils.PublishSequences(ctx, Producter, sequences) - however, send the messages synchronously (not async as PublishSequences() does), for now.
Return and log any errors, etc.

Note from Albin:
We don't want to compact the sequence. I.e., we should send exactly what we read from the file.
Since we'll use this for testing, the tool shouldn't do optimisations behind your back.
Note that compacting would be a no-op initially anyway. Since compacting is used to combine several sequences into a smaller number of sequences and we'll only have a single sequence initially.
Here's the unmarshalling code I promised to send you. Because we're using gogo proto, the process is a bit more complex than one might've anticipated:
https://github.com/G-Research/armada/blob/master/internal/testsuite/app.go#L362

You can use this pattern to populate parameters of whatever struct you use to represent the app.
https://github.com/G-Research/armada/blob/master/cmd/testsuite/cmd/test.go#L29
Here, initParams can extract whatever it needs from cmd to populate app.
In fact, you can have a look at this code, where we're setting up a Pulsar consumer from command-line arguments:
https://github.com/G-Research/armada/blob/master/cmd/eventsprinter/cmd/root.go#L11


Implement Balanced Neural Ratio Estimation loss

Targets #2.

Thank you for contributing. The PR has been merged. I will close #2.


gomobile: 2020-06-22 -> 2021-06-14

Motivation for this change
Go 1.15 is nearly out of its support window, and newer versions of gomobile do not work with older Go compilers.
This release together with upgrade to Go 1.16 drops support for iOS ARM32 builds.
In addition, the need for the patch was removed thanks to this fix.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

@ofborg eval


Package seems to allow environments with OCCT 7.7.1, but the bindings are incompatible.

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Package seems to allow environments with OCCT 7.7.1, but the bindings are incompatible.
I thought pin_compatible('occt', max_pin='x.x.x') would have prevented this, but it doesn't.
Installed packages
n/a

Environment info
n/a

This is what I see in the rendered recipe:
  run:
    - occt >=7.7.0,<7.8.0a0

I'll try adding one more x...


jacket requires sass (~> 3.3.0.rc.2)

Although I have Sass 3.4.5 installed jacket gem refuses to be installed :(
\Ruby193\Ruby193\bin>gem install jacket
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: jacket requires sass (~> 3.3.0.rc.2)

No trouble installing other gems like Susy, Brekapoint, sass-toolkit etc.
Thanks
Win7/Ruby1.93

+1 for this one, any chance this can be resolved?

Any updates?


Spark-Cobol-App

I get an error when I execute the command : mvn test  in the example Spark-Cobol-App.
The error is :
java.lang.IllegalStateException: Root segment SEGMENT_ID=='C' not found in the data file.

Good spot! The values of the segment field was something like "SL001", and later changed to be more meaningful. But the binary file remained.
This is fixed in master.