Allow cross-junction dependencies to be listed as strings

See original issue on GitLab
In GitLab by [Gitlab user @cs-shadow] on Dec 6, 2018, 16:52
Background
While writing element definitions, one could either list it as a string or as a dependency. Since build-depends and runtime-depends were introduced, we generally prefer using them over the dict approach as they keep the element definitions small and more readable.
But, we have to revert to using dicts when working with elements across junctions (which are the majority). Sometimes this results in a weird mix of dependency lists, where half of them are dicts and the other half is strings.
As junctions are currently the only thing that have to be expressed via dicts, it would be nice to be able to do so using just strings. Luckily for us, we already have such a notation that we use in CLI (using : as separator), so we can simply extend that to element definitions as well.
So, instead of:
dependencies:
- normal-dep.bst
- filename: junction-dep.bst
  junction: junction-element.bst

one would be allowed to say:
dependencies:
- normal-dep.bst
- junction-element.bst:junction-dep.bst

Task description

[ ] Provide a way to express cross-junction dependencies as strings in one-line

Acceptance Criteria

In GitLab by [Gitlab user @cs-shadow] on Dec 6, 2018, 16:54
mentioned in commit e46ae107ef40f2a90a9a6b3af7fea87a25a15bd6

In GitLab by [Gitlab user @cs-shadow] on Dec 6, 2018, 16:56
mentioned in merge request !998

In GitLab by [Gitlab user @cs-shadow] on Dec 6, 2018, 16:58
I have created a WIP MR - https://gitlab.com/BuildStream/buildstream/merge_requests/998 - to address this issue. I haven't added any tests yet as I wanted to ensure if this makes sense to people or not. So, any early review will be much appreciated.

In GitLab by [Gitlab user @jmacarthur] on Dec 7, 2018, 11:04
The approach and the code look good to me, as long as nobody makes an element name with a ':' in it. Should we make that explicit in the documentation? It will probably be an issue for the existing command-line syntax too.

In GitLab by [Gitlab user @lchlan] on Dec 7, 2018, 11:15
It needs to be explicit and enforced with suitable handling.

In GitLab by [Gitlab user @cs-shadow] on Dec 7, 2018, 14:40
Agree with both of you. As mentioned on the MR, I will write something to the ML about documenting legal characters for element filenames.

In GitLab by [Gitlab user @cs-shadow] on Dec 30, 2018, 21:38
mentioned in merge request !1028

In GitLab by [Gitlab user @cs-shadow] on Dec 30, 2018, 21:44
I have created https://gitlab.com/BuildStream/buildstream/merge_requests/1028 to define what are valid element names. Unfortunately, it seems like we might not be able to detect all cases when this happens. Like in this case, since we intend to use : as a separator for junctioned elements, we can't properly disambiguate between junctioned elements and the elements actually having : in their names.
!1028 also updates the docs as mentioned above, but since we can't warn on : anyway, there is now no dependency between !998 and !1028. So, both can be reviewed and merged individually.

In GitLab by [Gitlab user @cs-shadow] on Dec 30, 2018, 22:18
mentioned in commit 224a1249006dee8df9d4bac351848a1a272cd18d

In GitLab by [Gitlab user @tristanvb] on Dec 31, 2018, 19:17
mentioned in merge request !1029

In GitLab by [Gitlab user @tristanvb] on Dec 31, 2018, 19:28

Unfortunately, it seems like we might not be able to detect all cases when this happens. Like in this case, since we intend to use : as a separator for junctioned elements, we can't properly disambiguate between junctioned elements and the elements actually having : in their names.

This seems to be fine by itself because I would expect that the : strings will be broken down and used to lookup a junction - so there is no such thing as an invalid element name which has : in the name, there is only invalid junction name references (left side of :), or references to absent elements across the junction (right side of :).
I've made sure that both failure scenarios (missing junction, or missing subproject element) are tested as a part of !1029.
Here are a few edge case observations which should probably be tested as well:
Expanding filename in absence of junction
If the junction: field is not specified, then I think the filename: field should be treated as a full name, i.e. one should be able to specify:
depends:
  filename: junction.bst:element.bst
  type: runtime

Error if colons are found where they shouldn't be
If on the other hand, both of the filename: and junction: fields are specified, then it is a naming error if any : character is found in the filename: field, e.g.:
depends:
  filename: invalid.bst:colon.bst
  junction: junction.bst
  type: build

At the same time, at any point where colons are separated, the same name validation logic should of course be applied to the split components.
Finally, I think as a rule, we never allow more than one : (you cannot do recursive lookups).

In GitLab by [Gitlab user @cs-shadow] on Feb 12, 2019, 12:04
mentioned in commit 0f092d363e8698a79dc08d844fe7b25ab03a74ac

In GitLab by [Gitlab user @cs-shadow] on Feb 12, 2019, 14:48
mentioned in commit 1b02c550ba1790e3a8a97ddba4f836cd3fb9f520

In GitLab by [Gitlab user @cs-shadow] on Feb 12, 2019, 15:00
mentioned in commit fd1d40bff9c6c2c1bc55d11090201fa065ac4627

In GitLab by [Gitlab user @cs-shadow] on Feb 18, 2019, 17:59
mentioned in commit 2a4e48436f4240d325d4801747fa00a811e58045

In GitLab by [Gitlab user @cs-shadow] on Feb 18, 2019, 18:26
mentioned in commit ad3a85b8ab58f25cea9f7a41f297012f23213a30

In GitLab by [Gitlab user @cs-shadow] on Feb 18, 2019, 18:31
mentioned in commit 5e188e3d0dd18a607fece1c7367fc5f06b2a73e8

In GitLab by [Gitlab user @cs-shadow] on Feb 25, 2019, 21:35
mentioned in commit 88ace418b0e9d1608b58c78e206d203af8fc6eeb

In GitLab by [Gitlab user @marge-bot123] on Feb 25, 2019, 22:16
closed via merge request !998

In GitLab by [Gitlab user @marge-bot123] on Feb 25, 2019, 22:16
mentioned in commit d6ec082a3017882e69b070f1f5435b5a5eead29f

In GitLab by [Gitlab user @cs-shadow] on Jul 25, 2019, 17:21
mentioned in commit 76709f8e8f58885bb1ae6aa8d8a4bb6952499390

In GitLab by [Gitlab user @cs-shadow] on Jul 25, 2019, 18:02
mentioned in commit 48d2ead06ad35f5019d02f3b2b743c40490609a8

In GitLab by [Gitlab user @cs-shadow] on Jul 25, 2019, 18:10
mentioned in commit ccf32059d0ddd0d78f830b11e9d576d771cb7c74


App crashes on importing SVG

This SVG causes the app to crash:
https://gist.github.com/alexjlockwood/0db6f64f81eb1eb54434636155463615
The error in the JS console is something like 'can't get property stroke from undefined'.

To avoid the crash, I think maybe you have to change this function to:
let simpleAttr_ = (nodeAttr, contextAttr) => {
  if (node.attributes && node.attributes[nodeAttr]) {
    context[contextAttr] = node.attributes[nodeAttr].value;
  }
};

I guess it is possible for node.attributes to be undefined if no attributes are specified.


Support assertions in tests, not just screenshots

Shouldn't crash when one fails; should report it.

https://github.com/ihodes/seltest/commit/189c25fe64f4dc4d54bf09804540aa1576d692fa


fix: check if we are sent 512 characters or more

huge pr take your time to check all files and read it all

huge pr take your time to check all files and read it all

ahahah menteur


Upgrade GCP dependencies

GCP adapter is still using alpha GCP function framework api. Can we upgrade this as follows.
functions-framework-api from 1.0.0-alpha-2-rc3 to 1.0.3
java-function-invoker from 1.0.0-alpha-2-rc4 to 1.0.1
If someone is not working, would be happy to take it up. Thanks.

I can do this!


fix: update - using icinga2-script mount from junos-automation project

IMO, We should create a commit status that cover all CI pipelines result to block PR until all integration tests passed
@svtechnmaa/sre


Read the Docs: vent/core correctly lists the modules but doesn't have the corresponding documentation

I think I know the problem.
Soooo, Sphinx needs to import the packages before it can generate documentation. Unfortunately, vent/core modules have - in them and Python doesn't like importing packages with - in the name.
So original plan was to change the file names from - to _, call sphinx-apidoc to generate the documentation, and make html for Sphinx to create the HTML pages to view. Then, the file names are changed back. That works on a local host.
The ball is thrown into Read the Docs' fence. Read the Docs build documentation from the GitHub repo. There, vent/core still has the - and Read the Docs' Sphinx can't handle that. That's why anything in the core section of the repo doesn't have documentation.
This is a pretty big blocker. Maybe I'll look into using GitHub pages instead of Read the Docs

So the documentation shows up on my local machine, and it should show up on the actual page. The only problem I'm having right now is automating the doc build process.


nixos/matrix-appservice-irc: Allow syscalls in the @chown set

Description of changes
The preStart script uses sed if a previous registration file already exists. sed make a call to fchown which fails as it is part of the @privileged set which was not allowed.
This is currently broken in 23.11, so this fix should be backported.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This looks like a dupe of https://github.com/NixOS/nixpkgs/pull/271740 (which is already merged and backported)?


Problems with updating db relations. The instance of entity type cannot be tracked because another instance of this type with the same key is already being tracked.

I'm currently trying to update some related data in my database. I've descrived it accurately here, but well, no answers yet. Since the docs looks rather empty I'm not sure if I'm using it correctly. As far as I remember, this way worked quite well on previous versions of EF, so maybe it's a bug?
As I mentioned before, I've described it already on StackOverflow, but see my entire function that I use:
[HttpPut("{id}")]
        public IActionResult PutNote(int id, [FromBody] Note note)
        {
            if (!ModelState.IsValid)
            {
                return HttpBadRequest(ModelState);
            }

            if (id != note.NoteId)
            {
                return HttpBadRequest();
            }

            try
            {

                if (note.TagsToAdd != "" && note.TagsToAdd != null && note.TagsToAdd != note.TagsAsSingleString)
                {
                    var dbNote = db.Notes.Include(x=>x.NoteTags).ThenInclude(x=>x.Tag).FirstOrDefault(x => x.NoteId == note.NoteId);
                    dbNote.NoteTags.Clear();
                    dbNote.NoteTags = TagsToAddToTags(note).NoteTags;
                }
                db.SaveChanges();
            }
            catch (DbUpdateConcurrencyException)
            {
                if (!NoteExists(id))
                {
                    return HttpNotFound();
                }
                else
                {
                    throw;
                }
            }
            catch (Exception e)
            {
                Trace.WriteLine(e);
            }

            return new HttpStatusCodeResult(StatusCodes.Status204NoContent);
        }

The error from title appeares in the second "catch".
Error:

System.InvalidOperationException: The instance of entity type 'ConsoleNotepad.Models.NoteTag' cannot be tracked because another instance of this type with the same key is already being tracked. For new entities consider using an IIdentityGenerator to generate unique key values.

TagsToAddToTags function:
//it converts tags provided by user as a string, to tags as c# objects
public Note TagsToAddToTags(Note note)
        {
            string[] separators = { " " };
            List<string> tags = note.TagsToAdd.Split(separators, StringSplitOptions.RemoveEmptyEntries).ToList();
            note.NoteTags = new List<NoteTag>();
            note.TooManySpecialTags = false;
            foreach (var t in tags)
            {
                Tag tagInDb = db.Tags.FirstOrDefault(x => x.Name == t);

                if (tagInDb == null)
                {
                    tagInDb = db.Tags.Add(new Tag { Name = t }).Entity;
                }

                note.NoteTags.Add(new NoteTag { Tag = tagInDb});
            }

            return note;
        }

As the error suggests, you are ending up with two entity instances that represent the same NoteTag. The problem is that you query for all NoteTags from the database, then you also add all the incoming ones - and there are presumably some duplicates.
I would handle this by querying from the database, comparing the loaded NoteTags to the incomings ones, and then adding the new ones and removing the deleted ones.


chore: added doc for column freeze functionality

Adds documentation changes for the new feature column freeze
Issue: #837

@danciaclara I have got this PR reviewed, can you take this forward?

Closing this PR; content added by alternate PR


corrected a mangled unicode example

The documentation markdown source wasn't correctly encoding a single UTF-8 character, as well as having unbalanced single quotes and an en-dash that should have been a hyphen for a SQL comment.

Hi @edmacauley, would you review the proposed changes? Thanks.

@NReilingh, thank you kindly for fixing that error.  #sign-off


Webpack 4, bundle optimizations

Todo

[ ] Add deployment script for Cloudflare worker

Changelog
Added

Dynamically import the new editor and its renderer. This leads to a much smaller bundle size for the initial load.
Automated blue-green deployment of athene2-assets and server side renderer for new editor
Log version to browser console

Changed

Upgrade to Webpack 4

Fixed

Load all plugins in render server for new editor
When server side rendering fails, still pass state down to client for improved debugging

Breaking Changes

Removed CommonsChunkPlugin, i.e. there are no more commons.js and common.css
Renamed editor to legacy-editor, i.e. one has to include legacy-editor.js resp. legacy-editor.css instead of editor.js resp. editor.css
Asset bundle moved to https://packages.serlo.org/athene2-assets@a/ resp. https://packages.serlo.org/athene2-assets@b/ (blue-green deployment)
Google Cloud Function moved to https://europe-west1-serlo-assets.cloudfunctions.net/editor-renderer-a resp. https://europe-west1-serlo-assets.cloudfunctions.net/editor-renderer-b (blue-green deployment)

@Knorrke: can you please review the automated deployment script (mostly done, except for additional logs (e.g. webpack) and success checks (e.g. GET bundle)) https://github.com/serlo-org/athene2-assets/blob/ca8e94663b41c7ee1c24da90621e5b9fc00c3433/scripts/deploy.ts


Integration of Okta Authentication with Custom Login Screen

Describe the feature request?
am currently working on integrating Okta authentication into our company application. After reviewing the dynamic app example provided in the Okta IDX Android GitHub repository, I noticed that it displays its own login screens for user authentication.
However, I would like to retain our existing login screen and implement Okta authentication in the background. My goal is to allow users to enter their username and password on our custom UI while still leveraging Okta’s authentication services.
Could you please provide guidance on how to achieve this?
New or Affected Resource(s)
Android Application Developers
Provide a documentation link
No response
Additional Information?
Specifically, I’m looking for insights on:
How to bypass the default login screens provided by the Okta SDK.
How to programmatically authenticate users using Okta with the credentials collected from our custom login screen.

Hi @chowdarym05, here is a small sample I adopted from okta-idx-swift's basic login sample:
class BasicLogin {
    val flow: InteractionCodeFlow = InteractionCodeFlow()

    suspend fun login(username: String, password: String): OAuth2ClientResult<Token> {
        // Starts authentication, getting the first initial response. This
        // usually is a prompt to input the user's identifier (username), and
        // depending on policy settings, may also include a field for the user's
        // password.
        when (flow.start(redirectUri = Uri.parse(BuildConfig.REDIRECT_URI))) {
            is OAuth2ClientResult.Error -> TODO("Error case")
            else -> {
                // Do nothing
            }
        }

        var result = flow.resume()

        while (result is OAuth2ClientResult.Success && !result.result.isLoginSuccessful) {
            val response = result.result
            if (response.messages.messages.isNotEmpty()) {
                throw Exception(response.messages.messages[0].message)
            }

            // Look for username remediation and proceed, then do the same for password in the next iteration
            response.remediations.get(IdxRemediation.Type.IDENTIFY)?.let { usernameRemediation ->
                val usernameField =
                    usernameRemediation["identifier"] ?: throw Exception("No username field")
                usernameField.value = username
                result = flow.proceed(usernameRemediation)
            } ?: run {
                val passwordRemediation =
                    response.remediations.get(IdxRemediation.Type.CHALLENGE_AUTHENTICATOR)
                        ?: throw Exception("No username or password field")
                if (passwordRemediation.authenticators.get(IdxAuthenticator.Kind.PASSWORD) == null) throw Exception(
                    "Unexpected authenticator"
                )
                val passwordField = passwordRemediation["credentials.passcode"]
                    ?: throw Exception("No password field in password remediation")
                passwordField.value = password
                result = flow.proceed(passwordRemediation)
            }
        }

        val response = result.getOrThrow()
        if (response.isLoginSuccessful) {
            return flow.exchangeInteractionCodeForTokens(response.remediations[IdxRemediation.Type.ISSUE]!!)
        } else {
            throw Exception("Something went wrong")
        }
    }
}

Let me know if this helps with your use case. I will look to adding this sample into this repository for smoother experience

Hi Rajdeep, Thanks alot for the code snippet.
I am able to successfully implement okta login.

I am working on logout using credential.revokeToken(RevokeTokenType.ACCESS_TOKEN), and token refreshing part.
I am facing an issue here.

I am trying to store access token using  Credential.default = Credential.store(result.result)
But getting below exception:
java.lang.UnsatisfiedLinkError: dlopen failed: library "libsqlcipher.so" not found

Any suggestion here would be appreciated

Hi @chowdarym05, I wasn't able to reproduce this issue, but I found a similar issue reported on stackoverflow: https://stackoverflow.com/questions/70987929/java-lang-unsatisfiedlinkerror-after-changing-minsdkversion
The suggested fix is putting extractNativeLibs="true" in your app manifest. Could you check if that fixes your issue. I can update okta-mobile-kotlin with that if it fixes your issue


Revert "refactor(rect-query): prefer client-only import over 'use client'"

Reverts TanStack/query#5626

I'll try the real approach


Feature: Want to add twitter icon

Is your feature request related to a problem? Please describe.
Twitter icon is not there I want to add it.
Kindly assign it to me @sanjay-kv

After hovering

This issue already exist


brew bundle cleanup with cask 'docker' prints warning - but, doesn't work

Link to my Brewfile
As you can see, I use the cask version of docker.
Command that I ran: brew bundle cleanup --file=~/Brewfile
With the latest version of homebrew, I am getting the following warning:
Updating Homebrew...
Warning: Treating docker as a formula. For the cask, use homebrew/cask/docker
Would untap:
homebrew/services

brew --version output is:
Homebrew 2.5.12
Homebrew/homebrew-core (git revision 1d64f7; last commit 2020-11-30)
Homebrew/homebrew-cask (git revision 3b3b6; last commit 2020-11-30)

This is a known issue that will be fixed when Homebrew/brew 2.6.0 is released. It cannot be fixed before that.

I got the latest version of the master branch with this command:
git -C /usr/local/Homebrew checkout master && git -C /usr/local/Homebrew pull origin master

And this is still the error I get:
Updating Homebrew...
Warning: Treating docker as a formula. For the cask, use homebrew/cask/docker
Untapping homebrew/services...
Untapped 1 command (49 files, 372.7KB).


New release of Mx4PC Data Transfer tool (expected release date around October 11)

Our team is planning to release a new version of the Private Cloud data transfer tool this week, this PR contains updated release notes and a few small changes in its documentation.

@zlogic I've reviewed the file. Let me know when we're ready to publish.


initrd-flash: Add argument to format internal mmc partitions

Preparation for adding support to flash wic images on external devices

This seems like a too-specific addition to the script.  It might help if I could see more context around how this would enable use of wic for external devices (which might be relevant for #1323 as well).
Otherwise, I'd like to morph this into adding a generic mechanism for adding custom extensions to the initrd-flash process, maybe by installing extension scripts into a known location in the flashing initrd plus adding extension client-side script fragments into the tegraflash package that the initrd-flash script would automatically consume.  That way, if anyone has stuff they need to add to the flashing process for their specific needs, they can do that.

Look like this is very aligned with our use case in the Linux microPlatform (LmP) as it is to solve possible issues when we do an over the air update after moving the rootfile system from the internal mmc to the external nvme. I sent this ones separately because it was easy to decouple from all other patches on the serie I have.
I agree with you that the better approach for this is adding support for installing extension scripts as well as script fragments into the tegraflash to control them. I plan to come back to this in the next few weeks to add the pending patches so can try to implement such feature too.
Thank you very much for your input, which is always very valuable.

About the https://github.com/OE4T/meta-tegra/pull/1323: our implementation is to flash the wic on the nvme using the initrd flasher and using the tegra target to do that. We don't flash yet the nvme directly on the host machine for now.

@quaresmajose Can you take a look at #1535 and see if the generic callout implemented there would work for you?

@quaresmajose Can you take a look at https://github.com/OE4T/meta-tegra/pull/1535 and see if the generic callout implemented there would work for you?

This solution sounds good, I will adapt my patch with this generic callout and will do some tests.


Issue with Android 10 API 29

[Enter feedback here]
As I'm working with external storage for my App and Write and Read files. The issue comes when I target API 29 (Android 10) and the App crashes because access is denied even tho the user to this step granted permissions. But when I downgrade API level to 28 (Android 9) the App just works fine. Is there a new storage thing I must know ?

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

ID: 0297c8ec-f20a-6e75-91f0-15e3eaa17e02
Version Independent ID: e2be85c7-bd3c-ec8a-837f-b8784dc2b3c6
Content: File access on external storage with Xamarin.Android - Xamarin
Content Source: docs/android/platform/files/external-storage.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @davidortinau
Microsoft Alias: daortin

The specific code error on API 29 is by calling "WriteAllBytes".
File.WriteAllBytes(pathFile, myResultado);
Where pahtFile is: "/storage/emulated/0/" + "DocumentNameThatChanges" + ".pdf"
And "myResultado" is the byte array I get from my web service

Hi @AldairOrta
Thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Other channels you can use to seek help include Developer Community, the Xamarin Forums, and Stack Overflow.


Rack times out out of the box on stylesheet_link_tag and javascript_include_tag

Hi,
I did things as simply as possible:

orats new my_project
docker-compose up --build
everything launches correctly
going to <IP_ADDRESS>:3000

Then I got the following error:
Rack::Timeout::RequestTimeoutException in PagesController#home
Request ran for longer than 5000ms

The time out is on:
  <%= stylesheet_link_tag    'application', media: 'all', 'data-turbolinks-track': 'reload' %>

If I remove this line, I get the same error, but on the next line:
  <%= javascript_include_tag 'application', 'data-turbolinks-track': 'reload' %>

If I also remove this line, it works, but of course, I have no CSS nor JS.
Am I missing something ? Help please :)
More informations:

My environment:

OS X 10.11.6
docker version 1.11.1, build 5604cbe
docker-compose version 1.7.1, build 0a9ab35

The full stack is:
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in `visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:169:in `block in visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in `with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:168:in `visit_children'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `block in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:400:in `visit_prop'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in `block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in `with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in `with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `block (2 levels) in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `map'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `block in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in `with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:431:in `visit_rule'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in `block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in `with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in `with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `block (2 levels) in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `map'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in `block in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in `with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:431:in `visit_rule'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in `block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in `with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in `with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in `block (2 levels) in visit_import'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in `map'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in `block in visit_import'
sass (3.4.22) lib/sass/stack.rb:88:in `block in with_import'
sass (3.4.22) lib/sass/stack.rb:115:in `with_frame'
sass (3.4.22) lib/sass/stack.rb:88:in `with_import'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:325:in `visit_import'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in `block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in `with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in `with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in `visit'
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in `block in visit_children'
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in `map'
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in `visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:169:in `block in visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in `with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:168:in `visit_children'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `block in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:188:in `visit_root'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:159:in `visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:8:in `visit'
sass (3.4.22) lib/sass/tree/root_node.rb:36:in `css_tree'
sass (3.4.22) lib/sass/tree/root_node.rb:20:in `render'
sass (3.4.22) lib/sass/engine.rb:281:in `render'
sass-rails (5.0.5) lib/sass/rails/template.rb:47:in `evaluate'
tilt (2.0.5) lib/tilt/template.rb:102:in `render'
sprockets (3.6.3) lib/sprockets/legacy_tilt_processor.rb:25:in `call'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:75:in `call_processor'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in `reverse_each'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in `call_processors'
sprockets (3.6.3) lib/sprockets/loader.rb:134:in `load_from_unloaded'
sprockets (3.6.3) lib/sprockets/loader.rb:60:in `block in load'
sprockets (3.6.3) lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
sprockets (3.6.3) lib/sprockets/loader.rb:44:in `load'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:20:in `block in initialize'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:47:in `load'
sprockets (3.6.3) lib/sprockets/bundle.rb:23:in `block in call'
sprockets (3.6.3) lib/sprockets/utils.rb:196:in `dfs'
sprockets (3.6.3) lib/sprockets/bundle.rb:24:in `call'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:75:in `call_processor'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:57:in `block in call_processors'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in `reverse_each'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in `call_processors'
sprockets (3.6.3) lib/sprockets/loader.rb:134:in `load_from_unloaded'
sprockets (3.6.3) lib/sprockets/loader.rb:60:in `block in load'
sprockets (3.6.3) lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
sprockets (3.6.3) lib/sprockets/loader.rb:44:in `load'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:20:in `block in initialize'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:47:in `load'
sprockets (3.6.3) lib/sprockets/base.rb:66:in `find_asset'
sprockets (3.6.3) lib/sprockets/base.rb:92:in `[]'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:338:in `find_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:330:in `find_debug_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:212:in `block in lookup_debug_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:225:in `block in resolve_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in `each'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in `detect'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in `resolve_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:211:in `lookup_debug_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:153:in `block in stylesheet_link_tag'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:152:in `map'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:152:in `stylesheet_link_tag'
app/views/layouts/application.html.erb:12:in `_app_views_layouts_application_html_erb__2183925308731787587_69962785508040'
actionview (5.0.0) lib/action_view/template.rb:158:in `block in render'
activesupport (5.0.0) lib/active_support/notifications.rb:166:in `instrument'
actionview (5.0.0) lib/action_view/template.rb:348:in `instrument'
actionview (5.0.0) lib/action_view/template.rb:156:in `render'
rack-mini-profiler (0.10.1) lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout'
actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:14:in `render'
actionview (5.0.0) lib/action_view/renderer/renderer.rb:42:in `render_template'
actionview (5.0.0) lib/action_view/renderer/renderer.rb:23:in `render'
actionview (5.0.0) lib/action_view/rendering.rb:103:in `_render_template'
actionpack (5.0.0) lib/action_controller/metal/streaming.rb:217:in `_render_template'
actionview (5.0.0) lib/action_view/rendering.rb:83:in `render_to_body'
actionpack (5.0.0) lib/action_controller/metal/rendering.rb:52:in `render_to_body'
actionpack (5.0.0) lib/action_controller/metal/renderers.rb:144:in `render_to_body'
actionpack (5.0.0) lib/abstract_controller/rendering.rb:26:in `render'
actionpack (5.0.0) lib/action_controller/metal/rendering.rb:36:in `render'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
activesupport (5.0.0) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
/usr/local/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'
activesupport (5.0.0) lib/active_support/core_ext/benchmark.rb:12:in `ms'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
activerecord (5.0.0) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:43:in `render'
actionpack (5.0.0) lib/action_controller/metal/implicit_render.rb:36:in `default_render'
actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in `block in send_action'
actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in `tap'
actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
actionpack (5.0.0) lib/abstract_controller/base.rb:188:in `process_action'
actionpack (5.0.0) lib/action_controller/metal/rendering.rb:30:in `process_action'
actionpack (5.0.0) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
activesupport (5.0.0) lib/active_support/callbacks.rb:126:in `call'
activesupport (5.0.0) lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
activesupport (5.0.0) lib/active_support/callbacks.rb:455:in `call'
activesupport (5.0.0) lib/active_support/callbacks.rb:101:in `__run_callbacks__'
activesupport (5.0.0) lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
activesupport (5.0.0) lib/active_support/callbacks.rb:90:in `run_callbacks'
actionpack (5.0.0) lib/abstract_controller/callbacks.rb:19:in `process_action'
actionpack (5.0.0) lib/action_controller/metal/rescue.rb:20:in `process_action'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
activesupport (5.0.0) lib/active_support/notifications.rb:164:in `block in instrument'
activesupport (5.0.0) lib/active_support/notifications/instrumenter.rb:21:in `instrument'
activesupport (5.0.0) lib/active_support/notifications.rb:164:in `instrument'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
actionpack (5.0.0) lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
activerecord (5.0.0) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
actionpack (5.0.0) lib/abstract_controller/base.rb:126:in `process'
actionview (5.0.0) lib/action_view/rendering.rb:30:in `process'
rack-mini-profiler (0.10.1) lib/mini_profiler/profiling_methods.rb:102:in `block in profile_method'
actionpack (5.0.0) lib/action_controller/metal.rb:190:in `dispatch'
actionpack (5.0.0) lib/action_controller/metal.rb:262:in `dispatch'
actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:32:in `serve'
actionpack (5.0.0) lib/action_dispatch/journey/router.rb:39:in `block in serve'
actionpack (5.0.0) lib/action_dispatch/journey/router.rb:26:in `each'
actionpack (5.0.0) lib/action_dispatch/journey/router.rb:26:in `serve'
actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:725:in `call'
rack (2.0.1) lib/rack/etag.rb:25:in `call'
rack (2.0.1) lib/rack/conditional_get.rb:25:in `call'
rack (2.0.1) lib/rack/head.rb:12:in `call'
rack (2.0.1) lib/rack/session/abstract/id.rb:222:in `context'
rack (2.0.1) lib/rack/session/abstract/id.rb:216:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/cookies.rb:613:in `call'
activerecord (5.0.0) lib/active_record/migration.rb:552:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
activesupport (5.0.0) lib/active_support/callbacks.rb:97:in `__run_callbacks__'
activesupport (5.0.0) lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
activesupport (5.0.0) lib/active_support/callbacks.rb:90:in `run_callbacks'
actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:36:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
web-console (3.3.1) lib/web_console/middleware.rb:131:in `call_app'
web-console (3.3.1) lib/web_console/middleware.rb:20:in `block in call'
web-console (3.3.1) lib/web_console/middleware.rb:18:in `catch'
web-console (3.3.1) lib/web_console/middleware.rb:18:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.0) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.0) lib/rails/rack/logger.rb:24:in `block in call'
activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in `block in tagged'
activesupport (5.0.0) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in `tagged'
railties (5.0.0) lib/rails/rack/logger.rb:24:in `call'
sprockets-rails (3.1.1) lib/sprockets/rails/quiet_assets.rb:13:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.1) lib/rack/method_override.rb:22:in `call'
rack (2.0.1) lib/rack/runtime.rb:22:in `call'
rack-timeout (0.4.2) lib/rack/timeout/core.rb:122:in `block in call'
rack-timeout (0.4.2) lib/rack/timeout/support/timeout.rb:19:in `timeout'
rack-timeout (0.4.2) lib/rack/timeout/core.rb:121:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.0) lib/action_dispatch/middleware/static.rb:136:in `call'
rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
rack-mini-profiler (0.10.1) lib/mini_profiler/profiler.rb:278:in `call'
railties (5.0.0) lib/rails/engine.rb:522:in `call'
puma (3.4.0) lib/puma/configuration.rb:224:in `call'
puma (3.4.0) lib/puma/server.rb:569:in `handle_request'
puma (3.4.0) lib/puma/server.rb:406:in `process_client'
puma (3.4.0) lib/puma/server.rb:271:in `block in run'
puma (3.4.0) lib/puma/thread_pool.rb:114:in `block in spawn_thread'

Sorry for the long delay. You need to increase the rack timeout variable in
the .env file.
Five seconds is not enough time for your workstation. Try setting it to 30.
On Sep 15, 2016 3:28 PM, "teriiehina"<EMAIL_ADDRESS>wrote:

Hi,
I did things as simply as possible:

orats new my_project
docker-compose up --build
everything launches correctly
going to <IP_ADDRESS>:3000

Then I got the following error:
Rack::Timeout::RequestTimeoutException in PagesController#home
Request ran for longer than 5000ms
The time out is on:
<%= stylesheet_link_tag    'application', media: 'all', 'data-turbolinks-track': 'reload' %>
If I remove this line, I get the same error, but on the next line:
<%= javascript_include_tag 'application', 'data-turbolinks-track': 'reload' %>
If I also remove this line, it works, but of course, I have no CSS nor JS.
Am I missing something ? Help please :)
More informations:
[image: screen shot 2016-09-13 at 15 50 59]
https://cloud.githubusercontent.com/assets/435970/18564045/9b766cb2-7b25-11e6-87e6-9db68fe627a9.jpg
My environment:

OS X 10.11.6
docker version 1.11.1, build 5604cbe
docker-compose version 1.7.1, build 0a9ab35

The full stack is:
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in visit_children' sass (3.4.22) lib/sass/tree/visitors/perform.rb:169:in block in visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in with_environment' sass (3.4.22) lib/sass/tree/visitors/perform.rb:168:in visit_children'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in block in visit' sass (3.4.22) lib/sass/tree/visitors/perform.rb:400:in visit_prop'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in visit' sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in block in with_base' sass (3.4.22) lib/sass/stack.rb:115:in with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in with_base' sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in block (2 levels) in visit_rule' sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in map'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in block in visit_rule' sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:431:in visit_rule' sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in block in visit' sass (3.4.22) lib/sass/stack.rb:79:in block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in with_frame' sass (3.4.22) lib/sass/stack.rb:79:in with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in visit' sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in block (2 levels) in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in map' sass (3.4.22) lib/sass/tree/visitors/perform.rb:433:in block in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in with_environment' sass (3.4.22) lib/sass/tree/visitors/perform.rb:431:in visit_rule'
sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in visit' sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in block in visit'
sass (3.4.22) lib/sass/stack.rb:79:in block in with_base' sass (3.4.22) lib/sass/stack.rb:115:in with_frame'
sass (3.4.22) lib/sass/stack.rb:79:in with_base' sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in block (2 levels) in visit_import' sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in map'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:328:in block in visit_import' sass (3.4.22) lib/sass/stack.rb:88:in block in with_import'
sass (3.4.22) lib/sass/stack.rb:115:in with_frame' sass (3.4.22) lib/sass/stack.rb:88:in with_import'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:325:in visit_import' sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in block in visit' sass (3.4.22) lib/sass/stack.rb:79:in block in with_base'
sass (3.4.22) lib/sass/stack.rb:115:in with_frame' sass (3.4.22) lib/sass/stack.rb:79:in with_base'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:160:in visit' sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in block in visit_children'
sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in map' sass (3.4.22) lib/sass/tree/visitors/base.rb:52:in visit_children'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:169:in block in visit_children' sass (3.4.22) lib/sass/tree/visitors/perform.rb:181:in with_environment'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:168:in visit_children' sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in block in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:188:in visit_root' sass (3.4.22) lib/sass/tree/visitors/base.rb:36:in visit'
sass (3.4.22) lib/sass/tree/visitors/perform.rb:159:in visit' sass (3.4.22) lib/sass/tree/visitors/perform.rb:8:in visit'
sass (3.4.22) lib/sass/tree/root_node.rb:36:in css_tree' sass (3.4.22) lib/sass/tree/root_node.rb:20:in render'
sass (3.4.22) lib/sass/engine.rb:281:in render' sass-rails (5.0.5) lib/sass/rails/template.rb:47:in evaluate'
tilt (2.0.5) lib/tilt/template.rb:102:in render' sprockets (3.6.3) lib/sprockets/legacy_tilt_processor.rb:25:in call'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:75:in call_processor' sprockets (3.6.3) lib/sprockets/processor_utils.rb:57:in block in call_processors'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in reverse_each' sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in call_processors'
sprockets (3.6.3) lib/sprockets/loader.rb:134:in load_from_unloaded' sprockets (3.6.3) lib/sprockets/loader.rb:60:in block in load'
sprockets (3.6.3) lib/sprockets/loader.rb:317:in fetch_asset_from_dependency_cache' sprockets (3.6.3) lib/sprockets/loader.rb:44:in load'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:20:in block in initialize' sprockets (3.6.3) lib/sprockets/cached_environment.rb:47:in load'
sprockets (3.6.3) lib/sprockets/bundle.rb:23:in block in call' sprockets (3.6.3) lib/sprockets/utils.rb:196:in dfs'
sprockets (3.6.3) lib/sprockets/bundle.rb:24:in call' sprockets (3.6.3) lib/sprockets/processor_utils.rb:75:in call_processor'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:57:in block in call_processors' sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in reverse_each'
sprockets (3.6.3) lib/sprockets/processor_utils.rb:56:in call_processors' sprockets (3.6.3) lib/sprockets/loader.rb:134:in load_from_unloaded'
sprockets (3.6.3) lib/sprockets/loader.rb:60:in block in load' sprockets (3.6.3) lib/sprockets/loader.rb:317:in fetch_asset_from_dependency_cache'
sprockets (3.6.3) lib/sprockets/loader.rb:44:in load' sprockets (3.6.3) lib/sprockets/cached_environment.rb:20:in block in initialize'
sprockets (3.6.3) lib/sprockets/cached_environment.rb:47:in load' sprockets (3.6.3) lib/sprockets/base.rb:66:in find_asset'
sprockets (3.6.3) lib/sprockets/base.rb:92:in []' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:338:in find_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:330:in find_debug_asset' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:212:in block in lookup_debug_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:225:in block in resolve_asset' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in each'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in detect' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:224:in resolve_asset'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:211:in lookup_debug_asset' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:153:in block in stylesheet_link_tag'
sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:152:in map' sprockets-rails (3.1.1) lib/sprockets/rails/helper.rb:152:in stylesheet_link_tag'
app/views/layouts/application.html.erb:12:in _app_views_layouts_application_html_erb__2183925308731787587_69962785508040' actionview (5.0.0) lib/action_view/template.rb:158:in block in render'
activesupport (5.0.0) lib/active_support/notifications.rb:166:in instrument' actionview (5.0.0) lib/action_view/template.rb:348:in instrument'
actionview (5.0.0) lib/action_view/template.rb:156:in render' rack-mini-profiler (0.10.1) lib/mini_profiler/profiling_methods.rb:102:in block in profile_method'
actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:66:in render_with_layout' actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:52:in render_template'
actionview (5.0.0) lib/action_view/renderer/template_renderer.rb:14:in render' actionview (5.0.0) lib/action_view/renderer/renderer.rb:42:in render_template'
actionview (5.0.0) lib/action_view/renderer/renderer.rb:23:in render' actionview (5.0.0) lib/action_view/rendering.rb:103:in _render_template'
actionpack (5.0.0) lib/action_controller/metal/streaming.rb:217:in _render_template' actionview (5.0.0) lib/action_view/rendering.rb:83:in render_to_body'
actionpack (5.0.0) lib/action_controller/metal/rendering.rb:52:in render_to_body' actionpack (5.0.0) lib/action_controller/metal/renderers.rb:144:in render_to_body'
actionpack (5.0.0) lib/abstract_controller/rendering.rb:26:in render' actionpack (5.0.0) lib/action_controller/metal/rendering.rb:36:in render'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:44:in block (2 levels) in render' activesupport (5.0.0) lib/active_support/core_ext/benchmark.rb:12:in block in ms'
/usr/local/lib/ruby/2.3.0/benchmark.rb:308:in realtime' activesupport (5.0.0) lib/active_support/core_ext/benchmark.rb:12:in ms'
actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:44:in block in render' actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:87:in cleanup_view_runtime'
activerecord (5.0.0) lib/active_record/railties/controller_runtime.rb:25:in cleanup_view_runtime' actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:43:in render'
actionpack (5.0.0) lib/action_controller/metal/implicit_render.rb:36:in default_render' actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in block in send_action'
actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in tap' actionpack (5.0.0) lib/action_controller/metal/basic_implicit_render.rb:4:in send_action'
actionpack (5.0.0) lib/abstract_controller/base.rb:188:in process_action' actionpack (5.0.0) lib/action_controller/metal/rendering.rb:30:in process_action'
actionpack (5.0.0) lib/abstract_controller/callbacks.rb:20:in block in process_action' activesupport (5.0.0) lib/active_support/callbacks.rb:126:in call'
activesupport (5.0.0) lib/active_support/callbacks.rb:506:in block (2 levels) in compile' activesupport (5.0.0) lib/active_support/callbacks.rb:455:in call'
activesupport (5.0.0) lib/active_support/callbacks.rb:101:in __run_callbacks__' activesupport (5.0.0) lib/active_support/callbacks.rb:750:in _run_process_action_callbacks'
activesupport (5.0.0) lib/active_support/callbacks.rb:90:in run_callbacks' actionpack (5.0.0) lib/abstract_controller/callbacks.rb:19:in process_action'
actionpack (5.0.0) lib/action_controller/metal/rescue.rb:20:in process_action' actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:32:in block in process_action'
activesupport (5.0.0) lib/active_support/notifications.rb:164:in block in instrument' activesupport (5.0.0) lib/active_support/notifications/instrumenter.rb:21:in instrument'
activesupport (5.0.0) lib/active_support/notifications.rb:164:in instrument' actionpack (5.0.0) lib/action_controller/metal/instrumentation.rb:30:in process_action'
actionpack (5.0.0) lib/action_controller/metal/params_wrapper.rb:248:in process_action' activerecord (5.0.0) lib/active_record/railties/controller_runtime.rb:18:in process_action'
actionpack (5.0.0) lib/abstract_controller/base.rb:126:in process' actionview (5.0.0) lib/action_view/rendering.rb:30:in process'
rack-mini-profiler (0.10.1) lib/mini_profiler/profiling_methods.rb:102:in block in profile_method' actionpack (5.0.0) lib/action_controller/metal.rb:190:in dispatch'
actionpack (5.0.0) lib/action_controller/metal.rb:262:in dispatch' actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:50:in dispatch'
actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:32:in serve' actionpack (5.0.0) lib/action_dispatch/journey/router.rb:39:in block in serve'
actionpack (5.0.0) lib/action_dispatch/journey/router.rb:26:in each' actionpack (5.0.0) lib/action_dispatch/journey/router.rb:26:in serve'
actionpack (5.0.0) lib/action_dispatch/routing/route_set.rb:725:in call' rack (2.0.1) lib/rack/etag.rb:25:in call'
rack (2.0.1) lib/rack/conditional_get.rb:25:in call' rack (2.0.1) lib/rack/head.rb:12:in call'
rack (2.0.1) lib/rack/session/abstract/id.rb:222:in context' rack (2.0.1) lib/rack/session/abstract/id.rb:216:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/cookies.rb:613:in call' activerecord (5.0.0) lib/active_record/migration.rb:552:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:38:in block in call' activesupport (5.0.0) lib/active_support/callbacks.rb:97:in run_callbacks'
activesupport (5.0.0) lib/active_support/callbacks.rb:750:in _run_call_callbacks' activesupport (5.0.0) lib/active_support/callbacks.rb:90:in run_callbacks'
actionpack (5.0.0) lib/action_dispatch/middleware/callbacks.rb:36:in call' actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/remote_ip.rb:79:in call' actionpack (5.0.0) lib/action_dispatch/middleware/debug_exceptions.rb:49:in call'
web-console (3.3.1) lib/web_console/middleware.rb:131:in call_app' web-console (3.3.1) lib/web_console/middleware.rb:20:in block in call'
web-console (3.3.1) lib/web_console/middleware.rb:18:in catch' web-console (3.3.1) lib/web_console/middleware.rb:18:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/show_exceptions.rb:31:in call' railties (5.0.0) lib/rails/rack/logger.rb:36:in call_app'
railties (5.0.0) lib/rails/rack/logger.rb:24:in block in call' activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in block in tagged'
activesupport (5.0.0) lib/active_support/tagged_logging.rb:26:in tagged' activesupport (5.0.0) lib/active_support/tagged_logging.rb:70:in tagged'
railties (5.0.0) lib/rails/rack/logger.rb:24:in call' sprockets-rails (3.1.1) lib/sprockets/rails/quiet_assets.rb:13:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/request_id.rb:24:in call' rack (2.0.1) lib/rack/method_override.rb:22:in call'
rack (2.0.1) lib/rack/runtime.rb:22:in call' rack-timeout (0.4.2) lib/rack/timeout/core.rb:122:in block in call'
rack-timeout (0.4.2) lib/rack/timeout/support/timeout.rb:19:in timeout' rack-timeout (0.4.2) lib/rack/timeout/core.rb:121:in call'
actionpack (5.0.0) lib/action_dispatch/middleware/executor.rb:12:in call' actionpack (5.0.0) lib/action_dispatch/middleware/static.rb:136:in call'
rack (2.0.1) lib/rack/sendfile.rb:111:in call' rack-mini-profiler (0.10.1) lib/mini_profiler/profiler.rb:278:in call'
railties (5.0.0) lib/rails/engine.rb:522:in call' puma (3.4.0) lib/puma/configuration.rb:224:in call'
puma (3.4.0) lib/puma/server.rb:569:in handle_request' puma (3.4.0) lib/puma/server.rb:406:in process_client'
puma (3.4.0) lib/puma/server.rb:271:in block in run' puma (3.4.0) lib/puma/thread_pool.rb:114:in block in spawn_thread'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nickjj/orats/issues/15, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxoo_gAUm7Lo12JTxTMJn848UsaeLhiks5qqZxPgaJpZM4J-QNY
.

Hi @nickjj,
Even after upping the timeout to 30s, I have the same error. I have a 2,7 GHz Intel Core i5 with 16Gb of RAM. Using "vanilla" rails in a docker container doesn't give this error.
I guess I will have a look later, as I have to go forward on my current project.
thank you for your answer.

Hmm that should be plenty fast. You could try changing it to 300 and make sure you restart the server after this change.
If it's problematic you could also remove the rack timeout gem and rebuild the image.


Mobile manipulation

Hello,
Thank you for sharing your amazing research! Great work!
In regard to your paper on SLAP,  can you please elaborate on how PerAct and SLAP were deployed with mobile manipulation?
Specifically for PerAct, was the voxel grid size increased to cover the entire environment? And what are the camera views used to collect the data?

@zephirefaith can comment on this
We kept most parameters the same, are you referring to Stretch or Franka experiments?
For Stretch we used the head camera
For Franka we used a camera on the end of the arm, and just had it move to a couple predefined "look" poses on one side of a table

I was curious about the experiments on Stretch (Table 3 in the paper), since they involved mobile manipulation.
Since the stretch robot would be moving, for PerAct would the input voxel grid be static w.r.t to the world or would it be dynamic moving with the robot. And if the voxel grid dimensions were increased to cover the mobile manipulation scene

It's static wrt the robot base, so it will always be a fixed volume near the robot. Unfortunately we didn't end up doing whole scenes, although that's part of the plan - if you're interested in that direction, i think 3d-llm has a similar architecture with a perceiver backbone: https://vis-www.cs.umass.edu/3dllm/
So this seems to indicate the approach will scale.
You would/should apply this to a voxel grid in world coordinates if you wanted to do this.

Ah okay. Thank you for the information and additional directions! @cpaxton

Ah okay. Thank you for the information and additional directions! @cpaxton

@sriharshakoribille Glad to know you found our research useful! Thanks for responding @cpaxton, but to add some more detail: on Stretch we changed the voxel volume of PerAct's input to be 1.5mx1.5mx1.5m which is coarser than the one used for Franka. This is both due to the different embodiment and unconstrained scene geometry wrt robot's base.
Our experiments use PerAct in an open-loop manner, where every prediction is with respect to the 1st scene and 1st position of the end-effector wrt base-frame. Hope that clarifies things some. Please do not hesitate to reach out again and tag me for details.


Cannot include double quotes in search queries

Describe the bug
Including a double quote " character causes search query to fail
To Reproduce
Steps to reproduce the behavior:

Go to Datahub React UI
Search with double quotes

Expected behavior
It should not error
Screenshots
n/a
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This has been fixed in 0.8.0


set @quantity to the entire table, no matter what item is rolled

there are ways to do it without this option. i wont tackle this for now


Add requirements

Default command for new steps should include a pip install of requirements.txt
The requirements.txt will include valohai-utils as it's not part of any default Docker images, and needed to run scripts that use utils.
- pip install -r requirements.txt
- python myfile.py {parameters}

Updated tests as the default behavior has changed now.

You accidentally committed valohai/.DS_Store. Can you remove that and also add it to .gitignore.
Otherwise looks good.


[DOCS] Step-by-Guide-for adding Linkfree to GH profile

Description
I was scrolling through the Linkfree website to see if there was a guide on how to add the link of my Linkfree profile to my GitHub and Linkedin profiles, and I didn’t see one. I think it’ll be beneficial to add this section there.
Screenshots
No response
Additional information
No response

Hi can someone guide me on this issue?

Hi can someone guide me on this issue?

Maybe you can look at the format of the current guides and use them as a reference for creating the guide?

Hi can someone guide me on this issue?

Hi @pratushrai0309. Do you need clarity or an idea on how to write the guide?

Would be helpful 🙂

Hi can someone guide me on this issue?

Hi @pratushrai0309. Do you need clarity or an idea on how to write the guide?

Would be helpful 🙂
I'm visualizing a written guide with screenshots that show users how they can add a link to their Linkfree profile on their Github profile, social media accounts, Linkedin, and their website.  I came up with this because I was trying to do this myself and thought that other members might be having the same problem. Does that make sense now?

Actually I was asking if you could help me how to write the guide?

Actually I was asking if you could help me how to write the guide?

Sure! Formatting wise, I think we could do something like thisGetting Started

Here's what I have so far: https://docs.google.com/document/d/1UfYuyhEvpVCTY3B1v74WjIH94KiPaHmUfNPf32jf8d4/edit

Thanks everyone 👍
We have started making a big push on the docs, there is an open Pull Request that we are working on, and hopefully release the first version of the new docs in about 1 week https://github.com/EddieHubCommunity/LinkFree/pull/2208
You can see what it will look like on the beta deployment (this could break at anytime, so please don't use these links for your profile) https://beta.linkfree.eddiehub.io/docs/quickstart

hey! can i contribute to this

@eddiejaoude can u guide me on this issue , i need some clarity please provide me it would be a great help!

After some thought, we can't write docs for every platform, they have their own docs that are up to date. So I will close this issue.


BackgroundColor doen't work with DynamicResource.

Issue:
BackgroundColor doesn't work with DynamicResource.
Expected Behavior:
BackgroundColor work with DynamicResource.
Environment:
Platform: Windows, Android, iOS
.NET Version: 8.0.0
Mopups Version: 1.3.1
Maui Version: 8.0.6
Steps to Reproduce:

Clone Project.
Click the button
See that is not background and other components work the DynamicResource like the buttons.

Repro
https://github.com/MADSENSE/MADSENSE.MAUI.Sample.App/tree/BackgroundColor-not-work-with-dynamics

Working fine with Background={DynamicResource ...} instead of BackgroundColor={DynamicResource ...}

Working fine with Background={DynamicResource ...} instead of BackgroundColor={DynamicResource ...}

Had the same issue and this worked for me.

Working fine with Background={DynamicResource ...} instead of BackgroundColor={DynamicResource ...}

Thanks! Had same issue and workaround is also valid for me!

However, BackgroundColor is not working in the current version and should be fixed (worked in version 1.2.0).
Can confirm, that workaround with Background works!


How to get babel to transpile node_modules?

I just want to transpile one of the subfolders to node_modules but can't find out whether i do it in the .babelrc or the webpack config. How do I find good info on this?

it should not be your responsability as developer to transpile it

I disagree because as a developer, I want to run my app in different environments. The library author will not know which environment(s) I will run in, and I don't want to default to the worst-performing compiled code designed for IE 8. I'd like to target new browsers and old browsers with custom builds, so I transpile node_modules myself. Only a developer can do this, but not the library author (unless library author provides runnable build steps for compiling for various environments, but I have not seen any library author do that except for those at Meteor.com).

Plus, how far back should library author compile for in Node.js? What about in browsers? Only an app developer can truly make that decision.

@tomsoderlund I mean that it should be provided already transpiled, it should not be your responsability as developer to transpile it

Why should a library developer decide up to which browser version his library is supported? A library developer should use latest-and-greatest ES features when writing his library code. Only the developer building the end product which will eventually run on customer browser should decide the level of browser support.
If I'm using ten different libraries in my project and all the ten library developers transpile their code to different browser support, how will I have control over the browser support of the end product. When I use target in my .babelrc, I expect the final generated code, including the ones in node_modules to support that specific target browsers, and not just the code I wrote.

@timneutkens Sorry to drag up an old/recurring topic, but what's the official stance on this?
We recently ran into it here: https://github.com/isaachinman/next-i18next/issues/191
I agree that it should be up to the end user to decide what targets are appropriate for them.

I just ran into the problem because I'm using<EMAIL_ADDRESS>which is distributed as a ES2018 source (uses for/of and spread syntax), but I need to support IE11. Because next is not transpiling anything in node_modules the webpage fails at runtime due to a parse error.

This is a problem for the JavaScript community in general - it's not specific to Next.
Off the top of my head, what there was a webpack plugin that, instead of fully ignoring node_modules, checked for the presence of package.module and transpiled the dep in that case, but otherwise ignored it?
Seems like something similar already exists, although it doesn't seem to be used by many people.

You can't use the presence of "modules" as a signal whether you should transpile or not. Even if the package uses normal entry point (ie. "main") it doesn't mean it's IE11 compatible. There are packages which use "main" but also use modern JS syntax.
Transpiling everything would be safest, but would add some overhead during production builds.

@wereHamster What signal do you suggest? It's absolutely not safe to retranspile previously transpiled code.

I was not aware that it's not safe. Can you point me towards potential issues when transpiling already processed source code?

It's absolutely not safe to retranspile previously transpiled code.

How so? 🤔 transpiled code is still 100% valid javascript code...

I'm really confused why people keep posting here while we have an open issue for node_modules compilation / other solutions here: #706.

How so? 🤔 transpiled code is still 100% valid javascript code...

I think Isaac is referring to the fact that if you run Typescript on Babel output it breaks, same in reverse. Similar things used to happen with webpack, but webpack mitigates it pretty well.

My fault, let's lock this in favour of #706.


Body missing ApplyBuoyancyImpulse

I am adding an ApplyBuoyancyImpulse method, and am on the latest 0.11.0. I can see the method in the IDL in the repository, but the body is missing it at runtime. I checked the example, and I should have the same setup:

Nevermind, user error. I was not on the latest build.

Do you have the same error with npm
when new jolt version released
you do npm update
but then no new version installed
I have to remove package and then install, to get new version
npm r jolt-physics
npm i jolt-physics

other packages updating fine

Yeah, I have the same issue. I remove the line jolt-physics module line in the package.json, then it adds the latest. Not sure what's up.


[CS2103T-W11-2] JARVIS

As the cohort of NUS computing students increases over the years, the workload of the computing tutors is bound to increase. Fret not because JARVIS, a program that specializes in alleviating the cumbersome administrative tasks of tutoring, is here to aid the CS1101S avengers!

Codecov Report

Merging #74 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #74   +/-   ##
=========================================
  Coverage     72.31%   72.31%
  Complexity      400      400
=========================================
  Files            70       70
  Lines          1228     1228
  Branches        124      124
=========================================
  Hits            888      888
  Misses          308      308
  Partials         32       32

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 6389d85...dd95c41. Read the comment docs.

Codecov Report

Merging #74 into master will decrease coverage by 19.70%.
The diff coverage is 23.51%.

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


You must specify an object for the Get-Member cmdlet

scoop update docker-desktop
docker-desktop: 4.16.2 -> 4.16.3
Updating one outdated app:
Updating 'docker-desktop' (4.16.2 -> 4.16.3)
Downloading new version
Starting download with aria2 ...
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: b63527|OK  |    23MiB/s|D:/scoop_user_apps/cache/docker-desktop#4.16.3#https_desktop.docker.com_win_main_amd64_96739_Docker_20Desktop_20Installer.exe_DockerDesktopInstall.exe
Download: Status Legend:
Download: (OK):download completed.
Checking hash of Docker%20Desktop%20Installer.exe ... ok.
Uninstalling 'docker-desktop' (4.16.2)
Running uninstaller... done.
Unlinking D:\scoop_user_apps\apps\docker-desktop\current
Installing 'docker-desktop' (4.16.3) [64bit] from dev-tools bucket
Loading Docker%20Desktop%20Installer.exe from cache.
Running installer... done.
Linking D:\scoop_user_apps\apps\docker-desktop\current => D:\scoop_user_apps\apps\docker-desktop\4.16.3
Running post_install script...
Get-Member: D:\scoop_user_apps\apps\scoop\current\libexec\scoop-hold.ps1:58
Line |
  58 |      $json | Get-Member -MemberType Properties | ForEach-Object { $ins …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You must specify an object for the Get-Member cmdlet.
docker-desktop is now held and can not be updated anymore.
'docker-desktop' (4.16.3) was installed successfully!
Notes
-----
All files will be installed into DEFAULT docker directory. (C:\Program Files\Docker)
I suggest to change the docker images location:
https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file

Updating is handled by docker itself.
Run 'scoop hold docker-desktop' to disable updates via Scoop.

'scoop uninstall docker' will uninstall docker completely.
Images, VM, settings, ...

Cannot reproduce, i tried to run it and it ran without any problems:
PowerShell 7.3.4
PS C:\Windows\System32> scoop install anderlli0053_DEV-tools/docker-desktop
WARN  This is a nightly version. Downloaded files won't be verified.
Installing 'docker-desktop' (nightly-20230430) [64bit] from anderlli0053_DEV-tools bucket
Loading Docker%20Desktop%20Installer.exe from cache.
Running pre_install script...

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Error: 5

An error occurred while creating the log file.
Ensure that the path to the log file exists and that you have Read/Write permissions on the folder where the log files will be created.

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Error: 5

An error occurred while creating the log file.
Ensure that the path to the log file exists and that you have Read/Write permissions on the folder where the log files will be created.
Running installer... done.
WARN  Installer added 'C:\Users\ander\scoop\apps\docker-desktop\nightly-20230430\resources\bin' to system path. You might want to remove this manually (requires admin permission).
Linking ~\scoop\apps\docker-desktop\current => ~\scoop\apps\docker-desktop\nightly-20230430
Creating shim for 'docker'.
'docker-desktop' (nightly-20230430) was installed successfully!
Notes
-----
Conditions:
refer to the:
https://learn.microsoft.com/en-us/windows/wsl/install
PS C:\Windows\System32>


Added support for template parameters

When using templates, you can configure the root node of the template by setting expressions on the importing node, but this offers rather limited control over customization. Ideally, you want to be able to configure properties of nodes inside the template, and that's where parameters come in.
You define parameters by adding <param/> nodes inside an ordinary Layout node:
<!-- MyTemplate.xml -->
<UIView>
    <param name="text" type="String"/>
    <param name="image" type="UIImage"/>

    <UIImageView image="{image}"/>
    <UILabel text="{text}/>
</UIView>

Each <param/> node has a name and type attribute. The parameter defines a symbol that can be referenced by any expression defined on the containing node or any of its children.
Parameters can be set using expressions on the importing node:
<UIView
    template="MyTemplate.xml"
    text="Lorem ipsum sit dolor "
    image="Rocket.png"
/>

You can set default values for parameters by defining a matching expression on the containing node. It will be overridden if the same expression is defined on the importing node:
<!-- MyTemplate.xml -->
<UIView text="Default text">
    <param name="text" type="String"/>
    ...
</UIView>

<UIView
    template="MyTemplate.xml"
    text="Lorem ipsum sit dolor "
    image="Rocket.png"
/>

Any concern about amguity (either literal, or perceived) between these custom parameters and properties on the class? I'm guessing the/a problem is you can't introduce differentially syntax (e.g. \text="") without breaking XML..

Got it. My 2¢ for when you revisit this stuff is the addition of namespaces like 'state.x', 'const.x', 'param.x' would be great for clarity, even if optional.


Remove hardcoded limit of 4 bone weight influences

This PR aims to remove the hardcoded limit of 4 bone weight influences.
I have tested it manually on a few skeletal meshes from a game that use 8 bone weight influences, and it seems to work.
However, I couldn't try out the glTF export, since it seems to be broken on the current master branch (throws a NullReferenceException when exporting)?

looks fire!! i don't think this would work properly with psk though bc the importers are hardcoded to 4 weights afaik so that may need to be looked at before merging

looks fire!! i don't think this would work properly with psk though bc the importers are hardcoded to 4 weights afaik so that may need to be looked at before merging

Thank you, half! ❤ I have tested the change with both io_scene_psk_psa (DarklightGames) and BlenderPSKPSA (Zain), and both of those Blender addons seem to handle the additional influences without issue. 😊
I think the only obstacle to merging this change is that the 4 weight limit is also hardcoded into FModel's animation snooper code. 😿

snooper is probs an easy fix, I'm not too familiar but I don't think it should be terribly hard
also a lot of people probably still use the old psk importer so maybe give that a go too? (https://github.com/Befzz/blender3d_import_psk_psa)

confirmed works with befzz importer and fixes issues with weights on fortnite skins, will merge


Automating overrides for trivial KSP updates

My initial partially manual process
Given a mod name, basic algorithm is look at highest version CKAN file, make sure its checked for ksp 1.0.2, then create the branch with that name, use a sed script to add the override cod substituting in the version scraped off the CKAN file, build the result with netkan.exe, and if that's all clean, move the resultant CKAN file into a review directory just in case, then commit the changes to my local branch, and checkout the master, push the branch from local to my github fork
once that's done, I open the ckan file for review, if it looks sane, then I would do a test install, and then go to github and start the PR.  If there is an easy way to test the CKAN file then I could probably automate the whole thing.  This would allow iteration on a list of mods.
So in that usage, generate the list by finding all the mods that list compatibility with a specific version we are looking to override, and make the list from that, then iterate the override script on each of those mods.
That way CKAN admins could automatically override something like the 1.0.3 to 1.0.4 safe patch for apps that are already at 1.0.3 - but not 1.0.2 -> 1.0.4 until the authors or forums agree its stable.  And in the event that bunches are trickling in, those could be batched to have the same thing done, maybe even have an automated way for authors to trigger an override via this script (maybe the indexing bot would detect something that would be a signal from the author to override)
Anyway, at least for hotfixes, it should help get a lot more mods available and "current" for users very quickly.
Initial chat: http://pastebin.com/G6BBRVek

this can be done in a shell script.  Or if you want, perl or python.

Would you be interested in writing up a wiki page with your code so that it's documented and easy to find?

Sure, just need to get some time. Been a bit busy lately with my hospital
duties. Heat brings on heart attacks, and I'm in Texas and it's mid summer.
On Thursday, July 16, 2015, Matthew<EMAIL_ADDRESS>wrote:

Would you be interested in writing up a wiki page
https://github.com/KSP-CKAN/CKAN/wiki/_new with your code so that it's
documented and easy to find?
—
Reply to this email directly or view it on GitHub
https://github.com/KSP-CKAN/NetKAN/issues/1796#issuecomment-122142414.

Everything can be solved by giving more NS =)

Closing this as https://github.com/KSP-CKAN/CKAN/pull/1499 should mostly address this.


[nrf noup] ci: use ci-tools in west manifest

also report PENDING to github with callback link
Signed-off-by: Thomas Stilwell<EMAIL_ADDRESS>

Some checks failed. Please fix and resubmit.
checkpatch (informational only, not a failure)
-:423: WARNING:LONG_LINE: line over 80 characters
#423: FILE: subsys/testsuite/ztest/include/ztest_test.h:161:
+	ztest_user_unit_test_setup_teardown(fn, z_test_1cpu_start, z_test_1cpu_stop)

-:839: WARNING:LONG_LINE: line over 80 characters
#839: FILE: tests/kernel/lifo/lifo_usage/src/main.c:471:
+			 ztest_1cpu_unit_test(test_timeout_threads_pend_on_lifo));

-:863: WARNING:LONG_LINE_COMMENT: line over 80 characters
#863: FILE: tests/kernel/mbox/mbox_api/src/main.c:34:
+			 ztest_1cpu_unit_test(test_mbox_kinit),/*keep init first!*/

-:873: WARNING:LONG_LINE: line over 80 characters
#873: FILE: tests/kernel/mbox/mbox_api/src/main.c:41:
+			 ztest_1cpu_unit_test(test_mbox_target_source_thread_block),

-:891: WARNING:LONG_LINE: line over 80 characters
#891: FILE: tests/kernel/mbox/mbox_api/src/main.c:52:
+			 ztest_1cpu_unit_test(test_mbox_async_put_to_waiting_get),

-:1030: WARNING:LONG_LINE: line over 80 characters
#1030: FILE: tests/kernel/mem_protect/sys_sem/src/main.c:589:
+			ztest_1cpu_user_unit_test(test_sem_take_timeout_forever),

-:1034: WARNING:LONG_LINE: line over 80 characters
#1034: FILE: tests/kernel/mem_protect/sys_sem/src/main.c:592:
+			ztest_1cpu_user_unit_test(test_sem_multiple_threads_wait));

-:1222: WARNING:LONG_LINE: line over 80 characters
#1222: FILE: tests/kernel/mutex/mutex_api/src/test_mutex_apis.c:149:
+			 ztest_1cpu_user_unit_test(test_mutex_reent_lock_forever),

-:1226: WARNING:LONG_LINE: line over 80 characters
#1226: FILE: tests/kernel/mutex/mutex_api/src/test_mutex_apis.c:152:
+			 ztest_1cpu_user_unit_test(test_mutex_reent_lock_timeout_pass)

-:1324: WARNING:LONG_LINE: line over 80 characters
#1324: FILE: tests/kernel/pipe/pipe_api/src/main.c:65:
+			 ztest_1cpu_user_unit_test(test_pipe_user_thread2thread),

-:1546: WARNING:LONG_LINE: line over 80 characters
#1546: FILE: tests/kernel/semaphore/semaphore/src/main.c:774:
+			 ztest_1cpu_user_unit_test(test_sem_take_timeout_forever),

-:1555: WARNING:LONG_LINE: line over 80 characters
#1555: FILE: tests/kernel/semaphore/semaphore/src/main.c:781:
+			 ztest_1cpu_unit_test(test_sem_multiple_take_and_timeouts),

-:1638: WARNING:LONG_LINE: line over 80 characters
#1638: FILE: tests/kernel/threads/thread_apis/src/main.c:294:
+			 ztest_1cpu_unit_test(test_threads_suspend_resume_cooperative),

-:1655: WARNING:LONG_LINE: line over 80 characters
#1655: FILE: tests/kernel/threads/thread_apis/src/main.c:306:
+			 ztest_1cpu_user_unit_test(test_customdata_get_set_preempt),

-:1781: WARNING:LONG_LINE: line over 80 characters
#1781: FILE: tests/kernel/workq/work_queue_api/src/main.c:537:
+			 ztest_1cpu_user_unit_test(test_user_work_submit_to_queue_thread),

-:1782: WARNING:LONG_LINE: line over 80 characters
#1782: FILE: tests/kernel/workq/work_queue_api/src/main.c:538:
+			 ztest_1cpu_unit_test(test_delayed_work_submit_to_queue_thread),

-:1783: WARNING:LONG_LINE: line over 80 characters
#1783: FILE: tests/kernel/workq/work_queue_api/src/main.c:539:
+			 ztest_1cpu_unit_test(test_delayed_work_submit_to_queue_isr),

-:1786: WARNING:LONG_LINE: line over 80 characters
#1786: FILE: tests/kernel/workq/work_queue_api/src/main.c:542:
+			 ztest_1cpu_unit_test(test_delayed_work_cancel_from_queue_thread),

-:1787: WARNING:LONG_LINE: line over 80 characters
#1787: FILE: tests/kernel/workq/work_queue_api/src/main.c:543:
+			 ztest_1cpu_unit_test(test_delayed_work_cancel_from_queue_isr),

- total: 0 errors, 19 warnings, 1239 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Your patch has style problems, please review.

NOTE: Ignored message types: AVOID_EXTERNS BRACES CONFIG_EXPERIMENTAL CONST_STRUCT DATE_TIME FILE_PATH_CHANGES MINMAX NETWORKING_BLOCK_COMMENT_STYLE PRINTK_WITHOUT_KERN_LEVEL SPLIT_STRING VOLATILE

NOTE: If any of the errors are false positives, please report
      them to the maintainers.

Gitlint issues
Commit 8134f0f47c:
1: UC5 Title exceeds max length (82>75): "[nrf fromtree] tests/kernel/sched/schedule_api: Relax preemption order constraints"
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

Zephyr history was rewritten in preparation for the next release. Please rebase this PR.


How to conditional include in lexer for language dialects?

(Original issue 1059 created by adamretter on 2014-11-10T23:55:20.677287+00:00)
Hey guys,
I have been working on a number of updates to the XQuery Lexer, my current progress is here: https://bitbucket.org/adamretter/pygments-main/commits/all
I am now looking for something like a conditional version of include in my lexer. I want to take a 'dialect' option which I have figured out how to do. However, I want to enable/disable rules in my 'root' lexer depending on the 'dialect' option. Can you suggest a way to do this?
For example, the existing XQuery Lexer (before I event started) already had some rules that are specific to the MarkLogic implementation of XQuery rather than the W3C standard: https://bitbucket.org/adamretter/pygments-main/src/f9e0dba6d236199ff171923dfff03efb0cf819c9/pygments/lexers/webmisc.py?at=default#cl-729
Ideally, I would like to disable these by default but have them enabled when the dialect=marklogic option is set.

(Original issue 1059 last updated on 2014-11-23T17:55:48.781330+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by tshatch on 2014-11-13T14:36:24.029901+00:00)
I can think of a few different ways.

If possible, make a single lexer highlight any syntax without setting options.  We did this with BashLexer and MakeLexer, and get approx. 0 complaints.
Move a lot of logic to outside the tokens dict, and instead in the more generally line-based get_tokens_unprocessed.  The haskell Literate* family does this.
Do it with a callback, if it's just different keywords being builtins.  See PhpLexer's funcnamehightlighting.
Do something hacky like CSharpLexer's unicodelevel.  shudder
Make more than one lexer.  We do this with Python3Lexer and the MozPreproc* family.

(Original comment by adamretter on 2014-11-23T17:55:39.466920+00:00)
Okay thanks

(Original comment by adamretter on 2014-11-23T17:55:48.795343+00:00)
Done.


install_requires should fix dependencies to specific versions

The install_requires value in setup.py does not specify the exact versions (dependency==0.1.0) and / or version bounds (dependency<=0.2). This means that someone could install this project a year from now and it may not work because a dependency could have introduced a backwards incompatible change. It's therefore better to specify the versions and upgrade them yourself when you've verified that a newer version of a dependency works fine with this project.

You should not assume that a major update of a dependency will certainly break your application.
specifying minimum version is great,
but maximum versions easily leads to dependency-hell.
Only specify them if:

you know for certain your app will break
you are now to going fix that


Enhanced DistributedObjectAdmin to compare for inconsistencies between instances

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[ ] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Hoist-core PR: https://github.com/xh/hoist-core/pull/426
No toolbox PR.

I think the UI can be adjusted a bit to take better advantage of the space
how about we make the main tree grid narrow, allowing the wide instance grid to go to the right, with the instance detail below it?
Would also like to see a single button for "Clear All Hibernate Caches" in the top toolbar.  The ability to clear individual hibernate caches can appear as a context menu item, only appearing if entire selection is made up of Hibernate caches


Multiple expect pattern fails in race conditions

Describe the bug
"Greed tests" fails
To Reproduce
import wexpect

p = wexpect.spawn('python list100.py', maxread=1)
assert p.expect(['1, 2, 3', '2,']), 1

The list100.py can be found in tests directory.
Expected behavior
To pass the assertion.
Environment:

OS Name  Microsoft Windows 10 Home
Version  10.0.18362 Build 18362
Python 3.7.5
wexpect v2.3.9

Fixed in v4.0.0


Instance Unification

Proposal for unified isFlowerPot detection
Whilst it is well understood at this point that a well-specified and suitably future-proof API for Minecraft will need to be appropriately decoupled from Minecraft internals to withstand future changes to the underlying platform as effectively as possible, there are some aspects of the underlying platform which are intrinsically immutable and thus safe to propagate up to the API layer.
In many cases it is fully possible to achieve high levels of abstraction within the API, as demonstrated by the recent additions of the Inventory API and Item Data API. However there are still places where abstraction simply does not provide any measurable benefit to the end user, and adhering more faithfully to the internal architecture of the underlying Minecraft platform has no immediate or developer-facing drawbacks.
Where we can achieve some tangible improvement however is in homogenising developer-facing interfaces in order to provide a consistent and intuitive aspect-oriented development paradigm, reinforced by rigid adherance to integrated vertical software development disciplines.
The Chaos at the Heart of Minecraft
With Minecraft, what you see is not always what you get. Crowd-sourced names for internal API structures can often fall somewhat short of making any sense whatsoever, but still provide valuable insight for newcomers into Minecraft internals, albeit tainted by occasionally apocryphal or sometimes downright nonsensical assignment of meaning to something that the assignor didn't understand or couldn't be bothered to decipher. Nevertheless, these little curios persist in the deobfuscated Minecraft codebase, and their legacy is one of some entertainment and wry humor when the truth of a particular field or method's origins come to light.
The typical ways of dealing with these conflicts between the status quo and common sense resolve into two camps:

Argue about it pretty much forever
Accept the nonsense and move on

An example of the former is the most hotly contested field of all time World.isRemote, sorry I meant World.isClient or is that World.isR... okay, okay I'll stop. However one of the most notable examples of the latter is the somewhat controversially named isFlowerPot method in Minecraft's Block class.
This method and its somewhat peculiar naming was the subject of some discussion until a Mojangsta was nailed down and forced to cough up the original name, which turned out to be something like handlesOwnClone, however the charm of the original (kind of quirky and entertaining) isFlowerPot was just too strong, and the method maintains its apocryphal nomenclature to this day.
ClassLoading and You - a song of ice and fire soliloquy in five parts
Everyone is aware that Sponge is powered by black magic Mixins, however Class Loading in Java is a complex topic and Mixins are unable to adequately solve every problem we might throw at them. Fundamental to the successful application of Mixins is the core idea that a mixin is used to implement some aspect of the defined API.
isFlowerPot thus presents a problem. How can we adequately represent whether or not something is a flowerpot or not if we don't adequately encode this crucial information in the developer-facing portions of the API?
The answer is: define this information explicitly in each interface.
Taking a purely java-based approach to solving this problem alleviates several issues which would otherwise be caused. Whilst we could of course inject the required code at runtime, this rapidly becomes a very expensive operation when we factor in the sheer number of classes involved, and also the potential conflicts it creates with other non-flowerpot-aware code.
The beauty of this extremely elegant and efficient implementation approach is that it provides a unified and 100 percent intuitive way of determining whether literally any object is or is not a flowerpot at runtime, without introducing complex transformer logic or polluting existing mixins with unrelated code. This allows mixins to focus on their task of implementing literally everything, whilst isFlowerPot logic can be handled in pure Java at a fundamental level within both the API and the Sponge implementation.
Implemented by Sponge#217

This PR no longer is mergable. Please address.

Poor Travis... RIP

Travis should only check the very last commit.

@Zidane I don't know what you're talking about.

Why is this under a 'hotfix' branch? This is a pretty important and all-encompassing PR. I argue that since the success of the project depends on this PR, we should put it under the 'urgent/instance-checks' branch.

When did this become a thing also what magic creates 300+ commits?

When did this become a thing

It became a thing today.

what magic creates 300+ commits?

Time... Also, not all commits (and their messages) are the same ;)

Diff summary: https://gist.github.com/CptSpaceToaster/e9f5aea794d069c0ab92

I can't tell you how many times I needed to know when a block was a flower pot.  This is a godsend.

internal crying

I am confused.
The only part of this PR i get is that it has nothing to do with flowerpots, but the flowerpot is a well known term/name.
Can somebody please describe the purpose of that method to me?
And i also have some more general questions.
Why isnt there a usefull interface declaration? If every class is FlowerPotable. This will really improve code cleanless and provide a usefull location for additional javadocs. Which are defenitly are needed if you ask me.
Why do our static enum like classes needs flower pots as well?

8/10 Not enough flower pots - IGN

I commented on the changes. Please fix or I'll close tonight.

Happy April Fools!


SLIM-710: Deletes a scheduled task on failure

All is well.

All is well.

All is well.

All is well.

All is well.


Added a  new rebus

Associated Issue: #121
Summary of Changes

Added new rebus, a little bit thematic

Message to dear maintainers
I hope it is going to be merged before the solution of this rebus 🎃
Thank you for nice way to learn how to create first contribution,
Kind Regards, Łukasz

Pull Request Test Coverage Report for Build 676

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Local communication support

Inspired by https://github.com/vanackej/risco-lan-bridge, local support in Python will enable a native HA integration without reliance on Risco cloud on the one hand, or external components (e.g. mqtt) on the others.
I started to implement it in the local_comm branch. The encoding and encryption / decoding and decryption part is already implemented, and confirmed agains the test cases in https://github.com/vanackej/risco-lan-bridge/blob/main/test/crypto.test.ts
Next up is the socket part. I'll only be implementing the direct mode, since there's no easy way to run a proxy from within HA, and the proxy doesn't have to be tied to the library - it probably makes more sense to implement it as an external component and point the library at it.
@vanackej would love your support on this if possible.

Ok so you consider a full port of the library in python ? Good news !
I agree that proxy mode is a pain to maintain. I only kept it because the original creator of the library started implementing it, but it's really complex to maintain and has a lot of edge cases.
The socket communication layer is not really simple to implement by itself, because of the encyption issues, unexpected data buffer that are sometime sent by the panel, socket disconnection when inactivity, duplicated response received, switching from unencrypted communication to enrypted communication, device discovery part, ...
I really encourage you to port the typescript library as close as possible to my code, as I spent a lot of time making it work correctly.
I'll be happy to help you if you have any question, just let me know.

I'm definitely seeing some of the finer points come up, but I already have the encryption working, and initial socket implementation working as well - I'm able to send commands and get responses.
I deviated quite a lot from the typescript library, because I'm giving up on a lot of features so I'm able so simplify:

No proxy - like I said, it could be external
No code or panel id discovery. If someone is looking to brute force the system, they can write their own script
No enabling/disabling of cloud. Once again, I think this can be done outside the library. If I understand correctly, that also means I don't have to support programming commands.

I was having a hard time with the random clock commands I'm getting (took me a while to realize those weren't responses to my commands - I kept thinking I was doing something wrong), or with commands that included \x03 not in the final position, but I got over those.
Would love to find time we can maybe go over it together?


Josdk version update

Updated JOSDK version to 4.3.0.

You can remove this PR. I obviously did something wrong. Sorry :)


[docs] integrate app template components

Our docs should exemplify how vivid is integrated from the ground up.
All app template scaffolding should include vivid

top app bar
side drawer
layout

blocked by vonage/vivid#1229
importing components from skypack reveals missing dependency issues 👆


Fix undefined function

We are using your excellent library in a React Native project, and stumbled onto an issue where some native elements would trigger the throttled functions without any callback. This would trigger a unhandled exception that would crashes the application.
To fix this I simply added the optional chaining operator ?. to the function_ argument, so that if function_ is not set - it will not be called.

I think this is something you should handle, not the throttle function. The throttle is documented to accept a non-optional function (in readme and TS). Either guard the call, or pass in a noop function as fallbacK; throttle(foo ?? () => {}).

Alright, thanks for the feedback - I think using a noop function instead as fallback is a good idea. :thumbsup: