Testing cf-abacus-dataflow failed.

Hi Team,
I am just trying to clone cf-abacus and build and run it locally.
yarn run build  .. fails at this point.
yarn -v : 1.3.2
node -v:  v8.9.4
Testing...
abacus-dataflow
√ log input (110ms)
dataflow mapper
√ runs a map transform and stores inputs and outputs (1140ms)
√ expects map func to be called with system scope (63ms)
√ save to output db when it gets duplicate (409) (781ms)
√ does not store map outputs when error exists (610ms)
√ detects error when there is no sink (1015ms)
√ propagates mapper error from the sink, does not store to output (594ms)
√ limits db connections to error db (94ms)
on error
√ stores map errors to error db (719ms)
√ removes mapper error docs from db (1203ms)
with documents missing in the output db
√ replays data (469ms)
dataflow reducer
1) runs a reduce transform and stores its inputs and outputs
2) save to output db when it gets duplicate (409)
3) runs a reduce transform and down samples outputs
4) does not store reduce outputs when error exists
5) detects error when there is no sink
6) propagates reducer error from the sink and does not store to output
√ does batch post, and gather the errors (282ms)
√ limits db connections to error db (109ms)
on error
7) stores reducer errors to error db
8) removes reducer errors docs from db
with documents missing in the output db
9) replays data
dataflow sink
√ returns correct URI
√ distributes sampled db data evenly (94ms)
√ distributes random orgs evenly (187ms)
√ organization sticks to a node (187ms)
17 passing (49s)
9 failing

abacus-dataflow dataflow reducer runs a reduce transform and stores its inputs and outputs:
Uncaught AssertionError: expected 't/0001517381507772-0-0-0-1/k/4' to match /t/[0-9].*-0-0-0/k/4/
at postspy (src\test\test.js:1656:31)
at Object.batch_post (src\test\test.js:54:29)
at Timeout.flush [as _onTimeout] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\abacus-batch\src\index.js:79:5)

abacus-dataflow dataflow reducer save to output db when it gets duplicate (409):
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer runs a reduce transform and down samples outputs:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer does not store reduce outputs when error exists:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer detects error when there is no sink:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer propagates reducer error from the sink and does not store to output:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer on error stores reducer errors to error db:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer on error removes reducer errors docs from db:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it r
esolves.

abacus-dataflow dataflow reducer with documents missing in the output db replays data:
Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

Child process exited with code 9
----------|----------|----------|----------|----------|----------------|

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Lines

All files
86.94
75.46
96.26
87.87

index.js
86.94
75.46
96.26
87.87
... 4,1305,1306

----------
----------
----------
----------
----------
----------------

error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Please help.

Hi hsiliev,
OS Version that I have is Windows 10 64 bit OS.
And I am using Git Bash terminal to run the commands.
Node Version : v8.9.4
npm Version : 4.2.0
yarn Version : 1.3.2
Yes I have run this test on Feb 1st.
Is there any other pre requisite for building cf-abacus in local ???  Or any Environment Variables I need to set or cross check ???
Thanks In Advance.

@RadhikaKS There are no additional prerequisites for building Abacus.
What happens if you re-rerun Abacus build? Is the problem still there?

@hsiliev   I just tried to Rebuild Abacus locally.  Though previously mentioned error is not occurring now, it is failing yet at another point mentioned below...and the build ends.

node_modules/abacus-mocha: yarn test
< node_modules/abacus-cfpush: yarn test
$ abacus-eslint && nyc abacus-mocha

Testing...
Test command line args
√ verify all arguments parsed
√ verify optional arguments
√ verify mandatory arguments
Test abacus cfpush
when application is successfully pushed
1) verify CF_HOME content is copied to tmp dir
2) verify manifest is adjusted
3) verify prepareZdm
4) verify cf push executed
when application push fails
5) verify cf push was retried until retry attempts is reached
6) verify cf push was retried until successful push
with missing app manifest
7) fails
3 passing (97ms)
7 failing

Test abacus cfpush when application is successfully pushed verify CF_HOME content is copied to tmp dir:
AssertError: expected copySync to be called with exact arguments
at Object.fail (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:96:21)
at failAssertion (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:55:16)
at Object.assert.(anonymous function) [as calledWithExactly] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:80:13)
at Context.it (src\test\cfpush-test.js:174:14)

Test abacus cfpush when application is successfully pushed verify manifest is adjusted:
AssertError: expected writeFile to be called once but was called 0 times
at Object.fail (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:96:21)
at failAssertion (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:55:16)
at Object.assert.(anonymous function) [as calledOnce] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:80:13)
at Context.it (src\test\cfpush-test.js:179:14)

Test abacus cfpush when application is successfully pushed verify prepareZdm:
AssertError: expected exec to be called with exact arguments
at Object.fail (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:96:21)
at failAssertion (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:55:16)
at Object.assert.(anonymous function) [as calledWithExactly] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:80:13)
at Context.it (src\test\cfpush-test.js:192:14)

Test abacus cfpush when application is successfully pushed verify cf push executed:
AssertError: expected stub to be called 4 times but was called 0 times
at Object.fail (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:96:21)
at failAssertion (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:55:16)
at Object.assertCallCount [as callCount] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:137:13)
at Context.it (src\test\cfpush-test.js:205:14)

Test abacus cfpush when application push fails verify cf push was retried until retry attempts is reached:
AssertionError: expected [Function: runCLI] to throw an error
at Context.it (src\test\cfpush-test.js:239:37)

Test abacus cfpush when application push fails verify cf push was retried until successful push:
AssertError: expected exec to be called twice but was called 0 times
at Object.fail (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:96:21)
at failAssertion (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:55:16)
at Object.assertCallCount [as callCount] (C:\Users\i338670\Desktop\TestCFAbacus\node_modules\sinon\lib\sinon\assert.js:137:13)
at verifyPushRetryAttempts (src\test\cfpush-test.js:220:14)
at Context.it (src\test\cfpush-test.js:250:7)

Test abacus cfpush with missing app manifest fails:
AssertionError: expected [Function: runCLI] to throw an error
at Context.it (src\test\cfpush-test.js:261:37)

Child process exited with code 7
------------------|----------|----------|----------|----------|----------------|

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Lines

All files
36.22
7.14
25
38.02

src
41.24
12.5
29.17
42.55

index.js
41.24
12.5
29.17
42.55
... 173,174,175

src/lib
20
0
0
22.22

remanifester.js
20
0
0
22.22
... 40,41,43,45

------------------
----------
----------
----------
----------
----------------

error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I have tried installing ESLint through npm install -g eslint , But still it fails at this point.

What you can do is to build Abacus with yarn provision. This will only take care to get all dependencies, without running the tests. Then you should be able to do yarn start and get Abacus running locally.
I'll leave this issue open so we can establish Windows build since now we're running CI on Mac/Linux. That's another option if you're still having problems with the build.

@hsiliev
FYI...
I tried building abacus with yarn provision and it was success.
But yarn start is not working.
$ yarn start
yarn run v1.3.2
$ bin/start
'bin\start' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Even if I go till bin folder of cf-abacus and start it , it will start and then again same error I am getting When I try to do yarn run demo

You'll have to use *nix system (Linux/MacOS) to get Abacus running at the moment.
We got rid of zip executable requirement (#239) but it seems we have more work to do here.


Does OpenNI2 support Registration of Kinect?

The Driver Libfreenect can provide  a mode that output registration depth data.
Can OpenNI2 support that when the Driver is libfreenect?

Dear wpjsolo
I have the same problem, could you tell me how did you solve it?

For me it was enough to check the call sequence of the OpenNI functions.
Checking the availability and enabling the registration AFTER the creation of the color and depth streams changed the return code of setImageRegistrationMode() from 4 to 0.


small fix for #117

fix issue #117

Yikes 😆

we actually never use it so it doesn't affect anything but still should be fixed ahah


Bugfix: allow annotations on parent assignments with released peer reviews

Proposed Changes
(Describe your changes here. Also describe the motivation for your changes: what problem do they solve, or how do they improve the application or codebase? If this pull request fixes an open issue, use a keyword to link this pull request to the issue.)
Currently, if a submission has a released peer review, the annotation validations prevent adding new annotations on the result in the parent assignment. This is a bug, which this PR fixes. Resolves #7184
...

Screenshots of your changes (if applicable)

Associated documentation repository pull request (if applicable)

Type of Change
(Write an X or a brief description next to the type or types that best describe your changes.)

Type
Applies?

🚨 Breaking change (fix or feature that would cause existing functionality to change)

✨ New feature (non-breaking change that adds functionality)

🐛 Bug fix (non-breaking change that fixes an issue)
x

🎨 User interface change (change to user interface; provide screenshots)

♻ Refactoring (internal change to codebase, without changing functionality)

🚦 Test update (change that only adds or modifies tests)

📦 Dependency update (change that updates a dependency)

🔧 Internal (change that only affects developers or continuous integration)

Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)
Before opening your pull request:

[x] I have performed a self-review of my changes.

Check that all changed files included in this pull request are intentional changes.
Check that all changes are relevant to the purpose of this pull request, as described above.

[x] I have added tests for my changes, if applicable.

This is required for all bug fixes and new features.

[ ] I have updated the project documentation, if applicable.

This is required for new features.

[ ] If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

[x] I have updated the project Changelog (this is required for all changes).
[x] I have verified that the pre-commit.ci checks have passed.
[x] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported by Coveralls.
[ ] I have requested a review from a project maintainer.

Questions and Comments
(Include any questions or comments you have regarding your changes.)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1913 unchanged lines in 60 files lost coverage.
Overall coverage decreased (-39.9%) to 51.729%

Files with Coverage Reduction
New Missed Lines
%

app/lib/markus_logger.rb
1
71.93%

config/dummy_lti_config.rb
1
66.67%

config/initializers/01_init_app.rb
1
50.0%

spec/factories/groups.rb
1
66.67%

config/initializers/resque.rb
2
84.62%

spec/factories/annotations.rb
2
92.86%

spec/factories/flexible_criteria.rb
2
84.62%

spec/factories/grouping_starter_file_entries.rb
2
80.0%

spec/factories/marking_scheme.rb
2
77.78%

spec/factories/rubric_criteria.rb
2
81.82%

Totals

Change from base Build<PHONE_NUMBER>4:
-39.9%

Covered Lines:
3822

Relevant Lines:
7200

💛  - Coveralls


For different serialization format

So far, we only have JSON format for serialization. In this PR, I'd like to include other serialization formats such as protobuf.
I'm expecting the number of serialization formats won't be larger. Thus, I'll prepare serialization functions for each serialization format.

This change is

Protobuf seems to be hard to integrate into quisp right now. I'll remove protobuf for now and will think what is a good way to include it into quisp

Instead of protobuf, I'd like to introduce bitsery here.


Table without border and header truncates last line

Describe the bug
A table which as no border and no header will truncate its last line. In this case the table height is miscalculated.
Additional context
For instance a table with no header and a single line shows nothing.
func (t *Table) computeHeight() int {
	hasHeaders := t.headers != nil && len(t.headers) > 0
	return sum(t.heights) - 1 + btoi(hasHeaders) +
		btoi(t.borderTop) + btoi(t.borderBottom) +
		btoi(t.borderHeader) + t.data.Rows()*btoi(t.borderRow)
}

t.heights in this case is 1 so we end up with a total height of 0. It works with a header because the header height is accounted for twice: once in t.heights and once again with btoi(hasHeaders).
The -1 is the culprit here I guess

maybe will help to debug: happens on narrower terminal when table doesent fit from the first run and recalculate logic is triggered.
On a first pass my StyleFunc is getting row/column iteration with rows starting at 1-to-len. With second pass (resize) it goes col/row, but rows are in the range of 0-to-(len-1), which is causing issues for me, but I think its a same bug.


WIP: Extracting zoneminder to a new library

Description:
In #15324, @jantman was trying to expose the ZoneMinder run state to Home Assistant and @MartinHjelmare and @balloob asked for the device specific logic to be moved to a new pypi library before any new functionality changes be made.
I've taken a first stab at splitting out the platform with the camera.zoneminder component so far. I was hoping to get a quick review to confirm that I'm on the right track before I continued with migrating out switch.zoneminder and sensor.zoneminder. I have intentionally not set the REQUIREMENTS variable since I have not published the library yet.
I've spun up a new repo to hold the new library and have opened a PR in it for visibility: https://github.com/rohankapoorcom/zm-py/pull/2
This should not require any configuration changes (nor any documentation updates) in Home Assistant.
Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@MartinHjelmare I believe everything should be all set here besides publishing zm-py to pypi and setting the REQUIREMENTS variable in the components that need it. If you think this makes sense, I'll go ahead and wrap that last part up.

@MartinHjelmare All comments addressed, library published on pypi and REQUIREMENTS updated. Let me know if anything else is needed here.

Please make a new PR and add yourself to codeowners. :+1:


Upgrade to Gateway API v1.0

In the latest versions of Kubernetes the deprecated v1alpha2 API has been removed definitively. I cannot provide any docs but I hope to find some exact details. I gathered this information from the Kubernetes Slack channel.

This error is raised only when the gateway class and gateway are being updated. Not sure @rg0now  if you know about this but it doesn't matter what API version we create the resources with. It will be overwritten on the first upgrade event from the operator. In this line the API version will be ignored and will be set to v1alpha2 and used further on during the whole process.
The main problem that this raises is that the operator won't be able to run on the latest versions of k8s.

I'm not sure it's a Kubernetes issue, I'd rather say it's most probably GKE advancing really fast. That being said, this will need to be fixed before the new release: our GatewayClass and Gateway must be upgraded to v1beta1. The idea is that every time we create/manage/delete/watch any Gateway API resource we must update the package version from v1alpha2 to v1beta1. This will be a PITA because all the zillions places in the code and the tests where we refer to a Gateway or GatewayClass the reference will have to be updated. AFAIK UDPRoutes have not migrated to v1beta1 (yet?), so only GatewayClass and Gateway are affected. Any takers?

With the Gateway API going GA, we should repurpose this issue to move the operator to the Gateway API v1.0.

Another fact that hurries us to upgrade is that some Gateway API users, e.g., Envoy-gateway, are already using the v1.0 API which is not compatible with our current state.

Done in v0.17.0.


Support for UTF-8 Latin-1 | SO/IEC 8859-1

As the title says, I'm asking for support for Latin languages because, so far, it doesn't support the Latin characters that are used in Portuguese.

At the top it should be showing: Lembretes por Urgência
The other one is: Não Urgente

Thanks for bringing this to my attention, is this only an issue in the reminder chart or is it happening elsewhere?

I only noticed on the reminder chart, its seems to be working everywhere except for the reminder
Currently trying to figure out how to make a pull request for the translation.

I just released 1.1.3, this bug should be fixed, there are also more strings to translate with it.

Just finished translating the new strings and confirmed the reminder dashboard is fixed.
I asked some friends to review the translation even though i was talking to them in VC on discord while translating it and they found 2 strings that could be improved.


invalid error from front-end: complaining about not implementing private members

I'm seeing compile-time errors produced by the FE in code that I believe is valid.
Seems to come up when using generic types in private members of an interface, and implementing such interface from a different library. Here is an example repro:
a.dart:
import 'b.dart';

class A implements I<dynamic> {
  dynamic get foo => 1;
}

b.dart:
class I<T> {
  T get foo => _foo;
  T _foo = null;
}

When  running:
pkg/front_end/tool/fasta compile --strong a.dart

This error is reported:
`abstract_wat.dart:3:7: Error: The non-abstract class 'A' is missing implementations for these members:
  '_foo='.
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.

class A implements I<dynamic> {
      ^
abstract_wat.dart:3:7: Context: '_foo=' is defined here.
class A implements I<dynamic> {

Marked as P1 as this blocks rolling out dart2js in strong mode (this came up trying to run dart2js in strong-mode using -dev.50 on internal customer applications.)

Upon closer review, I believe this is a P0, I'll send more details offline.

Moving to P0 because this also blocking the Flutter roll.
This is likely caused by 9c2fcedaf4abafa1404aafc726323c04fc4d05cd (/cc @askeksa-google) which I suggest reverting unless the fix is easy.

/cc @yjbanov

@mraleph - thanks for the link to the possible cause, I'll try reverting locally to see if it can unblock our work.
The context I wanted to mention earlier is that this shows up on most targets of internal apps, so unless the revert works, it would also block us from making progress on our investigation of dart2js strong-mode issues.

I tried reverting 9c2fced on https://dart-review.googlesource.com/c/sdk/+/53169 and Siggi's test seem to pass.

This is because of the forwarding stubs, this is another place where we need logic to treat them as if they weren't there.

The check for missing implementations got confused by a forwarding stub. Fix coming up.

/cc @athomas, can we get a dev build once this fix is in?

Sure, I'll create a release as soon as this lands!

The fix has landed.

Thanks! I'll give it a try asap.

I'll create the release.


Reorganize examples to make them language-specific directories.

This will make it easier to link to a language-specific README inside a language-specific directory :)

Can you confirm the Java move works? I remember battling with java because I originally had it under examples/, but Bazel freaked out about stuff.

Ah good call, it builds but doesn't run. I'll dig in a bit more.

OK, this should be good to go.


Adding new example for circuitpython requests_https

I've been asked to add my example to the directory of example. It's uses requests_https on circuitpython and has been tested on an Adafruit Metro ESP32 Express

hihi looks like needs a copyright notice at the top, maybe black and pylint - do ya know how to do those?

Sorry not sure what they are or how to fix it now that the code on my end has been committed and pushed.  It was amazing that I got that for. I'm guessing that you have a generic copyright that can be inserted.  What happen is someone pointed me to an example that wouldn't work and I fixed it. I uploaded that to the forum for anyone interested.  Someone asked me to put it on github.  Turned out that the example was really for python on a raspberry pi using the blinka library.  So here we are.  The is where I was told to post the example this time. I was able to fork, clone, add the file commit and push.  That's about all this 70 year old can do.

ha ok @dherrada can help you out with the rest, you're really close!

@jfabernathy Ok, so it looks like you're currently failing two of the pre-commit checks.
The first one is the black check. This one is pretty easy to fix.
Now, you also added a file, so you're gonna need to add a license to it. I'd just copy the text from the other example files and change the name to your name and possibly the year if it isn't 2021.
Let me know if you've got a

@jfabernathy This is the license for examples. Since you're adding a new one that you wrote, replace ladyada with your name (can be either your GitHub name or your actual name). Looks like your fork was made before I added them to this library which makes sense as to why you didn't see them.
# SPDX-FileCopyrightText: 2021 ladyada for Adafruit Industries
# SPDX-License-Identifier: MIT

after I added the License statements I committed and pushed.  It failed again and I finally found out why.  pylint really doesn't like my import statements and I have no idea why. The code runs fine.

@jfabernathy the details of what pylint is failing is here: https://github.com/adafruit/Adafruit_CircuitPython_Requests/pull/68/checks?check_run_id=1826084237 It's not necessarily "right", but you can re-sequence the imports as it suggests and see if that makes it happy.

I've made progress but still failing with one error, exit code 1.  So not sure what to do. imports seem fine now.

I'm not sure about that one, maybe dherrada can advise.

If pre-commit finds anything it will exit that way.
https://github.com/adafruit/Adafruit_CircuitPython_Requests/pull/68/checks?check_run_id=1826367683#step:11:24
At that line, you can see that black wanted to reformat a file.
 I know. ;-) But you got this !

I ran black again, added, committed, and pushed again. It didn't reject this time. Only good news about this process is it will drive you to drink :-)

@jfabernathy Great to see that it's passing!

Merging since we've got 2 approvals


pykdgrav import potential fail

Hi,
Apparently, pykdgrav requires a non-standard module,
numba, which is not automatically installed when installing
pykdgrav via pip, e.g.:
pip install pykdgrav
Unfortunately,
pip install numba
fails.
Any hints on how to get a full, working installation of pykdgrav
would be much appreciated.
Thor.

Hi,
Unfortunately, there’s a whole mess of problems and inconsistencies involved in installing Python libraries, so I’m not going to be able to give very specific advice. If you set up an Anaconda environment for Python, that should have numba with it and behave fairly well. Otherwise, you’ll have to look through the documentation for numba, check your Python and numpy are the right versions, check if you need to set any paths correctly etc.
Alternately, many SPH/N-Body codes have an option to dump the potential at run-time, or have modes where they can read in a snapshot and calculate the gravitational forces and potentials without changing anything. So I would check the documentation for your simulation code too.
There are also other third party codes that you could download and run from the command line - I think SKID from the n-body shop is an old-school code that does potential calculations to find halos, for instance.
Cheers,
David

On 6 Jun 2019, at 5:03 am, thor<EMAIL_ADDRESS>wrote:
Hi,
Apparently, pykdgrav requires a non-standard module,
numba, which is not automatically installed when installing
pykdgrav via pip, e.g.:
pip install pykdgrav
Unfortunately,
pip install numba
fails.
Any hints on how to get a full, working installation of pykdgrav
would be much appreciated.
Thor.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/omgspace/pykdgrav/issues/1?email_source=notifications&email_token=ACDXXRRHQ4HLEKCMHWB2CH3PZCEC5A5CNFSM4HUX3LUKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GX5QGDQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDXXRVBDTCPWBW2ECUWGC3PZCEC5ANCNFSM4HUX3LUA.

Hi Thor,
I wasn't able to reproduce your error - numba installs from PyPI just fine for me. There may be some system dependency that numba needs that you don't have, depending on your OS, etc.  I suggest examining the specific error message returned when you try to install numba.
Best,
Mike


Issues with workspaces settings

I use two workspaces.
I noticed those things that probably are broken:

When updating dbeaver (I switched from 7.0.5 to 7.1.0) one of the two workspaces has been unregistered. I had to add it again.

When switching to a new workspace, you have copy options that don't work: nothing is copied. Furthermore that's the same option for switching to an existing workspace: if the workspace already exists these copy options should not be there, because if they worked, they could lead to damage the target workspace.

When modifying database connection in two different workspaces (at the same time) I always receive an alert saying:
"The secured storage file has been modified by another program. Saving secure storage will overwrite file's contents. Would you like to save?"

The option 'Prompt for workspace on startup' never worked. Dbeaver open with the last workspace you switched.

thanks for the bug report


Crash when using SwitchStore

Description
When I use SwitchStore I'm getting a crash. I'm probably using it wrong but I reproduced it in a small case.
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
I would expect no crash and the different feature views swapped out.
Actual behavior
Getting a crash with
Fatal error: No ObservableObject of type StoreObservableObject<State, Action> found. A View.environmentObject(_:) for StoreObservableObject<State, Action> may be missing as an ancestor of this view.

Steps to reproduce
import ComposableArchitecture
import SwiftUI

struct MyApp: App {
    var body: some Scene {
        WindowGroup {
            FeatureView(
                store: Store(
                    initialState: Feature.State()
                ) {
                    Feature()
                }
            )
        }
    }
}

struct Feature: Reducer {
    struct State: Equatable {
        var color: Color.State?
    }

    enum Action: Equatable {
        case buttonTapped
        case color(Color.Action)
    }

    struct Color: Reducer {
        enum State: Equatable {
            case red(Red.State)
            case blue(Blue.State)
        }

        enum Action: Equatable {
            case red(Red.Action)
            case blue(Blue.Action)
        }

        var body: some ReducerOf<Self> {
            Scope(state: /State.red, action: /Action.red) {
                Red()
            }
            Scope(state: /State.blue, action: /Action.blue) {
                Blue()
            }
        }
    }

    var body: some ReducerOf<Self> {
        Reduce { state, action in
            switch action {
            case .buttonTapped:
                switch state.color {
                case .none:
                    state.color = .red(.init())
                    return .none
                case .red:
                    state.color = .blue(.init())
                    return .none
                case .blue:
                    state.color = nil
                    return .none
                }
            case .color:
                return .none
            }
        }
        .ifLet(\.color, action: /Action.color) {
            Color()
        }
    }
}

struct FeatureView: View {

    let store: StoreOf<Feature>

    var body: some View {
        WithViewStore(self.store, observe: { $0} ) { viewStore in
            Button("Tap Me") {
                viewStore.send(.buttonTapped)
            }
            SwitchStore(store.scope(state: \.color, action: { .color($0) })) { state in
                switch state {
                case .red:
                    CaseLet(
                        /Feature.Color.State.red,
                        action: Feature.Color.Action.red
                    ) { store in
                        RedView(store: store)
                    }
                case .blue:
                    CaseLet(
                        /Feature.Color.State.blue,
                        action: Feature.Color.Action.blue
                    ) { store in
                        BlueView(store: store)
                    }
                case .none:
                    Text("No Color")
                }
            }
        }
    }
}

struct Red: Reducer {
    struct State: Equatable { }
    enum Action: Equatable { }
    var body: some ReducerOf<Self> { EmptyReducer() }
}

struct RedView: View {

    let store: StoreOf<Red>

    var body: some View {
        WithViewStore(self.store, observe: { $0} ) { viewStore in
            Text("RedView")
                .foregroundColor(.red)
        }
    }
}

struct Blue: Reducer {
    struct State: Equatable { }
    enum Action: Equatable { }
    var body: some ReducerOf<Self> { EmptyReducer() }
}

struct BlueView: View {

    let store: StoreOf<Blue>

    var body: some View {
        WithViewStore(self.store, observe: { $0} ) { viewStore in
            Text("BlueView")
                .foregroundColor(.blue)
        }
    }
}

The Composable Architecture version information
1.2.0
Destination operating system
No response
Xcode version information
No response
Swift Compiler version information
No response

The behavior you're seeing is related to Swift's optional promotion and the fact that CaseLet is not in a context that can be influenced by type inference. In this case a Store<State?, Action> is passed to SwitchStore, which makes the exhaustive switch's types line up, but the CaseLet is working with a non-optional case path expression, which makes its body look for an environment object of a store of non-optional state to be hydrated with.
So the fix is to make the types line up. One option is to update the CaseLet with extraction functions that fully account for the optionality:
switch state {
case .some(.red):
  CaseLet(
    (/Feature.Color.State?.some).appending(path: /Feature.Color.State.red).extract,
    action: Feature.Color.Action.red
  ) { store in
    RedView(store: store)
  }
case .some(.blue):
  CaseLet(
    (/Feature.Color.State?.some).appending(path: /Feature.Color.State.blue).extract,
    action: Feature.Color.Action.blue
  ) { store in
    BlueView(store: store)
  }
case .none:
  Text("No Color")
}

Or you can take 2 steps, first using an IfLetStore to unwrap the optional color state, before switching on the non-optional color state that can be switched over directly:
IfLetStore(store.scope(state: \.color, action: { .color($0) })) { colorStore in
  SwitchStore(colorStore) { state in
    switch state {
    case .red:
      CaseLet(
        /Feature.Color.State.red,
         action: Feature.Color.Action.red
      ) { store in
        RedView(store: store)
      }
    case .blue:
      CaseLet(
        /Feature.Color.State.blue,
         action: Feature.Color.Action.blue
      ) { store in
        BlueView(store: store)
      }
    }
  }
}

With the current way Swift works and SwitchStore works, we don't think we can work around this quirk, so I'm going to convert this to a discussion. We do plan on retiring SwitchStore in the future, though, which will help avoid this gotcha.


ERROR: Cannot add firewall rule through SSMS

We receive the following error when trying to add the rule through SSMS on the UAT environment:
Msg 5001, Level 16, State 5, Procedure sp_set_firewall_rule, Line 1 [Batch Start Line 0]
User must be in the master database.

We're connected with the user 'axdbadmin' as stated in the readme. However, we're not able to select the master database from the list in the 'Connection properties' tab. The only database which is available is the actual UAT db (also known as the AxDB on the DEVTEST environment).
When I type the database name 'master' into 'Connection Properties -> Connect to database' field I receive a popup that I have to allow an IP address and gives me a popup where I have to enter my azure credentials, however my account doesn't seem to have enough privileges.
What am I supposed to do in this situation?
Should I use a different account? If so where can I find this account, is that the Environment Administrator account?

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

ID: cb08fb04-94d5-ef25-8162-a0d79f5ee70a
Version Independent ID: 6d43b4b7-cc2e-49bc-564a-5eb5eacefa84
Content: Debug a copy of the production database
Content Source: articles/fin-ops-core/dev-itpro/database/dbmovement-scenario-debugdiag.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @laneswenka
Microsoft Alias: laneswenka

The issue seems to be resolved after doing another restore (this time without an error):
We are now able to configure an IP address by following the docs.
There was an error the very first time the database had been restored, the DSE team had resolved this issue. However, the restore probably caused this issue to occur as well.


Tab bar display is not correctly updated when editors open and close

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.65.2
OS Version: Windows 10

Steps to Reproduce:

open and close many tabs

I originally planned to submit this based on

the last tab sometimes had the x for close after the menus icons in the tab bar
when hovering over the tab the "X" to close would show to the right of the icons

the last tab would hide the menu icons in the tab bar

I can't seem to reproduce those two issues with today's version of vscode, but I am including them for completeness.
However, there are still some things that don't look right.
Based on what I see today, maybe it is only:

last tab is longer than necessary and puts the close "X" at the right edge of the panel, when all other tabs are sized based on title content. The below image without hovering shows the modified file "dot", but hovering would put the "X" there too.

sometimes a tab is left on a second line when there is clearly room for both it and the menu icons on the first line. Added to the previous problem it looks very strange.

Just a thought, but it might also help to always have the menu icons at the end of the first line, even if there are multiple lines. That would leave less of a gap after the last tab when the next tab and the menu icons won't both fit on the first line.

If you disable tab wrapping (via workbench.editor.wrapTabs: false), it should work as desired. With tabs wrapping enabled, in order for the wrapping to work properly, some UI behaviour was added that might seem not natural.
Related issues: https://github.com/microsoft/vscode/issues/126532 and https://github.com/microsoft/vscode/issues/115136

If you disable tab wrapping (via workbench.editor.wrapTabs: false), it should work as desired. With tabs wrapping enabled, in order for the wrapping to work properly, some UI behaviour was added that might seem not natural.
Related issues: #126532 and #115136

I shouldn't have to disable wrapping to get it to work correctly.
Thanks for the related issues. I will read them.
Today I have this showing. Yet another variation of bad. This time the last tab is under the menu icons.

I read #126532 and it had the same suggest that I gave. If the last tab and the menu icons won't fit, leave the menu icons on the top line and put the tab on another line. Actually I think the menu icons should stay on the top line all the time.

I also read #115136 and #46403. All of them seem to be closed without a good resolution.


DM-26988: Update TE1, TE2 metrics and add TE3,TE4 metrics

This PR updates ellipticity residual correlation metrics based on discussions at the virtual DM F2F meeting in Feb 2021. There are several notable changes:

TE1 and TE2 were previously computed from matched single-visit catalogs. Now TE1 and TE2 are computed from deep coadd.
TE3 and TE4 are similar to TE1 and TE2, and use the same underlying mathematical operations, but are measured on individual visits. This PR adds TE3 and TE4.
Utility functions for computing correlation functions involving ellipticity residuals have been ported from pipe_analysis. The implementation in pipe_analysis was done in a general way that allows all of the rho statistics to be computed. The various rho statistics and particular range of angular scales can now be easily selected in configuration. In other words, it should be straightforward to compute all the rho statistics now.
Added a function to merge the individual detector catalogs (for visits) and individual patch catalogs (for tracts). This function also applies the photometric and astrometric calibrations from the associated photo_calib and wcs of each input catalog. This function should probably be modified slightly to make the photometric and astrometric calibrations optional. Something to consider here is that the run methods of many measurement tasks will now be taking in multiple data arguments (e.g., catalogs, photo_calibs, astrom_calibs) as well as metric name, and sometimes dataIds. This is because I think we want to be somewhat flexible with how the merging and calibration is done, allowing this to be set in configuration, rather than in the run or runQuantum method of the base class that calls the run method of the specific measurement task. My preference would be to have a convention that puts the metric name as the first argument, rather than as a second or third argument, as currently seems to be the case for many of the measurement tasks.

Things I would still like to do:

Add a function for applying basic selections (e.g., fully deblended, PSF-like, SNR threshold, quality flags) to catalogs. I'd like to pull out this general functionality since it will likely be applied for many metrics.
Add option to use distortion or shear convention for ellipticity calculation

Still to be done:

Add unit tests
Apply to some larger test dataset such RC2 to have more statistics to gauge performance
It's likely the current changes broke something in WPerp calculation. Need to check.

Adding an option to use distortion or shear convention is good. I think the distortion convention is currently in place. We should keep this and implement the (now more commonly used) shear convention in the next iteration

Application to some larger test dataset is something that we can do for all metrics we are updating to the current iteration in one run. RC2 would be good.

Added unit tests. Added option to use shear ellipticity convention. Now using camelCase consistently. Now passing scons.
Discussed with @leannep to make a separate ticket to create a function to apply basic selection criteria for bright well measured stars consistently across metrics.


chore) update to use go dep

Codecov Report

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

@@          Coverage Diff          @@
##           master     #7   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          31     31
=====================================
  Hits           31     31

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 9ae1564...0b48051. Read the comment docs.


Add bg prop to ProgressBar.Item

Adds a bg prop for on ProgressBar.Item as discussed in https://github.slack.com/archives/GACAW0NPM/p1726839001767409
Follow-up task

[x] Once merged: merge this one: https://github.com/primer/eslint-plugin-primer-react/pull/237

Changelog

Adds a bg prop for on ProgressBar.Item

Rollout strategy

[ ] Patch release
[x] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[ ] None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

Would be super nice to have some VRT tests as well, I can add some on main so that we get a nice diff 👍


Limit of CPU cores per region per subscription is 10? This seems to be wrong

It think this is wrong.
I the page https://github.com/MicrosoftDocs/azure-docs/blob/master/includes/container-instances-limits.md
we have the following limit:
Standard sku cores (CPUs) per region per subscription | 10
There must be some information missing there, as I am sure a subscription can use more than 10 CPUs

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

ID: c7a4f16d-190f-a1c0-fab0-5a9065554166
Version Independent ID: 0dab3702-f14f-7fb8-f9d7-e39be7230ab5
Content: Service quotas and region availability - Azure Container Instances
Content Source: articles/container-instances/container-instances-quotas.md
Service: container-instances
GitHub Login: @macolso
Microsoft Alias: macolso

@RenSilvaAU Thanks for the Feedback, we will check and update the document accordingly.

@RenSilvaAU
The limit that you see in the document are the default limits that are imposed per subscription and region.
These limits can be increased based on the subscription type as documented.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#container-instances-limits
Hope that clarifies.


add support for changing brighteness during the day/night

Hi, I added a support for changing brighteness during the day/night. Unfortunately it comes with two caveats:

It brings a bunch of new dependencies and was tested only on Arch.
Tested only on one setup (laptop screen + two external screens).

YMMV

Thanks for taking time opening a PR. However, I do not plan to work actively on this anymore. Besides, with more and more new monitors having auto brightness control, I don't think it will be necessary to do it programmatically.
Have fun with the script and sorry for the late reply!

Sure, np. Thanks!


fieldgroup request: "Customer Bank Account", "Vendor Bank Account"

Please add fieldgroup DropDown to tables "Customer Bank Account" and "Vendor Bank Account" so we can extend it.
Gest regards,
Katarina

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


burrego: implement missing Glob builtins

Epic: https://github.com/kubewarden/policy-evaluator/issues/56
These are the builtins that burrego has to provide that belong to the Glob area:

[x] glob.quote_meta

Implemented.


Resource function for *.csv no longer requires leading text

Before the regex was .+\*.+ which due to the first +, did not
support *.csv because it didn't have anything leading up to the *.
We replace the + with a * to allow for zero leading characters
Fixes #85

I can confirm that this fixes #85. Thanks!

Great!  Merged.  As always, thank you for reporting issues.  The scope of into is large enough that we really rely on good reporting from the community.


feat: implement Keep-Alive header parsing in Session

Implemented get_keepalive_values method to parse Keep-Alive header, resolving a TODO in the codebase.

✅ I marked it as accepted. Our internal tooling will digest it, and it will appear in this repo (squashed but maintaining authorship) in a week or so. When that happens, we'll mark this pr as closed. Thanks!

Merged via https://github.com/cloudflare/pingora/commit/7166444a79f63e539024bfa1f4bae7db40511c4d


Chore: Facebook api support information

Related to: https://github.com/chatwoot/chatwoot/issues/4648

@tejaswinichile Please update the screenshots as per this guideline. https://www.chatwoot.com/docs/handbook/marketing/guidelines-taking-product-screenshots-or-screencasts#general-guidelines

@tejaswinichile Please update the commit messages as per https://www.chatwoot.com/docs/handbook/engineering/pr-guidelines#commit-message-structure

@pranavrajs I have made the respective changes, let me know if that seems okay?


Allow setting FFmpeg video parameters

Currently, setting the GOP size with -g is essential when using SVT-AV1 via FFmpeg, because the default GOP size is fairly small and results in larger files than necessary. Another thing to consider is -sc_detection 1 to enable scene change detection, which is currently off by default since it's not optimized. However, I still prefer it to having a constant GOP size.
There's also an -svtav1-params option being planned, but no code for this has been merged to either SVT-AV1 or FFmpeg currently.
While being able to set -g and -sc_detection would be good enough, being able to define any FFmpeg output options (including filters) would be ideal. But this does bring up extra complexity with VMAF calculation in situations that involve any modification of the source, like cropping or scaling, since such operations will also have to be applied to the source file when calculating VMAF.
In case it helps, I'll include a couple of sample FFmpeg commands I use for calculating the VMAF for modified encodes. I'm not sure if the setpts filter is required for this use case, but I think I found it necessary in the past for some x265 timestamp issues.
Scaled encode:

ffmpeg -hide_banner -r 24 -i 720p.mkv -r 24 -i source.mp4 -an -sn -map 0:V -map 1:V -lavfi "[0:v]setpts=PTS-STARTPTS[dist];[1:v]setpts=PTS-STARTPTS,scale=1280:-2[ref];[dist][ref]libvmaf=n_threads=16" -f null -

60 fps source, 30 fps distorted file:

ffmpeg -hide_banner -r 30 -i 30fps.x264.medium.RF23.mkv -r 60 -i ../bbb_sunflower_1080p_60fps_normal.mp4 -an -sn -map 0:V -map 1:V -lavfi "[0:v]setpts=PTS-STARTPTS[dist];[1:v]setpts=PTS-STARTPTS,fps=30[ref];[dist][ref]libvmaf=n_threads=16" -f null -

I was leaving towards just not supporting advanced ffmpeg usage and suggesting that be done directly. However, it may make sense to add fmpeg args. It could be a leaky abstraction though.
For example, we're not encoding av1 using ffmpeg. Ffmpeg simple converts to yuv and pipes into SvtAv1EncApp (a bit like I described https://alexheretic.github.io/posts/av1-p1/#re-encoding-h264--friends).
On the other hand I'm generally happy to expose any svt-av1 option on ab-av1 that someone has a user for. See https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/svt-av1_encoder_user_guide.md & let me know which ones you'd want exposed. I actually tried adding scene detection but found it had little effect on my test inputs so didn't commit.

Oh, I didn't realize this uses SvtAv1EncApp directly.
In SvtAv1EncApp, maximum GOP size is set with --keyint and scene change detection is controlled with --scd. These two would be good to have.

I actually tried adding scene detection but found it had little effect on my test inputs so didn't commit.

The maximum GOP size is so small by default that scene change detection won't have much of an effect. But with an allowed max GOP size of 10 seconds (which is pretty standard), the encoder has better chances to place keyframes in locations where there's a scene change while also maintaining efficiency.
Whether having support for FFmpeg filters is worth it does depend on the use case. Not being able to crop or scale would limit the program's usefulness as an all-in-one encoding tool (for example, I've got Blu-rays that I want to crop). crf-search would still be useful for non-scaling use cases, because cropping the black borders doesn't affect quality much (if I remember correctly). I can definitely see myself mostly using the auto-encode command.
Another thing I noticed is that the FFmpeg pipe uses the yuv420p10le pixel format by default, and this results in the encode being 10-bit. I know some people will say it makes no sense to use AV1 to encode anything but 10-bit, but I think there should be a choice for yuv420p too.

Thanks for the info. Yep having options for all of these make sense, including ffmpeg filters. I'll look into it.

I've added svt-av1 args & default keyint=10s + scd when the input duration is over 3 minutes.


Chore: redesign welcome popup box text

Issue #601 : welcome popup box text is not properly visible solved
Type of PR

[X] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): ___________

Description
Fixes #601 solved
Screenshots / Videos (if applicable)
Before:

After:

Checklist

Add X in the box to specify.
[X] I have performed a self-review of my code.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Thank you for reviewing my pull request!

please merge my pull request

please merge this pull request


HDDS-5957. Bump proto-backwards-compatibility from 1.0.5 to 1.0.7

Preparing for the native (not using x86 JVM via Rosetta 2) Apple Silicon (darwin/osx aarch64/arm64 architecture) development environment.
See plugin release notes: https://github.com/salesforce/proto-backwards-compat-maven-plugin/releases
Side note: I am able to dev and run tests in IntelliJ with darwin arm64 native JVM after compiling 3 different protobuf versions for arm64, and compiling rocksdbjni 6.25.3 for osx-aarch64. Running native arm64 is significantly faster than using x86 JVM with Rosetta 2 translation layer on an M1-series Mac. Docker ozone-runner still only has x86 containers for now (which can be run in x86 qemu for testing, but slow).

Thanks @adoroszlai for checking this out and +1. :) Will merge this in a minute.


build_main_platforms and build_cplay_platforms commands not found

While pushing a PR to Travis. It fails with the following errors:
$ build_cplay_platforms
build_cplay_platforms: command not found
The command "build_cplay_platforms" exited with 127.
$ build_main_platforms
build_main_platforms: command not found
The command "build_main_platforms" exited with 127.
I noticed this on another PR that had failed for the same reason. Since this repo is the source of those commands, it seemed appropriate to file this here.

hmm ok please revert the last PR, seemed like it should have worked but did not

Just confirmed that reverting it fixed this.

I can investigate the issue, how where you running the script
Surely you forgot to update the link to the build,
thoses comments are no more sourced, I can fix it but it works if you call $TRAVIS_BUILD_DIR/install.sh build_platform esp8266 for example

This is being called in automated builds in several hundred libraries. Can this be updated in a way so it doesn't break all these libraries?

Done,
I was trying to not doing something messy but I didn't thought that may brake previous installs, so now the functions are sourced for travis AND callable through argument for Github


Publish Action to Github Marketplace

https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/publishing-actions-in-github-marketplace
https://docs.github.com/en/free-pro-team@latest/developers/github-marketplace/requirements-for-listing-an-app
https://docs.github.com/en/free-pro-team@latest/developers/github-marketplace/security-review-process-for-submitted-apps

@brianwyka, I just noticed that this has been sitting out here for far too long.  Are you good with me publishing the latest tag?  Looks like it's v0.5.

Sure @amyschoen , that would be great.  Haven't had a chance to work on this in a while, but would definitely give some visibility.


Refactor schema definitions to reuse common elements

There is not much difference between the three existing schema (image, overrides, module).  It would be nice to define common elements in one place and include them in the specific schema.  This would ease the maintenance burden and would allow the code related to the fields to be common across them (well, this is the way it is, but it prevents missing a schema update should the implementation change).

Yes, this is planned. We see this too.

I was looking at this today as part of module definitions reorganizing and was hit by this issue: https://github.com/Grokzen/pykwalify/issues/88. This is a blocker for us to use pykwalify 1.6.0 and still trying to use common elements across our validations. It seems that fix for this is hanging there for a while... https://github.com/Grokzen/pykwalify/pull/100 and https://github.com/Grokzen/pykwalify/pull/108.
Possible solution is to downgrade to pykwalify 1.5.2, but with this we loose the assert function.

cannot we just simply have "common schema" included once in image, module, overrides for now and refactor to better inclusion in more granular way later?

I'm not sure what you mean. Schemas for override and for image are different.

Either case - I'll have a proposal for this soonish.

they are almost same as you can see:
https://www.diffchecker.com/5dJCARMK
and even some non required parts of overrides should be required (names for envs)...

So, yes, a proposal is available in #42. I've tried several different approaches and found that this is the best one. There is one thing to note - I changed the behavior of merge_dictionaries method, where simple types are used from the second, not first dictionary. This seemed to me weird that we left them and caused issues with properly merging dictionaries for schemas.

#42 seems to complicated for me. I don't like such a complex changes and us doing merge dictionaries for schema to fix library bug.

Explain in details what is complicated there, please. It's a lot of refactoring, but look at the code instead.

And no, I don't use that broken feature of pykwalify anymore in my PR.

Also I'm strictly against changing/overriding schemas in runtime - schemas are now totally unclear to read by user.
Schema should server not only concreate, but also can be used in editors to check if image.yaml is correct during development - need to run the tool to check the schema is weird behavior.
For example if I look at https://github.com/goldmann/concreate/blob/f12a629f63e9a03d7d60a9b2dcf11a8f8d29df09/concreate/schema/image.yaml  it seems only from is valid the image.yaml.

You have everything in this file: https://github.com/goldmann/concreate/blob/f12a629f63e9a03d7d60a9b2dcf11a8f8d29df09/concreate/schema/schema.yaml. If there are any modifications needed on top of this common schema, you can find them in specific YAML files, like the one you mentioned above. It means - use everything from common, but for the from key - use this definition.

Ok tell me how can I view complete schema for image, module and overrides? I can't now and i need to know how they're are merged/overrided which is not a part of a kwalify but our added logic which I think is not a good idea.

You can't. This is the whole point of reusing and sharing image schema across multiple types of definitions (image, module, overrides). Common schema is defined somewhere and only specific changes are maintained separately, not the whole thing.

I can't now and i need to know how they're are merged/overrided which is not a part of a kwalify but our added logic which I think is not a good idea.

I can use this argument against image descriptor overrides: I cannot see the effective image descriptor when looking at a particular image descriptor file because everything is merged (sic!) at runtime...
But hey, this is a feature, right?

yes but I think we are here to much after sharing and reusing. Why we cant have simple stuff like:
overrides schema
from: ...
name: ...
include labels
include envs
include ...

image schema
from: ...
include lables
include envs

I can use this argument against image descriptor overrides: I cannot see the effective image descriptor when looking at a particular image descriptor file because everything is merged (sic!) at runtime...

But hey, this is a feature, right?
Effective image descriptor will be logged to target dir - IT was discussed before.
I'm ok with merging schema, if you will just commit to repo after merging - so I can see them whole and have a simple tool to regenerate them from shared sources.

Why we cant have simple stuff like
Because this is unsupported in pykwalify.

I'm ok with merging schema, if you will just commit to repo after merging - so I can see them whole and have a simple tool to regenerate them from shared sources.

I don't get that request. What is the benefit of seeing the final schema? Schemas are for us - Concreate developers, to define what we expect from users. We know the schema. Documentation, together with error messages from schema validation is for users. If we (as developers) will debug issues in schemas - we should add debug statements to see the target schema, as usual.

Oh ok, it seems that I misinterpreted kwalify manual. Hmm so probably your solution is the only possible one for now.

I didn't find anything better while working on it for the last 6 hours...

Ok. I made review of the PR. Its only minor adjustments- so decide if we need them.


Fixed table formatting in markdown.

The file configure-an-oracle-publisher.md had an error where the table was not formatted correctly because of a missing newline character.

@isermaniac : Thanks for your contribution! The author, @MashaMSFT, has been notified to review your proposed change.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: isermaniac sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@isermaniac : Thanks for your contribution! The author, @MashaMSFT, has been notified to review your proposed change.

The formatting changes look good; merging.

@isermaniac - Thanks!


AttributeError: 'SegDirectoryIterator' object has no attribute 'next'

@ahundt @aurora95 need help here!!
I met this issue when I run train.py
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\lib\threading.py", line 916, in _bootstrap_inner
self.run()
File "C:\ProgramData\Anaconda3\lib\threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\keras\utils\data_utils.py", line 568, in data_generator_task
generator_output = next(self._generator)
File "C:\ProgramData\Anaconda3\lib\site-packages\keras\preprocessing\image.py", line 737, in next
return self.next(*args, **kwargs)
AttributeError: 'SegDirectoryIterator' object has no attribute 'next'
lr: 0.010000
Epoch 1/250
Traceback (most recent call last):
File "train.py", line 233, in
label_suffix=label_suffix, ignore_label=ignore_label, label_cval=label_cval)
File "train.py", line 163, in train
class_weight=class_weight
File "C:\ProgramData\Anaconda3\lib\site-packages\keras\legacy\interfaces.py", line 87, in wrapper
return func(*args, **kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\keras\engine\training.py", line 2011, in fit_generator
generator_output = next(output_generator)
StopIteration
I debugged for all day and have no idea why is that happening :(
my sys Env is win10 python3.6 keras 2.0.8 tensorflow 1.2.1   any suggestion？
Thanks a lot!!!!

@unixnme @ahundt @PavlosMelissinos @aurora95 please！

hey, do u handle this issue? I meet the question too.

@cemsaz I'm running it on python3 and it works fine. Doesn't seem to be problem in python3 as in general.

@cemsaz  I have the same problem. Could you please specify in which script and in which lines I should do the replacement? Thanks in advance

Would someone be willing to explicitly post the solution to this issue, I am having a hard time getting around it. Thank you!!

@simonsayshi  Could you tell me your final solution? Thank U very much

@daodao1991 plz follow the instruction above..

@simonsayshi  I run it  on Ubuntu16.04 ，and  try tensorflow-gpu 1.3.0/1.2.1  with keras 2.0.8/2.1.2，and Python3.6/2.7 have been used.  I just  fail  again and again，which  drives me crazy. Please  help me!!
I  know this repository is good, but I cann't run  it.  So frustrated!

attach your full log maybe？dont know how to run in ubuntu but logs may help
a lot
On Wed, Aug 21, 2019 at 21:37 daodao1991<EMAIL_ADDRESS>wrote:

@simonsayshi https://github.com/simonsayshi I run it on Ubuntu16.04
，and try tensorflow-gpu 1.3.0/1.2.1 with keras 2.0.8/2.1.2，and
Python3.6/2.7 have been used. I just fail again and again，which drives me
crazy. Please help me!!
I know this repository is good, but I cann't run it. So frustrated!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aurora95/Keras-FCN/issues/68?email_source=notifications&email_token=AHQ4RSTLT2GG63MQUF4ZPTTQFYJWPA5CNFSM4ESIT7P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD433HBY#issuecomment-523744135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQ4RSSAVJSAHDR47NZZOALQFYJWPANCNFSM4ESIT7PQ
.

@simonsayshi Thank u for your reply, I change to win 10, and install tensorflow-gpu 1.4.0 && keras 2.1.2 && python 3.5 , but also failed. This is error logs:
(tf_1_4) F:\Pycharm_Projects\FCN\aurora95\Keras-FCN>python train.py
Using TensorFlow backend.
D:\Anaconda3\envs\tf_1_4\lib\site-packages\scipy_init_.py:115: UserWarning: Numpy 1.13.3 or above is required for this version of scipy (detected version 1.13.1)
UserWarning)
Traceback (most recent call last):
File "train.py", line 16, in
from models import *
File "F:\Pycharm_Projects\FCN\aurora95\Keras-FCN\models.py", line 6, in
from keras_contrib.applications import densenet
File "D:\Anaconda3\envs\tf_1_4\lib\site-packages\keras_contrib-1.2.1-py3.5.egg\keras_contrib_init_.py", line 2, in
File "D:\Anaconda3\envs\tf_1_4\lib\site-packages\keras_contrib-1.2.1-py3.5.egg\keras_contrib\backend_init_.py", line 14, in
File "D:\Anaconda3\envs\tf_1_4\lib\site-packages\keras_contrib-1.2.1-py3.5.egg\keras_contrib\backend\tensorflow_backend.py", line 10, in
ImportError: cannot import name '_postprocess_conv3d_output'
I change it to keras 2.0.8,  it will go back to the old error,

@simonsayshi  Hi, I fix the above problem by copying the revalent from a previous version of keras which included it. But ....
Then, python train.py, it seems to be running like this ：
Total params: 134,346,581
Trainable params: 134,346,581
Non-trainable params: 0

lr: 0.000625
Epoch 1/250
2019-08-24 16:47:49.694895: W C:\tf_jenkins\home\workspace\rel-win\M\windows-gpu\PY\35\tensorflow\core\common_runtime\bfc_allocator.cc:217] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.14GiB
. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory is available.
2019-08-24 16:47:50.586328: W C:\tf_jenkins\home\workspace\rel-win\M\windows-gpu\PY\35\tensorflow\core\common_runtime\bfc_allocator.cc:217] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.14GiB
. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory is available.
2019-08-24 16:47:50.594907: W C:\tf_jenkins\home\workspace\rel-win\M\windows-gpu\PY\35\tensorflow\core\common_runtime\bfc_allocator.cc:217] Allocator (GPU_0_bfc) ran out of memory trying to allocate 1.07GiB
. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory is available.
2019-08-24 16:47:50.610010: W C:\tf_jenkins\home\workspace\rel-win\M\windows-gpu\PY\35\tensorflow\core\common_runtime\bfc_allocator.cc:217] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.13GiB
. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory is available.
2019-08-24 16:47:50.681211: W C:\tf_jenkins\home\workspace\rel-win\M\windows-gpu\PY\35\tensorflow\core\common_runtime\bfc_allocator.cc:217] Allocator (GPU_0_bfc) ran out of memory trying to allocate 1.07GiB
. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory is available.
27/11127 [..............................] - ETA: 3:17:14 - loss: 1.7019 - sparse_accuracy_ignoring_last_label: 0.6480
My new question is, the following error occurs when the program reads an image, it seems like GPU resource exhausted :
ResourceExhaustedError (see above for traceback): OOM when allocating tensor with shape[7,7,512,4096]
[[Node: training/SGD/gradients/fc1/Square_grad/mul = Mul[T=DT_FLOAT, _class=["loc:@fc1/Square"], _device="/job:localhost/replica:0/task:0/device:GPU:0"](training/SGD/gradients/fc1/Square_grad/mul/x
, fc1/kernel/read)]]
[[Node: metrics/sparse_accuracy_ignoring_last_label/Reshape/_277 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/t
ask:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_471_metrics/sparse_accuracy_ignoring_last_label/Reshape", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
The strange thing is that my program has the following code:
config = tf.ConfigProto()
config.gpu_options.allocator_type = 'BFC'
config.gpu_options.per_process_gpu_memory_fraction = 0.80
session = tf.Session(config=config)
K.set_session(session)
Now I'm stuck with this bug and I don't know how to fix it. Help me !! I'm gratitude to you for helping me !!

have you solved the problem yet? If it, can you help me? thank you! @daodao1991

https://github.com/aurora95/Keras-FCN/pull/56/files#diff-884514ab248f7857177828d3a62cbdc5R194 shows the changed made for keras==2.1.x, as i used keras==2.0.8, so i go back to the origin code, the code is in utils/SegGenerator.py.
then i can run the train.py


Styling and markup fixes

add local stylesheet for specific CSS rules not part of the design system
change the template structure to follow how crispy expects them to be
remove content as per the designs

Minor comment about commit message, otherwise approved


"All Exceptions" doesn't de-activate after unchecking it

VSCode Version: 1.12.0-Insiders
OS Version: Windows

Steps to Reproduce:

Launch Extension: I used our cpptools extension.
Select the All Exceptions breakpoints option and have some exception trigger.
Uncheck the All Exceptions option.

Bug: It keep breaking on All Exceptions until I stop debugging.

This issue was moved to Microsoft/vscode-cpptools#652

@mjbvz No, this is a bug with VS Code's javascript debugging. This repros without the cpptools extension installed. I'm using VS Code to debug the cpptools extension.

Ok, so you are debugging your cpp extension with the extension debugger? Not debugging code with the cpp extension?

Yes, I do Launch Extension with our cpptools extension workspace for typescript debugging.

duplicate of https://github.com/Microsoft/vscode-node-debug/issues/135


Generator update version

Use generator to update the version in package.Jason and manifest

not sure if generator is the best way to do it

https://github.com/SAP/open-ux-tools/blob/main/examples/simple-generator/src/app/index.ts

https://github.com/SAP/yeoman-ui

Currently no time to further develop the generator (also because I see no need). Notes added to documentation and npm package deprecated


Fix small doc errors in rasterband

[x] I agree to follow the project's code of conduct.
[ ] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

read_band_as and write had incorrect argument lists in the documentation.

bors r+

Oof.

bors r+


Only build either shared or static library, but not both

CMake has a flag called BUILD_SHARED_LIBS that is used to control whether or not a shared library or static library is built. The benefit of this change is that consumers of zlib-ng's CMakeList.txt can use this flag to control which version of the library they want built. Which is what you might do if using zlib-ng's CMakeList.txt from another project using ExternalProject CMake function.  (See #338)

What specifically is the pros and cons here?
It doesn't seem to change cmake complexity much at least.

If any distribution wants to use cmake to make zlib-ng binary packages, then this will make building packages more complex. This is however one of those reasons why we would want to keep configure.

You have to think that people will want to use/include our CMakeLists.txt or reference them from their own projects. Having them build both shared and static versions of the library in that use case doesn't make much sense and only adds to overall build time for them. Using BUILD_SHARED_LIBS is the preferred way to switch building static versus shared when using CMake. If you look at the changes I made in the CMakeList.txt I think it actually makes the CMake code more clear and simplified.
The con is probably that  we need to add specific Travis test to make sure that CMake builds properly with BUILD_SHARED_LIBS=ON.
@mtl1979 - I am not sure I understand the additional complexity that would be required. Wouldn't it just be a matter of using the -DBUILD_SHARED_LIBS=ON flag?

@nmoinvaz As far as I know, the build system works by running the build script once and then grouping the output files from single source package to multiple binary packages. If cmake can only build either static or shared libraries, it means the build step needs to run twice in same output directory and that is forbidden on cmake.

I have made a change so that if BUILD_SHARED_LIBS is not set it will output both SHARED and STATIC. If BUILD_SHARED_LIBS explicitly set to ON, then only SHARED library will be built. If BUILD_SHARED_LIBS explicitly set to OFF, then only STATIC library will be built.

Ok ready.


[Server] Locales are out of date

Following locales need translations:
Russian
Spanish
Korean
Italian
Swedish
Polish
Dutch
Japanese
French
German
Turkish
Czech
Hungarian
Files can be found in: Aki_Data/Server/database/locales/server
The en.json file has all keys and is the base to use when translating
https://dev.sp-tarkov.com/SPT-AKI/Server/src/branch/master/project/assets/database/locales/server

Originally written by chomp

Working on Spanish SPT-AKI/Server#88

Originally written by BySempron

I'm working on Chinese translation. In old Chinese locale file, watermark-discord_url is not the same as other languages' "https://discord.sp-tarkov.com". It's "https://sns.oddba.cn/". Is it Okay?

Originally written by ghost114514

Going to be updating Dutch (NL) translations
Updated up to 13.5.0-25837 test build

Originally written by Lave

Just an idea. I could give the en file to chat gpt and let it generate all the translations. I am pretty sure it wouldn't be a perfect translation but its better than half finished translations. Or is this a bad idea? @chomp

Originally written by Lilxdomi

Crowdin being used for this, closing for now

Originally written by CWX


Move envvar to specific package

What type of PR is this?
/kind cleanup
What does this PR do / why we need it:

Move Envvar functions from config package to own package.
Make multi-line env variables possible (#4783)
Removes the possibility to use --env a=b,c=d instead of --env a=b --env c=d for odo config set
Checks the name of env variables with the regexp ^[a-zA-Z_][a-zA-Z0-9_]*$

By replacing cobra.StringSliceVar by cobra.StringArrayVar, we can pass multi-line values, but cannot use --env a=b,c=d anymore
Which issue(s) this PR fixes:
Part of #5247
Fixes #4783
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

@kadel What do you think would be more important (because we cannot have both)?

being able to have multi line values for env variables (to fix #4783)
being able to continue to use the short syntax odo config set --env a=b,c=d instead of odo config set --env a=b --env c=d (which is a non documented feature)

being able to continue to use the short syntax odo config set --env a=b,c=d instead of odo config set --env a=b --env c=d (which is a non documented feature)

We don't need short syntax. I think that --env a=b --env c=d is completely fine.

@valaparthvi, thanks for your review. I've added the missing tests

/approve
/lgtm


restart flinksql The actual failed but option logs show start status success after last flinksql has error and run status failed

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
restart flinksql The actual failed but option logs show start status success after last flinksql has error and run status failed 。i use flink nactive on kubernetes ，In this scenario, there is no log to find out why actual failed. At the same time ，kubectl get pod -A can not find any flinksql k8s pod ，and cannot use kebectl logs podid to  find out why actual failed.
StreamPark Version
1.2.4-dev
Java Version
jdk8
Flink Version
1.14.5-2.12
Scala Version of Flink
2.12
Error Exception
there is no log

Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

[root@server237 logs]# cat warn.2022-10-26.log
2022-10-26 09:11:45.310 StreamPark [streampark-deploy-executor-3] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:11:45.319 StreamPark [streampark-deploy-executor-3] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:11:50.230 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:11:50.409 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:56651 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:11:55.036 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:11:55.226 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:56651 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:12:00.035 StreamPark [ForkJoinPool-1-worker-30] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:12:00.203 StreamPark [ForkJoinPool-1-worker-30] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:56651 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:12:00.377 StreamPark [streampark-deploy-executor-4] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:12:00.385 StreamPark [streampark-deploy-executor-4] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:12:05.223 StreamPark [ForkJoinPool-1-worker-44] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:12:05.410 StreamPark [ForkJoinPool-1-worker-44] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:59745 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:12:10.039 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:12:10.232 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:59745 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:12:15.038 StreamPark [ForkJoinPool-1-worker-23] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:12:15.234 StreamPark [ForkJoinPool-1-worker-23] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:56651 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:12:20.035 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:12:20.220 StreamPark [ForkJoinPool-1-worker-51] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:56651 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:46:35.230 StreamPark [streampark-deploy-executor-5] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:46:35.237 StreamPark [streampark-deploy-executor-5] WARN  o.a.flink.core.plugin.PluginConfig:69 - The plugins directory [plugins] does not exist.
2022-10-26 09:46:40.210 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:46:40.397 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:46:45.036 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:46:45.217 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:05.035 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:05.224 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:10.038 StreamPark [ForkJoinPool-1-worker-59] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:10.246 StreamPark [ForkJoinPool-1-worker-59] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:15.036 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:15.223 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:30.038 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:30.231 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:35.039 StreamPark [ForkJoinPool-1-worker-2] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:35.229 StreamPark [ForkJoinPool-1-worker-2] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:40.043 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:40.264 StreamPark [ForkJoinPool-1-worker-16] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.
2022-10-26 09:47:45.035 StreamPark [ForkJoinPool-1-worker-2] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:220 - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
2022-10-26 09:47:45.225 StreamPark [ForkJoinPool-1-worker-2] WARN  o.a.s.f.k.w.FlinkJobStatusWatcher:227 - The retry fetch failed, final status failed, errorStack=Connect to http://<IP_ADDRESS>:64399 [/<IP_ADDRESS>] failed: 拒绝连接.

at this streampark deploy host，kubectl get node and kubectl logs  is ok

According to the k8s event, the flinksql job is started. Maybe the flinksql job still has an error and failed to run. k8s pod was simply deleted.

In this case, do not delete k8s pod. In the streampark web ui , add a button to force deletion to delete? Or delete the failed k8s pod before the next restart

In this case(flink nactive on kubernetes), do not delete k8s pod. In the streampark web ui , add a button to force deletion to delete? Or delete the failed k8s pod before the next restart


[fix][build] Fix checkstyle issue.

Motivation
There are 2 errors reported by Checkstyle 8.37 with /Users/tboy/tboy/workspace_1/pulsar/buildtools/src/main/resources/pulsar/checkstyle.xml ruleset.
[ERROR] src/main/java/org/apache/pulsar/io/jdbc/JdbcAbstractSink.java:[28,8] (imports) UnusedImports: Unused import: java.util.ArrayList.
[ERROR] src/main/java/org/apache/pulsar/io/jdbc/JdbcAbstractSink.java:[337] (sizes) LineLength: Line is longer than 120 characters (found 139).

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

@Technoboy- @mattisonchao @codelipenghui @poorbarcode I suggest we proceed with #18142 to resolve checkstyle issues globally since it adds a CI task to prevent regression.

@Technoboy- @mattisonchao @codelipenghui @poorbarcode I suggest we proceed with #18142 to resolve checkstyle issues globally since it adds a CI task to prevent regression.

Ok


qPDF code and tutorial

This PR implements the final version of the qPDF model, documentation and tutorial.

@AdrianPerezSalinas @stavros11 this PR collects all the pieces for the qPDF paper.
However I am not sure if we should keep all the pretrained models here, it is also true that the file sizes are not big.

Hi @scarrazza @stavros11 ,
with respect to the pre-trained models, maybe we could keep just the *results.pkl files, whose size is very small and may save a lot of time. If we decide to do so, I have to take care of introducing the last results in the folder.

@AdrianPerezSalinas yes, please remove/update the pickle files.

Done!

@AdrianPerezSalinas looks good to me.
@stavros11 could you please have a quick look at this?
The paper will be out tomorrow, so would be great to have this PR merged asap (and eventually fix potential issues later).

@stavros11 thanks you very much, I have implemented all points you have raised.


Usage code snippet

Great work.. can you please share the usage code snippet? It would be greatly helpful.

You can find it in README under Usage section.

Thanks..Does this return phone number only android? What about IOS?

Phone number is only Android

Thanks for the quick response...is there any way we can validate the phone number for ios?  what are your suggestions.
Should I only rely on authenticating IOS user by sending validation code via SMS..Is this the only way to check the user's valid phone number in ios?

You should ask the user to enter his/her own phone number.
It is valid on Android too because the phoneNumber field can be empty or wrong.
Sending the validation code to this number is the only way to check the phone number validity.

Thanks a lot.


Fix recognition of "<" as operator in some context

rust-mode identifies the "<<" as open angle brackets in
let x = a[i][(1 << i)];
This patch fixes the problem by changing rust-is-in-expression-context
to treat "]" as starting an expression in brace context.
Fixes #212

Merging this per the discussion in the bug.


CachedImage does not respect size when set aspect property to AspectFill on Android

If I define this use to CachedImage:
<ff:CachedImage x:Name="imageAvatar"
Source="{Binding Source}"
LoadingPlaceholder = "progress"
ErrorPlaceholder="user_100"
DownsampleToViewSize="true"
CacheDuration="0"
HeightRequest="90"
WidthRequest="90"
Aspect="AspectFill"/>
The image does not respect the defined size if it is not a square, exceding in the major dimension. This behavior happens only on Android.

It's Xamarin.Forms bug. Duplicate & more info here: https://github.com/luberda-molinet/FFImageLoading/issues/830


information_schema.tables missing last_altered column

I eluded to this issue in https://github.com/tekumara/fakesnow/pull/122#issuecomment-2267340187, but not all of duckdb's exactly match snowflakes.
Now, at least, I actually have a concrete location in which it negatively affects my ability to test 😆, i.e. information_schema.tables's missing last_altered column.
My first thoughts would be:

I assume we can't mutate the duckdb information_schema
if this is something you want to support fixing, I could attempt creating a _fs_information_schema with at least a view pointing at the original with the missing column

Seems impractical to actually support the semantics behind, for example, that column(?)

Search every query for table references and swap any that point at information_schema to the new schema?

or perhaps just .tables in the short term, since it would otherwise require stubs for every information_schema table, not sure off the top of my head how many there are

Yes that makes sense and follows the exisiting pattern 😊


ECU-R shows entire lifetime energy consumed during one hour in the energy

I have the same issue her as mackowskim since a couple of days. I did an upgrade of the ecu-r plugin. After the upgrade it looks like the ECU plugin sometimes write a zero in the entity "sensor.ecu_lifetime_energy" . If the next data is correct again (e.g. 400kWh) Then the statistics will giva a value of 400 because of the delta from 400-0 = 400.
Is it possible that the ECU-R plugin writes a zero when there is no connection to the gateway ? Is it a plan to block the updates of the entity "sensor.ecu_lifetime_energy" if the value is zero.
PS The entity sensor.ecu_today_energy" does nog have any gliches.

In version 1.2.19 I removed the check because out-of-the-box ECU's do have zero lifetime energy. I will reintroduce the check and figure out a way around that for freshly connected ECU's. The zero values are under some circumstances received from the ECU they are not produced by the intergration.

Thanks for your reply and your hard work !!

Released v1.2.23 where I re-introduced the check on zero values for life-time energy.


activeTerminal undefined for first terminal even when visible

When there are no terminals, and then a terminal is created and shown with the following code, the terminal is visible but vscode.windows.activeTerminal is still undefined. Once a second terminal has been created, activeTerminal works fine.
const myTerminal = vscode.window.createTerminal(`My Terminal #${NEXT_TERM_ID++}`);
myTerminal.show(true);

VSCode Version: 1.48.2
OS Version: Windows 10
Version: 1.48.2 (system setup)
Commit: a0479759d6e9ea56afa657e454193f72aef85bd0
Date: 2020-08-25T10:13:11.295Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18362

Steps to Reproduce:
To try to make a minimal reproducible example, I have made a small change to one of the Extension Samples. You can see my modification to the Microsoft version here: https://github.com/microsoft/vscode-extension-samples/compare/master...andycraig:master?expand=1

Download/clone my version from https://github.com/andycraig/vscode-extension-samples/tree/master

File -> Open Folder... -> vscode-extension-samples/terminal-sample

Run -> Start Debugging

Close existing terminal

Command Terminal API: Create & Show Terminal

Observe terminal appears, and message 'onDidOpenTerminal, name: My Terminal #1'

Command Terminal API: Check activeTerminal

Observe message 'activeTerminal is undefined'
Unexpected, as 'My Terminal #1' is visible.

Command Terminal API: Create & Show Terminal

Observe terminal appears, and message 'onDidOpenTerminal, name: My Terminal #2'

Command Terminal API: Check activeTerminal

Observe message 'activeTerminal: My Terminal #2'
This is as expected.

If 'My Terminal #2' is closed, activeTerminal correctly becomes 'My Terminal #1'. If this is closed, and the steps repeated, the message 'activeTerminal is undefined' will appear again.
Things DO work as expected if the terminal is created and shown with Terminal API: Create Terminal and Terminal API: Show, then verified with Terminal API: Check activeTerminal: this produces the message 'activeTerminal: Ext Terminal #1'. So it seems somehow specific to the code at the top of this issue.

Does this issue occur when all extensions are disabled?: Yes
I identified this while following up on a discussion at #105944. There are some activeTerminal issues that look related, like #53107, but I couldn't find one describing this problem.

I'm the author of the Angular Schematics extension (400 000+ users), and I'm also facing an issue with unreliable vscode.window.activeTerminal.
But the issue seems much larger than what is described here, for me the activeTerminal API is totally buggy.
For short, my extension is using a terminal to launch Angular CLI commands, and I would like to switch back to the previously active terminal (generally there will be a terminal with npm start / ng serve running) once it's done. See cyrilletuzi/vscode-angular-schematics#396
So I'm storing vscode.window.activeTerminal to show it back after, but the value is rarely right.
For example, if I open a terminal, launch any command (like echo 'world'), then open another terminal (with the "+" button), launch any command, then use my extension, the first terminal will be displayed back instead of the second.
Things get more and more messier if I delete terminals, add new ones, switch between them, etc.
Seems to me there is a lot of cases where vscode.window.activeTerminal is not updated at all. When looking in the repo issues, I've seen quite of a lot of related issues closed while not really being fixed.
@Tyriar as you tagged this issue, do you know what's the status about this issue and this API in general?

I'm the author of the Angular Schematics extension (400 000+ users), and I'm also facing an issue with unreliable vscode.window.activeTerminal.
But the issue seems much larger than what is described here, for me the activeTerminal API is totally buggy.
For short, my extension is using a terminal to launch Angular CLI commands, and I would like to switch back to the previously active terminal (generally there will be a terminal with npm start / ng serve running) once it's done. See cyrilletuzi/vscode-angular-schematics#396
So I'm storing vscode.window.activeTerminal to show it back after, but the value is rarely right.
For example, if I open a terminal, launch any command (like echo 'world'), then open another terminal (with the "+" button), launch any command, then use my extension, the first terminal will be displayed back instead of the second.
Things get more and more messier if I delete terminals, add new ones, switch between them, etc.
Seems to me there is a lot of cases where vscode.window.activeTerminal is not updated at all. When looking in the repo issues, I've seen quite of a lot of related issues closed while not really being fixed.
@Tyriar as you tagged this issue, do you know what's the status about this issue and this API in general?

For info, its back to normal in VS Code 1.53. So I'll unsubscribe from this issue.

@cyrilletuzi Thank you for the update!
I have tested in VS Code 1.53 too and the bug I reported no longer happens. The active terminal is now the visible terminal, as expected. I will close this issue. @Tyriar If you fixed this, thank you!