Errors in homotopy implementations in MSL 3.2.1

Modified by dietmarw on 28 Jan 2013 09:46 UTC
It seems that there are errors in homotopy implementations in MSL 3.2.1:

in Modelica.Fluid.Fittings.BaseClasses.QuadraticTurbulent.BaseModel:

 if from_dp then
    m_flow = homotopy(...,
                     m_flow_nominal*dp_fg/dp_nominal);
 else
    dp_fg = homotopy(...,
                     m_flow_nominal*dp_fg/dp_nominal);
 end if;

The second expression should be something like: simplified=dp_nominal*m_flow/m_flow_nominal

in Modelica.Fluid.Fittings.SimpleGenericOrifice:

 if from_dp then
   m_flow = homotopy(...,
                      m_flow_nominal*dp_fg/dp_nominal);
 else
   dp_fg = homotopy(...,
                    m_flow_nominal*dp_fg/dp_nominal);
 end if;

The second expression should be something like: simplified=dp_nominal*m_flow/m_flow_nominal

MSL 3.3Dev is built completely differently, and doesn't contain these models.

Best regards,
Eric Thomas

Reported by Eric Thomas on 27 Jan 2013 19:13 UTC
It seems that there are errors in homotopy implementations in MSL 3.2.1:
1/ in Modelica.Fluid.Fittings.BaseClasses.QuadraticTurbulent.BaseModel:
if from_dp then
m_flow = homotopy(...,
m_flow_nominal*dp_fg/dp_nominal);
else
dp_fg = homotopy(...,
m_flow_nominal*dp_fg/dp_nominal);
end if;
The second expression should be something like: simplified=dp_nominal*m_flow/m_flow_nominal
2/ in Modelica.Fluid.Fittings.SimpleGenericOrifice:
if from_dp then
m_flow = homotopy(...,
m_flow_nominal*dp_fg/dp_nominal);
else
dp_fg = homotopy(...,
m_flow_nominal*dp_fg/dp_nominal);
end if;
The second expression should be something like: simplified=dp_nominal*m_flow/m_flow_nominal
3/ MSL 3.3Dev is built completely differently, and doesn't contain these models.
Best regards,
Eric Thomas

Migrated-From: https://trac.modelica.org/Modelica/ticket/974

Modified by otter on 27 Jan 2013 19:16 UTC

Comment by dietmarw on 28 Jan 2013 09:46 UTC
Improved readability of code listing.

Comment by dietmarw on 28 Jan 2013 09:46 UTC
Thomas, I'm wondering which MSL 3.3Dev you are referring to. Currently there is no such thing and in trunk is the development version that is going to be released as MSL 3.2.1. Could you clarify?

Comment by eth on 30 Jan 2013 21:32 UTC
You are right. It seems that I have confused several development versions. I don't find it again. It is better.

Comment by dietmarw on 30 Jan 2013 21:46 UTC
Now I have to ask again:

Did you find this issue in the Specification or in the Modelica Standard Library?
Is the issue still present?

Comment by rfranke on 31 Jan 2013 18:06 UTC
the bug is present in the trunk and needs to be solved for MSL 3.2.1.

Modified by dietmarw on 31 Jan 2013 18:07 UTC

Modified by dietmarw on 23 Feb 2013 12:57 UTC

Comment by fcasella on 5 Mar 2013 22:38 UTC
Fixed in e888ba44b4688768758900269d9791864ae10461


fix(ONYX-225): show showAddToMyCollectionBottomSheet on the MyC empty state

This PR resolves ONYX-225
Description

Show showAddToMyCollectionBottomSheet (modal with Add Artist and Add Artwork buttons) on the MyC empty state instead of navigating to Add Artist screen
Slack thread: https://artsy.slack.com/archives/C05EQL4R5N0/p1691572134461639
PR Checklist

[x] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

show modal with Add Artist and Add Artwork buttons on the MyC empty state -daria

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (show modal with Add Artist and Add Artwork buttons on the MyC empty state -daria)

  Generated by :no_entry_sign: dangerJS against 6ad8fd22ae1c34c509f7da9ef6c3ce9a0a70ac95


fix(edition): remove placeholder for now available sources

This PR removes placeholder from textcritics and source lists in op12 and op25. The targeted sources are now available.

ref.openModal('OP12_SOURCE_NOT_AVAILABLE') --> ref.openModal('OP12_SOURCE_NOT_AVAILABLE')


Update omniscale (map tile) api key to new paid token

Same deal as https://github.com/replicahq/graphhopper/pull/139, updating our omniscale API key, this time to a new key linked to a paid account to avoid losing access (thread for context)
Untested, but it can't make things worse 🤷
cc @bnaul

That's exactly right @bryanwilliams1025 - "user research" shows that the run-graphhopper-cloud script is still too much work for folks, so there's been a push to keep up "hosted" routers that can be accessed instantly via a browser
🤷


Use keyworded arguments for optional parameters.

In functions like heatmap()...
def heatmap(self, lats, lngs, threshold=10, radius=10, gradient=None, opacity=0.6, maxIntensity=1, dissipating=True)

...the many optional parameters makes the function definition longer than it should be, hurting its readability and maintainability (a contributer might accidentally add a new parameter in the middle instead of at the very end, breaking the interface).
It also makes it tougher to introduce API changes; in the above case, removing threshold (which is deprecated) would break this interface for all users calling this function with positional arguments, as in the following example:
heatmap(lats, lngs, 10, 15) # silent bug; if `threshold` is removed,
                            # `radius` will be set to 10 (instead of 15)
                            # and `gradient` will be set to 15

Using kwargs...
def heatmap(self, lats, lngs, **kwargs)

...would help make gmplot's interfaces more robust; users won't be able to pass in optional parameters as positional arguments, so a smaller subset of users would be affected by any future interface changes.
With this implemented, the above example would look like:
heatmap(lats, lngs, radius=15) # if `threshold` (or any other optional parameter)
                               # is removed from the interface, this function call
                               # won't be affected

@sandrotosi I'd like to hear your thoughts on this. This will require us to upgrade the major version number for gmplot (since it is an interface change), but I'm hoping that it'll make any future breaking interface changes less disruptive to users.


Ambiguous event extension description

This part of the documentation is very confusing. Which one is more performant?

event extension: Allows for the most performant event loop implementation.
libevent extension: Similar to the event extension, it allows for a more performant event loop implementation.

They are about the same actually, with perhaps a slight preference toward event. I plan on adding one or two more loop implementations in the near future and will make this clearer then.

An event loop implementation supporting the ev extension has been added and is now the preferred extension for the event loop. The section suggesting extensions has also been updated to clarify which extension is preferred. Thanks for pointing this out!


Provide an interop API to enable other extensions to provide code base locations

void SetUriBases(IEnumerable<Uri> uriBases).
By request from @GabeDeBacker (his team's extension will use it) and for parity with VS Code extension per @jeffersonking.
@michaelcfanning FYI

Larry is moving forward on this one...

@jeffersonking  @lgolding @GabeDeBacker to discuss


Create Azure DNS CLI in Node.js

Microsoft provides a DNS CLI managemnet tool only for PowerShell, restricting this to Windows users.
I need to manage Azure DNS entries from a Linux host, and that's why I'm creating a CLI in Node.js.
Some useful links:

http://azure.github.io/azure-sdk-for-node/azure-arm-dns/latest/
https://azure.microsoft.com/en-gb/documentation/articles/dns-getstarted-create-dnszone/
https://azure.microsoft.com/en-gb/documentation/articles/dns-getstarted-create-recordset/
https://azure.microsoft.com/en-gb/documentation/articles/dns-domain-delegation/

I'll try an alternative DNS server for now because I need to urgently setup 20 hosted zones.
I'll retake on this CLI tool task soon.

References for Azure REST API:

https://msdn.microsoft.com/pt-br/library/azure/dn776326.aspx#EnableRESTAPI
https://msdn.microsoft.com/pt-br/library/azure/mt130626.aspx
https://msdn.microsoft.com/pt-br/library/azure/mt130594.aspx
https://msdn.microsoft.com/pt-br/library/azure/mt130627.aspx

Azure documentation won't help Linux developers. That's a big thumbs down for them! :-1:


Import deprecate method

Should be ok, thanks.

return Variation::StrainSlice. We probably want to get rid of this as well in the future? For now it avoids the StrainSlice module in the core API and uses the new one in the variation API.

I try to move this into the variation API now and remove the dependency.

OK. I moved get_by_strain to the variation API.

thank you


[Bugfix] Switch tar crate to make tar.gz decompression work

Fixes #27

I just ran into #27. Is there anything preventing this from being merged? This is a pretty important fix since it's somewhat impossible to tell ahead of time what tarfiles will work and what won't.

I suspect tests are the long pole here? /cc @zertosh
Also, the fixtures still point to a personal repo (which is something we needed to do when this repo was still private prior to launch so it didn't break the internal Meta CI), but ideally that would also be changed now, e.g.:
https://github.com/facebook/dotslash/blob/76bbc2554a394afe26e215163c1a88bab6c48f2f/tests/generate_fixtures.py#L28
https://github.com/facebook/dotslash/blob/76bbc2554a394afe26e215163c1a88bab6c48f2f/tests/dotslash_tests.rs#L704

@kageiit can you rebase this PR?

I am conflicted here. I can repro the problem, and I can also repro that switching to binstall_tar fixes at least the ruff extracting issue. BUT, I don't have a lot of confidence in binstall_tar. It looks like they just grabbed the latest alexcrichton/tar-rs and applied (blindly?) many outstanding PRs. I don't know about the quality or how vetted anything has been. I also tried alexcrichton/tar-rs#298 by itself and it addresses the ruff issue too.
@bolinfest, wdyt?

FWIW, looks like alexcrichton/tar-rs will be maintained again: https://github.com/alexcrichton/tar-rs/issues/379
The sparse files PR was merged 2 weeks ago: https://github.com/alexcrichton/tar-rs/pull/375

@abhinav so is a bump to the latest https://crates.io/crates/tar (currently 0.4.42) all that is needed now?

@abhinav so is a bump to the latest https://crates.io/crates/tar (currently 0.4.42) all that is needed now?

Yes, I believe so, but @kageiit or @zertosh would have to confirm whether their repros are fixed with the upgrade.

@abhinav so is a bump to the latest https://crates.io/crates/tar (currently 0.4.42) all that is needed now?

Yes, I believe so, but @kageiit or @zertosh would have to confirm whether their repros are fixed with the upgrade.

Let me confirm

Unfortunately, tar 0.4.42 does not fix this. I just tried it and it fails the same way. I'm still going to update to 0.4.42 since I did the work internally for that anyway

This pull request has been merged in 4ee240e.

No no... I just referenced this PR saying that the tar 0.4.42 update doesn't fix the issue


[WIP] Pocket Network Implementation

Motivation
I would love to add POKT support.
About Pocket Network
Pocket Network is a decentralized node infrastructure protocol that enables users (applications/developers) to access blockchain data. Users submit API requests (relay requests) to service nodes via access points (Gateways) that build on top of the POKT Network. source
Changes Made

Implemented the necessary functions to interact with Pocket Network.
Updated the user interface to include options for Pocket Network.
Installed two external NPM packages protobufjs and long

Limitations
Currently, the CI/CD pipeline for Kraken Wallet is hosted on GitLab (just guessing) and is not open-sourced, making contributions challenging for open-source developers. It would be great to open-source development tools, instructions, the tests directory, and lockfiles.
Todos

[ ] can Harmony API support POKT or do we need to use Pocket RPC Endpoint?
[ ] properly handle fetchTransactions - i drafted the implementation which is working, but it renders tx as "contract interaction"
[ ] create and use /assets/images/assetGroup/asset-group-pokt.png for empty state (currently it's using default image)
[ ] use some API to obtain USD value of POKT holdings

Disclaimer
I'm not affiliated with Pocket Network.
Screenshots

Transaction that was sent by Kraken Wallet (using iOS Emulator): https://poktscan.com/tx/99BA508138ED6205DDE9A531995100978284E5ADE94220496F67B7617AA756A1

@studna is the point of this PR to switch from using the default nodes Kraken Wallet supports to using a node run by the POKT network? Can you give more background on the purpose?

@erickuhn19 The scope of this PR is limited to adding POKT as another wallet/asset supported by Kraken Wallet, essentially allowing users to send and receive POKT on the Pocket Network blockchain (as you can see on screenshots).
I'm not sure if the Harmony API can support the POKT blockchain (or when it might be able to), so I implemented a pocket-specific transport that uses the Pocket mainnet RPC Endpoint provided by Grove.city (the official POKT Gateway). Based on this implementation it can be even implemented under Harmony API and replaced with Harmony Transport.

is the point of this PR to switch from using the default nodes Kraken Wallet supports to using a node run by the POKT network?

While the ability to switch from the Harmony API to decentralized RPCs for all networks would be a positive step toward a more transparent and decentralized wallet, that's not the purpose of this PR.

@erickuhn19 I’m closing this PR as it’s becoming outdated. Pocket Network is transitioning to a native ERC20, and while this implementation works, it will be deprecated with a protocol upgrade by the end of the year.


ARROW-971: [C++/Python] Implement Array.IsValid/IsNull

This closes ARROW-971.

CI on Windows failed because of logging.h.
  c:\projects\arrow\cpp\src\arrow\util\logging.h(138): error C2220: warning treated as error - no 'object' file generated [C:\projects\arrow\cpp\build\src\arrow\arrow_static.vcxproj]
"C:\projects\arrow\cpp\build\INSTALL.vcxproj" (default target) (1) ->
"C:\projects\arrow\cpp\build\ALL_BUILD.vcxproj" (default target) (3) ->
"C:\projects\arrow\cpp\build\src\arrow\python\arrow_python_shared.vcxproj" (default target) (17) ->
"C:\projects\arrow\cpp\build\src\arrow\arrow_shared.vcxproj" (default target) (18) ->
  c:\projects\arrow\cpp\src\arrow\util\logging.h(138): error C2220: warning treated as error - no 'object' file generated [C:\projects\arrow\cpp\build\src\arrow\arrow_shared.vcxproj]
    79 Warning(s)
    2 Error(s)
Time Elapsed 00:13:59.08

I need to think a bit about this one. The Python API side is OK, but on the C++ side we might want to make this kernel-like

@wesm So you mean this should be implemented so as to be reusable in another component?

Right, this computation might be a unit of work in some more general computational pipeline, so it would be useful for this to be implemented with a similar API to other array kernel functions

@Licht-T What's the status of this PR? Do you plan to move this to a kernel?

This is marked for the 0.12 release. We should rewrite as a kernel

Closing as stale, let us revisit in an upcoming release cycle


Keep straight.el from automatically adding files to recentf-list

If you use recentf, recentf-list can get polluted with files from straight/build. Since the user should have no interested editing such files, it would be good to keep these from being added in the first place.

This will probably involve hacking one of the byte-compilation functions to use insert-file-contents-literally instead of insert-file-contents, or something like that.

Yeah, that's what I figured.

Should be fixed, please test.


Getting Help (and getting commands)

Summary of the new feature / enhancement
Some ideas for improving Get-Help.

Get-Help should accept pipeline input.
This:

Verb-Noun | Get-Help
Verb-Noun _defaultParameterValue_

takes a couple more keystrokes than:
Get-Help Verb-Noun
Verb-Noun _defaultParameterValue_

However, this:
Verb-Noun | Get-Help -Detailed
is preferable to:
Get-Help Verb-Noun -Detailed
Partly because the cursor goes to the right (correct & side) end of the previous command line when user depresses up arrow.

Get-Help should have closer integration with parameter names.
Instead of:
Get-Help Verb-Noun -Parameter _parametername_
this should work:
Verb-Noun -_ParameterName_ | Get-Help

Get-Help should have a paging switch parameter.
Instead of:
Get-Help Verb-Noun -Detailed | Out-Host -Paging
this should be possible:
Verb-Noun | Get-Help -Detailed -Paging

Verb-Noun -? is equivalent to Get-Help Verb-Noun. Great, but why stop there?
This should be possible:
Verb-Noun [-Examples | -Detailed | -Full | -Online]
That is, why not add these switches to common parameters?

Get-Help output would be easier to read with some coloring, especially examples.
Copy & paste any help out output into VSCode. That might be going to far, but some $PSStyle would be appreciated.

Get-Command should also accept pipeline input.
This should be possible:
Verb-Noun | Get-Command -Module

Get-Help remarks should include module information.

REMARKS
    Verb-Noun comes from the _ModuleName_ module.
    To see all the commands in this module, type: "Verb-Noun | Get-Command -Module"
    Alternatively, type: "Get-Command -Module _ModuleName_"

I think this would aid the discoverability of commands.
Proposed technical implementation details (optional)
No response

Partly because the cursor goes to the right (correct & side) end of the previous command line when user depresses up arrow.

User can press upArrow; F1 for detailed help or type Space;-? for brief one.

Indeed, the PSReadLine module offers convenient functions for invoking help context-sensitively.
The default key bindings are:
PS> Get-PSReadLineKeyHandler | oss | Select-String help

F1            ShowCommandHelp   Shows help for the command at the cursor in an alternate screen buffer.
Alt+h         ShowParameterHelp Shows help for the parameter at the cursor.

As stated, ShowCommandHelp  uses an alternate screen buffer (a separate screen, so to speak) to show Get-Help -Full output for the command to the left of the cursor with paging; if there's a parameter to the left of the cursor, the relevant description inside the command's help topic is directly jumped to. On typing q, the original screen is restored.

Note:

As of this writing, the parameter name must be spelled out in full (use tab-completion); while not a hardship, the behavior is surprising and it would be nice if that weren't required - see https://github.com/PowerShell/PSReadLine/issues/3560
Parameter aliases aren't supported (e.g., -lp for -LiteralPath), which will hopefully be fixed - see #13418
On macOS, the use of Alt-based keyboard shortcuts requires one-time configuration of the terminal application - see https://github.com/PowerShell/PSReadLine/issues/1075#issuecomment-1412449026

ShowParameterHelp shows type information and the description for the parameter to the left of the cursor below the current command line (the same constraints re recognizing parameter names as above apply).

The above I think addresses many of your usability concerns.
To address your suggestions: Get-Help does accept pipeline input, but only via an object whose .Name property contains the command name:
[pscustomobject] @{ Name = 'Get-Date' }  | Get-Help

This is somewhat helpful when piping the output of a Get-Command call:
Get-Command Get-Date | Get-Help

However, that is more verbose than Get-Help Get-Date or - with paging, using the built-in help function - help Get-Date.
The pipeline is not a good fit here in general, as only one topic can be meaningfully processed.
More fundamentally, while something like 'Get-Date' | Get-Help could be made to work (though doesn't seem worth it, the following suggested by you can not work (the same applies to your Get-Command suggestion):
# !! Cannot work syntactically, because Get-Date is *invoked*.
Get-Date | Get-Help

# !! Ditto
Get-Date -Year | Get-Help

This should be possible: Verb-Noun [-Examples | -Detailed | -Full | -Online]

Providing more control over what help content is displayed without involving Get-Help would be nice, but we don't want to introduce new common parameters unless absolutely necessary, given the invariable risk of name collisions (especially with switches such as -Online.
See https://github.com/PowerShell/PowerShell/issues/4137 for a proposed solution based one extending -?
As for the remaining suggestions, it's probably better to open separate, focused issues:

Get-Help output would be easier to read with some coloring, especially examples.

Good idea. Not only would coloring help, but also a better formatting of the syntax diagrams, with richer information.
Several issues in that vein already exist:

#8692
#6856
#4715
#4135
#4626

Get-Help remarks should include module information.

Good idea.

Partly because the cursor goes to the right (correct & side) end of the previous command line when user depresses up arrow.

User can press upArrow; F1 for detailed help or press upArrow and type Space-? for brief one.

That may be true, but is it reasonable to expect that user knows about this?
A function called Create-Shortcut cannot be authored without getting a squiggly line in vscode, and a WARNING from Import-Module, because the unchecked proliferation of verbs, supposedly jeopardizes the discoverability of commands. How is the hypothetical user supposed to discover PSReadLine key sequences?
If it is deemed reasonable that key sequences are learned, then why is not also reasonable that the user learns about commands by typing; (Get-Command Vern-Noun).Module.ExportedCommands? Then we could do away with approved verbs, and start naming commands with more appropriate semantics. Ex: End-Process or Kill-Process vs Stop-Process.
My point is; what sort of user is Powershell usability aimed at? If the general answer is "system admins", then I would suppose that that user would prefer;
End-Task to Stop-Process, because the first is a closer match to the Windows GUI, and also prefer;
Get-ADUser | Get-Help -Detailed to Get-Help Get-ADUser -Detailed, because the first is closer to the familiar some.exe /? syntax, and less 'hacking' of the command line is required when the user presses up arrow.

More fundamentally, while something like 'Get-Date' | Get-Help could be made to work (though doesn't seem worth it, the following suggested by you can not work (the same applies to your Get-Command suggestion):
# !! Cannot work syntactically, because Get-Date is *invoked*.
Get-Date | Get-Help

# !! Ditto
Get-Date -Year | Get-Help

In the case of Get-Date, I'm inclined to ask; so what if it is invoked? Get-Help would see a date object, and could apply Get (which I think is the default verb) to that object, to derive Get-Date. The command date is supposedly identical to Get-Date, although I noticed that date -? does not give the expected result.
For commands with mandatory parameters, could Powershell get the first mandatory parameter, and if the value is $null, and the next token on the command line is |, send a name parameter down the pipeline, and finalize processing that command? So this would then work:
PS > Copy-Item | Get-Help
This too:
PS > Copy-Item | Out-Host
Copy-Item

Along the same line, this would also work:
Copy-Item -ToSession | Get-Help
Thanks for all the links!

That may be true, but is it reasonable to expect that user knows about this?

Let's try to fix that:

https://github.com/MicrosoftDocs/PowerShell-Docs/issues/9796

In the case of Get-Date, I'm inclined to ask; so what if it is invoked?

What if the cmdlet does something destructive (which it obviously shouldn't?
What if it prompts for missing parameters?
What if the parameter is a switch, which doesn't need an argument?
...
(And there's no way to infer from a given output object's type what cmdlet it came from.)
Creating syntax exceptions the way you propose is asking for trouble and conceptual confusion - I strongly advise against it.
Again, F1 and Alt-h are the solution, and they just need to be documented better (see previous comment).

Creating syntax exceptions the way you propose is asking for trouble and conceptual confusion - I strongly advise against it.

How pleasing or confusing this would be to use, should be determined in a usability lab, and/or with an experimental feature.

Again, F1 and Alt-h are the solution, and they just need to be documented better (see previous comment).

The fact that these keyboard shortcuts exist, indicates that the command line alternatives are inefficient.
Alt-H is okay, but F1 is not fun to use - no PgUp|PgDn, spacebar scroll or scroll wheel, and 'Q' to escape is a bit odd.

How pleasing or confusing this would be to use, should be determined in a usability lab, and/or with an experimental feature.

Not every idea is worth exploring further, if there are fundamental reasons that suggest that it is a dead end.
Of course, deeming this to be the case in this instance is my personal assessment, but in the absence of arguments to the contrary my original rationale stands. Let's see if others weigh in.

Alt-H is okay, but F1 is not fun to use - no PgUp|PgDn, spacebar scroll or scroll wheel, and 'Q' to escape is a bit odd.

See the previously linked to:

https://github.com/PowerShell/PSReadLine/issues/3561

So going back to your original rationale...

What if the cmdlet does something destructive (which it obviously shouldn't?
What if it prompts for missing parameters?
What if the parameter is a switch, which doesn't need an argument? ...
...
(And there's no way to infer from a given output object's type what cmdlet it came from.)

Don't these arguments apply to Verb-Noun -??
How is that syntax able to work without issue, that could not also work with Verb-Noun | Get-Help?
I would presume that as the Powershell engine is always in control of all operations, there are no fundamental obstacles to any syntax format.

Again, F1 and Alt-h are the solution, and they just need to be documented better (see previous comment).

Those suggestions would be great if implemented, but what if the user wants -Examples or -Online help? Do they revert to using the command line?

Those suggestions would be great if implemented, but what if the user wants -Examples or -Online help? Do they revert to using the command line?

That would make for great additions to https://github.com/PowerShell/PSReadLine/issues/3561 - I've just updated the proposal there.

Don't these arguments apply to Verb-Noun -??

No; you can think of -? as a common parameter, like -ErrorAction (which is also why it only works for cmdlets and advanced functions/scripts), and the invocation syntax clearly indicates the intent to seek help.
The bottom line is this: a given invocation of a command (say, Get-ChildItem -File) should always act the same, whether stand-alone or in a pipeline, and what specific command is in the next pipeline segment should never fundamentally change the behavior of such an invocation.

Don't these arguments apply to Verb-Noun -??

No; you can think of -? as a common parameter, like -ErrorAction (which is also why it only works for cmdlets and advanced functions/scripts), and the invocation syntax clearly indicates the intent to seek help.

Unlike -ErrorAction though, -? is not included in the tab-completion list, so it would be better to think of -? as a hidden common parameter. Perhaps it should be unhidden and named -Help.

The bottom line is this: a given invocation of a command (say, Get-ChildItem -File) should always act the same, whether stand-alone or in a pipeline, and what specific command is in the next pipeline segment should never fundamentally change the behavior of such an invocation.

So your bottom line is that there should be no special cases. That leaves us with the following situation.
Verb-Noun -?  # for help
Get-Help Verb-Noun -Detailed  # for detailed help
Verb-Noun[F1]  # for full help
Get-Help Verb-Noun -Online  # for online help
Get-Help Verb-Noun -Parameter spelloutparameter  # for parameter help
Get-Help about_topic  # for language construct commands and other subjects help
Get-Command Verb-Noun -Syntax  # for syntax help

Compare all this with...
anyCommand [Parameter] | Get-Help [-Detailed | -Full | -Online | -Syntax]
Which is the least confusing?

-? is not included in the tab-completion list

Excellent point: please open a new issue focused on that.

Which is the least confusing?

That 's easy; the following is the least confusing:

a given invocation of a command (say, Get-ChildItem -File) should always act the same, whether stand-alone or in a pipeline, and what specific command is in the next pipeline segment should never fundamentally change the behavior of such an invocation.

As for Get-Help about_topic and the desire to get help for language keywords such as while and foreach:
I agree that these should be easier to discover, and F1 could be extended to recognize those as well.
Please open a feature suggestion at https://github.com/PowerShell/PSReadLine/issues (don't just comment on https://github.com/PowerShell/PSReadLine/issues/3561)

@Andrew74L  Thank you for the issue -- The working group finds nothing actionable here. @mklement0 has provided answers for these issues.


chore(main): release uniform 0.10.3

:robot: I have created a release beep boop
0.10.3 (2024-11-11)
Bug Fixes

uniform: improve form debug disable logic, add setting for custom ls key (23345dc)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

uniform-v0.10.3
:sunflower:


[TextField] Floating label does not recover after hovering the autofill suggestions

I noticed that starting with version 4.4.3 of the Material UI (https://v4-4-3.material-ui.com/components/text-fields/ this has been used in the GIF provided as demo) if you hover the autofill suggestion but you don't select one and click away, the label remains floated up and does not animated back to placeholder position.
On earlier versions of Material UI (eg. https://v4-3-3.material-ui.com/components/text-fields/) the issue is not reproducible.
Is this something which can be fixed on Material UI side OR has to do with the way browsers handle autofill suggestions? Thank you!

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Notice that the label didn't animate back to placeholder and is still floating.
Expected Behavior 🤔
The floating label should animate back to placeholder position when clicking away even if no selection has been made.
Steps to Reproduce 🕹
You can use this link to reproduce https://v4-4-3.material-ui.com/components/text-fields/
I also attached a GIF to demonstrate the behavior.

Steps:

Focus an input
The label is floated up
Hover the list of autofill suggestions, BUT don't make any selection
Click away
Notice that the label didn't animate back to placeholder and is still floating.

Context 🔦
Not blocking, just UI bug.
Your Environment 🌎

Tech
Version

Material-UI
> v4.4.3

React
^16.13.1

Browser
Chrome Version 81.0.4044.138

@mihaela-kokoon Do you have a reproduction with the latest version?

@oliviertassinari Here it is a GIF with the latest version and the bug reproducing:

Here is also the codesandbox link: https://codesandbox.io/s/unruffled-shirley-62q2e?file=/src/Demo.js

@mihaela-kokoon Thanks for reporting this regression, from https://github.com/mui-org/material-ui/issues/14427#issuecomment-534277159. Could you confirm this fix?
diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
index 2b1f12b2b..eb62c96c3 100644
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -31,12 +31,8 @@ export const styles = (theme) => {

   return {
     '@global': {
-      '@keyframes mui-auto-fill': {
-        from: {},
-      },
-      '@keyframes mui-auto-fill-cancel': {
-        from: {},
-      },
+      '@keyframes mui-auto-fill': {},
+      '@keyframes mui-auto-fill-cancel': {},
     },
     /* Styles applied to the root element. */
     root: {
@@ -98,6 +94,7 @@ export const styles = (theme) => {
       minWidth: 0,
       width: '100%', // Fix IE 11 width issue
       animationName: 'mui-auto-fill-cancel',
+      animationDuration: '10ms',
       '&::-webkit-input-placeholder': placeholder,
       '&::-moz-placeholder': placeholder, // Firefox 19+
       '&:-ms-input-placeholder': placeholder, // IE 11
@@ -391,10 +388,12 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
     };
   }

If it does work, do you want to submit a pull request? :)

@oliviertassinari Thanks a lot for the fast answer! Appreciate it! I'll make some time (hopefully this weekend) and will check it! Cheers!


Unable to run demo

Ubuntu 16.04 fresh install with ROS kinetic. I followed steps from readme and while executing the command roslaunch aerial_mapper_demos 0-synthetic-cadastre-dense-pcl.launch  the following error message is shown. What could be wrong here?
p.s. I am new to ROS/catkin
Finished  <<< aerial_mapper_demos                          [ 59.1 seconds ]
[build] Summary: All 31 packages succeeded!
[build]   Ignored:   22 packages were skipped or are blacklisted.
[build]   Warnings:  13 packages succeeded with warnings.
[build]   Abandoned: None.
[build]   Failed:    None.
[build] Runtime: 1 hour 4 minutes and 15.6 seconds total.
[build] Note: Workspace packages have changed, please re-source setup files to use them.
mapper@mapper-VirtualBox:~/catkin_ws_aerial_mapper/src$ roslaunch aerial_mapper_demos 0-synthetic-cadastre-dense-pcl.launch
[0-synthetic-cadastre-dense-pcl.launch] is neither a launch file in package [aerial_mapper_demos] nor is [aerial_mapper_demos] a launch file name
The traceback for the exception was written to the log file

source ../devel/setup.bash is required after catkin build aerial_mapper to run the demos, fixes my issue

Hi,
kindly guide about running custom dataset. My system cant find ROS nodes.
Error is here:
ERROR: cannot launch node of type [aerial_mapper_demos/aerial_mapper_demos_dense_pcl]: can't locate node [aerial_mapper_demos_dense_pcl] in package [aerial_mapper_demos]
I have set path of dataset in config file

See the previous question. You have to source your workspace after the build.


Argent wallet doesn't work

Currently when you submit a tx using Argent, the tx doesn't appear to register in LS and you have to refresh the game to get updates

Currently when you submit a tx using Argent, the tx doesn't appear to register in LS and you have to refresh the game to get updates

Hey @dgnscan !
This could also be a hardware failure on the Argent Wallet
It sounds like your query would be best dealt with by the support team.

I’ll have to refer you to the official support live platform with the ticket ID ARG7463
Please see the link below to our dedicated support line:

Argent Wallet Ticket Support Requests for possible solutions.

Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent for further assistance
Regards.

As discussed this is know working so closing issue


Issue with generating a model through Xcode, generating random models

Describe the bug
When generating a model through Xcode, the model is different than the one I requested.
Amplify CLI Version
4.41.2
To Reproduce
Through Xcode,

Editing schema.graphql to my custom Model
in amplifytools.xcconfig: push=true, modelgen=true
Run the projects
Update Completed

Expected behavior
The generated custom model that I have created in schema.graphql. Instead I am getting some unknown to me models: Task and Note
Screenshots
Model created through Xcode for deployment:

Configuration:

Model changes in schema.graphql after successful deployment:

Model actually deployed visible from the Admin Console

Desktop (please complete the following information):

OS: Mac Apple M1 BigSur 11.2
Node Version: 15.8.0

Hi,
I found a walkaround.

configure pods with libraries
init and push amplify
go to AWS console
Create a model from an admin console in aws amplify

in Xcode:
configure Graphql file as you configured your model in an admin console
Modelgen to true
push to true
build and run project. In that step, Xcode will create the model that you have just modified.
All should work as supposed to.

Anyone ve met that issue before? May thanks for clues about what is wrong

hi @jmgawecki, thanks for reaching out.
The build phase script provided by the Amplify/Tools pod is not longer recommended. It's currently deprecated and it will be completely removed in a future release.
The functionality provided by the amplify-tools.sh is currently integrated with the Amplify CLI and iOS projects can leverage it without any extra dependency.
amplify codegen models will correctly generate and add models to an AmplifyModels group in your Xcode project.
This Xcode integration was added to the CLI on version 4.40.0.
We believe that relying on the CLI provides a fast and reliable developer experience.
I'd recommend to run amplify codegen models to generate Swift models out of your schema and amplify push to deploy your changes.
Please let us know if you have further questions.

Also starting from Amplify v1.6.1, a deprecation warning will be issued when the amplify-tools.sh is invoked as part of an Xcode build script.
You can find more details about AmplifyTools deprecation here.
I'll optimistically close this issue but feel free to re-open if you have more questions.


Connection refused: getsockopt

Describe the problem
I'm really sorry - I'm a bit of a noob with all things server management. Ever since the update where they required Java 21 (1.20.4?) we haven't been able to connect to our server. I just get "Connection refused: getsockopt". There are no logs since that update happened.
Container definition
minecraft:
    container_name: minecraft
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    # version: "1.20.4"
    image: itzg/minecraft-server
    restart: unless-stopped
    volumes:
      - ./minecraft:/data
    environment:
      - EULA=TRUE

Container logs
Paste logs here

There must be some kind of logs...try this:
docker compose pull
docker compose up -d
docker compose logs -f
# use control-c to stop following the logs

Maybe the docker compose pull was enough to fix it. I've never used that discussion before. Seems to work now though. Thanks!

where should I put this?

minecraft-mc-1  | java.lang.RuntimeException: An exception occurred when launching the server!
minecraft-mc-1  |       at net.fabricmc.loader.impl.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:71)
minecraft-mc-1  |       at net.fabricmc.installer.ServerLauncher.main(ServerLauncher.java:69)
minecraft-mc-1  | Caused by: java.lang.RuntimeException: Error invoking MC server bundler: java.lang.UnsupportedClassVersionError: net/minecraft/bundler/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0
explained by my friend chatgpt:
This error indicates that the version of Java you are using is too old for the version of Minecraft you're trying to run. The error message states that the class file version is 65.0, which corresponds to Java 17. Your Docker image needs to be updated to use Java 17.

my bad forgot to update my docker image so it tried to mix recent fabric with the old image.


Have the Replay scene read .pb.cobs.gz files

The log files are now compressed. The Replay scene should be able to read those.

https://gitlab.com/bikelab/phobos-visualizer/merge_requests/2/diffs

Merged (even though gitlab says its not).


'The engine "node" is incompatible with this module' as of 2.4.0

Describe the bug
Was just updating to latest to grab a bug fix and came across the following error when installing via yarn:
$ yarn
yarn install v1.22.15
[1/4] Resolving packages...
[2/4] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=14". Got "12.22.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Previous versions do not appear to produce this error.
To Reproduce
Steps to reproduce the behavior:

Add 2.4.0 to package.json.
Install with yarn, although probably npm works too.

Expected behavior
Should install the latest version.
Screenshots
N/A
Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser: N/A
Version: N/A

Smartphone (please complete the following information):
N/A
Additional context
2.3.5 appears to install correctly. I have pinned my version to that dependency for now.

Sry, I changed in package.json node engine to 14 since some tests fail on v12. Will see and add it back, but keep in mind that other libraries are already on v14+. If I add it back, it will be until the end of the maintenance period (2022-04-30) and after that, it will be dropped.

Fix v2.4.1 is now live


Auto-formatting of sass in Vue files via sass-formatter doesn't work

For Vetur, we have set up:
{
  "vetur.format.defaultFormatter.sass": "sass-formatter",
}

Which then formats the style section of a Vue file using that sass-formatter.
Eg.
<style lang="sass">
 .class
  color :  black;
</style>

becomes:
<style lang="sass">
.class
  color: black
</style>

Volar seems to not have this Feature?
For our use case this would be required for Volar to be able to replace Vetur in our projects. : )
Thank you very much.

See https://github.com/johnsoncodehk/volar/discussions/444#discussioncomment-1263519.
Third-party formatter would be support by plugin API (#185).

@johnsoncodehk Hmmm, ideally we would want the formatting feature natively built into Volar.
Especially since Evan wants to push Volar to be the default library instead of Vetur.
Expecting users to install both Volar and Vetur and then set Vetur to only formatting seems a little bit complex for newer developers, and especially newer developers are the ones that benefit most from auto-formatting of the style section in Vue files.
Do you have no plans to change your thought train on this feature? I'm interested to know your thoughts.
Best regards,
Luca

@johnsoncodehk Hmmm, ideally we would want the formatting feature natively built into Volar.
Especially since Evan wants to push Volar to be the default library instead of Vetur.
Expecting users to install both Volar and Vetur and then set Vetur to only formatting seems a little bit complex for newer developers, and especially newer developers are the ones that benefit most from auto-formatting of the style section in Vue files.
Do you have no plans to change your thought train on this feature? I'm interested to know your thoughts.
Best regards,
Luca

ps: I see that you want to implement it via a Volar plugin? interested how newbie friendly this can be. Is this like a VSCode plugin to complement the Volar extension? Or how would this work?
ps2: I become a sponsor 🎉

volar was not developed for the purpose of replacing vetur. I have strong subjective opinions on ide support, I just design volar's features in the correct way in my view. We will not implement a feature because vetur have it, so volar many features designs are actually very different to vetur.
If you want to know why I think so:

Built-in support for non-built-in features of vue is not a suitable design
This project is huge, I need to make sure its core is streamlined to move forward smoothly

Adding features is simple usually, but sometimes this will increase the complexity of the project, the increase in complexity will increase the difficulty of the project's maintenance exponentially. Therefore, in order to prevent the project becoming a monster, it is more important to "do not add some features" correctly. (Of course this requires a comprehensive consideration of many factors)

ps: I see that you want to implement it via a Volar plugin? interested how newbie friendly this can be. Is this like a VSCode plugin to complement the Volar extension? Or how would this work?

I hope it to be like this. https://docs.unity3d.com/Manual/upm-ui.html
But everything is undecided, the goal of full-time development is still far away.

ps2: I become a sponsor 🎉

Thank you!

@johnsoncodehk I understand the design philosophy.
Is there any way we can keep this issue open until it's possible to have auto-formatting via some plugin? Much appreciated.
I think we can consider opening this issue and attaching issue-hunt goal as well. So people can come and put money in towards this feature specifically.
Auto-formatting of the vue files with sass css is pretty important I believe ;)

If you just want sass formatting out of the box instead of a configurable formatter, I can actually simply add it in next version. And move it out after implemented plugin api.

@johnsoncodehk
that would be very very very much appreciated! I don't care so much about configuring.
I think for sass, there's no configuring anyway?
The formatter that Vetur uses for lang="sass" is this one: https://github.com/TheRealSyler/sass-formatter
So if this can be run on <style lang="sass"> sections of Vue files, then I think I have everything I need from Volar to switch from Vetur.

The template and script sections are already formatted through Volar (powered by Prettier) right?
Then, since Volar will be the one doing formatting for Vue files, we need to set .vscode/settings.json to this, right?
{
  "[vue]": { "editor.defaultFormatter": "johnsoncodehk.volar" },
}

Basically, sass-formatter would be added to the readme here:

because sass seems to be the only one left out that doesn't have any auto-formatting with Volar. 😅

Added in https://github.com/johnsoncodehk/volar/commit/1cc570de60982748f80791776d71745adcbf6ace


FileSessionHandler tries to read non-existing session file

Laravel Version: 5.2.45
PHP Version: 5.6
Database Driver & Version: MySQL PDO

Description:
I get the following fatal error, seemingly at random, quite a lot:
[2017-03-08 13:16:07] local.ERROR: exception 'ErrorException' with message 'file_get_contents(/myapp/storage/framework/sessions/1ab19e392734aa1191529ab9b857b1aba94aa5c5): failed to open stream: No such file or directory' in /myapp/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:38
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'file_get_conten...', '/myapp...', 38, Array)
#1 /myapp/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php(38): file_get_contents('/myapp...')
#2 /myapp/vendor/laravel/framework/src/Illuminate/Session/FileSessionHandler.php(71): Illuminate\Filesystem\Filesystem->get('/myapp...')
#3 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(124): Illuminate\Session\FileSessionHandler->read('1ab19e392734aa1...')
#4 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(108): Illuminate\Session\Store->readFromHandler()
#5 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(92): Illuminate\Session\Store->loadSession()
#6 /myapp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(104): Illuminate\Session\Store->start()
#7 /myapp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(57): Illuminate\Session\Middleware\StartSession->startSession(Object(Illuminate\Http\Request))
#8 [internal function]: Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#9 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(136): call_user_func_array(Array, Array)
#10 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#11 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#12 /myapp/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#13 [internal function]: Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#14 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(136): call_user_func_array(Array, Array)
#15 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#17 /myapp/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#18 [internal function]: Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#19 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(136): call_user_func_array(Array, Array)
#20 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#21 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#22 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#24 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(726): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#25 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(699): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#26 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(675): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#27 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(246): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#28 [internal function]: Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#29 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(52): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#30 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(44): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#31 [internal function]: Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#32 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(136): call_user_func_array(Array, Array)
#33 [internal function]: Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#34 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#35 [internal function]: Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#36 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): call_user_func(Object(Closure), Object(Illuminate\Http\Request))
#37 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(132): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#38 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(99): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#39 /myapp/public/index.php(54): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#40 {main}

Looking at the trace, it seems like the session file was deleted between these lines: https://github.com/laravel/framework/blob/5.2/src/Illuminate/Session/FileSessionHandler.php#L69-L71
I can't figure out why that would happen.
The only thing I can think of that makes this app interesting in this regard is that there is middleware that creates a User for everyone that doesn't have a cookie with user id in it (and logs those that do in).
Steps To Reproduce:
Seems to happen at random for all requests in the application.

Please ask on the forums, I'm sure someone will be able to help you there. We try to keep this repo for bug reporting only.
I also recommend that you upgrade to a more recent version since 5.2 is not supported anymore, many fixes was added to the framework since that release.

I'll try to migrate to a more recent version then, but what makes you think this is not a bug in the framework?

I updated Laravel to version 5.4.15.
PHP version: 7.0.16
Although a little bit different, the error persists.
[2017-03-09 15:44:55] local.ERROR: exception 'ErrorException' with message 'fopen(/myapp/storage/framework/sessions/DsYiDF6umqNGGxAVyXIxWCHy9KqaT1H1nIFNlgfH): failed to open stream: No such file or directory' in /myapp/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:54
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'fopen(/home/tim...', '/myapp...', 54, Array)
#1 /myapp/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php(54): fopen('/myapp...', 'rb')
#2 /myapp/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php(38): Illuminate\Filesystem\Filesystem->sharedGet('/myapp...')
#3 /myapp/vendor/laravel/framework/src/Illuminate/Session/FileSessionHandler.php(71): Illuminate\Filesystem\Filesystem->get('/myapp...', true)
#4 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(96): Illuminate\Session\FileSessionHandler->read('DsYiDF6umqNGGxA...')
#5 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(86): Illuminate\Session\Store->readFromHandler()
#6 /myapp/vendor/laravel/framework/src/Illuminate/Session/Store.php(70): Illuminate\Session\Store->loadSession()
#7 /myapp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(103): Illuminate\Session\Store->start()
#8 /myapp/vendor/laravel/framework/src/Illuminate/Support/helpers.php(878): Illuminate\Session\Middleware\StartSession->Illuminate\Session\Middleware\{closure}(Object(Illuminate\Session\Store))
#9 /myapp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(104): tap(Object(Illuminate\Session\Store), Object(Closure))
#10 /myapp/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(58): Illuminate\Session\Middleware\StartSession->startSession(Object(Illuminate\Http\Request))
#11 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#12 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#13 /myapp/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#14 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#17 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(561): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#18 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(520): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#19 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Router.php(498): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#20 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(174): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#21 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#22 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(148): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 /myapp/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 /myapp/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#26 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(149): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#27 /myapp/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#28 /myapp/public/index.php(54): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#29 {main}


What  are the tags that looks like {: .nolineno } called? What language is that?

Checklist

[X] I have read the newlest tutorials and know the correct effect of the functional design.
[X] There is no similar question on existing issues (including closed ones).
[X] I have tried to find the answer on Jekyll Forum and StackOverflow.
[X] My question is based on the latest code of the master branch.

Description
Short Question
First let me say: Thanks for this theme. It's awesome and my blog looks so nice now.
On to my question: What are the "tags" that look like {: <some content> } called? What language or syntax is this from? Is this part of Jekyll or Liquid? Or is this a convention you developed with custom code? An example is {: .nolineno }
Context
This isn't an issue with your theme but I need some more context to solve an issue with a code formatter I'm using.
I like to use prettier to format my markdown. But one issue I have is that some of the "tags" that I use must have spacing preserved (like {: .nolineno }).
For example, if I have the following code

```javascript
var x = someFunction()
```
{. nolineno }

And format it with prettier it'll put a space between the code block and the no line number tag like this:

```javascript
var x = someFunction()
```

{. nolineno }

And that space appears to break the functionality. If it is moved like that, then I'll end up with line numbers.
Thanks for any assistance you can give me. I'd like to see if there is a plugin I can write to stop that behavior, or otherwise ask prettier if they can add support for tags like this.

Searching your repo I found this https://github.com/search?q=repo%3Acotes2020%2Fjekyll-theme-chirpy+nolineno+language%3ASCSS&type=code&l=SCSS
and it looks like perhaps {: .nonlineno } is a way to "embed" a little CSS tag into Markdown?

sorry I think I found the answer. Looks like it is supported by kramdown: https://kramdown.gettalong.org/syntax.html#attribute-list-definitions

And its already a known issue: https://github.com/prettier/prettier/issues/3645


TypeError: bt.io.prepare

Dear team,
I am trying to use your bt.io.prepare function to transform my annotated pictures into an AnnData object.
I load the molecules as a np.df, cell_seg and other_seg (DAPI stain) are both np.ndarray. When I run the bt.io.prepare function I get the following error:

Seems a bit weird to me given that np.array and np.ndarray are in principle the same, and np.array is asked as input for the cell segmentation.
Looking forward to hear your thoughts.

Hi @nynkekatinka, thanks for giving this a try! We don't have any tutorials on this yet, we are actually in the middle of refactoring to use SpatialData instead of AnnData, stay tuned for that. It supports ingesting standard output formats from other platforms e.g. Xenium, CosMx, Vizgen, etc.
For your error, try passing a dictionary like so: other_seg={'DAPI': DAPI}. But fair warning we are reworking IO at the moment.

Hi @ckmah that indeed solved the current issue at hand. I was wondering whether you have any timeline for when you hope to have finished the transition from AnnData to SpatialData?

Hi @nynkekatinka , I am closing this issue as we have officially transitioned to SpatialData with v2.1. Check out the revamped tutorials and look out for tutorials for major platforms soon!


Added README.md for date processor

Signed-off-by: Asif Sohail Mohammed<EMAIL_ADDRESS>Description
Date processor documentation
Issues Resolved
Check List

[ ] New functionality includes testing.
[x] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1059 (7051026) into main (cc0a6fc) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 7051026 differs from pull request most recent head 7e6c5e0. Consider uploading reports for the commit 7e6c5e0 to get more accurate results

@@            Coverage Diff            @@
##               main    #1059   +/-   ##
=========================================
  Coverage     91.32%   91.32%
  Complexity      683      683
=========================================
  Files            84       84
  Lines          1994     1994
  Branches        168      168
=========================================
  Hits           1821     1821
  Misses          132      132
  Partials         41       41

Continue to review full report at Codecov.

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

Looking good. Let's address the formatting nitpick raised by @dinujoh and then I will approve. Thanks!


overview size lessened, border added

Description
Overall overview size is now smaller. Overview now has a border as well.
Type of change

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

also please remove the issue from PR, it's not related

@l3enQ
Done


feat: add drag/drop for sas content

Summary
This makes a few changes to support dragging/dropping of SAS content.

First, this moves treeview creation into ContentDataProvider. This more closely mimics the vscode samples, and makes the drag and drop controller work in a more predictable way
This sets up drag/drop and supports the following features:

Dragging one or more files from an external source (explorer or file system) into sas content
Dragging files within sas content to the recycle bin or favorites (NOTE: Once they are in favorite/recycle bin, a user needs to use the context menu options to remove them)
Dragging folders from an external location into sas content

Additionally, this solves an issue around retrieving corrupted auth credentials
NOTE: This doesn't support dragging files from sas content to the external filesystem. I've not found a way to do that, yet

Testing

[x] Test dragging file from file explorer into sas content
[x] Test dragging file from external file system into sas content
[x] Test dragging a sas content file to my favorites (NOTE: partially blocked by https://github.com/sassoftware/vscode-sas-extension/pull/284)
[x] Test dragging a sas content file from my favorites (should be prohibited)
[x] Test dragging a sas content file to recycle bin
[x] Test dragging a sas content file from recycle bin (should be prohibited)
[x] Test dragging files to various prohibited locations
[x] Test moving folder out of child folder and back to "My folder" (try the same with file)

Hey @Becky-Williamson. If you've not started testing this yet, hold off for a bit. I discovered one bug around content selection that I need to sort out. I'll let you know when it's ready to test :)

Hey @Becky-Williamson. If you've not started testing this yet, hold off for a bit. I discovered one bug around content selection that I need to sort out. I'll let you know when it's ready to test :)

This has now been sorted :). Test at your leisure


MINOR: Updating files with release 2.7.1

We need to wait for the artifact to show up in Maven before merging
Also I don't have permissions to push the artifacts to our S3 bucket. Can someone do it for me? Thanks
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mjsax @vvcephei can you take a look? Thanks

Also I don't have permissions to push the artifacts to our S3 bucket.

Yeah. Confluent own this bucket... We need to find a better solution for this... uploaded both artifacts. Can you double check that you can read them?

Build failed with Could not find org.apache.kafka:kafka-streams:2.7.1. -- we should try to run it again later and only merge after it passed to be sure the artifact are accessbile.

Thanks @mjsax, I can see the artifacts now. I've rekicked the build

@mjsax / @chia7712  Can you take another look? Thanks

@rajinisivaram @omkreddy Can you take a look? We need this PR and https://github.com/apache/kafka-site/pull/354 in order to release 2.7.1. Thanks


JS SDK QuickStart Updates

Enhanced background section
Added simple intro
Simplified language to use JSVM over enclave
Simplified setup
Added details to build, deploy, and interact sections
Added help & feedback section

I feel as though we need to agree upon terminology. This document will get confusing once we release the standalone SDK and calling this the enclave quick-start (IMO) sets expectations and (i hope) will help developers find what they're looking for.


Elixir compatibility

Evaluation needed on running the PRNGs on Elixir

Elixir 1.2.0 has introduced OTP rand module based PRNGs. No need to pursue this further. Closed.


feat: implement bitShiftRight function push down

What problem does this PR solve?
Issue Number: close #5100
Problem Summary:
Implement bitRightShift function push down.
What is changed and how it works?

Register bitShiftRight func name in scalar_func_map.
Wrap builder with buildBitwiseFunction by updating DAGExpressionAnalyzerHelper::function_builder_map.
Update CH version's BitShiftRightImpl to handle a C++ undefined behavior of shift operation.

Check List
Tests

[x] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

Looks good

/run-all-tests

/merge

Add release note like 'Support to pushdown bitShiftRight to TiFlash'.
And add the pr link of tidb?

/run-all-tests

/merge

/merge

/merge


@types/react-redux is incorrect for mergeProps when mapDispatchToProps is null/undefined

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

React:
ReactDOM/React Native:
Redux:
React Redux:

What is the current behavior?
Discussed here: https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/59297
The error is that the types do not consider a code-supported case where mergeProps is defined, but mapDispatchToProps is not. The types expect that the passed value will be undefined, whereas the code actually passes { dispatch: Dispatch }.
This means that, when the Typescript option strictFunctionTypes is set to true, correctly typed usages of this pattern will fail.
What is the expected behavior?
When turning strictFunctionTypes on, the types should still compile for this specific use case. A PR has been opened to fix the issue.
I was asked to file this issue to make sure it gets tracked for v8 development.
Which browser and OS are affected by this issue?
No response
Did this work in previous versions of React Redux?

[ ] Yes

This got merged in DT, and also added to v8.


Misuse of React Router leads to incorrect HTML structure

Steps to reproduce:

Open app: https://spring-library-frontend.herokuapp.com/
Open DevTools and check HTML structure

Actual result:

Expected result:
The body contains three separate components: menu, main and footer. All of them are on the same level.

Fixed in 930d85f0a0718fa16ef74f805ae3061acbf3d1ae


This plugin is not working in older browser for chrome and mozilla

Try to tell what the problem and send me documentation for browser version compatability.

Which browser versions have you tried ?

Chrome 28 version
On 08-Nov-2016 12:07 pm, "Boniface Pereira"<EMAIL_ADDRESS>wrote:

Which browser versions have you tried ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/craftpip/jquery-confirm/issues/166#issuecomment-259058008,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWPPPq-rUq5EeweC9HsKEowtEmFnvkTGks5q8Bi3gaJpZM4Krc_t
.

I've tested it in chrome 28, it works in it, jquery defer doesn't seem to work properly in it.


Allow sorting by modification date

As my number of project grows, I've noticed that it sometimes takes a moment before I've found my project in the explorer. Would it be possible to show the modification date for each project as a column, so that the user can sort by modification date?

Yes that should be possible and is a good idea. I also plan on making a filter box, in which users can enter a string to (partially) match with project and file names. All non-matching tree items should then be hidden.

That was easy enough. The data was readily available in the API response and could directly be used.
I just pushed v1.2.2 to our various channels. This shows columns in the tree with Created and Modified, where applicable. Can you check if this works for you?

Beautiful! Yes, it works.


Prefer use STUN server over TURN server?

We are using SimpleWebRTC for our chatting web app (Electron/Chrome), but found it seemed to prefer TURN server over STUN server. Could you please explain how should we let it try STUN server first?

I believe the browser decides which ICE candidates to use first, and IIRC, browsers are moving toward using TURN first for faster connection establishment, then renegotiate to STUN if possible. @fippo will know that better than I.

@xdumaine not yet, but otherwise you're correct. STUN will be used whenever possible, TURN is only the fallback. If TURN is used that means STUN could not be used.

Strange then, we tested our coTURN server under stun-only mode and the connection seemed to be good. Don't know what was going on there.

The same problem.


Add support for exporting and importing reports

These rake scripts and classes provide functionality for exporting/importing of the following ManageIQ object types:

Reports

This PR uses the framework that was implemented for PRs #14126, #15256, #16717, and others to export/import other ManageIQ object types.
These scripts are based on the CFME RH Consulting Scripts and are used by Red Hat consultants to enable storing customizations in Git and maintaining customizations between environments (e.g. dev/qa/prod) for an SDLC lifecycle.
Links [Optional]

Tracking Issue: Implement export/import functionality of Miq objects via command-line

Steps for Testing/QA [Optional]
Exporting

Create a directory for the exports

mkdir /tmp/reports

Export user defined reports

vmdb
bin/rake evm:export:reports -- --directory /tmp/reports

Importing

Import all report yaml files in a directory

# vmdb
# bin/rake evm:import:reports -- --source /tmp/reports

or Import specific report yaml file

# vmdb
# bin/rake evm:import:report -- --source /tmp/reports/Test_Report.yaml

@branic I just got to this today. Looks good so far. Need to looks at the tests...

@branic This looks good. Can you please take care of the rubocop issues with trailing spaces in the report yamls? Once that's done I'll merge.  Thanks 👍

@gtanzillo Fixed the rubocop trailing spaces and squashed all the commits into one.


[capstone2llvmir]: unhandled branch instruction format #2

Running retdec-decompiler.py returns "[capstone2llvmir]: unhandled branch instruction format #2
Error: Decompilation to LLVM IR failed" using powerpc. I cannot supply the exe file.

This is thrown only at one place in translation, so I might be able to look into it even without the input. If not, I will at least add better error message that would contain the instruction that causes problems - that way, you would not have to supply the whole input file, only the problematic instruction in question.

I think I also face the same error message : unhandled branch instruction format #3. How can I avoid it?


chore: added new zone, new regions and sorted the vms

Describe your changes
I have added region europe-west4, all relevant zones based on the https://cloud.google.com/vertex-ai/docs/general/locations#user-managed-notebooks-locations
I have also added the A100 GPU VM machines I found available in the web UI.
Issue ticket number and link
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] My changes generate no new warnings

Codecov Report
Patch and project coverage have no change.

Comparison is base (9dffe31) 74.42% compared to head (8cd9de6) 74.42%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #101   +/-   ##
=======================================
  Coverage   74.42%   74.42%
=======================================
  Files          57       57
  Lines        2839     2839
=======================================
  Hits         2113     2113
  Misses        726      726

Files Changed
Coverage Δ

src/wanna/core/utils/gcp.py
56.81% <0.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Some breaking changes for 0.11

Nothing too drastic but still will require small simple migrations steps from users.
Move ssr build from priv/static/assets into priv/svelte
priv/static/assets files are exposed through Plug.Static, priv/static files are digested and compressed with phx.digest task. Neither of those things need to apply to ssr build, so changed it location to priv/svelte.
Migration: a user will need to update optsServer.outdir in build.js and add priv/svelte to gitignore.
Set dev in svelte compiler options
Activate dev mode in non-deploy builds for svelte. It enables various things like @debug tag and logs warnings on improper usage of components. (Not a breaking one since it applies only to assets/copy.)
Instead of pushEvent/pushEventTo pass live hook with live prop
Unless user exports both pushEvent and pushEventTo svelte complains about passing of unknown props in dev mode. It is annoying and unfortunately there is no way to check if a component exports those... To limit that annoyance replace pushEvent/pushEventTo with a single prop live and pass live hook instance into it so now to remove that warning exporting that prop is enough. It also gives a user access to more of live view capabilities - handleEvent/removeHandleEvent/upload/uploadTo.
Migration: need to replace export let pushEvent with export let live and pushEvent calls with live.pushEvent.
Replace render/exportSvelteComponents with getRender
exportSvelteComponents was needed because there was usage of require and delete require.cache in ssr render function. But that usage has been removed already, so api can be changed to more clean one. (That commit also contains somewhat subjective clean up of internal js.)
Migration:  need to replace three lines in assets/js/server.js with two shorter ones.
This PR is based on previous not-yet-merged about typescript definitions and split into corresponding four commits for git history readability.

These are all great thank you, exporting live instead of pushEvent/pushEventTo is a lot better.
Let me wrap my head around the changes for a little bit, I don't want to rush breaking changes, but will highly likely merge these during this week.
If you have more changes planned let me know so I'll wait a bit so I can do everything in one go :)

Nothing planned much. But yeah, no hurry, take time.
For record just now I experimented with adding a preprocess to add export let live = undefined to a script if it does not contain it, simple to do but it leads to warning about an unused variable, so I guess no way to silence that thing.

I looked into updating svelte version in package json from 3 to 4. There is an import in hooks from svelte/internal - import {detach, insert, noop} from "svelte/internal" and unfortunately esbuild does not tree shake it properly, even now it generates around 100 lines of unneeded code (out of 260 total). If version is updated to 4th one then that number grows. So I removed that import by copying those functions, thankfully those are basic one-liners.
Question: Why priv/static not in gitignore? Usually build files are put into ignore.

Ok, I rebased, split last commit into two - about render and about refactor in hooks, removed preprocessor commit.

I don't see this error, I have dev: !deploy set.

Strange, as you can see from linked code unless $$props or $$restProps are used there should be a warning for an unknown prop in dev mode. And I do get it, for example by going to example number 1, /simple.
Removed preprocessor for now, yeah it is not perfect, I don't think you can make an ideal one, there are tradeoffs to be made. It is an optional thing anyway, so can be forgot about for now.

Ok nvm I see the error now.
Thanks for the quick response, I'll take a look at everything again now!

Merged the changes, thanks for the great work :)

Available in 0.11.0


Content for step 6 is not accurate in tutorial "Chase the pizza"

Describe the bug
Content for step 6 is not accurate in tutorial "Chase the pizza"
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Tutorials------>Chase the Pizza----->JavaScript Start Tutorial
Expect behavior
The variable should be named pizza
Actual behavior
Content for step 6 is not accurate in tutorial "Chase the pizza".

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.3.20
3.Microsoft MakeCode version: 6.7.2

It also happened in python tutorial.

@shakao - code collapse (when diffs is false) seems to not show some changes in hints.

oh hmm, i will take a look!

@shakao - this funny diff behavior is still occurring. I'm gonna pass it to you to look at. Let me know if I need to make some change to it.

@ganicke fixed!! sorry for the delay, was totally a markdown rendering bug eating the code and not a content thing haha


ARTEMIS-2215 largemessage have been consumed but not deleted

During the backup and live synchronization, the client consumes the largemessage, then the live crash(the performCachedLargeMessageDeletes method is not executed), after the live startup, the largemessages that have been consumed are not deleted from the disk.

Im less familar with the journal stuff in general from what i can tell though it looks good, so will let @franz1981 give a thumbs up on the logic change, but from better use of collection libs +1 one me.


Add updates for SSP content & validation for declaration

Brings in the following changes to the SSP:

copy changes to the hint text for the 'add a new service' journey:

https://github.com/alphagov/digitalmarketplace-ssp-content/pull/63

validation messages for the supplier declaration:

https://github.com/alphagov/digitalmarketplace-ssp-content/pull/53

I'm just going over the other SSP content PR now to check question numbers reconcile properly.
Fine to merge this now if you like, but was planning to get all pending changes in before bumping the content.

@TheDoubleK makes sense to do them in order.

Does that mean we should close this PR and wait for one that encompasses all changes?

Yeah, I'll do that until the numbers in the validation match the content. Once we're at that point I'm happy to rewrite this one to encompass those other changes.

Aargh, sorry Tom, this update has gone in now with a different PR.

@TheDoubleK If you point to it I'm happy to redo this one to remove those changes.

https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/205
This one just needs to be closed I think as it's the same change. (Don't think you had re-opened this one yet when I made that one).


Libre Alarms Using Non Calibrated Data

Describe the bug
Using Libre, when a high or low notification is sounded, the app appears to be using non calibrated data to trigger the alarm, despite being lower (in this case) than the alarm trigger point.
To Reproduce
Steps to reproduce the behavior:

Calibrate Libre sensor to a value below default
Observe when default value in GCM settings exceeds threshold, but calibrated value is below.
Observe high alert

Expected behavior
A clear and concise description of what you expected to happen.
High alert only applies to calibrated values.
Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information): iPhone 15 Pro
Setup Information (please complete the following information):

Pump type - DASH
CGM type and CGM app - Freestyle Libre 2, Libre App (don't use)
Trio version, branch and git reference (see Trio Settings) Open-iAPS Alpha c8ceccc

Additional context
Add any other context about the problem here.

Tagging @dabear in case this is not on your radar already.

I am not certain I understand this problem. Libretransmitter has its own experimental calibration feature. Libretransmitters alarm feature does work on top of this calibration. allowsEditingFactoryCalibrationData must be set to true though (it's experimental so not something that should be set to true by default).
If trio implements calibration on top of the value returned by Libretransmitter, Libretransmitter would not know about or use that for alarming. If Trio modifies the glucose values returned,  it should also be responsible for sending out any alarms rather than letting Libretransmitter do it

Ok, thanks for the info, I believe Trio has its own calibration on top. Maybe the Libre alarms should be disabled when libretransmitter is used in Trio?
Tagging @kskandis , whom I believe is working on alarms/alerts in Trio?

If needed, I can add a feature flag to libretransmitter to programatically disable alarms, both from ui and the alarm handling code itself

I believe Loop now also supports a cheaper Dexcom targeted at T2 without alarms in its accompanying app. Hence this discussion will probably reemerge. Adding the alarms at the CGM manager level sounds a little like duplicating of work across CGM managers.

Pete did not accept the pull request for Stelo support into Loop yet. He is wearing one himself but was concerned about alarms.

Ok, thanks for the info, I believe Trio has its own calibration on top. Maybe the Libre alarms should be disabled when libretransmitter is used in Trio? And replaced with Trio specific alarms perhaps?
Tagging @kskandis , whom I believe is working on alarms/alerts in Trio?

Yes, agree, Libre plugin has its own set of notifications that are enabled in the plugin by the user in NotificationsSettingsView, saved to UserDefaults, and based on those settings, Libre will send APN in NotificationsHelper.  This is similar to what Trio does.  Trio ,of course, already has High/Low BG notifications if the user enables them in Settings - Notifications - Glucose Notifications.  The other Libre notifications are Libre specific which Trio currently has no way of accessing that data.


Fix gtest-not-found bug

This change fixes #1030, which arises from the changes made in #1022.
It works for me on Ubuntu 16.04, but it should be checked by a user on Debian Buster to confirm that the original fix still works as expected.

@sloretz can you please try this with Debian Buster?

@jwhendy Can you also check if this fixes your build issues on Arch?

I can confirm that the fix-1030 branch from @mikepurvis works when building ros-melodic-realtime-tools on arch linux, while kinetic-devel does not.
I do get a bunch of warnings like this, but they don't seem to affect the build.
CMake Warning (dev) at /usr/src/gmock/CMakeLists.txt:47 (add_subdirectory):
  Policy CMP0013 is not set: Duplicate binary directories are not allowed.
  Run "cmake --help-policy CMP0013" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  The binary directory

    /home/jwhendy/catkin_ws/build/moveit_tutorials/gtest

  is already used to build a source directory.  This command uses it to build
  source directory

    /usr/src/gtest

  which can generate conflicting build files.  CMake does not support this
  use case but it used to work accidentally and is being allowed for
  compatibility.
This warning is for project developers.  Use -Wno-dev to suppress it.

Thanks for taking a stab at this @mikepurvis !

@jwhendy Please provide more context: what platform are you seeing these warnings on, what version of CMake are you using? Also this seems to be unrelated to this PR. Can you please check if the same warning happens with older versions of catkin?

@sloretz can you please try this with Debian Buster?

I'm able to build noetic up to realtime_tools (with a patch to realtime_tools I need open a PR for) using this branch, though there are a couple extra include paths passed to g++. The ones ending in /include make sense to me, but the ones without it don't. I haven't figured out where they come from yet.
/usr/bin/c++  -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 -DROS_PACKAGE_NAME=\"realtime_tools\" -I/home/sloretz/rtt/src/realtime_tools/include -I/home/sloretz/ws/noetic/devel_isolated/roscpp/include -I/home/sloretz/ws/noetic/devel_isolated/roscpp/include/ros -I/home/sloretz/ws/noetic/src/ros_comm/clients/roscpp/include -I/home/sloretz/ws/noetic/src/ros_comm/utilities/xmlrpcpp/include -I/home/sloretz/ws/noetic/src/ros_comm/utilities/xmlrpcpp/include/xmlrpcpp -I/home/sloretz/ws/noetic/devel_isolated/rosgraph_msgs/include -I/home/sloretz/ws/noetic/devel_isolated/std_msgs/include -I/home/sloretz/ws/noetic/src/std_msgs/include -I/home/sloretz/ws/noetic/src/rosconsole/include -I/home/sloretz/ws/noetic/src/roscpp_core/roscpp_serialization/include -I/home/sloretz/ws/noetic/src/roscpp_core/rostime/include -I/home/sloretz/ws/noetic/src/roscpp_core/roscpp_traits/include -I/home/sloretz/ws/noetic/src/roscpp_core/cpp_common/include -isystem /usr/src/googletest/googlemock/include -isystem /usr/src/googletest/googlemock -isystem /usr/src/googletest/googletest/include -isystem /usr/src/googletest/googletest  -O3 -DNDEBUG   -pthread -DGTEST_HAS_PTHREAD=1 -o CMakeFiles/realtime_box_tests.dir/test/realtime_box_tests.cpp.o -c /home/sloretz/rtt/src/realtime_tools/test/realtime_box_tests.cpp

From above, highlighting:
    -isystem /usr/src/googletest/googlemock/include
    -isystem /usr/src/googletest/googlemock
    -isystem /usr/src/googletest/googletest/include
    -isystem /usr/src/googletest/googletest

@dirk-thomas sorry on the delay, I was out of town. It is unrelated to this PR, but not unrelated to my overall issues of getting catkin and gmock to work on Arch in #1030. I forgot that I already commented on this over there.
I'll add a followup comment there instead of muddying the waters here, but this is almost certainly an issue on how to get Arch + gmock package files correct, nothing to do with catkin. Sorry about that.

there are a couple extra include paths passed to g++. The ones ending in /include make sense to me, but the ones without it don't. I haven't figured out where they come from yet.

I think this is from the CMakeLists.txt shipped with googletest, so it can be ignored.
# Where Google Test's .h files can be found.
set(gtest_build_include_dirs
  "${gtest_SOURCE_DIR}/include"
  "${gtest_SOURCE_DIR}")
include_directories(${gtest_build_include_dirs})

I don't understand why this works,

:zipper_mouth_face:

but it works on Debian Buster.

:ship: :crossed_fingers:

Thanks to everyone for creating / testing the patch.


def test_create_user_access_denied - Test_Users_api.py

Fix Test Assertion: If the token is valid but the user does not have permission to perform the action, the correct status code is 403 Forbidden. If the token is invalid, the correct status code is 401 Unauthorized.

https://github.com/kaw393939/event_manager/blob/main/tests/test_api/test_users_api.py


Inspect/fix multiple active tabs in manager.tabs.

Motivation

Requirements

[ ] There should be only one active tabs object per window.

Note
Currently the window focus handling is work in progress.

UPD: Had trouble repeating this bug after merging together all the pending changes for 0.1.0.


Win 7 support

Hi, any chance of this becoming a vagrant-plugin with Win 7 support so that gulp - running on the vagrant VM - could send it's notifications to a Win7 host?

My original intent was to make use of it from vagrant-notify, but as per https://github.com/fgrehm/vagrant-notify/issues/24 I've stepped down as a maintainer of that project since I haven't been using it that much recently.
As per Win7 support, I don't use this on windows so I'm going to rely on the community to provide a patch for it. Sorry about that :disappointed:

No problem - fully understood.


The i18n / l10n doesn't scale

This project has/had an awesome amount of PRs in to make it multilingual by default, but with how things are currently implemented, they tend to conflict with each other. Can we come up with something better?

Yea, should support ISO language code (e.g. en-US)


Trouble with cvxpy

I seem to have error in importing cvxpy for some reason.
I have looked for solutions, but I can't find the solution. Below is the error I got.
I am using PyCharm and my OS is Mac.
Traceback (most recent call last):
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/data_prep.py", line 5, in
from deepdow.benchmarks import Benchmark, OneOverN, Random
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/deepdow/benchmarks.py", line 5, in
from cvxpylayers.torch import CvxpyLayer
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/cvxpylayers/torch/init.py", line 1, in
from cvxpylayers.torch.cvxpylayer import CvxpyLayer  # noqa: F401
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/cvxpylayers/torch/cvxpylayer.py", line 1, in
import diffcp
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/diffcp/init.py", line 3, in
from diffcp.cone_program import solve_and_derivative,
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/diffcp/cone_program.py", line 3, in
import diffcp.cones as cone_lib
File "/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/diffcp/cones.py", line 6, in
from _diffcp import dprojection, project_exp_cone, Cone, ConeType
ImportError: dlopen(/Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/_diffcp.cpython-38-darwin.so, 2): Library not loaded: @rpath/libc++.1.dylib
Referenced from: /Users/chriskang/Desktop/OneDrive - HKUST Connect/Pycharm/2021_Toy/DeepDow/venv/PycharmProjects/VirtualEnvList/lib/python3.8/site-packages/_diffcp.cpython-38-darwin.so
Reason: image not found
Please help

Hey there!
Looking at the traceback I think this issue has to do with incorrect installation of cvxpylayers and more specifically it's dependency diffcp.
I would image that if you try to run the following import inside of Python you get the same error, right?
import diffcp.cones as cone_lib

Anyway, if that is the case, I would definitely encourage you to read through issues in the following repos. And if none of them addresses your problem you should probably create a new issue.

https://github.com/cvxgrp/cvxpylayers/blob/master/setup.py
https://github.com/cvxgrp/diffcp

If you figure out the problem, feel free to close this issue and potential describe what measures you took:)


logging: Disable logfile access for "other".

Set logfile mode to 0640 rather than 0666 for safety.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Coverage remained the same at 33.333% when pulling 167a534cbd664b69d3a377a6ab0dcb90a54a97f3 on jodh-intel:restrict-perms-on-logfile into cea22a0179596408e98bc1c1cd212a9ca186d3b8 on clearcontainers:master.

lgtm


Add feature to add shapes to the shape, to create group of shapes

It includes correct selection of shapes in the group, display the properties of correct shape when select it, correct rearrange of parent/child relationship of shapes when remove parent shape.


[2.0 branch] Tracking issue - Unified API

This is a non-exhaustive list containing todo's to refactor the current 2.0 branch to conform the unified SDK API see: https://docs.sentry.io/clientdev/unified-api/
In general, all points are up for discussion. This should be a rough guideline to hold on to while we progress through it.

[ ] Up minimum PHP version to 7.1 and use features (like: Return type declarations, nullable types, Throwable, …)
[ ] General wording changes to functions (e.g.: leaveBreadcrumb -> addBreadcrumb, Config -> Options)
[ ] Change Sentry protocol version to 7
[ ] Update SDK identifier + User Agent (sentry.php)
[ ] Context → Scope
[ ] Create Hub which takes some responsibility of the Client / ClientBuilder
[ ] Breakup Client

[ ] Move getLastEventID to Hub
[ ] Move breadcrumbs, context information into Scope
[ ] Refactor Middleware's to Integrations
[ ] Remove some public setter/getter

[ ] DSN → We no longer need path (projectRoot)
[ ] shouldCapture → beforeSend
[ ] Do not setTags in Configuration
[ ] Stacktrace should be stacktrace.values[].frames
[ ] Breadcrumbs should be breadcrumbs.values[].crumb
[ ] Remove base64 encoding
[ ] Remove sanitization
[ ] Remove docs from repo, they new live in https://github.com/getsentry/sentry-docs
[ ] Write + Update Docs https://github.com/getsentry/sentry-php/issues/650

Closing this in favor of https://github.com/getsentry/sentry-php/pull/677


Viability of using minimina for a local testing engine

Problem
I've heard that local networks tend to crash after a couple hours of operation and may be too resource intensive.
Assessment Criteria
Gain confidence in the direction of using minimina as a local testing engine and record metrics.
Tasks

[x] Run minimina on local machine
[x] Monitor various metrics, e.g. RAM, CPU usage
[ ] Understand the requirements of a typical test network
[ ] Run minimina under the load of a typical test network

This would be an invaluable way for devs to test tiers 1 & 2 locally, before merging/running their code on the CI

With a {push, pull}-based Network_state utilizing GQL it will be possible to use minimina for local test deployments


Update overview.md

CLA Agreement signed

Can you rebase this against master @edavidcsoft ? https://kubernetes.io/docs/contribute/intermediate/#work-on-the-local-repository has tips on how to do that.

/close
@edavidcsoft please rebase this PR as suggested by @sftim .
Closing this PR for now. Please feel free to reopen after the rebase.