Layout/ArgumentAlignment: Align the arguments of a method call if they span more than one line.

Supported styles:
With first argument
# Standard method calls
a_relatively_long_method_call(:thing,
                              :another_thing)

# DSLs
belongs_to :thing,
           class_name: 'ThisThing',
           foreign_key: :this_thing_id
has_many :other_things,
         class_name: 'ThisOtherThing',
         foreign_key: :this_other_thing_id
validates :field,
          presence: true

With fixed indentation
# Standard method calls
a_relatively_long_method_call(:thing,
  :another_thing)

# DSLs
belongs_to :thing,
  class_name: 'ThisThing',
  foreign_key: :this_thing_id
has_many :other_things,
  class_name: 'ThisOtherThing',
  foreign_key: :this_other_thing_id
validates :field,
  presence: true

This one bugs me a lot, but honestly, I don't like either. I'm open to changing the rule, but I'd also recommend the following syntax:
a_relatively_long_method_call(
  :thing, :another_thing
)

Or, if there are a lot or arguments, or the arguments are long:
a_relatively_long_method_call(
  :a_long_argument,
  :another_long_argument,
  :a_third_long_argument
)

As far as the actual Cop though, I'd vote for "with fixed indentation". I don't like the first syntax because then you have weird looking code, and you lose a lot of real estate.
My vote is to change the Cop to "with fixed indentation", but try to follow the convention I listed above -- in my opinion, it's the best of both worlds.

Done with https://github.com/publicstrategies/rubocop-config/commit/f3fd82ae14a5f97c91764f4142a53a7f5579357e


ENH: Improve Test Coverage

This patch expands test coverage, modernizes test syntax, and prefers the use
of ITK testing macros to manual testing.  Line coverage is improved from 83.9%
to 88.6%.  Function coverage is improved from 62.7% to 80.8%.

Before patch:

After patch:

Awesome!

Very nice @DVigneault !! Thank for improving the coverage.


Any plans to continue work on this provider?

As the title says, do you have any plans to continue working on this provider? I'm really sorry that I don't know Go and can't help.
The feature that I would be most interested in is being able to create Connections in the same manner as you did for Variables.

Yes, this is used in production at work, so i am definitely maintaining it :) Connection support should be fairly straight forward to add, but before you try that path, I recommend giving the new secrets backend a try first if you can fit all your connections into a single AWS secrets manager instance.


Prune last_status_type domain

Not all legal values are actually being used.
The first step in this issue will be to get consensus from the squad and then compare that consensus to what last_status_type values are stored in the feature class.  It may be necessary to update old, rare, attributes to match the pruned domain.

Current distribution of status types:
LAST_STATUS_TYPE | KOUNT
------------------------+-------
CONSTRUCTED             |1081510
ALTERATION              |   1253
SPLIT                   |    313
MARKED FOR CONSTRUCTION |    259
INITIALIZATION          |     93
MARKED FOR DEMOLITION   |     79
MERGED                  |     77
CORRECTION              |     56
INVESTIGATE CONSTRUCTION|     49
GEOMETRY                |     17
DEMOLITION              |      9
INVESTIGATE DEMOLITION  |      3


Fish and Zsh completion

Hello, it would be nice to have also Fish and Zsh completion scripts

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTBTOOL-724


The results on Semantickitti testset are lower than mentioned in the paper

I train the training set and validation set of semanticKITTI together, then I upload the test result to Codalab. But the mean IOU is 69.4, It is much lower than the 74.8mIOU showed in the paper. The gap is too large. I have chosen the model_last.pth. How did you choose the model during testing? Did you do any other processing during the testing?
Thank you！

I had the similiar result with u ,and my several classes' acc is nearly 0 ,what about u

I had the similiar result with u ,and my several classes' acc is nearly 0 ,what about u

Each class I measured has a corresponding IOU, but the mean IOU is lower than claimed in the paper

Could u please show me your results and environment by email<EMAIL_ADDRESS>

@WYRTDCQ  Hi, please refer to https://github.com/dvlab-research/SphereFormer/issues/1.

@illuosion hi,I have encountered the same problem as you. The miou of class7 and class11 is very low (no more than 0.01). Do you know why this is now


Crash and restart hosts in a runtime

My goal is to crash and restart hosts randomly according to some distribution. This way I can see the long-running behavior of my code under duress.
Currently, this looks like
loop {
  sim.step();
  if sim.elapsed() > next_crash_time {
    sim.crash(host);
    next_crash_time = ...
  }
}

However, what would be really nice is if I could crash hosts in a runtime, like this:
loop {
    let next_crash_in = ...;
    sleep(next_crash_in).await;
    sim.crash(host);
    let repair_in = ...;
    // Eventually restart the host.
    spawn(async move {
        sleep(restart_in).await;
        warn!("Restarting node {}", node_to_crash);
        sim.bounce(node_to_crash);
    });
}

I tried to do this in a client, but it doesn't work because client already holds the &mut sim, and I need a &mut sim to crash a host. This means the future can't be Send, so the program doesn't compile.
Is it possible to do this? If not perhaps we could:

expose a free function, like how elapsed() and hold() work
expose a runtime so we can inject tasks into the sim

Also, is this a good first issue? If so, I wouldn't mind taking this issue if I could get some guidance on how to start

I can't tell what the difference is between the two examples. The same amount of time would be elapsing in between each event. It's structured like this due to how the state is managed and mutated. I don't see a good way to do this right now, but you are welcome to take a look and propose one.


Create dataset loader for SPAMID-PAIR

Dataloader name: spamid-pair/spamid-pair.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?spamid-pair

Dataset
spamid-pair

Description
SPAMID-PAIR is data post-comment pairs collected from 13 selected Indonesian public figures (artists) / public accounts with more than 15 million followers and categorized as famous artists. It was collected from Instagram using an online tool and Selenium. Two persons labeled all pair data as an expert in a total of 72874 data. The data contains Unicode text (UTF-8) and emojis scrapped in posts and comments without account profile information.

Subsets
-

Languages
ind

Tasks
Text Classification

License
Creative Commons Attribution 4.0 (cc-by-4.0)

Homepage
https://data.mendeley.com/datasets/fj5pbdf95t/1

HF URL
-

Paper URL
https://dx.doi.org/10.14569/IJACSA.2022.0131110

#self-assign


improvementSupport identical column name in different index.

For each column stats meta in tableStatsMeta, add the index name as key along with column name, so we can tell columns with identical names, and trigger auto analyze after a new mv created.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run external


Fix ci actions

Thanks for this @LanderU, with this, shall I submit the CI PR to ros-planning/moveit2 master? I will be asking for your help to review it

@vmayoral, this is HRIM repo.

My bad, you're right. Nevertheless, it still applies, I'll be asking for your help if that's ok.

I'll be asking for your help if that's ok.

Sure!

https://github.com/AcutronicRobotics/moveit2/issues/27
thanks!


How to select the first row in the grid programmatically ?

I want to select and highlight the selection of the first row in the grid programmatically.  Is there any way to achieve this?

What about grid.select(row, true) method, is something your are looking for ?

Thanks ! It helps.


How to work with nginx?

Hello,
Socket.io works well when requested directly with the example:
const cluster = require("cluster");
const http = require("http");
const { Server } = require("socket.io");
const numCPUs = require("os").cpus().length;
const { setupMaster, setupWorker } = require("@socket.io/sticky");
const { createAdapter, setupPrimary } = require("@socket.io/cluster-adapter");

if (cluster.isMaster) {
  console.log(`Master ${process.pid} is running`);

  const httpServer = http.createServer();

  setupMaster(httpServer, {
    loadBalancingMethod: "least-connection", // either "random", "round-robin" or "least-connection"
  });

  setupPrimary();

  httpServer.listen(3000);

  for (let i = 0; i < numCPUs; i++) {
    cluster.fork();
  }

  cluster.on("exit", (worker) => {
    console.log(`Worker ${worker.process.pid} died`);
    cluster.fork();
  });
} else {
  console.log(`Worker ${process.pid} started`);

  const httpServer = http.createServer();
  const io = new Server(httpServer);
  io.adapter(createAdapter());
  setupWorker(io);

  io.on("connection", (socket) => {
    /* ... */
  });
}

but once reversed by nginx with followed config:
http {
  server {
    listen 80;
    root /var/www/html;

    location / {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $host;

      proxy_pass http://ip:3000;

      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }
  }
}

It failed with 404 response:

How can I proxy socket.io-sticky with cluster module properly

Hello. I have the same issue while testing polling transport only. My implementation is almost the same as yours, but I'm using the Redis adapter instead of the cluster adapter. I tried different implementations, but the issue seems to come from this package directly (probably related to keep-alive header?).


ZRANGEBYLEX and ZREVRANGEBYLEX commands support

Hi. I added support to 2 new commands
Also stable redis-rb doesn't support all these features well (see https://github.com/redis/redis-rb/pull/492)
Comments are welcome

Thanks!


Do we follow googlefonts.github.io/python recommendations?

I propose to update this repo to conform to https://googlefonts.github.io/python if there are any places it deviates, or, change those recommendations if there are good reasons not to.
(Tagging as a quick issue to first confirm conformance to that checklist)

yes, after quickly glancing over the list, I can confirm we follow most of that. We used to use tox, but that was removed recently by @miguelsousa and I decided to do the same because I was also not using it. As https://googlefonts.github.io/python has "TODO" and "Why tox?" when discussing tox, I think it is fine. Maybe it is actually not essential to use it. Or would need stronger explanation of why we should always adopt it.
Also, very recently we started using black.

"Fail CI when pytype fails."

That's something we still don't do.

"extras_require specifies development-only dependencies under the key called dev"

We recently improved a lot the way dependencies are handled and we're using many vendor-specific extras. It would be very simple to add the dev one as well. And I'd put "pytest" in it, which would be enough for running code-tests locally during development (which is also why tox was suggested, I guess)

@felipesanches

As https://googlefonts.github.io/python has "TODO" and "Why tox?" when discussing tox, I think it is fine. Maybe it is actually not essential to use it. Or would need stronger explanation of why we should always adopt it.

Running tox locally can help cleaning up PR before they are run with CI.

Running tox locally can help cleaning up PR before they are run with CI.

I often run pytest -x tests locally.

I often run pytest -x tests locally.

That’s probably good enough for testing before pushing commits.
Tox can be used to run it in different python versions but not on different platforms. So to be thorough running it on CI is better anyway. I’ɗ say it’s fine not to use tox locally.


fix node label issue in cluster-configuration start & stop

Coverage remained the same at 33.933% when pulling 0148099b72b1196981ee3685eaff06d296c74073 on suiguoxin:nodes-label into a5f5e1c22e45c63731356bbb092a3a2668f9d947 on microsoft:master.

Coverage remained the same at 33.933% when pulling 0148099b72b1196981ee3685eaff06d296c74073 on suiguoxin:nodes-label into a5f5e1c22e45c63731356bbb092a3a2668f9d947 on microsoft:master.


Please add runkit7 to the enable-able php modules

ISSUE TYPE

Feature request

SUMMARY
Please add runkit7 to the enable-able php modules.
https://www.php.net/manual/en/book.runkit7.php
Goal
Currently, I have to install it by hand every time I restart the php container. It would be great if it could be automatic.
Thank you!

Did you noticed that there is not yet a stable release since the begining of its development.
Personnaly I'm not agree to have it included in any php-fpm docker images of the devilbox.

Alternative will be to include uopz extension (https://www.php.net/manual/en/book.uopz.php) that already have stable releases.
Or just check the project https://github.com/badoo/soft-mocks if it match your needs @ultrablue
Personnaly I don't think it's a PHP development best practice to allow to modify functions on fly but I admit it just be allowed to write unit tests and mock some of internal PHP functions like time()

@ultrablue If you install runkit7 yourself on the PHP image, it will persist as long as you only "stop" the docker container.
See difference between docker-compose stop and docker-compose down

Hi, @llaville  and @cytopia:
Thanks for the response. @llaville good points. However, I'm stuck with runkit7 from a legacy application.
@cytopia thanks for the tip. I have been using down. :/

If I wanted to modify Devilbox myself, how would I go about doing that?
Thanks again! Devilbox is the best.

Hello @ultrablue
I'm working on a new refactoring (again) of cytopia project https://github.com/devilbox/docker-php-fpm.
My first approach was to fixed some issues before cytopia finally fixed it in official version by my fork still available at https://github.com/llaville/docker-php-fpm/tree/software_enabled_refactoring
and added new extensions. https://github.com/devilbox/docker-php-fpm/issues/199
But I must admit that even if it's now easy for me (after a learning stage) to modify docker-php-pfm images, it could be not so easy for a beginner !
My new work is to simplify building of docker-php-fpm mods image that define and include PHP modules.
This work used the open source project https://github.com/mlocati/docker-php-extension-installer that have lof of PHP extensions supported https://github.com/mlocati/docker-php-extension-installer#supported-php-extensions
It's almost ready and I should present it later this week.

Hi, @llaville:
Oh, cool, thanks.
I appreciate your efforts on this. If there's anything I can do to be of assistance, let me know.
Thanks!

@ultrablue review my new report https://github.com/devilbox/docker-php-fpm/issues/215 and give me your feedbacks are welcome

Instead of runkit7, @ultrablue consider to use https://pecl.php.net/package/uopz extension that come with a PHP 8 compatible release (7.0.0) since yesterday

I have tried uopz, however some php and pecl commands were failing after it had been installed:
Build process completed successfully
Installing '/usr/local/lib/php/extensions/no-debug-non-zts-20200930/uopz.so'
install ok: channel://pecl.php.net/uopz-7.1.1
configuration option "php_ini" is not set to php.ini location
You should add "extension=uopz.so" to php.ini
+ docker-php-ext-enable uopz
+ true
Removing intermediate container 89b28eadd0a8
 ---> 1d03aabd59d6
Step 56/65 : RUN set -eux       && pecl install uploadprogress  && docker-php-ext-enable uploadprogress         && true
 ---> Running in bbbabcae7c74
+ pecl install uploadprogress
Segmentation fault (core dumped)

The only version I was able to install it without issues was PHP 8.1

@cytopia I've let down support for uopz extension, because I noticed like you that, side effects with others extensions.
I do not recommend to add it.


nonexist file included in searching results ?

I really love leaderf.
$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
Included patches: 1-1689
Extra patches: 8.0.0056
Modified by<EMAIL_ADDRESS>
Compiled by<EMAIL_ADDRESS>
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +tag_binary
+arabic          +file_in_path    +mouse_sgr       +tag_old_static
+autocmd         +find_in_path    -mouse_sysmouse  -tag_any_white
-balloon_eval    +float           +mouse_urxvt     -tcl
-browse          +folding         +mouse_xterm     +terminfo
++builtin_terms  -footer          +multi_byte      +termresponse
+byte_offset     +fork()          +multi_lang      +textobjects
+channel         +gettext         -mzscheme        +timers
+cindent         -hangul_input    +netbeans_intg   +title
-clientserver    +iconv           +packages        -toolbar
-clipboard       +insert_expand   +path_extra      +user_commands
+cmdline_compl   +job             -perl            +vertsplit
+cmdline_hist    +jumplist        +persistent_undo +virtualedit
+cmdline_info    +keymap          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       -python          +vreplace
+cscope          +lispindent      +python3         +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      -lua             +rightleft       +writebackup
+diff            +menu            -ruby            -X11
+digraphs        +mksession       +scrollbind      -xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xsmp
+emacs_tags      -mouseshape      +startuptime     -xterm_clipboard
+eval            +mouse_dec       +statusline      -xterm_save
+ex_extra        +mouse_gpm       -sun_workshop    -xpm
+extra_search    -mouse_jsbterm   +syntax
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=f
ormat-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim        -lm -ltinfo -l
nsl  -lselinux  -lacl -lattr -lgpm -ldl     -L/usr/lib/python3.5/config-3.5m-x86_64-linux-gnu -lpython3.5m -lpthread -l
dl -lutil -lm

:echo has("python3")
1

:py3 print(sys.version):
3.5.2 (default, Nov 23 2017, 16:37:01)
[GCC 5.4.0 20160609]

Operating system:

[x]  Linux

Configurations related to LeaderF in vimrc:

let g:Lf_RootMarkers = ['.git']
let g:Lf_WorkingDirectoryMode = 'Ac'
let g:Lf_DefaultMode = 'FullPath'

let g:Lf_WildIgnore = {
  \ 'dir': ['.git', 'build'],
  \ 'file': ['*.sw?','~$*','*.bak','*.o','*.so','*.py[co]']
  \}

nnoremap ;f :LeaderfFunction<CR>

Question
rename testing.c to test.c in a project, and quit vim. I search test.c file using fuzzy full-path when re-entering the project in vim, and see the result contains testing.c file which does not exists any more. why would this happened ?

You can refresh the result using <F5>.
Also refer to issue #161 to get more information.

@Yggdroot I add the following settings into my .vimrc, but not work properly. I can still see the deleted files in searching results.
let g:Lf_UseCache = 0
let g:Lf_UseMemoryCache = 0

The above settings mean leaderf will auto refresh when starts every time.
but it does not work in my vim. I try <F5> to refresh the cache, but failed.
sorry to bother you, any advice ?

You should press <F5> after you have launched LeaderF.
I don't know why
let g:Lf_UseCache = 0
let g:Lf_UseMemoryCache = 0

does not work, did you restart vim after adding them into vimrc?

I restart vim, but nothing changes.
Entering LeaderF, and press <F5> does not work even though I set the
let g:Lf_UseCache = 0
let g:Lf_UseMemoryCache = 0

a little weird.

What is the output of :echo g:Lf_Debug_Cmd?

your said is right. let g:Lf_UseCache = 0 is set, and I delete the item, nothing changes.
:echo g:Lf_Debug_Cmd, the output is:
git ls-files && git ls-files --others --exclude-standard

Got it. the root cuase is that git ls-files && git ls-files --others --exclude-standard can still list the deleted files even though it does not read the cache.
You can set let g:Lf_UseVersionControlTool = 0 so that LeaderF use "rg"/"pt"/"ag"/"find" instead to index the files.

nice job, thanks a lot.


Allow svg-based images

Describe the feature you'd like
In addition to the existing support of adding pixel-based images, it might be good to allow the user to include svg-files in a page.
Describe the benefits this feature would bring to BookStack users
Especially for vector-based graphics and diagrams, exporting them to raster decreases quality and sharpness, especially when scaling is involved. This gets even more important since, as explained in #1108 , it does not seem possible to upload high-resolution images and scaling is used quite extensively and unavoidable in some cases. Allowing SVG-based images would help a lot here.
Additional context
Partially related to #1108

Thanks @nmehlei for your request.
Support for uploading SVG images is already open under #1103. Therefore I'm going to close this request to cut down on duplicates.


Fix Drop impl for OwnedHandle

Thank you!

@yah01 You need to sign all commits and then we can merge it.

@yah01 You need to sign all commits and then we can merge it.

Just done that, thanks!


Add a privacy manifest in realm-dart for iOS

What happened?
We recently became aware that, according to the new Apple privacy regulations, third-party SDKs will also be required to provide a Privacy Manifest  , Pls help us to add this
Repro steps
I can see its done RealmSwift, Could you please provide fix for Flutter
Version
1622
What Atlas Services are you using?
Local Database only
What type of application is this?
Flutter Application
Client OS and version
iOS and Android
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response

This is a duplicate of https://github.com/realm/realm-dart/issues/1551.


spotifyd: 0.2.16 -> 0.2.18

Motivation for this change
Things done

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

[X] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Perhaps you could add yourself as maintainer
sure, I'll do it in the next version bump :)


fix throws "Value is undefined" when hovering mouse over the chart

Type of PR: bugfix
PR checklist:

[+] Addresses an existing issue: fixes #1499

Overview of change:
This fix ignores the bug because the events are asynchronous and when a series is deleted, we can't know about it. We probably need to fix the Click/DblClick events as well, but simultaneous deletion of a series and a click is very rare.

@nikepan Thanks for submitting your PR.
I haven't been able to reproduce the initial bug but based on the error in the console seen within the video I think that this PR: https://github.com/tradingview/lightweight-charts/pull/1529 would potentially fix the issue. Could you please check if the other PR does indeed fix your issue?

@nikepan Thanks for submitting your PR.
I haven't been able to reproduce the initial bug but based on the error in the console seen within the video I think that this PR: #1529 would potentially fix the issue. Could you please check if the other PR does indeed fix your issue?

Yes. Your fix works fine. Thank you!


New EF Hub + toc, docfx and breadcrumb toc updates

I forgot to create a tracking issue for this work item I already fixed with a PR.  So creating and closing as fixed at the same time.
Fixed with PR #2279
Updates:

Create a new Hub page for Entity Framework/Entity Framework Core using the latest - docs.microsoft.com design guidelines
Update breadcrumbs and links to the old Hub design.

We reviewed data related to these primary items (and others) to determine the Hub organization:

What are new and established developers the most interested in?
Which content are developers bouncing out of too quickly or clicking through too much, likely indicating they didn’t find what they were looking for.
What content is doing well and what may need some help.

Fixed with PR #2279


Improve Call[WithContext] expansion for the generated enum type

Instead of using IntoOpt and making use of the Call[WithContext] impl of the converted-to generated opt type the macro now generates a match based impl for the enum type own its own. This should be more intuitive for readability as well as more idiomatic Rust code and likely also more efficient.

Codecov Report

Merging #2 (a6e7b88) into main (b9cea67) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
- Coverage   15.48%   15.39%   -0.10%
==========================================
  Files          13       13
  Lines        1937     1949      +12
==========================================
  Hits          300      300
- Misses       1637     1649      +12

Impacted Files
Coverage Δ

macro/src/expand.rs
0.00% <0.00%> (ø)

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


[BUG]SfSteps

Describe the bug
After performing v-if on one of the steps, which is initially true and changes to false, this step does not disappear from view and still occurs.
It is possible that it is copied to 'data' so maybe it is not refreshed later.
How to reproduce
Steps to reproduce the behavior:

Give about 3 steps
On the first one give v-if where the flag points to true
Change the flag
Step remains visible

Expected
A request for verification and a fix for this in 0.6.5 fix if possible
Actual behavior
It breaks the workflow in checkout

@akrajna Will you please describe more this issue?
I just check with the version 0.7.18 & not able to reproduce the issue. Might be fixed in the latest version.

fixed in the previous version


Not able to run project locally

reference
reference

The project currently not supportable above /later node version 14.16.0, I suggest to use node version v14.16.0


FAQ - Is there a tool available for unit testing Harness rego policie…

…s before deployment?
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[X] Feature
[ ] Maintenance/Chore

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Overhaul of the server certificate verification

Current situation
I am in the middle of my work, aiming to rewrite the server certificate verification by delegating most work to the SSL library. In my opinion, the current handling has these issues.

No hostname verification
As pointed out in #914 , SE verifies the certificate by either comparing it to a saved one or looking for its issuer CA in the trust list. It didn't verify the hostname. That is to say, any certificate issued by the same CA will pass the verification.

Incomplete trust evaluation
Since we only look for the immediate issuer in the trust list, any certificate will fail if there is some intermediary CA that is not added to the trust list. In other words, we only verify the leaf certificate instead of the whole chain.

Ignoring the default trust store
SSL library ships with a default trust store including trustworthy root CAs. It's a good idea to trust that (as an option) so that verifying certificates issued by public CAs can be done out of the box. It can be further improved to utilize the Windows certificate store.

Typical scenarios

Server with self-signed certificate
This is the default setting. Now we will be able to verify the hostname as well.

Server with public certificate (such as Let's Encrypt)
With hostname verification and the use of the default trust store we can perform modern TLS validation with zero configuration.

Options to be added
The existing Verify server certificate option will still serve as the general switch that enables / disables the entire verification.
On top of that, I plan to add these options in the client / cascade config.

Trust CAs from the default store
Prompt if verification fails
This will give user the final say on whether the connection should continue. It's only useful on Windows. On other platforms if it fails, it fails dead.

Options to be removed

Retry on untrusted certificates
This option was added in #335 . We already have the retry setting. But in two situations the retry is disabled. Untrusted certificate is one of them. (The other is the failure of a secure device)
Since trust evaluation depends on the server configuration and thus is not an internal thing, I think the check should be removed. That is to say, untrusted certificates should use the same retry setting as other errors. If the client is set to retry endless, it should retry in trust failure as well.

I am planning to show these options in the client manager so I want only necessary ones due to the limited space.
I am about to finish the first draft by this week. Comments and suggestions are welcome.

Closing in favor of #1522


Google Maps (and the app) crashes on Android after zooming in/out

Description of issue
It seems that Google maps interactions (zoom in/out) causes the app to crash
Expected behaviour
The app doesn't crash if you zoom in and out.
Steps to reproduce
Open the parade tab and interact with the map a bit - zoom in and out etc and notice it crashes.
OS / Browser / Device model
Tested on Samsung 8 and Pixel 2 (probably applies to all android)
Screenshots
If it's a visual bug, please provide screenshots or screen captures.

https://github.com/redbadger/pride-london-app/issues/453

I may have found a fix

#473 may fix this

This is now in master. Once released we should no longer see bugsnag errors like these:
#418
#446
#453
#458
#459
#460
#461
#462
#463
#467
#468
#472

In production for Android and no longer crashing 👍


Theme aware rcparams

Can we read the theme from within our python script, and in turn set rcParams to match?

I've been working on this issue and I found this is quite heavy and challenging problem... I mean, this is more difficult than how it looks :(.
Here is my report on this problem. I hope this helps you guys.
What I have done so far
Searching on Google
I found the official document of the theme, which is not helpful for our purpose.
We can understand how to make a custom theme but we never know how to automatically detect the theme.
Searching on community forum of Streamlit
I found two people who want to do the exactly same thing.

This one avoided the problem.
This one gave it up.
When I found these I was glad but soon I realized these are not what I expected.

Searching on Issue of Streamlit GitHub
I have good news and bad news. The good news is, finally, I found something useful :). The bad news is that I realized that we cannot solve this problem easily :(.
I found two helpful posts.

This post is simply not popular. I have no idea why. Not been solved yet.
On the contrary, this post is super popular (again I don't know why). We can see that there is no function for our purpose for now. Because it does not have related information in the backend. Also not been solved yet.

Possible solutions I have (and imagine)
Using Plotly (cool)
Thankfully and mysteriously, st.plotly_chart can detect the theme. One possible suggestion is creating all new figures with Plotly. (However, as all of you know, I am a big fan of Matplotlib and I can implement what I want to do faster with it. Therefore, I continue to use my dearest Matplotlib XD)
I checked the source code but I cannot understand how it works. Absolutely, it has a connection with the frontend (you know graphs of Plotly is interactive which means they somehow get information from the frontend).
Only one mode (uncool)
I found the dark theme of Matplotlib. Thus, if we fix the theme of either "light
or "dark", we can make sophisticated pages but when users change the theme the pages become not well-designed.
Waiting for a newer version of Streamlit (cool, cool, cool)
I guess, at some point, developers will implement some features to solve this problem. As you know, the development pace of Streamlit is fast, so we can fairly expect to solve this problem by just waiting ;).
Conclusion

I gathered all information regarding this problem as far as I can.
My intensive research revealed that, for now, due to technical reasons, solving this problem is not easy but we still have ad-hoc solutions. We can expect this problem can be solved easily in the near future.

I would like to add one more solution I recently noticed.
Using Matplotlib with a user-defined theme
As I mentioned before, there is a dark theme for Matplotlib. Depending on the user-defined theme, we can switch to the dark theme. I get a user-defined theme from st.radio and use an if sentence. An example is below.
    theme = st.radio("Choose theme", ("Light", "Dark"), horizontal=True)

    if theme=="Light":
        plt.rcdefaults()
    else:
        plt.style.use('dark_background')

By using this, we can avoid migrating from Matplotlib to Plotly. You know, it is too much to remake all figures we already have with Plotly.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1500 in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @MagisterLeon, @BSN4, @appsplash99, @DavidDomkar, @bonham000, @Aureom, @ziloka, @moon-hai, @kespinola, @Mohammedaltamemy, @CMEONE, @waldstation, @Beacon-Heart, @rajraj, @xnull, @aureljpeg, @lukemoderwell, @legua25, @xiaofeng98, @lottamus, @sumanthyalaga, @MrCx0810, @DavidNix, @starbt, @brngklp, @theemack, @richin13, @ccampbell, @fenghaojiang, @1dad-io, @gmarat, @NeutronStarPRO, @MilesDavis23, @yezi1108, @JohnCido, @wiredhikari, @guillermoap, @rideddy84, @pc3b3r, @haumanto, @nuarc, @t2krew, @WebsterLi, @cfl0ws, @cyan92128505, @wulianonline, @shkstar, @SargeKhan, @MOZGIII, @luohaha


[Fix] Revert platform_automation_msgs

Status
DEVELOPMENT
Description
platform_automation_msgs is pinned to 51ceed at #1420.
e71cdf0a74c94a871424b5e39e6b231d4d4d2432 accidentally changes the submodule revision.
This pull request reverts it.
Related PRs

branch
PR

feature/beyond_pixel
#1473

@kfunaoka thanks!


Fixed typo and handle empty set of instances

A couple small fixes for the GCE provider.

Coverage decreased (-13.2%) to 52.237% when pulling<PHONE_NUMBER>9cab3a2b5c5cf4b3afb601bda2fc80 on machristie:gce-fixes into 8a075e3d15e600122bb848fe1627056f2c38cc0e on gvlproject:gce.

Thanks. This also fixes one of the bugs reported in #32.


steps to do

can you please help me on how to use it idk what to do

im really a noob could please explain exactly how i can do it im not really geeky


No such device exception seen while running install.sh on Ubuntu 18.04

Seeing following error while running Stenographer install.sh
Nov 20 07:50:43 ip-172-31-18-102 stenographer[25641]: 2019-11-20T07:50:43.528685Z T:225257 [stenotype.cc:606] CHECK(SUCCEEDED(__check_success_error__)) builder.Bind(flag_iface, &v3): No such device#012ABORTABORTABORT
Nov 20 07:50:43 ip-172-31-18-102 stenographer[25641]: /usr/bin/stenotype(+0x70b0) [0x55b4096760b0]#012/usr/bin/stenotype(+0x2219a) [0x55b40969119a]#012/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f7b20ed0b97]#012/usr/bin/stenotype(+0x45fa) [0x55b4096735fa]
Nov 20 07:50:43 ip-172-31-18-102 stenographer[25641]: 2019/11/20 07:50:43 Stenotype stopped after 744.78279ms: stenotype wait failed: signal: aborted (core dumped)
Nov 20 07:50:43 ip-172-31-18-102 stenographer[25641]: 2019/11/20 07:50:43 Stenotype ran for too little time, crashing to avoid stenotype crash loop

Here is how my config file looks -
{
  "Threads": [
    { "PacketsDirectory": "/etc/stenographer/packets"
    , "IndexDirectory": "/etc/stenographer/index"
    }
  ]
  , "StenotypePath": "/usr/bin/stenotype"
  , "Interface": "eth0"
  , "Port": 1234
  , "Host": "<IP_ADDRESS>"
  , "Flags": ["-v"]
  , "CertPath": "/etc/stenographer/certs"
}

Resolved by changing the Interface from eth0 to ens3
{
  "Threads": [
    { "PacketsDirectory": "/etc/stenographer/packets"
    , "IndexDirectory": "/etc/stenographer/index"
    }
  ]
  , "StenotypePath": "/usr/bin/stenotype"
  , "Interface": "ens3"
  , "Port":8000
  , "Host": "<IP_ADDRESS>"
  , "Flags": ["-v"]
  , "CertPath": "/etc/stenographer/certs"
}


fix: update ru translations to remove English language

Description
I deleted the duplication of the English translation in brackets, leaving only the Russian translation, as in all other languages. The problem was that the text overflowed in the buttons, taking up a lot of space
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

@opimand - do you mind removing any remaining English translations that sit next to the Russian translation, please? Keeps it consistent. Thanks.


dickssportinggoods.com blocked (Unclear why)

Match found in https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts:
dickssportinggoods.com
This common shopping website is blocked. The metrics.dickssportinggoods.com is also blocked (appropriate) but it seems strange Dick's sporting goods main site is also. Please remove from blacklist. Thanks!

Ping Mitchell @mitchellkrogza can you look into this for us?  Thanks!

Thanks for alert @StevenBlack @chado99 indeed one of the very old false positives from early on will be removed this morning in commit


add characterLimit option

Fix #3

@PauloGoncalvesBH can you try this PR with uses: guilhem/rss-issues-action@27966e7

My third and final suggestion is to complement the README with this new option 😅
jobs:
  gke-release:
    runs-on: ubuntu-latest
    steps:
-     - uses<EMAIL_ADDRESS>+     - uses: guilhem/rss-issues-action@3
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          feed: "https://cloud.google.com/feeds/kubernetes-engine-release-notes.xml"
+         characterLimit: "255"
          prefix: "[GKE]"
          dry-run: "false"
          lastTime: "92h"
          labels: "liens/Kubernetes"

You can test it with branch 3 ;)

I really liked the change, it's great 🎉


[core]java.lang.NoClassDefFoundError: ch/qos/logback/core/joran/spi/JoranException

Checks before report

[x] check latest unstable build (maybe issue already fixed)
[x] search existing issues by exception message
(for example JadxRuntimeException: Can't find immediate dominator for block)
[x] check Troubleshooting Q&A section on wiki

Describe error
can not run the jadx-gui and jadx, and when i tried to unzip logback-core jar file, i got this:
> unzip logback-core-1.2.3.jar
Archive:  logback-core-1.2.3.jar
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of logback-core-1.2.3.jar or
        logback-core-1.2.3.jar.zip, and cannot find logback-core-1.2.3.jar.ZIP, period.

provide full name of method or class with error
provide full java stacktrace

Failed to instantiate SLF4J LoggerFactory
Reported exception:
java.lang.NoClassDefFoundError: ch/qos/logback/core/joran/spi/JoranException
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at jadx.gui.JadxGUI.(JadxGUI.java:15)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.core.joran.spi.JoranException
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 6 more
Exception in thread "main" java.lang.NoClassDefFoundError: ch/qos/logback/core/joran/spi/JoranException
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at jadx.gui.JadxGUI.(JadxGUI.java:15)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.core.joran.spi.JoranException
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 6 more

Note: no need to copy method fallback code (commented pseudocode)

attach or provide link to apk file (double check apk version)
Note: GitHub don't allow attach files with .apk extension, but you can change extension by adding .zip at the end :)

I am sorry but I don't see the connection between your problem unzipping a defect logback-core-1.2.3.jar and jadx. For running jadx you don't need to do anything with logback. Just download jadx, unzip the downloaded file and run jadx.

@ljsalm089 I think redownload jadx bundle will help, if not please let us know.

@skylot  it works after i redownload it, thx!


Request textDocument/completion failed.

create new ts file or new tsx file,sometimes volar will crash

Can you reproduce this problem in https://github.com/johnsoncodehk/volar-starter?

Duplicate of #1885


Let's make the server actions in account-actions.tsx work properly (version 3).

TODO:

Handle errors everywhere.

Figure out if I should delete the sessionID cookie whenever Django sends a 401 response.
Figure out why a 401 error on initial render is causing the page to not display.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Implement new backend views.
Handle !response.ok everywhere.
Get signOut to delete all cookies.
Figure out if I should delete the sessionID cookie whenever Django sends a 401 response.
Figure out why a 401 error on initial render is causing the page to not display.
Create Delete Account button.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:
Implement new backend views.
Handle !response.ok everywhere.
Get signOut to delete all cookies.
Figure out if I should delete the sessionID cookie whenever Django sends a 401 response.
Figure out why a 401 error on initial render is causing the page to not display.
Create Delete Account button and associated warning dialog.
Test everything!
TODO for future branches:
Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Implement new backend views.
Make account/ pages use client components for error displays.
Display errors in account/ pages.
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Get signOut, deleteAccount to delete all cookies.
Figure out why a 401 error on initial render is causing the page to not display.
Create a warning dialog for the Delete Account button.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages.
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Figure out why a 401 error on initial render is causing the page to not display.
Create a warning dialog for the Delete Account button.
Test everything!
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages.
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Figure out why a 401 error on initial render is causing the page to not display.
Create a warning dialog for the Delete Account button.
Test everything!
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

Example response:
backend-1   | INFO:     <IP_ADDRESS>:53674 - "GET /users/authenticated HTTP/1.1" 200 OK
backend-1   | INFO:     <IP_ADDRESS>:59244 - "POST /users/create-account HTTP/1.1" 201 Created
backend-1   | INFO:     <IP_ADDRESS>:59244 - "GET /users/authenticated HTTP/1.1" 200 OK
backend-1   | INFO:     <IP_ADDRESS>:59250 - "GET /users/authenticated HTTP/1.1" 200 OK
backend-1   | INFO:     <IP_ADDRESS>:59254 - "POST /users/sign-out HTTP/1.1" 200 OK
backend-1   | INFO:     <IP_ADDRESS>:59254 - "GET /users/authenticated HTTP/1.1" 200 OK
frontend-1  | tA [Error]: Cookies can only be modified in a Server Action or Route Handler. Read more: https://nextjs.org/docs/app/api-reference/functions/cookies#cookiessetname-value-options
frontend-1  |     at Proxy.callable (/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:13:12752)
frontend-1  |     at o (/.next/server/chunks/585.js:1:9509)
frontend-1  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
backend-1   | INFO:     <IP_ADDRESS>:59262 - "GET /users/authenticated HTTP/1.1" 200 OK
frontend-1  | tA [Error]: Cookies can only be modified in a Server Action or Route Handler. Read more: https://nextjs.org/docs/app/api-reference/functions/cookies#cookiessetname-value-options
frontend-1  |     at Proxy.callable (/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:13:12752)
frontend-1  |     at o (/.next/server/chunks/585.js:1:9509)
frontend-1  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Apparently you can't call a Server Action from a server-rendered component? Okay, time for some changes...

TODO:

Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages.
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Figure out why a 401 error on initial render is causing the page to not display.
Create a warning dialog for the Delete Account button.
Test everything!
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Fix bug where Account doesn't update authentication state correctly.
Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages (maybe using .bind to attach setError functions?).
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Figure out why a 401 error on initial render is causing the page to not display.
Create a warning dialog for the Delete Account button.
Test everything!
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

At the expense of Account not updating correctly, I think I've fixed the "Cookies can only be modified in a Server Action or Route Handler" bug.

TODO:

Fix bug where Account doesn't update authentication state correctly.
Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages (maybe using .bind to attach setError functions?).
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Handle !response.ok everywhere.
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Make sure that all updates to fetched data either occur on page changes or with manual re-fetching.
Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages (maybe using .bind to attach setError functions?).
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

Oh, I just realized: since isAuthenticated doesn't return a 401 error, deleting sessionid cookies on 401 returns won't exactly delete sessionid cookies whenever we know that they should be deleted.

Okay, here's the plan:
There are three pieces of information that I need to worry about staying updated for account / homepage purposes: the authentication state as needed in AccountButton, the debate name as needed in DebateName, and the username/email as needed in the Change Account page.
For the authentication state of AccountButton, there are five ways it should change: during sign up, during account creation, during sign out, during account deletion, and from any backend responses that indicate that the user is signed out. The first four ways all involve page redirects when successful, and since AccountButton lives inside a template it will refresh accordingly (CONSTRAINT: ALL FOUR OF THESE ACTIONS MUST HAVE REDIRECTS OR REVALIDATES!). As for backend responses, there are two sub-cases: isAuthenticated and everything else. isAuthenticated gets called by AccountButton itself, and so long as isAuthenticated only gets called by AccountButton, we're safe (CONSTRAINT: isAuthenticated CAN ONLY BE CALLED BY AccountButton AND THE AUTHORIZATION VIEW SHOULD ONLY BE CALLED BY isAuthenticated!). As for everything else, every other action that checks for authentication should return a 401 response when the user is not authenticated (CONSTRAINT: ALL OTHER VIEWS THAT RETURN INFORMATION ABOUT USER AUTHENTICATION SHOULD DO SO BY RETURNING 401). Then the fetchWrapper function can check for 401 responses and redirect to the sign-in page automatically, hence refreshing AccountButton (CONSTRAINT: fetchWrapper MUST REDIRECT / REVALIDATE WHEN GETTING A 401 STATUS). That should cover everything.
For the debate name, that can only get changed when in the debates view, so it will only need to be checked on page redirects

TODO:

Implement the constraints in the big comment above.
Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors in account/ pages (maybe using .bind to attach setError functions?).
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.
Test everything!

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

I'm encountering a bizarre bug where changing the password (not the username or email) will automatically delete the sessionid cookie. I'm not getting a 401 response either.

TODO:
Implement the authentication-state constraints in the big comment above.
Implement the username-email-state constraints in the big comment above.
Make sure I never call a server action from a server-rendered component.
Remove any 'use server' commands that turn out to be unnecessary.
Have fetchWrapper return a response object with an error code and message rather than throwing errors. Alternatively, have fetchWrapper either return a string error message or the response data.
Make account/ pages use client components for error displays.
Display errors (including from submitSignInForm parsing) in account/ pages (maybe using .bind to attach setError functions?).
Make fetchWrapper automatically delete the sessionid cookie if the response status is 401.
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.
Test everything!
TODO for future branches:
Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO (INCOMPLETE):
Make the manage-account page look a bit better (I don't know why it just looks wrong)
Figure out if the debate name can be made to truncate and shrink for smaller window widths rather than cutting off the links on the right
Make the errors meaningful and good to display
Duplicate password box on create account / manage account

TODO:

Figure out if the debate name can be made to truncate and shrink for smaller window widths rather than cutting off the links on the right
Make the errors meaningful and good to display
Write down / formalize how I'm managing account state, cookies, and redirects/refreshes in the Issue.
Figure out how DebateName will update inside a layout instead of a template (do I need to revert?)
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO:

Figure out if the debate name can be made to truncate and shrink for smaller window widths rather than cutting off the links on the right
Write down / formalize how I'm managing account state, cookies, and redirects/refreshes in the Issue.
Figure out how DebateName will update inside a layout instead of a template (do I need to revert?)
Create a warning dialog for the Delete Account button.
Check that all of my status codes look reasonable.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out if I need to insert a bunch of "await" commands throughout my entire codebase to prevent subtle bugs in the future.

TODO (Incomplete):
TODO for future branch:
Figure out why the rectangular shadow on the claim box is wrong (I thought I fixed that...)
Make the syntax box on constraint claims flat at the top (I thought this looked good but now I've changed my mind)

TODO:

Write down / formalize how I'm managing account state, cookies, and redirects/refreshes in the Issue.
For the backend, maybe create a custom decorator for my standard authentication if/else.

TODO for future branches:

Figure out how DebateName will update inside a layout instead of a template (do I need to revert?)
Figure out if the debate name can be made to truncate and shrink for smaller window widths rather than cutting off the links on the right
Figure out why the rectangular shadow on the claim box is wrong (I thought I fixed that...)
Make the syntax box on constraint claims flat at the top (I thought this looked good but now I've changed my mind)

TODO for future branches:

Figure out how DebateName will update inside a layout instead of a template (do I need to revert?)
Figure out if the debate name can be made to truncate and shrink for smaller window widths rather than cutting off the links on the right
Figure out why the rectangular shadow on the claim box is wrong (I thought I fixed that...)
Make the syntax box on constraint claims flat at the top (I thought this looked good but now I've changed my mind)
Write down / formalize how I'm managing account state, cookies, redirects/refreshes, error messages / responses, and debate name information in the Issue.


Rasberry Clock Problem

Hey, thanks for your aweasome work, does help me alot with my project.
Now, I did build your project nd tried it out on my ubuntu VM, there it works perfectly as it is supposed to be. So yeah but I want to let it run on my small "Server" a Rasberry Pi B^^
Anyway the error I get is that the recvWindow is not enough, I found some solutions like checking my timezone from my PI and stuff but nothing worked, the time is synchronised by NTP as it should be, and I did put it on my actual Timezone where I live.
I tried to extend the string in the binance_account.cpp but it didnt help.
So yeah, here I am, dont know what to try else, I think it could be cause of the Pi has no Hardware Clock and maybe binance detects that and doesnt like it?

Please help :)
BTW: just seen that you are from Zurich aswell so you can answear in german aswell if you prefer :D

Hi this is an interesting one, thanks!
Right, I saw this before on x86, and the reason was a clock skew. Even a small skew of milliseconds is important for Binance. So you should sync your clock with NTP server quite often. Aside of this, the code in binance::get_current_ms_epoch() utility function could very well be involved:
unsigned long binance::get_current_ms_epoch( )
{
        struct timeval tv;
        gettimeofday(&tv, NULL);

        return tv.tv_sec * 1000 + tv.tv_usec / 1000;
}

Blind guess is the embedded ARM chip does not offer enough accuracy for gettimeofday() function, which is actually not mandated. I mean it's rather our issue here that we should use some high-precision timer here explicitly.
I think this API code should be replaced with C++11 chrono (with care - without breaking Windows as well). If you have time to experiment, patches on this to binance-cxx-api are very welcome!

https://stackoverflow.com/questions/47658329/std-chrono-time-synchronization
Found this actually, so it seems not that easy. Cause yeah if I just use chrono with the time from my system it will probably still be wrong.
Or do you think the accuracy from chrono to the usual time function is enough to fit?

System always should have a high-precision realtime clock such as clock_gettime on Linux. There should be its equivalent in chrono. But this is not epoch time. The second part is to somehow align this clock to the low-precision epoch clock.

So yeah changed that one now to chrono, doesnt solve the problem but makes the code more handy^^
What another idea is which binance is recommending is extending the recvWindow.
https://github.com/ccxt/ccxt/issues/936
In your code I found this in the binance_account.cpp, but if I try to just add some value, this doesnt change anything, and yeah this is a value which should be given by calling the function, hmm.

(has a namespace for chrono in it, and didnt delete your functions cause I just wanted to test^^)

Please try the following and let me know if it works better for you:
--- a/src/binance_utils.cpp
+++ b/src/binance_utils.cpp
@@ -78,16 +78,20 @@ time_t binance::get_current_epoch( )
 {
        struct timeval tv;
        gettimeofday(&tv, NULL);
-
        return tv.tv_sec ;
 }

 unsigned long binance::get_current_ms_epoch( )
 {
+#ifdef _WIN32
        struct timeval tv;
        gettimeofday(&tv, NULL);
-
        return tv.tv_sec * 1000 + tv.tv_usec / 1000;
+#else
+       struct timespec tv;
+       clock_gettime(CLOCK_REALTIME, &tv);
+       return tv.tv_sec * 1000 + tv.tv_nsec / 1000 / 1000;
+#endif
 }

Just did the update but still the same error, prob I have to increase the recvWindow

OK, could you please tell us what actually happens when you call ntpdate:
$ sudo ntpdate pool.ntp.org
17 May 17:22:17 ntpdate[17498]: adjust time server <IP_ADDRESS> offset -0.005519 sec

If you repeatedly call ntpdate, does the second offset show zero?

Looks quite good to me

Thanks for testing. Meanwhile, I've bumped bitrader to 92d907e4c9691832f7c50bf055534d5cfb8019f1 which cleans out redundant dependency on OpenSSL. I also re-checked that everything works.

BINANCE_ERR_CHECK(account.getInfo(result));

where the recvWindow argument actually equals zero, by default!
Maybe you'd want to confirm your issue on a clean build of the newest version (thanks in advance!)

Just did a clean rebuilt, deleted everything and started from a new git clone.


datahub check local-docker is not a command

Describe the bug
In the docs, it says that I can use datahub check local-docker to check that everything is running as it should. This returns Error: No such command 'local-docker'. Seems to me the command was removed, and that the docs should be updated.
datahub check --help
.../lib/python3.8/site-packages/datahub/ingestion/source/metadata_common.py:7: UserWarning: importing from datahub.ingestion.source.metadata_common is deprecated; use datahub.ingestion.api.workunit instead
  warnings.warn(
Usage: datahub check [OPTIONS] COMMAND [ARGS]...

  Helper commands for checking various aspects of DataHub.

Options:
  --help  Show this message and exit.

Commands:
  mce-file  Check the schema of a MCE JSON file.
  plugins   List the enabled ingestion plugins.

To Reproduce
Steps to reproduce the behavior:

Install datahub CLI
datahub check local-docker
???
See error

Desktop (please complete the following information):

OS: Ubuntu 20.04
Version <IP_ADDRESS>

Sorry about that @dingobar - the command should be datahub docker check. Will fix this soon


Expected string or buffer

Brief Description: After setting my Bitcoin wallet to recieve founds and setting the description for a pending item to be sold and i recieve the message "expected string or buffer" after a few tries the plataform accepts the pending sale.
Windows 7, updated.

@cpacia any thoughts on what this error message indicates? Possibly related to unexpected characters in the description?

This issue has not been possible to reproduce.


fix: pin isbot to 3.x

PR Checklist

[x] Addresses an existing open issue: reported by Joe in slack 😄
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Fix broken deploys from the isbot@4 - Internal remix entry.server.tsx file relies on isbot@3

So by default you own your entry points (entry.server.tsx, entry.client.tsx), but since they are mostly boilerplate and don’t often need to be customized - you are able to delete them and remix has its own internal implementations (currently using the isbot v3 API).  One Joe updated the dep to v4, things went awry since the internal impl still assumes v3 (we’ll be fixing this assumption in the next remix release)
If you run npx remix reveal you’ll see the “normal” setup which removes the “hidden” usage - so that could be more appropriate for a shared repo such as this one where different folks with different levels of Remix familiarity will be contributing.

One Joe updated the dep to v4, things went awry since the internal impl still assumes v3 (we’ll be fixing this assumption in the next remix release)

That's not quite true — I updated to v4 just to see if that would fix the issue before moving on with my day :-)
I think what happened is:

The repository got created with "isbot": "latest",
isBot updated their "latest" to point to v4 today (https://www.npmjs.com/package/isbot)
Our cron job that regularly rebuilds the site in order to make sure the "up next" events list is correct grabbed this update, which broke stuff!

Oh interesting, my bad.  I think I thought we installed latest at app creation but that it left the numerical version in package json after that, not ‘latest’ verbatim. Does pnpm’s lock file not store the v3 version resolved to by ‘latest’?  Or does the cron job do a full reinstall and not use the lock file (I.e., npm install versus npm ci)?  I’m not too familiar with pnpm.
Aren’t y2k bugs fun?!?


coqPackages.coq-simple-io: 0.2 -> 1.0.0

Also update QuickChick for compatibility.
Motivation for this change
Major update.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build coqPackages.QuickChick coqPackages_8_9.simple-io


[gasoracle]feat: enrich logs for gas oracle

Goals of PR
Core changes:

enrich logs for gas oracle, especially for calculating token ratio

please execute go mod tidy


feat: Improve error handling in SignInWithGoogle by rethrowing exceptions

This PR enhances the exception handling in the SignInWithGoogle process by rethrowing exceptions. This will allow us to differentiate between the types of exceptions that occur, including distinguishing between an actual error and a user cancellation.
closes #2417
Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update contains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[ ] I added new tests to check the change I am making.
[ ] All existing and new tests are passing.
[x] Any breaking changes are documented below.

recheck

I have read the CLA Document and I hereby sign the CLA


Uncaught class error, Plugin not found

Fatal error: Uncaught Error: Class 'HeaderRewritePlugin' not found in D:\xampp\htdocs\test\index.php:89 Stack trace: #0 {main}thrown in D:\xampp\htdocs\test\index.php on line 89
What is the error in this senario

I meant how can I fix it


dotty: 0.20.0-RC1 -> 0.23.0-RC1

Motivation for this change
Update to latest RC
Things done
Update version and sha

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Impact on closure size is +1.4M
@karolchmist @virusdave

Looks good :) But I can't merge PR


.NET Debugging is supported only in Microsoft versions of VS Code error in VS Code 1.36.0

After updating to VS Code 1.36.0 (current released version) to users are running into the following error when they start debugging -
".NET Debugging is supported only in Microsoft versions of VS Code. See https://aka.ms/VSCode-DotNet-DbgLicense for more information."

@sborkowski @guardrex are you both on Windows? if not, what OS are you on?

Win10 here

Win10 also.

I have a fresh installation of the Microsoft VS Code version 1.36.1.  I am receiving the warning in the console.

@dan-maxwell That isn't a warning. It is just the license text. Unless you are seeing ".NET Debugging is supported only in Microsoft versions of VS Code. See https://aka.ms/VSCode-DotNet-DbgLicense for more information." you are all good.

Got it.  Thanks.  Wish I could hide it though.

Just run into this issue with 1.36.0 on Manjaro (Arch) and SDK 2.2. Not sure I can try Insider build.

@torquerrr Are you using a distribution of VS Code from Microsoft? Note that an insiders build wouldn't help here.

@gregg-miskelly
I believe mine is Community-OSS version from Manjaro community repo.

@torquerrr what you are running into is expected -- only Microsoft official distributions of VS Code are supported. See https://aka.ms/VSCode-DotNet-DbgLicense for more information.

@gregg-miskelly
Oh, my bad!
Sorry for wasting your time on this and thanks for pointing me in the right direction. I will try to install the MS-distributed version now and see how it goes.
I have updated the aforementioned document, please, take a look.

Hi, I also ran into this issue in my code-server. Any ideas?
OS: Windows10 20H2  WSL2 Ubuntu2004

@Weijee what you are running into is expected -- only Microsoft official distributions of VS Code are supported. See https://aka.ms/VSCode-DotNet-DbgLicense for more information.


VSCode error compiling c++ exe not found

VSCode Version: 1.7.2
OS Version: windows 8.1 v6.3 build 9600

Steps to Reproduce:

i have a problem with compiling .cpp to .exe, but i can compile from cmd without problems
when i click debug it gives me an error main.exe not found
after trying i am clicking ctrl+shift+b to build then F5 to run, why i can't just click F5 and it should build and run? thank you

tasks.json
{
    "version": "0.1.0",
    "command": "C:\\CodeBlocks\\MinGW\\bin\\g++.exe",
    "isShellCommand": true,
    // compiles and links with debugger information
    "args": ["-g", "-o", "main.exe", "main.cpp"],
    // without debugger information
    //"args": ["-o", "hello.exe", "hello.cpp"],
    "showOutput": "always"
}

launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "C++ Launch (Windows)",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceRoot}/main.exe",
            "MIMode": "gdb",
            "miDebuggerPath": "C:\\CodeBlocks\\MinGW\\bin\\gdb.exe",
            "stopAtEntry": false,
            "cwd": "${workspaceRoot}",
            "externalConsole": false,
            "visualizerFile": "${workspaceRoot}/my.natvis"
        },
        {
            "name": "C++ Attach (Windows)",
            "type": "cppvsdbg",
            "request": "attach",
            "processId": "${command.pickProcess}"
        }
    ]
}

I believe you need to set a preLauchTask in the launch.json. This will automatically run the build task when you launch the debugger with f5.
Let me know if that solves your problem.

@mjbvz thank you, i have added "preLaunchTask": "C:\\CodeBlocks\\MinGW\\bin\\g++.exe" and it works, but one small problem when i click F5 the output console pops up instead of the debug console, is there a way to fix it or a shortcut? thank you

@mjbvz thank you, i have added "preLaunchTask": "C:\\CodeBlocks\\MinGW\\bin\\g++.exe" and it works, but one small problem when i click F5 the output console pops up instead of the debug console, is there a way to fix it or a shortcut? thank you


LPFG-717 Add audience

Add audience frontend templates and backend connection to lpg-learning-catalogue

@jakub-kainos can you update and resolve any conflicts


Replace run-checks.[ps1/sh] with cargo-xtask pattern instead

Using the cargo-xtask pattern for implementing this script would be a better natural fit instead of the current setup.
This also gains us the benefit that this can be expanded in the future.
For developers, the invocation of these checks would be changed from:
> run-checks.ps1

to:
> cargo xtask run-checks

This should be pretty straightforward to port over, as the script is already written in Rust :)

Cc'ing @Luni-4

Closing as complete via #757


Provide raw counters metrics

Is your feature request related to a problem? Please describe.
Pulsar is offering many built-in metrics, which is pretty awesome. You can find metrics on any layer, from the pulsar-proxy to Bookkeeper. There are easy to plot within Grafana as most of the rate are already computed, for example pulsar_throughput_in is directly offering the total throughput of the namespace coming into this broker in bytes/second.
However, for some usages, metrics based on rate are not enough. For example, to bill users according to messages produced, you cannot rely on a rate, you need the raw counter associated.
Describe the solution you'd like
I would like to add a new boolean to the configuration exposeTopicLevelMetricsAsCounterInPrometheus, which default is false. By setting it to true, broker will expose new counter metrics, which will be the raw counters used to compute the rates internally. The new metrics could be suffixed by _counter, for example:

pulsar_throughput_in_counter
pulsar_in_counter

and so on. We could also do the same work for any metrics which are a rate, but I think we should start with the topic metrics.
Describe alternatives you've considered
Using the rate to compute the counter is not offering enough precision.
What do you think about it? We can discuss on the name of the parameter and the naming schemas.

Thanks @PierreZ for working on this. it sounds good to me.  Add @sijie @merlimat, to see if they have more suggestions.

@PierreZ +1
Can I suggest using names like "pulsar_in_bytes_total" or "pulsar_in_bytes_counter", "pulsar_in_messages_total" or "pulsar_in_messages_counter"?

I like pulsar_in_bytes_total!

I started working on it. From what I see, the rate is computed through Rate, which seems to be hold by Producer which Represents a currently connected producer. The rate is polled frequently. As the classes are representing by connected {Producer, Consumer} and the fact the update is async, we can miss events between two polls if a {Producer, Consumer} disconnects.
I'm wondering if the metrics can be generated from a place less volatile, maybe at the opening of the managed ledger? What do you think?

Found a naive solution, by creating a Counter directly on the AbstractTopic class. I am not sure if this is recommend though. What do you think @sijie?

I don't think we have used Prometheus counter directly.
I would suggest:

use LongAdder in AbstractTopic for counting only.
expose those counters in PersistentInternalTopicStats or TopicStats
update NamespaceStatsAggregator to expose those counters to prometheus servlet.

Thanks, I will do this 👍


Calling SongBird::join() while already in the voice channel causes a deadlock

Songbird version: 0.1.6
Rust version (rustc -V): 1.51
Serenity/Twilight version: 10.5
Features: (Songbird & Serenity)
[
    "driver-tokio-02",
    "gateway-tokio-02",
    "serenity-rustls-tokio-02",
]

Description:
Calling SongBird::join() while already in the voice channel causes a deadlock. The second call to join will never return.
Steps to reproduce:
Modify the serenity voice example to call join twice in the join command. The second one should return an error or be idempotent and succeed. Either way it shouldn't deadlock the bot.
voice_manager.join(guild_id, voice_channel_to_join).await;
voice_manager.join(guild_id, voice_channel_to_join).await;

Thanks for the detailed bug report! This issue is fixed in the next breaking release by #47.
Until then, you will need to check join state yourself. I hope to have a pre-release up soon -- there were one or two further changes I wanted to fit in, but have been busy with work.


Issue #652 fix development_runner bug

The application should now reload once only, and the module parameter is no longer overwritten.

Coverage remained the same at 99.731% when pulling a702e08942eb23a58103ed61bf3fb44b7970cd31 on brainnwave-herve:issue/652 into e1f6a20589913998913b875679be1fbf34cae15e on timothycrosley:develop.

Coverage remained the same at 99.731% when pulling a702e08942eb23a58103ed61bf3fb44b7970cd31 on brainnwave-herve:issue/652 into e1f6a20589913998913b875679be1fbf34cae15e on timothycrosley:develop.

Coverage remained the same at 99.731% when pulling a702e08942eb23a58103ed61bf3fb44b7970cd31 on brainnwave-herve:issue/652 into e1f6a20589913998913b875679be1fbf34cae15e on timothycrosley:develop.

Coverage remained the same at 99.731% when pulling a702e08942eb23a58103ed61bf3fb44b7970cd31 on brainnwave-herve:issue/652 into e1f6a20589913998913b875679be1fbf34cae15e on timothycrosley:develop.


Add support for Cohere embed V3

Feature request
The new cohere V3 embed endpoints have a new required parameter - input_type.
Langchain currently doesn't support this parameter
https://txt.cohere.com/introducing-embed-v3/
Motivation
Being able to use the newest multilingual embedding capabilities is something users who are developing an international product would find very important
Your contribution
Documentation!

I can take that task over. I've already contributed to Cohere embeddings.

@kacperlukawski that would be awesome - I can take a stab at the nodeJS implementation. much more familiar with that one

@kacperlukawski thanks for putting in the work! Can you update us here once it's ready?

@jnance314 Added a new PR with that change: #12940

Merged with https://github.com/langchain-ai/langchain/pull/12940

Hi. Quick question on the input_type parameter. Looks like cohere API considers search_document for the actual doc and search_query for the query.  How would you pass this to langchian here. Should search_document be used for embed_documents func and aembed_documents be used for?

@mehradans92 embed_documents uses input_type="_search_document". Instead, embed_query uses input_type="search_query. You can see this in PR #12940 code changes

Great! Thanks @antoniolanza1996


✨ [FEAT]: SEO - Add Google Search Console Integration

Summary
Plausible provides a way to integrate with Google SRPs - do it.

Tasks

[ ]

URL
https://www.dgrebb.com/

Closed by #1136


Make sure activation function of neurons get switched back to TanH from Identity when appropriate

Fixed in 74d8b2d..21defef


Invalid expires attribute date on setting Cookies during Analyzer

During analyzer run, using --info, this warning can be seen:
WARN  org.apache.http.client.protocol.ResponseProcessCookies - Invalid cookie header: "Set-Cookie: AWSALBCORS=<CORS_REDACTED>; Expires=Tue, 28 May 2024 12:45:19 GMT; Path=/; SameSite=None; Secure". Invalid 'expires' attribute: Tue, 28 May 2024 12:45:19 GMT

The package org.apache.http.client.protocol.ResponseProcessCookies is not from us. Can you share more context from the stacktrace?

@heliocastro, do you see this when running one of the SW360 commands? Because that seems to be the only place where ORT is using Apache Http instead of OkHttp. If so, this might solve it.

Hi @sschuberth, I did some investigation and the issue comes from the maven implementation on Ort, not related to the sw360, and happens during Analyzer stage: Here's exact snippet where it happens in eclipse-aether:
I'll try to debug further
10:05:46.809 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - Ignoring local repositories [vw-central (https://jfrog.devstack.vwgroup.com/artifactory/public/, default, releases), vw-dp-common (https://jfrog.devstack.vwgroup.com/artifactory/gvo-maven-dataproductscommon/, default, releases+snapshots), central (https://repo.maven.apache.org/maven2, default, releases), sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots, default, snapshots), central (https://repo.maven.apache.org/maven2, default, releases)].
10:05:46.809 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - Searching for 'org.webjars:swagger-ui:jar:4.18.2' in [vw-central (https://jfrog.devstack.vwgroup.com/artifactory/public/, default, releases), vw-dp-common (https://jfrog.devstack.vwgroup.com/artifactory/gvo-maven-dataproductscommon/, default, releases+snapshots), central (https://repo.maven.apache.org/maven2, default, releases), spring-release (https://repo.spring.io/release, default, releases), spring-snapshot (https://repo.spring.io/snapshot, default, releases+snapshots), sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots, default, snapshots)].
10:05:46.809 [DefaultDispatcher-worker-1] DEBUG org.ossreviewtoolkit.plugins.packagemanagers.maven.utils.MavenSupport - Trying to download artifact 'org.webjars:swagger-ui:jar:4.18.2' from https://jfrog.devstack.vwgroup.com/artifactory/public/org/webjars/swagger-ui/4.18.2/swagger-ui-4.18.2.jar.
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.eclipse.aether.internal.impl.DefaultTransporterProvider - Using transporter HttpTransporter with priority 5.0 for https://jfrog.devstack.vwgroup.com/artifactory/public/
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider - Using connector BasicRepositoryConnector with priority 0.0 for https://jfrog.devstack.vwgroup.com/artifactory/public/ via localhost:9000 with org.eclipse.aether.util.repository.JreProxySelector$JreProxyAuthentication@4ddacff8
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.client.protocol.RequestAddCookies - CookieSpec selected: default
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection request: [route: {tls}->http://localhost:9000->https://jfrog.devstack.vwgroup.com:443][total available: 3; route allocated: 1 of 50; total allocated: 3 of 100]
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection leased: [id: 0][route: {tls}->http://localhost:9000->https://jfrog.devstack.vwgroup.com:443][total available: 2; route allocated: 1 of 50; total allocated: 3 of 100]
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-0: set socket timeout to 0
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-0: set socket timeout to 1800000
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.execchain.MainClientExec - Executing request HEAD /artifactory/public/org/webjars/swagger-ui/4.18.2/swagger-ui-4.18.2.jar HTTP/1.1
10:05:46.810 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.execchain.MainClientExec - Target auth state: UNCHALLENGED
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.auth.HttpAuthenticator - Authentication required
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.auth.HttpAuthenticator - jfrog.devstack.vwgroup.com:443 requested authentication
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Authentication schemes in the order of preference: [Negotiate, Kerberos, NTLM, CredSSP, Digest, Basic]
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for Negotiate authentication scheme not available
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for Kerberos authentication scheme not available
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for NTLM authentication scheme not available
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for CredSSP authentication scheme not available
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for Digest authentication scheme not available
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection [id: 0][route: {tls}->http://localhost:9000->https://jfrog.devstack.vwgroup.com:443] can be kept alive indefinitely
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-0: set socket timeout to 0
10:05:46.860 [DefaultDispatcher-worker-1] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection released: [id: 0][route: {tls}->http://localhost:9000->https://jfrog.devstack.vwgroup.com:443][total available: 3; route allocated: 1 of 50; total allocated: 3 of 100]
10:05:46.860 [DefaultDispatcher-worker-1] WARN  org.apache.http.client.protocol.ResponseProcessCookies - Invalid cookie header: "Set-Cookie: AWSALB=rlhopvySkjsYFSk30vL2SO3xIcok/rnQ98TEfEjWBgT5F9X+8RcToudxqjv26n9TW9k0h/sx0f/PVIjxajAeFUU5WN1i5sxiYqwHkssgyquG0NwbZUlXoJH+rnzq; Expires=Mon, 01 Jul 2024 08:05:46 GMT; Path=/". Invalid 'expires' attribute: Mon, 01 Jul 2024 08:05:46 GMT
10:05:46.860 [DefaultDispatcher-worker-1] WARN  org.apache.http.client.protocol.ResponseProcessCookies - Invalid cookie header: "Set-Cookie: AWSALBCORS=rlhopvySkjsYFSk30vL2SO3xIcok/rnQ98TEfEjWBgT5F9X+8RcToudxqjv26n9TW9k0h/sx0f/PVIjxajAeFUU5WN1i5sxiYqwHkssgyquG0NwbZUlXoJH+rnzq; Expires=Mon, 01 Jul 2024 08:05:46 GMT; Path=/; SameSite=None; Secure". Invalid 'expires' attribute: Mon, 01 Jul 2024 08:05:46 GMT

Still looks like this should be reported against https://maven.apache.org/resolver/issue-management.html instead.

Opened here: https://issues.apache.org/jira/browse/MRESOLVER-574

Thanks, let's close this in favor of the upstream issue then; we'll automatically benefit from a fix if a new version of the resolver library with the fix is released.

Version 1.9.21 of Maven resolver will have the fix.


amplify not pulling gitHub updates, also banner on UI keeps loading

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
dhjilswhbtpyw
AWS Region
us-east-1
Amplify Hosting feature
Deployments
Describe the bug
amplify not pulling gitHub updates, also banner on UI keeps loading. it worked fine till 1 day ago.
Expected behavior
amplify should deploy updated code. the banner on UI should have guidance/instructions as usual.
Reproduction steps

make a change in the code 2. commit/push to github, 3. amplify fails to deploy

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

I'm experiencing the same. AppId: d263pg34gxs8oh

i tried creating new app, connected to same gitHub. on initial deployment, it worked but when i updated code again, same issue.

Hi @vijayendra-roy @foobarnes , we are actively investigating into this to narrow down the root cause of the issue.

Same here. I tried two commits and neither triggered a build.

A quick update on the root cause:
Amplify Hosting uses GitHub web-hooks to trigger your builds and the root cause of this issue seems related to this ongoing GitHub event: https://www.githubstatus.com/ .

appreciate the quick deep dive. i see the GitHub incident is resolved. trying new build, likely working now, will confirm in a bit.

Thanks @vijayendra-roy!
@foobarnes @richie42690 Please retry triggering a new build as the GitHub incident is resolved.

@Jay2113 The build queue automatically resolved/triggered for me. Thanks for keeping us updated!

All good! Thanks @Jay2113 and team for digging in and keeping us updateed.


Chrome/chromium: travelers not rendering when set way off-screen and then scrolled on-screen

OS: Windows 10
Browser: Chrome/chromium
Repro: Load wayfinder's trialgrounds on a page approximately 976px by 1154px. Scroll all the way to the bottom of the page--sometimes the final test traveler and the x-clipping test traveler won't be rendered. Click hide and then click show. Scroll all the way to the top--sometimes the control, size, and absolute test travelers won't be rendered.
This issue is caused by a bug in Chromium's content-visibility and/or contain rendering optimizations. Chrome attempts to improve rendering performance by not rendering elements that are off-screen and then rendering them as soon as they are brought on-screen. Unfortunately, it seems that Chrome fails to detect that particular elements have been brought on-screen (or something to that effect). The hidden divs can usually be brought back by interacting with them with pointer events.
Attempted solutions:

Use "visibility: visible" on the wayfinder div. No effect.
Use "content-visibility: auto" on travelers. Solves the main issue, but introduces another issue where travelers' overflowing content isn't rendered.
Use "content-visibility: auto" on travelers, and also use a css property that I forgot (something about setting margin-borders extremely wide) in order to force the overflowing content to render. Solves the overflowing rendering issue, but the overflowing content cannot take pointer events. Couldn't find a solution for the mouse events issue.
Use "content-visibility: auto" on the wayfinder div. Broke many things.
Use "content-visibility: auto" on the body. iirc, it fixed the rendering issue, but it broke the rendering of fixed divs anywhere on the page. (iirc, fixed divs with "height: 100vh" were taking the height of the page, not the viewport, or something like that.)

Solutions not attempted yet:

Passive or active listeners for travelers being brought on-screen. I'm not a fan of this idea, cause I feel it will bloat the code and perform poorly. Might look into it eventually.

can't repro anymore

can't repro anymore


[Bug] UnboundLocalError at auto-annotations with empty data.

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour
UnboundLocalError does not occurs. Response returned with status code = 400 Bad Requests.
Current Behaviour
UnboundLocalError occurs.
Possible Solution
Fix the bug.
 No
Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 20.04
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:

File "/home/diman/.local/lib/python3.8/site-packages/rest_framework/views.py", line 502, in dispatch
response = handler(request, args, *kwargs)
File "/home/diman/git/cvat/cvat/apps/lambda_manager/views.py", line 499, in func_wrapper
data = func(*args, **kwargs)
File "/home/diman/git/cvat/cvat/apps/lambda_manager/views.py", line 594, in create
'{} lambda function was run '.format(function) +
UnboundLocalError: local variable 'function' referenced before assignment

Next steps
You may join our Gitter channel for community support.

@DmitriyOparin , could you please prepare a PR for the bug?

@nmanovic, yes, I will fix this error


Response style changed

cant you add the response after all the if statements.
also check is failing

No.. because the response style is different for different intents..

these were the issues.. i have fixed them... i am pushing these changes
R GAUTAM
B.E CSE
KCG College of Technology
+91<PHONE_NUMBER>
On Sun, Dec 17, 2017 at 4:51 PM, Gautham Santhosh<EMAIL_ADDRESS>wrote:

cant you add the response after all the if statements.
also check is failing
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Anna-Assistant/Anna/pull/66#issuecomment-352248642,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQEzFchnns8AyUQb1e4vgIzgllpSvr6oks5tBPlUgaJpZM4REi46
.