Timezone error in merging Dask and Pandas

I have two data frames, which to me look to have the same format. One is in Dask and one is in Pandas.
They both look similar to this:
    	                    Volume	Open	High	Low	Close
Date
2003-03-28 14:00:00+00:00	221	0.78049	0.79010	0.77941	0.79009
2003-03-31 06:00:00+00:00	55	0.78227	0.78494	0.78169	0.78223
2003-03-31 14:00:00+00:00	283	0.78277	0.78277	0.76909	0.77179
2003-04-01 06:00:00+00:00	49	0.77798	0.78011	0.77634	0.77902
2003-04-01 14:00:00+00:00	197	0.77794	0.78427	0.77628	0.78209
...	...	...	...	...	...
2021-05-11 13:00:00+00:00	79681	4.73908	4.78913	4.71059	4.78343
2021-05-11 21:00:00+00:00	39958	4.78244	4.80514	4.75803	4.77426
2021-05-12 05:00:00+00:00	77975	4.77438	4.81015	4.70926	4.75015
2021-05-12 13:00:00+00:00	71397	4.75027	4.77359	4.70566	4.74045
2021-05-12 13:00:00+00:00	71399	4.75027	4.77359	4.70566	4.74070

However, when I try to merge the two, I get the following error:
dd.merge(ddf, df, left_index=True, right_index=True))

TypeError: Cannot join tz-naive with tz-aware DatetimeIndex

However, both data frames do contain the same time zone information:
ddf.compute().index gives:
DatetimeIndex(['2003-03-28 14:00:00+00:00', '2003-03-31 06:00:00+00:00',
               ...
               '2021-05-12 13:00:00+00:00', '2021-05-12 13:00:00+00:00'],
              dtype='datetime64[ns, UTC]', name='Date', length=13815, freq=None)

while
df.index gives:
DatetimeIndex(['2021-10-14 21:00:00+00:00', '2021-10-15 05:00:00+00:00',
               '2021-10-15 13:00:00+00:00'],
              dtype='datetime64[ns, UTC]', name='Date', freq=None)

ddf.compute().info gives:
<class 'pandas.core.frame.DataFrame'>
DatetimeIndex: 13815 entries, 2003-03-28 14:00:00+00:00 to 2021-05-12 13:00:00+00:00
Data columns (total 5 columns):
 #   Column  Non-Null Count  Dtype
---  ------  --------------  -----
 0   Volume  13815 non-null  int64
 1   Open    13815 non-null  float64
 2   High    13815 non-null  float64
 3   Low     13815 non-null  float64
 4   Close   13815 non-null  float64
dtypes: float64(4), int64(1)
memory usage: 647.6 KB

and
df.info() gives:
<class 'pandas.core.frame.DataFrame'>
DatetimeIndex: 3 entries, 2021-10-14 21:00:00+00:00 to 2021-10-15 13:00:00+00:00
Data columns (total 5 columns):
 #   Column  Non-Null Count  Dtype
---  ------  --------------  -----
 0   Volume  3 non-null      int64
 1   Open    3 non-null      float64
 2   High    3 non-null      float64
 3   Low     3 non-null      float64
 4   Close   3 non-null      float64
dtypes: float64(4), int64(1)
memory usage: 144.0 bytes

I am using Dask v2021.08.1 and Partd v1.2.0
I cannot understand why I get this error. They both look to me to be of the same format.

Just tested dd.concat([df, ddf]) and that seemed to work...

Checking in here, @oeyvindds can you provide the information @jsignell mentioned in this comment https://github.com/dask/dask/issues/8269#issuecomment-946154525?

Closing due to lack of activity. Feel free to re-open if you'd like to continue


Actor fixes

Now functions:
myactor.setPosition(0, 0, Align.left);
is equal to
myactor.setX(0,Align.left);
myactor.setY(0,Align.center);
Move half actor to down and full to left (before that it moved only half actor down. All "aligns" were inverted - bottomLeft was topRight, left was right and so on)
And setOrigin is now relative to actor as is written in doc:
“Sets the origin position which is relative to the actor's bottom left corner."

I have a feeling that you misunderstood how the position with alignment works. What is aligned is the point to which the coordinates refer inside the Actor, not the actor around the point.
Also, the origin is independent on the Actor's position, as documented. This makes the origin relative to world coordinate system, which will probably break a lot of things inside the libGDX.
Please try to understand how the library works first, before concluding that it is broken.

ok, thank you for explanation. I understand now.


Crash - same key added

We got this error on Serval Ext QA, Mon Jan 29th, 7:06 PM
Value: [ var='B0' metric='{app="serval-api", container="serval-api", container_id="689a92c75db67b1735bf52d9b3f078762c6daa6cd07c2e1c7265e1c071887b96", host="kb6", log="fail: Microsoft.AspNetCore.Server.Kestrel[13]\n      Connection id \"0HN0RCC5B6O4B\", Request id \"0HN0RCC5B6O4B:00000009\": An unhandled exception was thrown by the application.\n      System.ArgumentException: An item with the same key has already been added. Key: 65b83d3c725849ee917450da\n         at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)\n         at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)\n         at System.Linq.Enumerable.ToDictionary[TSource,TKey](List`1 source, Func`2 keySelector, IEqualityComparer`1 comparer)\n         at Serval.Translation.Services.EngineService.StartBuildAsync(Build build, CancellationToken cancellationToken) in /app/src/Serval.Translation/Services/EngineService.cs:line 196\n         at Serval.Translation.Services.EngineService.StartBuildAsync(Build build, CancellationToken cancellationToken) in /app/src/Serval.Translation/Services/EngineService.cs:line 265\n         at Serval.Tr", namespace="serval", pod="serval-api-7c4fb9c65c-h2qmf", pod_id="34cc5008-64c6-4703-a0fe-451fec345112", pod_template_hash="7c4fb9c65c",

Two builds start at the same time?

Looks like the same corpus is referenced multiple times in trainOn or pretranslate properties.

Multiple times in each or one in each?

Multiple times in each. I think we should error out with a 400. If the same corpus is specified multiple times, then each could have different settings. It would be unclear which to use.


Machine is already provisioned

Operating System: Win 7 x64
Vagrant Version: 1.91
Virtual Box Version: VirtualBox-5.1.18-114002-Win
I have no problem initialising and running the vagrant up command and vccw works as expected so far. The issue I have is that after performing a vagrant halt (switch machine off) and then running vagrant up (switch back on) I get a Machine is already provisioned issue.
==> vccw.dev: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> vccw.dev: flag to force provisioning. Provisioners marked to run always will still run.

The output suggests using the -no-provisioning flag but then the machine simply halts obviously this behaviour is not ideal as each switch off kills the box.

I do not think it is a problem of the VCCW.
Are there same problem with VVV or another vagrant machine?


while algorithm is serving other algorithm "get from peer" request it should not go down

while algorithm is serving other algorithm get from peer request it should not go down
In case of  algorithm output followed by batch,
As long of the batch is consuming the algorithm output
the algorithm should stay up and server the requests

tested on
systemVersion: "v1.3.130",
fullSystemVersion: "v1.3.130-1601470196131",


How do you send an $http post request to a restricted api?

The user is signed in. But the 'angular-devise' does not send the access token along with the headers automatically? How else should I make $http request?

Probably you need to disable protect_from_forgery or to send cookie XSRF-TOKEN .
Check the link from README or you can find demo example on my blog


add IronHide command

I think we can add a command to close the iron window simpler.
If needed, I will add the doc for this.

Hi @tristone13th, thanks for the contribution!
I'm sorry for taking long to merge this - I was off on vacations.

Hi @tristone13th, thanks for the contribution! I'm sorry for taking long to merge this - I was off on vacations.

No problem, thanks for your good work!


Pass headers to knox-mpu and auto detect content type if not set

This is a prop to add support to automatically set the Content-Type and pass headers to knox-mpu
Related to issue #1 and http://stackoverflow.com/questions/25206528/how-to-add-acl-and-content-type-parameters-when-using-skipper-s3
Checked in knox-mpu and seems that there is no need for changes.
The mime package is also used with knox but only in a call to putFile.
https://github.com/LearnBoost/knox/blob/master/lib/client.js#L363

This looks like it's fixed, but it's still confusing people largely because I don't think there's documentation for it. (e.g. #26 and even an alternate repo). I can fix the documentation if someone explains to me how exactly to use this fix. I think you need a headers member of the options object, and inside that header parameter you need to somehow specify 'public'. How does I?

Aha. Found this


The selected entities are not highlighted if using 'Select All' action

Storage Explorer Version: 1.25.0-dev
Build Number: 20220722.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.4 (Apple M1 Pro)
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.24.3)
Steps to Reproduce

Expand one storage account -> Tables.
Open one non-empty table -> Click 'Select All'.
Check whether the selected entities are highlighted.

Expected Experience
The selected entities are highlighted.

Actual Experience
The selected entities are not highlighted.

@v-xianya Actually, all of the items are highlighted. The only difference is the table doesn't have focus. The color used for selected, unfocused items is different for selected, focused items. I don't think swapping focus to the table is a good idea, especially for keyboard users, because they usually want to perform some action on those items, but focusing on the table moves users away from the toolbar which contains those actions.

I need to check if this is due to us not setting the class on selection update.

The selection class name is updated correctly but the we are not initializing the state of "current active explorer" correctly.

Verified this issue on the build 20220725.1. Fixed. So, we close it.


[bug] extendTheme doesn't work w/ pigment

Steps to reproduce
Link to live example
Steps:

clone repo & install deps npm ci
run npm run start
see the theme src/theme.ts has no effect on mui.Fab

Current behavior
extendTheme doesn't change the styles of the mui.Fab
Expected behavior
extendTheme affects mui.Fab
Context

https://github.com/mui/material-ui/pull/42781

this reproduction example follows the PR's upcoming docs

Your environment

npx @mui/envinfo
    "@pigment-css/react": "0.0.16",
    "@pigment-css/vite-plugin": "0.0.16",

  System:
    OS: macOS 14.5
  Binaries:
    Node: 22.1.0 - /opt/homebrew/bin/node
    npm: 10.7.0 - /opt/homebrew/bin/npm
    pnpm: 9.0.2 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.127
    Edge: 112.0.1722.39
    Safari: 17.5
  npmPackages:
    @emotion/react:  11.11.4
    @emotion/styled:  11.11.5
    @mui/base:  5.0.0-beta.51
    @mui/core-downloads-tracker:  6.0.0-dev.240424162023-9968b4889d
    @mui/material: 6.0.0-alpha.13 => 6.0.0-alpha.13
    @mui/private-theming:  6.0.0-dev.20240529-082515-213b5e33ab
    @mui/styled-engine:  6.0.0-dev.20240529-082515-213b5e33ab
    @mui/system:  6.0.0-dev.240424162023-9968b4889d
    @mui/types:  7.2.14
    @mui/utils:  6.0.0-dev.20240529-082515-213b5e33ab
    @types/react: 18.3.3 => 18.3.3
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.5.2 => 5.5.2

Search keywords: pigment, extendTheme
Search keywords:

Vite has deps optimization that does not work with Pigment CSS
This is the vite config that work so far:
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { pigment } from '@pigment-css/vite-plugin'
import { extendTheme, stringifyTheme } from '@mui/material/styles'

const theme = extendTheme();
// @ts-expect-error ignore
theme.toRuntimeSource = stringifyTheme;

// https://vitejs.dev/config/
export default defineConfig({
  optimizeDeps: {
    include: [
      "prop-types",
      "react-is",
      "hoist-non-react-statics",
      "react",
      "react-dom",
      '@emotion/react',
      '@emotion/styled',
    ],
    exclude: ["@mui/material"],
  },
  plugins: [
    react(),
    pigment({
      theme,
      transformLibraries: ["@pigment-css/react", "@mui/material"],
    }),
  ],
})

Note: this is a workaround to get the app working, need #169 to be released.

@siriwatknp @aarongarciah
Please reopen the issue, as it still doesn't work using the latest versions of @mui/pigment... and @mui/material and following exactly the Migration Guide.
Updated the repro. Related issue https://github.com/mui/pigment-css/issues/180

@aarongarciah
cc @siriwatknp
Thank you for confirming and describing point 2 in more detail.
The issue in point 2 is: incorrect typings then, that allow you to pass extended prop and doesn't enforce you to migrate to the new way of declaring variants. (see screenshot)

I'm beginning to get this exact error:
Details posted over on https://github.com/mui/material-ui/issues/43411

How do I exclude libraries which make building stuck until you make this production ready?

extended is not a slot, it's a variant. The only slot in Fab is root. You can override styles based on props (like variant) like this

@aarongarciah I have a custom theme with lots of overrides for both variants and slots in many styleOverrides objects like:
createTheme({
  components: {
    MuiPaper: {
      styleOverrides: {
        elevation: ({ theme }) => ({
          boxShadow: "0px 9px 16px rgb(176 176 176 / 18%), 0px 2px 2px rgb(176 176 176 / 32%)",
        }),
      }
    }
  }
})

At first glance, it seems impossible to distinguish variant overrides from slot overrides, so it will be very time-consuming to figure out one-by-one which override to migrate to the variants array notation.
Is there a way to handle this better? Are there any plans to make styleOverrides for variants working in Pigment CSS also? Perhaps a codemod could assist with this kind of migration? Apparently, the theme-v6 codemod only moves variants from outside the styleOverrides property inside the root override, but does not cover the case shown above. TypeScript also does not complain about unknown properties.


[zh] sync logging.md, system-logs.md, and test.md

Sync 3 files with en #41395 and #41863
content/zh-cn/docs/concepts/cluster-administration/logging.md
content/zh-cn/docs/concepts/cluster-administration/system-logs.md
content/zh-cn/docs/test.md

See previews:

logging.md
system-logs.md
test.md

/lgtm

/approve


Port the Crawlers from QSE

This issue is about tracking progress with porting the crawlers from qse.  A crawler is considered done after a PR that introduces it has been merged to main.

[x] SZ
[x] SPON
[x] Welt
[x] Zeit
[x] BZ
[x] DW
[x] Focus
[x] Merkur
[x] Orf
[x] Tagesschau
[x] NDR
[x] Taz
[x] NTV(#132 )
[x] Stern(#127)
[x] FAZ
[x] WAZ(#128)

I just remembered that there are some more:

[ ] Bild
[ ] Tagesspiegel

Some ones I worked on locally:

[ ] Frankfurter Rundschau
[ ] Freitag
[ ] MDR
[ ] T Online
[ ] Heise
[ ] Zdf

All of the publishers present in qse have been done.


Alpha release 0.2.0

Creation of an overarching client, cleanup of testing for more coverage, and added functionality to easily generate Address Script Hashes from public addresses.

#4 introduced as neo_get_scripthash_from_address

Pull Request Test Coverage Report for Build 15

45 of 72 (62.5%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+4.6%) to 93.201%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

switcheo/Fixed8.py
4
5
80.0%

switcheo/neo/transactions.py
2
3
66.67%

switcheo/test_public_client.py
4
5
80.0%

switcheo/switcheo_client.py
8
32
25.0%

Totals

Change from base Build 13:
4.6%

Covered Lines:
562

Relevant Lines:
603

💛  - Coveralls


[BUG] Mongo: cannot use spring-boot-starter-data-mongodb and langchain4j-mongodb-atlas together

More details can be found here: https://stackoverflow.com/questions/79258092/maven-dependency-problem-between-spring-data-mongo-and-langchain4j-mongo-atlas

Hi @katcharov, could you please help with this? 🙏

Has this problem been fixed?

@misselvexu AFAIK not yet, would you like to help here please? 🙏


Drag is not working

Looks like drag don't affect particle motion. I expect value of 0 to be no drag and 1 to be absolute drag (immidiatly kills any velocity and acceleration), but neither 0 nor 1 has any effect.

It was working the last time I checked, but I'll double-back and make sure it's still the case. If it is working, then I'll put together a little example for you that you can try on your machine and see if it works for you, too.

Ah, this will be down to the way I calculate drag, which may well be incorrect.
I'll have a look a the GLSL code that does this and see where it can be improved.

Okay, so I've had a look at the calculation and the way it's implement and it's working as I intended.
For the drag effect, I followed the lead of Unreal Engine's particle system's drag. The drag video on that page (right click, and select 'loop' to see the effect properly!) shows the effect.
What I didn't do was apply the drag calculation to the acceleration values as well as the velocity values. The reason being that originally, I was thinking of drag as similar to air resistance, and therefore separate from acceleration (acceleration being a force produced by the particle itself and not a force acting on the particle). In that sense, velocity should be the only force affected by drag, with acceleration acting independently.
If I apply the drag calculations to acceleration as well as velocity, the forces acting on the particles still will not be zeroed out immediately if drag is set to 1, as that's not how drag works (it's an exponential increase of the opposite force, or if you think of it the other way around: an exponential decay of the forces acting on a particle). Should a drag value of 1 immediately cause particles to not move anywhere, it wouldn't be drag, but rather a scaling of the velocity and acceleration values. Drag is a function of time, not a scaling factor.
With that in mind, I'm now conflicted as to whether to alter the drag behaviour to make it affect acceleration values as well as velocity. It differs from my original intentions, but if you feel it would be a suitable "upgrade" do let me know.
@DelvarWorld: do you have any thoughts on this?

Closing due to inactivity.

Thank you for the knowledge nuggets @squarefeet , this is a great and well thought out explanation.


Suppress zoom modals when screen is single column

The layout shifts to single column at size md. At that point, the chart is the largest it can be on the screen and shouldn't be zoomed. The zoom modal currently is too large for the screen and can't be closed.

Done


Bash utilities for opticks cannot find proper paths

Steps to reproduce the issue:
export OPTIX_DIR=/usr/local/optix
curl -Os https://bnlnpps.github.io/esi-shell/esi-shell && chmod u+x esi-shell
./esi-shell -v 1.0.0-beta.6

opticks-full

Then use test a bash utility from opticks
g4-;g4-cls G4Cerenkov

Error Message
root@579a2b0ce636:/esi/opticks# g4-;g4-cls G4Cerenkov
bash: cd: /opt/spack/opt/spack/linux-ubuntu22.04-sapphirerapids/gcc-11.4.0/geant4-11.1.2-z4zrvgbct5pf2uhyrxf7xlo5mjalfiwf/..build/geant4.10.04.p02/: No such file or directory
/esi/opticks
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
vi -R
bash: vi: command not found

Probable cause
The utility is inside the externals folder and sets the paths through shell commands.
root@579a2b0ce636:/esi/opticks# ls externals
asiozmq.bash	g4.bash        nljson.bash	     optix7c.bash
assimp.bash	g4dae.bash     ocmake.bash	     optix7sdk.bash
bcm.bash	g4dev.bash     ocsgbsp.bash	     optixnote.bash
boost.bash	g4oktest.bash  odcs.bash	     owl.bash
clhep.bash	glad.bash      oimplicitmesher.bash  oyoctogl.bash
cub.bash	gleq.bash      oof.bash		     plog.bash
cuda.bash	glew.bash      openmesh.bash	     rcs.bash
cudalin.bash	glfw.bash      opticksaux.bash	     root.bash
cudamac.bash	glm.bash       opticksdata.bash      thrust.bash
denoise.bash	imgui.bash     optix.bash	     xercesc.bash
externals.bash	mgpu.bash      optix7.bash	     zmq.bash

g4-cls(){
   local iwd=$PWD
   g4-cd
   pwd
   g4-cls- source    $* ;
   cd $iwd
}

g4-cls-(){
   local base=${1:-source}
   local name=${2:-G4OpBoundaryProcess}

   local h=$(find $base -name "$name.h")
   local hh=$(find $base -name "$name.hh")
   local cc=$(find $base -name "$name.cc")
   local icc=$(find $base -name "$name.icc")
   local src=$(find $base -name "$name.src")

   local cc2=""
   if [ "$name" == "G4SteppingManager" ] ; then
       cc2=$(find $base -name "${name}2.cc")
   fi

   local vcmd="vi -R $h $hh $icc $cc $src $cc2"
   echo $vcmd
   eval $vcmd
}

What is this command g4-cls G4Cerenkov supposed to do?

What is this command g4-cls G4Cerenkov supposed to do?

It's a command line utility that's supposed to show the class description. May be they are not activated by default since they fall under the category of foreign externals.  https://simoncblyth.bitbucket.io/opticks/docs/externals.html

Do I understand correctly that G4Cerenkov is a Geant4 class? If so, here is the reference API https://geant4.kek.jp/Reference/11.1.2/classG4Cerenkov.html
It appears to me that g4-cls is broken because geant4 is not installed in /usr/local/opticks_externals
$ g4-cls
bash: cd: /usr/local/opticks_externals/g4_1042.build/geant4.10.04.p02/: No such file or directory
/home/dmitri
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
find: 'source': No such file or directory
vi -R
bash: vi: command not found

Geant4 is installed via Spack:
$ spack find -p geant4
-- linux-ubuntu22.04-sapphirerapids /<EMAIL_ADDRESS>----------------
<EMAIL_ADDRESS>/opt/spack/opt/spack/linux-ubuntu22.04-sapphirerapids/gcc-11.4.0/geant4-11.1.2-z4zrvgbct5pf2uhyrxf7xlo5mjalfiwf
==> 1 installed package

Yes, that is exactly where opticks finds Geant4 via CMake. In the container we simply don't have another instance of Geant4 besides the one installed with Spack

But it's in the image, right?

But it's in the image, right?

Yes, all the dependencies (including Geant4) opticks is compiled against are in the image.

@plexoos Is there a work around for the bash utilities to work without geant4 being present in the externals folder?

I don't think there is an easy workaround to make commands from g4.bash work as some of them expect the Geant's source directory. Currently, we don't keep the source files, but this default Spack's behavior can be changed.

I don't think there is an easy workaround to make commands from g4.bash work as some of them expect the Geant's source directory. Currently, we don't keep the source files, but this default Spack's behavior can be changed.

In that case, I don't think this is a priority for us. We would just make a disclaimer that those external utilities don't work within esi-shell.

To summarize, the issue is about a feature in opticks to reference Geant4 classes (and related documentation). Since we don't have plans to support opticks, the users can use the official Geant4 documentation available elsewhere.


Make usage of new gmsaas getInstance 'endpoint' of 1.6.0

Description
In gmsaas version 1.6.0, as per Wix' request, a reach onto the getInstance endpoint via gmsaas was introduced through the gmsaas instances get <uuid> command. This PR plugs that in into the driver by reimplementing lookup-service' getInstance(), which previously fetched all instances and manually filtered them (which wasn't scalable - hence the point in all this).
This comes alongside a preliminary check in the driver's prepare() of that the gmsaas executable is sufficiently new on the host machine.

Note: Initially, this PR should fail because gmsaas on the agents isn't up-to-date (1.5.x). This is a good test of that this works. Following a failure, I will upgrade the agents as well.


How to stop the UdpEndpoint

I need to stop UDP Endpoint when click a button. How to add code to implement it?

Hi @parallelbgls I'm very sorry I never received a notification on this issue!  I will add it to my list.


Allow all data types when using travelTo

travelTo currently only accepts a DateTimeInterface but it is passed to Carbons setTestNow which accepts all data types.
Before:
$this->travelTo(now()->parse('12:00'));

After:
$this->travelTo('12:00');

Removing the typehint here is a breaking change to the method signature. I personally also would leave it in place but you're free to attempt a PR to master to see if Taylor would accept it.


Fixed 301 links

Fixed the 301 (Moved Permanently) links returned by travis/awesome_bot.
The travis log is below. I fixed the 301 ones.
  01. [L088] 302 http://www.designerspics.com  → /
  02. [L093] 301 https://www.morguefile.com/archive  → http://morguefile.com/archive
  03. [L093] 301 https://www.morguefile.com/terms  → http://morguefile.com/terms
  04. [L134] 403 http://getrefe.tumblr.com
  05. [L149] 301 https://facebook.github.io/design/  → http://facebook.design/
  06. [L149] 301 https://facebook.github.io/design/disclaimer.html  → http://facebook.design/disclaimer.html
  07. [L223] 301 http://www.materialui.co/icons  → http://materialui.co/icons
  08. [L235]  https://www.coleure.com/ SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
  09. [L243] 301 http://www.materialui.co/colors  → http://materialui.co/colors
  10. [L253] 301 http://www.sitebuilderreport.com/stock-up  → https://www.sitebuilderreport.com/stock-up
  11. [L261] 301 http://html5up.net/  → https://html5up.net/
  12. [L262] 301 http://templated.co/  → https://templated.co/
  13. [L262] 301 http://templated.co/license  → https://templated.co/license
  14. [L296] 302 https://www.linkedin.com/shareArticle?mini=true&url=https://github.com/neutraltone/awesome-stock-resources&title=Awesome%20Stock%20Resources&summary=&source=  → https://www.linkedin.com/uas/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2FpostLogin%3Fsession_rikey%3Dw-8YoO2IB1Jcnt-UONzL-viqBTByZvZ0Dg2Lb1oJJkcGWx6g62dubSx0i9P7qBtVM2gQ-DD-ikK75NTF8zSL3bltD3gvVgbGWZY%26l%3Dhttps%253A%252F%252Fwww%252Elinkedin%252Ecom%252FshareArticle%253Fsummary%253D%2526mini%253Dtrue%2526source%253D%2526title%253DAwesome%252BStock%252BResources%2526url%253Dhttps%25253A%25252F%25252Fgithub%25252Ecom%25252Fneutraltone%25252Fawesome-stock-resources%26id%3D0%26b%3D5532c871-1d6d-4234-8cc4-6fbb2db49335%26h%3De50S%26m%3DGET

Fantastic thanks! It's a bit of game of a whack-a-mole :D


Use timeout to allow usage of interpolated bindings

I have a need to show more than one card form on a page. Since the card-container binding is required and it wants an element id, having duplicate ids on a page won't work. So, using an id with something like card-container{{$id}} solves the unique issue, but when the Card class is instantiated, angular has not yet completed the interpolation and so Card cannot find the element. Using a timeout solves this issue.
If there is a better way to solve this, please let me know.

Thanks.
Added v0.3.9


Updating routes.php, changelog.md

Updating routes.php for the Fleet and Flight Homepage links

Look good, please go ahead.


remove typings for @storybook/addon-knobs

references #1166
blocked by https://github.com/DefinitelyTyped/DefinitelyTyped/pull/17399

@shilman changed the base here as well.

The DefinitelyTyped package has been released, can I merge this into the 3.2 branch @ndelangen @shilman?


feat(level): add default level to config + implement enabled

Level given as parameter into WASMLayerConfig

I think we need to improve the WASMLayerConfig object so it's private with setters or using with builder pattern. Otherwise, if we release a new version of tracing-wasm, it will break dependent codebases.


[WIP] Only filter the EC2 actions by VPC.

The query commands were failing due to the permission being too strict
and incorrect.

I'm not sure I understand your commit message - there are still EC2 actions that aren't specific to a VPC?

No longer using.


Line breaks

Aren´t linebreaks supposed to be converted into ? Any ways to fix this in a nice way?

See https://github.com/rexxars/react-markdown/issues/105#issuecomment-346103734
I'll keep this open as a reminder to add some documentation about it.

Ah, silly me - should have read the spec more carefully. Thanks for clarifying.

What was the problem? I'm using react-markdown to convert a richtext to HTML. but seems like my \ are not converting to
What's my mistake?


Getting started - Errors when running npm commands

When I run npm start, I get this:

<EMAIL_ADDRESS>start /home/andreas/software/caffejs
cd docs-pages && http-server
sh: 1: cd: can't cd to docs-pages

And when I run npm install, I get this:

typings install
typings WARN deprecated 5/9/2016: "registry:dt/dagre#0.7.0+20160505164908" is deprecated (updated, replaced or removed)
typings WARN deprecated 9/6/2016: "registry:dt/d3#0.0.0+20160620220125" is deprecated (updated, replaced or removed)
typings WARN deprecated 10/4/2016: "registry:dt/whatwg-fetch#0.0.0+20160524142046" is deprecated (updated, replaced or removed)

Hi @atenpas
right now it's a bit weird to get started, you have to compile the docs running gulp docs. This requires to have gulp and typescript installed (npm install -g gulp-cli typescript typings).
Another great option to play around with CaffeJS is to just checkout the gh-pages branch (the one that is hostet here https://chaosmail.github.io/caffejs/ via git checkout gh-pages. Now you should be able to spin up a local webserver via http-server (once it is installed via npm install -g http-server).
Hope this helps you!
Best,
Christoph


⚠ GitLab Server has degraded performance

In fb20891, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 13466 ms

Resolved: GitLab Server performance has improved in 6de4736.


Add nulls_compare_equal to SeriesEqualityOperator

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

Comparison is base (18859a0) 100.00% compared to head (407d3bf) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #150   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          686       694    +8
  Branches       171       172    +1
=========================================
+ Hits           686       694    +8

Impacted Files
Coverage Δ

src/coola/_pandas.py
100.00% <100.00%> (ø)

src/coola/_polars.py
100.00% <100.00%> (ø)

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


Sorting does not work in folder_contents view

Login as admin
Go to https://volto.kitconcept.com/contents
Sort the folder_contents view by any way
-> nothing happens
-> it seems no sort_on param is sent by react

Possible duplicates or similar issues:
https://github.com/plone/volto/issues/1035
https://github.com/plone/volto/issues/940


Set custom AppCenter names

⚠ Is your feature request related to a problem? Please describe
Now to upload app to AppCenter, we should create apps which correspond to pattern <appNamePrefix>-<variantName>. For example TestProject-debug, TestProject-release.
It can be useful to add possibility to set custom names for each variant. For example, instead of appNamePrefix we can add appName property. But if appName isn't set we can use <baseFileName>-<variantName>, for example example-base-project-android-debug, example-base-project-android-internal.

PR is in progress


jquery post resulting in Unsupported Media Type

Description
I am using jquery post to post some data. Looks like the validator code is throwing a unsupported media type error while processing.
Expected behaviour
Get a 200 response
Actual behaviour
Response I get:
{
  "detail": "Invalid Content-type (application/json), expected JSON data",
  "status": 415,
  "title": "Unsupported Media Type",
  "type": "about:blank"
}

request header
Accept: application/json
Access-Control-Allow-Methods: POST, GET, OPTIONS
Access-Control-Allow-Origin: *
Authorization: Bearer <redacted>
Content-Type: application/json
Origin: http://localhost:8888
Referer: http://localhost:8888/epayconnect/light-bootstrap-dashboard-master/customer.html
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
x-api-key: <redacted>

Steps to reproduce
Post /localhost/current/customer via jquery
$.ajax({
                type: "POST",
                processData: false,
                contentType: false,
                crossDomain: true,
                dataType: 'json',
                type: 'POST',
                data: data,
                headers: header,
                url: "http://<IP_ADDRESS>:5000/current/customer",
                success: function(response) {
                    alert(response['response']);
                },
                error: function(err) {
                    alert('Error', err);
                }
            });

Additional info:
I am able to use curl POST via command line without any issues.
curl -X POST -H "Authorization: Bearer $ACCESS" --header "x-api-key: $key_value" "${endpoint}/customer" -d @/tmp/customer -H "Content-Type: application/json"

Output of the commands:

python --version
python 3.6.3
pip show connexion | grep "^Version\:"
Version: 1.1.9

Ref code: https://github.com/zalando/connexion/blob/master/connexion/decorators/validation.py#L152

One more observation that via jquery, there is an additional OPTIOS call (which doesnt appear with curl.

Apologies. Need to apply JSON.stringify to the json obect before posting.


Add February release Blog post for review

February Release Blog Post
This pull request is for the February release to publish the blog post to the website
How to use
We need to review the auto generated link to make sure everything looks as expected before merging the PR.
Testing done
So far I've previewed using StackEdit but I won't know for sure how the website looks until the preview is generated.

@blixtra could you please review and merge whenever you feel comfortable?


Dependency update

Thank you very much for this!
To what degree did you test this? There are a few major bumps in there.

THAT is why I requested a review. My dev environment isn't complete for all feature testing, so I made the PR to notify you, since you're more aware of what some of the dependencies are utilized for and in what modules.. The other major bump is the bitcoin dependency. It is now deprecated and has moved to bitcoin-core. I haven't tried to implement that one yet.

I've also requested a dependency update from discord-irc to fix the simple-markdown issue again

hey guys, could someone please try to run this branch and see if the bot still works? I currently don't have the time to do it but I feel like this PR should be merged sooner rather than later

I'm working on spinning up a full dev environment. The issue is that most features typically go unused except on the LBRY server (like claimbot). So I just need to configure everything. Should have this done by the end of the week.

Thanks @Coolguy3289! If we can do anything to assist env wise, please post a message in chat.

any updates on this one?


Is there a way to set line break for a placeholder option?

Summary
I know there is a option for placeholder in editor,
but I cannot find a way to set link break in the content of the placeholder.
I tried
 for a line break, but it doesn't work.
Is there any way to do that?
Version
@toast-ui/editor:  2.4.0
@toast-ui/vue-editor: 2.4.0
Additional Content
I tried
 for a line break, but it doesn't work
<editor     :initialValue="value"     ref="refEditor"     :options="editorOptions"     initialEditType="wysiwyg"  />
editorOptions: {         placeholder: "line1
 line2"   },

@djbicycle First, put a newline character between the text you want to newline.
const editor = new Editor({
  // ...
  initialEditType: 'wysiwyg',
  placeholder: 'line1 \n line2'
});

Then, you need to customize it. You can add a style to the CSS selector as follows.
.tui-editor-contents-placeholder::before {
  white-space: pre;
}

@djbicycle First, put a newline character between the text you want to newline.
const editor = new Editor({
  // ...
  initialEditType: 'wysiwyg',
  placeholder: 'line1 \n line2'
});

Then, you need to customize it. You can add a style to the CSS selector as follows.
.tui-editor-contents-placeholder::before {
  white-space: pre;
}

It works, thank you!


Dynamic time trigger starting at random intervals

Hi, thanks for all the good work around the project.
I have set up a notification containing the rank of the current hour whenever my automation starts the boiler based on the dynamic trigger. I am using 2,5 hour interval.
Sometimes the boiler is started even in the 22nd cheapest hour...which is a bit useless and counter-productive as it's actually doing quite the opposite of what it should be doing :)
I think the problems occur whenever:

negative prices appear (imho even for the following day)
Home Assistant is restarted

I will gather more data and add it here, but i had to already write something because the note is on my desk already for longer than a few months and i need to stop procrastinating... O:-)
I am using the prices for Austria.
Thanks.
Marek

Which service provider are you using? If it is Epex Spot Web Scraper, then you don't get prices from the past - which could cause issues if HA is restarted.

I am using your HACS integration, followed the manual for implementation.
Boiler switch logs show very interesting data - there seem to be some data issues when the sensor falls into an unknown state. Afterwards the length is not followed.

October 7, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 4:00:00 AM - Yesterday EPEX Spot Binary Sensor - dynamic time - boiler turned on 2:00:00 AM - Yesterday October 6, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 3:51:00 PM - 2 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned on 1:00:00 PM - 2 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned off 12:00:00 PM - 2 days ago EPEX Spot Binary Sensor - dynamic time - boiler became unknown 12:00:00 AM - 2 days ago October 5, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 3:00:00 PM - 3 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned on 1:00:00 PM - 3 days ago October 4, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 2:00:00 PM - 4 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned on 1:00:00 PM - 4 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned off 5:00:00 AM - 4 days ago EPEX Spot Binary Sensor - dynamic time - boiler turned on 4:00:00 AM - 4 days ago October 3, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 5:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 3:00:00 AM - Last week October 2, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 5:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 3:00:00 AM - Last week October 1, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 4:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 2:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 12:00:00 AM - Last week September 30, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned on 10:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 2:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 1:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 4:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 3:00:00 AM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 12:00:00 AM - Last week September 29, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned on 11:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 10:02:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 10:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 5:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 4:40:16 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned off 3:00:00 PM - Last week EPEX Spot Binary Sensor - dynamic time - boiler turned on 1:00:00 PM - Last week September 28, 2024 EPEX Spot Binary Sensor - dynamic time - boiler turned off 3:00:00 PM - 2 weeks ago


Fix output parsing when using debugger

Description of changes:
The first object returned is now a non-JSON version string line from Kani. This is a result of the change from https://github.com/model-checking/kani/pull/2619.
This PR adds a fix to the output parsing when parsing the JSON objects in debugger mode.
Resolved issues:
Resolves #ISSUE-NUMBER
Related RFC:

Optional #ISSUE-NUMBER.
Call-outs:

Testing:

How is this change tested?

Is this a refactor change?

Checklist

[ ] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

What makes it non-JSON? I don't understand why this is needed, can you show an example?

What makes it non-JSON? I don't understand why this is needed, can you show an example?

Here is a sample array of objects that is returned from Kani
0:
'Kani Rust Verifier 0.33.0 (cargo plugin)'
1:
{"reason":"compiler-message","package_id":"sample-coverage 0.1.0 )","manifest_path":"...","target":{"kind":["bin"],"crate_types":["bin"],"name":"sample-coverage","src_path":"/Users/jaisnan/Desktop/temp/sample-coverage/src/main.rs","edition":"2021","doc":true,"doctest":false,"test":true},"message":{"rendered":"warning: unused variable: `y`\\n  --> src/main.rs:44:9\\n   |\\n44 |     let y = est…hlight_start":9,"text":"    let y = estimate_size(x);"}]}]}],"code":{"code":"unused_variables","explanation":null},"level":"warning","message":"unused variable: `y`","spans":[{"byte_end":776,"byte_start":775,"column_end":10,"column_start":9,"expansion":null,"file_name":"src/main.rs","is_primary":true,"label":null,"line_end":44,"line_start":44,"suggested_replacement":null,"suggestion_applicability":null,"text":[{"highlight_end":10,"highlight_start":9,"text":"    let y = estimate_size(x);"}]}]}}'
2:
{"reason":"compiler-message","package_id":"sample-coverage 0.1.0 ","manifest_path":"...","target":{"kind":["bin"],"crate_types":["bin"],"name":"sample-coverage","src_path":"/Users/jaisnan/Desktop/temp/sample-coverage/src/main.rs","edition":"2021","doc":true,"doctest":false,"test":true},"message":{"rendered":"warning: 1 warning emitted\\n\\n","children":[],"code":null,"level":"warning","message":"1 warning emitted","spans":[]}}'
3:
{"reason":"compiler-artifact","package_id":"sample-coverage 0.1.0 ","manifest_path":".../Cargo.toml","target":{"kind":["bin"],"crate_types":["bin"],"name":"sample-coverage","src_path":"/Users/jaisnan/Desktop/temp/sample-coverage/src/main.rs","edition":"2021","doc":true,"doctest":false,"test":true},"profile":{"opt_level":"0","debuginfo":2,"debug_assertions":true,"overflow_checks":true,"test":true},"features":[],"filenames":[".../sample_coverage-e06b8dc25d1abcec"],"executable":"../sample_coverage-e06b8dc25d1abcec","fresh":true}'
4:
{"reason":"build-finished","success":true}'

But we don't have a minimum version check in the VS Code extension, right? Some users may have a previous version and then they'll miss the first object because of this hack.

Or maybe you can fix this on Kani's end?

In this particular case, this should be backwards compatible as well since we only care about the last but one JSON blob from Kani. That blob contains the path for the debugger executable. I think we can and should fix it on Kani's end, but till then, this hack allows existing users to use the debugger.


When using with HTTP Chunked Transfer Encoding, 6.7MB becomes 10.5MB due to chunking overheads

This is a big problem for me. I am using transit-json on a Web endpoint, and I am streaming the result of encoding. The stream is using HTTP chunked transfer encoding. This essentially indicates the overall size is unknown, and informs you of how many bytes are about to come repeatedly until it is finished.
Due to the flushes from Transit, these chunks end up very small. Usually just a string and some open/close parens. This overhead causes the 6.7MB of transit to transport as 10.5MB of HTTP.  That is, it gets significantly bigger when transferred this way. For this application and expected timing, this directly impacts 10s of load time.
transit-clj seems to flush after every write (https://github.com/cognitect/transit-java/blob/cff7111c2081fc8415cd9bd6c6b2ba518680d660/src/main/java/com/cognitect/transit/impl/AbstractEmitter.java#L189). I would guess this is related to #43.

Additionally, these chunking overheads seem to drastically limit the ability of gzip to function.

https://clojure.org/community/contributing
https://ask.clojure.org/

Those links are primarily for Clojure itself or the Clojure contrib libraries. transit-clj is not a Clojure core project, it is managed by Cognitect (admittedly this is mostly the same people, but they have different licenses and contribution processes).
This is the proper place to log this issue for this project.

sry. my bad.

Reporting from Slack. Saw this exact behaviour when using transit-body-interceptor from pedestal, which uses .flush. Using the strategy mentioned by @borkdude in #43 improves matters significantly.


Fix DiagFramePlane diagnostic

Nice. I ran into the issue with ghost cells on the Sydney flame case and worked around it by turning off interpolation. I'll test this fix on that case to make sure it works with interpolation now.
One more thing with diagnostics that I ran into is that if there is a derived variable with multiple components, you have to call out the individual component names rather than the derive name. I was going to look into relaxing that requirement.

I've been looking at this, and it might be tricky to get the diagnostics to interact with the derived because the intent was to have the diagnostics be as separate as possible in order to move them to PeleAnalysis at some point. I'll try something.

I've been looking at this, and it might be tricky to get the diagnostics to interact with the derived because the intent was to have the diagnostics be as separate as possible in order to move them to PeleAnalysis at some point. I'll try something.

It's not a big issue because one can simply list out all the components if desired. But it would be good to throw an error if someone requests a multi-component derive rather than the individual component, because right now that case is not handled properly.


Fix #5 'deterrent' is undefined

I went ahead and sent in this small PR in case you want it.
Keep rocking it - cool project!

Thanks for all these fixes !


Updated byte from 5 to 6 for Size function

Updated byte from 5 to 6 for Size function implementation for points

Can you add changes to the points.js file, and use yarn build so they propagate to the glify.js file?

@robertleeplummerjr
Sure, i'll do that

Nice work!

Published.

Nice work!

Thanks Robert.
Appreciate your work for creating this amazingly fast library.


ZIR-191: added SHA3 tests and blank string tests

looks like this isa renaming? @iddo-bentov did you intend to add more files?


Create setup.py for beaker Python package

Closes https://github.com/twosigma/beakerx/issues/5156 and https://github.com/twosigma/beakerx/issues/5067
This allows the beaker Python package to be installed using pip from the root directory of the project: pip install -e .
Once installed, beaker can be imported from any directory: from beaker.plot import *

The beaker package is now importable, but the Plot class doesn't seem to be working properly:
from beaker.plot import Plot

Plot(title="Title",
     xLabel="Horizontal",
     yLabel="Vertical",
     initWidth=500,
     initHeight=200)

Ok, updated!

Is there a display class that needs to be used with Plot?


What is Stream_204?

So, I'm also working with YouTube on the Wii and whenever I try to play a video it requests from s.youtube.com/stream_204. I've tried researching on what it is or was and couldn't find anything about it. So if anyone knows about this, please let me know

may be ads, since it is blocked in many hosts files

stream_204 and player_204 are logging requests, which could explain it being blocked described above. HOWEVER /stream_204 requests could also be made in case there was an error with video playback.
in case of wii's apiplayer, a logPlayerEvent function is used to initiate sending such requests, and if you're looking for the source of stream_204 requests, they are made whenever logData is streamingerror, which should sound pretty self-explanatory.
however, as streamingerror itself in an error request can be pretty vague, you CAN text search for streamingerror within the apiplayer swf and find logPlayerEvents that mention streamingerror.
an example string you may find:
this.logPlayerEvent("streamingerror",_loc2_);

there will be several matches like this, all of which you can look at the function name and add that to the streamingerror, as that will be sent with the request (and thus you will be able to see in the network tab).
for example, such logPlayerEvent call will be in a function called onFormatUnset, which could happen when no formats are sent OR the formats can't be played on your setup (for example h264 mp4's will have trouble playing on flash 8 and they will send a formatunset because of that).
you can change the logPlayerEvent call in onFormatUnset to better reflect what the streaming error is about.
this.logPlayerEvent("streamingerror",_loc3_);

could become
this.logPlayerEvent("streamingerror_formatunset",_loc3_);

while this could now send a /player_204 instead of /stream_204 (streamingerror is hardcoded as a thing to be sent to /stream_204), it could give you a better insight as to what's going on within the player.

Ok, Thank you for responding, this helps me out a lot

Ok, so I figured all that out and I did do the thing where you can make it download a flv and....

If you need more context, I'll provide more info


[$2000] Web - Login - Non-clickable LHN instead of "Abracadabra, you're logged in" page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Scenario 1

Log out of NewDot and request a new magic link
Navigate to email and locate the magic link - change to staging if needed
Open an new tab and navigate to the staging link

Scenario 2

Log out of NewDot and request a new magic link
Navigate to email and locate the magic link - change to staging if needed
Open an new tab and navigate to the staging link
Verify the 2FA required page is displayed. Should have a message similar to "Please enter the two-factor authentication code where you are trying to sign in."
Navigate back to the original tab - Keep the second tab open
Verify the log in flow is now asking the user to enter the 2FA code
Enter the 2FA code
Verify the user can log in
Navigate to the secondary tab
Verify the "Abracadabra, you're logged in" page is displayed

Scenario 3:

Log out of NewDot and request a new magic link
Navigate to email and locate the magic link - change to staging if needed
Open an new INCOGNITO window and navigate to the staging link

Scenario 4:

Log out of the account
Enter the email on the email field and continue
Verify the there's a message below that says "Not [Email]?" and a link to "Go back"
Click on "Go Back"
Verify the email is still displayed in the email field
Continue with the log in flow
Navigate to the email inbox and look for the magic link email
Change the link to staging if needed
Open a new tab and paste the link in the URL

Scenario 5:

On the log in screen, enter a new account email
Navigate to the email inbox and open the validate email and copy the link
Modify the last portion of the link by a character, i.e.
In a text box - Formulate the URL by using the path obtained from step 3 http://staging.new.expensify.com/v/

E.g if the original link was https://stagin.new.expensify.com/v/7453760/123884
change a single character > https://staging.new.expensify.com/v/7453760/123888

Navigate to the compiled link
Verify you're redirected the "Magic code expired" page
Click on the "Request new magic code here"
Verify the user receives a new magic link
Change the link to staging, open a new tab and navigate to the link

Expected Result:
For both scenarios: "Abracadabra, you're logged in" page should be displayed
Actual Result:
For both scenarios: Non-clickable LHN (logged in pp) is displayed instead of "Abracadabra, you're logged in"" page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
https://expensify.testrail.io/index.php?/tests/view/3490257
https://expensify.testrail.io/index.php?/tests/view/3490091
https://expensify.testrail.io/index.php?/tests/view/3490191
https://expensify.testrail.io/index.php?/tests/view/3490257
https://expensify.testrail.io/index.php?/tests/view/3490256
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Scenario 1
https://github.com/Expensify/App/assets/93399543/0d371892-bca6-4a70-a51a-82709bf82baa
Scenario 2
https://github.com/Expensify/App/assets/93399543/68d0fff0-6373-46b8-a1dc-f2ac1f28819d
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team / @natnael-guchima
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0154116efc17a0ee13
Upwork Job ID:<PHONE_NUMBER>300412928
Last Price Increase: 2023-06-24

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Taking this over from @joelbettner

Wasn't able to reproduce w/ scenario 1 in dev, but was able to reproduce on staging. I think the difference was that the desktop deeplink was making it not work as expected?

Was able to reproduce this in dev by removing this dev environment check

So it seems like what's happening here is that we're redirecting to new-expensify://URL here, and that's causing the request to the transition page w/ the correct exitTo to be cancelled:

and that seems to be why the flow is failing?

I reproduced this on production. Demoting it from deploy blocker to regular bug.

No initial proposals till now. Will circle back once we have.

No proposals still

@roryabraham There hasn't been any proposals for this issue. Could we raise the bounty?
I think the BZ here is @puneetlath  but I think he is out this week.

Doubled the bounty

@hoangzinh I tried even now on staging and I am getting a unresponsive spinner page with LHN.
There was also a another mention of similar issue in slack bug as well - https://expensify.slack.com/archives/C049HHMV9SM/p1686903317694329
Could you try with any of these steps as well?

Is it connected to the navigation refactor in a way that I can help you anyhow?

We already have one proposal. But it needs some dive deep and more testing time since whenever we repro this bug, it is making the local web non-actionable after that. Will try to complete the review before tomorrow.

Sorry for the delay @hoangzinh . It seems whenever i try to reproduce this issue, the local gets messed up and blocking me to focus on other priority issues as well. Will close it out this weekend by spending more time on it.

@hoangzinh  Could you kindly check if you able to reproduce the issue with the slack tests you mentioned currently? It is only leading to this bug https://github.com/Expensify/App/issues/21258
Not of the steps is reproducible currently

Just to make sure I understand. The bug is still happening? Or it's working as expected now?

Requested a retest by Applause: https://expensify.slack.com/archives/C9YU7BX5M/p1688079598241329

Just to make sure I understand. The bug is still happening? Or it's working as expected now?

@puneetlath  The bug was transforming into different cases for sometime(since there where multiple scenarios in OP), could be due to external changes. As of now, the bug is transformed into a relatable state of this bug https://github.com/Expensify/App/issues/21258, where the view is frozen but the content is shown. (which is also fixed and recently deployed)
So I doubt this will be reproducible but not entirely sure if all related scenarios are fixed, so its a good thing we have requested for a re-test - https://github.com/Expensify/App/issues/20410#issuecomment-1613900475

@hoangzinh please report this as a new bug in #expensify-bugs as it seems different from what this issue was originally about.


[BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?
Starting ROBLOX on acer nitro laptop and all i see is def ROBLOX i turned tracking and every thing on and still def i clicked force reinstall same issue still.

Also preview wont work it just loads endlessly

I don't understand, can you better explain please?

Nvm PC broke lol


Mass-assign catalog to manifests

This was a head-scratcher of an omission, because you can mass-nest manifests by shift-clicking a list and then selecting options already, but when I try to add a catalog(which is my number 1 workflow oversight when adding manifests!)  to multiple manifests the selections don't appear. I'm asking other folks to confirm it's not just my install/setup

This is now implemented in 1.2.0. You can select multiple manifests, right-click and assign them to catalogs.


⚠ Bofrost.fr has degraded performance

In 2aaf7db, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 819 ms

Resolved: Bofrost.fr performance has improved in 974d412 after 6 minutes.


bump version to 010 and make it snapshot, and rename container to engine-container

calling it docker-engine-container reinforces that this is for making a container once we have deployed a docker host.  this is to distinguish it from other future approaches viz using jclouds:docker and specifying the docker image in that API.

👍 lgtm, agree with the rationale for the renaming.


ClassCastException while triggering a build

Instead of triggering the build, the following exception occurs in the jenkins.log:
WARNUNG: org.jenkinsci.plugins.pollmailboxtrigger.PollMailboxTrigger.run() failed for org.jenkinsci.plugins.workflow.job.WorkflowJob@3898e0ce[MyTISM-Core]
java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject
at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:124)
at hudson.triggers.Trigger.checkTriggers(Trigger.java:278)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:226)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Steps to reproduce
How can we reproduce the issue

Create a pipeline
configure build trigger with poll-mailbox-trigger plugin
wait until the trigger occurs

Expected behaviour
Build should have been triggered
Actual behaviour
Above mentioned CCE is thrown and logged in jenkins.log
Server configuration
Operating system: Ubuntu 16.04.2
Jenkins Version: 2.60.1
Plugin Version: 1.025
Mail Server: gmail
Additional Steps/Questions

[x] other information which may help? setup is too simple
[x] Do you know if you're you able to connect to to your mail server via IMAP? Sure
[x] What log messages do you receive, when you press the "Test Connection" button? Everything is ok there, it finds the trigger message I put there
[x] Have you followed the [troubleshooting section on the plugin page]:
not applicable, the mail setup is ok.

Pipeline/workflow job is unsupported.
Try Freestyle job which works.
Is it possible to add Pipeline support?

Can we have this feature for the pipeline/workflow.

I've created the following issue, to track adding Jenkins Pipeline support.
If anyone (@autogun / @sumitg1) has any experience of adding pipeline support, please feel free to submit a PR (thanks).


prometheus Startup Readiness probe keeps on failing. pod Events: Startup probe failed: HTTP probe failed with statuscode: 503

Prometheus Startup Readiness probe keeps on failing. pod Events: Startup probe failed: HTTP probe failed with statuscode: 503
I have increase the timeout but still it's giving
Events:
Type     Reason                  Age                 From                     Message

Normal   Scheduled               13m                 default-scheduler        Successfully assigned monitoring/prometheus-k8s-0 to da-cicd-r2-srv-17
Normal   SuccessfulAttachVolume  13m                 attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-f8997b2a-37ab-408a-8c7b-39bd7e150518"
Normal   Pulled                  13m                 kubelet                  Container image "quay.io/coreos/configmap-reload:v0.0.1" already present on machine
Normal   Created                 13m                 kubelet                  Created container rules-configmap-reloader
Normal   Pulled                  13m                 kubelet                  Container image "quay.io/coreos/prometheus-config-reloader:v0.33.0" already present on machine
Normal   Created                 13m                 kubelet                  Created container prometheus-config-reloader
Normal   Started                 13m                 kubelet                  Started container prometheus-config-reloader
Normal   Started                 13m (x2 over 13m)   kubelet                  Started container prometheus
Normal   Pulled                  13m (x2 over 13m)   kubelet                  Container image "quay.io/prometheus/prometheus:v2.24.1" already present on machine
Normal   Created                 13m (x2 over 13m)   kubelet                  Created container prometheus
Normal   Started                 13m                 kubelet                  Started container rules-configmap-reloader
Warning  Unhealthy               11m (x11 over 13m)  kubelet                  Readiness probe failed: HTTP probe failed with statuscode: 503
apiVersion: apps/v1
kind: StatefulSet
metadata:
labels:
app: prometheus
prometheus: k8s
name: prometheus-k8s
namespace: monitoring
ownerReferences:

apiVersion: monitoring.coreos.com/v1
blockOwnerDeletion: true
controller: true
kind: Prometheus
name: k8s
spec:
podManagementPolicy: Parallel
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
app: prometheus
prometheus: k8s
serviceName: prometheus-operated
template:
metadata:
creationTimestamp: null
labels:
app: prometheus
prometheus: k8s
spec:
containers:

args:

--web.console.templates=/etc/prometheus/consoles
--web.console.libraries=/etc/prometheus/console_libraries
--storage.tsdb.retention.size=30GB
--config.file=/etc/prometheus/config_out/prometheus.env.yaml
--storage.tsdb.path=/prometheus
--storage.tsdb.retention.time=15d
--web.enable-lifecycle
--storage.tsdb.no-lockfile
--web.enable-admin-api
--web.route-prefix=/
image: quay.io/prometheus/prometheus:v2.24.1
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 6
httpGet:
path: /-/healthy
port: web
scheme: HTTP
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
name: prometheus
ports:
containerPort: 9090
name: web
protocol: TCP
readinessProbe:
failureThreshold: 120
httpGet:
path: /-/ready
port: web
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 15
resources:
requests:
memory: 2Gi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /etc/prometheus/config_out
name: config-out
readOnly: true
mountPath: /prometheus
name: prometheus-k8s-db
subPath: prometheus-db
mountPath: /etc/prometheus/rules/prometheus-k8s-rulefiles-0
name: prometheus-k8s-rulefiles-0

args:

--log-format=logfmt
--reload-url=http://localhost:9090/-/reload
--config-file=/etc/prometheus/config/prometheus.yaml.gz
--config-envsubst-file=/etc/prometheus/config_out/prometheus.env.yaml
command:
/bin/prometheus-config-reloader
env:
name: POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
image: quay.io/coreos/prometheus-config-reloader:v0.33.0
imagePullPolicy: IfNotPresent
name: prometheus-config-reloader
resources:
limits:
cpu: 100m
memory: 25Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /etc/prometheus/config
name: config
mountPath: /etc/prometheus/config_out
name: config-out

args:

--webhook-url=http://localhost:9090/-/reload
--volume-dir=/etc/prometheus/rules/prometheus-k8s-rulefiles-0
image: quay.io/coreos/configmap-reload:v0.0.1
imagePullPolicy: IfNotPresent
name: rules-configmap-reloader
resources:
limits:
cpu: 100m
memory: 25Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /etc/prometheus/rules/prometheus-k8s-rulefiles-0
name: prometheus-k8s-rulefiles-0
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext:
fsGroup: 2000
runAsNonRoot: true
runAsUser: 1000
serviceAccount: prometheus
serviceAccountName: prometheus
terminationGracePeriodSeconds: 600
volumes:

name: config
secret:
defaultMode: 420
secretName: prometheus-k8s
emptyDir: {}
name: config-out
configMap:
defaultMode: 420
name: prometheus-k8s-rulefiles-0
name: prometheus-k8s-rulefiles-0
updateStrategy:
type: RollingUpdate
volumeClaimTemplates:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
prometheus: k8s
creationTimestamp: null
name: prometheus-k8s-db
spec:
accessModes:

ReadWriteOnce
resources:
requests:
storage: 50Gi
storageClassName: rook-block
volumeMode: Filesystem
status:
phase: Pending

I'm running into this same issue on k3s v1.24.2+k3s2 using release-v0.11
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.4 LTS
Release:	20.04
Codename:	focal
Interestingly, v0.10 didn't have this problem when I tested it, but I went to v0.11 as it's listed as supported on Kubernetes v1.24.2
Digging into the logs I quickly found what the issue appears to be:
ts=2022-08-22T19:53:02.086Z caller=manager.go:317 level=error component="discovery manager scrape" msg="Cannot create service discovery" err="open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory" type=kubernetes
For some reason the kubernetes bearer token isn't being loaded into the container. I verified by logging into the container and found that the /var/run/secrets/kubernetes.io/serviceaccount/ path doesn't exist. I'm not sure what changed between 0.10 and 0.11 that might cause this behavior.

Facing the same issue, with version v2.8.0. Please help ?

This is probably caused by the service account not auto-mounting the token.
To fix it update your ServiceAccount (change <NAME>):
kubectl patch serviceaccount <NAME> -p '{"automountServiceAccountToken": true}'

This is probably caused by the service account not auto-mounting the token.
To fix it update your ServiceAccount (change <NAME>):
kubectl patch serviceaccount <NAME> -p '{"automountServiceAccountToken": true}'

Adding automounting the service token, still did not fix this issue.


Generate Button on click (The button Text still remains same)

Since I noticed that if I clicked on the generate button in the GitHub Profile generator then text appears below the button that produces. Still, changing the button text will be more useful and more user-friendly.

Also while Reviewing the Code I noticed there are unnecessary codes are there:

Like here the await will have no effect on that instruction.

So please assign me this issue I will work on this and please add the labels hactoberfest and gssoc-extd.

@BamaCharanChhandogi  please look for this issue and assign it to me

@BamaCharanChhandogi  I am looking forward to your response

@BamaCharanChhandogi  I made the pull request #94


Remember previously merged PRs for detecting pushes to master

Adds an extra list to the state with recently merged PRs. When detecting a push to master we use this list to check if the push is from merging one of the known PRs.

@OpsBotPrime merge

Rebased as e163a285993ad723be9be15bc792371ce449f161, waiting for CI …

CI job :yellow_circle: started.


[help] deploy to other platform

I have spent several hours trying to deploy this project to google app engine, but because of  i wouldn't like to add billing info  to google console or because of there are changes to site i can't manage.
Could you please, give instruction or intergrate to the readme file a link to deploy your project to other free hosting server like heroku or pythonanyehre?

Only GAE can host It.


associated content types with policy group type and assigned group pe…

This PR does not account for "advanced outsider permissions" - only permissions within the group type. This PR may include updates in previous PRs, so please review and merge AFTER merging the prior PRs.

Merged all previous PRs prior to this one.


Update Android TensorFlow classifier

Hi!
Any chance to update the Android TensorFlow classifier according to these changes?:

https://github.com/Azure-Samples/cognitive-services-android-customvision-sample#compatibility
https://github.com/Azure-Samples/cognitive-services-android-customvision-sample/blob/master/app/src/main/java/demo/tensorflow/org/customvision_sample/MSCognitiveServicesClassifier.java

Done in the latest version - it will look for the relevant transformation layer and only apply the image RGB changes if the layer is not present.


Poor coverage of langtools by openjdk tests

There are almost no langtools tests ran. (not even tier1 used in GHA by upstream)
extended.openjdk:

target
jdk
tests

langtools_extpath_j9
ibm/j9
tools/javap/ExtPath.java

special.openjdk:

target
jdk
tests

langtools_custom
all
only runs default tools/javac/4241573/T4241573.java

@zzambers as mentioned in slack I have assigned the issue to you.  Please feel free to update the project status according to your work plan. Initially I've set as Q2 iteration 6 (June 11 - June 30).

done by: https://github.com/adoptium/aqa-tests/pull/5353


Adds CSS for rtl

Seems to work OK to me on fawiki.

That looks ok to me, even though I can't test it now


defer logging config to the application

applications should manage log levels, etc
e.g. see relay-py:samples/app.py + logging.yml

good point.  will merge this with or after the update to the sample.


Add support json in node/edge metadata

Ex:
{
Metric: {
Last: 123,
Start: 456
}
}

https://softwarefactory-project.io/r/#/c/7631/

patch merged.


Webpack 4.16.1 reverses chunk orders on Storybook

Bug or support request summary
I've noticed a bug happening on the latest Storybook alpha (v4.0.0-alpha.14) with Webpack v4.16.1 and up. Specifically it's https://github.com/webpack/webpack/pull/7721. This change has caused the orders of the production build of Storybook JS and CSS chunks to be injected in reverse (from runtime -> vendor -> main file to the other way around).
Steps to reproduce
The CRA example can be used to reproduce this issue.

Go to the example CRA app and run npm run build-storybook after doing the npm install prerequisite steps. Granted it seems like the current state of it is broken so I had to run npm install moment for the missing dependency and comment out LifecycleLogger stories because of an unidentified production build issue.
Make sure you're running Webpack ^4.16.1, so anything above is fine.
Run the static Storybook generated app on http-server or anything else.
Inspect the manager and the iframe for the preview. In both cases the injected JS and CSS would be injected in the reverse order.

Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/react 4.0.0-alpha.14 (and any other related packages)
webpack 4.16.1 and up

Affected platforms
Only happens on production build because that's the only time chunk splitting based on vendors and runtime occurs.
Screenshots / Screencast / Code Snippets (Optional)

Tried it again on the current version of master and it seems like @ndelangen fixed it with #3919. I haven't looked into how, but thanks!

Let me know if you run into any troubles following that change @diagramatics 🙇


[HPM] Error occurred while trying to proxy request /weatherforecast from localhost:4200 to https://localhost:5001

I am following the steps outlined in this document and getting the error that you mention in the Troubleshooting section. However, just refreshing the browser does not resolve it and I'm having trouble finding any resources on the web to help troubleshoot it.

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

ID: c924f1c1-823e-3e29-bf09-405fc4c6bbb8
Version Independent ID: 585c2426-5f9b-8499-8eda-0e56bd64c93c
Content: Create an ASP.NET Core app with Vue - Visual Studio (Windows)
Content Source: docs/javascript/tutorial-asp-net-core-with-vue.md
Product: visual-studio-windows
Technology: vs-javascript
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@itf2012 -- thank you for your feedback.  Please consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

cc @Mikejo5000 for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.

Why is this closed with no resolution??  I am having the same issue as the OP.  Please advise.

@dstep2007 @itf2012  Thanks for your feedback and for reporting this issue. To make sure that this is logged in the right place, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.

@dstep2007 If you identify a doc issue that we can address, such as a workaround, please let us know. Thanks!


Prevent mutation of color variables passed to color setters

Background
#2732
Changes
Instead of mutating the color variables when missing the alpha value, return a new color array instead.

getColor is handled similarly in PathTesselator.

getColor is handled similarly in PathTesselator.

Fixed this one as well!


Add 'recursive' mode to the workflow

Makes the workflow clone the repo and its submodules, fixing the error on the last run.

Seems like there's yet another error in the workflow, will see if i can fix it.


Don't allow missing conformances from superclasses to block Sendable subclasses

Fixes rdar://83636964.

@swift-ci please smoke test and merge


Installation on Any Kubernetes?

Bugs should be filed for issues encountered whilst operating bank-vaults.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
Hi guys, is this operator supported for any Kubernetes installation or it's just Banzai's Kubernetes?
I am trying to follow https://banzaicloud.com/blog/inject-secrets-into-pods-vault-revisited/ and can't move ahead as one of the secrets seems to be missing.

➜  bank-vaults git:(master) export VAULT_TOKEN=$(kubectl get secrets vault-unseal-keys -o jsonpath={.data.vault-root} | base64 --decode)
Error from server (NotFound): secrets "vault-unseal-keys" not found

Expected behaviour:
I should get this secret to move ahead.
Steps to reproduce the bug:
Follow the exact steps from the bug.
Additional context:
Add any other context about the problem here.
Environment details:

Kubernetes version (e.g. v1.10.2): v1.15.6
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): AWS using KOPS
bank-vaults version (e.g. 0.4.17): Not sure. Just following the blog.
Install method (e.g. helm or static manifests): Helm
Logs from the misbehaving component (and any other relevant logs):
Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

/kind bug

HI @ashishxooa,
the operator runs on any kind of Kubernetes installations and has no dependencies on the Banzai Cloud Kubernetes Distribution (PKE), the CI tests (if you check them) run on Minikube and KinD for example.
Could you please check the logs of the Pods first?

@bonifaido thanks for the clarification.
So I did a re-installation again and still having the same issue. I found one of the pod is crashing, not sure if that was the case last time also.

➜  helm-new git:(master) ✗ kubectl logs -f vault-operator-549cf4bc89-blv82
{"level":"info","ts":1586869928.524237,"logger":"cmd","msg":"Watched namespace: "}
{"level":"info","ts":1586869933.1233077,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8383"}
{"level":"info","ts":1586869933.1236484,"logger":"cmd","msg":"Registering Components."}
{"level":"info","ts":1586869936.637184,"logger":"cmd","msg":"Starting the Cmd."}
I0414 13:12:16.721974       1 leaderelection.go:242] attempting to acquire leader lease  vault-infra/vault-operator-lock...
{"level":"info","ts":1586869936.7224932,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
I0414 13:12:34.160710       1 leaderelection.go:252] successfully acquired lease vault-infra/vault-operator-lock
{"level":"info","ts":1586869954.1610103,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"vault-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1586869954.4215934,"logger":"controller-runtime.controller","msg":"Starting Controller","controller":"vault-controller"}
{"level":"info","ts":1586869954.4218082,"logger":"controller-runtime.controller","msg":"Starting workers","controller":"vault-controller","worker count":1}
{"level":"info","ts":1586870103.2286444,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870131.1221032,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870133.2322128,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870173.4761329,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870228.2673376,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870283.0550942,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870337.8428705,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}
{"level":"info","ts":1586870392.63062,"logger":"controller_vault","msg":"Reconciling Vault","Request.Namespace":"vault-infra","Request.Name":"vault"}

=============================================

➜  helm-new git:(master) ✗ kubectl logs -f vault-0 vault
telemetry.disable_hostname has been set to false. Recommended setting is true for Prometheus to avoid poorly named metrics.
==> Vault server configuration:

                 Cgo: disabled
          Listener 1: tcp (addr: "<IP_ADDRESS>:8200", cluster address: "<IP_ADDRESS>:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "enabled")
           Log Level: debug
               Mlock: supported: true, enabled: true
       Recovery Mode: false
             Storage: file
             Version: Vault v1.3.1

==> Vault server started! Log data will stream in below:
2020-04-14T13:15:34.662Z [INFO]  proxy environment: http_proxy= https_proxy= no_proxy=
2020-04-14T13:15:34.663Z [WARN]  no api_addr value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set
2020-04-14T13:15:34.663Z [DEBUG] storage.cache: creating LRU cache: size=0
2020-04-14T13:15:34.722Z [DEBUG] cluster listener addresses synthesized: cluster_addresses=[<IP_ADDRESS>:8201]
2020-04-14T13:15:34.826Z [INFO]  core: security barrier not initialized
2020-04-14T13:15:36.419Z [INFO]  core: security barrier not initialized
======================================================================

➜  helm-new git:(master) ✗ kubectl logs -f vault-0 bank-vaults
time="2020-04-14T13:21:27Z" level=info msg="initializing vault..."
time="2020-04-14T13:21:27Z" level=info msg="vault metrics exporter enabled: :9091/metrics"
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

using env:	export GIN_MODE=release
using code:	gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /metrics                  --> github.com/gin-gonic/gin.WrapH.func1 (3 handlers)
[GIN-debug] Listening and serving HTTP on :9091
time="2020-04-14T13:21:27Z" level=info msg="initializing vault"
time="2020-04-14T13:21:27Z" level=fatal msg="error initializing vault: error testing keystore before init: error getting secret for key 'vault-test': secrets "vault-unseal-keys" is forbidden: User "system:serviceaccount:vault-infra:vault" cannot get resource "secrets" in API group "" in the namespace "default""
Anywhere else to check? I can't see any logs for the init container config-templating. Which pod is supposed to create the secret?

There is a missing RBAC role issue here:
time="2020-04-14T13:21:27Z" level=fatal msg="error initializing vault: error testing keystore before init: error getting secret for key 'vault-test': secrets "vault-unseal-keys" is forbidden: User "system:serviceaccount:vault-infra:vault" cannot get resource "secrets" in API group "" in the namespace "default""

You have to apply the rbac.yaml as well first. From the blog:

Create a Vault instance with the operator which has the Kubernetes auth method configured
kubectl apply -f operator/deploy/rbac.yaml
kubectl apply -f operator/deploy/cr.yaml

@bonifaido I did that already.
➜  bank-vaults git:(master) kubectl apply -f operator/deploy/rbac.yaml
serviceaccount/vault unchanged
role.rbac.authorization.k8s.io/vault-secrets unchanged
rolebinding.rbac.authorization.k8s.io/vault-secrets unchanged
clusterrolebinding.rbac.authorization.k8s.io/vault-auth-delegator unchanged

Oh! got it, need to have the RBAC in default namespace, I did that in the vault-infra namespace. Will check after doing it in the default ns.

Yes, the RBAC example in the repo is prepared for the default namespace ServiceAccount.

@bonifaido thanks, that worked.
Moving ahead with the demo, one of the command says "vault kv put secret/accounts/aws AWS_SECRET_ACCESS_KEY=s3cr3t",
I was getting some error there, doubted it to be with Istio which was enabled on my default namespace. Removed Istio from default and it worked. So is there any compatibility issue with Istio? as Istio is a must for my workload.
➜  bank-vaults git:(master) ✗ vault kv put secret/accounts/aws AWS_SECRET_ACCESS_KEY=s3cr3t Get https://<IP_ADDRESS>:8200/v1/sys/internal/ui/mounts/secret/accounts/aws: EOF
On the proxy also, I could see some error.
Handling connection for 8200
E0414 19:54:27.712763   10911 portforward.go:400] an error occurred forwarding 8200 -> 8200: error forwarding port 8200 to pod 1fe23c493be9edf756619fddf5af03eb86e4d33f91d43ae60b05f49eb368b0d9, uid : exit status 1: 2020/04/14 14:24:28 socat[28660] E connect(5, AF=2 <IP_ADDRESS>:8200, 16): Connection refused

Istio is supported, but you have to enable the support first, see: https://github.com/banzaicloud/bank-vaults/blob/2481a75e3767e2cf3e4cf5e948692ce83b9f44ca/operator/deploy/cr.yaml#L195

Closing this, since the original issue has been answered.

this issue happen to me when I delete/redeploy everything, except the namespace.
After investigation, I found that vault-unseal-keys secret has not been deleted when I deleted vault-operator, vault-cluster,... etc.
So to fix the issue, I just delete the secret manually:
k -n vault delete secret vault-unseal-keys


Mapping multiple entities from one response

How do I map multiple entities types from a single response?
Say for instance I hit a user_with_tasks endpoint which returns me a user but all their tasks also. What would I use to map to both models. I found some code somewhere that shows I would use "dataTransformer" and then inside use
data.tasks.map((task) => {
     Object.assign(task);
     Object.assign(task.attributes);
});

does this look right? I might be completely misunderstanding.

Yeah I was on the wrong track although the above works assign operation is important in my context the active ingredient to map to multiple models is simply the relationship  settings if that is setup the mapping to multiple models is automatic <3


autoscale-lr ,imgs_per_gpu and lr?

It seems autoscale-lr does not count imgs_per_gpu, does that mean if I changed imgs_per_gpu, I can no longer use a simple autoscale-lr? Instead I need to apply linear scale rule to manually set lr in config?

Yes.

We recommend modifying the learning rate manually.