TypeError in Model Selection

Hi again, I'm working through the model selection section and I think I've hit a bug. I'm passing scipy distributions as indicated in the examples, but omitting from below as there's quite a lot.
Truncated Code:
`from mlens.metrics import make_scorer
mae_scorer = make_scorer(mean_absolute_error, greater_is_better=False)
evaluator = Evaluator(mae_scorer, cv=5, random_state=seed, verbose=1)
evaluator.evaluate(X_mean, y, estimators, params, n_iter=10)`
Error:
`---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
 in ()
65
66 evaluator = Evaluator(mae_scorer, cv=5, random_state=seed, verbose=1)
---> 67 evaluator.evaluate(X_mean, y, estimators, params, n_iter=10)
C:\Anaconda2\lib\site-packages\mlens\model_selection\model_selection.pyc in evaluate(self, X, y, estimators, param_dicts, n_iter)
387         self.estimators = check_instances(estimators)
388         self.n_iter = n_iter
--> 389         self._param_sets(param_dicts)
390
391         if self.verbose > 0:
C:\Anaconda2\lib\site-packages\mlens\model_selection\model_selection.pyc in _param_sets(self, param_dicts)
494             # the expected param_dicts key is 'est_name'
495             for est_name, _ in self.estimators:
--> 496                 self._set_params(param_dicts, est_name)
497         else:
498             # Preprocessing
C:\Anaconda2\lib\site-packages\mlens\model_selection\model_selection.pyc in _set_params(self, param_dicts, key)
478         try:
479             self.params[key] =
--> 480                 self._draw_params(param_dicts[key])
481         except KeyError:
482             # No param draws desired. Set empty dict.
C:\Anaconda2\lib\site-packages\mlens\model_selection\model_selection.pyc in _draw_params(self, param_dists)
469             draws = dist.rvs(self.n_iter, random_state=self.random_state)
470
--> 471             for i, draw in enumerate(draws):
472                 param_draws[i][param] = draw
473
TypeError: 'int' object is not iterable
`
Looks to me as though draws = dist.rvs(self.n_iter, random_state=self.random_state) should be  draws = dist.rvs(size=self.n_iter, random_state=self.random_state) ?

Hi,
Yeah that's the intended behavior. Guess I've only used classes where size is the first positional argument. Feel free to make a pull req with the fix, otherwise I'll make the update later this week.

Btw in the latest update you can avoid having to set the backend argument all the time either by setting an MLENS_BACKEND environmental variable, or start your code with
from mlens import config
config.set_backend('threading')

Nice, thanks! I'll try and do a pull request this evening if I get time.

Patched in <IP_ADDRESS>


New version: Scorpio.sco version 2.6.0

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.6 schema?

Microsoft Reviewers: Open in CodeFlow

Hi @+Validation-Defender-ErrorBinary-Validation-ErrorError-Analysis-TimeoutError-Hash-MismatchError-Installer-AvailabilityInternal-ErrorInternal-Error-Dynamic-ScanInternal-Error-ManifestInternal-Error-URLManifest-AppsAndFeaturesVersion-ErrorManifest-Installer-Validation-ErrorManifest-Validation-ErrorPossible-DuplicatePullRequest-ErrorURL-Validation-ErrorValidation-DomainValidation-Executable-ErrorValidation-Hash-Verification-FailedValidation-Missing-DependencyValidation-Merge-ConflictValidation-No-ExecutablesValidation-Installation-ErrorValidation-Shell-ExecuteValidation-Unattended-FailedPolicy-Test-1.2Policy-Test-2.3Policy-Test-2.3Validation-Forbidden-URL-ErrorValidation-Unapproved-URLValidation-RetryNeeds-Author-Feedback[0],
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 832.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-02-27 12:14:01.258 [FAIL] Installer failed security check. Url: https://github.com/qingfeng346/Scorpio-CSharp/releases/download/v2.6.0/sco-2.6.0-win-x64.msi Result: 0x80004005

(Automated response - build 832.)

Enter a pull request number: 141188

Manifest validation succeeded.
Found sco [Scorpio.sco] Version 2.6.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/qingfeng346/Scorpio-CSharp/releases/download/v2.6.0/sco-2.6.0-win-x64.msi
  ██████████████████████████████  31.4 MB / 31.4 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Name          : sco
Publisher     : Scorpio
Version       : 2.6.0
ProductCode   : {E24CF46E-04C3-4BF1-AB5D-206E7C7AA6B8}
Registry Path : Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{E24CF46E-04C3-4BF1-AB5D-206E7C7AA6B8}
Uninstall     : winget uninstall --id "{E24CF46E-04C3-4BF1-AB5D-206E7C7AA6B8}"

Press any key to continue . . .

Pretty sure its because its marked as Trojan:Script/Wacatac.B!ml tho..
Edit: Yup


Empty getElementById() request

Hello,
I saw a problem with this component, the JS error "An empty parameter sended to getElementById()".
This problem is also present on your demo page https://dalelotts.github.io/angular-bootstrap-datetimepicker/

Many thanks

Interesting - I do not see this error.

If I do the right thing (not sure !) it appear empty.

Which browser?

Not sure what to tell you. I don't care about this unless something is not working correctly.

Everything appear working correctly !
Only, it's not really "clean" to have error message for a functional thing.
This error may cause other errors in specific cases ?

It could be related to the locale (language) setting - but I cannot fix it if I cannot reproduce it or at least see the call stack to see what is triggering the error. The information I have now is not enough.
I agree it is not clean, but I cannot reproduce in any way so there is nothing I can do. This directive does not require jquery so do not include jquery and this message should go away.


Split inferentia CI workflows

These workflows take too long: they need to be split.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Try building on win64.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


[DEPRECATED] Change ProtoShell-related files to be securely accessible by select (root) user(s) and prefix file names

Sensitive files containing calls to functions requiring proto_key should have specific permissions setup such that only privileged users may view/edit. These files should be prefixed with an easily identifiable token to distinguish them from normal files.

WIP

This feature is no longer required due to a change in ProtoShell design on company's end => ProtoShell is now running as an independent Laravel application which performs processing on raw and perms data.

This feature is no longer required due to a change in ProtoShell design on company's end => ProtoShell is now running as an independent Laravel application which performs processing on raw and perms data.


Merge pull request #6 from Srwats0n/main

Merge pull request #5 from Srwats0n/conteudos

atualizacao


Add work score tests from TIP

https://github.com/iotaledger/tips/blob/tip46/tips/TIP-0046/tip-0046.md#basic-block-id--work-score-tagged-data-payload

Closed by https://github.com/iotaledger/iota-sdk/pull/1914


opt: parallel batch reverse

@ChengYueJia  this parallel opt does not help.

@ChengYueJia this parallel opt does not help.

Got it. This can be closed.


Add startAt/endAt cursors to MockQuery

Hey,
I needed the functionality of the Query.startAt/Query.endAt methods for some tests in my project.
I implemented them in a way which only simulates the cursor on a concrete match, that means
[0, 1, 2, 3, 4, 5, 7, 8, 9].startAt(5) = [5,7,8,9]
[0, 1, 2, 3, 4, 5, 7, 8, 9].startAt(6) = [0, 1, 2, 3, 4, 5, 7, 8, 9]
I don't know whether this suffices for a PR, but since this feature has been requested in Issue #73, I didn't want to withhold my implementation from you.

Thanks for your PR @maxluchterhand1. I'll take a look this weekend. In the meantime, would you mind writing unit tests for your new code?

Hey, thanks for your feedback. I just took care of everything you asked for.

Thanks again for the PR. I published it to https://pub.dev/packages/cloud_firestore_mocks/changelog#083.
Also I annotated some of your tests when they were different with Firestore for future reference at https://github.com/atn832/cloud_firestore_mocks/commit/39f0ae41ee7842bbf613d5f5eee1b826ad587f9d.


Angular 9 Project w/ Harp.gl

Describe the bug
We are trying to create a MapView object within an Angular project using angular-builders/custom-webpack and harp-webpack-utils packages. The webpack config returned from harp-webpack-utils overrides the default Angular configuration, resulting in Angular not building the appropriate bundles: main.bundle.js, polyfills.bundle.js etc.

Hi @gbrown97 , is your project hosted on github ? I can look at it and guide you further.

Here is a link to the repo:
https://github.com/gbrown97/harp-app


New versions not getting published

Hi,
since some time new versions do not get published anymore.
The last published workflow: https://github.com/cdklabs/cdk-import/actions/runs/7950789940
The first not-published workflow: https://github.com/cdklabs/cdk-import/actions/runs/7960957810

Hi @tenjaa. Thank you for raising this issue. This has been fixed via this PR - https://github.com/cdklabs/cdk-import/pull/933


Weights Download Link is Dead

As the title says, clicking the link from README.md results in a 404.
This is the link: https://drive.google.com/drive/folders/1GNwxJwKyAZybAP71T0N0wo2yH6GAgzkP?usp=share_link

I have fixed the link. Let me know if it works now

Oh thank you! Now it works!
Not sure where to place this message but I appreciate your work. This is my first time tinkering with these kinds of projects. Been holding it off for so long since these are "fun" projects for me. Not work related.
Didn't see any roadmap in your docs. I want to contribute back and if  you need help making this more accessible or integrate-able to other projects, perhaps I can help you out. You give directions and I can do the legwork.


Unable to resolve resource vscode-vfs:// on https://github.dev

@piradata a few questions

do you have a firewall that might be blocking our ability to access the extensions marketplace?
which browser are you using, does this occur with all browsers?
if you open browser devtools, are there any errors, if so can you copy and paste them in a comment below?


Integrate Amplitude with Tealium

Dear all ,
I want to use the JS SDK with Tealium , and i want to know if there is any doc that could guide/help me please.
Regrads

@bloodymind there's now a Tealium integration with Amplitude: https://tealium.com/integrations/amplitude_amplitude_connector.php


Tip: Getting this to work on Google cloud engine

Prerequisites

[ x] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[ x] Checked that your issue isn't already filed.
[ x] Checked if no PR was submitted that fixes this problem.

Versions

PHP version:  7.4
Laravel version: 8
Nova version: 3.27
Package version: 1.2

Description

Server error 500 when downloading Excel file because the folder /storage/framework/cache/laravel-excel can not be created at run time by Google App Engine.
Steps to Reproduce

Vanilla install
Tip to solve - recommend adding this to the readme or manual:

the GAE deploy uses the .gitignore files to determine which directories should be created on the Google App Engine platform
Ensure the folder exists locally (which will be the case in most cases as you probably did run some tests)
create a dummy file dummy.txt in  /storage/framework/cache/laravel-excel
modify the .gitignore file on  /storage/framework/cache/.gitignore and add these 2 lines:

!laravel-excel
!laravel-excel/dummy.txt

The total .gitignore file should read something like:

*
!data/
!.gitignore
!laravel-excel
!laravel-excel/dummy.txt

Expected behavior:

Actual behavior:

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

If there should be changes to the documentation, please PR it to the docs repo: https://github.com/SpartnerNL/laravel-excel-docs


Add preserve namings option to cli

Proposed Changes

Add cli option to preserve naming found in the application.json spec whereever possible instead of attempting to sanitize it into something javascript-y
Fixes #76

@joe-p I don't suppose you have a good example contract I could add to demonstrate this feature?


Update README

fix syntax highlighting for Go code

Codecov Report

Merging #238 into master will decrease coverage by 3.29%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #238     +/-   ##
=========================================
- Coverage      84%   80.71%   -3.3%
=========================================
  Files          42        8     -34
  Lines        2939     1872   -1067
=========================================
- Hits         2469     1511    -958
+ Misses        328      273     -55
+ Partials      142       88     -54

Impacted Files
Coverage Δ

vm/vmConvertToX.go
52.3% <0%> (-6.16%)
:arrow_down:

vm/vmStmt.go
79.87% <0%> (-3.72%)
:arrow_down:

vm/vmToX.go
76.63% <0%> (-1.87%)
:arrow_down:

vm/vmExpr.go
81.83% <0%> (-0.92%)
:arrow_down:

vm/vmExprFunction.go
69.63% <0%> (-0.81%)
:arrow_down:

ast/astutil/walk.go

packages/sortGo18.go

packages/osNotAppEngine.go

packages/strings.go

packages/fmt.go

... and 29 more

Continue to review full report at Codecov.

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


Vuex mocking not working?

Hi, I have this component:
<template>

</template>

and this test:
import jest from 'jest';
import Vuex from 'vuex';
import {
  createLocalVue,
  shallow,
} from 'vue-test-utils';

import Foo from '@/components/Foo';

const localVue = createLocalVue();
localVue.use(Vuex);

describe.only('Foo.vue', () => {
  let actions;
  let store;

  beforeEach(() => {
    actions = {
      SOME_ACTION: jest.fn()
    };
    store = new Vuex.Store({
      state: {},
      actions
    });
  });

  it('should dispatch action when created', () => {
    shallow(Foo, {
      localVue,
      store
    });
    expect(actions.SOME_ACTION).toHaveBeenCalled();
  });
});

If I'm not missing anything, this is the same structure as the one used here.
But when I run jest, I get this:
 FAIL  src/__tests__/components/Foo.spec.js
  ● Console

    console.error node_modules/vue/dist/vue.runtime.common.js:432
      [Vue warn]: Error in created hook: "TypeError: Cannot read property 'dispatch' of undefined"
      [...]

  ● Foo.vue › should dispatch action when created

    TypeError: _jest2.default.fn is not a function

      at Object.<anonymous> (src/__tests__/components/Foo.spec.js:19:35)

  ● Foo.vue › should dispatch action when created

    TypeError: Cannot read property 'SOME_ACTION' of undefined

      at Object.<anonymous> (src/__tests__/components/Foo.spec.js:32:19)

I'm using<EMAIL_ADDRESS>Thanks.

Some clarification: I'm guessing the problem is with Vuex mocking because of the Cannot read property 'dispatch' of undefined message. I added a log before the this.$store.dispatch and this.$store was indeed undefined.
The other two messages are worrisome too, jest.fn should be a function for sure, but I'm not sure if they are related with the store problem.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.

It looks like the error is thrown because you're trying to access a property on an object that isn't defined. You can read about hot to test Vuex in using with Vuex.

Hi, I wasn't asking a question. I understand how Vuex is supposed to be tested, I even referenced the "Using with Vuex" section in my second comment.
I'll double check that there are no mistakes on my side, but I wanted to clarify that this is, from my perspective, a bug report.

same issue ... did you solved it ? nothing on this topic in StackOverflow ( I posted an issue ..)

Hello @erwin16. In my case, the problem was that I was requiring Jest (const jest = require('jest')) and then using that for mocking the actions in the before hook. I had to use the injected global instead. But errors thrown in the before hooks don't prevent tests from running, and that made me believe that the issue was with vue-test-utils (it wasn't).

@fvictorio hi! Could you post working example please? I'm stuck with exactly this error for 2 days already.

@frutality did you solve this? My app is working, but my test is failing due to no $store on this. I did not import jest and use the injected jest instead, but I still have this issue.

@Anima-t3d honestly, can't remember. I refused to write tests for vuex-related components. It feels wrong. Only writing tests for simple components.

This is what worked for me:
<template>

</template>

// note no import of jest
import Vuex from 'vuex';
import {
  createLocalVue,
  shallow,
} from 'vue-test-utils';

import Foo from '@/components/Foo';

// add the 2 lines below
const localVue = createLocalVue();
localVue.use(Vuex);

describe.only('Foo.vue', () => {
  // add the 2 lines below
  let actions;
  let store;

  // add this before each
  beforeEach(() => {
    actions = {
      SOME_ACTION: jest.fn()
    };
    store = new Vuex.Store({
      state: {},
      actions
    });
  });

  it('should dispatch action when created', () => {
    // I forgot to add localVue and store
    shallow(Foo, {
      localVue,
      store
    });
    // change expecting a result to expect the action to be called.
    expect(actions.SOME_ACTION).toHaveBeenCalled();
  });
});

@Anima-t3d : I tried the way you have suggested for a component calling a store dispatch . Still am getting the same error 'this.$store.dispatch is not a function'.  Any other alternative ??

@arun045 Can you put your code here? Meanwhile, did you see This.$store.dispatch() is undefined Vuex?

Also had the same issue but was able to fix it with this approach:
-- MyComponent.spec.js --

import { shallowMount } from '@vue/test-utils'
import store from '@/store'
import router from '@/router'
import MyComponent from '@/components/MyComponent'

describe('MyComponent', () => {
  const wrapper = shallowMount(MyComponent, {
    router,
    store,
  })
  it('render without crashing', () => {
     ...
  })
})

 -- store.js --

import Vue from 'vue'
import Vuex from 'vuex'

const test = {
  namespaced: true,
  state: { ... },
  getters: { ... },
  actions: { ... },
  mutations: { ... },
}

Vue.use(Vuex)

const debug = process.env.NODE_ENV !== 'production'

export default new Vuex.Store({
  modules: {
   test,
  },
  strict: debug,
});

-- router.js --

import Vue from 'vue'
import VueRouter from 'vue-router'

import MyComponent from '@/components/MyComponent'

const routes = [
  { path: '/', name: 'My Component', component: MyComponent },
]

Vue.use(VueRouter)

export default new VueRouter({
  mode: 'history',
  routes,
})


move package under haystack_integrations/*

Fixes #208
See #100 for details

@masci Do we have to do this for all integrations, and this is a prototype of how to do it for other integrations?

@vblagoje we have to do similar changes to all the integrations, see #100 it contains the list


chore(deps): bump Trivy to v0.51.1

Description
Bump Trivy to v0.51.1

@simar7 Take a look, when you have time, please.

@DmitriyLewen Thanks for the PR but I'd like to have this PR merged first as it will really be great to have tests in place prior to making changes to Trivy Action. I believe @nikpivkin is almost finished with it and the PR will be merged soon.

@DmitriyLewen could you rebase on the latest main branch? I've merged the tests PR.

@DmitriyLewen I updated it here https://github.com/aquasecurity/trivy-action/pull/353 - we can close this PR


Add support of int type

At this moment database should set only integer type. Let's use alias also

Any reason why not target this PR to thedoctor0/laravel-factory-generator?


fix: upgrade to latest peerjs-python

remove stale github action

:tada: This PR is included in version 1.1.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


What namespace to indicate?

I am following the GMT getting started at:
https://eclipse-winery.readthedocs.io/en/latest/user/yml/index.html#modeling-an-application
What should one indicate in the namespace? If I follow what shown in the video I get nowhere as the Editor starts with an error and then there are no graphical elements available to draw the TOSCA model

What kind of error did the editor show? The image you posted don't show errors. These are just "info" messages.
Have you started Winery based on the instructions available here?
https://eclipse-winery.readthedocs.io/en/latest/user/getting-started.html#launching-with-docker
If you have no types for modeling you may missed to set the WINERY_REPOSITORY_URL variable at docker run ....

Before I was using the README.md instructions for the initial bootstrap.
I have now cloned restarted docker, went to a new folder without cloning
gmt into it, and simply typed:
docker run -it -p 8080:8080
-e PUBLIC_HOSTNAME=localhost
-e WINERY_FEATURE_RADON=true
-e WINERY_REPOSITORY_PROVIDER=yaml
-e WINERY_REPOSITORY_URL=https://github.com/radon-h2020/radon-particles
opentosca/winery
At the end of the process this is what I get:
[image: image.png]
With console output:
12:10:53.936 [http-nio-8080-exec-9] INFO
o.g.jersey.logging.LoggingFeature:132 log - 9 * Server has received a
request on thread http-nio-8080-exec-9
9 > GET http://<IP_ADDRESS>:8080/winery/admin/namespaces/
9 > accept: application/json
9 > accept-encoding: gzip, deflate
9 > accept-language: en-US,en;q=0.9,de;q=0.8,es;q=0.7,it;q=0.6
9 > connection: keep-alive
9 > host: <IP_ADDRESS>:8080
9 > referer: http://<IP_ADDRESS>:8080/
9 > user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
12:10:53.937 [http-nio-8080-exec-9] INFO
o.g.jersey.logging.LoggingFeature:132 log - 9 * Server responded with a
response on thread http-nio-8080-exec-9
9 < 200
9 < Content-Type: application/json
[ ]
12:10:53.942 [http-nio-8080-exec-5] ERROR
o.e.w.r.backend.AbstractRepository:121 getDefinitions - Could not read
content from file RepositoryFileReference{parent=class
org.eclipse.winery.common.ids.definitions.ServiceTemplateId /
{radon.blueprints.testing}ABMasterOnly, subDirectory=Optional.empty,
fileName='ServiceTemplate.tosca'}
javax.xml.bind.UnmarshalException: null
at
javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:335)
On Tue, 19 May 2020 at 13:01, Michael Wurster<EMAIL_ADDRESS>wrote:

What kind of error did the editor show? The image you posted don't show
errors. These are just "info" messages.
Have you started Winery based on the instructions available here?
https://eclipse-winery.readthedocs.io/en/latest/user/getting-started.html#launching-with-docker
If you have no types for modeling you may missed to set the
WINERY_REPOSITORY_URL variable at docker run ....
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/radon-h2020/radon-gmt/issues/25#issuecomment-630773154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDBKEHQGS6MYFNRSBQD5ALRSJYKVANCNFSM4NE5G5OQ
.

You were using a wrong Docker image most probably due to an outdated getting started guide. Please check the command again. However, make sure you are using the opentosca/radon-gmt Docker image.

Further, I added a hint on what to put into the "namespace" field.
Essentially it's there to group your service templates, e.g., into com.example.blueprints and/or radon.blueprints etc.

Works well now, thanks a lot.
On Tue, 19 May 2020 at 13:21, Michael Wurster<EMAIL_ADDRESS>wrote:

Further, I added a hint on what to put into the "namespace" field.
Essentially it's there to group your service templates, e.g., into
com.example.blueprints and/or radon.blueprints etc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/radon-h2020/radon-gmt/issues/25#issuecomment-630781943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDBKEA2LKHWZLCLFTAUKH3RSJ2TLANCNFSM4NE5G5OQ
.


Bots to simplify project managment

Hi folks,
I was having a look at the dependencies that we manage in the project and I saw we're quite out of sync with the most recent version upgrades for almost all dependencies:

Although it's not the perfect tool and may be not valid for certain dependencies that we want to stick to certain versions (ie, knative or kubernetes), I was wondering if we should start introducing some bot to manage dependencies, as dependabot. I think it will help us, maybe not immediately as we will have may PRs to review, but in the long run we should have good results.
Also, another bot I'd like to introduce is a stale bot in order to automatically close inactive issues. I'm finding quite difficult to browse along issues that seems are no longer needed/meaningful.
Thoughts?

I think it makes sense to use dependabot in go projects. We need to be sure to avoid update on fundamental dependencies, as you said, so +1.

Although it's not the perfect tool and may be not valid for certain dependencies that we want to stick to certain versions (ie, knative or kubernetes)

Most of the dependencies are transitively inherited from the Kubernetes version. Actually, the tree is mostly k8s / client-go > controller-runtime | Knative. As you've nailed it, we want to control these. Actually I don't think dependabot would be able to resolve the conflicts between Knative / controller-runtime, and our own schedule of k8s versions support. Not to mention k8s support by KinD for testing. So I anticipate more noise from dependabot than added-value. We can try to prove the above wrong, otherwise that'd be -1 for me.
On the other-hand, +1 for stale bot 😃.

For example, right now, we cannot upgrade to controller-runtime 0.9.0, because it depends on k8s 1.21, while the latest Knative version still depends on k8s 1.20. And client-go 1.21 introduces a breaking change. So we have to wait until Knative release a new version (the upgrade has been done in main branch recently).
From my experience, this situation happens quite often, almost at every k8s upgrade, and I don't think dependabot is capable of handling these. For instance, in your example, it suggests to upgrade to k8s 1.22.

Although it's not the perfect tool and may be not valid for certain dependencies that we want to stick to certain versions (ie, knative or kubernetes)

Most of the dependencies are transitively inherited from the Kubernetes version. Actually, the tree is mostly k8s / client-go > controller-runtime | Knative. As you've nailed it, we want to control these. Actually I don't think dependabot would be able to resolve the conflicts between Knative / controller-runtime, and our own schedule of k8s versions support. Not to mention k8s support by KinD for testing. So I anticipate more noise from dependabot than added-value. We can try to prove the above wrong, otherwise that'd be -1 for me.

Not sure how feasible and how much value it will bring, but eventually those "problematic" deps can be excluded from dependabot checks

Although it's not the perfect tool and may be not valid for certain dependencies that we want to stick to certain versions (ie, knative or kubernetes)

Most of the dependencies are transitively inherited from the Kubernetes version. Actually, the tree is mostly k8s / client-go > controller-runtime | Knative. As you've nailed it, we want to control these. Actually I don't think dependabot would be able to resolve the conflicts between Knative / controller-runtime, and our own schedule of k8s versions support. Not to mention k8s support by KinD for testing. So I anticipate more noise from dependabot than added-value. We can try to prove the above wrong, otherwise that'd be -1 for me.

Not sure how feasible and how much value it will bring, but eventually those "problematic" deps can be excluded from dependabot checks

I fear it would be equivalent to excluding 80% of the project dependencies, which would defeat the purpose of it.

I'd also argue that dependency management is too critical for a project like Camel K, that evolves in a fast-moving ecosystem, to be delegated to tools as naive as dependabot. You also miss the opportunity to learn new APIs and concepts introduced in newer versions. In that fast-moving context, a qualitative upgrade is seldom just a version bump. I'd rather keep Camel K at the cutting edge, granted it requires some worthy manual efforts from time to time, than considering Camel K already ready to ride the slope of the "plateau of productivity" 😃.

Thanks for the comments. I see the arguments and I guess we can keep the dependabot out of scope for the time being. However, I see no objections on the stale bot. If that is okey with the rest of people I'll proceed in the next days to enable it.

You also miss the opportunity to learn new APIs and concepts introduced in newer versions.

The PRs are created with links to changelog and new commits

I fear it would be equivalent to excluding 80% of the project dependencies, which would defeat the purpose of it.

it is already a win for 20% of the dependencies and does not impact the 80 other percent.

I'd also argue that dependency management is too critical for a project like Camel K, that evolves in a fast-moving ecosystem, to be delegated to tools as naive as dependabot.

I tend to think the exact opposite. Because it is a fast-moving ecosystem, we need to try to follow-up on latest versions and detect incompatibilities even faster than slow-paced projects.

For example, right now, we cannot upgrade to controller-runtime 0.9.0, because it depends on k8s 1.21, while the latest Knative version still depends on k8s 1.20. And client-go 1.21 introduces a breaking change. So we have to wait until Knative release a new version (the upgrade has been done in main branch recently).
From my experience, this situation happens quite often, almost at every k8s upgrade, and I don't think dependabot is capable of handling this. For instance, in your example, it suggests to upgrade to k8s 1.22 and controller-runtime 0.9.0, which is not possible ATM.

vote for it: https://github.com/dependabot/dependabot-core/issues/1296 (even k8s case specifically mentioned https://github.com/dependabot/dependabot-core/issues/1296#issuecomment-902195531 )

You also miss the opportunity to learn new APIs and concepts introduced in newer versions.

The PRs are created with links to changelog and new commits

I fear it would be equivalent to excluding 80% of the project dependencies, which would defeat the purpose of it.

it is already a win for 20% of the dependencies and does not impact the 80 other percent.

I'd also argue that dependency management is too critical for a project like Camel K, that evolves in a fast-moving ecosystem, to be delegated to tools as naive as dependabot.

I tend to think the exact opposite. Because it is a fast-moving ecosystem, we need to try to follow-up on latest versions and detect incompatibilities even faster than slow-paced projects.

This is exactly what we are doing. The issue statement forget to mention that very point! So it's an issue for a problem that does not really exists, and propose to apply a one-size fits all solution that is less efficient that the current process. For instance, the screenshot of the proposed upgrades is totally inapplicable, because the logic is so naive. On the other hand we did the upgrade with #2655 in less that 24 hours after it became possible.

I randomly picked some. These dependencies cannot be upgraded or they were missed? I find strange that all of them cannot be upgraded.

github.com/go-logr/logr v0.4.0  new release available since 7 july
github.com/Masterminds/semver v1.5.0  new release available since 12 September 2019
github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring 0.42.1  new release available since 23 September 2020
go.uber.org/multierr v1.6.0 new release available since 6 May
github.com/spf13/cobra v1.1.3  new release available since 1st July
github.com/operator-framework/api v0.3.8 new release available since 27 July 2020

Thanks, these are the 20% :D If it's possible to configure an allow list for these dependencies, so that all the noise generated for the 80% is avoided, we'll be happy to access a PR.

You also miss the opportunity to learn new APIs and concepts introduced in newer versions.

The PRs are created with links to changelog and new commits

I fear it would be equivalent to excluding 80% of the project dependencies, which would defeat the purpose of it.

it is already a win for 20% of the dependencies and does not impact the 80 other percent.

I'd also argue that dependency management is too critical for a project like Camel K, that evolves in a fast-moving ecosystem, to be delegated to tools as naive as dependabot.

I tend to think the exact opposite. Because it is a fast-moving ecosystem, we need to try to follow-up on latest versions and detect incompatibilities even faster than slow-paced projects.

This is exactly what we are doing. The issue statement forgets to mention that very point! So it's an issue for a problem that does not really exists, and propose to apply a one-size fits all solution that is less efficient than the current process. For instance, the screenshot of the proposed upgrades is totally inapplicable, because the logic is so naive. On the other hand we did the upgrade with #2655 in less than 24 hours after it became possible.

Just a note about the screenshot. It was an example taken from VSCode to illustrate the issue :) . It has nothing to do with dependabot and the suggested changes may not be what the bot would pick up.

Just a note about the screenshot. It was an example taken from VSCode to illustrate the issue :) . It has nothing to do with dependabot and the suggested changes may not be what the bot would pick up.

Right, I think the issue also fails to identify the problem at hand, which is reducing the latency there could be between the time an upgrade is possible and it's actually done. From that standpoint, I think the project has been doing well as with #2655 , granted it's for the 80% most important dependencies. And for these, I still fail to see how dependabot would help.


prompt user for more input

profile questions
name
git hub account name
about me
project questions
project name
project description
programming languages
project link

did dis stuff


The testing result is bad

hi，
I have used best_model and its config on the LRS2 data set provided by you, used the LRS2 data set provided by you and conducted pre-processing, but the test index is poor, as shown in the figure below

could you please provide some advice or help?
thanks!

I think it may be that the pre-training of your model is not loading correctly.


Using MXParallaxHeader in UITableView with headers

Hi there,
I'd like to use MXParallaxHeader in my UITableView, which worked great until I started adding section headers.
The section header anchor point seems to be at the end of the ParallaxHeader, so the section headers stop there. Moreover the passed headers are moving above the HeaderView.
Is there a way to change this behaviour or a workaround?
Thanks in advance!

I'm after the same functionality. Did you manage to solve this @iDevo?

The support of table view with sections have been removed because it removes the header touch on upward position, please refer to #40. As a workaround, you can embed your view controller in a MXScrollViewController, I havent tried yet but it should work.

I did manage to make it work right  by creating a scrollview and adding to it MXParallaxView and UITableView. But what I've notice is that when user start scrolling it accidently recongnize gesture as tap not swipe and calls actions like didSelectRow:
I think it's because both delegates of scrollview and tableview are hinder each other.
Do you have any ideas how to fix it?
And thanks a lot for this project! Great job!

You have the same issue with me.
In my case, I change tableview style plain to group. After that, set background for tableview and set height for header and footer in section in tableview delegate.
Hope this help.

I have the same issue with section header.
In my case, i change table view style plain to group. After that, set heightForHeaderInSection, heightForFooterInSection in tableview delegate. The section header will not sticky when scroll.
Hope this help!

@maxep How would u go about embedding the viewController in in the MxScrollViewController

i Solved by         contentView.layer.zPosition = 1

@jeremypiednoel @minhchau273 on & in MXParallaxHeader/MXParallaxHeader.m - (void)layoutContentView method . write objc c equivalent code ( tableView.parallaxHeader.contentView.layer.zPosition = 1) at bottom of function.


Trivial grammatical fix to README

*sigh* Why am I doomed to keep making this same mistake over and over and over...!? 😫
Thanks you for the fix. 👍


Add CSS styling support

This PR adds CSS styling support by implementing CssProvider, StyleProvider, and StyleContext. An approach similar to that used with WidgetTrait was taken. get_screen is also implemented for WidgetTrait so this screen can be used with StyleContext::add_provider_for_screen.
There are some TODOs in the code for adding the proper #![feature] attributes. The Gtk documentation doesn't give this number for every method/class, and I think this is due to a lack of documentation, not the fact that the method/class was introduced before gtk3. How should I find these feature numbers?

Very nice work ! =D
@gkoz: Code looks fine for me, I'm waiting your review. ;-)

Since you use impl_GObjectFunctions! I don't think there's a need for FFIStyleProvider.
The reference counting isn't handled well but I guess this will be fixed by the objects reform.
If the minimum GTK version for a method or class isn't specified it's safe to assume that it's present in GTK 3.4, which is the lowest version we support (also 'since 3.0' and 'since 3.2' can be ignored).

Ok, fixed.
One more question: The gtk_style_context_add_provider method takes a guint method but I pass in an enum. Could the size mismatch cause a problem?

The gtk_style_context_add_provider method takes a guint method but I pass in an enum. Could the size mismatch cause a problem?

I believe a lot of the definitions currently assume that sizeof(c_enum) == sizeof(c_int) but here we can avoid that assumption by making the ffi type c_uint and casting the enum to c_uint in add_provider. What if someone wanted to pass a value in between the constants (e.g. 117) though?

What if someone wanted to pass a value in between the constants (e.g. 117) though?

Should I add another variant called CustomPriority(u32)?

Should I add another variant called CustomPriority(u32)?
It would not be a C-like enum any more so you'd lose any conveniences and some derived traits. And anyone could put 100 or 200 there etc. Maybe simply using constants is the way. Or we could leave the type as u32 and tell the users to do the casting themselves if they want predefined values.

Ok, I think I'll change the type to a u32 and convert the enum into constants.

Ok, I added the constants. You can access them with gtk::traits::style_provider::PRIORITY_USER, as I decided not to export them.

I also just added a commit that documents the priorities. I copied the documentation directly from the Gtk docs.

You can access them with gtk::traits::style_provider::PRIORITY_USER, as I decided not to export them.

It looks like we're going to reexport all symbols in the top namespace and the names would have to be longer in that case, e.g. STYLE_PROVIDER_PRIORITY_USER.
We may want to investigate using associated constants -- they seem to be available in the nightlies. Example: https://github.com/rust-lang/rust/blob/master/src/test/run-pass/associated-const-inherent-impl.rs

It looks like we're going to reexport all symbols in the top namespace and the names would have to be longer in that case, e.g. STYLE_PROVIDER_PRIORITY_USER

Why not just use proper namespaces?

We may want to investigate using associated constants -- they seem to be available in the nightlies. Example: https://github.com/rust-lang/rust/blob/master/src/test/run-pass/associated-const-inherent-impl.rs

StyleProvider is a trait here, so it wouldn't work. Maybe after object reform?

We may want to investigate using associated constants -- they seem to be available in the nightlies. Example: https://github.com/rust-lang/rust/blob/master/src/test/run-pass/associated-const-inherent-impl.rs

StyleProvider is a trait here, so it wouldn't work. Maybe after object reform?

Err, actually if you can provide default values for constants (which wasn't in the documentation), than we could do this.

Why not just use proper namespaces?

Some reasons here: https://github.com/rust-gnome/glib/pull/47#issuecomment-112803730
It may just be a fool's errand to try to add structure to all of GTK because it's too diverse. While converting every module to the new framework I find it very difficult to organize them coherently. An arbitrary mediocre structure may be worse that the flat convention.

I guess, we could also just have a flat series of modules (gtk::widget, gtk::button, gtk::style_provider, etc) and have constants live there. I'm not enthusiastic about this approach.

Ok, I just left them as normal constants.

I guess we can reexport these consts in the root module now.
Otherwise seems okay to merge. Small style nits I'd just tweak in the process of refactoring.

Oops, forgot to reexport. Fixed.

:+1:
@GuillaumeGomez

@gkoz: Thanks for taking care of this one and helping him !
@gsingh93: Thanks for your work !


Source Switcher doesn't work on Edge 16

i think problem with this part of player
player.videoSources.forEach(function(source) {
                        if (source.title == videoChangedTo.innerText) {
                            player.setBuffering();
                            player.setVideoSource(source.url);
                        }
                    });

I can reproduce the issue @gibigate, marked this as a bug to be looked into.

Hi @gibigate, your fix for this issue went live with v2.4.0. Thanks for your contribution! Closing issue.


clue: Refactor Anagrams into builder model

Implementing the next set of @emerald000 changes. First, convert the Anagram clue scroll object creation into builders.
Why Builders?
The original method served us well for basic data about each clue scroll. However, the proposal to implement suggested teleports (and auto checking requirements for those teleports) requires a more malleable form of building each clue scroll's properties. Feel free to take a look at the original commit as an example.
Why not do them all at once?
I would like to, except each clue type is fairly unique in its requirements. Not only that, but for each clue type, I manually (or via scripts I write myself) verify the correctness of the data. I also use the scripts to rebuild the data-set in builder format. This takes time to do, and in a world where new clue scrolls can be added any time, I believe it is prudent to merge structural changes in sooner, rather than later.
What else has changed in this PR?
Fix a small bug -- when objectId is -1, return an empty array instead.
We also update some area descriptions for anagram clues. These are purely opinionated, and largely come from emerald000 or myself. Feel free to suggest edits to these descriptions.

@Nightfirecat do you mind reviewing specifically the area description updates in this?

@Adam- @Nightfirecat approved the area description changes. I think this is ready to land. I'll be moving onto map clues next.


Error loading page Domain: NSURLErrorDomain Error Code:-1004 Description: Could not connect to the server

Bug description:
According to my user feedback, when I visited a domain name page I gave through webview on my ios mobile phone,webview suddenly gave an error message as shown in the following during the visit:
Error loading page
Domain: NSURLErrorDomain
Error Code:-1004
Description: Could not connect to the server
wath happen?
At first, the user was able to access normally, but later in the process, this prompt suddenly popped up
To Reproduce:

Expected behavior:

Screenshots/Videos:

Environment:

OS: ios
OS version: ios 15.6 (but not 100%)
react-native version: 0.70.5
react-native-webview version: ^11.23.1

Sounds like the phone couldn't connect to the server.


Added C# binding

Hi,
I've made a C# binding Standard library based on the 3.2.0 version of the H3 library.
It is available here: https://github.com/entrepreneur-interet-general/H3.Standard
A related nuget package has been released:
PM> Install-Package H3 -Version 3.2.0-alpha.

Cool, thank you! Closing this as a dupe of the pull request #155.


Use addEventListener instead of deprecated API addListener

Note:  Minimum version of safari supported for this API should be 14.

@ad1992 what's the purpose of the latest change, and why was it made here :smile:? Anyway, as per our discussed, let's close this PR as I don't see we'll be merging it any time soon.

@ad1992 what's the purpose of the latest change, and why was it made here 😄? Anyway, as per our discussion, let's close this PR as I don't see we'll be merging it any time soon.

My old habit of reusing the same branch name made me overwrite this branch :D.


Add ToJson/ConvertToJson method to parse existing H5 file

Add a top level method to receive a file name and output a Json object of the file content.

closing for now. not a lot of benefit


Updated README with guided demos and videos

Issue link
#286
What changes have been made
Added guided demos and video to README
Verification steps
Make sure the links all work, and that there are no typos
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[x] Testing is not required for this change

@MichaelClifford is the only person who can approve this


Todo: Fix webpack issues currently active on the project

These issues are present in the webpack pipeline for local dev server and when building for production. They should be easy to fix so I am making an issue here to track so we can do so 👍.
I'm not sure what introduced the less files (something in antd) but it's a file loader issue and it doesn't look like Create React App supports less loading out of the box...
The ESLint warnings are easy to fix, however.

I was able to clean up the terminal in #50 on branch aws_regions.


Bug: can not get last_flushed_decree from meta cf occasionally when rolling_update from 2.0.x

Bug Report
When rolling_update Pegasus server from 2.0.0 to 2.2.0, replica server generate a coredump that could not find the last_flushed_decree occasionally.

Basic background
In Pegasus 1.x version, each write request will write request-decree into RocksDB Manifest file, which is hard for us to upgrade RocksDB official new release. To remove this logic, Pegasus firstly release 2.0.0, which will write request-decree both into Manifest file and RocksDB column family called meta, and read it from Manifest file. In the following release 2.1.0, 2.2.0, decree will only be read and wrote through meta column family.
When and how will it happend
When the cluster upgrade Pegasus from 2.0.0 to higher version(for example 2.2.0), the bug will be happened satifying all following conditions:

Cluster has a table doesn't trigger flush memtable after upgrading to 2.0.0
One partition of this table is not close gracefully when upgrading to 2.2.0 (When close function called, partition will flush memtable, inluding meta column famlity, decree would be found while reopen RocksDB instance).

How to avoid it
To avoid this bug, we should gurantee partitions would be closed gracefully in upgrade process.


Fix test workflow, bis

This is a continuation of @ogonkov's work at #4251, which I'm personally pushing directly to the main  repo in order to rule out any effects from permissions. I also wanted to try a couple of things. If I end up merging this branch, #4251 will automatically be recognized as merged as well.

@ogonkov @paulfalgout I got the Sauce Labs tests to run, mostly reliably, with the exception of Firefox 11. See the details of the above (failed) workflow run.
If you agree with the logic changes you see here, we can merge this. However, we need to make a decision about the lowest Firefox version.
The tests do pass in Firefox 11, as you can see on Sauce Labs: https://app.eu-central-1.saucelabs.com/tests/08d1010d4bea46dda25b29f2a6a9a698. However, something is going wrong in the connection with Karma. I tried this on a couple of OS versions and I had a single attempt on Windows 10 where the connection suddenly worked (run 53). So far, I haven't been able to reproduce this, but this is the reason why the karma.conf-sauce.js currently lists Firefox 11 with Windows 10.
I also tried Firefox 18, 25 and 32, but they all behaved similarly flaky, although versions 18 and 32 eventually succeeded on second attempts. See run 55.
I see three possible courses of action:

Keep Firefox 11 and accept that it will fail on most runs.
Drop Firefox 11 without replacement, making 40 the oldest version. This would mean that we are only testing relatively recent versions of Firefox.
Find a version between 11 and 40 with a better tradeoff between reliability and age. This can be done with a "quadrisect" (cf git bisect) where 18-25-32 was the first recursive step.

Please let me know what you think!

Can you run sause labs config with config.LOG_DEBUG? May be we get more info about what exactly the problem is

That was a good suggestion. The visible difference between FF11 and the other browsers was that FF11 was creating additional socket connections and then immediately closing them again. I tried increasing Karma's browserDisconnectTimeout, but that only seems to lead to accumulation of even more sockets.
Haven't been able to find a solution for "Response has empty body" or "Request failed with status 204" yet. Still searching the web.

Some requests (which one?) has been responded with empty body, that was unexpected for client. There also warn about old client. May be it is something related to old client, used by plugin?

Yes, good suggestion. I was just considering to upgrade the devDependencies in case that's playing a role. Will do that now.

@ogonkov Upgrading the dependencies doesn't seem to have improved matters much, except that there is more debug log output. I'm tired now, so I'll resume this chore at a later date.
If you have any ideas in the meanwhile, please feel free to submit a PR to the patch-1 branch on my fork. I'll merge it as soon as I see it and push it to the main fork, so it will run in here with full permissions.

@ogonkov I'm just going to remove Firefox 11 for now, so at least we have something to work with. I will create a new issue ticket to document the open challenge.

I'm stuck again because Sauce Labs hasn't converted my trial account to Open Sauce yet and my trial has run out of testing minutes. To be continued.

Update: I haven't heard back from Sauce Labs since January 17. I just made a third attempt at reestablishing contact, using a different email address.

Update again: they finally enabled Open Sauce, so we can run browser tests again. I will resume the debugging labour soon.

Open Sauce doesn't seem to be really enabled. To be continued...

May be we can mark sause labs tests as non blocking for workflow and merge it in master, to fix units in PRs?

Yes that makes sense. Good idea. How do you do that?

High five!


Update .gitignore for AppCode

Add .idea to ignore AppCode files.

I think that the individual developer should be responsible for managing the gitignore for their editor of choice. I'd recommend just using a global ~/.gitignore for your editor and you won't need to add this to any of your projects :smile:


chore(master): release 1.0.1

:robot: I have created a release beep boop
1.0.1 (2023-10-23)
Bug Fixes

build script (7ef7faf)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ScribeLabsAI/ScribeMiNode/releases/tag/1.0.1 :sunflower:


Compatibility issue with Thaumic Energistics

Thaumic Energistics crashes when Mekanism is added while using Cauldron.
http://pastebin.com/8GuwKKyg

This is actually rooted in AE2 compatibility.  Not on my end.


Why is admin > 6.6 needed?

The problem
Hi,
Why is admin version 6.6 needed, while 6.3 is official?
Version of nodejs
20
Version of ioBroker js-controller
N/a
Version of Adapter
0.5.1
Operating system running ioBroker
Linux
Checklist of files to include below

[X] iobroker.current.log (Please share the logs in debug mode)
[X] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads
No response

Same here. I am unable to use this adapter on a Pi4 with ioBroker image because admin is on 6.3.5

I suppose, it has something to do with the admin itself - it changed the depency to admin 6.3, but I am not able to create any custom app. Notification can be sent to the clock.

But how can I update to admin 6.6 with the official pi 4 image?

Then, beta repository

Developing adapters is so much fun.... people add feature requests over feature requests and want more and more features... so the configuration in a table component wasn't possible anymore
So I've invested some days (!!!) to create a new jsonConfig Component for the admin (= accordion). And this component is devlivered with admin >= 6.6.0. And after all, I have to explain why I did that... 😞
You can use an older version of the admin adapter, but you won't be able to create any app (since the component is missing).

You have to install the adapter via beta repository. Just don't use GitHub installs and you don't have problems (since you also get the newest admin beta in that case)

i changed the depency to admin 6.3

Hint: The dependency wasn't set to >= 6.6.0 to annoy you. That's not very smart

Thanks. The hint to the beta repo helped. And regarding this:
Developing adapters is so much fun.... people add feature requests over feature requests and want more and more features...
When you start a open-source project, and it becomes successful, you start as the entrepreneur and end up as the janitor.  Made the same experience with some of my projects (mtoensing/Docker-Minecraft-PaperMC-Server and mtoensing/simpletoc) So my decision was: keep it simple. Don't add everything just because you can. And don't merge every PR. Or the codebase will get so big that nobody, including you, can handle it. It is better to have something small that is maintainable rather then to sit on a pile of s... that no one can update. =) But this is just my opinion.

So my decision was: keep it simple.

Indeed. But: It is simple. Just use the beta repository and fulfil the dependencies 😄
No fancy GitHub installations, just 2 clicks.

I did want to offend you. You did everything right. As i said: After you told me about the beta repo everything is fine.
I commented on your sentence about feature requests from the community and so on. I related to that. =)


Shrinkwrap dependencies

We want to make try and protect users from supply chain attacks similar to incidents we've seen in the past (specifically rc and ua-parser-js hijacking [1, 2], colors sabotage 3). We can use a shrinkwrap file to do this [4], by distributoing npm-shrinkwrap.json in our package users who install the kit will install the same dependency tree as we develop with, meaning we can audit dependency updates for them.

I thought it would just be a case of running npm shrinkwrap, but of course, with Node.js it's never that simple 🤦
It turns out with older versions of npm there are two major downsides to shrinkwrap; one is that it makes npms deduplication work less well, and two is that npm will install dev dependencies from the shrinkwrap file. These problems are likely to affect users with older installations of Node. This will mean users with older versions of npm will get a larger node_modules folder than necessary. The kit should still work fine though.
Another fun issue is that Node 12 and 14 still ship with those older versions of npm, and in our tests another issue with shrinkwrap breaks the kit installation script. It seems that npm@6 doesn't like it when we install a directory with a shrinkwrap file 🤷 But it can handle installing a tarball with a shrinkwrap file. So if we want to use shrinkwrap and keep the install script the way it is we could change our tests to use a tarball, or upgrade npm before running our CI tests, or stop testing Node 12 and 14.

We've dropped support for Node 12 and 14 (see #1753), which means testing this change is no longer an issue. Merging.


backend/s3: Unnecessary copy on member access

Hi,
In restic/backend/s3/s3.go the Load, Save, Stat methods operate with value receiver instead of with pointer receiver. So the struct s3 is copied on every method access.
Is this safe to convert to pointer receiver?
Or was it intentional? The main item in the struct is *minio.Client which, as a pointer member, won't have its data copied anyway.

Hi, thanks for pointing this out. I think that this will not impact performance at all, neither will the memory usage rise or fall when changing this. But you have a point, it's at least inconsistent. If you like, please create a pull request.

I'll close this PR for now, I don't think it's relevant.


Timer event documentation link leads to "Page not found" for a brief period

Issue reference: https://github.com/camunda/camunda-modeler/issues/2413
Comment reference: @MaxTru  https://github.com/camunda/camunda-modeler/issues/2413#issuecomment-919068364
Describe the Bug
On clicking the documentation link in the timer event, for a short period "page not found" message is displayed until it is redirected to the actual documentation page.
Steps to Reproduce

In the Modeler, open a new BPMN diagram for cloud and add a timer event.
Open the properties panel and click on the field Timer event.
Now click open the link "documentation: Timer events"
We could see that for a very short period "page not found" is displayed until the actual documentation page is displayed.

Expected Behavior
On clicking the link it should directly lead to the documentation page without any error page popping up.
Environment
OS: [Windows 10]
Camunda Modeler Version: [4.10.0]
Execution Platform: [Camunda Cloud]

According to @MaxTru's comment on the original issue, there is a small fix.
Is it okay if I try to fix it?

@chincholikarsalil Please go ahead!

Related to https://github.com/camunda/camunda-modeler/issues/2413


Fixed counter bug using an extra counter, incremented in view and vie…

Includes tests that fail without the fix.
The extra counter is a little unsatisfying though, given that the required value is in the cascading counter for the last stage of the flow already.

 It refers to squashed commits?

Can you bump the minor version number.

@stephanh Okay, I've addressed all those comments, and rebased.

:+1:


Readme.md is outdated

Nuff said. Trying to use redux-loop, and can't find any examples of usage. Npm readme is missing, and even readme in the master branch of this repo is 50% useless. And after couple of hours I found out that the only good doc is in 3.0 branch. Could you guys please update the readme or even merge the master with 3.0?

Yeah it's too bad, this is a pretty sweet project. Just seems like it's fallen behind a little. Maybe the core contributors have fully moved on to Elm :)
In any case, @lukewestby would love to help out if there were some like "required-for-3.0-official-release" issues we could knock out.

I would be happy to help get this project going again, @lukewestby is there anything that we can do to help move things along?

Hi everyone.
Sorry it's been so long since you've heard back. I'm going to be taking over maintenance of redux-loop. I'd like to get an update out in the next few days.
I know there have been a few proposed API changes in the last year. I've been using a fork of one those proposed version 3's for a while in projects that I've worked on (https://github.com/bdwain/redux-loop). I'd like to make that the starting point for any future changes. Luke and I discussed these changes last year and I think it'll be an improvement over version 2 without being too drastic of a change for people who are currently using it. It doesn't have typescript typings yet, but I would like to add that in the next few days as well.
The main idea behind the changes in my branch can be seen here in this issue . It's passing action creators to effects/cmds instead of putting them in your side effect functions. Though since that discussion, i've consolidated some of the Cmd types.
I'll keep this issue open for now and close it when I've got everything updated. Sorry again for the delay!

Version 3.0 has been released. Sorry for all of the confusion. Details about the new features (since version 2) can be seen here.


The Semantic Head

Thanks for your excellent work! I'm trying to reproduce this repo recently! I found that The Sementic Head which is defined as part_classifier in the main_solider.py is seemly not optimized, could you please explain why? By the way, could you please provide the supplementary materials of the cvpr paper？

The Sementic Head is actually trained in SOLIDER in the student branch. And the supplementary materials can be found on CVF Open Access.

Thanks for the supplementary materials! But I still can't find where the semantic head is trained and optimized in the source code of main_solider.py. Could you please point it out?


Document value of _Alignof(max_align_t) on RV32G and RV64G

Closes #104.

I think this should depend on ABI and not architecture.  And if it does depend on the architecture, then you have to use the base architectures rv32i, rv64i, and rv32e instead of rv32g and rv64g.  But probably simpler to just state unconditionally that it is 16 for now, because that is correct for all current ABIs.

@jim-wilson We do have options. For example, iff we wanted to make, e.g., long double or __int128 "optional" in some architectures, or give them an alignment requirement lower than 16 on some architectures, then it would make sense to make _Alignof(max_align_t) architecture-dependent.
AFAICT, we want to require long double and __int128 for all architectures, and at least long double is always going to have an alignment requirement of 16. So if this is the case, making this unconditional, makes the most sense. Do you agree?
If so, I'll amend the commit to remove the "for RV32G and RV64G" part, and leave this guarantee as unconditional.

We don't have options.  The ABI was fixed when we upstreamed glibc.  We can't change it now (except in case of dire emergency).  At least that is true for rv64.  The rv32 glibc hasn't been upstreamed yet, but changing the ABI would still be disruptive and should be avoided.  So no ABI changes.  We can only document what the ABI already is.  You can see what the ABI already is by compiling small testcases with gcc.
Assuming that we need to document what max_align_t is.  I've been looking for evidence of that, the older x86 psABIs I pointed at don't document this, but I found newer ones at
https://github.com/hjl-tools/x86-psABI/wiki/X86-psABI
I don't see a mention of max_align_t, but maybe this value is implied somewhere.  I will have to try reading it tomorrow.

I don't see a mention of max_align_t, but maybe this value is implied somewhere. I will have to try reading it tomorrow.

See: https://gitlab.com/x86-psABIs/x86-64-ABI/blob/master/x86-64-ABI/low-level-sys-info.tex#L149

So I see that they moved from github to gitlab, and left all of the github stuff behind to confuse people like me.  Looking at the correct docs on gitlab now, I see that 6 days ago HJ added docs for max_align_t.  You filed this request 7 days ago which is interesting timing.
Anyways, yes, the latest revision looks correct, and adds something already present in the x86-64 psABI docs, so we should add it to the RISC-V psABI.


Feat applause button

Fix #537
Fix #532

Thanks a ton for this. Sorry for improper code ( I think I need to learn more about elegant structure .e.g code placement and use of jinja macro)
it works great:

Maybe the cause of previous problem is we need to close the tag.

Maybe the cause of previous problem is we need to close the tag.

I think that was because of including CSS incorrectly.

I think that was because of including CSS incorrectly.

Oh.
Sorry, I want to ask:

instead of merging this PR, why do you still need to open new pr #541 ?
how do you move my commit in my previous pr to this pr. using cherry-pick?

instead of merging this PR, why do you still need to open new pr #541 ?

I mistakenly opened it against the master branch. All PR should open against next branch.
Next branch  is merged to master only when releasing a new version.

how do you move my commit in my previous pr to this pr. using cherry-pick?

Downloaded the patch (just add .patch to any PR url) and then applied it.

I mistakenly opened it against the master branch. All PR should open against next branch.
Next branch is merged to master only when releasing a new version.

Oh, I don't spot that. I thought it's a form of 'trick'

Downloaded the patch (just add .patch to any PR url) and then applied it.

Yeah, This my way too. I just ask to gain new knowledge, cause you did it so fast :), I thought there were other tricks.
Thank you.


Crash - SIGABRT: malloc_consolidate(): invalid chunk size

Today my Ambilight didn't work for first time in weeks. Webinterface of HyperHDR was unreachable so couldn't get to any logs. This is all I could find:
<EMAIL_ADDRESS>- Hyperion ambient light systemd service  for user pi
   Loaded: loaded<EMAIL_ADDRESS>enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-12-29 18:33:25 CET; 1 weeks 0 days ago
 Main PID: 13262 (hyperiond)
    Tasks: 16 (limit: 4915)
   CGroup<EMAIL_ADDRESS>           └─13262 /usr/bin/hyperiond

Jan 05 13:17:54 pi4 hyperiond[13262]: malloc_consolidate(): invalid chunk size
Jan 05 13:17:54 pi4 hyperiond[13262]: Hyperion caught signal :SIGABRT

It seems to work fine again after restart.
Hardware
Pi4 4Gb running latest Raspberry OS
HyperHDR v<IP_ADDRESS>
WLED Controller Type
USB HDMI Grabber
System
HyperHDR Server:

Build:           (HEAD detached at d35314e) (GitHub-9795cc8/d35314e-1608750238)
Build time:      Dec 23 2020 20:19:43
Git Remote:      https://github.com/awawa-dev/HyperHDR
Version:         <IP_ADDRESS>
UI Lang:         auto (BrowserLang: en-GB)
UI Access:       expert
Avail Capt:      v4l2
Database:        read/write

HyperHDR Server OS:

Distribution:   Raspbian GNU/Linux 10 (buster)
Architecture:   arm
CPU Model:      ARMv7 Processor rev 3 (v7l)
CPU Type:       Raspberry Pi 4 Model B Rev 1.2
CPU Revision:   c03112
CPU Hardware:   BCM2711
Kernel:         linux (5.4.79-v7l+ (WS: 32))
Qt Version:     5.11.3
Python Version: 3.7.3
Browser:        Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.101 Safari/537.36

Did you run some action just before the crash for ex. change the resolution or some other setting? Did you use the live video preview in the WWW then?

Did you run some action just before the crash for ex. change the resolution or some other setting? Did you use the live video preview in the WWW then?

No, I wasn't using the webinterface at all. Hardly touching it. It just runs on my Pi which is always on and yesterday the LEDs suddenly just didn't respond anymore. I don't know what I was doing around 13:17:54 because my WLED only turns on when the sun is down, so didn't notice it at the time it crashed. So not much info, but wanted to share it anyway.

No, I wasn't using the webinterface at all. Hardly touching it. It just runs on my Pi which is always on and yesterday the LEDs suddenly just didn't respond anymore. I don't know what I was doing around 13:17:54 because my WLED only turns on when the sun is down, so didn't notice it at the time it crashed. So not much info, but wanted to share it anyway.

OK, thanks anyway. After reviewing code related to that crash (around 'free' and memory allocation) I found some inconsistency in one, quite important module. But I'm not sure if that was the cause of that crash.

OK, thanks anyway. After reviewing code related to that crash (around 'free' and memory allocation) I found some inconsistency in one, quite important module. But I'm not sure if that was the cause of that crash.

If there is any way I can provide you with more logs, let me know. I don't know where to find the logs expect through the webinterface, which is kind of useless when it crashes. Any way to log this to a file?

If there is any way I can provide you with more logs, let me know. I don't know where to find the logs expect through the webinterface, which is kind of useless when it crashes. Any way to log this to a file?

You can run it not as a service/deamon but execute "/usr/bin/hyperiond -d" instead and leave it for example under "screen" or redirect output to the file.

You can run it not as a service/deamon but execute "/usr/bin/hyperiond -d" instead and leave it for example under "screen" or redirect output to the file.

Had the same happening yesterday. Mighy have been exactly at the point I turned on my TV + Receiver with HDMI grabber on one of the monitors. Not sure since again I discovered later it has crashed.

Had the same happening yesterday. Mighy have been exactly at the point I turned on my TV + Receiver with HDMI grabber on one of the monitors. Not sure since again I discovered later it has crashed.

Please compile HyperHDR in the debug (not default release) mode, run it as a program (not service) and attach log to this report when/if that crash happens. Maybe that would provide come clues. HyperHDR is a complex. multi-threaded program that uses many external and system internal components. As I'm unable to reproduce it on my systems (both linux and windows, maybe your unique configuration or running service for a few days play some part in it) searching for possible reason is like searching for a needle in a haystack. As you can see chances for succeed are slim and as it's a very rare problem I'd prefer to spend my resources to implement new features. And as I checked in valgrind there is no obvious memory leak/access in the HyperHDR itself.

Please compile HyperHDR in the debug (not default release) mode, run it as a program (not service) and attach log to this report when/if that crash happens. Maybe that would provide come clues. HyperHDR is a complex. multi-threaded program that uses many external and system internal components. As I'm unable to reproduce it on my systems (both linux and windows, maybe your unique configuration or running service for a few days play some part in it) searching for possible reason is like searching for a needle in a haystack. As you can see chances for succeed are slim and as it's a very rare problem I'd prefer to spend my resources to implement new features. And as I checked in valgrind there is no obvious memory leak/access in the HyperHDR itself.

I completely understand. I just never have compiled it myself and don't really know how to do this, but will look into it.

I completely understand. I just never have compiled it myself and don't really know how to do this, but will look into it.

Instruction are here: https://github.com/awawa-dev/HyperHDR/blob/master/CompileHowto.md
1 After preparing build environment  & download sources from git (as per the instruction, before building) you must stop HyperHDR service. It MUST NOT be running all the time
 sudo systemctl stop<EMAIL_ADDRESS>2 configure project in DEBUG mode (assume that you are in the build folder as per instruction)
cmake -DCMAKE_BUILD_TYPE=Debug ..
3 make it:
make -j $(nproc)
4 run it and wait for possible crash, then log the output from the console:
bin/hyperiond -d
or redirect output to the file for example: /bin/hyperiond -d > /tmp/hyperhdr.log
5 ssh terminal must be opened all the time. Otherwise after disconnecting that process is killed. To overcome this you can use standard Linux util: 'screen'

Instruction are here: https://github.com/awawa-dev/HyperHDR/blob/master/CompileHowto.md
1 After preparing build environment  & download sources from git (as per the instruction, before building) you must stop HyperHDR service. It MUST NOT be running all the time
 sudo systemctl stop<EMAIL_ADDRESS>2 configure project in DEBUG mode (assume that you are in the build folder as per instruction)
cmake -DCMAKE_BUILD_TYPE=Debug ..
3 make it:
make -j $(nproc)
4 run it and wait for possible crash, then log the output from the console:
bin/hyperiond -d
or redirect output to the file for example: /bin/hyperiond -d > /tmp/hyperhdr.log
5 ssh terminal must be opened all the time. Otherwise after disconnecting that process is killed. To overcome this you can use standard Linux util: 'screen'

The issue has not appeared again, so it's probably some weird edge-case scenario. I will install the new version nonetheless.

I'm not sure it's related but this what I have after an HA command:
May 14 21:52:35 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:35.087 V4L2:AUTO              : <INFO> Video FPS: 20.02, av. delay: 64ms, good: 1201, bad: 0 (60.04,15)
May 14 21:52:51 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:51.871 HYPERHDR               : <DEBUG> PriorityMuxer.cpp:162:registerInput() | Register new input 'Home Assistant@::ffff:<IP_ADDRESS>/COLOR' with priority 128 as inactive
May 14 21:52:51 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:51.872 HYPERHDR               : <DEBUG> PriorityMuxer.cpp:208:setInput() | Priority 128 is now active
May 14 21:52:51 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:51.872 HYPERHDR               : <DEBUG> PriorityMuxer.cpp:378:setCurrentTime() | Set visible priority to 128
May 14 21:52:51 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:51.872 HYPERHDR               : <DEBUG> HyperHdrInstance.cpp:550:handlePriorityChangedLedDevice() | priority[128], previousPriority[240]
May 14 21:52:51 hyperhdr hyperhdr[28092]: 2021-05-14T21:52:51.873 IMAGETOLED             : <DEBUG> ImageProcessor.cpp:180:setHardLedMappingType() | set hard led mapping to multicolor_mean
May 14 21:52:51 hyperhdr hyperhdr[28092]: QJson: Document too large to store in data structure
May 14 21:52:51 hyperhdr hyperhdr[28092]: malloc(): unsorted double linked list corrupted
May 14 21:52:51 hyperhdr hyperhdr[28092]: Hyperion caught signal :SIGABRT

Web UI was stuck after that and I had to restart the HyperHDR daemon.

Don't know if it's related either. Seems there is no defense on external data overload or an incompatible structure was sent and it should be done better in HyperHDR. Could you provide me more information about a path to reproduce the problem using HA?

Don't mean to reopen a can of worms but I may be able to provide more information on this problem. I encountered the same error when upgrading my capture card. I tried restarting the service but it did not help. From my dmesg logs the issue may be a result of a failed capture card initialization.
Environment:
RPi4 Model B
OS: 32-bit rasbian lite (Linux raspberrypi 5.10.17-v7l+ #1414 SMP Fri Apr 30 13:20:47 BST 2021 armv7l GNU/Linux)
WS218x PWM Driver
Logs
Here is my journalctl:
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.695 hyperiond JSONSERVER   : <DEBUG> JsonServer.cpp:28:JsonServer() | Created instance
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.696 hyperiond JSONSERVER   : <INFO> Started on port 19444
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.702 hyperiond LEDDEVICE    : <INFO> Start LedDevice 'ws281x'.
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.702 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:148:init() | deviceConfig: [{"colorOrder":"grb","currentLedCount":183,"dma":10,"gpio":1
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.702 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:413:setLatchTime() | LatchTime updated to 0ms
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.702 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:438:setRewriteTime() | Refresh interval = 1000ms
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.703 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:444:setRewriteTime() | RewriteTime updated to 1000ms
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.703 hyperiond LEDDEVICE    : <DEBUG> LedDeviceWS281x.cpp:65:init() | ws281x strip type : 1050624
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.703 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:41:setNewComponentState() | Smoothing: enabled
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.703 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:687:selectConfig() | cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.00
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.704 hyperiond FLATBUFSERVE : <INFO> Started on port 19400
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.704 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:687:selectConfig() | Previous line repeats 1 times
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.705 hyperiond FLATBUFCONN  : <INFO> Connecting to Hyperion: <IP_ADDRESS>:19401
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.706 hyperiond PROTOSERVER  : <INFO> Started on port 19445
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.707 hyperiond EFFECTENGINE : <INFO> Run effect "Rainbow swirl fast" on channel 1
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.708 hyperiond EFFECTENGINE : <DEBUG> EffectEngine.cpp:181:runEffectScript() | Start the effect: name [Rainbow swirl fast], smoothCfg [2]
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.708 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:165:registerInput() | Register new input 'System/EFFECT' with priority 1 as inactiv
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.708 hyperiond HYPERION     : <INFO> Initial foreground effect 'Rainbow swirl fast' started
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.709 hyperiond EFFECTENGINE : <INFO> Run effect "Fire" on channel 254
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.709 hyperiond EFFECTENGINE : <DEBUG> EffectEngine.cpp:181:runEffectScript() | Start the effect: name [Fire], smoothCfg [2]
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.709 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:165:registerInput() | Register new input 'System/EFFECT' with priority 254 as inact
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.709 hyperiond HYPERION     : <INFO> Initial background effect 'Fire' started
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.710 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:165:registerInput() | Register new input 'System/V4L' with priority 240 as inactive
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.710 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:41:setNewComponentState() | V4L capture device: enabled
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.711 hyperiond BOBLIGHT     : <DEBUG> BoblightServer.cpp:28:BoblightServer() | Instance created
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.711 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:41:setNewComponentState() | LED device: enabled
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.712 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.714 hyperiond HYPERION     : <INFO> Hyperion instance 'ws281x' has been started
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.715 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.734 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:91:handleSettingsUpdate() | Apply Webserver settings
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.734 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.736 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.737 hyperiond WEBSERVER    : <INFO> Started on port 8090 name 'Hyperion Webserver'
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.738 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:175:handleSettingsUpdate() | Setup SSL certificate
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.738 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:191:handleSettingsUpdate() | Setup private SSL key
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.739 hyperiond WEBSERVER    : <INFO> Started on port 8092 name 'Hyperion Webserver'
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.804 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:271:setInputImage() | Priority 1 is now active
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond HYPERION     : <DEBUG> BGEffectHandler.h:91:handlePriorityUpdate() | Stop background (color-) effect as it moved out of scop
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:292:clearInput() | Removed source priority 254
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond EFFECTENGINE : <INFO> Run effect "Fire" on channel 254
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond EFFECTENGINE : <DEBUG> EffectEngine.cpp:181:runEffectScript() | Start the effect: name [Fire], smoothCfg [2]
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:165:registerInput() | Register new input 'System/EFFECT' with priority 254 as inact
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond HYPERION     : <INFO> Initial background effect 'Fire' started
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.805 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:374:setCurrentTime() | Set visible priority to 1
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.806 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:687:selectConfig() | cfg [2]:  Type: linear - Time: 200 ms, outputRate 25.00
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.806 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:566:handleSourceAvailability() | priority[1], previousPriority[255]
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.806 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:577:handleSourceAvailability() | new source available -> Resume output processing and sw
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.807 hyperiond HYPERION     : <DEBUG> BGEffectHandler.h:91:handlePriorityUpdate() | Stop background (color-) effect as it moved out of scop
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.807 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:292:clearInput() | Removed source priority 254
Jan 11 02:02:00 raspberrypi hyperiond[1933]: Hyperion caught signal :SIGSEGV
Jan 11 02:02:00 raspberrypi hyperiond[1933]: 2022-01-11T02:02:00.816 hyperiond CORE         : <ERROR>         /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0xb540c130]
Jan 11 02:02:00 raspberrypi hyperiond[1933]: malloc_consolidate(): invalid chunk size
Jan 11 02:02:00 raspberrypi hyperiond[1933]: Hyperion caught signal :SIGABRT

Here is my dmesg:
[  236.912326] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  238.262367] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  238.262972] usb 1-1-port3: attempt power cycle
[  241.622301] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  242.972317] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  242.972922] usb 1-1-port3: attempt power cycle
[  246.332278] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  247.682242] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  247.682848] usb 1-1-port3: attempt power cycle
[  251.042219] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  252.392252] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  252.392858] usb 1-1-port3: attempt power cycle
[  255.752203] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  257.102175] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  257.102819] usb 1-1-port3: attempt power cycle
[  260.462119] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  261.812208] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  261.812819] usb 1-1-port3: attempt power cycle
[  265.172251] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  266.522221] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  266.522823] usb 1-1-port3: attempt power cycle
[  269.892353] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  271.242396] usb 1-1-port3: Cannot enable. Maybe the USB cable is bad?
[  271.243430] usb 1-1-port3: attempt power cycle

@ztnel I doubt since it's not even log from HyperHDR.


Develop script DuplicateServiceValidation.cs and TestPageContent.cs

Testcase:
Duplicate service. - Develop script DuplicateServiceValidation.cs and TestPageContent.cs.
Design:

Create a browser instance.
Get all service tags in the test page.
Check if there are duplicate services.
Store the names in the HashSet.
When HashSet returns false, duplicate service names are stored in another array.
Log the error message in the report, need engineer's manual check.

Result:
Link

Message:
Error Link: https://learn.microsoft.com/en-us/python/api/overview/azure/?view=azure-python.
Error Info: Have Duplicate Service: Functions.
Number of Occurrences: 1.
Locations of Errors:
Expected: True
But was:  False
@zedy-wj  and @v-xuto for notidication.

@v-xuto -  design not change, please review it, thanks.

@v-xuto - design not change, please review it, thanks.

No issue, please merge.

@zedy-wj  Please merge.


Some typings wrong compared to the API response

I'm using the PaymentMethod type to try and typecheck the API response from "list customer payment methods". The type has Card with an uppercase C, while the api returns an object that has a lowercase c. Obviously the app will crash when using paymentMethod.Card instead of paymentMethod.card. This either leaves me with an invalid typecheck, forces to use "any" instead of PaymentMethod or plain JavaScript.

What method are you using to "list customer payment methods"?

It looks like you're comparing the types of @stripe/stripe-react-native with the API response from a stripe server. @stripe/stripe-react-native doesn't have any responses containing the billing_details key. However, if you are getting that logged response directly from @stripe/stripe-react-native, please let me know how I can reproduce it


Return empty array instead of null for empty definitions result

The result of the Definition Request is Location|Location[]. LSP says nothing about null. Thus, if no definition is found we should return an empty array instead of null.
Returning null breaks at least one client - the Typefox Java binding.

 Last update e75c159...a1b5f06

True, violating the protocol here. I was wondering whether it would be better to through an exception though, see #55 . Do you know what other language servers do?

Seems like the TS server does not return an error, so I'm fine with it

I was wondering whether it would be better to through an exception though, see #55

No definition found should be a valid situation and should not be considered as an error state.

Seems like the TS server does not return an error, so I'm fine with it

@felixfbecker Could you point me to the source code of the TS server? I'd like to examine it for other things.

Again it is not open source, maybe not even using LSP yet. I just checked if VS Code displays an error when I get a definition for whitespace.

*Afaik


need to update to match poetry's new sources

Code improvement description
saw this in passing while skimming the 1.5 changelog, we need to account for it as we have at least one unit test of the deprecated flags, indicating we look for the old keys at least...
<rest of issue description is WIP as I'm about to head to bed, will fill this in more in the morning>

Introduce priority key for sources and deprecate flags default and secondary (#7658).

[[tool.poetry.source]]
name = "PyPI"
priority = "primary"

this causes dependabot to break.
--------Check platform/messages gunicorn 20.1.0
/bot/vendor/ruby/3.1.0/gems/dependabot-python-0.232.0/lib/dependabot/python/helpers.rb:23:in `run_poetry_command': The Poetry configuration is invalid: (Dependabot::SharedHelpers::HelperSubprocessFailed)
  - [source.0] Additional properties are not allowed ('priority' was unexpected)
  - [source.1] Additional properties are not allowed ('priority' was unexpected)
  - [source.1] 'url' is a required property


feat: support after comment

close https://github.com/ti-community-infra/ti-community-bot/issues/384

/assign @Mini256
PTAL~ Thanks!

/merge


{AKS} Align the implementation of several commands with azure-cli

This checklist is used to make sure that common guidelines for a pull request are followed.
Align the following commands with azure-cli.

aks browse: take the implementation from azure-cli, and update the min cli version (azext_metadata.json).
aks show: already implemented in aks-preview.
aks list: already omitted in aks-preview, would fall back to the implementation in azure-cli.
aks get-versions: remove the duplicated implementation in aks-preview, which would fall back to the implementation in azure-cli.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

AKS

The backward compatibility test (result) for aks browse looks good.


coredns obsolete record is not cleaned if related DNSendpoints resource is updated

In federation v2, we use multiple clusters DNS: a DNS for service in multiple clusters. For a service, we have DNSEndpoint resource. E.g. with 2 member clusters
  spec:
    endpoints:
    - dnsName: test-service.test-namespace.test-domain.svc.example.org
      recordTTL: 300
      recordType: A
      targets:
      - <IP_ADDRESS>
      - <IP_ADDRESS>

For the service, cluster1 has target IP: 172.x and cluster2 has target IP: 192.x.
Now, we have 2 record after fix #807 for the service.
However, when cluster2 is failed. Target 192.x is removed from the DNSEndpoint. However, external-dns will not delete the record in DNS (coreDNS + etcd). This should be a bug. It is preferred to clean the obsolete record in DNS if it is removed fron DNSEndpoint.
@istalker2  @linki

I've noticed something similar, possibly from the same root cause. When adding a target annotation to an ingress object I can create a DNS record in etcd for use w/ coredns, however, if I update the ingress resource with a different target annotation, a new record is added, but the only one persists. I'm looking through the coredns provider code to try to grok why, but I'm not holding my breath on figuring it out.

Just going to add that I validated this issue only exists when the owner flag is set to TXT, I suspect this might be to blame? https://github.com/kubernetes-incubator/external-dns/blob/master/provider/coredns.go#L276-L295 it seems like this will read records in twice if they have both Host and TXT fields, however I tried nesting the TXT field logic under an else block to the Host test to not duplicate them but the tests start failing, so maybe this is by design and I don't know what the intention of this code is... there seems to be another bug in master causing records to be created continuously that doesn't exist in 0.5.11, so I can't easily test my code changes as I don't know where this bug was introduced


chore(template): clean up templates

I have somewhat of a nit regarding this. I understand that it's not in alphabetically order, but at the moment none of the other blueprints are. Accepting this PR makes the component blueprint the outlier.
Can I ask you to change the other ones as well?

Sure can. It did more, I believe (it's been a while), but they were fixed in various rebasings.

Removed ddescribe and iit because https://github.com/karma-runner/karma-jasmine/issues/73
According to @Brocco's comment (https://github.com/angular/angular-cli/pull/918#issuecomment-223588543) class curly braces should be on separate lines, I extended this to constructor functions since ngOnInit was already doing it. I can move the braces for the constructor and ngOnInit back to one line depending on how you would like it, @filipesilva.
I wasn't sure what to do with https://github.com/angular/angular-cli/pull/741/files#diff-8360312d36bd87696ebdad9888e6dec5R13 - It looks ugly either way I put it. One breaks the character line limit in tslint, one just looks ugly.
I was thinking of doing something like
it('should ...',
  inject([<%= classifiedModuleName %>Service],
  (service: <%= classifiedModuleName %>Service) => {
    expect(service).toBeTruthy();
  }));

Thoughts?

To be clear re: curly braces, I believe that if there is nothing going inside then they should be on the same line, but in the case you referenced, it was for a class definition, which will always have code inside.
For your specific example, I think the line breaks you have are fine, just update the indenting....
it('should ...',
  inject([<%= classifiedModuleName %>Service],
    (service: <%= classifiedModuleName %>Service) => {
    expect(service).toBeTruthy();
  }));

@Brocco correct. It was only for classes. So, in the case of constructor and ngOnInit for the various Components, Services, etc, braces on the same line or not?
Also, the formatting you pointed out, are you sure about services being indented one more level? It feels wrong that it is indented again with the expect on the same indentation level.

I like that extra indentation because it's a carry over of the parameters to the function.
To sum up my thoughts on curly braces. If you are going to put stuff in there, then put the closing one on a new line, if not then the same line is fine. So class definitions new line, constructor same line, ngOnInit I could go either way but lean towards new line.

Ah, I missed that in the inject. Woops...
Okay then, what about this? I just hate that it's becoming a pyramid o' doom, though. Bah. It calls out the callback function better though, imo.
it('should ...',
  inject([<%= classifiedModuleName %>Service],
    (service: <%= classifiedModuleName %>Service) => {
      expect(service).toBeTruthy();
    }));

@filipesilva - @Brocco, I believe everything has been fixed. 😄
Let me know if there is anything else you would like done.
I included https://github.com/angular/angular-cli/pull/1023 along with other new line fixes.

Just updated the PR that included @Brocco's changes to the spec files and anything else released in beta6.

Why add a space between the curlies ? constructor() { } vs constructor() {} ?

@johnpapa: VSCode formats it that way (afaik, I don't think I changed anything to make it do so), therefore I changed it since most of the community seems to be using VSCode.

Hmm, I just rebased and caused a timeout. Could someone restart this?
Also, is there anything else that someone has a question about or something else that the team would like me to do?

Since this isn't getting merged in, I updated the spec templates to follow the new testbed for rc.4 found here https://github.com/angular/angular/pull/9564. This PR will fail until it's released.
That said, would it be preferable to import the testing exports as seen here: https://github.com/angular/angular/pull/9564/files#diff-7603ee1fd936988af932c5804ceba9e4R9? @Brocco I believe it was you who imported all the jasmine exports last time. Thoughts?

Updated to include rc.4 and the beta.2 router.
Let me know if there are any other questions so that I can fix them. 😄

@delasteve Please leave the extra imports in the spec files. They are the common ones which most devs will use and we want them there for convenience.
After that please rebase and I'll merge this in.

@Brocco, the angular team deprecated those as of rc.4. Would you still like those in?
https://github.com/angular/angular/pull/9564