Rock Paper Scissors Game

I would like to add the popular Rock Paper Scissors game built using HTML,CSS,JS. I am a GSSOC22 participant.
Code of Conduct✅

[x] I agree to follow this project's Code of Conduct.
[x] I checked the current issues for duplicate problems.
[x] I have gone through project README.

@prer45 Sorry but I have to close this issue because this already exists. Feel free to raise a new one or contact one of us mentor for doubt or support


Remove obsolete portable server install scripts

https://github.com/google/earthenterprise/blob/master/earth_enterprise/legacy_installer/Scripts/portable/create_linux_installer.sh is broken post unbundling of python.
We already have a replacement in https://github.com/google/earthenterprise/blob/master/earth_enterprise/src/portableserver/build.py

Scope has expanded to cover removal of all the portable server scripts - update title.

Update from @tst-ppenev:

This issue seems to require agreements among people who we may not hear from immediately. My vote is to move the <server_extra> directory under <earth_enterprise/artwork> for now, and remove the rest of the portable legacy installer generators.

@bradh: I was trying to make it easier for whoever is going to review the usage rights on all the different icon images, and whatever other artwork there is. We could also delete the ones for the Portable Server on master, and refer to past commits.
Sometimes there's a lot of discussion on even a simple issue, especially, with a heterogenous team.
It would be OK, if you re-opened your pull request, either deleting everything, or moving the icons.


V0.2/docker security profile

This adds a new release-only job to the CircleCI build that creates an augmented Docker security profile and adds that to the artifacts folder. The idea is to include this file on a GitHub release.
The job works by running make build in the docker/ folder that in turn runs a small Python script. I chose Python for the convenience of hacking JSON. The resulting profile allows calls to personality that have the flags required by Poplog.

I was going to say: "can you update https://github.com/GetPoplog/Seed/wiki/Running-poplog-under-Docker", but then I go and have a look at it and you've already done it! Very thorough Steve! Nice Job!


Choose iOS or Android as OS option for React Native app on AppCenter

Should I choose iOS, Android or create 2 separate apps for React Native?

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

ID: 7ed0fde7-9e78-c318-9f8c-9d921ec7d7b3
Version Independent ID: 946ead1c-4b65-8318-c77a-ef98873adac7
Content: Get Started with React Native - Visual Studio App Center
Content Source: docs/sdk/getting-started/react-native.md
Service: vs-appcenter-sdk
Sub-service: app-center-general
GitHub Login: @lucen-ms
Microsoft Alias: lucen

I think it should be separate?

@CyberMew Thanks for your comment!
It mentions here https://docs.microsoft.com/en-us/appcenter/distribution/codepush/rn-get-started

As with all other React Native plugins, the integration experience is different for iOS and Android, so follow the setup steps depending on the platform(s) you target for your app. Note, if you're targeting both platforms it's recommended to create separate CodePush applications for each platform.


infiniteScroll won't stop after reaching last page

path: 'api/users?page={{#}}',
checkLastPage: '.pagination__last',
responseType: 'text',
append: false,
loadOnScroll: false,
button: '.js-show-more-button',
status: '.page-load-status',
<a class=".pagination__last" href="api/users?page=4">last
After reaching last page, last event does not occur.
it requests a non-existent page "api/users?page=5", and then error event occurs.

Thanks for reporting this issue. I'm tracking this issue in #840


Search Github Profile Template

# SEARCH GITHUB PROFILE
This template can be used in any website for the user to search the Github Profile/User to see the

Profile Image
Username
Followers
Following
Repositories - (max upto 6 repositories will be seen)

Issue Fixed:
A person with no knowledge of github can now search for a user and see his/her profile.
Fixes Issue : #846
Tech-Stack Used:

HTML5
CSS, SCSS
JavaScript

ScreenShots:

Suggestions on improving the template are welcomed!

@VidhiBhatt01 please check the issues section, the project has been labeled with a GSSOC22 label.
Kindly, please consider the contribution.


Prevent users from changing critical storage and cookies information and the reloading to temporarily gain access rights

Also this is a problem part of the bigger security system I've building. Browser crashes, cache misses, DDOS, data corruptions , SYN floods/attacks, vulnerabilities in third parties
Should not fatally affect the state of the user's session, just make it working or give valid reason before proceeding with next action.
This is issue is a priority since some user/browser storage can be used by users to manually change checked info, even if it doesn't reflect on website always.

Options:

should add to the async session and Auth handler I made some code to handle these transgressions
Make a listener that detects these
Specific changes and validates with backend session if this is right (if Rare Cases where it would be , if any)
Change the storage design of the whole authentification to rely more on tokens or use more secure storage (cookies are safe however)

Permission and Security issues fixed, manual storage/cookie alteration blocked now and reset automatically by my backend Idtoken authorization system + my frontend user context (though the latter might still need some work)


[v0.14.2] The function NewStaticResolver has a bug, the main branch has been fixed, and no new tag has been added

new tag 0.15.0 is up


NO-ISSUE: upgrade linter packages in requirements-dev.txt

Upgrading flake8 is needed for Python 3.12 compatibility

https://github.com/PyCQA/flake8/issues/1885

Saw this happen

https://github.com/skupperproject/skupper-router/issues/1350


Brainstorming

As this repository will most likely be a Laravel (and Lumen eventually?) package, here are the expected features:

Response Macros (same as in the previous version)
A lightweight CORS middleware

Feel free to add suggestions
Thanks!

This is where I step in :D

@jadsalhani You mean the other repo 😄

I just can't wait for use that with Lumen... :D

@birkansava I'll be working on a package that has Response macros only for now, which will work with Lumen as well

@birkansava https://github.com/jadjoubran/laravel-angular

@jadjoubran I actually made it work with Lumen :) but still waiting for Angular2

We're waiting for Angular 2 template :)

Hi @vtnhan
What do you mean exactly? Can you give an example?

Like this but now is Angular 2 :)

@vtnhan This is currently taken care of by the Angular CLI
They do an amazing job at generating, serving, deploying (and much more) your Angular projects


Fixes multiple alignment problems and an overlaping condition

This aims to fix two things by improving the use of bootstrap container>row>col>content model:

miss alignment between lists and nav/pagination and search bar;
overlap of nav/pagination and search bar when there is no pagination.

That is very nice. Thank you Nuno Mota. It has already been merged and deployed.


rpi-update: Add support for updating the bootloader EEPROM

Download the latest EEPROM release to the local /lib/firmware/raspberrypi/bootloader directory
Update the rpi-eeprom tools
Remove the old eeprom_version check
Check bootloader commits as well as firwmware commits
SKIP_BOOTLOADER default to 1 for now until fully tested

@popcornmix I think the bootloader update is ok, might be missing some integration bits for rpi-update but seems to work

@popcornmix I think this is ok now!

I tested this and:
pi@pi5:~/projects/rpi-update $ sudo UPDATE_SELF=0 SKIP_BOOTLOADER=0 ./rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
FW_REV:d16727d5c99846538e1996b709e31470e6412e46
BOOTLOADER_REV:7e22b8ff470c813d0331f8ef64b6c08125b179cc
WANT_32BIT:0 WANT_64BIT:1 WANT_PI4:1 WANT_PI5:0
#############################################################
WARNING: This update bumps to rpi-6.1.y linux tree
See: https://forums.raspberrypi.com/viewtopic.php?t=344246

'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.

DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
Downloadng bootloader tools

Downloading bootloader images
BOOTLOADER: up to date
   CURRENT: Wed 29 Nov 12:53:31 UTC 2023<PHONE_NUMBER>)
    LATEST: Mon 20 Nov 19:40:17 UTC 2023<PHONE_NUMBER>)
   RELEASE: latest (/lib/firmware/raspberrypi/bootloader-2712/latest)
            Use raspi-config to change the release.
 *** As requested, not updating kernel
 *** As requested, not updating kernel modules
 *** As requested, not updating VideoCore libraries
 *** As requested, not updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to d16727d5c99846538e1996b709e31470e6412e46
 *** A reboot is needed to activate the new firmware

Should I have got this update?

WANT_PI5 says zero ?

Ah - WANT_PI5 is set automatically only if kernel_2712.img exists on /boot/firmware/os_prefix.
I currently have kernel8.img but not kernel_2712.img.
Possibly using /proc/cpuinfo and Model:  would be more reliable, but I guess my setup is an edge case.
Adding WANT_Pi5=1 did update to d16727d5c99 as desired.
pi@pi5:~ $ vcgencmd bootloader_version
2023/12/06 18:29:25
version e02d33b3122450accf9dea471a177d3b5623f5ad (release)
timestamp<PHONE_NUMBER>
update-time<PHONE_NUMBER>
capabilities 0x0000007f

@pelwell mentions that detecting Pi model may be better done with:
pi@pi5:~ $ cat /proc/device-tree/compatible
raspberrypi,5-model-bbrcm,bcm2712

which should work with upstream and downstream kernel.
(/proc/cpuinfo revision and model may not be available with non-downstream kernels).
Not necessarily something for this PR, but worth considering generally (raspi-config would be another example which could use this).

Ok, I'll do the proc-device-tree thing

Updated to force upgrade/downgrade if BOOTLOADER_REV_IN != master

Down and up-grade worked for me. Let's merge (and consider making the bootloader part enabled by default as a subsequent change).


Eigendistortion.plot_distorted_image breaks when eigen_index is not 0 or -1

The method "plot_distorted_image" of eigendistortion class (synthesize.eigendistortion.Eigendistortion) breaks when the argument "eigen_index" is not 0 or -1. I think the problem is in the method "_indexer".

Will fix this during this week's sprint.


Add support enums

Please, add support enums for macro

They are supported, just like with @AppStorage.


Add back asm.jar which was missed when manually solve the conflict.

Add back asm.jar which was missed when manually solve the conflict in https://github.com/AdoptOpenJDK/openjdk-tests/pull/185
This asm.jar is only used by systemtest for now, may be better to move to its own build.xml or has its own get script. The most probability is this is a common required jar so leave as is for now.
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

As part of solving conflict, merge with no review.


run multipe python files

I open a python file, right click, choose "Run Python File in Terminal", it create a new terminal and run it. Then i open another python file, right click, choose "Run Python File in Terminal", it does create a new terminal, instead it jumps to previous terminal. What i expects is it create another new terminal and run it automatically.

Duplicate of #14094


useReducer in calculator

Test using useReducer in calculator

Commenting in https://github.com/revery-ui/revery/pull/174#issuecomment-451256065 🙂

This looks really good to me. I'll review this as soon as I'm done with lunch


ui issue when admin  try to click on search  order in notification  in movile view

Bagisto Version

[ ] master branch

Steps To Reproduce

go to notification bar and try to search

Actual Result

@prateek-webkul
I am getting this issue on desktop view also. Please find the screenshot Here

@prateek-webkul
Thanks, now this issue is fixed. so I am closing this issue.
And I have attached a screenshot for future reference Here


Add histogram / unique counter function to Series

duplicate issuehttps://github.com/wesm/pandas/issues/247/close


Switching to es2015 compile target dropped code coverage

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
Switching to es2015 compile target in tsconfig.json dropped our code coverage by ~10%. We are uploading lvoc report to sonarqube.
Does anyone else discovered this by switching to diffrential loading
🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

Angular CLI: 8.3.3
Node: 12.3.1
OS: win32 x64
Angular: 8.2.7
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

Package                            Version------------------------------------------------------------
@angular-devkit/architect          0.803.3
@angular-devkit/build-angular      0.803.5
@angular-devkit/build-optimizer    0.803.5
@angular-devkit/build-webpack      0.803.5
@angular-devkit/core               8.3.3
@angular-devkit/schematics         8.3.3
@angular/cdk                       8.1.2
@angular/cli                       8.3.3
@angular/flex-layout               8.0.0-beta.26
@angular/material                  8.1.3
@angular/material-moment-adapter   8.1.3
@angular/pwa                       0.801.3
@ngtools/webpack                   8.3.5
@schematics/angular                8.3.3
@schematics/update                 0.803.3
rxjs                               6.5.3
typescript                         3.5.3
webpack                            4.39.2

Anything else relevant?

Hi, do you have some code that can demonstrate the difference in code coverage metric between es5 and es2015?

@alan-agius4
here is a simple pipe and the lcov report

Left is before es6 and right is es6 change
here is the code:
import { Pipe, PipeTransform } from '@angular/core';

/**
 * Returns color string based on remaining value.
 * Example: value = 10;max = 100; => 90% => red
 */
@Pipe({
  name: 'indicator'
})
export class IndicatorPipe implements PipeTransform {
  transform(percentage: number, treshhold?: number[]): string {
    if (!treshhold) {
      treshhold = [60, 90]; // default treshhold
    } else if (treshhold.length !== 2) {
      throw new Error('Treshold parameter should be array of two numbers');
    }
    if (percentage !== undefined) {
      if (percentage >= treshhold[1]) {
        return 'red';
      } else if (treshhold[0] <= percentage && percentage < treshhold[1]) {
        return 'orange';
      } else {
        return 'gray';
      }
    } else {
      return 'gray';
    }
  }
}

Spec file
import { TestBed } from '@angular/core/testing';
import { configureTestSuite } from 'ng-bullet';
import { IndicatorPipe } from './indicator.pipe';

describe('IndicatorPipe', () => {
  let pipe: IndicatorPipe;

  configureTestSuite(() => {
    TestBed.configureTestingModule({
      providers: [IndicatorPipe]
    });
  });

  beforeEach(() => {
    pipe = TestBed.get(IndicatorPipe) as IndicatorPipe;
  });

  it('should mark as red everything above 90%', () => {
    expect(pipe.transform(100)).toEqual('red');
    expect(pipe.transform(92)).toEqual('red');
    expect(pipe.transform(90)).toEqual('red');
  });

  it('should mark as gray if value is negative', () => {
    expect(pipe.transform(-8)).toEqual('gray');
  });

  it('should mark as red if value is greater than max', () => {
    expect(pipe.transform(888)).toEqual('red');
  });

  it('should mark as orange everything above 60% and below 90%', () => {
    expect(pipe.transform(88)).toEqual('orange');
    expect(pipe.transform(60)).toEqual('orange');
  });

  it('should mark as gray everything below 60%', () => {
    expect(pipe.transform(59)).toEqual('gray');
    expect(pipe.transform(0)).toEqual('gray');
  });

  it('should set correct values based on custom treshold', () => {
    expect(pipe.transform(15, [20, 80])).toEqual('gray');
    expect(pipe.transform(20, [20, 80])).toEqual('orange');
    expect(pipe.transform(79, [20, 80])).toEqual('orange');
    expect(pipe.transform(80, [20, 80])).toEqual('red');
  });
});

I've observed the same after moving to es2015 module type and only using import/export syntax.
We lost around 5% code coverage and 15% in size when compared to a build with commonjs.
I am not entirely sure but I think that code coverage metrics are calculated based on javascript file and not typescript, hence if output is different - metrics will be different.

same issue for me
any updates?

I had a quick look at this, and indeed it seems to be caused by what @FDIM described as the transpilled code which is later instrumented is different.
Left ES5, Right ES2015

I think we can close this issue now as we have found out what's the reason.


SQLite: update to latest, support LIMIT on UPDATE and DELETE statements

This PR is 99% reworking the build process for SQLite so I can plug in the right flags and 1% plugging in the right flags.
SQLite is now built from plain old source instead of from the amalgamation. This requires pulling in rules_foreign_cc to drive the whole ./configure && make song and dance.
The user-visible change is that LIMIT is now supported in UPDATE and DELETE statements, so if you want to delete some stale data but not spend too much time cleaning up the whole DB, you can say DELETE FROM my_table WHERE stale=1 LIMIT 100 to delete at most 100 stale rows.

Hopefully the linux-debug and windows-debug tests pass. They failed last time because they spent 6 hours making very slow progress and then got cancelled.

6 hour time limit

Tests / test (linux-debug) (pull_request) Successful in 358m

:cold_sweat:

The build here seems very slow. There are a fair number failed package fetches in the log (network issue?). We have a cache for one of the packages, if this happens more regularly we should consider caching more packages/
BTW, the -debug and -asan are purely informational (non-blocking); to merge, only the plain builds to pass.

This can't merge just yet; our internal tests fail with this change since the test environment doesn't have tclsh. I'm working on it.

The non-amalgamation build is needed to do some configuration needed for the LIMIT change which affects the assembled sqlite.c file, right?
As Orion said, we should make sure to avoid the fetch-related slowdowns, which could slow down CI a lot.

With the update to 3.44.0, there's some new functions which are enabled by default but aren't in the allowlist. I thought I'd just mention them here rather than make a suggestion/PR to add them, as there might be reasons for some of them not being allowed.
3.41.0
unhex()
Already allowed.
base64() and base85()
Not enabled by default, available as an extension (see https://www.sqlite.org/src/file/ext/misc).
3.42.0
JSON5 support in JSON functions
Whilst this doesn't bring any new functions, it's a noteworthy change that might be worth mentioning on https://developers.cloudflare.com/d1/learning/querying-json/ (cc @elithrar)
3.43.0
timediff()
Not in allowlist.
Part of https://www.sqlite.org/lang_datefunc.html
https://github.com/cloudflare/workerd/blob/7dc97db44a027046118cabe4a55a2bb6b32b1624/src/workerd/util/sqlite.c%2B%2B#L174
octet_length()
Not in allowlist.
Part of https://www.sqlite.org/lang_corefunc.html
https://github.com/cloudflare/workerd/blob/7dc97db44a027046118cabe4a55a2bb6b32b1624/src/workerd/util/sqlite.c%2B%2B#L127
3.44.0
concat()
concat_ws()
Not in allowlist.
Part of https://www.sqlite.org/lang_corefunc.html
https://github.com/cloudflare/workerd/blob/7dc97db44a027046118cabe4a55a2bb6b32b1624/src/workerd/util/sqlite.c%2B%2B#L127
string_agg()
Not in allowlist.
Part of https://www.sqlite.org/lang_aggfunc.html
https://github.com/cloudflare/workerd/blob/7dc97db44a027046118cabe4a55a2bb6b32b1624/src/workerd/util/sqlite.c%2B%2B#L185

@KianNH Thanks for the list of new functions. I'll add most of those.
base64 and base85 appear to be shell-only, at least from my reading of main.mk in the SQLite source. They aren't available for making queries using the library, so workers can't use them.


Error: Unable to download data from https://rubygems.org/

Windows Server 2012 R2
ArcGIS 10.4.1
Chef 12.12.15
When trying to execute the 'arcgis-server::system' recipe I am receiving an an error:
"Unable to download data from https://rubygems.org/ - Errno::ECONNABORTED: An established connection was aborted by the software in your host machine. - SSL_connect (https://api.rubygems.org/specs.4.8.gz)".
Do you know how I can resolve this error?  More detailed output below.
Thanks
Matt
[2016-08-10T15:52:08+01:00] INFO: *** Chef 12.12.15 ***
[2016-08-10T15:52:08+01:00] INFO: Platform: x64-mingw32
[2016-08-10T15:52:08+01:00] INFO: Chef-client pid: 2464
[2016-08-10T15:52:16+01:00] INFO: Setting the run_list to ["recipe[arcgis-server::system]"] from CLI options
[2016-08-10T15:52:16+01:00] INFO: Run List is [recipe[arcgis-server::system]]
[2016-08-10T15:52:16+01:00] INFO: Run List expands to [arcgis-server::system]
[2016-08-10T15:52:16+01:00] INFO: Starting Chef Run for myserver.mydomain
[2016-08-10T15:52:16+01:00] INFO: Running start handlers
[2016-08-10T15:52:16+01:00] INFO: Start handlers complete.
[2016-08-10T15:52:16+01:00] INFO: HTTP Request Returned 404 Not Found: Object not found:
[2016-08-10T15:52:24+01:00] INFO: Loading cookbooks<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[2016-08-10T15:52:25+01:00] WARN: "method access to node attributes (node.foo.bar) is deprecated and will be removed in Chef 13, please use bracket syntax (node["foo"]["bar"]) at c:/chef/local-mode-cache/cache/cookbooks/chef_handler/attributes/default.rb:23:in from_file' at C:/opscode/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.12.15-universal-mingw32/lib/chef/event_dispatch/dispatcher.rb:43:in call'
[2016-08-10T15:52:25+01:00] INFO: Processing chef_gem[multipart-post] action install (arcgis-server::system line 20)
[2016-08-10T15:52:27+01:00] WARN:  failed to find gem multipart-post (>= 0) from [https://rubygems.org/]
[2016-08-10T15:52:30+01:00] ERROR: chef_gem[multipart-post] (arcgis-server::system line 20) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
---- Begin output of C:/opscode/chef/embedded/bin/gem install "multipart-post" -q --no-rdoc --no-ri  ----
STDOUT:
STDERR: ERROR:  Could not find a valid gem 'multipart-post' (>= 0), here is why:
      Unable to download data from https://rubygems.org/ - Errno::ECONNABORTED: An established connection was aborted by the software in your host machine. - SSL_connect (https://api.rubygems.org/specs.4.8.gz)

It looks like Chef was not able to install multipart-post gem because connection to  https://api.rubygems.org/specs.4.8.gz was blocked by a firewall.
Before running chef, please try to install the gem manually.
>gem install multipart-post

Thanks for responding so quickly.  The local install seems to have worked.


"restart" not running on Ubuntu Trusty 14.04

see here ... https://gist.github.com/swade1987/e4dcad7edf9b5d46e6c7

Same as https://github.com/agileorbit-cookbooks/artifactory/issues/15


Implement getPlaylists and getPlaylist endpoints

Allow to serve the M3U playlists (that have been generated by beets' smartplaylist plugin).
Relates to https://github.com/beetbox/beets/pull/5121

Thanks a lot for your contribution!


[WIP] u-boot: query customer OTP register in rpi3

This patch adds support for querying the firmware
for one customer OTP register, as an alternative
for the case where bootmode register cannot be
inspected due to missing TAG implementation in firmware.
Since documentation does not seem to specify that TAG,
asked question in upstream whether it is available or not.
This patch is incomplete and should not be merged as-is.
Changelog-entry: u-boot: query customer OTP register in rpi3
Signed-off-by: Alexandru Costache<EMAIL_ADDRESS>

@floion interesting. there is a way from uboot to query otp registers.
perhaps @acostach can look into supporting usb boot
https://github.com/balena-os/balena-raspberrypi/issues/341
https://github.com/balena-os/meta-balena/issues/1575
tl;dr. in arch call, it was decided uboot should query otp bits if usb boot is enabled, then scan for usb devices as well if it is.

@ZubairLK yes, that's the point of this PR

Since documentation does not seem to specify that TAG, asked question in upstream whether it is available or not.

Just for reference: the relevant upstream issue appears to be https://github.com/raspberrypi/firmware/issues/1286
(and https://github.com/raspberrypi/firmware/issues/719 is also partially relevant).

Upstream response is there is no such tag to obtain the bootmode register using mailbox.
So we could check from u-boot if there's no sd-card with a BalenaOS image and consider uboot has been loaded from usb, or program any of the other 8 customer registers and check from there, etc.

Closing this PR since upstream developers confirmed firmware does not support querying for this specific data.


Collapse multiple expression lines into one in Variable panel.

As far as I can tell, .debug-hover-widget never has ancestors .monaco-list-row .expression, so that should not actually be affected (and should probably be removed). I am also not sure why there are two rules for this in two separate files  right next to each other, maybe that can be cleaned up, too.
Fixes #212167.

I'm going to close this pending my comment in the issue, https://github.com/microsoft/vscode/issues/212167#issuecomment-2099724140


floormattress01 too long error??

JManny: pac>arena>floormattress>01  - tried extract in place. file too long error in newest version. tried in 2.2.8, worked

This does not appear to be an issue on the new release.  Please confirm with JManny reopen as needed.


Does this work with mainnet?

I'm trying to get current version https://github.com/freddiecoleman/chia-network-scanner/tree/270c769c4d4a0a90f83be211ae74195a84705dd1 to work, using the provided README.md example.
Here is my adaption for mainnet:
#!/usr/bin/env ts-node

import { ChiaNetworkScanner } from 'chia-network-scanner';

const chiaNetworkScanner = new ChiaNetworkScanner({
    // The network to scan and protocol to use
    network: {
        networkId: 'mainnet',
        protocolVersion: '0.0.32',
        softwareVersion: '1.0.3'
    },

    startNodes: [{
        hostname: 'introducer.chia.net',
        port: 8444,
    }],

    // Identifies this peer on the network
    peer: {
        nodeType: 1,
    },

    // Used to timeout on various operations such as handshake
    connectionTimeout: 20000,

    // Number of peers to scan concurrently. Bigger is faster but uses more sockets and memory :)
    concurrency: 50,

    // Full node public key
    keyPath: '/home/mynode/.chia/mainnet/config/ssl/full_node/public_full_node.key',

    // Full node public cert
    certPath: '/home/mynode/.chia/mainnet/config/ssl/full_node/public_full_node.crt'
});

// const peers = await chiaNetworkScanner.scan();
console.log("test");
const peers = chiaNetworkScanner.scan();
console.log("test2");

It fails on await/yield when const peers = await chiaNetworkScanner.scan();. Therefore i removed await.
But then it fails on the first handshake:

test
{"level":30,"time":1618061257044,"pid":481383,"hostname":"mynode","msg":"Starting scan of Chia Network"}
test2
{"level":30,"time":1618061257046,"pid":481383,"hostname":"mynode","visited":false,"hostname":"introducer.chia.net","port":8444,"timestamp":1618061257,"msg":"Visiting peer"}
{"level":30,"time":1618061257047,"pid":481383,"hostname":"mynode","visited":false,"hostname":"introducer.chia.net","port":8444,"timestamp":1618061257,"msg":"Establishing websocket connection"}
{"level":30,"time":1618061257047,"pid":481383,"hostname":"mynode","msg":"Attempting websocket connection to wss://introducer.chia.net:8444/ws"}
{"level":30,"time":1618061257785,"pid":481383,"hostname":"mynode","msg":"Established websocket connection to Chia node introducer.chia.net:8444"}
{"level":30,"time":1618061257785,"pid":481383,"hostname":"mynode","visited":false,"hostname":"introducer.chia.net","port":8444,"timestamp":1618061257,"msg":"Websocket connection established"}
{"level":30,"time":1618061257786,"pid":481383,"hostname":"mynode","msg":"Encoded handshake<PHONE_NUMBER>2c000000076d61696e6e657400000006302e302e333200000005312e302e3320fc010000000100010000000131"}
{"level":30,"time":1618061257786,"pid":481383,"hostname":"mynode","msg":"Sending 1 message"}
{"level":30,"time":1618061257952,"pid":481383,"hostname":"mynode","msg":"Received message of type 1"}
{"level":30,"time":1618061257952,"pid":481383,"hostname":"mynode","msg":"Decoded message to {\"network_id\":\"mainnet\",\"protocol_version\":\"0.0.32\",\"software_version\":\"1.0.3\",\"server_port\":8444,\"node_type\":5}"}
{"level":30,"time":1618061257952,"pid":481383,"hostname":"mynode","msg":"Encoded 43 2b0000000000"}
{"level":30,"time":1618061257952,"pid":481383,"hostname":"mynode","msg":"Sending 43 message"}
{"level":30,"time":1618061258119,"pid":481383,"hostname":"mynode","stack":"Error: 1\n    at WebSocket.ws.on (/home/mynode/git/typescript-node-minimal/node_modules/chia-network-scanner/MessageChannel.ts:77:61)\n    at WebSocket.emit (events.js:198:13)\n    at WebSocket.EventEmitter.emit (domain.js:448:20)\n    at WebSocket.emitClose (/home/mynode/git/typescript-node-minimal/node_modules/ws/lib/websocket.js:198:10)\n    at TLSSocket.socketOnClose (/home/mynode/git/typescript-node-minimal/node_modules/ws/lib/websocket.js:886:15)\n    at TLSSocket.emit (events.js:203:15)\n    at TLSSocket.EventEmitter.emit (domain.js:448:20)\n    at _handle.close (net.js:607:12)\n    at TCP.done (_tls_wrap.js:388:7)","type":"Error","msg":"Connection closed"}
{"level":50,"time":1618061277953,"pid":481383,"hostname":"mynode","stack":"Error: introducer.chia.net:8444 did not respond after 20.00 seconds. Bailing.\n    at Timeout.setTimeout (/home/mynode/git/typescript-node-minimal/node_modules/chia-network-scanner/PeerConnection.ts:119:53)\n    at ontimeout (timers.js:436:11)\n    at tryOnTimeout (timers.js:300:5)\n    at listOnTimeout (timers.js:263:5)\n    at Timer.processTimers (timers.js:223:10)","type":"Error","msg":"introducer.chia.net:8444 did not respond after 20.00 seconds. Bailing."}
fin introducer.chia.net:8444 null

https://github.com/freddiecoleman/chia-network-scanner/blob/main/encoder.ts#L7-L8
You can replace it with
request_peers: 63,
respond_peers: 64


Add reactive java app version

hey @antonputra , this is my pr of the reactive version of the java app for the lesson 201, which is a comparison between quarkus (java) and golang (fiber). I think I covered most of the blocking part. There is only the AtomicInteger usage, which is indeed thread safe but replacing with UUID can increase perfomance. I do still want to try the vertx Counter which is a properly way to have an atomic counter in a vertx/reactive environment.
for now, I think it can be already used
btw, Is there any problem changing the key of image file from using a counter to use an uuid as follow?
String imgKey = "java-thumbnail-" + UUID.randomUUID() + ".png";
Image img = new Image(imgKey);

thanks for your working with all these benchmarks!!

Thanks @ericsouza for the PR, let me test it and i'll merge

Thanks @ericsouza for the PR, let me test it and i'll merge

Thanks!
If you don't see a big difference, please consider removing the counter used by the upload method and replacing with an uuid string


Ra3 Bridge connection - Crashes homebridge upon booting

Describe The Bug:
Plugin crashes upon reading RA3 "devices" properties
To Reproduce:
Connect Caseta leap plugin to RA3 Controller
Expected behavior:
Boot without crashing and inventory devices, as it does with Caseta and RA2 Select
Logs:
[5/24/2023, 5:09:46 AM] [Lutron] got request to add bridge 04e58ac4
TypeError: Cannot read properties of undefined (reading 'Devices')
    at SmartBridge.getDeviceInfo (/homebridge/node_modules/homebridge-lutron-caseta-leap/node_modules/lutron-leap/src/SmartBridge.ts:135:53)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[5/24/2023, 5:09:46 AM] [Lutron] Child bridge process ended

Plugin Config:
   {
            "name": "Lutron",
            "platform": "LutronCasetaLeap",
            "options": {
                "filterPico": false,
                "filterBlinds": false,
                "clickSpeedDouble": "default",
                "clickSpeedLong": "default"
            },
            "secrets": [
                {
                    "bridgeid": "04E58AC4",
                    "ca": "-----BEGIN CERTIFICATE-----
                         \n-----END CERTIFICATE-----\n",
                    "cert": "-----BEGIN CERTIFICATE-----
                                 n-----END CERTIFICATE-----\n",
                    "key": "-----BEGIN RSA PRIVATE KEY-----
                                  -----END RSA PRIVATE KEY-----\r\n"
                }
            ],
            "_bridge": {
                "username": "0E:99:2C:7C:FC:C1",
                "port": 55365
            }

Screenshots:

Environment:

Plugin Version:
Homebridge Version: <1.6.1 (latest)>
Node.js Version:
NPM Version:
Operating System: <!-- Raspbian

Hi @NBerk2 this crash is not a great one, and I'm sorry it's happening to you. I don't have a quick fix, but as a workaround, you can remove the secret entry for the RA3 processor, as it's not supported by this plugin. I've got plans (and a fair pile of code) to enable future support for non-Caseta devices, but it's not available yet.

All good, I realized post submission that bug, was a mistake and feature request was the more accurate submission but could not change it after the fact.
While contributing HW is not doable for me personally, if I can facilitate in any way I’d be happy to do so. Appreciate the work done thus far in your plugin.
Thank you for the follow up!
On May 24, 2023, at 10:28 PM, Brandon Matthews @.***> wrote:

Hi @NBerk2https://github.com/NBerk2 this crash is not a great one, and I'm sorry it's happening to you. I don't have a quick fix, but as a workaround, you can remove the secret entry for the RA3 processor, as it's not supported by this plugin. I've got plans (and a fair pile of code) to enable future support for non-Caseta devices, but it's not available yet.
—
Reply to this email directly, view it on GitHubhttps://github.com/thenewwazoo/homebridge-lutron-caseta-leap/issues/110#issuecomment-1562204730, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6774DP3K4PJODH2MACBPPTXH3GULANCNFSM6AAAAAAYM2LW3E.
You are receiving this because you were mentioned.Message ID: @.***>


Decouple dmod.scheduler from Docker

dmod.scheduler has a firm dependence on Docker, which makes sense considering that this is a product that operates through Docker. The hard coupling, however, makes it difficult, if not nigh impossible, to inject an alternative of some sort.
The parts that directly link to Docker should be abstracted out into a common base class with the docker implementation defined within another module. That module should then be referenced dynamically so that dmod.scheduler may be loaded into memory, even on systems without access to docker.
The scope of this issue does not extend to creating alternate implementations. That should be in a task that may be completed after this step.

dmod.scheduler has a firm dependence on Docker, which makes sense considering that this is a product that operates through Docker.

dmod.monitor is in this camp and to an extent the dmod.dataservice.

The parts that directly link to Docker should be abstracted out into a common base class with the docker implementation defined within another module.

To be fair, the concept of a Job is abstracted from Docker Swarm concepts (i.e. services and tasks). The dmod.scheduler is a service, and I think it is up for debate how generic / configurable a service should be. However, point taken.
The difficulty in this problem is not Docker or Docker Swarm, but exposing data to the computational environment. So, in our case, getting data from the dataservice mounted into one or more swarm services (Jobs that require mpi, each mpi "node" is a separate swarm service). So, going from minio -> s3 docker volume -> running swarm service task.
In our current architecture, the dataservice is aware of the computational environment, in that it knows how to create a volume that is compliant and usable by the scheduler. Adding an abstraction to the scheduler over the current docker swarm implementation will not address this issue.

The metric of success here is the ability to write another implementation of some of this logic so that docker may be avoided and for an instance of a configured ngen to run sans container. Let's call it the 'dumb implementation'. Job may not be the correct piece of the puzzle (neither dmod.scheduler nor dmod.monitor are my area of expertise), but the thing that launches and tracks ngen execution needs to be able to support a non-docker environment and preferably a laptop/desktop environment (although this mode of play should never be the version deployed anywhere).
The concept behind the idea isn't really the point; it's the mechanics. The mechanics just need to be able to support the base/dumb/idiotic case all around. For instance, the dataservice shouldn't be a primary docker product either, just a product that can (and probably should) use docker).  Liken it to Django - when running locally, it doesn't require gunicorn or nginx, but, when deploying it, it better use a reverse proxy/load balancer and attached webserver. Or imagine using the type hint of typing.MutableMapping - 90% of the time that's just another way of saying dict, but another implementation of a mutable mapping may come along that needs support, yet looks the exact same.
If implemented right, it'll be non-trivial but possible to switch out the used docker implementation for an implementation that can play with a K8 API.

The JobManagerFactory requires a Launcher object that is tightly coupled to docker (parent class is even SimpleDockerUtil) and requires the passing of things like hard coded image names (magic strings are sort of another no-no as well).
Forming a means of breaking Launcher objects away from docker functions will probably achieve this. Imagine having stuff like a LocalLauncher, K8Launcher, CloudLauncher, MockLauncher, and DockerLauncher.

@christophertubbs, I get what you are saying that there is a need for a workload management abstraction. What i'm trying to convey is that the operations a workload management abstraction should handle are split between the scheduler and the monitor service and how to generically provide data to a workload management abstraction is unclear.

Forming a means of breaking Launcher objects away from docker functions will probably achieve this. Imagine having stuff like a LocalLauncher, K8Launcher, CloudLauncher, MockLauncher, and DockerLauncher.

Not sure exactly when Launcher became a subclass (it started out as its own base class).  But wouldn't be too difficult to build a basic ABC and pull the docker specific pieces into its own subclass.
This has been on the wish list for some time, along with deployment support for different backends (e.g. control_stack options for deploying dmod on different systems)

To that point, @hellkite500, if we do go down this road, I think there is a strong argument to combine the some of the functionality of the scheduler and the monitor services. If we were to go that route, I think we can generalize the concept of scheduling and monitoring making it easier to support and maintain existing backends and introduce different backends if needed in the future.


ISPN-13590 include source.version field in migrator example

https://issues.redhat.com/browse/ISPN-13590
Needs backport to 13.0.x

Thanks @oraNod


Update README Shell wallet

@twhy In this PR we updated README file. Can you review it for us?
Also, it has been more than a week since we updated the new README file but it has not been published on npm yet. Can you please check this case for us again?
Thank you in advance.

@BusinessShellWallet https://www.npmjs.com/package/@cosmos-kit/shell It has been updated.

Thank you so much! @twhy


return empty search

Search containing only a "space" should return an empty results page, not error page...
@Mitso Please review
Before

After

:100: pretty cool!


apply clusterstack resource once the CRDs are applied

/kind feature
In discussion with @janiskemper we discussed that we should apply the clusterstack resource using a button on the top. As of now, we apply it too early and we apply it every time tilt starts. This issue tracks the same.

Ref: https://github.com/SovereignCloudStack/cluster-stack-provider-openstack/pull/88#discussion_r1490940100
tracking of openstackrelease should be removed from tilt and then we should apply it in the next step.

I think this is done now, closing this one.
Implemented via https://github.com/SovereignCloudStack/cluster-stack-provider-openstack/pull/88


LogServerSignatureResult.Invalid.SignatureFailed

Started getting Invalid Signature  for the same domain which was working fine until yesterday.
Seems like version 1 log_list stops working https://www.gstatic.com/ct/log_list/log_list.json
When I tried with version 2 log_list URL it is working fine as expected https://www.gstatic.com/ct/log_list/v2/log_list.json
@mattmook Please help me out

Both should work, although we should all migrate to the v2 schema. I don't know if/when the v1 schema will be removed.
Indeed with the latest release of this library, v0.2.0, we have removed support for the v1 schema completely.
What version of the library are you using and what is the domain you are hitting so I can try to replicate this.

I experienced same issue earlier today:Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature) while I was running certificatetransparency-android:0.1.4
However, it did suddenly work again around 2019-08-22 00:14:15 CET.
Have any log server been unavailable today?

@mattmook As @pholst mentioned we are also using the same version certificatetransparency-android:0.1.4
You may be aware I have raised issue in google group as well after the discussion it started working we have no idea about the root cause yet.
Ref : https://groups.google.com/d/msg/certificate-transparency/zZwGExvQeiE/3GAOK2WvDgAJ

I saw the discussion in the Google Group, there are a couple of things that might have happened.
firstly at a point in time the json and sig files may have been out of sync. we don't know how long this happened for if it even happened. with that regard, there's not much we can do about that.
secondly though, the library could have inadvertantly cached one of those files out of sync with the other. any issue could have persisted for longer than the files were actually out of sync. as such I'm going to re-evaluate how caching is working for these files and ensure there are suitable tests to reduce issues like this and ensure if they do occur they don't persist for long.

@mattmook Thanks for the evaluation.
I'm afraid this can be applicable for updated library certificatetransparency-android:0.2.0(version 2 schema) also
Note: We have tested the incident more than 4 different devices & everything gives me the same result.

I recently added this library and things were working fine. Starting today, cert transparency is failing:
Failure: Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature)

we are sporadically getting the same thing too using 0.2.0
 Failure: Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature)

I recently added this library and things were working fine. Starting today, cert transparency is failing:
Failure: Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature)
I'm using version 0.2.0 of the library.
Looking further, it seems to be an issue with the Signature class failing verification of the log_list.json . I found this thread and I'm having issues with the exact thing.

This issue is no longer happening. It's very scary that one moment it works and then another it doesn't.

I recently added this library and things were working fine. Starting today, cert transparency is failing:
Failure: Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature)
I'm using version 0.2.0 of the library.
Looking further, it seems to be an issue with the Signature class failing verification of the log_list.json . I found this thread and I'm having issues with the exact thing.

This issue is no longer happening. It's very scary that one moment it works and then another it doesn't.

Exact same thing happened to us. It came and then went. This is the second time we randomly saw a sudden spike in errors. We have debated whether to take out this library of our app but we don't want to sacrifice security. We are going to do that as a very last resort. After this second spike in incidents, we have decided to have a way to remotely enable or disable this feature.
Here is an example of our Kotlin code for our app:
Interceptor certificateTransparencyInterceptor = new Interceptor() {
    private Interceptor _certificateTransparencyInterceptor =
        new CTInterceptorBuilder()
            .includeHost("*.example.com")
            .setLogger(new BasicAndroidCTLogger(BuildConfig.DEBUG))
            .build();

    @NonNull
    @Override
    public Response intercept(@NonNull Chain chain) throws IOException {
        // FeatureFlag is a class we made that wraps a remote feature flag toggle service
        if (FeatureFlag.CERTIFICATE_TRANSPARENCY.isEnabled()) {
            return _certificateTransparencyInterceptor.intercept(chain);
        } else {
            return chain.proceed(chain.request());
        }
    }
};

// Some example client
OkHttpClient exampleOkHttpClient = getClient().newBuilder()
    .addNetworkInterceptor(certificateTransparencyInterceptor)
    .build();

As I previously mentioned, I recently added this library and when doing so, I added logs with CTLogger to capture NoCertificates, is LogServersFailed, NoScts, is TooFewSctsTrusted, is UnknownIoException in our codebase. These logs are sent to our application monitor. After encountering this issue, I reviewed my logs and found the same issue has happened a few other times:

Jan 22, 2020 7:50:49 AM UTC
Jan 30, 2020 10:17:36 AM UTC

It has occurred on various devices and OS versions.

We saw the same spike on Jan 30 and Feb 5. Interesting!

Having faced the same issue today our investigation concluded that the problem was on the wrong certificate transparency log was served by https://www.gstatic.com/ct/log_list/v2/log_list.json .
We described the issue here https://github.com/google/certificate-transparency/issues/1476 if you want to go in detail.
TLDR The library is requesting le log list with a header Accept-Encoding: Gzip which gives back a cached version of the log list.
The cache expired in 24 hours and now things are in their place. I imagine this will happen again. We could either explicitly remove the header added in the library or rely on the log list to be next time updated  simultaneously for both cases, or just wait for the cache to expire.
https://github.com/babylonhealth/certificate-transparency-android/pull/39 is a welcomed addition I don't think it fixes the problem.

@vivascu Removing the header is not enough. The non gzipped "version" is also cached and can also diverge from the .sig file. Right now fetching the signature and json from gstatic is fundamentally broken because their cache lifetimes are not the same.

It looks like Google has attempted to fix the caching problem by creating a zip file containing the files: https://github.com/google/certificate-transparency/issues/1476. @mattmook I was curious if the library needs to be updated to use this zip or not.

@blinkmacalahan yes it will require an update, I’ve got a PR ready but just doing some more testing on it first before I hit merge. https://github.com/babylonhealth/certificate-transparency-android/pull/49


Numpy runtime error

Hi, I'm getting this error even though numpy is installed on my system. Any ideas? Thank you.
/home/krysztof/.local/lib/python3.11/site-packages/torch/cuda/_utils.py:24: UserWarning: Failed to initialize NumPy: module compiled against API version 0x10 but this version of numpy is 0xf (Triggered internally at ../torch/csrc/utils/tensor_numpy.cpp:77.)   device = torch.device(device) Extracting audio from Quartetto Italiano (documentario - 2005)... Generating subtitles for Quartetto Italiano (documentario - 2005)... This might take a while. Traceback (most recent call last):   File "/home/krysztof/.local/bin/auto_subtitle", line 33, in <module>     sys.exit(load_entry_point('auto-subtitle==1.0', 'console_scripts', 'auto_subtitle')())              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/home/krysztof/.local/lib/python3.11/site-packages/auto_subtitle/cli.py", line 43, in main     subtitles = get_subtitles(                 ^^^^^^^^^^^^^^   File "/home/krysztof/.local/lib/python3.11/site-packages/auto_subtitle/cli.py", line 99, in get_subtitles     result = transcribe(audio_path)              ^^^^^^^^^^^^^^^^^^^^^^   File "/home/krysztof/.local/lib/python3.11/site-packages/auto_subtitle/cli.py", line 44, in <lambda>     audios, output_srt or srt_only, output_dir, lambda audio_path: model.transcribe(audio_path, **args)                                                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/home/krysztof/.local/lib/python3.11/site-packages/whisper/transcribe.py", line 84, in transcribe     mel = log_mel_spectrogram(audio)           ^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/home/krysztof/.local/lib/python3.11/site-packages/whisper/audio.py", line 112, in log_mel_spectrogram     audio = torch.from_numpy(audio)             ^^^^^^^^^^^^^^^^^^^^^^^ RuntimeError: Numpy is not available

Oh never mind, seems that the distro package manager had installed an older numpy. Deleting that and installing through pip again did the trick.


fix: correct the consistency checker's config "type" validation

Some small corrections to the consistency checker's validation of the type field in config:

"integer" is not valid (at least in Juju 3.4.0), so remove it
"number" is not valid (at least in Juju 3.4.0), so remove it
"float" is missing, so add it
This is currently undocumented (that should be fixed soon) but "type: secret" is valid from Juju 3.4 onwards, so add it (conditionally on the Juju version)

Adjust tests to match.
See also canonical/operator#1166 for type:secret issue in Harness.

Oh, and thanks for this, Tony -- appreciated!


Update gfx-rs, and fix some window names

My gfx-rs fork's master is synced with main, but uses debug-utils (which I have submitted a PR for on gfx-rs main). Pretty soon, we can just point to gfx-rs directly!

(actually, this PR is a work in progress, since I just realized a bunch of stuff is broken)


Warning TraktApi was never awaited

Since the upgrade to Home Assistant 2024.1, we are now getting the following warning with Trakt-Integration 0.8.6:
2024-01-10 09:05:28.180 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:256: RuntimeWarning: coroutine 'TraktApi.fetch_upcomings' was never awaited
  return await self.update_method()

2024-01-10 09:05:28.181 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:256: RuntimeWarning: coroutine 'TraktApi.fetch_recommendations' was never awaited
  return await self.update_method()

2024-01-10 09:05:28.181 WARNING (MainThread) [py.warnings] /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:256: RuntimeWarning: coroutine 'TraktApi.fetch_next_to_watch' was never awaited
  return await self.update_method()

Let me know if I can help testing.
Thanks

Fixed v0.8.7

Thank you.  Works!


Failed to Build :Type Error/[locale]/[workspaceid]/layout.tsx

./app/[locale]/[workspaceid]/layout.tsx:97:19
Type error: Argument of type '{}[]' is not assignable to parameter of type 'SetStateAction<never[]>'.
  Type '{}[]' is not assignable to type 'never[]'.
    Type '{}' is not assignable to type 'never'.

   95 |
   96 |     const assistantData = await getAssistantWorkspacesByWorkspaceId(workspaceId)
>  97 |     setAssistants(assistantData.assistants)
      |                   ^
   98 |
   99 |     for (const assistant of assistantData.assistants) {
  100 |       let url = ""

This problem occurs when doing npm run build or Deploy to Vercel.

@seabite  did u figure this out?
when i build i get
'Type error: Object literal may only specify known properties, and 'assistant_id' does not exist in type '{ chat_id: string; content: string; created_at: string; id: string; image_paths: string[]; model: string; role: string; sequence_number: number; updated_at: string | null; user_id: string; }'.'

I get the same issue

You can mitigate this for your existing Supabase messages table by executing:
ALTER TABLE messages ADD assistant_id uuid
through your Supabase client dashboard: http://localhost:54323/project/default/sql/1


Added confirm-email

I did not see this PR before I started working on #4. I think we can close this one in favor of #4.
cc: @amitu @Arpita-Jaiswal


fix: skip process gateways for gatewayclass with merge gateways enabled but marked as deleted

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #2637

hey @shawnh2 tring to better understand the issue and fix, can you help outline all the steps.
Its unclear to me why this issue is specific to mergeGateways and skipping processing
of gateways means we'll never we able to clean them up (if a GatewayClass was deleted before a Gateway)

Discussed this in today's community meeting, this fix will introduce another bug: the Gateways will not be deleted with this fix.
The expected behaviour should be if we remove GatewayClass before Gateways, the merge-gateways features should not be failed.

Fow now, if we deleted GC first, merge-gateways feature will not fail.
But if we trying to delete all the resources (including GC, EnvoyProxy, GTWs, Routes), the finalizer of GC will not be removed. Because the EnvoyProxy got deleted before GC, this will casue controller to raise a reconcile error in here:
https://github.com/envoyproxy/gateway/blob/607d8bcd9a833841eee057b263c0bdc06de0fbea/internal/provider/kubernetes/controller.go#L238
and return, skip the finalizers check logic in here:
https://github.com/envoyproxy/gateway/blob/607d8bcd9a833841eee057b263c0bdc06de0fbea/internal/provider/kubernetes/controller.go#L288

So IMO the fix here will be: introduce a finalizer for EnvoyProxy
Since the EnvoyProxy is a parameterRef of GC, the EnvoyProxy should not be deleted if it got GC associated with it.

I can help you out there, I was thinking about refactoring it and bringing this topic back

I can help you out there, I was thinking about refactoring it and bringing this topic back

I can help you out there, I was thinking about refactoring it and bringing this topic back

Great, thanks, so this fix will only concentrating on the merge-gateways should not fail if GC delete first part.

Awesome @shawnh2, I will make sure to test this one for you, as I have some examples lying around.
I did work on the finalizer before https://github.com/envoyproxy/gateway/issues/865 and I still think that it is worth bringing it back, now you have another point that supports this.

hold this, need to add finalizers for EnvoyProxy before resolving this.

looking into finalizer, will send the PR soon


Code actions from prisma-fmt

Closes: https://github.com/prisma/language-tools/issues/1181
Note: code action was implemented here https://github.com/prisma/prisma-engines/pull/3011

@pimeys apparently the character is shifted by +1 on Windows, any idea why?
https://github.com/prisma/language-tools/runs/7127920866?check_suite_focus=true#step:6:239
After that we can merge
 1) Quick Fixes
       from prisma-fmt
         @relation referenced side missing @unique:
      AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected ... Lines skipped
  [
    {
...
          range: {
            end: {
+             character: 55,
-             character: 54,
              line: 14
            },
...
              range: {
                end: {
+                 character: 12,
-                 character: 11,
                  line: 7
                },
                start: {
+                 character: 12,
-                 character: 11,
                  line: 7
...
      title: 'Make referenced field(s) unique'
    }
  ]

On windows the newline is \r\n and everywhere else it's \n. There you get the extra character.

I'm working on detecting the newline, so we can add the correct one to the change text.

Now we have a prisma format problem
      -  id    Int     @id @default(, autoincrement())
      +  id    Int     @id @default(autoincrement())

https://github.com/prisma/language-tools/runs/7184531718?check_suite_focus=true
this schema
https://github.com/prisma/language-tools/blob/main/packages/vscode/fixtures/format/schema.prisma
Is expected to match the following result
https://github.com/prisma/language-tools/blob/main/packages/vscode/fixtures/format/expected.prisma
But somehow prisma format decided now to do this
id    Int     @id @default(, autoincrement())
instead of
id    Int     @id @default(autoincrement())


Add picture with width or height, whichever is greater

My idea is to confine too wide or too long images.  I've already done that, and it works fine:
import requests
from docx.image.image import Image, _ImageHeaderFactory

def get_binary_image(image_url):
    response = requests.get(image_url)
    binary_img = io.BytesIO(response.content)
    return binary_img

# Some code here to initialise paragraph `p`

binary_img = get_binary_image(sn)
image_stream = Image(None, None, _ImageHeaderFactory(binary_img))
if image_stream.width > image_stream.height:
    p.add_run().add_picture(binary_img, width=Inches(2))
else:
    p.add_run().add_picture(binary_img, height=Inches(1.5))

My question is: Is it the most efficient way to implement that?

Seems pretty straight forward..
You have a function that grabs the binary image and then your conditionally checking the width to then add to a paragraph. - I would leave it.
I would suggest closing the issue and asking the question on stackoverflow and tagging the question against python-docx if your not happy with your code.


warning in MainActivity.java after suggested changes

Note: D:\addlance\android\app\src\main\java\io\ionic\starter\MainActivity.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
This warning is showing during app run via android studio.
Note:- I am using same code as suggested in MainActivity.java file.

can you please try on latest capacitor + plugin ?


Multilingual setup / hreflang

Hi there,
there are quite a few issues about this in plugin repositories, but as it's something with Grav itself I would like to post it here.
It seems like there is currently no way to directly link an hreflang tag from a page to its counterpart(s) in other languages when there is a translated slug. Grav only loads one language at the time and thus uses the raw route for langswitching or building hreflang tags by plugin.
Google on the other hand wants us to have the hreflangs between the final URLs, not redirects and I believe this could be a dealbreaker for quite a few people that would love to use Grav but can't for this reason - at our agency it is.
http://www.thesempost.com/google-dont-link-hreflang-redirecting-urls/
I'm not deep enough into Gravs Core Architecture but it would be great to have some people discuss this

I've just noticed this now too. In the sitemap plugin only the main language slug shows for the other language's page(s) which is not expected behaviour.

This is a duplicate based on the fact that this is how Grav's multilang is able to be flexible and still performant: https://github.com/getgrav/grav/issues/1695#issuecomment-337585687


SD-420 Spring Security authentication and authorization

This Pull Request adds authen/authorization with Spring Security.
strongbox-security-context.xml sets up two providers

one that uses custom implementation based on OrientDB (first time using OrientDB, so be kind! :-) )
one that uses simple provider with hardcoded users in the context.xml

To add other types of providers see the links in the .xml file.
To add more security:

add more <security:intercept-url> entries in the context.xml and define which roles are allowed/denied to reach them
provide REST APIs to add/edit/remove users (with roles)

At the moment there are two demo users:

martin/agent007 - an Admin user who is allowed to open /configuration/strongbox/xml
james/bond - a normal (i.e. non-admin) user who is allowed to open any REST endpoint but /configuration/strongbox/xml


Decoder auto-detection

I have a use-case where I don't know the compression of a file up-front. It would be nice if there was a way to use this crate to figure out the compression algorithm based on the magic number at the beginning of the compressed file.

A PR is welcomed, I am aware of crates doing such thing (IIRC it's called file-format, it has many breaking releases due to the enum), but just not sure whether it can be trusted for such use case.
Maybe we should build a generic one, that enables user to plug in their own implementation?


IP Enrichment master playbook creation

Created IP Enrichment master playbook
Change(s):

added nested playbook GeoIP
added nested playbook HYAS Insights
added nested playbook Recorded Future
added nested playbook RiskIQ
added nested playbook Virus Total

Hi @ospeka
Can you please incorporate the changes requested by anki-narravula
Thanks

Maintain the similar naming convention for all the nested playbooks

Can you show me example of wrong naming?

/MasterPlaybooks/IP-Enrichment/HYAS_Insights-IP-Enrichment/readme.md

Prerequisites and some other sections are missing in readme
RecordedFuture-IP-Enrichment \ readme

Prerequisites and some other sections are missing in readme
VirusTotal-IP-Enrichment \ readme

"Post deployment" steps are missing

This issue will be solved via email.

Maintain the similar naming convention for all the nested playbooks

Can you show me example of wrong naming?

/MasterPlaybooks/IP-Enrichment/HYAS_Insights-IP-Enrichment/readme.md

Prerequisites and some other sections are missing in readme
RecordedFuture-IP-Enrichment \ readme

Prerequisites and some other sections are missing in readme
VirusTotal-IP-Enrichment \ readme

"Post deployment" steps are missing

This issue will be solved via email.

Hi @ospeka -
For example below are current names. We can give same naming structure like I have given below example
Current

Enrich-Sentinel-Incident-HYAS-Insight-IP-C2-Attribution
RecordedFuture-IOC_Enrichment-IP_Domain_URL_Hash
RiskIQ-Data-Whois-Ip
Get-VirusTotalIPReport

New can be

< Device Name >-< Action >-< Nested >
HYASInsight-IP_C2-Enrichent-Nested
RecordedFuture-IP_Domain_URL_Hash-Enrichment-Nested
RiskIQ-Ip-Whois-Enrichment-Nested
VirusTotal-IP-Report-Enrichment-Nested

@ospeka Please look into the feedback provided.
Thanks

@ospeka Please look into the feedback provided. Thanks

PR updated in this commit in accordance to provided comments.
https://github.com/Azure/Azure-Sentinel/pull/5557/commits/02eb42528ac5186ea213f62c0d944182f05f384b


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 0deb8e0:
:clock10: Pending: waiting for processors (36 builds ahead of you)
:warning: Docs Build is busy, currently there are 36 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 0deb8e0:
:clock10: Full build: the average full build time is 6 min(s) 13 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 0deb8e0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Center text configuration

Some people requested if it's possible to have the text centered.

Done!


Update DeveloperGuide (CrimeCase: package, adding, deleting, finding by name)

Pull Request Test Coverage Report for Build 329

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.119%

Totals

Change from base Build 323:
0.0%

Covered Lines:
2567

Relevant Lines:
3204

💛  - Coveralls


Move ShardedDeviceArray and DeviceArray to top-level jax namespace

Simple use-case:
assert(isinstance(x, jax.pxla.ShardedDeviceArray))
is only possible with internal API.

This is long fixed by jax.Array!


Invalid hook call

I get this when trying to use the hooks. The default render props works fine though:
Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
▶ 2 stack frames were collapsed.
useClearCache
src/index.tsx:13
  10 | export function useClearCache(props: OwnProps = {}) {
  11 |   const { duration = 60 * 1000, auto = false } = props;
  12 |
> 13 |   const [loading, setLoading] = React.useState(true);
  14 |   const [isLatestVersion, setIsLatestVersion] = React.useState(true);
  15 |   const useAppVersionState = createPersistedState('appVersion');
  16 |   const [appVersion, setAppVersion] = useAppVersionState('');
View compiled
App.render
src/App.js:14
  12 | }
  13 |
> 14 | render() {
     | ^  15 |   const { isLatestVersion, emptyCacheStorage } = useClearCache();
  16 |   return (
  17 |

I have checked this and I only have one react installed and both react and react-dom is v16.12.0
https://reactjs.org/warnings/invalid-hook-call-warning.html
This is my whole app.js:
import React, { Component } from 'react'
import './App.css'
import './print.css';
import MainPage from './mainPage'
import { useClearCache } from "react-clear-cache";

class App extends Component {
  render() {
    const { isLatestVersion, emptyCacheStorage } = useClearCache();
    return (

          {!isLatestVersion && (

               {
                  e.preventDefault();
                  emptyCacheStorage();
                }}
              >
                Update version

          )}

        <MainPage />

    )
  }
}

export default App;

Ok defining as suggested by the readme works so I guess it's just me using the hooks wrong. Would be nice to understand why though.
import React from 'react'
import './App.css'
import './print.css';
import MainPage from './mainPage'
import { useClearCache } from "react-clear-cache";

const App: React.FC<{}> = () => {
  const { isLatestVersion, emptyCacheStorage } = useClearCache({'auto':true});
  return (

        {!isLatestVersion && (

             {
                e.preventDefault();
                emptyCacheStorage();
              }}
            >
              CLICK TO LOAD LATEST VERSION

        )}

      <MainPage />

  );
};

export default App;

hi @Joohansson , sorry for delayed response. Anyway, you can't use hooks inside a class. Please check this faq. https://reactjs.org/docs/hooks-faq.html#should-i-use-hooks-classes-or-a-mix-of-both


Drafting generic issuer implementation

Summary

Release Note

Documentation

@cpanato, the motivation is to simplify CI/CD OIDC provider onboarding. Rather than have each OIDC provider have to modify code to add a new provider, they instead should only need to modify a configuration file which will contain the mapping between OIDC claim and x509 extension value.

@cpanato, the motivation is to simplify CI/CD OIDC provider onboarding. Rather than have each OIDC provider have to modify code to add a new provider, they instead should only need to modify a configuration file which will contain the mapping between OIDC claim and x509 extension value.

that is nice! thanks for the clarification

Once this PR is ready for review and all comments addressed, can you post here?

Once this PR is ready for review and all comments addressed, can you post here?

Hey @haydentherapper, could you take a look?

In terms of release, I'm planning to cut 1.5 from before this PR, then we'll merge this and the other related changes and cut v1.6


Still Place order when current price is over ATH

Hi Chrisleekr,
i have an issue with ATH when current price is over ATH restricted price, the bot is still place buy order. how to do resolve ?

Did you enable auto trigger buy?

Did you enable auto trigger buy?

would it will be better if there is an option to still check the ATH restriction before executing this feature?

@azorpax Well, that defeats the purpose of auto-trigger buy. The purpose of auto-trigger buy is to purchase the coin for following the rise.

@azorpax Well, that defeats the purpose of auto-trigger buy. The purpose of auto-trigger buy is to purchase the coin for following the rise.
yes i get that. i think the auto trigger will still be beneficial because it will still be triggered without the need of hitting the buy trigger price. its just the ATH price that i think we should have an option to avoid. Lets just resched the auto trigger timer if it wasnt able to trigger because of the ATH restriction.

@azorpax Right, so rescheduling auto-buy trigger until it's under the ATH. Sounds like enhancement rather than a bug. Let me put it in the TODO list.
@thanhtran72085 Could you please confirm you enabled the auto-buy trigger? If yes, you can close the issue because that is not a bug.

Did you enable auto trigger buy?

I confirm, i don't enable this function, i saw many this issue.

@thanhtran72085
Again, please follow the bug template. You will need to provide more information to find out what happened.
I cannot tell what is going on with just one screenshot.
Are you saying, you didn't enable the auto-trigger buy, but the bot automatically purchase?
What are your settings? Can you provide a setting?
Have you set up Slack? What messages did you receive in Slack?
Have you tried to see the log?

Hi Chrisleekr,
In fact, I never enable "auto-trigger buying", bad news as i don't screenshot the setting at that time, i have Slack logging, can you see them as bellow:

@thanhtran72085
Are you still experiencing the bot is automatically placing an order without enabling "Auto trigger buy"?

@thanhtran72085
Are you still experiencing the bot is automatically placing an order without enabling "Auto trigger buy"?

@thanhtran72085
Are you still experiencing the bot is automatically placing an order without enabling "Auto trigger buy"?

I don't see this issue again, now, if i see it again, i will screenshot and send you slack logging.

Ok. Please close the issue and re-open it when it happens.


[ENHANCEMENT]  Add information for Scaleway on their various datacentres

I'm creating this issue here because I've tried emailing directly, asking the Scaleway Slack, asking on Twitter, and I haven't had any responses back yet and multiple users have got in touch with us asking to mark them as Green.
Their report linked below (along with their sustainability page) seems to suggest they would qualify, but I can't find the independent third party confirmation we need.
This is a slightly abridged version of the email I sent to their<EMAIL_ADDRESS>account.

I am raising a support request as a customer because I have a few questions about Scaleway's sustainability measures that I can’t find from the website or from reading various reports.
I asked about this on August 18th, in the #community channel on the scaleway slack, and I think my colleague Justine (cc’d in ) has also asked about some of this too.
You can see the link to my question in the scaleway customer support slack - https://scaleway-community.slack.com/archives/C7Z76CCUE/p1660815196586619
Confirming 100% renewable power, and pointing to the independent audit or attestation of the supply
We maintain a directory of services and providers of hosting on our website, where we point to providers of hosted services using green energy. We also use your services ourselves for object storage, and occasionally compute.
While we can find information for the French regions, we want to mark Scaleway as green but we haven’t been able to find any independent audit, or information attesting that the energy for the Warsaw and Amsterdam datacentres run on energy where the emissions are accounted for.
For reference this page here outlines the criteria we use, and the evidence we look for:
https://www.thegreenwebfoundation.org/what-we-accept-as-evidence-of-green-power/
I see a mention of guarantees of origin and certificates in the report on page 15 of the Scaleway CSR report linked below:
https://www-uploads.scaleway.com/Impact_Report_All_Pillars_EN_3fd59b985a.pdf?updated_at=2022-07-04T12:16:38.190Z
I have attached a copy of the document we have to account for the French datacentres.
Can you please point me to:
the equivalent certificates for the other datacentres, (we use the Amsterdam one ourselves, and we’d like to be able to point supporting evidence for the Warsaw one too)
Alternatively, some document from Advaes that we can link to providing independent confirmation of how the energy is sourced?
Many thanks
Chris

I'll add information here as I find it.
Here's the certificate for the French datacentre in Paris. We'd need the one for the Netherlands and Poland to be able to do the same linking to the supporting evidence for evidence that shows as being those regions
Certificat_Vert__Scaleway_2021-1.pdf

Brief update. I tried again with the support team, and they're working to escalate this to the right people internally now.

ok, that wasn't that helpful either.

Hello sir,
Thank you for your patience. I'm sorry about the situation. Support team doesn't handle such request. We will ask you to patiently wait for the email feedback. Best regards, ---- Ian FREMONT Customer Excellence Specialist Scaleway Dedibox / Elements

Time to resend the email I sent in October, I guess.

OK, that wasn't that helpful either.

Hello sir,
Thank you for your patience. I'm sorry about the situation. Support team doesn't handle such request. We will ask you to patiently wait for the email feedback.
Best regards, ---- REDACTED Customer Excellence Specialist Scaleway Dedibox / Elements

Time to resend the email I sent in October to the transparency address again, I guess.

I've had a couple of requests about the information I'm looking for since posting about this on Linkedin, so I'll outlined the specific things I'm looking for.
Scaleway's public comms uses this quote:

100% of electricity consumption in our global data centers has been supplied by wind power and hydroelectricity since 2017.

Now I know very few places are running true 24/7 hourly matched carbon free power for their own energy use, and our own critieria are based around being able to account on annual volumetric basis anyway (ie. so for 7000 MWh of power was used, you would need to provide information that showed you have accounted for all 7000 MWh of power).
We have evidence for the Paris DCs in the form a certificate, and we have the report to go on as further evidence we can use. But looking at the other countries it's less clear:

France - certificate from their power company
Poland - nothing yet
Netherlands - nothing yet

To mark all the DCs as green, assuming it's the same power provider used for all the DCs in each country, we would something similar for France. There is some mention of RECs from Alpiq and Enedis below on page 15 - perhaps these account for the other providers use?

OK, we have all this now - asking on LinkedIn put me in touch with the right people to get the third part assurance info we needed, and it should be linked below:
https://www.thegreenwebfoundation.org/green-web-check/?url=www.scaleway.com
I've added a screenshot taken just now to save clicking through


Enforce complete KDoc documentation

This is a question / feature request? to include support for enforcing complete / well-formed KDoc documentation as part of this plugin. Is that an option that you may consider?
Tried to find that kind of check in detekt and ktlint but couldn't find anything.
For example, if I have the following function, I'd love to get a warning as the @param is not added to the KDoc.
/**
 * Describes awesome API.
 */
fun awesomeApi(enabled: Boolean)

The well-formed KDoc should be 👇
/**
 * Describes awesome API.
 *
 * @param enabled set to true if you want to enable awesome API, false if not
 */
fun awesomeApi(enabled: Boolean)

Do you know any tools that perform this kind of enforcement? If not, is this something that could be integrated as part of the plugin?
Thanks a lot in advance and thanks for sharing this KDoc formatter plugin, it's really cool!

This feels like it should belong to the Kotlin plugin since you'd want this to be an IDE inspection, with configurable severity, an ability to suppress it, etc.
However, I should point out that this isn't actually something that the Kotlin coding conventions encourage; see
https://kotlinlang.org/docs/coding-conventions.html#documentation-comments
"""
Generally, avoid using @param and @return tags. Instead, incorporate the description of parameters and return values directly into the documentation comment, and add links to parameters wherever they are mentioned. Use @param and @return only when a lengthy description is required which doesn't fit into the flow of the main text.
// Avoid doing this:
/**

Returns the absolute value of the given number.
@param number The number to return the absolute value for.
@return The absolute value.
/
fun abs(number: Int): Int { /...*/ }

// Do this instead:
/**

Returns the absolute value of the given [number].
/
fun abs(number: Int): Int { /...*/ }

"""

Thanks so much for your quick response @tnorbye
Yeah that's exactly what I was looking at https://kotlinlang.org/docs/kotlin-doc.html#kdoc-syntax 🤔
Which is going to be even harder to confirm and enforce...
Maybe it doesn't make sense to enforce it at all 🤔
In any case, it feels it wouldn't belong to kdoc-formatter. I'm going to close here.
Thanks again!


After use "intended()" to assert the intent that attempt to launch other external activity, unable to continue next test

I hit an issue while I tried to use intended() to verify the intent that is been sent by my app.
In Espresso test, after I perform click in my app to launch other external activity with an intent (assuming I am trying to launch HTML Viewer to view a text file from my app), then Espresso works good while I use intended() method to verify the intent that I passed while launching the external activity. However, the problem is that after I called intended(), the app focus will not get back to my app and I will not be able to continue my next test method if they are in the same class. Is there any way I can work around it?

Yes, Am facing the same.

I've worked around this issue by using UiDevice.pressBack() to exit whatever activity or chooser has been presented. Note that you have to use UiDevice and not Espresso's pressBack method in order to interact with a component that is not part of your app's process.

Are you stubbing the Intent?
https://github.com/googlesamples/android-testing/blob/master/ui/espresso/IntentsAdvancedSample/app/src/androidTest/java/com/example/android/testing/espresso/intents/AdvancedSample/ImageViewerActivityTest.java
(pressBack() is not a good idea, do not go that way!)
And please don't use this issue tracker, it's just for issues related to the site.


Update rebar.config.script

Overview

Testing recommendations

Related Issues or Pull Requests

Checklist

[x] Code is written and works correctly
[x] Changes are covered by tests
[x] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

I'm not sure what you're trying to do here, but this doesn't look like an acceptable pull request, sorry.


Stability tests: add script to check results

147dda285fd4:firelens-stability wppttt$ bash check_results.sh us-west-2 2_31_11-E-2023-05-11T181755926-nuy7hnAc-ecs-firelens-stability-tests
Cluster: 2_31_11-E-2023-05-11T181755926-nuy7hnAc-ecs-firelens-stability-tests us-west-2
____GOLDEN PATH____
ecs-firelens-stability-tests-golden-path-no-onepod-low-throughput: 40
ecs-firelens-stability-tests-golden-path-onepod-low-throughput: 40
ecs-firelens-stability-tests-golden-path-onepod-low-throughput-real: 5
ecs-firelens-stability-tests-golden-path-no-onepod-high-throughput: 40
ecs-firelens-stability-tests-golden-path-onepod-high-throughput: 40
____S3 stability____
ecs-firelens-stability-tests-s3-stability-s3-throughput-1mbps: 40
ecs-firelens-stability-tests-s3-stability-s3-throughput-30mbps: 40
____S3 sensitivity____
ecs-firelens-stability-tests-s3-sensitivity-s3-control: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-outputPluginCount-10: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_compression-gzip: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_key_format-advanced: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-throughput-10mbps: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-total_file_size-1M: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-upload_timeout-1m: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-use_put_object-on: 5
147dda285fd4:firelens-stability wppttt$ gs

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Added core counts too:
147dda285fd4:firelens-stability wppttt$ bash check_results.sh us-west-1 r1-celadon-2_31_10-E-2023-04-20T193935238-hzwG9BCc-ecs-firelens-stability-tests E-2023-04-20T193935238-hzwG9BCc
Cluster: r1-celadon-2_31_10-E-2023-04-20T193935238-hzwG9BCc-ecs-firelens-stability-tests us-west-1
Execution: E-2023-04-20T193935238-hzwG9BCc
____Task Counts____

____GOLDEN PATH Task Counts____
ecs-firelens-stability-tests-golden-path-no-onepod-low-throughput: 0
ecs-firelens-stability-tests-golden-path-onepod-low-throughput: 0
ecs-firelens-stability-tests-golden-path-onepod-low-throughput-real: 5
ecs-firelens-stability-tests-golden-path-no-onepod-high-throughput: 0
ecs-firelens-stability-tests-golden-path-onepod-high-throughput: 0
____S3 stability Task Counts____
ecs-firelens-stability-tests-s3-stability-s3-throughput-1mbps: 38
ecs-firelens-stability-tests-s3-stability-s3-throughput-30mbps: 40
____S3 sensitivity Task Counts____
ecs-firelens-stability-tests-s3-sensitivity-s3-control: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-outputPluginCount-10: 3
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_compression-gzip: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_key_format-advanced: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-throughput-10mbps: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-total_file_size-1M: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-upload_timeout-1m: 5
ecs-firelens-stability-tests-s3-sensitivity-s3-use_put_object-on: 5
____Core Counts____
Total Cores: E-2023-04-20T193935238-hzwG9BCc:        2

____GOLDEN PATH Core Counts____
ecs-firelens-stability-tests-golden-path-no-onepod-low-throughput:        0
ecs-firelens-stability-tests-golden-path-onepod-low-throughput:        0
ecs-firelens-stability-tests-golden-path-onepod-low-throughput-real:        0
ecs-firelens-stability-tests-golden-path-no-onepod-high-throughput:        0
ecs-firelens-stability-tests-golden-path-onepod-high-throughput:        0
____S3 stability Core Counts____
ecs-firelens-stability-tests-s3-stability-s3-throughput-1mbps:        0
ecs-firelens-stability-tests-s3-stability-s3-throughput-30mbps:        0
____S3 sensitivity Core Counts____
ecs-firelens-stability-tests-s3-sensitivity-s3-control:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-outputPluginCount-10:        2
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_compression-gzip:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-s3_key_format-advanced:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-throughput-10mbps:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-total_file_size-1M:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-upload_timeout-1m:        0
ecs-firelens-stability-tests-s3-sensitivity-s3-use_put_object-on:        0


BUG: Fix resample in SegPostProcessCLP

It was missing setting the direction for the output image.
Fix #40
Fix https://github.com/Kitware/SlicerSALT/issues/123

Thanks, updating SlicerSALT asap.


Require PHP 7.4

Q
A

Type
improvement

BC Break
yes

Fixed issues
#2464

Summary
Bumps minimal PHP version to 7.4 and PHPUnit to 9.x

Do we have any outstanding todos or PHP version checks that could be removed now? They should be removed along with this PR if present. All other improvements are better than fine in separate PRs :)

Yes, we definitely still have some PHP version checks in the code. I will be solving them step by step, also planning to incorporate Rector to speed things up but that will come in separate PRs so it's easier to review.

Cool, thanks. I've removed now-obsolete required checks :)


[Bug Report] Failed Write Minfreq

Device: Oneplus 7T Pro running OOS 11
Only working on official kernel, tried Dora and Blu-spark , none of them working.
log here:
13:56:31 I uperf v3(22.07.24)[c4ae5755], by Matt Yang<EMAIL_ADDRESS>13:56:31 I Config 'sdm855/sdm855+/sdm860[22.07.24]' by 'yc@coolapk' 13:56:31 I Current home is 'com.teslacoilsw.launcher' 13:56:32 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0 13:56:32 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0 13:56:32 E Tried CpufreqWriterPpmFixed: Failed to open MTK PPM hard userlimit minfreq knob 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterMsmPowersave: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterPowersave: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterMsmFixed: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterPerformance: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterFixed: Failed to write freq 13:56:32 E Retrying... 13:56:32 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0 13:56:32 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0 13:56:32 E Tried CpufreqWriterPpmFixed: Failed to open MTK PPM hard userlimit minfreq knob 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterMsmPowersave: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterPowersave: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterMsmFixed: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterPerformance: Failed to write freq 13:56:32 E Cpufreq target 1113600 actual 1785600 13:56:32 E Tried CpufreqWriterFixed: Failed to write freq 13:56:32 E Exception thrown: No CpufreqWriter supported for this platform

Me Too !
Device:SAMSUNG Tab S6 T860

redmi k20p, Android 12, 类原生系统，同样问题
日志：
07:34:51 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0
07:34:51 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0
07:34:51 E Tried CpufreqWriterPpmFixed: Failed to open MTK PPM hard userlimit minfreq knob
07:34:51 E Tried CpufreqWriterMsmPowersave: Failed to open msm minfreq knob
07:34:51 E Tried CpufreqWriterPowersave: Failed to set powersave governor
07:34:51 E Tried CpufreqWriterMsmFixed: Failed to open msm minfreq knob
07:34:51 E Cpufreq target 1305600 actual 1708800
07:34:51 E Tried CpufreqWriterPerformance: Failed to write freq
07:34:51 E Cpufreq target 1305600 actual 1708800
07:34:51 E Tried CpufreqWriterFixed: Failed to write freq
07:34:51 E Exception thrown: No CpufreqWriter supported for this platform

realme gt neo flash edition, Android 12, RealmeUI 3.0(RMX3350_11_C.17), 相同故障
17:49:49 I uperf v3(22.07.24)[c4ae5755], by Matt Yang<EMAIL_ADDRESS>17:49:49 I Config 'Dimensity 1200(mt6893)/1100(mt6891z)[22.07.24]' by 'yc@coolapk'
17:49:49 I Current home is 'com.android.launcher'
17:49:50 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0
17:49:50 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPpmFixed: Failed to write freq
17:49:50 E Tried CpufreqWriterMsmPowersave: Failed to open msm minfreq knob
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPowersave: Failed to write freq
17:49:50 E Tried CpufreqWriterMsmFixed: Failed to open msm minfreq knob
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPerformance: Failed to write freq
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterFixed: Failed to write freq
17:49:50 E Retrying...
17:49:50 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0
17:49:50 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPpmFixed: Failed to write freq
17:49:50 E Tried CpufreqWriterMsmPowersave: Failed to open msm minfreq knob
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPowersave: Failed to write freq
17:49:50 E Tried CpufreqWriterMsmFixed: Failed to open msm minfreq knob
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterPerformance: Failed to write freq
17:49:50 E Cpufreq target 1250000 actual 2000000
17:49:50 E Tried CpufreqWriterFixed: Failed to write freq
17:49:50 E Exception thrown: No CpufreqWriter supported for this platform
17:49:50 I Failed to start uperf(pid=7425)

魅族17类似故障

Sony Xperia 1 IV, Android 12, Snapdragon 8gen1, 使用第三方内核时出现同样故障。
$ uname -a
Linux localhost 5.10.81-Kirisakura_Nagara_S_1.0.0-00037-gdca213822279-dirty #1 SMP PREEMPT Mon Aug 15 09:23:09 UTC 2022 aarch64

$ cat /sdcard/Android/yc/uperf/uperf_log.txt
16:23:30 I uperf v3(22.09.04)[acc04447], by Matt Yang<EMAIL_ADDRESS>16:23:30 I Config 'sdm8g1[22.09.04]' by 'yc@coolapk'
16:23:31 I Current home is 'shubh.ruthless'
16:23:31 I No available opp of cpu7, use generated opp instead
16:23:31 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0
16:23:31 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0
16:23:31 E Tried CpufreqWriterPpmFixed: Failed to open MTK PPM hard userlimit minfreq knob
16:23:31 E Tried CpufreqWriterMsmPowersave: Failed to set powersave governor
16:23:31 E Tried CpufreqWriterPowersave: Failed to open scaling min knob for cluster2
16:23:31 E Cpufreq target 1075200 actual 1075200
16:23:31 E Cpufreq target 1651200 actual 1651200
16:23:31 E Cpufreq target 1900000 actual 2515200
16:23:31 E Tried CpufreqWriterMsmFixed: Failed to write freq
16:23:31 E Tried CpufreqWriterPerformance: Failed to open scaling min knob for cluster2
16:23:31 E Tried CpufreqWriterFixed: Failed to open scaling min knob for cluster2
16:23:31 E Retrying...
16:23:31 E Tried CpufreqWriterEpicPowersave: Failed to open epic minfreq knob for cluster0
16:23:31 E Tried CpufreqWriterEpicFixed: Failed to open epic minfreq knob for cluster0
16:23:31 E Tried CpufreqWriterPpmFixed: Failed to open MTK PPM hard userlimit minfreq knob
16:23:31 E Tried CpufreqWriterMsmPowersave: Failed to set powersave governor
16:23:31 E Tried CpufreqWriterPowersave: Failed to open scaling min knob for cluster2
16:23:31 E Cpufreq target 1075200 actual 1075200
16:23:31 E Cpufreq target 1651200 actual 1651200
16:23:31 E Cpufreq target 1900000 actual 2515200
16:23:31 E Tried CpufreqWriterMsmFixed: Failed to write freq
16:23:31 E Tried CpufreqWriterPerformance: Failed to open scaling min knob for cluster2
16:23:31 E Tried CpufreqWriterFixed: Failed to open scaling min knob for cluster2
16:23:31 E Exception thrown: No CpufreqWriter supported for this platform
16:23:31 I Failed to start uperf(pid=13342)


[communication] phonenumbers - fix false positive purchase/release test, harden exception tests

add a check for status code to avoid the false positive scenario where service failed
add a check for error type to our error tests, to provide better information if test fails
edited the LRO recordings to remove redundant calls to make ci run faster

/azp run js - communication-phone-numbers - tests

/azp run js - communication-phone-numbers - tests


[XLA] Define ssize_t for Windows

Split from #15310.
#15213

Can one of the admins verify this patch?

Jenkins, test this please.

GPU CC CI test is failing:
tensorflow/core/platform/cloud/file_block_cache_test.cc:464
Value of: WaitForNotificationWithTimeout(&notification, 10000)
  Actual: false
Expected: true
Timeout waiting for concurrent thread to start.

See https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/platform/cloud/file_block_cache_test.cc#L464
Should be unrelated to my change.

It breaks windows bazel build

@snnn Sorry for the breakage. I did not run a rebuild after moving the ssize_t typedef to new file platform/windows/integral_types.h. Can you check if applying #15579 fixes the issue? Thanks!

I'd prefer to put the change in build_config.bzl


After clicking create volume instance always throws this 400 error on web page

In Services menu, after clicking on volume create it throws the below error please find the screen shot

@Shruthi-1MN please attach the network call request and response from the developer console (F12 -> Network tab)

I was not able to recreate this issue. Also it seems like an environment setup issue. Closing.