About v3 and v4 - Deprecate v3?

          @4lessandrodev Before starting, please feel free to reach out to me for any improvement requests.

And once again, a huge thank you for your work and for this library, truly! I use it in many projects and on a daily basis.
Here are some ideas for improvements and greater clarity.
Dependency Management
So, I don’t know exactly how Lerna works (I’m a user of Turbo created by Vercel), but for example, with Turbo, you have two strategies for managing dependencies:

Either you assume that all your packages can access your dependency (in this case, rich-domain), so you just need to add the dependency in the root package.json (and not in the individual package.json files of the packages).
Or the dependency is used only by one package (or 2 or 3, but not all packages), in which case, you should add the dependency only in the package.json of the specific package (and not in the global package.json of the repository).

For version 4, I noticed that all your packages contain rich-domain except the logger package. If you were using Turbo, it would be wise to remove the rich-domain dependency from the packages and keep it in the root package.json of the repository.
Even if logger could technically use rich-domain (which wouldn’t make sense), it won’t affect the build or the size of this package's build.
I don’t know if Lerna adopts the same strategies as Turbo, but if it does, I would advise keeping the dependency only in the root package.json, which will make version upgrades easier instead of having to change every package.json.
Managing v3 and v4
If v3 and v4 offer the same features and it’s just a matter of restructuring the repository into packages, then it might be wise to consider deprecating types-ddd and communicating the migration to @type-ddd/core, to stop maintaining both versions. If necessary, you could provide documentation for migrating from v3 (types-ddd) to v4 (@type-ddd/core).
Example App Based on types-ddd and @type-ddd/core
I’m not sure if it would be beneficial to consolidate your example repositories (finance-project-ddd, simple-ddd-app-example, ddd-app, ddd-demo-youtube) into an examples folder in your repository or to add links to all these repositories in your documentation (currently, only the link to ddd-app is there).
Because from my own experience, I had to look through your GitHub profile to find the examples and see how each mechanism of your library works in different contexts (especially to implement a Domain Events system with Redis Queue or SQS in my use case).
What do you think about that?
Originally posted by @GaetanCottrez in https://github.com/4lessandrodev/type-ddd/issues/444#issuecomment-2367596702

@GaetanCottrez Thank you for your suggestions.
Comparison between Lerna and Turbo
Both Lerna and Turbo are tools used to manage monorepositories, but they have different approaches. Lerna is widely used to manage multiple npm packages within a single repository, facilitating versioning and individual publishing of each package. Turbo, created by Vercel, focuses on speeding up builds and sharing cache, optimizing the workflow in monorepos.
rich-domain Dependency in Each Subpackage
The presence of the rich-domain library in each subpackage is intentional because each subpackage can be installed individually. For example, when you run npm install @type-ddd/email, the installation will consider only the dependencies present in the package.json of the email package since it is published separately. This ensures that each package has all the necessary dependencies to function autonomously, without relying on the root package.json of the repository.

@GaetanCottrez I thought of an action plan with next steps

Migrate the Repository to a GitHub Organization

[ ] Create a new GitHub organization with a name relevant to the project.
[ ] Transfer the current repository to the new organization.
[ ] Update all links and references to the old repository in documentation and examples.

Deprecate Version 3 (types-ddd)

[ ] Mark version 3 as deprecated in the repository and in package registries (npm).
[ ] Add clear warnings in the documentation indicating that v3 is deprecated.
[ ] Communicate the deprecation to users through announcements in the README, issues, and other communication channels.

Create Migration Documentation

[ ] Develop a detailed migration guide from v3 to v4.
[ ] Include step-by-step instructions, code examples, and highlight changes in the API or usage.
[ ] Make the documentation available in the repository and any associated official website.

Encourage Users to Migrate to Version 4 (@type-ddd/core)

[ ] Highlight the benefits and improvements of v4 compared to v3.
[ ] Announce the new version and the deprecation of the old one in blogs, newsletters, and social media.
[ ] Offer community support during the migration process through issues, forums, or chats.

Consolidate and Update Example Repositories

[ ] Gather existing example repositories into an examples folder in the main repository or add links to all of them in the documentation.
[ ] Ensure all examples are updated to reflect the changes in v4.
[ ] Facilitate access to the examples so that users can better understand how to use the new version in different contexts.

Focus on Version 4

[ ] Direct development and maintenance efforts solely toward v4.
[ ] Monitor user feedback to identify areas for improvement.
[ ] Plan future updates and features based on community needs.

@4lessandrodev This is a wonderful action plan!
If the community can help you with certain tasks, let us know ;-).
I would be delighted to contribute towards this transition.

#486


[review] describe library as C++11, add mentions for later standards where applicable

from http://lists.boost.org/Archives/boost/2017/04/234234.php

Awesome job, I love the matrix.

You may want to cover future compiler versions where everything works by saying something like "Clang >= 4.0.0". Otherwise you'll have to revise these tables every time a new supported compiler is released, which may be a lot of work (and will end up with very large matrices).

@ldionne I considered this, but I think this would be misleading. I am only comfortable listing compilers that I have tested. While I have made every effort to future-proof the code using feature detection macros, compiler regressions are possible.

Fair enough!


Empty position is advertised

As observed on the cluster state
"value": "{\"01HQ1W3SMARYQ3P0MQ7ZMTYR7R\":\"~00000000000000096443\",\"01HQ1XAM5PDP0DC82B23J632AX\":\"\",\"01HQ1XNTDCTM51CXH7D7D3NXQN\":\"~00000000000000005112\",\"01HQ1XZPPEGWF36XD1W34B3GD7\":\"~\",\"01HQ1Y9X75YDTHWGHG4W85KQVH\":\"~00000000000000209501\",\"01HQ214G8ZNKEDPDJP7XMCJTW1\":\"\",\"01HQ21FVS46GTAY0JK8XFS7RFM\":\"\",\"01HQ21GVJHDVCC42S33GJKC8CK\":\"\"}",

note the \"01HQ21GVJHDVCC42S33GJKC8CK\":\"\"
This prevents any truncation on the WAL of the associated ingester

This is actually normal. That's how we express Beginning


[Feature Request] Advanced Molecular Assemblers

That would be good to have Advanced Molecular Assemblers which have an inventory for 5+ crafts and maybe more slots for Acceleration Cards. Issue with AE2 ones is you have that massive space consuming 'flowers'  which are needed for some recipes. So my suggestion is to make 5 (I always connect 5 to every ME Interface, some may be used for more ME Interfaces - depending on how much free space do I have) of them into one, maybe with only one 'interface' side - to make sure people won't connect more than one ME Interface to them.
Also another small problem is Assemblers are showing crafted item inside the block. It is unnecessary, and may require some rendering power. Possible solution - make opaque and non-opaque versions?
Sorry about my poor English.

I like the current system in AE, it's versatile - you can do flowers, you can put them in grid patterns, etc. depending on your needs and available space and resources.
I don't think this is something that needs changing.


Bad performance of MIB datasets reading

Processing time for MIB dataset (8 GB, path="/cachedata/users/ruzaeva/34/01_ms1_10K.mib"), which is not split into small datasets, takes too long.
The reason is, probably, that data is not divided into partitions.

Thanks for the report! Yes, this needs to change, and can be implemented similarly to the FRMS6 DataSet implementation. As there are actually quite some similarities between readers, this may be considered part of #252.

This is now done in the ds-refactor branch, and will be merged soon.


Not working in Sketch 3.4.3 and 3.4.2

Hi!
I'm using Sketch 3.4.3 and OS X 10.10.5. Unfortunately, the plugin didn't even install (from Toolbox):

And it never appears in the plugin folder:

Could you please help me?
Thanks!)

@asyla
Sorry, I changed my plugin name. That's why you cannot install the plugin from Sketch Toolbox.
Fortunately, Sketch Toolbox owner accepted PR to change my plugin name, so you can do that now!
Please install Material Design Color Palette, it's new,  not Material Design Color Palette Sketch Plugin.

Great, thank you so much! It really works now)


Add support for 'named tensors'

Title says it all.
See: https://pytorch.org/docs/stable/named_tensor.html?highlight=named tensors

@MovGP0 -- this is in response to your issue #568. If you have a change to take a look, that would be great.

WIP NAMED TENSORS
Creating named tensors

[ ] torch.empty()

[ ] torch.rand()

[ ] torch.randn()

[ ] torch.ones()

[ ] torch.tensor()

[ ] torch.zeros()

Named dimensions

FYI: TorchScript Support for Named Tensors
Other supported (and unsupported) features

[ ] JIT support; (Not Yet, perhaps in 1.3)


Colons in filenames cause problems in Windows

As in, the file won't be created when git cloning the repo.

You need to update package.js too.


Add possiblity to react on RxBle#Radio: FINISHED

I'd like to react in my app when RxBle#Radio: FINISHED happened - because for example I'd like to inform my UI when device actually finshed disconnecting.
Now, I believe, I can only unsubscribe from subscription on RxBleDevice#establishConnection and I don't know what happened later.

Hey,
you can use RxBleDevice#getConnectionState() to get detailed information about the lifecycle.

I was using it but I was unsubscribing from subscription on RxBleDevice#establishConnection just after I disconnect (i.e. unsubscribing from subscription on RxBleDevice#establishConnection).
This is why I was not informed by RxBleDevice#getConnectionState().

Anyway on logcat I see:
08-05 11:03:57.336 1736-1736/com.test.app V/XXXConnStateSubscriber: onNext: RxBleConnectionState{DISCONNECTED} thread Thread[main,5,main]
08-05 11:03:57.337 1736-1736/com.test.app D/XXXBleEngine: disconnected on thread Thread[main,5,main]
08-05 11:03:57.338 1736-1736/com.test.app V/XXXBleXX:XX:XX:XX:XX:XX: observeConnectionStateChanges doOnUnsubscribeXX:XX:XX:XX:XX:XX
08-05 11:03:57.339 1736-1736/com.test.app D/RxBle#Radio:   QUEUED RxBleRadioOperationDisconnect(177432340)
08-05 11:03:57.339 1736-1736/com.test.app D/XXXBleEngine: syncWithStorage, onCompleted
08-05 11:03:59.563 1736-1748/com.test.app D/RxBle#BluetoothGatt: onDescriptorWrite descriptor=00002902-0000-1000-8000-00805f9b34fb status=0
08-05 11:03:59.572 1736-1795/com.test.app D/RxBle#Radio: FINISHED RxBleRadioOperationDescriptorWrite(177380646)
08-05 11:03:59.572 1736-1795/com.test.app D/RxBle#Radio:  STARTED RxBleRadioOperationDisconnect(177432340)
08-05 11:03:59.574 1736-1736/com.test.app D/BluetoothManager: getConnectionState()
08-05 11:03:59.574 1736-1736/com.test.app D/BluetoothManager: getConnectedDevices
08-05 11:03:59.580 1736-1736/com.test.app D/BluetoothGatt: cancelOpen() - device: XX:XX:XX:XX:XX:XX
08-05 11:03:59.605 1736-1872/com.test.app D/BluetoothGatt: onClientConnectionState() - status=0 clientIf=5 device=XX:XX:XX:XX:XX:XX
08-05 11:03:59.605 1736-1872/com.test.app D/RxBle#BluetoothGatt: onConnectionStateChange newState=0 status=0
08-05 11:03:59.610 1736-1736/com.test.app D/BluetoothGatt: close()
08-05 11:03:59.610 1736-1736/com.test.app D/BluetoothGatt: unregisterApp() - mClientIf=5
08-05 11:03:59.612 1736-1795/com.test.app D/RxBle#Radio: FINISHED RxBleRadioOperationDisconnect(177432340)

So onNext: RxBleConnectionState{DISCONNECTED} happens more than 2s before RxBle#Radio: FINISHED.

@farmazon3000 I am revisiting this issue and I have an idea.
I do not think it will be possible to react on RxBle#Radio: FINISHED but it should be possible to modify the moment when .observeConnectionStateChanges() will emit RxBleConnectionState.DISCONNECTED (when the RxBleRadioOperationDisconnect would finish).
This change would cause a need for further changes. Things to consider:

At what point the CONNECTING state should be emitted?
I think that it should be emitted right after the subscription to .establishConnection() regardless of the execution of connect operation as this may be a distant operation in the queue and the user would like to know if the library acknowledged the intent.
In the above case what should happen if user would like to establish a new connection after he unsubscribed from the previous .establishConnection() but the disconnect operation did not yet finished?
My opinion is that in this situation emitted sequence would look like: CONNECTING -> CONNECTED -> DISCONNECTING -> CONNECTING.

This is an invite for a discussion on how the feature should look like.
FYI @uKL @Cierpliwy

A few thoughts from me. I think that status should reflect the library state of readiness when the DISCONNECTED is received it should be safe to establish the connection right away.
I think the current implementation is a little bit too optimistic in terms when it is emitted.
The correct logic is implemented within theRxBleGattCallback which reacts on the status from the onConnectionStateChange. It may be a good idea to rework status reporting at all to have one consitent source.

when the user will subscribe to .establishConnection() but there are other queued operations the library changes state for a particular RxBleDevice to CONNECTING even before the actual function BluetoothDevice.connectGatt() will be called.

I don't like this behaviour at all. It is inconsistent with what is actually happening and it is a reason of a lot of edge cases which need to be handled. Every subscription is asynchronous by nature and I don't see any need to immediately apply CONNECTING state when .establishConnection() is called. Does it help with anything? User could do that by himself if he needs it?

Then we could have an opposite situation to:

So onNext: RxBleConnectionState{DISCONNECTED} happens more than 2s before RxBle#Radio: FINISHED.

The onNext: RxBleConnectionState{CONNECTING} could happen long time after the .establishConnection() is subscribed due to RxBleRadio being busy. Maybe it is acceptable and understandable by the user?

For me it would be acceptable, but I would like to hear feedback from other developers.

I think CONNECTING would best be when bleDevice.connectGatt() is called.  If I want to know when the library got the request, I can use doOnSubscribe(), can't I?
For DISCONNECTED, I'd like to get that after the disconnect radio operation finishes.  As noted, after RxBleRadioOperationDisconnect  would be fine.

That is true. Though in some situations the time distance between subscribing to .establishConnection() and emission of CONNECTING may be significant. But I get your point. Maybe someone else would also share their point of view.

Should be available in 1.4.0-SNAPSHOT shortly.


bump up cosign version to v1.0.1

Signed-off-by: Hirokuni-Kitahara1<EMAIL_ADDRESS>
bump up cosign version to v1.0.1
fix return code of each sub command

@hirokuni-kitahara thank you.
@nadgowdas thank you for notifying these fixes in sub command.


Metadata - Different DX

Brainstorm from @dalssoft:
I've been thinking about the developer experience when dealing with glues. Although it is correct to have a folder and files for each glue (ex: graphQL and REST) from the architecture point of view, it doesn't make it clear the idea of metadata to developers.
Thinking about that I created a different way to specify the metadata:
(1) You would have a folder \infra\meta...
https://user-images.githubusercontent.com/209287/122963117-5e735200-d35c-11eb-996a-4e710618f243.png
(2) Meta for Entities
https://user-images.githubusercontent.com/209287/122962983-413e8380-d35c-11eb-99d1-cad70bd9f797.png
(2) Meta for Usecases
https://user-images.githubusercontent.com/209287/122963058-52879000-d35c-11eb-8315-19328a175fd1.png
Different approachs come to my mind but I think this one is the one I like most. What do you think?

Given now we have Herbarium I don't think this issue is relevant any longer.


Add displayName and __ui__ to components

Closes #2915
Description
Set displayName for the @yamada-ui/typography component to make debugging easier.
This change improves the ability to identify the component name in development tools.
Current behavior (updates)
Currently, displayName is not set for the @yamada-ui/typography component, making it difficult to identify the component in debugging tools like React Developer Tools.
New behavior
With displayName set, the @yamada-ui/typography component now displays its name correctly in debugging tools like React Developer Tools, making it easier for developers to identify and debug the component.
Is this a breaking change (Yes/No):
No.
Additional Information
None.

Thanks!


added bounty hunter program doc

still need to do the formatting

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

@adipolak Closing the PR as we decided to move forward with a web landing page instead of docs.


question about get_local_structure_map

hello Keir,
Nice work on ChIRo! we've been exploring its application for the task of protein-ligand affinity prediction at my startup.
I have gotten the model to train and it seems to be working, but I have a question about the way get_local_structure_map is defined. I noticed that it's meant to work on batches of psi_indices. Is there any specific reason why this was done? Would it be possible to define a similar function that just generates the input features LS_map and alpha_indices for one molecule at a time? This is more from an engineering perspective.
https://github.com/keiradams/ChIRo/blob/2686d3a1801db8fb3dec10b61fb0cb0cec047c7c/model/train_functions.py#L22-L37
Thanks!

Hi Min Htoo, sorry for the delayed response! I'm glad you've gotten use out of ChIRo. As per your question, there's no reason why I initially made get_local_structure_map operate on batches of psi_indices apart from convenience. Note that it was designed to be used with torch_geometric dataloaders, which automatically increment psi_indices by the total number of nodes/atoms in each graph. If applied to one molecule at a time separately, you'd want to ensure that alpha_indices and LS_map are incremented properly (that is, if you plan to batch those individual molecules together).

Got it, thanks!


Key commands should be matched exactly

Currently if you press opt-cmd-B or ctrl-cmd-B it toggles bold, even though the key command is configured for just META+B or CTRL+B, but not both together.

Good catch, the culprit is in findKeyCommands here where we're currently just checking for the defined keys but not checking if any others are pressed.
return (modifier && key.hasModifier(modifier)) || (!modifier && !key.hasAnyModifier());

I think maybe a bitmask for the key modifiers would simplify this? I may take a stab at this later today.


Initial guess 'atom' does not work in PySCF 2.4.0

Hi, I'm running a simple DFT calculation of a CO molecule in PBC. However, if I use 'atom' as the initial guess, the following error occurs:

IndexError: boolean index did not match indexed array along dimension 1; dimension is 28 but corresponding boolean dimension is 14

I'm using PySCF 2.4.0 and Python 3.9.12. Below is my script for the calculation:
from pyscf.pbc import gto, dft, scf, df
from pyscf.pbc.lib import chkfile
import os

cell = gto.Cell()
cell.build(unit = 'angstrom',
           a = [[10.0729742049999995, 0.0, 0.0], [0.0, 8.7234516144000001, 0.0], [0.0, 0.0, 40.0]],
           atom = '''
           C    5.036482    4.360231    7.027104
           O    5.036476    4.360919    8.184654
           ''',
           dimension = 3,
           max_memory = 48000,
           verbose = 5,
           basis='def2-svp',
           precision = 1e-10)

from pyscf.pbc.tools import k2gamma
kpts = cell.make_kpts([1,1,1])
cell, phase = k2gamma.get_phase(cell, kpts)

kmf = dft.RKS(cell).rs_density_fit(auxbasis='def2-svp-ri')
kmf.xc = 'pbe'
kmf.chkfile = 'co.chk'
kmf.init_guess = 'atom'
kmf.kernel()

I've also tested the earlier version (2.0.1) of PySCF, which did not give this error.
Could anyone help to fix this issue? Thanks!

The latest master branch should work.


Is this all as a description of the Customizations property?

This is a very weak topic. First of all the property customizations should start with a capital and then what format needs SimpleCustomization to be? Comma separated string?

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

ID: ee6d69d8-d604-5eb5-c979-b1250cec527e
Version Independent ID: 8bc6b6b0-a0ce-7d40-ae49-742903ce13a8
Content: Customizations Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-customizations-property.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for your feedback, this issue is fixed with the next refresh of the docs.


Change DTS boot partition from FAT32 to EFI System Partition type

The DTS boot partition is standard FAT32, not EFI System Partition type. As a result it cannot be found by ESP scanning in Dasharo firmware.

Moved to dasharo-issues https://github.com/Dasharo/dasharo-issues/issues/692


B #4793: Read monitor address from monitord.conf

Do not merge, although it covers some cases, it's still not complete


'_' and ' ' is not accept by Typefox yang parser, but it is accepted by pyang 1.7.3

We defined a string type with patten.
type string {
pattern '[a-zA-Z0-9-_ ]+';
}
Yang parser with report this pattern is invalid due to '_' and ' '.
But pyang 1.7.3 accept this kind of pattern.
I think that '_' and ' ' is valid

I get Invalid regular expression pattern and I think it is OK, because the '-' after the '9' is not allowed as the '9' is already the right operand of the range '0-9'. Without the '-' after '9' it works nicely. If you want to include the '-' char you have to quote it as '-'. So to me this looks like a missing validation in pyang.
Please don't hesitate to reopen if I missed something.

Hi Jan,
I can understand your explaination. But in our yang module, there are two smiliar types.
type string1 {
pattern '[a-zA-Z0-9-]+';  // Yang Parser accepted
}
type string2 {
pattern '[a-zA-Z0-9-]+'   // Yang Parser report as error;
}
The only difference between the two pattern is one ''.
So here I would like to figure out whether it is the last '-' or the last '_', which trigger the validation error.
Because according to my understanding to your words, the two patterns should be wrong both.

Hi Jan,
I can understand your explaination. But in our yang module, there are two smiliar types.
type string1 {
pattern '[a-zA-Z0-9-]+'; // Yang Parser accepted
}
type string2 {
pattern '[a-zA-Z0-9-_]+' // Yang Parser report as error;
}
The only difference between the two patterns is one '_'.
So here I would like to figure out whether it is the last '-' or the last '_', which trigger the validation error.
Because according to my understanding of your words, the two patterns should be wrong both.
Do I understand correctly?

OK my bad.
I tested with (this online regexp tester)[https://regex101.com/] and it seems to be valid. The minus after a character range seems to be valid even without quoting.
Regexp implementations vary a lot, and it seems that the regexp validator from EMF which we use does not support this. I am switching to Java's built-in Pattern.compile for validation.
https://github.com/theia-ide/yang-lsp/pull/93

Re-reading the spes, YANG uses the XML schema regexp which states that - has to be quoted
https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#nt-charClassEsc
So pyang is wrong here. Closing.

Alright, I get your point. For the second pattern, I think you are right.
But regarding to the first pattern, the last '-' should also be reported as an error, right?
type string1 {
pattern '[a-zA-Z0-9-]+'; // Yang Parser accepted
}
type string2 {
pattern '[a-zA-Z0-9-_]+' // Yang Parser report as error;
}
Actually, my doubt is the two patterns are almost the same (both have incorrect '-' without backslash).
Why one is valid and another is invalid?

It's a bug in the EMF regexp validator we use. It is based on a stale version of Apache Xerces. Switching to a newer version of Xerces https://github.com/theia-ide/yang-lsp/pull/98

Merged PR


Fix nctl upgrade test 6 and 7

This PR fixes two nctl upgrade tests.  The tests both involved having nodes 1 and 10 missing the upgrade (running through it but without the new binary staged) then restarting them after staging their upgrades to ensure they rejoin and sync up.
With the network component now rejecting connections between different protocol versions, the two affected nodes need to have their launchers' state files removed so that on restart the launcher runs the highest binary.
Closes #3619.

bors merge


Use Reflection.Emit for object invocation.

This will give us a huge performance boost.
Using what we've learned in #36, we should not send callbacks to the native world.
Instead, every NetMethodInfo and NetPropertyInfo will have a unit long Id. This id will be used to lookup cached dynamic methods that perform as little as possible.
For example:
public void Invoke(IntPtr t, IntPtr m, IntPtr p, IntPtr r)
{
    using (var method = new NetMethodInfo(m))
    using (var target = new NetReference(t))
    using (var parameters = new NetVariantList(p))
    using (var result = r != IntPtr.Zero ? new NetVariant(r) : null)
    {
        // This will be dynamically compiled!
        ((SomeClass) target.Instance).WithMethodWithStringIntParameters(parameters.Get(0).String, parameters.Get(1).Int);
    }
}

The same thing can be done with property reading/setting.

Just in case you're interested:
With Refit, it allows you to define an interface and add attributes to it, and then Refit generates the meat of the code (either using a standalone app or an msbuild task).
Refit does this by scanning the source files using Roslyn, and then generating output files (again using roslyn/template files).
https://github.com/reactiveui/refit/blob/master/InterfaceStubGenerator.Core/InterfaceStubGenerator.cs

Oh, wow! I was wondering how they supported Xamarin where it does AOT compilation. Turns out, they aren't using Reflection.Emit!
I haven't thought about an approach like this. I'm not sure how it would look in Qml.Net.

Absolutely. Figured I'd at least mention it just in case it's applicable :). And would work with AOT restrictions on mobile platforms if/when you got there.


Feature new homepage

Fixes #237
@jvillarejo @faloi @aguspina @PalumboN Please and/or make changes to this PR
This is how it looks like

Alternatively, this is how it would look if navbar was removed:

+1 to the navbar
The "red" button doesn't convince me, I think the previous version was better

I like this new style... but im not sure of the button color. I think the previous one was better.
+1 to the navbar too.
the description section seems like a mess to me. Maybe if all paragraphs was alligned to the left, i don't know. .I'll think a way to make it better.

@aguspina @faloi please propose changes or add commits to this PR as soon as possible. I would like to apply suggested changes and merge it before weekend.

The problem with the dark blue button is that it does not get attention. Actually, it worked, since you all get focused on it :stuck_out_tongue:
Perhaps we could find a better color later.


Feature request: Relative entityHttpResourceUrls

This issue is for a: (mark with an x)
- [] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Versions

1.0.0-beta.2

First of all thanks for a great lib! It really helps reducing all the boilerplate.
I have noticed that the root config is not respected if you specify entityHttpResourceUrls for an entity.
I would like to specify root url e.g. https://www.backend.com and then specify relative entityHttpResourceUrls e.g. api/user.
Now I have to specify full url which is not very convenient.

Please propose the exact API and rules that you'd like to see. Perhaps a PR would clarify?

Closing as this issue is old and I haven't heard from you.


Instagram app won't open iOS 9.3.3

Sharing to Instagram doesn't seem to work...
This line:
window.plugins.socialsharing.canShareVia("instagram", "message", null, null, null, instagramSuccessCallback, instagramErrorCallback)

returns success.
However this line:
window.plugins.socialsharing.shareViaInstagram(message, fileOrFileArray, successCallback, errorCallback)

opens the list of apps as expected. Instagram is one of them. When I tap the Instagram icon... Nothing happens.
I have instagram included in my LSApplicationQueriesSchemes. And I see it in my generated plist file.
Any ideas why this would be happening?

More Clues:
Other apps in the list open fine like Notes, Pinterest, Google Drive.... They display an instagram.igo object. Not sure what that is. I added to instagram.igo to the LSApplicationQueriesSchemes and NSAppTransportSecurity to see if that did anything: nothing.
Also the successCallback on the shareViaInstagram is getting called with a null result passed to it.

More Clues:
Everything is working fine when I point the app to my staging environment on heroku. Which is awesome. However, shareViaEmail and shareViaInstagram do not work when I point my app to my local server via a local tunnel (ngrok). It used to work fine... ngrok domains are properly whitelisted...

Did you ever get to the bottom of this?  I'm bumping up against the same problem.

@erikcw no I didn't. :( I have been testing this on staging and production... It's not that big of a deal that it doesn't work through a local tunnel. There is a lot that doesn't work that way. I use local tunnels for specific debugging only.

In my case -- it won't even work from my staging server (also heroku).
The share-sheet is displayed, but nothing happens after tapping instagram.  The instagram share-sheet extension does work from the Photos app though, so it's not entirely broken.

Have anyone found a solution to this? I'm going through exactly same problem, and it's pretty frustrating...
Thanks.


Make error with 'gemm.cpp'

Thanks for the feedback.  That symbol should be the last few releases of rocBLAS so would like to know what version of ROCm or rocBLAS you are building against?   If you download and build a local newer version of rocBLAS which isn't installed you can use it by setting the environment variable:
export ROCBLAS_PATH=/...yourlocalpath.../rocBLAS/build/release/rocblas-install
I'll update the documentation to specify a minimum ROCm  (3.5+).

My rocm is v2.9, so this question is raised by the version of Rocm?

and rocblas is v2.6

Documentation was updated so closing this old task.  The latest master will require rocm and rocblas 4.2 or later for some examples.


Section 5.3.3

CRSum...is this an error?  Where does this come from?

@ayoumans it is a mistake.
@joanma747 At least this sentence needs to be rewritten in my opinion as I cannot make sense of it grammatically:

Specifically, Ordered list of names of the dimensions defined in the CRSum rectangular bounding region surrounding a geometry whose set of points span the value discontinuity in an angular coordinate axis.

The CRSum mistake was introduced by https://github.com/opengeospatial/2D-Tile-Matrix-Set/commit/b0b6cbeea61291c379f5e4a918368287979c396b#diff-0add2601d8308c9591e3a5cf929e41a16c4e9c1d7916e8888e7eea9aa49c8815L124
The sentence starts with specifically, but I have no idea what this specifically refers to?
It talks about Ordered list of names, but that seems unrelated to the rest of the sentence.
This paragraph and the next seems to be talking about intricacies with angular units and some kind of projections near the poles when specifying the bounding box of the TileMatrixSet, but I am not clear on why that bounding box would not be a minimum rectangular bounding region?
Perhaps with version 2 which has a separate bounding box for the TileSet this is no longer relevant, since the bounding box here is not about the data, but about the definitions of the tile matrix set itself?

Thanks for spotting the mistake and when the mistake was produced.
It is clear to me that this was some wrong editorial process.
I have rolled the sentence back.


Release 24.2

coverage: 90.579% (+0.02%) from 90.557%
when pulling 9b7a3d5af9e200eb06eabeb8c293fc24a16cab71 on release/24-2
into 88afb1d3dafcd59a39f1d83050bdb1e31ee572cb on main.


Don't try to sudo echo

- What I did
Another try at getting permissions right inside of GitHub Actions

I should only need sudo for the mkdir


Feature: Give option to hide/show elements

Give the option via config to show/hide different elements:

Ends at display
Intention
Start button
+ x min buttons

Depends on #6 so that start/stop can be hidden and app still is usable.

Depends on creating a settings overlay.
Either via #3 or create here and use in #3

Easiest would be a shortcut to toggle all extra elements.
That would toggle between full and compact mode.
Compact mode would be similar to n10 then.


Multiple multiaddrs

How should multiple multiaddr addresses be expressed? (both in string and binary form). There may be a nice way to allow "anything that takes one multiaddr" to take "n multiaddrs".

This is discussed in #20


fix: tolerations in values.yaml for edgemesh helm chart

tolerations are handeled as map[]

/assign @Poorunga

Will update the package once #390 is done, because both modify the helm chart.

@Poorunga rebased this PR on lastest master after #390 and updated edgemesh helm package as well.

/lgtm
/approve


Suggest ----When the wallet is not unlocked, execute “cleos wallet keys” return []

Suggest changes to tips
Error 3120003: Locked wallet Ensure that your wallet is unlocked before using it! Error Details: Wallet is locked: default
Like execution
cleos wallet import

For security reason people should not see the public keys of a locked wallet.


update npm package

I see that currently there is a release v 3.2.0 here on github, however with npm I get only version 3.0.0 installed. Can somebody update the available package for npm?
Thanks!

Is this the official repository on npm?
https://www.npmjs.com/package/swiss-styleguide?activeTab=versions

To me it looks like it is. At least it forwards onto the same guide/example page.

Next Version will be published on NPM
Issue will be closed

When will the next version be published?

@gillerr any update on the release of 4.0? Thank you! 🙂

@kplanz I assume the tickets are not really maintained here on github (See age of this ticket). I would propose you go the internal way via the BIT.


Sequencer is CPU-hungry

I'm noticing that fundsp uses much more processor time (maybe ~5× as much?) if I'm working through a Sequencer. It also seems like the number of active Events is the main factor that determines how much CPU is used rather than the total amount of DSP going on inside the events. (This was all measured from release mode builds.) Is there a fix for this or should I avoid Sequencer if there might be a lot of concurrent voices?

The number of active events will be the main factor as every event concurrently active will double the resources used. Do you mean that if you activate the same number of events using something other than 'sequencer' you are getting a different result?

I'm sorry, I was completely off track here! The component hogging CPU in my use case wasn't even part of fundsp, and the association with Sequencer was a coincidence.


Fixes for stuck builds

Description
Fixes for stuck builds
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Pull request rejected by merge tool. Multiple change entry files found:

Show entries
- changelogs/unreleased/add_get_current_resource_state.yml
- changelogs/unreleased/ensure-agents-do-not-start-when-active-session.yml
- changelogs/unreleased/ensure-agents-improvements.yml
- changelogs/unreleased/fix-move-back-to-available-states.yml
- changelogs/unreleased/fix_resource_details.yml
- changelogs/unreleased/test_fixes.yml

This may happen when a change entry was removed from the remote repository due to a reverted change. In that case, make sure the latest changes from origin/master are merged into issue/buildmaster_hang_fixes before triggering merge bot.

Merged into branches master in f87c5b9a2d373ed5dfdacde6f72ecaed42109f80

Processing #7669.


feat: selectionHandleColor prop on Android

Summary:

This PR addresses the problem raised in the #41004 issue.
The current logic is that selectionColor on iOS sets the color of the selection, handles, and cursor. On Android it looks similar, while it doesn't change the color of the handles if the API level is higher than 27. In addition, on Android there was an option to set the color of the cursor by cursorColor prop, but it didn't work if the selectionCursor was set.
Changelog:

[GENERAL] [ADDED] - Make same behavior of the selectionColor prop on Android as iOS
[ANDROID] [ADDED] - Introduced selectionHandleColor as a separate prop
[ANDROID] [CHANGED] - Allowing cursorColor and selectionHandleColor to override selectionColor on Android
Test Plan:

Manual tests in rn-tester:
selectionColor same as iOS, sets selection, handles and cursor color
There is a way to set only "rectangle" color by setting other props as null

selectionHandleColor

cursorColor

Thanks for contributing!
Having props that overlap require careful handling. If in a state update you change just selectionColor, the previous value set for selectionHandleColor will be overwritten. There's also no guarantee to which order setters are called.
Can you validate that when you change these properties in different order (eg add useState hook to control each individually) that this still works correctly?

Hi @javache,
I've tested this in rn-tester and can confirm that changing in different order works correctly. selectionHandleColor and cursorColor will overwrite selectionColor regardless of the setting order. Below is a short video of this test.
During the testing, I also found incorrect behavior when changing from color to undefined so I uploaded a fix.
https://github.com/facebook/react-native/assets/39670088/544ed0e9-88d5-476f-a1cc-7b0adfb44b58


pathPrefix not working as expected

Description
I first deployed a monorepo including a Gridsome app, using Now, but realised that the assets were trying to load from the root path, which is expected for an app like this: https://now-examples-p1p0qbqf7.now.sh/ (note how there is one directory called gridsome and clicking it shows the content.)
I looked up your documentation and saw that you had a pathPrefix option so I applied that an ended up with the following deployment: https://now-examples-dkzvrgkjw.now.sh/
As you can see with the latter deployment, by clicking on gridsome, there is a generated second gridsome directory, rather than just the assets being loaded from the gridsome directory I had already created.
Note: All deployment URLs shared here have the source publically accessible if you append /_src to the URL.
Steps to reproduce

Generate a Gridsome application in a sub-directory of a project directory, the full steps that I took can be found here: https://github.com/zeit/now-examples/tree/master/gridsome#gridsome
Setup a now.json file in the project's root directory with the following:

{
    "version": 2,
    "name": "now-examples",
    "builds": [
        { "src": "gridsome/package.json", "use": "@now/static-build" },
    ]
}

and add the following script to the gridsome package.json:
"now-build": "yarn build"

Deploy the project with Now and realise that the assets are not correctly pointing to the sub-directory that Gridsome exists in.
Change the Gridsome config to have the following content:

module.exports = {
  pathPrefix: '/gridsome'
  plugins: []
}

Deploy again and get the duplicate directory issue

Expected result
Gridsome should resolve assets to the directory set in the pathPrefix option instead of generating a duplicate directory so that monorepos can contain all Gridsome content in a single sub-directory.
Actual result
Gridsome generated a directory with the name of the pathPrefix settings

I agree that the current behavior of pathPrefix isn't as one would expect. Gridsome should generate files as normal directly under dist, and only prefix URLs for routes and assets. I'll include a fix for this in the next update  :)

@timothyis see comment above from @hjvedvik :point_up:
Have you tested if this works as expected in current version?


ISPN-9373 Update testng to the latest version

When updating to 6.14.3 the following classes started reporting compilation errors:
CustomMarshallerEventIT.java
NamedTestMethod.java
XMLTranscoderTest.java
SpringRemoteCacheManagerFactoryBeanContextTest.java

<disableXmlReport>false</disableXmlReport> and <usedefaultlisteners>false</usedefaultlisteners> We will let PolarionJUnitXMLReporter generate the reports to us. There are projects that contains a mix of Junit and TestNG tests and setting this equals false was generating a third report. The third report is the content of the testNG and the Junit report. Let's say (this is an example) that the junit report contains 10 tests and testNG 20 tests. The third report will be generated with 30 tests. The "Test Result" in Jenkins will show a wrong number of tests. In this case, 60 tests will be reported.

I don't see any major issue with Force use of JUnit, since TestNG+Arquillian break in wonderful ways. I removed those workarounds.

Without the new dependency <artifactId>testng</artifactId> and keeping the plugin <artifactId>surefire-junit47</artifactId> was generating an error before the test phase have been started. In this case, the project will be SUCCESS with 0 tests, 0 failures, 0 errors, 0 skipped.

Jenkinsfile - Using the new version of testNG. The tests now are under a subfolder and start with "TEST-"

PolarionJUnitXMLReporter.java - We delegate the whole process to JUnitReportReporter and kept the custom code that we need that is related to the tests case name.

Utils.writeUtf8File(suite.getOutputDirectory().replaceAll(".Surefire suite", ""),           generateFileName(suite) + ".xml", document.toXML());

The code above is not needed because the new version don't generate folders with space.

@alanfx:
From the commit 3082f7822a8083724b8ab096cdcdbff2606f8aff we got the following results from the log. This build run in DEV-CI.
diego@diego-note:~/Downloads/grep$ ./run.sh consoleText_dev_1.txt
==========FAILURE==========
[ERROR] ScatteredSplitAndMergeTest(org.infinispan.partitionhandling.ScatteredSplitAndMergeTest)  Time elapsed: 0.036 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0.001 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] query.blackbox.ClusteredCacheWithAffinityIndexManagerTxTest(org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTxTest)  Time elapsed: 0.155 s  <<< FAILURE!
[ERROR] query.blackbox.ClusteredCacheWithAffinityIndexManagerTest(org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTest)  Time elapsed: 2.503 s  <<< FAILURE!
[ERROR] query.blackbox.ClusteredCacheWithAffinityIndexManagerTxTest(org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTxTest)  Time elapsed: 5.582 s  <<< FAILURE!
[ERROR] query.blackbox.ClusteredCacheWithAffinityIndexManagerTest(org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTest)  Time elapsed: 0.99 s  <<< FAILURE!
[ERROR] scripting.ScriptingTest(org.infinispan.scripting.ScriptingTest)  Time elapsed: 0.19 s  <<< FAILURE!
[ERROR] client.hotrod.event.ClientClusterFailoverEventsTest(org.infinispan.client.hotrod.event.ClientClusterFailoverEventsTest)  Time elapsed: 0.55 s  <<< FAILURE!
==========FAILURE==========

===========ERROR===========
===========ERROR===========

Tests run: 24542
Failures: 13
Errors: 0
Skipped: 51

From the commit 3082f7822a8083724b8ab096cdcdbff2606f8aff we got the following results from the log. This build run in QE-CI.
==========FAILURE==========
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0.013 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0.026 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0.001 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0 s  <<< FAILURE!
[ERROR] functional.FunctionalListenersTest(org.infinispan.functional.FunctionalListenersTest)  Time elapsed: 0.001 s  <<< FAILURE!
[ERROR] query.blackbox.ClusteredCacheWithAffinityIndexManagerTest(org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTest)  Time elapsed: 0.192 s  <<< FAILURE!
[ERROR] scripting.ScriptingTest(org.infinispan.scripting.ScriptingTest)  Time elapsed: 0.205 s  <<< FAILURE!
==========FAILURE==========

===========ERROR===========
===========ERROR===========

Tests run: 26771
Failures: 8
Errors: 0
Skipped: 135

I was expecting the same "Tests run", "Failures", "Errors" and "Skipped" when running in "Linux". I am closing this PR because more work is needed.


TOMEE-2934 Handle public inner classes when looking for a class in classpath

When trying to start up the ejbContainer EJBContainer.createEJBContainer
If a bean contains an inner class, used like this:
@Asynchronous
	@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
	public Future<Contract> processAsynchronously(Contract r)

Then you get an Exception stating that:
Cannot locate the class {0} from the codebase [{1}]
This attept to handle this case, if it also fails then the original exception is thrown.

Thanks for this PR. Could you fill a JIRA for this: https://issues.apache.org/jira/projects/TOMEE/issues?

Did you identify why the classname didnt have a dollar but a dot? Is it a configuration or scanning issue? It would be better to fix this rather than the consequence (since other code can fall into that issue elsewhere then).

@rmannibucau Of course you are correct and this is definetely not the way to go.
I will close this PR


Generate data in .md (Markdown) table format (Markdown plugin)

Create a Markdown plugin to export tables into Markdown format
    REQUIRE MD;
    SELECT * INTO MD("README.md",{headers:true}) FROM one

I suggest that we as default has headers set to true...


RCTMessageList找不到的问题

My environment:

OS:  win10
react-native version:0.57.0
aurora-imui-react-native version:0.12.3

Invariant Violation: Invariant Violation: requireNativeComponent: "RCTMessageList" was not found in the UIManager.
This error is located at:
in RCTMessageList (at messagelist.android.js:80)
in MessageList (at Chat.js:505)
in RCTView (at View.js:44)
in TestRNIMUI (at SceneView.js:9)
in SceneView (at StackViewLayout.js:574)
in RCTView (at View.js:44)
in AnimatedComponent (at StackViewCard.js:12)
in Card (at createPointerEventsContainer.js:28)
in Container (at StackViewLayout.js:612)
in RCTView (at View.js:44)
in RCTView (at View.js:44)
in StackViewLayout (at withOrientation.js:30)
in withOrientation (at StackView.js:63)
in RCTView (at View.js:44)
in Transitioner (at StackView.js:21)
in StackView (at createNavigator.js:59)
in Navigator (at createKeyboardAwareNavigator.js:11)
in KeyboardAwareNavigator (at createNavigationContainer.js:376)
in NavigationContainer (at App.js:8)
in App (at renderApplication.js:34)
in RCTView (at View.js:44)
in RCTView (at View.js:44)
in AppContainer (at renderApplication.js:33)

@JoshLipan 完全按照安装配置来的，网上查到有些原生组件也出现这个问题，貌似是说新版本就会有这个问题，所以在这里提了个问题。

已找到问题所在，并不是imui本身的问题，是受到其他插件的影响。

@spidersq 我也遇到这样的问题，请问你是怎么解决的？

+1

@spidersq 请问怎么解决的？


Added NJ 2019 States results

I had some issues using sciolyff to validate the data, so can someone maybe please do that for me? I'm pretty sure the data is correct and in the right format, but it would be nice to do it just as a precaution. Thanks!

Also, all of the netlify checks failed. Do I have to add/change other files in addition to adding the new .yaml files?

Thanks for the contribution! No other files need to be added/changed except for the new YAML files.
I had to make some modifications to the files to get them to pass the ScioyFF validator. For future reference, could you review those commits to see what needed to be changed?
Also, what were the specific issues with using the validator? I may be able to help -- the validator is an essential part of making sure the archived data is consistent and error-free.

Thanks for the feedback! I reviewed the changes and I think I understand the things that had to be changed.
Here's a screenshot of my command prompt:

Not sure if I did anything wrong or if there's actually a problem.

Oh, it looks like I used some Ruby 2.6 syntax. I'll update the gem to enforce a minimum Ruby version for now, although it may be wiser in the future for me to refactor that code to be compatible with earlier versions. You can workaround this for now by updating to the latest Ruby version.


[v1.7.x] Backport #17772

Description
Backport #17772 to branch v1.x
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Adding this PR to 1.7.0 roadmap https://github.com/apache/incubator-mxnet/issues/16864.

@mxnet-label-bot add [pr-awaiting-merge]

@ciyongch this PR is ready to be merged

@mseth10 thanks for backport the PR to v1.7.x branch, ping @TaoLv @pengzhao-intel to help merge.

@mseth10 minor typo in the description: It should be v1.7.x instead of v1.x


Create basics_of_stl.cpp

It has basics data structures of STL library.

Great work you can also star my repo🐱🏍


Order By custom field

Hi! First of all thanks for this package! It just makes everything easier! I'm trying to order a custom post type by a custom field, so when I do:
const callback = wp.customType()
            .order('desc')
            .orderby('votes');

I get (sorry the message is in Spanish):
{ code: 'rest_invalid_param',
  message: 'Parámetro(s) no válido(s): orderby',
  data:
   { status: 400,
     params:
      { orderby:
         'orderby no es ninguna de las siguientes author, date, id, include, modified, parent, relevance, slug, include_slugs, title.' } } }

How can I include my votes custom field to do this? Everything else works fine but the orderby
Thanks!

Unfortunately solving this is out-of-scope for this library, as the orderby values supported by the REST API out-of-the-box are intentionally limited. You may add PHP code to your plugin or theme to permit this particular query, see this thread from the original WP-API project repository for more information. I think you'd then want to be passing orderby( 'meta_value' ) if you go that route, however.


add a way to get all installed plugins version

What this PR resolves:
add a way to get all installed plugins version
Changes proposed in this PR:

Add a version property to j.core.state where we can inspect all plugins version

Version:  9.0
Fixes: #14

This change is

Comments from Reviewable


Feature: geocoding search

Let the use have the possibility to look for an address, by using one of the geocoding plugins

Definitely a good addition, I have a use case atm for searching for an address and place a marker.
Is it hard to implement a plugin?

I already did a quick test with leaflet-geosearch. The problem with that one is that it doesn't expose it properly, as it is written in ES6 and build with webpack. Should be a great feature, but first I need to properly get this library working

I got this working: https://github.com/perliedman/leaflet-control-geocoder but I could not get to the mendix specific functions to execute microflow etc..
see attachment
Leaflet_8309b0f7fd97e8dbb217bf76f56993965ad7252c.zip

Does this work in the cloud as well? I doubt it because of the structure of Geocoder

don't know, only tested locally..

Finally added to v2.2.0


'Officially Verified' text in dojo detail adding extra line

Officially Verified adds an extra line in there. I think 'Verified' text would suffice.

after change:

Up to @rosalanghammer if she thinks it would be okay to change this.
One reason not to do this would be because users may not know what "Verified" means. Suggest we add a tooltip (title attribute in html) to explain what verified means, when the user hovers over the tick mark and verified.
We will inevitably have a Dojo with an even longer name at some stage that will push "verified" to the next line in the future anyway.

yea, it only happens on certain length dojo names, it's fine since they all get bumped down anyways.

I would just go for 'Verified' - hopefully due to this mechanism being used on twitter etc. this is recognisable to users. Also no unverified Dojos should be viewable anyway!

Cool, you can change it then if you want @kennanseno


Mongo Support

If this ORM is really meant to be a Game Changer it should support NoSQL DBs like Mongo.
Are there any plans for Mongo?

I don't see drizzle implementing Mongo. It is not a relational database and Drizzle is an ORM for relational databases. Also one of the goals of Drizzle is to do a query with a single database call which would bot be possible with Mongo.

Drizzle ORM will only support SQL databases. Mongo was always out of scope.


Add missing German translations

Hey,
I noticed that there are strings that needed a translation.
Feel free to message me when you add new locales in the future. :)

Oh I see, I didn't knew that! :D


SourceKit-LSP Output the wrong comment format of hover on code.

Description
LSP convert comment of class String to Uninterpretable markdown format.
Steps to reproduce
hover on the symbol names String
Expected behavior
Response normal markdown content to IDE
Screenshot

Environment

Swift compiler version 5.7

After second ``` it must append new line


Not working running zsh?

Hi!
I'm not able to get this to work on my Mac using zsh. The direnv works as expected on the command line, but the env variables are not available from IntelliJ. Any idea why?

I experience the same. It says it was reloaded, but when I run my Spring Boot application, variables are not there. Could someone have a look on this please?


scale mask  ratio

https://github.com/princeton-vl/RAFT-Stereo/blob/f1fa15abd34187d101806f65b813f4d9d6f93ab0/core/update.py#L137.
Is the scale mask ratio 0.25 set because of the downsampling ratio of raft-stereo is 0.25？If the answer is yes, the ratio should be 0.125 for raftstereo-realtime.

This should answer your question: https://github.com/princeton-vl/RAFT/issues/24)](https://github.com/princeton-vl/RAFT/issues/24

Thank you very much！


Pagination broken on Admin Content Management

Describe your problem
No content is displayed when first visiting content Management, until the next/last button is clicked. Then all are displayed.

Steps to reproduce the problem
Add about 10 parent pages or more, each with  about 6  child pages.
Bludit version
V3.9.2.
I would expect it to at least show pages on first pages and break after x pages regardless of parent/child.
I would hope the parent would be repeated as continued on the next page if child pages go onto next page.

Same issue exists in v3.10.0

Hello, with the new version of Bludit v4.0 rc1, I would like to close the old Github issues. If you feel that your issue is not resolved in the latest version, create a new ticket.

Help and Support use the Forum https://forum.bludit.org
Bugs and new requests here in Github https://github.com/bludit/bludit/issues


Fixed Tasks header causing MergeAndOrderSections to fail with Robot Framework 6.0+

Fixes #490

Codecov Report
Patch coverage: 75.00% and no project coverage change.

Comparison is base (6703048) 97.10% compared to head (a3aec0f) 97.10%.

:exclamation: Current head a3aec0f differs from pull request most recent head 819facc. Consider uploading reports for the commit 819facc to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #496   +/-   ##
=======================================
  Coverage   97.10%   97.10%
=======================================
  Files          47       47
  Lines        4311     4311
=======================================
  Hits         4186     4186
  Misses        125      125

Impacted Files
Coverage Δ

robotidy/decorators.py
68.96% <0.00%> (ø)

robotidy/transformers/MergeAndOrderSections.py
100.00% <100.00%> (ø)

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

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


[Bug]: got error: invalid_target

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
success login into
Actual behavior
got error: invalid_target

Verbose output
E:\dev\shopify\themes>shopify theme pull --store xxxxx.myshopify.com --verbose
2024-06-06T08:20:13.867Z: Running command theme pull
2024-06-06T08:20:13.878Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2024-06-06T08:20:13.879Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store xxxxx.myshopify.com:
[]

2024-06-06T08:20:13.880Z: Getting session store...
2024-06-06T08:20:13.880Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "xxxxx.myshopify.com"
  }
}

2024-06-06T08:20:13.880Z: Initiating the full authentication flow...
2024-06-06T08:20:13.881Z: Authorizing through Identity's website...

To run this command, log in to Shopify.
👉 Press any key to open the login page on your browser
2024-06-06T08:20:28.382Z: Reading the content of file at<EMAIL_ADDRESS>2024-06-06T08:20:28.406Z: Reading the content of file at<EMAIL_ADDRESS>2024-06-06T08:20:28.886Z: Authorization code received. Exchanging it for a CLI token...
2024-06-06T08:20:28.887Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=authorization_code&code=TUV4bmNNcTcyb3RPQ1J2cHEyVXU3ZGV0YjFFMWVuekczQ2V5UTZTMnduODQvbTNhZDBjY1hVSkxjejR5ZkhKYVlRUDM4SjR2NkRTSXRNdjRSR2JPUG5aSTV6R2Q4bDRSeE13K2hjaGI1bFdmV2RBd1FoK0N0MUtqWXRDSUEzM0VVbWJzaDVhbGhjNFpnUkNKNGFiR2xsbDBFS3ZJYVI5bkNSVzdZYUVtNjdHWjFTYmNMdDNVSEFrOWtibVk0SHU5V25lSElQN09melVzYmtLaGJDSTRLOHpSdFFFdHRQa1dvTUNvejV3MWlhYWpNeHhjeUpJRGFPbTZmK04xOUcrbXdoZG1yVW1OdnBlTUp2b082VUhzN3BCUEw3UjhGMS9JcU95Q3U0Uk4rcHNZRnZNZEFQaTJFY3pRSi96TkVpRDFaZFdiM0N6TmZRPT0tLUhMd1hRMjlScUtwTXd0NDctLXJiSjM3eFYvcUYxQmtMWlN6eXBQUlE9PQ&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%3A3456&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&code_verifier=vEUzN8vCkVy7NXzWrbt9HwJD7ffLFX7MDQHK8xSNrNg
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2024-06-06T08:20:29.851Z: Request to https://accounts.shopify.com/oauth/token?grant_type=authorization_code&code=TUV4bmNNcTcyb3RPQ1J2cHEyVXU3ZGV0YjFFMWVuekczQ2V5UTZTMnduODQvbTNhZDBjY1hVSkxjejR5ZkhKYVlRUDM4SjR2NkRTSXRNdjRSR2JPUG5aSTV6R2Q4bDRSeE13K2hjaGI1bFdmV2RBd1FoK0N0MUtqWXRDSUEzM0VVbWJzaDVhbGhjNFpnUkNKNGFiR2xsbDBFS3ZJYVI5bkNSVzdZYUVtNjdHWjFTYmNMdDNVSEFrOWtibVk0SHU5V25lSElQN09melVzYmtLaGJDSTRLOHpSdFFFdHRQa1dvTUNvejV3MWlhYWpNeHhjeUpJRGFPbTZmK04xOUcrbXdoZG1yVW1OdnBlTUp2b082VUhzN3BCUEw3UjhGMS9JcU95Q3U0Uk4rcHNZRnZNZEFQaTJFY3pRSi96TkVpRDFaZFdiM0N6TmZRPT0tLUhMd1hRMjlScUtwTXd0NDctLXJiSjM3eFYvcUYxQmtMWlN6eXBQUlE9PQ&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%3A3456&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&code_verifier=vEUzN8vCkVy7NXzWrbt9HwJD7ffLFX7MDQHK8xSNrNg completed in 960 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"32d9e7dfb5de8aa6d6f32a9758b325e5"
 - x-request-id: 48c072a0-28d0-4236-8889-dd840eac8a20-1717662034

2024-06-06T08:20:29.854Z: CLI token received. Exchanging it for application tokens...
2024-06-06T08:20:29.855Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2024-06-06T08:20:29.855Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2024-06-06T08:20:29.855Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2024-06-06T08:20:29.855Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fxxxxx.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.60.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2024-06-06T08:20:30.753Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fxxxxx.myshopify.com%2Fadmin completed in 895 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - x-request-id: 5c8a0f3e-b62a-43d1-85b9-7ece1426989c-1717662035

╭─ error ────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  invalid_target                                                                        │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────╯

2024-06-06T08:20:30.780Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=**** completed in 924 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"72953fcb223cff6bf40aa84594c0c795"
 - x-request-id: 5fd7d1a3-76d5-4783-9ac0-cfff78c5f9b1-1717662035

2024-06-06T08:20:30.795Z:
Running system process:
  · Command: ruby -v
  · Working directory: E:/dev/shopify/themes

2024-06-06T08:20:30.804Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=**** completed in 948 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"0c276e602648b9c6e7109aec109c780f"
 - x-request-id: c59ce262-1632-4e76-94b7-42695f6880cc-1717662035

2024-06-06T08:20:30.828Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=**** completed in 971 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"c6380df57905810f6389db490e560c00"
 - x-request-id: 3a4bbbdf-73ea-446f-b05a-934d49dbd64e-1717662035

2024-06-06T08:20:31.641Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 835 ms
With response headers:
 - x-request-id: fdedd840-b965-4946-a528-71e30beb744a

2024-06-06T08:20:31.642Z: Analytics event sent: {
  "command": "theme pull",
  "time_start":<PHONE_NUMBER>868,
  "time_end":<PHONE_NUMBER>772,
  "total_time": 16904,
  "success": false,
  "cli_version": "3.60.1",
  "ruby_version": "3.3.2",
  "node_version": "18.18.2",
  "is_employee": false,
  "uname": "windows amd64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/cli\"]",
  "env_shell": "cmd.exe",
  "env_device_id": "2710bf244ea79f9ffbf7959ec5cc5dbd905cae88",
  "env_cloud": "localhost",
  "env_package_manager": "unknown",
  "env_is_global": true,
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_all_timing_network_ms": 1889,
  "cmd_all_timing_prompts_ms": 14979,
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "theme",
  "cmd_all_plugin": "@shopify/cli",
  "cmd_all_force": false,
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "00aaf2c242c5fd7060f79c5ece3116f2b72be299",
  "cmd_all_timing_active_ms": 34,
  "cmd_all_exit": "expected_error",
  "args": "--store xxxxx.myshopify.com --verbose",
  "error_message": "invalid_target",
  "env_plugin_installed_all": "[\"@shopify/cli\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2024-06-06T08:20:31.648Z: Reporting handled error to Bugsnag: invalid_target

Reproduction steps

run command: shopify theme pull --store xxxxx.myshopify.com
got error: invalid_target

Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.60.1
Shell
cmd
Node version (run node -v if you're not sure)
v18.18.2
What language and version are you using in your application?
No response

👋 thanks for reporting this issue, this typically happens when the shopify store name is malformed. the command you shared typically would work on mac or linux, but im wondering if windows is not parsing the command correctly. have you been able to use any other CLI command with this store domain exactly as youve typed it?

some other things you can try as well to confirm what we think is happening true:

does running shopify theme pull prompt you with a list of themes to choose from ? (it should use your most recent store you authenticated and used a command with)
does using an environment variable for the store SHOPIFY_FLAG_STORE return different behavior?
if you have multiple stores, does using a different storename still return invalid target?

Hi @zmzimpl 👋
We've deployed an improvement to the error messaging here, to make it more clear that the store name or ID is likely incorrect. It will be available on the next minor CLI version release.
If you've confirmed that you have the correct store name/ID, and you've reviewed the steps in @mgmanzella's comments above, let us know.


error: GLSL 3.30 is not supported

Lapce Version
Lapce 0.2.0
System information
Ubuntu jammy amd64, Intel i5 M480
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 22.0.5
OpenGL shading language version string: 1.20
Describe the bug
Cannot run the app when using Intel HD. When I switch to the dedicated amd gpu, it works.
What is weird is that the command claims that GLSL 3.30 was available even though the Intel HD uses 1.20, see above.
Additional information
$ RUST_BACKTRACE=full /bin/lapce
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
', /github/home/.cargo/git/checkouts/piet-wgpu-913b036275d2afb6/f863b3e/src/pipeline.rs:89:13
stack backtrace:
   0:     0x55e9dd183ba1 - std::backtrace_rs::backtrace::libunwind::trace::h8217d0a8f3fd2f41
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x55e9dd183ba1 - std::backtrace_rs::backtrace::trace_unsynchronized::h308103876b3af410
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x55e9dd183ba1 - std::sys_common::backtrace::_print_fmt::hc208018c6153605e
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:66:5
   3:     0x55e9dd183ba1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf89a7ed694dfb585
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:45:22
   4:     0x55e9dc50d12c - core::fmt::write::h21038c1382fe4264
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/fmt/mod.rs:1197:17
   5:     0x55e9dd159d64 - std::io::Write::write_fmt::h7dbb1c9a3c254aef
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/io/mod.rs:1672:15
   6:     0x55e9dd185ab6 - std::sys_common::backtrace::_print::h4e8889719c9ddeb8
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:48:5
   7:     0x55e9dd185ab6 - std::sys_common::backtrace::print::h1506fe2cb3022667
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:35:9
   8:     0x55e9dd185ab6 - std::panicking::default_hook::{{closure}}::hd9d7ce2a8a782440
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:295:22
   9:     0x55e9dd186b47 - std::panicking::default_hook::h5b16ec25444b1b5d
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:314:9
  10:     0x55e9dd186b47 - std::panicking::rust_panic_with_hook::hb0138cb6e6fea3e4
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:698:17
  11:     0x55e9dd186622 - std::panicking::begin_panic_handler::{{closure}}::h4cb67095557cd1aa
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:588:13
  12:     0x55e9dd186596 - std::sys_common::backtrace::__rust_end_short_backtrace::h2bfcac279dcdc911
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/sys_common/backtrace.rs:138:18
  13:     0x55e9dd186552 - rust_begin_unwind
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
  14:     0x55e9dc3b0572 - core::panicking::panic_fmt::h1de71520faaa17d3
                               at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
  15:     0x55e9dced0930 - core::panicking::panic_display::h06547b41252f6337
  16:     0x55e9dced06db - piet_wgpu::pipeline::create_program::ha9242a56ebb85a91
  17:     0x55e9dc6ac396 - <O as gtk::auto::widget::WidgetExt>::connect_realize::realize_trampoline::h208e72816736d083
  18:     0x7f5330032d2f - g_closure_invoke
  19:     0x7f533004eb76 - <unknown>
  20:     0x7f5330050554 - g_signal_emit_valist
  21:     0x7f53300507a3 - g_signal_emit
  22:     0x7f532fb92967 - gtk_widget_realize
  23:     0x55e9dce48c2a - druid::win_handler::AppState<T>::build_native_window::h860832897dbf1d78
  24:     0x55e9dce3c75a - lapce_ui::app::launch::hd15c8707b5c5e2ba
  25:     0x55e9dc44fb83 - std::sys_common::backtrace::__rust_begin_short_backtrace::hc34edafa94416cdb
  26:     0x55e9dc44fef6 - main
  27:     0x7f532f093d90 - __libc_start_call_main
                               at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  28:     0x7f532f093e40 - __libc_start_main_impl
                               at ./csu/../csu/libc-start.c:392:3
  29:     0x55e9dc44fa4a - _start
  30:                0x0 - <unknown>

I get the same error on Intel i3 550 with integrated graphics.

get same error, on intel i3-380M

Lapce need minimum OpenGL 3.3 due to dual source blending which is used for subpixel text rendering which was added to the OpenGL 3.3 specification I think, maybe try running LIBGL_ALWAYS_SOFTWARE=1 lapce if you are on Linux as mentioned in https://github.com/lapce/lapce/issues/1108

Lapce need minimum OpenGL 3.3 due to dual source blending which is used for subpixel text rendering which was added to the OpenGL 3.3 specification I think, maybe try running LIBGL_ALWAYS_SOFTWARE=1 lapce if you are on Linux as mentioned in #1108

Or at least use that command in case your only gpu is not supported.

Closing in favour of #1108


fix huge rdma_recv_block_type no effect issue.

It has no effect for huge type of recv_block_size
which is as large as 2^21, because the block_size
variable is defined as type uint16_t, its maximum
value is 2^16. So, change the type of block_size
to uint32_t with relevant updates.
What problem does this PR solve?
Issue Number:
Problem Summary:
What is changed and the side effects?
Changed:
Side effects:

Performance effects(性能影响):

Breaking backward compatibility(向后兼容性):

Check List:

Please make sure your changes are compilable(请确保你的更改可以通过编译).
When providing us with a new feature, it is best to add related tests(如果你向我们增加一个新的功能, 请添加相关测试).
Please follow Contributor Covenant Code of Conduct.(请遵循贡献者准则).

LGTM


use tzinfo instead of str to identify the TimeZone in ZonedDateTime

The ZonedDateTime class uses a str to identify the timezone. Please consider using the standard tzinfo class instead. Using tzinfo allows alternative timezone libraries to be used instead of the one baked into whatever (presumably zoneinfo).
I have my own timezone Python library. It provides 2 different implementations of tzinfo. Both are drop-in replacements for zoneinfo, pytz, or any other Python timezone libraries. Given the current implementation of ZonedDateTime,  I cannot use my own timezone library with whatever.
Why do I want to use my own? Because zoneinfo has bugs in obscure edge cases. (pytz has even more bugs,  as well as the year 2038 problem). My libraries don't.

Interesting! You'll agree though that the 'customized tzinfo class' use case is niche. My general approach to these kind of issues are to allow them if the API doesn't become too complex for the 'average' user.
What immediately comes to mind is to allow tz= argument of ZonedDateTime to be str | tzinfo. However, this will affect the API:

the .tz attribute is no longer guaranteed to output a IANA timezone name.
serializing to/from a canonical string format is no longer possible.

Another potential solution is to provide a CustomDateTime class (perhaps in a separate whenever.advanced package), which has a tzinfo= argument. This class is an AwareDateTime subclass but then doesn't have a canonical string representation.

Because zoneinfo has bugs in obscure edge cases.

Pardon my ignorance, but: shouldn't these be fixed there then? Are these bugs with the Python library, or the actual IANA tz db?
Alternatively, isn't it possible to modify the zoneinfo files on your system yourself if you know better? Then the ZoneInfo package would automatically adjust to your needs.

I'll address your questions about the zoneinfo library in a separate post. It's complicated.
I think the least desirable solution is a CustomDateTime. Your library already has too many subclasses of AwareDateTime. :-)
I agree that using a non-IANA timezone identifier may be niche, but I think the need or desire to use a different timezone library may be more common than you might think:

Backwards compatibility An app may want to upgrade from datetime to whenever, but keep using pytz, for backwards compatibility with previous versions of the app. It may want to migrate to zoneinfo eventually, but do the migration in phases, first datetime->whenever then to pytz->zoneinfo.
Cross compatibility A system may be composed of multiple Python apps, servlets, modules, etc. One part of the system may be on pytz and need to remain there for some time. A different part of the system may need to continue to use pytz for cross compatibility.
Deterministic Reproducibility An app may need to pin a specific version of zoneinfo or pytz for integration testing and validation.
Better timezone library A new timezone library that is faster, smaller, and more accurate than zoneinfo may be created in the future.
zoneinfo is not available In resource-constrained, bare-metal (no OS) embedded environments, the zoneinfo library may be too large and not available. Smaller timezone libraries may need to be used. (In theory, my timezone libraries should fit into something on the order of 32-96 kB, instead of the multi-megabytes required by zoneinfo).

Proposed Solution
Here is my solution that I think is compatible with your current constraints on ZonedDateTime. My solution would continue use tz: str parameter in ZonedDateTime. But instead of hardcoding the dependency to zoneinfo, we add a layer of indirection (... "all CS problems can be solved with a layer of indirection"...), whose purpose is to provide an instance of tzinfo from its str:
(Sorry for any dumb syntax errors below, I haven't done much Python coding in several years...)
import zoneinfo
from typing_extensions import Protocol
[...]

class TzProvider(Protocol):
    def gettz(name: str) -> tzinfo:
         ...

class ZoneInfoProvider(TzProvider):
    def gettz(name: str) -> tzinfo:
        return zoneinfo.ZoneInfo(name)

Then at the whenever module level, we can provide hooks to replace the default TzProvider:

_tz_provider = ZoneInfoProvider()

def set_tz_provider(provider: TzProvider) -> None:
    _tz_provider = provider

def get_tz_provider() -> TzProvider:
    """Probably useful only for testing purposes"""
    return _tz_provider

Interesting Consequences
I realize that a pluggable TzProvider infrastructure is getting into Enterprise Java territory, but sometimes, Enterprise Java uses certain techniques because it actually solves real problems.
A pluggable TzProvider achieves the decoupling of the DateTime related classes and the TimeZone related classes, as I mentioned in #30, when I was speculating that the reason that LocalDateTime/SystemDateTime was needed was because there is too much coupling between "date/time" concepts and "timezone" concepts.
One interesting consequence is that this solution is that it allows whenever to support POSIX-style timezone rules naturally:
from whenever import ZonedDateTime
from whenever import TzProvider
from whenever import set_tz_provider

class PosixProvider(TzProvider):
    def gettz(name: str):
        # ...

posix_provider = PosixProvider()
set_tz_provider(posix_provider)

tz = ZonedDateTime(tz="NZST-12NZDT,M9.5.0,M4.1.0/3")

Implications for Pickling
I don't actually understand the requirements of Python pickling, so I don't know what is required of the ZonedDateTime class to support this pickling thing. Seems to me that it would be up to the specific TzProvider instance to decide whether it can handle a special, non-IANA, name identifier.

Lots to think about.
My impression is that most issues are solved by:

referring users to the inherent flexibility of zoneinfo itself as a tz provider
allowing ZoneInfo instances to be passed directly to ZonedDateTime

zoneinfo as a tz provider
As far as I can see, zoneinfo already supports almost everything you'd need from a tz provider:

Want to save space? Ship your system with fewer or smaller zoneinfo files
Want to pin a specific tz db version? Set TZPATH or using the tzdata PyPI package
Want to add your own timezone? Use ZoneInfo.from_file() and read all about its caveats in the official stdlib docs
zoneinfo not in your slimmed-down Python version? Use backports.zoneinfo.

What is zoneinfo itself it too large for your system?
I'm not familiar with using Python in super-constrained environments, but the zoneinfo library itself is only about 1k lines. And there's also a compiled C version that is probably smaller.
I'd feel safe saying that if 1k lines of code make a difference, then users are probably better off sticking to the standard library.
What about other timezone libraries?
I'm not yet convinced of the need to support alternate libraries. The IANA tz db (accessible through zoneinfo) is the overwhelming worldwide standard. AFAIK there is currently no reason to choose an alternative:

In case you're on dateutil.tz or pytz, you can/should probably migrate to zoneinfo anyway.
A hypothetical better future standard/library shouldn't clutter the API.


startup-notification: add description

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same formula update/change?
[x] Have you built your formula locally prior to submission with brew install <formula> (where <formula> is the name of the formula you're submitting)?
[x] Does your submission pass brew audit --strict --online <formula> (after doing brew install <formula>)?

Some URL fixes to apply here, if you fancy taking a swing at it:
        Error: 2 problems in 1 formula
homebrew/x11/startup-notification:
  * Stable: Please use https:// for http://www.freedesktop.org/software/startup-notification/releases/startup-notification-0.12.tar.gz
  * http://www.freedesktop.org/wiki/Software/startup-notification/ should be styled `https://wiki.freedesktop.org/www/Software/project_name`

Merged in https://github.com/Homebrew/homebrew-x11/commit/ce7a93fb9d69309d8fbe3d10c116897c297c5e4d. Thanks again @miguelarauj1o! 😃


[fix] gws memo messages fixture

Coverage decreased (-0.02%) to 79.074% when pulling d37efd3d6458884377c0de96856258035649f25c on ShinjiTanimoto:fixture into 9d43f61d5651840f4b7c858787e4a5d09f810c8b on shirasagi:master.


Uncaught Error: Cannot read property 'object' of undefined

Atom Version: 1.10.0-beta1
Electron Version: 0.37.8
System: Mac OS X 10.11.6
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/objects-registry.js:44:28)
at EventEmitter. (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/rpc-server.js:309:31)
at emitMany (events.js:121:13)
at EventEmitter.emit (events.js:195:7)
at EventEmitter. (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/api/web-contents.js:141:25)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
At /Applications/Atom Beta.app/Contents/Resources/electron.asar/renderer/api/remote.js:178

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/objects-registry.js:44:28)
    at EventEmitter.<anonymous> (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/rpc-server.js:309:31)
    at emitMany (events.js:121:13)
    at EventEmitter.emit (events.js:195:7)
    at EventEmitter.<anonymous> (/Applications/Atom Beta.app/Contents/Resources/electron.asar/browser/api/web-contents.js:141:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)
    at metaToValue (/Applications/Atom Beta.app/Contents/Resources/electron.asar/renderer/api/remote.js:178:13)
    at undefined.remoteMemberFunction (/Applications/Atom Beta.app/Contents/Resources/electron.asar/renderer/api/remote.js:112:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/atom-environment.js:636:29)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/atom-environment.js:670:36)
    at WindowEventHandler.module.exports.WindowEventHandler.handleWindowBlur (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/window-event-handler.js:182:35)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61

Commands
     -1:10.3.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:09.2.0 core:move-up (atom-text-editor.editor.is-focused)
  7x -1:08.9.0 core:move-right (atom-text-editor.editor.is-focused)
     -1:07.0 core:backspace (atom-text-editor.editor.is-focused)
     -1:06.5.0 core:move-down (atom-text-editor.editor.is-focused)
     -1:00.8.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:58.3.0 core:save (atom-text-editor.editor.is-focused)
     -0:35.4.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:33.3.0 core:undo (atom-text-editor.editor.is-focused)
     -0:32.5.0 core:save (atom-text-editor.editor.is-focused)
     -0:31.1.0 core:close (atom-text-editor.editor.is-focused)
     -0:28.3.0 git-plus:add-all-commit-and-push (atom-workspace.workspace.seti-ui-no-icons.theme-firewatch-syntax.theme-one-dark-ui.scrollbars-visible-when-scrolling)
     -0:25 core:backspace (atom-text-editor.editor.is-focused)
     -0:22.3.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:22.3.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:21.8.0 core:close (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "audioBeep": false,
    "themes": [
      "one-dark-ui",
      "firewatch-syntax"
    ]
  },
  "editor": {
    "invisibles": {},
    "showInvisibles": true
  }
}

Installed Packages
# User
aesthetic-ui, v2.0.0 (inactive)
atom-jade, v0.3.0 (active)
color-picker, v2.2.2 (active)
es6-javascript, v1.0.0 (inactive)
file-icons, v1.7.18 (active)
firewatch-syntax, v1.0.1 (active)
git-plus, v5.16.2 (active)
github-atom-light-syntax, v0.2.0 (inactive)
highlight-selected, v0.11.2 (active)
language-erlang, v3.0.0 (active)
linter, v1.11.16 (active)
linter-xo, v0.16.0 (active)
minimap, v4.24.7 (active)
minimap-highlight-selected, v4.4.0 (active)
my-github-profile, v0.2.1 (active)
pigments, v0.31.2 (active)
pretty-json, v1.5.1 (active)
project-manager, v2.9.7 (active)
terminal-plus, v0.14.5 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.5.0 (active)
one-light-ui, v1.5.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.3 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (active)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.38.1 (active)
find-and-replace, v0.201.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.2 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.65.0 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.241.0 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.0 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.100.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.208.2 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

This is a duplicate of #11692 - feel free to subscribe there for updates.


moved domains should be reselected after move

Select these three domains:

And move them. They should still be selected after the move (in case the user wants to move them again), but they are not:

This works properly for moving strands, and it is handled in middleware/reselect_moved_copied_strands.dart. I must have simply forgotten to include similar logic when implementing issue #416.
It's non-trivial to implement because the domain objects after moving are different objects than the ones before the move. Look at the logic of middleware/reselect_moved_copied_strands.dart to see how we do it for strands; essentially recording addresses of strands that can be looked up after the reducer is applied (through the call to next(action); in the middle of the middleware function). This is one of those rare situations where it makes sense to do middleware logic both before and after the call to next(action);.


chore(readme): Fixed and improved headers

I just read your readme and fixed some of the headings =)
Thanks for this ... just ordered the hardware and will try to get this running =)

Thank you!