Intermitent failure when executing kapp deploy command

What steps did you take:
Occasionally, executing kapp deploy command fails with the following error
What happened:
      if [ "$(kubectl api-resources --api-group=kappctrl.k14s.io -o name | wc -l)" -eq 0 ] ; then \
      	kapp deploy \
      		--yes \
      		--app=kc \
      		--namespace=kube-system \
      		--file=https://github.com/vmware-tanzu/carvel-kapp-controller/releases/latest/download/release.yml ; \
      fi
      Target cluster 'https://<omitted>:<port>' (nodes: <omitted>, 3+)
        kapp: Error: error converting YAML to JSON: yaml: line 8: mapping values are not allowed in this context

Kapp version: kapp version 0.47.0

@abubakarm94 Thank you for creating the issue.
kapp: Error: error converting YAML to JSON: yaml suggests that something is wrong in the yaml provided to kapp, but I don't see any issue with the kapp-controller release.yml. Does the error happen while using https://github.com/vmware-tanzu/carvel-kapp-controller/releases/latest/download/release.yml or with a modified version of the yaml?

Hi @praveenrewar, It happens when using https://github.com/vmware-tanzu/carvel-kapp-controller/releases/latest/download/release.yml

Hi @praveenrewar, happy to help. here are my responses to your questions:

It happens randomly, I've not observed that it happens under certain conditions.
It does get resolved if I continue to re-run the command, it takes up to 3-4 tries on occasion.
We have a test on our CI that attempts to install a particular application via Kapp.  And if Kapp is already installed on the test cluster, it doesn't make sense to reinstall it, hence the need for the IF condition.

Feel free to let me know if you have any other questions.

Not silly questions at all.

The error doesn't occur frequently, it's possible to go weeks without seeing it. However, on the days it occurs, it happens multiple times.
And yes, the error is always the same.

I'll update our script to download the file and use it the next time it happens. Thanks for the suggestion.

i bet this would correlate to github having occasional spike of errors/outages for downloading assets. looking at the code seems like we are missing status 2xx check: https://github.com/vmware-tanzu/carvel-kapp/blob/e0bf1c9d485c5c59a23b4cfe75915782e7fb4b42/pkg/kapp/resources/file_sources.go#L58-L72. /cc @jtigger same in ytt.

i bet this would correlate to github having occasional spike of errors/outages for downloading assets

I did think of something similar, but couldn't find any issue related to this anywhere, but this is the only reason that makes sense.

Adding reproduction steps for something similar:
$ kapp deploy -a test -f https://github.com/fake/path/
Target cluster 'https://<IP_ADDRESS>:8443' (nodes: minikube)

kapp: Error: error converting YAML to JSON: yaml: line 163: mapping values are not allowed in this context

Expected error should be something like this:
$ /kapp deploy -a test -f https://github.com/fake/path/
Target cluster 'https://<IP_ADDRESS>:8443' (nodes: minikube)

kapp: Error: Requesting URL 'https://github.com/fake/path/': 404 Not Found

Fix available in v0.49.0


update docs for recent changes

rm terraform
multiregion
ssh command

Docs PR Template
update doc for the current state of cli

How this works

How these changes were tested

To prevent any errors while building

[] run vale /docs/file/path on all changed .md files to ensure all grammar rules pass
[] run markdownlint /docs/file/path on all changed .md files to ensure all linting rules pass
[] complete the above two checks and all additional rules outlined in style-checker-notes.md to
ensure all checks pass

If a document was removed/deleted

[] the path to that doc must be redirected to a valid URL via the
_redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

If a document was moved

[] all files that were moved from their current directory to a new path have had their paths
redirected via the _redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

hey @arturrez, it'd be really helpful if you could resolve the comments made by @sukantoraymond in the above PR

@arturrez Hi, this is a kind reminder to please fix the linting issues.

@laviniat1996 please approve now


⚠ Minecraft has degraded performance

In 5925ee2, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 889 ms

Resolved: Minecraft performance has improved in d7eba18.


Implicit process variables have names appended with query character

Referencing my Forum post: https://forum.camunda.org/t/what-is-issue-36-introduce-optional-variables-in-the-camunda-camel-extension/11453
If the process calls the camel service bean with no explicit variables, in the past, all the process variables were put into the Camel exchange as name-value pairs in a Map in the Body. We use this capability to decouple our Camel routes from our Camunda processes. The routes can pick whichever variables they want to use from the set of all process variables in the process execution, instead of being told what they can have by the call to the Camel service bean from that process.
There is a commit; https://github.com/camunda/camunda-bpm-camel/commit/87322c859fc581b43b1ceaabc618c5abe70203b6 which is part of pull request 37 (https://github.com/camunda/camunda-bpm-camel/pull/37), which is titled ’ Issue 36: Introduce optional variables’. This change seems to be a breaking change to the Camel service bean, which has changed all the names of the process variables being implicitly fetched from the process execution by appending '?'. What is the intent of this? AFAIK, this should be a defect, since the documentation doesn't tell me why I should rename all the process variables that we use in all our Camel routes to have a '?' on the end, so that I can upgrade to version 0.6.
Sadly, I also need to do the upgrade because 0.5 seems to be responsible for the asyncResponseTimeout in the REST ExternalTask API 'fetchAndLock' not working properly. See my earlier forum post https://forum.camunda.org/t/fetchandlock-using-asyncresponsetimeout-returns-empty-body/9511

The commit https://github.com/camunda/camunda-bpm-camel/commit/87322c859fc581b43b1ceaabc618c5abe70203b6 did not change the behavior you describe:
Still, if there are no variables declared in the routes, all process variables will be exposed. Previously, if there was a null-valued variable, you got an exception but now you get a map entry with a null value. This change is also documented.
If you declare variables in the route the question marks may be placed but don't need to. Without them it behaves like before: you get an exception for variables with null values. Placing the question mark only skips this null check.
But yes, there seems to be a bug that all variable names are exposed including the question marks. I have to test this and I will send an update for this.
But upgrading to a newer Camunda version should be possible without upgrading the Camunda camel plugin. I don't see any dependency because the plugin does not use the rest API.

Thanks @stephanpelikan for looking into it! If anybody could provide a PR I am more than happy to merge it - and then we could also release a fix version

Probably this line?
https://github.com/camunda/camunda-bpm-camel/commit/87322c859fc581b43b1ceaabc618c5abe70203b6#diff-c2b0f268eee6f094e1054fe109f4dd7bR55

The problem seems to be that the code has changed between version 0.5 and 0.6 to append a '?' to the variable name in the list, if the list is pulled from the execution, rather than explicitly named. When the value of the variable is fetched, the code recognizes if the name ends in a '?' and fetches by the name without that character, but when the name/value pair is added to the list to send, the name used is the one that includes the '?'. Unfortunately, I don't know what the requirement is that caused the code to change, so I can only fix it by removing all the '?' usage and effectively put the code back to how it was in 0.5.
I'm happy to do that and provide a PR, but I think I'm not seeing the whole picture.
@berndruecker WDYT?

@nickthearchitect:
You changed a lot of whitespace. May you use a different code formatter than defined at https://github.com/camunda/camunda-bpm-platform/blob/master/CONTRIBUTING.md.
I adopted your commit by removing those changes and also tried to make it a litte bit more readable. I hope you agree with this.

@stephanpelikan
I agree. Thank you so much for interpreting my code change into a useful form.
What would be the next steps for this? Will you create a PR?

as far as I can see the changes are committed to master. Can you confirm that this issue is fixed by them? Then I could release a new version with that change.

@berndruecker
Sorry, I don't see the commit in master. AFAIK it is only in stephanpelikan/camunda-bpm-camel

Yes, I have to do a pull request. I wanted to test it before. Sorry for the delay, there are a lot of things to do at the moment. I try to make it this week.


Add support for Python 3.5.

This is a bit tongue-in-cheek.
But don't you want to be supporting python 3?

I quite like the idea of supporting python 3.5, would you suggest using six or something like that, or would you roll your own compat thing?

I used six, but I haven't done this on a large project.
You don't seem to have many requirements; they should all support python 3 (even cothread, but you can't use that on Travis, I find).

You may need to update landscape for python 3 checks:
https://docs.landscape.io/configuration.html#python-targets-2-3

Changes integrated in #51


Integration test Tab Edit test scenarios.

Fixes

Integration test Tab Edit test scenarios.
https://issues.redhat.com/browse/HACBS-1462
Description

Reach the "Edit integration test" page by:

Go to an IT's Details page and click on the "Edit integration test" option under the "Actions" dropdown.
Go to IT list view, and click on the "Edit" option under IT's kebab menu.

Then test the Edit form by making sure that:

Integration test name input is marked as read-only and cannot be edited.
Save changes button only gets enabled if the edit form has new changes.
update the pipelineName and Mark Optional For Release
Verify that the latest changes are reflected on the IT list and detail view.

Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[x] Other (please describe): Test Case

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/retest

/retest

@subhashkhileri We don't have the integration test tab or the action item in the UI anymore. How are you testing it?

@rohitkrai03 I have tested with MVP_FLAG false in my local, and these tests are skipped so will not run in PR check.


Trim the tenantDomain and return it in-order to avoid the space in the tenantDomain

User core retrieves the tenant domain from the database, where we need to trim the tenantDomain and return it in order to avoid unwanted spaces in the tenatDomain.

Root cause of this issue is described in https://github.com/wso2/product-is/issues/12508


Running generate crashes dev server

Environment
From StackBlitz reproduction:

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.12.2
CLI Version:      3.12.0
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-53r4wj?file=package.json
Start a new project and run npm install && npm run dev. Start a new terminal and run npm run generate, reload the browser.
Describe the bug
I get an 500 error:
Package import specifier "#internal/nuxt/paths" is not defined in package /home/projects/nuxt-starter-53r4wj/package.json imported from /home/projects/nuxt-starter-53r4wj/.nuxt/dist/server/server.mjs

Additional context
You can see output on the dev server while the generate is running.
On my system, I get [500] Package import specifier "#internal/nitro" is not defined
Since the behaviour is totally unexpected and the error message might change based on the project, I believe this can be the root cause of other unsolved issues like https://github.com/nuxt/nuxt/issues/26731
Logs
No response

Tried to reproduce on StackBlitz however I do not get any error ...

Yes, that's the current behavior (you can't run dev & build at the same time). This is meant to be changed in the future though
Let's track in https://github.com/nuxt/nuxt/issues/14607


Potentially have mypy use --install-types

Example downstream error:
datazen/paths.py:12: error: Library stubs not installed for "pkg_resources" (or incompatible with Python 3.7)
datazen/paths.py:12: note: Hint: "python3 -m pip install types-pkg_resources"
datazen/paths.py:12: note: (or run "mypy --install-types" to install all missing stub packages)
datazen/paths.py:12: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports
tests/resources.py:11: error: Library stubs not installed for "pkg_resources" (or incompatible with Python 3.7)

fixed here: https://github.com/vkottler/vmklib/commit/5795cd30fd32a8ad89b6bd7ec231b8619b5ec651
now we have python-sa-types


fix: modal icon - table full width

When modal has header icon, the table has not the full modal width
Before:
MaxWidth::ExtraSmall

MaxWidth::Medium

MaxWidth::Full

After:
MaxWidth::ExtraSmall

MaxWidth::Small

MaxWidth::Medium

MaxWidth::Full

MaxWidth::Screen

Hi! Thanks for the PR! Any reason why it's 5.2rem instead of the 5.25rem that filament applies by default when there is a modal icon?

merged :) thanks!


Comment not relevant error when scanning specific folders

Hi,
I have a PR open here: https://github.com/ministryofjustice/opg-lpa/pull/541/
which has an action with multiple tfsec scans on different specific folders. the action is based on the example in the readme, but with a matrix for the terraform_path.
On a violation I am seeing errors similar to the following.
Comment not written [Resource aws_s3_bucket.mailbox has no associated aws_s3_bucket_public_access_block.], not part of the current PR

The commit to remove the ignore is also in this PR branch. can you advise why this might be happening?
Please see example here in a run:
https://github.com/ministryofjustice/opg-lpa/pull/541/checks?check_run_id=3056251557#step:4:13
Any advice will be greatly appreciated.

Hey @williamfalconeruk  - this is an odd one. The error is informational, it's telling you that you don't have logging on the bucket yes, but it is dropping it on the floor because this PR isn't to blame for it.
The odd bit is that it is even raising an AWS002 when the ignore is in place.
Let me take a proper look and come back to you.

I was completely misreading this - the ignores are being removed not added :facepalm:
The pr-commenter is not as sophisticated as you maybe hope, it can't recognise that the resource block is now failing and should be stopped - it can only tell you issues with lines that are specifically changed in the PR.
One option you have, with this being a public repo, is to use the tfsec-sarif-action which will report all issues across the branch of the PR and put them in the security scan block https://github.com/ministryofjustice/opg-lpa/security. As they do different tasks, I think both together would work around this.
In the meantime, I'll look at if we can make it more intelligent under #14

Owen,
Thanks for taking a look at this, really appreciated!
I'll add the tfsec-sarif-action for now, keep me posted on any developments
on the commenter.
William Falconer
On Sat, 17 Jul 2021 at 09:11, Owen Rumney @.***> wrote:

I was completely misreading this - the ignores are being removed not added
🤦
The pr-commenter is not as sophisticated as you maybe hope, it can't
recognise that the resource block is now failing and should be stopped - it
can only tell you issues with lines that are specifically changed in the PR.
One option you have, with this being a public repo, is to use the
tfsec-sarif-action https://github.com/aquasecurity/tfsec-sarif-action
which will report all issues across the branch of the PR and put them in
the security scan block
https://github.com/ministryofjustice/opg-lpa/security. As they do
different tasks, I think both together would work around this.
In the meantime, I'll look at if we can make it more intelligent under #14
https://github.com/aquasecurity/tfsec-pr-commenter-action/issues/14
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/tfsec-pr-commenter-action/issues/13#issuecomment-881854796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDV6MXRJFHWDNI7ITMNFD3TYE3KVANCNFSM5AI5J4OA
.

I too have run into this issue.  I don't get the issue though with this tfsec action though so I'm continuing to use it (in private repos) until this gets sorted.

I am having this issue as well. I've followed what @heathsnow mentioned, but I'd really like to be able to use the comment functionality that this action offers.

Update on the above - I switched to https://github.com/reviewdog/action-tfsec and commenting works great.

Hi,
I'm still running to these issues with violation errors & no comments even on the same PR.  Any updates would be great, as I'm hoping to use aquasecurity official repos.
Thanks in advance.

Is there any update on this issue ?


Add example of TodoMVC

React
Redux (domain concept layout)
Typescript
Real Acceptance Testing
Real Integration Testing

sorry for the delay - accepted!


ADC-S2000-T-RA Temperature Sensor

The alarmdotcom maintainers don't have direct access to all Alarm.com devices. We need your help to support new devices.
Please open one issue per device.
Which device would you like us to support?
Provide the device name and a link to a page with device details.
Alarm.com Temperature Sensor - https://www.geoarm.com/adc-s2000-t-rb-alarm-dot-com-temperature-sensor.html
Where does this device appear in the Alarm.com mobile app?
Thermostat --> Temperature Sensors
What types of actions does this device support?
Displays temperature readings, when assigned to a thermostat the readings are averaged to reduce hot/cold spots.
Which provider do you use?
Integrated Alarms
Include pyalarmdotcomajax Server Output
This is an important step. It's helpful for us to see how this device is represented on the Alarm.com server. We have a tool for dumping this data via the command line.

Install Python >= 3.9.
Install pyalarmdotcomajax via pip: pip install pyalarmdotcomajax.
Run adc -u YOUR_USERNAME -p YOUR_PASSWORD -c YOUR_2FA_COOKIE -vx
The above command dumps server data for all devices that are known to ADC developers, including a few devices that are currently unsupported. Heads Up! This command may leak sensitive information. It does not dump your email address, address, or any other account information, but it may output coordinates from GPS devices (like an Alarm.com car sensor) and names of family members (e.g.: Michael's Room Window Sensor). Be sure to review the data before posting to scrub anything that you're not comfortable posting online.

 Can you run adc -v -u YOUR_USERNAME -p YOUR_PASSWORD -c YOUR_2FA_COOKIE get -x to see whether the temperature sensors show up as their own devices under the ====[ Remote Temp ]==== category? If they do, can you post that data here?

Closing as stale. @rsaSean027, please reopen if you're able to follow up on the last question.


View Loaded Commands from the CodeFactory Runtime

Need a better way to see the loaded code factory commands other then in the output window for code factory.
Please give us a UI screen in visual studio that is easy to find so we can see which commands are in use.

Should begin design analysis for runtime updates later this week.

Have added to the 1.0.20230.1 build of the runtime


Incorrect URL encoding of /

When I enter something like !github alii/search, it redirects to https://github.com/alii%2Fsearch instead of https://github.com/alii/search, which leads to a 404-page.
This might be related to 0f6404d, because it used to work just fine before.
(In case that matters, I'm using Firefox, haven't tried it in Chromium-based browsers.)

The same thing happens on Chromium-based browsers.


syncer: support start from empty gtid config

What problem does this PR solve?

Issue Number: close #3731
What is changed and how it works?
mariadb could use 0-0-0 as empty gtid config

support user to use uuid:0 as mysql empty gtid config

Check List
Tests

Integration test
Manual test (mariadb)

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update key monitor metrics in both TiCDC document and official document

Release note
Support start an incremental task with nil MySQL GTID set.

/run-dm-integration-test

Codecov Report

Merging #5340 (044a3e3) into master (687e248) will decrease coverage by 0.0104%.
The diff coverage is 54.3836%.

Flag
Coverage Δ

cdc
60.9708% <54.3836%> (+0.3721%)
:arrow_up:

dm
52.2691% <ø> (-0.2005%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #5340        +/-   ##
================================================
- Coverage   56.1240%   56.1135%   -0.0105%
================================================
  Files           522        526         +4
  Lines         65325      69199      +3874
================================================
+ Hits          36663      38830      +2167
- Misses        25094      26657      +1563
- Partials       3568       3712       +144

/run-all-tests

/merge


i18n(fr): Adding install/manual.md translation

What kind of changes does this PR include?

[x] New or updated content
[x] Translated content

Description

What does this PR change? Adds /fr/install/manual.md to the french translation.

It's normal if the Check link is failing, it's referencing #675 which is not merge at the moment

By the way, I just noticed that your branch still uses an old version of the link checker. If you want to use the latest version, you need to go to your fork's main branch on GitHub and click on "Fetch upstream" -> "Fetch and merge", and then navigate to your open branch(es) and repeat the same step. Then they will use the latest version.

I know, my main branch is completely full of merge conflicts and i ended up by ignoring changes and just use the main branch as a save for my old translation and the reworked ones


The RFI app is installed in /opt/venvs/irfi

This is something to be aware of, when writing the playbook.
It's because the package itself is called irfi, and dh-virtualenv works this way.

checked and done with : https://github.com/ideascube/ansiblecube/blob/oneUpdateFile/roles/ideascube/tasks/ideascube.yml#L5


macOS application getting  "Cannot send mail on this platform" error.

Below code we used.
func installCrash() {

        // add crash report
        let installation = self.crashReportEmail()
        installation.install()
        KSCrash.sharedInstance()?.deleteBehaviorAfterSendAll = KSCDeleteNever
        installation.sendAllReports { (reports, completed, error) in
         if completed {
              print("Sent reports: \(String(describing: reports))")
            } else {
                 print("Failed to send report: \(String(describing: error?.localizedDescription))")
            }
        }
    }

func crashReportEmail() -> KSCrashInstallation {

        // email instance creation.
        let email = KSCrashInstallationEmail.sharedInstance()
        email?.recipients =<EMAIL_ADDRESS>        email?.subject = "Crash Report"
        email?.message = "This is a crash report"
        email?.filenameFmt = "crash-report-%d.txt.gz";
        email?.addConditionalAlert(withTitle: "Crash Dectected",
                                      message: "The app crashed last time it was launched. Send a crash report?",
                                      yesAnswer: "Sure!",
                                      noAnswer: "No thanks")
        email?.setReportStyle(KSCrashEmailReportStyleApple, useDefaultFilenameFormat: true)
        return email!
     That is needed if the user has not configured Mail and is using another default mail app such as Outlook.

some problem

same problem


fix: updated deps

:tada: This PR is included in version 2.7.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Multiple routes with the same name, but different parameters

I would like to propose a new feature / enhancement for Vue Router which takes inspiration from other routing systems - such as that found in the Django framework.  Vue router already supports named routes, and that's very useful for keeping static URLs in a singular location, but what it doesn't support is having two routes with the same name, but with different parameters.
Here's a few examples of where this would be useful:
router.map({
  // List of exhibits.
  '/exhibits': {
    name: 'exhibits:listing',
    component: Exhibits,
  },

  // Exhibit detail page.
  '/exhibits/:exhibitSlug': {
    name: 'exhibits:detail',
    component: Exhibit,
  },

  // Exhibit within an exhibition.
  '/exhibition/:exhibitionSlug/:exhibitSlug': {
    name: 'exhibits:detail',
    component: Exhibit,
  },
})

router.map({
  '/news/': {
    name: 'news:listing',
    component: NewsListing
  },

  '/news/:year/:month/:day/': {
    name: 'news:listing',
    component: NewsListing
  },

  '/news/category/:categorySlug/': {
    name: 'news:listing',
    component: NewsListing
  },

  '/news/author/:authorSlug/': {
    name: 'news:listing',
    component: NewsListing
  },
})

I've tried to give examples where just having optional parameters isn't enough and where re-using the same name would actually be useful.  Primarily these situations would be ones in which you're using the same view / templates but with different contexts or filters.

Why do you want them have the same name? What is the benefit?
When you do router.go({ name: 'exhibits:detail' }) it becomes unclear, at which route you would end up.

It's not unclear at all, that particular route wouldn't exist (assuming all parameters are required).  In the first example, your code would look like this:
router.go({ name: 'exhibits:detail', params: { exhibitSlug: 'foo' } })
 -> /exhibits/foo/

router.go({ name: 'exhibits:detail', params: { exhibitionSlug: 'bar', exhibitSlug: 'foo' } })
 -> /exhibits/bar/foo/

The implementation changes should be straightforward too - router matches against a list of routes instead of a single route.

What is the benefit?

@danielsamuels - I'm curious too - have used django for several years but haven't taken advantage of this feature. Is there any other benefit to this aside from stylistic preferences?

In a recent case for a project I worked on (from which I took and tweaked for the exhibit example above) I had to have a router map which looked like this:
router.map({
  '/exhibits': {
    name: 'exhibits:listing',
    component: Exhibits,
  },
  '/exhibits/:exhibitSlug': {
    name: 'exhibits:detail',
    component: Exhibit,
  },
  '/exhibition/:exhibitionSlug/:exhibitSlug': {
    name: 'exhibitions:exhibit_detail',
    component: Exhibit,
  },
})

Having the proposed feature would have mean I could just use exhibits:detail for both names, and just pass in the exhibitionSlug if I want the Exhibit within the context of an Exhibition, or without if I just wanted it as a singular item.

@danielsamuels Why not:
router.map({
  '/exhibits': {
    name: 'exhibits:listing',
    component: Exhibits,
  },
  '/exhibits/:exhibitSlug': {
    name: 'exhibits:detail',
    component: Exhibit,
  },
  '/exhibition/:exhibitionSlug/:exhibitSlug': {
    name: 'exhibitions:exhibit_detail',
    component: Exhibit,
  },
})

In current version of vue router it's possible to achieve this behaviour with optional parameters.
names are intentionally unique and a part of the codebase is build around that

i wrote a utility function to resolve route by parameters name, to work you must define name and meta -> name for each route:
import Router from 'vue-router';
/**
 * Find route based on parameter count
 * @param {String} name
 * @param {Object} params
 */
Router.prototype.$resolve = function(name, params, replace = true){
	const route = getAllRoutes(this.options.routes);
	function getAllRoutes(routes){
		if(Array.isArray(routes)){
			for(let index in routes){
				let route = routes[index];
				if(route.children){
					const res = getAllRoutes(route.children);
					if(res){
						return res;
					}
				}else{
					if(route && route.name && route.meta && route.meta.name && route.meta.name == name){
						let unproceed = 0;
						if((route.path.match(/:/g) || []).length == Object.keys(params).length){
							for (const param in params) {
								if (params.hasOwnProperty(param)) {
									var rx = new RegExp(`(:${param}\\/)|(:${param}\\/?$)`,"g");
									if(!`${route.path}`.match(rx)){
										unproceed++;
									}
								}
							}
						}else{
							unproceed = 1;
						}

						if(unproceed == 0){
							return route.name;
						}
					}
				}
			}
		}
		return false;
	}

	if(!!route){
		if(replace){
			this.replace({name: route, params});
		}else{
			this.replace({name: route, params});
		}
		return true;
	}else{
		return false;
	}
}

sample route:
[
{
   name: 'route-a',
   path: '/:a',
   meta: {
      name: 'test-route'
   }
},
{
   name: 'route-b',
   path: '/:a/:b',
   meta: {
      name: 'test-route'
   }
}
]

usage in component:
this.$router.$resolve('test-route', { a: 1 }); // redirect to route-a
this.$router.$resolve('test-route', { a: 1, b: 2 }); // redirect to route-b
this.$router.$resolve('test-route', { a: 1, c: 3 }); // return false no route found


fix(core): empty .config.json file in project root gets picked up as lerna-lite config

Describe the bug
If I have an empty .config.json file in my project root then lerna-lite will crash because it assumes that the config file was for itself and not for something else (and it tries to parse it and then crash because the config property is undefined)
IMO, since lerna-lite is a tool that is commonly used as part of tooling of projects that have their own config files, the tool shouldn't assume that a generic name such as .config.json is a config file that is intended for itself (now that I think about it my app also shouldn't assume that TBH, but maybe it has a slightly stronger claim to "squat" on a generic name like this).
Expectation
TLDR: The default search path for config files should consist of files that have lerna or lerna-lite in their names, not the generic ones. This is just my opinion though, not a strongly held one either.
Or if you think that it's okay to assume .config.json belonging to lerna-lite, that's fine by me, but then it should at least validate the config and error out with something more obvious explaining that the config was missing certain (mandatory) properties from it.
Reproduction

cd some-lerna-project-root-dir
touch .config.json
yarn lerna run 'echo hello'

Which will then crash with:
TypeError: Cannot read properties of undefined (reading 'rootPath')
    at file:///home/peter/a/cacti/node_modules/@lerna-lite/core/dist/command.js:51:47

And if you add some more logging inside the error handler, you can log out this one in addition (same crash):

TypeError: Cannot use 'in' operator to search for 'extends' in undefined
    at applyExtends (file:///*****/node_modules/@lerna-lite/core/dist/project/lib/apply-extends.js:9:19)
    at Object.transform (file:///*****/node_modules/@lerna-lite/core/dist/project/project.js:47:34)
    at load (/*****/node_modules/cosmiconfig/dist/ExplorerSync.js:20:32)
    at emplace (/*****/node_modules/cosmiconfig/dist/util.js:12:20)
    at ExplorerSync.load (/*****/node_modules/cosmiconfig/dist/ExplorerSync.js:23:42)
    at ExplorerSync.search (/*****/node_modules/cosmiconfig/dist/ExplorerSync.js:30:33)
    at new Project (file:///*****/node_modules/@lerna-lite/core/dist/project/project.js:60:31)
    at file:///*****/node_modules/@lerna-lite/core/dist/command.js:30:54
file:///*****/node_modules/@lerna-lite/core/dist/command.js:51
                    writeLogFile(this.project.rootPath);
                                              ^

Lerna config and logs
lerna.json

{
  "packages": [
    "packages/cactus-*",
    "examples/cactus-*",
    "extensions/cactus-*",
    "packages/cacti-*",
    "examples/cacti-*",
    "extensions/cacti-*",
    "weaver/common/protos-js",
    "weaver/sdks/fabric/interoperation-node-sdk",
    "weaver/sdks/besu/node",
    "weaver/core/drivers/fabric-driver",
    "weaver/core/identity-management/iin-agent",
    "weaver/samples/fabric/fabric-cli",
    "weaver/samples/besu/besu-cli",
    "weaver/samples/besu/simpleasset",
    "weaver/samples/besu/simplestate"
  ],
  "version": "2.0.0-alpha.1",
  "npmClient": "yarn",
  "useWorkspaces": "true",
  "command": {
    "version": {
      "message": "chore(release): publish"
    }
  },
  "changelogPreset": "angular"
}

lerna-debug.log

Environment Info
System:
  OS: Linux 5.10 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
  CPU: (24) x64 12th Gen Intel(R) Core(TM) i7-12850HX
  Memory: 11.17 GB / 15.44 GB
  Container: Yes
  Shell: 5.1.16 - /bin/bash
Binaries:
  Node: 16.20.2 - ~/.nvm/versions/node/v16.20.2/bin/node
  Yarn: 3.6.0 - ~/.nvm/versions/node/v16.20.2/bin/yarn
  npm: 8.19.4 - ~/.nvm/versions/node/v16.20.2/bin/npm
npmPackages:
  @lerna-lite/cli: 2.5.1 => 2.5.1
  @lerna-lite/exec: 2.5.1 => 2.5.1
  @lerna-lite/list: 2.5.1 => 2.5.1
  @lerna-lite/publish: 2.5.1 => 2.5.1
  @lerna-lite/run: 2.5.1 => 2.5.1
  @lerna-lite/version: 2.5.1 => 2.5.1

Used Package Manager
yarn >= 2.x
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

I did not have a chance to try it out yet, but I know there was an update in cosmiconfig which extends TypeScript config in this PR on that project, I wouldn't be surprised that this caused your problem. Could you try an older version of Lerna-Lite v2.4.0 and see if that fixes your issue to avoid including this newer cosmiconfig version and let me know if that worked.

I did not have a chance to try it out yet, but I know there was an update in cosmiconfig which extends TypeScript config in this PR on that project, I wouldn't be surprised that this caused your problem. Could you try an older version of Lerna-Lite v2.4.0 and see if that fixes your issue to avoid including this newer cosmiconfig version and let me know if that worked.
EDIT
I think I found pretty much the same error you got in this upstream cosmiconfig issue Config search fails if there is a file named .config, it says the bug was fixed in cosmiconfig v8.3.6 but Lerna-Lite v2.5.1 is referencing cosmiconfig v8.3.5 which is probably why it included similar bug. I will test it out in the next couple days and probably release a new version including this cosmiconfig fix

@ghiscoding Thank you so much for investigating! Looking forward to the fix! If there's anything else I can help with, just let me know!

you can maybe verify the cosmiconfig fix by using yarn override resolutions to bump cosmiconfig to v8.3.6

you can maybe verify the cosmiconfig fix by using yarn override resolutions to bump cosmiconfig to v8.3.6

@ghiscoding No luck unfortunately. It fails the exact same way with the same repro steps.
I double checked on the file-system that it is importing v8.3.6 and no other version of cosmiconfig is installed dangling either, so I'm 100% that v8.3.6 is still broken. :-(

I have opened an issue Lerna-Lite project having an empty .config.json file gets picked up by cosmiconfig and is unexpected - behavior changed after 8.0 in the upstream repo. Waiting for a reply and potential fix, typically resolved within few days or couple weeks, we'll wait and see
A potential alternative might be to use yarn resolutions to use a lower version of cosmiconfig (8.0), "cosmiconfig": "8.0.0" seems to be the last known working version, that is after trying it in Lerna-Lite with a breakpoint.

this should be fixed in v3.1.0, cheers


Update asr_engine.py

PR types

PR changes

@lesliexufdu Thank you for your valuable comments. We have modified the code of ASR engine. You can use   conf/application.yaml to set  "num_decoding_left_chunks". For details, please see this PR.


Use Traefik for non-Docker/Kubernetes websites

Is it possible to use Traefik to reverse proxy a website made traditionally on a linux sever or an admin site from a purchased NAS.  Specifically I have a QNAP NAS and would like to access this from a Traefik server, running on Docker if possible.  This NAS is running Apache as far as I can research.  Thank you,  Bill

Hey @bvalvik thanks for requesting! I'll it to the boilerplates as soon as I can

Thank you Christian and MrSnakeDoc.  I have tried both options and unfortunately neither are working properly.  In both cases I am getting a 404.
I added this code to my config.yml file listed under traefik directory.
Taking Christians template I have this for my config.yml:
http:
routers:
http:
#region routers
routers:
qnap:
entryPoints:
- "https"
rule: "Host(qnap.local.mydomain.com)"
middlewares:
- default-headers
- https-redirectscheme
tls: {}
service: qnap
#endregion
#region services
services:
qnap:
loadBalancer:
servers:
- url: "http://<IP_ADDRESS>:8080/cgi-bin/"
passHostHeader: true
I am not sure I correctly applied what I was supposed to.  Let me know this need altering.

More on the error.  I go this from traefik"
RULE
Host(http://<IP_ADDRESS>:8080/cgi-bin/)
NAME
vaultdata_http@file
ENTRYPOINTS
http
SERVICE
ERRORS
the service "nas-service@file" does not exist

I have success.  I owe this update to TechnoTim.  Here is the config.yml that is working for me with my qnap NAS and pihole as well.
http:
#region routers
routers:
qnap:
entryPoints:
- "https"
rule: "Host(qnap.local.valvik.us)"
middlewares:
- default-headers
- https-redirectscheme
tls: {}
service: qnap
pihole:
entryPoints:
- "https"
rule: "Host(pihole.local.valvik.us)"
middlewares:
- redirectregex-pihole
- default-headers
- addprefix-pihole
- https-redirectscheme
tls: {}
service: pihole
#endregion
#region services
services:
qnap:
loadBalancer:
servers:
- url: "http://<IP_ADDRESS>:8080/cgi-bin/"
passHostHeader: true
pihole:
loadBalancer:
servers:
- url: "http://<IP_ADDRESS>:80"
passHostHeader: true
#endregion
middlewares:
addprefix-pihole:
addPrefix:
prefix: "/admin"
https-redirectscheme:
redirectScheme:
scheme: https
permanent: true
redirectregex-pihole:
redirectRegex:
regex: "/admin/(.*)"
replacement: /
default-headers:
  headers:
    frameDeny: true
    browserXssFilter: true
    contentTypeNosniff: true
    forceSTSHeader: true
    stsIncludeSubdomains: true
    stsPreload: true
    stsSeconds: 15552000
    customFrameOptionsValue: SAMEORIGIN
    customRequestHeaders:
      X-Forwarded-Proto: https

I hope this helps.

Take a look and let me know any comments.  I am good now.  For me we can close this.
Thank you both and TechnoTim in helping me figue this out.


Azure CLI 2.0 slow startup/warmup, command overhead

Description
It takes seconds for any command to complete, the first time you run Azure CLI it's really really slow to get going. It's especially annoying that even the built-in help takes more than a couple of seconds to display.

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
MSI
CLI Version: What version of the CLI and modules are installed? (Use az --version)
azure-cli (2.0.16)
acr (2.0.11)
acs (2.0.14)
appservice (0.1.15)
batch (3.1.2)
billing (0.1.4)
cdn (0.0.7)
cloud (2.0.7)
cognitiveservices (0.1.7)
command-modules-nspkg (2.0.1)
component (2.0.7)
configure (2.0.10)
consumption (0.1.4)
container (0.1.9)
core (2.0.15)
cosmosdb (0.1.12)
dla (0.0.11)
dls (0.0.13)
eventgrid (0.1.3)
feedback (2.0.6)
find (0.2.6)
interactive (0.3.9)
iot (0.1.11)
keyvault (2.0.9)
lab (0.0.10)
monitor (0.0.9)
network (2.0.13)
nspkg (3.0.1)
profile (2.0.11)
rdbms (0.0.6)
redis (0.2.8)
resource (2.0.13)
role (2.0.11)
servicefabric (0.0.3)
sf (1.0.8)
sql (2.0.10)
storage (2.0.14)
vm (2.0.13)
Python (Windows) 3.6.1 (v3.6.1:69c0db5, Mar 21 2017, 17:54:52) [MSC v.1900 32 bit (Intel)]
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
OS Version: What OS and version are you using?
Windows 10 Pro 64-bit
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
cmd.exe

On Windows, the python may be impacted by the Windows Defender for the startup. You can verify if it is indeed the root cause by adding python.exe to your Windows Defender (or other AV) whitelist.
However, we do NOT recommend this as a solution. It is important to keep your environment secured.

Okay, so I did some digging, here's what I found.
Real-time system protection had basically no impact, we're talking sub 100 ms if any.
Then I used to procmon to try and figure out what it was that was taking time. There's a lot of file scanning going on in the C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\Lib directory.
I noticed the occasional ACCESS DENIED error when it was trying to write back a precompiled python script and given that it's installed under Program Files that's normal.
I then ran in an elevated command prompt and the performance doubled.
I then tried running in a normal command prompt and the performance was the same. So there's a 2x perf hit right there because you are not running as an admin all the time!?
But even with a 2x perf gain it's IMAO too slow. About 1.5 seconds for each run, even if it's not doing anything.
I'm assuming you can trace this back to all the file scanning that is still happening. I think you need to have an index file so that you don't have to resort to full file scanning every time you run a command. You've made the most common case progressively slower as more commands are added to the CLI tools.
You can see my measurements in the Google spreadsheet I linked below.
https://docs.google.com/spreadsheets/d/1K-gdsBQ9fKKwYuzz39Kvc7INzY_RWsIJdF6o3hQE6M0/edit?usp=sharing

Okay, so I went back and checked two more things.
If you run

az configure

and say yes, you get to answer a few questions, I chose to disable logging and telemetry.
That's another 2x perf
Is there any reason logging and telemetry cannot be async?

Thank you for the measuring. And I assume you're running az for all your testing. Can you try running az cloud list on your machine and measure the time?

Telemetry is async. After the command process is stopped, a new process is started to uploading telemetry in the background (which runs telemetry_upload.py). It is not expected to impact the perceiving of the command performance.
Can you turn on the logging but keep telemetry off to test the logging's impact?

So, yes. Here's the deal. When you run az we collect all the modules to print the full sub-commands list, therefore it reads more files. When you run a subcommand directly, for example az cloud, we can pinpoint to the individual command module and reduce the number of imported modules.
The az cloud list command performance here is in line with our tests. Do you think it is an acceptable performance?

timings with logging enabled
az

0.7710953
0.7403197
0.7441196
0.7853553
0.7542274
0.7374869
0.7466202
0.7708723
0.7846359
0.7925548

az cloud list

0.2445698
0.2627537
0.2784114
0.2815754
0.2404466
0.2456656
0.2328953
0.2678627
0.2267679
0.2247044

az with telemetry enabled

1.6212685
1.6762963
1.5584562
1.7061276
1.5949917
1.5022682
1.7164641
1.7227445
1.5963353
1.915089

az cloud list with telemetry enabled

1.3457957
1.4373729
1.0507627
0.9569793
1.3228079
1.2569795
1.2466929
1.0923828
1.17191
1.1996368

@troydai the 250 ms for az cloud list is acceptable but it doesn't take much more to make it feel sluggish which I think is sad.

more timings
az resource list --help

0.6549282
0.6460973
0.6551568
0.6934735
0.6563829
0.6648705
0.6467416
0.6695768
0.6433284
0.6766644

az resource list -g ...
2.7330824
1.2484462
1.2020567
1.1738106
1.1390877
1.2295843
1.5307826
1.1470495
1.2544168
1.2158291

Ideally, no command that doesn't traverse the network should have a latency greater than 250 ms. That is my firmly held opinion, given what I've learned so far.

Thank you for the measurement.
I notice that the telemetry seems to take a toll on the performance for Windows platform (as far as I can tell we didn't observe the delay on Linux/Unix). I think spawning a new process is blocking the command from exiting and cause the performance issue here. I will do more testing on the Windows platform.
I'm glad that the 250ms response time works for you. However, in many cases, the command communicates with the Azure service. Whenever there is network communication the network latency will dwarf any other factor.
I do agree with you that we can and should do much better when the command is run locally. And thank you for bringing our attention to this.
I filed following two issues to track the specific topics:

https://github.com/Azure/azure-cli/issues/4524
https://github.com/Azure/azure-cli/issues/4525

@troydai super!
It's just really annoying having to way for the CLI to respond if you make a typo. For example, I just started using the CLI and I use the --help command to explore a lot. But I had to wait for 3 seconds each time. 750 ms is better, a lot better but it's noticeable and a bit annoying. 250 ms feels great.

I agree. -h serve help information and it should be fast since it will be hit repeatedly just like your scenario.
I logged another issue regarding the performance difference between admin and user priviliege. In all, I think these three issues conclude all the discovers here.

https://github.com/Azure/azure-cli/issues/4526

So I will close this issue now. Please tracking above three github issue for the progress. And feel free open new github issues for any problem you meet with the Azure CLI. Again, thank you for reporting issues and the detailed measurement.

Let me ask here again what I already asked in #6265 :
why should the default be to upload "telemetry data" at all?? Inmy case that seems to be reporting my OS version, Python version and machine id strings to Azure...
Please turn that default off.

Telemetry does not seem to be done async, or at least blocks the main command to finish if it hangs (see  #6265 and #6248 ).
Disabling it using "az configure" gave me a perceived factor 2 in speed running a bash for-loop:
for BLOB in ... ; do   az storage blob download --container-name .... ; done

This in on Linux, not Windows.

A year and a half later and this is still a problem, on linux anyway.  Running az configure and turning off logging and telemetry makes performance bearable.


⚠ Samsung has degraded performance

In 4d911dc, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2669 ms

Resolved: Samsung performance has improved in 09c6fd1.


Avoid having to do your own checkout in user workflows

so instead of
        - name: checkout
          uses: actions/checkout@v2
        - name: Create a draft deposition in a new collection
          env:
            ZENODO_SANDBOX_ACCESS_TOKEN: ${{ secrets.ZENODO_SANDBOX_ACCESS_TOKEN }}
          uses<EMAIL_ADDRESS>
it would be better to have
        - name: Create a draft deposition in a new collection
          env:
            ZENODO_SANDBOX_ACCESS_TOKEN: ${{ secrets.ZENODO_SANDBOX_ACCESS_TOKEN }}
          uses<EMAIL_ADDRESS>

Hi
I just want to submit a new release inside an artifact with filenames from a previous job. the checkout does not seem necessary to me.
- uses: actions/download-artifact@v3

- name: "uploading to zenodo sandbox"
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    ZENODO_SANDBOX_ACCESS_TOKEN: ${{ secrets.ZENODO_SANDBOX_ACCESS_TOKEN }}
  uses<EMAIL_ADDRESS>  with:
    filenames: artifact/release.zip

Thanks for the feedback. Just to clarify, the code snippet you posted works, right? Without doing the checkout I mean. Although you may need to fiddle a bit with the path and/or name properties of download-artifact.

No, it does not work. It will throw an error for missing some git (I do not remember the exact error, but you will probably know which one!)
To avoid the error, I do the checkout anyway.
My current workaround for the path and name is to mv the file out of the artifact folder.
For documentation purposes:
with the code snippet above, the file name on zenodo will be artifact/release.zip instead of release.zip.
Therefore, I use the following code in my github action:
# download artifact in folder artifact/
- uses: actions/download-artifact@v3
# mv release.zip one level up
- run: |
     mv ./artifact/release.zip ./

Could you consider options like
file_path: artifact/release.zip
file_name: release.zip

My knowledge of typescript/javascript is quiet; otherwise, I would try to make a pull request.


sphinxcontrib.plantuml is no dependency

When setting up a new venv and installing sphinx-needs 1.0.2 with
pip install sphinx-needs

and then importing the library I get an exception:
$ python
Python 3.10.7 (main, Sep  6 2022, 21:22:27) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sphinx_needs
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/__init__.py", line 2, in <module>
    from sphinx_needs.needs import setup  # noqa: F401
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/needs.py", line 11, in <module>
    from sphinx_needs.api.configuration import add_extra_option
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/api/__init__.py", line 7, in <module>
    from .need import add_external_need, add_need, del_need, make_hashed_id  # noqa: F401
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/api/need.py", line 25, in <module>
    from sphinx_needs.directives.needuml import Needuml, NeedumlException
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/directives/needuml.py", line 10, in <module>
    from sphinx_needs.directives.needflow import make_entity_name
  File "/home/marco/.venv/lib/python3.10/site-packages/sphinx_needs/directives/needflow.py", line 10, in <module>
    from sphinxcontrib.plantuml import (
ModuleNotFoundError: No module named 'sphinxcontrib.plantuml'

This happens because sphinxcontrib.plantuml is not listed in [tool.poetry.dependencies].
The documentation says it is an optional dependency, however it is already a mandatory import in need.py.

The workaround for this for the time being:
pip install sphinxcontrib-plantuml

this import is now in try/except blocks within the processing methods (with warnings)


Error: ENOENT: no such file or directory, open '.next/serverless/pages-manifest.json'

Hi
Trying to use the new component. However, when I try deploy, I get this problem:
Error: ENOENT: no such file or directory, open '/.next/serverless/pages-manifest.json'
Here is my folder structure:
@types
README.md
client
declarations.d.ts
next-env.d.ts
next.config.js
node_modules
package.json
pages
scripts
server
serverless.yml
static
tools
tsconfig.json
tslint.json
yarn.lock

@barrysteyn Strange. Looks like there is a build problem in your app. When the next app is built there should be a /.next/serverless/pages-manifest.json file. Are you building using target: "serverless" ? Also, can you share your serverless.yml next app bit and any other info you may think is relevant.

Are you building using target: "serverless" ? Also, can you share your serverless.yml next app bit and any other info you may think is relevant.

No, I am trying to convert a project from the plugin to the component, and the plugin automatically makes the target serverless. I think for testing locally, we have left target as it's default.

Perhaps is best to add some validation in the component to make sure the next.config.js is set to serverless.

Perhaps is best to add some validation in the component to make sure the next.config.js is set to serverless.

Yes, this would be great. Maybe (as in the plugin version) it can just silently be inserted if not present. But an easier way would be just to add a documentation section explaining to people who are migrating that they need this present.
Great work Daniel, this is amazing.

Great work Daniel, this is amazing.

Thanks Barry!
I've added a separate issue for the target validation work.  https://github.com/danielcondemarin/serverless-next.js/issues/194

Hi, I had same issue, adding {target: 'serverless'} to next.config.js fixed. It will be great to add target validation.

I am also facing the same issue, as .next folder was not present so the error was coming on running  serverless command
  error:
  Error: pages-manifest not found. Check if `next.config.js` target is set to 'serverless'
    at CLI.renderError (/usr/local/lib/node_modules/serverless/node_modules/@serverless/cli/src/Context.js:308:15)
    at Object.runComponents (/usr/local/lib/node_modules/serverless/node_modules/@serverless/cli/src/index.js:218:13)
    at process._tickCallback (internal/process/next_tick.js:68:7)

  1s › myNextApp › pages-manifest not found. Check if `next.config.js` target is set to 'serverless'

serverless command should auto-generate .next folder

I am having the same issue after update to 1.7.1
My workaround is run next build before serverless deploy.


Comment:Step-Basic-Hooks-1

Comment:Step-Basic-Hooks-1
When pointing node at 1.js in the hooks folder, received this. Swapped remove with discard and got no error.

DEPRECATED. Use discard. (remove)

Just thought I should let you guys know so the feather-docs could be updated.
Loving the tutorial so far, thank you for all your work.

discard is not exactly the same as remove.
Thanks for the mention though.


Site does not work without Javascript

Version
Current
Steps to reproduce
Disable Javascript in browser.
Navigate to almost any page, e.g. https://echarts.apache.org/en/tutorial.html
What is expected?
The page should display content
What is actually happening?
Most pages display nothing.

Whilst it is fine to use JavaScript to enhance a website, it should not be a requirement:
https://monsido.com/blog/accessibility-issues#accessibility-issue-7-javascript-rendering
At the very least, the page should display some content to tell the user to use JavaScript.

Hi, @sebbASF Since most of the pages require JavaScript, we added tips to tell the visitors to enable JavaScript.

The /en/ pages don't seem to have notification that JS is needed.
Also the main page requires JS to change language; that seems unnecessarily restrictive.
Please try using the site without JS and see how it appears to users.

This is the notice @plainheart added when JavaScript is disabled.

Note that some users may not have the option of enabling JavaScript - for example, some assistive readers may not support JS.
So the site should as far as possible work without it.
JS should be used to provide additional features only, not for basic site content.
In particular, it should not be necessary to enable JS to change language!

Also the footer overlaps the page content, which means that some of the content cannot be seen properly.

Just updated our .htaccess file and most of the website pages are using server redirects for language now. Will keep working on it. Thanks for the advice @sebbASF

Thanks, the site is working a bit better, though the menu items do not work - there's really not need to use JS for that.
There is an issue with the way the  message has been implemented. For example, on the main index page, the message overwrites the footer.
Also, most of the index page does work without Javascript; it would be better to show the message in place of the bits that don't work. Same for some other pages such as https://echarts.apache.org/handbook/en/get-started/

Any updates here?


Allow coloring of the results of a SPARQL query

Is your feature request related to a problem? Please describe.
I would like to be able to set the color of the results of my SPARQL query in the visualization
Describe the solution you'd like
When running a SPARQL query that is visualized I would like it to color the results by label by rdf:type.  I would also like it to allow me to specify the property it will use to color by.

PR for previous work done on this issue for Gremlin
https://github.com/aws/graph-notebook/pull/15


Stop incrementing LMP after appointment date has passed

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?
Stop incrementing LMP after appointment date has passed

What feature or behavior is this required for?
One of the nicer features for our case managers is a running calculator that lets them know how far along a patient is. This is getting called by last_menstrual_period_display_short. It continues to increment indefinitely currently. We should change the behavior so that it stops incrementing at appointment date.

How could we solve this issue? (Not knowing is okay!)
We should pop into the last_menstrual_period_helper. Note that this behaves like a concern (we wrote it before I knew about concerns :( ), so you have Patient object methods and attributes available. Probably the easiest way is to alter the behavior of last_menstrual_period_now to account for appointment date as well.

Anything else?
Nope!

Me!


Automation Account

The Automation Account that is created by the landing zone scripts fails the Audit Diagnostic Setting policy from the PBMM Controls.
It either doesn't have Logging or Metrics setup I haven't dug too much into it yet:

The condition for this policy is for both Logs & Metrics.
Snippet from the policy:
          "existenceCondition": {
            "allOf": [
              {
                "field": "Microsoft.Insights/diagnosticSettings/logs.enabled",
                "equals": "true"
              },
              {
                "field": "Microsoft.Insights/diagnosticSettings/metrics.enabled",
                "equals": "true"
              }
            ]
          }

As part of landing zone automation, we only enable Logs to avoid extra cost.  Metrics will be part of Azure Monitor and doesn't need to be sent to Log Analytics Workspace.
Unfortunately, there's no way to disable the check on the metrics.  We will file a feature request to Azure Policy/engineering team to see whether they can allow the customization.

Yeah I dug into it right after and noticed it was for the Metrics. I'm filling out our 30 day cloud guardrail form and noticed that this was causing some of the audit policies to fail, I'll include a justification on my side for why it's failing when i fill out the guardrails document.

I've created a feature request via JimGBritt/AzurePolicy#41 to allow for customization at assignment time.

I'm looking into this update on my side @SenthuranSivananthan  but also realize it will be a breaking change for anyone using this in production already as a parameter will need to be added that provides the option between AuditIfNotExists and DeployIfNotExists. In addition, I want to review this from an option to allow this to be created as an optional path as opposed to the only path so that customers can migrate this direction if desired gradually.
My initial thought is introducing a parameter switch "-AuditIfNotExits" that will generate this option and it can be used.  This then will allow the policy to be flipped when ready to move from Audit to Deploy (potentially).  The beauty here is the script already provides the option for a unique Initiative name so you could deploy this twice - once for deploy and once for audit and all the policies will just inherit what the assignment is looking to apply.  I'll look into this after my current update goes out hopefully soon.
                "type": "string",
                "defaultValue": "AuditIfNotExists",
                "allowedValues": [
                    "AuditIfNotExists",
                    "DeployIfNotExists",
                    "Disabled"
                ],
                "metadata": {
                    "displayName": "Effect",
                    "description": "The effect determines what happens when the policy rule is evaluated to match"
                }

Thanks @JimGBritt for looking into this.  I think we also need the ability to choose which type of data to audit/deploy.  Today, the Audit diagnostic settings policy expects both Metrics & Logs to be enabled.  It will be helpful to have this be toggled.
This is the existence condition:
          "existenceCondition": {
            "allOf": [
              {
                "field": "Microsoft.Insights/diagnosticSettings/logs.enabled",
                "equals": "true"
              },
              {
                "field": "Microsoft.Insights/diagnosticSettings/metrics.enabled",
                "equals": "true"
              }
            ]
          }

To avoid breaking changes, I think the default value for these parameters can be true so they enable both data streams.
This would also have be changed at the Initiatives like Canada Federal PBMM or HIPAA/HITRUST that needs to be updated too with similar parameters & defaults.

Enable logs and metrics are already parameters so note sure there will be much to do there but will review.

FYI this is the built-in policy for reference:

@SenthuranSivananthan understood.  Also for reference - if we are talking about updating my script to add an effect of AuditIfNotExists and having enabled (true/false) that is already in my artifact export [see below]

My thought was to just add in a parameter for effect (AuditIfNotExists/DeployIfNotExists/Disabled) so that there is an option to toggle.  Should be trivial.

Azure Policy engineering team has updated PBMM Policy Initiative (policy set) so that diagnostic settings are configurable to enable/disable both metrics & logs.  We will update the landing zone automation to accommodate shortly.


Broken links in the README file

Still pointing to the old Theseus organization.
Grep through all the projects to see if there are any other links in README files or documentation still pointing to Theseus.

No Theseus references left.


:truck: chore(stackblitz): move stackblitz config to root for now

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #66   👈

This comment was auto-generated by Graphite.


[FormBuilderDropdown]: use DropdownButtonFormField

It would be nice to use DropdownButtonFormField for FormBuilderDropdown

Can test this on pre-release 9.0.0-dev.1

Nice, thanks


:hover on touch devices

There is actually no such a thing there, as there is no pointer. It leads to persistent :hover state after interaction is done.
I have fixed this for now by removing :hover selectors/rules at runtime https://github.com/kof/remove-hover
mostly because I don't want to modify topcoat for this.
Ideally, mobile only build should not contain :hover declarations or it should be configurable via css ....

We are cleaning up and getting ready for a new start on Topcoat from a team within Adobe. We should be able to make a way to bring back the hover classes if needed.


Reasoning against pre-reasoned sources

Expanding upon https://github.com/SolidLabResearch/Challenges/issues/14#issuecomment-1062554186 with some implementation specific ideas.
As a first-pass lets make the following assumptions (which can be verified inside the appropriate actors test method) to simplify the problem:

We have one pre-reasoned source that is reasoned with using the ruleset we wish to apply
We have one non-reasoned source
The rules we are applying are in a premise-conclusion style format (i.e. no quantification, nesting etc.)

As a 'naive' first implementation we can then do the following:

On the first iteration of reasoning with our (already optimized) rule set - we first check the premise of each rule against the 'unreasoned' dataset. If there are no premises that match that rule it is not included in this round of reasoning. If there is a match evaluate the remainder evaluate the rule against both databases, using the matches from the unreasoned dataset as initialBindings.
For each following round of reasoning the logic is similar to 1, except now we create these initialBindings using results produced in the previous iteration of reasoning.

^^ Most of this logic would also be re-usable to optimize the current rule evaluation strategies as well.

One can possibly view this reduced problem as one of 'incremental reasoning' - where the pod data can be abstractly considered as an 'insertion' into the main KB.

For extra points - handle dialogical reasoning https://github.com/SolidLabResearch/Challenges/issues/22


Firebase codelab section has non-clear ending point

RE: https://codelabs.developers.google.com/codelabs/flutter-firebase/#5
It's not clear where the iOS-only step "Configure Google Sign-In on iOS" section ends.
We think it ends after "This URL type will handle the callback when a user logs into your app.", but if so, a new section heading seems to be missing before "If you run the app".
This bug was found during a "dryrun" of the Firebase codelab in AAR by @floitschG, @mravn-google, and @mit-mit.

Inserted a heading Run Friendlychat


Create Study plan generator.md

📝 Description
You enter the syllabus, days left before exam and enter subject name. It provides day to day schedule giving a organized timetable
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
Hacktoberfest2023

Same as #2645  , so I will close the expired ones


Consider effective types/narrowed types when checking unreachability in match pattern with type quard

Description:
$title
Describe your task(s)
public function main() {
    int|boolean a = 1;

    match a {
        var x if a is int|string => {

        }
        var y if a is int|int[] => { // this should be unreachable

        }
    }
}

Related Issues (optional):
https://github.com/ballerina-platform/ballerina-lang/issues/30191
Suggested Labels (optional):

Suggested Assignees (optional):

Instead of assignability, we should check intersections with effective/narrowed type at https://github.com/ballerina-platform/ballerina-lang/pull/31428/files#diff-6b4a8cb1f7bd56d5a95a80500c4febcba531cdde5af59b66a477acd35e8485acR1525.


lua and lua roadrunner seperation

Before issuing a pull request, please see the contributing page.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4  👈
#2
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @minerkid08 and the rest of your teammates on  Graphite


fix: don't refresh TradingView when switching from wallet to trading tab

Proof of concept fix for #2525
I can say for certain that going into settings still triggers a refresh - I'm not sure if we care about this, though. Otherwise, it seems to work and it does not refresh when swapping from wallet to trading tab. If this general approach is acceptable (which maybe has wider-reaching impacts?), then I can re-add the animation to swap from wallet to trade tabs and we can merge this.

I think the approach makes sense.

Nice solution. What other implication could this have?

It keeps the state for all of the pages under the wallet & trade screen

Nice solution. What other implication could this have?

It keeps the state for all of the pages under the wallet & trade screen. This may or may not be an issue but I'm not quite sure how to evaluate it.

I guess this is ok given our application is quite small.

Going to update the animation now and then make this ready for merge

Here is how it looks on main:

And on this branch:

We could try implement a slide animation or leave it as is

Actually, this branch might be fine.
Here is how it looks on main: youtube.com/shorts/2LxbveDbIGc
And on this branch youtube.com/shorts/BO8j9-eOpKo?feature=share
We could try implement a slide animation or leave it as is

The webview plugin we are using is not supported on desktop. Try running it in a simulator.

The webview plugin we are using is not supported on desktop. Try running it in a simulator.

I'm not testing the webview plugin but rather the animation of switching between the two views themselves. It works fine with the webview plugin in the simulator

I'm going to merge this for now and we can change the animation in a followup if we like


How do you use it with formik?

I'm building a multi step form and on each step I need to validate different fields. The problema I'm finding is that I have to wrap te steps outside the Wizard component and I need to load formik inside the Wizard component to have access to the activeStep, like
 <Wizard>
      <Formik
        initialValues={{
          firstName: '',
          lastName: '',
          email: '',
          password: '',
          username: '',
          phoneNumber: '',
        }}
        validationSchema={SignUpValidations[activeStep]} # I know it'I have not used useWizard to get this value, I can wrap that later,  but you get the ide.
        onSubmit={handleOnSubmit}
      >
        {() => (
          <>
            <StepOne />
            <StepTwo />
          </>
        )}
      </Formik>
    </Wizard>

with formik I used to do:
const stepsValidations = [
  StepOneSchema,
  StepTwoSchema,
]

<Formik
    validationSchema={stepsValidations[steps]}
   ....
``

any solution to this?

Hi, thanks for creating this issue. Any reason why you don't wrap <Formik /> around every <Step />?

yes, because it's a big form that should submit at the end. Each formik for each step cannot share data, right?

Hello, @fddayan did you were able to use formik wizard. I am trying to do something similar If you have any recommendations it can be really helpful?

I'll suggest adding a Context to store all the data and wrap your Wizard with it. Then each of your steps will be its own Formik form.
I've found that using that approach allows me to better control the validation of the forms, and in your case, you can validate based on the step too.
In each Formik form, you can use the onSubmit to update the context and move a step in the wizard. And in your last form, grab all the data from the context + the last form to create a single payload to your endpoint.

See https://github.com/devrnt/react-use-wizard/issues/119#issuecomment-1916188255


[Feature Request] do not auto select first completion item in suggestion dialog

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
Currently suggestion dialog will select first completion item by default:

In our scenario we want to be very aggressive about triggering the suggestion dialog, thus we'd like the user to "opt out" from the suggestion dialog by pressing ENTER, otherwise users that would like to go to the next line will get unwanted completion items instead.
the suggestion is as follows:

when suggestion dialog is opened, no item is selected. pressing enter will close the suggestion dialog without any text inserted. pressing the down arrow instead will cause the first item to get selected.

It sounds like you may be looking for https://github.com/microsoft/vscode/issues/139825?

sounds like it!


Enums and disables - a rather bad title and large PR

This PR merges all the issues being worked on. Preparing for an alpha release.

LGTM


Invalid username

Describe the bug
$  instaloader meta/+args.txt -l blg002
Loaded session from /Users/blg002/.config/instaloader/session-blg002.
Logged in as blg002.
meta/+args.txt: Invalid username meta/+args.txt
Saved session to /Users/blg002/.config/instaloader/session-blg002.

Errors or warnings occurred:
meta/+args.txt: Invalid username meta/+args.txt

Instaloader version
4.9.5

@blg002 it appears you have passed a parameter in the wrong place, what were you looking to get with the meta/+args.txt?

@blg002 it appears you have passed a parameter in the wrong place, what were you looking to get with the meta/+args.txt?

--latest-stamps=/Users/blg002/Downloads/instaloader/meta/latest-stamps.txt
--no-captions
--no-videos
--no-video-thumbnails
--no-metadata-json
--no-compress-json
nasa
espn
...continuing list of instagram handles...

Start with the command line examples provided in the documentation, you are not setting up correctly

I did start there. Then slowly migrated to the args.txt file example from the docs. That all worked until the other day. I received the following type of errors
HTTP redirect from https://i.instagram.com/api/v1/users/web_profile_info/?username=USERNAME to https://i.instagram.com/accounts/login/?next=/api/v1/users/web_profile_info/

HTTP redirect from https://i.instagram.com/api/v1/users/web_profile_info/?username=USERNAME to https://www.instagram.com/accounts/login/?next=/api/v1/users/web_profile_info/
USERNAME: Redirected to login page. Use --login.

So i followed the examples for --login from the docs and am now at this point.
I'll try again from the command line, like you suggest, but would be surprised if thats the issue… but crazier things have happened.

Figured it out. the + character has to begin the path to the "args.txt" file, i.e.  instaloader +meta/args.txt. I forgot I had moved that file into its own folder.


add ResourceFiles

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

#sign-off


npm install on Windows shared folder

I try to use sane on a Windows shared folder (mounted with cifs), but I need to npm install --no-bin-links for a working install.
Do you have any idea for doing that ?
Thanks in advance

I have not tried that yet. Is it throwing any errors? But can hopefully test soon.

Example of error (there is many like that) :
Installing Sails packages for tooling via npm....npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "node" "/usr/local/bin/npm" "i" "sails-generate-ember-blueprints" "lodash" "morgan" "pluralize" "sails-disk" "--save"
npm ERR! node v0.10.35
npm ERR! npm  v2.1.16
npm ERR! path ../rimraf/bin.js
npm ERR! code UNKNOWN
npm ERR! errno -1

I already have the problem for another node project, and add --no-bin-links to npm install works for me, I've found the solution here : http://askubuntu.com/questions/269727/npm-errors-when-installing-packages-on-windows-share
Is there any solution, or possible workarounds for specify some arguments to node install with the sane cli ? I'm ready for testing some code, or help in some way for this issue.

Oohh, you mean that you have something like sane new project --no-bin-links?

Yes, somthing like that, or maybe with the .sane-cli file, which let us specify various arguments to add to npm install, or maybe sane new project --install="--no-bin-links"

Oh yeah, what you can do in the meantime btw, is try sane new project --skip-npm and then you can install everything manually.
Plus once all packages are installed you would also need to run sails generate ember-blueprints


Warn users when opening Python environment folders as workspace folders

We have seen users doing this quite often in the past, and things didn't work,
To my recollection execution didn't work, in in this case interpreter discovery does not work either #21218 (i.e. discovering the python env).
Suggestion: If this is not a supported scenario (i.e. opening these folders and having things not working), can we have the Python extension display a warning or the like that would educate them and prevent them from opening such folders in the future.
I understand there are circumstances when users (advanced) might want to open such folders, however I believe that is the minority, and given the fact that we've run into this in the past I think we might want to look into educating the users in some form or the like.

We seem to discover such envs just fine:

Hence closing.


Consul warning: WARN Service tag "..." will not be discoverable via DNS due to invalid characters. Valid characters include all alpha-numerics and dashes.

This is a warning but an issue people continually bring up. Fix this so it no longer occurs. Most likely requiring encoding of tag values using gzip and hex.

Hi!
Very quickly regarding the topic issue:
github.com/micro/go-micro/registry/consul_registry.go
consul_registry.go.patch.gz
Probably we've to implement according to rfc2782?
Here's details: https://www.consul.io/docs/agent/dns.html
Alex

Hi!
Very quickly regarding the topic issue:
github.com/micro/go-micro/registry/consul_registry.go
Probably we've to implement according to rfc2782?
Here's details: https://www.consul.io/docs/agent/dns.html https://www.consul.io/docs/agent/dns.html
Alex

On Mar 16, 2016, at 1:29 PM, Asim<EMAIL_ADDRESS>wrote:
This is a warning but an issue people continually bring up. Fix this so it no longer occurs. Most likely requiring encoding of tag values using gzip and hex.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/micro/go-micro/issues/62

The only comment Consul provides on this is that tags are opaque strings and must be of the alpha-numeric format. Converting to hex is probably going to be the easiest solution. I welcome any more appropriate solutions to convert JSON to something of a valid format.

https://github.com/micro/go-micro/pull/63

https://github.com/micro/go-micro/pull/63 now merged. Next step will be to stop registering old encoding entirely, while still decoding them if they exist. That should completely remove the warnings but will be the point at which any old service cannot read new services.

It's been sometime since the encoding fix was merged. In the next few weeks I will strip the old encoding so it removes the warnings.

now stripped https://github.com/micro/go-micro/commit/06ee80fd0a9594fc38e68d16d2e7a7e9b2ed0ecf


Wrong condition in /mail/EmailAddress.php

Good day,
The next condition on line 73 is wrong (file /mail/EmailAddress.php).
if (!is_string($emailAddress) && filter_var($emailAddress, FILTER_VALIDATE_EMAIL))
It turns out that email address shouldn't be a string and should be a valid address simultaneously in order to throw exception.
Probably the right condition is:
if (!(is_string($emailAddress) && filter_var($emailAddress, FILTER_VALIDATE_EMAIL)))

FYI this logic seems to fail once over 10000 times or so, such that the error is thrown when it shouldn't be. We are forcing the email to a string and legitimate emails are still throwing this exception. We've had to comment out this validation because it craps out too often.


Fetch-lib. Fix for #315

#315 had an issue with tls_certificates v3. Checking here so noctua doesn't force push on my commit.

Tests passed locally, but grafana had a brief error:
unit-grafana-1: 13:58:18 ERROR unit.grafana/1.juju-log certificates:2: Could not restart grafana at this time: cannot perform the following tasks:
- Start service "grafana" (cannot start service: exited quickly with code 1)
----- Logs from task 0 -----
2024-04-25T17:58:18Z INFO Most recent service output:
    (...)
    logger=provisioning.plugins t=2024-04-25T17:58:18.516812528Z level=error msg="Failed to read plugin provisioning files from directory" path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
    logger=provisioning.notifiers t=2024-04-25T17:58:18.516834278Z level=error msg="Can't read alert notification provisioning files from directory" path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
    logger=provisioning.alerting t=2024-04-25T17:58:18.516849248Z level=error msg="can't read alerting provisioning files from directory" path=/etc/grafana/provisioning/alerting error="open /etc/grafana/provisioning/alerting: no such file or directory"
    logger=provisioning.alerting t=2024-04-25T17:58:18.516855357Z level=info msg="starting to provision alerting"
    logger=provisioning.alerting t=2024-04-25T17:58:18.516862268Z level=info msg="finished to provision alerting"
    logger=modules t=2024-04-25T17:58:18.516971128Z level=warn msg="No modules registered..."
    logger=ngalert.state.manager t=2024-04-25T17:58:18.516974078Z level=info msg="Warming state cache for startup"
    logger=grafanaStorageLogger t=2024-04-25T17:58:18.517046737Z level=info msg="storage starting"
    logger=ngalert.state.manager t=2024-04-25T17:58:18.517146777Z level=info msg="State cache has been initialized" states=0 duration=172.249µs
    logger=ngalert.multiorg.alertmanager t=2024-04-25T17:58:18.517188197Z level=info msg="starting MultiOrg Alertmanager"
    logger=ticker t=2024-04-25T17:58:18.517197237Z level=info msg=starting first_tick=2024-04-25T17:58:20Z
    logger=server t=2024-04-25T17:58:18.518468975Z level=error msg="Stopped background service" service=*api.HTTPServer reason="cert_file cannot be empty when using HTTPS"
    logger=tracing t=2024-04-25T17:58:18.518571835Z level=info msg="Closing tracing"
    logger=ticker t=2024-04-25T17:58:18.518727614Z level=info msg=stopped last_tick=2024-04-25T17:58:10Z
    logger=grafana.update.checker t=2024-04-25T17:58:18.518759164Z level=error msg="Update check failed" error="failed to get latest.json repo from github.com: Get \"https://raw.githubusercontent.com/grafana/grafana/main/latest.json\": context canceled" duration=1.539637ms
    logger=auth t=2024-04-25T17:58:18.521339439Z level=error msg="failed to lock and execute cleanup of expired auth token" error="context canceled"
    logger=serviceaccounts t=2024-04-25T17:58:18.522056807Z level=warn msg="Failed to get usage metrics" error="context canceled"
    logger=infra.usagestats t=2024-04-25T17:58:18.522125307Z level=error msg="Failed to get last sent time" error="context canceled"
    logger=infra.usagestats.collector t=2024-04-25T17:58:18.522235617Z level=error msg="Failed to get system stats" error="context canceled"
    Error: ✗ *api.HTTPServer run error: cert_file cannot be empty when using HTTPS
2024-04-25T17:58:18Z ERROR cannot start service: exited quickly with code 1

Specifically:

open /etc/grafana/provisioning/plugins: no such file or directory
open /etc/grafana/provisioning/notifiers: no such file or directory
cert_file cannot be empty when using HTTPS

Seems like the first two are non-critical errors, and the empty cert_file is what brings it down.
Context:
25 Apr 2024 13:56:42-04:00  juju-unit  allocating
25 Apr 2024 13:56:42-04:00  workload   waiting      installing agent
25 Apr 2024 13:56:54-04:00  workload   waiting      agent initialising
25 Apr 2024 13:57:28-04:00  workload   maintenance  installing charm software
25 Apr 2024 13:57:28-04:00  juju-unit  executing    running install hook
25 Apr 2024 13:57:30-04:00  juju-unit  executing    running grafana-relation-created hook
25 Apr 2024 13:57:30-04:00  juju-unit  executing    running certificates-relation-created hook
25 Apr 2024 13:57:31-04:00  juju-unit  executing    running replicas-relation-created hook
25 Apr 2024 13:57:32-04:00  juju-unit  executing    running leader-elected hook
25 Apr 2024 13:57:33-04:00  juju-unit  executing    running grafana-pebble-ready hook
25 Apr 2024 13:57:37-04:00  juju-unit  executing    running litestream-pebble-ready hook
25 Apr 2024 13:57:38-04:00  juju-unit  executing    running database-storage-attached hook
25 Apr 2024 13:58:04-04:00  juju-unit  executing    running config-changed hook
25 Apr 2024 13:58:08-04:00  juju-unit  executing    running start hook
25 Apr 2024 13:58:10-04:00  workload   unknown
25 Apr 2024 13:58:10-04:00  juju-unit  executing    running litestream-pebble-ready hook
25 Apr 2024 13:58:10-04:00  juju-unit  executing    running grafana-pebble-ready hook

unit-grafana-1: 13:58:12 INFO unit.grafana/1.juju-log Restarted grafana-k8s
unit-grafana-1: 13:58:13 INFO unit.grafana/1.juju-log Restarted grafana-k8s
unit-grafana-1: 13:58:14 INFO unit.grafana/1.juju-log Initializing dashboard provisioning path
unit-grafana-1: 13:58:15 INFO unit.grafana/1.juju-log Restarted grafana-k8s

25 Apr 2024 13:58:15-04:00  juju-unit  executing    running replicas-relation-joined hook for grafana/0

(BOOM)

unit-grafana-1: 13:58:18 ERROR unit.grafana/1.juju-log certificates:2: Could not restart grafana at this time: cannot perform the following tasks:
- Start service "grafana" (cannot start service: exited quickly with code 1)
...

25 Apr 2024 13:58:16-04:00  juju-unit  executing    running certificates-relation-changed hook
25 Apr 2024 13:58:19-04:00  juju-unit  executing    running certificates-relation-joined hook for ca/0
25 Apr 2024 13:58:19-04:00  juju-unit  idle
25 Apr 2024 13:58:19-04:00  juju-unit  executing    running replicas-relation-changed hook for grafana/0
25 Apr 2024 13:58:20-04:00  juju-unit  executing    running certificates-relation-changed hook for ca/0
25 Apr 2024 13:58:23-04:00  juju-unit  idle
25 Apr 2024 13:58:24-04:00  juju-unit  executing    running grafana-relation-changed hook
25 Apr 2024 13:58:25-04:00  juju-unit  idle
25 Apr 2024 13:58:25-04:00  juju-unit  executing    running grafana-relation-joined hook for grafana/0
25 Apr 2024 13:58:26-04:00  juju-unit  executing    running grafana-relation-changed hook for grafana/0
25 Apr 2024 13:58:58-04:00  juju-unit  idle
25 Apr 2024 13:58:59-04:00  juju-unit  executing    running replicas-relation-changed hook for grafana/0
25 Apr 2024 13:59:00-04:00  juju-unit  executing    running certificates-relation-changed hook
25 Apr 2024 13:59:10-04:00  juju-unit  idle
25 Apr 2024 13:59:10-04:00  workload   active
25 Apr 2024 13:59:16-04:00  juju-unit  executing    running replicas-relation-changed hook for grafana/0
25 Apr 2024 13:59:17-04:00  juju-unit  idle
25 Apr 2024 14:00:25-04:00  workload   maintenance  stopping charm software
25 Apr 2024 14:00:25-04:00  juju-unit  executing    running stop hook
25 Apr 2024 14:00:26-04:00  workload   maintenance  Application is terminating.
25 Apr 2024 14:00:26-04:00  workload   maintenance
25 Apr 2024 14:01:03-04:00  juju-unit  executing    running upgrade-charm hook
25 Apr 2024 14:01:15-04:00  juju-unit  executing    running config-changed hook
25 Apr 2024 14:01:20-04:00  juju-unit  executing    running start hook
25 Apr 2024 14:01:22-04:00  juju-unit  executing    running grafana-pebble-ready hook
25 Apr 2024 14:01:31-04:00  juju-unit  idle
25 Apr 2024 14:01:31-04:00  juju-unit  executing    running litestream-pebble-ready hook
25 Apr 2024 14:01:32-04:00  juju-unit  executing    running certificates-relation-changed hook
25 Apr 2024 14:01:35-04:00  juju-unit  idle
25 Apr 2024 14:01:36-04:00  juju-unit  executing    running grafana-relation-changed hook
25 Apr 2024 14:01:37-04:00  juju-unit  idle
25 Apr 2024 14:02:07-04:00  juju-unit  executing    running replicas-relation-changed hook for grafana/0
25 Apr 2024 14:02:07-04:00  juju-unit  executing    running certificates-relation-changed hook
25 Apr 2024 14:02:20-04:00  juju-unit  idle
25 Apr 2024 14:02:20-04:00  workload   active
25 Apr 2024 14:02:23-04:00  juju-unit  executing    running replicas-relation-changed hook for grafana/0
25 Apr 2024 14:02:24-04:00  juju-unit  idle


[microTVM][ARM] Enable tests that were skipped unintentionally

cc @Lunderberg @alanmacd @areusch @gromero

@mehrdadh Hi. Could you please give a bit more of context here? The tests where skipped when / by which commit? Is if fixing which bug exactly? Any CI error or log you can point out /  share so I can take a look on the error fixed by this fix?

@gromero sorry for lacking of details. I changed the description


Unable to load 'librdkafka' in CentOS

I have used the latest 0.9.5.RC4 and it runs properly on windows. but when i try to run it on CentOS it throws
Unhandled Exception: System.TypeInitializationException: The type initializer for 'Confluent.Kafka.Impl.LibRdKafka' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'librdkafka': The specified module could not be found.
(Exception from HRESULT: 0x8007007E)
at Confluent.Kafka.Impl.LibRdKafka.NativeMethods.rd_kafka_version()
at Confluent.Kafka.Impl.LibRdKafka.version()
at Confluent.Kafka.Impl.LibRdKafka..cctor()
--- End of inner exception stack trace ---
at Confluent.Kafka.Impl.LibRdKafka.conf_new()
at Confluent.Kafka.Impl.SafeConfigHandle.Create()
at Confluent.Kafka.Consumer..ctor(IEnumerable1 config)    at Confluent.Kafka.Consumer2..ctor(IEnumerable1 config, IDeserializer1 keyDeserializer, IDeserializer`1 valueDeserializer)
I have manually added the rhel-x64 links in the deps.json file, but i end up in having version mismatch error.
Unhandled Exception: System.TypeInitializationException: The type initializer for 'Confluent.Kafka.Impl.LibRdKafka' threw an exception. ---> System.IO.FileLoadException: Invalid librdkafka version 904c9, expected at least 904ff
at Confluent.Kafka.Impl.LibRdKafka..cctor()
--- End of inner exception stack trace ---
at Confluent.Kafka.Impl.LibRdKafka.conf_new()
at Confluent.Kafka.Impl.SafeConfigHandle.Create()
at Confluent.Kafka.Consumer..ctor(IEnumerable1 config)    at Confluent.Kafka.Consumer2..ctor(IEnumerable1 config, IDeserializer1 keyDeserializer, IDeserializer`1 valueDeserializer)
i think the librdkafka redist is not updating the rhel-x64 version of librdkafka libraries.

right, so there are two problems - 1. on CentOS the native libraries are not being deployed correctly. when that is resolved manually 2. the version number for rhel-x64 libraries in the package apparently indicates they are in fact older than 0.9.5.
I have not looked into problem 1 (which we need to be fixed before calling this a release). For problem 2, as a potential quick fix I changed the check in Confluent.Kafka to allow librdkafka version 0.9.4 (note: the only critical fix in 0.9.5 is for the CPU issue for windows users). I put the corresponding nuget package from appVeyor on nuget.org: 0.9.5-RC5-ci-207 (which is hidden but accessible).

Ive verified that the linux libraries included in librdkafka.redist.0.9.5 indeed report version 0.9.5 (0x000905ff)

thanks @edenhill
On CentOS, I see that the Windows .dlls are being copied into the x86 and x64 directories. I also see this was the case in 0.9.4.
@suganthkumar we obviously want to fix this. but something to consider right now: if docker is an option, this issue does not occur when running inside the microsoft/dotnet docker images.

This is not a regression (was broken in 0.9.4 as well), so we've decided to postpone fixing until 0.9.6 as 0.9.5 contains a critical fix for windows users that we want to get out now.

@mhowlett
Strange, the dll should only be copied for net project, or nuget works differently on centOs.
(didn't test the rhel package on my side, only the debian ones)

Ideally we should set up an automated test for each supported platform. It's time consuming to manually do a basic test on all platforms prior to release and easy to cut corners..

i did a full compile on CentOS for the librdkafka library, and once the new library is deployed, its working properly. so its seems the only issue is nuget is not deploying the right native libraries.

Do you have a workaround until next release?

Confluent.Kafka.dll just needs to be able to find librdkafka. install it from source (not hard) which will put it in /usr/local/lib or put it in the same directory as Confluent.Kafka.dll.

for CentOS i'd recommend getting the librdkafka source git clone https://github.com/edenhill/librdkafka.git then follow the build/installation instructions to build from source (it's not hard).
the nuget package RdKafka.Internal.librdkafka is no longer relevant - we reference librdkafka.redist.

Personally, i can confirm that this solution (recompile library directly from CentOS) works for .net core projects

Thanks for confirming - this should also be resolved in next nuget package
We may add doozer CI for testing on centos soon

Version 0.11.0
I also have this problem on CentOS, I've solved it through the following command :
sudo yum install librdkafka-devel

centos7 compatible builds of librdkafka are now included in librdkafka.redist - manual install of librdkafka is no longer required on this platform.


Support instanceof checks for exported Scala class constructors

At the moment, instanceof checks do only work for classes that extend js.Object. Unfortunately case classes must not extend js.Object.
Motivation (copied from Gitter): I would like to define Scala ADTs (represented by sealed traits plus cases classes) by TypeScript union types. A common pattern for exhaustiveness checks in TypeScript is to use flow typing with instanceof checks.

To summarize our conversation on Gitter:
It is possible for us to do so by setting .prototype on exported constructors. We'd need a new IR node for this.
The downside of this is that we would lock-in certain structural constraints on how Scala.js implements Scala classes in JavaScript.
@sjrd does that summarize the discussion well?

Yes, that is a fairly accurate summary.
I'll add that I think the most promising way to implement this is on top of Symbol.hasInstance, although that means it would only work when emitting ECMAScript 2015 code.

Oh, also to double check my understanding: The reason we are reluctant to support case classes that extend js.Object is because equals and hashCode would not work, right? (apply and unapply could be made to work, right)?

I'll add that I think the most promising way to implement this is on top of Symbol.hasInstance, although that means it would only work when emitting ECMAScript 2015 code.

This is interesting now that I think about this: Wouldn't this give us a way forward if we chose a different encoding? In ES5.1 we could rely on .prototype. This would lock us in on the encoding, but we could make any potential new encoding dependent on being in ES6.

Oh, also to double check my understanding: The reason we are reluctant to support case classes that extend js.Object is because equals and hashCode would not work, right? (apply and unapply could be made to work, right)?

That's right. And if equals doesn't work for a case class, I'm sure a lot of expectations in users would be very broken.

I'll add that I think the most promising way to implement this is on top of Symbol.hasInstance, although that means it would only work when emitting ECMAScript 2015 code.

This is interesting now that I think about this: Wouldn't this give us a way forward if we chose a different encoding? In ES5.1 we could rely on .prototype. This would lock us in on the encoding, but we could make any potential new encoding dependent on being in ES6.

In theory, yes. In practice, that would mean more code paths if we change the encoding for ES6 but we have to preserve the old one for ES5.1.
Another problem with .prototype is that it accidentally gives too much power. For example, it would kind-of allow a user to extend a Scala class from JavaScript, if the stars align. For example if the class is eligible for the inline-init optimization, like the following:
@JSExportTopLevel("Foo")
@JSExportAll
class Foo(val x: Int)

it would be rougly translate as
class $c_Foo extends $c_jl_Object {
  constructor(x) {
    super()
    this.f_x = x;
  }
  get "x"() {
    return this.f_x;
  }
}
function Foo(x) {
  return new $c_Foo(x);
}
Foo.prototype = $c_Foo.prototype;

which means that the following user JS code would happen to "work":
class Bar extends Foo {
  constructor(x, y) {
    super(x);
    this.y = y;
  }
}

var bar = new Bar(5, 6)
bar.x // 5
bar.y // 6

So it would appear that one can meaningfully extend an exported class, even though that's completely undefined behavior, and will break in obscure situations (not final anymore, 2 reachable constructors, etc.).

Maybe then we should just make it an ES2015 feature only. We do have precedent for this with static member inheritance, right?

Yes, that's right.

I dug up https://github.com/scala-js/scala-js/commit/ce17362666d2f1fa556c48f236b97b68e8fb1be4 , in which we actually removed that (then unspecified) behavior. 🤷♂


errors building tmsp-cli

getting these errors:
smb:tmsp$ go install github.com/tendermint/tmsp/cmd/tmsp-cli
# github.com/tendermint/tmsp/cmd/tmsp-cli
cmd/tmsp-cli/tmsp-cli.go:43: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:50: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:57: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:64: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:71: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:78: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:85: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:92: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value
cmd/tmsp-cli/tmsp-cli.go:99: cannot use func literal (type func(*cli.Context) error) as type func(*cli.Context) in field value

Happy to fix and submit a pull request, if someone can point me in the right direction.

Hi, sorry about this - the library we use for the command line interface recently hard forked at virtually the entire go community's expense. Can you try updating your dependencies by running go get -u ./... and then retrying the install?

works - sweet!