discussion: Boot menu entry titles are very generic

The created boot menu entries all have the title "openSUSE Tumbleweed" and a version of number@kernel_version, where number is the snapshot number.
However, this is not very desriptive. In GRUB, the entries created by snapper all have a desciptive title, containing the time when the snapshot was created, the reason and kernel version.
This should optimally also be included here, but normal boot entries that use the r/w snapshot should still be named openSUSE and shouldn't have the number@kernel_version version scheme but only kernel_version as this might otherwise be confusing to the end user.
Currently, all entries explicitly specify a snapshot they boot into, however, is this really necessary? When performing a rollback, the default snapshot that's booted into is automatically changed.

There's two issues in here. The one with the lack of description probable needs to be solved via the bootloader spec to allow for some more descriptive text. Not sure all of that information makes sense to encode in version or title.
The other issue is the one of the default subvolume. In the mode I chose the default subvolume basically has no meaning (see https://github.com/lnussel/sdbootutil/blob/wip/ARCHITECTURE.md, still WIP).
Regarding the UI your submenu patch could probably fix this by not showing the version if there's only one entry anyway.

There's two issues in here. The one with the lack of description probable needs to be solved via the bootloader spec to allow for some more descriptive text. Not sure all of that information makes sense to encode in version or title.
The other issue is the one of the default subvolume. In the mode I chose the default subvolume basically has no meaning (see https://github.com/lnussel/sdbootutil/blob/wip/ARCHITECTURE.md, still WIP). Regarding the UI your submenu patch could probably fix this by not showing the version if there's only one entry anyway.

Yes, that's true, I also coudn't come up with a good way to encode all information that might be of interest in only those two fields. I could create a PR for systemd that includes a new "description" attribute for entries and see what Lennard think about it or is there a better way (e.g. first create a github issue on their side).
What I as user would expect as information: OS: openSUSE, version: 6.4.2-1 as kernel version and snapshot information: e.g. *zypp,post,2023-07-23 20:12:02,22.
However, I noticed the following:
In the current implementation one might end up in a situation like this:

I created snapshots of the system, updated it, rolled back to a state before the update (snapshot 16) and updated again.
This also created snapshots, 17-22.
However, due to the sorting, they appear on top of nr 16, creating the impression, they are newer, even though they aren't.
We could add the snapshot information to the version, but this would confuse even more, as the current rw system can then not be distinguished from other ro entries.
So, from a user perspective, I would expect my current system version to not appear like a snapshot.
Another issue I noticed is the sorting. Currently, the entries are sorted by their file name, which leads to all new kernel version being on the top and all older kernel versions being below. I think it would be more logical to have them sorted by snapshot number. This is fairly easy as it just requires adding a sort-key attribute to all entries, e.g. "sort-key    openSUSE", then it looks like this:

This makes sorting (at least for me) a bit more logical, but the nr 16 is now even further down in the list.
These two issues could be solved with seperate entries for the default snapshot, as the sorting of the entries would also be confusing and misleading on MicroOS.

Another issue I noticed is the sorting. Currently, the entries are sorted by their file name, which leads to all new kernel version being on the top and all older kernel versions being below. I think it would be more logical to have them sorted by snapshot number. This is fairly easy as it just requires adding a sort-key attribute to all entries, e.g. "sort-key openSUSE"

Yes, that was a bug, fixed.

These two issues could be solved with seperate entries for the default snapshot, as the sorting of the entries would also be confusing and misleading on MicroOS.

How would title, version and sort-key for the default snapshot look like so it gets sorted on top of the list always?

How would title, version and sort-key for the default snapshot look like so it gets sorted on top of the list always?

From https://uapi-group.org/specifications/specs/boot_loader_specification/#:~:text=The Boot Loader Specification,loaders installed on one device.
Sorting #
The boot loader menu should generally show entries in some order meaningful to the user. The title key is free-form and not suitable to be used as the primary sorting key. Instead, the boot loader should use the following rules:
Entries which are subject to boot counting and are marked as “bad”, should be sorted later than all other entries. Entries which are marked as “indeterminate” or “good” (or were not subject to boot counting at all), are thus sorted earlier.
If sort-key is set on both entries, use in order of priority, the sort-key (A-Z, increasing alphanumerical order), machine-id (A-Z, increasing alphanumerical order), and version keys (decreasing version order).
If sort-key is set on one entry, it sorts earlier.
At the end, if necessary, when sort-key is not set or those fields are not set or are all equal, the boot loader should sort using the file name of the entry (decreasing version sort), with the suffix removed.
However, systemd-boot sorts this way:
sort-key -> machine_id -> version -> id and the id contains for type1 entries the file name.
The sort-key gets sorted alphabetically here as specified, so setting a sort-key that's always lower than the sort-key of the other entries will sort it higher. E.g setting openSUSE as sort-key for the default snapshot and openSUSE Snapper for the other entries as done here:

However, we then need to manage the sort-key when setting the default subvolume and it doesn't fix the issue that higher snapshot numbers might indicate that the system version is newer.

Hmm, using a different sort key is an interesting idea. Especially with a menu patch that would collapse the key for the snapshots.
I'd probably only do that on classic TW though. In MicroOS the highest snapshot number is normally the one used, unless booting into a newer one failed for some reason. So the ordering is correct there.

Hmm, using a different sort key is an interesting idea. Especially with a menu patch that would collapse the key for the snapshots. I'd probably only do that on classic TW though. In MicroOS the highest snapshot number is normally the one used, unless booting into a newer one failed for some reason. So the ordering is correct there.

Oh good to know that there's such a difference between Tumbleweed and MicroOS.
Should we change the version to show more information on the snapshot, like grub does? I guess on MicroOS these infomration would also be of interest.
Is there an easy way to check if the system is Tumbleweed or MicroOS (except parsing /etc/os-release)
Since none of these techniques solve the issue though that the version information for the default snapshot would be misleading on TW, I have a few ideas:

since we need to check if we're on  TW or MicroOS for the correct menu sorting, we can also do this to shot extra entries that don't show in the version that it's a snapshot for the default snapshot on TW, so that the boot menu behaves mostly the same as with GRUB, with "normal" entries and snapshot entries. On MicroOS these could be abandonded.

add a config option to set if you want extra entries for the default snapshot that don't make it obvious that it's actually a snapshot to make it configurable on a per-system level. Here, one could also configure if the default snapshot should be sorted as first entry.
I don't know how/if you planned to support UKIs, but if this tool should also be able to utilize these at some point, a config option to switch between kernel/initrd and uki could be provided. Then we'd need a config file anyway.

I could write a seperate tool to handle these, but that would cause quite some code duplication between our tools.

What do you think?

Is there an easy way to check if the system is Tumbleweed or MicroOS (except parsing /etc/os-release)

Currently I do it like this: https://github.com/openSUSE/sdbootutil/blob/main/10-sdbootutil.snapper#L6

Since none of these techniques solve the issue though that the version information for the default snapshot would be misleading on TW, I have a few ideas:
1. since we need to check if we're on  TW or MicroOS for the correct menu sorting, we can also do this to shot extra entries that don't show in the version that it's a snapshot for the default snapshot on TW, so that the boot menu behaves mostly the same as with GRUB, with "normal" entries and snapshot entries. On MicroOS these could be abandonded.

Suppose we do that. So we'd have some "openSUSE Tumbleweed" entry that refers to snapshot 1 (or none to use the default subvol). Then rollback to snapshot 66. We end up with snapshot 77 as new default subvol. So the tool would have to deal with the previous default entries somehow. Rename them and edit the title and sort key. Also, if it they didn't have subvol=1 in the parameters that would have to be added (how do we know?).

2. add a config option to set if you want extra entries for the default snapshot that don't make it obvious that it's actually a snapshot to make it configurable on a per-system level. Here, one could also configure if the default snapshot should be sorted as first entry.

I wouldn't add config options. We need a sensible default behavior.

Hmm maybe I think too simple again, but my idea would be: We don't specify a specific subvolume. When a new kernel gets installed, we add an entry, when one gets removed we remove the corresponding entry (kernel name could be in the file name to find it).
When a user does a rollback, we simply delete all those entries and recreate them for the then installed kernels. This way, we don't have to manage them in detail. Yes, when a kernel is installed in both snapshots that entry gets created again, but that's not a big overhead, as it's just about text files.
The snapshot files should be independant of those (so the files pointing to snapshots aren't converted to Tumbleweed ones and vice versa, this is also the behaviour of grub, where entries in the snapshot submenu exist for the current default snapshot).
Am I missing something?
I could create a prototype to try it. :)

Completed by #17


HHH-6974 Redirect naturalId criteria queries to new API

Add a check in SessionImpl for critera queries that use the NaturalIdentifier criterion and
redirect the call to NaturalIdLoadAccess
Add NaturalId query execution tracking into the statisticsHHH-6974 Redirect naturalId criteria queries to new API

Thanks Eric.  This work will be in 4.1 as well.


[v6] RFC: Complex Fields API addition

Currently my application has complex inputs that are wired with two fields. Although this is totally achievable with the current API, I've had to create multiple wrapper components and string through Field props to get what I'd like. Consider this example:
We're building a todo item with two fields "description" and "tags". Not only can you add tags to a todo item, but they're also automatically added if a tag's name is in anywhere in the description. Currently I'd have to wire it up like so:
const TodoItemDescriptionEnhancedWithDescriptionAndTags = ({ descriptionField, ...tagsField }) => {
    <input
        {...descriptionField}
        onChange=(event => {
            descriptionField.onChange(event)
            const value = event.target.value
            if (tagInDescription(value)) {
                tagsField.onChange((tagsField.value || []).concat(value))
            }
        })
    />
}

const TodoItemDescriptionEnhancedWithDescription = descriptionField => {
    <Field
        name="tags"
        component={TodoItemDescriptionEnhancedWithDescriptionAndTags}
        descriptionField={descriptionField}
    />
}

const TodoItemDescription = () => {
    <Field
        name="description"
        component={TodoItemDescriptionEnhancedWithDescription}
    />
}

<Field
    name="description"
    component={TodoItemDescription}
/>

As you can see this is a pain. It gets worse if you want TodoItemDescription to take its own props as those have to wired through all the components themselves to not get subsumed into the field props.
What if Field's name prop also takes an array of field names and if it is an array and for every element (let's say named "foo") in that array it generates a "fooFields" object that contains all the props for the "foo" field. Then the code would be much simpler and look like so:
const TodoItemDescription = ({ descriptionField, tagsField }) => {
    <input
        {...descriptionField}
        onChange=(event => {
            descriptionField.onChange(event)
            const value = event.target.value
            if (tagInDescription(value)) {
                tagsField.onChange((tagsField.value || []).concat(value))
            }
        })
    />
}

<Field
    name={["description", "tags"])
    component={TodoItemDescription}
/>

Wanted to see if this seemed valuable to others before trying to send out a PR to accomplish this goal. Lemme know!

Fields made it possible! Check #1554


Change the version tag format to v${VERSION}

This change should remove the odd parent-pom-$version scheme and to offer something more convenient for GitHub users and for deployments to DockerHub.

Ci is dead so 🤷♂ . Alpha anyway


Cursor has to be empty to take out fluids in form of buckets

Describe the bug
It's not possible to take out fluids while dragging an empty bucket. The cursor must be empty for it to work.
https://github.com/user-attachments/assets/b68e5ac5-777e-43b2-ad3d-d172e25ff08c
How can we reproduce this bug or crash?

Put water into the grid
Try to pick it up while dragging an empty bucket

What Minecraft version is this happening on?
Minecraft 1.21
What NeoForge or Fabric version is this happening on?
21.0.61-beta
What Refined Storage version is this happening on?
v2.0.0-milestone.4.4
Relevant log output
No response

will this work with the mekanism integration and allow you to extract gasses with chemical tanks/pippets

Yes


Why does replacing the dataset  with ShapeNetPart report an error as follows.

Why does replacing the dataset in command
‘python main.py
--dataset ModelNet40
--data_path /your/path/to/dataset/
--transfer_attack_method ifgm_ours
--surrogate_model pointnet_cls
--target_model pointnet_cls
--step_size 0.007
--max_steps 50
--eps 0.16’
with ShapeNetPart report an error as follows：
‘UnboundLocalError: local variable 'batch_id' referenced before assignment’？Looking forward to your response, thanks!

Could you please provide the whole log that reports this error?
I guess it is because your data loader is an empty iterator, thus please check whether the ShapeNetPart dataset is successfully downloaded and loaded.

Thank you very much for your reply, I tried to download the dataset from somewhere else and solved the problem, but when I run srs defense command
’python main.py  --dataset ModelNet40 --data_path /data/YwData/PC_work/data/modelnet40_normal_resampled/ --transfer_attack_method ifgm_ours  --surrogate_model pointnet_cls  --target_model pointnet_cls --defense_method srs --step_size 0.007  --max_steps 50  --eps 0.16‘
, I get the following error,
’AttributeError: 'NoneType' object has no attribute 'data'‘
but SOR as well as DUP-Net is normal, what is wrong with mine?

May I ask from which place you downloaded the ShapeNetPart dataset, I also encountered the same problem as you. The direct download with the command wget https://shapenet.cs.stanford.edu/ericyi/shapenetcore_partanno_segmentation_benchmark_v0.zip --no-check-certificate is not correct either.

Using random seed 2022
Start Loading Dataset...
Finish Loading Dataset...
0it [00:00, ?it/s]
Traceback (most recent call last):
File "main.py", line 202, in
main()
File "main.py", line 141, in main
atk_success /= batch_id + 1
UnboundLocalError: local variable 'batch_id' referenced before assignment


[1.15] switchSelectionEndpoint doesn't work

Windows Terminal version
1.15
Windows build number
No response
Other Software
No response
Steps to reproduce
I entered mark mode (or just started with a mouse selection), and switchSelectionEndpoint doesn't do anything.
It might be important to note that I'm using it from the command palette.
Expected Behavior
No response
Actual Behavior

(putting this here for if somebody comes by before I do)
The weirdest thing! This doesn't repro on a Debug or Release build of main, but it 100% repros on the WT Preview build we're selfhosting! I'll take a closer look after the holidays!


[REQ] Ability to override fonts loaded from the Roblox Marketplace

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
Some places use fonts that are from the Roblox Marketplace and I would like for Bloxstrap to have the ability to override those fonts with the custom font set. Y'know, for consistency with the custom font.
feel free to call me based lol

Impossible


Add Test of Premine Beneficiary with nth Receiving Address

We cannot rule out that premine beneficiaries generated a non-standard public receiving address, for instance by invoking neptune-cli own-receiving-address multiple times. It is important to ensure that they can still claim their premine allocation without jumping through hoops or invoking technical support. To this end, let's add a test that:

generates a wallet, and generates a sequence of n generation addresses
allocates a portion of premine tokens to the nth generation address
synchronizes the wallet to a network initialized with this premine allocation
verifies that the wallet in question has the right balance.

Similar tests are already in place but only for n = 0. So this task involves adapting this test to higher n, say n = 15 or so.
Cfr. #299.

Note that this test must simulate recovery from seed phrase, so any supplementary state (counters or indices) must be reset.


syscall.SIGUSR1,syscall.SIGUSR2,syscall.SIGTSTP,syscall.Kill makes endless unusable on windows

i found endless uses syscall.SIGUSR1,syscall.SIGUSR2,syscall.SIGTSTP,syscall.Kill, these things are not defined on Go 1.6.2 on windows. so codes using endless can not even be compiled.
endless: 2cdc20a776897c0f406853c048c33e2c1a9f0ebf
would you please fix this?

Windows does not provide sophisticated process controls or signalling; the best endless would be able to achieve on Windows is hard restarts.

This is problematic for even developing on windows. I export to linux, but testing and running on windows is impossible.

..\vendor\github.com\fvbock\endless\endless.go:64: undefined: syscall.SIGUSR1
..\vendor\github.com\fvbock\endless\endless.go:65: undefined: syscall.SIGUSR2
..\vendor\github.com\fvbock\endless\endless.go:68: undefined: syscall.SIGTSTP
..\vendor\github.com\fvbock\endless\endless.go:111: undefined: syscall.SIGUSR1
..\vendor\github.com\fvbock\endless\endless.go:112: undefined: syscall.SIGUSR2
..\vendor\github.com\fvbock\endless\endless.go:115: undefined: syscall.SIGTSTP
..\vendor\github.com\fvbock\endless\endless.go:119: undefined: syscall.SIGUSR1
..\vendor\github.com\fvbock\endless\endless.go:120: undefined: syscall.SIGUSR2
..\vendor\github.com\fvbock\endless\endless.go:123: undefined: syscall.SIGTSTP
..\vendor\github.com\fvbock\endless\endless.go:224: undefined: syscall.Kill
..\vendor\github.com\fvbock\endless\endless.go:224: too many errors


Context
its helps understand what twitter brains are saying
Term
IRL
Definition
In real life
List of category options
General (i.e. blockchain, fud, fomo, gm, etc...)
Additional Information
No response

Thanks for submitting the request @agbadilawal !  I'll schedule this for upload


puckel-airflow-with-docker-inside Removed

I tried today running: docker-compose up and I got the following:
Pulling webserver (puckel-airflow-with-docker-inside:latest)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.
It seems that the image got removed. Any ideas how can we work around it?

Never mind. I should've built the image first.


Add blog contributors data

Why:

Some blog post authors are no longer on the team, some were just
guests.

Forever in our :heart:


Fix automated tests, test with fixed dependencies

Flamedisx's continuous integration testing is currently broken: TravisCI now requires payment, and CodeFactor seems to have gone silent  after https://github.com/FlamTeam/flamedisx/commit/8f231df9edb956bef03f44e00bb3f730819eef65 (and complained about too many things before that).
This will:

Add configuration for GitHub Actions. This will run our unit tests and a code style checker (flake8) automatically on commits.
List one specific version of all dependencies in requirements.txt. Users have the option to use these version if they do pip install flamedisx[strict-deps], but by default the version restrictions are unchanged (and now listed in requirements_minimal.txt). GitHub Actions will always use the strict/pinned dependency versions for testing; otherwise, the tests could randomly break if a dependency pushes an update.
Add configuration for Dependabot, which (after this is merged and I change a few settings in the repo config) will make weekly PRs to update requirements.txt with new dependency releases, much like in https://github.com/XENONnT/base_environment/pulls. This will give us a chance to see if new tensorflow/numpy versions etc. break flamedisx or not.
Remove the now-obsolete codefactor and travis configurations.
Fix a few PEP8 errors, which may have crept into flamedisx while the style checker was off. I currently let flake8 ignore x1t_sr1.py: there are a few PEP8 things there, but I don't want to mess up the code Pueh is maintaining. @plt109, whenever you get a chance to look at that file, we can remove the ignore.

TravisCI also used to take care of uploading new releases to pypi. We'll have to do that manually, or add another github action workflow.

Sorry guys, I am going to breach protocol and merge this; otherwise we can't really be sure any of the other PRs work.


[BEAM-10496] Improve nullability analysis for :sdks:java:core

The total number of nullability issues in :sdks:java:core is very high. These are some baby steps towards embracing nullability typing. While not discovering any latent NPE this time, it did uncover improvements to the core SDK:

inlining completely trivial functions and their trivial tests
moving to Java function instead of Guava function
moving to Java streams instead of Guava FluentIterable
moving irrelevant null check out of utility function that has no reason to accept null parameters

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Based on the quality of null handling in zetasketch, pinging you on other similar PRs @robinyqiu

Flakes were https://issues.apache.org/jira/browse/BEAM-9968 and https://issues.apache.org/jira/browse/BEAM-10470

Run Java PreCommit


Cleanup db.Provider code

This PR does a few minor simplifications of the db.Provider code, and adds a more helpful error message when the user gives an unsupported provider.

Oh, also the build is failing


put last updated file for every AJAX call

when you're running in kiosk mode, sometimes the browser that YANPIWS is running in will die after a long time.  if we update a file for ever AJAX call then it'll be easy to tell when the browser last updated

reopened by accident!

ok - reopening for reals ;)  We should add a {{healthcheck}} endpoint on ajax.php.  This way the main browser hits it when loaded, but the other devices wont (eg ones just getting temps or datetime and what not)


Add gist:refersTo object property

Proposal: Add gist:refersTo data property, with a domain of gist:Content.  Definition: "The Subject content indicates, signifies, or points to the Object."
Background: I was looking for a way to associate an Address (which is content) with a GeoRegion.  It is improper to say "content is located in a GeoRegion".  I considered using the extant gist:isAbout property.  But that didn't seem quite right.  After a bit of Teams discussion, I decided to propose gist:refersTo as a new property.
Example:

:_1617Humboldt a gist:Address .
:_RussianRiverWatershed a gist:GeoRegion .
:_Steven gist:residesAt :_1617Humboldt .
:_1617Humboldt gist:refersTo :_RussianRiverWatershed .

This is a peculiar example. How can a street address refer to a watershed?

indicates, signifies, or points to

It might be a good idea to have a property that means "indicates, signifies, or points to" but those
words are not what comes to mind by the phrase 'refers to'
Dave often says a physical address corresponds to a routing algorithm to a physical place.
Michael

Given that opening from @uscholdm ...
The idea that an address is a subClassOf Content seems wrong to me. And that is not just an off the cuff remark, I've been thinking about it since Dan posted his "aha" message (not on github).
I've read the several threads this has been discussed in and I keep coming back to this. The capturing of the address, the written manifestation of an address is content (in RDF, the literal(s) that contain the address). But the idea of an address is something different, it is a destination where something physical or electronic can be delivered. That idea/concept, the class itself, I do not think is content.
I do not know where in gist I would put it. I think an address is part Artifact (or maybe not... we deal with human addresses which are artifacts, but even without humans the concept would still be valid), part Commitment (follow the routing guidelines and something should be deliverable), part Goal (we create addresses in the hope of being able to deliver something), part Place (except that gist:Place is too narrowly defined to be a specific geographic physical feature and excludes virtual places [how is that going to work in the metaverse?]).
Also, I think the use of the words physical and virtual when describing addresses might be subtly incorrect. The "physical" means that something physical can be delivered to the address, but the destination represented by the "physical" address might not be a specific physical spot that can be identified by GPS coordinates and never moves. The use of the word "virtual" I think has been used to represent an electronic destination. The address itself is not physical or virtual, but specifies what types of things can be delivered/received.

I think this might mean we should make gist:isAbout's documentation slightly more general or slightly more specific. As it is currently it looks like it is somewhere between dcterms:subject and ^dcterms:isReferencedBy.
dcterms doesn't express this but I do think "being the subject of something" is a more specific kind of "being referenced by something." Given that, another option is to add Dan's proposed gist:refersTo as a superproperty (and an object property) of gist:isAbout. That would give Gist near equivalents to ^dcterms:isReferencedBy and dcterms:subject though.

The capturing of the address, the written manifestation of an address is content (in RDF, the literal(s) that contain the address).

Yeah, @Jamie-SA , I think gist:Address as a subclass of gist:Artifact makes sense. But maybe it doesn't need to go further down the tree to gist:Content?

Jamies comments are very interesting. Addressed that correspond to physical places often do not correspond to what is a fixed area on the surfact of the earth. A PO box is a good idea. The physical location of my wifes po box moved to  a mile a way. The address, as content did not change.  Dave's emphasis that an address always corresponding to a routing algorithm to get to 'somwhere' applies here. The address stayed the same, the routing algorithm may have been the same, but the inputs to the algorithm may have changed to pop out a new physical place.
ALso, many addresses inside companies go to a slot in a mail room which is never going to correspond to a GeoRegion, you;d need something more granular - an danywah the mail room can move down the hall or to a different floor much like my wifes' PO box.
So I;'m leaning towards keeping address as content.

the use of the words physical and virtual when describing addresses... The address itself is not physical or virtual, but specifies what types of things can be delivered/received.

What I mean by a physical address is that the routing algorithm at any given moment will take you to a physical place on the earth - whether in a house, or a mailroom or a PO Box post office or most interestingly perhaps, a slot in a room on a shipp for a shipping address for a naval officer whose ship could be anywhere.
THE other addresses whether we call them virtual or electronic, I don't have a view, but what is definitely true is that the routing algorithm will not take a message to a physical place in any useful sense of 'physical place'.

The physical location of my wife's po box moved to a mile a way. The address, as content did not change.
Similarly, a house's address can be changed (road name, building number, even city can be changed), but the house remains fixed to the earth.

All this discussion should more appropriately be conducted under my #721 ticket.

Circling back to @uscholdm's original comment... If we assume that Address remains a subclass of Content, what verb would you suggest we use to link a physical address to a geopoint and/or georegion?

what verb would you suggest we use to link a physical address to a geopoint and/or georegion?

'routesTo' is one possibility

That works when you are tying an address to a very specific place.  But what if I want to tie the address to the country georegion?  In that case routesTo doesn't seem as appropriate, IMO.

what verb would you suggest we use to link a physical address to a geopoint and/or georegion?

oh, i think gist already has the thing needed (from the other direction): gist:hasAddress?

Intersting, isAddressOf would be the natural name for that property.  Most often it is a person or a business that has an address, sometiems a building, rarely a GeoRegion.

@justin2004  "America hasAddress :4815TabardPl" doesn't work.
We need a way to say that an Address points to or indicates some Place.  That Place can be as big as a country or as specific as a building.  It is very natural in business data to want to link an address to its country, state, city (which have their own IRIs).

@DanCarey404 I think I might do something like:
[ gist:hasAddress  :4815TabardPl ]  gist:isGeographicallyContainedIn :America .

Upgrading the bnode as necessary. What do you think?

Nope, because the blank node could be a person, an org, a building that has the address.  The domain and range on :isGeographicallyContainedIn are :Place.  (Also, I am generally opposed to relying on blank nodes when transforming data.)

How about:
:pep0 a gist:Person .
:pep0 gist:hasPhysicalLocation :loc0 .
:org0 a gist:Organization .
:org0 gist:hasPhysicalLocation :loc0 .
:bldg0 a gist:Building .
:bldg0 gist:hasPhysicalLocation :loc0 .
:loc0 gist:hasAddress :4815TabardPl ;
         gist:isGeographicallyContainedIn :America .

While that works, it adds a level of indirection.  I'd prefer to find a property name that does what the ticket is requesting.

I feel like one of Gist's purposes is to prevent two arbitrary things from being directly connected. It feels ideal for some things to have some semantic distance between them.
Gist makes you say "thing X has a physical location - that location has an address - that location is contained within a place."
And the corresponding triple patterns:
?thing gist:hasPhysicalLocation ?loc .
?loc gist:hasAddress ?addy ;
       gist:isGeographicallyContainedIn* ?place .

(I know you know that too I just wanted to type it it to see how the indirection feels.)
I think I prefer that indirection. Without some indirection we'd have full mesh graphs!

I agree with @DanCarey404 - the address discussion should be moved to the other issue. To comment on the proposal of gist:refersTo, @DanCarey404 I think you mean an object property rather than a datatype property? I've take the liberty of changing the issue title. I have just had a need to define an object property refersTo in a client ontology, and support the addition of this predicate to gist.

@justin2004 gist:hasAddress does not mean the same thing. Dan wants my home address to point to, say, the city, state, country in which it's located, but this is not the address of that place.

@rjyounes , I meant that in Dan's example we can follow gist:hasAddress backwards.
e.g.
?addy ^gist:hasAddress/gist:isGeographicallyContainedIn* ?place

Also, @DanCarey404 , I didn't see gist:residesAt in the current version of Gist.

I have just had a need to define an object property refersTo in a client ontology, and support the addition of this predicate to gist, without the domain specification.

Semantically, refersTo is closely related to gist:identifies (inverse of identifiedBy) - perhaps a super-property?

?addy ^gist:hasAddress/gist:isGeographicallyContainedIn* ?place

Inverse of hasAddress has Address as its domain.  That makes ?addy a gist:Address, which I don't think you mean.

That is what Dan wanted in his example:
:_1617Humboldt a gist:Address .
:_RussianRiverWatershed a gist:GeoRegion .
:_Steven gist:residesAt :_1617Humboldt .
:_1617Humboldt gist:refersTo :_RussianRiverWatershed .

:_1617Humboldt  is a gist:Address

@DanCarey404 I did a little experiement with an OWL 2 RL reasoner.
I put Gist and this:
:refersTo owl:propertyChainAxiom  ( [ owl:inverseOf gist:hasAddress ] gist:isGeographicallyContainedIn  ) .

into the the Tbox and this:
:stevens_house gist:hasAddress :addy0 .
:stevens_house gist:isGeographicallyContainedIn :watershed0 .
:watershed0 gist:isGeographicallyContainedIn :franklin_county .
:franklin_county gist:isGeographicallyContainedIn :america .

into the Abox.
Then ran:
prefix : <http://example.com/>
select * where {
   ?s :refersTo ?o .
  }

which yields:

s
o

http://example.com/addy0
http://example.com/watershed0

http://example.com/addy0
http://example.com/franklin_county

http://example.com/addy0
http://example.com/america

Which is a long way of me saying I think defining a :refersTo using Gist primitives in a sub-ontology might be the way to go.

residesAt does not exist in gist, it is in a proposal of modeling addresses proposed by Dave. He does not necessarily propose adding the predicate to gist, but may be just using it illustratively. PowerPoint attached.
Addresses in gist  -  Read-Only.pptx

Semantically, refersTo is closely related to gist:identifies (inverse of identifiedBy) - perhaps a super-property?

@uscholdm In my use case it is not in at all related to gist:identifies.

See also #471, #483, #594, #721, #1009

@DanCarey404

We need a way to say that an Address points to or indicates some Place. That Place can be as big as a country or as specific as a building. It is very natural in business data to want to link an address to its country, state, city (which have their own IRIs) because you want to query for the Addresses in that GeoRegion.

I think it would be better to point an address to the narrowest physical place that makes sense.  The place where the routing algorithm takes you.  From there, you can use geo containment to your heart's content. Having one predicate for directly linking an address to many regions of different sizes seems like a bad idea to me.

Completed in gist 13.0.0.


Optimize performance of IsAnonymousType method.

I have came across performance drop when reading from DB after upgrade from v3 to v5.
The profiler shows that one of bottlenecks is IsAnonymousType method which is quite expensive.
This fix resolves two problems.

call IsAnonymousType only if BsonValue.IsDocument
optimise IsAnonymousType method - use Attribute.IsDefined instead of GetCustomAttributes, because it is more performant (there is #if because it is not available for .NET Standard 1.3)

Thanks!
I don't know how slow is Attribute.IsDefined or GetCustomAttributes, but I think it should check FullName at first as faster condition and check for attribute only if name is correct.

Very good point!
FullName check is much faster than Attribute check. Maybe then it is not necessary to use Attribute.IsDefined and avoid #if (always use GetCustomAttributes) to prefer simpler code.
I will update the PR.

There are some numbers to support these changes.
Reading 1 000 000 items from DB (single collection).
Items are represented by this simple class
class Entity
{
    public object Data { get; set; }
}

Before optimization: 3443 ms
After optimization: 1888 ms
Performance improvement is most noticeable when using object type properties in DB entities.

@yaho86 I'll try to create a Benchmark for this case as well 🙂

@JensSchadron I used just simple FindAll() to get these numbers. This optimization helps always if deserialized class has properties of type object.
Anyway, thanks for the merge and great work with LiteDB 🙂


Skip unrecognized JSON files when loading models

Issue #, if available: #1841
Description of changes:
This commit updates the model loading process so that JSON files that are not objects or that don't contain a top-level "smithy" key are skipped. This can be useful when loading directories that contain Smithy models mixed with other JSON files. JAR files that contain Smithy models are not permitted to refer to unrecognized JSON files that lack a valid "smithy" version key/value pair.
This commit also only creates InputStreams for files that Smithy can actually load or attempt to load. Smithy would previously open an InputStream for all recursive files in a directory even if it was unable to load the file based on the filename. It now only creates an InputStream when the file has a .json, .smithy, or no file extension.
Closes #1841
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mtdowling do you have a timeline for the next release? This and #1838 would be really nice to have for my team.

We're planning for a Monday release

awesome, thanks!


Terminating extension renderer for bad IPC message

crash after restart electron main process occasionally

electron version                17.1.2
os mac mini(M1, 2020)    11.6.2
plugin version                    1.0.5
used in https://github.com/umbrella22/electron-vite-template.git

I have not reproduced it locally. try:


Update land-use information and database handling scripts and docs

Description
Checklist
Please confirm that this pull request has done the following:

[x] Documentation added (where applicable)
[x] Changelog item added to changelog/

@eleanororourke this will update the web page (in a couple of minutes once it's deployed). The preview is here: https://input4mips-controlled-vocabularies-cvs--127.org.readthedocs.build/en/127/database-views/input4MIPs_delivery-summary_CMIP6Plus.html

Alrighty @eleanororourke all live here: https://input4mips-controlled-vocabularies-cvs.readthedocs.io/en/latest/database-views/input4MIPs_delivery-summary_CMIP6Plus.html

Quick check - should land use be (0850-2024) or (1850-2024)? It is showing currently as 0850-2024

0850-2024. I'm not sure why, but there data starts in 850 not 1850

Ok, 0850-2024 is now on the website!

Some of these data are temporally extended as far back as they can go (@znichollscr pushes back to year 0001, @taubry pushes back to 1750) as many are used across MIPs and pre-1850 matters for some of these.. if we can extend these further back, great. The SSTs are imaginary pre-1950s, but the HadISST data extends back to 1850 v2, v1 starts in 1870


favicon 404 on firefox desktop

I am getting a 404 error on firefox when it attempts to load the icon.
I think this may have to do with the order that it loads the website, it first does a redirect to /en then attempts to load the icon from the URL /en/favicon.png causing a 404.

I think this could be fixed by making sure the favicon.ico loads which at the moment isn't present in the networking tab.
I can go ahead and add this to #199

Changing the following seems to be fixing the issue in my local build:
export const config = {
  // TODO: Find a way to handle these dynamically
  matcher: [
    '/((?!_next/static|_next/image|assets|favicon.ico|android-icon|favicon|manifest.json).*)',
  ],
}

it is Redirecting android-icon and favicon to /[lang], hence the 404

I think that this can be closed now actually, with #199, #247 now in master I do not seem to be getting those 404 errors

In firefox I am still getting 2 -  404 for favicon-32x32 and android-icon-192x192:

Sorry commented too quickly, definitely still an issue. Is this because in our head.tsx file our image hrefs are /favicon-192x192.png and not /_next/image?url=%2Fandroid-icon-192x192.png&w=3840&q=100

Changing the following seems to be fixing the issue in my local build:
export const config = {
  // TODO: Find a way to handle these dynamically
  matcher: [
    '/((?!_next/static|_next/image|assets|favicon.ico|android-icon|favicon|manifest.json).*)',
  ],
}

That didn't work as expected for me

Changing all of the Links in head.tsx to follow this format fixes this for me
<link
  rel="icon"
  type="image/png"
  sizes="192x192"
  href="/_next/image?url=%2Fandroid-icon-192x192.png&w=3840&q=100"
  />

But is this really the only/ best solution?

Changing all of the Links in head.tsx to follow this format fixes this for me
<link
  rel="icon"
  type="image/png"
  sizes="192x192"
  href="/_next/image?url=%2Fandroid-icon-192x192.png&w=3840&q=100"
  />

But is this really the only/ best solution?

I have created a draft PR #254
this is the network tab output for favicon and android-icon in firefox:


"Named" callables; i.e. array('name' => $callable)

Named callables what?

I do not speak English well. I will make an example for 10 min and show.

rules required should be checked first and then all the rest.
Send form but do not fill in the field. To check the rule required
https://dev.dilexy.ru/

Maybe need change
return array_merge($callbacks, $new_rules);
to
return array_merge($new_rules, $callbacks);

No, callbacks do come before required.


suggestion: add CI checks

I suggest adding CI checks, like formatting and linting checks and tests, to ensure all PRs are up to your standards and don't break anything.

I do need to make some tests, that always tends to be an afterthought. For the linting, I'll need to look into it as it's new to me and seems to offer a lot.

3076754085f0b8d81734771a4b203dd5fab273f1


PR to resolve issue [incubator/kafka] Add support for imagePullSecrets #18227

Hey,
I've added the condition and stanza needed to define imagePullSecrets to pull the broker image from a private registry.
I tested the deployment in one of our kubernetes clusters and
...
imagePullSecrets: []
...

and
...
imagePullSecrets:
  - name: <secretName>
...

worked fine with helm install kafka/ --name kafka --namespace <test-namespace>.

@OlGe93
Kafka needs a version bumped to latest.

@zanhsieh
Where should the version be bumped and why to latest? :)

@OlGe93
Check the ci/circleci: lint-charts below:
==> Linting incubator/zookeeper
Lint OK

1 chart(s) linted, no failures
Error linting charts: Error processing charts
------------------------------------------------------------------------------------------------------------------------
 ✖ kafka => (version: "0.20.1", path: "incubator/kafka") > Chart version not ok. Needs a version bump!
 ✔ zookeeper => (version: "2.2.0", path: "incubator/zookeeper")
------------------------------------------------------------------------------------------------------------------------
Exited with code 1

/retest


how to start image in docker?

Hi,
I have built a dockerfile from the directory "2.4". I did copy the file to my ubuntu OS, and ran following commands:
$ docker build -t my-apache2 .
$ docker run -it --rm --name my-running-app my-apache2
The first command seems to works. It took quite a while but then it finished. But running the image is not possible. Im getting the following error response:
docker: Error response from daemon: Container command 'httpd-foreground' not found or does not exist..
Any idea what this could be? Or am I following the wrong path? (im a docker newbie!)
thanks.
Arjan

You probably need to chmod +x httpd-foreground in the 2.4 directory and docker build again.


Connected but not authenticated

Describe the bug
Hey :)
I've been trying to use ibeam and I've successfully connected after 2fa but none of the APIs actually work. When I check my authentication status I see that it is because authenticated is set to false, although connected is set to true.
I've tried using the authentication / session inits from the docs but none of them worked.
Although, when I downloaded the latest gateway client, all I had to do was connect normally (once through the browser + 2fa) and then I was immediately authenticated and able to run all API calls.
To Reproduce
Steps to reproduce the behavior:

run docker run --env-file ibeam.env -p 5000:5000 voyz/ibeam when ibeam.env contains your authentication variables (IBEAM_ACCOUNT, IBEAM_PASSWORD)
After connection, send POST to https://localhost:5000/v1/api/iserver/auth/status
check authenticated field

Expected behavior
To have authenticated: true
Environment
IBeam version: 0.3.0
Docker image or standalone: Docker image
Python version (standalone users only):
OS:
Additional context
Add any other context about the problem here.
Suggest a Fix
I don't know what the problem exactly is, I've tried re-building the image with the latest gateway client but I haven't had any success because when it tries accessing the login page it shows access denied. If nobody here has some quick fix then I'll keep investigating this issue.
Thanks!

Hey @sidfeiner welcome to IBeam! 😊
Thank you very much for describing your issue in so much detail - I appreciate it! At the same time, I'm sorry to say that this seems to be a duplicate of this (not so well named) other issue #19. Just like there, my suggestion would unfortunately come down to:
I'd recommend you get in touch with the IBKR support and try to work with them to figure out why the authentication fails despite providing correct credentials. I'm sorry I cannot be of more help, but this is a known problem that we cannot jump over on IBeam side despite multiple attempts. Feel free to suggest any fixes if you can think of any.
In reality this seems to be a matter of luck - not which version of the Gateway we're running. I'd recommend these steps to verify this statement.
It sucks, but it's a known problem and the solution lays on IBKR side, therefore pushing them to fix it is the only way we've found so far. As with other users running into this issue - if you can think of some intermediate solution, please feel free to share it. Thanks!

Hey @sidfeiner I'm going to close this issue as a duplicate. Feel free to reopen if you feel you'd like to continue the discussion. Thanks for reporting nevertheless!


Account Registration

When a user registers their account will be created, but will not be usable until verified through email.

[ ] Hash password
[ ] Create new unverified user in database
[ ] Send verification email

 Create Account


change module to ThreeDotsLabs/watermill-jetstream

@ma-hartma FYI - you should just be able to repoint your upstream.

@AlexCuse Thanks! Cool, that this is an official implementation now! :)

@AlexCuse could you please tag the current version as a release since go mod will throw following error:
go: downloading github.com/ThreeDotsLabs/watermill-jetstream v0.0.4
go<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/AlexCuse/watermill-jetstream
                but was required as: github.com/ThreeDotsLabs/watermill-jetstream

Done just wanted to merge the proto thing first.


dhcpcd: No need to hack around broken patchShebangs anymore

Motivation for this change
Now that https://github.com/NixOS/nixpkgs/pull/43833 has landed.
Things done

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

[ ] NixOS
[ ] macOS
[ ] 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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

I wonder if runtimeShellPackage should be automatically in build inputs? This could lead to less surprises as it has historically just worked when not cross compiling.

So by the "principle of least authority" I'm usually cautious about adding auto deps. It complicates bootstrapping (c.f. crossLibcStdenv for building libc) too. But I'd be OK with it as part of the strictDeps transition or something.

Success on x86_64-linux (full log)
Attempted: dhcpcd
Partial log (click to expand)
shrinking /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/sbin/dhcpcd
shrinking /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/lib/dhcpcd/dev/udev.so
gzipping man pages under /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/share/man/
/nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8
strip is /nix/store/rf59n87kcrrnrnw3l3s94q879m8vaspm-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/lib  /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/libexec  /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/sbin
patching script interpreter paths in /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8
/nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/libexec/dhcpcd-run-hooks: interpreter directive changed from "/bin/sh" to "/nix/store/c7jw834if7hnq8blv8yw0zbw4dj5wpck-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8...
moving /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/sbin/* to /nix/store/jc3jh4fgdb0mw4y6yimiya4gygwbr257-dhcpcd-7.0.8/bin

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: dhcpcd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: dhcpcd
Partial log (click to expand)
shrinking /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/lib/dhcpcd/dev/udev.so
shrinking /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/sbin/dhcpcd
gzipping man pages under /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/share/man/
strip is /nix/store/lw308kxqcm9frx4vlfjh30da1x4gsmwx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/lib  /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/libexec  /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/sbin
patching script interpreter paths in /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8
/nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/libexec/dhcpcd-run-hooks: interpreter directive changed from "/bin/sh" to "/nix/store/4y6cwvlhgijd84z5q0y6cdar81kjrljp-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8...
moving /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/sbin/* to /nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8/bin
/nix/store/vfksnj3xv9sf78bl2bs65z5v451l1qd4-dhcpcd-7.0.8


Update web-audit extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Nothing happens when I open/close tips - what is supposed to happen? 😊

@pernielsentikaer the issue should be fixed now 😊

The only thing I miss is a loading indicator, maybe something like:
      {loading && <Detail isLoading={true} navigationTitle="Analyzing..." />}
      {result && !loading && (
      ...

And then set the initial state to true for loading


Fix typo

Thanks!
@bors r+

:pushpin: Commit de64acecb2d60bab73d6ab666bfd9ef79ca49609 has been approved by ehuss

:hourglass: Testing commit de64acecb2d60bab73d6ab666bfd9ef79ca49609 with merge 9d9cbd11ab2866cf554c5aa3057cc8dab414732c...

:sunny: Test successful - checks-azure
Approved by: ehuss
Pushing 9d9cbd11ab2866cf554c5aa3057cc8dab414732c to master...


Feature Request: Enhanced Privacy Mode

Upload Thing has proved to be an efficient and effective solution for setting up file uploads in my project. However, I am currently facing a challenge with user privacy. The application I am developing requires users to upload files that are intended to be private. As it stands, these files are openly accessible on S3, which does not suit my needs.
I propose the implementation of an Enhanced Privacy Mode for file uploads. This could be achieved by adding a private: true flag to uploads, which would restrict file access only to authenticated download requests. The access to these files should be limited to the server that contains the UPLOADTHING_SECRET.

Yup. this is on our roadmap!

Would this mean that if we pass along an { access: "private" } option, the files uploaded to S3 would be accessible only from the nextjs server that uploaded the files?
I guess if the user is the owner of the file can still be handled in a middleware, but would be nice to have the files be protected on S3's side.

This would require having the files be protected on S3 (or whichever backing provider) otherwise requesting the files from s3 (or other provider) would bypass the "security".
We do have plans on how we are going to support this, it has just been a bit more work than initially anticipated 😅

Unfortunately not, it is purely an infrastructural thing. We are working on it though, hoping to have something out for end of year

This seems to have been implemented now?

Yup! Sorry I forgot to circle back here!


Fix #3477. Clarify Model.fetch docs

Modified the docs for Model.fetch to describe what happens to attributes set on
the model but not sent by the server. This should address BUG #3477
Before:
Fetch the model from the server. If the server's representation of the
model differs from its current attributes, they will be overridden,
triggering a "change" event.
After:
Fetch the model from the server. If the models differ the two are merged.
Conflicting attributes are overridden by the server's model, triggering a
"change" event.

Thanks for this. You might want to also alter the index.html docs too since it also references the "overrides" terminology.

What about something like:
https://github.com/wettowelreactor/backbone/compare/patch-1

Cool, thanks. Will fix up in a sec.


53 edit remaining holidays

changes since last PR:

added gem 'whenever' that fires every January 1st and updates remaining leave (remaining_leave_last_year = remaining_leave; remaining_leave = 28)
added warning label that exists from Jan 1st to March 31st and tells the user that remaining leave from last year will expire on April 1st
fixed Datepicker appearance
added translations

Auch hier: soll euer team3review branch hinter dem aktuellen Dev sein?

der Review Branch ist jetzt auf dem Stand des Dev

Besides that, LGTM :+1:


Fix sqlite dbd

Fixes #16 and a few other related bugs. Tested with pythons 2.7 and 3.5.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thanks for contributing


House Rent Analysis and Prediction of Mumbai #444

Pull Request for ML-Crate 💡
Issue Title: House Rent Analysis and Prediction of Mumbai #444

Info about the related issue (Aim of the project) :  Create a ML model for analyzing and predicting the house rents of Mumbai based on the given dataset
Name: Aniket Ray
GitHub ID: https://github.com/raysofani
Idenitfy yourself:  Contributer

Closes: #444
Describe the add-ons or changes you've made 📃
I have created the rent analysis and prediction model in Bombay using different ML model algorithms.
Give a clear description of what have you added or modifications made

I have explored the dataset
Perform Exploratory Data Analysis
Visualize the data and relation among features
Done Feature engineering
Identified the outliers and fixes them
Performed machine learning models
used models are:- Linear Regression, Random Forest Regressor, Support Vector Machine, XGBoost
Get the accuracy and rsme  (root mean square error)
Visualize the accuracy and rsme

Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested
Describe how have you verified the changes made
Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

@abhisheks008 sir as in my previous pull request there was an issue, where my files were not showing so i have closed that one and open new pull request with all the visible changes. kindly review it.

@abhisheks008 folder is renamed. Kindly review it

Arrange the images properly, it's looking awful.

@abhisheks008 i have arranged the images properly in readme file. kindly review it

Hi @raysofani please share your email ID for further communication.

@abhisheks008  Thank you approving my work sir!! You guidance will definitely help me in learning and improving my skills.
My email ID-<EMAIL_ADDRESS>


[Search v1] Duplicate Expensify Card charge

Not sure what's going on here, though we should look into this one. I'm seeing a duplicate for a recent Expensify Card transaction on a recent trip.

Clicking on the __fake__ report gives me the "hmm it's not here" not found error. In contrast, the expense which correctly shows the Expensify workspace appears in the RHP without issue.
Assigning internally as part of this release.

@JmillsExpensify is this duplicate charge still visible for you? Could you get the transactionID of both transactions? You could do this by:

Opening browser console: cmd + option + i
Navigate to the Application tab
Select Storage > IndexedDB > OnyxDB > keyvaluepairs
Search for snapshot
Click on the result and expanding data
Look for the transactions with the amount above (note amounts are in cents)
Expand the transaction once you find it and take a screenshot of the data stored

I wanna compare the data to see what's going on with them.

Yes, I still see the duplicates. I can only find data for one of the transactions though in the Onyx DB.

Here's what I'm seeing for those transactions.

Clicking on the __fake__ row gives me a "Hmm, it's not here" error in the RHP.

PR up

PR is merged and deployed. Closing this one.


Lookup scrapers by name, not by initial

Replaces #235 Helps with issues in #229 , #230 , #271 , #273
Checklist

[X] I have read the Contribution & Best practices Guide and my PR follows them.
[X] My branch is up-to-date with the Upstream master branch.
[ ] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

#230 (comment) Lookup scrapers by name instead of by a single letter.
Reduce repetitive scraper list + scraper dict down to a single scraper dict (prep for #233)

@gabru-md Your thoughts?

@cclauss it is definitely a better option as we see the error with yahoo and yandex is caused because both have same initial.
@AnshulMalik please comment

@cclauss any reason why this PR was closed ?


feat(toolbar): Add platform icons

Currently getting this error:
[ERROR] No loader is configured for ".svg" files: node_modules/.pnpm/platformicons<EMAIL_ADDRESS>I have also tried using vite-plugin-svgr for the svg loader too, and a few different configs in tsconfig. I suspect that there may be circular dependencies (see file name above) causing this error
Relates to https://github.com/getsentry/sentry-toolbar/issues/75

The config of platformicons package is completed in https://github.com/getsentry/sentry-toolbar/pull/99
A followup PR is coming to render the icons as needed, replacing this PR.


Warning regarding contentPosition on web

After upgrading to Solito@v3, expo-image and also react-native-web@v19 I am now getting the warning:
Warning: React does not recognize the `contentPosition` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `contentposition` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
    at img
    at eval (webpack-internal:///../../node_modules/next/dist/client/image.js:233:11)
    at eval (webpack-internal:///../../node_modules/next/dist/client/image.js:306:11)
    at SolitoImage (webpack-internal:///../../node_modules/solito/build/image/expo/image.web.js:19:108)
...

contentPosition is not a prop of next/image so maybe it should be omitted when passed to NextImage component on https://github.com/nandorojo/solito/blob/18b283a0dbdfdc78f9115a460e4bfbf9b3d57c33/src/image/expo/image.web.tsx#L32.

oh looks like RNW is no longer stripping props. that’s interesting…
I’d accept a PR.

+1, wanted to open an issue about it didn't found time do to so

is this not in the latest version?

Fixed on 3.2.8


Hypothesis plugin does not work for ConstrainedStr

@Zac-HD's Hypothesis plugin https://github.com/samuelcolvin/pydantic/pull/2097 works great for some constrained type (e.g. ConstrainedInt), but not for others (e.g. ConstrainedStr):
from pydantic import ConstrainedInt, ConstrainedStr
import hypothesis.strategies as st

class MyInt(ConstrainedInt):
    gt = 10
    lt = 15

class MyStr(ConstrainedStr):
    regex = "[A-Z][0-9]{10}"

st.from_type(MyInt).example()  # As expected, values are between `gt` and `lt`

st.from_type(MyStr).example()  # Returns empty str :-(

Thanks for the awesome work by the way @Zac-HD!

Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.1
            pydantic compiled: True
                 install path: /Users/.../lib/python3.8/site-packages/pydantic
               python version: 3.8.8 (default, Feb 24 2021, 13:46:16)  [Clang 10.0.0 ]
                     platform: macOS-10.16-x86_64-i386-64bit
     optional deps. installed: ['dotenv', 'email-validator', 'typing-extensions']

Ah, right - that's because the registration hook (_registered()) for strings is in the constr() helper function, whereas for ConstrainedInt I was able to attach it to the ConstrainedNumberMeta metaclass.
So MyStr = constr(regex="[A-Z][0-9]{10}") is your workaround.
If explicit inheritance from ConstrainedStr et al is supported as part of the public API, I think the best option is to add a new metaclass for all constrained types which ConstrainedNumberMeta can then inherit from.

I believe subclassing Constrained* is preferable over using con* because of https://github.com/samuelcolvin/pydantic/issues/975: mypy will complain that T = con*(...) is not a valid type.
I tried using constr instead of ConstrainedStr and Hypothesis can indeed generate valid examples of it, but not when it's used inside of a BaseModel:
from pydantic import BaseModel, constr
import hypothesis.strategies as st

MyStr = constr(regex="[A-Z][0-9]{10}")

class MyModel(BaseModel):
    foo: MyStr

st.from_type(MyStr).example()  # Generates valid strings
st.from_type(MyModel).example()  # Fails with a ValidationError :-(

It also appears that other constrained types such as ConstrainedList and ConstrainedSet don't work yet either, probably for the same reasons:
from pydantic import ConstrainedList, ConstrainedSet
import hypothesis.strategies as st

class NonEmptyList(ConstrainedList):
    __args__ = [int]
    item_type = int
    min_items = 1

class NonEmptySet(ConstrainedSet):
    __args__ = [int]
    item_type = int
    min_items = 1

st.from_type(NonEmptyList).example()  # Returns [] :-(
st.from_type(NonEmptySet).example()  # Returns NonEmptySet() :-(

I believe subclassing Constrained* is preferable over using con* because of #975: mypy will complain that T = con*(...) is not a valid type.

I don't have any objection to this, but so far as I know all the docs show the latter T = con*(...) style and it's not clear that explicit inheritance is meant to be supported.  Either way, expanding the docs to say would be good.

I tried using constr instead of ConstrainedStr and Hypothesis can indeed generate valid examples of it, but not when it's used inside of a BaseModel:

This is bizzare, and apparently also under-tested 😥
Fixing this would have to start with some detailed investigation that I don't really have time for this week...

It also appears that other constrained types such as ConstrainedList and ConstrainedSet don't work yet either, probably for the same reasons

Different reasons, actually - a particular subtype of e.g. ConstrainedList is a parametrized generic type, and Hypothesis' type-to-strategy resolution machinery only deals in non-parametrized generics (by registering a function which takes a parametrized type object and returns a strategy).
Which would be fine, except that per https://github.com/samuelcolvin/pydantic/pull/2097#issuecomment-753603121 we're waiting on https://github.com/cython/cython/issues/3537!
At present, you just have to provide (or register) a strategy for each model that uses a constrained list or set field.  Maybe the docs should explicitly list what the plugin doesn't handle, too?

Also bumped into this. As already mentioned, the problem is that mypy doesn't approve of = constr() (dynamic type assignment). So you need to sub-class types. Which then doesn't work with hypothesis, currently.
This should be mentioned in the docs, at least.

I was able to workaround this by manually calling pydantic.types._registered() for my sub-types, like:
class Str1(StrictStr):
    min_length = 1

pydantic.types._registered(Str1)

Alternative would be to register them via a decorator of a metaclass, but nah, this is simplest to begin with.

I'm seeing the same issue with conlist. Hypothesis is unaware of the min/max length.

A year later, can we have an update on this ?
Is this going to be solved ? Or should we go with the workaround ?
I think it's a critical feature to be developed

Still blocked on https://github.com/cython/cython/issues/3537

Still blocked on cython/cython#3537

Looks like that is fixed now, or?

Still blocked on cython/cython#3537

Looks like that is fixed now, or?

Unfortunately while the fix has been merged, it still hasn't been released yet and therefore doesn't help us.  This is definitely one of the design considerations for Pydantic v2, but I think probably can't be fixed before then 😥

We’re no longer actively developing Pydantic V1 (although it will continue to receive security fixes for the next year or so), so we’re closing issues solely related to V1. If you really think this shouldn’t be closed, please comment or create a new issue 🚀.


Please Sign the Godot release executables for Windows

I have multiple Whitelist softwares running and all of them try to contain or block Godot.
Then I noticed that Godot executables are not signed.
Now a days even small FOSS devs seem to be able to get certificates for signing.
I don't know the disadvantages of signing. Other than certificate being stolen. (A hardware wallet with encryption is good I guess)
Do other people think signing is a good idea? Please reply.
If we need the same for Linux we could use PGP.
Maybe PGP in addition or instead of normal signatures in Windows.

@Zireael07
Then atleast PGP signing?

Duplicate of https://github.com/godotengine/godot/issues/11984.
Unfortunately, GPG signatures won't prevent Windows SmartScreen from blocking those executables since Microsoft only recognizes its own code signing system.

@Calinou But since it is free it will be good at least for Linux users and users who are paranoid and check for GPG signature.
Morever even hashes are not shown in the website IIRC.

Show hashes like Sha256.
Maybe PGP sign if possible.
The concern I was having about this was that the signature can be stolen and USB hardware has to be used which might be a hassle, but then I realized if the PC of the person compiling software is compromized, the Godot executables are gonna backdoored too.

Adding SHA-256 hashes could be done, please open an issue on the godot-website repository about that.


Mixin doesn't generate slash for self closing tags

I prepared 2 branches:

works with pure-pug self-closing-outer-mixin-pure-pug
doesn't work with pug-plugin self-closing-outer-mixin

I use doctype html5 to pug adds me slash for self closing tags.
2 test cases:

works - when I use markup without mixin output generates slash for self closing tags
doesn't work - when I use markup inside any mixin (mixin is placed inside/outside of files) output doesn't generate slash for self closing tags: source, img, link, etc

Actual:
<link rel="stylesheet" href="/styles.css">
<source srcset="/assets/img/image.png" type="image/png">

Expected:
<link rel="stylesheet" href="/styles.css"/>
<source srcset="/assets/img/image.png" type="image/png"/>

Quick fix: add slash at the end of pug tag - img(src="..")/
Input
mixin my-picture
  picture
    source(
      srcset=require(`/assets/img/image.png`)
      type='image/png'
    )
    img(
      src=require(`/assets/img/image.jpeg`)
      alt=''
    )

doctype html5
html
  body
    h2 picture + img - mixin
    h3 doesn't work
    +my-picture

~Output
    <picture>
      <source srcset="/assets/img/image.0acbc4558e7b27c288531b5c4f5971c7-737w.png" type="image/png">

@silveoj
I have checked your self-closing-outer-mixin repo.
All works fine exact as you wish, if you change the index.pug:
doctype html5 <-- add exact `html5` for self closing tags with '/' at end.
html <-- add html tag as ROOT tag for `head` and `body`
  head
  ...
  body
  ...

Build dist
npm run build:prod

Generated dist/index.html
<!DOCTYPE html5>

    <link rel="stylesheet" href="/assets/css/styles.fc84a125.css" />

    Index
    <picture>
      <source type="image/webp" />
    </picture>

Note: to generate formatted HTML, add to PugPlugin the pretty: true option.

@silveoj why you need legacy XHTML syntax with / for self-closing tags? Today it is not recommended to use.
W3C recommend to use the <!DOCTYPE html>, which is without / for self-closing tags, e.g.: .

@silveoj
yes, I can reproduce the issue with missing />, using mixin.

@silveoj
I found the problem!
In the original pugjs/pug-loader the default value of the doctype option is html.
doctype: query.doctype || "html",

But, in the pug-cli, the default doctype is undefined.
It means, that if you want use custom doctype in Pug, then must be defined the pug-loader option doctype too.
Here is the dilemma:

in my Pug loader set default doctype as undefined. It's BREAKING CHANGE and will be not compatible with original pug-loader. I prefer to keep compatibility.
stay as by original pug-loader. Then you must define the doctype option by pug-loader self.

Working solution
Pug template:
mixin img
  img(src='image1.png')

doctype html5
html
  body
    +img
    img(src='image2.png')

Webpack config:
const PugPlugin = require('pug-plugin');
module.exports = {
 // ...
  module: {
    rules: [
      {
        test: /\.pug$/,
        loader: PugPlugin.loader,
        options: {
          doctype: 'html5', // <-- add this option
        },
      },
    ],
  },
};

Will be generate:
<!DOCTYPE html5>


multiline editing!

Hi thank you for this great editor, I like it so much and using it for my PhD project.
I would like to ask if multiline editing is possible in spyder? I searched online but could find anything related to the topic
Thanks in advance.

We are currently working on this and this should be available in Sypder 4. Please see https://github.com/spyder-ide/spyder/issues/2112 for more info on this topic.

Closing as duplicate of https://github.com/spyder-ide/spyder/issues/2112

2022 how it's going with multiline editing?


infra: re-check travis windows container

and disable AppVeyor, which got stuck since vscode 1.47

still has the error about missing dll files


ci: add Node.js v23

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request?
CI

What changes did you make? (Give an overview)
Add Node.js v23 environment
Related Issues
No
Is there anything you'd like reviewers to focus on?
No

LGTM, thanks! But there are other checks failing. We should fix those problems first I think.

In local I am not getting errors. I check in the node v20 and 22.

In local I am not getting errors. I check in the node v20 and 22.

I am getting errors locally after deleting node_modules and running npm install again and then npm run build.

ya, I am also getting errors after deleting and installing node_modules.

@fasttime @nzakas Done!


Fixed broken link to "Hugo Nested Replies" article in README

Duplicate of https://github.com/eduardoboucas/staticman/pull/261


Pulling media files from server with 1gb of RAM fails through direct API call or export generation

Attempting to export submissions for https://test.central.getodk.org/#/projects/188/forms/all-widgets/submissions produces a 45byte, corrupt zip (presumably empty).

[x] verify that published form definition works in Collect
[x] look at resource utilization when request being handled -- memory usage from node and postgres go up
[x] download submissions with Briefcase to see whether there are any media attachments -- yes and biggest is 17mb.
[x] try the same form definition with fewer submissions -- works fine without media
[x] look at DO's memory usage -- doesn't seem to have gone above 80% in last 14 days?!
[x] try with text submissions plus the one with the largest attachment -- works fine
[ ] explore whether the issue is related to a threshold of total media files across submissions or aggregate size of media files for a single submission - Same form, I get failures when pulling from Briefcase using the submission attachments endpoint with 1gb of RAM. The CPU also spikes when attachments are requested. Once I add swap and do the original export, 400mb of swap gets used. The resulting zip is 115mb.

Possible actions:

[ ] Always recommend swap when using a machine with 1GB of RAM
[ ] Add troubleshooting section that recommends adding memory or as a second option, adding swap

Possibly related service log though I don't see it happening with every failed request:
service               |
service               | <--- Last few GCs --->
service               | ma[458:0x3482490]   243418 ms: Mark-sweep 31.7 (36.5) -> 31.7 (36.5) MB, 27.9 / 0.0 ms  (+ 0.1 ms in 2 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 114 ms) (average mu = 0.872, current mu = 0.858) finalize incremental m[458:0x3482490]   243584 ms: Mark-sweep 31.7 (36.5) -> 31.7 (36.5) MB, 18.1 / 0.0 ms  (+ 0.1 ms in 2 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 82 ms) (average mu = 0.880, current mu = 0.890) finalize incremental ma
service               |
service               | <--- JS stacktrace --->
service               |
service               | ==== JS stack trace =========================================
service               |
service               |     0: ExitFrame [pc: 0x13162b9]
service               | Security context: 0x09e716040911 <JSObject>
service               |     1: fromString(aka fromString) [0x3e3bbccf34e9] [buffer.js:327] [bytecode=0x2d63ab9768a1 offset=151](this=0x2d47e73c04d1 <undefined>,0x286e43202f41 <Very long string[29575502]>,0x168ea14a8b89 <String[#3]: hex>)
service               |     2: from [0x1eac040b7c89] [buffer.js:198] [bytecode=0x27cf830aadf1 offset=11](this=0x3e3bbccc4a51 <JSFunction Buffer (sfi = 0x1eac0409edd1)>,0x286e4...
service               |
service               |     at processTicksAndRejections (internal/process/task_queues.js:85:5)FATAL ERROR: NewArray Allocation failed - process out of memory
service               |  1: 0x9aedf0 node::Abort() [/usr/local/bin/node]
service               |  2: 0x9aff86 node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
service               |  3: 0xb078ce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
service               |  4: 0xb07c49 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
service               |  5: 0xb07d3b  [/usr/local/bin/node]
service               |  6: 0xb2b3b6 v8::String::Value::Value(v8::Isolate*, v8::Local<v8::Value>) [/usr/local/bin/node]
service               |  7: 0xa652a3 node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Local<v8::Value>, node::encoding, int*) [/usr/local/bin/node]
service               |  8: 0x994571 node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) [/usr/local/bin/node]
service               |  9: 0x99480b  [/usr/local/bin/node]
service               | 10: 0xb8df76  [/usr/local/bin/node]
service               | 11: 0xb8fe97 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
service               | 12: 0x13162b9  [/usr/local/bin/node]

yes, that's correct: the root table is the first stream inserted into the zip so it's the first thing over the wire.

it's the first thing over the wire

And so everything else for the export including all media has to fit in memory?

no. there is backpressure, managed by node stream internals.

On Oct 10, 2020, at 12:48, Hélène Martin<EMAIL_ADDRESS>wrote:

it's the first thing over the wire
And so everything else for the export including all media has to fit in memory?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Does this mean that the root table must be /started/ for the zip to start being delivered but in principle, media files should be inserted as they are processed? Right now it seems like there's a threshhold of total media file size beyond which the server crashes and nothing ever gets sent.

solutions here are imprecise. i can only limit my results from the database by number of rows, not total size in the stream buffer. so when we get blobs to stream i set it to a number that is not likely to ever run out of memory given the number of entries (i think it's like 4 or 8 or something pretty tiny), but it can still happen.
either way, it is not true that the media attachments all sit around in node memory. that's what the backpressure's for. the small number of blobs should just sit until the main data is done processing, then the rest of the blobs come in. it just apparently isn't good enough.

once we insert streams into the archives they are there in that order. we can't "insert" media files midway.

I did another trial with ~1.5mb images. The export RAM utilization was roughly the same between 1000 and 2000 submissions. When the download starts, there's a spike of about 400mb in memory usage (same as with original scenario) and then that holds steady. In htop, see 8 processes with each roughly the same RAM usage. Seems that's the 8 rows @issa was talking about and I think it's all seeming consistent and explainable. I'm surprised that each row requires so much RAM but for most contexts it shouldn't matter.
One thing I'm not clear on is whether each attachment does need to be able to be held entirely in memory. That is, if there's one 500mb attachment, will the process handling it need 500+mb of memory? I vaguely remember someone saying they couldn't export because their audit file got really big but I'm not immediately finding it. Do you know, @issa-tseng? This is also something I could try if we'd rather see how it looks for real.

We recently found out that we were affected by https://github.com/brianc/node-postgres/issues/2240 which has a big effect on media performance. I haven't verified these exact scenarios with the patch but given what I have tried I'm pretty sure that the behavior is much better now.


Add missing discord endpoints

Added endpoints for fetching:

discord channel messages
discord guild channels
discord user guilds
discord guilds for discord workers.

closes #81

Hey, tried like an hour to make it work and having issues with all discord endpoints. If you can share a successful run of each it would suffice to me.
Also, validators were slower on this branch than main, something to have in mind 👀


Add tagged union benchmarks

No idea why codspeed claims there were performance regressions, I only added benchmarks?

Hey @adriangb , @samuelcolvin
I had a thorough look at the execution profiles. It seems the variability comes from mimalloc. In the base run of this branch, the benches weren't calling the _mi_clock_now function while it seems they are calling it now.
https://github.com/microsoft/mimalloc/blob/8d6a9df7521181afc276d94b3a6ef2a9dd60bd06/src/stats.c#L420-L428
This seems to have something to do with the order of the benches. Maybe some allocations are done and reused in later benchmarks? Do you think it makes sense?
Normally, the diff of the sub-costs should be visible in the UI when we will display the callgraph(it's coming very soon for Python but will require Cpython 3.12).

Seems weird to me that, if it was explained by OnceCell etc., that adding benchmarks would make others slower. I would think it would just make them faster, but maybe if it reordered them it could explain something?

I can confirm that the issue is from the allocator. I tested  test_core_str from #655 and using the default allocator there is no performance difference. And in fact the default allocator performs a couple percent better than MiMalloc (for this benchmark at least). IMO it seems to me like we over optimized by messing with the allocator and are paying a price at least in terms of engineering time now. I suspect this is also what was going on with https://github.com/pydantic/pydantic-core/pull/602 (cc @davidhewitt on that because we spent some time looking at the compiled code to see if we could figure out what was happening).

@art049 we're interested in maybe running benchmarks both with and without MiMalloc. Is there any way to do two runs and combine with with CodSpeed?


feat: Force workspaces removal after deleting target

Pull Request Title
Description
This feature enables automatic deletion of all workspaces within the target upon target removal.

[ ] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
This PR addresses issue #423
/claim #576

@Tpuljak I reopened the PR after realizing the commit message was wrong

@mobley-trent if your PR is ready for review, please mark it as such.
Moreover, please let me know how to test your changes.
Lastly, you referenced the right issue in the This PR addresses issue description line, but submitted a bounty claim to the wrong, unrelated issue.

One last thing, it's okay to edit PRs, there's no need to close and reopen every time you need to make a minor change. Anything in the PR can be edited. This makes it easier for us to review and doesn't bloat issue references.

You can test it out by deleting a dummy target with workspaces initialized within it.

One last thing, it's okay to edit PRs, there's no need to close and reopen every time you need to make a minor change. Anything in the PR can be edited. This makes it easier for us to review and doesn't bloat issue references.

Sorry, I took the one commit per message instruction too seriously then.

Lastly, you referenced the right issue in the This PR addresses issue description line, but submitted a bounty claim to the wrong, unrelated, issue.

That is the issue related to the bounty

Sorry, I took the one commit per PR instruction too seriously then.

That one commit can be edited with git commit --amend if you want to change it before submitting the PR for review. After you get a review, you should push new commits that we will then squash when merging so one commit will be merged to main.

That is the issue related to the bounty

I don't understand, you are solving issue #423 which has a bounty posted on Opire. You can not claim a bounty on #576 because this PR does not address that issue.

/claim #423

Hi @mobley-trent, unfortunately you cannot use the Opire commands in this project since the opire bot is not installed (you can see that the bot has not answered you). It is important to read the reward message to avoid misunderstandings.
To claim the reward you can do so from the opire website by entering the programmer dashboard. Sorry for the inconvenience 🙏🏻

The user @mobley-trent has claimed all the rewards in #423 👀 We've notified the reward creators here.
@mobley-trent make sure you have your payment account ready to receive the payment for your hard work 💪

Will this suffice to claim the bounty on #423 @Tpuljak @idagelic ?

Will this suffice to claim the bounty on #423 @Tpuljak @idagelic ?

From what I can see in https://github.com/daytonaio/daytona/issues/423#issuecomment-2129349994 you can claim the bounty yourself.


iOS build failing with develop branch

For iOS I am not able to build the app with the develop branch
"react-native": "0.63.3"
"@voxeet/react-native-voxeet-conferencekit": "git://github.com/voxeet/voxeet-uxkit-reactnative.git#develop"
"@voxeet/react-native-voxeet-firebase": "^2.0.2"

Did you properly installed the pods ?

Yes, I also tried after reinstalling the pods

@codlab Recently i was facing issues with few pods of low deployment target so I added this in podfile
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
end
end
end
This changes the deployment target for all pods. What should be the target for voxeet ? I will set that and will try with that version.

@codlab The build is failing with the develop branch, once i reinstalled with master branch it worked fine and the build was successful

Make sure to be using Xcode Version 12.5 (12E262)

@codlab The build is failing with the develop branch, once i reinstalled with master branch it worked fine and the build was successful

I`ve same problem
Can you put your pod File?
What do you believe may have been the problem?

You can find its content here : https://github.com/voxeet/voxeet-uxkit-reactnative-testapp/blob/master/ios/Podfile
Notice the lock file as well at https://github.com/voxeet/voxeet-uxkit-reactnative-testapp/blob/master/ios/Podfile.lock
make sure that when you installed the latest develop commit (or for the future, the latest release which will have all these), you upgraded the local pods repository

My Xcode version is 12.3 can that be an issue ?
I will upgrade it today and then try with your podfile.

I solved problem
I had to update the RN's library, because 21 days ago a patch was released to support for Xcode 12.5 and Swift 5.4.
Or can manually add the lib (https://github.com/voxeet/voxeet-sdk-ios/releases/tag/v3.1.5)

Closing this ticket since it's only related to Xcode + react-native compatibility (hopefully, one day Xcode's tools will have an dev experience as smooth as the gradle integration, until then this kind of issues will arise each time we need to bump our iOS SDK implementation). Please open a new ticket if something else happens


Irrelevant Achievements

Duplicate #485 #487 #488 #491 #493 #497 #498 #500 #504 #513 #517 #524 #532 #537 #538 #539 #540 #552 #557 #558 #560 #565 #580 #581 #584 #598 #600

This is really annoying and exists for about few months. Please fix it.

This is really annoying and exists for about few months. Please fix it.

It's actually coming up to over a year being there in the list. I remember reporting this back around Nov last year...


Add information that pyi files are used in runtime when use attach_stub

In this PR I try to clarify that attach_stub impacts not only type checking for IDE but also runtime.
closes #38

Thanks @Czaki!


Create README in english

If you assign me this. I would really like to create a README.md in ENGLISH for pokemodle.

Thanks for supporting @Akash190104 🥇
Would you like to translate the game too?

I would love to. But I need some instructions for that. Like which files would I need to add and where is the original file with Portuguese texts that I need to translate.

@salteadorneo Please review the changes. Thank you

@salteadorneo Can you please review this?


Flesh out queue documentation

Add some doc tests for some of the simpler queue API functions.
On my machine, the is_timeout test fails for now (#15), and if you like I can make it no_run.
As is, maybe it's useful as an indicator that timeouts aren't supported?
Thank you :smile:

Technically you could test is_timeout by just setting the user_data of a nop to LIBURING_UDATA_TIMEOUT without actually running a timeout.
In fact you can test this method without even doing IO, by just creating a CQE and setting the user_data field. Not sure what our policy on that should be. Setting up new IoUring instances for every doctest is going to have some impact on test speed, though its probably not important.

That is a nice workaround, I will replace it with something like this:
let mut ring = IoUring::new(2)?;
let mut sqe = ring.next_sqe().unwrap();

// make a fake timeout with a nop for testing
unsafe { sqe.prep_nop(); }
ring.submit_sqes()?;

let mut cq_event;
cq_event = ring.wait_for_cqe()?;
cq_event.raw_mut().user_data = sys::LIBURING_UDATA_TIMEOUT;
assert!(cq_event.is_timeout());
Ok(())

but edited to show up like
cq_event = ring.wait_for_cqe()?;
assert!(cq_event.is_timeout());

If I set the sqe's user data before submission, the test appears to hang on this machine without timeout support.

Setting up new IoUring instances for every doctest is going to have some impact on test speed, though its probably not important.

I can't help myself, doctests are my favourite. Please let me know if you think I've gone overboard with them, now or in the future. I will try to limit their memory usage to the minimum required to run the test or demo the API.
I will also rebase these commits after #18 lands.

I can't help myself, doctests are my favourite. Please let me know if you think I've gone overboard with them, now or in the future. I will try to limit their memory usage to the minimum required to run the test or demo the API.

Not at all! If doing IO in every doctest becomes a problem, we will just figure out a way to mock the IO in doctests.