Change wording from Data to Dataverse

[Enter feedback here]
Under section Set up the custom connector in item number 1. change wording of Data > Custom Connectors to Dataverse > Custom Connectors
Also Item 5 please change Client secret to Client secret Value. The client secret has an ID and a Value so for clarity the instruction needs to be more specific.

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

ID: 1855a9ee-8713-c8e6-2091-bc972f877c13
Version Independent ID: c87a0108-4de6-49df-8ba3-3bdb06216ad8
Content: Set up audit log components - Power Platform
Content Source: power-platform/guidance/coe/setup-auditlog.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Fixed locally ready for our next update. Thank you, looks like the Product UI has changed here to call this Dataverse now :)

Updated with latest release, thanks for the feedback!


Migration directory error when using Custom Migration Source

Environment
Knex version: 0.21.1
Database + version: sqlite3
OS: Windows 10
Bug
Description
I'm using Custom Migration Source
class MigrationSource {
  getMigrations = () => this.migrations.map((x, i) => i)
  getMigrationName = i => i
  getMigration = i => this.migrations[i]
  migrations = [{
    async up(knex) {},
    async down(knex) {},
  }]
}

The migrations are specified within the source itself, i.e. no need to look for a migration directory.
It works fine on the first run.
But subsequently it gives the following error:
Error message
Error: The migration directory is corrupt, the following files are missing: 0
    at validateMigrationList (...\node_modules\knex\lib\migrate\Migrator.js:556:11)
    at ...\node_modules\knex\lib\migrate\Migrator.js:62:11

It's looking for a migration directory...
Reduced test code
Run the following code twice. Works the first time but gives the above error on second run:
const Knex = require('knex');

const knex = Knex({
  client: 'sqlite3',
  connection: { filename: 'database.db' }
});

class MigrationSource {
  getMigrations = () => this.migrations.map((x, i) => i)
  getMigrationName = i => i
  getMigration = i => this.migrations[i]
  migrations = [{
    async up(knex) {
      if (!await knex.schema.hasTable('user'))
        await knex.schema.createTable('user', t => {
          t.string('username').unique();
        });
    },
    down: knex => knex.schema.dropTableIfExists('user')
  }]
}

knex.migrate.latest({ migrationSource: new MigrationSource() });

Ah, my bad. User error.
class MigrationSource {
-  getMigrations = () => this.migrations.map((x, i) => i)
+  getMigrations = () => this.migrations.map((x, i) => String(i))

That fixed it.


Installation not working

I am trying to install this package as:
pip install --no-cache-dir -U https://aws-s3-plugin.s3.us-west-2.amazonaws.com/binaries/0.0.1/1c3e69e/awsio-0.0.1-cp38-cp38-manylinux1_x86_64.whl
(Grabbed the wheel location from the docker file)
And when I run the test:
bash tests/smoke_tests/import_awsio.sh
I see the following error:
from awsio._version import version
ModuleNotFoundError: No module named 'awsio._version'

which platform are you running it on? Can you provide more details?

I am trying to install it on an ec2 instance. May be there are more prereqs needed?

I recommend using following containers for no-hassle use. You can "docker pull" any of the following container, log into it and start using the plugin directly
763104351884.dkr.ecr.us-west-2.amazonaws.com/pytorch-training:1.9.0-cpu-py38-ubuntu20.04-v1.1
763104351884.dkr.ecr.us-west-2.amazonaws.com/pytorch-training:1.9.0-gpu-py38-cu111-ubuntu20.04-v1.1
763104351884.dkr.ecr.us-west-2.amazonaws.com/pytorch-training:1.8.1-cpu-py36-ubuntu18.04-v1.6
763104351884.dkr.ecr.us-west-2.amazonaws.com/pytorch-training:1.8.1-gpu-py36-cu111-ubuntu18.04-v1.7

@sravya8
Try cd tests/smoke_tests/, then run bash import_awsio.sh
I got the error as well when running in the project root dir, and python imports the local awsio/ package directly instead of the one you installed previously.

@Roshrini Do you have any timeline on when the wheel would be released?

Hi all, , I've updated the installation guide for the plugin: https://github.com/aws/amazon-s3-plugin-for-pytorch#installation
However, we're deprecating support for the S3 plugin, and I suggest to try the new torchdata S3 IO datapipes. The S3 IO is upstreamed into torchdata package. We're supporting the new torchdata package, and continuously improving user experience and performance of the S3 IO datapipes.


update contrib/gofpdi from v1.0.3 to v1.0.7

Updates contrib/gofpdi from v1.0.3 to v1.0.7

imports pdf documents from any io.ReadSeeker
exposes page sizes of imported pdf documents

@phpdave11 Thanks again for your quick release. I hope this PR meets with your approval.

Thanks, @mrtsbt!


Bump actions/upload-artifact & actions/download-artifact from 3 to 4

Supersedes #2640  & #2641, the bump has to be done in one go.
This is just a squashed commit with the contents of both aforementioned PRs.

Before merging this, we should pay attention if it won't break our test reports, as dorny/test-reporter seems to still rely on the incompatible<EMAIL_ADDRESS>

So this seems to have been fixed in https://github.com/dorny/test-reporter/releases/tag/v1.9.1 (although I'm not exactly sure why), as per https://github.com/dorny/test-reporter/issues/363#issuecomment-2381625959.
Test reports run successfully, which is good enough for me.


Some Fixes for HTTP. V2

Changes since v2:

Dropped commit "Sol-HTTP-Client: Username and password should be encoded.", since Curl already encodes the username and password.
Added a FBP test for commit 0740590
Added a TODO at commit 0740590 , since we're not if SOL_HTTP_PARAM_FRAGMENT should be considered a sol_http_param_type.
set_cookies_from_params() no longers steals encoded buffer data.

Merged with the fixes.


Ensure that re-authenticating on mobile devices is not required

We have received a fair amount of feedback around the need to re-authenticate on mobile devices. Most people seem to expect that re-authentication on a mobile device should not be required. Therefore, we should be using cookies with a longer expiration (30 days to start off with?) on mobile devices.

Assigning to @mrvisser for fix

Addressed in https://github.com/oaeproject/Hilary/pull/1135


Removed unnecessary initialisation of camunda config arrays.

This causes skipping of default camunda initialization like batchHandlers (migration etc)  #196

Thanks Ron ... I am a bit afraid to remove the init() completely, thats why I created #198 to replace it. After implementing this, I suppose the PR won't be fully required anymore. I will come back to you!

I adopted your changes, but kept an init method that sets all the custom lists because I do not want to null check everytime I add a custom value. see #227


Add a Stack Overflow link option

Unfortunately, the icon isn't squared like the others, but maybe this is better than nothing?
See https://github.com/FortAwesome/Font-Awesome/issues/3190 for the square icon request.

Thanks!


Unable to edit LinuxServer config when pulling the latest version (v0.15.1) by palworld.

Describe the bug
Use "docker-compose pull" to get the latest version, but starting the server always resets the LinuxServer/PalWorldSettings.ini.
To Reproduce
Steps to reproduce the behavior:

docker-compose down
edit LinuxServer/PalWorldSettings.ini
docker-compose up -d

Expected behavior
Linux server/PalWorldSettings.ini will not be reset
Actual behavior
Linux server/PalWorldSettings.ini has been reset
OS information

OS:
Palworld Version:
Docker Image Version:
Ubuntu 22.04.3 LTS
Docker version 25.0.1
Palworld Version: 0.15.1

Hardware information
8 core 32G
docker-compose.yml contents
services:
   palworld:
      image: thijsvanloef/palworld-server-docker:latest
      restart: unless-stopped
      container_name: palworld-server
      ports:
        - 8211:8211/udp
        - 27015:27015/udp
      environment:
         - PUID=1000
         - PGID=1000
         - PORT=8211 # Optional but recommended
         - PLAYERS=16 # Optional but recommended
         - SERVER_PASSWORD="mainloadpw" # Optional but recommended
         - MULTITHREADING=true
         - RCON_ENABLED=true
         - RCON_PORT=25575
         - TZ=UTC
         - ADMIN_PASSWORD="mainloadpassword^."
         - COMMUNITY=true  # Enable this if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD!
         - SERVER_NAME="MainLoad_China_Server"
      volumes:
         - ./palworld:/palworld/

Container/Host Logs
****EXECUTING USERMOD****
usermod: no changes
****Checking for new update****
Current Version:<PHONE_NUMBER>637542021
The Server is up to date!
****GENERATING CONFIG****
Using Env vars to create PalWorldSettings.ini
****Compiling PalWorldSettings.ini****
Compiling PalWorldSettings.ini done!
****GENERATING CRONTAB****
BACKUP_ENABLED=true
Adding cronjob for auto backups
Cronjobs started
****Starting Server****
./PalServer.sh -queryport=27015
time="2024-03-04T06:04:54Z" level=info msg="read crontab: /home/steam/server/crontab"
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
Shutdown handler: initalize.
Increasing per-process limit of core file size to infinity.
- Existing per-process limit (soft=18446744073709551615, hard=18446744073709551615) is enough for us (need only<PHONE_NUMBER>3709551615)
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Setting breakpad minidump AppID = 2394010
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
Waiting for RCON port to open to show player logging...
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password
cli: password is not set: to set password add -p password

Additional context

Hi @zyknow please use server Password and admin password and Server Name without the quotations if you are using KEY=VALUE.
You can use quotations but you have to use the new way of setting variables as shown in the docker-compose.yml https://github.com/thijsvanloef/palworld-server-docker/blob/main/docker-compose.yml

Also in regards to the settings being reset, if you want to change the palworldsettings.ini manually you would have to set DISABLE_GENERATE_SETTINGS=true or configure the server with environment variables: https://palworld-server-docker.loef.dev/getting-started/configuration/game-settings


feature/5624 add preview for 2 links

Description

This PR implements preview for the two following links:

Statistics info, FAQ (AppStrings.Statistics.Info.faqLink)
Info for risk card with low-risk encounters, FAQ (AppStrings.Home.riskEncounterLowFAQLink)

The link preview feature was requested at #2179.
Also I did a small cleanup in the ExposureDetectionViewModel.
This function explanationSection is never called with a positive numberOfExposures;
so I could remove the parameter and the related code.
Note: PR #3877 covers mocking of the links during unit tests. I recommend to merge #3877 before this PR.
Note 2: Originally I had planned to cover also the FAQ at Error reports (AppStrings.ErrorReport.faqURL); but the accessibility identifier did not work as expected, and the robots caught it.
Link to Jira

Jira: Internal Tracking ID: EXPOSUREAPP-5624
github: #2179
Screenshots

@marcussc @pascal-brause
Well ... actually I was looking for an execution path to that code, because I wanted to test the behaviour of the link ...
but I couldn't find one; so I concluded that it is dead code (maybe forgotten to cleanup after a refactoring ... ).
But of course, I may be wrong.
And even if not: if you want to keep this code, e.g. for future use, I don't insist to delete it, I can bring it back.
Still I would like to understand it ... I still don't see the execution path ...
There are two functions explanationSection(...) in this class, and both functions are private - so we can limit our analysis to this class, right?
This one is called from the inactiveModel and from the failureModel and both don't have a parameter numberOfExposures, so they get the default value -1 and don't hit that condition.
The lowRiskModel has such a parameter, but it calls the other function.
And the highRiskModel calls a separate function highRiskExplanationSection.


Set debugState for tests

Is your feature request related to a problem? Please describe.
During tests I need some certain state in order to test other methods logic. Since I often have an initialisation method that sets the state.
For that reason, currently I have to mock the initialisation logic first (prepare the state) in order to test my other method. At some places that is super cumbersome.
Describe the solution you'd like
We currently have access to the getter debugState. Can we also have a setter like setDebugState that wraps the setter state under the hood but that is not marked as protected?
It's a quick solution that would work. I'm open for other suggestions and happy to contribute in any way.
Additional context

Sounds reasonable. It's a low priority for me though. Fancy making a PR?

Awesome! Yes, for sure. I'll be opening the PR anytime this week

Notifier.state is now @visibleForTesting – both the getter and setter.


Feat/msdk 612 quit unilaterally portfolio custodian

:tada: This PR is included in version 7.0.0-alpha.7 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Card group] Style bugs in Web components

Web Components – With Card in card story – grid mode narrow (16px):

There is a right border for the first 2 cards that is applied to the dds-card-group-item which has padding instead of margin so the border is applied to the padding spacing also.

Web Components – With Card in card story – the collapsed grid has some spacing errors

The same errors from 2 and 3 are visible for the With Card in card and Image cards story

Shixie and Dragos will break out the style issues (Sev 3) and the storybook issues (Sev 4).

2 additional items. Card in card is missing border when grid mode is set to border, and card in card is seperated from card group in storybook causing issues where one can have narrow, and the other broder grid modes for example. I think it might also be creating some of the spacing issues we see above.

Looking through this issue trying to break it down, and I think some of here might be not bugs.
React version of this component is behind web components. Some issues are tracked but not all:

with Card in card variant https://app.zenhub.com/workspaces/carbon-for-ibmcom-5d449f3642eb1962336cbe52/issues/carbon-design-system/carbon-for-ibm-dotcom/5339
with mixed media variant

I made an edit to the description above to focus the issue on Card group web components style bugs
New issue for Web components storybook knob changes: #6338

Hi @BrunnoM7
I re-QAed it again, and I just see this one now for Card group – With card in card and image cards story. When I switch to the collapsed grid, there is no top border for the cards – its image touching image. Also, when I switch back to a narrow grid, the 16px top spacing is not there. I don't know if this second one is a Storybook bug, or a component bug, because the default story has a narrow grid. Here's what I see:
https://images.zenhubusercontent.com/193129061/dff6be3e-fae5-4bb1-bb22-bbdbcb6d8df3/card_group_with_card_in_card_and_image_cards.mov

Having reviewed the production version of this component's With card in card and With card in card and image cards variants, it appears these layout issues have been resolved. If these issues resurface, potential fixes can be found in #7409.
cc: @emyarod @jeffchew


[BUG] Contact Us form has missing minimum height

Description
The Contact Us form does not have a minimum height and it looks ugly when it is reduced . A minimum height should be given to the input box.
Screenshots
Before:

It will look like this:

Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@rohansx @k-deepak04 Please assign me this issue under GSSoC 23

@JAYESHBATRA go for it


mature -> sensitive code changes for the API

Fixes

Fixes #3723 by @AetherUnbound
Description

This PR applies the code changes for the API necessary to use sensitive internally rather than mature. Per the implementation plan linked in #3723, the mature property on the serializer and the mature property of Elasticsearch hits are unaffected.
This PR requires 2 migrations in order to appease Django. Both are no-ops:

Make explicit the tables which the mature media records are using
Rename the models and fields from mature to sensitive

Below are the sqlmigrate outputs for each migration:
j api/dj sqlmigrate api 0055

BEGIN;
--
-- Rename table for matureaudio to api_matureaudio
--
-- (no-op)
--
-- Rename table for matureimage to api_matureimage
--
-- (no-op)
COMMIT;

j api/dj sqlmigrate api 0056

BEGIN;
--
-- Rename model MatureImage to SensitiveImage
--
-- (no-op)
--
-- Rename model MatureAudio to SensitiveAudio
--
-- (no-op)
--
-- Alter field media_obj on sensitiveaudio
--
-- (no-op)
--
-- Alter field media_obj on sensitiveimage
--
-- (no-op)
COMMIT;

Warning:
I am no DRF aficionado, so I'm really not sure if everything I've done here is idiomatic or makes sense! Please let me know if there's a better approach to tackling this issue 😄

Testing Instructions

Tests should pass, and all routes should also work locally!
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@obulat I tested that result on main and it also shows no value for unstable__sensitivity. I'll look into why that's the case, but given that it's on main I don't think it should block this PR!

Ah, right! It's because we use a mock sensitive terms list: https://github.com/WordPress/openverse/blob/7427bbd4a8178d05a27e6fef07d70905ec7ef16b/ingestion_server/ingestion_server/static/mock_sensitive_terms.txt

we use a mock sensitive terms list: 7427bbd/ingestion_server/ingestion_server/static/mock_sensitive_terms.txt

Does that means that items with those terms should be marked as sensitive? I searched for them but I couldn't find any. How can we check for an item where "mature": true?

I'm not sure! I believe it's separate from the work on this PR though; @krysal or @obulat would either of you be willing to look into it this week to see if/how that mock list is being used?

Does that means that items with those terms should be marked as sensitive? I searched for them but I couldn't find any.

Yes, anything with those terms locally will get marked with having sensitive text. Compare the following two requests:
http://<IP_ADDRESS>:50280/v1/images/?q=water&unstable__include_sensitive_results=True
http://<IP_ADDRESS>:50280/v1/images/?q=water
All results with water are marked sensitive text with correctly populated sensitivity list.

How can we check for an item where "mature": true?

None of these exist in the testing data. That's why the one @obulat brought up isn't matched, it has none of the mock terms, and isn't marked mature in the index.
To test for mature: true locally, you need to add a confirmed sensitivity report via your local Django admin. Go to http://localhost:50280/admin/api/imagereport/add/?reason=mature&status=mature_filtered and select a media object to mark as "mature" (just choose any one of them you want) and save the report. Then you'll have one result with mature: true in the index.

No special considerations here! It will run the two no-op migrations on deployment, but nothing about the application itself should change 😄

Going to merge and make sure it works in staging!


Are there any plans to support zookeeper?

Thank you. We are counting on it.

Hi, @ngaut,
Actually, we removed whatever limited support we had for a Zookeeper store in commit https://github.com/cloudfoundry/storeadapter/commit/f1d94be678bf9e61bd4d2cdf22dae4acd4417da5 over a year ago. We don't currently have plans to restore that functionality. Could you explain more about your use case for it?
Thanks,
Eric, for the CF Runtime Diego team

Hi, @ematpl
We need to support zookeeper and etcd. So I build a simple adaptor a few days ago. I do not need it now. Thanks anyway


netdata: 1.31.0 -> 1.32.1

Motivation for this change
Update netdata:

netdata: go.d.plugin: 0.28.1 -> 0.31.0
netdata: 1.31.0 -> 1.32.1

cc @Mic92 @TilCreator
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Could this be backported?

Backports are now created by a bot, I don't know how to start it.

ah indeed - I just created https://github.com/NixOS/nixpkgs/pull/154164 but maybe it just needs labeling "backport" or so

added the label, let's see what happens


update rspirv 0.11 to 0.12

The rspirv update is required to get the spirv symbols required for mesh shaders, which will be added in a separate PR.
Original mesh shader PR: https://github.com/EmbarkStudios/rust-gpu/pull/1019

While porting, I've noticed that rustc_codegen_spirv::spirv_type_constraints::instruction_signatures(Op) somehow seems to validate a lot of SPIR-V Ops on their input and output types, and that spirv/grammar/autogen_table.rs seems to also contain a giant List of auto-generated instructions with all their inputs and outputs. Maybe something could be simplified there?

Basically ready to merge, apart from LiteralFloat still being a todo!. If it's essentially unused, should it just be replaced with some kind of error message, and done with it?

@Firestar99 #1127 just landed, you'll need to rebase (but I should be able to review concurrently).


[Testing] Add a simple test of a service from Docker

Defining a test using testcontainers, docker.
In this example using MockServer.
But ideally able to put in tests against a Socks Proxy, or SSL server.

Somewhat a fork of https://github.com/square/okhttp/pull/7645/files

@swankjesse requesting post review. CI only and would like to have to test issues on bugs like SOCKS support.


Indri index

I couldn't find out how to build indri index. Could you tell me more about this? Thank you!

Indri can be built using the IndriBuildIndex command. More information about Indri building can be found here: https://sourceforge.net/p/lemur/wiki/IndriBuildIndex Parameters/

Indri can be built using the IndriBuildIndex command. More information about Indri building can be found here: https://sourceforge.net/p/lemur/wiki/IndriBuildIndex Parameters/

OK, I got it, thanks for your help!


Missing some selectors on Vyper 0.3.10 contracts

In these curve contracts, not all methods have been found:

https://etherscan.io/address/0xef484de8C07B6e2d732A92B5F78e81B38f99f95E#code
https://etherscan.io/address/0x9e10f9Fb6F0D32B350CEe2618662243d4f24C64a#code

Tried with:
cast selectors $(cast code 0xef484de8C07B6e2d732A92B5F78e81B38f99f95E) --resolve

0x081579a5	uint256,int128,uint256,uint256       	remove_liquidity_one_coin(uint256,int128,uint256,address)
0x0b4c7e4d	                                     	add_liquidity(uint256[2],uint256)
0x18160ddd	                                     	totalSupply()
0x1be913a5	                                     	ma_exp_time()
0x23b872dd	uint256,uint256,uint256              	transferFrom(address,address,uint256)
0x30c54085	                                     	withdraw_admin_fees()
0x3644e515	                                     	DOMAIN_SEPARATOR()
0x52d2cfdd	uint256,uint256,uint256,uint256      	remove_liquidity_imbalance(uint256[2],uint256,address)
0xb4b577ad	                                     	future_A()
0xddc1f59d	int128,int128,uint256,uint256,uint256	exchange(int128,int128,uint256,uint256,address)

The ABI shows 68 methods (read + write)

Confirmed.
In this contract execution flow depends on CALLDATA AND_OPERATOR CONSTANT.
I need time to investigate and think about possible fixes.

Fixed in master, will be in the next release.
Vyper does signature % n_buckets, but sometimes it's optimized(?) to signature AND (n_buckets-1) (with different bucket content of course). Now it's supported.

That's awesome, great work! Closing this issue then :)

Fixed in v0.3.8 release - https://cdump.github.io/evmole/#0xef484de8C07B6e2d732A92B5F78e81B38f99f95E/eth (Ctrl+F5)


Rainloop doesn't use application.ini after some time and looks default

RainLoop version, browser, OS:
<IP_ADDRESS>]
Expected behavior and actual behavior:
When php-fpm restart - all ok., but after some time rainloop login page opened with default theme and doesnt use application.ini
even restart php-fpm all ok again, and when enter admin and change settings application.ini saves.
Sometime need hour, sometime day, sometime 5 minuts to this stuck.
Im try to changes rules of nginx and other, update php, change php-fpm config, but this issue come again.
Logs or screenshots:
[10:02:23.015][cf710b80] INFO[DATA]: [DATE:15.12.16][OFFSET:-00][RL:<IP_ADDRESS>][PHP:5.6.28][IP:*****][PID:29028][nginx/1.11.7][fpm-fcgi]
[10:02:23.015][cf710b80] INFO[DATA]: [Suhosin:on][APC:on][MB:on][PDO:mysql,sqlite][Streams:tcp,udp,unix,udg,ssl,sslv3,sslv2,tls,tlsv1.0,tlsv1.1,tlsv1.2]
[10:02:23.016][cf710b80] INFO[NOTICE]: exception 'RainLoop\Exceptions\ClientException' with message 'InvalidToken[101]' in /public_html/rainloop/v/<IP_ADDRESS>/app/libraries/RainLoop/ServiceActions.php:133
Stack trace:
#0 [internal function]: RainLoop\ServiceActions->ServiceAjax('')
#1 public_html/rainloop/v/<IP_ADDRESS>/app/libraries/RainLoop/Service.php(146): call_user_func(Array, '')
#2 public_html/rainloop/v/<IP_ADDRESS>/app/libraries/RainLoop/Service.php(56): RainLoop\Service->localHandle()
#3 /public_html/rainloop/v/<IP_ADDRESS>/app/libraries/RainLoop/Service.php(79): RainLoop\Service->__construct()
#4 public_html/rainloop/v/<IP_ADDRESS>/app/handle.php(94): RainLoop\Service::Handle()
#5 public_html/rainloop/v/<IP_ADDRESS>/include.php(225): include('/home/webmail/w...')
#6 public_html/index.php(13): include('/home/webmail/w...')
#7 {main}{"Action":"FolderInformation","Result":false,"ErrorCode":101,"ErrorMessage":"","ErrorMessageAdditional":"","Time":13}

Reference: https://github.com/RainLoop/rainloop-webmail/issues/1509
Commit: https://github.com/RainLoop/rainloop-webmail/commit/f695a1acd2359cc2e94846b828265e9b11fdd402


Docker Developer Environments experience

Tell us about your request
Provide a simple way for developers to share their work in progress code, connect code into a container to edit it/rebuild it and a way to do this within a compose project using one container as my development environment while still running the others.
Keep my development container backed up, up to date and provide simple tools to share these with my team so anyone can look at what I am working on in one click
Which service(s) is this request for?
Docker Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Making it simple to move between versions of the same code and to develop a containerized application on my local machine. Allow me easily share code in containers with my team mates.
Are you currently working around the issue?
Sharing branches which requires git magic on my machine to move between them
Additional context

 👀

I am very much looking forward to JetBrains (PyCharm/GoLand/IntelliJ/WebStorm) integration for this.

Hi Greate Feature,
I really want to share with all my Developrts team, But we all cli linux users so with (Jebrain Ultimate, use most of the IDE's).
We will be more then happy to have this feature support in CLI and Jetbrain environments

Throwing in my vote for IntelliJ support.

While you wait for IntelliJ to get on the devcontainer bandwagon, for a more IDE-agnostic bootup of dev containers check out this neat project:
https://github.com/nikaro/devc
It's a CLI to start a devcontainer without an IDE and supports most of the devcontainer.json spec.

I know the dev containers project has broad goals, but since this appears to solicit feedback:

Upfront: this setup works okay for development IF your workload is more-or-less the "hub and spoke" kind--where there is one main code base in the service tier and smaller services "behind" in its orbit... Maybe the "main" code base is an existing monolith that you are [or aren't] decomposing, OR maybe: you have NO monolith, and "main" is just your focus. i.e. "main" project = code YOU work on in a "leave one out" strategy--where other services change less often than your focus, and can run the whole system based upon tagged mainline images in some kind of registry, which you do in prod anyway.

Provided you've got and editor or IDE where you do most of your development, that can drive the main focus outside a container and interact via mapped ports on localhost with the "satellite" services and DBs, etc.
In most places I've worked we do this:

if you're outside the k8s ecosystem, just write one or more docker-compose.yml files
spec your data tier and other stuff like SQL servers, Redis, or whatever ^^^ in here
persist data in volumes, which optionally map to the host: ./data/redis:/data:rw
run your actual services with env/net or w/e configured in the compose file(s)
provide a Makefile with targets for developers, which spin everything up/down
if part of your workflow is to seed schema or data into DBs, add a target
you can also fit this around k8s (e.g. via minikube) or transition later
the Makefile just maintains stable targets, e.g. clean, dev, sane, stop

It has the following drawbacks:

this doesn't scale to large teams or projects of a certain scope (one main focus)
developers need some operational awareness, or find CLIs or an IDE/GUIs that help them
compose can have wonky interaction with AWS ECR and other registries (has various solutions)
specifically, compose does not auto-pull; to restart everything w/ mainline satellites in orbit:

# You can create a Makefile target to run the commands in this order.
docker-compose stop # to bring down the local stack before cleanup
docker-compose rm -f
docker-compose pull # or, write a script to docker login (then pull)
docker-compose up -d
# Provided everything came up sanely, you've got latest mainline.

That's a summary of my experience, plus some warnings and advice re: growing pains FWIW.

Sorry if my last comment was long and boring. That's just how I've coped over the years w/o more turn-key support for this in Desktop. The spec sounds like it'll help folks on many projects, and I guess what I'm also interested to hear is: how will the new features integrate with compose, if at all?

In most places I've worked we do this:

if you're outside the k8s ecosystem, just write one or more docker-compose.yml files
spec your data tier and other stuff like SQL servers, Redis, or whatever ^^^ in here
persist data in volumes, which optionally map to the host: ./data/redis:/data:rw
run your actual services with env/net or w/e configured in the compose file(s)
provide a Makefile with targets for developers, which spin everything up/down
if part of your workflow is to seed schema or data into DBs, add a target
you can also fit this around k8s (e.g. via minikube) or transition later
the Makefile just maintains stable targets, e.g. clean, dev, sane, stop

This is almost exactly what I have also ended up doing. The result is that this works great for cmd-line, (but also needs a lot of knowledge transfer to any new joinee on the tooling + process involved). The drawback,  as stated above, is that this completely forgets about the IDE-based experience.

Tip: if they're using Jetbrains IDEs, you can create .run configs for the make targets, etc.
@vraravam: That way, some can point and click or "fork" the supported versions that you git-commit.

As noted by others above, this is almost frictionless using Docker Compose with PyCharm atm. (shameless plug) I wrote a walkthrough for setting this up:

https://baumannalexj.medium.com/how-to-use-pycharm-to-remotely-debug-your-flask-app-running-in-docker-c66eb9b8aa72

I wouldn’t mind an option to have all my dev tools in a container that could join a dev environment when I need to work on it.

In case anyone mentioning JetBrains IDEs in here hasn't seen it yet: https://www.jetbrains.com/remote-development/

Can only start 1 container on Windows Docker Desktop dev environment?

Hi Docker Team,
Just checking in on the docker dev environment feature, is it going to be deprecated?
Recently found that your documentation states that it is no longer under active development while still stuck in beta status for docker dev environments.
Ref: https://docs.docker.com/desktop/dev-environments/

Important
Dev Environments is no longer under active development.
While the current functionality remains available, it may take us longer to respond to support requests.

Beta
The Dev Environments feature is currently in Beta.

Also noticed PRs for the removal of docker dev environment references:

https://github.com/docker/awesome-compose/pull/488
https://github.com/docker/docs/pull/20083

Sample apps with Compose
The following samples show the various aspects of how to work with Docker
Compose. As a prerequisite, be sure to install Docker Compose
if you have not already done so.
Key concepts these samples cover
The samples should help you to:

define services based on Docker images using
Compose files docker-compose.yml files
understand the relationship between docker-compose.yml and
Dockerfiles
learn how to make calls to your application services from Compose files

Samples tailored to demo Compose
These samples focus specifically on Docker Compose:

Quickstart: Compose and Django - Shows how to use Docker Compose to set up and run a simple Django/PostgreSQL app.

Quickstart: Compose and Rails - Shows how to use
Docker-compose  to set up and run a Rails/PostgreSQL app.

Quickstart: Compose and WordPress - Shows how to
use Docker Compose to set up and run WordPress in an isolated environment
with Docker containers.

v22.2.2
command:v22.2.2
- [ ] Sample apps with Compose

The following samples show the various aspects of how to work with Docker
Compose. As a prerequisite, be sure to install Docker Compose
if you have not already done so.
Key concepts these samples cover
The samples should help you to:

define services based on Docker images using
Compose files docker-compose.yml files
understand the relationship between docker-compose.yml and
Dockerfiles
learn how to make calls to your application services from Compose files

Samples tailored to demo Compose
These samples focus specifically on Docker Compose:

Quickstart: Compose and Django - Shows how to use Docker Compose to set up and run a simple Django/PostgreSQL app.

Quickstart: Compose and Rails - Shows how to use
Docker-compose  to set up and run a Rails/PostgreSQL app.

Quickstart: Compose and WordPress - Shows how to
use Docker Compose to set up and run WordPress in an isolated environment
with Docker containers.


Added new installer script targeted at interactive users

This installer script, install.sh is intended for use by interactive users of Waldo CLI only. The older installer script, install-waldo.sh, is unchanged and is intended for use in a CI environment.

I shall attempt to incorporate all the above feedback before I merge. Thank you all!


beakerVendor.js is large enough to cause significant slowdown when using Beaker over the internet.

It's currently at about 10MB, and it contains, among other things, Angular, so it would be difficult to render anything meaningful until it's fully downloaded.
The majority of the file appears to consist of some sort of base64 encoded binary content (sourcemaps, or something along those lines?)

Ok, I think that we can put a pretty simple fix in for this. As you stated, the end of the file looks like binary content, that content is the inline source-maps for our JS. For the normal build of beaker we should be able to use external sourcemaps which will only be downloaded if someone opens dev tools.
This should trim us down quite a bit.
thoughts @spot ?

an external source map sounds good, yes please.


ARTEMIS-3198 - Fix order of concurrency parameter...

...in schema file so it matches documentation

I would suggest rather than changing the order which will break existing installs the docs are simply updated.

It is not released yet, just sent that PR a few days back

This has not been released yet.  What is the issue ?

@clebertsuconic there is no issue if it hasnt been released yet. As i said, disregard my comment if it hasn't.

I'm completely lost on what was the issue Michael. I'm on the iPhone. I will review this later :)

I even thought this was the original PR. So disregard anything I said also.

LGTM tbh.


[release-1.22] Bump runc to v1.1.4

Proposed Changes
Bump runc to v1.1.4
Types of Changes
version bump / bugfix
Verification
See linked issue
Testing
n/a
Linked Issues

https://github.com/k3s-io/k3s/issues/6077

User-Facing Change

The bundled version of runc has been bumped to v1.1.4

Further Comments

Codecov Report

Merging #6074 (c722ae0) into release-1.22 (3daf4ed) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release-1.22   #6074   +/-   ##
============================================
  Coverage          9.58%   9.58%
============================================
  Files               136     136
  Lines              9936    9936
============================================
  Hits                952     952
  Misses             8786    8786
  Partials            198     198

Flag
Coverage Δ

unittests
9.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


more config stuff

Moves config commands to !config, and adds add and remove commands for dealing with arrays (eg. in the greetings module)

!config get <module> <option> -> shows value
!config get <module> -> shows all options for a module
!config set <module> <option> -> set option
!config add <module> <...values> -> push values to a list
!config remove <module> <...values> -> remove values from a list

Example:

!config add greetings greetings "Weoooow hiiiii @!" "@, You're my favourite person in the whole wide world <3"
!config remove greetings emoji :heart:

Todo: maybe make !config set take types into account, so if you do !config set module option lol and module.option is an array, it sets it to [ "lol" ] instead of "lol".

is the intent if you wanted to directly set a config option? instead of doing !module set foo

Currently the config commands are !set module foo value and !get module foo, I mostly moved those to !config get/set module foo [?value] because !add and !remove could be better used as future Waitlist add/removal commands. (plain !get/set still works, though)

mergeth?


[GH-144] Fix Control-C issue, first version.

https://github.com/input-output-hk/cardano-shell/issues/144
Working first version.

You actually don't need to orun the scripts/nix-tools-generate.sh script. You can push to CI, the stack2nix build will fail but also provide you with a patch.

Updated this in https://github.com/input-output-hk/cardano-ledger/pull/487


Moderator end the meeting, but meeting still ongoing

Actual behavior: When moderator end meeting, the meeting still ongoing.
Expected behavior: When moderator end meeting, should show up two options for moderator, #1 End meeting for all #2  Leave meeting.
https://github.com/jitsi/jitsi-meet-flutter-sdk/assets/65479486/0b220846-686a-40ec-a637-cd45b4c6578f

That depends on how your server is configured. By default it just leaves the meeting.
You need to enable the end conference component.

Currently, I'm using Jaas Service. Please tell me how to enable it.

That feature doesn't work on JaaS, you need you use an API call for it: https://developer.8x8.com/jaas/docs/webhooks-jaas-endpoints see DESTROY_ROOM.
Please raise a support ticker for further JaaS questions and to request we look into enabling this feature in the UI.


Use always available CMake executable for zipping archive

Available since CMake 3.3 the "format" option for the tar command
allows for generation of zip archive.
closes  #647

/azp run


Pre-compile functions

At present, each time any function is called, the function parser runs through each file on disk and re-creates all the functions. This is unnecessary, and noisy in the logs.
I think there should be a script that runs pre-deploy to create the exported and compiled index file. This should represent all of the exports that firebase functions is expecting.
While this may not be an issue with a handful of apis - I could see this being a problem if there were many more.

@adamschnaare I didn't know this is the case. I though the index file is only run once.
When I'm using it the logs only print out once unless I change the source code then it rebuilds all of them. When doing normal requests only the function that's supposed to fire is printed out.
Unless I've ignored that in my mind when looking at the logs. Which is possible.

@FilledStacks , From what I can tell, the deployed function is just a parser, it isn't actually separate functions. The only thing that the index file exports is something to handle a request - it doesn't actually export multiple functions recognized by firebase.
Meaning, when you run firebase deploy, only one function gets deployed, no matter how many functions you have developed in the system. This means that each time that one function runs, all of its logic has to run as well - namely the parsing of the function files.
I am about 70% through a draft attempting to precompile them. So the proposed flow would be:

npm run prebuild -> compiles built files for each function
firebase deploy / firebase emulators:start -> run or deploy functions

Okay...so, I think I was wrong. I retested and I only see the parsing functions logs after:

I rebuild
I invoke that particular function (either restful or reactive)

So...apologies for the noise, but I'm closing this.


Unable to create persistent volume using YAML file

What happened?
I'm unable to create a persistent volume using yaml file and kubectl deploy option. Below is my YAML file
apiVersion: v1
  kind: PersistentVolume
metadata:
  name: postgresql-pv-volume
spec:
  storageClassName: manual
  capacity:
    storage: 2Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  hostPath:
    path: '/mnt/data/postgresql'

I then get the following error
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "/v1, Resource=persistentvolumes", GroupVersionKind: "/v1, Kind=PersistentVolume"
Name: "postgresql-pv-volume", Namespace: ""
Object: &{map["apiVersion":"v1" "kind":"PersistentVolume" "metadata":map["annotations":map["kubectl.kubernetes.io/last-applied-configuration":""] "name":"postgresql-pv-volume"] "spec":map["accessModes":["ReadWriteOnce"] "capacity":map["storage":"2Gi"] "hostPath":map["path":"/mnt/data/postgresql"] "persistentVolumeReclaimPolicy":"Retain" "storageClassName":"manual" "volumeMode":"Filesystem"]]}
from server for: "STDIN": persistentvolumes "postgresql-pv-volume" is forbidden: User "system:serviceaccount:worldofchatting-d3646568:devspace" cannot get resource "persistentvolumes" in API group "" at the cluster scope

What did you expect to happen instead?
Persistent volume created
How can we reproduce the bug? (as minimally and precisely as possible)

clone my repo https://github.com/slevine111/WorldOfChatting
checkout the develop branch
create a space on devspace
run devspace deploy on the develop branch

Local Environment:

Operating System: mac
Deployment method: kubectl apply

Kubernetes Cluster:

Cloud Provider: DevSpace Cloud
Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.9-gke.15"}

Anything else we need to know?
Here is my ~/.kube/config-devspace
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ***
    server: ***
  name: devspace-my-app
contexts:
- context:
    cluster: devspace-my-app
    namespace: my-app-0167643e
    user: devspace-my-app
  name: devspace-my-app
current-context: devspace-my-app
kind: Config
preferences: {}
users:
- name: devspace-my-app
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - use
      - space
      - --provider
      - app.devspace.cloud
      - --space-id
      - "681"
      - --get-token
      command: devspace
      env: null

Here is my ~/.kube/config
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ***
    server: ***
  name: devspace-worldofchatting
- cluster:
    certificate-authority: ***
    server: ***
  name: minikube
contexts:
- context:
    cluster: devspace-worldofchatting
    namespace: worldofchatting-d3646568
    user:  devspace-worldofchatting
  name: devspace-worldofchatting
- context:
    cluster: minikube
    user: minikube
  name: minikube
current-context: devspace-worldofchatting
kind: Config
preferences: {}
users:
- name: devspace-worldofchatting
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - use
      - space
      - --provider
      - app.devspace.cloud
      - --space-id
      - "932"
      - --get-token
      - --silent
      command: devspace
      env: null
- name: minikube
  user:
    client-certificate: **
    client-key: ***

/kind bug

Hi @slevine111! Creating persistent volumes directly is not permitted in DevSpace Cloud managed clusters. Instead, you will have to create a persistent volume claim and then a persistent volume will be created for this claim: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims
The reason why it is not allowed to create persistent volumes directly is that they are not namespaced, instead they are cluster-wide resources. In DevSpace Cloud you can only create resources in your namespace and nothing which cluster-wide, so you have to create a persistent volume claim in your namespace/space and then the cluster will create the persistent volume for you.
In your case, you want to create a postgres database. Instead of creating the yaml files yourself, you could simply tell DevSpace to use the postgresql helm chart. You can do this by adding this to the deployments section, so that your devspace.yaml would look like this:
version: v1beta3
images:
  webserver:
    image: dscr.io/slevine111/worldofchatting
    createPullSecret: true
deployments:
  - name: database
    helm:
      chart:
        name: stable/postgresql
      values:
        postgresqlDatabase: "db_website"
        postgresqlUsername: "db_user"
        postgresqlPassword: ${DB_PASSWORD}
  - name: worldofchatting
    kubectl:
      manifests:
        - k8s
dev:
  sync:
    - imageName: default
      excludePaths:
        - node_modules
        - npm-debug.log
        - .git
        - .gitignore
        - Dockerfile
        - k8s
        - devspace.yaml/

After adding this, just run devspace dev or devspace deploy and DevSpace will ask you to provide a value for ${DB_PASSWORD} and then create the postgres database for you. You can connect to the database via hostname: database-postgresql
Hope that helps. Let me know if anything is unclear.

@slevine111 Were you able to provision your persistent volumes with my explanation above or are there still questions open regarding this issue? Let me know if we can close this.

@LukasGentele Sorry for delayed response. Yep I was able to provision the persistent volume. Thanks a lot for your detailed explanation. I sticked to using manifests. i haven't yet read up on Helm but I plan to and give that a go.
I'm now having some trouble with devspace in CircleCI. Specifically I'm having trouble when I try to run "devspace use space worldofhchatting." worldofchatting is the space I have previously created. Below are my config.yml file for DircleCI and screenshots of the installation of devspace and devspace login in CircleCI running successfully and then the error I'm getting with devspace use space. Would you like me to create a separate issue for this? Thanks

version: 2
jobs:
  build_and_deploy:
    docker:
      # specify the version you desire here
      - image: circleci/buildpack-deps:jessie

    steps:
      - checkout

      - run:
          name: put environment variables in secrets
          command: |
            POSTGRES_USER_ENCODED=$(echo $POSTGRES_USER | base64)
            POSTGRES_PASSWORD_ENCODED=$(echo $POSTGRES_PASSWORD | base64)
            REDIS_PASSWORD_ENCODED=$(echo $REDIS_PASSWORD | base64)
            JWT_SECRET_ENCODED=$(echo $JWT_SECRET | base64)
            jwt_secret_lines=$(echo $JWT_SECRET_ENCODED | tr " " "\n")
            sed -i "s/ENV-VAR-POSTGRES-USER/${POSTGRES_USER_ENCODED}/" ./k8s/secret.yaml
            sed -i "s/ENV-VAR-POSTGRES-PASSWORD/${POSTGRES_PASSWORD_ENCODED}/" ./k8s/secret.yaml
            sed -i "s/ENV-VAR-REDIS-PASSWORD/${REDIS_PASSWORD_ENCODED}/" ./k8s/secret.yaml
            for line in $jwt_secret_lines
            do
                sed -i "s/ENV-VAR-JWT-SECRET/${line}ENV-VAR-JWT-SECRET/" ./k8s/secret.yaml
            done
            sed -i "s/ENV-VAR-JWT-SECRET//" ./k8s/secret.yaml

      - run:
          name: install devspace
          command: |
            curl -s -L "https://github.com/devspace-cloud/devspace/releases/latest" |\
            sed -nE 's!.*"([^"]*devspace-linux-amd64)".*!https://github.com\1!p' | xargs -n 1 curl -L -o devspace && chmod +x devspace;
            sudo mv devspace /usr/local/bin;

      - run:
          name: devspace login
          command: devspace login --key ${DEVSPACE_CLOUD_ACCESS_KEY}

      - run:
          name: set up space to use
          command: devspace use space worldofchatting

      - run:
          name: deploy
          command: devspace deploy

  test:
    docker:
      # specify the version you desire here
      - image: circleci/buildpack-deps:jessie

    steps:
      - checkout
      - setup_remote_docker

      - run:
          name: build test image
          command: docker-compose build

      - run:
          name: test
          command: docker-compose run webserver npm run test

      - run:
          name: containers
          command: |
            docker container ls
            docker container ls -a

      - run:
          name: copy coverage file
          command: docker cp worldofchatting-webserver-test:/user/src/app/coverage-circleci ./coverage-circleci

      - run:
          name: check
          command: |
            pwd
            ls

      - store_artifacts:
          path: ./coverage-circleci

workflows:
  version: 2
  test_build_and_deploy:
    jobs:
      - test
      - build_and_deploy:
          requires:
            - test
          filters:
            branches:
              ignore: master

@slevine111 yes, it would be great if you could create a separate issue for this. Definitely a bug. We'll ship a fix with the next release (probably on Monday). Thanks for reporting this.

@LukasGentele I have created a new issue for that. Thanks for taking care of it so quick

Hi,
It would have been good if you had given an example of a Persistent Volume Claim and how it is used inside a devspace.yaml to create persistent volume?

It really depends on if you're using a helm chart or kubernetes manifests or the component helm chart we provide. For the component-chart, you can find documentation here: https://devspace.sh/component-chart/docs/guides/persistent-volumes

Hi
What if I want two pods/deployments to share the same volume but both of them have the ability to RW access?
How does that scenario work? I am inclined to use kubectl manifests and I am using an AKS cluster for the same.
-Srikanth


Upgrade to .NET Core SDK 5.0.100

Upgrade to .NET Core SDK 5.0.100.
Dropped support for netstandard1.1.
Update the .editorconfig file which has changed in a breaking way (https://github.com/RehanSaeed/EditorConfig/pull/42) to support VS 16.8.
Enable EnforceCodeStyleInBuild (This is awesome).
Fix all the new warnings.
Switch from is object to is not null. This has been on my mind for a long time. There is a lot more that could be done but getting some C# 9 in early.

Looks good to me! Wasn't sure that C# 9 features were going to be supported by older runtimes (eg. Framework) as I remember seeing something saying that new C# features were going to coincide with new .NET releases but it is pretty cool to find out that at least things like is not null will be.
While this is not directly relevant to this issue, thought I would share something that I found out recently with some Microsoft.* 5.0.0 dependencies: https://github.com/Azure/azure-functions-vs-build-sdk/issues/472
This has nothing to do with us targeting .NET 5 in our tool/tests or using the SDK but if we were to update the wrong assemblies, it may cause issues under particular circumstances.