Cannot find plugin

Expected behaviour
It should be able to find installed plugins.
Actual behaviour
The reverse of "expected behaviour", innit? :)
It's not able to find installed plugins.
03 01 2017 11:54:18.262:WARN [plugin]: Cannot find plugin "karma-phantomjs-launcher".
  Did you forget to install it ?
  npm install karma-phantomjs-launcher --save-dev

Environment Details
Karma version 0.13.14
frameworks: ['jasmine'],
browsers: ['PantomJS'],
plugins: [
 'karma-phantomjs-launcher',
 'karma-jasmine',
 'karma-junit-reporter'
],

Steps to reproduce the behaviour

Clone Angular-seed
npm i
npm i --save-dev karma-phantomjs-launcher
Change the browsers and plugins fields in karma.conf.js like above
karma start karma.conf.js

Ok, one thing I found is that somehow I magically had some modules installed in the nodejs installation directory - that's not where they're supposed to be put. Global packages normally go into the user profile.
So, trying again...
karma start karma.conf.js
module.js:472
    throw err;
    ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\karma\bin\karma'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:420:7)
    at startup (bootstrap_node.js:139:9)
    at bootstrap_node.js:535:3

That's better. At least it tells me where it cannot find whatever it needs this time.

Okay, one more update, for those who also come across this problem.
There where executables for jasmine and karma in the nodejs installation folder (again, not where they're supposed to be installed). I deleted those, removed-and-reinstalled karma-cli globally, and now it works. Or at least I'm not getting any errors trying to run karma.
So, remains one question: why or how does karma decide that a plugin isn't installed when it clearly is?
Can karma please also output where it didn't find the plugin it was looking for? That would help greatly in figuring out the how&why of a problem like this.

I think the issue is a typo in browsers. It should be PhantomJS not PantomJS =/
To answer your plugin resolution question:
By default, plugins are resolved via Node.js' require statement. There is support for pattern matching (e.g. karma-* loads all matching modules) but based on your config that isn't a problem:
https://github.com/karma-runner/karma/blob/v1.3.0/lib/plugin.js#L13-L19
Node.js' require looks for a local node_modules folder and if not found, it goes up one directory, looks again, and keeps on going until it hits / and throws an error:
https://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders

Oops @ typo :D
But that didn't cause the 'cannot find plugin' error.
Anyway, it would still help (others as well I'm sure) if karma would print out the location(s) of a plugin when it couldn't find it. Googling around, it seems to be a fairly common problem.

I think the current message is the best we can do. As linked, it's hard to predict where the node_modules folder should be (e.g. someone can be inside of test/path/to/nested/folder and run karma which resolves from node_modules, not test/path/to/nested/folder/node_modules). If we were to output that, it would be a whole lot of confusing feedback to the user x_x
We didn't find the package, please verify it was installed at one of the following:

- /home/todd/github/project/test/path/to/nested/folder/node_modules
- /home/todd/github/project/test/path/to/nested/node_modules
- /home/todd/github/project/test/path/to/node_modules
- /home/todd/github/project/test/path/node_modules
- /home/todd/github/project/test/node_modules
- /home/todd/github/project/node_modules
- /home/todd/github/node_modules
- /home/todd/node_modules
- /home/node_modules
- /node_modules

I took a look at this, and what I suspect happened is that the step to run cd angular-seed was forgotten. I was not able to reproduce this, this is highly likely a user error.

We didn't find the package, please verify it was installed at one of the following:

- /home/todd/github/project/test/path/to/nested/folder/node_modules (and below)

Fixed that :)
The thing is, I did not forget the cd angular-seed, honestly. I think it was trying to find the plugins in the global installation (in the user profile) or in the superglobal installation (in the nodejs program directory). Whichever the case, a message like "We didn't find the plugin here & here" would help in diagnosing what went wrong.
Because with all due respect, things like "maybe you forgot such&such" or "maybe you can try this&that" is rather unscientific guesswork, while proper logging could have prevented that.


error on create and migrate database

I tried to follow the installation instructions but it error when i tried to run
mix ecto.create && mix ecto.migrate
with the following message
Compiling 34 files (.ex)
warning: unused alias Repo
web/models/board.ex:5
== Compilation error on file web/router.ex ==
** (CompileError) web/router.ex: internal error in v3_core;
crash reason: {case_clause,
{'EXIT',
{badarg,
[{erl_anno,anno_info,[-1],[{file,"erl_anno.erl"},{line,360}]},
{v3_core,record_anno,2,[{file,"v3_core.erl"},{line,2410}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,539}]},
{v3_core,safe,2,[{file,"v3_core.erl"},{line,1593}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,528}]},
{v3_core,safe,2,[{file,"v3_core.erl"},{line,1593}]},
{v3_core,'-safe_list/2-anonymous-0-',2,
[{file,"v3_core.erl"},{line,1608}]},
{lists,foldr,3,[{file,"lists.erl"},{line,1276}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,538}]},
{v3_core,safe,2,[{file,"v3_core.erl"},{line,1593}]},
{v3_core,'-safe_list/2-anonymous-0-',2,
[{file,"v3_core.erl"},{line,1608}]},
{lists,foldr,3,[{file,"lists.erl"},{line,1276}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,538}]},
{v3_core,safe,2,[{file,"v3_core.erl"},{line,1593}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,528}]},
{v3_core,safe,2,[{file,"v3_core.erl"},{line,1593}]},
{v3_core,'-safe_list/2-anonymous-0-',2,
[{file,"v3_core.erl"},{line,1608}]},
{lists,foldr,3,[{file,"lists.erl"},{line,1276}]},
{v3_core,expr,2,[{file,"v3_core.erl"},{line,652}]},
{v3_core,exprs,2,[{file,"v3_core.erl"},{line,512}]}]}}}
in function  compile:'-select_passes/2-anonymous-2-'/2 (compile.erl, line 530)
in call from compile:'-internal_comp/4-anonymous-1-'/2 (compile.erl, line 315)
in call from compile:fold_comp/3 (compile.erl, line 341)
in call from compile:internal_comp/4 (compile.erl, line 325)
in call from compile:'-do_compile/2-anonymous-0-'/2 (compile.erl, line 175)
(stdlib) lists.erl:1338: :lists.foreach/2
(phoenix) expanding macro: Phoenix.Router.before_compile/1
web/router.ex:1: PhoenixTrello.Router (module)
(elixir) lib/kernel/parallel_compiler.ex:116: anonymous fn/4 in Kernel.ParallelCompiler.spawn_compilers/1
I am on
Arch Linux
Erlang 19
Elixir 1.3.2
Additional info
I don't know if this is relevant, at first i have to update jose dependency.
==> jose
Compiling 72 files (.erl)
compile: warnings being treated as errors
src/jose_jwe_alg_aes_kw.erl:103: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwk_kty.erl:198: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwk_kty_ec.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_okp_ed25519.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_okp_ed25519ph.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_okp_ed448.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_okp_x25519.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_okp_x448.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_rsa.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_pem.erl:40: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwa_pkcs1.erl:267: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
src/jose_jwa_pkcs1.erl:416: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
src/jose_jwa_pkcs1.erl:605: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwe_alg_pbes2.erl:73: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwe_enc_aes.erl:198: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
src/jose_jwe_enc_aes.erl:201: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
compile: warnings being treated as errors
src/jose_jwk_kty_okp_ed448ph.erl:13: behaviour jose_jwk_kty undefined
compile: warnings being treated as errors
src/jose_jwk_kty_oct.erl:13: behaviour jose_jwk_kty undefined
src/jose_jwk_kty_oct.erl:91: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1
could not compile dependency :jose, "mix compile" failed. You can recompile this dependency with "mix deps.compile jose", update it with "mix deps.update jose" or clean it with "mix deps.clean jose"
==> phoenix_trello
** (Mix) Encountered compilation errors
In orde to get rid of this error i run
mix deps.update jose

Same os/erlang/elixir, same problem :) Thanks for adding quick solution.

still getting the same problem after running  mix deps.update jose
any ideas?

guys we need to update phoenix_html and phoenix it self.
Please run the following
mix deps.update phoenix_html
mix deps.update phoenix
then you are good to go.
By the way i found this issue have been solved on https://elixirforum.com/t/erlang-19-0-elixir-1-3-and-phoenix-1-1-4-compatible/911/6


Refuses to acknowledge I've selected a shape

Just installed the plugin using Sketch 52.5 (most recent version).
I select a shape and activate the plugin but it simply states I should select a shape.

Also getting this issue

@mlemmers @smlparry This plugin no longer maintained due duplication native Sketch feature. Please use Smooth Corners in app to get the similar effect as in Egmont plugin. If you need outlined shape, select Flatten option in Layer→Combine menu.


Wiki: Referencing SharePointDsc

The wiki is referencing SharePointDsc instead of xNetworking.

@tysonjhayes - I couldn't find this in any code, so I'm presuming it was added manually and this was just copy/paste error. So I fixed this by editing the side bar in the Wiki and changing it to xNetworking. Is that the correct way to do it?

Yup, it was a copy paste error, fix looks good.


clear description on pascals triangle

The pascals triangle exercise description is not explicit ,
Actual Mathematical Formula for finding pascals triangle( coefficient of Binomials)
Here P refers to Permutation => n!/(n-r)!
Here C refers to Combination => n! / (n-r)!r! , or , nPr / r!
(x + a)^0 =  C(0,0) = 1
(x + a)^1 = C(1,0) , C(1,1) = 1  1
(x + a)^2 = C(2 , 0) , C(2 , 1) , C(2 , 2)  = 1 2 1
from above we can say ,
n row = C(n ,  0) , C(n , 0+1),   ..... C(n , n)
i request that you change that, soon

when I look at the current description: https://github.com/exercism/x-common/blob/master/exercises/pascals-triangle/description.md
It looks explicit enough to me.
There could still be a benefit for explaining it in terms of combinations. Would you please explain the benefits of doing so?
I would recommend that that explanation be in addition to what's currently there, not replacing it.

Just letting them know there are two possible solutions!.


Backspace on the line before a folded block deletes the folded code

https://user-images.githubusercontent.com/44893228/231163449-8141ae35-0257-40f6-8786-9d95758c5e18.mp4

Related to #175


False positives when authenticating in the RouteMatched event listeners

Laravel Version: 5.8 and below
PHP Version: irrelevant
Database Driver & Version: irrelevant

Description :
Laravel internally fires a RouteMatched event, when a route is matched and BEFORE any middleware is executed.
So if we use auth()->check() in the listener of that event, it always gives us null (even if the user is logged in) because the middleware which is responsible for Starting the session is not run yet.
This is expected. but...
The bug is :
if we write feature tests and send a request to an end point $this->get('/my-url') the  auth()->check() within the event listener of RouteMatched works properly ! and returns true if the user is logged in!
So it gives false positives. in case we need to check authentication in that listener.
To be clear, let me say that again:
in the below code sample :

real web request from a browser: auth()->check() (does not work)
a simulated request from a  feature test $this->get('/my-url') :  auth()->check() (will work)

// in the AppServiceProvider.php
\Event::listen(\Illuminate\Routing\Events\RouteMatched::class, function () {
    dd(auth()->check());
});

that was hiding a bad bug in my package for a long time.
In other words, your tests tell you that auth()->check(); will work properly in the code above, and that is a lie ! it won't work....
let me note that, all the authentication stuff (like : ->id(), ->user()) are subject to the same thing, not just  auth()->check();
The cause :
it's because if we try to login the user in your feature test before sending the request, by using auth()->loginUsingId(1), then the auth()->check(); will return true, even in the target app instance.
Steps to Reproduce :
fresh laravel
plus, basic setup of authentication. (users table, a sample user to login with)
// in the AppServiceProvider.php
\Event::listen(\Illuminate\Routing\Events\RouteMatched::class, function () {
    dump(auth()->check());
});

// tests/feature/ExampleTest.php
  public function testBasicTest()
  {
     $this->actingAs(User::first());
     $this->get('/');
   }

1- login as a user (how ever you want to)
2- visit '/' from your browser.
3- you should see false printed out by dump function.
4 - run the test
5- you will see that true is printed out. (that contradiction strep 3)

An appropriate fix would be to offer a new method which only sets a cookie on the request and persist the session to be checked later.

Please fill out the issue template when posting issues.

@driesvints I think it should be more clear now.

Hmm, yeah I can see that being a problem. But I'm wondering why you need to check for auth state in that listener?

In real-life this happened to me while working on this package : https://github.com/imanghafoori1/laravel-heyman
for example this needs it :
Heyman::whenYouRouteName('foo')->youShouldbeGuest()->otherwise()->redirect('/home');

How did you solve the bug?

Now the routeMatched listener,only adds a middleware at the end of the middleware stacks, using the prepend method.
and that middleware can check for authentication and other stuff. since it is after the SessionStart.
RouteMatched Listener :
https://github.com/imanghafoori1/laravel-heyman/blob/master/src/WatchingStrategies/Routes/RouteEventListener.php
The middleware is:
https://github.com/imanghafoori1/laravel-heyman/blob/master/src/WatchingStrategies/Routes/MatchedRoute.php

That seems a little bit overkill to me. I don't have time to deep-dive into this atm. Feel free to send in a PR.

Since there has been only one report of this and nobody else experienced this since I'm closing this.


Timing format improvements

Before, with the default widgets:
$ python3 progress.py
100% (60 of 60) |########| Elapsed Time: 0:00:06.027589 Time: 0.9040819999999999

After:
$ python3 progress.py
100% (60 of 60) |#############################| Elapsed Time: 0:00:06 Time: 6.03

Specific changes:

Hide the microseconds in the Timer class. They're either updating too fast to read, or they're out of date by the time you read them anyway. This required some rearranging to make Timer inherit from FormatLabel.
Fix AdaptiveETA's display of the total elapsed time after progress is finished (see the 'before' example, it says ~0.9 when it should say ~6.0).
Limit ETA and AdaptiveETA's display of the total elapsed time to 2 decimal places. This was fairly arbitrary, but showing the full floating point precision is clearly not helpful.
Fix the calculation of seconds_elapsed - microseconds were being added to seconds without scaling them.

Indeed a good fix, much better default this way. The large rewrite in the beginning of this year left some things unfinished/unpolished. This helps a lot :)

Great, thanks for merging both of these. There's a couple more things I'm
planning to work on, particularly around handling UnknownLength. I'll
probably look at that tomorrow. :-)
On 10 Oct 2015 11:42, "Rick van Hattem"<EMAIL_ADDRESS>wrote:

Merged #28 https://github.com/WoLpH/python-progressbar/pull/28.
—
Reply to this email directly or view it on GitHub
https://github.com/WoLpH/python-progressbar/pull/28#event-432074657.

That's great, thanks so much. I just have way too little time to properly maintain it right now. Any help is greatly appreciated!


Improved language (de.cfg)

Great work @0n1cOn3 👍

Thanks - I hope its worth it after spending an hour on it :-D


figure comparing mlrMBO with grid search is not reproducible

this is "res1.png" on the tuning slides (good job at picking descriptive filenames, too! :+1:)
needs to be chnaged since it uses SVM terminology, there's no script to reproduce, no source given in the slides. @berndbischl, is this yours? git blame would indicate it is.

i can easily change this during the sprint, the code might be gone but it kinda easy to do with mlrMBO.
which method do we want to use? problem is, most of what we cover is that super-interesting for tuning?

CART or RF?  The latter is what I used to replace the other tuning example that was based on GBM. If you use large enough ranges for the pars, you do see some sensitivity there as well.
I don't want to wait until your sprint -- I think it's very likely that you're not even going to get all of your own stuff done in time and we'll frustrate Heidi.
I'll try to get it done with mlrMBO and ping you or Janek for advice if I get too badly stuck.

CART or RF? The latter is what I used to replace the other tuning example that was based on GBM. If you use large enough ranges for the pars, you do see some sensitivity there as well.

if that works, absolutely fine. RF probably better than CART.
regarding waiting: pls ping me, not janek. janek is not even LMU anymore.
if the code is in the repo and we do asynchronously i can quickly help and we can get it done super quickly


Error report has no state

I noticed that react-safe-render exposes some parts of the component such as displayName, props, and the lifecycle method that threw the error. Is their a reason the state isn't exposed as well? Why not expose the component itself in the report?
An additional benefit other than your entire tree not getting locked up is that you can now reveal exactly which components in your app are failing and what state they were in when they failed. It would be useful to have as much information as possible. Thoughts?

@vinnymac maybe their components are mostly dump components which only having props.

(wild speculation ...)_
Exposing state might be as simple as altered the wrap function to include it in report here.

@lenards I too am using this to log with raven-js to Sentry. Modifying this to report the state should not be difficult, I was just wondering if the creator intentionally left it out for a reason. If you have success with it, be sure to let me know!

I did not leave it out for any particular reason. I just haven't invested any time in it, because Facebook has been promising a library fix for this for a long time. If anyone wants to add it I think it sounds like a good idea!

@skiano awesome! I am looking forward to Facebook coming out with an official solution as well.
Would this solution suffice for most people?
Change this line to be
component : this,

Then we should be able to access state and props as necessary.

i think it would be better to add state as a key rather than turning over all of "this". Because there's so much in "this" and who knows what people would start depending on that isn't covered in the tests

also for reference
this is the thread that has been going about this:
https://github.com/facebook/react/issues/2461
it's been on their radar for quite a while

Good point, well in that case, we should just do
state : this.state,

It looks like some progress is being made, but at least we have this lib in the meantime thanks to you.

I agree with @skiano - I'd cite something like "principle of least authority" for not handing over this and scope to this.state (not that devising a position is really needed).
Thank you Greg for the library. I'll see if I can get a PR put together & submitted.


Add auto merge

@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/pylatte-feedstock#2.


Feature/speedup github actions

Speedup github actions using actions/cache@v2

@NobodyXu it looks like CI broke because your changes to ci.yml and cross_platform.yml are invalid and preventing the files from being parsed

Thanks for your work here! I'll take a closer look soon 🙂

Thanks for your work here! I'll take a closer look soon 🙂

This PR basically adds caching to the jobs and uses cargo-nextest for testing.
cargo-nextest executes all tests in parallel

@NobodyXu it looks like CI broke because your changes to ci.yml and cross_platform.yml are invalid and preventing the files from being parsed

There is indeed a syntax error regarding indentation in ci.yml and cross_platform.yml.
- name: ...
   run:

yml rejects the code above and requires me to write:
- name: ...
  run:

@ParkMyCar This PR is now ready for merge!
Looking at the times taken, this PR indeed speedup the github actions.
For cargo-miri, fuzzing and x-plat, using cache can speedup the workflow to roughly 7-8 minutes, while originally takes roughly 9 minutes or longer.
For job cargo-test and cargo-test-nightly, the speedup is even more significant thanks to caching plus the use of cargo-nextest.
It takes roughly 30s for these jobs.
One thing to note that is the time listed above is all performed on the exact same codebase with no modification.
Once deployed, the actual improvement might be smaller than the number listed above, but never the less, I think this PR would make checks in PR run faster.

Thanks for doing this work! Merging!


What's going on?

@gnab so currently it seems like there's a lack of communication. I'm sure you have good reason for it, and you're probably very busy.
It doesn't seem like things are going the right way though, and especially not when it comes to the pace. Most of the issues aren't getting replies, and at least 1/3 of them could probably be closed.
A new release isn't anywhere in sight, and changes to the wiki are non-existent.
A reply explaining what's going on and what's going to happen could clarify quite a bit. Perhaps getting some trustworthy collaborators could be a good idea. (I personally would like to become one, even though JavaScript isn't my main language. And if not for the development, then for the issues, update on the wiki and perhaps a new release).
I think that people as much as me, would like to get an update in terms of what's going to happen to Remark.

@BenTearzz @gnab Also happy to help if I can in any way. I (and I'm many others) have committed lots to this project in the form of slide decks that would need to be rewritten if it goes away. That investment means we're all invested in the project's success and happy to help make it happen if we can!

Yes, we all love remark.js and want to help, as indicated in #548. However, I suggest that you close this issue and keep the discussion in #548 (for the reason I just explained in #571).


Support React 17

Please enable support for React 17

It is not meant for Reavt v17. However, from my limited testing, it seems to work well with it. You can install it using the --legacy-peer-deps flag to give it a go. However, it's not an ideal solution.

<Textfit mode="single" forceSingleModeWidth={true} >
        {this.props.isRoman === true
         ? "lol"//this.toRoman(this.props.interText)
         : "lol"//this.props.interText
}
</Textfit>

Im on react 17, maybe it's an issue with typescript but got fatal error on this


build(main): release 1.6.2

:robot: I have created a release beep boop
1.6.2 (2024-10-04)
Features

Add condition to check for null values in event message includes (5d82468)
Add conditional check before appending MenuButtonDeleteItem menu item (59d7916)
docker: Refactor Dockerfile to use ENTRYPOINT and remove CMD instruction (8cd095b)
Make possible to refresh lists of source and destination chats manually, during the configuration of forwardRules. (d3d90e8)
Preparation for universal keywords rules functionality (459cb47)
Refactor code to make telegram-menu-structured fully independent from Telegram Client or Bot library (08961bf)
Switch to use telegram-menu-from-structure package instead of local (56262e9)
Update package version to 1.0.70 and add strftime dependency. Improving the logging. (ea0adf6)

Bug Fixes

Add annotations to docker deployment workflow (d4a3a37)
docker building for arm64 (b8a436e)
Fix onSetAfter function call for resubscribeInterval (96f4025)
Fix doubling the Menu messages due to not updated SendMessageAsync, which still returned the whole message instead on message id. (a3bf4b7)
fix some variable declarations (ebba407)
logger: make it secured, not show the sensitive information in logs (ebba407)
telegram-menu-structured: Fix call with text parameters of i18n conversion after #eb13300 - i18n decoupling (33edf86)
telegram-menu-structured: Fix issue with prompts in inputs after #eb13300 - i18n decoupling (33edf86)
Update name of workflow to build and push docker image (efec570)

Code Refactoring

Add 'User' and 'Bot' types instead of Chat, with appropriate translations. (f5903c3)
Add default false for all command-line options (b39c8af)
Add new command-line option --no-debug-cache to disable debug for the Cache instance (212d9af)
Add new command-line option --no-debug-menu to disable debug for the telegram-menu-from-structure (b39c8af)
Add resubscribe function call in resubscribeInit (1721bd8)
align changes in "interface" functions sendMessage and editMessage in telegram-menu-from-structure. Fix lowest version of telegram-menu-from-structure to 1.1.1. (96f4025)
Align functions in structure to the changes in<EMAIL_ADDRESS>(a3bf4b7)
Cache: Refactor Cache to make possible to disable debug only for Cache (212d9af)
Change a log.debug statement to log.info in the begging of the onMessageToForward function in index.js. (f97ce85)
Change logic to set logger to the menu code (b61bec4)
docker: Update npm install command to use 'npm ci' in Dockerfile and make it dependant on TARGETPLATFORM. (f31b0e9)
fixed issues after previous commit, now edits of messages looks functional, as planned. Additionally fixed eventHandlers cleanup. (cb249ff)
Get rid of includes and excludes. Replace message by universal content with appropriate renaming. (d3ebf57)
Implement confirmation of user actions in Menu by confirmCallBackQueryAsync introduced in telegram-menu-from-structure version 1.3.0. (ead8d3f)
Improve debug for message handling (053f495)
Improve handling of undefined messages in refreshDialogs function (56954b6)
Improve message forwarding logic and handling of null values in event message includes (857e291)
Improve the configuration initialization to default values. Automatically delete non-existing values from Cache. (31b13f1)
In rules - universal structure is changed. Check of the universal keyword rules is implemented. (5977220)
localization: Refactor localization strings to use placeholders for dynamic values (96f4025)
Made users in configuration be refreshed manually (a07bee4)
Make fromIds update only in updateForwardListener. (73ce0f6)
Make forum topics data cached, to prevent overloading Telegram API by such requests. (fce75cd)
Make possible to pass basic parameters as environment variables (8cd095b)
menu initialization and drawing logic (e4d7ac4)
menuStructured: first step to make separate module (85720d0)
menuStructured: Now the defaults was moved out from MenuItem class to a separate new menuDefaults object in the MenuItem file. (b971ba3)
Modify getDialogId function in index.js to include an optional force parameter for refreshing dialogs (d3d90e8)
package.json: Update telegram-menu-from-structure to minimal version 1.2.0 to use extraRefresh feature. (d3d90e8)
Partially change the variable declaration style. (31b13f1)
Preliminary preparation to catch edited messages, as event or direct check of lastForwarded or lastProcessed messages. (ee034ab)
Preparation to edit additional users to be allowed to use the bot via Configuration. (b86ed1f)
Refactor telegram-menu-structured. (07e03e5)
Refactor cache event registration in index.js and fix type conversion issue in refreshDialogs() (c9a6dba)
Refactor code to use external makeButton function. (33edf86)
Refactor logging statements in Cache.js (dfc6aa4)
Refactor logging to reuse the logger from the gramjs (ebba407)
Refactor menu logger import to use correct casing (bfd8508)
Refactor MenuItemRoot class and light improvement of README.md (3ddba9a)
Refactor to accept command only as Bot via Bot Menu (6679b03)
Remove unused translation strings and update dependencies. Align with telegram-menu-from-structure version 1.1.5 (b64423d)
SecuredLogger: Refactor SecuredLogger to implement canLog compare of logLevel with external one (212d9af)
Some adjustments for keywords related texts (16f4306)
telegram-menu-structured: Get rid of dependency on external i18n object. Additionally property logger is converted to private. (eb13300)
telegram-menu-structured: Implemented Cancel button for the Inputs. (33edf86)
telegram-menu-structured: Improve menuDefaults to store and provide min, max and step for params. (08961bf)
telegram-menu-structured: Refactor menu button classes to work only as Bot to simplify command handling (6679b03)
telegram-menu-structured: Refactor MenuItem class to handle command checking and value setting (5401c21)
telegram-menu-structured: Refactor message editing and sending logic in MenuItem class to await approach with edit, send and delete Message (0348289)
telegram-menu-structured: Updated the menu module to remove unused code and fix a typo in the comments. (5a2d59a)
Update event message includes check to handle null values (for true picture messages) (4e9edef)
Update logic of representation and working with the menu defaults (b971ba3)
Update menu button creation logic. (75d0632)
Update menu initialization and drawing logic (d8bdbbd)
Update menuRootStructure in index.js to use the new configuration property names (d3d90e8)
Update telegram-menu-from-structure to version 1.3.1 to fix the buttons splitting on rows for the menu (a07bee4)
Update version to 1.0.86, make allowedUsers configurable from a menu and improve MenuItemStructured class (f019bc9)
Update version to 1.0.88 with initial version of README.md (bb6ca4f)
Update version to 1.1.0, added and-fast edit delay, improved logging on message forwarding, improved versions numeration approach (51ce3a8)
Update VSCode settings and MenuItemStructured class. Decrease the debug count and content. (f6fb2bc)

Build System

deps-dev: Bump @babel/core, and @babel/eslint-parser to version 7.25.7 (a3bf4b7)
deps: Bump version of telegram-menu-from-structure to 1.3.2. (a3bf4b7)
main: release 1.1.4 (bbde681)
main: release 1.1.5 (04b54cf)
main: release 1.2.0 (4d7b5c1)
main: release 1.2.1 (e9fce12)
main: release 1.2.2 (a4a21cf)
main: release 1.3.0 (13d538a)
main: release 1.3.1 (edde09f)
main: release 1.4.0 (ad8ee69)
main: release 1.4.1 (7816f1e)
main: release 1.4.2 (f509c91)
main: release 1.4.3 (8009123)
main: release 1.4.4 (ebe0ba5)
main: release 1.4.5 (5cd5edd)
main: release 1.5.0 (9ff1d9f)
main: release 1.5.1 (2310ff6)
main: release 1.6.0 (816191b)
main: release 1.6.1 (8a29668)
main: release 1.7.0 (aa2cc87)
Update eslint-plugin-sonarjs to version 2.0.2 (023ee56)

Continuous Integration

Add release-please-action to prepare releases and Changelog.md (f31b0e9)
docker: Refactor Docker deployment workflow to make completion of image URLs in README.md before update repo description (9f27e9c)
update package-lock.json (47f11f6)
Update package-lock.json (f97ce85)
Update release-please-config.json. Change order of Changelog sections. (535821f)
Update repo description in deploy_docker_on_tag.yml (97eb443)

Miscellaneous Chores

Add "gramjs" to cspell.json (c1dc8c7)
Add babel.config.json with "sourceType" set to "script" (a4af91e)
align menu Init to be comply with changes (b39c8af)
Bump version to 1.0.103. Fix catching missed messages on start. (bd499a4)
Bump version to 1.0.104, show forwardRule state in menu (enabled or disabled) (556a2d6)
Bump version to 1.0.110, for edited messages added content compare (e56f6da)
deps-dev: Bump @babel/core from 7.24.7 to 7.24.9 (aebeebb)
deps-dev: Bump @babel/core from 7.24.9 to 7.25.2 (645c642)
deps-dev: Bump @babel/eslint-parser from 7.24.7 to 7.24.8 (b159335)
deps-dev: Bump @babel/eslint-parser from 7.24.8 to 7.25.1 (51c38f4)
deps-dev: Bump eslint from 9.6.0 to 9.7.0 (d204670)
deps-dev: Bump eslint from 9.7.0 to 9.8.0 (ed98002)
deps-dev: Bump eslint-plugin-sonarjs from 1.0.3 to 1.0.4 (b10eec7)
deps-dev: Bump eslint-plugin-sonarjs from 2.0.2 to 2.0.3 (7bc450f)
deps-dev: Bump globals from 15.6.0 to 15.8.0 (cffa729)
deps-dev: Bump globals from 15.9.0 to 15.10.0 (456c312)
deps: Bump node from 18-alpine to 22-alpine (58a81ce)
deps: Bump telegram from 2.22.2 to 2.23.10 (84dfe6c)
deps: Bump telegram from 2.24.11 to 2.25.4 (4e9b729)
deps: Bump telegram from 2.25.4 to 2.25.11 (36237e2)
Modify the spaceBetweenColumns configuration parameter maximum value (08961bf)
Readme.md - update bot menu configuration options with appropriate screenshots. (19fb324)
release 1.6.2 (7d5bea7)
release 1.6.2 (ac7a28c)
Remove unused genversion dependencies and scripts (f31b0e9)
Remove unused labels from docker deployment workflow (76b225b)
telegram-menu-from-structure: Update telegram-menu-from-structure package to version 1.0.1 (b39c8af)
Update @eslint/js dependency to version 9.8.0 (a9c422d)
Update docker deployment workflow to exclude provenance (77af43a)
Update docker deployment workflow to get back labels labels (6fb411f)
Update docker deployment workflow to include metadata annotations (dfc4b60)
Update localization and dependencies. (524116b)
Update logging imports in MenuButton.js, MenuItemStructured and MenuItem.js (7017b72)
Update npm version in Dockerfile (48a04d9)
Update package version to 1.0.68 and add process replay on forwarded message functionality. Fixed processing commands from "work" user. (474d78e)
Update to version 1.0.65, fix Dockerfile and refreshDialogs. (077e3fb)
Update version to 1.0.100, improve debug logging on message reaction (62f2e44)
Update version to 1.0.101, fix message edited debug logs on refresh (8538f56)
Update version to 1.0.102, fix message edited debug logs on refresh (6906e9b)
Update version to 1.0.65 (f824320)
Update version to 1.0.89, change dev dependencies, fix Dockerfile. (5b65c63)
Update version to 1.0.90, fix applying the default values of MenuItemStructured using structuredClone, add missing translation key (b2f5554)
Update version to 1.0.91, process last message for edits only one time via refresh (1343f52)
Update version to 1.0.92, store last processed  message Id only if it has a higher Id then previous (d07e64e)
Update version to 1.0.93, fix message retrieval using message IDs for edited messages via Refresh (2588af1)
Update version to 1.0.94, improve message edited detection on refresh (508ad71)
Update version to 1.0.95, improve debug logging on refresh (1be5d95)
Update version to 1.0.96, another improve debug logging on refresh (6200508)
Update version to 1.0.97, improve message edited detection on refresh (a07c0a4)
Update version to 1.0.98, improve message edited debug logs on refresh (ea92c13)
Update version to 1.0.99, improve message check on refresh on start (929e9aa)
Update version to 1.1.1 and add the docker building workflow (d54d519)
Update version to 1.1.2, exclude message content comparison on edit event, not store message content on forward, code improvement related to the edited messages and update docker deployment workflow to include Docker Hub (b090bf7)

Documentation

Add a forwarding rules configuration to the bot menu, excluding filtering options, i.e. Keywords group, and without images. (5ad1635)
Finalize readme (16f4306)
Fix CHANGELOG.md (1aff623)
Refactor installation and run chapters (8cd095b)
Small fixes in README.md (9f27e9c)
Update CHANGELOG.md by previous changes (bfc597d)
Update command-line description (432bebb)
Update images for forwarding rules configuration in README.md (c9c5677)
Update README.md with information about filtering by keywords groups (aa86156)
Update README.md with new configuration option nad appropriate images. (9dfced5)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.6.2
:sunflower:


API.setPlayback(-1) doesn't seem to work

I was looking to implement a forward/backward functionality in my videoplayer and took a look at the forward button in the controls plugin, copied the code for it and called API.setPlayback(-1); to get the player to play backwards. The call didn't seem to have any effect since the video kept playing forwards. When I call API.setPlayback(2); it does accelerate to 2x speed.
The documentation states: "setPlayback(playback): Sets playback. Param plaback must be an integer with a value between 0 and 2", the HTML5 video tag however does support a playbackrate of -1.0 and in a previous email question I was told that -1 should work, so I guess this is either not suppored or a bug?

Most of browsers doesn't support negative playback rate. Test it here:
http://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_av_prop_playbackrate


Support for dependency groups

Is there currently support for https://github.com/python-poetry/poetry/issues/1644 if not could it be added?

This action just installs the poetry tool

So poetry install --with ... should be ran inside a separate step?

Yes, this action just installs poetry itself. Then you would restore your virtualenv if you cached it and run poetry commands.

Ok thank you for the clarification


Use Hooks

Is it possible to use hooks inside getCellContent to access redux store where my data is stored?

No


Move all the codes for simulator into new directory

What type of PR is this?

/kind cleanup
What this PR does / why we need it:
Create /simulator directory and move all simulator-related codes to /simulator dir.
Which issue(s) this PR fixes:

Fixes #191
Special notes for your reviewer:
/label tide/merge-method-squash

/assign @196Ikuchil @everpeace

It would affect all PRs which currently submitted.

Yeah.... 😅 Hope the rebasing won't be so hard since it need to change file paths and import paths.

@196Ikuchil Fixed

Thank you, nice work.
/lgtm


Apllied Energistics uptime

I am running resonant rise 3 pack from the atlauncher with code pxoVTdul.  I have a few of the max sized compact machines inside my base but the majority of my applied energistics system is not in one.  I have terminals and input and output buses on systems inside these compact machines.  I use mostly ender conduit to run both power and ae into the compact machines.  While inside looking at things in the terminals will go down at random intervals and then reconnect and come back up.  It seems to lose connect like it disconnected from the main line and then reconnected.  It happens quite frequently.

That seems to happen to me when i try and shift-click an inventory full of items into the me system.
I dunno what it is, but i hope it doesn't get worse.

update it happens every 2 minutes and is down for about 5 seconds.

@Badcholo in the case you described it is definitely a power surge. Try putting some AE energy cells on your system.
@deathglow is your main base, or wherever your AE system is, chunkloaded? You could also try out what I suggested to Badcholo.

The me system does have a energy cell in it and the main base has a chunk loader to keep it going at all times.  I have no issues back at my base, only inside the compact machines dimension.

yes, i only had a simple energy acceptor, a fluix cable, terminal, me drive, and storage drives.
maybe the Energy acceptor only transfers a set amount of power, i'm going to check the configs.
I'll try adding an energy cell.
I'm in the same dimension.

@Badcholo the AE system can only consume as much power as it can store.

After messing with a few things I am pretty sure it is fixed.  It seems that my AE system is just to big and causes lag issues.  When I break a controller and reattach the system seems to fix itself.


Create buyer email domains via the API

Trello ticket: https://trello.com/c/JxwDhnDh/82-migrate-existing-domain-check-to-use-database

Add the BuyerEmailDomain model (used to generate the schema migration in PR 1) and a serialize method
New route to create new BuyerEmailDomain objects
Validate requests using JSON schema
Ensure buyers with a domain already approved (either in the DB or the .txt file) can still create an account

NB This branch is based on the schema migration branch in order to make the tests pass, so the migration will be included in the diff until that gets merged. Travis will fail on this PR until the APIClient PR is merged.
This is PR 3 out of 4.
PR 1: Schema migration alphagov/digitalmarketplace-api#672
PR 2: API Client https://github.com/alphagov/digitalmarketplace-apiclient/pull/102
PR 4: Data migration https://github.com/alphagov/digitalmarketplace-api/pull/675

I feel like even for MVP we should have at least a list domains endpoint, otherwise there's no way to review the list.
If we're planning to add admin features for this I think delete could be pretty important as well, because typos will happen sooner or later. We'd need to do something about buyer accounts that only exist thanks to that domain record though, which could be an argument for making this check  affect user active flag on each read for example.

We did think about whether list/delete endpoints were necessary just yet - I think we agreed they're probably out of scope for this particular story. Happy to discuss further on Monday with the team?


Add BigDecimalAssertion for floatingPointFormat and IntegerPointFormat

This is my first attempt to contribute the open sources, so I am not sure what I should do exactly.
I add Assertion and AssertionTest for floatingPointForamt and IntegerPointFormat following

close #3532

Please let me know, if I should do something more or something to fix
Thank you
Check List:

Unit tests : YES
Javadoc with a code example (on API only) : YES
PR meets the contributing guidelines

Following the contributing guidelines will make it easier for us to review and accept your PR.

@joel-costigliola
Thank you for the great comment. I change the files following the comment.

Add the error unit test
change assertThat -> BDDAssertions.then
use parametized test instead of using pure test
mvn spotless:apply


How to Build APK with Plugin Lib?

I am using a lib like this,
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.2
image_picker: ^0.6.7+4
app-release.apk(file size 16M) does not work, but app-debug.apk(49M) can work fine.
How can fix this problem?

Hi @mkkatjp
What is the problem?
What exactly is not working?
Can you please provide your flutter doctor -v and a minimal complete reproducible code sample?
Thank you

Hi @mkkatjp
What is the problem?
What exactly is not working?
Can you please provide your flutter doctor -v and a minimal complete reproducible code sample?
Thank you

C:\flutterSDK\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel master, 1.26.0-2.0.pre.200, on Microsoft Windows [Version 10.0.18363.1256], locale ja-JP)
• Flutter version 1.26.0-2.0.pre.200 at C:\flutterSDK\flutter
• Framework revision d0e9959a46 (8 hours ago), 2021-01-05 22:14:03 -0500
• Engine revision e115066dcd
• Dart version 2.12.0 (build 2.12.0-179.0.dev)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\flutterSDK\flutter
• Platform android-30, build-tools 30.0.3
• ANDROID_SDK_ROOT = C:/Users/m/AppData/Local/Android/sdk
• Java binary at: C:\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] VS Code (version 1.52.1)
• VS Code at C:\Users\m\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.18.0
[√] Connected device (3 available)
• ASUS X00ID (mobile) • J2AXB760V768V75 • android-arm64  • Android 7.1.1 (API 25)
• Chrome (web)        • chrome          • web-javascript • Google Chrome 87.0.4280.88
• Edge (web)          • edge            • web-javascript • Microsoft Edge 87.0.664.66
• No issues found!
Process finished with exit code 0

C:\flutterSDK\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel master, 1.26.0-2.0.pre.200, on Microsoft Windows [Version 10.0.18363.1256], locale ja-JP)
• Flutter version 1.26.0-2.0.pre.200 at C:\flutterSDK\flutter
• Framework revision d0e9959a46 (8 hours ago), 2021-01-05 22:14:03 -0500
• Engine revision e115066dcd
• Dart version 2.12.0 (build 2.12.0-179.0.dev)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\flutterSDK\flutter
• Platform android-30, build-tools 30.0.3
• ANDROID_SDK_ROOT = C:/Users/m/AppData/Local/Android/sdk
• Java binary at: C:\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] VS Code (version 1.52.1)
• VS Code at C:\Users\m\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.18.0
[√] Connected device (3 available)
• ASUS X00ID (mobile) • J2AXB760V768V75 • android-arm64  • Android 7.1.1 (API 25)
• Chrome (web)        • chrome          • web-javascript • Google Chrome 87.0.4280.88
• Edge (web)          • edge            • web-javascript • Microsoft Edge 87.0.664.66
• No issues found!
Process finished with exit code 0

main.dart
import 'dart:io';
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';
void main() => runApp(MyApp());
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
home: MyHomePage(),
);
}
}
class MyHomePage extends StatefulWidget {
@override
_MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
File _image;
final picker = ImagePicker();
bool camera = true;
Future getImage() async {
var v = ImageSource.camera;
if (!camera) v = ImageSource.gallery;
var pickedFile = await picker.getImage(source: v);
setState(() {
  if (pickedFile != null) {
    _image = File(pickedFile.path);
  } else {
    print('No image selected.');
  }
});

}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text('Image Picker Example'),
),
body: Center(
child: _image == null
? Text('No image selected.')
: Image.file(_image),
),
floatingActionButton: FloatingActionButton(
onPressed: () {
getImage();
camera = !camera;
},
tooltip: 'Pick Image',
child:
Icon(Icons.add_a_photo),
),
);
}
}

main.dart
import 'dart:io';
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';
void main() => runApp(MyApp());
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return MaterialApp(
home: MyHomePage(),
);
}
}
class MyHomePage extends StatefulWidget {
@override
_MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
File _image;
final picker = ImagePicker();
bool camera = true;
Future getImage() async {
var v = ImageSource.camera;
if (!camera) v = ImageSource.gallery;
var pickedFile = await picker.getImage(source: v);
setState(() {
  if (pickedFile != null) {
    _image = File(pickedFile.path);
  } else {
    print('No image selected.');
  }
});

}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text('Image Picker Example'),
),
body: Center(
child: _image == null
? Text('No image selected.')
: Image.file(_image),
),
floatingActionButton: FloatingActionButton(
onPressed: () {
getImage();
camera = !camera;
},
tooltip: 'Pick Image',
child:
Icon(Icons.add_a_photo),
),
);
}
}

pubspec
name: my_image_picker01
description: A new Flutter application.
publish_to: 'none'
version: 1.0.0+1
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.2
image_picker: ^0.6.7+4
flutter:
uses-material-design: true

pubspec
name: my_image_picker01
description: A new Flutter application.
publish_to: 'none'
version: 1.0.0+1
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.2
image_picker: ^0.6.7+4
flutter:
uses-material-design: true

android/build.gradle
buildscript {
repositories {
google()
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:4.1.0'
}

}
allprojects {
repositories {
google()
jcenter()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
task clean(type: Delete) {
delete rootProject.buildDir
}
dependencies {
}

android/build.gradle
buildscript {
repositories {
google()
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:4.1.0'
}

}
allprojects {
repositories {
google()
jcenter()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
task clean(type: Delete) {
delete rootProject.buildDir
}
dependencies {
}

app/build.gradle
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
compileSdkVersion 30
defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.triumph.my_image_picker01"
    minSdkVersion 16
    targetSdkVersion 30
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}
flutter {
source '../..'
}

app/build.gradle
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
compileSdkVersion 30
defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.triumph.my_image_picker01"
    minSdkVersion 16
    targetSdkVersion 30
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}
flutter {
source '../..'
}

gradle-wrapper.properites
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-6.5-all.zip

gradle-wrapper.properites
#Fri Jun 23 08:50:38 CEST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-6.5-all.zip

Thanks for you reply.
I can RUN in my smartphone, in Debug Mode.
But when I build it in release mode,
app-release.apk(file size 16M)  can install in smartphone, but It does not work in smartphone,
(can not show Picker Page?[or Dialog])
but app-debug.apk(49M) can work fine.
How can fix this problem?

Thanks for you reply.
I can RUN in my smartphone, in Debug Mode.
But when I build it in release mode,
app-release.apk(file size 16M)  can install in smartphone, but It does not work in smartphone,
(can not show Picker Page?[or Dialog])
but app-debug.apk(49M) can work fine.
How can fix this problem?

@mkkatjp
Does it shows any error/crash logs in the console?

@mkkatjp
Does it shows any error/crash logs in the console?

No any Error or Crash in console. It is all OK when in Debug mode.

No any Error or Crash in console. It is all OK when in Debug mode.

Hi @mkkatjp
I was able to reproduce the issue however there is already a similar issue (https://github.com/flutter/flutter/issues/72759) so I'm going to close this one. Please follow up on that issue for updates!
Closing this as duplicate.
Thank you.

Hi @mkkatjp
I was able to reproduce the issue however there is already a similar issue (https://github.com/flutter/flutter/issues/72759) so I'm going to close this one. Please follow up on that issue for updates!
Closing this as duplicate.
Thank you.


What's the difference between In2ReferenceOpenHashMap and Int2ObjectOpenHashMap?

Dear fastutil experts,
Could u please kindly let me know what's the difference between In2ReferenceOpenHashMap and Int2ObjectOpenHashMap?
Really appreciate ur great help in advance!
Thanks,
Roy

Issues should be issues—please use the mailing list for questions.
If you just use the key/value association, no difference. But if you use values(), in the first case the collection is by reference, in the second case by value. So if you do a values().contains() the results might be different. Since it is very rare to use values() in such way, just use Int2Object.

Thx @vigna for ur clear explanation! I will use the mailing list for questions from now on.


Program closes immediately.

Keyboard: K95 RGB Platinum
Windows 10 Pro 64-bit
The program appears in the notification bar after opening and the keyboard's existing default profile (rainbow-y) turns off. After roughly 2 seconds, the program closes in the notification bar and the keyboard flicks back to default.

What sound system do you use when this occurs?

Keyboard: K95 RGB Platinum
Windows 10 Pro 64-bit
Same problem for me using 2 sound system : Realtek Digital Output(Optical) so an optical output and an usb output. But desactivate them once by once still doesn't work. In admin mode the program crash faster. Compatibility version don't work. Hope you can fix that if you have any question.

Working fllawlessly for circa 18month on my Strafe Cherry MX Red (not RGB), now showing same as above, Win 10 64-bit is my OS, running latest FW and CUE

Alrighty... Anybody in here a programmer? If so, please give me something to work with.
Steps if you are not a programmer:

Install Visual Studio 2015
Clone this project and load up the solution in Visual Studio (double-click the .sln file in the extracted folder)
Press F5 and let me know WHERE the point (Line # and what file) is where it fails! (Bonus points for screenshots of the Visual Studio window)

I'm sorry if I sound like I'm being rude, but apparantly I might get fired from my job, so I'm not really happy at the moment

Well something goes wrong in CueSDK.Initialize,
updating to new CueSdk just works fine,
I think DarthAffe's fork  should be merged to master which just works fine for me.
Thanks for the app again .

Huh, that is something that I never expected to be a problem.
Also, I'm not the owner of this repository, so I unfortunately can't merge or upload anything to the repository and @AterialDawn has gone radio-silent.
Thanks anyway for finding what went wrong. Maybe people can find this post and download the fork and compile it themselfes =)

Well I belive compiling is something pain in the a.. , so while I got my hands on it I put the compiled files here.
Anyone may download it with this link:
CUEAudioVisualizer(DarthAffe fork).zip

Thanks musakasim, don't have time to recompile myself, works fine now.

@pcnorden and @musakasim thank you both, you're right to say i'm an infrastructure guy, last programming I did was Fortran 5 !!!  Thank you again, most appreciated.

Just dropping a line here to tell you all about (DartAffe's visualizer)[https://github.com/DarthAffe/KeyboardAudioVisualizer].
It works a LOT better with 5.1 and 7.1 audio systems.
Take care!


Improve GitHub search

Hey there!
When searching for admin template here in GitHub, the most stared result is a template with 5k stars. Which means AdminLTE missed this simple search.
The AdminLTE readme has this text: "AdminLTE -- is a fully responsive admin template"
So, even with this headline, this template misses the search I said above.
Is there a way to improve GitHub search for this template, so it would get even more stars/users?
Thanks!

I think it is in the algorithm form github.


Kernel updates for 2023-06-14

Description of changes
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.3.8
Notably fixes a "route of death" DoS vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2023-2156
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

Tested 6.3.8, seems fine, merging because it's a pretty bad CVE.


[Bot Channels Registration] Cannot find app secret when creating SDK bot through Azure Portal

Congratulations on the GA release of the bot service and LUIS!
I'm trying to create a new bot registration, and obviously, dev.botframework.com doesn't let me anymore. So I follow the process of creating a Bot Channels Registration in the Azure Portal. Everything goes well. I realize I don't have my app id/secret. I find the app id in settings. Great. Still no secret. So I click the manage link and find it hidden there.
No problem, I figure let's create a new password but I get this error since yesterday (Friday 12/15) afternoon:

So, basically can't create bot registrations anymore.
Can you support?
Thanks
-s

Thanks for reporting this to us. This underlying issue has been identified and is being addressed by the team. We apologize for the inconvenience.

@srozga check out
https://docs.microsoft.com/en-us/bot-framework/bot-service-quickstart-registration#bot-channels-registration-password

Thanks @nwhitmont . Great doc. I'll keep it handy.


fix(dependencies): upgrades  react-addons-shallow-compare and fixes view-prop-types

+1 for this one in order to fix:

https://github.com/advisories/GHSA-r683-j2x4-v87g
https://github.com/advisories/GHSA-w7rc-rwvf-8q5r

+1, this PR should be accepted as soon as possible

Please this will killed fbjs 0.84 is too much old.
This PR should be accepted


Fix excessive processing / system load at startup

After running docker-compose up --build -d on Windows, there's >2 minutes of high CPU usage. After that's over, there's another 10 seconds or so before the server is actually up.

This no longer seems to happen for me.

Was clearly fixed at some point last year.


Tuning SHT75 Sensor

Hi,
I really appreciate the python library for the SHT75 sensor. However the temperature results I'm getting are routinely a little high and I cant yet figure out why. At the moment all I have as references are 3 separate temperature and humidity monitoring devices. Consumer products from Maplin Electronics so not seriously accurate but hopefully not too off the mark.
The readings I'm getting from the SHT75 ( I have two ) are constantly 2 to 4 degrees higher than the other consumer units show.  One SHT75 is 2 degrees higher and the other is 4 degrees higher.
I'm using a Raspberry Pi 2 and attaching the SHT75 to the 3.3V, GND, a CLK pin, and a DATA pin.  There is a 10K pull up resistor on the Data pin per the data sheet pdf from Sensirion.
Is your setup any different ?
Have you by any chance developed a way to look at the register? It may be the heater is turned on ! but that seems strange.
The data sheet also refers to self-heating if measurements are too frequent.  I'm measuring at 10 second intervals so that should be OK.  I have varied it from 5 seconds to 10 seconds and not seen any noticeable difference.
Is it possible the device should be turned off (power removed) between readings?
Thanks in advance.

Don't think I can be of much help here, unfortunately.
I'm not a metrologist, don't know much about what's inside these sensors and what can affect them beyond what is common knowledge.
Only worked with these on hobby projects and one-off jobs, where high accuracy wasn't a concern.
So please don't take my word as any kind of reliable source of info on the subject.
Obvious thing to check - which you've probably covered, but guess I'll mention it anyway - is that when you compare results, sensors are right next to each other in exactly same conditions, and measurements are taken at the same time.
Even room temperature can vary by few degrees for sensors a meter or two apart, I think, not to mention direct sunlight, steam/vapor from coffee mug below or whatever other huge factors.
Not sure if wire temperature should affect these sensors much (i.e. how well they're shielded from that), but it sure does a lot with e.g. simple thermistors.
So I'd also suggest trying to compare data from these with wires in the same env as sensor, as e.g. thermistor with long wire on the outside vs inside can easily give few degees of difference.
Then I'd also check the voltage on VDD/GND pins - RPi should probably have stable 3.3V, but might be still worth checking, as that might be off due to e.g. bad wire/contacts, and should affect the measurements, not sure if by that much though (and yet still work).
Currently have DHT22 and SHT75 sitting ~0.5m apart, difference seem to be 0.2 C (26.85 vs 27.02), connected to diff boards, and one on ~2m wire, so looks close enough to me.
Wrt sensor defects - with three DHT22 sensors next to each other, had one that was always about 2C higher than others, one DHT22 consistently gives random -5C delta every once in a few minutes when it's below zero, etc... but maybe SHT75 shouldn't have such quirks.

Is your setup any different?

No, same stuff, though I did connect VDD to 5V instead of 3.3V in some cases.

Have you by any chance developed a way to look at the register?

No, never needed it, really.
All commands for that are in datasheet though, so you can probably add that yourself rather easily.
Don't think sensor should keep state of the heater bit on power-cycling, so I think it's gotta be off for sure, wouldn't bother to implement anything to check it.

Is it possible the device should be turned off (power removed) between readings?

Fairly sure it should not be the case - haven't seen anything like that in the datasheet, seem to work fine without that, and it doesn't make sense to me on many levels.

The data sheet also refers to self-heating if measurements are too frequent.

I'd think that it'd refer to taking measurements in a tight loop, like 1/s or whatever device itself permits, but don't really know.
Few seconds sound fine, and indeed easy to rule-out via simple test (where t doesn't go up) like you did.

I have (blushing) found that the distance from the Raspberry Pi is be a big factor in the odd readings. Heat from the Pi caused the issue !! . Still some fine tuning remaining I believe though.
Many thanks for the reply. You have given me some insights that are very interesting.
Another question.
How are you physically arranging the sensor and the wires and the pull up resistor. I have not yet found a nice and cost effective way to connect things. The sensor and board package are quite delicate. There are professional enclosures with nice cables but they are expensive. The pull up is awkward to add in between the flying leads and I cant see another way to add the resistor !
Thanks again for the reply.

Um, I just solder resistor to the wires near the board (or whatever) connector.
Always connected these to wires (e.g. 4-wire 1mm ribbon cable), once by soldering wires to leads directly, but other times by soldering something like PBD1.27-10 ( http://www.promelec.ru/UPLOAD/2013/11/13/131186.jpg ) and then plugging sensor into that.
And then you can solder pull-up to any place on that cable.
Looks like a rather obvious option though, so maybe I don't understand constraints/requirements that you have (e.g. have to solder thing to PCB or something like that).
With RPi and short-ish cable (not meters of it), don't think you need to bother with pull-ups at all, as RPi has internal (~50-60K) pull-ups, which can easily be enabled from software.
Iirc they worked fine with all sorts of sensors and devices for me, including this one.
If you need pure-python code to enable them (via /dev/mem), can grab it here - https://github.com/mk-fg/fgtk/blob/master/rrd-sensors-logger#L923-L949 (it's for RPi only, of course, as it writes stuff to SoC-specific registers).

No pull-up is a nice idea. Thanks. I'll try that out. Makes the whole building process much simpler.
Thanks for the help.

GPIO.setup(24, GPIO.IN, pull_up_down = GPIO.PUD_UP)

Yeah, should work too, or you can also use "gpio" binary from wiringpi.
This module uses /sys/class/gpio/ interface though, exporting pins there might or might not reset pull-up/down registers, not sure...


Wrong width on table-responsive

Now on large screens table not stretch on full width: http://joxi.ru/bmoO3EnFBP9Xmy
Need apply class table-responsive only if screen < 768px

Dupe of #21577.


Packaging nnvm for NixOS

Hi! I am trying to write a package expression describing the build process of nnvm in Nix language. Actually, tvm and nnvm build steps already work (all addons are disabled), the problem appears when I try to build nnvm/python module.
The error is below:
nnvm (unittest.loader._FailedTest) ... ERROR

======================================================================
ERROR: nnvm (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: nnvm
Traceback (most recent call last):
  File "/nix/store/cwxxbpfz2i2j34f3sgmd6vdl6wv98c2s-python3-3.6.4/lib/python3.6/unittest/loader.py", line 462, in _find_test_path
    package = self._get_module_from_name(name)
  File "/nix/store/cwxxbpfz2i2j34f3sgmd6vdl6wv98c2s-python3-3.6.4/lib/python3.6/unittest/loader.py", line 369, in _get_module_from_name
    __import__(name)
  File "/tmp/nix-build-python3.6-nnvm-0.8.drv-0/python/nnvm/__init__.py", line 6, in <module>
    from . import _base
  File "/tmp/nix-build-python3.6-nnvm-0.8.drv-0/python/nnvm/_base.py", line 47, in <module>
    _LIB = _load_lib()
  File "/tmp/nix-build-python3.6-nnvm-0.8.drv-0/python/nnvm/_base.py", line 39, in _load_lib
    lib = ctypes.CDLL(lib_path[0], ctypes.RTLD_LOCAL)
  File "/nix/store/cwxxbpfz2i2j34f3sgmd6vdl6wv98c2s-python3-3.6.4/lib/python3.6/ctypes/__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /nix/store/8xzvqzqhdan9lviznks75ma8nczms55y-nnvm/lib/libnnvm_compiler.so: undefined symbol: _ZTIN3tvm4NodeE

I've done some investigation and found that libnnvm_compiler.so contains undefined symbol mentioned above, which is actually defined in libtvm.so
$ nm result/lib/libtvm.so | grep _ZTIN3tvm4NodeE
0000000000845dd0 V _ZTIN3tvm4NodeE

AFAIK, the Python module should be linked with both libraries, but putting path to libtvm.so in LD_LIBRARY_PATH didn't help. Could you please guess what I am missing here? How to ask Python to take libtvm.so into account?
Regards,
Sergey

I've managed to solve the issue - I forgot to build tvm-python which brings the missing .so library.


Add header to authenticated request/messsage

It seems currently not possible to add a header to an authenticated restrequest/transportmesssage. This is only possible in the AuthenticationFailureHandler when things go wrong. Adding headers to the final HTTP 200 message would be required for implementing GSSAPI mechanisms IMHO. Any plans/advices here?

Hi @salyh,
You are correct. As realms are currently implemented, we do not intercept the responses of messages or have a way to add such a header on a success. We are looking at how we can enable this type of functionality.
When you refer to GSSAPI, are you mainly thinking of HTTP SPNEGO based Kerberos(RFC 4559)? In terms of an immediate solution/workaround, this type of authentication can work without the final token in the HTTP 200 response. The proper solution though is to comply with the RFC and always send back the token if there is one to return.

Exactly, i am working on a SPNEGO Realm for Shield.

Kerberos Realm is released: https://github.com/codecentric/elasticsearch-shield-kerberos-realm

Any updates?

This should be possible in the next major version since we changed how we handle headers and context with requests in elasticsearch. I do not think we will have anything before then

@salyh this is now possible in the 5.0 series. You can add the ThreadContext to your token during extraction and then in the authenticate method you can call ThreadContext#addResponseHeader.


Fix: Create text on image #146

Fixes Issue #146 text_on_image Creator - Web design

@NtemKenyor
Can you please check the PR.
Thanks

Dear Ntem, Kenyor K.,
Thank you for the warm welcome to the Kwickerhub project! I'm excited about the progress and the upcoming GPT release. The sponsorship activation is fantastic, and I'm fully on board to support. Congratulations to the team, and I'm grateful to be part of this journey.
Best regards,
Vipraj Telukoti


Added stderr output as additional callback parameter

gpg sends some additional information to stderr even if everything was fine. For example the key verification information during decryption.
To provide access to this information without redirecting it to stdout this change adds the "error" as a third parameter to the callback function.
This allows users to get the decrypted content and the additional information separately if needed.
My usecase:
I wanted to review the key verification information during decryption.
gpg: encrypted with 2048-bit RSA key, ID C343C0BC, created 2015-06-01
      "Node-GPG Test Key (Keypair used for node-gpg testing<EMAIL_ADDRESS>
currently this information is not accessible through node-gpg as stderr is ignored when the call to gpq was successful. One solution would be to redirect stderr to stdout but this would change the decryption result and add this additional information.
To solve this this PR adds the error as a third parameter to the callback that can be used or not and should not affect any backwards compatibility.
Usage:
gpg.decrypt(encryptedString, function(err, decrypted, stderr) {
  console.log(err);
  console.log(decrypted);
  console.log(stderr);
});

nice, thanks for the quick feedback and the merge.
what is your policy regarding releasing new versions?

I reviewed/merged my first PR last night on my phone ;) I'll go ahead and do a new release now.

hehe ;) great :octocat:
thanks a lot!


LinkError: pre-link script failed for package jirinovo::pubchempy-1.0.3-py_0

Preparing transaction: done
Verifying transaction: done
Executing transaction: failed
LinkError: pre-link script failed for package jirinovo::pubchempy-1.0.3-py_0
location of failed script: /home/pan081/miniconda3/pkgs/pubchempy-1.0.3-py_0/bin/.pubchempy-pre-link.sh
==> script messages <==

==> script output <==
stdout:
stderr: + /miniconda3/envs/my_new_env/bin/python /miniconda3/pkgs/pubchempy-1.0.3-py_0/link.py
/miniconda3/pkgs/pubchempy-1.0.3-py_0/bin/.pubchempy-pre-link.sh: line 2: /miniconda3/envs/my_new_env/bin/python: No such file or directory

I also get the same error when installing molminer using the ff: command:
conda create -n molminer python=3.5 molminer


index rebuild exceeds 80w limit and 65536 cassandra limit

Actual behavior 实际表现

HugeException: Too many records(must <=800000) for the query: ....

or

HugeException: Batch statement cannot contain more than 65535 statements...

Steps to reproduce the problem 复现步骤

insert > 80w vertices
create secondary/range index

Specifications of environment 环境信息

hugegraph version: 0.8.0

v0.12.0本版执行g.V().out().limit(10)还是报这个错误啊，大约120W条数据一共


weatheril library in DEBUG mode no matter what settings for ims is

@arnonm
can you share your: logs: section in configuration.yaml

logs:
homeassistant.components.xiaomi_ble: info
homeassistant.components.ble_monitor: info
custom_components.ims: info
custom_components.weatheril: info
custom_components.hacs: error
custom_components.samsungtv_smart.api.samsungws: info
custom_components.lms_tts_notify: debug

@arnonm - and which debug logs are you seeing?

Snippet from ha core logs (after reset):
2023-08-20 10:22:51.622 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration sonos_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-20 10:22:59.826 | DEBUG    | weatheril:_get_data:228 - Getting data from https://ims.gov.il/en/now_analysis/21
2023-08-20 10:23:00.049 | DEBUG    | weatheril:get_current_analysis:76 - Getting current analysis
2023-08-20 10:23:00.049 | DEBUG    | weatheril:get_current_analysis:79 - Got current analysis for location 21
2023-08-20 10:23:00.367 | DEBUG    | weatheril:get_forecast:115 - Getting forecast
2023-08-20 10:23:00.368 | DEBUG    | weatheril:_get_data:228 - Getting data from https://ims.gov.il/en/full_forecast_data/21
2023-08-20 10:23:00.596 | DEBUG    | weatheril:get_forecast:121 - Got forecast for location 21
2023-08-20 10:23:00.976 | DEBUG    | weatheril:get_radar_images:182 - Getting radar images
2023-08-20 10:23:01.178 | DEBUG    | weatheril:get_radar_images:196 -                 Got: 21 IMS Radar Images;                11 Radar Images;                13 Middle East Satellite Images;                13 European Satellite Images
Snipplet above will also appear periodically.

Snippet from ha core logs (after reset):
2023-08-20 10:22:51.622 WARNING (SyncWorker_4) [homeassistant.loader] We
found a custom integration sonos_cloud which has not been tested by Home
Assistant. This component might cause stability problems, be sure to
disable it if you experience issues with Home Assistant
2023-08-20 10:22:59.826 | DEBUG    | weatheril:_get_data:228 - Getting
data from https://ims.gov.il/en/now_analysis/21
https://ims.gov.il/en/now_analysis/212023-08-20 10:23:00.049 | DEBUG    |
weatheril:get_current_analysis:76 - Getting current analysis2023-08-20
10:23:00.049 | DEBUG    | weatheril:get_current_analysis:79 - Got current
analysis for location 212023-08-20 10:23:00.367 | DEBUG    |
weatheril:get_forecast:115 - Getting forecast2023-08-20 10:23:00.368 |
DEBUG    | weatheril:_get_data:228 - Getting data from
https://ims.gov.il/en/full_forecast_data/21
https://ims.gov.il/en/full_forecast_data/212023-08-20 10:23:00.596 |
DEBUG    | weatheril:get_forecast:121 - Got forecast for location
212023-08-20 10:23:00.976 | DEBUG    | weatheril:get_radar_images:182 -
Getting radar images2023-08-20 10:23:01.178 | DEBUG    |
weatheril:get_radar_images:196 -                 Got: 21 IMS Radar Images;
11 Radar Images;                13 Middle East Satellite
Images;                13 European Satellite Images
Snipplet above will also appear periodically.
On Sun, Aug 20, 2023 at 10:19 AM Guy Khmelnitsky @.***>
wrote:

@arnonm https://github.com/arnonm - and which debug logs are you seeing?
—
Reply to this email directly, view it on GitHub
https://github.com/t0mer/ims-custom-component/issues/56#issuecomment-1685208311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5BWKLL2EUYNPC7CRNAZJLXWG26NANCNFSM6AAAAAA3WUEDDM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Strange.
Try this:
logger:
  default: info
  logs:
    custom_components.sensor.ims: debug
    custom_components.ims: debug
    custom_components.weather.ims: debug

Actually, changed all to info:
custom_components.ims: info
custom_components.weather.ims: info
custom_components.sensor.ims: info
and the messages don't appear again!!!
Great, thanks. Worth adding to the readme.

Good to hear. :)


Fix/vercel headers fix

This should fix #117 using the solution from gdomaradzki
It reverts the logic of getHeaders function, and deployments to Vercel work correctly

We're going to fix this on the Vercel side, so no need to merge this PR.

We're going to fix this on the Vercel side, so no need to merge this PR.

Sure, then feel free to the PR

This is the PR that fixed it, and it's been deployed to production in Vercel.

Thanks @TooTallNate for fixing it on Vercel's side!
I'm closing this PR and the associated issue.


settings.json conflicts when there aren't any changes

Issue Type: Bug
I don't know how to reproduce it.
After leaving VSC open, I get an error saying:
Failed to save 'settings.jsons': The content of the file is newer.
Please compare your version with the file contents or overwrite the content of the file with your changes.

When comparing, they're both the same.
If I overwrite it, the notification just comes back a few hours later and the settings.json file gets opened.
 Can you please bisect your extensions and see which extension is causing it? Please follow this doc - https://code.visualstudio.com/blogs/2021/02/16/extension-bisect for doing extension bisect.

Just to add here, I'm having the same issue and I see it happening when the system theme changes during automatic mode. The theme changes to either dark or light and this causes vscode to add the workbench.colorTheme attribute in light mode and then brings the unsaved changes popup.

This issue has been affecting me as well as of the last 10 days or so, which also happens to be the age of this reported issue. And indeed, it coincides with when my system switches from light mode to dark mode and vice versa: suddenly I'm asked to confirm changes to settings.json (which I haven't touched), and when I click to compare what the changes are, there are none.

I have exactly the same experience reported buy others - it seems to happen when the system switches from light to dark mode automatically.

I had the exact same problem, and somehow I fixed it whilst replicating it for a screen recording to post here.
I didn't want to screen record any sensitive code, so I was opening a new vs code window to show it happening, but it didn't happen. So I created a workspace to see if that's why, and now it's fixed in all my other opened workspaces too!
I had three other workspaces open, and when I was replicating the bug, it was occurring in all three workspaces. I'm on the latest VS Code as of writing.
Version details
```
Version: 1.64.2
Commit: f80445acd5a3dadef24aa209168452a3d97cc326
Date: 2022-02-09T22:00:56.651Z (1 wk ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 21.3.0
```

Here's what I did (in macOS), hopefully it helps someone!

opened a new vs code window
saved as a workspace in my home folder
opened the file explorer sidebar
it was empty because I hadn't added any folders yet
clicked "Open Folder"
in the file dialog, I created a new folder in my home directory, and chose it
vs code popped up to ask "Do you trust the authors of the files in this folder?" even though it was empty
I clicked yes
then I saved a new workspace (same as step 2) but in the folder I just created
hit issue #122293 where the Running 'File Create' participants... dialog shows and the file isn't created yet
waited 60s for the file to be created (the .code-workspace file from step 9 in the folder from step 6)
created a text file in the folder via vs code File: New File
again waited 60s (again because of issue #122293)
opened my settings json
opened my macOS General settings window above the vs code window
switched theme from Light to Dark
💥 the settings json switched theme and saved without the conflicts popup!

Absolutely no idea why any of that is related, but my issue is gone! I was seeing this issue for the past few days, since I would lock my macbook, then in the evening, macOS Night Shift would turn on, which would cause Dark appearance to be applied. Over the winter, this was occurring during my working hours, so I was seeing VS Code shift automatically to my dark theme (it was great!). So it must've been doing this now whilst the macbook was locked, because it's getting dark later in the evening. I'd unlock in the morning and see this exact issue on all of my open workspaces, with unsaved changes to my settings json, but no discernible differences, presumably because it had already switched back to Light theme in the morning.
Anyway, issue gone, and I'm so thankful! I hope the above is helpful to someone, whether they're another user who gets to fix it on their side too, or a VS Code dev who's able to make a connection and find the affected code. Sorry I can't screen record to replicate it!

This is really annoying. I can reproduce this with all extensions disabled and with workspace trust disabled. Repro instructions:

Open VSCode on macOS
Configure a different light and dark theme (I left Preferred Dark Color Theme and Preferred Light Color Theme as their default values, which are Dark+ (default dark) and Light+ (default light))
Open some directory in one window
Open some other directory in a different window
Change the system appearance in System Preferences back and forth a few times

Unexpected: One of the two windows will show Failed to save 'settings.json': The content of the file is newer. Please compare your version with the file contents or overwrite the content of the file with your changes. This is extremely annoying with more than two VSCode windows open (I typically have 10+ for different projects) as all but one window will have the settings.json file open and dirty. I then have to dismiss the alert, undo the edit, and close settings.json in each window. It means theme switching in VSCode is barely usable.
Here's a screen recording that shows how annoying it is:
https://user-images.githubusercontent.com/406394/154816941-1d87f4e2-f639-4e15-8315-27e8953aec22.mov

This happened to be on Windows 10 as well, though it does not trigger every time I do the theme switch via "Setting -> Personalization -> Colors -> Light/Dark", and only in one workspace.
I guess fewer people are affected on Windows as the system does not provide an option to auto-switch theme when the time of day changes, but the issue is there. I get for macOS it can be annoying with the "Auto" switch theme option.

I think I saw this issue before, but I'm unable to repro it now, even with Stable. Is anyone here able to confirm whether or not the issue has been fixed on the latest Insiders?

@rzhao271 I can reproduce it in stable (I am on Mac) Please follow these steps:

Use fresh user data directory
Open multiple VS Code windows (around 4)
Set auto detect color scheme setting to true "window.autoDetectColorScheme": true
Open System Preferences > General and toggle appearance between Light and Dark
Stable shows conflicts error and Insiders should not

Ok, it was most likely because I had that setting off, but I got the issue confirmed and verified now 🚀

I have the same issue here on Mac since 2 weeks or so.

@devatrox are you on the Insiders release? If you're on Stable, a new version with the fix should be out this week.

@rzhao271 Thanks for the info. I'm on stable

Thanks! I'm using the latest Insiders build and this seems to fixed now!

I'll chime in, too. It seems to be mostly fixed for me, but I'm still at times getting my settings.json file randomly showing as open, and edited, in my project window when I return to VS Code after leaving my computer asleep for the night. Not as bad as before but seems worth mentioning.


fix pid_suffix and fix test case

Resolve #346

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (9e07a99) 100.00% compared to head (fd5cc18) 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff            @@
##            master      #348   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines         2236      2236
=========================================
  Hits          2236      2236

Impacted Files
Coverage Δ

src/viztracer/main.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hmm, this is still not the expected behavior. If the user specifies -o output.json --pid_suffix, the output file should be output_<pid>.json. Also there could be potentially other formats in the future(html is kind of deprecated now). I think we should deal with it in VizUI.save.

Hmm, this is still not the expected behavior. If the user specifies -o output.json --pid_suffix, the output file should be output_<pid>.json. Also there could be potentially other formats in the future(html is kind of deprecated now). I think we should deal with it in VizUI.save.

Fixed it. Actually I'm not sure if a user specific -o and --pid_suffix in a commandline, what kind of result he expects.


clippy::cast-possible-truncation generates warnings

We don't normally run the rule -W clippy::cast-possible-truncation but if I try we see a few messages such as :
warning: casting u64 to usize may truncate the value on targets with 32-bit wide pointers
   --> src/lib.rs:950:13
    |
950 |             config.local_transport_params.initial_max_streams_bidi as usize,
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `-W clippy::cast-possible-truncation` implied by `-W clippy::pedantic`
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#cast_possible_truncation

warning: casting u64 to usize may truncate the value on targets with 32-bit wide pointers
   --> src/lib.rs:954:13
    |
954 |             config.local_transport_params.initial_max_streams_uni as usize,
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#cast_possible_truncation

warning: casting u64 to usize may truncate the value on targets with 32-bit wide pointers
    --> src/lib.rs:1173:13
     |
1173 |             b.get_varint()? as usize
     |             ^^^^^^^^^^^^^^^^^^^^^^^^

There's probably a lot of those messages, and in most cases they don't indicate bugs (which is why the lint is not enabled by default).
Though the first two examples you mentioned are probably bugs, so I made #122 to fix them.

Cool yeah clippy pedantic is pretty spammy and I dont think we should respect all of its moaning. I suspect some of them are from the recent 32bit changes but will assume that these changes fix possible problems.


build: default to on push change detection strategy

#552  👈
main

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

Join @davidlj95 and the rest of your teammates on  Graphite


Add eslint to catch incorrect javascript patterns

Description
Add eslint to catch potentially-problematic patterns in javascript, using https://github.com/google/eslint-config-google to follow the google js style guice

Codecov Report

Merging #2777 (e460269) into main (9333c58) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #2777   +/-   ##
=========================================
  Coverage     77.34%   77.34%
- Complexity     2106     2107    +1
=========================================
  Files           271      271
  Lines          8416     8417    +1
  Branches        567      566    -1
=========================================
+ Hits           6509     6510    +1
  Misses         1696     1696
  Partials        211      211

Impacted Files
Coverage Δ

server/app/services/role/RoleService.java
100.00% <0.00%> (ø)

server/app/modules/FeatureFlagsModule.java
100.00% <0.00%> (ø)

...app/services/question/ActiveAndDraftQuestions.java
100.00% <0.00%> (ø)

server/app/models/Version.java
76.59% <0.00%> (+1.04%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


⚠ Bofrost.at has degraded performance

In 644a6c0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 918 ms

Resolved: Bofrost.at performance has improved in a98086f after 305 days, 4 hours, 43 minutes.


DocGen improvements

This PR improves several features of our newly introduced DocGen CLI tool.
Some notable improvements and fixes:

Static comment for all auto-generated files indicating that documentation files are not to be overwritten
Updated the heading level of notes and examples when a function has multiple signatures
Indicating deprecation in navigation sidebar if a class, a type or all of the signatures of a function are deprecated
Multi-line comments will not break parameter tables

getting better and better! I will change the signatures of the other hooks

I'll merge this PR, then any changes to the signatures will be reflected in markdown files correctly.


Get back net6 support

.NET6 support is valid until November 12, 2024, more than half a year, I'm not sure this is a good idea to abandon .NET6 support in Electron.NET.
I would like to suggest making the project multitarget and support both LTS versions (.NET6 and .NET8)
dotnet tool doesn't support self-contaied tools (see https://github.com/dotnet/sdk/issues/9565), so that <PublishSelfContained>true</PublishSelfContained> can be useful only for binaries but not for dotnet tool so I decided to remove the line

The structure of CLI dotnet tool package I got after executing `dotnet pack`
.
|   ElectronNET.CLI.nuspec
|   output.txt
|   PackageIcon.png
|   [Content_Types].xml
|
+---package
|   \---services
|       \---metadata
|           \---core-properties
|                   553c89be248c4da09d1469f93f9abb2f.psmdcp
|
+---tools
|   +---net6.0
|   |   \---any
|   |           dotnet-electronize.deps.json
|   |           dotnet-electronize.dll
|   |           dotnet-electronize.pdb
|   |           dotnet-electronize.runtimeconfig.json
|   |           DotnetToolSettings.xml
|   |
|   \---net8.0
|       \---any
|               dotnet-electronize.deps.json
|               dotnet-electronize.dll
|               dotnet-electronize.pdb
|               dotnet-electronize.runtimeconfig.json
|               DotnetToolSettings.xml
|
\---_rels
        .rels

The structure of API package I got after executing dotnet pack
.
|   ElectronNET.API.nuspec
|   output.txt
|   PackageIcon.png
|   [Content_Types].xml
|
+---lib
|   +---net6.0
|   |       ElectronNET.API.dll
|   |       ElectronNET.API.xml
|   |
|   \---net8.0
|           ElectronNET.API.dll
|           ElectronNET.API.xml
|
+---package
|   \---services
|       \---metadata
|           \---core-properties
|<PHONE_NUMBER>fe4b75b8c25a49aef2d054.psmdcp
|
\---_rels
        .rels

I double checked if the packages worked correctly with my .NET6 app and .NET8 demo webapp.
Let me know if I should check something else.

No structure looks fine to me!
Let's keep it like that - thanks for checking!


Art/update level 2 lights and boss scene

updated lights in level 2 and boss scene. fixed laser blocks and laser beams in first gauntlet for level 2.

Already tested. Looks very nice! Great job!


🐛 model dump시 json mode 적용

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

Current dependencies on/for this PR:

#89
#88
#87  👈
#86
#85
main

This stack of pull requests is managed by Graphite.

Merge activity

Feb 24, 9:32 AM EST: @mingi3314 started a stack merge that includes this pull request via Graphite.


Flex psql

close #79

Added a comment. Should refrain from tf fmt to much noise in changes. Also will this model work across the other providers? Thinking the variables should be create_postgres and then possibly postgres_type where we identify what type of postgres server is being created. This could help simplify the conditional logic.

This Flexible Server is Azure specific offering that other providers don't seem to have yet, so not sure who this cuts across other IaC projects. As for switching to postgres_type I'd agree it'll be up to the user to enter a valid string to match with the type of Postgres.

Will pull from draft once it's out of preview.

Closing in lieu of https://github.com/sassoftware/viya4-iac-azure/pull/220


Update refined to 0.9.3

The 2.13.0-M4 build failed because refined 0.9.3 is only available for 2.13.0-M5.

@fthomas Yes, we're still waiting on Jawn. I'll try to get this sorted this week.

@fthomas Thanks again! I've included this commit in #1015.


Markdown processor supports TOC

We want to write our docs in markdown and have a table of content by writing something like [toc]. So readers can know what's in the page and navigate if necessary.
Acceptance criteria

[x] I can write [toc] or similar in markdown document that gets rendered as table of content of the page

Tasks

[x] use https://github.com/Oktavilla/markdown-it-table-of-contents to enable tocs

FIXED. When writing markdown use [[toc]] that will render table of content of the page. Supported levels are - 1, 2, 3, 4, 5, 6.


API not returning

It appears that the API chat endpoint does not have a timeout logic, and sometimes it stucks in a request and does not return anything for a long time.

Hi @marcelofprado, thanks for letting us know. Could you please try again? The service should be stable now.

I've just had the same issue and we are investigating. Thanks for letting us know.

Hello, i've been encountering the same issue for the past few days. Some requests seem to hang for hours without returning any results. Any insights or solutions would be greatly appreciated.

Closing this as we haven't observed this behaviour recently.