Limactl start not working, when ed25519_sk doesn't exist

Try to start lima on a new machine
How to reproduce
Make sure that your ~/.ssh looks like this:

Install lima with brew:  brew install lima
Run limactl start
Use the default configuration
Notice the crash, because ed25519_sk doesn't exist

? Creating an instance "default" Proceed with the default configuration
INFO[0005] Downloading "https://github.com/containerd/nerdctl/releases/download/v0.11.1/nerdctl-full-0.11.1-linux-amd64.tar.gz" (sha256:ce7a6e119b03c3fb8ded3d46d929962fd17417bea1d5bbc07e0fce49494d8a09)
172.67 MiB / 172.67 MiB [----------------------------------] 100.00% 30.20 MiB/s
INFO[0012] Downloaded "nerdctl-full-0.11.1-linux-amd64.tar.gz"
INFO[0014] Attempting to download the image from "~/Downloads/hirsute-server-cloudimg-amd64.img"
INFO[0014] Attempting to download the image from "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img"
554.25 MiB / 554.25 MiB [----------------------------------] 100.00% 10.14 MiB/s
INFO[0071] Downloaded image from "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img"
INFO[0073] [hostagent] time="2021-09-03T11:24:45+02:00" level=fatal msg="stat /Users/max/.ssh/ed25519_sk: no such file or directory"
FATA[0073] host agent process has exited: exit status 1

Workaround
Create empty ed25519_sk file:
touch ~/.ssh/ed25519_sk

Thanks for reporting.
Seems duplicate of #182, fixed in https://github.com/lima-vm/lima/pull/184.
The fix will be included in v0.6.2 (perhaps next week)


Cannot find bash history

As the title says it cannot find the history.
Failed to import current history. The following exception occured: <class 'ValueError'>: /root/.shell_history/history: no such file
I am running Raspbian GNU/Linux 9 (stretch)
Any idea how to solve it?

Woohoo first issue :tada: ! Thanks for your interest :smile: !
A few questions:

is bash the default shell on your distro?
did you load shell history by sourcing the file (as mentioned in readme)? is it sourced each time you start bash?
does /root/.shell_history/history file actually exist?
what command did you use to run the web application?

To check if shell history is enabled, simply enter set -x in your shell. You should see all the instructions run by shell history. Deactivate this mode with set +x.
All this is a bit wonky, sorry :confused: I plan on improving installation process and robustness.

I am using bash, and inserted . '/home/pi/git/shell-history/shellhistory.sh' into /root/.bashrc.
ls: cannot access '/root/.shell_history/history': No such file or directory
/root/.shell_history/db --> exists
-rw------- 1 root root 18K Oct 12 21:48 /root/.bash_history --> exists
root@sont:~# set -x
root@sont:~# set +x
+ set +x
root@sont:~# set -x

This is everything i found.

Ah, maybe you just forgot to add shellhistory enable after . '/home/pi/git/shell-history/shellhistory.sh' in .bashrc?

I found your project really awesome. I love visualization!

Thanks a lot! Yeah I love visualization too, transforming some raw data in useful/meaningful graphics :grin:

Nope, I've added it. :(

Sorry for the delay.
Here is how I use shell-history myself:
shopt -s histappend

export HISTSIZE=-1

. "/path/to/shellhistory/shellhistory.sh"
shellhistory enable

Could you try to set histappend and HISTSIZE like above?

Also, what version of Bash do you have? bash --version

Still no result 😞
GNU bash, version 4.4.12(1)-release (arm-unknown-linux-gnueabihf)

Hi @sontqq!
I just packaged the application using Poetry, and pushed a release to PyPI.
Could you try again with the new version?
The default directory is now ~/.shellhistory instead of ~/.shell_history. If you don't have a history file yet, you can simply delete the old database and directory, as the new one will be automatically created.
On my side I will try to see if I can launch a Raspbian docker container to see if it works.

Just finished testing on a Raspbian VM, it seems to work fine.

No updates, closing :slightly_smiling_face:


Deployment failed "PrincipalNotFound"

Simple deployment without an application randomly fails:
{
"status": "Failed",
"error": {
"code": "PrincipalNotFound",
"message": "Principal c936aacc547d4cdbbbb73e31fba068e7 does not exist in the directory 9ef060d3-1c7d-47f0-ae5e-3be36d7ba188."
}
}

It looks like the random failure is caused by the timing issue, which means the service principal is created asynchronously, see https://stackoverflow.com/questions/35172941/azuread-powershell-new-azurermroleassignment-keeps-failing.

I also asked question in Microsoft internal StackOverflow: https://stackoverflow.microsoft.com/questions/299178.

When I verified the new release after rolling out https://github.com/WASdev/azure.liberty.aro/pull/78, the deployment failed with the following error messages:
{
      "code": "InvalidPrincipalId",
      "message": "A valid principal ID must be provided for role assignment."
}

I think the root cause is similar that the service principal is created asynchronously, and we need to wait a while until it's available.


Add block and epoch roots to JMT

Is your feature request related to a problem? Please describe.
When fuzzy message detection happens, we'll want a way to efficiently stream just epoch roots or just block roots for the portions of the chain which aren't relevant to the fuzzily detected results. Right now, the only thing we could do is stream entire compact blocks, which uses unnecessary bandwidth.
Describe the solution you'd like
We should add two new families of keys to the shielded pool storage: shielded_pool/block_root/{block_height} and shielded_pool/epoch_root/{epoch_index}, and populate them during EndBlock commit of the CompactBlock.
This part should happen before mainnet launch, because it's consensus state.
Then, at some later time (possibly in same PR but could be whenever) we can add new gPRC streaming methods to fetch streams of these roots in particular specified ranges, modeled after the compact block streaming query.
Describe alternatives you've considered
The only alternative I can see is to do nothing, which means that we would be forced to stream entire compact blocks always, or to add a non-authenticated sidecar storage area for this data, which could happen whenever, but loses the ability to have a network-efficient authenticating light client that uses FMD.

After discussion with @hdevalence: we should also include bidirectional reverse lookups for these two, like shielded_pool/block_root_height/{block_root} and shielded_pool/epoch_root_index/{epoch_root}, mapping to the block height and epoch index of those block and epoch roots, respectively. These can be maintained at the same place in the code as their inverses.


There should be no _bound_members before a Traversable is actually bound

Codecov Report

Merging #61 into master will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #61      +/-   ##
==========================================
+ Coverage   99.14%   99.23%   +0.08%
==========================================
  Files          62       62
  Lines        8188     8852     +664
==========================================
+ Hits         8118     8784     +666
+ Misses         70       68       -2

Impacted Files
Coverage Δ

iommi/endpoint.py
98.24% <100.00%> (ø)

iommi/member.py
97.65% <100.00%> (+0.01%)
:arrow_up:

iommi/table__tests.py
100.00% <100.00%> (ø)

iommi/traversable.py
96.74% <100.00%> (ø)

iommi/base.py
100.00% <0.00%> (ø)

iommi/table.py
98.86% <0.00%> (+0.34%)
:arrow_up:

iommi/form.py
99.90% <0.00%> (+0.45%)
:arrow_up:

Continue to review full report at Codecov.

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


Fixie sometimes fails parameterized tests with "chunkLength" error

I understand this is a bit vague, but I am hoping that an extra pair of eyes (that is familiar with this tool's architecture) could spot a reason in which the following failure(s) could start occurring.
Steps to Reproduce
I am not certain how to reproduce this, as we cannot (as of yet) identify why this started happening, and it is a "flaky" behavior in that it seems to sometimes work (with different build agents under different use pressures?) Our use of Fixie for L1 tests in an Azure DevOps YAML pipeline has been pretty stable.
While I am hopeful of a fix, I realize this is a "long shot". I am probably not able to provide enough detail to reproduce and identify the problem because:

The "flaky" and "emerging" nature of the failures (They only recently started failing, and fail about 70% of the time)
The proprietary context in which it exhibits (I cannot share the full context/code of the issue)
The failure does not occur locally (where I could debug myself) but only in a YAML pipeline hosted in Azure DevOps. (All local runs succeed)
This may all be a function of the very specific kind of tests (DB/DataLayer L1s) and the custom execution implementation involved (that I am not at liberty to disclose)
This could simply be masking some internal error that, when reported up to fixie, does so in an unexpected way and breaks the reporting mechanism.

Expected Behavior
Continued reliable execution of tests (that had worked fine up until some shift in code/nuget/version/agent/?).
Actual Behavior
Parameterized tests all fail with the same Exception:
Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'chunkLength')

and callstack:
System.ArgumentOutOfRangeException
at System.Text.StringBuilder.ToString()
at Fixie.Internal.ExecutionRecorder.Pass(Test test, String name)
at Fixie.Test.RunCore(Object instance, Object[] parameters)
at OurCustomExecutionImplementation...

Thanks for your time and consideration...I will continue to attempt small shifts on my side to see if I can force more context, but I am hoping that there may be a flash of insight that might help solve this.

Unfortunately you are likely facing Fixie v3's biggest flaw, one that will hopefully go away in v4 as a breaking change. Unfortunately, for reasons I get at in #262 I won't be entertaining PRs for it, and won't be getting specific about time frame: I don't mean to be rude, just realistic.
What I write below, then, is about giving you some context in the hopes it lets you better troubleshoot what all might have changed recently to provoke Fixie's preexisting flaw, and to hopefully work around it.
This likely is not about parameterization, but instead about the consequences of the way Fixie attempts to capture the console's standard-out stream in the presence of multiple threads.
In an attempt to capture console writes that occur during test runs, the original "real" standard output TextWriter is wrapped very early in Fixie's execution, so that when your test or the system under test writes to System.Console.Out, we get an opportunity to also accumulate that text into a hidden StringWriter for inclusion in the per-test-result reporting. Usually this works out just fine, since the Fixie test runner itself is single-threaded, the default convention and all example custom conventions in the docs are single threaded, and the careful "mutable state juggling" we do as we move from one test to another seemed to be safely written in terms of a single apparent thread.
If you recently changed your custom IExecution to itself kick off multiple threads, such as attempting to run two tests at the same time, then that is unfortunately not supported in v3 for multiple reasons including this console capture problem.
For the rest of this comment, I'll assume your IExecution itself is not "doing thread things" itself directly.
Then the most likely thing that is going on is that some other thread is writing to System.Standard.Out at an unfortunately inconvenient time. Your stack trace strongly suggests this. Fixie's convinced it's a safe moment to take the underlying StringBuilder and call ToString() on it, but in fact some other thread is writing to System.Standard.Out around the same time, which in turn is getting appended into the underlying StringBuilder, and StringBuilder naturally isn't able to safely manage its own private state being hit like that from multiple threads.
There's a chance your test code is writing explicitly from some background thread it kicked off, or else your system under test is doing that, or else something more sneaky is going on. The first time someone reported this to me, in their case they started encountering the problem whenever they opted into some Entity Framework logging feature... presumably EF was offloading some of its own logging feature to a secondary thread it had kicked off; perfectly reasonable but revealing of Fixie's own assumptions. I suppose any logging framework might be doing a similar offloading of standard output writes to another thread.
If the console writes are coming direclty from your test code, you might instead write to the Console property of the TestEnvironment that I pass to your ITestProject. This console property is the real original value of System.Console.Out without the flawed wrapper involved, and is in fact what I write to in all the reporting infrastructure when a report needs to really write something to the user-facing console they ran dotnet fixie from.
The only reason I even bothered to capture console output was that some reporting sinks like Azure DevOps and the VS Test Explorer UI allow such output to be reported per test case. If you don't care about witnessing that in reports, you might try to "hit this problem with a sledgehammer" by redirecting standard out (this time, away from my flawed wrapper) very early in your IExecution.Run(...) method:
using TextWriter throwAwayConsole = new StringWriter();
System.Console.SetOut(throwAwayConsole);
// Reports won't show anything useful for the console output of individual
// test results, but at least we get the bug out of the way.

It would be even better, though, to take the TestEnvironment passed to your ITestProject, pass it into your IExecution, and then in IExecution.Run(...) do the following:
System.Console.SetOut(environment.Console);
// Again reports won't show console capture per-test-result, but at least all console output will actually go
// to the console, and could for instance appear in a CI log where you see `dotnet fixie` being invoked.

I hope this helps!

Indeed, it does help. And no worries about being frank on timeline/etc. I am a huge fan of this project, and the work you have done is excellent...It has already allowed me to build out some very interesting automated testing scenarios, and I am grateful for the project and the work you have already poured into it.
The thing you said about sneaky / opt in logging...especially around EF Core may well be the clue I needed. One of the moving pieces on our side was a move to EFCore 7.0, which may indeed have shifted what gets logged and how.
Your description of what you are doing to capture output and the perils involved helps me look into what sort of thing could be destabilizing. Thanks for your time and consideration. It is much appreciated.
I am closing this. Not only is your response an actionable hint, but also this is probably more a question/guidance inquiry than a "bug". I would have labeled it as such if I could have figured out how to do so.
Regards,
Elliott


Screencast: enable validation and color picker for screencastMode.mouseIndicatorColor

Testing #105721

open the JSON settings, add "screencastMode.mouseIndicatorColor": "#ff00ff"
-> there's no color decorator or color picker as for other colors
change the value to ff00ff: No error shown

You all get that by adding "format": "color-hex" to the setting configuration. But css color names (red, ...) are not supported by that.
As other color settings don't support the css names either, I suggest to only support hex for consistency reasons.

Excellent. Now you can use Color.fromHex to read (and verify) the settings value and color.toString to get the CSS string. Right now 'blue' would still work


spike: Investigate TC command mapping in executor

Overview
This ticket covers the research needed to be done to determine the scope of the executor work for TC.
Implementation details
Investigate mapping of the following api calls:

[ ] openLid
[ ] closeLid
[ ] activateLid
[ ] deactivateLid
[ ] activateBlock
[ ] deactivateBlock
[ ] runProfile

Acceptance criteria

Clear path forward for beginning executor work.
Reach consensus about blocking/non blocking behavior and ability to pivot in the future.

How to error out when unsupported asynchonous behaviors are specified in protocol commands
The language of the v4 JSON TC commands is async with "setX" and "awaitX" vocabulary (except for open/close lid which is sync. However, API and TC hardware itself currently only support sync TC temperature commands.
When an await immediately follows an async set, it's equivalent to a sync set. Eg, thermocycler/setTargetLidTemperature + thermocycler/awaitLidTemperature = "sync set temp". But if the command immediately after the set isn't a corresponding await command, the protocol has expressed something the executor is not capable of supporting, so the executor needs to throw an error.
Until we want it to do differently, PD will always do set + immediate await for these TC commands. So this guard is only for user-created JSON (or PD bugs? That'd be a pretty bad bug though to mess up the commands array like that)
One way: dispatch_json could first call some has_async_thermocycler_commands(commands) helper fn that returns a boolean, and if that boolean is true, raise a RuntimeError with a human-readable message (targeted at a user making JSON protocols outside of PD, probably?).
thermocycler/setTargetBlockTemperature + thermocycler/awaitBlockTemperature
tc.set_block_temperature(temperature). Will block until temp is reached.
SIDE NOTE: I don't think this applies to us, but you can also set and await. tc.set_block_temperature(4, hold_time_seconds=15, hold_time_minutes=45, block_max_volume=50)
thermocycler/setTargetLidTemperature + thermocycler/awaitLidTemperature
tc.set_lid_temperature(temperature). Will block until temp is reached.
thermocycler/runProfile + thermocycler/awaitProfileComplete
profile = [
  {temperature: 10, hold_time_seconds: 30},
  {temperature: 60, hold_time_seconds: 30}]

tc.execute_profile(steps=profile, repetitions=100, block_max_volume=30)

How JSON command params plug into Python fn args:
params.volume can plug into block_max_volume
params.profile maps to steps=profile (we need to change params.profile[i].holdTime to hold_time_seconds, it is seconds just different key name)
repetitions kwarg is not relevant, we just do repetitions in the profile array itself.
thermocycler/deactivateBlock
tc.deactivate_block()
thermocycler/deactivateLid
tc.deactivate_lid()
thermocycler/openLid
tc.open_lid()
thermocycler/closeLid
tc.close_lid()

We should probably do a first pass over the protocol that coalesces commands like that and emits some intermediate command stream, that should handle the problem without having to make dispatch_json stateful

This all looks good and I second Seth's comment.  Keeping the dispatch_json stateless is a good idea.  We may have to do this level of command-order validation in the future, so it makes sense to me to generalize our approach.


Feature Request: Add Total Page Number Option

See this example:
https://github.com/AdeleD/react-paginate#props
Basically your options object would allow a "totalPageNum" or something that would be user-defined. So If your server has 1,000 users, and you show 20 users per page, then you would set "totalPageNum" to 50. Yes your plugin does this automatically IF you get all 1,000 users, but for us using server limits and offsets, I can only get 20 users at a time. So Now I have a table with only 20 users in it, but I need to show the web viewer they have more users to see based on the number of pages available to select (then I use your custom page click callbacks to get users based on the page selected).
With all your features for custom function callbacks and onPageClick call backs, this should already be in your plugin but I can't find it. I can see if I can submit a PR, but not sure how much time I have. Am I missing something and this is already implemented? Just seems an obvious feature to have with this feature-rich library you have.
I think there is some misunderstandings of english terms too, because I see paginationSize but that turns out to REALLY be more of a range of pages to display, not that ACTUAL size of pages to display. I might suggest to change some of that wording around.
I guess I am requesting to be able to override the totalDataSize value, so I can just throw in "1000" and all pages will show according to the other options used (in my example, 50 pages should show up).

After delving into more of the source code and your remote examples, I noticed you do have this feature (I thought you would). Thanks!

@jflayhart, yes, that's what you want :+1:

Im seing remote-paging.js example, but dont know how could implement it.
            <BootstrapTable
              data={rows}
              striped={true}
              remote={true}
              deleteRow={ true }
              selectRow={ selectRowProp }
              options={ this.getOptions() }
              pagination={true}>
              <TableHeaderColumn dataField="id" isKey={true} dataAlign="center" dataSort={true}>ID</TableHeaderColumn>
              <TableHeaderColumn dataField="date" dataSort={true}>date</TableHeaderColumn>
              <TableHeaderColumn dataField="name" dataFormat={ this.dateFormatter } dataSort={true}>Name</TableHeaderColumn>
            </BootstrapTable>
            <RemotePaging
              onPageChange={ this.onPageChange.bind(this) }
              onSizePerPageList={ this.onSizePerPageList.bind(this) }
              { ...this.state }
            />

With import { BootstrapTable, TableHeaderColumn, RemotePaging } from 'react-bootstrap-table';
It should works? Can you give me a working example? Thanks!

hello @luisfuertes, sorry for lately reply. could you please describe your question that will helpful to me to help you?
Anyway, enable the remote prop which means you want to handle the data manipulation(ex: sort, insert, search, filter, pagin  etc.) on your server or flux instead of react-bootstrap-table self. so the example mentioned before, is a simple example which we handle the paging  outside of react-bootstrap-table.
You can check react component and its store to see how it work.
Let me know if you still have any question :)

Thanks for answer.
Yesterday i try did it with this example: https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/remote/remote-store-paging.js
But after i found this other example ( https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/remote/remote-paging.js ) and i can do it works.
But i dont understand how can apply the first example in a real  element.
Only see the < RemotePaging />  in example but dont know how can i use with

But i dont understand how can apply the first example in a real < BootstrapTable /> element.
Only see the < RemotePaging /> in example but dont know how can i use with < BootstrapTable />

RemotePaging is just only a wrapper for BootstrapTable, so in the remote-store-paging.js we render RemotePaging.

Oh ok, thanks for answer @AllenFang


Stake Pool Relays

The stake pool relays (in the pool registration cert) should not be a list of urls. We need to decide what exactly we want and implement it.
In CDDL, we probably want something more like a list of:
relay = [ port: uint / null
        , dnsname: tstr .size (0..64)
        / ipv4: bytes .size 4
        / ipv6: bytes .size 16
        ]

So we've concluded we want something corresponding to this Haskell type
type StakePoolRelays = [StakePoolRelay]
data StakePoolRelay =
     SingleHostAddr (Maybe IPv4) (Maybe IPv6)  -- ^ One or both of IPv4 & IPv6
   | SingleHostName DnsName                    -- ^ An @A@ or @AAAA@ DNS record
   | MultiHostName  DnsName                    -- ^ A @SRV@ DNS record

Oh I forgot to include the optional port number. Each of the three forms of the StakePoolRelay can have an optional port number.
And as above, IPv4 can be a 4 byte bytesting IPv6 size 16, and the dnsname is up to 64 byte text.


Feature Request: Autosuggestions, persistent, history logging

Summary of the new feature/enhancement
Feature Request: autosuggestions, persistent, history logging...
Like https://fishshell.com/

Proposed technical implementation details (optional)

@Chaython Please add more information what you are requesting. It seems the features is already in PSReadline.


Reduce fsm mem

remove the need for transition list definition by defining the resulting transition table directly.
remove redundant information:

id in FsmState, since the index into the FsmState list is the id of the state
curr_state change from a state pointer to a StateId (integer), store the state list in fsm to allow this.
num_transitions from FsmSetting

main:
   text    data     bss     dec     hex filename
  28368    1408   13808   43584    aa40 build/arm/bin/projects/centre_console

reduce_fsm_mem:
   text    data     bss     dec     hex filename
  28296    1452   12952   42700    a6cc build/arm/bin/projects/centre_console

I think if we take transition out, might as well take states and initial state out as well, kinda weird storing only two values in the setting.
fsm_init(fsm, states, transitions, initial_state, context)
but I think adding an assert for transition and state length is definitely good to have.
(even jankier can be that we just not have an initial_state parameter, and just make sure that the first state is the one the fsm starts on. As of rn, all fsm starts with state 0)
as for redundancy for num_transitions, while I was making changes, I found the power had multiple duplicate transitions, so I don't think the num_transitions count is very indicative, best to just keep the transitions organized.


Calendar - setup page

When visiting the site for the first time, the user should see the /setup "new calendar" flow. Once they create a calendar, the main calendar view should present.
Few details need to be ironed out:

Is it possible to animate the faded calendar in?
How do we want the components to be laid out?

Blocked on at least #30, #31 to be implemented first


IN clause suppor (task #9659)

IN clause support in conditions for API "index" endpoint. This will allow passing multiple values for a single column, using the following query string:
/api/leads.json?conditions[name][]=foo&conditions[name][]=bar
Will be converted to the following where clause:
$conditions = [     'Leads.name IN' => ['foo', 'bar'] ];

@eliamariutti it would be great if we could add some tests for this.


Reland "Reland - Introduce tone-based surfaces and accent color add-ons - Part 2"

Reverts flutter/flutter#144262
The Golden diffs have been approved before, it should be safe to land this change now:)

Can you push another commit without a force push so I can double check the goldens?

Can you push another commit without a force push so I can double check the goldens?

Yes! Just pushed some empty commits. Since there was a conflict, so after I solved it, pushed another one.

Ah thanks! Looks like Gold is good here, is the Google testing failure expected?

Ah thanks! Looks like Gold is good here, is the Google testing failure expected?

Yes! Google testing failures are expected:)

Oh weird, the github UI glitched when I submitted.

LGTM!

Thanks!

This caused an application I'm working on to change color, from:

...to:

...and I can't figure out what value to pass to ColorScheme.fromSeed to get the old colors.
Was that intentional?

I have some questions about the ColorScheme upgrade.
In the latest version, I saw that background and onBackground were removed. In my project, I use it to define the background color of the page or card, without using surface and onSurface. Because onSurface is used in the system's built-in long-press popup option.
There are some other similar situations, but not many. For such situations, I generally avoid using this attribute.
In the latest version, background and onBackground have been removed. For me, I can only use surface and onSurface, but onSurface is occupied by the system. Do you have any good suggestions for this problem?

I have some questions about the ColorScheme upgrade. In the latest version, I saw that background and onBackground were removed. In my project, I use it to define the background color of the page or card, without using surface and onSurface. Because onSurface is used in the system's built-in long-press popup option. There are some other similar situations, but not many. For such situations, I generally avoid using this attribute. In the latest version, background and onBackground have been removed. For me, I can only use surface and onSurface, but onSurface is occupied by the system. Do you have any good suggestions for this problem?

Hi! We can add color roles by using ThemeExtension! Here's an example showing how we can add more colors in theme:)

I have some questions about the ColorScheme upgrade. In the latest version, I saw that background and onBackground were removed. In my project, I use it to define the background color of the page or card, without using surface and onSurface. Because onSurface is used in the system's built-in long-press popup option. There are some other similar situations, but not many. For such situations, I generally avoid using this attribute. In the latest version, background and onBackground have been removed. For me, I can only use surface and onSurface, but onSurface is occupied by the system. Do you have any good suggestions for this problem?

Hi! We can add color roles by using ThemeExtension! Here's an example showing how we can add more colors in theme:)

Great, thank you very much!


ChromeDriver Zombie Processes

Issue
Running wallaby on elixir with chromedriver is leaving zombie processes.
We're running the application from within a docker instance.
Test Code & HTML
The following code:
use Wallaby.DSL
import Wallaby.Query
{:ok, s} = Wallaby.start_session()
try do
...
after
Wallaby.end_session(s)
end
Is executed every 30 minutes, using a Quantum Job on Elixir. After every execution we're left with zombie processes:
HOST MACHINE:
❯❯❯ ps -ef | grep chrome
root      5170  5155  0 18:11 ?        00:00:00 /bin/sh /opt/app/lib/wallaby-0.20.0/priv/run_command.sh /usr/bin/chromedriver --port=59649
root      5172  5170  0 18:11 ?        00:00:00 /usr/bin/chromedriver --port=59649
root      6225  4881  0 18:30 ?        00:00:00 [chrome] <defunct>
root      6258  4881  1 18:30 ?        00:00:03 [chrome] <defunct>
DOCKER INSTANCE:
244 root       0:00 {run_command.sh} /bin/sh /opt/app/lib/wallaby-0.20.0/priv/run_command.sh /usr/bin/chromedriver --port=59649
246 root       0:00 /usr/bin/chromedriver --port=59649
263 root       0:00 [chrome]
292 root       0:03 [chrome]
DOCKER INSTANCE ENVIRONMENT:

Elixir version 1.6.4.
Erlang 20.3
/opt/app # apk info chromium-chromedriver
chromium-chromedriver-61.0.3163.100-r0 installed size: 13455360
/opt/app # apk info chromium
chromium-61.0.3163.100-r0 installed size: 217829376

After fiddling around on alpine, the $(ps pid,pgid | ...) command doesn't return the same as within the host.
Problem is with running this on docker instance from alpine.


Mirgrate from pip to uv

In order to improve build time performance, this change switches usage of pip to uv. The uv command is a pip alternative promising much faster installs of Python packages.
For more information on uv, see:
https://github.com/astral-sh/uv
Closes #2748
All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

New Feature Submission:

[x] Does your submission pass the tests?
[x] Have you linted your code locally prior to submission?

Changes To Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?

After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

I've compared the execution time to other PRs that don't use uv yet, but I don't find any significant improvement on the runtime of jobs.
However, I think we can still go ahead with this PR anyway.

I've compared the execution time to other PRs that don't use uv yet, but I don't find any significant improvement on the runtime of jobs.
However, I think we can still go ahead with this PR anyway.

Yeah, I didn't see much of a performance boost. I suspect its probably because poetry is installing most of the dependencies.


Release to Central

Summary

Decide correct groupId and get permission https://github.com/wiremock/community/issues/55
Use correct package in the code
Update README with that groupId

Which repo should I use seems like  testImplementation "org.wiremock.spring:wiremock-spring-boot:X" has no effect to me. Exact version also is not helping here.

It is not yet released.
Here is the old readme:
https://github.com/wiremock/wiremock-spring-boot/tree/v2.1.3

https://repo1.maven.org/maven2/org/wiremock/integrations/wiremock-spring-boot/


Add NorthKerbinDynamics

http://spacedock.info/mod/214
http://forum.kerbalspaceprogram.com/index.php?/topic/118667-wip10x-north-kerbin-dynamics-nuclear-bombs-and-heavy-ordnance-pack-and-other-things-06/

Looks all fine as far as I can see, and Jenkins is happy. Merging!


object type in activity settings should not be nested under mapping

Environment
How are you running Flogo Web?

[X] Docker (Specify the docker image that you're using and the command you used to start the container)
[ ] Other (Provide details of your environment)

Describe the bug
A clear and concise description of what the bug is.
When a variable in activity settings is of type object or array, and configured as, e.g., { "key": "mykey", "attributes": ["x", "y"]}, this configuration is exported as nested under "mapping" in the app's json file.  Since the settings are not object mappings, it should be exported as the configure object as is, similar to what it does for trigger handler settings.
How has this issue affected you? What are you trying to accomplish?
In my implementation of an activity that requires more complex configurations than simple primitive type variables, I would have to manually remove the wrapper of "mapping" in code for any config variable of object/array type.  This would not be necessary if Web UI can export the settings without the nested "mapping" wrapper.
Providing context helps us come up with a solution that is most useful in the real world
To Reproduce
Steps to reproduce the behavior:

define a new activity, and in descriptor.json, add a variable of object or array type under settings.
use the activity in a model, and configure the variable in WebUI
export the model, you should see that the configured setting contains an extra wrapper under "mapping"
If in the activity implementation, you use the common function call to extract the configured object, such as metadata.MapToStruct(ctx.Settings(), settings, true).  The call will fail, because you have to manually remove the nested "mapping".

Include error logs if applicable.
Expected behavior
export the app model without the extra nesting of "mapping" for activity settings.
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Possible Solution
Not obligatory, but suggest a fix/reason for the bug,
or ideas how to implement the addition or change
Additional context
Add any other context about the problem here.

The UI assumes that Flogo allows the use of mappings in the activity settings. It seems that's not case and the UI should prevent the "mapping" wrapper from happening. So definitely a bug.
The other issue here is that the UI is always wrapping objects with the "mapping" props in the inputs section. And although the wrapper doesn't hurt for inputs, it is unnecessary when the object is static. Fixing that will require some work in the mappings parser so the parser can expose when an object is static or not.

I agree that the nesting of "mapping" does not seem necessary even for inputs.  I noticed that the Flogo OSS and Enterprise export/import trigger/activity settings differently.  OSS actually handles settings and handler-settings better than FE when configured attributes are JSON objects.  FE cannot import complex trigger settings, FE also requires fe_metadata for complex activity settings, while fe_metadata is not a standard core metadata attribute.  So, I had to write code to convert models between OSS and FE models to support both UIs.  I hope that these 2 UIs can get in sync on handling JSON objects in trigger/activity configurations.

I agree that the nesting of "mapping" does not seem necessary even for inputs.  I noticed that the Flogo OSS and Enterprise export/import trigger/activity settings differently.  OSS actually handles settings and handler-settings better than FE when configured attributes are JSON objects.  FE cannot import complex trigger settings, FE also requires fe_metadata for complex activity settings, while fe_metadata is not a standard core metadata attribute.  So, I had to write code to convert models between OSS and FE models to support both UIs.  I hope that these 2 UIs can get in sync on handling JSON objects in trigger/activity configurations.

As noted in Gitter, there are exceptions to the mappings in settings. The "return" type activities do support the mappings in settings so the UI should still support using those in settings for actreply, actreturn and mapper activities.

As noted in Gitter, there are exceptions to the mappings in settings. The "return" type activities do support the mappings in settings so the UI should still support using those in settings for actreply, actreturn and mapper activities.


Add support for sending MQTT messages to Azure IOT Hub

Some custom config will be needed to handle authentication.

Won't do for now. Added support for Azure Event Grid instead.


Not working in Xcode 7.3 - swift project - pod installation

Hi,
I have used Xcode 7.3 and added QMServices using pod as below
pod 'QMServices', '~> 0.4'

The project is swift - uses most of swift files and few objective c files.
So while importing QMServices in bridging header, it gives error that file not found.
 #import <QMServices.h>
Also tried with importing below statement but no luck
#import "QMServices.h"
Not sure what could be the problem.

Even I'm facing same issue with pod 'QMServices'. Can someone help us.

I have added header search path from private directory to solve this issue
On Wednesday 19 October 2016, sushmithaGope<EMAIL_ADDRESS>wrote:

Even I'm facing same issue with pod 'QMServices'. Can someone help us.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QuickBlox/q-municate-services-ios/issues/272#issuecomment-254732469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH_TrCl9iPZUgBv8VbiVq3-D4WXWehAHks5q1cSPgaJpZM4KVx9M
.

Hi,
Actually, I'm able to run the project with out errors in New Xcode Project
by using below steps
$ git submodule add https://github.com/QuickBlox/q-municate-services-ios.git
Vendor/QMServices
$ git commit -m "Added QMServices submodule"
also in pod file I used pod 'QMServices'
So, it is working fine.
But when I use same steps in existing project, it is not working.
I’m getting error at this line
#import "QMServices.h" QMServices file not found.
I also tried installing QMservices once by only using pod ‘QMServices’ and once only by $ git submodule add https://github.com/QuickBlox/q-municate-services-ios.git
Vendor/QMServices
Either I’m getting QMServices file not found OR Redeclaration/duplicate errors in many files (like QMDBStorage.h)
Can you please help me to solve this issue.

Hi @phiren and @sushmithaGope
@phiren If you are still having any other troubles, please let us know by creating a separate issue.
@sushmithaGope I have answered you in your issue, lets continue it there.

See my initial comment, you have to add header search path for QMservices.
There is some prb with the pod, it does not add header search path for
QMservices. Also those headers not in public folder , only in private
folder. So give path to private folder. If you have other working pods too,
then see how header search path was added for those library, it just not
add path of QMServices, not sure what's wrong with the pod.
Thanks
On Thursday 20 October 2016, sushmithaGope<EMAIL_ADDRESS>wrote:

Hi,
Actually, I'm able to run the project with out errors in New Xcode Project
by using below steps
$ git submodule add https://github.com/QuickBlox/
q-municate-services-ios.git
Vendor/QMServices
$ git commit -m "Added QMServices submodule"
also in pod file I used pod 'QMServices'
So, it is working fine.
But when I use same steps in existing project, it is not working.
I’m getting error at this line
#import "QMServices.h" QMServices file not found.
I also tried installing QMservices once by only using pod ‘QMServices’ and
once only by $ git submodule add https://github.com/QuickBlox/
q-municate-services-ios.git
Vendor/QMServices
Either I’m getting QMServices file not found OR Redeclaration/duplicate
errors in many files (like QMDBStorage.h)
Can you please help me to solve this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QuickBlox/q-municate-services-ios/issues/272#issuecomment-255093604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH_TrHGhNblhVMYopP9VsW4i-5gdnmUtks5q12BigaJpZM4KVx9M
.


I am confused by the discussion of how to reference variables defined in one job in another job

In the discussion of libraries and variables, there is an example of how to reference a variable defined in one job in a subsequent job.  The example is:
- job: A
  steps:
  - task: MyTask@1  # this step generates the output variable
    name: ProduceVar  # because we're going to depend on it, we need to name the step
- job: B
  dependsOn: A
  variables:
          # map the output variable from A into this job
    varFromA: $[ dependencies.A.outputs['ProduceVar.MyVar'] ]
  steps:
  - script: echo $(varFromA) # this step uses the mapped-in variable`

I see where ProduceVar comes from.  I see where A comes from.  varFromA makes sense to me.
But where does MyVar come from?  Is dependencies a keyword or an identifier.  If an identifier, then what does it identify?
[Enter feedback here]

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

ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
Content: Define variables - Azure Pipelines
Content Source: docs/pipelines/process/variables.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

dependencies is a keyword. I agree the example is unclear - there's a comment hinting that a task produced that variable, but it's easy to miss. It would be clearer if I'd said:
jobs:
- job: A
  steps:
  # assume that MyTask generates an output variable called "MyVar"
  # (you would learn that from the task's documentation)
  - task: MyTask@1
    name: ProduceVar  # because we're going to depend on it, we need to name the step
- job: B
  dependsOn: A
  variables:
    # map the output variable from A into this job
    varFromA: $[ dependencies.A.outputs['ProduceVar.MyVar'] ]
  steps:
  - script: echo $(varFromA) # this step uses the mapped-in variable


Reproduce "Melting of PCM" benchmark from danaila2014newton

We've successfully tested the basic capability in issue #14, but it still may be difficult to obtain a solution for the exact parameters from danaila2014newton.

Reducing r to 0.005 (from 0.05) makes the Newton method rapidly diverge.

I was able to converge one time step of the melting octadecane PCM benchmark here: https://github.com/geo-fluid-dynamics/phaseflow-fenics/tree/benchmark/melting_octadecane_pcm
There are some deficiencies:

It required about 150 Newton iterations, and changing the initial mesh refinement or time step size makes the Newton solver blow up.
Using a regularization smooth factor, r, smaller than around 0.05 makes the Newton solver blow up.
The error is being estimated already below 1.e-4 with the initial grid (refined near the hot wall), and so no adaptive mesh refinement is being performed, and so the error is not being controlled as time goes on. Setting the tolerance to 1.e-5 ends up refining every cell, which then does not converge.
A second time step can also converge given enough Newton iterations, but convergence behavior only gets worse (because the mesh is not being adaptively refined).

Maybe relaxing the Newton solver would do the trick, since this has seemed to handle rapid divergence pretty well before. I added issue #154 for this.

So far relaxing the solver isn't helping.

In this lid-driven cavity example, the metric u[0]*fenics.dx was not useful, while u[0]*u[0]*fenics.dx worked very well. So maybe I just need to get more creative with the metric for this melting case.

I just noticed that when solving the nonlinear variational problem, a Krylov solver is being mentioned, e.g.

Solving nonlinear variational problem.
Newton iteration 0: r (abs) = 1.817e+01 (tol = 1.000e-08) r (rel) = 1.000e+00 (tol = 1.000e-04)
Solving linear system of size 8244 x 8244 (PETSc LU solver, umfpack).
PETSc Krylov solver starting to solve 8244 x 8244 system.
Newton iteration 1: r (abs) = 1.182e-02 (tol = 1.000e-08) r (rel) = 6.507e-04 (tol = 1.000e-04)
Solving linear system of size 8244 x 8244 (PETSc LU solver, umfpack).
PETSc Krylov solver starting to solve 8244 x 8244 system.
Newton iteration 2: r (abs) = 1.146e-03 (tol = 1.000e-08) r (rel) = 6.306e-05 (tol = 1.000e-04)
Newton solver finished in 2 iterations and 2 linear solver iterations.

This is perplexing. I began exploring this in issue #156 .
Having had no luck pinpointing this problem yet, I think it's about time I try making a minimal script that solves the melting octadecane PCM benchmark (without Phaseflow). If the new script also somehow invokes a Krylov method, then maybe that will get me closer to a MWE that reproduces the issue.

At this point, I think I should verify the coupled problem with MMS before getting too worries about the benchmark case not working. Maybe my implementation is wrong.


Consistency in directive/component selectors

Bug, feature request, or proposal:
I'm not sure what it's. Maybe a proposal?
What is the expected behavior?
Maybe explain why some selectors are camelCase and others not?
What is the current behavior?
Currently there are kebab-case selectors, such as: md-button, md-icon-button and selectors in camelCase:  mdInput, mdPrefix, mdSuffix.
I'm just wondering about the standard here. Why not make everything kebab-case or camelCase? Is there any reason behind the scenes?

Still about consistency, currently we use the native input (for inputs type text, number, etc.), native textarea and native button with their respective directives, but... for inputs type radio, checkbox, "slide-toggle" and also for select, option, etc, we have to use a, let's call it, non-native way. Have you ever considered allowing us to use the native elements for them also?
As an example, for radio, we could have something like:

  <input type="radio" name="rad" value="0" md-ratio-button>0
  <input type="radio" name="rad" value="1" md-ratio-button>1

IIRC the plan is to use kebab-case for component selectors and camelCase for directives. Unfortunately I can't find where I read that - this is the best I found https://github.com/angular/material2/issues/2636#issuecomment-272507135

@andrewseguin is already in the middle of making sure all of the selectors are consistent.
It is true that @Component selectors are dash-case and @Directive is camelCase... with a couple of caveats:

Some @Directives pretend to be components (e.g., they would be a @Component but don't have a template)
Some directives have both an element selector (which must be dash-case) and an attribute selector.

For consistency as a developer using the angular material framework, why does it matter if it is a component or a directive?  That's an implementation detail most user's won't care about.  Isn't what matters when you are writing html code is weather or not it is an element or an attribute?
  <button md-button [mdMenuTriggerFor]="optionMenu">Menu</button>   <md-menu #optionMenu="mdMenu">     <button md-menu-item (click)="option1()">Option 1</button>     <button md-menu-item (click)="option2()">Option 2</button>   </md-menu>
It feels like md-button should be mdButton, and md-menu-item should be mdMenuItem.
Also, md-list-item is a component with selector 'md-list-item, mat-list-item, a[md-list-item], a[mat-list-item]'.  Wouldn't this fit into the developer mindset better as:
'md-list-item, mat-list-item, a[mdListItem], a[matListItem]'?

In my humble opinion, I think everything should be consistent regardless if it's a component or a directive. Otherwise, it would be very confusing.

In 2.0.0-beta.10, there is a deprecation notice for dash-case directives, it it isn't linked to any document explaining why:

All dash-case @Directive selectors are deprecated in favor of the camelCase equivalent. The
dash-case selectors will be removed in a subsequent release. Some examples include:

And you find comments like this throughout the repository issues and PRs:

https://github.com/angular/material2/issues/6720#issuecomment-326012361

The picture is incomplete:

there are directives that can only have HTML attribute selectors, like the ones that style the native <button> tag; this is because you can not fully replace the native button tag
there are cases with no clear guidelines on what to do.

For example, take a look at the card module, you have directives that have different kind of selectors:

MatCardContent, MatCardFooter, MatCardActions, etc --  that can only be used as HTML tags
and MatCardTitle, MatCardSubtitle -- that can also be used as a HTML attributes.

There should be some clear guidelines on how to choose between using an HTML attribute and an HTML tag or between @Component and @Directive decorators... and then you have dash-case vs camelCase and all those other exceptions for the <form> and related elements. Some guidelines should be written in a document somewhere and have people discuss about them (in public).
@jelbourn, are there publicly available notes from discussion that you talk about in the linked comment?

Realted: #3125


Support for blockly dropdown images in packages

Blockly supports dropdown images. We currently have support for these images for targets, but no support for packages.

Not supported for packages.


Support for meteor test command

I forked this and merged into my master. :) Working great for me so far.

Hey there! I tried to use this with<EMAIL_ADDRESS>and
<EMAIL_ADDRESS>practicalmeteor:chai

but i get this error when running spacejam test:
I20160328-13:31:49.952(2)? MochaRunner.runServerTests: Starting server side tests with run id Eq5baL8oDyXdnTZFY
W20160328-13:31:49.956(2)? (STDERR) MochaRunner.runServerTests: failures: 0
Exception from Tracker recompute function:
AssertionError: expected undefined to be a function
    at http://localhost:4096/packages/practicalmeteor_chai.js?hash=8fb9a4aa7055fa02f8b35e05fb1f05c8787c8a46:900
    at an (http://localhost:4096/packages/practicalmeteor_chai.js?hash=8fb9a4aa7055fa02f8b35e05fb1f05c8787c8a46:1131)
    at assert (http://localhost:4096/packages/practicalmeteor_chai.js?hash=8fb9a4aa7055fa02f8b35e05fb1f05c8787c8a46:3981)
    at ClientServerReporter (http://localhost:4096/packages/practicalmeteor_mocha.js?hash=81215895bcf916ea0cbd4f49d1218662f8ea051e:463)
    at http://localhost:4096/packages/practicalmeteor_mocha.js?hash=81215895bcf916ea0cbd4f49d1218662f8ea051e:2508
    at http://localhost:4096/packages/practicalmeteor_mocha.js?hash=81215895bcf916ea0cbd4f49d1218662f8ea051e:6920
    at http://localhost:4096/packages/practicalmeteor_mocha.js?hash=81215895bcf916ea0cbd4f49d1218662f8ea051e:366
    at http://localhost:4096/packages/tracker.js?hash=b267c37effdf4af331d16fc647c0370c2eaff44d:341
    at http://localhost:4096/packages/tracker.js?hash=b267c37effdf4af331d16fc647c0370c2eaff44d:360
    at http://localhost:4096/packages/tracker.js?hash=b267c37effdf4af331d16fc647c0370c2eaff44d:499
    at onGlobalMessage (http://localhost:4096/packages/meteor.js?hash=ec96c6f2d27fb027b17df77301967ce893b45963:391)
spacejam: phantomjs exited with code: 0
spacejam: killing meteor
spacejam: meteor killed with signal: SIGTERM
spacejam: All tests have passed. Exiting.

@DominikGuzei Please try the following:
meteor add<EMAIL_ADDRESS>spacejam test --mocha

You removed the file src/phantomjs-test-in-console.coffee on your branch refactor.
Maybe create a new folder containing phantomjs scripts ?

Would love to see this merged in and have another console logging option available.  Using practicalmeteor:mocha-console-runner and dispatch:mocha-phantomjs with the meteor test command has been unreliable so far.

Any news on this? Not being able to test properly on my CI is quite a pain.

SWEET
Thank you, thank you!

As I expected, travis can't run bin/spacejam, it throws this error:
	npm install -g https://github.com/practicalmeteor/spacejam/tarball/master coveralls
	spacejam test            --loglevel debug --driver-package=practicalmeteor:mocha-console-runner --coverage
	module.js:340
	throw err;
	^
	Error: Cannot find module '../lib/log'
	at Function.Module._resolveFilename (module.js:338:15)
	at Function.Module._load (module.js:280:25)
	at Module.require (module.js:364:17)
	at require (module.js:380:17)
	at Object.<anonymous> (/home/travis/.nvm/v0.10.40/lib/node_modules/spacejam/bin/spacejam:3:1)
	at Module._compile (module.js:456:26)
	at Object.Module._extensions..js (module.js:474:10)
	at Module.load (module.js:356:32)
	at Function.Module._load (module.js:312:12)
	at Function.Module.runMain (module.js:497:10)
	The command "spacejam test --loglevel debug --driver-package=practicalmeteor:mocha-console-runner --coverage" exited with 8.

You can find the entire log here: https://travis-ci.org/serut/meteor-coverage-app-exemple/builds/134144135
Node try to require the file ../lib/log.js and not the file ../lib/log.coffee. This is exactly this use case: https://stackoverflow.com/questions/4768748/requireing-a-coffeescript-file-from-a-javascript-file-or-repl
Please integrate my pull request https://github.com/practicalmeteor/spacejam/pull/57 that fix this issue.


chroot update (and subsequent reinstall) not completed

this is the final section of the screen at reinstall (after a failed update) ARM 7l Samsung Chromebook. Trusty was running nicely for months until now. Ideas?
  patch
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 80.5 kB of archives.
After this operation, 183 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main patch armhf 2.7.1-4ubuntu2.3 [80.5 kB]
Fetched 80.5 kB in 0s (122 kB/s)
Selecting previously unselected package patch.
(Reading database ... 13881 files and directories currently installed.)
Preparing to unpack .../patch_2.7.1-4ubuntu2.3_armhf.deb ...
Unpacking patch (2.7.1-4ubuntu2.3) ...
Setting up patch (2.7.1-4ubuntu2.3) ...
patch set to automatically installed.
Compiling CRAS (native)...
common/cras_config.c: In function 'cras_config_get_system_socket_file_dir':
common/cras_config.c:16:9: error: 'CRAS_SOCKET_FILE_DIR' undeclared (first use in this function)
  return CRAS_SOCKET_FILE_DIR;
         ^
common/cras_config.c:16:9: note: each undeclared identifier is reported only once for each function it appears in
common/cras_config.c:17:1: error: control reaches end of non-void function [-Werror=return-type]
 }
 ^
cc1: all warnings being treated as errors
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...
chronos@localhost / $

Please describe your issue
when updating it wouldn't complete the setup of chroot and at subsequent reinstallation AFTER powerwash, I get the same message.
If known, describe the steps to reproduce the issue:
update process and subsequently reinstall process

I should have mentioned that I am on:
Version 52.0.2727.0 dev
Platform 8302.0.0 (Official Build) dev-channel daisy
Firmware Google_Snow.2695.117.0
and using the latest crouton version:
Chromium OS Universal Chroot Environment https://goo.gl/fd3zc

all of this while trying to update (then reinstall Trusty) with targets xfce and core.

OKay I see it's a CRAS issue from #2583. What is the solution to this?

Fix was merged, just try again. (you will want to remove the cache in /tmp/*-installer-cache before re-running the installer)

tip o' my cap to you, Drinkcat. amazing that you guys can figure this stuff
out and make it fly. miraculous that I found the temp directory you flagged
figured out rm -rf to eradicate the old cache. an old dog learning new
tricks.
best wishes and thanks,
Dave
On Tue, May 17, 2016 at 9:55 PM, drinkcat<EMAIL_ADDRESS>wrote:

Fix was merged, just try again. (you will want to remove the cache in
/tmp/*-installer-cache before re-running the installer)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/2593#issuecomment-219904740


Iceberg View Support

          We haven't talked about [Iceberg Views](https://iceberg.apache.org/view-spec/) yet and I'm not sure if you would like to support them in the future. I'm actually really interested in using views.

I don't want to include view support in this PR but I would like to future proof the catalog design to easily support views in the future.
The REST catalog is in the process of adding view support. However, I have the feeling that the initial REST catalog API wasn't designed with views in mind. There is one issue that comes up with the current design that we might be able to avoid for our catalog design. I will try to explain the issue.
Imagine a query engine wants to perform a query like the following:
SELECT first_name, last_name, age FROM users WHERE age > 18;

Without the catalog information the query engine doesn't know whether users refers to a view or a table. So if the catalog only exposes a load_table and load_view operation, the query engine doesn't know which one to call. I would prefer a load_tablelike (the naming is not important) operation that returns an
enum TableLike {
    Table(Table),
    View(View)
}

All iceberg catalogs except for the REST catalog return a "table metadata location" and it would be easy to distinguish between Tables and Views based on the metadata.
Let me know what you think.
Originally posted by @JanKaul in https://github.com/apache/iceberg-rust/issues/54#issuecomment-1702390543

Forward @JanKaul's discussion here.

Thank you for sharing! The relationship between view and table is quite interesting. At Databend, we consider a view as a special type of table, and our engine can distinguish the differences and determine how to execute the SQL accordingly.

I'm wondering if it's possible to avoid exposing the view details at the Catalog level and instead leave them for the catalog implementer to decide.

From @JanKaul

Converting from Table to TableLike is straightforward:
impl From<Table> for TableLike {
    fn from(value: Table) -> Self {
        TableLike::Table(value)
    }
}

So you would only need to call table.into().
For the table scan operation you would need to check whether your input is a table or a view and then execute the corresponding scan operator. As long as we don't have view support it could look like:
let table = if let TableLike::Table(table) = tablelike {
        Ok(table)
    } else {
        Err(Error::new(... , "Views are not supported yet"))
    }?:

Also invite @Fokko, @liurenjie1024，@ZENOTME to join this discussion.

I'm not familiar with the details of databend but I'm guessing that you would also need some way to distinguish between a table and a view. Can you think of an ideal design for databend that supports tables and views?

I'm guessing the problem we met here is iceberg has different spec for Table and View which needs different handling?

So for constructing TableMeta for views and tables, wouldn't you also need a TableLike to specify the correct engine?

From @liurenjie1024

Hi, @JanKaul Good point for view. Except for view, I think there will be other entities like materialized view. So the question is about name resolution:

Should we keep separate method for resolving tables, views, event materialized view?

fn load_table(&self, table_name: TableId) -> Result<Table>;
fn load_view(&self, view_name: ViewId) -> Result<View>;

I think it's still useful to keep separate methods for each kind of entity. For example when I want to execute dml like:
insert into t values(1), (2)

The query engine knows that it should load a table to check it.

Should we have a method for resolving entities without knowing its entity type?

As @JanKaul said it's would be quite useful in query:
select * from t;

In this case the catalog api should provide sth like:
fn load_entity(&self, table: &TableId) -> Result<TableLike>

Should we keep both methods or just load_entity?

Keep load_entity method only can solve problem in 1. But I still want to keep methods in 1 for several reasons:

The api is more user friendly.
This gives concrete implementation more chances to do optimization, especially in cases where many tables and views are defined.

So for constructing TableMeta for views and tables, wouldn't you also need a TableLike to specify the correct engine?

Oh, sorry for missing this part. We have those information from our SQL Parser directly, for exmaple, CREATE VIEW and CREATE TABLE.

Hi, @JanKaul Good point for view. Except for view, I think there will be other entities like materialized view. So the question is about name resolution:
1. Should we keep separate method for resolving tables, views, event materialized view?

fn load_table(&self, table_name: TableId) -> Result<Table>;
fn load_view(&self, view_name: ViewId) -> Result<View>;

I think it's still useful to keep separate methods for each kind of entity. For example when I want to execute dml like:
insert into t values(1), (2)

The query engine knows that it should load a table to check it.
2. Should we have a method for resolving entities without knowing its entity type?

As @JanKaul said it's would be quite useful in query:
select * from t;

In this case the catalog api should provide sth like:
fn load_entity(&self, table: &TableId) -> Result<TableLike>

3. Should we keep both methods or just `load_entity`?

Keep load_entity method only can solve problem in 1. But I still want to keep methods in 1 for several reasons:
* The api is more user friendly.

* This gives concrete implementation more chances to do optimization, especially in cases where many tables and views are defined.

Good points, @liurenjie1024. I think it would make sense to have load_table, load_view and load_entity. Just that for SELECT queries it would be good to use load_entity. For cases where the query engine knows whether it's a table or a view it can call load_table and load_view.

I'm guessing the problem we met here is iceberg has different spec for Table and View which needs different handling?

I'm not sure what the best procedure for the REST catalog is. Maybe optimistically try to fetch the table metadata and if it fails then fetch the view metadata.
For all catalogs that obtain the "metadata location" Serde should be able to handle this. Since TableMetadata and ViewMetadata have different structures, Serde can identify whether it's a table or a view during deserialization.

So for constructing TableMeta for views and tables, wouldn't you also need a TableLike to specify the correct engine?

Oh, sorry for missing this part. We have those information from our SQL Parser directly, for exmaple, CREATE VIEW and CREATE TABLE.

What if you use an external iceberg catalog? Do you still have that information?

What if you use an external iceberg catalog? Do you still have that information?

Great point! This information is essential. Thank you for the explanation. Now I got your point.

This gives concrete implementation more chances to do optimization

Good points, @liurenjie1024. I think it would make sense to have load_table, load_view and load_entity. Just that for SELECT queries it would be good to use load_entity. For cases where the query engine knows whether it's a table or a view it can call load_table and load_view.

Agree with having load_entity, load_table and load_view.

For cases where the query engine knows whether it's a table or a view it can call load_table and load_view.

What I concern is whether is way will cause redundant code.🤔 E.g.
if we can determine is table :
    let table = load_table
    <process1>
else if we can determine is view :
    let view = load_view
    <process2>
else
    let tableike = load_entity
    <process3>

<process1>,<process2>,<process3> may be redundant.

What I concern is whether it will cause redundant code.🤔 E.g.

I don't get your point, if the engine knows entity type(for example, table), why they need other process(process2, process3)

Your talking about a case where the query engine doesn't know what kind of entity its dealing with. In that case I think it should just use load_entity and then match on the result, like so:
match load_entity(identifier) {
    TableLike::Table(table) => {
            <process1>
        },
    TableLike::View(view) => {
            <process1>
        }
}

Your talking about a case where the query engine doesn't know what kind of entity its dealing with. In that case I think it should just use load_entity and then match on the result, like so:

Thanks! That's what I mean and apparently it's not a big deal. 🥵

I have a new idea for naming: How about using Tabular?
So we will have:

load_tabular() / load_table() / load_view()
Tabular::Table / Tabular::View

What do you think?

I have a new idea for naming: How about using Tabular?
So we will have:

load_tabular() / load_table() / load_view()
Tabular::Table(table) / Tabular::View(view)

What do you think?

I would avoid the confusion with the vendor.

I would avoid the confusion with the vendor.

Oh, I didn't take the vendor into consideration. I think tabular is a good alternative to table like and widely used in pandas ecosystem.

I have a new idea for naming: How about using Tabular?
So we will have:

load_tabular() / load_table() / load_view()
Tabular::Table(table) / Tabular::View(view)

What do you think?

I asked chatgpt, and he also thinks it's good idea. BTW, should we raise discussion in iceberg community to add an api to catalog interface?
Both java and python all have catalog interface:
https://github.com/apache/iceberg/blob/f0149a5860efe3f78d7cb07b81b4e1910b438020/api/src/main/java/org/apache/iceberg/catalog/Catalog.java#L33
https://github.com/apache/iceberg/blob/master/python/pyiceberg/catalog/__init__.py

I have a new idea for naming: How about using Tabular?
So we will have:

load_tabular() / load_table() / load_view()
Tabular::Table(table) / Tabular::View(view)

What do you think?

Nice one, I think it's a fitting name.

I have a new idea for naming: How about using Tabular?
So we will have:

load_tabular() / load_table() / load_view()
Tabular::Table(table) / Tabular::View(view)

What do you think?

I asked chatgpt, and he also thinks it's good idea. BTW, should we raise discussion in iceberg community to add an api to catalog interface?
Both java and python all have catalog interface:
https://github.com/apache/iceberg/blob/f0149a5860efe3f78d7cb07b81b4e1910b438020/api/src/main/java/org/apache/iceberg/catalog/Catalog.java#L33
https://github.com/apache/iceberg/blob/master/python/pyiceberg/catalog/__init__.py

Good point. I think this should be really valuable for java and python. I don't see a way for them to easily get around this issue.

Independant on how the the actual loader functions work, I believe implementing the Iceberg Spec for Views is a good idea.
As I have needed the structs from the spec, I have created a PR https://github.com/apache/iceberg-rust/pull/331. As of now, it only contains the spec definitions and doesn't really provide a way to use them.
I hope this helps going forward.


Error if invalid configuration option found

Complimentary to #545
If the repository is configured with an unknown/invalid configuration field (not found in config definitions.js) then the user should see an error and we should logger.warn for the administrator too.
Particularly important for Onboarding.
Suggested to use traverse for this as it's already in use for log serialization.

If the error is by the administrator (i.e. prior to any repository configs) then we should perhaps even consider it a fatal error and exit, to prompt them to fix?


preflight: Improve libvirt/qemu detection

At the moment, we decide if libvirt/qemu need to be installed by
checking for the availability of the 'virsh' binary. On current fedoras,
it's possible to install only the libvirt-client package, and no
other libvirt/qemu packages. This will install virsh, but
libvirtd/qemu-system-x86_64 which crc need will be missing.
This commit extends the checkLibvirtInstalled preflight check to parse
virsh capabilities to look for an appropriate hypervisor (ie qemu
binary)
Testing
What is the bottom-line functionality that needs testing? Describe in pseudo-code or in English. Use verifiable statements that tie your changes to existing functionality.
Without this PR:

Run 'yum remove 'qemu*' 'libvirt*'"
Run 'yum install libvirt-client'
Run 'crc setup' -> it succeeds
Run 'crc start' -> libvirt failure to start the crc VM

After this PR:

Run 'yum remove 'qemu*' 'libvirt*'"
Run 'yum install libvirt-client'
Run 'crc setup' -> it installs the needed libvirt/qemu packages
Run 'crc start' -> success

/lgtm


Hi, How to avoid the swipe to rear view?

I have 1 total of 4 VC(ViewControllers) in my project, for example VC1(homeViewController), VC2(MenuViewControllers), VC3, VC4. When I click Menu button from VC1 then VC2 shows after I am choose navigating to VC3 from VC2(Menu) and back to VC1(home) then goes to VC2(menu) then choose navigating to VC4, So now I am in VC4 here only I face the issue suppose If I drag or swipe the View means its pop(navigate) to VC3 or whatever VC before use the current VC.
Still now not sure of the solution to this issue and the same happens for other Views also please help me for find out the issue.

In fact when you are in VC3 or VC4 you don't want to be able to open the left menu, you want to come back to Home (VC1), right? And you want to be able to open the left menu only from Home (VC1), right?

Yes right.

The deal is to push the vc3 or vc4 the front view navigation controller and reveal (or push) the home view controller. I'll write a sample.

This code was I used for to move other view controller from menu..
let mainstoryboard:UIStoryboard = UIStoryboard(name: "Main", bundle: nil)
let InformationVC = mainstoryboard.instantiateViewController(withIdentifier: "InformationViewController") as! InformationViewController
let FrontController = UINavigationController.init(rootViewController: InformationVC)
revealviewcontroller.pushFrontViewController(FrontController, animated: true)
And this code was I used for back to Home View Controller(VC1)..
let nav = storyboard?.instantiateViewController(withIdentifier: "HomeNavigationController") as! UINavigationController
let menuTableVC = storyboard?.instantiateViewController(withIdentifier: "LeftMenuViewController") as? LeftMenuViewController
let mainRevealController = SWRevealViewController(rearViewController: menuTableVC, frontViewController: nav)
navigationController?.pushViewController(mainRevealController!, animated: true)
self.navigationController?.navigationBar.isHidden = true
Thanks..

Can you Please write including this functionality in sample, how navigate to other viewcontroller from Menu and how to back to Homeviewcontroller(VC1) from other viewcontroller..

I wrote this sample:
SWHomePushSwift.zip
If you want a navigation bar with a title on left menu, just check Shows Navigation Bar in Navigation controller scene in storyboard.
Hope it helps!

Ok thanks I will check it now.

Very Very Thanks its helpful for me.

One More doubt I have, Can I ask Now?

When I use Segue for Navigating Menu Button not works, for example In HomeViewController(VC1) at first time I open menu via menu button then choose HomeViewController option from menu so it directs to HomeViewController but this time I unable to open Menu because Menu button not works.
How to fix the Current issue?

Not sure to understand. Do you instantiate HomeViewController each time? Don't use segue for that, save the reference of your HomeViewController as in the sample.

ok sure.


Remove TransitionStub / TransitionGroupStub from docs

They were removed without further notice in beta 30, but the docs are not updated. It took me quite some time to figure out that they don't exist anymore, and how to fix my failing test:
<transition name="toast">

...

</transition>

toastElement.querySelector('.close').click()
await wrapper.vm.$nextTick()

toastElement = document.querySelector('.toast')
expect(toastElement).to.equal(null)

Test fails; there is a .toast element with .toast-leave-active class.
Replacing the nextTick with await new Promise(resolve => setTimeout(resolve, 5)) works, but doesn't look like it's safe against race conditions.

This is not a usage question; I couldn't select vue-test-utils version 1.0.0-beta30 in the Issue Helper.

Apologies for the problem with our issue helper.
@FloEdelmann , thank you for reporting this. I believe the docs are fixed. Can you confirm? https://vue-test-utils.vuejs.org/api/components/

Thanks, the updated docs look fine now. Maybe you want to add one sentence about the removed stub components? That'd be helpful for people upgrading (like me), but will be less useful in the future.

+1 to @FloEdelmann we updated from beta29 to 30 and now all our components that contain transitions fail.
There is no documented way of having global stubs (for transitions in this case) rather than adding the stub manually to each test.

Maybe this? @nachogarcia  https://vue-test-utils.vuejs.org/api/#config

Nope, I already tried with
config.stubs.transitioncomponent = '
'
config.stubs['transition-group'] = '
'

and all of our tests fail, probably because children are not rendered since it needs a stub like the previous one https://github.com/vuejs/vue-test-utils/blob/f0b863252398f2b163f4b267d16103f06c7a53a2/packages/test-utils/src/components/TransitionStub.js which is not exported anymore

@nachogarcia We’re about to update the docs with a better transitionStub. Can you give these instructions a try? https://github.com/vuejs/vue-test-utils/pull/1375/files

Looks like, as documented there, using this
const transitionStub = () => ({
  render (h) {
    return this.$options._renderChildren
  }
})

config.stubs.transitioncomponent = transitionStub()
config.stubs['transition-group'] = transitionStub()

along with await wrapper.vm.$nextTick() works @JessicaSachs .
But this way I'm going to need to refactor hundreds of tests, adding the line and an making them async to wait for an update that so far has been done automatically :S seems weird.

@JessicaSachs The updated docs in #1375 are exactly what I was searching for when I was upgrading to 1.0.0-beta.30. I've suggested some changes there.
Since the docs are now clearly explaining what I was missing, I'm closing this issue.

Unfortunately, the nextTick changes will remain required for future
versions of VTU. To explain the need for these changes, please take a look
through #1137
You can pin at version 28 if you’d like to remain synchronous.
On Tue, Dec 17, 2019 at 11:24 AM Nacho García<EMAIL_ADDRESS>wrote:

Looks like, as documented there, using this
const transitionStub = () => ({
render (h) {
return this.$options._renderChildren
}
})
config.stubs.transitioncomponent = transitionStub()
config.stubs['transition-group'] = transitionStub()
along with await wrapper.vm.$nextTick() works @JessicaSachs
https://github.com/JessicaSachs .
But this way I'm going to need to refactor hundreds of tests, adding the
line and an making them async to wait for an update that so far has been
done automatically :S seems weird.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-test-utils/issues/1367?email_source=notifications&email_token=AAVL4BHCJHJZMW23FEOQZ4DQZD4NVA5CNFSM4JZLZQ6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHDDPGI#issuecomment-566638489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVL4BCEIGPHTSU6UIHBYK3QZD4NVANCNFSM4JZLZQ6A
.


:key-fn for encoding keys with babashka.json/write-str

Would it make sense to add :key-fn for babashka.json/write-str for encoding keys since this is already supported for decoding keys with read-str?

Right now I'm using babashka.json with an HTTP API that uses snake_case.
This works:
(json/read-str s {:key-fn inflections/hyphenate})

But not this:
(json/write-str s {:key-fn inflections/underscore})

I guess so, if the underlying libraries support it too?

I can check if any of the libraries don't support this and get back to you.

@borkdude: I wrote a test to show how this is done for each lib (see README to run it yourself):
https://github.com/rads/json-key-fns/blob/main/src/rads/json_key_fns.clj
The only one that doesn't support it easily is charred. Overriding the behavior requires a custom :obj-fn and the default-obj-fn is private so I had to copy-paste the implementation and modify it slightly. There are a few options to move forward here:

Do nothing and close this issue
Use the custom obj-fn with the copy-pasted code
Talk to @cnuernber to see if there is a simpler way or a possible improvement we can make to charred to make this easier

If we want to move forward with this, I can follow up with a PR for #2 and reach out to @cneurnber for #3. If it's not worth the effort, I'll go ahead and close this issue.

Added another option to the list above to throw an exception if using :key-fn with charred.

And one more option for coercing the keys before calling charred. 😄

Talking to the charred author seems like a reasonable next step?
On Sat, Nov 9, 2024 at 12:02 AM Radford Smith @.***>
wrote:

And one more option for coercing the keys before calling charred. 😄
—
Reply to this email directly, view it on GitHub
https://github.com/babashka/json/issues/10#issuecomment-2465877351, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACFSBUVBOV4FLM2VP45NQTZ7U7HPAVCNFSM6AAAAABROLOI6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVHA3TOMZVGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
https://www.michielborkent.nl
https://www.eetvoorjeleven.nu

Sounds good, I'll get back to you when I have some more info.


Upgrade Inventory UI dependencies, looks and usability

Added room overview and replaced the manual UUID action with a button. Also, added Axon favicon, page title and Axon colors


Refresh tracer metadata on CRaC snapshot restore

What does this PR do?

Checklist

Initial proposal for https://github.com/elastic/apm-agent-java/issues/2982

[ ] This is an enhancement of existing features, or a new feature in existing plugins

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[ ] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[x] This is something else

[x] I have updated CHANGELOG.asciidoc

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-02-26T15:48:52.163+0000

Duration: 3 min 17 sec

Steps errors
Expand to view the steps failures

Load a resource file from a library

Took 0 min 0 sec . View more details here
Description: approval-list/elastic/apm-agent-java.yml

Error signal

Took 0 min 0 sec . View more details here
Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/ArtyomGabeev return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/ArtyomGabeev : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/ArtyomGabeev : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

+1

Hi, thank you for this contribution it's really interesting! I'll be looking at this, it may take a little while as I'm also on other things. First thing though, can you please sign the contributor agreement

You seem to have 2 email addresses, one is signed up but the one associated with this PR isn't. I've tried to add the latter email address, did you get an email?

You seem to have 2 email addresses, one is signed up but the one associated with this PR isn't. I've tried to add the latter email address, did you get an email?

Thank you, looks like CLA is signed off.

+1

+1

still pending :+1

run docs-build


Possibly unintended behavior for modal margins

In v4-alpha-6, there is some possibly unintended behavior for modal margins. In the current setup, modals have margin: $modal-dialog-margin by default (https://github.com/twbs/bootstrap/blob/v4-dev/scss/_modal.scss#L45) and switch to margin: $modal-dialog-sm-up-margin-y auto above the small media breakpoint (https://github.com/twbs/bootstrap/blob/v4-dev/scss/_modal.scss#L130).
However, this means that if the small breakpoint is set to be smaller than the max-width of the modal, then the modal will have no margins. In my case, I notice this effect with a small breakpoint of 480, the default modal width of 500, and using the modal code from the documentation:

<button type="button" class="btn btn-primary" data-toggle="modal" data-target="#exampleModal">
  Launch demo modal
</button>

Modal title

        <button type="button" class="close" data-dismiss="modal" aria-label="Close">
          ×
        </button>

        ...

        <button type="button" class="btn btn-secondary" data-dismiss="modal">Close</button>
        <button type="button" class="btn btn-primary">Save changes</button>

Under these conditions, when the screen width is between 480px (the small breakpoint) and 500px (the max-width of the modal), the modal has no margins.
This issue can be worked around fairly easily, but it does seem like unintended behavior. It might be better if the modal was guaranteed to have nonzero margin at all breakpoints, rather than just below the small breakpoint.

Closing as a won't fix—modals saw some style changes to move from width to max-width and I believe they're working as intended now. If not, please comment again with a demo JS Bin and we can revisit.


CompletionItem decorator

From @TheColorRed on October 25, 2016 15:46
Is there a way to add a decorator to a CompletionItem?
I would like to add a color like the way CSS shows the color of the item. Is this possible? If so how can I do it?
Copied from original issue: Microsoft/vscode-extension-vscode#40

Yeah - use kind: Color and make the label match a color, like #22ee44 or hsl(122, 221, 32)


Tweaks .ci/make.sh to clean up after itself

Tweaks to .ci/make.sh

Now also removes the specified output path, not just the hardcoded version.
Publishing nuget packages now no longer uses a special subfolder _packages to publish.
This to fall in line with how other clients  will use .ci/make.sh.

remove references to _packages from other targets

Manually backported to 7.x and 7.10


Fix #12139

Objective
Fixes #12139
Solution

Derive Debug impl for Entity
Add impl Display for Entity
Add entity_display test to check the output contains all required info

I decided to go with 0v0|1234 format as opposed to the 0v0[1234] which was initially discussed in the issue.
My rationale for this is that [1234] may be confused for index values, which may be common in logs, and so searching for entities by text would become harder. I figured |1234 would help the entity IDs stand out more.
Additionally, I'm a little concerned that this change is gonna break existing logging for projects because Debug is now going to be a multi-line output. But maybe this is ok.
We could implement Debug to be a single-line output, but then I don't see why it would be different from Display at all.
@alice-i-cecile Let me know if we'd like to make any changes based on these points.

could you give this PR a more descriptive title? The title ends up in the commit history of the main branch


Creating new data stream toscience json

In this branch the new MappingWorkFlow Amb --> toscience --> Metadata2 has been implemented.

Good question.
Only the necessary elements were added to the AmbContent so that the artifact core can process the given AmbContent.
Affiliation-Name at contributors will be mapped later in LRMIMapper .
Optimally, Affiliation-Name at creators and contributors would be mapped in class AmbHelper, in that case upload process can be faster by some milliseconds.


[Insets] imePadding() leaves extra space due to BottomNavigation

Description
I'm not sure if this is considered a bug. When calling imePadding() in a component in BottomNavigation(), it leaves extra white space between the component and the keyboard.
Is it possible to have imePadding() subtract the bottom padding from the parent component?

It sounds like imePadding() is working as expected?
One thing that might be helpful for your case is that imePadding() is just a shortcut for specific values of the insets.
navigationBarsWithImePadding() might also be useful, or you can look at the exact values from LocalWindowInsets.current.ime to perform any necessary math for your use case.

Thank you. I must have missed that function.

It still doesn't work. The problem is the padding from the parent component, not the systemBar, The simplified code is as follows
Scaffold(bottomBar = { BottomNavigation() }) { innerPadding ->
    NavHost(modifier = Modifier.padding(innerPadding)) {
        LazyColumn(modifier = Modifier.imePadding())
    }
}

A dirty solution:
    modifier = Modifier.imePadding().padding(
        rememberInsetsPaddingValuesX(
            insets = LocalWindowInsets.current.ime,
            additionalBottom = (-56).dp
        )
    ),

This requires overriding the calculateBottomPadding method of the InsetsPaddingValues class:
    override fun calculateBottomPadding(): Dp = (additionalBottom + when {
        applyBottom -> with(density) { insets.bottom.toDp() }
        else -> 0.dp
    }).coerceAtLeast(0.dp)

I'm not sure if there is anything that needs to be changed in the InsetsPaddingValues, I think you have all of the information you need.
It sounds like you want the LazyColumn to have additional content padding of the difference between the IME insets and the inner padding, if that difference is larger than 0.
Instead of using imePadding, you just setup the padding directly:
LazyColumn(
    contentPadding = PaddingValues(
        bottom = with(LocalDensity.current) {
            LocalWindowInsets.current.ime.bottom.toDp() - innerPadding.bottom
        }.coerceAtLeast(0.dp)
    )
) { ... }

I see. I will close this issue later.

Please also see my comment here.


Benchmarks: AnswerQuestionCombineCsv

Overview
Challenge Info
Evo Logs [1] [2]
Observations
Very related to the behavior of https://github.com/polywrap/evo.ninja/issues/257; but there are two CSVs rather than one. This makes me think that we should probably prompt Evo with something like "You have your workspace where u can see if there's needed information"? Then, it could check the files there and see if something might be useful? Not sure...

This has been passing consistently


[e2e]: generic schedule main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5329693515
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Jun 21 03:16:19 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5341202565
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Jun 22 03:22:44 UTC 2023
Tests are passing now. Closing this issue.


[Tutorial] Possible improvement in the "Clean labels using your model loss" tutorial

After running the function for computing the loss in this tutorial, it is required to turn the dataset into a Pandas data frame. When running the code, the following warnings are shown:
/var/folders/ym/p8klf4tx3cb_7q9vsngj0z4w0000gn/T/ipykernel_16926/2192143421.py:4: UserWarning: To copy construct from a tensor, it is recommended to use sourceTensor.clone().detach() or sourceTensor.clone().detach().requires_grad_(True), rather than torch.tensor(sourceTensor).
input_ids = torch.tensor(batch["input_ids"], device=device)/var/folders/ym/p8klf4tx3cb_7q9vsngj0z4w0000gn/T/ipykernel_16926/2192143421.py:5: UserWarning: To copy construct from a tensor, it is recommended to use sourceTensor.clone().detach() or sourceTensor.clone().detach().requires_grad_(True), rather than torch.tensor(sourceTensor).
attention_mask = torch.tensor(batch["attention_mask"], device=device)
/var/folders/ym/p8klf4tx3cb_7q9vsngj0z4w0000gn/T/ipykernel_16926/2192143421.py:6: UserWarning: To copy construct from a tensor, it is recommended to use sourceTensor.clone().detach() or sourceTensor.clone().detach().requires_grad_(True), rather than torch.tensor(sourceTensor).
labels = torch.tensor(batch["labels"], device=device)
Therefore, these variables can be changed to:
input_ids = batch["input_ids"].clone().detach()
attention_mask = batch["attention_mask"].clone().detach()
labels = batch["labels"].clone().detach()
Then, the warning disappears.

Done in #714


Aggressive postgres instantiation ctx timeout causes intermittent failures in Datastore initialisation

What platforms are affected?
linux
What architectures are affected?
others
What SpiceDB version are you using?
v1.31.0
Steps to Reproduce

Start Spice DB locally with a remote cloud postgres which can take more than 5 second to respond.
Before the initialisation steps can complete the ctx times out very frequently eventhough intermittently

Expected Result
The initialisation should be able to work with slow or remote postgres instances.
It should either be made configurable. Or increased to higher number like 20/30 . As this is the initialisation flow.
The exact line were this is set is below:
https://github.com/authzed/spicedb/blob/4262bfd23266888fdfff5e01a24f76e6d30c98ef/internal/datastore/postgres/postgres.go#L227
Actual Result
The context times out very frequently . An example log below
2024-10-18 15:53:02 {"level":"trace","preshared-keys-count":1,"time":"2024-10-18T10:23:02Z","message":"using gRPC auth with preshared key(s)"} 2024-10-18 15:53:02 {"level":"trace","preshared-key-1-length":13,"time":"2024-10-18T10:23:02Z","message":"preshared key configured"} 2024-10-18 15:53:02 {"level":"info","time":"2024-10-18T10:23:02Z","message":"using postgres datastore engine"} 2024-10-18 15:53:02 {"level":"warn","details-url":"https://spicedb.dev/d/force-custom-plan","plan_cache_mode":"force_custom_plan","time":"2024-10-18T10:23:02Z","message":"defaulting value in Postgres DB URI"} 2024-10-18 15:53:07 {"level":"debug","pgx":{"args":[],"err":"timeout: context deadline exceeded","pid":23643,"sql":"SHOW track_commit_timestamp;","time":645.80925},"time":"2024-10-18T10:23:07Z","message":"Query"} 2024-10-18 15:53:07 {"level":"error","error":"failed to create datastore: timeout: context deadline exceeded","time":"2024-10-18T10:23:07Z","message":"terminated with errors"}

Have added a PR to address the issue. Please do consider. If it needs to be fixed differently please do let me know.
https://github.com/authzed/spicedb/pull/2095

Thanks for reviewing and merging the fix.
Also the workaround of spicedb datastore repair for the pg_dump approach is something we missed when we tried that. Thanks for that information.


Add early dynamic resource loading

Overview
Under a Project/Plugin's Content folder, there would be:

Dynamic Contents: assets including static meshes, materials, textures, being referenced during Sim run.
Static Contents: assets statically referenced and configured by actor, material, etc. BPs.
Both of these are both baked when the package is built and loaded up at run time.

For dynamic contents, early async resource loading should be employed at Sim's initialization, so during Sim's run, they could be used instantly, without having to invoke StaticLoadObject/LoadObject which requires passing a hard-coded path to the asset and thus compromises the performance. (Ref: void AWorldLoader::ConstructLevel())
Reference:
"Avoid Referencing Assets by String"
https://docs.unrealengine.com/en-US/Resources/SampleGames/ARPG/BalancingBlueprintAndCPP/index.html
Implementation Details

[x] Add RRGameSingleton, holding loaded resource assets data (static meshes, materials, textures, etc.)
[x] Add RRGeneralUtils, RRAssetUtils, RRTypeUtils under Tools folder.
[x] RRObjectCommon, holding common structs like ERRResourceDataType, FRRResource, FRRResourceInfo which could be included globally to avoid cyclic inclusion among header files.
[x] [UE_rapyuta_assets.Build.cs] Add PhysicsCore dependency, for linking UPhysicalMaterial, a particular type of material resource.
[x] [Content] Add DynamicContents + RapyutaGeneric map for testing this dynamic resource loading
[x] Add RRGameMode, which initializes early resource loading before other GameState, PC's BeginPlay
[x] Also add LogRapyutaCore category for the plugin

How to test
In the application project,
1- Configure Level map's Override Gamemode as RRGameMode
2- In DefaultEngineBase.ini
Under [/Script/Engine.Engine], add:
GameSingletonClassName=/Script/RapyutaSimulationPlugins.RRGameSingleton
Load the map up, there should appear 2 messages on screen:
LOADING SIM DYNAMIC RESOURCES..
ALL DYNAMIC RESOURCES LOADED

Note:

The specifc asset object (UStaticMesh*, UMaterialInterface*, etc.) would then be fetched through URRGameSingleton::GetStaticMesh(InStaticMeshName) & ::GetMaterial(InMaterialName) respectively
Since the resources are stored in a map with its name as key, each static mesh or material is expected to have unique asset name of its type, regardless of which folder it resides.
This PR includes the early loading for StaticMesh and Material only. For Texture, Curve, etc., they will be added in other PRs upon specific requirements of application projects.

Risk

Without steps being taken above, this PR does not impact the stakeholder projects (io_amr_UE/turtlebot3_UE) yet.

Next step

Update ROS2GameMode BP: made to inherit RRGameMode in case some client map that is configured as ROS2GameMode uses dynamic resources.
Update io_amr_UE/turtlebot3_UE following above steps & using URRGameSingleton's resource fetching API

is there a use for RapyutaGeneric.umap?
seems to be empty
if there's no use, please remove it
do we also need to have copies of basic shape in this plugin for this to work?

Yeah, the map is only for testing this PR. It would be removed then.
Regarding the basic shapes or dynamic resources in general, so

They should be moved to the specific folder DynamicContents, which Sim will load from.
For other static assets that are not referenced during Sim run, they could be kept as they are, under our project/plugin's Content outside of (DynamicContents) or built-in Engine's Content folder.

@tetorea Sorry, I just updated the description on Steps of How to Test to our new plugin name, which should be:
GameSingletonClassName=/Script/RapyutaSimulationPlugins.RRGameSingleton

The config path in .INI file is actually not a physical path on disk, and only used as the internal key to a UPROPERTY(config) member value.

@Tadinu thanks, it's better with the new line
I get the messages when I play the RapyutaGeneric map. The environment is completely black though, is it normal?