Custom theme is broken in latest release

Bug report 🐞
The latest version of GeistUI not supporting theme customization.
When I set the theme to "light" and set a custom palette, it doesn't reflect on the site.
Code: https://github.com/pankaj9296/create-next-app/blob/master/pages/_app.js
Vercel deployment: https://create-next-app-olive.vercel.app/
Also when I set the theme to "Custom", it builds the project successfully but throws an error on page load "An unexpected error has occurred."
Code: https://github.com/pankaj9296/create-next-app/blob/develop/pages/_app.js
Vercel deployment: https://create-next-app-ae613lkyu.vercel.app/
Also, the Grid and other components are broken in the latest release:
Check my live site, it's all broken:  https://iconvey-app-5bxc74haf.vercel.app/
It used to look like this: https://iconvey-app-2wq17a38v.vercel.app/
I had to revert back to use the 2.0.3 version to fix it temporarily.
Version & Environment

Version of browser: Chrome latest
Version of geist-ui/react: latest 2.1.2

Expection
The behavior I expect is, it should not break on page load and the theme should reflect on components.
Actual results (or Errors)
I got an error: An unexpected error has occurred.
code

Hi @pankaj9296, first, thanks for the demos, I was able to reproduce it easily.
When you create a Theme, you should to use Themes.create / Themes.createFromLight / Themes.createFromDark to import all the default values into your theme.
Note that the light / dark names are in use, so the first example will not work.
When you are missing values in the Theme (like gap and breakpoints), the Grid will not work either, like in the third example.
This is how it should look like:
const myTheme = Themes.createFromDark({
  type: 'my-light-theme',
  palette: {
    success: '#6C63EE', // primary/theme color
    link: '#6C63EE',
    successLight: '#7b73ff',
    successDark: '#574fdb'
  }
});

Thanks @ofekashery for the quick response.
The custom theme is now working.
Although I've one more issue with the latest version.
the GRID is broken.
Attached a video that shows the issue.
the new CSS property "display: inherit" seems to be breaking all existing GRID for me.
https://user-images.githubusercontent.com/17493609/108215513-6d03ef80-7157-11eb-9c1c-2f87cdcc9a59.mov
Please let me know if I'm doing anything wrong or you need a demo deployed on Vercel.

@pankaj9296
display: inherit; is the correct behavior, and inherit means that in most scenarios, the default property of display is flex, so, alignItems and justify such flex proprietary properties to work properly.
If your layout is broken, don't worry, it can be updated in just a few simple steps:

Vertically aligned and vertically centered (as in the video):

<Grid xs={24} justify="center" alignItems ="center" direction="column" />

Remove of flex layout, this is only in very few scenarios:

<Grid>

</Grid>

If you don't want to change any layout and just need the default layout model, you can force change display to unset/block. (this will invalidate properties such as justify, alignItems, because they only work under flex.)

<Grid xs={24} style={{ display: 'block' }} />

Although display: inherit will automatically set display to flex, but I think it would be better to just set it to flex, what do you think about here?

Thanks @unix for the help.
I'll go with the second solution to temporarily fix all GRID items for now.

Hi guys,
I just found another issue with the latest version of geist-ui.
On the page load, the theme takes some time to apply on page load. it creates a minor blink.
Like on page load the Success color is blue and after a moment, the color changes to purple (my theme color).
here's my latest preview deployment if you want to review https://iconvey-app-lc9hnnik7-pankaj9296.vercel.app
FYI, I'm using tree-shaking to reduce bundle size, I guess that doesn't affect it.
Thanks

I guess this may be related to server-side rendering, which will take some time to debug, I will follow up on this issue.

Great Thanks, Witt.

I think it's related to this problem (#258), but still no best solution.
If anyone would like to share their best practices, please reopen.


feat: add Italian translation

Please check if the PR fulfills these requirements

[X] It's the right issue type on the title
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[X] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[X] It does not introduce a breaking change or has a description of the breaking change

Description
Translations for Italian

@mredaelli Thanks for the contribution
Could you fix your PR refer to https://github.com/nhnent/tui.editor/pull/205/files ?
Then I can merge it.

Should be done. Let me know if I missed something :)

Looking forward for this merge. Thanks @mredaelli :)

Thank you @mredaelli !! I will merge it soon @michgerts :)


fix: fix markup error in summary

Goals:
Fix error when some pattern is shown in summary

Codecov Report
Base: 87.85% // Head: 88.42% // Increases project coverage by +0.56% :tada:

Coverage data is based on head (5352671) compared to base (bb9d1c3).
Patch coverage: 66.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #739      +/-   ##
==========================================
+ Coverage   87.85%   88.42%   +0.56%
==========================================
  Files         133      133
  Lines        6614     6615       +1
==========================================
+ Hits         5811     5849      +38
+ Misses        803      766      -37

Flag
Coverage Δ

docarray
88.42% <66.66%> (+0.56%)
:arrow_up:

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

Impacted Files
Coverage Δ

docarray/document/mixins/plot.py
79.04% <66.66%> (+0.12%)
:arrow_up:

docarray/array/mixins/parallel.py
71.66% <0.00%> (+3.33%)
:arrow_up:

docarray/document/mixins/sugar.py
80.00% <0.00%> (+15.00%)
:arrow_up:

docarray/array/mixins/post.py
95.12% <0.00%> (+78.04%)
:arrow_up:

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

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


Remove iOS stubs

Plugins that don't actually support iOS are no longer required to have
an iOS stub to prevent build failures. This removes all iOS stubs from
plugins that don't support iOS, and changes the fallback behavior for
the repo tooling to treat a missing flag as Android-only.
Partially fixes https://github.com/flutter/flutter/issues/58285

Turns out this is blocked by https://github.com/flutter/plugin_tools/pull/102/files#diff-7a0a4bb084bbea210ea6f06f08df00fd93af181200e48ba2acff4c7a1d87d077R182. We need to either do the breaking change, or figure out a more targeted legacy filter than assuming any platform with either iOS or Android supports both.

@cyanglaz I think this is ready for review; most is rubber-stamp, but I made slight changes to drive_examples_command.dart and .cirrus.yml to unblock the removal that should be reviewed.
(@blasten I think this is an example of a change where I'd feel more comfortable having unit tests, re recent conversation.)

I see. In the past, there was a time when the script were misconfigured, and tests were skipped as a result. Unfortunately, the issue wasn't in the tool, but in the scripts. or even in the .cirrus file.  I think with GitHub actions it's very clear what tests ran because it shows the check, so instead of  build-ipas+drive-examples CHANNEL:beta PLUGIN_SHARDING:--shardIndex 0 --shardCount 4  there is a plugin-foo/driver test (iOS).
Hopefully we  can clean this up entirely. :)

(I'm not going to republish anything for this change; it shouldn't really affect any plugin users.)


Broken link to https://alpha.openaddressesuk.org/about/addingdata

On this page https://alpha.openaddressesuk.org/blog/2015/02/12/inference.

Thanks, just waiting for CI to pick up this fix:
https://github.com/OpenAddressesUK/theodolite/pull/211


x/build: add builder that tests usage of gccgo to bootstrap go gc

There have been issues now and in the past about bootstrapping Go gc from gccgo being broken #40855, #30771.
Documentation at https://golang.org/doc/install/source#bootstrapFromGccgo suggests that bootstraping from gccgo is supported.
If this is the case I suggest we add a builder for that. To not be blocked on ressources I would assume a build only linux/amd64 builder would suffice to catch bootstrap issues.
/cc @ianlancetaylor @dmitshur

Given we say it is supported, I agree we should aim to have a test or a builder to confirm that it hasn't regressed.
We have some make.bash-only builders (e.g., search for CompileOnly in x/build/dashboard), so this can probably be arranged in a similar way.
Which version of Gccgo should be tested, and how often should we aim to update it?
/cc @cagedmantis @toothrot @andybons

gccgo is released as part of GCC, and a new major version of GCC is released once a year.


[path-colors] Update path color css

Quick CSS update for inheriting colors when possible, and removing unnecessary lines.

 Path Colors Quick Fix


Bucketer: Fix LOG_LEVEL.WARN -> LOG_LEVEL.WARNING

Fixes the only instance of LOG_LEVEL.WARN, which is undefined. The available level is LOG_LEVEL.WARNING: https://github.com/optimizely/node-sdk/blob/master/lib/plugins/logger/enums.js#L20

build

@stiliyan Thanks for the PR! Did you sign our CLA?

@wangjoshuah just did.

Coverage remained the same at 98.558% when pulling ac8d125e13a013e8284eb35b6549797d476d2390 on stiliyan:patch-1 into 7efd5b97ba61422d06ee8509213d0a21ec726c37 on optimizely:master.


Autorest Regen Preview to 3.0.0-alpha.20230411.1 by Dapeng Zhang from refs/pull/3257/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3257

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.EventHubs


fix: drop joblib dependency

Joblib was only used for joblib.hash for dataframes, but there's hash_pandas_object for that.
This naturally changes the hashes generated (but so could have any internal change in joblib so far) and furnishes for that by adding a 2@ (version 2) prefix to the newly-generated hashes.
Tangentially refs #1056

Codecov Report
Base: 90.91% // Head: 90.92% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (b187f90) compared to base (2462119).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head b187f90 differs from pull request most recent head 0b115b4. Consider uploading reports for the commit 0b115b4 to get more accurate results

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1090   +/-   ##
========================================
  Coverage    90.91%   90.92%
========================================
  Files          174      173    -1
  Lines         4929     4934    +5
========================================
+ Hits          4481     4486    +5
  Misses         448      448

Flag
Coverage Δ

py3.8-ubuntu-latest-pandas
90.92% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/pandas_profiling/utils/dataframe.py
80.48% <100.00%> (+1.00%)
:arrow_up:

tests/unit/test_typeset_default.py
95.45% <0.00%> (-4.55%)
:arrow_down:

tests/unit/test_utils.py
100.00% <0.00%> (ø)

tests/issues/test_issue523.py
100.00% <0.00%> (ø)

tests/issues/test_issue545.py
100.00% <0.00%> (ø)

...ndas_profiling/model/pandas/correlations_pandas.py
100.00% <0.00%> (ø)

src/pandas_profiling/utils/compat.py

src/pandas_profiling/model/typeset_relations.py
89.33% <0.00%> (+0.29%)
:arrow_up:

src/pandas_profiling/model/correlations.py
89.65% <0.00%> (+1.13%)
:arrow_up:

..._profiling/model/pandas/describe_numeric_pandas.py
98.38% <0.00%> (+1.46%)
:arrow_up:

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

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


Alessandro scremin dashboard hackathon

Adjust changes from original merge request by Alessandro Scremin

@AlessandroScremin
We are currently creating a guideline for merge requests to the repository to facilitate the process.
Initially the build crashed due to the following errors that can also be seen in the attached screenshot:

A colon (":") in the Description key caused the error YAMLSemanticError: Nested mappings are not allowed in compact mappings.

The interpreter recognizes this as a new (nested) key unless you specify the description as string with "YourText" or provide a pipe symbol ("|") before the text, as can be seen for the License key.

Square brackets in GeographicalCoverage and TemporalAvailability keys indicate an array, but the interpreter expects a string.
A file with the name ICEYE_E13c.yaml was a complete duplicate of ICEYE_E13b.yaml and the build could not find the respective subfolder and readme because it was not provided.


306: Enhance Ausweisen-Tab

New screenshots, yay:
Without Eak-Card

With Eak Card

With Eak Card, Tap on "Weitere Aktionen"

After Positive Verification:

Wasn't able to test this full. The Administration backend crashes for with
Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data
That mean I can not generate a qr code right now for validation.

@maxammann The local administration?

@maxammann The local administration or on staging / production?

local

Ahh... Okay, I think we check if the user is logged in but there's no possiblity to log in at the moment :D I always used a card that I had already generated. @aiquita We need the login asap :D

I addressed all your issues with landscape mode and tablet viewport. If you want you can re-review.


Add @pepyakin as a bindgen reviewer

🎉🎉🎉
r? @emilio

This change is

@bors-servo r+

:pushpin: Commit d94b1fe has been approved by emilio

:hourglass: Testing commit d94b1feb3960e68592ef46b587ef3e6a9347e1c0 with merge df07d3ace136a1c4594042af659f8584ba59e8fb...

:broken_heart: Test failed - status-travis

:sunny: Test successful - status-travis
Approved by: emilio
Pushing df07d3ace136a1c4594042af659f8584ba59e8fb to master...

This doesn't seem to have been enough to let @pepyakin r+ things... anyone know what else needs to happen?
https://github.com/rust-lang-nursery/rust-bindgen/pull/1061#issuecomment-334546471

Presently highstating buildmaster to actually apply these changes :)


[WIP] SlickDriver configures an AsyncExecutor for JNDI resources

Fixes #142

FYI, I am working on a change such that the slick configuration is loaded by an akka extenstion. See https://github.com/dnvriend/akka-persistence-jdbc/compare/enable-single-db-configuration
Using this, I want to create the possibility to create a single slick database which is used for the journal, read-journal and for the snapshots. Maybe this resolves the problems above.

@WellingR yes, that will help.
We will need a global config thing as well to have one single config for the AsyncExecutor.

closing because superseded by #151


Add support for a "nightly" alias

Describe the bug
I had to comment out the next PHP 8.2 version as it does not exist yet for this action.
See: https://github.com/phpmyadmin/sql-parser/commit/dd2f634b9918ef7986783b324c734016ef7d2f09
TravisCI (sorry to mention it, I would prefer that we forget about it) had support for "nightly" in the php version matrix. This was helpfull
Are you willing to submit a PR?
Sorry, I am missing time

Ah, form mistake, not a bug

8.2 should work and set up 8.2.0-dev from the master branch of php. I added builds last week. The docs will be updated in the next release.
Test workflow: https://github.com/shivammathur/setup-php/runs/3496421413?check_suite_focus=true#step:6:1
In Travis, IMHO this was broken as they won't update the nightly as it would shift to the next to next version (8.2) and you would not be testing the next version (8.1) in your workflow until support is added for it and you add it to your workflow.
Instead of a nightly tag, I would rather prefer that for testing master, projects add the version in the workflow.

Added in develop (https://github.com/shivammathur/setup-php/commit/d068c17d9e2904a5b2c36561a68ad75857c30a22). It Will be in the next release.
Test workflow; https://github.com/shivammathur/test-setup-php/actions/runs/1204939520/workflow

Added in develop (d068c17). It Will be in the next release.
Test workflow; https://github.com/shivammathur/test-setup-php/actions/runs/1204939520/workflow

Thank you so much!
Will wait for the release and apply this on all repos

Released in 2.14.0


KeyError when calling map_ecotopes() on example data

When running map_ecotopes() on the example data (https://github.com/ghendrickx/EMMA/blob/master/examples/ex_map_data/output_map.nc) I got the following error:
KeyError: "No variable named 'mesh2d_face_x'. Variables on the dataset include ['FlowElem_xcc', 'FlowElem_ycc', 'waterdepth', 'ucx', 'ucy', 'sa1']"

The wrong map-configuration was set as default, this has been resolved (c9e51470da12c593bc9cb8a7370ceda507069194).


Optimise trajectory grid intersection for regular grids

The current trajectory grid intersection code handles the general case of IjkGridRepresentation (resqpy Grid) objects, including handling of faults, pinchouts and K gaps.  Intersections with regular grids (resqpy RegularGrid) would gain significant speedup from optimised code.

Initial optimisation has been made.  Further speed up could be achieved with more work if needed,

Closing this issue as existing optimisation is good enough.


Is Pyrosm dead?

Is this library still being maintained? I see there haven't been any new comments since late 2023 and the last closed issue is also from 2023. I am relatively new to processing osm data with python and would liketo know whether I can still rely on this library or whether I should turn to something a bit lower level like pyosmium which is much less user friendly but has regular updates?

Hi! I would not call us dead yet, although unfortunately I have had very limited time to maintain this library. However, the key functionalities of pyrosm should work regardless of the past inactivity in the repo. Depending on what you need, in addition to pyosmium you could also check the osmnx library which provides easy-to-use interface to fetch OSM data via Overpass API.


LogTracker_CharacterData_US - Updates

Any ability to auto update this data daily? Or document for those that can pull their own and implement into the addon?
Looks like
LogTracker_CharacterData_US hasn't been updated in almost 1 month.

https://www.reddit.com/r/wotlk/comments/10o7fr2/alternative_to_logtracker_addon/
People are asking updates on reddit too. @ForsakenNGS how can we help you to update data?
If you can give/open source the scraper we all can pitch in! And maybe change the update to weekly rather than daily?

See #13 I could release the code, but it breaks the TOS of warcraftlogs and may result in the account being banned. Until there is an official data source that allows this, I will maintain the freshly released intermediate solution that just shows the raid progression.


project active anymore?

is this project active anymore ?
did not see any codechange for a while
just curious if this would work with a current version of guacamole too (1.5.0)?

No, I do not develop it actively currently. Guess you’ll have to try if it works with newer version. On 2023-02-21, at 15:25, Norbert M Haigermoser @.***> wrote:
is this project active anymore ?
did not see any codechange for a while
just curious if this would work with a current version of guacamole too (1.5.0)?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Support reading java9Home from enviroment variable

Context
This way, contributors don't need to constantly remember to add -Djava9Home=$java9Home to running the Gradle build..
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Thanks. In my env it's an environment variable. My ~/.gradle/gradle.properties has enough in it.


Moves upload component to mobX

Changes introduced in this PR:

Introduces mobx and mobx-react-lite as core dependencies.
Intorduces eslint-plugin-mobx as a dev dependency.
Updates @typescript-eslint/parser

Issue

The upload experience did not scale well with large number of documents.
The upload experience couldn't handle Cancel all synchronously.

Changes
This PR introduces mobx as state management library for the Upload feature.
The cancellation feature has been enhanced by batching mechanisms.

LGTM. @SanjalKatiyar to tag.

/retitle Moves upload component to mobX

/lgtm

/cherry-pick release-4.18

/cherry-pick release-4.18-compatibility


chore: Added inactive issue workflow

Issues that are stale for 30 days will be marked as stale
Issues that are marked as stale for more than 14 days will be automatically closed.
No changes will be done to PRs

Ref: https://docs.github.com/en/actions/use-cases-and-examples/project-management/closing-inactive-issues

@mdwcrft  @proelke


python310Packages.aioswitcher: 3.2.0 -> 3.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.aioswitcher is: "Python module to interact with Switcher water heater"
meta.homepage for python310Packages.aioswitcher is: "https://github.com/TomerFi/aioswitcher"
meta.changelog for python310Packages.aioswitcher is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2.1 with grep in /nix/store/zqxj398cadr6z1b4rvpcq6yyw6hqyjax-python3.10-aioswitcher-3.2.1
found 3.2.1 in filename of file in /nix/store/zqxj398cadr6z1b4rvpcq6yyw6hqyjax-python3.10-aioswitcher-3.2.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.switcher_kis
python310Packages.aioswitcher
python39Packages.aioswitcher

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zqxj398cadr6z1b4rvpcq6yyw6hqyjax-python3.10-aioswitcher-3.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.aioswitcher https://github.com/r-ryantm/nixpkgs/archive/7be75f26dd9a8e2d033aae14d5264492ab46e31b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zqxj398cadr6z1b4rvpcq6yyw6hqyjax-python3.10-aioswitcher-3.2.1
ls -la /nix/store/zqxj398cadr6z1b4rvpcq6yyw6hqyjax-python3.10-aioswitcher-3.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.switcher_kis
python310Packages.aioswitcher
python39Packages.aioswitcher

Maintainer pings
cc @fabaff for testing.

@ofborg eval


Statsd deployment name is broken

So a few days ago one of our monitoring dashboards stopped working. Rather than the usual deployment name of cf, the deployment name was now p("statsd_injector.deployment").empty? ? spec.deployment : p("statsd_injector.deployment"). Interesting, we thought. Turns out the <%= ... %> that were removed here were kinda important : )
Looks like there's also PR #4 that does the right thing as well.

Thanks for the heads-up. We'll take a look at it.


uuids of the demo users are hardcoded

Describe the bug
When playing around with OCM I noticed (again) that uuids of the demo users are hardcoded, which makes them unusable for OCM tests. See details below:
Steps to reproduce

As admin on instance A create an OCM invitation
As einstein on instance B use the OCM invitation to accept the federated connection
Create a folder test and open the Sharing panel in the sidebar
Select External as user type and search for Einstein
external Einstein is shown ✅
Select external Einstein and create the share

Expected behavior
External einstein is shown as share receiver
Actual behavior
Internal einstein is shown as share receiver since both einsteins have the same uuid and then oCIS seems to prefer the internal user.
Thoughts
This is not really a software bug, as we expect the uuids to be unique! But maybe it is possible to randomize the uuids of the demo users? Is there a valid reason to hardcode them? Or did we just never have the need to make them unique? For OCM demo purposes it would be important.

Is there a valid reason to hardcode them?

I think the only remaining reason is the hardcoded default role-assignments in the settings service: https://github.com/owncloud/ocis/blob/master/services/settings/pkg/store/defaults/defaults.go#L353

Related ticket: https://github.com/owncloud/ocis/issues/9927  (and probably the better way to address this)

This has been fixed meanwhile. By https://github.com/cs3org/reva/pull/4833 and followups.


Bug: steam login users may have same nickname or violates the restriction of casdoor username

The current version  (v1.133.0) uses Steam nickname as username, but multiple Steam users can use the same username, and the username can contain CJK characters. Suggest to use unique 64bit steamtid as username.
https://github.com/casdoor/casdoor/blob/v1.133.0/idp/goth.go#L285
#1203

Fixed by: https://github.com/casdoor/casdoor/commit/8b222ce2e396dc52feb3b6adc55d3ad58d31d4b3


[SPARK-18567][SQL] Simplify CreateDataSourceTableAsSelectCommand

What changes were proposed in this pull request?
The CreateDataSourceTableAsSelectCommand is quite complex now, as it has a lot of work to do if the table already exists:

throw exception if we don't want to ignore it.
do some check and adjust the schema if we want to append data.
drop the table and create it again if we want to overwrite.

The work 2 and 3 should be done by analyzer, so that we can also apply it to hive tables.
How was this patch tested?
existing tests.

cc @yhuai @gatorsmile
The first commit is from another PR and you can ignore it. Do you think we should target this ticket to 2.1? It's kind of a refactor but do fix some problems.

Test build #69084 has started for PR 15996 at commit 7f90a10.

Test build #69084 has finished for PR 15996 at commit 7f90a10.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69084/
Test FAILed.

A general issue: after we moving the execution of Append and Overwrite into DataFrameWriter, the verification in AnalyzeCreateTable is not called. Some logics are still required.

Test build #70026 has started for PR 15996 at commit 89f148b.

@gatorsmile , can you point out which verification we need to add back from AnalyzeCreateTable?

Test build #70026 has finished for PR 15996 at commit 89f148b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70026/
Test FAILed.

Test build #70061 has started for PR 15996 at commit 172f6eb.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70061/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #70074 has started for PR 15996 at commit 172f6eb.

Test build #70074 has finished for PR 15996 at commit 172f6eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70074/
Test PASSed.

Merged build finished. Test PASSed.

Test build #70187 has started for PR 15996 at commit 1efb892.

Test build #70188 has started for PR 15996 at commit 6c64007.

Test build #70187 has finished for PR 15996 at commit 1efb892.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70187/
Test FAILed.

Test build #70188 has finished for PR 15996 at commit 6c64007.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70188/
Test FAILed.

Test build #70305 has started for PR 15996 at commit 4178112.

Test build #70305 has finished for PR 15996 at commit 4178112.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70305/
Test PASSed.

Could we update the PR description and add the test case in PartitionProviderCompatibilitySuite.scala to reflect the external behavior changes of CTAS on partitioned data source tables?

Test build #70407 has started for PR 15996 at commit 28f88ef.

Test build #70408 has started for PR 15996 at commit 97dc307.

Test build #70407 has finished for PR 15996 at commit 28f88ef.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70407/
Test PASSed.

Test build #70408 has finished for PR 15996 at commit 97dc307.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70408/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

Test build #70455 has started for PR 15996 at commit 7481150.

Test build #70465 has started for PR 15996 at commit 59f06ce.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70465/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70455/
Test FAILed.

retest this please

Test build #70472 has started for PR 15996 at commit 59f06ce.

Test build #70472 has finished for PR 15996 at commit 59f06ce.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70472/
Test PASSed.

Test build #70532 has started for PR 15996 at commit 9a1ad71.

Test build #70532 has finished for PR 15996 at commit 9a1ad71.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70532/
Test FAILed.

LGTM. Can you update the comment to address my last comment (https://github.com/apache/spark/pull/15996#discussion_r93730700)?

ah https://github.com/apache/spark/commit/9a1ad71db44558bb6eb380dc23a1a1abbc2f3e98 failed.

Test build #70633 has started for PR 15996 at commit be9e7b5.

Test build #70633 has finished for PR 15996 at commit be9e7b5.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70633/
Test FAILed.

Test build #70634 has started for PR 15996 at commit 3a610ea.

Test build #70634 has finished for PR 15996 at commit 3a610ea.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70634/
Test FAILed.

Test build #70637 has started for PR 15996 at commit 3d14939.

Test build #70637 has finished for PR 15996 at commit 3d14939.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70637/
Test PASSed.

Test build #70654 has started for PR 15996 at commit 7f8d8c9.

Test build #70654 has finished for PR 15996 at commit 7f8d8c9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70654/
Test PASSed.

Merged build finished. Test PASSed.

LGTM except three minor comments

Test build #70672 has started for PR 15996 at commit d8f31f1.

Test build #70672 has finished for PR 15996 at commit d8f31f1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70672/
Test PASSed.

LGTM

LGTM. Merging to master.


Let's sort it out v1.0

Feature ✅
Description
The task is to implement:

Insertion sort
Selection sort
bubble sort

Example
First input will be name of algorithm followed by list of integers in next line.
Input: Selection
1 8 3 9 33 02 0 93 64 22 1 35
Output: sorted list of input
You are encourage not to copy code from online sources just for the name of open source contribution
Mention language in comments

@pratik-choudhari I'd like to work on this

I would like to do this in C++.

I would like to do this in JAVA @pratik-choudhari

Can I work on this in C++?

@codermind-divya This code has been assigned to @Awanit512 for C++, you can take up Java.

I am not well-versed with Java. No problem! I'll take up another issue.

Can i work with java? @pratik-choudhari


[Question]: Why RecurrentActorCriticPolicy State Placeholder Shape

Dear stable-baselines team,
I am using the RecurrentActorCriticPolicy in PPO2. In line 347 of policies.py, you define the variable state_ph_shape = (self.n_env, ) + tuple(state_shape). Should it be state_ph_shape = (n_batch, ) + tuple(state_shape)?
Thank you so much for the clarification.
Best regards,
Bruno

When dealing with RNNs the training the training has to be done sequentially, i.e. you can not sample two different batches of data from the same environment and first train on one and then on another, as the hidden states do not make sense after the first update (they differ from what the network would now create). The only way to parallelize the computation is to use multiple envs, leading to the "batch dimension" being of size "n_env".

Thanks for the explanation @Miffyli . As I understand each batch is modeled as a sequence hence, this implementation.
In the case, we want to consider a variable size of the observation space we would need to employ dynamic rnns and use the sequence dimension for the observation space, correct? In that case, we could not model the batch dimension as a sequence, correct? Is my point clear?
Thanks for the feedback.
Best regards,
Bruno

If by "variable size of observation space" you mean variable sequence length, then yeah that would require some dynamic rnns and more tuned handling of varying-length sequences. The current implementation does include treatment for episode boundaries (when episode ends, rest of the trajectory contains samples from a new trajectory and hidden state is reset).  I do not think implementation for this would be easy, though.
If there are no more issues/bugs to raise specifically about stable-baselines, you may close the issue.

That is all! Thanks a lot!


[WIP] polish code in rules

related to #150 and etc

Codecov Report
Attention: Patch coverage is 60.54422% with 58 lines in your changes missing coverage. Please review.

Project coverage is 77.07%. Comparing base (c2472a2) to head (936433d).

Files with missing lines
Patch %
Lines

pkg/inst-api/instrumenter/instrumenter.go
50.00%
26 Missing and 1 partial :warning:

...api-semconv/instrumenter/db/db_client_extractor.go
54.54%
11 Missing and 4 partials :warning:

...-semconv/instrumenter/http/http_attrs_extractor.go
63.63%
8 Missing and 4 partials :warning:

...emconv/instrumenter/net/network_attrs_extractor.go
50.00%
4 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (c2472a2) and HEAD (936433d). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (c2472a2)
HEAD (936433d)

4
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #171      +/-   ##
==========================================
- Coverage   82.60%   77.07%   -5.54%
==========================================
  Files          18       19       +1
  Lines         713      772      +59
==========================================
+ Hits          589      595       +6
- Misses        102      147      +45
- Partials       22       30       +8

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


Bug: Adjust data table column spacing on the cdd

Test Case
TC621
Steps to Reproduce

Navigate to the custom data download
Select hourly emissions as a sub type
Apply required criteria
select preview data
Select the columns on the data preview

Some of the data elements with in the data table are cut off. The specified column width will need to be adjusted for each data elements that is cut off. This will need to be fixed for emissions, allowance, compliance, and facility sub types. As apart of the scope of this ticket, the column width for each data label with need to adjusted to accommodate for the additional icon that will be added to the data table at a later time. See wireframes:
For reference: CDD column widths
Columns that need to be adjusted are highlighted in yellow/ and or have a note. Ensure, all of the columns are adjusted to accommodate for the additional icon that will be added. see:  wireframes
 Adjust all column widths to accommodate the additional icon that will be added to the data table
Actual Results
Some of the data elements with in the data table are cut off. See the screen shot below.

CDD column widths
Requirements
User Story
Acceptance Criteria

Tested #2717. Data elements look fine. Let me know if you have any feedback @tlageman-epa


Topic create and delete

Closes #26.

We do have admin API that expose everything.  However it uses static generic sig which is difficult for non Rust lang.  if we have dynamic version, that should help


[Help required] Access "/" result to a 404 (Windows/Ubuntu)

Hi everyone,
I have created an ASP.net project with Xamarin Studio, and then I have added "Nancy.Hosting.AspNet" package from NuGet.
I'm on Windows 8.1 and if I execute this code:
namespace NancyBlog
{
	using Nancy;

	public class HelloModule : NancyModule
	{
		public HelloModule ()
		{
			Get["/"] = _ => "Hello Nancy World";
		}
	}
}

The web brower returns me a 404, I tried to change the port in case or another webserver listen to 8080 and I have the same result, 404 error is returned by Mono.WebServer.XSP/<IP_ADDRESS> Win32NT server according to the HTTP response headers.
The "funny thing" is if I change the url, for example Get["/hello"] things works as expected.
Do you have any idea on fix this and why do I encounter this issue ?

Hi,
same issue on ubuntu/mint OS.
bash sudo apt-get install monodevelop sudo apt-get install mono-xsp4
Then in MonoDevelop, I did the same step explained in the previous post => 404 catched by Nancy.
This is very annoying.

So is it a nancy 404 or a web server / host 404?

@grumpydev thank you to help me, I'm pretty sure it's from nancy.

It does seem to be, but I'm at a loss as to why, I'd put my money on it being a weird mono/XSP bug/issue, but I haven't seen anyone else with the same or similar problems, and we have plenty of mono users.

No idea why that would help, but if it's fixed it's fixed :)

yes, pragmatism before all :D

@grumpydev sadly, this bug remains in Windows environnement :/ (Xamarin studio, any web browser, any port used).
To resume: "/" => 404
"/anything-i-want-as-url" => 200

Still a bug in XSP though by the looks of it.

how to fix it ?
I tried to use different versions of .NET availables on my PC, but the issue remains :(


fix nullability of ScrollMetrics

Description
Fixes flutter_gallery_sksl_warmup__transition_perf_e2e.
Related Issues
https://github.com/flutter/flutter/pull/65528

Submitting this on red since it fixes the tree.


Add Insteon & Z-Wave Thermostat support to ISY994 Component

Description:
This PR is to add Climate support for Insteon and Z-Wave Thermostats that are exposed by the ISY994 Controller hub component.
This will expose the climate device, as well as 2 binary_sensors for the Insteon thermostats which have a Heat Control and Cool Control sub-node for the main climate device node.
In addition, the isy994_control event has been updated to also expose value.  This is expected to be a non-breaking change in PyISY; (PyISY's event is now a dict instead of a string, but will represent itself the same as the command string it used to pass).  This change is vital to the climate integration, as some values are only made available from the event stream, not the node definition.
HOLD PENDING PACKAGE UPDATE
Please note, this PR requires an update to be included in the PyISY package.  Currently, it is pending https://github.com/automicus/PyISY/pull/44 which fixes some malformed commands for controlling the devices.  I am submitting this here now to make it available for review and make any changes required while the package changes are pending.  I have included a temporary commit that redirects the requirements to my fork with the changes--my intention is to revert that commit once the changes are incorporated and before this PR is accepted.
Related issue (if applicable): n/a
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8475
Example entry for configuration.yaml (if applicable):
n/a

Checklist:

[*] The code change is tested and works locally.
[*] Local tests pass with tox. Your PR cannot be merged unless tests pass
[*] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[*] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[*] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[n/a] New dependencies are only imported inside functions that use them ([example][ex-import]).
[*] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[*] New files were added to .coveragerc.

If the code does not interact with devices:

[n/a] Tests have been added to verify that the new code works.
Tested and functioning with my ISY device.

NOTE: PLEASE DO NOT MERGE UNTIL PyISY HAS BEEN UPDATED TO 1.1.2

@shbatm ping me when the library is updated.

Updated the PyPi requirements to use PyISY_beta==1.1.2.  This is a fork of the original PyISY I have pushed to PyPi.  This was done because I have not received any response from the PyISY developer in several months.  I'm not really in favor of accepting this PR using a forked requirement like this, but I will leave it up to the reviewers if they want to accept it for now and if the original PyISY is updated, reset the dependency.

It would be good if there is a github fork announced together with the pypi fork, so that other community members that want to continue evolving PyISY can rally together on a common repo.

I see there was some activity from the maintainer in one PR about a month ago in the PyISY repo. On the other hand there are PRs which haven't had a reply for years. 🤷♂

Yeah, it's been hit or miss with previous changes and I know there's a lot of active development on a different ISY interface that uses the library so I've been hesitant to run off in my own direction.

@balloob what do you want to do? Should we change to the pypi PyISY-beta fork?

I know that maintainer. Texted him to see if he prefers we fork or we can add people as collaborators.

Yeah, that maintainer guy is the worst. 😉
I gave Paulus owner access to the PyISY repo and the PyPI project so he can help with keeping it up to date. I highly suggest that someone else take over development of the PyISY library. I actually don't have any ISY's connected at the moment so I don't really have any way of maintaining the integrity of the library.

Alright, I will be giving @OverloadUT access to PyISY, and he will take it from here.

Confirming that I am taking over maintainance of the PyISY library. I'll start going over the PRs on that side, starting with the one that this change depends on!

@rmkraus -- Thank you for the development and support thus far, awesome module!
@balloob / @OverloadUT -- Thank you both as well for the support on this. Just want to let you know I'll be away for the next ~10 days.  Anything you need from me please let me know and I will address when I return.  There have been a couple people from the community testing this change as a custom_component and I know there is one issue that has not yet been investigated with a Z-Wave Thermostat, raised at (shbatm/home-assistant#1), and for @OverloadUT: my PyISY_beta branch has automicus/PyISY#46 incorporated as well as my changes from automicus/PyISY#44.

Just an update: I'm watching #23899 and once there is some resolution and consensus with things being discussed there, I will move forward with updating this PR to match the new climate 1.0 framework.  For the time being I have pushed a re-base to the current dev branch for my testing.  Please disregard and continue to hold this where it is.

Thanks for the update. I'll be sure to get the PyISY changes merged to align with those changes

Original PR has been amended to include a broader scope of changes to the ISY994 platform.  These are being included as one PR because the improvements have become intertwined with the addition of the climate platform.
Relevant feedback from the forums, including testers:
https://community.home-assistant.io/t/insteon-thermostat-2441th-for-isy
https://community.home-assistant.io/t/isy994-z-wave-sensor-enhancements-testers-wanted
https://community.home-assistant.io/t/isy994-variables-as-sensors
https://community.home-assistant.io/t/isy994-zwave-multilevel-sensor-6

Please consider splitting this PR into multiple logical parts. It's already too big.

Thanks so much for working on this, shbatm!  Great job and much appreciated.

Closing this PR for now until PyISY changes are implemented. All changes are available on my isy994-climate fork and can be tested as a custom component. Discussion will continue in the forum links above.
Once PyISY changes are implemented I will resubmit several PRs for the various changes implemented here.


Folders: Update command is_collaboration_restricted_to_enterprise not available

[ X] I have checked that the CLI documentation and API documentation doesn't solve my issue

Description of the Issue
The folder update API has a setting is_collaboration_restricted_to_enterprise which controls the setting of who can be invited to a folder. This is not available in the CLI v2.1.0
Versions Used
Box CLI:2.1.0
Operating System: MacOS Sierra
Steps to Reproduce
box folders:update -h
Error Message, Including Stack Trace
NA

@jacquesvandermerwe Thanks for letting us know about the missing flag; I opened a PR to add it and that should make it into the next CLI release.


⚠ Bofrost.de has degraded performance

In badb2bb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 950 ms

Resolved: Bofrost.de performance has improved in a295892 after 48 minutes.


ClueGaudiAlgorithmWrapper in nightlies not found

After sourcing the nightlies and running the 'ClueGaudiAlgorithmWrapper', this is not found:
Traceback (most recent call last):
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-08-07/x86_64-centos7-gcc12.2.0-opt/k4fwcore/338f4ec16d29a8e0d2b2ae98ea781d06fa62d7a8=develop-wmlbp3/bin/k4run", line 124, in <module>
    opts = parser.parse_known_args()
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-06-24/x86_64-centos7-gcc12.2.0-opt/python/3.10.10-jyeoxq/lib/python3.10/argparse.py", line 1859, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-06-24/x86_64-centos7-gcc12.2.0-opt/python/3.10.10-jyeoxq/lib/python3.10/argparse.py", line 2054, in _parse_known_args
    positionals_end_index = consume_positionals(start_index)
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-06-24/x86_64-centos7-gcc12.2.0-opt/python/3.10.10-jyeoxq/lib/python3.10/argparse.py", line 2031, in consume_positionals
    take_action(action, args)
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-06-24/x86_64-centos7-gcc12.2.0-opt/python/3.10.10-jyeoxq/lib/python3.10/argparse.py", line 1936, in take_action
    action(self, namespace, argument_values, option_string)
  File "/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-08-07/x86_64-centos7-gcc12.2.0-opt/k4fwcore/338f4ec16d29a8e0d2b2ae98ea781d06fa62d7a8=develop-wmlbp3/bin/k4run", line 45, in __call__
    exec(open(wrapper.name).read(), globals())
  File "<string>", line 1768, in <module>
ImportError: cannot import name 'ClueGaudiAlgorithmWrapper' from 'Gaudi.Configurables' (unknown location)

The error does not appear in case I source an old version of the stack (key4hep-stack/2023-04-08) with:
source /cvmfs/sw.hsf.org/key4hep/setup.sh

Solved with https://github.com/key4hep/key4hep-spack/pull/515


Add CHANGES.md

Created CHANGES.md
If is not obvious this is to keep track of individual changes on each release.

related to #141

Coverage increased (+0.1%) to 36.107% when pulling e5baf8ca806eb22d333ad2fef5208360eefbb671 on simontorres:add_changes_md into 8588c3d1baa1156e2ea6e95d545d1d2d12d6f75c on soar-telescope:master.


Push notification not working on some device (Unexpected behaviour)

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4
Firebase SDK version: 5.14.0
Firebase Component: Messaging
Component version: 3.2.2
Installation method: CocoaPods

[REQUIRED] Step 2:
Push notification not working on some device even after restarting and reinstalling app. Also it is successfully generating the token, when we send push from "https://fcm.googleapis.com/fcm/send" api it shows success but notification wont come. Also we tried from firebase console messaging section to sent globally and with the specific token too. It is only for some devices and even on the same device one day it will work and another day wont.
Steps to reproduce:
Random behaviour so unable to reproduce. Only thing is common sometimes it works on the same device and sometimes it wont.

Experiencing the same issue

Same, I've tried from PushTry and every other platform to test on my iOS device only with one specific correct token but still facing same issue.

Just observed one behaviour, few hours ago device A is getting the notification but device B is not. But after 1 hour on the same build when tried to send global notification from firebase console device B starts getting the notification but now device A is not getting.

Thanks for the report.
@ankitjaiswal1994 the version of Firebase you're using is well over a year old - we're currently on Firebase 6.23.0.
@vishvabhatt  and @anshumandash1995 can you please share which version of Firebase you're using?
Without specific reproduction steps it'll be hard to track anything down here. It could be an issue with the backend or APNS itself.
@chliangGoogle do you know of any backend issues recently?

@ryanwilson Thanks for your response.
I was using the exact same latest version 6.23.0. But in this thread someone mentioned that downgrading the version works fine https://github.com/firebase/firebase-ios-sdk/issues/2438
In conclusion, I am facing the same issue on latest and older version both.

Do you have device logs you could share? Without logs and without a repro there's likely nothing we can do to make progress on this.

@ryanwilson I don't what logs will help you. But I can give you the token which is not working. Here it is :
ctimO_nsM4I:APA91bGZtrZBFYvjfzvNgjfL0ioRcLDR2cVVNhGJPJEKwijK1Gqv2_kHaITCMCvjryQL5a_hWoW_gOACVggcZ66z5xR1OFqje3xZtF1VVKchatxXYhdTCIB3nrGzoTUKnZGoD84zaCf2
I hope using this token you can debug what is actually going wrong.

Hey all, if you're running into Messaging issues that you cannot reproduce but you are able to isolate individual Instance IDs that fail to receive messages, please file a support issue so the Firebase staff will be able to look directly at your project information.

Hi all, I am having the same issue myself using Messaging 6.16.0. So far the issue only seems to affect iOS 13 devices (tested on 13.3 - 13.4.1), never happened on an older version so far.   The first difference I noticed between iOS 12 and 13 is that while for iOS 12 the framework returns nil as the fcmToken at fresh install, for iOS 13 I get the token from the previous app install until the defaultToken is downloaded.  Maybe this caching behaviour for the token could cause the issue?
I am using https://fcm.googleapis.com/fcm/send from Postman to send the notification.
Instance ID: dr1JrjVysEzBgHJOXSaIQ5
Token: "dr1JrjVysEzBgHJOXSaIQ5:APA91bFqaOz1fqdeWVtHQH_mNCvDXckIv_XnWuNTy4B3T8C3SziwevFHlgSsBLPNSha0XCySjg9BhEiHBTCB5Rx4EtJrqRNs0aAHG6klUhXmbFVEzhTW4c4Pr3QQguWIQdS5_KR2H-jH"
P.S. If I try to send a push using a cached token (from a previous app install on the same device), I don't receive "error:NotRegistered" but a success. In the past, using an old token from the same device would give the mentioned error.
In order to get notifications working again on those devices, I had to do several reinstalls of the app.

I'm having the same issue with 6.14.0 and watchOS. It used to work fine, what I have done meanwhile is upgraded to watchOS 6.2.5 beta. Something I noticed, is that instance ID (?) part of the token is 22 characters long compared to my iOS token, which is 11 (and contains an underscore).
Also I found out if I use the old sendToDevice() function firebase-admin (on Cloud Functions) the push notification is sent, if I use the send(), it fails either on invalid-arguments or not-registered depending if the token is new or not accordingly.
The watchOS push messaging is interesting as I'm not 100% sure which GoogleService-Info.plist I need to provide. In the watch extension I use watchkitextension plist but Firebase complains about it on startup (I've tried to use watchkitapp plist, but it doesn't affect the messaging outcome, it does not complain about the plist though):
[Firebase/Core][I-COR000008] The project's Bundle ID is inconsistent with either the Bundle ID in 'GoogleService-Info.plist', or the Bundle ID in the options if you are using a customized options. To ensure that everything can be configured correctly, you may need to make the Bundle IDs consistent. To continue with this plist file, you may change your app's bundle identifier to 'xxx.yyy.zzz.watchkitapp.watchkitextension'. Or you can download a new configuration file that matches your bundle identifier from https://console.firebase.google.com/ and replace the current one.

@charlie8093 your issue seems different than the one filed, can you file a new issue so we can follow up separately?

@ankitjaiswal1994 Can you provide debug log or file a customer support issue so we can follow up with you on the token query internally with our teams.
Here's how you collect the debugLog following the steps:
Enable "debugLog" by adding -FIRDebugEnabled flag on your xcode scheme: more details here https://firebase.google.com/docs/analytics/debugview


Fix issue #2

This wagon will be only associated with a GitLab protocol, thus avoiding conditionals seems like a pretty straightforward way of eliminating the issue altogether

I believe this should fix #2. Any chance it could be merged and published?


docs: fix typo

Deploy preview for docute ready!
Built with commit 8dca695bd6b51b1eb24ca78fe74ec9b4dab4706c
https://deploy-preview-193--docute.netlify.com

:tada: This PR is included in version 4.6.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update route-datastore-canary-default-tls.yaml

Updating from targetPort to service port.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Needs to be validated.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/70300

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/72950


Learn Relational Databases by Building a Mario Database - Typo in hint

Describe the Issue
Writing issue in the hints
Affected Page
https://www.freecodecamp.org/learn/relational-database/learn-relational-databases-by-building-a-mario-database/build-a-mario-database
Your code
look at the screeenshot
Expected behavior
Rename CREAT TABLE table_name(); into CREATE TABLE table_name();
Screenshots

System

Device: [Windows PC]
OS: [Windows 11]
Browser: [Chrome]
Version: [22]

Additional context
No response

This is the file with the typo - and here's some info on how to work on those repos.


[FB] launch_ancils:  Update merge-base to commit 42a1964

It is noted that when the feature branch was update, there were conflicts in the following files:
requirements/core.txt   - resolved by using requirements in master (the pinning in previous commits is no longer required)
lib/iris/tests/unit/fileformats/netcdf/test__load_aux_factory.py  - these conflicts are resolved by keeping the "cube_parts".


[ CNF-4622 ] - Trigger backup task and reconcile with the controller

Initial commit for triggering backup job

added backup templates
added backup implementation
added conditions to launch jobs and monitoring the states
update the status back to operator
modified reconcile logic
updated rest api return when backup field is nil

Also, please whenever you're done with the commits, squash them, thanks!

/unhold

/cc @vitus133

/retest

No further comments from me. @vitus133, anything further?

/lgtm


fix(launch): add missing launch args and defaults to lidar_based_detection.launch.xml

Some launch arguments were missing. These arguments and their defaults were added.
Description

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@alireza-moayyedi
Thank you so much for your contribution to Autoware!
Similar to other perception mode launchers, like camera_lidar_fusion_based_detection, even without adding these args to lidar_based_detection.launch.xml, the ones defined in the perception.launch will be inherited, so it will work without any issues.
Is there a specific reason for adding these arguments?

@alireza-moayyedi
I see. You mean you don't use perception.launch but use lidar_based_detection.launch directly.

@miursh precisely.

@miursh Hello, can this PR be merged or is there something more to do?

@alireza-moayyedi Thank you for the notification. I have just pressed the merge button


Update-Help has issues? Seems general issue?

PS C:\Projects\git\BuildAndReleaseFunctions\PowershellScripts> Update-Help -UICulture en-US
Update-Help: Failed to update Help for the module(s) 'PSReadline' with UI culture(s) {en-US} : One or more errors o
ccurred. (Response status code does not indicate success: 404 (The specified blob does not exist.).).
English-US help content is available and can be installed using: Update-Help -UICulture en-US.

I've now forced it with
Update-Help -Verbose -Force -ErrorAction SilentlyContinue
Source: https://stackoverflow.com/questions/39834452/powershell-fails-with-update

I'm not positive, but I think that's a known problem that, as a one-time migration step, requires renaming the local folder from PSReadline to PSReadLine - note the uppercase L.

Yes - this is a 'well known' problem. For certain definitions of well know. I hit it this week in a book chapter I am writing.
It is awful that the help URIs are case sensitive.  But given that. What brain-child thought that up?
But in the mean time, is there ANY chance of some remediation possible? Could the MSI, for example, so a silent rename of this folder?


Enforcing docstring length (not the code snippets)

Is it possible to enforce docstring length (I know this possible for code snippets, but I mean the strings). Here's an example: Enforce docstring line length of 75:
def f(a, b):
	"""
	Very long long long long long long long long long long long long long long long long long description.

	Parameters
	----------
	a: int
		First number to add
	b: int
		Second number to add

	Returns
	-------
	int
		Another long long long long long long long long long long long long long long long long description.
	"""

def f(a, b):
	"""
	Very long long long long long long long long long long long long long long
    long long long description.

	Parameters
	----------
	a: int
		First number to add
	b: int
		Second number to add

	Returns
	-------
	int
		Another long long long long long long long long long long long long
        long long long long description.
	"""

Hy @ma-sadeghi
Not yet. We want to add docstring (the comment content) formatting in the future and are also thinking about string formatting in general (automatically splitting or collapsing them) but this isn't supported today.

@MichaReiser thanks for your quick reply. Looking forward to it!

Not sure if this is also what you had in mind @ma-sadeghi, but I'd suggest not only convert this:
def foo():
    """
    Foo foo foo foo foo foo foo foo foo foo one two three four five six seven eight nine ten.
    """
    return "foo"

Into:
def test_filter_tariffs_no_filter():
    """
    Foo foo foo foo foo foo foo foo foo foo one two three four five six
    seven eight nine ten.
    """
    return "foo"

But also:
def foo():
    """
    Foo foo foo foo foo foo foo foo foo foo
    one two three four five six seven eight
    nine ten.
    """
    return "foo"

Into:
def test_filter_tariffs_no_filter():
    """
    Foo foo foo foo foo foo foo foo foo foo one two three four five six
    seven eight nine ten.
    """
    return "foo"

@Peque Yep, that makes sense!

+1 to this request

I came across this and it's really annoying. With the following config, I get errors from ruff check that ruff format can't fix:
pyproject.toml:
[tool.ruff]
line-length = 120

[tool.ruff.lint]
extend-select = [ "E" ]

[tool.ruff.format]
docstring-code-format = true
docstring-code-line-length = 70
# Proposed:
# docstring-format: bool = true
# docstring-line-length: int = [tool.ruff].line-length

example.py
"""This is doing nothing really! It shall only show, how to confuse ruff in a way that it throws an error it cannot fix itself... Which I find kind of annoying."""

def main():
    """aaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"""

Using these files, I get this when running ruff check:
example.py:1:121: E501 Line too long (163 > 120)
  |
1 | """This is doing nothing really! It shall only show, how to confuse ruff in a way that it throws an error it cannot fix itself... Which I find kind of annoying."""
  |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ E501
  |

example.py:5:121: E501 Line too long (134 > 120)
  |
4 | def main():
5 |     """aaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"""
  |                                                                                ^^^^^^^^^^^^^^ E501
  |

Found 2 errors.

yet, ruff format outputs 1 file left unchanged.
ruff 0.6.8

Funny addition, don't know if it's a bug:
When running ruff check against this change, it says All checks passed!
diff --git a/example.py b/example.py
index 4752a9e..5726fe6 100644
--- a/example.py
+++ b/example.py
@@ -1,5 +1,5 @@
-"""This is doing nothing really! It shall only show, how to confuse ruff in a way that it throws an error it cannot fix itself... Which I find kind of annoying."""
+"""Thisisdoingnothingreally!Itshallonlyshow,howtoconfuseruffinawaythatitthrowsanerroritcannotfixitself...WhichIfindkindofannoying."""

 def main():
-    """aaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"""
+    """aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"""


WSPR spot labels do not align with the spots themselves

WSPR Trace IDs are once again not aligning with the actual Trace.
Bob K4RCG

Hi Bob, the intended display is like this, with all WSPR traces at the top. This helps prevent overlap because WSPR traces are more dense than the labels (this is why numbers are used)

Understood, but my problem is that the numbers do not align with
traces...i.e. they do not superimpose on the trace.
Bob
On Wed, Aug 19, 2020 at 8:54 PM Scott W Harden<EMAIL_ADDRESS>wrote:

Hi Bob, the intended display is like this, with all WSPR traces at the
top. This helps prevent overlap because WSPR traces are more dense than the
labels (this is why numbers are used)
[image: image]
https://user-images.githubusercontent.com/4165489/90688341-53332f80-e23c-11ea-8d85-998abb4d3de3.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swharden/FSKview/issues/44#issuecomment-676694189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEHCPNMEITIFLPYFAEVW3DSBQ3XRANCNFSM4QFK7GAQ
.

My bad Bob, I misunderstood your initial description. I think the problem here is that your dial frequency doesn't exactly match what it should be - looks 30Hz off to me!

Ahhhh....  good catch!!  Calibration issue affecting the ID placement!
TNX!!!!
Bob
On Wed, Aug 19, 2020 at 10:43 PM Scott W Harden<EMAIL_ADDRESS>wrote:

My bad Bob, I misunderstood your initial description. I think the problem
here is that your dial frequency doesn't exactly match what it should be -
looks 30Hz off to me!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swharden/FSKview/issues/44#issuecomment-676786332,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEHCPMKAN2T4CDXLTDKACLSBRIS5ANCNFSM4QFK7GAQ
.

That’s definitely my problem! My rig calibration is off a wee bit. I
typically tune off my desired frequency by a few Hz to center QRSS in the
band. After you mentioned that may be my trace ID issue, I’ve been trying
to use the Calibration function
to address that issue.
I’m involved with a Scottish WSPR group and we will be doing propagation
tests tonight on 30m. Additionally, participants will be looking at their
WSPR traces using your FSKview app. Good stuff!’
73
Bob K4RCG
On Wed, Aug 19, 2020 at 18:49 Robert Stohlman<EMAIL_ADDRESS>wrote:

Ahhhh....  good catch!!  Calibration issue affecting the ID placement!
TNX!!
Bob
On Wed, Aug 19, 2020 at 10:43 PM Scott W Harden<EMAIL_ADDRESS>wrote:

My bad Bob, I misunderstood your initial description. I think the problem
here is that your dial frequency doesn't exactly match what it should be -
looks 30Hz off to me!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swharden/FSKview/issues/44#issuecomment-676786332,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEHCPMKAN2T4CDXLTDKACLSBRIS5ANCNFSM4QFK7GAQ
.


Show error when compiling external modules with -out or -outFile option

See this issue:
http://stackoverflow.com/questions/34816304/why-does-adding-this-require-import-stop-node-js-outputing-to-the-console/34826050#34826050
This took me ages to get to the bottom of. no error messages to indicate I was doing something stupid just no output at all in the js file.
Suggest that an error message is displayed when we are compiling external modules with an invalid option like --out or --outFile

Hey, sorry about the frustration. Instead of giving an error, we decided to do the "right" thing. #5090 should fix this.
Can you give the nightlies a try and let us know how it works out?

The user is using commonjs based on the stackoverflow tsconfig. Hence it will still not work (https://github.com/Microsoft/TypeScript/pull/5090#issuecomment-163746277) and maybe should give an error :rose:

That works fine in the nightlie. I get a message:
"Only 'amd' and 'system' modules are supported alongside --out"
Many thanks


VMware Carbon Black Cloud - Failing due to processing speed, Function app time out duration

Describe the bug
With larger carbon black environments where carbon black events are being brought in from S3, the function app will fail due events being generated in larger quantities than the function can handle. This results in not all events being processed before the function time out are hit (Default 5 minutes)
Increasing the function time out further than the interval will allow the function app to complete but creates an issue of other missed logs since the interval and timeout do not match.
Increasing the function app ASP to a premium plan does not fix the issue.
To fix the issue, there needs to be a way to have the function run faster, this may be a limitation with using PowerShell, and need to unzip all the files from S3.
I looked at seeing if we could implement some type of parallel processing loop for this function app but was unable to get it to work.
To Reproduce
Steps to reproduce the behavior:

Try to use the function app to bring in all events from a mid size environment (2000+ seats)

@cfbv : This seems to be an old problem, and this connector may have already had numerous updates, can you please confirm if your problem has been solved? Thanks!!

hi @cfbv, based on previous comment closing this issue. Feel free to reopen issue if you still need assistance.  Thanks!


Configure once and create multiple instances...

Is it possible to statically initialize a machine and reuse its definition in multiple instances ?

You typically write a class that holds the definition and all actions. When you create multiple instances of this class you get what you asked for, without "cloning".
See https://github.com/appccelerate/sensorsample/blob/master/source/SensorSample/Sensors/DoorSensor.cs for an example: the DoorSensor uses an Appccelerate.StateMachine in this way.
The Appccelerate.StateMachine is just the driver, the class holding the instance and providing the action is the actual state machine.
Does this help?

Yes, i was implementing my class like that, but it could be interesting to configure the machine once and instantiate that multiple times in different threads.
Could this be a feature request ?

It surely can be a feature request. This would solve the problem, that the setup is rather slow compared to other libraries (as I was told - didn't find the time to check for myself.

Finally done in version 5.1.


[DOC] #noqa comment appears in docs

Brief Description of Fix

A #noqa:E501 comment in the docstring from encode_categorical() appears in the docs. The #noqa:E501 comment exists due to a long url in the docstring which angers pycodestyle.
I'm currently not familiar enough with reStructuredText or Sphinx to know how to solve this issue.
A quick search of the published docs shows a number of #noqa comments that may not be desired.
Relevant Context

Link to documentation page
Link to exact file to be edited

This is a great catch, @hectormz! I'm not too worried about these; the # noqa comments are in the docstrings, and as such they get linted. A way around them is to modify the code blocks, but that shouldn't be a big problem.
For now, I'll tag this as "needs further discussion", as I don't have strong opinions on whether they should appear in the docs or not - but I'd like this to continue to be discussed.

Sure, not mission critical. Just happened to notice it, and knew it wasn't our intent to have #noqa leak into docs.
On a related note, it looks like the url in remove_empty doc is formed correctly, while convert_matlab_date is not.
That should be an easy fix

I had this problem in a package I maintain, and we solved it by moving #noqa to the line where the triple quote ends, like this:
"""A fancy docstring.

It'd be a shame if we ruined this beautiful docstring with a long
`StackOverflow`_ link.

.. _StackOverflow: https://stackoverflow.com/questions/38884538/python-pandas-find-all-rows-where-all-values-are-nan
"""  # noqa: E501

Example from my package's code: https://github.com/glotzerlab/freud/blob/0dae9cee1423ae9a0ed8923547e44c41b93b5672/freud/order.pyx#L188-L194

Thanks for the suggestion @bdice it worked nicely! @ericmjl , do you agree this is a good way forward, to apply #noqa E501 to docstrings? The only drawback is that all new content in the docstring gets a pass, but only hyperlinks should be allowed to be "too long".

@hectormz let's use the trick that @bdice suggested.
In the future,
I am going to push for us to use semantic line breaks
rather than 79-character line breaks.
We get more lines of docs,
but they are easier to diff and read.
:smile:

@ericmjl I see what you did there. 😆 Glad to see that worked for you. Good luck!


Update package.json to allow angular 17

Type of change

[ ] Docs
[ ] Bug fix
[ ] Feature

Packages

[ ] @livechat/widget-core
[ ] @livechat/widget-react
[ ] @livechat/widget-vue
[x] @livechat/widget-angular

Issue

Description

Hello again. Patch has just landed on the prod


Bug: redirect_to redirecting via HTTP instead of HTTPS

redirect_to url, turbolink: true
Redirects via HTTP instead of HTTPS on an HTTPS website which causes the following problem:
The browser rejects the HTTP request with the following error:
Mixed Content: The page at 'https://example.com/login' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://example.com/'. This request has been blocked; the content must be served over HTTPS.

Fixed by 9d0e8f0a464142901b298eec11ad8d7a768a2c8b.

The weird thing is that I am experiencing this same issue with Turbolinks 5.0.1 in a Rails 5.0.1 app.
Shouldn't this fix be applied there, if it indeed fixed it?

Tubolinks 5 is in another project. See turbolinks/turbolinks.


Modify PGBouncer file permissions to permit viewing by authorized accounts

Describe the bug
After deploying PGBouncer, the userlist.txt and pgbouncer.ini files are set to 640:

-rw-r----- 1 root root    0 Apr 28 07:28 userlist.txt
-rw-r----- 1 root root 9.2K Apr 28 07:28 pgbouncer.ini

To Reproduce
Default result of chart
Expected behavior
File permissions to be set to 644 to permit viewing. Perhaps the userlist.txt should remain 640 for security.
Deployment
timescaledev/timescaledb-ha:pg12.4-ts1.7.2-latest

These lists are not used in the default pgBouncer configuration - the pgBouncer is a pass-through configuration,
verifying users/databases against the actual database.
What is the issue/error message you're running into?

Is this using #222? Does pgbouncer not work with the userlist.txt? In my deployment (which isn't using #222 yet), ownership is root:postgres, not root:root

In my install it looks like this:
-rw-r----- 1 root root 0 Apr 28 07:28 userlist.txt
-rw-r----- 1 root root 9.2K Apr 28 07:28 pgbouncer.ini
To Feike, the pgbouncer.ini contains config info, per the docs:
Description
Generic settings
Log settings
Console access control
Connection sanity checks, timeouts
TLS settings
Dangerous timeouts
Low-level network settings
Section [databases]
Section [users]
Include directive
Authentication file format
HBA file format
Example
Not being able to see the config makes troubleshooting impossible.

pgbouncer is using the configuration file that is generated here:
https://github.com/timescale/timescaledb-kubernetes/blob/master/charts/timescaledb-single/templates/configmap-pgbouncer.yaml#L24
It is not using pgbouncer.ini, it using the one from the configmap:
This is the startup command for the pgbouncer container:
        command:
        - /usr/bin/env
        - -i
        - /usr/sbin/pgbouncer
        - /etc/pgbouncer/pgbouncer-sidecar.ini

Also, it is not using userlist.txt, however if we merge #222, it may, and then it will be visible.
To troubleshoot currently, you could do:
kubectl get configmap ${RELEASE}-pgbouncer -o 'go-template={{index .data "pgbouncer-sidecar.ini"}}'
Alternatively, you can have a look inside the sidecar container:
kubectl exec -ti pod/${RELEASE}-0 -c pgbouncer -- cat /etc/pgbouncer/pgbouncer-sidecar.ini

OK, Thanks very much Feike, I didn't know that. I think merging #222 is not a bad idea, just to be able to permit admins who don't have visibility to the charts.
Insofar as this issue, I'll close it as your answer is satisfactory and much appreciated,


Throw proper exception when missing resource

Fixes #143

Hi @ryanbrandenburg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@NTaylorMullen @DamianEdwards if you guys could review me here?

:watch:

:watch:

:up: :date:

:watch:

:shipit:

Looks like a change hid this. Re-raising it: https://github.com/aspnet/Localization/pull/184#discussion_r48516258

:watch:

:up: :date:

:shipit:


Display filename of vulnerable code snippet

Signed-off-by: chinggg<EMAIL_ADDRESS>Show filename along with full path above the vulnerable code snippet.
I think showing the filename may come in useful for the upcoming coding challenge in the future

🚫 I fail to see the value in disclosing the internal file names or even path structure of the Juice Shop codebase. Or at least not as a standalone feature for the current code snippets. Maybe this changes during GSoC if/when coding challenges are built, but let's not get ahead of ourselves.

I don't want to encourage people to look through the codebase. The snippets are hand picked and curated (with vuln-hide against spoilers), but showing the local path kind of suggests that it's okay to open it and read it. Which it isn't.

@bkimminich I have asked some questions about the code-snippet on Slack. I think I could write a good proposal only when I understood your original ideas about the code-snippet. Thanks for your feedback!

If a convincing proposal promises to implement "live code fixing" challenges, I'd be thrilled to have that, but I assume this is a tough nut. Therefore I think a good "select fixed code" proposal is just as good, because I'd assume it's definitely achievable. A two step approach would of course also be great.
But in the end I'm entirely open for creative ideas, also ones which change the current code snippets fundamentally. I see those as an experimental feature (also say so on release notes).


Text styling in hero, 25/75, disclaimer.

Text in Hero, 25/75 organsim and disclaimer text in the email organsim isn't styled. Data & Research page preview is a good example.  @KimberlyMunoz @jimmynotjim @anselmbradford @sebworks

@tnferrell resolved it'll be fixed in the next refresh push

The hero looks fixed, but the 25/75 and disclaimer text still look off.

The spacing between link and text in the 25/75 also looks like it varies depending on how many 25/75 are stacked. You can compare /consumer-help and /data-research.

@jimmynotjim hey when you create a PR for the disclaimer text on Email Sign up could you link it here?

Thanks for the reminder, this fell off my radar. PR opened here https://github.com/cfpb/cfgov-refresh/pull/1231. It's more than just the small change, I updated everything to use our latest and greatest data prototyping and included it all in the landing page so we can actually see what's going on.

Hey guys, I'm still noticing something wonky on the 25/75 one of my pages - /consumer-help/managing-credit/

It looks like Wagtail is doing something funky with the markup output. @kave or @kurtw, any ideas?
This is the rendered markup:

And this is the source:

{{ value.body.source | safe }}

Not really sure why it's stripping the p tags in the markup and inserting it's own.

Looks like value.body.source is wrapped in a
 tag. Can't put
 inside of
 so the browser kicks them to the outside and leaves an empty paragraph with a new one below.

@jimmynotjim @anselmbradford yup thats exactly it. the fix would be:

{{value.body.source}}

There's no short-desc on this one, it should be the serif font, so we just need {{ value.body.source }}?

Yep. That should be it. File a quick fix PR to flapjack?

Crud, I commented on the wrong one. Too many nested p tags. This one does need the short-desc class name. I can update this if no one else already has.

These are fixed in code and will be updated after the next refresh push


Main component refactoring

Hi, I partially refactored only the thead part of the table, could you confirm me that the approach is ok so I can continue on the other parts of the component?
Thanks

@LexZhukov could you take a look please?

Thanks for your feedback, I will fix everything when I will update the PR with the full component refactored. I was mainly looking for a feedback on the approach, but I will consider it ok so far ;)
Thanks

@damnko, your approach looks good:)


Improve CI config

Currently, the Travis configuration file is quite barebones and only builds the library without actually testing/linting the library for some reason.
This changelist hopes to help to improve the configuration file to better leverage Travis' features.
Please look through the changes before merging the PR. (Please also delete this line when you merge this PR)
EDIT: The failed checks are caused by outstanding lint issues. I'll address this in a future PR.

Hi Edric, the build is failing. Are you still working on this?

I've temporarily abandoned the PR as there are way too many internal changes to make in order to fix the build. As such, I'll close this PR.


Do not rename generated code files

If a compiled SDFG binary is already loaded, DaCe checks and generates a different binary name. The generated code files would unfortunately also be renamed, which caused some confusion among users. This only renames the output binary file rather than the code. This also clarifies some potential discrepancies between sdfg.name and the generated code's compiled sdfg.name.

Not a small modification, creates other issues.


installation successful but normal discord shows up and nothin else (linux)

it shows that the installation was successful but when i open discord all the features are the same as normal discord

Duplicate of #96.


DescribeWorkflow timeout on wf with 1500 pending activities.

DescribeWorkflow timeout because it try to fetch scheduled event for each of the pending activity, only because it needs to show ActivityType for each pending activity.
See the code:
// TODO: move to mutable state instead of loading it from event
scheduledEvent, err := mutableState.GetActivityScheduledEvent(ctx, ai.ScheduledEventId)
This lead to timeout when the number of pending activity is large.

Thanks for reporting this issue.
This issue seems to stem from how you're loading the ActivityScheduledEvent.
I'm a bit unclear on your context here. Could you please tell me what the mutableState is? Is it the Workflow execution state?
Additionally, to better understand, could you share the following:

What version of Temporal are you using?
What is the ai.ScheduledEventId representing?

Once I have this information, I can provide a more accurate solution.

Thank you for reporting this issue. It seems that the Workflow is timing out because it's trying to fetch scheduled events for each pending activity to display ActivityType. This can lead to timeout when the number of pending activities is large.
To avoid this timeout, you can consider moving the fetching of the scheduled event to the mutable state instead of loading it from the event each time.  This will help optimize the Workflow performance.
You can also explore using techniques such as chunking or pagination to reduce the number of events fetched at once.
Please let me know if you have any other questions.


[FEATURE REQUEST] Expand/Collapse array in JSON response

Checklist

[x ] I've searched for similar feature requests.

Enhancement request
At present it is possible to expand/collapse an object in the JSON response, but not arrays.

Problem it solves
Allows better readability of large data sets with arrays.

Additional information, screenshots, or code examples

I have just realised that this actually works correctly for some response payloads. It seems the the cases where it works, are smaller payloads. For larger payloads some arrays and objects do not have the expand/collapse buttons.


Memory leak in esp_transport_ws_init (IDFGH-1312)

There's a memory leak in esp_transport_ws_init() in a failure case; spotted while skimming code:
https://github.com/espressif/esp-idf/blob/826ff7186ae07dc81e960a8ea09ebfc5304bfb3b/components/tcp_transport/transport_ws.c#L299
(ws is leaked if the strdup() fails).

Hi @viettrungluu
Thank you for reporting this memory leak, will be fixed!
Please keep this open so it could be closed automatically upon merging the fix, thanks again!


Make Critical CSS

It is necessary to create a critical CSS. It should be loaded in a header, be small.
Need to provide inline embedding critical CSS. This should include: reset styles, grid styles, common colors, header, header menu. Everything else needs to be connected to the footer. Including font styles. Fonts should be loaded asynchronously. To do this, it's need to make separate connection functions for different hooks. For example wp_enqueue_scripts and wp_footer
This Issue is important for PageSpeed

merged to develop


AdaptiveCardExtensionContext httpClient is not assignable to type @microsoft/sp-http HttpClient

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
[ Windows 10 Enterprise, iOS 14.8 ] Operating System
[ v14.18.1 ] Node version
[ 4.0.2 ] Gulp version
[ @1.13.0  ] SPFx Generator version
Describe the bug / error
The AdaptiveCardExtensionContext.httpClient is not assignable to a @microsoft/sp-http HttpClient type since upgrading from:
"@microsoft/sp-adaptive-card-extension-base": "1.13.0-beta.24",  ---->  "@microsoft/sp-adaptive-card-extension-base": "1.13.0",
"@microsoft/sp-core-library": "1.13.0-beta.24", ----> "@microsoft/sp-core-library": "1.13.0",
"@microsoft/sp-property-pane": "1.13.0-beta.24", ----> @microsoft/sp-property-pane": "1.13.0",

error message:
Type 'import("c:/Users/ajohnson/Repos/AAM/AAM%20%E2%80%93%20POWERhouse%20Intranet%20Modernization/apps/dashboard/node_modules/@microsoft/sp-property-pane/node_modules/@microsoft/sp-http/dist/index-internal").HttpClient' is not assignable to type 'import("c:/Users/ajohnson/Repos/AAM/AAM%20%E2%80%93%20POWERhouse%20Intranet%20Modernization/apps/dashboard/node_modules/@microsoft/sp-http/dist/index-internal").HttpClient'.
  Types have separate declarations of a private property '_fetchProvider'.

Steps to reproduce
Steps to reproduce:

Scaffold an ACE with 1.13.0 SPFx generator version

Attempt to assign AdaptiveCardExtensionContext.httpClient to HttpClient property

import { AdaptiveCardExtensionContext } from '@microsoft/sp-adaptive-card-extension-base';
import { HttpClient, IHttpClientOptions, HttpClientResponse } from '@microsoft/sp-http';

export class WeatherService {
    private LOG_SOURCE: string = "WeatherService";
    private _context: AdaptiveCardExtensionContext;
    private client: HttpClient;
    constructor(context: AdaptiveCardExtensionContext) {
        this._context = context;
        this.client = this._context.httpClient;
    }

Expected behavior
Expect to be able to use AdaptiveCardExtensionContext.httpClient with @microsoft/sp-http HttpClient.

Do you have a reference to the beta builds somewhere?

@Annie-Johnson can you try deleting your node_modules folder and then re-installing? It seems like your package manager has two different versions of @microsoft/sp-http installed and pulling from both, which is causing the type mismatch.
node_modules/@microsoft/sp-property-pane/node_modules/@microsoft/sp-http/dist/index-internal
node_modules/@microsoft/sp-http/dist/index-internal


AC® Chronicles [PCSE00700]

App summary

App name: AC® Chronicles
App serial: PCSE00700
App version: 1.00

Vita3K summary

Version: v0.1.5
Build number: 2697
Commit hash: https://github.com/vita3k/vita3k/commit/1becdabd
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game runs at full speed with minor graphics issues (regardless of the resolution).
Screenshots

Log
vita3k.log
Recommended labels

Playable
graphics bug

Game crashing on Mali g52 t618.

Black screen after boot. Samsung  SM-A426U

Tested on Snapdragon 8+ Gen 1 with Vita3k v.12.  Too bad it doesn't work, it's a great mobile/tablet game.

Not working on Android.Wants to play on Android therefore I request devloper to fix this on vita3k V13.main problem is it stucks on intro and then a black screen comes.


Chat box dropping below search results

After the most recent update the chat box is dropping down below the search results on particular output or reliably when input is entered that exceeds the width of the box. Example in the video below:
https://user-images.githubusercontent.com/199140/222948886-dfe03c39-1b42-42d0-9e3d-07c6f12e90f8.mp4

Fixed in v1.26.1
You could reproduce this issue in the old version by entering a long continuous string of text, such as fdcsjkofsjogkerjgoekrjghmboktremhboktrhmoiknbmfdoisgjhbnheriokjngbegergher, and you can try again in the new version, the issue will not occur.
Furthermore, I noticed from your video that the current question input box seems inconvenient for long questions. The updated question input box in the new version supports multiple lines display.

Awesome. That worked great! Thanks.


error in cloning fano-api

hi
first, thank for sharing this project :)
this issue is related to repo fano-api
In your read-me I can read a statement to clone fano-api repository
git clone git@github.com:fanoframework/fano-api.git --recursive
but this is the response
Cloning in 'fano-api'...
The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Unable to read remote repository.

Make sure you have the correct access privileges
and that the repository exists.

I solved using this statement
git clone https://github.com/fanoframework/fano-api.git --recursive
I tried git submodule update --init but submodule fano is impossible to clone to me (again error is: Make sure you have the correct access privileges and that the repository exists.).
So I downloaded by hand fano repo into subfolder.
Can you fix this step in doc please?

This is issue about ssh, not directly to fano-api repository.
If you want to use git clone with ssh, you need to setup public key as this is ssh protocol requirement. ssh does not care if it is private repository or public repository.
However I update fano-api repository and edit readme to avoid any confusion.


Added: Update oauth URL to restart oauth when token is unset

Reason for change

Currently, if we receive a 401 status from the API, an unhandled exception will be thrown, and users will have to refresh the page to obtain a new auth token.
With this change, a 401 will cause the token to be refreshed, and the API call will retry.
Testing

Testing is tricky because tokens take a while to expire. You might want to watch this video where @domenicrosati demonstrates this working with fast-expiring tokens.
Checklist

[x] CHANGELOG: The Unreleased section of CHANGELOG was updated
[ ] Prop changes: docs were updated
[ ] Prop changes: E2E tests were updated, testing from the highest level possible

@dangodev I switched the oauthUrl prop back to being optional and added some tests.


Wrong typings for React Hooks

Describe the bug
baseOptions: ReactApolloHooks.QueryHookOptions<PersonQueryVariable> (described bellow) has wrong type parameters. Intellisense shows that the first parameter for QueryHookOptions is TData and the second one is TVariables
Obviously, the first parameter should be the query type:
baseOptions: ReactApolloHooks.QueryHookOptions<PersonQuery, PersonQueryVariables>

Reproduce:
Given a query:
query person($handle: String!){
  person(handle: $handle){
    name
  }
}

The following types are generated:
export type Person = {
  name: Scalars['String']
}

export type PersonQueryVariables = {
  handle: Scalars['String']
};

export type PersonQuery = ({ __typename?: 'Query' } & { person: Maybe<({ __typename?: 'Person' } & Pick<Person, 'name'>)> });

export const PersonDocument = gql`
  query person($handle: String!) {
    person(handle: $handle) {
      name
    }
  }
`;

export function usePersonQuery(
  baseOptions?: ReactApolloHooks.QueryHookOptions<PersonQueryVariables>
) {
  return ReactApolloHooks.useQuery<PersonQuery, PersonQueryVariables>(PersonDocument, baseOptions);
}

Intellisense shows an incompatible types error, because it assumes baseOptions is of type
ReactApolloHooks.QueryHookOptions<PersonQueryVariables, Record<string, any>>

because the first type parameter is omitted in the generated code.
Expected behavior
The generated code should type baseOptions correctly (as mentioned above)
Environment:

OS: W10

"@graphql-codegen/cli": "^1.9.1",
"@graphql-codegen/typescript": "^1.0.0",
"@graphql-codegen/typescript-operations": "^1.0.0",
"@graphql-codegen/typescript-react-apollo": "^1.0.0"

NodeJS: v11.13.0

codegen.yml:
overwrite: true
schema: "http://localhost:4000/graphql"
documents: "graphql/**/*.ts"
generates:
  lib/apolloComponents.ts:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-apollo"
    config:
      withHooks: true
      withHOC: false
      withComponent: false
      hooksImportFrom: "@apollo/react-hooks"

@ardatan can you please take a look?

@judehunter You might be using the old version for plugins.
Could you update all of them @graphql-codegen/* to the latest 1.10.0 without ^?