text:
I want to mark on pdf

hi
thank you for PdfViewer
I want to know if i Can I make mark  on page
Example
i open pdf with  AndroidPdfViewer i stop on page 20
When i open  next time i want pdf open on page 20 not page 1
If there is such a thing will be very cool
thank you

You add your own code to do this. It's just a case of storing the page and passing to page number when you reopen.

Closing due to no response from author

hi how i do this i dont no

Easiest was is pass the page number with the intent... then load the page number passed by the intent.

@sapq If you want to store page number on configuration change, then you have to save it in onSaveInstanceState() and restore in onRestoreInstanceState(). If you want to store page number for longer period, you may use SharedPreferences. In both cases you have to pass stored page number to .defaultPage(int) method, when opening PDF document.

can i have code sample pls thank you  this will help me

I gave you whole idea, if you still don't know how to do it, please learn Android API. Your problem is not related to this library. Using google you will find tons of articles about storing activity state.

i just want no how i do this  i dont have  Experience

As I said, there are many articles about storing activity state, use google to find them.

i try use this  but not work  pls tell me what the  proplem
`@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.newpdf);
pdfView = (PDFView) findViewById(R.id.pdfView);
displayFromAsset(SAMPLE_FILE);
}
private void displayFromAsset(String assetFileName) {
    pdfFileName = assetFileName;

    pdfView.fromAsset(SAMPLE_FILE)
            .defaultPage(SharedPreferences)
            .enableSwipe(true)
            .swipeHorizontal(false)
            .onPageChange(this)
            .enableAnnotationRendering(true)
            .onLoad(this)
            .scrollHandle(new DefaultScrollHandle(this))
            .spacing(10)
            .load();
}

@Override
public void onPageChanged(int page, int pageCount) {
    SharedPreferences.Editor editor = sharedPreferences.edit();
    editor.putInt(name,page);
    editor.commit();
}

@Override
public void loadComplete(int nbPages) {
    PdfDocument.Meta meta = pdfView.getDocumentMeta();
    printBookmarksTree(pdfView.getTableOfContents(), "-");

}

public void printBookmarksTree(List<PdfDocument.Bookmark> tree, String sep) {
    for (PdfDocument.Bookmark b : tree) {

        Log.e(TAG, String.format("%s %s, p %d", sep, b.getTitle(), b.getPageIdx()));

        if (b.hasChildren()) {
            printBookmarksTree(b.getChildren(), sep + "-");
        }
    }
}`

i fix my proplem thank you
`   public static final String MY_PREFS_NAME = "MyPrefsFile";
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.newpdf);
    pdfView = (PDFView) findViewById(R.id.pdfView);
    displayFromAsset(SAMPLE_FILE);
}

private void displayFromAsset(String assetFileName) {
    pdfFileName = assetFileName;

    pdfView.fromAsset(SAMPLE_FILE)
            .defaultPage(getPageNumber())
            .enableSwipe(true)
            .swipeHorizontal(false)
            .onPageChange(this)
            .enableAnnotationRendering(true)
            .onLoad(this)
            .scrollHandle(new DefaultScrollHandle(this))
            .spacing(10)
            .load();
}

@Override
public void onPageChanged(int page, int pageCount) {

    setPageNumber(page)
    setTitle(String.format("%s %s / %s", pdfFileName, (getPageNumber() + 1), pageCount));
}

@Override
public void loadComplete(int nbPages) {
    PdfDocument.Meta meta = pdfView.getDocumentMeta();
    printBookmarksTree(pdfView.getTableOfContents(), "-");

}

 public void setPageNumber(int pageNumber) {
        SharedPreferences.Editor editor = getSharedPreferences(MY_PREFS_NAME, MODE_PRIVATE).edit();
        editor.putInt("page_number", pageNumber);
        editor.apply();
    }

    public int getPageNumber() {
        SharedPreferences prefs = getSharedPreferences(MY_PREFS_NAME, MODE_PRIVATE);
        return prefs.getInt("page_number", 0);
    }

public void printBookmarksTree(List<PdfDocument.Bookmark> tree, String sep) {
    for (PdfDocument.Bookmark b : tree) {

        Log.e(TAG, String.format("%s %s, p %d", sep, b.getTitle(), b.getPageIdx()));

        if (b.hasChildren()) {
            printBookmarksTree(b.getChildren(), sep + "-");
        }
    }
}`

I have a problem  if  i have 40 PDF
when i use frist pdf i go page number 10 and i closed
the proplem is all  pdf when i open go page number 10
what i do to fix this proplem any idia
thank you

You also need to store the pdf path and if it reopens the and pdf reuse the page number otherwise use page 0.

authors: 1stmetro barteksc sapq


text:
docs(node): Update post Geth archive snapshot deprecation

What changed? Why?
Updates our docs post Geth archive snapshot deprecation
Notes to reviewers
N/A
How has it been tested?
Localhost

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

source: gharchive/pull-request

authors: cb-heimdall wbnns

repo: base-org/web

license_type: permissive

license_source: github-api


text:
ES5 transpiling

Issue https://github.com/basemate/matestack-ui-core/issues/238: Older browsers support through ES5 transpiling and polyfills.
Changes

[x] Updated ruby gems, specially webpacker to 4.0 version.
[x] Updated node packages to use latest babeljs, @babel/preset-env and necessary plugins.
[x] Updated .babelrc to use the newly version of babeljs and @babel/preset-env
[x] Added core-js polyfills to webpack entry file.

Notes

Please, take special care with the first bullet point above, since I'm not a ruby developer probably I broke something 🙁, if that's the case I'll gladly downgrade the packages and I'll only upgrade the webpacker since that's the only critical package to upgrade.

Hey @sigfriedCub1990! Thanks for your work here so far. I actually would ask you not to change the gem versions and only focus on the javascript adjustments :) Just to limit the scope of this PR. We will update the gems in other specific PRs. Thanks!

No problems @jonasjabari, the only gem I really need to update is the webpacker gem

Hey @sigfriedCub1990 thank you for the clarifications!
The thing with Gemfile.lock didn't turn out the way I hoped, though. Could you simply remove the file from your PR and I recreate it locally after merging your PR? :)

Hey @sigfriedCub1990, thank you for the fast reactions!
I've now checked out your changes locally and the tests suite passes, so we're fine on that side. In the vendor/assets/javascript/ however, there's still a number of const and let ES6 in the .js files that are created/updated by running ./bin/webpack in the builder/ directory.
Do you have an idea how to fix that? Or am I missing a step somewhere?

Hey @sigfriedCub1990, thank you for the fast reactions!
I've now checked out your changes locally and the tests suite passes, so we're fine on that side. In the vendor/assets/javascript/ however, there's still a number of const and let ES6 in the .js files that are created/updated by running ./bin/webpack in the builder/ directory.
Do you have an idea how to fix that? Or am I missing a step somewhere?

Let me check that after lunch :)

Hey @pascalwengerter, it seems like there is partial support in IE 11 for let and const declarations, so it shouldn't be a problem. More info here const, let.
Anyway, if we could test this with IE 11 users I would be more comfortable :) and if there's a problem I'll fix it.

repo: basemate/matestack-ui-core

license: MIT


text:
Flow <= 0.47 requires libelf

Running flow <= 0.47 in Docker containers is quirky because of it's requirement on libelf.
This requirement has been removed in 0.48.

Fixed by #10

source: gharchive/issue

repo: baseonmars/roc-plugin-flow

license: mit

license_source: bigquery


text:
Migration from nuxt-speedkit to nuxt-booster

Describe the bug
Build Size Increased from 104MB to 370MB After Migrating from Speed-Kit to Nuxt-Booster.
with nuxt-booster
nuxt verison: 3.5.3
nuxt-booster:3.0.16

with speed-kit
nuxt verison: 3.5.3
nuxt-speed-kit: 3.0.0-next.20

Hello @fareed13 ,
could you have a look at where in the .output folder the problem occurs?

I encountered an issue with build size when using nuxt-booster compared to speed-kit. Here are the details:

Folder Name
With Speed Kit
With Booster

_nuxt
19.5 MB
18.8 MB

admin
11.4 MB
58.5 MB

blog
4.3 MB
21.7 MB

classes
47 MB
219.6 MB

curriculum
7.1 MB
1.4 MB

instructor
4.3 MB
20.2 MB

location
1.9 MB
8.9 MB

locations
3.3 MB
14 MB

agreements
304 KB
1.4 MB

attendance
307 KB
1.5 MB

belts
319 KB
1.5 MB

checkout
318 KB
1.5 MB

customers
321 KB
1.5 MB

events
304 KB
1.4 MB

gift-card
317 KB
1.5 MB

login
310 KB
1.5 MB

privacy-policy
304 KB
1.4 MB

profile
314 KB
1.5 MB

referral-hero
304 KB
1.5 MB

refund-policy
304 KB
1.4 MB

reservation
314 KB
1.5 MB

reviews
304 KB
1.4 MB

schedule
312 KB
1.5 MB

setup
269 KB
1.4 MB

test
303 KB
1.4 MB

As shown, the build size increases significantly for most folders when using nuxt-booster compared to speed-kit. This is causing issues with our deployment. Any insights or suggestions would be appreciated.
Thank you.

Interesting, so either the index.html or _payload.json files seem to be larger?
Unfortunately I can't reproduce this, so can you take a closer look?
If necessary, please provide files so that I can take a look at what has happened.

Thank you for looking into this. I took a closer look, and it seems that the significant size differences are primarily in the index.html files. Here are the specific sizes:

Folder Name
With Speed Kit
With Booster

index.html
289 KB
1.1 MB

_payload.json
631 bytes
631 bytes

As shown, the index.html files are much larger with nuxt-booster, while the _payload.json files remain the same size.
Unfortunately, due to the nature of our client's private repository, I'm unable to share the specific files directly. However, if there are any specific details or logs you need me to look at, please let me know and I'll do my best to provide the necessary information.

To help you reproduce the issue, I have created a public repository with the necessary setup. You can find the repository here: nuxt-3.5.3.
In the main branch, you will find the setup with nuxt-speedkit, which has a build size of 14 MB. I have also created a separate branch named migration-to-booster, and a PR has been created for this migration, which results in a build size of 31.3 MB. Please note that this repository contains a very small chunk of the application, and the build size increases as more pages are added.
To reproduce the issue, follow these steps:
Clone the repository.
Checkout the migration-to-booster branch.
Run the following commands to set environment variables:

export DEFAULT_PAGE_DOMAIN=lahore.abbitest1.com
export PORT=3999

If you need any additional information or if there's anything more required, please feel free to ask.

Thanks @fareed13,
you are still using an old version 3.0.0-next.20 is already very old for not renamed 😉
At the moment another feature was added.
When generating the css files contained in the head are embedded.
Important in SSR, the CSS is already present.
This leads to the fact that 1 mb Vuetify CSS is now included.
Are you staying with Vuetify? has quite an overhead in itself and is not suitable for websites with good PageSpeed.
The focus is more on applications.
I can see the options right now:

add PurgeCSS, which removes unused CSS.
choose an alternative to Vuetify, e.g. https://tailwindcss.com/
deactivate the embedding of styles during generation

⚠ Still needs to be implemented
This would be an optional option that must be set separately.
Also leads to further initial requests

@ThornWalli You're right about we are using 3.0.0-next.20 version, it was latest when we shifted from nuxt2 to nuxt3. However this older version working far better then the new one in term of load speed as well as build size.
We can't move to another UI as we have a very large scale website already built with vuetify.
For your reference please check https://github.com/fareed13/nuxt-3.5.3/pull/1/files diffrences. You can see that only changing nuxt-speedkit(deprecated) to nuxt-booster result in 13.6mb to 29.4mb, more than 2X increase in build size. performance is same on both of builds, I checked google pagespeed. Speedkit performs lil better BTW.
here I have deployed the sites on netlify to see the performance difference as well.
Website with speedkit
Website with booster
https://github.com/basics/nuxt-booster/assets/85872908/d27b3be5-67b7-4a93-bbda-71b502ddd06d
here are the static build generated with nuxi generate command
builds.zip
So keep in mind that there is not a single change except for booster package, we got this results. Increase in build size and decrease in performance. When we implement this in our main a very large project, build size increases from 104mb to 370+mb as well as performance decrement. Doesn't make sense to me.
Your help is appreciated. thanks!

you could roughly deactivate this optimization with this https://basics.github.io/nuxt-booster/guide/options.html#optimizepreloads
Alternatively, I'm thinking about making it partially configurable, there's a lot going on https://github.com/basics/nuxt-booster/blob/main/src/utils/preload.js#L4

@fareed13 @muhammad-grayphite
Got an update: npm i nuxt-booster@3.0.17-next.3
The property optimizePreloads has been replaced with optimizeSSR.

The optimizeSSR property can be Boolean, then everything is activated
Or an object is set.

  optimizeSSR: false, // default: true

  optimizeSSR: {
    cleanPreloads: true,
    cleanPrefetches: true,
    inlineStyles: true
  }

The embedding of the style can be deactivated there, for example.
  optimizeSSR: {
    inlineStyles: false
  }

@ThornWalli, I noticed that the build size has decreased by about 80MB. I’m not sure if this will impact our website’s Lighthouse performance, but I checked and didn’t see much difference. Are there any cons to using these settings?
However, the build size is still 290MB (down from 370MB), which is quite large compared to the 110MB we had in the previous version of Speedkit. Is there any noticeable change in Booster that could be contributing to this increase in size?

@muhammad-grayphite

CSS files are initially loaded in the head. Should not make any difference to the old version.
If necessary, you can still integrate https://www.npmjs.com/package/@nuxtjs/critters, which I had also removed.

integrate the CSS into the head because of FOUC. (https://de.wikipedia.org/wiki/Flash_of_Unstyled_Content) But it makes no sense with a large frontend framework with a lot of CSS.

What do you see in the index.html files?
These were large because the css was embedded.
This should no longer happen with this setting.
 optimizeSSR: {
    inlineStyles: false
  }

Yeah I think I see the noticeable difference. I can still see CSS in index file, yes file size decreased but its not enough. Other thing I can look into critters if it can help us.

@muhammad-grayphite I removed all styles from the /index.html in the example, I noticed that the ssr payload is quite large. As formatted JSON >200KB.
Writes a lot of data when generating.
Maybe that would be interesting https://nuxt.com/docs/api/nuxt-config#renderjsonpayloads

authors: ThornWalli fareed13 muhammad-grayphite

repo: basics/nuxt-booster


text:
Add "featured on" section

https://realpython.com/podcasts/rpp/158/#t=1588
There was also feedback that the exclusios docs were hard to find.

Fixed in https://github.com/basnijholt/rsync-time-machine.py/pull/18.
Thanks again @digiglean!


text:
Theming: Animated gifs don't work in splash view

Hi @fabricecaruso Animated gifs in V34 don't work in the splash view, and this is an ideal place to put an animated gif as a loading spinner, can we fix this please?
Thanks

It will never work in the splash. It would need a complete rewrite to thread things.

Ok understood, a pity...

authors: fabricecaruso pajarorrojo


text:
Dark Mode

Converted into dark theme...
and here is the new look for dark theme:

It will make fossurl only dark 😞 i like it with white 😊

authors: aliglelo bauripalash

repo: bauripalash/fossurl


text:
CSV Parser should not complain about empty last line

Maybe resolvable (here)[https://github.com/bayesimpact/tds/blob/7f9d43de014ac333f05635abe45802a27a5fab89/frontend/src/utils/csv.ts#L50] by someone who knows what they're doing :)

authors: ericboucher tetraptych

repo: bayesimpact/tds


text:
Can't pull Ubuntu image

I try to pull an Ubuntu image from DockerHub.
oci_pull(
    name = "ubuntu",
    tag = "latest",
    image = "index.docker.io/library/ubuntu",
    platforms = [
        "linux/amd64",
    ],
)

I run:
bazel run @ubuntu_unpinned//:pin

It fails:
paul@Pauls-MBP redoapp % bazel run @ubuntu_unpinned//:pin
INFO: Invocation ID: 92366a73-2771-4d90-a1e8-d5c1adc254c8
DEBUG: /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl:235:14:
WARNING: fetching from https://index.docker.io/v2/library/ubuntu/manifests/latest without an integrity hash. The result will not be cached.
INFO: Repository ubuntu_unpinned instantiated at:
  /Users/paul/Dev/redoapp/redoapp/WORKSPACE.bazel:206:23: in <toplevel>
  /Users/paul/Dev/redoapp/redoapp/tools/container/workspace.bzl:4:13: in container_repositories
  /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl:582:16: in oci_pull
Repository rule pin_tag defined at:
  /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl:527:26: in <toplevel>
WARNING: Download from https://index.docker.io/v2/library/ubuntu/manifests/latest failed: class java.io.FileNotFoundException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'ubuntu_unpinned':
   Traceback (most recent call last):
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 512, column 33, in _pin_tag_impl
                downloader.download_manifest(rctx.attr.tag, "manifest_list.json")
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 282, column 74, in lambda
                download_manifest = lambda identifier, output: _download_manifest(rctx, state, identifier, output),
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 248, column 14, in _download_manifest
                _download(rctx, state, identifier, output, "manifests")
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 237, column 20, in _download
                download_fn(
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/private/download.bzl", line 117, column 25, in _bazel_download
                return rctx.download(**kwargs)
Error in download: java.io.IOException: Error downloading [https://index.docker.io/v2/library/ubuntu/manifests/latest] to /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/ubuntu_unpinned/manifest_list.json: GET returned 404 Not Found
ERROR: /Users/paul/Dev/redoapp/redoapp/WORKSPACE.bazel:206:23: fetching pin_tag rule //external:ubuntu_unpinned: Traceback (most recent call last):
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 512, column 33, in _pin_tag_impl
                downloader.download_manifest(rctx.attr.tag, "manifest_list.json")
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 282, column 74, in lambda
                download_manifest = lambda identifier, output: _download_manifest(rctx, state, identifier, output),
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 248, column 14, in _download_manifest
                _download(rctx, state, identifier, output, "manifests")
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/pull.bzl", line 237, column 20, in _download
                download_fn(
        File "/private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/rules_oci/oci/private/download.bzl", line 117, column 25, in _bazel_download
                return rctx.download(**kwargs)
Error in download: java.io.IOException: Error downloading [https://index.docker.io/v2/library/ubuntu/manifests/latest] to /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/ubuntu_unpinned/manifest_list.json: GET returned 404 Not Found
ERROR: java.io.IOException: Error downloading [https://index.docker.io/v2/library/ubuntu/manifests/latest] to /private/var/tmp/_bazel_paul/5a5efa90f7fa1e8cbf1caad71f9e5c69/external/ubuntu_unpinned/manifest_list.json: GET returned 404 Not Found
INFO: Elapsed time: 0.629s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
ERROR: Build failed. Not running target

I'm using macOS arm64.

Oh looks like ubuntu images now use oci image types. This will need a fix.

authors: pauldraper thesayyn


text:
Building issues on multiple operating systems

Description of the bug:
Building on MacOS 14.2.1 (23C71) with XCode Xcode 15.0 Build version 15A240d and CLang
Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: arm64-apple-darwin23.2.0
Thread model: posix
InstalledDir: /Applications/Xcode.15.0.0.15A240d.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Gives
mac.log
and on Windows 11 Pro 23H2 with Visual Studio 2022 Preview  I get the following in the Developer Command Prompt of Visual studio 2022
mac.log
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Build the latest development version on MacOS or Windows
Which IntelliJ IDE are you using? Please provide the specific version.
I built using command-line
What programming languages and tools are you using? Please provide specific versions.
Go
What Bazel plugin version are you using?
7.0.0
Have you found anything relevant by searching the web?
Many old complaints about old Bazel bugs.

The only OS I could build it on was Ubuntu 22 with gcc.

We are aware of this and working on fixing it. That's because of the ongoing bzlmod migration.

Good to know that. If I can be of any help just ask :)

authors: agluszak ahmedyarub

repo: bazelbuild/intellij


text:
Update scalafmt-core to 3.7.6

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.6.1 to 3.7.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #85.

repo: bbarker/diz


text:
Update scalafmt-core to 3.7.11

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.6.1 to 3.7.11
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #92.


text:
No warning for non-private class method: private; def self.methodname; end

This code is rubocop clean on version (0.35.1)
There is no warning that Self.not_priv is not a private method.
# This is properly private
class Eigen
  class << self
    # def caller; priv; end

    private

    def priv
      puts 'I\'m private in Eigen'
    end
  end
end

# Here, the `not_priv` method is *not* private - why?
class Self
  # def self.caller; not_priv; priv; end # both calls work just fine

  private

  def self.not_priv
    puts 'I am NOT private in Self'
  end

  private_class_method def self.priv
    puts 'Im AM private in Self'
  end
end

Self.not_priv # WORKS!?!? why not private??

# As expected: private method `priv' called for Eigen:Class (NoMethodError)
Eigen.priv

# As expected: private method `priv' called for Self:Class (NoMethodError)
Self.priv

Please try on master.

master warns appropriately. Will remember for future - thanks!

authors: HaleTom alexdowad

repo: bbatsov/rubocop


text:
add help to plot_channel

Currently, you have to look into the help of plotutil_channel1D resp 2D. But help should be available in plot_channel.

I can take this.

the help of 1D has slightly changed due to new functionality... (no .plotStd anymore but .plotStat instead).. I have filed a pull request but it's not merged, yet.

OK, it is merged, now, the help in master is up to date


text:
Warning when bundling with Vite

When bundling with Vite in a SvelteKit application, I get the following warning:
leaflet-rotatedmarker doesn't appear to be written in CJS, but also doesn't appear to be a valid ES module (i.e. it doesn't have "type": "module" or an .mjs extension for the entry point). Please contact the package author to fix.
If possible I would like to see this fixed, as it is kinda annoying to see pop up in my terminal.

This may be fixed in bbecquet/Leaflet.RotatedMarker#27
I tried it and I did not see that message

authors: ornato-t sakgoyal


text:
Write response in Raft

In the raft simulation, update the version when the leader replies that it was successfully committed.
This should boost the write latency and be more realistic.

Added a "commit latency" metric

repo: bbengfort/cloudscope


text:
Have to re-initialize constantly, daily

My Alexa Routine nodes are constantly asking me to "open http://192.168.x.xx:3456 in your browser", that IP being the IP address of my Home Assistant install. I go to that webpage in a browser and enter my Amazon username/password and then it tells me "Amazon Alexa Cookie successfully retrieved. You can close the browser.". It then starts working, but within a day, I notice my Alexa isn't speaking again. Have to do it all over again.
I see this in the Node-Red Add-On log during startup:
13 Sep 13:26:59 - [warn] [alexa-remote-account:66fb228ef256d965] ENOENT: no such file or directory, open 'authorizationAlexa'
13 Sep 13:26:59 - [info] [alexa-remote-account:66fb228ef256d965] intialising with the PROXY method and NO saved data...
13 Sep 13:26:59 - [warn] [alexa-remote-account:66fb228ef256d965] open http://192.168.1.9:3456 in your browser

And then when a flow triggers that tries to use it, I see this:
13 Sep 13:39:47 - [error] [alexa-remote-routine:Alexa Speak Living Room Only] Account not initialised!
After I go to the URL and log in, I see this in the log:
13 Sep 13:59:38 - [info] [alexa-remote-account:66fb228ef256d965] intialising with the PROXY method and saved data...
I never see a "Success" message or anything else, which there should be a log entry whether it succeeds or fails. Anyway.
It's quite an annoyance to have to do this daily. I don't exactly recall when this started happening, but I would estimate about 2-3 months ago; I have been procrastinating to figure out a solution until now. And I haven't found one.

Same here, every 24 hours i have to re-initialize. @bbindreiter is there any workaround for this issue?

Same here, every 24 hours, which sadly makes this add-on next to useless for me. I'm guessing Amazon changed something in the login process? @bbindreiter any ideas on how to resolve this?

@magyartj to me it looks like the file the cookie is saved to is not persisted? Is the file there when it asks you to reinitialize?
I am reinitializing every 12 hours in my node-red instance and haven't noticed any problem (so far). Doing that for years now.
I am sorry but this solution will never work reliability and it can break every day over and over again.. 😭

Here the file ist there, i remember i had to create the file and add the cookie-text. Is it still working like that or should the file be created itself after receiving the cookie from the Login amazon Website?

I am having most likely a permission problem. Whatever folder I put in the file field, I get some error:
"ENOENT: no such file or directory, open '/home/dietpi/alexa.txt'"
The authorization itself works, but is gone after redeploying something.

authors: Babelbernd DeepflashX alanthewild bbindreiter magyartj


text:
Install: gnomad for hg19 fails

After downloading, this error occurs after some time (~30-40 min):
> gsort version 0.0.6
uniq v0.57

options:     input VCF file        -normalize v
0.5         [o] output VCF file
-

options:     input VCF file                                  -
         [o] output VCF file                                 -
         [w] sorting window size                             10000
         [n] no fail on reference inconsistency for non SNPs true
         [q] quiet                                           false
         [d] debug                                           false
         [r] reference FASTA file                            ../seq/hg19.fa

[W::vcf_parse] Contig 'chr1' is not defined in the header. (Quick workaround: index the file with tabix.)
Warning: The tag "AC_nfe_bgr" not defined in the header
Warning: The tag "AN_nfe_bgr" not defined in the header
Warning: The tag "AF_nfe_bgr" not defined in the header
Warning: The tag "nhomalt_nfe_bgr" not defined in the header
Warning: The tag "AC_sas_male" not defined in the header
Warning: The tag "AN_sas_male" not defined in the header
Warning: The tag "AF_sas_male" not defined in the header
[W::vcf_parse] Contig 'chr1' is not defined in the header. (Quick workaround: index the file with tabix.)
Encountered error, cannot proceed. Please check the error output above.

stats: biallelic
          no. left trimmed                      : 0
          no. right trimmed                     : 0
          no. left and right trimmed            : 0
          no. right trimmed and left aligned    : 0
          no. left aligned                      : 0

       total no. biallelic normalized           : 0

       multiallelic
          no. left trimmed                      : 0
          no. right trimmed                     : 0
          no. left and right trimmed            : 0
          no. right trimmed and left aligned    : 0
          no. left aligned                      : 0

       total no. multiallelic normalized        : 0

       total no. variants normalized            : 0
       total no. variants observed              : 0
       total no. reference observed             : 0

Time elapsed: 0.00s

stats: Total number of observed variants   0
       Total number of unique variants     0

Time elapsed: 0.00s

Traceback (most recent call last):
  File "/opt/bcbio/anaconda/bin/bcbio_nextgen.py", line 221, in <module>
    install.upgrade_bcbio(kwargs["args"])
  File "/opt/bcbio/anaconda/lib/python3.6/site-packages/bcbio/install.py", line 106, in upgrade_bcbio
    upgrade_bcbio_data(args, REMOTES)
  File "/opt/bcbio/anaconda/lib/python3.6/site-packages/bcbio/install.py", line 348, in upgrade_bcbio_data
    args.cores, ["ggd", "s3", "raw"])
  File "/tmp/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 354, in install_data_local
    _prep_genomes(env, genomes, genome_indexes, ready_approaches, data_filedir)
  File "/tmp/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 480, in _prep_genomes
    retrieve_fn(env, manager, gid, idx)
  File "/tmp/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/genomes.py", line 850, in _install_with_ggd
    ggd.install_recipe(os.getcwd(), env.system_install, recipe_file, gid)
  File "/tmp/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/ggd.py", line 30, in install_recipe
    recipe["recipe"]["full"]["recipe_type"], system_install)
  File "/tmp/tmpbcbio-install/cloudbiolinux/cloudbio/biodata/ggd.py", line 62, in _run_recipe
    subprocess.check_output(["bash", run_file])
  File "/opt/bcbio/anaconda/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/opt/bcbio/anaconda/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bash', '/opt/bcbio/genomes/Hsapiens/hg19/txtmp/ggd-run.sh']' returned non-zero exit status 255.

Luca;
Apologies about the issue. gnomad 2.1 has been a difficult integration due to the large file sizes and challenges in filtering down the annotations. This is still a work in progress and @naumenko-sa has been working through potential solutions (https://github.com/chapmanb/cloudbiolinux/issues/298#issuecomment-489142860)

Is there a way to bypass this just in case, what is the datatarget that pulls this in? Because even after removing tmpbcbio-install and removing --datatarget cadd it still tries to download the gnomad exomes (and fails, see the linked bug report).

Hi @lbeltrame !
Thanks for reporting the issue and sorry that you have trouble updating gnomad to 2.1
I was able to reproduce and pushed a fix - now it works on a small file for me.
You may replace the recipe in your tmpbcbio-install/cloudbiolinux/ggd-recipes/hg19
and rerun bcbio_nextgen.py upgrade .. command
The new recipes for exome and genome are here
https://github.com/naumenko-sa/cloudbiolinux/tree/master/ggd-recipes/hg19
Or update after PR gets merged:
https://github.com/chapmanb/cloudbiolinux/pull/300
Let me know if you see any other issues.
@chapmanb,
gnomad2.1 genome processing is very slow. I'm generating grch37 for more than a week for now.
I propose just to generate them one time for grch37, hg38, and hg19 (I'm doing that)
and push somewhere in the cloud (cloudbiolinux bucket?)
Sergey

Sergey and Luca;
Thank you both for the reports and the helpful fixes. Hopefully the new updates get things running for Luca. For the longer term I'm agreed that the processing times here seem like a no-go and hosting these is probably the best option. The downside is always the hosting/download costs but I don't see a reasonable workaround so let's do it. Sergey, do you have prepared files on AWS/S3 or somewhere else? If you're having trouble getting it finished, we could also run this separately and get them uploaded, just trying to use your head start and knowledge of the problem. Thanks again.

Hi Brad!
I'm processing the files on a local cluster. Now with per chromosome processing in parallel, I hope to get all 6 finished in 2-3 days. Maybe we can ask the Ensembl team to host the resulting merged files? It would be beneficial for many of their users, not just for bcbio and it is not a huge addition to their ftp server. Do you know by any chance whom we may contact in Ensembl?  SN

Sergey;
That's a great idea. Hopefully Ensembl would have interest in hosting this. I don't have any specific contacts but I think posting on the development list (https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org) would be a good place to start. Thanks again.

Hi Brad!

Could you please merge
https://github.com/chapmanb/cloudbiolinux/pull/302
I found another issue - the order of vcf files when merging.
concatenated exome files are ready for hg38, hg19, grch37. They are 3.6G each.
gnomad genome per chr downloading and processing is running
Linking a thread in Ensembl mail list
https://lists.ensembl.org/pipermail/dev_ensembl.org/2019-May/013346.html

SN

Sergey;
Thanks much for the fixes, being on top of these, and the messages to the Ensembl mailing list. Fingers crossed they'll be able to host and then we can transfer this to a download based install, with the recipes just kept for future updates (which will hopefully be infrequent).

Hi Brad and everyone who follows gnomad2.1 drama!

Added correct merging for genome recipes and helper scripts to process and merge gnomad vcf locally
https://github.com/chapmanb/cloudbiolinux/pull/303. Please merge.
gnomad.vcf.gz for grch37 is ready. It is 55G (compared to 370G for original chr vcfs). It took 2 weeks to run the recipe with 1 thread. In parallel, with the helper scripts, it takes ~1day
gnomad.vcf.gz for hg38 and hg19 are almost ready, hopefully, <1day left
let me know if anybody has ftp server and wants to host these files, I'd be happy to upload.

SN

Hi Brad!
Unfortunately, Ensembl does not want to host these files.
https://lists.ensembl.org/pipermail/dev_ensembl.org/2019-May/013348.html
Do you think reaching gnomad team might help?
Or we might just roll back to gnomad2.0.1 - not ideal, but it is better to have working gnomad by default rather than not working gnomad. The advanced users may run processing scripts provided outside of cloudbiolinux to upgrade their gnomad to 2.1.
Sergey

Hi Brad!
Slim files for gnomad2.1 genome (55G) and exome (5G) for hg19/hg38/grch37 are ready for uploading.
The final portion of helper scripts:
https://github.com/chapmanb/cloudbiolinux/pull/305
S.

Sergey;
Thanks much for being on top of this and getting these all finished. I'm bummed about the Ensembl response and think your idea of asking the Gnomad team might work. Another idea is the genome in a bottle community (https://groups.google.com/forum/#!forum/giab-analysis-team). While this is less directly related there, it's a useful resource for variant interpretation and filtering, so might be of interest. Fingers crossed that one of these options works.

Wrote to Gnomad team:
https://gnomad.broadinstitute.org/contact

NCBI (GIAB) also cannot host the files. Can anybody kindly ping the Gnomad team, if you have contacts?
SN

Hi Sergey,
I tried tweeting at Dan, let's see if that works.

Is it correct that release 1.1.5 will not properly process hg38 gnomad 2.1? I need to upgrade for other reasons, what's the easiest way to get just the updated ggd recipes without having to upgrade to development?

Hi @ameynert !
bcbio1.1.5 uses new recipes from cloudbiolinux with gnomad2.1. I think they are working, just the processing is very slow - it might take 1 week to process gnomad genomes.
You may use helper scripts and this method to produce the merged gnomad 2.1 file:
https://github.com/chapmanb/cloudbiolinux/blob/master/doc/hacking.md#testing-a-ggd-recipe
https://github.com/chapmanb/cloudbiolinux/tree/master/ggd-recipes/hg38
Also if you can host the resulting gnomad2.1. vcf (55G) for the community, let us know. The file is ready and I can upload it.
Sergey

Thanks-- do you know if we have a way to disable the update to 2.1? When I pull in a --data update, I get 2.1 and it is more than I bargained for.

Thanks @naumenko-sa - my installer is on chr4 after <24 hours. I'll report back when it's finished or crashed. I will talk to our IT about the possibility of hosting the 55GB slim file.

Related to @roryk 's comment, how can I tell bcbio NOT to download the gnomAD genome files? I already built the exomes and that would be enough. However, with every --data I get prompted to get the genomes.
Another fresh install I'm doing is not doing that (so far), so I assume there must be something somewhere.

@naumenko-sa told me how to do it, but now I have forgotten. Sergey, could you remind us?

Hi @lbeltrame  and @roryk!
You may try to start the upgrade, wait till tmpbcbio-install/cloudbiolinux/ggd-recipes folder is created,
then terminate the upgrade. Modify tmpbcbio-install/cloudbiolinux/ggd-recipes/hg19/gnomad.yaml (just comment downloading and processing, or put there an old recipe). Restart the upgrade.
So it has been 2 months since we started trying to find a place to host for gnomad2.1. What should we do? Revert changes back to 2.0.1? @mbootwalla, any luck with hosting at your institution?
Sergey

Thanks, I think it makes sense to revert back while we figure out how to handle the 2.1 changes. @chapmanb what do you think?

https://raw.githubusercontent.com/chapmanb/cloudbiolinux/b6605021d7f9c9a36ae9c965819fe7ffa13c309d/ggd-recipes/hg38/gnomad_exome.yaml
and
https://raw.githubusercontent.com/chapmanb/cloudbiolinux/b6605021d7f9c9a36ae9c965819fe7ffa13c309d/ggd-recipes/hg38/gnomad.yaml
are the most recent 2.0.1 versions.

Luca -- if you want to skip gnomad installs/updates on an existing bcbio installation you can remove it from the datatarget options in bcbio/config/install-params.yaml, and then it will no longer try to grab it.
Sergey and Rory -- thanks for all the patience on this. My only other suggestion besides reverting is that we could host on S3 if we're cool paying the download costs. That might be a conversation to have since I know you spent a lot of time getting it prepared and it's a shame to have to go back.

It doesn't seem to work. I commented it out and it's still trying to download the hg38 exomes (which I already have in place).

@lbeltrame . Could you please try to set gnomad_exome,2.1 in your bcbio/genomes/Hsapiens/hg19/versions.csv. If you have 2.05 there, then bcbio is trying to install the new recipe which is 2.1
@chapmanb, @roryk. Gnomad now provides merged vcf files for all chromosomes.
https://storage.googleapis.com/gnomad-public/release/2.1.1/vcf/genomes/gnomad.genomes.r2.1.1.sites.vcf.bgz
WGS = 460G, EXOMES = 59G.
It solves the hosting problem, and now I can simplify the installation script. Maybe, it is not that bad? I tried a couple of connections now, including O2, it promised downloading WGS in 2-7h.
SN

Hi Sergey and bcbio team,
I am working with my supervisor on pushing this through. I will get back to
you guys in a couple of days and let you know where this stands. I
apologize for this taking so long.
Thanks,
Moiz
On Tue, Jul 2, 2019 at 9:08 AM Sergey Naumenko notifications@github.com
wrote:

@lbeltrame https://github.com/lbeltrame . Could you please try to set
gnomad_exome,2.1 in your bcbio/genomes/Hsapiens/hg19/versions.csv. If you
have 2.05 there, then bcbio is trying to install the new recipe which is 2.1
@chapmanb https://github.com/chapmanb, @roryk https://github.com/roryk.
Gnomad now provides merged vcf files for all chromosomes.
https://storage.googleapis.com/gnomad-public/release/2.1.1/vcf/genomes/gnomad.genomes.r2.1.1.sites.vcf.bgz
WGS = 460G, EXOMES = 59G.
It solves the hosting problem, and now I can simplify the installation
script. Maybe, it is not that bad? I tried a couple of connections now,
including O2, it promised downloading WGS in 2-7h.
SN
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bcbio/bcbio-nextgen/issues/2816?email_source=notifications&email_token=AAGP7RZWU7PX424Y5MNKEJ3P5N4RPA5CNFSM4HMA76W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZBY2OA#issuecomment-507743544,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGP7R7G66IZFYVPZ7C4T4TP5N4RPANCNFSM4HMA76WQ
.

Hi everyone,
Great-- if we grab https://storage.googleapis.com/gnomad-public/release/2.1.1/vcf/exomes/gnomad.exomes.r2.1.1.sites.vcf.bgz for the exomes and index it, is that enough for it to work as the gnomad_exome.vcf.gz file, or do we also need to do the fields_to_keep formatting and what not?

Hi Rory!
Sorry for the delay - could you please review and merge 3 recipes for gnomad exome?
https://github.com/chapmanb/cloudbiolinux/pull/322
SN

Thanks Sergey, that worked great!

authors: ameynert chapmanb lbeltrame mbootwalla naumenko-sa roryk

repo: bcbio/bcbio-nextgen


text:
Feat/calendar

Fully utilize the table calendar component,
implement style and
insert events, highlighted campaign (events and entries) marks on the calendar
call query to extract event/entries informations and show below

Good work!! See comments :) @ThomasWongHKG

authors: ThomasWongHKG andreasgan

repo: bcc-code/brunstadtv-app


text:
Migrate custom KeyCloak realm(s) to Gold Cluster

Migrate the BC Digital Trust Services realms from the gzyg46lx instances in the Silver cluster to the digitaltrust-citz instances in the Gold cluster.
Affected clients and applications:
bcgov-citz-issuer

ISED Business Banking Initiative
BC Services Card
[x] dev - https://bcgov-citz-issuer-dev.apps.silver.devops.gov.bc.ca
[x] test - https://bcgov-citz-issuer-test.apps.silver.devops.gov.bc.ca
[x] prod - https://bcgov-citz-issuer.apps.silver.devops.gov.bc.ca

bcreg-registration-issuer

ISED Business Banking Initiative
Verifiable Credentials
[x] dev - https://bcreg-registration-issuer-dev.apps.silver.devops.gov.bc.ca
[x] test - https://bcreg-registration-issuer-test.apps.silver.devops.gov.bc.ca
[x] prod - https://bcreg-registration-issuer.apps.silver.devops.gov.bc.ca

bcreg-relationship-issuer

ISED Business Banking Initiative
Verifiable Credentials
[x] dev - https://bcreg-relationship-issuer-dev.apps.silver.devops.gov.bc.ca
[x] test - https://bcreg-relationship-issuer-test.apps.silver.devops.gov.bc.ca
[x] prod - https://bcreg-relationship-issuer.apps.silver.devops.gov.bc.ca

issuer-kit-demo-verifier-chat

issuer-kit-demo-verifier-chat
Verifiable Credentials
[x] dev - https://pctftest-dev.vonx.io
[x] test - https://pctftest-test.vonx.io
[x] prod - https://pctftest.vonx.io

inoculation-issuer

essential-services-delivery
BC Services Card
[x] dev - https://inoculation-issuer-dev.apps.silver.devops.gov.bc.ca
[x] test - https://inoculation-issuer-test.apps.silver.devops.gov.bc.ca
[x] prod - https://inoculation-issuer.apps.silver.devops.gov.bc.ca

bcvcpilot-admin

trust-over-ip-configurations
IDIR / GitHub
[x] dev - https://bcvcpilot-issuer-admin-dev.apps.silver.devops.gov.bc.ca
[x] test - https://bcvcpilot-issuer-admin-test.apps.silver.devops.gov.bc.ca/
[x] prod - https://bcvcpilot-admin.vonx.io

bcvcpilot-web

trust-over-ip-configurations
Verifiable Credentials - Invite from bcvcpilot-admin only
Does not care about the redirect URL registration for the verifiable-credential IDP with vc-authn.
[x] dev - https://bcvcpilot-issuer-dev.apps.silver.devops.gov.bc.ca
[x] test - https://bcvcpilot-issuer-test.apps.silver.devops.gov.bc.ca/
[x] prod - https://bcvcpilot.vonx.io

identity-kit-admin

identity-kit-configurations
IDIR / GitHub
[x] dev - https://identity-kit-admin-dev.apps.silver.devops.gov.bc.ca
[x] test - https://identity-kit-admin-test.apps.silver.devops.gov.bc.ca
[x] prod - https://identity-kit-admin.vonx.io

identity-kit-public

identity-kit-configurations
Verifiable Credentials - Invite from identity-kit-admin
Does not care about the redirect URL registration for the verifiable-credential IDP with vc-authn.
[x] dev - https://identity-kit-dev.apps.silver.devops.gov.bc.ca
[x] test - https://identity-kit-test.apps.silver.devops.gov.bc.ca
[x] prod - https://identity-kit.vonx.io

The bcgov-citz-issuer, bcreg-registration-issuer, bcreg-relationship-issuer, issuer-kit-demo-verifier-chat, and inoculation-issuer KeyCloak clients and associated application and vc-authn configuration has been migrated to the realms in the Gold cluster.  All applications have been tested and are functioning as they were when connected to the previous realms.  The basic steps followed to migrate the KeyCloak clients and associated applications can be found here; KeyCloak Migration

identity-kit-admin and identity-kit-public were migrated to the new realms and tested yesterday (Thursday Dec. 15th).

The dev and test environments for bcvcpilot-admin  and bcvcpilot-web have been migrated.  Just coordinating with the admins for the bcvcpilot-admin prod environment before migrating the last two applications.

All applications have been migrated:

https://github.com/bcgov/ised-business-banking-initiative/pull/35
https://github.com/bcgov/issuer-kit-demo-verifier-chat/pull/82
https://github.com/bcgov/essential-services-delivery/pull/123
https://github.com/bcgov/trust-over-ip-configurations/pull/121
https://github.com/bcgov/identity-kit-configurations/pull/16

Backup exports of all of the old realms have been collected.  All application clients were disabled as the applications were migrated.  All Keycloak admin access (other than mine) has been revoked on the old realms.  The SSO team will be disabling the realms and disposing of them in January.

repo: bcgov/DITP-DevOps


text:
Transition to GitHub Projects for DITP Enterprise Teams

We can use this issue to track the transition from ZenHub to GitHub issues.
Proposed Approach:
Columns
Assignment Ready, Assigned, In Progress, In Review, with the assumption that closed issues/PRs disappear off the board.
Initialization:
Use ZenHub assignments, GitHub assignments to populate the project from the current work in process. On first pass, do not add anything that is not assigned.  There is not a need to add repos.
Process:

Get two side by side brower windows

For each person, view their GitHub assignments (all repos)
Add the tasks to the Projects.

Should be able to do them all in one from BC Gov repos, but will likely have to be done by repo in Hyperledger.

On going management:

Always create new issues in Project and in a repo

Avoid creating issues in specific repos if they are to be immediately part of the project, as we then have to do the extra step of importing the issue into the Project.
Can create issues in Hyperledger projects as well as BCGov issues by prefixing "hyperledger/" to the repo.
We can skip creating "general" issues in the DITP repo and just use Project issues (like this one) for that.
Continue to create "general" isssues in the DITP repo, as Project issues do not allow for comments.

When we are ready to add an issue from an existing project into the Project, import it, updating it as necessary.

I think this should be fairly easy to do during Standups.

Once a PR exists for an issue, I suggest closing the issue, and importing the PR into the Project. Importing the PR will be an additional step.

Developers will be "encouraged" (strongly) to add their own PRs to the Project for tracking.

Issues/PRs are NOT auto-added, and I don't think we want that. If the issue is going straight into the project, create it in the project -- no overhead in adding it.  If the issue already exists, only import it when (to be) assigned.
The only pain I see with that are the PRs, and that will be a matter of reminding the developer to add them as they are created, or add them during the Standups.
Bigger Efforts -- Epics
There is not the concept of an Epic in GH Projects, but I don't think we made a lot of practical use of that in ZenHub, and I think that is OK not to be there. The proliferation of repos in our world mostly covers that, and often the work of an "epic" is an assignment to an individual on our team. We can use milestones and/or per repo labels in place of epics to get "groupings" of work.
Permissions
We will still have the editing issues with Hyperledger tasks (e.g. assigning), but it appears anyone will be able to drag'n'drop work as they move status values.  We'll find out...
Standups:
The filtering will be sufficient during standups to manage/display the work by developer.

I think the migration is complete.  What I did:

Went through each team member in ZenHub and added their issues to Projects, moving their ZenHub issues to the "Migrated" column.

For ZenHub issues -- added the linked issue directly to the Project, if any. Added ZenHub only comments that were relevant.

Went through all remaining issues in the columns other than "New Issues" and "Epics", created them in the new Project, and moved them to "Migrated"
Left a couple of ZenHub only issues that were not linked to any GitHub issues.
Went through each team member's GitHub "All Assigned" PRs and Issues page and added any relevant ones not already in the Project to the Project.

Closing/unassigning issues as I went along.

I think we are now ready to go -- at least to get started.

repo: bcgov/DITP


text:
BEM correction Large Lake vs Landing

Just a quick check that both sections below meant to assign BEUMC_S1 to LL in the BEM corrections?

Large lake :  BCLCS_LEVEL_1 = 'N' AND BCLCS_LEVEL_5 = 'LA' AND Area_Ha >60 ha
Landing:  BCLCS_LEVEL_5 = 'LL'

ref:
https://github.com/bcgov/SSGBM-VRI-BEM/blob/a930c9dd9d3afd70aaaa08122b4e2e7ff52a22ca/Python_Scripts/01b_Step1_BEM_Corrections_BEC_Combo_Check_CSV_Output_v1.7.py#L299:L309
https://github.com/bcgov/SSGBM-VRI-BEM/blob/a930c9dd9d3afd70aaaa08122b4e2e7ff52a22ca/Python_Scripts/01b_Step1_BEM_Corrections_BEC_Combo_Check_CSV_Output_v1.7.py#L505:L510
There is no rush on this. I just wanted to raise a flag since those 2 conditions could have been combined into a single condition and it brought me to have some doubts on wether we really wanted to assign the LL value to both.

Great catch. That is an error.
The codes are a bit confusing here... a landing (where logs are loaded onto a truck) is coded LL and the lakes are coded LA.
We can't use w[cf.index("BEUMC_S1")] = "LL" for both of those.
We need to follow-up on this.
LL = Landing
A compacted area adjacent to a road used for sorting and loading logs.
LA = Lake
A naturally occurring static body of water more than two metres deep in some portion. The boundary for the
lake is the natural high water mark.
page 15
https://www2.gov.bc.ca/assets/gov/farming-natural-resources-and-industry/forestry/stewardship/forest-analysis-inventory/data-management/standards/vegcomp_poly_rank1_data_dictionaryv5_2019.pdf

authors: FrankBornais Jake-Bradshaw

repo: bcgov/SSGBM-VRI-BEM


text:
Park Information dashboard

Description
This PR includes the following proposed change(s):

BC-223

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[ ] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

Sorry about the big PR Arnel! I appreciate your help! :)


text:
Search and filter tables

As an internal user, I want to search or filter lists (Operators, BORO ID applications) (alphabetically or by timestamp) so that when I click into one thing and come back to my list, I will not need to re-sort my list to get back to the same spot in the list

@zoeyli-46 is going to specify which tables / refine

Team is already building this within each grid

authors: hannavovk patrickisaac zoeyli-46

repo: bcgov/cas-registration


text:
Simplify Serverless Sample App Code

Describe the Issue
As a developer I want a clean and clear example of an AWS ECF serverless application so that I can easily understand how a serverless application can be developed and deployed to the AWS ECF using GitHub Actions.
Additional Context

The original serverless sample app is an evolution of the container app which itself is a stripped down version of an openshift web app.
Because of the evolution of the app there is a lot of unused code and unneeded complexity.
This is just regarding the application code, not terraform or pipeline work.

Acceptance Criteria

Maintain all existing functionality
Remove all unused code
Simplify the code architecture
Ensure all libraries are updated
.
.
.
.
.
.
.
.
.
.
.

Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

Moving to the PB to accommodate higher priority work

https://github.com/bcgov/startup-sample-project-aws-serverless-OIDC/pull/13

https://github.com/bcgov/startup-sample-project-aws-serverless-OIDC/pull/13

authors: OmoAttah wrnu

repo: bcgov/cloud-pathfinder


text:
chore(deps): update vite to v4 (major)

This PR contains the following updates:

Package
Type
Update
Change
Pending

@vitejs/plugin-vue (source)
devDependencies
major
^3.0.3 -> ^4.0.0
4.2.3 (+1)

vite (source)
devDependencies
major
^3.0.9 -> ^4.0.0
4.3.6

Release Notes

vitejs/vite-plugin-vue
v4.2.1
Compare Source

fix: lang="tsx" can't be inlined (c3f5c9c), closes #159
chore: update changelog [ci skip] (9d0d7a7)

v4.2.0
Compare Source

feat: support 3.3 imported types in SFC macros (c891652)

v4.1.0
Compare Source

fix: avoid resolving to 2.7 compiler-sfc (cf36b3e)

v4.0.0
Compare Source

chore: update vite dep to ^4.0.0 (#49) (5a2f789), closes #49
chore(deps): update all non-major dependencies (#40) (4c95967), closes #40
chore(deps): update rollup and esbuild (#46) (92fec7b), closes #46

vitejs/vite
v4.3.5
Compare Source

fix: location is not defined error in cleanScssBugUrl (#13100) (91d7b67), closes #13100
fix: unwrapId and pass ssr flag when adding to moduleGraph in this.load (#13083) (9041e19), closes #13083
fix(assetImportMetaUrl): reserve dynamic template literal query params (#13034) (7089528), closes #13034
fix(debug): skip filter object args (#13098) (d95a9af), closes #13098
fix(scan): handle html script tag attributes that contain ">" (#13101) (8a37de6), closes #13101
fix(ssr): ignore __esModule for ssrExportAll (#13084) (8a8ea1d), closes #13084

v4.3.4
Compare Source

fix(define): incorrect raw expression value type in build (#13003) (8f4cf07), closes #13003
fix(importAnalysisBuild): support parsing 'VITE_PRELOAD' (#13023) (447df7c), closes #13023
fix(server): should respect hmr port when middlewareMode=false (#13040) (1ee0014), closes #13040
fix(ssr): track for statements as block scope (#13021) (2f8502f), closes #13021
chore: add changelog for vite 4.2.2 and 3.2.6 (#13055) (0c9f1f4), closes #13055

v4.3.3
Compare Source

fix: address file path mismatch when loading Vite config file on Windows (fix #12923) (#13005) (84c4118), closes #12923 #13005
fix: undefined document in worker (#12988) (08c1452), closes #12988
fix(resolve): deep import resolvedId error (#13010) (30a41ff), closes #13010
feat: optimize deps option to turn off auto discovery (#13000) (bd86375), closes #13000
chore(deps): update all non-major dependencies (#12805) (5731ac9), closes #12805

v4.3.2
Compare Source

fix: status optional in windows network drive regex (fix: #12948) (#12949) (f781fc6), closes #12948 #12949
fix: use realpathSync for node <16.18 on windows (#12971) (965839c), closes #12971
fix(ssr): hoist statements after hashbang (#12985) (07bd6d1), closes #12985
chore: build time message setting color (#12940) (ada7cd5), closes #12940
chore: remove extra ) in changelog (#12932) (e7924d2), closes #12932
chore: upgrade rollup (#12965) (bdb2f25), closes #12965
refactor: resolveExports (#10917) (ad21ec3), closes #10917

v4.3.1
Compare Source

fix: revert ensure module in graph before transforming (#12774) (#12929) (9cc93a5), closes #12774 #12929
docs: 4.3 announcement and release notes (#12925) (f29c582), closes #12925
chore: clean up 4.3 changelog (55ec023)

v4.3.0
Compare Source
Vite 4.3 is out! Read the announcement blog post here

In this minor, we focused on improving the dev server performance. The resolve logic got streamlined, improving hot paths and implementing smarter caching for finding package.json, TS config files, and resolved URL in general.
You can read a detailed walkthrough of the performance work done in this blog post by one of Vite Contributors: How we made Vite 4.3 faaaaster 🚀.
This sprint resulted in speed improvements across the board compared to Vite 4.2.
These are the performance improvements as measured by sapphi-red/performance-compare, which tests an app with 1000 React Components cold and warm dev server startup time as well as HMR times for a root and a leaf component:

Vite (babel)
Vite 4.2
Vite 4.3
Improvement

dev cold start
17249.0ms
5132.4ms
-70.2%

dev warm start
6027.8ms
4536.1ms
-24.7%

Root HMR
46.8ms
26.7ms
-42.9%

Leaf HMR
27.0ms
12.9ms
-52.2%

Vite (swc)
Vite 4.2
Vite 4.3
Improvement

dev cold start
13552.5ms
3201.0ms
-76.4%

dev warm start
4625.5ms
2834.4ms
-38.7%

Root HMR
30.5ms
24.0ms
-21.3%

Leaf HMR
16.9ms
10.0ms
-40.8%

You can read more information about the benchmark here
Features

feat: expose isFileServingAllowed as public utility (#12894) (93e095c), closes #12894
feat: reuse existing style elements in dev (#12678) (3a41bd8), closes #12678
feat: skip pinging the server when the tab is not shown (#12698) (bedcd8f), closes #12698
feat(create-vite): use typescript 5.0 in templates (#12481) (8582e2d), closes #12481
feat: use preview server parameter in preview server hook (#11647) (4c142ea), closes #11647
feat(reporter): show gzip info for all compressible files (fix #11288) (#12485) (03502c8), closes #11288 #12485
feat(server): allow to import data: uris (#12645) (4886d9f), closes #12645
feat: add opus filetype to assets & mime types (#12526) (63524ba), closes #12526

Performance

perf: parallelize await exportsData from depsInfo (#12869) (ab3a530), closes #12869
perf: avoid side effects resolving in dev and in the optimizer/scanner (#12789) (fb904f9), closes #12789
perf: parallelize imports processing in import analysis plugin (#12754) (037a6c7), closes #12754
perf: unresolvedUrlToModule promise cache (#12725) (80c526e), closes #12725
perf(resolve): avoid tryFsResolve for /@fs/ paths (#12450) (3ef8aaa), closes #12450
perf(resolve): reduce vite client path checks (#12471) (c49af23), closes #12471
perf: avoid new URL() in hot path (#12654) (f4e2fdf), closes #12654
perf: improve isFileReadable performance (#12397) (acf3a14), closes #12397
perf: module graph url shortcuts (#12635) (c268cfa), closes #12635
perf: reduce runOptimizerIfIdleAfterMs time (#12614) (d026a65), closes #12614
perf: shorcircuit resolve in ensure entry from url (#12655) (82137d6), closes #12655
perf: skip es-module-lexer if have no dynamic imports (#12732) (5d07d7c), closes #12732
perf: start preprocessing static imports before updating module graph (#12723) (c90b46e), closes #12723
perf: use package cache for one off resolve (#12744) (77bf4ef), closes #12744
perf(css): cache lazy import (#12721) (fedb080), closes #12721
perf(hmr): keep track of already traversed modules when propagating update (#12658) (3b912fb), closes #12658
perf(moduleGraph): resolve dep urls in parallel (#12619) (4823fec), closes #12619
perf(resolve): skip for virtual files (#12638) (9e13f5f), closes #12638
perf: avoid fsp.unlink if we don't use the promise (#12589) (19d1980), closes #12589
perf: back to temporal optimizer dirs (#12622) (8da0422), closes #12622
perf: cache depsCacheDirPrefix value for isOptimizedDepFile (#12601) (edbd262), closes #12601
perf: improve cleanUrl util (#12573) (68d500e), closes #12573
perf: non-blocking write of optimized dep files (#12603) (2f5f968), closes #12603
perf: try using realpathSync.native in Windows (#12580) (1cc99f8), closes #12580
perf: use fsp in more cases (#12553) (e9b92f5), closes #12553
perf(html): apply preTransformRequest for html scripts (#12599) (420782c), closes #12599
perf(optimizer): bulk optimizer delay (#12609) (c881971), closes #12609
perf(optimizer): start optimizer early (#12593) (4f9b8b4), closes #12593
perf(resolve): avoid isWorkerRequest and clean up .ts imported a .js (#12571) (8ab1438), closes #12571
perf(resolve): findNearestMainPackageData instead of lookupFile (#12576) (54b376f), closes #12576
perf(server): only watch .env files in envDir (#12587) (26d8e72), closes #12587
perf: avoid execSync on openBrowser (#12510) (a2af2f0), closes #12510
perf: extract regex and use Map in data-uri plugin (#12500) (137e63d), closes #12500
perf: extract vite:resolve internal functions (#12522) (6ea4be2), closes #12522
perf: improve package cache usage (#12512) (abc2b9c), closes #12512
perf: more regex improvements (#12520) (abf536f), closes #12520
perf: regex to startsWith/slice in utils (#12532) (debc6e2), closes #12532
perf: remove regex in ImportMetaURL plugins (#12502) (1030049), closes #12502
perf: replace endsWith with === (#12539) (7eb52ec), closes #12539
perf: replace startsWith with === (#12531) (9cce026), closes #12531
perf: reuse regex in plugins (#12518) (da43936), closes #12518
perf: use safeRealpath in getRealpath (#12551) (cec2320), closes #12551
perf(css): improve postcss config resolve (#12484) (58e99b6), closes #12484
perf(esbuild): make tsconfck non-blocking (#12548) (e5cdff7), closes #12548
perf(esbuild): update tsconfck to consume faster find-all implementation (#12541) (b6ea25a), closes #12541
perf(resolve): fix browser mapping nearest package.json check (#12550) (eac376e), closes #12550
perf(resolve): improve package.json resolve speed (#12441) (1fc8c65), closes #12441
perf(resolve): refactor package.json handling for deep imports (#12461) (596b661), closes #12461
perf(resolve): refactor tryFsResolve and tryResolveFile (#12542) (3f70f47)
perf(resolve): skip absolute paths in root as url checks (#12476) (8d2931b), closes #12476
perf(resolve): support # in path only for dependencies (#12469) (6559fc7), closes #12469

Bug Fixes

fix(build): do not repeatedly output warning message (#12910) (251d0ab), closes #12910
fix: escape msg in render restricted error html (#12889) (3aa2127), closes #12889
fix: yarn pnp considerBuiltins (#12903) (a0e10d5), closes #12903
fix: broken middleware name (#12871) (32bef57), closes #12871
fix: cleanUpStaleCacheDirs once per process (#12847) (2c58b6e), closes #12847
fix(build): do not warn when URL in CSS is externalized (#12873) (1510996), closes #12873
fix: build time deps optimization, and ensure single crawl end call (#12851) (fa30879), closes #12851
fix: correct vite config temporary name (#12833) (cdd9c23), closes #12833
fix(importAnalysis): warning on ExportAllDeclaration (#12799) (5136b9b), closes #12799
fix(optimizer): start optimizer after buildStart (#12832) (cfe75ee), closes #12832
fix: handle try-catch for fs promise when resolve https config (#12808) (0bba402), closes #12808
fix(build): correctly handle warning ignore list (#12831) (8830532), closes #12831
fix(resolve): use different importer check for css imports (#12815) (d037327), closes #12815
fix: ignore sideEffects for scripts imported from html (#12786) (f09551f), closes #12786
fix: warn on build when bundling code that uses nodejs built in module (#12616) (72050f9), closes #12616
fix(cli): pass mode to optimize command (#12776) (da38ad8), closes #12776
fix(css): resolve at import from dependency basedir (#12796) (46bdf7d), closes #12796
fix(worker): asset in iife worker and relative base (#12697) (ddefc06), closes #12697
fix(worker): return null for shouldTransformCachedModule (#12797) (ea5f6fc), closes #12797
fix: allow onwarn to override vite default warning handling (#12757) (f736930), closes #12757
fix: ensure module in graph before transforming (#12774) (44ad321), closes #12774
fix: update package cache watcher (#12772) (a78588f), closes #12772
fix: avoid clean up while committing deps folder (#12722) (3f4d109), closes #12722
fix: ignore pnp resolve error (#12719) (2d30ae5), closes #12719
fix: leave fully dynamic import.meta.url asset (fixes #10306) (#10549) (56802b1), closes #10306 #10549
fix: output combined sourcemap in importAnalysisBuild plugin (#12642) (d051639), closes #12642
fix: take in relative assets path fixes from rollup (#12695) (81e44dd), closes #12695
fix: throws error when plugin tries to resolve ID to external URL (#11731) (49674b5), closes #11731
fix(css): css file emit synchronously (#12558) (8e30025), closes #12558
fix(import-analysis): escape quotes correctly (#12688) (1638ebd), closes #12688
fix(optimizer): load the correct lock file (#12700) (889eebe), closes #12700
fix(server): delay ws server listen when restart (#12734) (abe9274), closes #12734
fix(ssr): load sourcemaps alongside modules (#11780) (be95050), closes #11780
fix(ssr): show ssr module loader error stack (#12651) (050c0f9), closes #12651
fix(worker): disable manifest plugins in worker build (#12661) (20b8ef4), closes #12661
fix(worker): worker import.meta.url should not depends on document in iife mode (#12629) (65f5ed2), closes #12629
fix: avoid temporal optimize deps dirs (#12582) (ff92f2f), closes #12582
fix: await buildStart before server start (#12647) (871d353), closes #12647
fix: call buildStart only once when using next port (#12624) (e10c6bd), closes #12624
fix: sourcemapIgnoreList for optimizedDeps (#12633) (c1d3fc9), closes #12633
fix: splitFileAndPostfix works as cleanUrl (#12572) (276725f), closes #12572
fix: throw error on build optimizeDeps issue (#12560) (02a46d7), closes #12560
fix: use nearest pkg to resolved for moduleSideEffects (#12628) (1dfecc8), closes #12628
fix(css): use charset: 'utf8' by default for css (#12565) (c20a064), closes #12565
fix(html): dont pretransform public scripts (#12650) (4f0af3f), closes #12650
fix: avoid crash because of no access permission (#12552) (eea1682), closes #12552
fix: esbuild complains with extra fields (#12516) (7be0ba5), closes #12516
fix: escape replacements in clientInjections (#12486) (3765067), closes #12486
fix: open browser reuse logic (#12535) (04d14af), closes #12535
fix: prevent error on not set location href (#12494) (2fb8527), closes #12494
fix: simplify prettyUrl (#12488) (ebe5aa5), closes #12488
fix(config): add random number to temp transpiled file (#12150) (2b2ba61), closes #12150
fix(deps): update all non-major dependencies (#12389) (3e60b77), closes #12389
fix(html): public asset urls always being treated as paths (fix #11857) (#11870) (46d1352), closes #11857 #11870
fix(ssr): hoist import statements to the top (#12274) (33baff5), closes #12274
fix(ssr): hoist re-exports with imports (#12530) (45549e4), closes #12530
fix: should generate Hi-res sourcemap for dev (#12501) (1502617), closes #12501

Clean up

refactor: simplify crawlEndFinder (#12868) (31f8b51), closes #12868
refactor: use simpler resolve for nested optimized deps (#12770) (d202588), closes #12770
refactor: import.meta.url condition from renderChunk hook of worker plugin (#12696) (fdef8fd), closes #12696
refactor: clean up preTransformRequest (#12672) (561227c), closes #12672
refactor: make debugger nullable (#12687) (89e4977), closes #12687
refactor: remove ensureVolumeInPath (#12690) (a3150ee), closes #12690
refactor: remove unused exports data props (#12740) (4538bfe), closes #12740
refactor: use resolvePackageData in requireResolveFromRootWithFallback (#12712) (1ea38e2), closes #12712
refactor(css): simplify cached import code (#12730) (0646754), closes #12730
refactor: improve scanner logs (#12578) (9925a72), closes #12578
refactor: isInNodeModules util (#12588) (fb3245a), closes #12588
refactor: remove idToPkgMap (#12564) (a326ec8), closes #12564
refactor: simplify lookupFile (#12585) (4215e22), closes #12585
refactor: tryStatSync as util (#12575) (92601db), closes #12575
refactor: use findNearestPackageData in more places (#12577) (35faae9), closes #12577
refactor: esbuild plugin config logic (#12493) (45b5b0f), closes #12493

Previous Changelogs
4.3.0-beta.8 (2023-04-19)
See 4.3.0-beta.8 changelog
4.3.0-beta.7 (2023-04-17)
See 4.3.0-beta.7 changelog
4.3.0-beta.6 (2023-04-14)
See 4.3.0-beta.6 changelog
4.3.0-beta.5 (2023-04-11)
See 4.3.0-beta.5 changelog
4.3.0-beta.4 (2023-04-09)
See 4.3.0-beta.4 changelog
4.3.0-beta.3 (2023-04-07)
See 4.3.0-beta.3 changelog
4.3.0-beta.2 (2023-04-05)
See 4.3.0-beta.2 changelog
4.3.0-beta.1 (2023-03-29)
See 4.3.0-beta.1 changelog
4.3.0-beta.0 (2023-03-23)
See 4.3.0-beta.0 changelog
v4.2.2
Compare Source

fix: escape msg in render restricted error html, backport #12889 (8758c5c), closes #12889

v4.2.1
Compare Source

fix: add virtual: to virtual module source map ignore (#12444) (c4aa28f), closes #12444
fix(css): inject source content conditionally (#12449) (3e665f6), closes #12449
fix(worker): using data URLs for inline shared worker (#12014) (79a5007), closes #12014
chore: changelog edits for 4.2 (#12438) (ce047e3), closes #12438

v4.2.0
Compare Source
Vite 4.2 is out!
Support env variables replacement in HTML files
Vite now supports replacing env variables in HTML files. Any properties in import.meta.env can be used in HTML files with a special %ENV_NAME% syntax:

Vite is running in %MODE%

Using data from %VITE_API_URL%

Sourcemaps improvements
The Chrome Dev Tools team has been working to improve the DX of Vite and Vite-powered frameworks in the dev tools. Vite 4.2 brings an improved experience and tools for framework authors to hide 3rd party code and build artifacts from the user from console log traces using server.sourcemapIgnoreList and build.rollupOptions.output.sourcemapIgnoreList.
ESM subpath imports
Vite 4.2 now supports subpath imports, thanks to @lukeed05's resolve.exports library.
TypeScript 5 support
Vite 4.2 also supports TypeScript 5's tsconfig extends array format, thanks to tsconfck.
esbuild 0.17
esbuild v0.17.0 improved the design of its incremental, watch, and serve APIs. Check out #11908 for the rationale of why we didn't consider the backward-incompatible changes breaking for our use cases. The updated esbuild design now allows Vite to properly cancel in-fly builds and improve server restarts.
Use Rollup types from the vite package
Expose Rollup types as a namespace. This is helpful to avoid type conflicts because of different versions of Rollup types in environments like vite-ecosystem-ci (#12316).
import type { Rollup } from 'vite'

Português Docs Translation
The Vite documentation is now translated to Português at pt.vitejs.dev thanks to Nazaré Da Piedade .
Features

feat: add status message for 504 caused by optimizer (#12435) (5cdd3fa), closes #12435
feat: update tsconfck to 2.1.0 to add support for typescript 5 config syntax (#12401) (3f1c379), closes #12401
feat: default esbuild jsxDev based on config.isProduction (#12386) (f24c2b0), closes #12386
feat(css): add build.cssMinify (#12207) (90431f2), closes #12207
feat(types): export Rollup namespace (#12316) (6e49e52), closes #12316
feat: add sourcemapIgnoreList configuration option (#12174) (f875580), closes #12174
feat: cancellable scan during optimization (#12225) (1e1cd3b), closes #12225
feat: don't override build.target if terser is 5.16.0+ (#12197) (9885f6f), closes #12197
feat: support ESM subpath imports (#7770) (cc92da9), closes #7770
feat(css): add preprocessor option to define stylus vars & funcs (#7227) (5968bec), closes #7227
feat(css): support resolving stylesheets from exports map (#7817) (108aadf), closes #7817
feat(html): support env replacement (#12202) (4f2c49f), closes #12202
refactor: customize ErrorOverlay (part 2) (#11830) (4159e6f), closes #11830
refactor: remove constructed sheet type style injection (#11818) (1a6a0c2), closes #11818
refactor(importAnalysis): cache injected env string (#12154) (2aad552), closes #12154
feat: esbuild 0.17 (#11908) (9d42f06), closes #11908
feat: ignore list client injected sources (#12170) (8a98aef), closes #12170
feat: support rollup plugin this.load in plugin container context (#11469) (abfa804), closes #11469
feat(cli): allow to specify sourcemap mode via --sourcemap build's option (#11505) (ee3b90a), closes #11505
feat(reporter): report built time (#12100) (f2ad222), closes #12100

Bug Fixes

fix: html env replacement plugin position (#12404) (96f36a9), closes #12404
fix(optimizer): # symbol in deps id stripped by browser (#12415) (e23f690), closes #12415
fix(resolve): rebase sub imports relative path (#12373) (fe1d61a), closes #12373
fix(server): should close server after create new server (#12379) (d23605d), closes #12379
fix(resolve): remove deep import syntax handling (#12381) (42e0d6a), closes #12381
fix: print urls when dns order change (#12261) (e57cacf), closes #12261
fix: throw s

Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: frontend/package-lock.json
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated @aws-amplify/ui@2.0.7: Versions '1.x' and '2.x' of '@aws-amplify/ui' have been deprecated. Please visit https://ui.docs.amplify.aws/ for the current version of Amplify UI.
npm WARN deprecated @aws-amplify/xr@3.0.64: The Amazon Sumerian service is no longer accepting new customers. Existing customer scenes will not be available after February 21, 2023. The AWS Amplify XR features depend on the Amazon Sumerian service to function and as a result, will no longer be available.
npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm ERR! code 127
npm ERR! path /tmp/renovate/repos/github/bcgov/nr-forests-access-management/client-code-gen/gen
npm ERR! command failed
npm ERR! command sh -c -- npm run build
npm ERR! > typescript-axios@1.0.0 build
npm ERR! > tsc && tsc -p tsconfig.esm.json
npm ERR! sh: 1: tsc: not found

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2023-05-16T06_47_32_570Z-debug-0.log

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

repo: bcgov/nr-forests-access-management