Can't start flexget in Asuswrt

I've been running flexget successfully for a while in my Asus AC-RT56U router for a while (v1.X). The router is running Merlin's version of the firmware. After setting it up on a Raspberry pi, I found out the new website and the updated 2.X version of flexget, and decided to update the version running on my router. Since the update (done with pip install --upgrade flexget), I haven't been able to run it, as it crashes with an error related to lib2to3.
Expected behaviour:
Running flexget -v would show the installed version
Actual behaviour:
Flexget crashes with the following error
Traceback (most recent call last):
  File "/opt/bin/flexget", line 7, in <module>
    from flexget import main
  File "/opt/lib/python2.7/site-packages/flexget/__init__.py", line 11, in <module>
    from flexget import logger
  File "/opt/lib/python2.7/site-packages/flexget/logger.py", line 20, in <module>
    from flexget.utils.tools import io_encoding
  File "/opt/lib/python2.7/site-packages/flexget/utils/tools.py", line 5, in <module>
    from past.builtins import basestring
  File "/opt/lib/python2.7/site-packages/past/__init__.py", line 88, in <module>
    from past.translation import install_hooks as autotranslate
  File "/opt/lib/python2.7/site-packages/past/translation/__init__.py", line 41, in <module>
    from lib2to3.pgen2.parse import ParseError
ImportError: No module named lib2to3.pgen2.parse

Steps to reproduce:
Install flexget following the instructions on the wiki (soma packages failed, is it because wiki needs update or because they are not available in entware for Merlin's AsusWRT?)
Run flexget
The program has been working before, with one of the 1.X versions, but I updated to the latest version and I haven't been able to run it.
Config:
Nothing out of the ordinary
Log:
Can't generate a log, flexget refuses to run
Additional information:

Flexget Version: 2.1.15
Python Version: 2.7.11
Installation method: pip install, as per the wiki.
OS and version: Merlin's AsusWRT 380.59
Link to crash log: Can't generate log

If some info is missing, please tell me and I will update the issue.

Duplicate of #1093


Bulky build size with lodash.isequal?

Hi, I was examining the output of npm run build:umd:min -- --display-modules, and found the lodash.isequal is incredibly large:
npm run build:umd:min -- --display-modules

><EMAIL_ADDRESS>build:umd:min /Users/siqitian/Desktop/react-web-animation
> cross-env NODE_ENV=production webpack src/index.js dist/react-web-animation.min.js "--display-modules"

Hash: cf2f4056f2768d51e2b0
Version: webpack 1.14.0
Time: 1685ms
                     Asset   Size  Chunks             Chunk Names
react-web-animation.min.js  25 kB       0  [emitted]  main
   [0] ./src/index.js 1.64 kB {0} [built]
   [2] ./src/animatable.js 4 kB {0} [built]
   [3] ./src/effect.js 7.77 kB {0} [built]
   [4] ./src/mixins/playable.js 4.01 kB {0} [built]
   [5] ./~/lodash.assign/index.js 16.7 kB {0} [built]
   [6] ./~/lodash.isequal/index.js 49.6 kB {0} [built]
   [7] ./src/animation.js 5.4 kB {0} [built]
   [8] ./src/animation_group.js 1.95 kB {0} [built]
   [9] ./src/animation_sequence.js 1.99 kB {0} [built]
  [10] (webpack)/buildin/module.js 251 bytes {0} [built]
    + 1 hidden modules

Would it sound like a good idea if we use lodash ^4.11.0 but import with:
import _isEqual from 'lodash/isEqual';

@SiqiTian-minted we are already only including the items from lodash we need. Namely, assign and isEqual. Unless, I am missing something, your proposed example is another way of doing the same thing

Yes, I agree. But it looks like the lodash.isequal standalone package is a custom build of lodash, not just isEqual. Individual lodash functions are usually <10 kb I think. I full build of lodash is about 49 kb. Looks like something wrong with the lodash.isequal package itself.

Asking at lodash https://github.com/lodash/lodash/issues/3067

@bringking did not get a satisfactory response there, i will try use selective import and if that helps bringing down the size, will do a PR

can close


fix(badge): put matBadgeDescription on host instead of badge element

Description from git commit
Fixes a screenreader issue on the mat-badge component where
screenreaders did not read the matBadgeDescription for badges hosted
on button elements.
Example:
<button mat-badge="2" matBadgeDescription="2 unread messages">open
messages</button>

As tested on Chromevox with Chrome browser, screenreader reads "open
messages" and does not read "2 unread messages". Screenreader does not
allow navigation to the badge element.
This happens because button's are not supposed to have multiple lines.
Solution is to align with tooltip by making the badge element
aria-hidden and applying the matBadgeDescription to the host element.
Why this is a draft
This is still a draft because we need to determine how to handle when a matBadgeDescription is not provided.
Exhibit A
Open messages
Previously, screenreaders could navigate to the badge element, which would be announced as "2" in this example. This change hides the badge element from screenreaders, so the button would be announced as "Open messages"
Our options are to either not put an aria-describedby at all when matBadgeDescription is missing, or fallback to using the content of matBadge for the aria-describedby.
I'm leaning towards no doing a fallback. If the app developer does not provide a matBadgeDescription then screenreaders will not read the badge. A developer might want to explicitly hide the badge from screen readers and there is nothing in the API that exposes aria-hidden.

@zarend I think this PR is superseded by https://github.com/angular/components/pull/23562
(I wasn't aware you had sent this PR until I was looking through open PRs this morning)

closing in favor of #23562


[QA] "Jump in" message remains on map after accessing selected place

Explorer Alpha build version:
Issue Description:
After opening the map, selecting a parcel to jump in and open the map again, the modal with info remains open.
Steps to reproduce:

Open the map and select a parcel
Use the Jump In option
Once teleported, open the map again

Expected behaviour:
Jump in option disappears
Current behaviour:
The option is still visible
Reproduction rate:

[ ] < 10%
[ ]  < = 25%
[ ]  50%
[ ]  < = 75%
[X]  100%

Severity:

[ ] Cosmetic
[X] Minor
[ ] Medium
[ ] High
[ ] Critical
[ ] Blocker

Priority:

[ ] High
[ ] Medium
[X] Low

Platforms / OS:

[ ] Windows 11
[X] Windows 10
[ ] Mac Sonoma
[ ] Mac (specify the version on Additional Notes)

Evidence:
https://github.com/decentraland/unity-explorer/assets/139157886/e155fd78-33f2-42cf-b964-4f43db50e66d
Additional Notes:

Fixed on build 0.3.236-main-ec5ece4


Untar using -xf instead of -xzf

Fixes #112
Unpacking XZ-compressed archives (like host_llvm_17.0.5_x86_64-unknown-linux.tar.xz) with GNU tar requires either using the -J flag or none at all (rather than the -z flag, which seems to be reserved for gzip). On macOS, -xzf behaves like -xf, which is likely why this issue didn't come up there.
With -xf both macOS and GNU tar automatically recognize the right format.

@swift-ci test


How can AVS return text in the response?

for example when I say "alexa,what‘s the weather in New York", avs response "New York would be cloudy at the time with the temperature from eighteen to twenty-eight."。both two is sound, how can i get text。
thanks

Hi @ZhangyeAye, to get the text of the speech response you can enable captions by following these instructions: https://developer.amazon.com/en-US/docs/alexa/avs-device-sdk/features.html#captions.
However, please keep in mind that captions should only be used for accessibility / UI purposes and not have business logic built on top of them.

Hi @wryley-amzn Thank you for your reply, but this is not what I wanted.
What I want is to return text via Alexa Voice Service without using DeviceSDK.
Thank you very much!

Please see this page for what is returned from the cloud for speak directives - perhaps something you need is there. https://developer.amazon.com/en-US/docs/alexa/alexa-voice-service/speechsynthesizer.html

Hello @EastApex,
Due to the inactivity of this ticket, this ticket will be closed. Please feel free to re-open the ticket if you have more questions or feel that your question was not been answered fully.


FR: single file watch mode

Is this a bug report or a feature request?
feature request
Version Info

Version of Majestic: v1.7.0
Version of Jest: v25
Version of Node:
Operating System:

Reproduction Repo
There is a watch mode in Majestic already. It would be nice if there  was a way to execute a watch mode on a single file. Jest supports this. I would recommend that a new button with the eye icon be added beside the run icon. In order to save space, the word run could be dropped from that button.
The benefit of this would be automatic running of tests from a single file. I find myself (and I assume others) end up working in a single test file for a while, writing and fixing a number of tests related to that file. Yes there is the overall watch mode that can be used, but I have found that it runs too many tests and takes longer than it needs to.

It turns out that this is already implemented. When I went looking in the code for how to implement this, I found that it is already implemented. Here is how you enable it:
click on the "start watching" button on the left side panel.
Then find the test file you want to run in watch mode.
click on that file to make it visible in the right panel
click on the run button in the upper right window of the single test panel.
This then runs jest in watch mode (because watch mode was toggled on) but for a the single file. It is now much faster running tests for this file over and over again as you work on the file.


Error about workspaces(multi packages) and cli-plugin-e2e-cypress

Version
3.0.4
Reproduction link
https://github.com/duduluu-contrib/vue-cli-bug00
Node and OS info
node v10.11.0 / yarn 1.9.4 / OS WSL ubutun18.04
Steps to reproduce
clone the repo and checkout branch with-e2e-cypress
go into the project 'packages/ts' directory and run yarn serve
What is expected?
Expect cli-service serve and build work fine, but not.
What is actually happening?
duduluu @ duduluu-i7 : /mnt/w/me/vue-cli-bug00/packages/ts (with-e2e-cypress)
$ yarn serve
yarn run v1.9.4
$ vue-cli-service serve --open
 INFO  Starting development server...
Starting type checking and linting service...
Using 1 worker with 2048MB memory limit
 94% after seal

 ERROR  Failed to compile with 1 errors                                                                    3:46:35 PM

Failed to resolve loader: babel-loader
You may need to install it.                                                                           Type checking and linting in progress...
No type errors found
No lint errors found
Version: typescript 3.0.3, tslint 5.11.0
Time: 3392ms

duduluu @ duduluu-i7 : /mnt/w/me/vue-cli-bug00/packages/ts (with-e2e-cypress)
$ yarn build
yarn run v1.9.4
$ vue-cli-service build

⠙  Building for production...Starting type checking and linting service...
Using 1 worker with 2048MB memory limit
⠦  Building for production...

 ERROR  Failed to compile with 1 errors                                                                    3:58:37 PM

Failed to resolve loader: babel-loader
You may need to install it.
 ERROR  Build failed with errors.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There is a branch without-e2e-cypress, the cli-service work fine on serve and build.

This only happens when the project is in workspaces.
Some times it will Error: Cannot find module '@babel/parser', it may be about other plugins, but I cannot reproduce at present.

the error about @babel/parse and postcss
at branch 'babel-parse-and-postcss'
duduluu @ duduluu-i7 : /mnt/w/me/vue-cli-bug00/packages/ts (babel-parse-and-postcss *)
$ yarn serve
yarn run v1.9.4
$ vue-cli-service serve --open
 INFO  Starting development server...
Starting type checking and linting service...
Using 1 worker with 2048MB memory limit
 94% after seal

 ERROR  Failed to compile with 2 errors                                                                    4:10:07 PM

 error  in ./src/views/Home.vue?vue&type=script&lang=ts&

Module build failed (from /mnt/w/me/vue-cli-bug00/node_modules/babel-loader/lib/index.js):
Error: Cannot find module '@babel/parser'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at _parser (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/parse.js:19:16)
    at parseWithCodeFrame (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/parse.js:145:16)
    at parseAndBuildMetadata (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/parse.js:43:15)
    at buildLiteralData (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/literal.js:53:35)
    at literalTemplate (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/literal.js:20:7)
    at Function.ast (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/template/lib/builder.js:52:42)
    at maybeCreateConstructor (/mnt/w/me/vue-cli-bug00/node_modules/@babel/plugin-transform-classes/lib/transformClass.js:196:58)
    at buildBody (/mnt/w/me/vue-cli-bug00/node_modules/@babel/plugin-transform-classes/lib/transformClass.js:212:5)
    at classTransformer (/mnt/w/me/vue-cli-bug00/node_modules/@babel/plugin-transform-classes/lib/transformClass.js:648:5)
    at transformClass (/mnt/w/me/vue-cli-bug00/node_modules/@babel/plugin-transform-classes/lib/transformClass.js:697:10)
    at PluginPass.ClassExpression (/mnt/w/me/vue-cli-bug00/node_modules/@babel/plugin-transform-classes/lib/index.js:104:54)
    at newFn (/mnt/w/me/vue-cli-bug00/node_modules/@babel/core/node_modules/@babel/traverse/lib/visitors.js:193:21)

 @ ./src/views/Home.vue?vue&type=script&lang=ts& 1:0-352 1:368-371 1:373-722 1:373-722
 @ ./src/views/Home.vue
 @ ./src/router.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080/sockjs-node (webpack)/hot/dev-server.js ./src/main.ts

 error  in /mnt/w/me/vue-cli-bug00/node_modules/normalize.css/normalize.css

Module build failed (from /mnt/w/me/vue-cli-bug00/node_modules/postcss-loader/lib/index.js):
Error: No PostCSS Config found in: /mnt/w/me/vue-cli-bug00/node_modules/normalize.css
    at config.load.then (/mnt/w/me/vue-cli-bug00/node_modules/postcss-load-config/src/index.js:55:15)

 @ /mnt/w/me/vue-cli-bug00/node_modules/normalize.css/normalize.css 4:14-132 14:3-18:5 15:22-140
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080/sockjs-node (webpack)/hot/dev-server.js ./src/main.ts
                                                                                WARNING in /mnt/w/me/vue-cli-bug00/packages/ts/src/main.ts
13:11 Parentheses are required around the parameters of an arrow function definition
    11 |   router,
    12 |   store,
  > 13 |   render: h => h(App)
       |           ^
    14 | }).$mount('#app');
    15 |
WARNING in /mnt/w/me/vue-cli-bug00/packages/ts/src/main.ts
13:22 Missing trailing comma
    11 |   router,
    12 |   store,
  > 13 |   render: h => h(App)
       |                      ^
    14 | }).$mount('#app');
    15 |
No type errors found
Version: typescript 3.0.3, tslint 5.11.0
Time: 2449ms

Duplicate of https://github.com/vuejs/vue-cli/issues/2599
As a workaround you can manually add babel-loader to your dependencies.

Thanks for your report. I think it's also been reported before https://github.com/vuejs/vue-cli/issues/2572

The two issues can be solved by adding these lines to vue.config.js:
module.exports = {
  css: {
    loaderOptions: {
      postcss: {
        path: __dirname
      }
    }
  },
  chainWebpack: config =>
    config.resolveLoader.modules.add(
      `${require.resolve('@vue/cli-plugin-babel')}/node_modules`
    )
}

Update: the original module path is wrong, I've updated it in the previous comment (should wrap the require.resolve call with path.dirname).

super thx


Use label selector in backup and restore lists

Fixes: #160
Signed-off-by: Nolan Brubaker<EMAIL_ADDRESS>

were you able to test this manually? since it's just in the client, you could build the binary locally and run against your existing server deploy. label some backups/restores and ensure the flag works as expected.

@skriss I did not; I will do so and provide output

@skriss Got it. I also notice that schedules are in a similar state- shall I go ahead and update them as well?

yeah, that'd be great.

Examples of the current code running against my small demo cluster:
% _output/bin/linux/amd64/ark restore get -l env=example
NAME                          BACKUP         STATUS      WARNINGS   ERRORS    CREATED                         SELECTOR
nginx-backup-20171031135557   nginx-backup   Completed   0          0         2017-10-31 13:55:57 -0700 PDT   <none>

% _output/bin/linux/amd64/ark backup get -l env=example
env=example
NAME           STATUS      CREATED                         EXPIRES   SELECTOR
nginx-backup   Completed   2017-10-31 13:52:46 -0700 PDT   21h       app=nginx

% _output/bin/linux/amd64/ark schedule get -l env=example
NAME         STATUS             CREATED                         SCHEDULE       BACKUP TTL   LAST BACKUP   SELECTOR
nginx-test   FailedValidation   2017-10-31 16:01:36 -0700 PDT   0 0 12 * * ?   24h0m0s      n/a           <none>

LGTM. Squash it down to 1 commit (lmk if you need a hand), and we'll merge it!


Dynamic history in memory

This PR optionally saves the transient history information in memory instead of writing and reading from disk. The disk IO option was causing significant slowdowns on parallel file systems.

Do we have a test for the case when save_to_disk is true? I may be missing something, but is the behavior different in the 2 cases now? If !save_to_disk, we auto checkpoint after every nonlinear solve, but I'm not seeing if that is still happening if save_to_disk==true? I may just be reading to quickly. Previously, this required a call to 'outputStateToDisk()'?

Good point. I'll auto-disk checkpoint if this option is on.

While trying to clean up the names, I came up with this more standardized approach using BasePhysics methods. Let me know what you think!

Codecov Report
Attention: Patch coverage is 78.57143% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 88.77%. Comparing base (7672d33) to head (cb291e4).

Files
Patch %
Lines

src/serac/physics/solid_mechanics.hpp
76.08%
11 Missing :warning:

src/serac/physics/heat_transfer.hpp
80.55%
7 Missing :warning:

src/serac/physics/base_physics.cpp
57.14%
3 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1086      +/-   ##
===========================================
- Coverage    88.85%   88.77%   -0.09%
===========================================
  Files          155      155
  Lines        12581    12628      +47
===========================================
+ Hits         11179    11210      +31
- Misses        1402     1418      +16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@kswartz92 , I reverted the API change. Internally, we are now group caching the requested cycle and just pulling from that if a different field from the same cycle is requested. This should reduce disk thrashing. Let me know if this works for you.

Do we have a test for the case when save_to_disk is true? I may be missing something, but is the behavior different in the 2 cases now? If !save_to_disk, we auto checkpoint after every nonlinear solve, but I'm not seeing if that is still happening if save_to_disk==true? I may just be reading to quickly. Previously, this required a call to 'outputStateToDisk()'?

I made two of the thermal dynamic adjoint tests use disk-based checkpointing and now automatically output to disk every timestep if this option is active.


Dupe bug in a patteren encoding

When you place item in a patteren, it takes item and imidealty you get a refund. When at the same item is in your inventory. After you double click item in a inventory you will also grab items from crafting grid. To perform this dupe you need at minimu 2 items.  You can not get back

Try this build i think it should be fixed - http://jenkins.bdew.net/job/ae2stuff-1.7.10/42/artifact/build/libs/ae2stuff-<IP_ADDRESS>-mc1.7.10.jar

Its fixed. I can no longer dupe items


New release with MIT license

As per discussion in https://github.com/coq-community/manifesto/issues/153, the project switched license to MIT. However, for this to be useful to library clients, there should ideally be another release of the project.
How about doing a release in the near future @womeier? Some low-hanging fruit in the form of deprecations could be fixed for this release:

the deprecation of the Arith.Lt file
the Fixpoint definition on line 15 of src/StringAsList.v doesn't make any recursive call, can be changed to Definition.

https://github.com/coq/opam/pull/2833
thanks! @palmskog


Syndicate Lobbying Bundle (briefcase with spacebucks)

About the PR

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Syndicate lobbying bundle: briefcase containing 30,000 spacebucks has been added to the uplink!

30,000 bucks for 1 TC is ludicrous

30,000 bucks for 1 TC is ludicrous

time for another gimmick Traitor purchase at 20TC?

30,000 bucks for 1 TC is ludicrous

Why tho? You can't put them in cargo console, for example, or do anything else. They are completely useless.

Why tho? You can't put them in cargo console, for example, or do anything else. They are completely useless.

wdym? you can sell them on the cargo shuttle for their equivalent value.

Why tho? You can't put them in cargo console, for example, or do anything else. They are completely useless.

wdym? you can sell them on the cargo shuttle for their equivalent value.

Dayum. I didn't know that. Perhaps, 2TC for 5k would be better?

I'm curious what would this be used for

i could see this being a pretty good item for bribing cargo, but IMO:

the amount needs to be balanced so that you can't completely invalidate other forms of money making
the briefcase and/or cash itself needs to be obnoxiously valid looking. I feel like cargo should know that taking 5k off of a suspicious looking guy is a syndie ploy.

wouldn't this make for a good cargo tech only item tho?
Unless there is cargo techy you must help to complete their objectives(or the other way around) i really don't see any uses from this purchase
(Let's be honest salvage don't need this one with all the weapons they hoard)

How would the current ruleset and player mentality handle this? Wouldn't accepting a syndicate briefcase fall under "cooperation with a syndicate member", and wouldn't players just go "HOLY SHIT SYNDIE BRIEFCASE RED ALERT CONFIRMED SYNDIES ON BOARD" upon seeing a briefcase with $30,000

im thinking traitor supply are just gonna buy tons of these and sell them all

new cargo meta

In the future, it would be best if unrelated changes (e.g. to capitalization of other items) are separate commits, so that if reverts need to happen they can happen individually.
This sounds pretty amusing and would be fun if we could come to an agreement on the numbers.

I don't think it would be a good idea to make it job-specific. I also increased the price of the item to 4TC for 5000 spacebucks, /tg/station-like.
What else can I do to balance it out?

In the future, it would be best if unrelated changes (e.g. to capitalization of other items) are separate commits, so that if reverts need to happen they can happen individually.

Noted

i think this is pretty fun. 5k is reasonable for 4TC and there's some interesting roleplay/bribe opportunities that can arise out of this.


feat(mis)!: replace assoc table name with slurm cluster name config

Description
The slurm script needs the name of the table associationTableName containing user association information. Most users don't care about the db structure created by slurm. Actually, the value is generated by slurm with format {cluster name}_assoc_table where the cluster name is set by user.
This PR replaces associationTableName config key to clusterName config key so that the user don't have to know the table name, but only need the cluster name in slurm.
Migration
This is a BREAKING change. Current deployed SCOW needs the following steps to migrate to the latest version

Replace the slurm.sh with the latest version
In the clusters/{cluster}.yaml files, replace the associationTableName config with clusterName and set the values to the name in slurm

Codecov Report

Merging #178 (3ec1067) into master (839ae50) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #178   +/-   ##
=======================================
  Coverage   70.72%   70.72%
=======================================
  Files          94       94
  Lines        2282     2282
  Branches      270      270
=======================================
  Hits         1614     1614
  Misses        634      634
  Partials       34       34

Impacted Files
Coverage Δ

...pps/mis-server/src/clusterops/slurm/utils/slurm.ts
31.25% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Localization/translation?

I know that this superb project is still in early beta stage :-)
But for everyday use by family it would be nice to have native language setup (OK thanks to lokalise we have a frontend native language for Alarm Panel at least)- as some of them are smart enough to add/delete something (with permissions but not enough English knowledge :-( )
That would make a great WAF effect :-)
Best, JR

I am currently changing the frontend quite a bit, all texts in the panel will be loaded from a localize file.
So preparations are being made for supporting multi-language UI.
I think its still a bit early-stage to start rolling out translations though...
Chances are that the files need to be revised often.
Eventually this is up to the volunteers/enthousiasts themselves to decide...
I will keep you posted if I have made more progress here.

Are you still interested in using Alarmo and helping out with the translation?
I think in the meantime the 'dust has settled', the UI will not change much now.

Hi, i can help you to translate in italian if you want.
Contact me if you want :-)

@mccoy88f if you want to contribute with a translation, please take this file as starting point: https://raw.githubusercontent.com/nielsfaber/alarmo/main/custom_components/alarmo/frontend/localize/languages/en.json
If you replace all texts by Italian translation, it can be added.
You can also propose improvements for the original English file.

Ok i Will work on It this night 💪

Is there a way to test it locally on my ha? I have a alpha version :-)

Is there a way to test it locally on my ha? I have a alpha version :-)

Yes there is, but it is not trivial.
If you make a full checkout of this repository, you can make changes to the frontend.
You will need to have node.js / npm + some packages to be able to work with it.
If you run npm install and then npm start (from the /frontend/ directory), the script should automatically recompile the typescript files when you make a change.
You could replace the en.json with your italian version, or add yours and update the localize.ts.
If you don't want to go through this trouble, you can also just open a PR with your it.json.
You can see the results when a next update is released.

I will close this issue since the translation of @Repsionu is now in place.
More translations are always welcome, if help is needed let me know.

Hi.
This is the translation in italian.
After the next update i will verify and correct it if needed.
My user on github is mccoy88f and my name is Antonello Migliorelli
Thanks a lot for your work
If there is something more to translate please let me know
Il giorno mer 16 dic 2020 alle ore 08:16 Niels Faber <
<EMAIL_ADDRESS>ha scritto:

I will close this issue since the translation of @Repsionu
https://github.com/Repsionu is now in place.
More translations are always welcome, if help is needed let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nielsfaber/alarmo/issues/1#issuecomment-745816131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMCHB26FQN7GHZDK22HGRFLSVBNE3ANCNFSM4S6Q3DRA
.

This is my italian translation add to next version to test it:
https://pastebin.com/tTdxaZH2
Thanks


Add getDelegatorsUnbondingLocks method to SDK

What's the problem? (required)
The has SDK has no default methods to get a Delegator's unbondingLocks.
What's the current behavior? (required)
Currently there is only a way to get a Delegator's unBondingLockNextId.
Describe a possible solution you've considered (optional)
I want to be able to call a method in the SDK to get all the unbondingLocks of any Delegator and I want to be able to do this through LivepeerJs graphql-sdk.
Additional context (optional)
Since a Delegator's unbondingLocksIds are stored in order and starts from 0, then getting the unbondingLockNextId from the getDelegator method in the SDK means that the  getDelegatorUnbondingLock method can be used to loop and decrement from unbondingLockNextId to 0 until all unbondingLock are acquired for any Delegator.

@Randy1Burrell I have implemented this. I added the below method to the sdk
 async getDelegatorUnbondingLocks(
      addr: string,
 ): Promise<Array<UnbondingLock>> {
     let { nextUnbondingLockId } = await getDelegator(addr)
      let result = []

      if (nextUnbondingLockId == 0) return result

      while (nextUnbondingLockId != 0) {
        const unbond = await getDelegatorUnbondingLock(
          addr,
          nextUnbondingLockId,
        )
        result.push(unbond)
        nextUnbondingLockId -= 1
      }
}
      return result

But I am facing an issue, to test changes in the graphql-sdk in the explorer package, is there a process to it?


update clFFT and include modern FindOpenCL.cmake

mainly doing this for the cmake script, trying to build arrayfire against rocm standalone and it's a battle.

@nevion I am changing the base to release-test branch. You can change the branch accordingly inbuild-clfft.cmake file.


test/functional: prevent read/write data race in klog.

Prevent grpc from triggering read/write data race
(concurrent klog flag.Set() by our klogcontrol and
klogging connection complaints by default grpc log)
by overriding the grpc logger.

Codecov Report

Merging #4 (6b7fd39) into devel/k8s-1.19.4 (42e83bc) will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           devel/k8s-1.19.4       #4   +/-   ##
=================================================
  Coverage             34.71%   34.71%
=================================================
  Files                    60       60
  Lines                  6484     6484
=================================================
  Hits                   2251     2251
  Misses                 3993     3993
  Partials                240      240

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 42e83bc...6b7fd39. Read the comment docs.


Error with binds

Hi,
When viewing a polymer like the attached file with the NGL viewer the links are not represented.
polymer.gro.zip
Any idea what is happening? Is it a NGL error?
Thanks

There's a message printed to the console when you load that file about a residue having more than 500 atoms (and therefore NGL skipping autobonding). Can you assign some appropriate residue numbers (it looks like a poly-ester - maybe increment the residue number each time you get back to O1?)

Thank you, that is!


Add contribution and pull request guide

Following up https://github.com/asakusafw/asakusafw/pull/617 .

Can one of the admins verify this patch?


client application folder structure is wrong

please only one folder javascript, one folder for stylesheets, not many
I would suggest
/js
/style
style/icons
style/images

Solved in #55


[AutoPR azure-kusto/resource-manager] Add codegen config for kusto api version 2019-05-15

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7019

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5613


Make a custom Logger wrapper

Since we will have a lot of logging to handle, a wrapper that handles whether to log something or not(depending on currently active logging level in config).. suffix etc

This sounds good, it would extend the slf4j Logger that Sponge uses?

it will just wrap around it... yes..

Sounds good to me.

This is under way, however, because config file is not available, currently it will not check if a message has to be logged or not

MCLogger is now an instance of org.slf4j.Logger
The PR should be in tomorrow


Only query advisory database on latest matching version

This pull request creates a new distinction between dependencies which are

always insecure: shown in red, where even the latest version (in range) of a dependency is not patched;
possibly insecure: (has at least one vulnerability in any version in the range)

Resolves #94 , and also reduces the number of queries to the advisory DB.
Summary:

Update project status page

show always insecure dependencies as insecure, and remaining ones as "possibly insecure"
show warning sign on all dependencies with possible vulnerability
tweak security banner in case all insecure dependencies are "possibly insecure"

Update badge

Only show the red "insecure" if at least one dependency is always insecure
show "possibly insecure" if all are up to date but might be vulnerable

I think #97 is a different bug to #94, but let's see.

Drafting this to better fulfill the new set of requirements proposed in #94. Namely:

The list of known vulnerabilities should still appear at the bottom of the project page.
Will consider also presenting direct dependencies as "possibly insecure" if at least one version admitted by the project is insecure.

Both of these will mean reverting several changes here, but IMO they will be worth it.

This PR is now open for feedback. See the first post for the summary of changes. Some points to evaluate:

How should "possibly insecure" dependencies and projects be presented at the various levels.
What colors should be used (banners, badges, etc)
Whether the "always insecure" logic should account for more than just the latest dependency in the range.


Vivian glass tweaks

Old glass/pane texture:

New glass/pane texture:

and organizational tweaks to the file/folder names.

Corners and edges are still kind of messed up, but I suppose it's the best we can do for now...


TestAsset has been setup incorrectly on linea

Describe the bug
The canonical id of TestERC20 should be 0x0000000000000000000000007ea6ea49b0b0ae9c5db7907d139d9cd3439862a1. but on linea it is 0x000000000000000000000000b4fbf271143f4fbf7b91a5ded31805e42b2208d6
TheTestERC20 token transfers to linea are getting stuck forever due to the incorrect asset setup

Update:

Both canonical ids registered onchain with the same TEST asset
The subgraph was storing the Asset entity under the local address emitted in the event
When the asset with id 0x000000000000000000000000b4fbf271143f4fbf7b91a5ded31805e42b2208d6 was registered after 0x0000000000000000000000007ea6ea49b0b0ae9c5db7907d139d9cd3439862a1, because they both shared the same local asset, the canonical id was overwritten

Solution:

Refactor subgraph to store Asset entity with hash(canonicalId, canonicalDomain)
Remove the AssetStatus entity, and instead add it to the corresponding Asset entity


Test Elixir 1.4 & OTP 19.2

Maybe use only the latest minor versions?
elixir

1.3.4
1.4.0

otp

18.3
19.2

Coverage remained the same at 98.198% when pulling 04cdad4cbe3d30bd4fdcb479603a23c1f29e7e79 on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.

Coverage remained the same at 98.198% when pulling 04cdad4cbe3d30bd4fdcb479603a23c1f29e7e79 on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.

Coverage remained the same at 98.198% when pulling 04cdad4cbe3d30bd4fdcb479603a23c1f29e7e79 on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.

Coverage remained the same at 98.198% when pulling 04cdad4cbe3d30bd4fdcb479603a23c1f29e7e79 on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.

Coverage remained the same at 98.198% when pulling 04cdad4cbe3d30bd4fdcb479603a23c1f29e7e79 on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.

Yes, that'd be much faster on travis.

Coverage remained the same at 98.198% when pulling b82ed2ed5c671c787c4400d16ced7a0d0cc4626d on jshmrtn:feature/test_elixir_1.4_and_otp_19.2 into 5a45979309f5a1832d779d34de40f181eca5b3f8 on c-rack:master.


[WFLY-19578] Upgrade WildFly Core to 26.0.0.Beta1

Jira issue: https://issues.redhat.com/browse/WFLY-19578

Tag: https://github.com/wildfly/wildfly-core/releases/tag/26.0.0.Beta1
Diff: https://github.com/wildfly/wildfly-core/compare/25.0.0.Final...25.0.0.Beta1

        Sub-task

[WFCORE-6908] -         Remove usage of deprecated AbstractAddStepHandler constructors in wildfly-controller/host-controller/server

[WFCORE-6909] -         Remove usage of deprecated AbstractAddStepHandler constructors in core-management subsystem

[WFCORE-6910] -         Remove usage of deprecated AbstractAddStepHandler constructors in domain-management

[WFCORE-6912] -         Remove usage of deprecated AbstractAddStepHandler constructors in jmx subsystem

[WFCORE-6914] -         Remove usage of deprecated AbstractAddStepHandler constructors in tests

[WFCORE-6915] -         Remove usage of deprecated AbstractAddStepHandler constructors in request-controller subsystem

[WFCORE-6916] -         Remove usage of deprecated AbstractAddStepHandler constructors in security-manager subsystem

[WFCORE-6917] -         Remove usage of deprecated AbstractAddStepHandler constructors in threads subsystem

[WFCORE-6918] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in wildfly-controller

[WFCORE-6919] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in core-management

[WFCORE-6920] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in deployment-scanner

[WFCORE-6921] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in domain-management

[WFCORE-6923] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in host-controller

[WFCORE-6924] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in IO subsystem

[WFCORE-6925] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in jmx subsystem

[WFCORE-6926] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in logging subsystem

[WFCORE-6927] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in remoting subsystem

[WFCORE-6928] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in wildfly-server

[WFCORE-6929] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in request-controller subsystem

[WFCORE-6930] -         Remove usage of deprecated AbstractWriteAttributeHandler constructors in testsuite

        Bug

[WFCORE-6874] -         Apply server candidate phase logs are not saved in log files when using Management CLI

        Task

[WFCORE-6813] -         Extract read-config-as-xml-file tests in individual test classes or methods

[WFCORE-6880] -         Bump the kernel management API version to 27.0.0

[WFCORE-6897] -         Remove usage of deprecated WildflyTestRunner class

        Component Upgrade

[WFCORE-6855] -         Upgrade JGit from to <IP_ADDRESS>406032230-r

[WFCORE-6885] -         Upgrade SSHD from 2.12.1 to 2.13.1

[WFCORE-6905] -         Upgrade Galleon to 6.0.2.Final and Galleon Plugins to 7.1.1.Final

[WFCORE-6906] -         Upgrade Installation Manager API to 1.0.3.Final

[WFCORE-6932] -         Upgrade commons-lang3 from 3.14.0 to 3.15.0

        Enhancement

[WFCORE-6869] -         Update OpenSSLTLSTestCase to use PKCS#12 KeyStores

[WFCORE-6889] -         Add a ModuleDependency.Builder class

[WFCORE-6895] -         Add a grace period to Management CLI Installer Windows script

[WFCORE-6901] -         Create Phase IDs for OpenTelemetry

Thanks @yersan


fixing issues

Fixes #3 .
Changes proposed in this Pull Request:

updated codacy badge URLs (markdown format error, human generated)
tests for node v0.12 and v0.10; Travis CI is cranky

Current coverage is 93.75%

Merging #4 into master will not affect coverage as of 6b442c9

@@            master      #4   diff @@
======================================
  Files            3       3
  Stmts           48      48
  Branches         0       0
  Methods          0       0
======================================
  Hit             45      45
  Partial          0       0
  Missed           3       3

Review entire Coverage Diff as of 6b442c9

Powered by Codecov. Updated on successful CI builds.

addresses #3


coq-elpi: 1.10.1 -> 1.10.2

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build coqPackages_8_13.coq-elpi coqPackages_8_13.hierarchy-builder

@GrahamcOfBorg build coqPackages_8_13.coq-elpi coqPackages_8_13.hierarchy-builder

We may need to update HB at the same time

Result of nixpkgs-review pr 126587 run on x86_64-linux 1

2 packages failed to build:

coqPackages.hierarchy-builder
coqPackages.mathcomp-analysis

1 package built:

coqPackages.coq-elpi

$ nix log /nix/store/mz5w8hsy72cx78wwl6vjm8h9k5q5b0q2-coq8.13-hierarchy-builder-1.1.0.drv | ix
http://ix.io/3uLY

We need to synchronise @CohenCyril

Note that on master I have updated hierarchy-builder to 1.1.0, so this needs rebasing.

@GrahamcOfBorg build coqPackages_8_13.coq-elpi coqPackages_8_13.hierarchy-builder


Cannot build kubernetes without go-runner

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest main-presubmit

/retest main-presubmit

/retest

/retest


Command '['update-ca-certificates']' returned non-zero exit status 1.

Describe the issue

Failed to load Additional CA integration.
Describe your setup (please complete the following information):

Installation type:  Docker
HAOS version (if applicable):
Home Assistant core version:  2024.12.3
Additional CA integration version:  0.2.4
Kind of certificate you use:  self-signed CA certificate

YAML configuration extract

default_config:

additional_ca:
  ng_ca: NG-CA.cert.pem
...

Logs

$ sudo docker logs homeassistant
...
2024-12-14 01:17:40.751 WARNING (MainThread) [custom_components.additional_ca.utils] 'update-ca-certificates' returned an error -> Command '['update-ca-certificates']' returned non-zero exit status 1.
2024-12-14 01:17:40.751 WARNING (MainThread) [custom_components.additional_ca] Additional CA setup has been interrupted.
2024-12-14 01:17:40.751 ERROR (MainThread) [homeassistant.setup] Error during setup of component additional_ca
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/homeassistant/setup.py", line 416, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/additional_ca/__init__.py", line 44, in async_setup
    await update_ca_certificates(hass, config, store)
  File "/config/custom_components/additional_ca/__init__.py", line 88, in update_ca_certificates
    update_system_ca()
    ~~~~~~~~~~~~~~~~^^
  File "/config/custom_components/additional_ca/utils.py", line 53, in update_system_ca
    status = subprocess.run(cmd, capture_output=True, check=True)
  File "/usr/local/lib/python3.13/subprocess.py", line 577, in run
    raise CalledProcessError(retcode, process.args,
                             output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['update-ca-certificates']' returned non-zero exit status 1.
...

Logs from Home Assistant WebUI
This error originated from a custom integration.

Logger: custom_components.additional_ca.utils
Source: custom_components/additional_ca/utils.py:55
integration: additional_ca (documentation, issues)
First occurred: 1:17:40 AM (1 occurrences)
Last logged: 1:17:40 AM

'update-ca-certificates' returned an error -> Command '['update-ca-certificates']' returned non-zero exit status 1.

This error originated from a custom integration.

Logger: custom_components.additional_ca
Source: custom_components/additional_ca/__init__.py:46
integration: additional_ca (documentation, issues)
First occurred: 1:17:40 AM (1 occurrences)
Last logged: 1:17:40 AM

Additional CA setup has been interrupted.

Logger: homeassistant.setup
Source: setup.py:416
First occurred: 1:17:40 AM (1 occurrences)
Last logged: 1:17:40 AM

Error during setup of component additional_ca
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/homeassistant/setup.py", line 416, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/additional_ca/__init__.py", line 44, in async_setup
    await update_ca_certificates(hass, config, store)
  File "/config/custom_components/additional_ca/__init__.py", line 88, in update_ca_certificates
    update_system_ca()
    ~~~~~~~~~~~~~~~~^^
  File "/config/custom_components/additional_ca/utils.py", line 53, in update_system_ca
    status = subprocess.run(cmd, capture_output=True, check=True)
  File "/usr/local/lib/python3.13/subprocess.py", line 577, in run
    raise CalledProcessError(retcode, process.args,
                             output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['update-ca-certificates']' returned non-zero exit status 1.

Additional context

What service/device are you trying to reach from Home Assistant with TLS/SSL ?

I am trying to connect to frigate with authentication on URI https://<IP_ADDRESS>:8971. It is newly supported by Frigate integration v5.6.0.
The folder structure inside docker:
# tree /config/
/config/
├── additional_ca
│   └── NG-CA.cert.pem
...
├── configuration.yaml
├── custom_components
│   ├── additional_ca
│   │   ├── __init__.py
│   │   ├── __pycache__
│   │   │   ├── __init__.cpython-313.pyc
│   │   │   ├── const.cpython-313.pyc
│   │   │   ├── storage.cpython-313.pyc
│   │   │   └── utils.cpython-313.pyc
│   │   ├── const.py
│   │   ├── manifest.json
│   │   ├── storage.py
│   │   └── utils.py

compose.yaml:
---
services:
  homeassistant:
    image: linuxserver/homeassistant:latest
    container_name: homeassistant
    deploy:
      resources:
        limits:
          memory: 2G
    network_mode: host
    environment:
      - PUID=1017
      - PGID=1017
      - TZ=Europe/London
      - REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "./config:/config:rw"
      - "./cctv/ha/hass_events:/cctv:rw"
      - "./cctv/ha/nest:/config/nest:rw"
      - type: volume
        source: cctv
        target: /cctv
        volume:
          subpath: ha/hass_events
      - type: volume
        source: cctv
        target: /config/nest
        volume:
          subpath: ha/nest
    restart: unless-stopped

@Athozs
Thanks a ton, mate!

Thanks for your reply.
I rather keep it running unprivileged.
Thanks to your hard work, it inspires me on how to get it working. As I am using a linuxserver.io release, it allows me to run a custom procedure before the main task. I have followed your footsteps to update the ca certificates.


Unobserved exception after creating virtual env

I'm on the latest from master.
Create new python application
Create virtual env based on CPython 3.5 32-bit
I went to do other stuff, came back and had this message box:
---------------------------
Assertion Failed: Abort=Quit, Retry=Debug, Ignore=Continue
---------------------------
An exception in a task was not observed. See ActivityLog.xml for more details.

System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> System.ObjectDisposedException: The semaphore has been disposed.

   at System.Threading.SemaphoreSlim.CheckDispose()

   at System.Threading.SemaphoreSlim.Release(Int32 releaseCount)

   at System.Threading.SemaphoreSlim.Release()

   at Microsoft.PythonTools.Ipc.Json.Connection.<SendMessage>d__23.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\Ipc.Json\Connection.cs:line 362

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()

   at Microsoft.PythonTools.Ipc.Json.Connection.<SendRequestAsync>d__13`1.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\Ipc.Json\Connection.cs:line 84

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<SendRequestAsync>d__122`1.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\PythonTools\PythonTools\Intellisense\ProjectAnalyzer.cs:line 1473

   --- End of inner exception stack trace ---

---> (Inner Exception #0) System.ObjectDisposedException: The semaphore has been disposed.

   at System.Threading.SemaphoreSlim.CheckDispose()

   at System.Threading.SemaphoreSlim.Release(Int32 releaseCount)

   at System.Threading.SemaphoreSlim.Release()

   at Microsoft.PythonTools.Ipc.Json.Connection.<SendMessage>d__23.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\Ipc.Json\Connection.cs:line 362

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()

   at Microsoft.PythonTools.Ipc.Json.Connection.<SendRequestAsync>d__13`1.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\Ipc.Json\Connection.cs:line 84

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<SendRequestAsync>d__122`1.MoveNext() in C:\Projects\huguesv\PTVS\Python\Product\PythonTools\PythonTools\Intellisense\ProjectAnalyzer.cs:line 1473<---

   at Microsoft.PythonTools.PythonToolsPackage.<>c.<.ctor>b__3_0(Object sender, UnobservedTaskExceptionEventArgs e) in C:\Projects\huguesv\PTVS\Python\Product\PythonTools\PythonToolsPackage.cs:line 200

   at System.Threading.Tasks.TaskScheduler.PublishUnobservedTaskException(Object sender, UnobservedTaskExceptionEventArgs ueea)

   at System.Threading.Tasks.TaskExceptionHolder.Finalize()

---------------------------
Abort   Retry   Ignore
---------------------------

This is fallout from fixing the FXCop complaints. We're not handling that exception in the right place.


pdfminer can't parse characters outside the ASCII encoding

Attached is a document in spanish that shows that pdfminer cant process latin characters like:
á, é, í, ó, ú, ñ, etc...

caixa-one-page-spanish.pdf

Sorry, I fail to understand the title, relative to the problem statement.
I understand this as "pdfminer can't parse characters outside the ASCII encoding"
(because the "accent" characters from French and Spanish etc. that you refer to are part of utf-8).
Probably I am just misunderstanding ?

It's actually more complicated than that.
Also: this behavior can also manifest on standard latin characters: it all depends on how the PDF document was encoded - a PDF can lack a complete textual mapping by omission since it is not an inherent purpose of the PDF format to provide the textual equivalent.
Related Issues:

https://github.com/axa-group/Parsr/issues/75
https://github.com/aarohijohal/pdfminer.six/issues/1
https://github.com/pdfminer/pdfminer.six/issues/130

Attached is a document in spanish that shows that pdfminer cant process latin characters like:
á, é, í, ó, ú, ñ, etc...

It's actually more complicated than that.
Also: this behavior can also manifest on standard latin characters: it all depends on how the PDF document was encoded - a PDF can lack a complete textual mapping by omission since it is not an inherent purpose of the PDF format to provide the textual equivalent.
Related Issues:

#75
aarohijohal/pdfminer.six#1
pdfminer/pdfminer.six#130

An interesting related patent: https://patents.google.com/patent/US20060288281

This is a general problem related to the extractors used, instead of being particularly Parsr's problem.


Adding Intel Compute Stick WiFi driver

Signed-off-by: Roman Shaposhnik<EMAIL_ADDRESS>

Yeah, in this particular case I'm inclined to ignore them (since the alternative is actually uglier).


Angular Dynamic Routing causes Canvas "Failed to execute 'toDataURL' error

I am using AngularJS built on top of Node/Express for a Web application. One of my routes has an HTML5 canvas that I convert to an image. If I traverse to that route with this, I have no issues with converting my canvas to an image:
when('/myroute/, { templateUrl: 'views/mytemplate.html', controller: 'myCtrl as vm' })

However, when I use dynamic routing (since I need to pass a unique ID to the 'myroute' page), the Canvas to image conversion throws the following error:

Failed to execute 'toDataURL' on 'HTMLCanvasElement': Tainted canvases may not be exported.

Here is the dynamic route syntax from my App.js:
when('/myroute/:ID, { templateUrl: 'views/mytemplate.html', controller: 'myCtrl as vm' })

Why would a dynamic route cause this... what appears to be a CORS issue, and how do I resolve it? Could it be related to "living" on top of Node.js/Express?
Here is an example of how I convert the Canvas to an Image:
var canvasImage = document.getElementById("c");
var img = canvasImage.toDataURL("image/png");

Update 1: I just tried the following, but received the same error:
var canvasImage = document.getElementById("c");
var img = new Image();
img.crossOrigin = "anonymous";
img.src = canvasImage;
img = canvasImage.toDataURL("image/png");

Please provide a live reproduction (e.g. using CodePen, Plnkr etc). It's next to impossible to tell what is causing the problem without a way to reproduce it.
Also, are you using html5Mode or "hashbang" mode ?

I am using html5 mode and for reasons beyond my control, I am not allowed to post the code.

If we don't have a demo, it's next to impossible to see where the error is. Basically, we cannot even see if the bug is in angular or in your app.

generalizing it may not give us what we need.
True, but before you haven't tried to create a minimal demo, you cannot be sure of that.

Fair enough, let me see what I can put together from a minimal standpoint. It will take some time, but appreciate all of yours!

Alright, I put together a plunk and found that the dynamic routing with a plain canvas worked. It is when I used a image from a server for an overlay that the CORS popped up. It shouldn't be, but it is. Closing this out.

Again, this is next to impossible to debug without  a reproduction.
But it sounds more likely like a CORS issue. Are you sure the server is configured properly ?

Yes, I am using Azure Blob Storage and it is loading the overlay on screen properly.

Yet, it seems to "taint" the canvas (it's not just a question of being displayed properly).

Correct, and there must be some sort of odd conflict somewhere since a static route works, but only when getting to the page via a dynamic route are there issues.

BTW, I wonder if using "hashbang" mode would make any difference.

Solved it. The issue was with Fabric.JS. Once I set the flag for crossOrigin anonymous on the overlay I was loading, it worked. Not sure why it worked with a standard route beforehand.

Good to hear that you solved it!


g.set_terminal_states doesn't change terminal_states_colors and terminal_states_names

Dear CellRank Team,
Thanks for developing this amazing tool! I am following the Kernels and estimators tutorial, and I want to manually set the terminal states for my dataset.
After I run g.set_terminal_states, I can see adata.obs['terminal_states'], adata.uns['terminal_states_colors'], and adata.uns['terminal_states_names'] are all set to my manually defined terminal states. The problem is that when I plot the terminal states cr.pl.terminal_states(adata, discrete=True), the adata.obs['terminal_states'], adata.uns['terminal_states_colors'], and adata.uns['terminal_states_names'] are setting back to the originally computed terminal states.
I tested the same code using the pancreas dataset (datasets/endocrinogenesis_day15.5.h5ad), the error is reproducible. Here is the code:
import scvelo as scv
import cellrank as cr
import scanpy as sc
import numpy as np

adata = cr.datasets.pancreas()
scv.pl.proportions(adata)
adata

scv.pp.filter_and_normalize(adata, min_shared_counts=20, n_top_genes=2000)
sc.tl.pca(adata)
sc.pp.neighbors(adata, n_pcs=30, n_neighbors=30)
scv.pp.moments(adata, n_pcs=None, n_neighbors=None)

scv.tl.recover_dynamics(adata, n_jobs=4)

scv.tl.velocity(adata, mode='dynamical')
scv.tl.velocity_graph(adata)

scv.pl.velocity_embedding_stream(adata, basis='umap', legend_fontsize=12, title='', smooth=.8, min_mass=4)

k = cr.tl.transition_matrix(adata)
g = cr.tl.estimators.GPCCA(k)
g.compute_schur(n_components=20, method='krylov')
g.compute_macrostates(cluster_key='clusters')
g.compute_terminal_states()

Then I check the automatically computed terminal states using the following code:
adata.obs['terminal_states']
adata.uns['terminal_states_colors']
adata.uns['terminal_states_names']

Here is the output:
adata.obs['terminal_states']
Out[24]:
index
AAACCTGAGAGGGATA-1-3    NaN
AAACCTGAGGCAATTA-1-3    NaN
AAACCTGGTAAGTGGC-1-3    NaN
AAACCTGTCCCTCTTT-1-3    NaN
AAACGGGAGTAGCGGT-1-3    NaN
                       ...
TTTGGTTTCCTTTCGG-1-3    NaN
TTTGTCAAGAATGTGT-1-3    NaN
TTTGTCAAGTGACATA-1-3    NaN
TTTGTCATCGAATGCT-1-3    NaN
TTTGTCATCTGTTTGT-1-3    NaN
Name: terminal_states, Length: 2531, dtype: category
Categories (3, object): ['Epsilon', 'Alpha', 'Beta']
adata.uns['terminal_states_colors']
Out[25]: array(['#cab2d6', '#1f78b4', '#b2df8a'], dtype='<U7')
adata.uns['terminal_states_names']
Out[26]: array(['Epsilon', 'Alpha', 'Beta'], dtype=object)

Next, manually define/set terminal states:
AlphaCell = (adata[adata.obs['clusters'] == 'Alpha']).obs_names[:30]
BetaCell = (adata[adata.obs['clusters'] == 'Beta']).obs_names[:30]
EpsilonCell = (adata[adata.obs['clusters'] == 'Epsilon']).obs_names[:30]
DeltaCell = (adata[adata.obs['clusters'] == 'Delta']).obs_names[:30]
tLable = pd.DataFrame({
    'Alpha': AlphaCell,
    'Beta': BetaCell,
    'Epsilon': EpsilonCell,
    'Delta': DeltaCell
})
tLable = tLable.to_dict(orient='list')
g.set_terminal_states(labels=tLable, cluster_key='clusters', add_to_existing=False)

Now, using the following code to check if the terminal states are manually set:
adata.obs['terminal_states']
adata.uns['terminal_states_colors']
adata.uns['terminal_states_names']

Here is the output:
adata.obs['terminal_states']
Out[33]:
index
AAACCTGAGAGGGATA-1-3      NaN
AAACCTGAGGCAATTA-1-3    Alpha
AAACCTGGTAAGTGGC-1-3      NaN
AAACCTGTCCCTCTTT-1-3    Alpha
AAACGGGAGTAGCGGT-1-3    Delta
                        ...
TTTGGTTTCCTTTCGG-1-3      NaN
TTTGTCAAGAATGTGT-1-3      NaN
TTTGTCAAGTGACATA-1-3      NaN
TTTGTCATCGAATGCT-1-3      NaN
TTTGTCATCTGTTTGT-1-3      NaN
Name: terminal_states, Length: 2531, dtype: category
Categories (4, object): ['Alpha', 'Beta', 'Delta', 'Epsilon']
adata.uns['terminal_states_colors']
Out[34]: ['#1f78b4', '#b2df8a', '#6a3d9a', '#cab2d6']
adata.uns['terminal_states_names']
Out[35]: array(['Alpha', 'Beta', 'Delta', 'Epsilon'], dtype=object)

Everything looks perfect so far, however, if I run this line of code cr.pl.terminal_states(adata, discrete=True). I can get an expected figure.

But if I check the terminal states again:
adata.obs['terminal_states']
adata.uns['terminal_states_colors']
adata.uns['terminal_states_names']

The terminal states are setting back to the original terminates states:
adata.obs['terminal_states']
Out[37]:
index
AAACCTGAGAGGGATA-1-3      NaN
AAACCTGAGGCAATTA-1-3    Alpha
AAACCTGGTAAGTGGC-1-3      NaN
AAACCTGTCCCTCTTT-1-3    Alpha
AAACGGGAGTAGCGGT-1-3    Delta
                        ...
TTTGGTTTCCTTTCGG-1-3      NaN
TTTGTCAAGAATGTGT-1-3      NaN
TTTGTCAAGTGACATA-1-3      NaN
TTTGTCATCGAATGCT-1-3      NaN
TTTGTCATCTGTTTGT-1-3      NaN
Name: terminal_states, Length: 2531, dtype: category
Categories (4, object): ['Alpha', 'Beta', 'Delta', 'Epsilon']
adata.uns['terminal_states_colors']
Out[38]: ['#1f77b4', '#ff7f0e', '#279e68']
adata.uns['terminal_states_names']
Out[39]: ['Lineage 0', 'Lineage 1', 'Lineage 2']

At this time, if I run this line of code cr.pl.terminal_states(adata, discrete=True), I got the following error:
Traceback (most recent call last):
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/IPython/core/interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-40-e2210f3bd42d>", line 1, in <module>
    cr.pl.terminal_states(adata, discrete=True)
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/pl/_init_term_states.py", line 150, in terminal_states
    return _initial_terminal(
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/pl/_init_term_states.py", line 92, in _initial_terminal
    mc.plot_terminal_states(
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/tl/estimators/_utils.py", line 148, in delegate
    return getattr(instance, attr)(
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/tl/estimators/_utils.py", line 62, in _method
    return method.__get__(obj, cls)(*args, **kwargs)
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/tl/estimators/_property.py", line 738, in _
    self._plot_discrete(data, prop, **kwargs)
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/tl/estimators/_property.py", line 481, in _plot_discrete
    self.adata.uns[f"{key}_colors"] = [
  File "/Users/zj/anaconda3/envs/1_scMFvenv/lib/python3.8/site-packages/cellrank/tl/estimators/_property.py", line 482, in <listcomp>
    colors[c] for c in data.cat.categories
KeyError: 'Epsilon'

Versions:
cr.logging.print_versions()

cellrank==1.2.0 scanpy==1.7.1 anndata==0.7.5 numpy==1.20.2 numba==0.53.1 scipy==1.6.2 pandas==1.2.3 scikit-learn==0.24.1 statsmodels==0.12.2 python-igraph==0.9.1 scvelo==0.2.3 pygam==0.8.0 matplotlib==3.3.4 seaborn==0.11.1

Please feel free to correct me if I do anything wrong. Thanks!

Hi @zhangjiaobxy ,
thanks for a really nice bug-report, I am able to reproduce this in 1.2.0! If you set cr.settings.verbosity = 4 before cr.pl.terminal_states(adata, discrete=True), you should see something like:
DEBUG: Unable to set attribute `._absorption_probabilities`, skipping
DEBUG: Unable to set attribute `._diff_potential`, skipping
DEBUG: Expected lineage names to be of length `3`, found `4`. Creating new names  # this is the problem
DEBUG: Expected lineage colors to be of length `3`, found `3`. Creating new colors  # there was a typo, should say: found `4`

We've fixed a part of this problem recently in 1.3.1, specifically in https://github.com/theislab/cellrank/pull/556 , it determined the number of terminal states based on adata.obsm['macrostates_fwd'], which is still 3. This however fixes only the 1st error (overwriting) and it will warn wrong #colors/names is found.
The 2nd error seems to still be present (calling cr.pl.terminal_states in succession) because of the inconsistency (4 categories in adata.obs['terminal_states'], but still only 3 columns in adata.obsm['macrostates_fwd'] and only the latter is being checked.
So it happily creates just 3 names/colors (cr.pl.terminal_states(adata, discrete=False) works and shows only these 3 macrostates), but when plotting these as discrete, the created color mapper only maps 3 names to colors: https://github.com/theislab/cellrank/blob/master/cellrank/tl/estimators/_property.py#L441 (it silently fails because Epsilon is cut out).
I've fixed this in #563 (still need to write tests though).
@Marius1311 we should refactor the estimator (by removing _property.py + defining a state machine) so that it's easier to handle (fix bugs, extend, ...). I will create an issue.

Thanks @michalk8 for your quick reply. I am glad to hear that you found the causes so fast. Please feel free to let me know when you fix it. I am happy to test the code. :)

Hi @michalk8, thanks for taking the initiative here - feel free to draft a refactoring of the estimators and we can discuss it!

Hi @zhangjiaobxy, I believe the bug you reported is fixed in #563, if you don't mind, would be great if you could test this!

Thanks @Marius1311. I can have a test. Should I test it under the developmental version?
pip install git+https://github.com/theislab/cellrank@dev

@zhangjiaobxy
This is still not yet on dev, pip install git+https://github.com/theislab/cellrank@fix_inconsistent_state should do the trick.
It's not perfect, but should solve the issue you've had. Proper fix can/wlll be issues when dealing with #564 (without refactoring, it's currently not possible).

@zhangjiaobxy
This is still not yet on dev, pip install git+https://github.com/theislab/cellrank@fix_inconsistent_state should do the trick.
It's not perfect, but should solve the issue you've had. Proper fix can/wlll be issues when dealing with #564 (without refactoring, it's currently not possible).

Thanks @michalk8 @Marius1311 ! I just tested this version. It works well. I guess the problem has been fixed. Thank you so much for your help!

closed via #563

Thanks a lot @zhangjiaobxy for testing the changes.


fix: Fix how metric labels are calculated

This PR depends on https://github.com/operate-first/peribolos-as-a-service/pull/183 for wrapOperationWithMetrics changes.
Fixes: https://github.com/operate-first/peribolos-as-a-service/issues/184

/cc @mimotej @SamoKopecky

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from tumido after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: SamoKopecky
To complete the pull request process, please ask for approval from tumido after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: SamoKopecky, tumido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [tumido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.


"Terminal" line disapperas when xterm is launched with -hold option

Neofetch version
Neofetch 5.0.0
Screenshot

Config file
https://pastebin.com/0WhC3QFm
Verbose log
https://pastebin.com/PC72uUx8
This is the command I used to launch xterm:
uxterm -geometry 64x20 -hold -name float -e neofetch
When launched with this line Terminal correctly shows..
uxterm -geometry 64x20 -hold -name float -e "neofetch -vv 2> neofetchlog"

I just tried with URxvt and the same thing happens

This only happens with w3m-img right?

Ok apparently if I use the same command in terminal it works, if I run it with sxhkd the issue happens. This is the command:
urxvt -geometry 68x16 -hold -e neofetch --backend w3m --source wallpaper

w3m-img issues aren't my problem.


forced Proxy test case

Added forced proxy implementation in connector_test.go

@yuewko Now Covers both the cases where forcedProxy == false and forcedProxy == true where request type is GET, In other places it will be false only.


[Feature Request] Support for FIPS 140-2 enforced mode.

In some customer service contracts (especially Government contracts), there is a requirement to run all services in FIPS 140-2 compliant/enforced mode.
Elasticsearch supports this currently in their xpack security plugin.
We, and I imagine others could benefit greatly with the ability to run OpenSearch in a FIPS 140-2 enforced mode JVM.
I see there was also an OpenDistro community post asking for this feature as well.

Thanks for reaching out.
I'll move this to our security plugin team.
Also @setiah probably you might interested!


microphone config files (audio + speech)

to assign devices (e.g. mic1 for audio feedback, mic2 for command detection)
as has been done in the vision node (config/cv_camera,yaml)

the problem is resolved in this PR #200, therefore close the issue


⚠ GLDDNS Server (ns2.glddns.com) has degraded performance

In 42d6b84, GLDDNS Server (ns2.glddns.com) (ns2.glddns.com) experienced degraded performance:

HTTP code: 200
Response time: 441 ms

Resolved: GLDDNS Server (ns2.glddns.com) performance has improved in 1e9c16a after 11 minutes.


[FEATURE] Handle individual batch call errors the same way return values are being handled right now

Introduction
If one of the calls from a batch request fails, return values from the following calls won't be returned (even if they are executed successfully).
I personally think it would be better if w3 returned an error when the batch request fails (network error, etc.) but NOT if one of the calls inside the batch request fails. Something similar to how go-ethereum handles their batch request calls.
Proposal
I propose we add a .Errors method to the CallFuncFactory, allowing us to specify where the error would get saved the same .Returns does.
Example
Consider the following snippet:
err := client.Call(
	eth.CallFunc(nonExistentFunc, w3.A("0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2")).
		Errors(targetErr1).
		Returns(res1),
	eth.CallFunc(funcBalanceOf, w3.A("0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2"), w3.A("0x000000000000000000000000000000000000c0Fe")).
		Errors(targetErr2).
		Returns(res2),
)

The caller would then be able to check the particular call errors via the targetErr1 and targetErr2 variables in this particular example. If targetErr2 == nil, I would then expect res2 hold the expected return value.

Thoughts?

I agree, the current error handling is not ideal. However, I would prefer to return something like
type CallErrors []error

in Client.Call instead. The success of an individual call could than be checked by its index.

Sure, that works!
I was considering that option as well but wasn't sure which idea would be more idiomatic.. 🙂

Call and CallCtx now returns the CallErrors type if the handling of one or more RPC responses failed. You can try this by importing the head instead of the v0.9.1. I will include it in a release after some playing around with it.
You need to check for an error and if that error is of CallErrors type. E.g.:
if err != nil {
  callErrs, ok := err.(w3.CallErrors)
  ...
}

This is now part of v0.10.0


[Bug]: Neo4j v5 Cluster when using neo4j helm chart as a dependency

Contact Details
No response
What happened?
While checking a Neo4j docs for cluster setup: https://neo4j.com/docs/operations-manual/5/kubernetes/quickstart-cluster/install-servers/ I discovered that we have to install the same chart 3 times with different names. Is there a way to create a cluster when using neo4j helm chart as a dependency of our own chart?
Chart Name
Cluster
Chart Version
5.5.0
Environment
Amazon Web Services
Relevant log output
No response
Code of Conduct

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

@psolarcz as of now in order to create a cluster you will need to install neo4j 3 times or the number of instances in a cluster you need.
You can do something like this as per helm
dependencies:
  - name: neo4j
    alias: server1
    version: 5.10.0
    repository: https://helm.neo4j.com/neo4j
  - name: neo4j
    alias: server2
    version: 5.10.0
    repository: https://helm.neo4j.com/neo4j
  - name: neo4j
    alias: server3
    version: 5.10.0
    repository: https://helm.neo4j.com/neo4j

and have each server values.yaml defined in your chart values.yaml under its own section
https://helm.sh/docs/chart_template_guide/subcharts_and_globals/
Any reason why it is marked as a bug @psolarcz  ?

Thanks @ojhughes and @harshitsinghvi22

Any reason why it is marked as a bug @psolarcz ?

I didn't see anything like ask question :)

there is one @psolarcz  , you can use the "question" tag

Are there any plans to utilise single helm chart to create a cluster?
With current setup am I able to distribute servers across AZs? Does rolling update work for the cluster?

Are there any plans to utilise single helm chart to create a cluster?
No
With current setup am I able to distribute servers across AZs?
yes, via nodeSelector
Does rolling update work for the cluster?
It's manual process since its one statefulset for each member , you take one statefulset down update it and continue


MSC2181: Add an Error Code for Signaling a Deactivated User

Rendered

otherwise this lgtm

Did you mean to leave a feedback as well?

I think this is trending towards the proposed solution, so
@mscbot fcp merge

@mscbot concern Users who log in with 3PIDs won't be told they're deactivated.

@mscbot resolve Users who log in with 3PIDs won't be told they're deactivated.
Implementations can hash user's 3PIDs instead of removing them, thus allowing them to continue to check if a user is deactivated without keeping personal information about.

This has an implementation so bumping it to spec-pr-missing: https://github.com/matrix-org/synapse/pull/5686

Spec PR has been created: https://github.com/matrix-org/matrix-doc/pull/2234


fix: Use os.Stdout if no logging filename is given

Use os.Stderr if no logging filename is given
Set default log to "" to enable stderr output
This makes it possible to use journald by using default log value
This solution is not optimal, but keeps backwards compatibility

Refs: https://github.com/nestybox/sysbox/issues/221

I have replaced Stdout with Stderr as recommended.

See discussion in https://github.com/nestybox/sysbox-fs/ as the changes here are identical.

Looks good, thanks!
Please sign off the commit (i.e., git commit --sign-off ...) as we need this in order to accept the patch. See here for more.

Done. Don't be confused by the email change. I forked the project into my private namespace and not into the company namespace.


[Feature] Enable num rows for server side pagination

Summary
Tables with serverside pagination can be navigated infinitely. Having an option to specify the number of rows will allow us to determine the number of pages

@Nikhil-Nandagopal If I understand the issue correctly, a potential solution to this would be to have a pageSize or pageRowCount configurable from the property pane, which will override the current computed pageSize property?

@Nikhil-Nandagopal If I understand the issue correctly, a potential solution to this would be to have a pageSize or pageRowCount configurable from the property pane, which will override the current computed pageSize property?

@riodeuno no this is the total number of records that this data set contains.
Total number/page size tells us the number of pages

@riodeuno no this is the total number of records that this data set contains.
Total number/page size tells us the number of pages


fix profile name

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[ ] PR closes #1416

[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[ ] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Hi,

Hey. I don't think this will correct anything, Twitter link is working well, thing is that sometimes it won't load identity of an address

I guess we should cache identities for faster load. But I guess we already do?


Spyder 4 GUI regressions on Windows

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Have noticed a number of GUI regressions on Windows after upgrading from Spyder 3 to Spyder 4.
On almost all of the panes, there is no "padding" between the toolbar controls and the elements above.
What steps reproduce the problem?

Set Appearance -> Main interface -> Interface theme: Light
Set Appearance -> Main interface -> Qt windows style: WindowsVista

What is the expected output? What do you see instead?
Top pixels of selected tab are cut off:

Toolbar controls are hard against the top, they should have the same padding above as below.

Versions

Spyder version: 4.0.1
Python version: 3.7.6
Qt version: 5.9.6
PyQt version: 5.9.2
Operating System name/version: Windows 10

@jnsebgosselin, is this something that's going to be address by your PR #10626?

I think a new option was added in Spyder 4 to adjust that, but I'm not sure.
@patrick984 Can you check if increasing the value of the pane margins in the preferences solve your issue?

@ccordoba12 Maybe the minimum value of the pane margins should be changed to 1 instead of 0?

Things look fine in the dark theme.

Things look fine in the dark theme.

It is true. It is probably due to the fact that a lot of 'hidden' hard coded padding is added in the dark theme.
So considering that, I think we should leave this option as is to allow 0 padding in the dark theme.


Remove dependency on ip.finish

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Given #143 was a red herring (as a result of removing the provider.tf and the oci provider subsequently using the oci config), I think we should remove the dependency on ip.finish file on admin host.
New or Affected Resource(s)
Remove all occurrences on ip.finish

Potential Terraform Configuration

# Copy-paste any Terraform configurations for how the requested feature may be used.

References

@redscaresu @styledigger @sauraahu  I'll need your help to test this

I've pushed to my fork and tested both with the provider.tf and without (i.e. the oci config will be used). Can you please test and let me know?
git checkout -b hyder-issue-154 master
git pull https://github.com/hyder/terraform-oci-oke.git issue-154
Thanks

@hyder Did test on issue-154, both apply and destroy worked without issues. Kubectl on admin host worked as well.
Test was done with provider.tf and default terraform.tfvars (just changed region to Frankfurt).

Merged in in #156


ionic 2 bug - if I hide nav bar and show nav bar my back button hide

Ionic version:  (check one with "x")
[ ] 1.x
[ x] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

If I hide nav bar, then show nav bar, back button not showing.
Expected behavior:

If I hide nav bar, then show nav bar, the back button should appear (because, In begin it was in nav bar).
Steps to reproduce:

if I use:
<ion-navbar color='indigos' *ngIf="showBlock">
    <ion-title>Title</ion-title>
    <ion-buttons end>
      <button ion-button icon-only (click)="searchToggle()">
        <ion-icon name="search"></ion-icon>
      </button>
    </ion-buttons>
  </ion-navbar>

and hide block, then I show It, that the back button no longer appears (before I hid nav bar - back button was).
Inspector showed, that main.css contains the following code:
.back-button {
    display:none;
}

Method this.viewCtrl.showBackButton(true) also not working.
If use, exmaple, [ngClass] and create class:
.hide {display:none}, that is OK:
<ion-navbar color='indigos' [ngClass]="addClass">
    <ion-title>Title</ion-title>
    <ion-buttons end>
      <button ion-button icon-only (click)="searchToggle()">
        <ion-icon name="search"></ion-icon>
      </button>
    </ion-buttons>
  </ion-navbar>

addClass - is variable:
public addClass:string = "";
 searchToggle() {
    this.addClass = "hide";
  }

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.5.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.1.7
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 8.1
Node Version: v6.9.5

Hello, thanks for using Ionic! You can check out this comment for an example of how to use the resize method in situations where you have functionality like you describe.

No! It other error (and resize() not decides this problem)! Header size is fixed (I hide nav bar and I show search bar), but when I show nav bar and hide search bar again, back button not show...

Same problem here!


Offer UI feedback when config.yml incorrect, and other issue...?

I ran into another bug. After successfully doing the oauth dance, logging in, seeing request return 200
https://api.github.com/repos/user/my-repo/git/trees/a92c534exxx.......

Sveltia UI updates and says Loading Site Data... but errors with following:
Uncaught (in promise) TypeError: re(...).findLast is not a function
    ry https://example.org/admin/sveltia-cms.js:387
    ry https://example.org/admin/sveltia-cms.js:387
    xO https://example.org/admin/sveltia-cms.js:401
    update https://example.org/admin/sveltia-cms.js:439
    update https://example.org/admin/sveltia-cms.js:439
    hv https://example.org/admin/sveltia-cms.js:1
    He https://example.org/admin/sveltia-cms.js:1
    promise callback*db https://example.org/admin/sveltia-cms.js:1
    pv https://example.org/admin/sveltia-cms.js:1
    ctx https://example.org/admin/sveltia-cms.js:1
    fU https://example.org/admin/sveltia-cms.js:452
    s https://example.org/admin/sveltia-cms.js:1
    De https://example.org/admin/sveltia-cms.js:1
    h https://example.org/admin/sveltia-cms.js:439
    EA https://example.org/admin/sveltia-cms.js:439
    EA https://example.org/admin/sveltia-cms.js:439
    ab https://example.org/admin/sveltia-cms.js:1
    $/< https://example.org/admin/sveltia-cms.js:1
    He https://example.org/admin/sveltia-cms.js:1
    promise callback*db https://example.org/admin/sveltia-cms.js:1
    pv https://example.org/admin/sveltia-cms.js:1
    ctx https://example.org/admin/sveltia-cms.js:1
    jA https://example.org/admin/sveltia-cms.js:439
    s https://example.org/admin/sveltia-cms.js:1
    f4 https://example.org/admin/sveltia-cms.js:217
    jA https://example.org/admin/sveltia-cms.js:439
    ab https://example.org/admin/sveltia-cms.js:1
    $/< https://example.org/admin/sveltia-cms.js:1
    He https://example.org/admin/sveltia-cms.js:1
    W https://example.org/admin/sveltia-cms.js:1
    dU https://example.org/admin/sveltia-cms.js:452
    kU https://example.org/admin/sveltia-cms.js:452
    ev https://example.org/admin/sveltia-cms.js:1
    <anonymous> https://example.org/admin/sveltia-cms.js:452

When switching to decap-cms / netlify-cms.js I see the following error:
Error loading the CMS configuration
Config Errors:

'collections[1].fields[2].fields[0]' must have required property 'search_fields'
...

Check your config.yml file.

After fixing a few bugs in my config and properly loading the content in Decap, I still see above error in Sveltia.
What is also interesting is the config works fine when using localhost version.

You’re right, I haven’t implemented comprehensive validation in Sveltia CMS. I think having a config editor is rather a must because hand-written config files are very problematic, but the CMS still needs a validator to catch any issue. In the meantime, please use Decap as a validator 🤣

And yeah, I think your error is unrelated to search_fields because the property is unused (not yet supported) in Sveltia CMS. I’ll figure out how it could happen.

It’s a mystery at a glance. I thought it might be a browser compatibility issue because findLast is relatively new, but it doesn’t make sense if it works with the local environment. 🤔

I think having a config editor is rather a must because hand-written config files are very problematic

Agreed 👍🏻 that's the dream. One things i've wished for with Netlify/Decap (which diverges from a validation + editor) is that configs could be split into multiple files:
admin/
├── index.html
├── sveltia-cms.js
├── config.yml
└── collections/
    ├── posts.yml
    ├── pages.yml
    └── widgets.yml

This increases number of requests on load, but the collections could be lazy loaded so it's not too bad. This would progressively enhance, while being backwards compatible, yet allow a dev to wrangle the hundreds of lines of YAML a bit better.


fix: @encoder / @decoder customization error

Description
I defined a custom override as documented to implement custom serialization. However, when I run it, I found that model_override.dart is not imported into jaspr_options.dart. I think it is needed to fix to import the file where the custom override is defined in order to run it.
Steps To Reproduce

Download the fluttercon app.
Upgrade all packages to the latest version.
Serve the app.
See the error, Error: Method not found: 'SessionCodex'.

Doctor Output
[✓] Jaspr CLI (Version 0.14.0)
  • Dart Version 3.5.0 (stable) (Tue Jul 30 02:17:59 2024 -0700) on "macos_arm64" at /opt/homebrew/Caskroom/flutter/3.24.0/flutter/bin/cache/dart-sdk/bin/dart
  • Running on macos Version 14.5 (Build 23F79) - Locale ko-KR
  • Analytics: Enabled

[✓] Current Project
  • Dependencies on core packages:
    • jaspr: ^0.14.0
    • jaspr_builder: ^0.14.0 (dev)
    • jaspr_web_compilers: ^4.0.9 (dev)
    • jaspr_router: ^0.5.0
  • Rendering mode: static
  • Uses jaspr compilers: true
  • Uses flutter embedding: false

Expected Behavior
The custom override should be imported and find the methods normally.
Additional Context
This is a different issue: I'm using melos to structure my project. Until the previous version, it would detect @encoder / @decoder in other packages as well and generate jaspr_options.dart. However, after upgrading, I found that it no longer detects annotations in other packages than the Jaspr app. (In fact, this issue was discovered after I tried to do a custom override in the app project because of this.) If this is an unintended consequence, I'd like to hear your thoughts on it. Thanks.

Fixed in 0.15.0. Also supports multi packages now.


Pagination bug when using search or filtering feature.

Pagination doesn't work when filtering only shows 10 pages. next page is not clickable or disabled.
Steps to reproduce the behavior using the demo:

Go to search bar
Type example "a"
See bug.

Only displays 10 items and the pagination is not clickable.

I have checked what is wrong.
So it looks that when filtering is on, RemoteDataSourceDetails field "filteredRows" has a value corresponding to a current number of rows returned by server instead of "The total amount of rows after a filter was applied".
I think that for fixing the sample, the total number of filtered rows should be returned by api.