fix: test errors and warnings - iteration 2 (#12212)

SUMMARY
Remove tests errors and warnings to improve results readability.
The following errors and warnings have been removed:
Warning: Failed prop type: Invalid prop `option` supplied to `MetricDefinitionValue`.

spec/javascripts/explore/components/MetricsControl_spec.jsx

Error: Not implemented: navigation (except hash changes)

spec/javascripts/components/AlteredSliceTag_spec.jsx

Warning: Unmatched <HTTP_METHOD> to <URL>

spec/javascripts/explore/components/SaveModal_spec.jsx
spec/javascripts/datasource/ChangeDatasourceModal_spec.jsx

Warning: Each child in a list should have a unique "key" prop.

spec/javascripts/explore/components/SelectControl_spec.jsx
spec/javascripts/explore/components/SelectControl_spec.jsx

Warning: Failed prop type: The prop `dashboardId` is marked as required in `ChartHolder`,
but its value is `undefined`.

spec/javascripts/dashboard/components/gridComponents/ChartHolder_spec.jsx

Warning: Failed prop type: The prop `slice` is marked as required in `Chart`, but its value is `undefined`.

spec/javascripts/dashboard/components/gridComponents/ChartHolder_spec.jsx

Warning: Failed prop type: The prop `filters` is marked as required in `Tab`, but its value is `undefined`.

spec/javascripts/dashboard/components/gridComponents/Tab_spec.jsx

Warning: Failed prop type: The prop `setDirectPathToChild` is marked as required in `Tab`,
but its value is `undefined`.

spec/javascripts/dashboard/components/gridComponents/Tab_spec.jsx

Error: fetch-mock: No fallback response defined for <HTTP_METHOD> to <URL>

spec/javascripts/datasource/ChangeDatasourceModal_spec.jsx
spec/javascripts/explore/components/EmbedCodeButton_spec
spec/javascripts/explore/components/SaveModal_spec.jsx
spec/javascripts/sqllab/QuerySearch_spec.jsx
spec/javascripts/views/CRUD/data/database/DatabaseModal_spec.jsx

Warning: Failed prop type: The prop `savedMetric.metric_name` is marked as required
in `AdhocMetricEditPopover`,  but its value is `undefined`.

spec/javascripts/explore/components/AdhocFilterControl_spec.jsx

UnhandledPromiseRejection: This error originated either by throwing inside of an async function
without a catch block, or by rejecting a promise which was not handled with .catch().

spec/javascripts/explore/components/EmbedCodeButton_spec

When testing, code that causes React state updates should be wrapped into act(...)

spec/javascripts/explore/components/EmbedCodeButton_spec
spec/javascripts/messageToasts/components/Toast_spec.jsx
spec/javascripts/views/CRUD/data/database/DatabaseModal_spec.jsx

Warning: Failed prop type: Invalid prop `option` supplied to `MetricDefinitionValue`.

spec/javascripts/explore/components/MetricsControl_spec.jsx

#12212
@rusackas @junlincc @villebro
ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12214 (44c947a) into master (84266bf) will decrease coverage by 6.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12214      +/-   ##
==========================================
- Coverage   66.16%   59.29%   -6.88%
==========================================
  Files        1015      959      -56
  Lines       49642    46878    -2764
  Branches     4970     4353     -617
==========================================
- Hits        32848    27794    -5054
- Misses      16656    19084    +2428
+ Partials      138        0     -138

Flag
Coverage Δ

cypress
50.98% <ø> (+3.44%)
:arrow_up:

javascript
?

python
63.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...uperset-frontend/src/dashboard/util/dnd-reorder.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...rset-frontend/src/dashboard/util/getEmptyLayout.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/resizable/ResizableHandle.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/dashboard/util/getFilterScopeFromNodesTree.js
0.00% <0.00%> (-93.48%)
:arrow_down:

...set-frontend/src/views/CRUD/alert/ExecutionLog.tsx
11.76% <0.00%> (-88.24%)
:arrow_down:

...src/dashboard/components/gridComponents/Header.jsx
10.52% <0.00%> (-86.85%)
:arrow_down:

superset-frontend/src/components/IconTooltip.tsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...rc/dashboard/components/gridComponents/Divider.jsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...end/src/SqlLab/components/ExploreResultsButton.jsx
8.00% <0.00%> (-84.00%)
:arrow_down:

...nd/src/views/CRUD/data/query/QueryPreviewModal.tsx
14.70% <0.00%> (-82.97%)
:arrow_down:

... and 397 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84266bf...44757eb. Read the comment docs.

Codecov Report

Merging #12214 (44c947a) into master (84266bf) will decrease coverage by 6.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12214      +/-   ##
==========================================
- Coverage   66.16%   59.29%   -6.88%
==========================================
  Files        1015      959      -56
  Lines       49642    46878    -2764
  Branches     4970     4353     -617
==========================================
- Hits        32848    27794    -5054
- Misses      16656    19084    +2428
+ Partials      138        0     -138

Flag
Coverage Δ

cypress
50.98% <ø> (+3.44%)
:arrow_up:

javascript
?

python
63.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...uperset-frontend/src/dashboard/util/dnd-reorder.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...rset-frontend/src/dashboard/util/getEmptyLayout.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/resizable/ResizableHandle.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/dashboard/util/getFilterScopeFromNodesTree.js
0.00% <0.00%> (-93.48%)
:arrow_down:

...set-frontend/src/views/CRUD/alert/ExecutionLog.tsx
11.76% <0.00%> (-88.24%)
:arrow_down:

...src/dashboard/components/gridComponents/Header.jsx
10.52% <0.00%> (-86.85%)
:arrow_down:

superset-frontend/src/components/IconTooltip.tsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...rc/dashboard/components/gridComponents/Divider.jsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...end/src/SqlLab/components/ExploreResultsButton.jsx
8.00% <0.00%> (-84.00%)
:arrow_down:

...nd/src/views/CRUD/data/query/QueryPreviewModal.tsx
14.70% <0.00%> (-82.97%)
:arrow_down:

... and 397 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84266bf...44757eb. Read the comment docs.


Add tests for plotting

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (9e9cc20) 67.84% compared to head (a9da163) 86.71%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##              dev      #14       +/-   ##
===========================================
+ Coverage   67.84%   86.71%   +18.86%
===========================================
  Files          11       12        +1
  Lines         395      399        +4
===========================================
+ Hits          268      346       +78
+ Misses        127       53       -74

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


Hey, I was trying to list all the orgs but it says no orgs found when it was listed there

Hey, I was trying to target an orgs with
But I have this in my orgs.. while I have this
ibm cloud foundry link](https://cloud.ibm.com/account/cloud-foundry
)

$ cf orgs
Getting orgs as<EMAIL_ADDRESS>No orgs found.

it doesn't match and there's no orgs found.

Hey @abrhambas01!
We unfortunately do not know how IBM CF manages orgs but I would assume it would be relatively similar to normal, what version of the cf CLI are you using, are you sure you're targeting the right API with the right user name?
Thanks!


patch

:white_check_mark: Build TheIdServer 7.1.2-ci.1+9.build.2932 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/c56f0985a0 by @aguacongas)


Remove the texlive dependency

itex can just install texlive when it is not installed yet.

This would add tar to the list of requirements


mapWritableState pollutes component definition

Reproduction
https://github.com/Demak/pinia-bug
Steps to reproduce the bug
Clone repository and open core directory in Visual Studio Code. Open src/App.vue file from explorer panel. Hover over "computed" property in component definition, tooltip should display that all properties from pinia's state are included in computed properties.

Hover over "this.stuff" inside "created" hook, tooltip should display that this property is present in component and display its type as set in store, even though this property is not included in component.

Only properties which are provided to mapWritableState are actually added on runtime, problem seems to be exlusively with typescript type definitions.
I am using extensions TypeScript Vue Plugin (Volar) version 1.1.3 and Vue Language Features (Volar) version 1.1.3.
If mapWritableState is replaced with mapState, component definition appears to be correct.

Expected behavior
Only properties defined in second argument of mapWritableState appear in component definition type.
Actual behavior
All properties from pinia state are extending component type definition and are considered present in editor.
Additional information
No response

Unfortunately recent fix seems to have lead to a new problem:

I am not sure what exactly is wrong now, VSCode doesn't give me much information about an error.

fixed

Seems to be working as expected now, thank you.


Status effect prediction is completely broken again

Description

Reproduction

Screenshots

Additional context

If this is just the one-tick stutter thing, AFAIK this is probably just the issue with collision start/stop mispredicts and not status effects, E.g., I haven't noticed any mispredicts after giving soap entities a slip-on-use-interaction and directly triggering a slip. The stutter only happens when relying on collision start/stop events.

i had a similar mispredict occur with other status effects but didnt get video

Got bad ui statuses while being a pAI and, after ghosting, the statuses persisted.
Made a bug report and got linked to this issue.
Pictures following of bad ui statuses:

i think i was wrong or it was fixed


feat: added a simple shell script for bundling

closes #2

Currently missing.

CI
Releases

Actually CI doesn't make much sense so far into the project.


Batch Update of SEO Scores

Currently if the SEO scoring mechanism changes then one would have to load and save each page individually as the score is calculated by JavaScript.  It would be good if there was some way, e.g. a development task, to update these scores in a batch like manner.
The problem here though is that the score is calculated using JavaScript which is not available to command line PHP without installing likes of Node, the only other option I can think of is pushing the score calculation back to PHP and calling a suitable method using AJAX.  However this would slow things down in the interface.
Just a placeholder for now, it's a nice to have.

I agree, and have been meaning to refactor the whole scoring proces to make it:

more configurable
more robust
less coupled

What I've come up with as an approach, would roughly be:

Have the javascript generated from php (templated js, like how DisplayLogic works), this way, knowledge about the calculations would have to be moved to - and be available in php (and configuration to yaml)
Generalize seo tests that can be applied to fields/properties, e.g. SEOTest_CountTags(htmltag), _Count(words/chars), _CountOccurences(subject), _CheckAttributes(subject) (I think this list about covers the current tests, testing attributes may need a bit of work)
By generalizing these tests, we can make them both know how to calculate their score themselves, as well as how to generate themed js to live-calculate the score
These tests could be configured individually, but we may also look at configuring them to cover all fields of a certain type (like Fluent gets its translatable fields)
A generic _AjaxCheck(subject) could leave room to have a kind of fallback for more complex calculations, for example check use of the current page subject on other pages (not sure of its use though)

Curious to get your opinion on this @gordonbanderson?

Just a quick note regarding synonyms, we could look at:

http://thesaurus.altervista.org/ (synonyms api it_IT, fr_FR, de_DE, en_US, el_GR, es_ES, de_DE, no_NO, pt_PT, ro_RO, ru_RU, sk_SK)
https://words.bighugelabs.com/ or https://www.wordsapi.com/ (en only syn apis)
or add some kind of custom synonyms getter

re 'DisplayLogic' can you please clarify, lots of different hits for that phrase in search engines.
Interesting idea re using third party services for synonyms, Words API looks nice.  Guess these would have to be cached though :)  I came across an openly licensed thesaurus file when I was working on a module for Elasticsearch, will see if I can find it again.

DisplayLogic: https://github.com/unclecheese/silverstripe-display-logic
From a quick glance, I don't think it uses themed js under the hood. But the point was regarding the syntax to generate js behaviour, e.g.;
$products->displayIf("HasProducts")->isChecked();

I had a brief look at the tools you mentioned.  I've implemented a very rough import using the  BigHugeLabs just to get a feel of what's available.  It not only offers synonyms but also antonyms (opposite meaning) and similar.  One thing I did not think about initially was synonyms based on the classification of a word, e.g. 'rain' as a noun or 'rain' as a verb. Curious to know how this would be represented in a GUI interface.
I think synonyms needs to be stored locally to avoid hits on third party services, and the results of third party services need normalized so that they can be stored consistently in SilverStripe.  This sounds to me like a separate module.  This would be advantageous for several reasons:

Caching as mentioned above
Editing of synonyms by a content admin, something that may be required if the content is in a niche area English language wise such as a biological science.
Import from a third party file.  One such example of a suitable source http://www.gutenberg.org/ebooks/10681, although the text file does not appear to indicate verb, adjective etc


OIDC ID Token, Authorization Headers, Refreshing and Verification

This PR includes the commits from/replaces #534 and #620 and adds proper OIDC token validation. Please see both original PRs for descriptions and conversations about the PRs.
This now fixes #530
To summarise:

#534: Adds the ability to expose the raw OIDC token to applications behind the proxy
#620: Implement background refreshing of OIDC tokens when cookie_refresh is set > 0
Verification: Implement ValidateSessionState for the OIDC provider to properly verify the id_token. The default providers implementation does not work with OIDC and was causing issues with refreshing

I have built an image and published it here: quay.io/joelspeed/kubernetes-3 which is built from https://github.com/pusher/oauth2_proxy/tree/kubernetes and contains the commits from this PR and #464
This PR has become quite large but, having opened #620, I realised there was a bug if the cookie_refresh period was shorter than the id_token lifetime (Thanks @jhohertz), to fix this, I needed to correctly implement ValidateSessionState for OIDC which then in turn needs the changes from #534
So the resulting PR is a combination of fixes that adds a bunch of new stuff to the OIDC provider

Testing this now... With the new PRs I can reliably reproduce your merged state in the pusher:kubernetes branch from the individual PRs.
The refresh seems to be working well now as well with your additional changes... for testing I have it expiring every 10 minutes, and it's been reliably and seamlessly refreshing each time it expires.
Great stuff @JoelSpeed , hope the maintainers take this merge in.

Hi, when using your quay.io/joelspeed/kubernetes-3 image I'm getting:
2018/06/22 12:27:12 main.go:109: Get https://dex.<my-domain>/.well-known/openid-configuration: x509: failed to load system roots and no roots provided

Is the image maybe missing CA certificates? The dex. has a proper Letsencrypt certificate. Before I was using your quay.io/joelspeed/whitelist-domains-1 which was working just fine.
Btw, thanks for the greate work! This is exactly what I was looking for.

@danielm0hr There is deliberately no ca-certificate bundle installed in the image, we mount it directly from the host /etc/ssl/certs/ca-certificates.crt, you can either do that or create your own image from this one that has them installed

@JoelSpeed Thanks.
I have added the ca certificates to the image gfkse/oauth2_proxy:kubernetes-3-ca-certs which is working fine now. This is built from https://github.com/gfkse/oauth2_proxy/blob/kubernetes/Dockerfile, if you want to incorporate that...

As I've said, we are deliberately mounting the certificates from our hosts, so I won't be updating my image to add the certificates.
Given CA certificates need to be kept up to date, we find it easier to maintain a single copy on the host and mount that into multiple containers rather than rebuilding each image regularly to keep the certificates up to date, YMMV

I see your point. But does it really hurt to have the additional 256 KiB of CA certificates in the image? You can still replace the path with your host mount, can't you?
But this would enable people to use the image without any additional precautions. E.g. I'm currently using the official oauth2_proxy helm chart with this image. The chart would also have to be changed to enable mounting CA certificates from the host.

Hello @JoelSpeed. Thanks a lot for contributing this. I'm looking to leverage your changes and have deployed your image of oauth2_proxy with the configuration you partially outlined in your article on The New Stack (great series, BTW). I have a setup with dex just like in the article. The OpenID dance between oauth2_proxy and dex works, and the OAuth flow between dex and GitHub Enterprise in my case also works. For some reason, however, in the last leg of the redirects, oauth2_proxy is not including the Authorization header in the response as per your change, even though I set --set-authorization-header=true in the options, and so I get prompted to login to the Kubernetes Dashboard.
There are no logs from oauth2_proxy to help figure out what's wrong. Any suggestions on how to debug this further?
Thanks in advance!

Hi @luispollo Glad you enjoyed the series 😄
I would recommend first checking the /oauth2/auth endpoint on your proxy once you have logged in. You should be able to request this page and see a 202 response with an authorization header set.
If you see the Authorization header set here, you should be able to retrieve the bearer JWT and check that it is indeed valid. If the header isn't there then there is a problem with your OAuth2 Proxy configuration.
If you can see the header there, then it would suggest to me that you aren't getting the authorization header passed correctly, double check your ingress object, it should have the configuration snippet:
ingress.kubernetes.io/configuration-snippet: |
 auth_request_set $token $upstream_http_authorization;
 proxy_set_header Authorization $token;

The line ingress.kubernetes.io/configuration-snippet could need changing depending on your ingress controller configuration, double check what you have the annotations-prefix set as within your ingress controller

Thanks @JoelSpeed. You nailed it. It was the annotation prefix (I was missing nginx in front of my annotation in my setup with the NGINX ingress).
Things are looking good now, except I ran into #580. The OIDC provider is currently not including the groups scope in the OAuth flow, and so dex does not include groups in the ID token in my setup. I know that's unrelated to your PR, but that's the only thing missing at this point for my ideal setup to work.

@luispollo Have you tried overriding the scope?
In my config file I have:
scope="openid profile email groups audience:server:client_id:kubernetes offline_access"

Which is sent to Dex to make the request. By default the scope is only openid profile email, so I've added groups, cross client trust in dex and the offline_access scope for token refreshing.
If you set your scope to include groups you should get the groups in the ID token into the dashboard

You beat me to it, @JoelSpeed. I just found out you could override scopes. 😄
I can see groups in the JWT now. Looking into the cross-client trust in dex next. Thanks!

@JoelSpeed I reiterate the thanks on contributing this. Although also seeking your help. I have leveraged your implementation and altered slightly to create a manual OIDC provider implementation for those that don't implement the introspection endpoint. (https://github.com/tlawrie/oauth2_proxy/tree/session-refresh)
However i am getting a 502 in the NGINX ingress on Kubernetes. This is occuring on testing the cookie refresh. Have not yet gotten to testing the 12 hour session refresh.
Any thoughts on what could be causing it? I added a lot of extra debug logging and I know that its performing a save session after the session timeout.

@JoelSpeed thanks for the information, I am going to give that a try very soon.
One clarification, I currently use both the auth-url and auth-signin ingress annotations for the protected paths. These currently point to an ingress that is defined for the oauth2_proxy
If i add this custom snippet in the configmap, I will then have conflicts with the defined kubernetes ingress and service definitions which achieve a similar implementation without the cache.
Is there a best way to implement this, either without the ingresses or without the configmap?

@tlawrie I would just try to add the cache parts of the gist (L41-L53) as a custom-snippet annotation on the ingress for your proxy, but you will still need to define the http-snippet from the ConfigMap to make sure the cache path is valid.

@JoelSpeed many thanks for this change.
Right now I'm using a fork of our own that includes this PR (among others) with nginx-ingress and Keycloak and our session info gets big enough to be split into two Cookies. When refreshing the token during an /auth request it seems nginx strips all newly set Cookies except for the first one, which invalidates the session, as it now consists of two inconsistent Cookies.
nginx-ingress basically does
			auth_request_set    $auth_cookie $upstream_http_set_cookie;
			add_header          Set-Cookie $auth_cookie;

which seems to only forward the very first Set-Cookie header.
Have you seen this as well and found a solution for it?

@JoelSpeed Thanks a lot for this PR, makes this project a lot more usable to run straight in front of the Kubernetes dashboard. My setup is running a Traefik proxy in front of it, with the oauth2_proxy handling all the traffic and authenticating against Google.
The first logon works well, then after an hour the refresh happens (succesful according to the logs) and I get a new cookie back (which seems properly set from my browser). However, the dashboard hits me back with an Unauthorized error. Looking at the Auth header using the /oauth2/auth endpoint, I see my new cookie value, but the response header is already expired when decoding it, so the passed/returned header does not seem to take into account the refresh?
Anything I can check to debug this?

I could get around this by initialising it as generic OIDC provider, but then I lose the refreshToken I believe

@bcorijn I don't follow as to why you would lost the refreshToken if you initialised up to Google as a generic OIDC provider? My understanding is that it should be able to work with Googles OIDC endpoint without trouble. The generic OIDC provider stores the refresh token as part of the cookie so it should always be there?

Made some changes in a local fork

Have you got a link for this fork?

@JoelSpeed Initialising a generic OIDC provider requires passing a IssuerURL, but doing so will also use the OIDC auto-discovered login-url instead of any URL you pass yourself (Cfr https://github.com/bitly/oauth2_proxy/blob/master/options.go#L152-L161). In Google's case you need to explicitly add a query parameter to your login URL if you want to receive refresh-tokens, something that will not be present in the auto-discovered URL.
I described this and its side-effects in a bit more detail in my issue https://github.com/bitly/oauth2_proxy/issues/632.
I just pushed my changes to a local fork of your repository, these are the changes that were needed for the Google provider to return the new ID Token: https://github.com/bcorijn/oauth2_proxy/commit/661210eb7e99024285fa28e97fd1cdbcb7c09a61
I have been running with these changes the last 2 weeks (combined with the newer Google endpoints as described in issue 632) and everything works flawlessly to secure our kubernetes dashboard behind Google OIDC.

@bcorijn I've implemented a Google Connector for a project called Dex which is based on the generic OIDC authentication and uses https://accounts.google.com's autodiscovery mechanism and works without issue for us. The code path is nearly identical to the one in the Bitly Proxy OIDC connector and therefore should work for Google.
What you are missing in terms of refreshing is the prompt=consent query parameter, see: https://github.com/JoelSpeed/dex/blob/c1b2a4f4d7b6ebc46fecfb6c7987e1bab023e336/connector/google/google.go#L123-L125
But you should be able to add offline_access to the scope parameter to get the offline_access part of the login URL sorted.
I've not needed to override the auto-discovered URLs in this implementation and I can assure you it is working.

@JoelSpeed Not sure I'm completely following you now. The auto-discovered URL from Google is perfectly correct for basic authentication, but in the current GenericOIDC implementation in this project it won't include the offline_access param that is needed for Google to provide you with refresh tokens (https://developers.google.com/identity/protocols/OAuth2WebServer#offline). The line you linked from the Dex implementation adds this exact parameter as far as I understand (together with the prompt=consent, which serves a different purpose)
The Google provider in this project does handle Google's specific implementation and will refresh it's token as expected, but will not update the original ID Token with the refreshed token (as the Generic one does after your PR), which is what I tried to solve in the commit I linked.
Creating the possibility of setting custom parameters on the GenericOIDC provider login URL's would also have the same end-result, but feels like including provider-specific functionality in the generic provider while leaving the Google provider in a broken state (returning expired ID tokens even after a successful refresh).

Hello @JoelSpeed!
we are trying to create simple configuration with oauth2_proxy as a proxy for dashboard
after successful login to google proxy proxy creates Authorization: Bearer eyJhbGciOiJSUzI1NiIsImt... token and pass it to dashboard
Dashboard says we are authenticated and try to access resources on api server.
Api reports this error:
E1004 10:44:12.649338       1 authentication.go:63] Unable to authenticate the request due to an error: [invalid bearer token, [invalid bearer token, invalid bearer token]]
We now use other oidc proxy, it works well, but want to replace it because of token refresh feature.
Could you please advise, what we miss with configuration ?

Fyi: there is an active discussion about forking this (obviously unmaintained) project here: #628


Bug: Can't get lsp-status.nvim to work with lualine

Self Checks

[x] I'm using the latest lualine and neovim nightly.
[x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem
My config:
  use {
    -- "hoob3rt/lualine.nvim",

    -- Fork that allows reloading config. See: https://github.com/hoob3rt/lualine.nvim/pull/311
    --
    "shadmansaleh/lualine.nvim",

    requires = { "nvim-lua/lsp-status.nvim" },
    config = function()
      require("lsp-status").config {}

      _G.setup_lualine = function(options)
        options = options or {}

        default_options = {
          tabline = {
            lualine_a = { "filename" },
            lualine_b = { require"lsp-status".status }
          }
        }

        final_options = vim.tbl_deep_extend("force", default_options, options)

        print("Setting up lualine with options: " .. vim.inspect(final_options))

        require("lualine").setup(
          vim.tbl_extend("force", default_options, options)
        )
      end

      setup_lualine()
    end
  }

(I need the global setup function to be able to switch color scheme later - it's currently not possible to change scheme without setting up lualine from scratch)
When I run nvim I get the message:
Setting up lualine with options: {
  tabline = {
    lualine_a = { "filename" },
    lualine_b = { <function 1> },
    <metatable> = {
      __tostring = <function 2>
    }
  }
}

So it's being set up with the correct options.
Actual behaviour
I only see the filename in the tabline, I don't see any output from "lsp-status.nvim":

But if I run the status function directly and print the output:

It's producing text, so why isn't it being displayed in the tabline? :confused:
Expected behaviour
I would expect the lsp-status text to be displayed in the tabline.
Aditional information
➜ nvim --version
NVIM v0.5.0
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim/src/neovim-0.5.0/build/config -I/build/neovim/src/neovim-0.5.0/src -I/usr/include -I/build/neovim/src/neovim-0.5.0/build/src/nvim/auto -I/build/neovim/src/neovim-0.5.0/build/include
Compiled by builduser

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Freshly updated packages using packer.nvim.
Minimal config to reproduce the issue
(See above)

wrap the lsp status function with a function to discard arguments provided by lualine

lualine_b = { function() return require"lsp-status".status() end }

The function signature for function components is
function(self, is_active)

while function signature for lsp_status is
function(bufnr)

So it doesn't work if you just give the function is lsp-status case.
Also tabline is updated really rarely by default in (neo)vim . To force an update at anytime you can run :redrawtabline if you're displaying anything that requires quick refresh I'd suggest setup a timer that calls the command periodically.

I need the global setup function to be able to switch color scheme later - it's currently not possible to change scheme

It is on myfork you can set the theme to auto and lualine will change it's theme as you change colorscheme with :colorscheme  command.
You can just change the theme too .
like
:lua require'lualine'.setup{options = {theme = 'gruvbox'}}

running that command will just change the theme to gruvbox.
Also there's easier way to setup from previous config.
require'lualine'.get_config()

will return currently active config . All these are in my fork though not here.

@shadmansaleh Oh damn, that's all insanely helpful information! I was pretty sure my usage was correct since I copied it directly from the lualine README :smile:

I will try the method you suggested to change colorschemes, thanks!


updated some stats

Updated coding job statistics

[x] I have read freeCodeCamp's contribution guidelines.
[*] My pull request has a descriptive title (not a vague title like Update index.md)
[*] My pull request targets the master branch of freeCodeCamp.
[*] None of my changes are plagiarized from another source without proper attribution.
[*] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Didn't check my boxes

Hi,
Thanks for this pull request (PR).
Unfortunately, we are closing this PR, because even though you added some interesting facts, you should support those facts to the source they came from.  Feel free to submit a new PR with such sourcing for the statistics you have provided.  For now, we are going to close this PR.
Thank you


[GHSA-jwpw-q68h-r678] Improper Neutralization of CRLF Sequences in dio

Updates

References
Source code location

Comments
This is actually a duplicate of GHSA-9324-jv53-9cc8, can we merge these as the same one? Also can we link this to the repo if they are not available for merge?

Hey @AlexV525, thanks for the contribution. We have a bit of tech debt preventing us from merging these two at the moment, but I'll go ahead and update this advisory and get them both added to a tracking issue for an eventual dedupe.


Proposal for solving "crossing date line geometries" problem

Warning: This is full R&D, POC, not mergeable at all in this state!
This follows the discussion we had about longitude wrapping and geometries crossing date line. With the 0.5 release (\o/) I've started thinking about this again.
As you already know, _my_ opinion is that removing wrapping from L.LatLng was a good move, but removing it from default Leaflet behaviour was not such a good one.
My main points are:

this breaks consistency with other GIS, like PostGIS (which doesn't accept longitudes over 180 when in  geography mode)
this doesn't totally solve the "cross date line" problem

I mean, for example, just trying to display a polygon around New Zealand will not give expected results. Say:
        L.polygon([
            [-40, 176],
            [-45, 178],
            [-46, -178],
            [-40, -175],
        ]).addTo(map);

This will result in a huge polygon crossing the whole world, instead of a small one crossing the date line.
So thinking about this, I went to this point:

Leaflet must use acute coordinates internally, and must be able to expose them to third party GIS
Leaflet should try to display things as close as possible as how humans expect them

In others words: data is for machines, displaying is for humans.
So I thought about some heuristical algorithm to determine where some ambiguous point has to be displayed.
This algorithm is very simple, but in the same time quite intrusive, and actually I don't fully like my current implementation, but here is what it looks like:

when projecting a point, try to give a context to disambiguate
this context is by default the map center
and when displaying a path, use previous point of the path to contextualize the next one

And than you can successfully display the above Polygon. :)
As previously said, the actual implementation lacks of some refactoring, it's just a proof-of-concept. The aim is to continue the discussion, and not just complaining, also making some proposals ;)
So, when you have some time, I'd like your opinion on this proposal. Hence, if you think some point merit to dig in and not just everything has to be trashed, I can work on it to reach a satisfactory state.

@mikeatlas Looking at the above dateline example you provided from Oct 24th 2014, it seems that the polyline for the top two points on the map should actually go over the top of the map when crossing the dateline, and not straight across which is a geographically longer route.
I think the solution to this needs to include both the max 180degree rule, but ideally it should also have a check when drawing lines on whether it is shorter to cross over a pole.  Whenever I fly between the US and China I have gone over the north pole because that is the shortest route between NYC and Beijing. Using your solution if i plotted both points on the map and drew a line, then the route would appear to go horizontally across the map instead of up and over.

@MuellerMatthew I'm certainly no expert, my solution is a "visual" workable hack, never claimed it was truly correct or would work for non web-mercator projections. I imagine in the future with the arctic circle melting, plus the rising stakes/claims between russia and canada over "northern routes" - it wont just be airplane flights that need better north-pole projection handling- imagine -180 to 180 at 85lat? non web mercator -a circle, of course!
D3.js has some great support for non-web-mercator projections, but I think leaflet's biggest strengths are
-free
-easy to use for JS beginners
-easy to make 1-off relatively static maps with low #s of objects
Even Leaftlet 1.0 doesn't seem to have any IDL dateline solution integrated, nor have I ever seen it used for anything other than WGS84 (I don't have a GIS background either) projection.
Perhaps we'll see something change in Leaflet 2.0 in a few years, I expect WebGL to be far more prevalent by then, and possibly many libraries like Leaflet may chose to re-implement or take a new approach to rendering web maps with widespread WebGL available. I've already seen a few non-free WebGL-only javascript attempts at Google-Earth like platforms (alpha status).

Also @mourner and @yohanboniface if you're considering re-approaching this (mourner added the needs-discussion label on May 8) and (yohanboniface referenced this pull request in umap-project/umap on Aug 2 POIs should be displayed outside the center of the world map #33)
I'd like to add that non-web-mercator projection may take on increasingly important roles in web-based mapping (along with the availability and support of WebGL) specifically for reasons mentioned above (the north passage becoming a reality; cross-polar flights already happen daily...)

Is there any hope that this will be fixed some day? I have been hoping to use Leaflet for a tsunami warning information app for the Pacific and National Tsunami Warning Centers to distribute warning information to emergency management personnel, but, given that tsunamis are largely a Pacific across-the-dateline phenomenon, this is a show-stopper for me.  I use datasources that are not under my control, and I cannot possibly hack all the longitude values.

Also +1

Subscribed and went to write an ugly hack

Has this issue been fixed so far ?

Aside from the four thousand commits between this branch and master, is performance still the blocker here? @lemon-tree 's suggestion to make this an option seems like a good compromise.

Has any progress been made on this at all recently?
From what I can gather, the performance concerns have stalled this feature, but could it not be implemented as a option flag that is off by default?


collection.ensureIndex deprecated in MongoDB 3.0.0

See this mongoose issue and this reference. The method ensureIndex becomes alias with createIndex starting Mongo 3.0.0. Thus, I propose, createIndex should be added to Monk API.

yeah, happy to accept a PR in this direction

I think ensureIndex sounds fine, moreover mongodb driver uses ensureIndex http://mongodb.github.io/node-mongodb-native/2.0/api/Collection.html#ensureIndex

Is there any chance to have a merge of #169 to master please?


connectToApSpinnerDialog Dismisses Too Early

DiscoverDeviceActivity.java: onPostExecute(SetupStepException error)
hideProgressDiaglog() may dismiss and return back to DiscoverDeviceActivity. Users may re-tap a Particle device on the WiFi fragment list which is undesirable in the setup process. It would be preferable if the progress dialog always dismisses when DiscoverDeviceActivity is destroyed.

@alvinsee I've tested this and yes, this is a real issue. It is sort of a lag during that process and most users will be impatient (with reason) and try to click the button again.. causing errors. I believe @idokleinman is and already has been looking into this issue. What specific version of android are you using?

@chobberoni I've tested and replicated the issue on both Android Lollipop and Marshmallow Preview 3.

I'm able to reproduce this -- I'll add this to the bug queue for an upcoming release.

@jensck much appreciated!

Just FYI- still exists on 0.3.0- I'm going to dig into the code tomorrow to see if there I can find a fix in the meantime, I'll report back if I find one.

@jensck any update on this? we have a client who is going into production run of their platform and need this bug fixed

@chobberoni I looked at it last night and I believe I found the cause; I'm going to implement and test the fix tonight.

thanks @jensck !!! :+1: :smile:

woo! Thanks, all!


Repitive content in footer fixed

Description: I have fixed the issue of repetitive text in footer fixes #191

Motivation and Context
It is just a repetition so must be removed

How Has This Been Tested?
deployment on local and vercel

Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@sau-mili you have deleted  a lot of dependencies


Canvas

DOM can be very slow and not appropriate for more graphically intensive games, Canvas would be a better to work with.

I second this. DOM is a recipe for disaster when it comes to a ton of moving objects on the screen.

Definitely on our list!

And concretely, what are we talking about?
Converting all of Canvas API as close as possible in Eve? Or just using Canvas, but a different API?
For example, what would something like a circle drawing in a canvas look like as Eve syntax ?
(something like this, for example : http://www.html5canvastutorials.com/tutorials/html5-canvas-circles/ )
Are we looking to do something like this :
bind @browser
   [#canvas width: 578 height: 200 children :
     [#arc centerX: 100 centerY: 100 ...]

etc...

Or something totally different?

This will definitely need a lot of consideration. I'd be tempted to say a separate API would be better. Something well suited to the domain language. But probably needs to be broad and general, then libraries can be made for more specific circumstances, e.g. games, graph creation, etc.

I second a separate API. While the DOM is slow it has baseline accessibility already built in. Screenreader support and other accessibility features to me are a must for any of the software I develop. (Yes Canvas has accessibility API's but they are off by default and very hard to work with and you usually just end up mostly mimicking the closet DOM elements you feel like your canvas element is like accessibility wise.)

This is partially implemented with a low level api in Eve v0.3.
See https://github.com/witheve/eve-starter/blob/master/programs/canvas-demo.ts for a demonstration.

If anyone is interested in exploring higher level APIs the canvas watcher should be flexible enough to build on top of. Let me know what you come up with!


Adopt Snippets in Swift Markdown

Add snippets with updated syntax to the project.
I verified that these all build/run as expected, and show up in the rendered documentation.
rdar://103054461

@swift-ci Please test

@swift-ci Please test


Login incompatible with POL

How us the fix going?

Haven't had a chance to work on it yet :/

I do not know how to help you :(

No worries. I'll get this done once my schedule clears up IRL. :)

When do you thi i you will be able to progress to at least the same level as uojs?

I'm not really sure yet. Several months I'm guessing. I'm currently studying three.js just to get more information on the basics. I've also been really busy lately with work and traveling.

Fixed?

It's not currently. :/


Bug: Cloud functions are not deploying

Our cloud functions are deployed automatically as part of our github actions workflows.
Github reports that the action for deploying is successful. However we can see that individual functions are failing to deploy.
See the following screen grab showing the github action has passed (green tick on left of screen) however individual functions have failed ("Quota exceeded" messages).

The way forward involves completing at least one of the following tasks, ideally both:

[ ] Update our functions to be 2nd generation functions
[ ] Combine many of our callable functions into a single API. e.g. we could have a single function which provides an API for generating reports, say. Or we could have a single function which provides an API for all callable functions! (to be agreed and decided)

@nickaddy assigned to you for review


Docker directory issue

Hi,
I tried the standalone pull just now, which terminated with an error. Any ideas ?
 I deleted the folders, and created the two files with touch.
This error disappeared, yet I seem to have problems accessing the server. Will troubleshoot here with our admin.

It seems to be that the server has not started (timeouts via webbrowser, no activity on docker container)
I copied the config.template to the directory /var/www/ibrowser/data/ and renamed as config.py.
I then tried to run ibrowser manually with this command:
IMPORTING BEHAVIOUR
IMPORTING FUNCTIONS
importing flask
importing jinja2
importing user database
importing sha3
importing vcf_walk
importing vcf_walk sql
importing image
importing sqlalchemy
SECRET KEY   '\xbbd}9\x7f\x0b\xa7\xd6@hF_Be\xe8\xa3\x9f\xe3\xe2\xf5\x18\xab\xc3$'
loading config /var/www/ibrowser/data/config.py
updating key DEBUG from True to False
updating key LIBRE_PATHS from ['/api', '/favicon.ico'] to ['/api', '/favicon.ico']
updating key SERVER_PORT from 10000 to 10000
updating key HAS_LOGIN from False to False
inited
No error messages, but no sign the browser is working.
root@f83a19cf91aa:/var/www/ibrowser# ps
PID TTY          TIME CMD
1 ?        00:00:00 bash
38 ?        00:00:00 ps
root@f83a19cf91aa:/var/www/ibrowser# ps -aux | grep py
root@f83a19cf91aa:/var/www/ibrowser# ps -aux | grep ibrowser
root        42  0.0  0.0   6572   660 ?        S+   07:27   0:00 grep --color=auto ibrowser
root@f83a19cf91aa:/var/www/ibrowser# ps -aux | grep rowse
root@f83a19cf91aa:/var/www/ibrowser#
Thanks for your help.


How can we close the image-picker/camera/image-library programatically?

I need to close the dialog from the code in some cases.
How can I do it?

+1 , I also want to know it


Add a a prarie vole atlas?

https://elifesciences.org/articles/87029
From a glance it looks v high quality.

Should post here to inform a potential user.

Closed by #336


In-progress skills support DO_NOT_MERGE

Description
This adds support for consuming skills on the JS side of things. Still needs auth support and unit tests so not ready to be merged.
Specific Changes

Testing

Plese re-open this as a DRAFT PR.


Proposal Feedback:

Proposal 4/4
Context and solutions look good.  Make sure you have some resources / an approach to solving the 2D / 3D component.

note: 3D was a typo, but it'd be interesting to tackle that problem in the future. It would not be too difficult to make this or even higher dimension models, linking north/south/east/west/upward/downward/forward/backward for 4th dimension, and so forth. Each vertex would ultimately just need more neighbors.
At any rate, primary features were to include:

maze generation
maze solver
maze graphic creator (creating a traditional look took longer to create, and is actually using an interesting graph structure in of itself.)
maze scrambler (deletes n branches to destroy tree-like structures)


Vuforia Camera taking time to start!!

Hi,
I have integrate vuforia with unity and using this package i am running unity from RN,
Now the problem is that, when i navigate to screen, Unity logo show up and vuforia camera take 10 to 12 second to start up, whereas if i directly run the build and run app from unity, then vuforia camera show up in only 3 seconds approx.
Can you tell me how can i reduce the time in React native

Hi @jawwad22  can you kindly share the steps which you have followed after exporting project for build and installation?


Blank page

After launching the container through "docker-compose up" and opening the port in the 8080 browser, the server receives a blank (white) page, the source code of which:

  | <!DOCTYPE html>
-- | --
  |
  |
  |
  |
  | <meta http-equiv="X-UA-Compatible" content="IE=edge">
  | <title>
  | Password cockpit
  | </title>
  | <meta name="description" content="">
  | <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no">
  |
  | <meta name="passwordcockpit_frontend/config/environment" content="%7B%22tinyMCE%22%3A%7B%22load%22%3Afalse%7D%2C%22modulePrefix%22%3A%22passwordcockpit_frontend%22%2C%22environment%22%3A%22production%22%2C%22rootURL%22%3A%22%2F%22%2C%22locationType%22%3A%22history%22%2C%22EmberENV%22%3A%7B%22FEATURES%22%3A%7B%7D%2C%22EXTEND_PROTOTYPES%22%3A%7B%22Date%22%3Afalse%7D%2C%22_APPLICATION_TEMPLATE_WRAPPER%22%3Afalse%2C%22_DEFAULT_ASYNC_OBSERVERS%22%3Atrue%2C%22_JQUERY_INTEGRATION%22%3Afalse%2C%22_TEMPLATE_ONLY_GLIMMER_COMPONENTS%22%3Atrue%7D%2C%22APP%22%3A%7B%22host%22%3A%22http://uib-t-logproxy:8080%22%2C%22namespace%22%3A%22api%2Fv1%22%2C%22languages%22%3A%5B%22en%22%2C%22it%22%2C%22de%22%2C%22fr%22%5D%2C%22userLanguages%22%3A%5B%7B%22value%22%3A%22%22%2C%22text%22%3A%22-%22%7D%2C%7B%22value%22%3A%22en%22%2C%22text%22%3A%22English%22%7D%2C%7B%22value%22%3A%22it%22%2C%22text%22%3A%22Italiano%22%7D%2C%7B%22value%22%3A%22de%22%2C%22text%22%3A%22Deutsch%22%7D%2C%7B%22value%22%3A%22fr%22%2C%22text%22%3A%22Fran%C3%A7ais%22%7D%5D%2C%22name%22%3A%22passwordcockpit_frontend%22%2C%22version%22%3A%221.3.0%2B5e286e3d%22%7D%2C%22passwordFormConfig%22%3A%7B%22icons%22%3A%5B%22key%22%2C%22user%22%2C%22user-secret%22%2C%22user-graduate%22%2C%22users%22%2C%22music%22%2C%22search%22%2C%22envelope%22%2C%22heart%22%2C%22star%22%2C%22film%22%2C%22th-large%22%2C%22th%22%2C%22th-list%22%2C%22check%22%2C%22times%22%2C%22power-off%22%2C%22signal%22%2C%22cog%22%2C%22home%22%2C%22file%22%2C%22clock%22%2C%22cloud%22%2C%22road%22%2C%22arrow-circle-down%22%2C%22arrow-circle-up%22%2C%22inbox%22%2C%22play-circle%22%2C%22list-alt%22%2C%22lock%22%2C%22flag%22%2C%22headphones%22%2C%22volume-up%22%2C%22qrcode%22%2C%22barcode%22%2C%22tag%22%2C%22book%22%2C%22bookmark%22%2C%22print%22%2C%22camera%22%2C%22wifi%22%2C%22address-book%22%2C%22anchor%22%2C%22asterisk%22%2C%22ban%22%2C%22bed%22%2C%22bell%22%2C%22bolt%22%2C%22bomb%22%2C%22bone%22%2C%22bong%22%2C%22briefcase-medical%22%2C%22briefcase%22%2C%22bug%22%2C%22building%22%2C%22bus%22%2C%22calculator%22%2C%22calendar%22%2C%22campground%22%2C%22candy-cane%22%2C%22capsules%22%2C%22car%22%2C%22certificate%22%2C%22coins%22%2C%22credit-card%22%2C%22desktop%22%2C%22download%22%2C%22exclamation%22%2C%22fingerprint%22%2C%22fish%22%2C%22flask%22%2C%22gamepad%22%2C%22gift%22%2C%22hammer%22%2C%22hdd%22%2C%22image%22%2C%22laptop%22%2C%22map-marker%22%2C%22money-bill%22%2C%22mobile-alt%22%2C%22paperclip%22%2C%22pastafarianism%22%2C%22poo%22%2C%22radiation%22%2C%22restroom%22%2C%22rss%22%2C%22satellite%22%2C%22save%22%2C%22sd-card%22%2C%22server%22%2C%22share-alt%22%2C%22shopping-cart%22%2C%22sim-card%22%2C%22smile%22%2C%22space-shuttle%22%2C%22thumbs-up%22%2C%22thumbs-down%22%2C%22toilet-paper%22%2C%22tools%22%2C%22tree%22%2C%22tshirt%22%5D%2C%22options%22%3A%7B%22content_css%22%3A%22%2Ftinymce.css%22%2C%22menubar%22%3Afalse%2C%22plugins%22%3A%22lists%22%2C%22toolbar1%22%3A%22bold%20italic%20underline%20%7C%20bullist%20numlist%22%2C%22formats%22%3A%7B%22underline%22%3A%7B%22inline%22%3A%22u%22%7D%7D%2C%22branding%22%3Afalse%2C%22base_url%22%3A%22%2Fassets%2Ftinymce%22%7D%7D%2C%22passwordEncryptionConfig%22%3A%7B%22failureLimit%22%3A10%2C%22encryptParameters%22%3A%7B%22mode%22%3A%22gcm%22%7D%7D%2C%22ember-simple-auth%22%3A%7B%22store%22%3A%22simple-auth-session-store%3Asession-storage%22%2C%22authorizer%22%3A%22authorizer%3Atoken%22%2C%22routeAfterAuthentication%22%3A%22folders%22%7D%2C%22ember-simple-auth-token%22%3A%7B%22tokenPropertyName%22%3A%22token%22%2C%22authorizationPrefix%22%3A%22Bearer%20%22%2C%22authorizationHeaderName%22%3A%22Authorization%22%2C%22tokenExpireName%22%3A%22exp%22%2C%22serverTokenEndpoint%22%3A%22http://uib-t-logproxy:8080%2Fapi%2Fauth%22%2C%22refreshAccessTokens%22%3Atrue%2C%22refreshTokenPropertyName%22%3A%22token%22%2C%22serverTokenRefreshEndpoint%22%3A%22http://uib-t-logproxy:8080%2Fapi%2Fv1%2Ftoken%2Fupdate%22%2C%22refreshLeeway%22%3A60%7D%7D" />
  |
  | <link integrity="" rel="stylesheet" href="/assets/vendor-d41d8cd98f00b204e9800998ecf8427e.css">
  | <link integrity="" rel="stylesheet" href="/assets/passwordcockpit_frontend-bd1f3da8557b6f49918c9d5a766605d8.css">
  |
  |
  |
  |
  |
  |
  |
  |
  |
  |
  |

  |

  |

  |

  |

  |
  |
  |

<!DOCTYPE html>

    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title>
        Password cockpit
    </title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no">

    <meta name="passwordcockpit_frontend/config/environment" content="%7B%22tinyMCE%22%3A%7B%22load%22%3Afalse%7D%2C%22modulePrefix%22%3A%22passwordcockpit_frontend%22%2C%22environment%22%3A%22production%22%2C%22rootURL%22%3A%22%2F%22%2C%22locationType%22%3A%22history%22%2C%22EmberENV%22%3A%7B%22FEATURES%22%3A%7B%7D%2C%22EXTEND_PROTOTYPES%22%3A%7B%22Date%22%3Afalse%7D%2C%22_APPLICATION_TEMPLATE_WRAPPER%22%3Afalse%2C%22_DEFAULT_ASYNC_OBSERVERS%22%3Atrue%2C%22_JQUERY_INTEGRATION%22%3Afalse%2C%22_TEMPLATE_ONLY_GLIMMER_COMPONENTS%22%3Atrue%7D%2C%22APP%22%3A%7B%22host%22%3A%22http://uib-t-logproxy:8080%22%2C%22namespace%22%3A%22api%2Fv1%22%2C%22languages%22%3A%5B%22en%22%2C%22it%22%2C%22de%22%2C%22fr%22%5D%2C%22userLanguages%22%3A%5B%7B%22value%22%3A%22%22%2C%22text%22%3A%22-%22%7D%2C%7B%22value%22%3A%22en%22%2C%22text%22%3A%22English%22%7D%2C%7B%22value%22%3A%22it%22%2C%22text%22%3A%22Italiano%22%7D%2C%7B%22value%22%3A%22de%22%2C%22text%22%3A%22Deutsch%22%7D%2C%7B%22value%22%3A%22fr%22%2C%22text%22%3A%22Fran%C3%A7ais%22%7D%5D%2C%22name%22%3A%22passwordcockpit_frontend%22%2C%22version%22%3A%221.3.0%2B5e286e3d%22%7D%2C%22passwordFormConfig%22%3A%7B%22icons%22%3A%5B%22key%22%2C%22user%22%2C%22user-secret%22%2C%22user-graduate%22%2C%22users%22%2C%22music%22%2C%22search%22%2C%22envelope%22%2C%22heart%22%2C%22star%22%2C%22film%22%2C%22th-large%22%2C%22th%22%2C%22th-list%22%2C%22check%22%2C%22times%22%2C%22power-off%22%2C%22signal%22%2C%22cog%22%2C%22home%22%2C%22file%22%2C%22clock%22%2C%22cloud%22%2C%22road%22%2C%22arrow-circle-down%22%2C%22arrow-circle-up%22%2C%22inbox%22%2C%22play-circle%22%2C%22list-alt%22%2C%22lock%22%2C%22flag%22%2C%22headphones%22%2C%22volume-up%22%2C%22qrcode%22%2C%22barcode%22%2C%22tag%22%2C%22book%22%2C%22bookmark%22%2C%22print%22%2C%22camera%22%2C%22wifi%22%2C%22address-book%22%2C%22anchor%22%2C%22asterisk%22%2C%22ban%22%2C%22bed%22%2C%22bell%22%2C%22bolt%22%2C%22bomb%22%2C%22bone%22%2C%22bong%22%2C%22briefcase-medical%22%2C%22briefcase%22%2C%22bug%22%2C%22building%22%2C%22bus%22%2C%22calculator%22%2C%22calendar%22%2C%22campground%22%2C%22candy-cane%22%2C%22capsules%22%2C%22car%22%2C%22certificate%22%2C%22coins%22%2C%22credit-card%22%2C%22desktop%22%2C%22download%22%2C%22exclamation%22%2C%22fingerprint%22%2C%22fish%22%2C%22flask%22%2C%22gamepad%22%2C%22gift%22%2C%22hammer%22%2C%22hdd%22%2C%22image%22%2C%22laptop%22%2C%22map-marker%22%2C%22money-bill%22%2C%22mobile-alt%22%2C%22paperclip%22%2C%22pastafarianism%22%2C%22poo%22%2C%22radiation%22%2C%22restroom%22%2C%22rss%22%2C%22satellite%22%2C%22save%22%2C%22sd-card%22%2C%22server%22%2C%22share-alt%22%2C%22shopping-cart%22%2C%22sim-card%22%2C%22smile%22%2C%22space-shuttle%22%2C%22thumbs-up%22%2C%22thumbs-down%22%2C%22toilet-paper%22%2C%22tools%22%2C%22tree%22%2C%22tshirt%22%5D%2C%22options%22%3A%7B%22content_css%22%3A%22%2Ftinymce.css%22%2C%22menubar%22%3Afalse%2C%22plugins%22%3A%22lists%22%2C%22toolbar1%22%3A%22bold%20italic%20underline%20%7C%20bullist%20numlist%22%2C%22formats%22%3A%7B%22underline%22%3A%7B%22inline%22%3A%22u%22%7D%7D%2C%22branding%22%3Afalse%2C%22base_url%22%3A%22%2Fassets%2Ftinymce%22%7D%7D%2C%22passwordEncryptionConfig%22%3A%7B%22failureLimit%22%3A10%2C%22encryptParameters%22%3A%7B%22mode%22%3A%22gcm%22%7D%7D%2C%22ember-simple-auth%22%3A%7B%22store%22%3A%22simple-auth-session-store%3Asession-storage%22%2C%22authorizer%22%3A%22authorizer%3Atoken%22%2C%22routeAfterAuthentication%22%3A%22folders%22%7D%2C%22ember-simple-auth-token%22%3A%7B%22tokenPropertyName%22%3A%22token%22%2C%22authorizationPrefix%22%3A%22Bearer%20%22%2C%22authorizationHeaderName%22%3A%22Authorization%22%2C%22tokenExpireName%22%3A%22exp%22%2C%22serverTokenEndpoint%22%3A%22http://uib-t-logproxy:8080%2Fapi%2Fauth%22%2C%22refreshAccessTokens%22%3Atrue%2C%22refreshTokenPropertyName%22%3A%22token%22%2C%22serverTokenRefreshEndpoint%22%3A%22http://uib-t-logproxy:8080%2Fapi%2Fv1%2Ftoken%2Fupdate%22%2C%22refreshLeeway%22%3A60%7D%7D" />

    <link integrity="" rel="stylesheet" href="[/assets/vendor-d41d8cd98f00b204e9800998ecf8427e.css](http://uib-t-logproxy:8080/assets/vendor-d41d8cd98f00b204e9800998ecf8427e.css)">
    <link integrity="" rel="stylesheet" href="[/assets/passwordcockpit_frontend-bd1f3da8557b6f49918c9d5a766605d8.css](http://uib-t-logproxy:8080/assets/passwordcockpit_frontend-bd1f3da8557b6f49918c9d5a766605d8.css)">

Docker webserver log:
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "GET / HTTP/1.1" 200 2565 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xd7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xd7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xd7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x07\x17\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xf7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xb7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x07\x17\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x07\x17\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xf7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x07\x17\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xd7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x07\x17\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xb7\x01" 400 392 "-" "-"
passwordcockpit  | <IP_ADDRESS> - - [29/Jul/2024:06:28:46 +0000] "\x16\x03\x01\x06\xb7\x01" 400 392 "-" "-"

How to fix it?

Please post your docker-compose.yml


Prevent collision with UITableView

Limit the width for the PanGestureRecognizer to prevent collision with
UITableView (swipe to delete)

[Current coverage][cc-pull] is 59.45%

Merging [#17][cc-pull] into [develop][cc-base-branch] will decrease coverage by 2.24%

@@            develop        #17   diff @@
==========================================
  Files             2          2
  Lines           141        148     +7
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             87         88     +1
- Misses           54         60     +6
  Partials          0          0

Powered by Codecov. Last updated by [27c794e...e30a06a][cc-compare]
[cc-base-branch]: https://codecov.io/gh/alexkrzyzanowski/SidebarOverlay/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/alexkrzyzanowski/SidebarOverlay/compare/27c794ed2bf8bc2bf55678c96c589f2419904afa...e30a06a19f2c96bd31315693efec1fff4ead5fee?src=pr
[cc-pull]: https://codecov.io/gh/alexkrzyzanowski/SidebarOverlay/pull/17?src=pr

Thank you for pull request @PeterGumball . I'll check it a bit later and try to cover code with automated tests.

Hey @alexkrzyzanowski.
Sorry for this commit. Small bug fixing. ;)

Actually, it's still a bit incorrect, because height goes out of the screen and the next line should be improved in a manner like:
let panView = UIView(frame: CGRectMake(0, CGFloat(heightOffsetForPanGestureRecognizer), CGFloat(widthForPanGestureRecognizer), self.view.frame.size.height - heightOffsetForPanGestureRecognizer))

Anyway I'll merge it because it is a solution. But not the best one. Today evening I'll try to recognize right-to-left swipe gesture to pass it to UITableView. I don't know if it is possible or not, but at least I can try.

Oh yes, i forgot.
I now it's not the best solution. ;)

I've already merged the PR :). I'll try to implement the best solution in a feature branch. If you want to be notified about progress on this issue, you can subscribe to issue https://github.com/alexkrzyzanowski/SidebarOverlay/issues/19.

Ok, thanks for the info.


bug: Search abruptly ends and Neovim returns to normal mode

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.9.4
Operating system/version
Docker
Describe the bug
Search abruptly ends and the cursor jumps to a "random" location returning to normal mode. Sequences that trigger the issue seem to depend on the file contents?
Steps To Reproduce

Start a default LazyVim Neovim instance e.g.

docker run -w /root -it --rm alpine:edge sh -uelic '
  apk add git lazygit neovim ripgrep alpine-sdk --update
  git clone https://github.com/LazyVim/starter ~/.config/nvim
  cd ~/.config/nvim
  nvim
'

Create a new file and type content asdasdasd
Return to normal mode
Type /asdd (No enter)
Observe cursor jumps to the nearest letter a and Neovim returns to normal mode.

For the file asdasdasd, for example /asf also triggers the issue but /asr does not.
Expected Behavior
Similar to any other search that is not found in the file, the search remains active.
Repro
Default starter config

The issue does not reproduce in a config without LazyVim e.g.
docker run -w /root -it --rm alpine:edge sh -uelic '
  apk add git lazygit neovim ripgrep alpine-sdk --update
  nvim
'

It's probably flash.nvim. Pls see #1410 for how to fix it. Also since this seems to be a user configuration issue, I believe it's more appropriate for the Discussions section.

Thank you, that seems to be the plugin causing the unexpected behavior.


Add option to update one dependency

When I work on a project which consists of both a library and a program in separate git repos, a common workflow is to:

add a feature to the library, commit and push it
run elm-install in the program dir, to update the dependency
use the new feature

However, step 2 takes a long time, because elm-install checks all the dependencies for updates. I specifically know that my own library has updated, and I am really only interested in updating that.
Would it be possible to add an option to check for updates for a specific dependency?
In the meantime, is there a quick way I can emulate this (eg. doing a 'git fetch' in ~/.elm-install/..., then a git checkout in elm-stuff/packages)?

This a complex issue which I don't really know how to resolve.
Basically there is a cache of git repositories in ~/.elm-install/, we can use that cache to install the dependencies. The question is when to invalidate the cache, but there are several ways that the repository can be used:

by version
by referencing a tag / branch or specific commit (refs)

We could just compare the versions of the remote with our local ones using git ls-remote which is somewhat faster (not much) than git fetch (which happens now), this would work for the versions but not for refs. That's why every repository is updated every time.
So the ideal solution to speed it up would be a quick (even dirty) was of checking if a local repository is different from the remote, but I'm not aware of any that would do it.

The other way to go is to have some option / action:

--skip-updates - this would just use the cache or clone if not found
update-package user/package - this would fetch the given package directly
--update-only user/package - this would only update the given package

I'm in favor of 1. and 2. so it would go something like this:
elm-install update-package user/package && em-install --skip-updates

For your use case you could to use the directory option so you can use both locally when developing and only push versions when necessary.

Also this issue might affect your install time: https://github.com/gdotdesign/elm-github-install/issues/42

I've implemented 1. and 3. form above, so now you can use: elm-install --only-update elm-lang/core

Awesome, thanks!


Parameter spacing has changed

Current docs (left) vs local build (right).
This could be a quirk in my local environment, so I'm opening this issue to keep track of it.

This happens in the online docs too now. It's not the end of the world -- maybe something got tweaked in the theme.


@Filter enabled on all Entity types instead of only on instances of TenantEntity

Hello again
Here is the scenario

I have entity A and B with their respective repository interfaces. A extends TenantEntity, B doesn't.
I have AController that is implemented the same as in your example code.
I have BController that is a public endpoint(non Authenticated). BController has a function to return some general information from the Database when you run a GET against it.

Unfortunately this setup fails because apparently the TenantServiceAspect enables the @Filter automatically on all Data repositories regardless of if the Repository Entity is an instance of TenantEntity.
In my case it crashes even before, when you run TenantAssistance.resolveCurrentTenantIdentifier() because there is no token in the request to BController:
  @Around("execution(public * *(..)) && enableMultiTenancy()")
  public Object aroundExecution(final ProceedingJoinPoint pjp) throws Throwable {
    final Filter filter =
        this.entityManager
            .unwrap(Session.class) // requires transaction
            .enableFilter(TENANT_FILTER_NAME)
            .setParameter(
                TENANT_FILTER_ARGUMENT_NAME, TenantAssistance.resolveCurrentTenantIdentifier());
    filter.validate();
    return pjp.proceed();

but regardless, I think that in general usage the above method should not enable the filter if the Entity of the Repository is not an instance of TenantEntity. Otherwise it is not correct.
I've been trying to add this condition in the above code for a certain number of hours (And maybe even submit a PR) but I cant manage to find a clear enough documentation on how to get the entity information in the above method using the Aspect programming.
Any ideas?
Thanks and have a good day

Bernard

Hi @bernardgut,
Your comment made me smile, thank you for that 😄
Last night have recreated your issue and already implemented some counter measurements locally (branch to be pushed later on)

A new annotation will be added to determine if a @Entity is not multi tenancy compliant
In the TenantInterceptor this annotation is checked to determine if a tenant_id value needs to be added or not. Default it will now throw a UnknownTenantException as it expects the non multi tenancy annotation or that the entity extends from TenantEntity. If you add both, it will also throw an exception.

This is added in case you forget to extend the entity with TenantEntity, it will throw an exception (to keep the default closed statement in mind). If you don't want Multi tenancy, the annotation can be added on top of your entity and this will by pass the TenantInterceptor addTenantIdIfObjectIsTenantEntity() method. And it should indeed also bypass the Hibernate filter.
Everything is done and tested so far except the Hibernate filter which is for now always auto applied.
I have been playing around with reflection and specific Spring JPA hooks to dynamically enable / disable the filter in case the annotation is present on a @Entity but for now, the solutions that i have done is always breaching one of my statements.
But i haven't been through all the roads yet, so i will continue to check on how this can be properly be implemented.
I will also publish the ways that i have already investigated in case you would like to work on it as well 👍
I will push the branch very soon and link it to this ticket.
Best regards,
Michael

With my limited understanding of this aspect thing I did this : in TenantServiceAspect I added :
  @Pointcut("execution(public * com.rogerhr.multitenancy.MultiTenant+.*(..))")
  void isMultitenantRepository(){
    /* aspect */
  }

  @Pointcut(value = "isMultitenantRepository()")
  void enableMultiTenancy2() {
    /* aspect */
  }

  @Pointcut("execution(public * org.springframework.data.repository.Repository+.*(..))")
  void isRepository() {
    /* aspect */
  }

  @Pointcut(value = "isRepository()")
  void enableMultiTenancy() {
    /* aspect */
  }

  @Around("execution(public * *(..)) && enableMultiTenancy() && enableMultiTenancy2()")
...

Then I added an empty MultiTenant interface :
public interface MultiTenant {
    /* Switch.
    To enable multi-tenancy on a repository, extends this from the repository interface
    */
}

that I use as a switch to enable multi-tenancy in selected repositories:
public interface UserRepository extends JpaRepository<User, Long>, MultiTenant {

	...
}

Simple enough and seems to work so far.
What do you think?

Hey @bernardgut, your solution works, but now you are explicitly enabling Multi tenancy on a repository. If you do not define you annotation, no multi tenancy is applied.
The framework is created so that developers could worry-free implement Multi tenancy.
Thanks to Spring AOP, the hibernate filter & interceptor this is currently being achieved.
I spent some few hours on a working draft solution which is pushed on branch: NoMultiTenancySupport.
Didn't really have much time last couple of days, so this is what i came up with.
Some key changes:

Multi tenancy is still enabled on all Repositories (all Highlights are still valid!)
Spring AOP is not modified!
Annotations are not inherited on class implementations (which makes sense), so using a third party Reflections library to perform a classpath scan on startup of the application which returns a list of Class<?> of which interfaces / classes.
The pointcut returns a ProceedingJoinPoint which contains the target class which when the take the interfaces from and compare it to the classpath scanned interfaces. When the annotation is present, disable the hibernate filter. If not, enable it and double check that it is enabled :)
(The double check verifies if the entity has a column named tenant_id. If this is not present, an exception is thrown)

Already added 2 tests that validate this, but still need to add a bunch of tests to make sure that this implementation is 100% water tight.
-- TODO: targetClass.getClass().getInterfaces() should also support targetClass.getClass() as the annotation should also support implementations.
But for now, this draft should resolve the issue that you have logged.
Best regards,
Michael

Still haven't found the necessary time to finish up the NoMultiTenancySupport branch, but the core design is already present.
Still some // TODO's that need to be resolved (like additional tests).
When this is completely tested and validated, this will also be added into the master branch


CI Configuration

This PR provides a CI setup for Unit Tests, and Deploying to crates.io when pushed to main.
This can be expanded out at a later time, but this is good enough for now.

Need to update artifact publishing of the header


Wrap countCursor.observeChanges added function with debounce

This helps avoid several method calls on initialization, which decreases the initial load time for very large datasets.

Solved this another way in https://github.com/aldeed/meteor-tabular/commit/aae69abe1d2cd39e32b6407572cf71fc14abcc5b


add mastodon icon

What is the purpose of this pull request?

[x] New Icon
[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other:

Description

This PR adds a new Mastodon icon to the project. The Mastodon icon is a widely recognized logo for the Mastodon social network and can be used in various applications to represent the brand.
Icon use case

Displaying a link to a user's Mastodon profile on a personal or company website.
Integrating Mastodon sharing functionality in a web or mobile application.

Alternative icon designs

No alternative designs provided.
Icon Design Checklist
Concept

[x] I have provided valid use cases for each icon.
[x] I have not added any a brand or logo icon.
[x] I have not used any hate symbols.
[x] I have not included any religious or political imagery.

Author, credits & license

[ ] The icons are solely my own creation.
[ ] The icons were originally created in # by @
[ ] I've based them on the following Lucide icons:
[x] I've based them on the following design:

Naming

[x] I've read and followed the naming conventions
[x] I've named icons by what they are rather than their use case.
[x] I've provided meta JSON files in icons/[iconName].json.

Design

[x] I've read and followed the icon design guidelines
[x] I've made sure that the icons look sharp on low DPI displays.
[x] I've made sure that the icons look consistent with the icon set in size, optical volume and density.
[x] I've made sure that the icons are visually centered.
[x] I've correctly optimized all icons to three points of precision.

Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

Brand icon


Agriculture - EarthStat

Use the EarthStat database to disentangle land by crop type:
http://www.earthstat.org/
Should be able to get fruit, wheat, etc.  Lots of nuance.
Overall cropland area should also be feasible.

categorical


fix timeformat bug

sometimes, the EOS API will return time string like "3/17/2019 5:50:57 PM"

Hm, I've briefly checked the EOS source code and it has to be the ISO format. Anyway, supplying a date in different formats would be weird. Could you please provide more information, i.e. the request you send, the field name with invalid date, the EOS node you use?


KERNEL: Allow using mfma for pure f16 matmul via upcasting

https://github.com/openxla/iree/pull/16527 addresses this.


Accessing history in REPL only partially working

In the REPL in Juno of Julia Pro, when I use the up key to get the last few expressions I typed, it doesn't work for more than the last command. The second up-key gives me an empty line and when I then use the down-key, very old commands are shown.
Here is a gif showing the behaviour. Pay attention to the keystrokes on the right

I had expected that this works like the history in a terminal. My system is XUbuntu 16.04 with JuliaPro <IP_ADDRESS>

What you could try short term is to rename ~/.julia_history and try again, but that might not even help. This bug should be fixed on the master branches of ink and/or julia-client, so with the next release you should be good to go.

I'll just close this for now, since it should be fixed on master.

@pfitzseb OK, thanks. Renaming .julia_history didn't help.


Cannot add code to PATH, permission denied

Issue Type: Bug
Opening the command palette and trying to add the code command to PATH results in the following error:
EACCES: permission denied, unlink '/usr/local/bin/code'

This is from a fresh install.
VS Code version: Code 1.58.2 (Universal) (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:09:06.581Z)
OS version: Darwin arm64 20.4.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
4, 4, 3

Memory (System)
16.00GB (0.41GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30321513
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
vsccppwt:30329788
pythonvssor306:30344512
bridge0708:30335490

Note that I got it into my PATH by following the workaround here.

I also just ran into this issue, fresh install m1 macbook air.

Same issue here as well. M1 MacBook Air

Same issue M1 Macbook Air, the above work around did not work. Fresh install, like 3 hours ago.

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

I ran into this as well but I managed to get code command to work yesterday but it wasn't working any more today. My problem was that the code was referring to an instance in a temporary folder. So I just removed /usr/local/bin/code and then added it again from VSCode (after making sure that I launched VSCode from the Applications).
So essentially this: https://apple.stackexchange.com/a/294178

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

this answer should be pinned to the top, thank you.

I am also facing the same issue with Mac M1. However, I was able to make it work as suggested by @Lazy-poet . Thank you for the help.

Apparently, M1 isn't short of issues. I haven't been able to get a docker project that uses elasticsearch set up on a new M1 machine. The above solution to fix code PATH worked for me and I just thought maybe I could ask about the docker issue here perhaps some might have faced and solved it.

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

This work for me too! Thank you!

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

This worked for me as well..Thank You..

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

This indeed was the fix for my MacBook-air-M1 running OS X 11.4.  Thank you @Lazy-poet

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

This worked for me as well..Thank You..

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

Lazy-poet your fix worked. Thank you

Glad to know the workaround works!

I ran into this as well but I managed to get code command to work yesterday but it wasn't working any more today. My problem was that the code was referring to an instance in a temporary folder. So I just removed /usr/local/bin/code and then added it again from VSCode (after making sure that I launched VSCode from the Applications).
So essentially this: https://apple.stackexchange.com/a/294178

thank you so much! from korea

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

Fixed it.. Ty!

Same issue M1 Macbook Air, the above work around did not work. Fresh install, like 3 hours ago.

Zac! I just ran into the same issue but doing the uninstall and reinstall did fix the problem. Good to cross paths again!

To solve this:
1- Open Terminal
2- run command sudo rm /usr/local/bin/code
3- open VSCode again and run CMD+SHIFT+p
It'll ask you for root password and install successfully.

@ajamous's solution doesn't resolve this for me. code is no longer found after I kill whenever the current terminal session. This also occurs for me on Macbook Air M1, arm build.

I found a fix. I simply uninstalled the code command from PATH in vscode and reinstalled. i.e open the command pallete, search "uninstall 'code'" and select the first option to uninstall. Do same for installing too. That should fix it

This works for me @ MacBook Air M1 macOS Monetary 12.0.1


Still need to implement Device Code flow for the Enrollment Application

As per the Title, i still need to implement the Device Code flow for the Enrollment Application.

Done with Azure Identity Library, going to commit soon.


Popular table query improvements

This PR updates the atlasclient version, which is a big change, along with the queries improvements for popular tables.
There used to be multiple calls in older version of atlasclient, which is fixed now. Also bumped the version of amundsen metadata.

@feng-tao @jinhyukchang ready for review

Sorry, I reverted the version back to 1.0.5 as there are some changes needed to be done on atlas_proxy based on new version of atlas. Will update the version after implementing those changes.
@feng-tao

Sounds good @verdan


Embedding model is reloaded cyclic when run on CPU

System Info / 系統信息
system: win10
python: 3.10
transformers: 4.46.2
Running Xinference with Docker? / 是否使用 Docker 运行 Xinfernece？

[ ] docker / docker
[X] pip install / 通过 pip install 安装
[ ] installation from source / 从源码安装

Version info / 版本信息
0.16.3 & 1.0.0
The command used to start Xinference / 用以启动 xinference 的命令
xinference-local.exe
Reproduction / 复现过程

start xinference-local.exe
launch bge-large-zh-v1.5 model on CPU in webui
do embedding request

The console logs model reload information repeated.
There is no problem if set device to GPU.
Expected behavior / 期待表现
serve embedding model normally on CPU device

Just report: the problem disappeared after upgrade to version 1.1.0


⚠ Bofrost.nl has degraded performance

In b2f3b4b, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1159 ms

Resolved: Bofrost.nl performance has improved in 96bd46a after 6 minutes.


Using FcmSharp with asp.net web api

hi
thank you for the great work you have done.
i used it in windows forms, xamarin forms and c# console app and everything works perfect.
but i want to use it in my web api and it just doesnt work and i dont know whats wrong.
I set the service account key build action to Embed Resource and Always copy ... is this right?
please guide.
thank you again.

Why not read it from a File, that you put somewhere in the File System?

I just tried it...
here is what i get:
Could not Read Credentials. (Reason = File Does Not Exist, FileName = '/serviceresx/servacc.json')
i think i just dont know how to address it properly or maybe it needs some permissions i dont know.

Thank you very muchhhh ,
lol I just used  HttpContext.Current.Server.MapPath to address the file and it worked great.
thank you again for the great job you have done.

@tickerman Great you figured it out. Good luck with your project!


BC: the 1.3.0 release is the same as 2.0.0 and break compatibility

You released 2.0.0 which introduce a BC but you also release the 1.3.0 with that same BC which is breaking our code. Could you remove the 1.3.0 release & tag from GitHub to BC?
https://github.com/javibravo/simpleue/compare/1.2.0...1.3.0 is the same as https://github.com/javibravo/simpleue/compare/1.2.0...2.0.0
Both release are on the same commit: 3e3508a
Thanks

Done.

Thanks!


ErrorResponseException on sending member to timeout

Question
Hey!
So I just started using JDA5 with my bot and rewrote a mute function of my bot to use the Member#timeoutFor function of JDA5. Everything worked fine, until the bot had to execute the "Send to timeout" command:
[ForkJoinPool.commonPool-worker-51] ERROR RestAction - RestAction queue returned failure: [ErrorResponseException] 50035: Invalid Form Body
communication_disabled_until
	- INVALID_COMMUNICATION_DISABLED_TIMESTAMP: Invalid communication disabled timestamp
net.dv8tion.jda.api.exceptions.ContextException
	at net.dv8tion.jda.api.exceptions.ContextException.here(ContextException.java:54)
	at net.dv8tion.jda.api.requests.Request.<init>(Request.java:71)
	at net.dv8tion.jda.internal.requests.RestActionImpl.queue(RestActionImpl.java:197)
	at net.dv8tion.jda.api.requests.RestAction.queue(RestAction.java:573)
	at net.dv8tion.jda.api.requests.RestAction.queue(RestAction.java:539)
	at components.moderation.ModEngine.run(ModEngine.java:39)
	at components.moderation.ModEngine.lambda$0(ModEngine.java:21)
	at java.base/java.lang.Thread.run(Thread.java:831)

I have no idea what this means, research didn't help either. And since the question seems to be difficult even for the discord server, I'm asking it here.
What is this? And: How can I fix this?
Example Code
guild.getMember(user).timeoutFor(28, TimeUnit.DAYS).queue();

Edit: Did all the troubleshooting btw :)

(and make sure you are using alpha9)

This is likely a race condition. You are timing the user out for exactly the maximum, which results in a date that is directly on the edge of being invalid. This date may be further ahead into the future due to clock drift on your specific machine. I would recommend lowering the timeout to 27 days to avoid this problem.


How to build the project on windows by visual studio?

Currently, XeTLA project only support Ubuntu OS + PVC platform.


Do you plan on releasing a production ready git-lfs server?

See https://about.gitlab.com/2015/08/13/towards-a-production-quality-open-source-git-lfs-server/#comment-2191074763 for the request to open an issue here.
Some questions we have, feel free to answer selectively:

Do you plan on releasing a production ready git-lfs server?
Is this repository based on code you run in production?
What would need to be added to this codebase to make it ready for production?
Are you accepting pull requests that make this codebase more ready for production?
Are you accepting pull requests that optionally bypass the user management that is currently in here or would you rather see us maintaining a fork?

Question 5 as prased by https://twitter.com/ethomson/status/631864576422772736 Are you open to adding a pluggable auth model?

No plans at this time.
Nope, not even close. It's just a test server with as few dependencies as possible.

We have no intentions of working on the lfs test server, beyond making it protocol compatible with the client. I'd much rather see you start over, or fork it.
I think an oss, production-ready lfs server with a pluggable auth model would be rad though :metal:

@technoweenie Thanks for the answers. We'll proceed with a fork that we'll try to wip into production shape over time.

Cool, thanks for reaching out!

https://github.com/blog/2069-git-large-file-storage-v1-0


Roll Flutter Engine from 0a5c6cdd5d02 to ed34ad0ff9b8 (7 revisions)

https://github.com/flutter/engine/compare/0a5c6cdd5d02...ed34ad0ff9b8
2023-07-25<EMAIL_ADDRESS>Roll ANGLE from 7ae6458b664f to 2d5fb09d7f0a (2 revisions) (flutter/engine#44002)
2023-07-25<EMAIL_ADDRESS>Roll Skia from 04ab62b4f8c9 to eb5b5bc4fb86 (2 revisions) (flutter/engine#44001)
2023-07-25<EMAIL_ADDRESS>Roll ANGLE from e8c8c5651223 to 7ae6458b664f (1 revision) (flutter/engine#43999)
2023-07-25<EMAIL_ADDRESS>[Impeller] Use basis of effect transform in MatrixFilter. (flutter/engine#43990)
2023-07-25<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from DO73K2Twew-a51xHm... to 0StTjIqUxGkc3nOWT... (flutter/engine#43996)
2023-07-25<EMAIL_ADDRESS>Roll ANGLE from 1b17c91e4231 to e8c8c5651223 (2 revisions) (flutter/engine#43997)
2023-07-25<EMAIL_ADDRESS>Roll Skia from 81ea617ee386 to 04ab62b4f8c9 (1 revision) (flutter/engine#43994)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from DO73K2Twew-a to 0StTjIqUxGkc
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jonahwilliams@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Updated version of #2125

This PR takes @mdkent and @inno's work from #2125 and updates the specs to be compatible with the currently used version of RSpec so they should now pass. It also adds an extra unit test to hopefully handle @tyler-ball's comment in #2125 about calling .to_s on nil
This PR adds functionality the yum_package provider to support both specifying the version requirement in the package name, which is what was broken and reported in CHEF-2911, and also to support specifying a version attribute in the yum_package resource in one of the following two formats:

Specific version, eg 3.0.1.el5
Version requirement, eg = 2.0.1.el5

@chef/client-core if you'd like to cast your gaze over this revised version, I'll tackle any spec fails travis surfaces...they pass locally, but then that doesn't really mean anything :p
Documentation updates etc will be completed once this PR assumes its final form.
Eventually, it'd probably also be a good idea to deprecate supporting version requirements in the resource name and just use the version attribute - depending what people think, that could be incorporated in this PR.

@btm I've refactored the new tests inside a context, haven't touched any of the existing ones for now although there's still quite a lot of duplication lying around.

:+1:
I've got a personal thing against the old cargo culted test pattern of it "should do this..." instead of it "does this" because the tests are an assertion, which I just mention to further my cause. :)

:+1:

I think @jaymzh  has the write lock on the yum provider in #2692 -- we need to get that merged and should really rebase this on top of that.

@lamont-granquist I'm fine to wait for that if it's quick-ish, but this is fixing a bug (albeit a longstanding one) rather than adding a new feature so I'd like to get it in soon - looks like there some outstanding questions still on #2692 .

bias caveat: it's fixing a bug that we need fixed.

I want the multipackage stuff in for 12.1.0 so all of this goes out in the same release anyway, and the rebase collisions this will cause will make phil's job a lot harder than it already is.

That's fair enough - easier for me to rebase this on top of Phil's work, and it doesn't hold up which release this goes out in.

Okay, all clear for rebase + merge

Great, will tackle that first thing tomorrow.

@chef/client-core this is now rebased against @jaymzh's multi-package work.
@lamont-granquist / @jaymzh would particularly appreciate you two giving this the once-over, all specs are passing and I think I've preserved the original intent of your work but it'd be good to get some more eyes on this

Thanks @jaymzh  - will take a look at fixing the above comments up and will try and add some additional specs to catch those cases

FWIW, I did most of my testing with chef-apply, and things like:
package ['ack', 'less', 'iptstate'] do
  action :upgrade
end

and:
package ['ack', 'less', 'iptstate'] do
  version [...]
  action :install
end

And then uninstall some/all of those before I run the chef-apply, and/or install old versions of some.
I guess the goal here is to make something like this work:
package ['ack-<version>', 'less-<version>', 'iptstate-<version>'] do
  action :install
end

?

@jaymzh can you give an example of when the above might be an array and not work? parse_dependancy is called inside the iterator for package_name_array so surely we'd be dealing with one package at a time there?

well, sure, when you use the name that was passed in. but when you reference @new_resource.package_name, you're looking back at the full resource and getting the full array. Same thing for @new_resource.version

@jaymzh aaah I get ya - rgr, will get that fixed and add some specs to test for it.

@jaymzh one more thing to double check. Is it a safe assumption that for every element in package_name_array there will be an equivalent entry in new_version_array, or it'll be blank? I'm going to need to pass the version number provided to parse_dependencies since I can't look at @new_resource and will of course need to make sure it's the correct version requirement.

Yup. In fact we zip them together a lot. Missing versions will be nil.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@jaymzh / @chef/client-core I've updated to cater for @new_resource being an array and added a couple more specs to test this case.

Yeah indexes on the *_array stuff all match up, and the superclass has a helper to step through them all in lock-step.

I would like to see a test showing that
package 'test-package = 2.0.1.el5' do
  version '2.0.1.el5' # or '3.0.0.el6'
end

fails sanely and with enough information for users to see what they did wrong.  It doesn't need to be a special message if the current error logging communicates this well enough.

Other than my minor comment and doc updates, :+1:

@tyler-ball currently, the parse method of the RPMDependency class would give precedence to the version requirement specified in the resource name - this is the way that worked before this patch too.
In terms of failure mechanism, I'm guessing you'd like to see an error if both are specified instead of the above behaviour?

@jonlives If it was not an error before, you don't need to change it to an error now.  But I think that test is still valuable for documentation purposes - it can just assert that the version specified in the resource name is the one that gets installed.

@tyler-ball I've added that final test per your request and updated the docs.
@lamont-granquist you're the other Enterprise Linux maintainer currently, would you be able to have a quick check over this please? Once everything's approved will rebase again off master before merging, there's a big ol' merge conflict resolution in this branch.

One thing is you should probably squash your commits, the history will probably be a bit confusing at this point.

@lamont-granquist absolutely - will make sure it's all cleaned up for merge.

Could you add a spec test to make sure that this works:
yum_package ["foo", "bar"] do
  version ["1.0.1", "2.0.1"]
end

Sure, I can get that added tomorrow - prob should have been done as part of #2692.

@lamont-granquist added a spec testing that case, hopefully it's along the lines of what you were after.

:+1: :100: :cake: :gift:

Sorta hoping to not only get load_current_resource, but see that the install action did the right stuff...

@lamont-granquist is that not covered by the existing tests that @jaymzh added for #2692 though?

I guess what I'm saying is I'm unclear where exactly we have a gap in test coverage here with the combination of @jaymzh's specs and the ones added in this PR. It's beginning to feel a bit like every day I wake up to another request for a spec and I'm never gonna get this merged so if possible it'd be good to bullet point the test cases I'm not catching here and I'll do my best to add specs for 'em - would love to get this in before the next version freeze :)

Yeah, grok.  I'm in triage mtg right now.  I'll have to inspect the code closer when I get a bit of time.

Awesome thanks - much appreciated :)

Okay yeah I get it, you only changed LCR codepaths, so if the output of that is correct, then its the responsibility of the rest of it to get the install right.
:+1:

Right - awesome, will get this rebased, squashed and merged by end of week. Thanks!

Ignore this, will open new PR with squashed version