fwrite(): send of 4 bytes failed with errno=32 Broken pipe

Sometimes I have an error in vendor/react/stream/src/Buffer.php (line:86)
fwrite(): send of 4 bytes failed with errno=32 Broken pipe
in this line:
$sent = fwrite($this->stream, $this->data);
What should I do? Thanks.
Info:
PHP version 5.6.26.
composer show -i:
cboden/ratchet            v0.3.5 PHP WebSocket library
evenement/evenement       v2.0.0 ├Йv├йnement is a very simple event dispatching library for PHP
guzzle/common             v3.9.2 Common libraries used by Guzzle
guzzle/http               v3.9.2 HTTP libraries used by Guzzle
guzzle/parser             v3.9.2 Interchangeable parsers used by Guzzle
guzzle/stream             v3.9.2 Guzzle stream wrapper component
monolog/monolog           1.21.0 Sends your logs to files, sockets, inboxes, databases and various web services
psr/log                   1.0.2  Common interface for logging libraries
react/event-loop          v0.4.2 Event loop abstraction layer that libraries can use for evented I/O.
react/socket              v0.4.3 Library for building an evented socket server.
react/stream              v0.4.4 Basic readable and writable stream interfaces that support piping.
react/zmq                 v0.3.0 ZeroMQ bindings for React.
symfony/event-dispatcher  v3.1.6 Symfony EventDispatcher Component
symfony/http-foundation   v3.1.6 Symfony HttpFoundation Component
symfony/polyfill-mbstring v1.2.0 Symfony polyfill for the Mbstring extension
symfony/routing           v3.1.6 Symfony Routing Component

Can you provide more of the stack trace? The is an error that shows up in your logs but everything continues to work, correct?
The error message is when a peer attempts to send data over a closed connection. Odds are this is just the result of a race condition that can be ignored. (The client closed the connection just as the server was sending it data).

Stack trace:
#0 [internal function]: React\Stream\Buffer->handleWrite(Resource id #171646, Object(React\EventLoop\StreamSelectLoop))
#1 /var/www/myproject.com/protected/ratchet/vendor/react/event-loop/src/StreamSelectLoop.php(240): call_user_func(Array, Resource id #171646, Object(React\EventLoop\StreamSelectLoop))
#2 /var/www/myproject.com/protected/ratchet/vendor/react/event-loop/src/StreamSelectLoop.php(201): React\EventLoop\StreamSelectLoop->waitForStreamActivity(NULL)
#3 /var/www/myproject.com/protected/ratchet/bin/push-server.php(33): React\EventLoop\StreamSelectLoop->run()
#4 {main}

The is an error that shows up in your logs but everything continues to work, correct?

Yes, if an error occurs, the work does not stop.

Try updating your dependencies. There was some logic change in the last update reactphp/stream with writing to stream buffers. (https://github.com/reactphp/stream/compare/v0.4.4...v0.4.5).
Also take a look at this unit test which is testing the exact error you received. The test is writing to a closed stream and expecting the error you received back. This is what leads me to believe this is an error you can ignore.

Hello from 2020
This issue is still persists with me.
2020-01-02 00:51:34 [-][-][-][error][RuntimeException] ErrorException: fwrite(): send of 4 bytes failed with errno=32 Broken pipe in /home/alua/api/vendor/react/stream/src/WritableResourceStream.php:118
Stack trace:
#0 /home/alua/api/vendor/react/event-loop/src/StreamSelectLoop.php(252): React\Stream\WritableResourceStream->handleWrite(Resource id #671746)
#1 /home/alua/api/vendor/react/event-loop/src/StreamSelectLoop.php(211): React\EventLoop\StreamSelectLoop->waitForStreamActivity(73973)
#2 /home/alua/api/vendor/cboden/ratchet/src/Ratchet/Server/IoServer.php(74): React\EventLoop\StreamSelectLoop->run()```

Happens every few weeks..

    "cboden/ratchet": "^0.4.1",

What should I try ?


uniqueName error when passed a number

Sometimes uniqueName can get called with a number. In this case, an error is thrown.
name.toLowerCase() is not a function

Will send pull request that fixes this shortly.

Thanks for the MR


[Docker] Upload Docker Images for Reproducing MLSys'21 Artifact to DockerHub

Just in case if people don't wanna rebuild those images again.

native1.6-cu10.2:
docker pull wangshangsam/hfta:mlsys21_native1.6-cu10.2

nvidia20.06
docker pull wangshangsam/hfta:mlsys21_nvidia20.06

@nixli @ypm1999 I'm wondering if you could help to check if those two images work, then update docs/mlsys21/a100_throughputs.md and docs/mlsys21/v100_rtx6000_throughputs.md accordinly (just say something like "if you don't want to build the image manually, you can pull our pre-built image by xxx")?

I am checking rtx6000, if you have not checked a100 yet, I can do that as well :)

I am checking A100, it works well up now

same for RTX6000, I'll update the README

@ypm1999 I don't see docker pull wangshangsam/hfta:mlsys21_native1.6-cu10.2 being mentioned in #27 .
@nixli I'm wondering if you could update https://github.com/UofT-EcoSystem/hfta/blob/main/docs/mlsys21/a100_throughputs.md#build-docker-image as well?

added in #34


Introduction of alembic caused regression

🐛 Describe the bug
Introduced in 0.1.82, the introduced alembic migrations cause an unexpected error preventing normal operation.
I believe this is under the condition that your project is also using alembic.
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) table ec_chat_history already exists

https://github.com/embedchain/embedchain/pull/1273

Hey, sorry for the trouble. You can fix this issue by doing 'rm -rf ~/.embedchain' and it will work fine.

Confirmed this resolved the issue, thank you.


Update getting_started.md

Adding message size limit to page.
Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Add IndRNN

Feature request: Add IndRNNCell to flax's recurrent cells.

Independently Recurrent Neural Network (IndRNN): Building a Longer and Deeper RNN. CVPR 2018.

It currently has 1004 citations according to Google Scholar.
I can submit a PR for this.

One big factor against adding IndRNN to Flax is that neither Pytorch nor Keras provides this layer.


[BUG] fastf1.events returning incorrect country data for some events.

Describe the issue:
For some particular races, fastf1.get_event() returns unexpected country names. Particularly, I've seen this with Miami GP and Emilia Romagnia GP. I'm not sure if this is a feature or a bug, but having accurate country names is crucial for the purpose I'm using it for.
Reproduce the code example:
event1=fastf1.get_event(gp=6, year=2024)
event2=fastf1.get_event(gp=7, year=2024)
print(event1['Country'])
print(event2['Country'])

Error message:
Miami
Emilia-Romagna

That was not intentional. It's fixed now in the data backend, so it should just work for you now and return "United States" and "Italy" respectively.


README.MD: Changed links on Travis and David DM badges to new reposit…

…ory.

It has already been changed.

Yeah- by me. I changed the image URLs but not the links. Look at the PR I sent.

Thanks!


Backlog refinement has placeholder content

There is no real content in this section, only place holder content

duplicate


Feature Request: Amazon EKS custom security groups, option to not modify

What kind of request is this (question/bug/enhancement/feature request):
Feature Request
Description:
Currently you can select your own Security Group when creating an Amazon EKS cluster however the Security Group settings will be changed after the cluster is deployed.  Specifically the outbound rules are changed to allow only 443 and 1025-65535.  This feature request is for the ability to have the chosen Security Group unmodified if the user has specific rules they want used instead.
gzrancher/rancher#6173

These are not modified in EKSv2. @sowmyav27 please validate.

Blocked by issue - https://github.com/rancher/rancher/issues/28144

Verified on master-head commit id: 9b0dd20b7

Deploy a hosted EKS cluster from rancher.
Select subnets and security groups.
Create the cluster. When the cluster comes up Active, verified that the security group selected during cluster creation, the outbound and inbound rules are not changed.


The script to install ior, fio, smallfile looks broken for RHEL 7.6 ami (ami-011b3ccf1bd6db744)

Errors that I got after running script-
#python ~/smallfile/smallfile_cli.py
ERROR: you must ensure that shared directory /var/tmp/smf is accessible from this host and every remote host in test
#ior
bash: ior: command not found
fio also failed to install but I fixed it using --skip-broken

Updated entire workshop to use Amazon Linux 2 and install smallfile manually.


Rename DDoS to DoS

Distributed Denial of Service (DDoS) is just one form of a denial of service attack. The constraints protect even against a single non-distributed attack.
https://en.wikipedia.org/wiki/Denial-of-service_attack

@dbrgn , Thanks for the correction. Can you please send the PR to the develop branch?

@rousan updated!

Thanks!


Apply clang-format for unified coding-style

Today, the coding style check is a manual review process, so I wondered if this could not be done by a static code analysis tool to offload that work from @mcallegari as our maintainer.
I first tried how far we could get with the well-established indent program, but style recommendations are too far from the current code and configuration options are not sufficient to get closer.
So I shifted to clang-format (version 14 as in Ubuntu 22.04) and came quite close. Nevertheless, the build system would have version 10 which does not support required options and clang-format is currently moving fast, so I fixed that to version 14.
Note that therefore the additional myci-actions/add-deb-repo@*, entry needs to be allowed in the actions configuration.
I applied two configurations, one for *.cpp and *.h and another one for *.js.
Let me know what you think.

Is it worth it or in the way when developing code?
Is it the right approach to put it into unittest.sh (rather than as a Make target)?
Is it close enough to the current formatting?
Can we live with how it wants the JS files to be formatted?

Hi, I'm not sure about this.
Some changes are good some other I don't like, especially QString &var vs QString& var.
See https://wiki.qt.io/Qt_Coding_Style
Except for curly braces (which for Christ sake they go on newlines!) I almost agree with that as it is.
Can you please re-run the parsing with adjusted settings?
Thanks

Anything that makes the code easier to maintain is definitely a plus. @mcallegari would you approve if we used their clang profile?
https://code.qt.io/cgit/qt/qt5.git/tree/_clang-format

The QLC style to be found in the current files differs significantly from the rules to be found at https://code.qt.io/cgit/qt/qt5.git/tree/_clang-format.
I'll modify the QLCplus rule set to get as close to the existing code with taking the original QT rules in mind and upload a re-ordered version of the original QT rules here, so they can be compared to the QLCplus configuration. It can then be decided what we want to see (with my current assumption: as few as possible changes to the existing and established code, which will then be consisten).

@hjtappe sorry but I've got some more things that I would adjust:

switch/case should look like this (nad yes, I don't like Qt style in this case)

switch (var)
{
    case 1:
    {
        // parenthesis needed only if a variable is defined in this block
    }
    break;
    default:
    break;
}

defines/includes should start from the beginning of the line unless nested to other defines
please leave aligned enum/define values, they're easier to read. Example:
https://github.com/mcallegari/qlcplus/blob/master/engine/audio/src/audiocapture.h#L34
https://github.com/mcallegari/qlcplus/blob/master/engine/src/function.h#L110
I saw multiple rows packed into a single line. Here there should be a limit to text columns. I think 80 columns is a reasonable value

Hello,

@hjtappe sorry but I've got some more things that I would adjust:

No problem. You can even still decide it that is the way to go or to cancel this and go another way. ;-)
Otherwise, please allow the additional myci-actions/add-deb-repo@*, entry in the github action, so github actions will be willing to build the code.

* switch/case should look like this (and yes, I don't like Qt style in this case)

I think that's now the case.

* defines/includes should start from the beginning of the line unless nested to other defines

Can you point me to a file where you see a misbehaviour, please? Looking at e.g. engine/src/doc.cpp, it indents according to the preprocessor expression level. Do you refer to that it should always start in the first column?

* please leave aligned enum/define values, they're easier to read. Example:
  https://github.com/mcallegari/qlcplus/blob/master/engine/audio/src/audiocapture.h#L34
  https://github.com/mcallegari/qlcplus/blob/master/engine/src/function.h#L110

I think I found the switch.

* I saw multiple rows packed into a single line. Here there should be a limit to text columns. I think 80 columns is a reasonable value

80 will have a significant breaking impact on code. Other standard configurations use 100 rather than 120. I have set that - please take another look if that could also fit our needs.

Hey @hjtappe sorry for leaving this behind!
I was thinking: is it possible to split this into several PRs or separate commits?
First I would tackle QString& var vs QString &var (same for *) and if( vs if ( (same for while, for, foreach, switch, etc)
I think that would cover already many cases in the existing code.
Then we can discuss other specific styles and the application of an automated style check.
Might help me to review this.

Hello @mcallegari, technically this does not work with the indentation program. It can't be told to apply only one set of rules, as far as I see.
I could nevertheless accomplish that with small "sed" scriptlets and run that on the current master before a careful review. I'll give that a try.
I wanted to proceeed with this and some other topics in the previous month, but life became too busy the last months. I think I can address this again next year and will set it to draft until I have made the next step.

Hello @mcallegari,
after some research - it is not possible to adress only the pointers indentation only. For a script solution, the pointer "wildcard" character is used in too many places and need semantics understanding of the character environments.
The tools helping in indentation all cannot be configured to fix only the pointers.
So let's approach the situation from another side.
So I provide the project with a script to help checking single files or directories and also to use for the indentation itself. This way, you (and whoever works to unify the code) can selectively update the code that is currently worked on.
-c|--check            Script mode: check (default) -h|--help             Print this help message -i|--indent           Script mode: indent -t|--target target    Build Target (qmlui|ui) default: qmlui -u|--unify            Add unified diff output
Later integration into unittest.sh and the build workflows is prepared but requires the clang-format is added to the commandline via Github actions permissions through myci-actions/add-deb-repo@11.
Does that work for you?

How about this instead of inventing our own script?
https://github.com/google/styleguide/tree/gh-pages/cpplint
I haven't tried it yet but it looks you can pass specific filters from command line


JWT Token expiry can not be configured when cache is enabed

See the doc [1],  It is mentioned
" If caching is enabled for the Gateway Manager or the Key Manager, the JWT expiry time is the same as the cache expiry time by default."
When caching is enabled, expiry time must be slightly larger than the default cache timeout value.  If cache time out is 15m  JWT expiry must be 20m (15m + X) as JWT is passing to the external system.  If it is not, it would be failed  even if time is sync.
As a fix,  when cache is enable,  we need to take the property in "JWTClaimCacheExpiry" as the expiry time & update the doc that "JWTClaimCacheExpiry" must be higher than the cache time out if cache is enabled.
[1] https://docs.wso2.com/display/AM210/Passing+Enduser+Attributes+to+the+Backend+Using+JWT#PassingEnduserAttributestotheBackendUsingJWT-ExpirytimeoftheJWT

Let's say the cache expiry time is 15 mins and JWT expiry is 20 mins. After 15 mins, we have to call the key manager anyway. We have 2 options at that point.

Generate a new JWT. - In this case, it's useless to have 20 min expiry time for the JWT as we regenerate it after 15 mins.
Give the same token - In this case, the JWT will be expiring in 5 mins and we will be adding it to a 15 min cache, which is a problem.

The ideal way to solve this is by considering a time skew when validating the JWT, considering network and other delays.


odo features reported in a inconsistent way

/kind bug
What versions of software are you using?
Operating System:
Win10Pro
Output of odo version:
odo v3.0.0-beta2 (c8e4458f4)

Server: https://api.sandbox-m2.ll9k.p1.openshiftapps.com:6443
Kubernetes: v1.23.5+9ce5071

How did you run odo exactly?
odo list -o json
odo describe component -o json
Actual behavior
odo list -o json reports the features as "runningIn": ["Dev"]
odo describe component -o json reports:
"supportedOdoFeatures": {
                        "dev": true,
                        "deploy": false,
                        "debug": true
                }

Expected behavior
Any logs, error output, etc?

they are reporting different things

odo list -o json reports the features as "runningIn": ["Dev"]

is the current status. It means that the component is currently running only in "Dev" mode.

odo describe component -o json reports:
"supportedOdoFeatures": {
                        "dev": true,
                        "deploy": false,
                        "debug": true
                }

Is reporting what "modes" or features are possible with the given devfile.
This tells you that you can run odo dev and odo dev --debug but the current devfile doesn't support odo deploy that means that it can never be in the  "runningIn": ["Deploy"]

You don't get me the issue is Dev vs dev which makes it more difficult to process by integrations

ah, so you mean the inconsistenci in the first letter capitalization?

this information is presented in 2 different forms: an array or a structured object

It is not the same information. For example, once we add support for devfile test commands then supportedOdoFeatures struct will also have test key. but runningIn will never show. test.
supportedOdoFeatures shows what odo commands/features are supported with the current devfile.
runningIn shows in what mode the current devfile is running in
Is the current state problematic?
We could change runningIn into a struct similar to supportedOdoFeatures. The benefit will be that you will see all possible running modes.

The only issue is have is that I need 2 different parsing code for the same information even if one will evolve in the future

The only issue is have is that I need 2 different parsing code for the same information even if one will evolve in the future

That is the thing. They are not the same information.

TBH on my side they are processed quite equally eg menu to stat dev mode is enabled if devfile has dev support and if dev mode is not running for the component.

runningIn: {"dev": true, "deploy": false}


ui error page doesn't honor the slack settings in config

Describe the bug
Temporal UI error page doesn't honor the slack settings in the config.
To Reproduce
Steps to reproduce the behavior:

break the ES integration with frontend pod by feeding wrong credentials or not creating indexes
load UI page and you will see 500 error page and in that there will be a link to slack

Expected behavior
href should use the slack url present in the config.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [macOS]
Browser chrome
Version [2.0.1]

Additional context
Add any other context about the problem here.

@feedmeapples sorry should have been a bit more explicit.
https://github.com/temporalio/ui/pull/519/files introduced FeedbackURL in the settings. I meant can we use this on the errorPage as well.

right, @canvanooo should we show the Feedback button on the error page as well?


failure with dyhead swin onnx model to tensorrt engine with FP16 using mmdeploy

Discussed in https://github.com/open-mmlab/mmdetection/discussions/9139

Originally posted by vedrusss October 25, 2022
Hi!
I'm trying to convert dyhead swin based model from onnx to tensorrt engine in fp16 mode using mmdeploy converter:
python tools/onnx2tensorrt.py  configs/mmdet/detection/detection_tensorrt-fp16_static-1280x1920.py detection_tensorrt_static-1280x1920/fp16/end2end.onnx detection_tensorrt_static-1280x1920/fp16/end2end
and running in following error:
-------------- The current device memory allocations dump as below --------------
[0]:34359738368 :HybridGlobWriter in reserveRegion: at optimizer/common/globWriter.cpp: 246 idx: 28 time: 0.000158613
[0x302000000]:11324620800 :HybridGlobWriter in reserveRegion: at optimizer/common/globWriter.cpp: 224 idx: 23 time: 0.00316042
[0x7f83c0000000]:29493600 :DeviceActivationSize in reserveNetworkTensorMemory: at optimizer/common/tactic/optimizer.cpp: 4603 idx: 8 time: 0.000331153
[10/24/2022-18:37:08] [TRT] [W] Requested amount of GPU memory<PHONE_NUMBER>8 bytes) could not be allocated. There may not be enough free memory for allocation to succeed.
[10/24/2022-18:37:08] [TRT] [W] Skipping tactic 4 due to insuficient memory on requested size of<PHONE_NUMBER>8 detected for tactic 31.
Try decreasing the workspace size with IBuilderConfig::setMaxWorkspaceSize().
[10/24/2022-18:37:08] [TRT] [E] 2: [pointWiseBuilder.cpp::splitVectorizedHub::277] Error Code 2: Internal Error (Assertion !never(a.z >= 0) failed. )
Traceback (most recent call last):
File "tools/onnx2tensorrt.py", line 73, in
main()
File "tools/onnx2tensorrt.py", line 58, in main
from_onnx(
File "/root/workspace/mmdeploy/mmdeploy/backend/tensorrt/utils.py", line 225, in from_onnx
assert engine is not None, 'Failed to create TensorRT engine'
AssertionError: Failed to create TensorRT engine
The actual available GPU memory onto my device is 16Gb and it does support FP16.
I'm able to obtain the tensorrt engine for the same model in FP32 mode and cannot find out the reason why FP16 doesn't work.
Are there any nuances with using mmdeploy and mmdetection models for obtaining FP16 engines?

Maybe you can raise an issue in MMDeploy, MMdetection has deprecated onnx.

DyHead is not officially supported for ONNX export.


NCGenerics: it's not experimental

This PR promotes the experimental feature to a full language feature. Also fixes a bug where you could use the feature without the right flags in the swiftinterface file for feature-guarded declarations (rdar://127701059)

@swift-ci test

@swift-ci test


SOLR-16677: Updated Solr to use new Lucene 9.5 storedFields() API

https://issues.apache.org/jira/browse/SOLR-16677
Description
Updated the Solr to use IndexReader.storedFields() and IndexReader.termVectors() instead of Deprecated IndexReader.document() and IndexReader.getTermVector().
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

proposed CHANGES.txt:
SOLR-16677: Update Solr to use new Lucene 9.5 storedFields() API. This removes the use of ThreadLocal for stored field state, reducing heap usage especially for high-core-count, high-field-count, high-thread-count cases (Vinayak Hegde, Christine Poerschke, Kevin Risden, David Smiley, Michael Gibney)

@vinayakphegde if you'd like to be credited some other way, please let me know; and thanks for your work getting the ball rolling on this!

I plan to merge this tomorrow, pending feedback.


Min/max width and height in game config are ignored by Phaser.Game constructor

Version

Phaser Version: 3.60.0

Operating system: any (found on Windows 11)

Browser: any (found on Google Chrome)

Description

According both to Phaser documentation and TypeScript type declarations, we can pass minimum and maximum game dimensions to the Phaser.Game constructor using min and max fields either in the game config itself or in its scale field.
Yet in the actual instance of Phaser.Game the respective parameters (game.config.minWidth, game.config.minHeight, game.config.maxWidth, game.config.maxHeight) remain on their default values (0) as if we didn't initialize them at all.
`
Example Test Code

const game = new Phaser.Game({
    min: {
        width: 640,
        height: 360,
    },
    max: {
        width: 1280,
        height: 720,
    },
    // we'll try 'em both just to be sure:
    scale: {
        min: {
            width: 640,
            height: 360,
        },
        max: {
            width: 1280,
            height: 720,
        },
    },
})

console.log(game.config.minWidth, game.config.minHeight) // expected:  640 360, actual: 0 0
console.log(game.config.maxWidth, game.config.maxHeight) // expected: 1280 720, actual: 0 0

Additional Information

As far as I understand the way to fix this bug is to alter these lines in the source code:
https://github.com/photonstorm/phaser/blob/master/src/core/Config.js#L107
https://github.com/photonstorm/phaser/blob/master/src/core/Config.js#L112
https://github.com/photonstorm/phaser/blob/master/src/core/Config.js#L117
https://github.com/photonstorm/phaser/blob/master/src/core/Config.js#L122
from
this.minWidth = GetValue(scaleConfig, 'minWidth', 0, config);
this.maxWidth = GetValue(scaleConfig, 'maxWidth', 0, config);
this.minHeight = GetValue(scaleConfig, 'minHeight', 0, config);
this.maxHeight = GetValue(scaleConfig, 'maxHeight', 0, config);

to
this.minWidth = GetValue(scaleConfig, 'min.width', 0, config);
this.minHeight = GetValue(scaleConfig, 'min.height', 0, config);
this.maxWidth = GetValue(scaleConfig, 'max.width', 0, config);
this.maxHeight = GetValue(scaleConfig, 'max.height', 0, config);

@NikitaShpanko nice catch! I tested this locally and created a PR.
This is the first PR I create for this project so please let me know if I'm missing something. I noticed that there are some linting changes that can be made to that file as well

Thanks for opening this issue, and for submitting a PR to fix it. We have merged your PR into the master branch and attributed the work to you in the Change Log. If you need to tweak the code for whatever reason please submit a new PR.

Hey there - thanks for this fix. When can we expect it to go live? 😇

It will be part of the 3.61 release. I don't give timescales, sorry, but hopefully, within the next couple of weeks.


Need public-friendly min OS and device descriptions for M2 launch

We need to have the official OS and device requirements for iOS and Android, for the M2 launch.
They need to be written in a comms-friendly way for web pages and so forth, so in a way that a member of the public can understand what they need.

Testing has been working with numbers decided on at the beginning of 2022 based on coverage of the population.
iOS 12+ at that time covered 99% of users. (Could be more than that now.)
Officially been testing on 12+ but have run 11 with no problems.
Android 8+ hits about 94% of users.
SDK 30 has been the minimum that has been tested officially.

Proposed that we go with:
iOS 12.0 or later
Android 11 (Red Velvet Cake) or later   [this is the version of Android that aligns with SDK 30)

I think that is reasonable. Can adjust in future milestones if need be.

It may be worse than 46% since Android 12 can have either API 31 or 32. I don't know the amount of Android 12 users in Canada that have API 12.


Cake 4

I got dizzy trying to understand current travis build matrix. So I'll leave it to you to remove/update jobs for PHP 7.1.

Cheers, also just updated the travis build matrix :+1:


can make SESSION_SERIALIZATION_FORMAT = 'json' work

I'm using the following code to try to make SESSION_SERIALIZATION_FORMAT generate 'json' like data on the session folder.
Unfornutatelly the session files generated there are binary no json readable.
This is my code based on the docs
from flask import Flask, session
from flask_session import Session
from cachelib.file import FileSystemCache

app = Flask(__name__)
app.config['SESSION_TYPE'] =  'cachelib'
app.config['SESSION_SERIALIZATION_FORMAT'] = 'json'
app.config['SESSION_CACHELIB'] = FileSystemCache(threshold=500,
    cache_dir=pathlib.Path.home() / pathlib.Path(".workapp/session")
Session(app)

I'm using Python3.10

Hi there sorry for the late response. There are some possible reasons.
Technically I think in cachlib situation it is JSON within a file so it depends how you are viewing the file. If your IDE won’t view it you can try using redis or memcach locally.
Also if you have previous sessions existing they will be in the old format until you modify view the session object.
If there is still an issue when you use redis please let me know


X-Frame-Options' to 'sameorigin'

Hi everyone!
I followed the init config, and now, when i run the app, i'm getting this error:
Refused to display 'https://MY-INSTANCE.my.connect.aws/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
How can me fix it? i already added localhost and <IP_ADDRESS> to approved origins and nothing changed...

I had this a while back and drove me mad as I had added the origins etc but there was something wrong with my cloudfront config so I recreated it and solve the issue.If you are not using CF then check you S3 bucket policyOn 31 Oct 2022, at 23:47, Jonathan López Londoño @.***> wrote:
Hi everyone!
I followed the init config, and now, when i run the app, i'm getting this error:
Refused to display 'https://MY-INSTANCE.my.connect.aws/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
How can me fix it? i already added localhost and <IP_ADDRESS> to approved origins and nothing changed...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@jlopez0313 did you manage to solve this issue? I am having the same issue

if you have already allowlisted the domain, it could be that you are not logged in to your connect instance.
could you try login into connect instance first ( just by loading connect url in a new tab and login) then access the app in a embedded mode? if that works make sure you configure loginPopup option to true.
please let me know if that helps


for @ldecicco-USGS suggestion on #160

For #160. I think this is preferred vs delays, unless we are using those for another reason. It is @ldecicco-USGS 's suggestion of putting a transparent box over the category button to catch the mouse events.

I didn't pursue this any more yesterday and went with delays because I was realizing that even with the rectangle behind, you would still be "mousing out" of the button. This works but I don't understand how. That's why I didn't bother with it yesterday.
Also, fyi Alison is not available for reviews until monday (she's heads down on writing today)

Oh wait, I'm digging more and see that it's part of the button group so it's whether you mouseout of the whole group or not. A much cleaner solution than delays.


Dev

This PR adds the following changes:

a restartAfterRun field to run targets that restarts the editor after the runtarget is finished
A refactoring of how a vertex controller is loaded and meant to be extended.

Remember to update version number


Percentage calculation result not changed

I'm trying to use feature toggle with percentage rollout, but result not changed even I called 100 times.
Notice: for percentage greater than 50% will return true.
UI config

Handler code

Test request script and result.

Heya!
Are you using a client evaluated key? You can tell as it has a * in it. If so, it would help Chris if you output the curl result as it shows what the server is sending back, and makes sure it's not a server issue.
Curl -v "https:...../features?apiKey=key"
Thanks!

@rvowles for result

Hey again! Excuse me if i'm misinterpreting this, i'm reading that json payload :-)
So your userkey is your hashed percentage value - so you appear to have two sets of rules, those for user agentx and those for user eddy, which are exclusive of each other. agentx when applied to the murmurhash (its consistent so you get the same experience, agentx will always get the same percentage translation across all platforms) and will either be a hot or a miss. I don't see how agentx gets true here as there is no true value being sent.
eddy you have two rules for, but again, only one will ever be chosen, based on that conversion.
i'm not really clear on what behaviour you are going for here? if you want straight percentage rules, you need to remove the userkeys in your strategies, as it is percentages will only be applied to two people and they will never change...
I'm not sure if this helps?

HI @Peelz - have you had time to have a look? Not sure if we have helped enough?


Add xclim to PyPi

I'll be parking xclim on the PyPi in order to ensure that the name doesn't get taken. This will make it so that any person running Python will be able to download this library using the following command:
pip install xclim

The bdist wheel is now accessible on PyPi!


OR
“
Kafka Support:

I do not want Kafka support.
I want Kafka set up in my Polaris Cluster.
I want to use Amazon MSK next to my Polaris cluster.
“

Suggestion: add support for MSK to the AWS Service Operator (https://github.com/awslabs/aws-service-operator) and then use #7 to deploy it.


Adding support for serializing datetime.datetime instances

Discussed in https://github.com/streamsync-cloud/streamsync/discussions/40

Originally posted by jreyesr June 17, 2023
Hello! I've been exploring Streamsync (awesome tool, BTW!) and I found out that apparently datetime.datetime instances cannot be serialized and sent to the frontend.

Minimal example
import datetime
import streamsync as ss

initial_state = ss.init_state({
  "now": datetime.datetime.now(),
})

This causes the following error to appear:

Error
Serialisation error

Traceback (most recent call last):
  File "/home/reyes/.local/lib/python3.10/site-packages/streamsync/core.py", line 239, in to_dict
    serialised_value = state_serialiser.serialise(value)
  File "/home/reyes/.local/lib/python3.10/site-packages/streamsync/core.py", line 129, in serialise
    raise StateSerialiserException(
streamsync.core.StateSerialiserException: Object of type <class 'datetime.datetime'> (MRO: ['datetime.datetime', 'datetime.date', 'builtins.object']) cannot be serialised.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/reyes/.local/lib/python3.10/site-packages/streamsync/app_runner.py", line 120, in _handle_session_init
    user_state = session.session_state.user_state.to_dict()
  File "/home/reyes/.local/lib/python3.10/site-packages/streamsync/core.py", line 241, in to_dict
    raise ValueError(
ValueError: Couldn't serialise value of type "<class 'datetime.datetime'>" for key "now".

As far as I can tell, this is due to the serialization code not supporting datetime.datetime instances
Background: I ran across this when trying to replicate Streamlit's starter tutorial in Streamsync. This tutorial has a Pandas DataFrame with a datetime column (it's a special Pandas datetime class, but it eventually inherits from Python's datetime.datetime)
Adding support for this would let users display data that has timestamp-style columns, such as "created on", "event time" and such.
Is there any interest in letting users pass datetime instances to the FE? I don't see any issues or discussions mentioning it, but it may be because Streamsync is fairly new. Any ideas?

datetime.datetime is now serialisable in 0.1.9.


-i # does not start cluster mode!

Trying to run my nodejs app with pm2 in cluster mode. The app works fine with:
CMD ["pm2", "start", "yarn start", "--no-daemon"] start 1 instance in fork_mode
But with:
CMD ["pm2", "start", "yarn start", "-i", "10", "--no-daemon"] 10 instances are started, yet still in fork_mode and I get errors regarding ports being already in use. How to force cluster mode? Is there an argument I'm missing?

your problem is on command at dockefile.
Try to add this params in CMD line.
CMD ["pm2-runtime", "your-confir-file.js"]


2 -  As a registered player I can log in to my account so I am able to navigate through the main menu

[x] The menu consists out of the following components: Play, Leaderboards, Tutorial
[x] The menu has a sidebar with additional buttons: My Profile, Logout, About Us
[x]  The Player can click on each menu item and gets redirected to the corresponding part of the application
[x]  By clicking on a Logout button the player is logged out and gets redirected to the home
screen ("/")

e47a65f5eac58b01e7d0264294b8d1db2073d7db


Update set-operators.md

Description & motivation
Add a code example for union (as suggested in dbt-beginners)
Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

Checklist
If you added new pages (delete if not applicable):
NA
If you removed existing pages (delete if not applicable):
NA

Love this! One small requested change from me

Thanks for your suggestion.  This is added now 🙂


configure lsp

# Options passed to the LSP server
"pylsp.plugins.autopep8.enabled" = false
"pylsp.plugins.yapf.enabled" = false
"pylsp.plugins.mccabe_lint.enabled" = false

Passes expected structures into the pylsp initialization, but unclear how / if pylsp is interpreting those values (or if it requires a configuration change message), from reading through pylsp's -vv double-verbose logs... issue raised with pylsp.
FYI python-lsp-black adds that formatter to pylsp, which was the initial thing I wanted to configure. Disabling format-on-save in the normal lapce settings is another way to avoid undesired formatters.

.. issue raised with pylsp.

I'm not sure I follow, sorry. Is the behavior an issue with pylsp or with the plugin/lapce?

We hoping you'd figured out how to configure pylsp through this plugin's configuration file.

It's something like this. The dotted names in toml expand to expected nested structures on init. Hard to tell if the parameter names are exactly right.
[configuration.options.settings]
pylsp.plugins.autopep.enabled = false

The language server probably expects a workspace/didChangeConfiguration message instead of (only) the initializationOptions message supported by lapce.
Sending notification 'workspace/didChangeConfiguration'.
Params: {
    "settings": {
        "python": {
            "autoComplete": {
                "extraPaths": []
            },
            "envFile": "${workspaceFolder}/.env",
...

Seems indeed that no lsp parameters specified in the plugin toml under [configuration.options] has an effect. I disabled all linting capabilities and i still have linting warning displayed.

Unfortunately I think that came out when moving to the Volt plugin API. It might be a bit until I get a chance to look into it, but I'm open to PRs.

should it not be solved when the PSP branch is merged ?

With lapce 0.2.6 o ly autocompletion suggestion is working. There are no docstring popup, no warning etc although I have all installed.


[WIP] Upload file flow updates

Progress

[x] Clean up file upload (read) state
[x] Fix error uploads block mockup generation
[ ] UI update on file list item
[ ] UI update on Upload position (Because of this, suggest handle with MUP-49 altogether)
[ ] Allow remove file list item

Wrong branch name, will close this


golang filter: implement HeaderMap.Add

Commit Message: golang filter: implement HeaderMap.Add
Additional Description:
Risk Level: Low
Testing: contrib/golang/filters/http/test/golang_integration_test.cc
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/review @doujiang24

Oops looks like needs a main merge.
/wait


Plugin v0.6 with Java 1.6

Hi,
I am using Java 1.6 (mandated by the client). Trying to use this extremely helpful plugin to run grunt tasks, but keep running into the error below. I suspect it is because the plugin is built with a later version of Java. Any chance you could help me resolve this? Thanks.
com/moowork/gradle/node/NodePlugin : Unsupported major.minor version 51.0

Tried to compile the source using
"gradlew clean build", but run into this error:

com/moowork/gradle/node/task/NpmTask : Unsupported major.minor version 51.0

Changed the compile compatibility to 1.6. Should work now.


[android] branch.subscribe fired only when app is closed

Hi, i trying to handle branch events in my root level component like that:
componentDidMount() {
  branch.subscribe(({ error, params }) => {
    console.log(params)
    if (error) {
      console.log('Error from Branch'  + error)
    }
  })
}

I get an event, but only when app is closed (during first app launch). When app is open and i trying to visit some url or send deeplink by adb - nothing happens.
Also if I add to componentDidMount this handler:
Linking.addEventListener('url', ({ url }) => {
  console.log(url)
})

I able to see urls, but  branch.subscribe still doesn't log anything.
Can you help me with it? Probably I missed something

Hi @EugeneDraitsev were you able to fix your issue? I am encountering probably the same one: https://github.com/BranchMetrics/react-native-branch-deep-linking/issues/322.


Failed to send ticket transcript to the ticket creator

Describe the bug
Ticket transcript does not send to ticket creator
To reproduce
When send_to_user is configured to true, type is set to attachment and /settings set log_messages:True
User closes ticket and error is sent in console and transcript is not sent to ticket creator (the transcript still successfully sends in guild channel ID)
[WARN] Failed to send ticket transcript to the ticket creator
2021-11-09 18:03:11 [ERROR] ReferenceError: transcript is not defined
at TicketManager. (/root/bot/node_modules/AnonDev-org.discord-tickets_transcripts/index.js:271:15)
at runMicrotasks ()
Expected behaviour
Transcript sends to both ticket creator and guild channel as configured.

Yes, I am aware of this bug. Will try to fix it when I will have time.

Does someone know what's wrong there?

Fixed in the new version - https://github.com/AnonDev-org/discord-tickets_transcripts/releases/tag/1.2.4

Now it should be completely fixed - you can choose if you want to DM the user when ticket was closed and if you want to include also transcript there or not


Retain cycle

There is a retain cycle that avoids to release the memory of the view controller using the PeekPop. The references to view controller and delegates inside the library should be weak.

Also for devices < 6S the gesture should be removed from the view in the deinit, otherwise the memory of the whole control will never be released.

I just submitted a pull request ( #21 ) to fix the delegates not being weak. I'm slightly confused about what you're talking about in the second comment though. Where exactly should the gesture be removed from the view?

Merged and released as 0.1.5. Thanks again @MrAdamBoyd.


Ab0 is missing

You are missing Ab0

actually the piano has 88 keys and it beggins from A0 Ab0 is not in the piano


skip flaky SignalR test: ErrorDuringPollWillCloseConnection

see #8138 for discussion on test priority and re-enabling

Blocked by https://github.com/aspnet/AspNetCore/issues/8182 (ironic...)

/azp run AspNetCore-helix-test


Explain D as a general-purpose programming language

From<EMAIL_ADDRESS>While D isn't a "scripting language" as stated in the thread, it can be used literally anywhere and for anything nowadays and thus imho "general-purpose" is a better description than "systems"
FWIW C++ is a "general-purpose" programming language as well. From Wikipedia:

C++ is a general-purpose programming language. It has imperative, object-oriented and generic programming features, while also providing facilities for low-level memory manipulation.

CC @aG0aep6G

Well, this definitely needs W&A's approval :) @WalterBright @andralex

What do you think about adding below something along the lines of:
"D scales from one-off scripts, through high-level application programming all the way down to low-level systems programming tasks like implementing operating system kernels." ?

Let's do this:
D is a general-purpose language with static typing, systems-level access, and C-like syntax.

Done.

Followup to avoid excessive hyphenation with the new text: #1783.


Add support for packetdiag and rackdiag

See https://github.com/yuzutech/kroki/pull/51

fixed in https://github.com/yuzutech/kroki-cli/commit/b802f44b870d62cdd631f2dfd6bd9af056778728


Fix and extend documentation

A few improvements to the documentation, things that were unclear to me as and outsider of this project:

You need to set AWS_REGION instead of AWS_DEFAULT_REGION, this is specified in the official docs as well: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-region.html
the controller needs either credentials or a role to read from AWS Secrets Manager, it's kinda obvious but I feel like this belongs in the doc anyway
small nitpick since it's not mentioned anywhere but supported, adding namespace to the example as an implicit option

@napcae thanks for this PR. Closing without merging. Please see comments above.


skbio.stats.gradient unit test failure

With the latest version of the natsort package, the following skbio.stats.gradient unit test fails:
======================================================================
FAIL: test_make_groups_natural_sorting (skbio.stats.tests.test_gradient.GradientANOVATests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "skbio/stats/tests/test_gradient.py", line 740, in test_make_groups_natural_sorting
    self.assertEqual(ga._groups, exp_groups)
AssertionError: defaultdict(<type 'dict'>, {'Col2': {'-42.0': ['a1'], '5': ['a10', 'a-10'], '1.0': ['a2'], '2e-5': ['a11.0']}, 'Col1': {'foo': ['a2', 'a11.0', 'a-10'], 'bar': ['a1', 'a10']}}) != {'Col2': {'-42.0': ['a1'], '5': ['a-10', 'a10'], '1.0': ['a2'], '2e-5': ['a11.0']}, 'Col1': {'foo': ['a-10', 'a2', 'a11.0'], 'bar': ['a1', 'a10']}}

@josenavas is this a legitimate failure or does the test just need to be modified to be less strict?

@jairideout I'm unsure on what to say. It all comes down on how natural sorting is defined. It looks like in this latest version, natsort changed the definition of natural sorting.
Before, the correct sorting was: ['a-10', 'a10'], but now is sorting those strings like this: ['a10', 'a-10']. Those strings represent sample names and they sorting is used to state the sorting in the gradient.
If we agree with natsort definition of natural sorting, then we should simply change the test. However, if we think that the previous definition is correct, we will need to implement our own natural sorting...
IMOO, I would use natsort, as I'm sure they have good reasons to have changed that, probably useful to take a look to their changelog?
@antgonza do you have any thoughts on this?

Agree on following natsort definition.

@josenavas since the difference is purely cosmetic, I will update the tests and bump the minimum version.

@ebolyen note that the difference is not purely cosmetic. It actually defines the order in which the samples should be analyzed. That's why I was rising the concern about the "correct" natural sorting.
In that case, it should be ok, but if natsort keeps changing their definition of "natural sorting" it is possible that the analysis won't be reproducible. At this point it is ok, as AFAIK, this code has not been used anywhere (it is some analysis that @antgonza and I where doing, but it is right now on the backlog). This is used for time series analysis.

@josenavas They say this:

The default sorting algorithm for natsort has changed in version 4.0.0 from signed floats (with exponents) to unsigned integers. The motivation for this change is that it will cause natsort to return results that pass the "least astonishment" test for the most common use case, which is sorting version numbers. If you relied on the default behavior to be signed floats, add alg=ns.F | ns.S to your natsort calls or switch to the new realsorted function which behaves identically to the older natsorted with default values. For 99% of users this change will not effect their code... it is only expected that this will effect users using natsort for science and engineering. This will also affect the default behavior of the natsort shell script.

Out of curiosity, why does the sample id have any bearing on the order of analysis? Doesn't that imply I can manipulate the results by changing ids? (Or perhaps I completely misunderstand where this id comes from)

The default behavior if the user doesn't provide a column for sorting their values it's using the sample ids. Anyway, if the user provides a column to sort the samples, we cannot make sure that we are using a numeric column, which will lead to the same behavior.
Given that they point out that this will change the results on science and engineering, I think we should start using their new realsorted function, which will output the same results.

I think we should start using their new realsorted function, which will output the same results.

:+1:, and update setup.py to rely on natsort >= 4.0.0. Is anyone available to work on a PR with this fix?

At this point it is ok, as AFAIK, this code has not been used anywhere (it is some analysis that @antgonza and I where doing, but it is right now on the backlog). This is used for time series analysis.

This code is used in QIIME's compare_trajectories.py script. @gregcaporaso and I have updated QIIME's setup.py to specify natsort < 4.0.0 to retain the current sorting behavior.


[Doc] Deploy Docker: outdated

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
in https://github.com/apache/pulsar/issues/14092#issuecomment-1253650641

Do we have to make any changes in text or link targets in doc on https://pulsar.apache.org/docs/next/deploy-docker ?

That document looks very much outdated. It doesn't make sense to me.

What is your suggestion?
update
Any reference?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@hpvd I think this issue can be an instance of #17495 and all these related documents should be considered in a rewrite on the topic "get started in containers (cluster)":

https://pulsar.apache.org/docs/next/deploy-docker
https://pulsar.apache.org/docs/next/getting-started-helm
https://pulsar.apache.org/docs/next/helm-install
https://pulsar.apache.org/docs/next/getting-started-docker
https://pulsar.apache.org/docs/next/deploy-kubernetes

Perhaps with some redirections and content merges.

@hpvd I think this issue can be an instance of https://github.com/apache/pulsar/issues/17495 and all these related documents should be considered in a rewrite on the topic "get started in containers (cluster)":

@tisonkun I think your mind is 'deployment in containers(cluster) '

Closed the issue since the reported topic has been updated and refreshed in #17853.
Regarding the doc improvements for Kubernetes deployments, I drafted https://github.com/apache/pulsar/pull/18015 to follow up.  //cc @tisonkun


Add LICENSE file

This makes the license more explicit :)

@fredyolarte @cvergarae 👀

We add the Licence. Thanks @caniszczyk


[getrelax.club] SIte support request (basically videomega.tv)

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.05.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):

$ youtube-dl -v "http://cdn.getrelax.club/avonline/25539_Getrelax_AV_.html"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://cdn.getrelax.club/avonline/25539_Getrelax_AV_.html']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.05.01
[debug] Python version 2.7.10 - Windows-XP-5.1.2600-SP3
[debug] exe versions: ffmpeg N-67100-g6dc99fd, ffprobe N-67100-g6dc99fd, rtmpdump 2.4
[debug] Proxy map: {}
[generic] 25539_Getrelax_AV_: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 25539_Getrelax_AV_: Downloading webpage
[generic] 25539_Getrelax_AV_: Extracting information
ERROR: Unsupported URL: http://cdn.getrelax.club/avonline/25539_Getrelax_AV_.html
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 1393, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 279, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=etree.TreeBuilder(element_factory=_element_factory)))
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 268, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
ParseError: not well-formed (invalid token): line 74, column 24
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 673, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 341, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2063, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://cdn.getrelax.club/avonline/25539_Getrelax_AV_.html
...
<end of log>

The site uses basically videomega.tv embed tags but they don't get regocnized.

Single video: https://www.youtube.com/watch?v=BaW_jenozKc

This looks like copyrighted content. youtube-dl does not support sites dedicated to copyright infringement. Do they have rights to distribute this? If not provide an example URL that does not violate any copyrights.


Baofeng RD-5R Dual Capacity Direct Mode

Greetings.
Original Baofeng software allows to define single TS for talking with repeater.
dmrconfig on other hand, don't set specified bit in codeplug until i manually change following line in rd5r.c:
   // Byte 50
    ch->dcdm              = 0x1;

After that my radio works fine on selected timeslot.
Maybe i miss something, but it appears to be a bug.

Well, it's definitely a bug. Thank you for the report. Not sure whether it's a bug in dmrconfig or in RD-5R firmware. Can you please send me an image of your configuration? I need more details. Is it simplex or duplex mode? Looks like RD-5R is using the DCDM mode flag in some unusual way.

Sure thing here is my codeplugs:
Codeplug.zip
First my radio work in simplex mode. Second there is something treaky about my particular model, because sticker on the back says it DM-5R Plus but model info shows RD-5R, so maybe it firmware problem.

Thank you for the codeplug.
Here is what I found on RadioReference forums: "Dual Capacity Direct Mode (DCDM) is a DMR enhancement that can be employed when using simplex (direct) communication between radios. When operating with a DMR repeater, the repeater provides a sync signal for the two DMR time slots. Normally, DMR simplex operation between radios does not use time slots since there is no sync signal available. DCDM is an added feature that allows one of the radios in a simplex communication to provide a sync signal, thereby allowing the use of both time slots (i.e. Dual Capacity)."
So DCDM mode is not for repeaters: it's only for direct communication to another radio. I can modify dmrconfig to always enable the DCDM bit on RD-5R in Simplex Digital mode. There is a problem of compatibility though.
From RD-5R group on Facebook: "If you enable DCDM on a simplex channel, you will NOT be able to talk to other hytera or motorola radios on that same simplex channel. With DCDM enabled on a simplex channel, I could ONLY talk to other baofeng radios with that SAME setting DCDM enabled."
Do you really want to make your radio incompatible with others in Simplex mode?

Here is what I found on RadioReference forums

Thank you for point that out!! An additional info really helps me to understand how it works.

compatibility issues

Oh it indeed change my first intend to use this Baofeng feature. Later on it can cause huge mess.
So as compromise, i think it possible to add optional field in digital channel settings with warning note about  compatibility troubles with other radios. Maybe someone in future will need  it.


long handling in python3

In order to get around the lack of a long in python3, compat does this:
class long(int): pass

but long is used by the prom.Field to create BIGINT fields in python2, the problem is that int in  python3 is the same as long in python 2 (so there isn't really a way to create BIGINT fields in python 3 without doing something like:
from prom.compat import long
from prom import Field

some_field = Field(long)

which seems horrible and is definitely counter-intuitive. I'm wondering if it is worth just making all integers BIGINT in python 3?

https://github.com/Jaymon/prom/issues/57


Locked repository: Unlock strategy

Hey all,
I ran a few tests and provoked a condition in which my test repository got locked. Before I would unlock manually and carry on. After #47 this doesn't seem possible anymore:
docker-compose run --rm backup-docker-services unlock
Checking configured repository 'rest:http://xxx:yyy@restic.server.de:8000/services' ...
Fatal: unable to create lock in backend: repository is already locked exclusively by PID 40 on jarvis by root (UID 0, GID 0)
lock was created at 2020-08-10 16:58:30 (14m26.520623527s ago)
storage ID 196a1a3b
Could not access the configured repository. Trying to initialize (in case it has not been initialized yet) ...
Fatal: create repository at rest:http://xxx:yyy@restic.server.de:8000/services failed: Fatal: config file already exists

Initialization failed. Please check error messages above and check your configuration. Exiting.

How do we want to deal with this? Is it reasonable to assume that if a command is given by the user the repository checking logic should be skipped?
Best! Thomas

Oh, I did not yet run into this because I am using docker exec all the time with my swarm-based approach.
Skipping initialization if any command is given sounds like a sensible approach to me. The init command can also just be called explicitely so there is no need to run the container without a command beforehand.
But if we change the behaviour, we should probably document that.

This still exists – not stale.

Or maybe just skip the repository checking logic if exactly the unlock command is given. That could prevent other regressions here.

I've the same problem. Before I discovered this container I'd a self generated script with a unlock between backup and forget.

If there are no objections, I will go and implement my last proposal.

I think the root cause of the problem should be solved upstream. I have/had the same problem with 2 different scripts. So for me this seems to be a wrong handling within restic.

When looking at the issues in restic repository you can see there are many of similar reports: https://github.com/restic/restic/issues?q=is%3Aissue+locked+is%3Aclosed

I agree that the locking mechanism in restic seems a bit wobbly. Also discussed in #60
@djmaze I wanted to tackle this and other topics we discussed in a pull request. Sadly my life is a bit unpredictable these days (in a good way). The PR will come but please do not feel blocked by that!
Imho the checking logic I "improved" is not a good approach after all. My latest thinking is that

the checks should be executed at startup and before every job
the checks should not stop execution, except in reasonable cases
checks should be skipped when the image is called with a command, like init or unlock

Or maybe just skip the repository checking logic if exactly the unlock command is given. That could prevent other regressions here.

Agreed 👍

@ThomDietrich  That sounds very reasonable. I like your comprehensive solution and I would be okay to wait for that.
By the way, I just released 1.3.0, which includes the update to Restic 0.11.

Maybe a useful workaround for anyone else landing here, When I need to manually remove a lock from a repository I issue a one-off docker-compose run of my resticer service and overriding the container's entrypoint like so:
docker-compose run --entrypoint="bash -lc" --rm <service-name> "restic --no-lock unlock"

bash isn't available in the container when i tried.
docker run --env-file .env --rm -it --entrypoint="sh" mazzolino/restic

Inside the container, check and clear the locks.
>> restic --no-lock list locks

>> restic --no-lock unlock


Update downstream applications

Description
Given #937, we need to ensure that once pycsw 3.0.0 is released, that the following downstream applications are updated to cover breaking changes (i.e. YAML configuration) and use new features (i.e. OGC API - Records support):

[ ] GeoNode
[ ] CKAN

https://github.com/GeoNode/geonode/pull/10380


Fix iOS NativeCamera texture pixel format

The BJS side creates the texture and specifies the format (as RGBA8, in NativeEngine.createDynamicTexture), and then the native side overrides the texture handle in the Graphics::Texture, but the other properties (including format) are not updated, so the format (BGRA8) is incorrect, and operations like readPixels won't work.
This change fixes the issue by using a shader to convert the camera's YpCbCr format into RGBA, similar to how it's done in XR.mm.
Related issue
https://github.com/babylonjs/babylonnative/issues/1107

Converted this to a draft because it's not up to date with Alex's latest changes. I'm not 100% happy with it yet but I'd like to get some eyes on it to make sure I'm not doing something dumb.

This is now working for macOS again and is ready for merge if there are no more changes needed.


Is there a way to make window_border work only on a specific application or in a specific space?

I'm very new to yabai.
Is there a way to make window_border work only on a specific application or in a specific space?
And how can I do that?

yabai -m config window_border off
`yabai -m rule --add app="^Safari$" border=on


Support metaformats fallback option

Describe the feature
An experimental option should be available to use meta tags as a fallback for sites that don't natively implement microformats. The Metaformats spec defines changes to the microformats parsing algorithm to support this.
Adding an opt-in feature would allow using microformats as the vocabulary for understanding other sites while not interfering with pure microformats parsing.
Example of input
GitHub Issue: https://github.com/microformats/microformats-parser/issues/39
Example of output
Here's the output of opengraph-mf2 which implements this general concept (though limited to OpenGraph).
{
    "type": [
        "h-entry"
    ],
    "properties": {
        "name": [
            "Provide JavaScript ES module export in distribution · Issue #39 · microformats/microformats-parser"
        ],
        "summary": [
            "Hi Aimee! Lovely to see a clean and modern implementation of a microformats parser; just what I need for my Micropub project! What type of feature is it? An additional option for importing this mod..."
        ],
        "featured": [
            "https://opengraph.githubassets.com/78fd25660d09eb046441b40894ba7dcc6668105efa381fdd8dd1cb3b2f5ba61e/microformats/microformats-parser/issues/39"
        ],
        "url": [
            "https://github.com/microformats/microformats-parser/issues/39"
        ]
    }
}

Additional context
This was prompted by getindiekit/mf2tojf2#20
More details found on the Indieweb Wiki.

Hi @aciccarello, thanks for the heads-up for this one.
I've started an implimentation in #226. I've not made any real progress except to introduce the experimental option, and a single test that is failing (as it's not implemented)
It will take me quite a while to get my head back into this and to figure out how to include it, but at least it's on my radar.
Any help here would be appreciated, even if it's just more test cases 🙏

@aimee-gm I'm glad to hear you're open to this feature 🎉 . As far as I know there hasn't been many implementations of metaformats so there could be a few questions that come during implementation. I took a look at the microformats-parser codebase earlier (which was impressively straightforward 👏 ) and think I've got an idea of where to go with this. I'll see if I can put some more code together.

I looked into this more today and there are a lot of potential edge cases. I've tried to add test cases on my fork for as many as I could
To name a few:

h-* class on <html> avoids parsing metaformats
h-* class on <head> avoids parsing metaformats
Documents with both mf2 and metaformats
mf2 property classes on meta tags reads from content attribute
og overriding twitter classes
handling multiples of og: properties
handling different og:type values

When I looked at some actual pages with meta tags and how to implement the spec, I had a lot of new questions about adjustments the spec may need

Why consider twitter tags when most sites also have og values?
Why have an explicit meta[name=twitter:card] check if all meta[property^=og:] or meta[name^=twitter:] imply h-entry?
Should it support og:video:url in addition to og:video?
Should the parser fix usage of name="og:x" rather than property="og:x"?
Should article:tag, profile:first-name, and profile:last-name be part of the spec?
Why not <title> or <meta name="description"> tags?
Is including og:image as u-photo going to imply photo post for things like blog posts (if using post type discovery)?

I'll try to work out the spec questions in the indieweb chat to get clarification. I'll also continue looking at a possible implementation. My initial attempt ran into problems with needing to keep track of whether metaformats were enabled and how to combine potentially conflicting meta tags.

The main thing to remember is that this is experimental - so for an initial pass, we can implement as much, or as little, as we'd like.
The main hurdles as I see it:

Getting <meta> tags to parse to something recognisable - as there is no "parent" that indicates microformats are hidden within
Once a h-* class is found on the <html> or <head> elements, meta tag parsing is not performed.

As for which I would attack first, I would consider just handling the og: use cases as a proof of concept.
Beyond that, it should just be implementation and interpretaion of the spec.
As for an approach, there is a step where the document goes through a "setup" phase - picking out elements with IDs, handling templates etc. Then the microformats are parsed. I was wondering if we were to add a step between these, which would see if metaformats would need parsing, and to modify the relevant elements to have necessary class properties to fool the parser into parsing them correctly.

That's a good point, we have some flexibility here. I like the idea of applying classes during a pre-parsing pass. My latest proof-of-concept was able to use that approach fairly well.
There are still some things to sort out. I think it would be good to indicate in the mf2 response an item was parsed using metaformats. While parsing, it could be challenging to figure out the fallback values when tags are in a different order. There could also be some intra-tag dependencies that could make things more difficult too.

Had some conversations in the indieweb chat. Sounds like there is consensus that metaformats should only be returned if there are no mf2 on the page. There are some concerns about badly formatted hentrys from WordPress templates causing problems so some validation of content may be needed.

@aciccarello this is now merged and released as v1.5.0 🎉

Great! Thanks for taking a look!


Configure .yml file to include codecov and add codecov badge

As a Developer
I need to add codecov badge
So that everyone who wants to clone main branch can know the coverage
Details & Assumptions:

Have .travis.yml file running

Acceptance Criteria:
Given I have my .yml file configured
When I click on the codecov badge
Then I see the codecov report for main branch

Updated build and codecov badge


feat: add openapi schema

Context

Closes #86.
Changes proposed in this pull request

Extension builds preview

Name
Link

Latest commit
4cf98e4de42e7a3a51a46bd7d21ff05790149b78

Latest job logs
Run #7622510255

DownloadDownloadDownloadDownload


show only versions newer than NVM_MIN if set

This is to fix #3250.

For example, running NVM_MIN_VER=18 nvm ls-remote --lts when v14 and v16 are installed:

Performance-wise there's not really much change or overhead, you can trust that awk is fast :-) Sometimes it might even run faster, esp. when many older versions are skipped.
Meanwhile the other sibling functions and even the tests are something I'm not really familiar with, may you can chime in here? @ljharb

@ljharb just added a test, however Travis CI seems stuck, any insight?

BTW, I had to adjust the travis job a bit, due to the error
pyenv: /opt/pyenv/versions/2.7.18 already exists

See the screenshot below (https://app.travis-ci.com/github/nvm-sh/nvm/jobs/623514514):

https://app.travis-ci.com/github/nvm-sh/nvm/jobs/624025129#L797
+rm -fR v* src alias test/test-xz
  ✗ Running 'nvm unload' should unset all function and variables
+BEFORE=./before.tmp

@ljharb any idea if the failing Travis test is related?

As we can see from the below screenshot, for v16.15.1, now all of its updates are listed:

When I run nvm ls locally with this PR, I get empty as the first item in the list.
When I run nvm ls-remote --min=4 locally with this PR, all versions are displayed.

When I run nvm ls locally with this PR, I get empty as the first item in the list.

Interesting, any idea where could this empty come from? Asking because here the change to nvm_print_versions only determines whether to skip certain versions or not, meanwhile all the versions are supplied by the caller.
May I ask what's the output of nvm ls when run from the master branch?

When I run nvm ls-remote --min=4 locally with this PR, all versions are displayed.

As a comparison, here's what I got with the same command:

Is it possible that the shell was still running the code anther branch, rather than that of the PR? Maybe check the output of type nvm_print_versions?

I'm certain that I'm using the code from this PR, yes.
I'm running this on a Mac; if you're not, then perhaps there's some platform-specific difference here?

hm, ok i did just figure out that i had a $NVM_DIR/versions/node/empty dir for some reason, so at least that's a red herring. Let me test again.

ok, testing again, and nvm ls-remote --min=4 (or 20, or whatever) still has no effect for me on my Mac.
What OS are you using exactly?

ok, testing again, and nvm ls-remote --min=4 (or 20, or whatever) still has no effect for me on my Mac.
What OS are you using exactly?

Actually I'm also on mac :-) How about NVM_MIN=4 nvm ls-remote? Can you also try to enable set -x within nvm_print_versions?

ohhh wait, lol i think this is the actual feature i asked for - i have tons of node versions installed, going back a very long way:
$ NVM_MIN=4 nvm ls-remote | wc -l
     711
$ nvm ls-remote --min=4 | wc -l
     711
$ nvm ls-remote | wc -l
     790

in other words, it's filtering some things out, but with the additional logic i requested, it's still showing me a lot of things i didn't expect. 🤔

ohhh wait, lol i think this is the actual feature i asked for - i have tons of node versions installed, going back a very long way:
$ NVM_MIN=4 nvm ls-remote | wc -l
     711
$ nvm ls-remote --min=4 | wc -l
     711
$ nvm ls-remote | wc -l
     790

in other words, it's filtering some things out, but with the additional logic i requested, it's still showing me a lot of things i didn't expect. 🤔

Because you have many versions installed? Or Would you change mind? :P
BTW, typically I just run something like NVM_MIN=18 nvm ls-remote --lts.

@ljharb FYI, just rebased with some minor fix in tests.

@ljharb how is it going? anything to note?

No progress yet; I've been traveling. I'm prioritizing a bug fix on nvm before this PR, but it'll be next in line after that.

ok, so i just tried it out again.
if i do nvm ls-remote --min=99, i get all the versions hidden below the lowest one i have installed - v0.4.12 - but i get every version higher. So, for me, it's not really that useful. I assume that on an empty system, or one where all installed node versions are above the min, it actually works as intended.
I'm starting to wonder if perhaps my original concern - about versions being hidden - is better addressed by prepending a message like "Minimum version X set: N versions hidden", and going back to the simpler logic? (i'm super sorry if this means you're doing work to undo the work i already asked you to do :-/ unfortunately sometimes it takes time and first-hand experience to really get a sense of the DX/UX of a thing)

@ljharb, although in some cases it's somehow possible to have a broad range of node versions installed, but I'm sure not everyone would need to do that.
Meanwhile I believe most people only need (a) several (if not a few), and (b) most recent, (c) typically LTS versions, installed for the projects they work on. Like what's shown in a previous comment:

And this is sort of the next step for the previous pr https://github.com/nvm-sh/nvm/pull/2827, that one has improved the performance of nvm ls-remote, by reducing the time needed for a complete nvm ls-remote from about 20s down to about 2s. This pr aims to also improve the ergonomics, by showing just what's really needed, like 797 vs 38 as shown below, nevertheless the time taken is also reduced as a side effect:
UnfilteredFiltered

# time nvm ls-remote --min=v0 | wc -l
798

real	0m1.253s
user	0m0.246s
sys	0m0.322s

# time nvm ls-remote --min=18 --lts | wc -l
38

real	0m0.545s
user	0m0.154s
sys	0m0.188s

And no worries, your initial proposal actually inspired me to think more about why people would need nvm ls-remote, or even nvm: it's because people would want to find newer versions of node delivering new features, patches or whatever improvements that are not available in currently installed versions. In that sense showing new patch versions definitely helps. Like the program automatically detect a suitable min version based on installed ones.

BTW, the error with nvm --version in the failed tests seems unrelated:

https://github.com/nvm-sh/nvm/actions/runs/11406338964/job/31739908143?pr=3277
https://github.com/nvm-sh/nvm/actions/runs/11406338964/job/31739908480?pr=3277


Using space in g:ale_sign_* variables causes error

Information

NVIM v0.4.0-370-gc0a29c365
Build type: RelWithDebInfo

Operating System: Arch Linux latest
What went wrong
I am not sure this is an error with ale or with vim itself.
I want to use a single character as error, warning, etc symbol, for instance > instead of `>>. But this fails.

Reproducing the bug

`let g:ale_sign_error = ' >'
e file/with/errors

The following error pops up:
Error detected while processing /home/me/.local/share/nvim/plugged/ale/autoload/ale/sign.vim:
line   71:
E239: Invalid sign text:

As a workaround I used a non-breaking space.

I also found that \ > works. Probably this is a vim limitation.

I think it's just a bug. I'll fix it by escaping the spaces.

That should work now.

Indeed it works. Thank you for covering my use case!

@w0rp
This commit has some side effort which make char like ✖ not useable.
E239: Invalid sign text: ✖\

To reproduce:
:let g:ale_sign_error='✖'
:echo substitute(g:ale_sign_error, '\\\| ', '\\\0', 'g')
✖\

That works for me. Try adding this to your vimrc file.
set encoding=utf-8
scriptencoding utf-8

Thanks, it works now. My mistake.


new

#19386

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @Rioname isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot


Bug: numba does not preserve dtype in scalar multiplications

Consider
import numpy as np
import numba

def f():
    h = np.uint32(2166136261)
    return h * h

@numba.njit()
def f_numba():
    h = np.uint32(2166136261)
    return h * h

@numba.njit()
def f_numba_workaround():
    h = np.uint32(2166136261)
    return np.uint32(h * h)

print(f())
print(f_numba())
print(f_numba_workaround())

In all 3 functions, h * h should be of type np.uint32 and an overflow should occur. However this does not happen in the standard numba JIT compiled version of the function. Instead the following output is observed:
~ python test_numba.py
test_numba.py: RuntimeWarning: overflow encountered in uint_scalars
1850947993
4692146301219060121
1850947993

Thanks for the report. This document is related http://numba.pydata.org/numba-doc/dev/proposals/integer-typing.html I'm not sure whether to see this as a bug or known defined behaviour.

Thanks for pointing out that document. For easy reference, quoting a part:

The typing of Python int values used as function arguments doesn’t change, as it works satisfyingly and doesn’t surprise the user.
The typing of integer constants (and pseudo-constants) changes to match the typing of integer arguments. That is, every non-explicitly typed integer constant is typed intp, the pointer-sized integer; except for the rare cases where int64 (on 32-bit systems) or uint64 is required.
Operations on integers promote bitwidth to intp, if smaller, otherwise they don’t promote. For example, on a 32-bit machine, int8 + int8 is typed int32, as is int32 + int32. However, int64 + int64 is typed int64.
Furthermore, mixed operations between signed and unsigned fall back to signed, while following the same bitwidth rule. For example, on a 32-bit machine, int8 + uint16 is typed int32, as is uint32 + int32.

Why is the bitwidth promotion on all operations is necessary? Wouldn't it be sufficient to represent not-explicitly typed integers as intp but match numpys behavior in case a type is explicit?
As you pointed out that this is documented and expected behavior I'm happy to close the issue as some users may rely on this behavior. I believe it can be surprising though, given that http://numba.pydata.org/numba-doc/latest/reference/numpysupported.html claims numpy scalar types are 'supported', ie. my interpretation: should work as in numpy.

@sklam: Do you recall how we ended up with the above rules?  I thought we generally tried to follow NumPy type promotion conventions...

This is known behaviour, I think to do the right thing the differentiating between the NumPy and CPython scalar types is required.


Planets aspects

Is there a way to get aspects like angles, degrees that involve two or more planets, for example, opposition angle 180°, square angle 90°,  trigone of angle 120° and conjunction?

Marcelo, those aspects you mentioned are between 2 planets.
I understand your question. Geometrically an angle is defined by 3 points.
But astrologically, we consider ourselves as one point in the center of the chart, and compare the aspects between 2 other planets.
For example, if the sun is up high in the sky and the moon is rising in the horizon, they form a square angle 90º.

Thank you @GoulartNogueira!
But is there a way to get these aspects that a mentioned above?
I know that there is a method called getAspec, for example:
# Retrieve the Sun and Moon
sun = chart.get(const.SUN)
moon = chart.get(const.MOON)

# Get the aspect
aspect = aspects.getAspect(sun, moon, const.MAJOR_ASPECTS)
print(aspect)

But I got this result: ```
Aspects:
<Moon Sun -1 None +00:00:00>

it sound weird!

There is nothing weird in the result.
Your chart probably doesn't have any aspect between the Sun and the Moon. That's perfectly usual.
I understand the code is working fine.
I suggest you to study a little more about astrology before trying to understand the code and programming.


[cassandra-schema] Make schema job run migration if TTL value changed

Requirement - what kind of business use case are you trying to solve?
I would like to like to adjust trace data TTL on the fly. While initially setting it with the schema job to say 60, I would like to run the schema job again and have it changed to 2400 for example.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Have the schema job perform a migration if a value has changed.

You can simply run ALTER TABLE against the relevant tables in your database and change the TTLs .
I don't feel that it's worth the trouble of maintaining yet another script.

Fair enough! Thanks.


Adds environment name to PROMPT on Cmd, Cmder,ConEmu

This PR makes cmd.exe and cmder/conemu show the virtual environment's name
in those shell's prompt.
This edit could also be in fork_cmder() , but that would not fix cmd.exe.
I understand the entire section might need some re-work and clean up but until this should be an easy and contained fix that will make a lot of windows users happy.

PS: this is my first PR for a large project

PS: This fixes https://github.com/pypa/pipenv/issues/2116

Is this really all it takes...

BTW we should upstream these to pew as well

@uranusjr This change is pretty small, while the 11.11 changes are somewhat large in scope.  I really like the idea of getting these improvements and quality of life fixes done, if you think these are ok (and we get an upstream pr to pew opened) we can consider point releasing for these

In general it is (%PROMPT% is essentially PS1 for cmd), but I wonder what consequences would it have on custom init scripts (clink.lua for example). Will it result in duplicate venv names, or put it in the wrong place? We’ll need to put this in the wild and see what happens. Yeah I’d say let’s do this.

Seems like a good reason to get this out before a minor release, we can work through that stuff.


Update Sinon

yea. chai-as-promised will never be compatible with IE11, so I had to remove it. It's still there for wd to use, but depending on how today goes, we might be on webdriver.io by next week.


Update to golang 1.18 and update test-infra

ci-tools needs an updated test-infra dependency, and thus release-controller gets one too. Since test-infra recently went to golang 1.18 we also need to update it here.

@smg247 You might need to bump the .ci-operator.yaml yaml to 1.18 as well.

@smg247 You might need to bump the .ci-operator.yaml yaml to 1.18 as well.

ah yes, good call

...and it appears that we don't have the golang-1.18 imagestream yet

/retest

/test all

Chances are this will fail until the openshift/release:golang-1.18 image is populated:
golang-1.18
  updates automatically from registry registry.ci.openshift.org/ci/origin-release:golang-1.18
    prefer registry pullthrough when referencing this tag

  ! error: Import failed (NotFound): dockerimage.image.openshift.io "registry.ci.openshift.org/ci/origin-release:golang-1.18" not found
      10 minutes ago

Chances are this will fail until the openshift/release:golang-1.18 image is populated:
golang-1.18
  updates automatically from registry registry.ci.openshift.org/ci/origin-release:golang-1.18
    prefer registry pullthrough when referencing this tag

  ! error: Import failed (NotFound): dockerimage.image.openshift.io "registry.ci.openshift.org/ci/origin-release:golang-1.18" not found
      10 minutes ago

yes...I am working on doing that now. I thought that it was ready, but I still needed to wait. I think we are good now so I am going to try again. Sorry for all the noise here...

/retest

I figured.  I'm pretty sure the default imagestream import time is 15 mins.
No problem at all!


Micro-CHP can only be up to 55% while all other technologies can be 100%

Is this what we desire?
If so, shouldn't we mention the why in the '?' ?

This is something I need time to look at. Removing milestone.

Closing, the micro-CHP has been removed in the recent heat overhaul


[FLINK-9325][checkpoint]generate the meta file for checkpoint only when the writing is truly successful

What is the purpose of the change
This PR in order to enhance the checkpoint's finalization a bit, write the metadata file first to a temp file and then atomically rename it (with an equivalent workaround for S3).
Brief change log

write the metadata file first to a temp file and then atomically rename it

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation
no

Hi @StephanEwen Could you please have a look at this?

I think this fix here might not work for S3, because a rename() with the S3 file systems will actually trigger a copy (or even a download and upload), so it is not a cheap operation.
The we can fix this by adding a create(...) method (or mode) to the FileSystem API that does not publish data in the file until close() is called. For hdfs://, file://, this would be using a temp file with renaming, for S3 we don't write to a temp file, because S3 makes the file only visible on close() anyways.

@StephanEwen Thank you very much for your great suggestion! I will address this that way.

How about adding the method createAtomically or so, with otherwise the same signature as the create(Path, WriteMode) method?

Hi @StephanEwen,

I prefer to introduce the create(Path, WriteMode), because I feel this is more extensible (it could allow us to introduce other WriteMode's in the future).
I would choose to throw unsupported operations exception for the others schema, I think that make the program more deterministic.

What do you think?

Hi @StephanEwen I have update the PR according to the above comments, it's ready for an another review.

Hi @StephanEwen Thank you very much for your reply, I'm not sure whether just overriding close() to do super.close() + rename() is enough, for example.
try (outputStream = new TwoPhraseFSDatautputStream(...)) {
    outputStream.write("part1");
    throw new RuntimeException("xxx");
    outputStream.write("part2");
}

This will also rename the tmp file to the target file, because we just rename() in close(). And the current TwoPhraseFSDatautputStream works as a wrapper so it should have supported all the file system. I'm not sure whether I misunderstand what your meaning... please let knows if I misunderstand something and your opinion, Thanks!

@StephanEwen After thinking your comments again, I think I misunderstood the Also, we need this method to be implemented in all FileSystem subclasses. 😭  , I will address that. But the question related to TwoPhaseFsDataoutputStream still a bit confuse to me...

Hi @StephanEwen, I added more tests for the FileSystem#createAtomically(), concerning the TwoPhaseFsDataoutputStream, can we introduce a commit_on_close option for it to make it easier to use? If the commit_on_close=true, we commit the writing in close() atomically. If the commit_on_close=false, we need user to call commit() manually, this could be useful in try-with-resource situation, what do you think?

Hi, I met a problem here, for the Hadoop FileSystem when the schema='hdfs', we can't rename a file to a existing file. This means that it hard(I'm not sure whether it's possible) to support the WriteModel.OVERWRITE for createAtomically() with schema='hdfs', if we work-around this by firstly rename the existing file to a tmp file and then rename the pre-commit file to the target file, then this two step operations is not atomic, which may lead to a inconsistent result if the JVM crashes between this operations. I'm running out of myself on this now...Do you have any suggestions for the createAtomically() when schema='hdfs' and writeMode='WriteMode.OVERWRITE'? @StephanEwen

Good point about the renaming on close() in case close is called for cleanup, rather than success.
We could follow the same semantics as in CheckpointStateOutputStream
There the semantics are:

close() means "close on error / cleanup" and closes the stream and deletes the temp file.
closeAndPublish() would mean "close on success" and close the stream and rename the file.
After ``closeAndPublish()has been called,close()` becomes a no-op.

The FsCheckpointMetadataOutputStream implements that pattern, I think it worked well and is easy to use.

@StephanEwen Thanks for your good suggestions! Will update PR like it, and what about the problem related to WriteMode.OVERWRITE, do you against if we don't support it in createAtomically()?

My gut feeling is that we don't need WriteMode.OVERWRITE in cases where one wants such an atomic file creation...

@StephanEwen I guess this PR is already for an another look now...

I think we need to have a special output stream type (AtomicCreatingFsDataOutputStream or similar) as the return type of FileSystem.createAtomic(). Otherwise, how can a user actually create a file? The closeAndPublish() method is not part of any API class.

Yes, @StephanEwen thanks for the continuous suggestions, will follow your suggestion.

@StephanEwen I've addressed your comments, could you please have a look again?

Could anybody have a look at this?

@sihuazhou I got caught up in some other tasks - will try to get back to this here soon, I would like to have this feature in as a base for "search for completed checkpoint".

@StephanEwen Thanks! Looking forward~

Hi @StephanEwen thanks for your comments! I was caught up by some terrible work recently, will have look at the RecoverableFsDataOutputStream and get back here probably this weekend. ;)

Do you mind i take over? @sihuazhou I met the same problems and want to solve it.
And any ideas on it @StephanEwen @wangyang0918


React to HttpAbstractions

Reacts to https://github.com/aspnet/HttpAbstractions/pull/873
@Tratcher

@HaoK,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


chore(master): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2023-05-20)
Features

added ConfigVariable decorator (ddd1091)
initial commit (399f67a)

This PR was generated with Release Please. See documentation.

Coverage report

St.:grey_question:
Category
Percentage
Covered / Total

🟢
Statements
100%
61/61

🟢
Branches
100%
11/11

🟢
Functions
100%
1/1

🟢
Lines
100%
61/61

Test suite run success
6 tests passing in 1 suite.
Report generated by 🧪jest coverage report action from 8176c0e58f3863bcfd12ae8895c56e47ef53bdc1

:robot: Release is at https://github.com/dworac/config/releases/tag/v1.0.0 :sunflower:


⚠ Samsung has degraded performance

In ac212b8, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2503 ms

Resolved: Samsung performance has improved in 785ff2b.


Image Slider on home.js not working

Hi @Anu27n  I would like to work on this. Please provide more details


Testing the Library

Hi Folks,
I'm new to the Haskell world, and I want to start contributing to an open-source library as a means of improving myself.
I picked this project because I'm a web developer by trade (though not training), and communicating with REST APIs is definitely in my wheel house.
That being said, how am I supposed to run the test suite for this library?
I have a running rest suite, I have twilio test credentials in the environment in which I am running the test suite, but then I get an error (the error is below).
It's obvious from the error that we are making a request to an endpoint that doesn't allow test credentials. Is the expectation for the test suite that live credentials would be put in there?
twilio-<IP_ADDRESS>: test (suite: Tests)

Tests: HttpExceptionRequest Request {
  host                 = "api.twilio.com"
  port                 = 443
  secure               = True
  requestHeaders       = [("Authorization","Basic IAmHidingThisBecauseIDon'tWantToBeHacked!")]
  path                 = "/2010-04-01/Accounts.json"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 (StatusCodeException (Response {responseStatus = Status {statusCode = 403, statusMessage = "FORBIDDEN"}, responseVersion = HTTP/1.1, responseHeaders = [("Access-Control-Allow-Credentials","true"),("Access-Control-Allow-Headers","Accept, Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since"),("Access-Control-Allow-Methods","GET, POST, DELETE, OPTIONS"),("Access-Control-Allow-Origin","*"),("Access-Control-Expose-Headers","ETag"),("Content-Type","application/json"),("Date","Fri, 13 Oct 2017 15:44:48 GMT"),("Twilio-Request-Duration","0.013"),("Twilio-Request-Id","RQa95adc7d0fe64dc8b171c98397cfc861"),("X-Powered-By","AT-5000"),("X-Shenanigans","none"),("Content-Length","155"),("Connection","keep-alive")], responseBody = (), responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose}) "{\"code\": 20008, \"message\": \"Resource not accessible with Test Account Credentials\", \"more_info\": \"https://www.twilio.com/docs/errors/20008\", \"status\": 403}")

Test suite failure for package twilio-<IP_ADDRESS>
    Tests:  exited with: ExitFailure 1
Logs printed to console

Hi @StevenXL,
That's great to hear! This is a pretty small hobby project. It lacks many features, some things we don't have a solution for yet (like, paging! it's a bit embarrassing 😅), and—as you've noticed (and others—the testing isn't in the best place. But, if you're willing to choose-your-own-adventure here, I hope you can contribute!
The tests we have currently are integration tests that require non-test credentials which are read in from the ACCOUNT_SID and AUTH_TOKEN environment variables. Travis CI will inject these environment variables into any PR opened from a branch on the repository itself, but it will not inject them on PRs opened from forks (see here).
You can override ACCOUNT_SID and AUTH_TOKEN, but the integration tests currently hard-code phone numbers specific to the test account (see here and here). In order to be able to run these on any account, we need to

Let these phone numbers be configurable, and
Document what capabilities these phone numbers should have (e.g., ability to send/receive SMS, etc.) and how to provision them with Twilio.

Just this would be an improvement for our integration tests, but we also really need unit tests, too. Right now, any changes to the JSON parsing have to be tested by way of the integration tests, which slows down development.


Bug: Incorrect Emissions Error Messaging Global

Steps to Recreate:
Navigate to Emissions Module Global View
Select a Config
Open Config
Try to view emissions data for a reporting period that has data
Observe below error
Private Zenhub Image

i did not notice the error for a reporting period that has data. However, the errors comes for a period with no emissions data.

Need to have discussion on if CVP or DPC will remediate this issue

Confirm if still a bug on dev and stg.

No errors were recreated. Additionally, attempting to open up global emissions screens with no data results in the following message:

Verified with ORIS 9, CTG-1 in global emissions screen. No error messages are returned when selecting a view that contains data, and the error message returned when a view does not have data looks correct.

The global view displays the expected error message when the data does not exist for the view:
ORIS 3, Location 1:

ORIS 470, Location 1: