Fix frozen-height conversion

Closes: #1710
Description
The fix in https://github.com/informalsystems/ibc-rs/pull/1640 was incomplete, so we basically needed to make sure that we serialize domain type frozen height None as Some(Height::zero()), because that's what ibc-go expects.

PR author checklist:

[x] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[x] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

[x] Reviewed Files changed in the GitHub PR explorer.
[x] Manually tested (in case integration/unit/mock tests are absent).

To test with basecoin-rs ->

Checkout the  hu55a1n1/module-verification branch
Apply the following diff to disable connection proof verification (that I'm yet to fix) ->

diff --git a/modules/src/core/ics03_connection/handler/verify.rs b/modules/src/core/ics03_connection/handler/verify.rs
index 917fb5ac..e6485ef6 100644
--- a/modules/src/core/ics03_connection/handler/verify.rs
+++ b/modules/src/core/ics03_connection/handler/verify.rs
@@ -16,17 +16,17 @@ pub fn verify_proofs(
     client_state: Option<AnyClientState>,
     height: Height,
     connection_end: &ConnectionEnd,
-    expected_conn: &ConnectionEnd,
+    _expected_conn: &ConnectionEnd,
     proofs: &Proofs,
 ) -> Result<(), Error> {
-    verify_connection_proof(
-        ctx,
-        height,
-        connection_end,
-        expected_conn,
-        proofs.height(),
-        proofs.object_proof(),
-    )?;
+    // verify_connection_proof(
+    //     ctx,
+    //     height,
+    //     connection_end,
+    //     expected_conn,
+    //     proofs.height(),
+    //     proofs.object_proof(),
+    // )?;

     // If the message includes a client state, then verify the proof for that state.
     if let Some(expected_client_state) = client_state {

Try to create a connection between the basecoin chain and a gaia chain using these instructions -> https://github.com/informalsystems/basecoin-rs/pull/20#issue-1011291897


Connection Refused When Using Nginx Proxy

Describe the bug
I followed the instruction here:
https://strapi.io/documentation/v3.x/deployment/nginx-proxy.html
But Nginx gives me 502 - Connection Refused.
Expected behavior
It should work!
Code snippets
It's just like the link above, except I don't have https.
System
I'm using strapi/strapi docker image, the latest one.
Additional context
I also tried adding proxy: true to the server config, which not worked.

Hello, you need to add the yarn build step in your Dockerfile

Hello, you need to add the yarn build step in your Dockerfile

Something similar to this:
FROM node:lts-alpine
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn
COPY . .
RUN yarn build
EXPOSE 1337
CMD ["yarn", "start"]

Hey there, sorry for the delay. I found out the problem some days ago but I was very busy I couldn't post it here. The problem was here:
upstream strapi {
    server <IP_ADDRESS>:1337;
}

As I said, I used Nginx in a container, and by doing that, I was referencing the Nginx container itself when I wrote <IP_ADDRESS>. I changed it to the container name and now it works! Although I still can't get the admin panel and the documentation from the subpath, which may be another thread or issue, at least the API works itself, and I will open another issue for that if needed.
Thanks again!

It would appear the Admin is not being rebuilt then based on: https://github.com/strapi/strapi-docker/blob/master/strapi/docker-entrypoint.sh
That would be an issue to post on https://github.com/strapi/strapi-docker though.

I just experienced this issue too, and lost hours trying to work out what the problem is. The yarn build inside the container fixed it, but I agree, the Admin should be rebuilt when you provide a PUBLIC_URL, or the PUBLIC_URL should be a variable read from a config file.

It would appear the Admin is not being rebuilt then based on: https://github.com/strapi/strapi-docker/blob/master/strapi/docker-entrypoint.sh
That would be an issue to post on https://github.com/strapi/strapi-docker though.

I just experienced this issue too, and lost hours trying to work out what the problem is. The yarn build inside the container fixed it, but I agree, the Admin should be rebuilt when you provide a PUBLIC_URL, or the PUBLIC_URL should be a variable read from a config file.


The hook "displayProductButtons" is deprecated

use "displayProductAdditionalInfo" instead

Questions
Answers

Description?
The hook "displayProductButtons" is deprecated, and need to be replaced by "displayProductAdditionalInfo"

Type?
bug fix

BC breaks?
no

Deprecations?
yes

Fixed ticket?
Fixes PrestaShop/Prestashop#29189.

How to test?
Please follow above issue's Step to reproduce before and after PR. Do not forget to Reset module in Back-office after PR.

Hello @leemyongpakvn can you add an upgrade file with unregisterhook('displayProductButtons')

@okom3pom n @PrestaEdit I did not see the upgrade directory so I thought this module is an exception. The upgrade file is uploaded now but I don't know how to create upgrade directory here :(

When the issue is ok for QA i approve

thank you @leemyongpakvn and @florine2623 !


Fix for:  Error dialog when deleting files from F# projects #319

Fixes dotnet/project-system#3195 (comment)
When deleting a file for a newly created F# project causes a Watson, and VS crashes and restarts.
The error happens because VS is in the process of loading and instantiating project, and at the same time starts the editor.  Our implementation of SetupNewTextView, queries the workspace to see if the project contains this document.  Unfortunately since the project is not yet fully instantiated, the workspace doesn't have information about the document.  The document will be added to the workspace and project as the project load proceeds normally, and workspace events will cause us to wire up intellisense correctly.
We need to ensure that we still enable the miscellaneous files behavior for loose F# documents.
The fix is to verify that hierarchy retrieved from the running document table for the document has the capability "CPS".  I.e. is a cps project.
If the document is associated with a CPS project we can be sure that necessary workspace events are on their way, and we can leave SetupNewTextView without doing any intellisense wireup, because it will be handled in the workspace events.
@brettfo, @Pilchie --- this fixes an AV does it meet the bar for 15.6
Will, brett, we need to try this out to make sure there are no other holes.
Kevin

From the bug, this isn't an AV, it's an error dialog that is handled, and only on project creation, not re-open, right?


Jeff Schaller: Watch freedriverupdater.com

Jeff Schaller requests the watch of the watch_keyword freedriverupdater\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

freedriverupdater\.com has been seen in 1 true positive, 0 false positives, and 1 NAA.

Approved by tripleee in Charcoal HQ


[Feature]: Automated testing to verify access control

A customer wants to automatically check whether access given to a user is being enforced correctly.
We would like to make a regular security check of the current access control rules. So that we can make sure that the actual state still corresponds to the target state.
Slack Thread
 Front conversations

Does this need to be automated or is it more like a role spoofing feature request to manually check?

It comes from a security POV so, I believe it's to do with automated checks. I'll get more details from the customer.


Agent tries to connect to 7-29-1-app.datadoghq.com, which does not resolve over privatelink.

Using AWS VPC Endpoints:
com.amazonaws.vpce.us-east-1.vpce-svc-0d560852f6f1e27ac
com.amazonaws.vpce.us-east-1.vpce-svc-025a56b9187ac1f63
com.amazonaws.vpce.us-east-1.vpce-svc-0ed1f789ac6b0bde1
The agent tries to go to 7-29-1-app.agent.datadoghq.com
This DNS does not resolve over private link.
However, agent.datadoghq.com does resolve.  Showing my VPC Endpoint is correctly configured.

Please remove the previous metrics PrivateLink endpoint (com.amazonaws.vpce.us-east-1.vpce-svc-0d560852f6f1e27ac) from your VPC before setting up this new, updated endpoint. The new endpoint does not require the dd_url/DD_DD_URL config option to be set to any specific value, it should be left unset in Agent config.
I'll go ahead and close this issue, but feel free to re-open and comment here if you're still running into issues with AWS PrivateLink, thanks!


Apt package salt cloud / api not found

E: Version '2014.7.2+ds-1trusty2' for 'salt-master' was not found
E: Version '2014.7.2+ds-1trusty2' for 'salt-minion' was not found
E: Unable to locate package salt-cloud
E: Unable to locate package salt-api
INFO[0098] The command [/bin/sh -c apt-get update &&     apt-get install -y salt-master=$SALT_VERSION salt-minion=$SALT_VERSION                 salt-cloud=$SALT_VERSION salt-api=$SALT_VERSION] returned a non-zero code: 100

Thanks for the issue report @radiumx3.
This is due to that latest version is 2014.7.4, will update docker file and setup a new branch


Genetic Attributes System (DNA)

Problem Description
The current Genetic Attributes System lacks depth and flexibility, hindering the ability to create diverse and dynamic creatures within the ecosystem. While it provides basic genetic attribute management, it falls short in supporting advanced genetic interactions, evolutionary dynamics, and integration with gameplay mechanics.
Proposed Solution
Enhance the existing Genetic Attributes System to support a wider range of genetic traits, dynamic attribute evolution, and seamless integration with creature behavior and interactions. This involves refining the genetic attributes structure, optimizing randomization mechanisms, improving the preset system, and integrating genetic attributes with creature AI and behavior.
Alternatives Considered
Developing a custom genetic attributes system tailored to the specific requirements of the game.
Additional Context
Improving the Genetic Attributes System is essential for creating a vibrant and diverse ecosystem within LP, enhancing player engagement and immersion. The proposed solution aims to address existing limitations while providing a solid foundation for future expansions and iterations of the genetic simulation mechanics.

Covered by PR #68
However better project structure will be needed to enhance the experience for any contributor


Added an option to resize the cropped bitmap to specific size

This feature allows setting a specific size for the result bitmap. The resize is done on the cropped bitmap.

That's thing that you had done is amazing, is it possible to implement center handles then?

Like this

i'm struggling with implementation, but i can't do that :(


[SWT-NNNN] Range-based confirmations

Swift Testing includes an interface for checking that some asynchronous event occurs a given number of times (typically exactly once or never at all.) This proposal enhances that interface to allow arbitrary ranges of event counts so that a test can be written against code that may not always fire said event the exact same number of times.
Read the full proposal here.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

Stuart has approved this PR and will be updating the forum thread shortly. Merging.

@swift-ci test

@swift-ci test

@swift-ci test Windows

@swift-ci test


Add possibility to see bot output (cards, etc) as it is will be in real chat (Teams, Skype)

Hello
Upon development of Bot I'm using Bot Emulator a lot! It's very useful tool to create business logic bug free apps.
But markdown and card formatting that is bright and shining in a Bot Emulator is quite different from what I see in Teams and Skype. May i ask you to incorporate viewing chat messages in Bot Emulator as it will be in real Teams, Skype with combobox or something.
So I won't need to publish app for testing.

Hi @SiarheiKuchukBelitsoft ,
Thanks for the feature request, but we have no current plans of emulating all the different channels as it would be an enormous effort both in implementation and maintenance.
Many of the channels support and add new features that aren't supported in other channels, and so we would have to implement all these different features in the Emulator. Additionally, we would have to constantly maintain parity with the channels as they updated these features indefinitely.
This is not feasible with the current team size and resources available to us.


Fixing bug in reads_trimer.py that leads to no barcodes_1.txt file being written

Hi Afonso,
while trying to get tnseeker to run I found a bug. Without these changes, at least in some cases/some machines, the whole barcode pipeline failed because the intermedaite barcodes_1.txt was never written (essentially because barcode_allow was by mistake set to False instead of True in read_trimer.

You are very right! I have mostly used the barcode option so I am not surprised this has passed unnoticied... Very nice find in that spaghetti code! Let me know if you need help, I know TnSeeker can still be confusing and buggy...

Will do, thanks for the quick merge! :)


Unable to get yank, write and undo to display in nvim-notify

Hi,
Thanks for the awesome plugin. It is amazing. I want to see yank and write to be displayed into nvim-notify.

I still get all the other notifications, like " file created", "file deleted" and some other error messages. I want to understand what am I missing.
Thanks in advance.

This is a question for noice.nvim, nvim-notify does not send these notifications


Adding Hydraulic Pneumatic Friction plugin

A new plugin and test framework is ready. Need to work on model accuracy.

Nice job Dharini making a clean and simple plugin to address this need.  I have a few suggestions for checking/consideration.   The friction force versus speed interpolation defined by:
pistonSpeed{-0.4F, -0.3F, -0.2F, -0.1F, 0.0F, 0.1F, 0.2F, 0.3F, 0.4F},
meanFriction{1200.0F, 1000.0F, 700.0F, 500.0F, 0.0F, -1000.0F, -1400.0F, -2100.0F, -2900.0F}
probably needs a larger extend, in the paper tests were done up to these speeds (+/- 0.4 m/s) but in actuality the piston could go quite a bit faster.  I'd say to be sure of covering the possibilities, the chart should go up to +/- 2m/s.  Because this interpolation consists of just a few straight lines, it may not be necessary to include points in the intermediate parts of the straight sections, which could speed up the interpolation some.  I  believe splinter may be configured to use the highest values in the interpolation table when independent variables greater than the defined extent are used, this would be good to include if it's possible.  @andermi knows what's possible I believe.
Also, in what's sure to be a continual source of confusion, the internal gazebo model uses and opposite sign for the position of the ram extension compared with the paper and actual system at sea.  So we need to swap the sign of the velocity relative to the paper.  For now I suggest we keep this annoyance as we've addressed it throughout the code in a number of places, if we decide to change it to match, we can do it once and hopefully find all places to fix it.
Finally, I will suggest a simpler name for this plugin.  I think PTO_Friction or similar is fine, the friction being simulated here is a combination of a lot of contributions, from the hydraulic ram, from the pneumatic part, from extraneous other seals, etc.  So avoiding the specificity of HydraulicPneumatic might be a good idea.  Not too important if it's challenging to change.

That's exactly the feedback I was looking for, thanks Andy!
I saw the behaviour with speed outside the bounds I modelled for was kinda weird. I would want to add all the values inclusive of the range speed will touch. Love some help on getting that data. Otherwise, I'm not sure how to configure the splinter to work that case, will ping Michael!
Changes upcoming:

Switching the speed's sign
Changing plugin name to PTOFriction

Michael is out on the boat today, so here's an example of splinter use from elsewhere that returns the endpoints when an out of bound request is made:
const double eff_m = this->hyd_eff_m.eval(rpm, splinter_ros::USE_BOUNDS);
I haven't tested this carefully, (in michael we trust...:), but in the friction case we'd still want a wide expanse and only count on this for the unexpected case of a higher speed than expected.  Otherwise I'm not sure what spinter returns when the argument is out of bounds, perhaps it extrapolates, or returns dragons...

Update the plugin as per feedback.
The model is still very inaccurate:
/home/osrf/buoy_ws/src/buoy_sim/buoy_gazebo/test/test_pto_friction.cpp:41: Failure
2: The difference between 0.0 and friction_model.eval(0.0, splinter_ros::USE_BOUNDS) is<PHONE_NUMBER>0000006, which exceeds 0.05, where
2: 0.0 evaluates to 0,
2: friction_model.eval(0.0, splinter_ros::USE_BOUNDS) evaluates to -150.00000000000006, and
2: 0.05 evaluates to 0.050000000000000003.
2: /home/osrf/buoy_ws/src/buoy_sim/buoy_gazebo/test/test_pto_friction.cpp:42: Failure
2: The difference between -2100.0 and friction_model.eval(-0.3, splinter_ros::USE_BOUNDS) is<PHONE_NUMBER>9851353, which exceeds 100.0, where
2: -2100.0 evaluates to -2100,
2: friction_model.eval(-0.3, splinter_ros::USE_BOUNDS) evaluates to -2293.7499728985135, and
2: 100.0 evaluates to 100.

What's our tolerance?

The model is still very inaccurate:

I'm going to open a PR in a moment to add a different interpolator. We have found issues with splinter not doing the right thing, unfortunately.

Pending removing splinter.

https://github.com/osrf/buoy_msgs/pull/36 has been merged, so you should be able to update accordingly here.

Replaced splinter, but the build will totally fail without the motor mode PR.

build will totally fail without the motor mode PR

Sorry, I didn't quite think that one through. The issue is that ElectroHydraulicPTO plugin still needs splinter_ros? ... and we can't remove the splinter_ros dependency without the switch to 1d interpolation on mechanical and volumetric efficiencies from motormode

Agreed, I am running down a couple of test issues with motormode but let's aim to get that merged this week so we can have a buildable main again.

buoy sc tests are failing since buoy position is now different with the friction added, working on updating the numbers.

Changing absement values is not affecting the piston motion

Changing absement values is not affecting the piston motion

fixed with 1ebd6c6


Opentrail manager

Here is an overview of how clientside addon development is happening at this point:
All code for client js and tests are being worked on in the goldstone-server repo, in .gitignored folders.
A set of watchers in Gruntfile.js is tracking any changes:
  opentrail: {
                files: clientIncludeOrder.opentrailWildcards,
                tasks: ['clean:ot', 'concat-ot', 'concat:ot_goldstone', 'lint', 'copy-ot']
            },
            opentrailTest: {
                files: clientIncludeOrder.otTest,
                tasks: ['lint', 'karma', 'clean:otTest', 'copy-otTest']
            }

When any OpenTrail client js files are modified, a set of tasks is kicked off that: deletes the client js files in the django-opentrail repo; concatenates the js files in a particular order into a bundle and stashes that in the opentrail repo; again concats the js files and stashes it in the goldstone-server repo to be available for immediate use via browser page refreshes; lints the files and if that passes, copies the individual js files into the django-opentrail repo so they can be checked into git.
When any of the OpenTrail test files are modified, a similar set of tasks is carried out. Explicitly: lint the test files; run the karma unit/integration test runner; blow away all the test files in the django-opentrail repo, and re-copy the from the goldstone-server repo to the django-opentrail repo.
Again the client and test files are in .gitignored folders, as this is currently a private project with no plans to open-source it.
The rationale for doing all the work in the goldstone-server repo, rather than directly in the django-opentrail repo is as follows:

immediate integration with the Grunt testing / filewatching framework.
immediate client dev feedback upon browser refresh.

One might ask why not just do the work in the addon repo and just set up a grunt task to copy the files to the goldstone-server repo for immediate client feedback upon browser refresh? Answer: Doing it as I have avoids setting up yet another node envionment within the addon repo that will handle running grunt and the watch/clean/copy tasks. This will hopefully make addon development going forward rather simple, as it will just require some new grunt targets, which should be a fairly straightforward copy/paste/modify of the existing targets.
Shortcomings of this method: Since all version control is being handled in the addon repo (which keeps private repos private, and not checked into goldstone-server), it's a one-way flow of information. If I were to try to use version control to work on a side feature on addon code, the code in goldstone-server doesn't reflect any changes that happen to the code in the addon repo. In order to accommodate that kind of workflow, it can be done by implementing another grunt task that will take the files from the addon repo, and copy them into the goldstone server repo. This can be done fairly easily, but is a task that should probably be saved until actually needed.
Please let me know if there are any questions/comments on the above,
and without further ado, the pull reqeust:

This pull request incorporates changes to the goldstone server repo in order to dynamically incorporate addon development.
This request:

Modifies Gruntfile.js with a number of watch/copy/clean tasks
Updates css files for opentrail related styles
Prevents info/alert divs from pushing page elements down while they are displayed
Upgrades font-awesome to 4.0.3 . fully open source ( http://fontawesome.io/license/ )
Updates gs router for flexibly integrating addon routes with ability to pass route params to view
adds and updates tests, including a small change to every integration test related to mocked server settings

:+1:

:+1:


[SPARK-15784] Add Power Iteration Clustering to spark.ml

What changes were proposed in this pull request?
According to the discussion on JIRA. I rewrite the Power Iteration Clustering API in spark.ml.
How was this patch tested?
Unit test.
Please review http://spark.apache.org/contributing.html before opening a pull request.

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/testing-k8s-prb-make-spark-distribution/3806/
Test PASSed.

Test build #91472 has started for PR 21493 at commit 15c087f.

Test build #91470 has finished for PR 21493 at commit a605a2d.

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/91470/
Test PASSed.

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/testing-k8s-prb-make-spark-distribution/3808/
Test PASSed.

Test build #91472 has finished for PR 21493 at commit 15c087f.

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/91472/
Test PASSed.

Merged build finished. Test PASSed.


Issue with creating a new folder through solution explorer

Describe the bug
Upon creating a new folder, the last created folder disappears.
To Reproduce
Steps to reproduce the behavior:

Go in Solution view
Create a folder
Create 2 folders in the folder you just created. One should disappear.

Expected behavior
Creating a new folder shouldn't make the other disappear.
Screenshots

Environment (please complete the following information):

OS: Windows 10 2004 build 19041.450
Version v0.3.10 (assuming this meant version of extension)
vscode version 1.48.0

Additional context
The files and folders are on the disk, but the extension doesnt display them, even though I created them through the extension.

Hi @OrangeDoggoo,
Would you mind to send me your project file (.XXproj)?


Gif disappeared when drag from left in UINavigationController

When use system gesture to pull a navigation controller.Gif was disappeared. I think it should generate a static picture. The gesture is system gesture, drag from edge of the left screen, not a speciall one.

We are planning to replace our GIF component in 4.0 with FLAnimatedImage. Hopefully this will take care of your issue.

Yes   Thanks :+1:

:+1:

:+1:

:+1:

@Onetaway  We have replaced our GIF component with a library from Flipboard (FLAnimatedImage). Could you try our 4.x branch (instructions) and see if it helps?

Closing. The FLAnimatedImage solution replacing our own GIF is integrated into the 4.x branch.


⚠ ClamAV has degraded performance

In 36309ac, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in d2e9e52.


Leever Enemy

I'll implmement the Leever enemy into the game.
Here's a sprite made by me and polished by Elginive

The behaviors are:

Moves invisibly underground toward a player, when it is near the player it emerges from the ground and continues pursuing the player for a short time before dropping back underground

While underground and in transition it does not deal damage and cannot take damage

If you have some ideas to make this enemy look better please tell me.
I plan to implement this little lovely thing in the end of the week, but maybe will need assistance because I never wrote an Enemy AI and especially not for such a special behavior.

Probably shouldn't call it the Leever.

Any Ideas for names?

 A play on "Wiggler" from Mario.

What about "Wrigglorn"? Or maybe that is too pokemon of a name.

One of the suggestions on discord was Wormlion, which could open up some sort of roar mechanics (since, you know, lions roar and it's a Wormlion)

One of the suggestions on discord was Wormlion, which could open up some sort of roar mechanics (since, you know, lions roar and it's a Worm_lion_)

I like Wormlion! Introducing some sort of roar mechanic would also go a long way towards not being Zelda and therefore not getting shut down!

Ok so, after some suggestions I'll stick to Wormlin.
IF someone really does not agree with it, tell me


upload images

The PR seems to break the CSS and HTML, at least on my side.

Images are much larger.
buttons lost their organization and style.

Please confirm.


Add Netframework and Netstandard unit tests

Feature Request
Description
as a develoiper i would like to run netframework and netstandard unit tests in CI/cd so that I can be confident things did not break when making changes

@AddressXception - its not clear to me if this is still needed after #192 ?


Unable to create more than 29 sites

Currently in v4 we won't be able to create more than 29 sites(unless some are disabled). This is because docker is unable to find new IP address to allocate - https://loomchild.net/2016/09/04/docker-can-create-only-31-networks-on-a-single-machine/
There is still a way around it(by manually specifying subnet during network create) and we need to check how to implement it.

For this issue, we have decided that currently, we'll go with a workaround of just allowing users to create a limited number of sites, 27 to be precise.
We might fix this in the future and since shared hosting is not high on the priority list for EasyEngine, this is something that might not be worked on soon. If someone is interested in actually working on fixing this issue, I would be glad to help with the implementation details.


Hot Module Replacement API

To do:

[x] refactor
[x] docs
[x] actually reload the page if updates can't be applied (how to make sure the reason for the reload is kept? console is flushed on the reload)
[x] update redux skeleton — https://github.com/brunch/with-redux/pull/2

After merged (in order):

[ ] release brunch
[ ] release commonjs-brunch
[ ] release auto-reload-brunch
[ ] add auto-reload-brunch as hmr-brunch's peerDep
[ ] release https://github.com/brunch/hmr-brunch
[ ] merge update for redux skeleton — https://github.com/brunch/with-redux/pull/2

What is intentionally missing from this PR:

source maps for cases when if (module.hot) { ... } checks are cut — since production isn't going to need source maps anyway
callback for self-accept accept() for when there is an error

Relevant PRs:

[x] https://github.com/brunch/deppack/pull/19 (deppack changes needed to support)
[ ] https://github.com/brunch/commonjs-require-definition/pull/21 (HMR runtime code)
[ ] https://github.com/brunch/auto-reload-brunch/pull/70

[ ] https://github.com/brunch/with-redux/pull/2 (only after this is merged and all releases are cut)

http://github.com/brunch/hmr-brunch

This PR is (and all its dependents are) ready for review @paulmillr @es128
I'm mostly ok with the state of this. If anything, introducing some private plugin API for a thing or two (https://github.com/brunch/brunch/pull/1298#discussion_r60193084) could help better structure this functionality logically, but I didn't do that just yet, want to hear your feedback first.


GroupConsumer does not support starting group at offset 0

Hello,
I've noticed when adding new GroupConsumers to a topic for watching, they start watching from the current position of the topic and not the start position. This means only new data from the time the consumer is added is reported on, which is often not the requirement (i.e. Adding a new consumer to read a log from start to finish, and then watch the tail).
Is there a flag or option to make the initial offset be 0 for a new consumer?
-Steve

So, as described in #2 I can't accept your PR. But this issue can be solved with two proposed options: #3 and #4. I prefer #4.

But for now the new startingOffset option will do.

Fixed in 0.1.5


Add Github Copilot as Chat option

Validations

[x] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[x] I'm not able to find an open issue that requests the same enhancement

Problem
People want one chat experience
Github copilot has a public api for chat
People that pay $10 for github copilot could save hundreds a month by using copilot as their chat, since it's virtually unlimited
Solution
Check for vscode.lm registered models, specifically "copilot" vendor for now
Include those models as options in the model dropdown

@RomneyDa /assign

Hi @PRANJALRANA11
We're not sure if we can do this without violating github terms, will backlog for now and look into it.
Thanks!

@RomneyDa https://docs.github.com/en/copilot/building-copilot-extensions/building-a-copilot-agent-for-your-copilot-extension/using-copilots-llm-for-your-agent
It's official for agents

Closing this issue as not planned due to terms

@sestinj Could you please clarify why this enhancement is not planned? Specifically, what terms are causing the issue?

Sorry, terms meaning Terms and Conditions

I got that part but I was asking which terms and conditions are the reason for not implementing this. A lot of other editors are adding the GitHub Copilot option for example Zed has an option to select GitHub Copilot as my AI for the IDE.


fix: SignUp continue with the link

This PR resolves [MOPLAT-501]
Description

https://user-images.githubusercontent.com/17421923/203330958-e7d976ef-2f71-4123-98de-5aec7c1fa329.mov
PR Checklist

[x] I tested my changes on iOS / Android.
[x] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Thanks @rajsam003 ! Can you change the heading of the modal to "No Artsy account found", and set the text to be as follows:

Your XXX account is not linked to an Artsy account. If you already have an Artsy account and you want to log in to it via XXX, you will first need to sign up with XXX. You will then have the option to link the two accounts.

where XXX is either Google or Facebook, depending on what they used.


Move folders

I moved the files around so that there is a folder for each question/analysis (which is just one right now) and then the notebooks nested within. I also added a README.md for the repo and the folder. Feel free to edit anything or give feedback on needed changes!

I updated this branch with my most recent .Rmd (bad me for not pushing sooner).


Theater mode no longer work

Theater mode no longer work, or att least the button is no longer present in the media-bar

the newer versions use the youtube embedded video player, you can downgrade to 5.3 (click the Raw button on upper right) and that version is mostly functional. it sometimes gets detected on prerolls, but you can refresh past it till it's fixed, at least


Revive tests with old beacons

Issue summary
This applies to RPC methods Filecoin.StateGetBeaconEntry and Filecoin.BeaconGetEntry
To check the compatibility with recent Lotus versions, we had to modify our tests to not check old beacons. See https://github.com/ChainSafe/forest/pull/4680
This is blocked by https://github.com/filecoin-project/lotus/issues/12414
Look for this issue's URL for tests that were suppressed.
Other information and links

This time it's blocked by performance of the new logic for handling the StateGetBeaconEntry https://github.com/filecoin-project/lotus/issues/12527


TracebackException only for python >=3.5

from traceback import TracebackException as TE
in scenario.py does not work in python 3.4. e.g. pyhon setup-database.py is not working due to that.

This issue was moved to energiekollektiv/openmod.sh#3


Check if frs sync.Map is nil within handleArchive

@hectorj2f pointed out that we were still seeing nil pointer dereferences/panics when failing to scan archives (i.e., frs is nil):
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x48955a]

goroutine 1652 [running]:
sync.(*Map).loadReadOnly(...)
	sync/map.go:114
sync.(*Map).Range(0x0?, 0x9a9154?)
	sync/map.go:478 +0x1a
github.com/chainguard-dev/malcontent/pkg/action.recursiveScan.func1({0xc00171fef0, 0x8d})
	github.com/chainguard-dev/malcontent/pkg/action/scan.go:246 +0x305
github.com/chainguard-dev/malcontent/pkg/action.recursiveScan.func3()
	github.com/chainguard-dev/malcontent/pkg/action/scan.go:292 +0x70
golang.org/x/sync/errgroup.(*Group).Go.func1()
	golang.org/x/sync@v0.8.0/errgroup/errgroup.go:78 +0x50
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 1
	golang.org/x/sync@v0.8.0/errgroup/errgroup.go:75 +0x96

This is the same issue as #462 but I only fixed the bug in the errIfHitOrMiss.

Thanks @egibs


Add encoding="utf-8" in setup.py file for smooth installation of tool in Windows Systems

As we have seen by directly running a installation command provided by you -
pip install git+https://github.com/RevoltSecurities/Subdominator

in windows, it give us the error related to encoding type.
But to overcome the issue we used an alternate method also but it is better to fix the issue for simplicity of tool.
Thank you for the tool... have attached the error file for reference!

Error.txt

Hello @Sherlock297 ,
Thank you for creating the issue and for providing valid attachements with nice blog 😄 ,
we will add this in next update of Subdominator. Once we push the update we request you to test it again
and give verification from your side.
Kind Regards,
@RevoltSecurities

Hi @Sherlock297 ,
We deployed the new version and made a fix , could you please check that the update is
working on windows installation.
Kind regards,
@RevoltSecurities

hi @RevoltSecurities ,
thanks! Issue is fixed for installation...!👏
But during runtime as you can see there is an another error related to module... attaching a screenshot for reference.

Hi @Sherlock297 ,
This issue can be easily resolved , you can use this command to install the missing package:
pip install tldextract

and once the subdominator runs smoothly bring back to us with information and if you think issue is resolved you can close it too.
Kind regards,
@Sherlock297

that is great @RevoltSecurities... thanks! closing the issue!


User is not emailed when feedback is complete

The owner of the plan does not get an email message when the admin clicks 'complete' for a feedback request.

This was a nasty error to debug. All of the system's emails are using the 'do-not-reply' address defined in the configuration files except for this one particular email. The code sets the 'from' address to the Org's contact email.
This practice violates AWS SES email rules (sender address must match the domain of the server). This should likely be updated in DMPRoadmap as any other installations that implement SES will have the same problem.


[csi-cephfs] cephfs PVC fails to mount in OCP4 postgresql pod

Cannot mount a cephfs PVC into a postgresql pod created from an openshift default template (attached).
Environment details

Image/version of Ceph CSI driver
$ cat operator-openshift-with-csi.yaml
...
CSI enablement
- name: ROOK_CSI_ENABLE_CEPHFS
value: "true"
- name: ROOK_CSI_CEPHFS_IMAGE
value: "quay.io/cephcsi/cephfsplugin:canary"
- name: ROOK_CSI_ENABLE_RBD
value: "true"
- name: ROOK_CSI_RBD_IMAGE
value: "quay.io/cephcsi/rbdplugin:canary"
- name: ROOK_CSI_REGISTRAR_IMAGE
value: "quay.io/k8scsi/csi-node-driver-registrar:v1.0.2"
- name: ROOK_CSI_PROVISIONER_IMAGE
value: "quay.io/k8scsi/csi-provisioner:v1.0.1"
- name: ROOK_CSI_SNAPSHOTTER_IMAGE
value: "quay.io/k8scsi/csi-snapshotter:v1.0.1"
- name: ROOK_CSI_ATTACHER_IMAGE
value: "quay.io/k8scsi/csi-attacher:v1.0.1"
helm chart version
No idea
Kubernetes cluster version
$ oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.2-201906121056+3569a06-dirty", GitCommit:"3569a06", GitTreeState:"dirty", BuildDate:"2019-06-12T15:47:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+d4417a7", GitCommit:"d4417a7", GitTreeState:"clean", BuildDate:"2019-06-12T15:47:30Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
ceph-postgresql-persistent.yaml.gz

Steps to reproduce the behavior:
Need to have created csi-cephfs storageclas

oc new-project postgresql
oc create -f ceph-postgresql-persistent.yaml
oc get pvc
oc get pods
postgresql pod in CrashBackOffLoop
oc logs <postgresql_pod>

Most likely it is due to securityContext of the pod. First pod is created from pod.yaml in ~/csi/examples/cephfs. Second pod is postgresql pod created from attached postgresql template using csi-rbd vs csi-cephfs storageclass (so that pod is created and you can look at yaml output).
$ oc get csicephfs-demo-pod -o yaml
...
securityContext:
capabilities:
drop:
- MKNOD
procMount: Default
$ oc get pod/postgresql-1-6c4z9 -o yaml (create using csi-rbd to create PVC so pod will succeed)
...
securityContext:
capabilities:
drop:
- KILL
- MKNOD
- SETGID
- SETUID
privileged: false
procMount: Default
runAsUser:<PHONE_NUMBER>

logs for failed postgresql pod (cannot mount PVC created from csi-cephfs)
$ oc logs -f postgresql-x-xxxxx
mkdir: cannot create directory '/var/lib/pgsql/data': Permission denied

Problem faced here is fixed in https://github.com/ceph/ceph-csi/pull/423
@netzzer The images in use in your setup do not have the fix "quay.io/cephcsi/rbdplugin:canary"
The PR that got merged into Rook today [1] has the changes to use the latest "quay.io/cephcsi/cephcsi:canary" images that do carry the fix mentioned. If the environment is shifted to use the same, the permission issue should not occur.
Request a retest with latest Rook images to ensure fix is working for you.
[1] Rook PR: https://github.com/rook/rook/pull/3324

I did retest with fresh clone of rook master branch and the issue is fixed. I am able now to mount a cephfs PVC in a postgresql pod.
$ oc rsh postgresql-1-l9tqb
sh-4.2$ df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         119G  6.8G  113G   6% /
tmpfs            64M     0   64M   0% /dev
tmpfs           7.7G     0  7.7G   0% /sys/fs/cgroup
shm              64M  8.0K   64M   1% /dev/shm
tmpfs           7.7G  3.8M  7.7G   1% /etc/passwd
/dev/nvme0n1p3  119G  6.8G  113G   6% /etc/hosts
ceph-fuse        10G   44M   10G   1% /var/lib/pgsql/data

@netzzer thanks for confirming. closing this issue.


Increase docker-compose.yml version

We should update docker-compose.yml to version 3 and set a minimum docker-compose and docker requirement.

Closed by #89


Issue 131 gratibot redeem

Implements Gratibot redeem and refund commands

Redeem - shows list of redeemable rewards including the cost, description and an image (if available). Dropdown is available to users to redeem an item which will deduct the appropriate amount of fistbumps from a users balance and start a MPIM (multi person instant message) with redemption admins (matt & layne in this PR).
Refund - Only available to redemption admins. If a redemption needs to be canceled for whatever reason, use the refund command to give users back their fistbumps (by removing the associated deduction from the db). Deduction id is given when a user receivers the item.

Not strictly important for this PR, but I want to call out that when this does go to production there will be a bit of extra work to migrate existing redeption tracking to the DB. Plus there will likely be some communication needed to explain the design of the refund feature.

Not strictly important for this PR, but I want to call out that when this does go to production there will be a bit of extra work to migrate existing redeption tracking to the DB. Plus there will likely be some communication needed to explain the design of the refund feature.

Yea was planning on pulling up with Layne/Matt before this goes to prod to talk through this new redemption method with them, and do any migration needed. Once it makes it to prod then was going to blast liatrio with the new feature, then if someone tries to redeem the old way then Layne can redirect them to the redeem command

What's the status on this PR? would be pretty cool. I may be able to carve some time out to help on this. Let me know.

What's the status on this PR? would be pretty cool. I may be able to carve some time out to help on this. Let me know.

Hasn't been touched since the last comment. Was thinking about looking at it again soon, but no concrete plans so if you're feeling it go ahead. I'd love to see this feature in place as well


Username is case sensitive

The user accounts packages recently stopped being case sensitive, any plans on following suit? I was getting this when using username with the wrong case:
{
  "status": "error",
  "message": "Unauthorized"
}

I'll look into this. I'd like to match the accounts API as you've suggested.

Hi @kahmali !
I have faced with this problem when users register on my site using uppercase letters in email and then they try to login they forget about uppercase. It will be good improvement to allow case insensitive login. It makes user experience better.
Thanks!


Allow template filenames with different file extensions

Would it be possible to allow template filenames with an extension other than .stencil?
Even the stencil docs make use of a .html extension.
To temporarily achieve this myself, I manually added StencilTemplateEngine.swift to my project and changed: public var fileExtension: String { return "stencil" }
to: public var fileExtension: String = "stencil"
Then I could change the extension myself in main.swift:
let templateEngine = StencilTemplateEngine()
templateEngine.fileExtension = "html"

PS. I also tried doing this using an extension:
public extension StencilTemplateEngine {
    public var fileExtension: String { return "html" }
}

Even though StencilTemplateEngine().fileExtension returned "html" it didn't work for whatever reason.

@jasonwoodland fileExtension is used when you do not specify file extension for your template in response.render and you register your template engine as a default. In all other cases, you just specify file extension of your template, be it .stencil or .html.
For example:
router.setDefault(templateEngine: StencilTemplateEngine())
response.render("document", context: context) // document.stencil will be rendered since
                                              // StencilTemplateEngine is the default template engine
response.render("document.html", context: context) // document.html will be rendered

Yeah I thought this is how it would behave, so I tried again:
Sources/main.swift:
import Kitura
import KituraStencil

let router = Router()

router.add(templateEngine: StencilTemplateEngine())
router.setDefault(templateEngine: StencilTemplateEngine())

router.get("/test") { request, response, next in
	let context: [String: Any] = [
		"test": "hello"
	]
	try response.render("test.html", context: context).end()
}

// Add an HTTP server and connect it to the router
Kitura.addHTTPServer(onPort: 8080, with: router)

// Start the Kitura runloop (this call never returns)
Kitura.run()

tree:
.
├── Package.pins
├── Package.swift
├── Sources
│   └── main.swift
├── Tests
└── Views
    └── test.html

And I tried:
% curl localhost:8080/test
Cannot GET /test.
%

Package.swift:
// swift-tools-version:3.1

import PackageDescription

let package = Package(
    name: "Framework",
    dependencies: [
        .Package(url: "https://github.com/IBM-Swift/Kitura.git", majorVersion: 1, minor: 7),
        .Package(url: "https://github.com/IBM-Swift/Kitura-StencilTemplateEngine.git", majorVersion: 1, minor: 8)
    ]
)

@jasonwoodland You are right, my fault. I forgot that you have to specify "html" in forFileExtensions parameter when you add your template engine:
router.add(templateEngine: StencilTemplateEngine(extension: _extension),
                   forFileExtensions: ["html"])

Added this line and a test case in
https://github.com/IBM-Swift/Kitura-Sample/blob/issue_19/Sources/KituraSampleRouter/RouterCreator.swift#L163, in  https://github.com/IBM-Swift/Kitura-Sample/issues/73 .

forFileExtensions: works for me. I still have to specify .html but I'm happy with this. Thanks


chore(release<EMAIL_ADDRESS><EMAIL_ADDRESS>

👀 PR includes
chore(release<EMAIL_ADDRESS><EMAIL_ADDRESS>

:tada: This PR is included in version @antv/s2-v1.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v1.11.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hyphens in subdomains fails the self-check with 404

Describe the bug:
When defining an Ingress with tls domains with a subdomain with hyphens the cert-manager gives the error wrong status code '404', expected '200'.
│ I0826 10:25:52.547842       1 controller.go:152] cert-manager/controller/challenges "msg"="syncing item" "key"="default/cert-test-wdq76-877982638-1714201790"                                  │
│ I0826 10:25:52.548096       1 pod.go:58] cert-manager/controller/challenges/http01/selfCheck/http01/ensurePod "msg"="found one existing HTTP01 solver pod" "dnsName"="web-socket-master.test.organization.com"  │
│ I0826 10:25:52.548352       1 service.go:43] cert-manager/controller/challenges/http01/selfCheck/http01/ensureService "msg"="found one existing HTTP01 solver Service for challenge resource" "dnsName"="web-so │
│ I0826 10:25:52.548533       1 ingress.go:91] cert-manager/controller/challenges/http01/selfCheck/http01/ensureIngress "msg"="found one existing HTTP01 solver ingress" "dnsName"="web-socket-master.test.organi │
│ E0826 10:25:52.575809       1 sync.go:183] cert-manager/controller/challenges "msg"="propagation check failed" "error"="wrong status code '404', expected '200'" "dnsName"="web-socket-master.test.organization │
│ I0826 10:25:52.575883       1 controller.go:162] cert-manager/controller/challenges "msg"="finished processing work item" "key"="default/cert-test-wdq76-877982638-1714201790"

Expected behavior:
The certification to be successfully generated.
Steps to reproduce the bug:
example ingress.yml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
    name: test
    namespace: default
    annotations:
        kubernetes.io/ingress.class: "nginx"
        cert-manager.io/cluster-issuer: "letsencrypt-prod"
        nginx.ingress.kubernetes.io/ssl-redirect: 'true'
spec:
    tls:
        - hosts:
            - test.organization.com
            - web-socket-master.test.organization.com
          secretName: cert-test
    backend:
        serviceName: test-master
        servicePort: 80
    rules:
        - host: test.organization.com
          http:
              paths:
                  - backend:
                        serviceName: test-master
                        servicePort: 80
                    path: /*
        - host: websocketmaster.review.zir-online.com
          http:
              paths:
                  - backend:
                        serviceName: websocket-test
                        servicePort: 3000
                    path: /*

Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2): v1.16.13-gke.1
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): v0.16.1
Install method (e.g. helm or static manifests):

helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --version v0.16.1 \
  --set installCRDs=true

/kind bug

I just checked and I was able to get the ACME challenge to pass with a hyphenated URL just fine.
Have you tried https://cert-manager.io/docs/faq/troubleshooting/ to check what might be causing the self-check to fail?
/remove-kind bug
/triage support

I have, I can perfectly curl to the challenge URL externally, and when removing the hyphens from the subdomain, not our main domain which also still contains a hyphen, it instantly works. That's why I reported it here as this seems to indicate some sort of issue with the hyphens. I will try and add the hyphens back in and see if it works now as previously when first starting with the cert-manager we forgot to properly set up the DNS and had to wait for the next day while the manager continued to try.

Well, I'll be darned, re-adding the hyphen suddenly makes it work again. Scratches head, last time it really didn't like it, ow well thanks for the effort anyway.


(Frosting) Support all commands that Cake does

For example, when you attempt to run:
.\build.ps1 --showtree

It should show the dependency graph of Tasks, but instead, it just runs the default task for the build.

Fixed by #2946


Update Modules.md

Thanks for trying to improve the docs, but this is 6 to keep it consistent with the same indentation as the above section also
###### `import type`


Add support for gRPC protocol

Close: #247
V2Ray recently add gRPC protocol, which seems to be harder to detect than WebSocket (over TLS), and can be forwarded by CDN.

May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 V2Ray 4.39.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.16.4 linux/amd64)
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 A unified platform for anti-censorship.
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 [Debug] app/log: Logger started
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 [Debug] app/proxyman/inbound: creating stream worker on <IP_ADDRESS>:9000
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 failed to start server: app/proxyman/inbound: failed to listen TCP on 9000 > transport/internet: grpc listener not registered.
May 26 14:03:34 testserver ssserver[7890]: ERROR plugin exited with status: exit status: 1
May 26 14:03:34 testserver ssserver[7890]: thread 'main' panicked at 'aborted with server exited unexpectly', bin/ssserver.rs:315:45
May 26 14:03:34 testserver ssserver[7890]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
May 26 14:03:35 testserver systemd[1]: shadowsocks-rust.service: Main process exited, code=dumped, status=6/ABRT
May 26 14:03:35 testserver systemd[1]: shadowsocks-rust.service: Failed with result 'core-dump'.

v2ray-core's gRPC is different from xray-core.
https://github.com/v2fly/v2ray-core/blob/master/transport/internet/grpc/config.go#L8
https://github.com/XTLS/Xray-core/blob/main/transport/internet/grpc/config.go#L8

There is a temporary solution can fix it.
https://github.com/teddysun/v2ray-plugin/commit/017759be74504e3b69a389ee1dc52b4d25405136

@ShrdBB
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 V2Ray 4.39.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.16.4 linux/amd64)
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 A unified platform for anti-censorship.
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 [Debug] app/log: Logger started
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 [Debug] app/proxyman/inbound: creating stream worker on <IP_ADDRESS>:9000
May 26 14:03:34 testserver ssserver[7890]: 2021/05/26 14:03:34 failed to start server: app/proxyman/inbound: failed to listen TCP on 9000 > transport/internet: grpc listener not registered.
May 26 14:03:34 testserver ssserver[7890]: ERROR plugin exited with status: exit status: 1
May 26 14:03:34 testserver ssserver[7890]: thread 'main' panicked at 'aborted with server exited unexpectly', bin/ssserver.rs:315:45
May 26 14:03:34 testserver ssserver[7890]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
May 26 14:03:35 testserver systemd[1]: shadowsocks-rust.service: Main process exited, code=dumped, status=6/ABRT
May 26 14:03:35 testserver systemd[1]: shadowsocks-rust.service: Failed with result 'core-dump'.

v2ray-core's gRPC is different from xray-core.
https://github.com/v2fly/v2ray-core/blob/master/transport/internet/grpc/config.go#L8
https://github.com/XTLS/Xray-core/blob/main/transport/internet/grpc/config.go#L8


Test using shorter hashs for -git

This can mostly be ignored as I am just playing around here to see how to get the hash down for repology

Well that worked better than expected :rofl:

I believe you can use cut to extract a substring. Don't use awk, it's too big for a simple extraction

You can but then you would need to set another pipe just to substring it via cut since you can't do multiple arguments in the same command

There that is how the situation would be when using cut.

@Henryws If you are fine with this solution of using cut I could change all git packages which currently use this method in a PR to make them use 8 char long hashes.

Yeah using two instances of cut will be faster than calling awk


Cache credentials so they don't need to be input every run

Cache credentials so they don't need to be input every time.
This can either be the password (encrypted, not plaintext) or http session cookie. I'm not familiar with how cookies TTL work, although it might be enough if the cookie can persist for a few days.

The session cookie has a TTL of 24 hours. This feature would be useful for reinvoking adhoc.
But as a scheduled task, the current logic of login every time scheduler goes off (to get fresh session cookie) would be necessary

If we need to store the user's credentials to relogin, we can store in the OS keystore using keyring package. Seems like this is the correct approach that avoids rolling our own solution.

From https://github.com/edmundmok/mealpy/pull/16#discussion_r274890299, a possible different solution for this issue:

There are three cookies returned on login: __cfduid, tt_visitor_id and _mealpal_session. The first two expire in 2020 (exactly 1 year from now), and the last one doesn't have an expiry. Whichever it is, it looks like we won't have to worry about cookies expiring. You can inspect MealPal(...).cookies after login to check the cookies, or use Chrome Dev tools.

We might be able to persist the cookie, in place of credentials. If we store it in config.yaml or keyring, this will persist for a year, for both adhoc runs and scheduled batch.

The cookies are all contained in .cookies of a MealPal object after .login is successful, which is of type requests.cookies.RequestsCookieJar. Not too sure about the security aspect of this but we can just pickle the cookie jar object to be stored as a binary file locally, and unpickle it again when we need it. With this, I don't think we will need keyring anymore?

I agree, with persisted cookies we can avoid using keyring altogether.
It looks to be FileCookieJar, from stdlib, is passed to the requests session and that is has support for serializing to disk.


Search for markdown docs

we really need search — Lexicon, Blueprints, Handbook, and others are growing — it's becoming increasingly difficult to rely only on the IA of the sidenav to find things.
Clay is using Algolia — might not be a bad place to start.

going to try out Docsearch

@plhnk can we consider this done as we are using Algolia? It is not implemented in blueprints and handbook but the solution is there and working.
Do we have plans to take it to the others?


Add functionality to get SATA SMART attribute flag prefailure and online bits

Functionality to provide the same output as smartctl does for prefailure (TYPE) and online (UPDATED) bits:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       192

@dskrypko I meant to drop that access function completely
The attribute flag field is already public and easily accessible by the user. Adding a wrapper function for the flag is extra complexity that must be avoided.

See the last commit in this PR

Ok

Thank you!
Merged as 99aa93943210595df3bf9fc20c9e733bf9241af6


Wondering if this is being used in production ...

Hi -- it doesn't have a README posted; is documentation elsewhere for Zalandos/others to find?

Hi Lauri,
yes it is. It's common Maven-configuration used by some libraries in 'zalando-stups'. Mostly used as 'parent' to avoid writing same xml in poms again and again.

Got it, thanks. I've included your point here in README.md, just so other Zalandos (especially new members of the tech team) are aware.


Document "limited availability"

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/19
Originally created by @DouweM on 2021-11-12 23:23:18

More accessible option in between 100% availability (regular work week) and 0% availability (vacation)
Taking multiple days or a week off can feel daunting because of the large amount of stuff to catch up on when back, and because of potential of blocking others. So people don't end up taking time off at all.
"During this week I will check in every day (work between 30min and 3hr) to make sure I'm not blocking anyone, but will not start any new work"
Was very useful for me when I visited the Netherlands for the first time since the start of the pandemic, and I was suffering from jetlag, working odd hours because of the time zone, and had lots of people to meet for lunch and dinner

View 1 previous comment from the original issue on GitLab

@therebbie Do you think this is worth documenting? I found it nice at the time to be able to explicitly be half-out and set expectations around that.

Great idea - handbook updated.


Errors while setting up “plone-react”.

Setting up the backend through plone-react itself ends up with an error:
Error: Couldn't find a distribution for 'zope.i18n[zcml]==4.2.0'
Instead of the above, If I installed Plone seperately, and only ran the frontend:
Cmd for running the backend: sudo ./plonectl fg (plone/zinstance/bin)
Cmd for running the frontend: yarn dev (plone-react)
Both the backend and the frontend seem to run fine, without any errors. But when I browse to http://localhost:4300/. I get the following on the page.
Something went wrong: Cannot read property 'replace' of undefined
Here is the entire log for sudo ./plonectl fg
x@y:/opt/plone/zinstance/bin$ sudo ./plonectl fg
instance: 2018-02-25 15:14:31 INFO ZServer HTTP server started at Sun Feb 25 15:14:31 2018
	Hostname: <IP_ADDRESS>
	Port: 8080
2018-02-25 15:14:31 INFO Zope Set effective user to "plone_daemon"
2018-02-25 15:14:33 WARNING ZODB.blob (15814) Blob dir /opt/plone/zinstance/var/blobstorage/ has insecure mode setting
2018-02-25 15:14:36 INFO Plone OpenID system packages not installed, OpenID support not available
2018-02-25 15:14:39 INFO Zope Ready to handle requests

Here is the entire log for yarn dev:
x@y:~/Prog/Plone/Contrib/plone-react$ yarn dev
yarn run v1.3.2
$ NODE_ENV=development npm-run-all dev:build
$ npm-run-all -ln clear:dist prepare:dev:build i18n:build development
[clear:dist       ]
[clear:dist       ] ><EMAIL_ADDRESS>clear:dist /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[clear:dist       ] > rm -rf dist
[clear:dist       ]
[clear:dist       ] $ rm -rf dist
[prepare:dev:build]
[prepare:dev:build] ><EMAIL_ADDRESS>prepare:dev:build /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[prepare:dev:build] > universal-webpack --settings ./webpack/universal-webpack-settings.js prepare
[prepare:dev:build]
[prepare:dev:build] $ universal-webpack --settings ./webpack/universal-webpack-settings.js prepare
[i18n:build       ]
[i18n:build       ] ><EMAIL_ADDRESS>i18n:build /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[i18n:build       ] > babel-node scripts/i18n.js build
[i18n:build       ]
[i18n:build       ] $ babel-node scripts/i18n.js build
[development      ]
[development      ] ><EMAIL_ADDRESS>development /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[development      ] > npm-run-all -ln --parallel build:dev:client build:dev:server run:dev:server
[development      ]
[development      ] $ npm-run-all -ln --parallel build:dev:client build:dev:server run:dev:server
[development      ] [build:dev:client]
[development      ] [build:dev:client] ><EMAIL_ADDRESS>build:dev:client /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[development      ] [build:dev:client] > better-npm-run run_dev_client
[development      ] [build:dev:client]
[development      ] [build:dev:server]
[development      ] [build:dev:server] ><EMAIL_ADDRESS>build:dev:server /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[development      ] [build:dev:server] > better-npm-run build_dev_server
[development      ] [build:dev:server]
[development      ] [run:dev:server  ]
[development      ] [run:dev:server  ] ><EMAIL_ADDRESS>run:dev:server /home/adithya/Prog/Plone/Contrib/plone-react/package.json
[development      ] [run:dev:server  ] > better-npm-run run_dev_server
[development      ] [run:dev:server  ]
[development      ] [build:dev:server] $ better-npm-run build_dev_server
[development      ] [run:dev:server  ] $ better-npm-run run_dev_server
[development      ] [build:dev:client] $ better-npm-run run_dev_client
[development      ] [build:dev:server] running better-npm-run in /home/adithya/Prog/Plone/Contrib/plone-react
[development      ] [build:dev:client] running better-npm-run in /home/adithya/Prog/Plone/Contrib/plone-react
[development      ] [run:dev:server  ] running better-npm-run in /home/adithya/Prog/Plone/Contrib/plone-react
[development      ] [build:dev:client] Executing script: run_dev_client
[development      ] [build:dev:client]
[development      ] [run:dev:server  ] Executing script: run_dev_server
[development      ] [run:dev:server  ]
[development      ] [build:dev:server] Executing script: build_dev_server
[development      ] [build:dev:server]
[development      ] [build:dev:client] to be executed: babel-node webpack/server.dev.js
[development      ] [run:dev:server  ] to be executed: nodemon --watch ./src/server.jsx --watch ./src --watch ./dist/server.js ./src/start-server.js --exec babel-node
[development      ] [build:dev:server] to be executed: webpack --config ./webpack/webpack.config.server.dev.entry.js --watch --hot --colors --display-error-details
[development      ] [run:dev:server  ] [nodemon] 1.14.11
[development      ] [run:dev:server  ] [nodemon] to restart at any time, enter `rs`
[development      ] [run:dev:server  ] [nodemon] watching: ./src/server.jsx /home/adithya/Prog/Plone/Contrib/plone-react/src/**/* ./dist/server.js
[development      ] [run:dev:server  ] [nodemon] starting `babel-node ./src/start-server.js`
[development      ] [run:dev:server  ] [nodemon] Internal watch failed: watch /home/adithya/Prog/Plone/Contrib/plone-react/src/components/theme/App/__snapshots__ ENOSPC
[development      ] [run:dev:server  ] error Command failed with exit code 1.
[development      ] [run:dev:server  ] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[development      ] [build:dev:server]
[development      ] [build:dev:server] Webpack is watching the files…
[development      ] [build:dev:server]
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [build:dev:server] Hash: 6542c9da98a9e5748b99
[development      ] [build:dev:server] Version: webpack 3.10.0
[development      ] [build:dev:server] Time: 14232ms
[development      ] [build:dev:server]         Asset     Size  Chunks                    Chunk Names
[development      ] [build:dev:server]     server.js   856 kB       0  [emitted]  [big]  server
[development      ] [build:dev:server] server.js.map   734 kB       0  [emitted]         server
[development      ] [build:dev:server]   favicon.ico  15.1 kB          [emitted]
[development      ] [build:dev:server] overrides.css  8.39 kB          [emitted]
[development      ] [build:dev:server]   [25] ./src/helpers/index.js 1.52 kB {0} [built]
[development      ] [build:dev:server]   [27] ./src/config.js 418 bytes {0} [built]
[development      ] [build:dev:server]   [38] ./src/reducers/index.js 3.54 kB {0} [built]
[development      ] [build:dev:server]   [48] ./src/constants/Languages.js 246 bytes {0} [built]
[development      ] [build:dev:server]   [49] ./src/reducers/userSession/userSession.js 1.84 kB {0} [built]
[development      ] [build:dev:server]   [50] ./src/server.jsx 6.7 kB {0} [built]
[development      ] [build:dev:server]   [59] ./dist/locales/nl.json 8.54 kB {0} [built]
[development      ] [build:dev:server]   [60] ./dist/locales/de.json 8.55 kB {0} [built]
[development      ] [build:dev:server]   [61] ./dist/locales/en.json 8.09 kB {0} [built]
[development      ] [build:dev:server]   [62] ./src/helpers/AuthToken/AuthToken.js 1.52 kB {0} [built]
[development      ] [build:dev:server]   [63] ./src/helpers/Url/Url.js 8.17 kB {0} [built]
[development      ] [build:dev:server]   [67] ./src/error.jsx 844 bytes {0} [built]
[development      ] [build:dev:server]   [68] ./src/routes.jsx 3.76 kB {0} [built]
[development      ] [build:dev:server]  [169] ./src/store.js 2.65 kB {0} [built]
[development      ] [build:dev:server]  [172] ./src/middleware/index.js 542 bytes {0} [built]
[development      ] [build:dev:server]     + 179 hidden modules
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [run:dev:server  ] ("/home/adithya/Prog/Plone/Contrib/plone-react/dist/webpack-chunks.json" not found)
[development      ] [run:dev:server  ] (waiting for the file to be generated; e.g. as a result of a Webpack build)
[development      ] [build:dev:client] Hash: 6c3ab785d831f4c3fbfb
[development      ] [build:dev:client] Version: webpack 3.10.0
[development      ] [build:dev:client] Time: 46104ms
[development      ] [build:dev:client]                                          Asset     Size  Chunks                    Chunk Names
[development      ] [build:dev:client]     icons.eot?dbc1ef8ba83ec7f4f34cb4a368193841  54.9 kB          [emitted]
[development      ] [build:dev:client]     flags.png?9c74e172f87984c48ddf5c8108cabe67  28.1 kB          [emitted]
[development      ] [build:dev:client]          df45b7de0654df9fd07d53ad002e18ba.woff  54.8 kB          [emitted]
[development      ] [build:dev:client]     icons.ttf?06400145288e8e87306ccac8b852b1d4  54.7 kB          [emitted]
[development      ] [build:dev:client]     icons.svg?022583c4ba2db2f47847c80e5511cb48   199 kB          [emitted]
[development      ] [build:dev:client]      Logo.svg?912d8f6db45eefe8abbd58d767f048e4  14.2 kB          [emitted]
[development      ] [build:dev:client] pastanaga.svg?08f24832ce4ee36a16d053130056f6bf  14.3 kB          [emitted]
[development      ] [build:dev:client]                   main-6c3ab785d831f4c3fbfb.js  28.2 MB       0  [emitted]  [big]  main
[development      ] [build:dev:client]                                  overrides.css  8.39 kB          [emitted]
[development      ] [build:dev:client]                                    favicon.ico  15.1 kB          [emitted]
[development      ] [build:dev:client]    [0] ./node_modules/react/react.js 56 bytes {0} [built]
[development      ] [build:dev:client]    [1] ./node_modules/babel-runtime/helpers/extends.js 544 bytes {0} [built]
[development      ] [build:dev:client]   [15] (webpack)/buildin/module.js 517 bytes {0} [built]
[development      ] [build:dev:client]   [24] ./node_modules/react-intl/lib/index.es.js 51.2 kB {0} [built]
[development      ] [build:dev:client]  [937] multi webpack-hot-middleware/client?path=http://localhost:4301/__webpack_hmr webpack/hot/only-dev-server ./src/client.jsx 52 bytes {0} [built]
[development      ] [build:dev:client]  [938] (webpack)-hot-middleware/client.js?path=http://localhost:4301/__webpack_hmr 7.35 kB {0} [built]
[development      ] [build:dev:client]  [939] ./node_modules/querystring-es3/index.js 127 bytes {0} [built]
[development      ] [build:dev:client]  [942] ./node_modules/strip-ansi/index.js 161 bytes {0} [built]
[development      ] [build:dev:client]  [944] (webpack)-hot-middleware/client-overlay.js 2.21 kB {0} [built]
[development      ] [build:dev:client]  [949] (webpack)-hot-middleware/process-update.js 4.33 kB {0} [built]
[development      ] [build:dev:client]  [950] (webpack)/hot/only-dev-server.js 2.37 kB {0} [built]
[development      ] [build:dev:client]  [951] (webpack)/hot/log-apply-result.js 1.31 kB {0} [built]
[development      ] [build:dev:client]  [952] (webpack)/hot/emitter.js 77 bytes {0} [built]
[development      ] [build:dev:client]  [954] ./src/client.jsx 2.29 kB {0} [built]
[development      ] [build:dev:client]  [968] ./node_modules/babel-polyfill/lib/index.js 833 bytes {0} [built]
[development      ] [build:dev:client]     + 2196 hidden modules
[development      ] [build:dev:client] webpack built 6c3ab785d831f4c3fbfb in 46104ms
[development      ] [build:dev:client] ℹ ｢wdm｣: Hash: 6c3ab785d831f4c3fbfb
[development      ] [build:dev:client] Version: webpack 3.10.0
[development      ] [build:dev:client] Time: 46104ms
[development      ] [build:dev:client]                                          Asset     Size  Chunks                    Chunk Names
[development      ] [build:dev:client]     icons.eot?dbc1ef8ba83ec7f4f34cb4a368193841  54.9 kB          [emitted]
[development      ] [build:dev:client]     flags.png?9c74e172f87984c48ddf5c8108cabe67  28.1 kB          [emitted]
[development      ] [build:dev:client]          df45b7de0654df9fd07d53ad002e18ba.woff  54.8 kB          [emitted]
[development      ] [build:dev:client]     icons.ttf?06400145288e8e87306ccac8b852b1d4  54.7 kB          [emitted]
[development      ] [build:dev:client]     icons.svg?022583c4ba2db2f47847c80e5511cb48   199 kB          [emitted]
[development      ] [build:dev:client]      Logo.svg?912d8f6db45eefe8abbd58d767f048e4  14.2 kB          [emitted]
[development      ] [build:dev:client] pastanaga.svg?08f24832ce4ee36a16d053130056f6bf  14.3 kB          [emitted]
[development      ] [build:dev:client]                   main-6c3ab785d831f4c3fbfb.js  28.2 MB       0  [emitted]  [big]  main
[development      ] [build:dev:client]                                  overrides.css  8.39 kB          [emitted]
[development      ] [build:dev:client]                                    favicon.ico  15.1 kB          [emitted]
[development      ] [build:dev:client]    [0] ./node_modules/react/react.js 56 bytes {0} [built]
[development      ] [build:dev:client]    [1] ./node_modules/babel-runtime/helpers/extends.js 544 bytes {0} [built]
[development      ] [build:dev:client]   [15] (webpack)/buildin/module.js 517 bytes {0} [built]
[development      ] [build:dev:client]   [24] ./node_modules/react-intl/lib/index.es.js 51.2 kB {0} [built]
[development      ] [build:dev:client]  [937] multi webpack-hot-middleware/client?path=http://localhost:4301/__webpack_hmr webpack/hot/only-dev-server ./src/client.jsx 52 bytes {0} [built]
[development      ] [build:dev:client]  [938] (webpack)-hot-middleware/client.js?path=http://localhost:4301/__webpack_hmr 7.35 kB {0} [built]
[development      ] [build:dev:client]  [939] ./node_modules/querystring-es3/index.js 127 bytes {0} [built]
[development      ] [build:dev:client]  [942] ./node_modules/strip-ansi/index.js 161 bytes {0} [built]
[development      ] [build:dev:client]  [944] (webpack)-hot-middleware/client-overlay.js 2.21 kB {0} [built]
[development      ] [build:dev:client]  [949] (webpack)-hot-middleware/process-update.js 4.33 kB {0} [built]
[development      ] [build:dev:client]  [950] (webpack)/hot/only-dev-server.js 2.37 kB {0} [built]
[development      ] [build:dev:client]  [951] (webpack)/hot/log-apply-result.js 1.31 kB {0} [built]
[development      ] [build:dev:client]  [952] (webpack)/hot/emitter.js 77 bytes {0} [built]
[development      ] [build:dev:client]  [954] ./src/client.jsx 2.29 kB {0} [built]
[development      ] [build:dev:client]  [968] ./node_modules/babel-polyfill/lib/index.js 833 bytes {0} [built]
[development      ] [build:dev:client]     + 2196 hidden modules
[development      ] [build:dev:client] ℹ ｢wdm｣: Compiled successfully.
[development      ] [run:dev:server  ] [BABEL] Note: The code generator has deoptimised the styling of "/home/adithya/Prog/Plone/Contrib/plone-react/dist/server.js" as it exceeds the max of "500KB".
[development      ] [run:dev:server  ] Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in  React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs
[development      ] [run:dev:server  ] Sun, 25 Feb 2018 09:46:24 GMT plone-react:server:info  ==> 🚧  Webpack development server listening on port 4300

Hope the above information is enough to solve the problem.

@adithyaov Hey! Currently this repo is in development. The Plone team is working to fix and update the repo to bring back to working state. You can expect it to be up and running in a few weeks.

@ajayns As a part of GSOC, I want to work on "plone-react", Contributing a little to "plone-react" will familiarize me with a lot of things and will help me in writing my proposal. I might not have a few weeks :-P

@adithyaov  You should try deleting node_modules folder and re run yarn command. This worked for me, I was having  the same problem before. :)

@nileshgulia1
I just restarted the entire process, Now, I can access
localhost:4300
localhost:4300/login (Cant login though)
localhost:4300/register (gives me the same error Something went wrong: Cannot read property 'replace' of undefined)
Do you know where this error can be caused? Maybe I will try fixing that file.
Thank you.

@adithyaov  Actually the development is going on the repo so some of the links are broken you should not care about this, as it will be fixed automatically after the React-sprint on march 12 hopefully.

@adithyaov  I feel this issue can be closed now?


Update the tex_clean method

Separate patterns into array and check for errors on cleanup.
Add an extra pattern where extra whitespace before empty lemmas is removed.
This is just a suggestion, but it makes it easier to add new patterns.

Don't merge this yet. I have found some bugs in the new pattern, that I will solve first.

It should work better now.

I now also added pattern to remove whitespace before punctuation that arises when punctuation is put on line on its own (typically after app entries).


Ensure that releases are not ran in parallel

This resolves builds beign pushed to maven in the wrong order: see the final few 13a builds here: https://meta.fabricmc.net/v2/versions/yarn/
This happens when PRs are merged all at once and its a race to release.

Seems to have built fine, going to merge this, let me know if there are any issues.

This seems to work well, I am going to bump the timeout on it however as 15 mins was pushing it when merging 6 prs.


Create Attendance Event Object and Fields

New HEDA Object: We are creating object and fields to support attendance events.

What is the motivation / use case for changing the behavior?
An attendance event records a student’s presence/participation in either an entire school day, or class period. Can represent both absences as well as tardies. Attendance can be assumed if no absence is reported. For our MVP we are focusing on storing attendance NOT taking attendance.

Note: This work item will focus on schema only. Logic/Automation are slated for farther down the road.

Acceptance Criteria
TBD

Hi @aligeez @JasonFitzy, mind if taking a quick review on this Github issue before I lurch it? Thank you!

@xinnanlisf - Good to go now. I edited it a bit.

@aligeez thanks, I will go ahead and lurch.

**lurch: add

Tracking W-031541

Included in beta release 1.78 (Beta 4)

Included in production release 1.78


Backport 1.3: Correct memory leak in ssl_set_hostname

This is the mbed TLS 1.3 backport of https://github.com/ARMmbed/mbedtls/pull/871.

Reviewed, tested, approved and merged.


Full source code

Hi,
Can you provide full source code for this example? I've tried but my extension doesn't work, not sure what's wrong, I need your source code to compare. Thanks.

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

ID: 6e6cb0ed-c129-901c-10a2-909354aa562f
Version Independent ID: ceb10d41-b306-0d3f-ccb2-124a3ba69332
Content: Add a custom control to the work item form
Content Source: docs/extend/develop/custom-control.md
Service: unspecified
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

A bunch are over here https://github.com/Microsoft/vsts-extension-samples, but I don't see that particular one

Hi @vietkuong , all of our full samples are in the github repo that @nschonni has pointed out, if it's not there then we likely don't have it. What problem(s) are you seeing?

I think the full code for this sample is available here: https://github.com/Microsoft/vsts-extension-color-control

Going to close this issue for now - creating new samples and better ramp-up documentation is on the backlog for writing extensions so hopefully that will address some documentation gaps found here.


Open Home Component on application start

User Story
As a user, when I am logged in, and I start the web app, I want the #25 to show so that I can get started quickly.
Implementation
Steps to implement the feature:

[ ] function (in DataManager), that returns the user's data
[ ] function that return an Array of Dates, on which daily notes exist
[ ] function that returns today's daily note (and creates an empty one if it does not already exist)

My: write function, that (actually) creates/logins user account
atm: automatic login into testuser account


Analysis: functional area definition for Events component

Description
During PR #161, there was a useful discussion about the internal and external capabilities and responsibilities. It will be useful to further define these and use consistent terminology when discussing changes.
In scope
Better separation between the following two functional areas:

receiving, storing and querying Cloud Events from external sources, both apps and non-apps (event sink component?)
forwarding received Cloud Events to external event sinks ("subscribers")

Out of scope
No response
Additional Information
No response
Analysis
No response
Conclusion
No response

We have agreed on terms publish and  subscribe. For now we have not received any feedback that communication around events has been unclear,so closing for now.


Virtual kubelet metrics API

Description
This PR introduces the metrics API implementation in the virtual kubelet. The virtual kubelet exposes a new endpoint for retrieving the stats of the offloaded pods running in the remote cluster.

the vk iterates over all the namespaces currently natted
all the pods in each natted namespace in the remote cluster having a specific label (a reference to the offloading virtual kubelet) are listed from the metrics API server
the data structure used by the kubelet is built upon the remote data and is retrieved to the caller.

ref. #367

/rebase


Adding CEP 4.0.0 puppet module

Signed-off-by: sajith<EMAIL_ADDRESS>

Thanks Sajith for your contribution on CEP puppet module! We have merged it to the master branch.
We are now in the process of redesigning the puppet module structure by including some of the best practices used by the WSO2 DevOps, Automation, Private PaaS teams and the Puppet community. We will be documenting this soon and refining this puppet module accordingly.

@sajithshn Noticed that you have included jar files in the Puppet module. Could you please remove all those jar files? Any jar dependency should be deployed to Puppet master through a bash script or any other means. Those should not be hosted in Git repo.
Thanks.


feat: allow zero slice using func

fix #268

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

No unit test? 😱🤔

No unit test? 😱🤔

i haven't find where to add ut

Let's wait for a maintainer.
But good thing you took this issue

As it's about slice, I would say here maybe
https://github.com/uber-go/nilaway/blob/main/testdata%2Fsrc%2Fgo.uber.org%2Fslices%2Fslices.go

As it's about slice, I would say here maybe
https://github.com/uber-go/nilaway/blob/main/testdata%2Fsrc%2Fgo.uber.org%2Fslices%2Fslices.go

ok, i will check it


encoding/*: allow exporting comments

Is your feature request related to a problem? Please describe.
Sometimes 3rd party systems require annotating configurations via comments.
For example, cloud-init requires that its yaml files have a she-bang line like this:
#cloud-config
<some yaml stuff>
......

See here https://cloudinit.readthedocs.io/en/latest/topics/examples.html for more examples.
Describe the solution you'd like
File test.cue
//cloud-config
foo: "bar"

hello: {
        // occupy
        world: "from mars?"
}

when exported via command cue export --out yaml --preserve-comments test.cue should produce something like this:
# cloud-config
foo: bar
hello:
  # occupy
  world: from mars?

Describe alternatives you've considered
There is an easy workaround when wrapping cue-cmd via bash script. It's suboptimal but it's not a blocker.
Additional context
Bonus point: Some comments may be relevant to cue language itself thus we do not really want to export them.
It could be nice to have a convention to export whitelisted comments. For example, only comments starting from /// will be exported.

This request seems reasonable to me for one main reason: we import comments, hence we should export them for round-trip-ness' sake if nothing else.
FWIW it's not possible to control the export comments at all (unless I am missing something): neither through cmd/cue, cue cmd, nor encoding/*.

@myitcv I agree that this makes a lot of sense for the round-trip-ness. I also did not see any way to export comments. My example above was a modified cue ( add cue.Docs(true) to this line https://github.com/cue-lang/cue/blob/master/pkg/encoding/yaml/manual.go#L38).
A few thoughts after poking around

The example above adds a space within the comment string, I think we might consider removing the space here: https://github.com/cue-lang/cue/blob/master/internal/encoding/yaml/encode.go#L300 though i
Tt might be worth considering how we might preserve the spacing / padding in the original sources better. Does this need to happen for import as well?
My initial thought was to use the Options variadic func args, much like Syntax from the API since that is used where the change is needed. That being said, I'm not sure it makes sense to open up the Options that much for the encoders, as incorrect Options may cause errors in the encoder itself.
Does it make sense to allow different options depending on the output? I was mainly thinking that the CUE output could support the full set of Options, not sure if there is any overlap with CUE output and the feature request to support single file output for CUE we have seen. Protobuf looks to have some extra flags for exporting already.

Makes a lot of sense. One alternative API is to export comments when used with def. I'm surprised that cue def --out yaml doesn't already export comments, actually.

I just ran into this problem and submitted a PR for it based on the approach suggested by @verdverm. I'm happy to adjust it if a different approach is preferred.
https://github.com/cue-lang/cue/pull/1549

@felixge I was about to land your PR but first needed to fix a test case. In fixing that, I realised that perhaps this issue isn't as straightforward as it might seem.
Here's the test case in question: https://review.gerrithub.io/c/cue-lang/cue/+/536265/2/cmd/cue/cmd/testdata/script/cmd_github.txt
Note all the comments that have appeared in the YAML output for the test (a Github Actions file). Those comments aren't really relevant to the output file - they're really there to describe the schema of the actions file, not the final rendered result. In the final rendered result, I'd imagine that more repository-specific comments would be appropriate.
Choosing a heuristic that decides which comments to be rendered in the final concrete output is tricky and will need some design input. Perhaps we might need to use an annotation hint; it could even be that it's not, after all, appropriate to include comments in rendered output.
So I've left the NeedsDesign label on this issue and removed the GoodFirstIssue label because it's clearly not entirely trivial!
Thanks for your input. Any further thoughts on this would be appreciated.

@rogpeppe I agree that this feature would benefit from a sophisticated design. But in the short term, I don't see the harm of letting the user chose to either include comments or not when they invoke the cue command. It seems like most use cases would be well served by this?

So long as we're in a NeedsDesign stage - got here because I was looking to produce comments based whether CUE processing of input data had fallen back on default values.
I realize that's a whole extra can of worms, but perhaps something like this could be made to work:
struct: {
  value: 17 @comment("from default")
}

Hi Guys - Are there any ideas of how to proceed with this issue? It would be so nice to be able to export comments from a cue file.

This might be slightly out of scope, but...
To add a small comment, the OP brought up shebangs, and there's at least a few places where shebangs are used regardless of their validity in the normal export format. The one that comes to mind is Saltstack -- if you're using anything other than the Jinja|YAML renderer, you need a shebang at the top to designate it, eg, #!json, even though that isn't valid JSON. (And hypothetically you'd put a #!cue line at the top if there's a working cue renderer for Saltstack.)
So maybe in addition to comments there might need to be some consideration or syntax for fixed annotations of whatever format in outputs? It may affect importing if you want to be able to round-trip data, too, though at least in the specific case of shebangs they're generally the first line so it's skippable...

@jpluscplusm described my need for round-tripping YAML comments very concisely here:

please let me round-trip a given YAML file to CUE and back again, so that I can actually have 2 sources of truth, and give my 2 camps of users (team YAML vs team CUE) a way to work in their encoding of choice, without [bothering] the other set of users. /Whatever/ that implies, please just let my users get on with work, whilst I incrementally convince team YAML folks to defect to team CUE, and prevent pointless arguments about this stuff at the user-to-user level.

Source: https://cuelang.slack.com/archives/CLT4FD7KP/p1694007965956239

@jpluscplusm described my need for round-tripping YAML comments very concisely here:

please let me ...

For completeness, I will just mention that this paragraph was written and posted in the context of me role-playing as David, projecting my impression of their underlying, real-world requirements. I wasn't expressing what I needed, personally! :-)

I began importing https://github.com/cue-lang/cue/pull/1549 into Gerrit in separate commits - first testdata files, then the Docs API fix that Felix spotted, and then after would come the enabling of comments when encoding YAML. See https://review.gerrithub.io/c/cue-lang/cue/+/1199690.
The Docs change uncovered a bit of a hidden problem: we never intended for cue export to output comments by default, as can be seen in filetypes/types.cue. It just does for cue export --out=cue now due to the bug that Felix is fixing in the PR.
It's also reasonable for a user to want to either export with or without comments, so we should support both modes - this would require a new flag, at least to enable or disable the inclusion of doc comments. This would also require threading this option through the internal/encoding Go API as well as each of the encoding Go APIs, such as encoding/yaml.
Moreover, @rogpeppe and @mpvl argue that a boolean flag and option might not be enough. If CUE values unify concrete data with schemas, for example, they might both have doc comments. In some cases the user might want to output the comments from just the data, or from just the schema, or both combined. So perhaps a flag where one can do --doc=all, --doc=schema, --doc=data, --doc=schema,data, and so on would be better.
I will continue with this work step by step, but because we want to add the flag before "fixing" cue export to not output comments as intended, and multiple encodings are involved, this may take me some time.
I will use this issue to track the ability to enable exporting comments via cmd/cue and each of the encoding Go APIs. Some encodings simply don't support encoding or decoding comments yet, so that should be tracked separately, e.g. https://github.com/cue-lang/cue/issues/3342. This issue originally used YAML examples, so I'll aim to support comments in YAML as the first end-to-end example of this working.

Hey @mvdan , my team can really use this feature in our project. Do we expect this to be available any time soon? Thanks!

@KeranYang after getting TOML to a working state and other work, this is back near the top of my TODO list. I can't promise any particular timeline but I hope to make progress here in the coming weeks.

Thank you very much @mvdan . Looking forward to it.


Autorest Regen Preview to 3.0.0-alpha.20230712.5 by Mingzhe Huang from refs/pull/3584/head

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

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Health.Insights.ClinicalMatching

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Health.Insights.ClinicalMatching Azure.Health.Insights.CancerProfiling Azure.Analytics.Purview.Sharing Azure.Analytics.Purview.Share

Those 4 SDKs are all in beta versions. We're OK to do the change in interface.

close since gen1 dataplane is not supported


Stamina and HP bar disappear when inventory is opened.

Whenever the inventory is opened, the HP bar and the stamina bar disappear and don't reappear until I log out, and then log back into a world. This issue just appeared after the last update.

Can confirm. It just disappears - the bug did not occur for the last week and without any change to the game or any mod version today. If you need any logs just say which or what.

@firez2469 Check if your Render Scale is not Native or 100% - i changed mine to 95% and then the bug occured. So changing it back to Native fixed it.

Yeah, Native scaling should fix this.


chore: update dependencies (PROOF-642)

Update catch2 and rules_cuda dependencies.
Also remove empty tests as the latest version of catch2 fails if there are no test cases.

:tada: This PR is included in version 1.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: