Peer to peer best practices review

For this feature I did the following

Copied code from my Todo list project
Made a github issue for reference
Updated the readme file
Here is the link to the github issue: https://github.com/Chimoneg27/To-Do-List/issues/5

Hi @Chimoneg27
Your project is complete! There is nothing else to say other than... it's time to merge it
Congratulations!

Highlights
✅ Linters are passing ✅ Good commit history ✅ Good Pull Request description
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
[OPTIONAL] Please consider refactoring your code into modules. Ideally, all your functions should be in different files/modules and then imported into the main index.js file. This is considered good practice as it is easier to maintain, update, and debug your code. You may extract these functions into separate modules:

saveTodo, checkTodo, deleteTodo, editTodo

[OPTIONAL] I have noticed you have not used ES6 arrow functions consistently throughout your project. Using ES6 arrow functions is considered neater in JavaScript best practices. You may consider refactoring in the next PR.
Cheers and Happy coding!:aplauso::aplauso::aplauso: Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.._)

Thanks for the review Edwin. I'm applying some of those changes now


Increase timeout in QuorumCommandIntegrationTest

This change should help reduce some of the test flakiness we're
seeing in builds on jenkins

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5074/
Test PASSed.

alluxio-bot, merge this please.


Panic on server with cores more than 40

run test_single.sh
error:
thread '<unnamed>' panicked at 'received 4 elements to spawn 16 threads', thread '/root/.cargo/git/checkouts/bellman-7a75f3b44e91e034/416f79d/src/multicore.rs<unnamed>:' panicked at '122received 4 elements to spawn 16 threads:', thread '9/root/.cargo/git/checkouts/bellman-7a75f3b44e91e034/416f79d/src/multicore.rs<unnamed>thread '
<unnamed>:' panicked at 'note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
' panicked at '122received 4 elements to spawn 16 threadsreceived 4 elements to spawn 16 threads:', ', 9/root/.cargo/git/checkouts/bellman-7a75f3b44e91e034/416f79d/src/multicore.rs/root/.cargo/git/checkouts/bellman-7a75f3b44e91e034/416f79d/src/multicore.rs
::122122::99

thread 'main' panicked at 'must run: Any { .. }', /root/.cargo/git/checkouts/bellman-7a75f3b44e91e034/416f79d/src/multicore.rs:85:12

It's by design. So if the circuits is too simple, we don't have to use large server.


Include weave exposed addresses in ps output

Fixes #385. Sample output:
$ sudo ./weave ps
e8f979801cd7 ae:50:e8:95:f6:03 <IP_ADDRESS>/24
2e25b47b08fe 6a:95:45:20:14:56
weave 7a:c4:8b:a1:e6:ad <IP_ADDRESS>/24

The final entry uses $BRIDGE in place of the container name, for lack of anything better - thoughts @rade @bboreham ?

$BRIDGE is fine.
Docs?

Doesn't "weave" clash with what you get from weave ps weave ?

Doesn't "weave" clash with what you get from weave ps weave ?

Very much so - well spotted. Container names are restricted to these characters
https://github.com/ajhager/docker/blob/master/runtime.go#L35
though so the literal string weave:expose is neither a valid container name nor identifier, and is exactly twelve characters long so the output remains nicely formatted:
$ sudo ./weave ps
e8f979801cd7 ae:50:e8:95:f6:03 <IP_ADDRESS>/24
2e25b47b08fe 6a:95:45:20:14:56
weave:expose 7a:c4:8b:a1:e6:ad <IP_ADDRESS>/24

Ammended the commit to use weave:expose, restore filtering and update documentation.


Change image in simnet CI jobs from parity/chaostools to paritypr/simnet

test paritypr/simnet image integration

@HarryHong please merge master.

bot merge


Web actions 2.5.1

Closes WC-1370

This seems to run in Studio pro 9.10.0 as far as I can see, is there anything else specific I should take a look at?

No, that's it


Migrate release from Azure Pipelines to GitHub Actions

Migrate release from Azure pipelines to GitHub Actions release.yml
Merge bleedingrelease.sh and tagrelease.sh into one script release.sh
Remove workflow updateGeofile.yml and integrate into release.yml

Finally, act the same as azure-pipelines.yml does.

Merge this first. And welcome a better way to build and release.


Change in payout alg posted by Friedgar

https://forum.blockstack.org/t/proposal-for-new-payout-algorithm/7722

Hey I think this is a duplicate of #80 🙏


nx-maven application generator fails

Hi
The nx-maven application generator throws an error (version 0.14.1):
The "request" argument must be of type string. Received an instance of Object

Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.
If the error persists, please run "nx reset".

Steps to reproduce:

generate a new nx repo

linda@DESKTOP-BJCBISQ:~/tmp$ npx<EMAIL_ADDRESS>foo

 >  NX   Let's create a new workspace [https://nx.dev/getting-started/intro]

✔ Which stack do you want to use? · none
✔ Package-based monorepo, integrated monorepo, or standalone project? · integrated
✔ Enable distributed caching to make your CI faster · No

 >  NX   Creating your v16.10.0 workspace.

   To make sure the command works reliably in all environments, and that the preset is applied correctly,
   Nx will run "npm install" several times. Please wait.

✔ Installing dependencies with npm
✔ Successfully created the workspace: foo.

Add nx-maven dependency

linda@DESKTOP-BJCBISQ:~/tmp/foo$ npm install --save-dev @jnxplus/nx-maven

call the init generator

linda@DESKTOP-BJCBISQ:~/tmp/foo$ npx nx generate @jnxplus/nx-maven:init

>  NX  Generating @jnxplus/nx-maven:init

✔ Which version of Java would you like to use? · 17
✔ What groupId would you like to use? · com.example.foo
✔ What parentProjectName would you like to use? · root-parent-project
✔ What project version would you like to use? · 0.0.1-SNAPSHOT
✔ Where do you want Maven config and projects to be placed? ·
✔ How to handle dependency management? · spring-boot-parent-pom
CREATE .mvn/wrapper/maven-wrapper.jar
CREATE .mvn/wrapper/maven-wrapper.properties
CREATE mvnw
CREATE mvnw.cmd
CREATE pom.xml
UPDATE nx.json
UPDATE .gitignore
CREATE .prettierrc
CREATE .prettierignore
CREATE .gitattributes

Call the app generator

linda@DESKTOP-BJCBISQ:~/tmp/foo$ npx nx generate @jnxplus/nx-maven:application app1

 >  NX   The "request" argument must be of type string. Received an instance of Object

   Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.
   If the error persists, please run "nx reset".

The error when I run with verbose:
 >  NX   The "request" argument must be of type string. Received an instance of Object

   Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.
   If the error persists, please run "nx reset".

{
  stack: 'TypeError [ERR_INVALID_ARG_TYPE]: The "request" argument must be of type string. Received an instance of Object\n' +
    '    at new NodeError (node:internal/errors:399:5)\n' +
    '    at validateString (node:internal/validators:163:11)\n' +
    '    at Function.resolve (node:internal/modules/cjs/helpers:115:5)\n' +
    '    at getPluginPathAndName (/home/linda/tmp/foo/node_modules/nx/src/utils/nx-plugin.js:32:30)\n' +
    '    at loadNxPluginAsync (/home/linda/tmp/foo/node_modules/nx/src/utils/nx-plugin.js:70:32)\n' +
    '    at loadNxPlugins (/home/linda/tmp/foo/node_modules/nx/src/utils/nx-plugin.js:124:27)\n' +
    '    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +
    '    at async retrieveProjectConfigurations (/home/linda/tmp/foo/node_modules/nx/src/project-graph/utils/retrieve-workspace-files.js:56:21)\n' +
    '    at async processCollectedUpdatedAndDeletedFiles (/home/linda/tmp/foo/node_modules/nx/src/daemon/server/project-graph-incremental-recomputation.js:129:34)\n' +
    '    at async processFilesAndCreateAndSerializeProjectGraph (/home/linda/tmp/foo/node_modules/nx/src/daemon/server/project-graph-incremental-recomputation.js:165:17)',
  message: 'The "request" argument must be of type string. Received an instance of Object\n' +
    '\n' +
    'Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.\n' +
    'If the error persists, please run "nx reset".',
  code: 'ERR_INVALID_ARG_TYPE'
}

nx maven 0.14.1 only work with nx 17.
To use nx 16.10 you need to use  0.12.0 version  but you will not have mavenRootDirectory option

Thanks for the fast reply! Will try :)


config/types/etcd: support 3.4

this change adds an Etcd3_4 config so that ct can support etcd 3.4.
it could definitely do with a second set of eyes making sure I've captured the changes appropriately. here's the diff between the 2 structs: https://gist.githubusercontent.com/JTarasovic/a3e9db802b9aead6af69abf274c75c82/raw/750710a37f756a5fe9be2882c2733ef14c1d6ead/diff.txt

coreos/bugs#2612


✨Tabs with recent and featured posts

Tabs with recent and featured posts, like shown on this Hugo theme would be a great new feature to have.
The image below shows how the theme above looks like with the tabs.

Recent and featured posts on a fixed sidebar are essential for news blogs.
With this feature I could finally convert my Wordpress blog to Hugo. I think that many people that are now using Wordpress feel the same.
Thanks!

@LITUATUI two questions:

Is this something to enhance the current recent articles experiences in the main page or something that would live in ALL article pages?
How do you currently mark which articles are featured in your solution?

These tabs would be shown in every page of the website, not just the homepage.
On the HBS theme, the featured posts are marked in the front matter.

Exemple of the front matter on one article that is both pinned (first article on homepage) and featured (shows on the sidebar):
---
title: Technologies that will make electric vehicles even better
author: Pedro Lima
type: post
featured: true
pinned: true
date: 2021-06-21T05:00:16+00:00
url: /2021/06/21/technologies-that-will-make-electric-vehicles-even-better/
images: [/images/posts/Electric-charge-road-sign.jpg]
featureImage: [/images/posts/Electric-charge-road-sign.jpg]
categories:
  - Evergreen
  - General
---

A fixed sidebar with tabs that show recent and popular/featured posts is very common in Wordpress themes. When more Hugo themes get this feature, more people will make the migration away from Wordpress.

Not implementing this navigation as described here, going with a related approach described in https://github.com/nunocoracao/blowfish/issues/495


#320 Added a getReleases() Method into Repository entity

Added the method in this pr.

👍 Thanks for the contribution!


testing: add samples/system tests with Cloud Build

Also removed the samples test with Github Actions

No for now. It's a feature request for the Cloud Build team
I think yes unfortunately


Add a with-count query parameter that works with the Eloquent implementation

This has long been requested for Laravel JSON:API. Part of doing the revamp was to make things like this easier to implement. Background here: https://github.com/cloudcreativity/laravel-json-api/issues/166
The idea is basically to give the client control over what relationships have a count field added to their meta.
https://laravel.com/docs/8.x/eloquent-relationships#counting-related-models
Something like:
GET /api/v1/posts?with-count=comments
Would return the posts resources with a count added to the meta of the comments relationship.
For relationship endpoints, we'd need to distinquish between counting the relation that is being retrieved, and adding a count to the models within the relation. E.g:
GET /api/v1/posts/1/comments?with-count=likes
In this request, the likes refers to a relationship on the comments resource. But we may want to include the count of how many comments the post has - so we need another parameter for indicating that for relationship endpoints. E.g. ?count-related.

Note that the JSON:API spec recommends using at least one non a-z character in the query parameter name, to avoid potential collisions with future additions by the spec. So with-count, with_count and withCount would all be ok. (To follow our convention, with-count should be the default but should be configurable.)

Once we've implemented for count, it presumably will be easy to implement the other aggregate functions.

Documentation:
https://github.com/laravel-json-api/docs/blob/develop/1.0/digging-deeper/countable.md


Firebase config overwrites unrelated keys

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Output production on hosting key options
If the current behavior is a bug, please provide the steps to reproduce.
With an existing firebase.json file:
npm run serve -- --server config --dest .

What is the expected behavior?
The file is merged only overriding the hosting key. A deep merge of the hosting key might be even better, but I don't know that it's really needed.
Merged firebase.json:
{
  "database": {
    "rules": "database.rules.json"
  },
  "hosting": {
    "public": "build",
    "rewrites": [
      {
        "source": "**",
        "destination": "/index.html"
      }
    ],
    "headers": [
      {
        "source": "**",
        "headers": [
          {
            "key": "Cache-Control",
            "value": "public, max-age=3600, no-cache"
          },
          {
            "key": "Access-Control-Allow-Origin",
            "value": "*"
          },
          {
            "key": "Access-Control-Max-Age",
            "value": "600"
          }
        ]
      },
      {
        "source": "/sw.js",
        "headers": [
          {
            "key": "Cache-Control",
            "value": "private, no-cache"
          }
        ]
      },
      {
        "source": "**/*.chunk.*.js",
        "headers": [
          {
            "key": "Cache-Control",
            "value": "public, max-age=31536000"
          }
        ]
      },
      {
        "source": "/",
        "headers": [
          {
            "key": "Link",
            "value":
              "</bundle.6acb8.js>; rel=preload; as=script, </style.ba975.css>; rel=preload; as=style, </route-home.chunk.8111b.js>; rel=preload;as=script"
          }
        ]
      }
    ]
  }
}

If this is a feature request, what is motivation or use case for changing the behavior?
When using CI/CD pipelines like Gitlab pipelines this config is going to change when the pipeline runs and should therefore be an automatable. In my case I also have a top level database key that I don't want overridden.
Please mention other relevant information.

node version
8.4.0
npm version
5.3.0
Operating system
mac sierra 10.12.6

So you're saying that we're overwriting the entire firebase.json file with our own contents, thus deleting whatever was there previously?

@lukeed that's correct. Notice in my expected config file I have a top level database key which is used for defining database rules. In my case I'm just pointing to another file so I can separate that out, but the inline content would look something like:
{
  "rules": {
    "users": {
      "$uid": {
        ".read": "auth != null && auth.uid == $uid",
        ".write": "auth != null && auth.uid == $uid"
      }
    }
  }
}

When I run npm run serve -- --server config --dest . to generate the config it writes the following to firebase.json.
{
   "public":"build",
   "rewrites":[
      {
         "source":"**",
         "destination":"/index.html"
      }
   ],
   "headers":[
      {
         "source":"**",
         "headers":[
            {
               "key":"Cache-Control",
               "value":"public, max-age=3600, no-cache"
            },
            {
               "key":"Access-Control-Allow-Origin",
               "value":"*"
            },
            {
               "key":"Access-Control-Max-Age",
               "value":"600"
            }
         ]
      },
      {
         "source":"/sw.js",
         "headers":[
            {
               "key":"Cache-Control",
               "value":"private, no-cache"
            }
         ]
      },
      {
         "source":"**/*.chunk.*.js",
         "headers":[
            {
               "key":"Cache-Control",
               "value":"public, max-age=31536000"
            }
         ]
      },
      {
         "source":"/",
         "headers":[
            {
               "key":"Link",
               "value":"</bundle.6acb8.js>; rel=preload; as=script, </style.ba975.css>; rel=preload; as=style, </route-home.chunk.8111b.js>; rel=preload;as=script"
            }
         ]
      }
   ]
}

Without looking at the code it could probably be fixed by reading the JSON contents if it exists and then writing out using a merge on the "hosting" key.
e.g.
pseudocode
firebaseConfig = readJSON('firebase.json`) || {}
writeJSON(
  JSON.stringify(
    Object.assign({}, firebaseConfig, {'hosting': preactFirebaseConfig})
  )
)

Got it, thanks! Was just double-checking.

I'll take a look into this in a couple hours after work


[21pt] Improve Performance for Post-Processing tools

The overall performance of the post processing steps is pretty slow, even though it has some multi proc in some parts. That section has slowly growing and the cumulate of them is now a bit of a problem. Consider analysizing each tool used in post processing to review performance. I suspect adding multi-threading in parts could have major performance gains. Research required.

One thing that might be good to add here is a check to see if fim_process_unit_wb.sh completes successfully or not before running fim_post_processing.sh on a HUC. I think the way it is now, fim_post_processing.sh is run even if fim_process_unit_wb.sh has failed for that HUC.

Yes... that is true. It does assume that at least one HUC passed. We do try to isolate each fim_process_unit_wb to pass/fail at will so they can be run in any form of a parallelized system (bash parallel or AWS).  There is no easy way for a parallized fim_process_unit_wb to tell bash that it passed or failed. While not pretty.. that is why we have bash code that scans log directories looking for HUC errors and puts them in the unit_errors.log file (or similar name)


CANT TYPE IN MY TERMINAL

ADD ISSUE DESCRIPTION HERE
I AM NEW TO USING VSCODE BUT I CANT SEEM TO TYPE IN MY TERMINAL. I HAVE TRIED RESETTING THE TERMINAL, COSING IT AND OPENING A NEW ONE, UPDATING VSCODE, AND NOTHING SEEMS TO DO THE TRICK. I DID JUST GET A MAC LAPTOP AND THAT SEEMS TO BE THE ONLY THING THAT IS DIFFERENT. HOWEVER, I CAN STILL LOG IN ON MY CHROMEBOOK AND IT WORKS JUST FINE
Version: 1.73.1
Commit:<PHONE_NUMBER>f055b99068d3688932416f2346dd3b
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6.1 Safari/605.1.15
Embedder: codespaces

disable terminal.integrated.gpuAccleration as it's not supported on certain versions of safari
/duplicate #165416

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Add examples

TSP examples
input data
opt process visualization

need some crate to do visualization, I don't know which to use


Output differences with the native hls downloader

To download for example twitch.tv vods via hls youtube-dl can use ffmpeg or the built in hls downloader.
I noticed that there are slight differences in the created files with the two options.
As a test I used this twitch vod: http://www.twitch.tv/lobosjr/v/3796842 which is reported as 1:13 long via the twitch player.
When downloading it with ffmpeg the file is 32.938.745 bytes big.
With the native hls downloader the file is 33.744.684 byte big. This is also exactly the same file I get when downloading the vod with a different tool for the same job (livestreamer).
When playing the files via vlc they feel different. Skipping to different times seems faster with the native version but produces a "key frame missing" effect for a short time, this does not happen with the ffmpeg version but skipping is a bit slower.
Using ffprobe on both files shows more differences like the files having a slightly different length (this is also noticeable in vlc but it says 1:13 and 1:12):
ffprobe ffmpeg.mp4:
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'ffmpeg.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf56.1.100
  Duration: 00:01:13.22, start: 0.000000, bitrate: 3599 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709/bt709/iec61966-2-1), 1280x720, 3521 kb/s, 60 fps, 60 tbr, 90k tbn, 120 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 114 kb/s (default)
    Metadata:
      handler_name    : SoundHandler

ffprobe native.mp4:
Input #0, mpegts, from 'native.mp4':
  Duration: 00:01:13.27, start: 62.901000, bitrate: 3684 kb/s
  Program 1
    Stream #0:0[0x100]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 134 kb/s
    Stream #0:1[0x101]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709/bt709/iec61966-2-1), 1280x720, 60 fps, 60 tbr, 90k tbn, 120 tbc
    Stream #0:2[0x102]: Data: timed_id3 (ID3  / 0x20334449)
Unsupported codec with id<PHONE_NUMBER> for input stream 2

When trying this with a longer vod (~37 minutes) the reported difference in length is still as minimal as here but the native version is 601mb whereas the ffmpeg version is only 586mb which is not a minimal difference.
Without looking at the ffmpeg source I'm guessing this is caused by the aac_adtstoasc bitstream filter that ffmpeg gets invoked with in downloader/hls.py but I dont know why this is needed or what exactly it does.
Im guessing the native version resembles the original more closely but the ffmpeg version seems to be a more proper file (as it does not contain an unsupported codec). I wonder which one is preferred and should the native downloader implement the bitstream filter too or should ffmpeg be invoked without it (or neither)?

Not sure if this is relevant at all but at least interesting, when you open the native version with an hexeditor or invoke strings on it you can see some twitch related text in it:
2015-02-16T17:11:22
2015-02-16T17:11:26
index-0000000000-K1Fq.ts
libavtwitch: e73cdbc45cfb6e9cc05c7d1G

Yes they are different and the causes are listed in your first post. Do you expect both methods generate identical files? It's not a goal of the native downloader.

I must have missed yan's comment. I just got a notification because the issue was closed.
In the original issue I was voicing confusion and I was not sure if this was a bug or not. I believe my speculation at the end of the original comment is correct and as yan says it is not expected to get the same file output. The actual audio and video should still be exactly the same which is what I was worried about.
It is fine to close this issue. This reply is for future reference.


pip-compile with --index-url option delivers packages that are not on package index

Environment Versions

OS Type: Windows 10 and Linux
Python version: 3.7 and 3.8
pip version: 21.3.1
pip-tools version: 6.4.0

Steps to replicate

pip-compile --index-url<EMAIL_ADDRESS>creates a requirements.txt with pinned versions

Expected result
All pinned versions in requirements.txt should be available on package index. Otherwise an error is returned.
Actual result
The requirements.txt contains package versions that are not on the private package index.
I thought that pip-compile uses only packages on the index because this allows to use pip-tools in combination with a private index.
Can anyone help and clarify the behaviour?

I have also asked this on SO: https://stackoverflow.com/questions/70438495/pip-compile-with-index-url-option-delivers-pinned-package-versions-that-are-no

@ckaldemeyer I'm going to close this. Looks like you got the answer on SO! Feel free to re-open if not.
GitLab pypi registry proxies requests to upstream pypi when package doesn't exist in GitLab registry. Perhaps this is the issue?  – Satya Mishra Dec 31 '21 at 12:20

You are right. This seems to be the issue!  – Cord Kaldemeyer Jan 5 at 15:07

Ye, thanks!


-2016281112 (Remediation failed)

It's still this same issue.
I have Windows 10 Pro 1809 joined to Azure AD with deployed policy to create Local account.
It's working fine - account is created successful, but... On Intune I have still this same error:
-2016281112 (Remediation failed)
Is there any fix for that? I can provide logs for Engineers ;)

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

ID: 309bae29-c769-5051-6c3f-aebeb455cd34
Version Independent ID: bbdfad82-025e-8aee-b3fc-bcfb8b110674
Content: Accounts CSP
Content Source: windows/client-management/mdm/accounts-csp.md
Product: w10
GitHub Login: @MariciaAlforque
Microsoft Alias: maricia

@dzejzipl - thank you for submitting feedback.
I think the best way forward is if you can open a service ticket so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for Windows 10 products:
https://support.microsoft.com/en-us/hub/4338813/windows-help?os=windows-10
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

@AndreaBarr - This issue can be closed. Thank you.


Improve __sdk_env

Don't restrict candidate names to lowercase letters (only require that candidate name doesn't contain =).
Fail immediately when there's an invalid candidate & version pair, since invalid line format also fails immediately
Parse candidate until first =, not until last =, but still parse version from first = (fixes problem when more than one = on a line).
Make line a local variable
Move normalised_line declaration outside of while to avoid message on iterations after the first
Improve error message
Remove unnecessary slash from ends of search & replaces in __sdkman_normalise

To raise a new Pull Request, the following prerequisites need to be met. Please tick before proceeding:

[X] a conversation was held in the appropriate SDKMAN Slack channel.
[ ] a Github Issue was opened for this feature / bug.
[ ] test coverage was added (Cucumber or Spock as appropriate).

Some nice improvements, thanks!

Looks good, would be good to have some tests to assert some of these improvements though.

Most of these are refactorings and already covered by tests. Though it wouldn't hurt to add 1 or 2 additional cases for the changes to the validation and splitting logic.

Not to be contrarian, but every test slows down every build, and adds to the scenarios that a dev might have to read.
If the minor bugs hadn't been there, but were instead avoided as per the code in this PR, you wouldn't have requested tests for that functionality (if you would have requested tests for that functionality, you would have requested the tests for the existing env code, and the minor bugs would have been found and prevented by those tests).
It seems overkill to test all these minor edge cases, like more than one = in a line, not restricting candidates to lowercase letters, not outputting extraneous confusing messages, etc.
For the last one, the code could output other messages besides the one we've seen so far, so the best way to ensure that there is no extra output is to change every test from checking if the output contains a string to checking if the output equals a string.  But that should probably be a change to all tests, not just the ones for env.

I modified an existing test to additionally cover more than one = on a line, and non-lowercase characters in candidate names.  I'll push it in a minute or so.

Pushed the modifications to env tests.  Covers the changes to .sdkmanrc line parsing.  Doesn't cover not outputting extra messages, because code could output any extra messages, not just the currently observed one.  Also, I think that might only occur on zsh, which isn't tested by the tests.

Right, now that you have demonstrated your intention through a test, I (and everyone else) understand what it is that you are trying to achive.
Here are some observations:

candidates are always expressed in lower case, with no caps or special characters allowed. this is not enforced anywhere, but is a convention throughout SDKMAN.
we should only accept simple key value pairs, separated by a singe =. Multiple = on a line should simply not be allowed.

In the end, the simplest approach trumps all. Why accommodate such odd edge cases when they should never occur in the real world? When/if these things become a problem, we will address them at that point.

I accommodated edge cases because doing so didn't add any complexity, and it designs for extensibility.
e.g., if there's an sdk called plan9 that someone wants on sdkman, the existing sdk env will fail on that candidate name.  Would you force someone to name the candidate plannine?  That doesn't make sense to me.
If, for some reason, there's a version that includes an =, then the existing code will fail on it.
It's one thing thing if I complicated logic to support this, but my change adds no complexity at all, and it reduces complexity of the system by removing artificial constraints, and, more importantly, removes constraints from places where they shouldn't be enforced.  If you want to enforce that all candidate names follow a certain pattern, __sdkman_env is not the place to do it.

Maybe we can rollback point 1 and 3 and keep the other fixes (candidate name and candidate parsing)? If these really become a problem we can revisit them. Just so we can get the feature out 🙂.

I've made the single change we needed (logging issue in ZSH) myself for now so as to unblock the release of your functionality @helpermethod.


⚠ Bofrost.at has degraded performance

In 3fb297c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2278 ms

Resolved: Bofrost.at performance has improved in d51dd52 after 6 minutes.


Fix doc comment.

It seems that the closing backticks need to be aligned with the opening ones, otherwise they are displayed verbatim in the documentation. Also, http://doc.rust-lang.org/book/documentation.html#code-block-annotations says that "text" should be used for plain text.

Awesome. Thank you!


Lots of "Not helpful" reports have no attached program

I don't know how this is happening, but I think it's even happened to me.

Eureka!  It seems that clicking on the line number for an error message clears the URL!


View Nested Iterations Work Item List [6]

Description
As a user, I want to see work items in nested iteration according to the hierarchy position of the iteration.
Functional Acceptance Criteria

The user can select an Iteration from the Iteration view.
The user can also select a sub-Iteration from the Iteration view.
When an iteration is selected, the Work Item List View displays the work items of the selected Iteration and all Iterations nested in the selected Iteration.

Non-functional Acceptance Criteria
None.
Dependent Stories

Userstory #1170
Userstory #1171

Tasks

@baijum UX contact is SJ (@essjaysee)

@essjaysee This story doesn't require any new wireframes, right?
Otherwise, please let me know if there is any UX tasks related to this story exists.
My understanding is the existing work item list gets updated based on the selected iteration.

Hi Baiju....
UX will need to run through the workflows to determine this. SJ is UX on
this and I will defer to her here.
There is work to do on how to display the iterations in the left pane,
create the nesting and establish any rules and behaviors around these
actions.
We will be looking at getting this work into our next sprint. Our current
sprint ends tomorrow.
-Monica
On Wed, Mar 15, 2017 at 5:56 AM, Baiju Muthukadan<EMAIL_ADDRESS>wrote:

@essjaysee https://github.com/essjaysee This story doesn't require any
new wireframes, right?
Otherwise, please let me know if there is any UX tasks related to this
story exists.
My understanding is the existing work item list gets updated based on the
selected iteration.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-planner/issues/1171#issuecomment-286694075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwqz2e8G_l_QS030zyKOKkGIYlNX1jks5rl7XagaJpZM4McXZL
.


[patch] Update readthedocs config

Bumping some versions, adding the versioneer[toml] install and build isolation, and removing other install directions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 88.923%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3171

Relevant Lines:
3566

💛  - Coveralls

Closes #350


Look into setting up a notification program for cluster status (drain etc)

I do too. Question is how long would it take to set up?


footer

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I want to add description about website in footer section please assign @ANSHIKA-26
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

not really needed , also #1259 is working on footer UI


Fixing issue with tabbing when a radio is the last element of the modal

The issue here was that the code was checking if the activeElement was the last element, but for radio groups, you can tab out without it being the last element. This checks if the tail and activeElement are part of the same radio group and if so treats it as if it were the last element
Acceptance Checklist:

[X] Tests
[ ] Documentation and examples (if needed)

Fixes #636 .

Moved that to a function and updated the basic form example to have the radios at the end to be able to see the functionality

@loganscharen @doeg Is there any accessibility tool or documentation where we chan check this behavior?

Do you mean checking whether the new behaviour is compliant with W3 standards?

Yep, please.

Is this what you mean?
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/#keyboardinteraction

@loganscharen Yas, but for the case of radio groups. If we are going to intervening on default browser behavior, we need to do it right.

https://www.w3.org/WAI/ARIA/apg/patterns/radio/#keyboardinteraction
So this? That tab is used to go into and out of the radio group and not between the elements of the group. So the radio group is the last tabbable element, not each radio button separately.

@diasbruno anything else needed to get this merged?

@loganscharen Thanks. That's what I was looking for.
There are some rules on that specification. Should we add tests to check if the behavior is correct (arrows, space)?
Also, long time ago there was this issue https://github.com/reactjs/react-modal/blob/master/src/helpers/scopeTab.js#L48, but I think I've implemented not respecting the radio specification. Should this cause this bug?

I don't see why we would need to test that space and arrow are working correctly, we're not touching that functionality at all.
The safari bug doesn't have any impact on this, this is just occurring because we're currently looking at the last element, but from a radio group, the last element isn't always the last tabbable element.

Ok. I'll have a look on it later.

@diasbruno Forgot about this, but any chance you could take a look at it again?

@loganscharen @diasbruno This issue still exists. Any reasons why y'all have held off on merging this PR?


Implement simplified tag naming syntax for connections

Adds tag support for particle arguments.
Allows for 'name' to be optional if tags are specified

Addresses #1149

Looks good to me, Doug and Shane have done more here but if there are changes requested we can do separately. Shane may not be able to look at this this week and I'm not sure about Doug's availability so it's ok to merge IMO if we haven't heard anything in a day or so.
Am sure you are aware but to state for other readers, the referenced issue also notes we should do this for verbs and slots. This PR focuses on just particle argument names as a first (useful!) step.


What should I do with this import error?

ImportError: libGL.so.1: cannot open shared object file: No such file or directory
thank you!

Hello,
Please consider following this guideline: https://stackoverflow.com/questions/55313610/importerror-libgl-so-1-cannot-open-shared-object-file-no-such-file-or-directo
Otherwise, if the error is in easyFermi or Fermipy, please send me a copy of the fermipy.log file and a print of the easyFermi window

Thank you! I have work it out by the link address you give. But soon I meet another problem, it's:
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
I have solved it by installing VcXsrv(by the way, I use WSL), it took me a long time, so I report it to you in case that someone encounters the same problem.

Hmm, I see. Could you please try to reinstall easyFermi following the tutorial here? We updated the installation steps yesterday.
Furthermore, are you using a Linux or Mac OS?

I am sorry I did not express it clearly. I indeed follow the new installation steps and I could run easyfermi already. The problem above is still existence after reinstalling by the new steps, and the way of resolution is mentioned above. I mean that my experience may be helpful.
I am using WSL, it's the Windows subsystem for Linux.

Ok, we updated the installation tutorial of easyFermi. You can check the requirements for WSL. In summary, you need to install libgl1 in your WSL with the following command:
sudo apt-get install libgl1


Are SEAHUB_PORTand FILESERVER_PORT working ?

FILESERVER_PORT probably yes since it's written in a config file.
SEAHUB_PORT probably not since seahub.sh isn't started with any specific port.
Need to do some testing.

Ok this is just a cosmetic stuff unless fastcgi is used which will probably never be the case. So I don't care.


bitrate is getting doubled while recording on firefox

Description
in videojs-record code base I can see that video bitrate has been set to 1200 but while using the example on firefox recorded file is having bitrate more than 2000
I checked for multiple bitrates as well for 100 it gave me 200 kbps video bitrate on firefox
Steps to reproduce
got to the URL - https://collab-project.github.io/videojs-record/demo/audio-video.html
record the video on both chrome and firefox and save it
extract the video using FFmpeg command -
ffmpeg -y -i input.webm -an -vcodec copy out.webm
get more details about the out.webm using ffprobe out.webm
Results
chrome - bitrate will be around 1200 kbps
firefox - bitrate will be double so approx it'll be around 2000 kbps
Expected
Please describe what you expected to see.
on firefox bitrate of the recorded file should be around 1200
Actual
bitrate of the video on firefox is getting doubled.
Additional Information
Firefox is generating large files compared to chrome

This is related to the recordrtc implementation of bitrate I think.

@AnshD12 could you try out this recordrtc demo: https://github.com/muaz-khan/RecordRTC/blob/master/simple-demos/bitsPerSecond.html (online demo: https://www.webrtc-experiment.com/RecordRTC/simple-demos/bitsPerSecond.html)
And try if the videoBitsPerSecond option has any effect on either browser.

@thijstriemstra Where in the videojs-record config does MediaRecorder's videoBitsPerSecond get passed in?

Does not seem to be possible to configure videoBitsPerSecond it seems, would be great to have as Safari has a higher default compared to Chrome which is not great for performance.


php composer installation failed

PC> composer require razorpay/ifsc
Using version ^1.0 for razorpay/ifsc
./composer.json has been updated
Loading composer repositories with package information                                                    Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- razorpay/ifsc 1.0.9 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.8 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.7 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.6 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.5 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.4 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.3 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.2 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.11 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.10 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.1 requires php-http/client-implementation ^1.0 -> no matching package found.
- razorpay/ifsc 1.0.0 requires php-http/client-implementation ^1.0 -> no matching package found.
- Installation request for razorpay/ifsc ^1.0 -> satisfiable by razorpay/ifsc[1.0.0, 1.0.1, 1.0.10, 1.0.11, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8,
1.0.9].
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.
Installation failed, reverting ./composer.json to its original content.
and my stability setting is as follows:
"minimum-stability" : "stable"

I am installing this with laravel 5.3 application. Can you please correct me where I am wrong?

You need to install one of the packages from this list as well: https://packagist.org/providers/php-http/client-implementation


[6128] - remove application_choice_id from analytics

Context
application_choice_id seems redundant for data insights team.
see: https://trello.com/c/23GqB007/6041-applicationchoiceid-all-showing-as-rugged-abacus-218110dataformapplyapplicationslatestregister and https://trello.com/c/WEIHSeYB/6128-applicationchoiceid-all-showing-as-rugged-abacus-218110dataformapplyapplicationslatestregister

 application_choice_id all showing as rugged-abacus-218110.dataform.apply_applications_latest_register


Fix background_jobs segment

This commit replaces the precmd hook with a call to jobs -l.
It is not ideal, but gets the job done.
Performance: This is not nearly as fast as using %j, but that yields the total count of background jobs only. And this is probably slower than the former precmd solution.
So, this is a possible Plan B, if we don't find a better solution.
Fixes #1196

Closed in favor of #1254


Updating docs to show support for Python 3.6 in Windows. (#12687)

Cherrypicking into r1.3 for docs gen.

Jenkins, test this please.

Jenkins, test this please.


Errors while initial make sync command and build

After make sync received such output

bedtime_stories git:(main) ✗ make sync
flutter pub get
Resolving dependencies...
  _fe_analyzer_shared 61.0.0 (65.0.0 available)
  analyzer 5.13.0 (6.3.0 available)
  archive 3.4.6 (3.4.9 available)
  auto_route 7.8.3 (7.8.4 available)
  auto_route_generator 7.3.1 (7.3.2 available)
  avatar_glow 2.0.2 (3.0.1 available)
  build_daemon 4.0.0 (4.0.1 available)
  build_resolvers 2.4.1 (2.4.2 available)
  build_runner 2.4.6 (2.4.7 available)
  built_value 8.6.3 (8.8.1 available)
  cli_util 0.4.0 (0.4.1 available)
  code_builder 4.7.0 (4.9.0 available)
> collection 1.18.0 (was 1.17.2)
  cross_file 0.3.3+6 (0.3.3+8 available)
  dart_openai 4.0.0 (5.0.0 available)
  dart_style 2.3.2 (2.3.4 available)
  dio 5.3.3 (5.4.0 available)
  envied 0.3.0+3 (0.5.2 available)
  envied_generator 0.3.0+3 (0.5.2 available)
  fetch_api 1.0.2 (1.0.3 available)
  file 6.1.4 (7.0.0 available)
  flutter_hooks 0.20.1 (0.20.3 available)
  flutter_lints 2.0.3 (3.0.1 available)
  flutter_native_splash 2.3.3 (2.3.8 available)
  flutter_riverpod 2.4.1 (2.4.9 available)
  flutter_tts 3.8.3 (3.8.5 available)
  freezed 2.4.5 (2.4.6 available)
  hooks_riverpod 2.4.1 (2.4.9 available)
  http 1.1.0 (1.1.2 available)
  intl 0.18.1 (0.19.0 available)
  lints 2.1.1 (3.0.0 available)
  lottie 2.6.0 (2.7.0 available)
  matcher 0.12.16 (0.12.16+1 available)
  material_color_utilities 0.5.0 (0.8.0 available)
> meta 1.10.0 (was 1.9.1) (1.11.0 available)
  path 1.8.3 (1.9.0 available)
  path_provider_android 2.2.0 (2.2.1 available)
  petitparser 5.4.0 (6.0.2 available)
  platform 3.1.2 (3.1.3 available)
  plugin_platform_interface 2.1.6 (2.1.7 available)
  provider 6.0.5 (6.1.1 available)
  retrofit 4.0.2 (4.0.3 available)
  retrofit_generator 8.0.0 (8.0.6 available)
  riverpod 2.4.1 (2.4.9 available)
  share_plus 4.5.3 (7.2.1 available)
  share_plus_platform_interface 3.1.2 (3.3.1 available)
  share_plus_windows 3.0.1 (4.0.0 available)
  shared_preferences_linux 2.3.1 (2.3.2 available)
  shared_preferences_web 2.2.1 (2.2.2 available)
  shared_preferences_windows 2.3.1 (2.3.2 available)
  source_gen 1.4.0 (1.5.0 available)
> stack_trace 1.11.1 (was 1.11.0)
> stream_channel 2.1.2 (was 2.1.1)
> test_api 0.6.1 (was 0.6.0) (0.7.0 available)
  url_launcher 6.1.14 (6.2.2 available)
  url_launcher_android 6.1.0 (6.2.0 available)
  url_launcher_ios 6.1.5 (6.2.1 available)
  url_launcher_linux 3.0.6 (3.1.1 available)
  url_launcher_macos 3.0.7 (3.1.0 available)
  url_launcher_platform_interface 2.1.5 (2.2.0 available)
  url_launcher_web 2.0.20 (2.2.2 available)
  url_launcher_windows 3.0.8 (3.1.1 available)
> web 0.3.0 (was 0.1.4-beta) (0.4.0 available)
  web_socket_channel 2.4.0 (2.4.1 available)
  win32 5.0.9 (5.1.1 available)
  xml 6.3.0 (6.5.0 available)
Changed 6 dependencies!
63 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.
dart run build_runner build  --delete-conflicting-outputs
Building package executable... (2.5s)
Built build_runner:build_runner.
[INFO] Generating build script completed, took 165ms
[INFO] Precompiling build script... completed, took 2.9s
[INFO] Building new asset graph completed, took 869ms
[INFO] Checking for unexpected pre-existing outputs. completed, took 0ms
[INFO] Generating SDK summary completed, took 2.1s
[WARNING] retrofit_generator on test/widget_test.dart:
Your current `analyzer` version may not fully support your current SDK version.

Analyzer language version: 3.1.0
SDK language version: 3.2.0

Please update to the latest `analyzer` version (6.3.0) by running
`flutter packages upgrade`.

If you are not getting the latest version by running the above command, you
can try adding a constraint like the following to your pubspec to start
diagnosing why you can't get the latest version:

dev_dependencies:
  analyzer: ^6.3.0

[WARNING] retrofit_generator on lib/core/src/network/rest_non_auth_client.dart:
ChatRequestModel must provide a `toJson()` method which return a Map.
It is programmer's responsibility to make sure the ChatRequestModel is properly serialized
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/jailbreak/jailbreak_page.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/jailbreak/jailbreak_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/core.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/jailbreak/jailbreak_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/usecases/usecases.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/common/common.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/hive.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/constants/constants.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/observer/observer.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/stream/stream.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/errors.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/theme/theme.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/utils/utils.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/navigation/navigation.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/jailbreak/jailbreak_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/usecases/usecase_stream.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/usecases/usecase_future.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/common/common_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/preference/preference.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/base/base.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/common/common_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/common/common_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/dimen/dimen.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/secure_database_manager.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/hive_operation.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/primitive_database.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/config/config.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/hive_encryption.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/network.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/define_story/define_story_page.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/start/start_page.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/story_detail/story_detail_page.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/history/history_page.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/constants/ui_constants.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/observer/app_navigator_observer.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/observer/app_provider_observer.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/stream/dispose_bag.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/app_exception_wrapper.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/app_error_listener_mixin.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/app_handle_exception.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/app_error_mapper.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/errors/app_error_listener.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/theme/text_theme.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/theme/text_styles.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/theme/app_theme.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/utils/log_utils.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/hive/hive_database_manager.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/navigation/app_routes.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/preference/app_preferences.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/base/wrap_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/base/base_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/base/base_vm_mixin.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/navigation/app_navigator.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/base/base_page_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/dimen/app_dimen.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/utils/date_utils.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/config/app_config.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/rest_non_auth_client.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/base/base.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/middleware.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/define_story/define_story_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/define_story/define_story_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/define_story/define_story_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/start/start_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/start/start_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/presentation.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/domain.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/data.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/base/dio_builder.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/access_token_interceptor.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/refresh_token_interceptor.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/custom_log_interceptor.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/refresh_token_api_service.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/core/src/network/middleware/header_interceptor.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/di/di.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/app.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/start/start.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/define_story/define_story.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/history/history.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/jailbreak/jailbreak.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/story_detail/story_detail.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/usecases.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/repositories/repositories.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/repositories/repositories.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/models/models.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/data_sources/data_sources.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/mapper/mapper.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/di/di.config.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/resources/resources.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/resources/src/generated/l10n.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/start/start_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/history/history_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/history/history_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/history/history_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/story_detail/story_detail_state.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/story_detail/story_detail_event.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/presentation/src/story_detail/story_detail_vm.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/get_story_by_id_usecase.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/get_stories_stream_usecase.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/completion_usecase.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/save_story_local_story_usecase.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/usecases/init_database_story_usecase.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/domain/src/repositories/openai_repository.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/repositories/openai_repository_impl.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/models/story_hive_model.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/data_sources/remote_data_source.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/data_sources/story_hive_operation.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/data_sources/local_data_source.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/mapper/story_mapper.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[WARNING] build_resolvers:transitive_digests on lib/data/src/mapper/chat_completion_mapper.dart:
Unable to read asset, could not compute transitive deps: bedtime_stories|lib/core/src/navigation/app_routes.gr.dart

This may cause less efficient builds, see the following doc for help:
https://github.com/dart-lang/build/blob/master/docs/faq.md#unable-to-read-asset-could-not-compute-transitive-deps
[INFO] Running build completed, took 12.6s
[INFO] Caching finalized dependency graph completed, took 103ms
[INFO] Succeeded after 12.7s with 196 outputs (2095 actions)

After flutter run

 bedtime_stories git:(main) ✗ flutter run
Launching lib/main.dart on iPhone 14 in debug mode...
Running pod install...                                             613ms
Running Xcode build...
Xcode build done.                                           13,9s
Failed to build iOS app
Error (Xcode): lib/resources/resources.dart:4:1: Error: Error when reading 'lib/resources/src/generated/l10n.dart': No such file or directory

Could not build the application for the simulator.
Error launching application on iPhone 14.

Alongside, I have the next list of errors in code:

Ok i will check it

Thank for your issue

@daachet  I fixed in new PR. You can git pull and run:
make sync


Environment names with spaces no longer work

Describe the Issue
npm upgraded directly from v4.4.0 to 9.4.0. It mostly went smoothly, but our database migration workflows stopped working. Our environment names include up and down to support reverting migrations.
Action Configuration
    steps:
      - name: branch-deploy
        id: branch-deploy
        uses: github/branch-deploy@91f77d0f24b03ff5f3d0fd24ce45498d1690d16b # pin 9.4.0
        with:
          environment: up sandbox
          environment_targets: up sandbox,down sandbox,up staging,down staging,up production,down production
          stable_branch: ${{ inputs.main_branch }}
          trigger: ".migrate"
          # We don't want the migration locks to interfere with the main chatops workflow
          lock_trigger: .an-lock-random-obscure-string-that-shouldnt-be-typed-ever
          unlock_trigger: .an-unlock-random-obscure-string-that-shouldnt-be-typed-ever
          skip_reviews: 'up sandbox,down sandbox'
          update_branch: warn

Relevant Actions Log Output
2024-08-22T19:44:55.6510210Z ##[group]Run github/branch-deploy@91f77d0f24b03ff5f3d0fd24ce45498d1690d16b
2024-08-22T19:44:55.6511127Z with:
2024-08-22T19:44:55.6511561Z   environment: up sandbox
2024-08-22T19:44:55.6512588Z   environment_targets: up sandbox,down sandbox,up staging,down staging,up production,down production
2024-08-22T19:44:55.6513632Z   stable_branch: master
2024-08-22T19:44:55.6514139Z   trigger: .migrate
2024-08-22T19:44:55.6514882Z   lock_trigger: .an-lock-random-obscure-string-that-shouldnt-be-typed-ever
2024-08-22T19:44:55.6516123Z   unlock_trigger: .an-unlock-random-obscure-string-that-shouldnt-be-typed-ever
2024-08-22T19:44:55.6517272Z   skip_reviews: up sandbox,down sandbox
2024-08-22T19:44:55.6518004Z   update_branch: warn
2024-08-22T19:44:55.6518711Z   github_token: ***
2024-08-22T19:44:55.6519184Z   status: success
2024-08-22T19:44:55.6519595Z   environment_url_in_comment: true
2024-08-22T19:44:55.6520209Z   production_environments: production
2024-08-22T19:44:55.6520898Z   reaction: eyes
2024-08-22T19:44:55.6521327Z   noop_trigger: .noop
2024-08-22T19:44:55.6521769Z   help_trigger: .help
2024-08-22T19:44:55.6522247Z   lock_info_alias: .wcid
2024-08-22T19:44:55.6522747Z   permissions: write,maintain,admin
2024-08-22T19:44:55.6523329Z   param_separator: |
2024-08-22T19:44:55.6523914Z   global_lock_flag: --global
2024-08-22T19:44:55.6524415Z   outdated_mode: strict
2024-08-22T19:44:55.6525146Z   required_contexts: false
2024-08-22T19:44:55.6525632Z   checks: all
2024-08-22T19:44:55.6526016Z   allow_forks: true
2024-08-22T19:44:55.6526449Z   admins: false
2024-08-22T19:44:55.6526822Z   admins_pat: false
2024-08-22T19:44:55.6527240Z   merge_deploy_mode: false
2024-08-22T19:44:55.6527750Z   unlock_on_merge_mode: false
2024-08-22T19:44:55.6528241Z   skip_completing: false
2024-08-22T19:44:55.6528824Z   deploy_message_path: .github/deployment_message.md
2024-08-22T19:44:55.6529453Z   sticky_locks: false
2024-08-22T19:44:55.6529890Z   sticky_locks_for_noop: false
2024-08-22T19:44:55.6530427Z   allow_sha_deployments: false
2024-08-22T19:44:55.6530965Z   disable_naked_commands: false
2024-08-22T19:44:55.6531545Z   skip_successful_noop_labels_if_approved: false
2024-08-22T19:44:55.6532244Z   skip_successful_deploy_labels_if_approved: false
2024-08-22T19:44:55.6532892Z ##[endgroup]
2024-08-22T19:44:55.9986797Z ✅ comment body starts with trigger: .migrate
2024-08-22T19:44:56.3924857Z 🌍 environment: up sandbox
2024-08-22T19:44:57.9089891Z ✅ CI checks passed and required reviewers have been disabled for this environment
2024-08-22T19:44:57.9102769Z 🍯 sticky_locks: false
2024-08-22T19:44:57.9107906Z 🍯 sticky_locks_for_noop: false
2024-08-22T19:44:58.6947265Z ##[error]HttpError: refs/heads/up sandbox-branch-deploy-lock is not a valid ref name. - https://docs.github.com/rest/git/refs#create-a-reference
    at /home/runner/work/_actions/github/branch-deploy/91f77d0f24b03ff5f3d0fd24ce45498d1690d16b/node_modules/@octokit/request/dist-node/index.js:125:1
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at createBranch (/home/runner/work/_actions/github/branch-deploy/91f77d0f24b03ff5f3d0fd24ce45498d1690d16b/src/functions/lock.js:290:1)
    at lock (/home/runner/work/_actions/github/branch-deploy/91f77d0f24b03ff5f3d0fd24ce45498d1690d16b/src/functions/lock.js:642:1)
    at run (/home/runner/work/_actions/github/branch-deploy/91f77d0f24b03ff5f3d0fd24ce45498d1690d16b/src/main.js:517:1)
2024-08-22T19:44:58.6966927Z ##[error]refs/heads/up sandbox-branch-deploy-lock is not a valid ref name. - https://docs.github.com/rest/git/refs#create-a-reference
2024-08-22T19:44:58.7364488Z Post job cleanup.
2024-08-22T19:44:58.8300657Z ##[warning]⛔ bypass set, exiting
2024-08-22T19:44:58.8507136Z Cleaning up orphan processes

Extra Information
No response

refs/heads/up sandbox-branch-deploy-lock is not a valid ref name

This certainly looks like its related to the upgrade that changed the way this Action handles locks. In the latest version of this Action, locks are environment specific. So it looks like a lock is trying to be created for the up sandbox environment. However this fails the GitHub API validation for new branches as up sandbox-branch-deploy-lock is an invalid ref name as it contains a space. I'll need to do some digging to look into a non-breaking way to fix this.

...Thinking out loud
I think it would be a good idea to simply translate the environment names to valid branch names for locking functionality.
Example:
up sandbox becomes up-sandbox-branch-deploy-lock.
This should be the only change required.

@hashtagchris I have published a pre-release (v9.7.0) that should fix this problem. When you have a moment to try it out, let me know if it fixes your issue. Thank you! 🙇

Related pre-release for users of the github/lock action: https://github.com/github/lock/releases/tag/v2.3.0

@GrantBirki Looks like it works. Thank you!
issue comment
.migrate up sandbox

Actions logging
Run github/branch-deploy@4445cd011b320a788114409e6c6f855732b20a3e
✅ comment body starts with trigger: .migrate
🌍 environment: up sandbox
✅ CI checks passed and required reviewers have been disabled for this environment
🍯 sticky_locks: false
🍯 sticky_locks_for_noop: false
🔒 created lock branch: up-sandbox-branch-deploy-lock
✅ deployment lock obtained
🚀 deployment started!


Revert "Fixed instruction::replace() logic. "

Reverts ROCm/AMDMIGraphX#3553

Why are we reverting this PR? What is the issue?

Why are we reverting this PR? What is the issue?

Failing our tests https://github.com/ROCm/AMDMIGraphX/pull/3572. Tests probably need updates