factorio: experimental 0.17.2 → 0.17.6

Motivation for this change
Factorio has been releasing a lot of bugfixes. This is the latest version (as of the time of writing)
Things done
Change the version and hashes

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Welp, Factorio 0.17.6 came out before this got merged, so I added it as another commit to this PR.


PointPillar's performance is not so good compared with published results

Hi @poodarchu Thanks for your great code! I trained pointpillar with default config, while the performance is as follow, which is similar to the results post by @s-ryosky in #18 .

For the category of car, the published mAP of moderate level on kitti 3D test dataset is 74.99, while my trained  one is only 75.66 on kitti val dataset. It seems cannot exceed the published one.
As far as I konw, other researchers could achieve about 77 on val with pointpillar, I wonder if there exists any problem in the configs? and can you pubulish your results? Thanks a lot!

PointPillars's config have been updated recently.
Which one did you use to train?
In old config the voxel_size was set as [0.2, 0.2, 4.0].
But in published results the voxel_size seems to be set as [0.16, 0.16, 4.0].
Please use smaller voxel size.

currently all versions of PyTorch's sync bn implementations have bugs. According to my experiments, APEX's implementation seem to be able to achieve the same performance as single-gpu versions on some models. So I think if you train Point Pillars using a single GPU might get a higher mAP.

training CBGS, the loss value are normal?
it looks like the x,y velocity loss take a major role in loss compute.
2020-01-07 11:27:01,209 - INFO - Epoch [5/20][5850/21350]	lr: 0.00060, eta: 4 days, 14:32:00, time: 1.150, data_time: 0.035, transfer_time: 0.048, forward_time: 0.367, loss_parse_time: 0.000 memory: 4948,
2020-01-07 11:27:01,209 - INFO - task : ['car'], loss: 3.2919, cls_pos_loss: 0.3375, cls_neg_loss: 0.0345, dir_loss_reduced: 0.3267, cls_loss_reduced: 0.4064, loc_loss_reduced: 2.8202, loc_loss_elem: ['0.0188', '0.0287', '0.2736', '0.0352', '0.0346', '0.0624', '0.7662', '1.3994', '0.2013'], num_pos: 19.6800, num_neg: 31705.3800

training CBGS, the loss value are normal?
it looks like the x,y velocity loss take a major role in loss compute.
2020-01-07 11:27:01,209 - INFO - Epoch [5/20][5850/21350]	lr: 0.00060, eta: 4 days, 14:32:00, time: 1.150, data_time: 0.035, transfer_time: 0.048, forward_time: 0.367, loss_parse_time: 0.000 memory: 4948,
2020-01-07 11:27:01,209 - INFO - task : ['car'], loss: 3.2919, cls_pos_loss: 0.3375, cls_neg_loss: 0.0345, dir_loss_reduced: 0.3267, cls_loss_reduced: 0.4064, loc_loss_reduced: 2.8202, loc_loss_elem: ['0.0188', '0.0287', '0.2736', '0.0352', '0.0346', '0.0624', '0.7662', '1.3994', '0.2013'], num_pos: 19.6800, num_neg: 31705.3800

It seems to be correct.

Thanks! @poodarchu @s-ryosky  I did train the model with a single gpu, while I didn't update the voxel_size and range in config as mentioned by @s-ryosky. I am not sure how much increase this modification could bring, but I 'll try it and release the results later.

@poodarchu  BTW, will you implement PointRCNN and release the code later?

@poodarchu BTW, will you implement PointRCNN and release the code later?

Yes. It will be released soon.

@poodarchu Thanks! Looking forward...

@poodarchu Thanks! Looking forward...

Are you interested in reproduce other models, such as VoteNet based on Det3D?

@poodarchu I am doing research on 3d detection and want to implement some ideas based on Det3D, maybe I will create some models based on VoteNet later, but I am not sure now. If I need it, I will implement it based on Det3D and pull a request.

@poodarchu I am doing research on 3d detection and want to implement some ideas based on Det3D, maybe I will create some models based on VoteNet later, but I am not sure now. If I need it, I will implement it based on Det3D and pull a request.

thanks

@Son-Goku-gpu @poodarchu  i had found this paper few months back but no implementation ,this has alround functionality https://arxiv.org/abs/1904.07537 please share your views on this
@Son-Goku-gpu  cna you share your mail id i have few queries which i would like to ask through mail if you have no issues

@poodarchu As mentioned by @s-ryosky, after changing the range and voxelsize in config file, I can achieve the mAP with PointPillar as follows:

The results seems more reasonable. Thank you!

@abhigoku10 I remember it's a workshop paper, the results are so poor that I didn't spend much time on it.  You may contact me with my email<EMAIL_ADDRESS>

I follow the newest，instructions train pointpillrs，the result are as follows，there is a big difference from the above 3d results，Any help would be appreciated.


Update BetterItemReloading.cpp

fix the "undeclared identifier 'GetItemEnchantMod'"
Thanks to @maloglolo and @zzy36

Changes Proposed:

Issues Addressed:

Closes

SOURCE:

Tests Performed:

How to Test the Changes:

thanks for the PR!


Organizational accounts should be changed to personal

Relates to https://github.com/UffizziCloud/uffizzi_platform/issues/107.

For testing refer to the comments in the related task for the platform.
https://github.com/UffizziCloud/uffizzi_platform/issues/107#issuecomment-1247967772

tested as part of the 107 task


[playsuisse] Add new extractor

This is a copy of the original youtube-dl PR. Now supports subtitles!
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Provide extractor for playsuisse.ch as requested in https://github.com/ytdl-org/youtube-dl/issues/27682 .
The website requires authentication, which can be provided to youtube-dl using the --username,  --password option, --add-header should also work. .netrc wasn't tested.
Account information for testing purposes:
E-Mail<EMAIL_ADDRESS>Password: asdfasdf12341234!

Please don't force push. It makes reviewing harder

@pukkandan is this PR ready or am I missing something?

Any eta when this will be reviewed @pukkandan?

I have made some untested changed (due to geo-blocking). test it and let me know

I have made some untested changed (due to geo-blocking). test it and let me know

@pukkandan Looks good now!

Apperantly there is now a V2 for the GraphQL API (V1 is still working but deprecated):
--- a/yt_dlp/extractor/playsuisse.py
+++ b/yt_dlp/extractor/playsuisse.py
@@ -46,7 +46,7 @@ class PlaySuisseIE(InfoExtractor):

     _GRAPHQL_QUERY = '''
         query AssetWatch($assetId: ID!) {
-            asset(assetId: $assetId) {
+            assetV2(id: $assetId) {
                 name
                 description
                 duration
@@ -69,7 +69,7 @@ class PlaySuisseIE(InfoExtractor):
                 }
             }
         }
-        fragment ImageDetails on Image {
+        fragment ImageDetails on AssetImage {
             id
             url
         }'''
@@ -86,7 +86,7 @@ def _get_media_data(self, media_id):
             }).encode('utf-8'),
             headers={'Content-Type': 'application/json', 'locale': 'de'})

-        return response['data']['asset']
+        return response['data']['assetV2']

     def _real_extract(self, url):
         media_id = self._match_id(url)

@thde Thanks for the heads-up, I will give the changes a try soon. Unfortunately I'm also geoblocked at the moment due to travel, hence need a couple of weeks to get it tested.

Thanks @sbor23! I actually found out something else: With shows (this at least) the download doesn't work, because the ID is pointing to a show with multiple episodes:
https://www.playsuisse.ch/watch/1115687/51/search-montreux-de?episodeId=1112663&locale=de

The actual ID of the video is the episodeId GET param in this case.
One could just use the episodeId of course. But with a small change to the query, all episodes can be looked up and it could be handeled as a playlist I think:
--- a/yt_dlp/extractor/playsuisse.py
+++ b/yt_dlp/extractor/playsuisse.py
@@ -47,9 +47,18 @@ class PlaySuisseIE(InfoExtractor):
     _GRAPHQL_QUERY = '''
         query AssetWatch($assetId: ID!) {
             assetV2(id: $assetId) {
+                ...Asset
+                episodes {
+                    ...Asset
+                }
+            }
+        }
+        fragment Asset on AssetV2 {
                 name
                 description
                 duration
+                seriesName
+                seasonNumber
                 episodeNumber
                 medias {
                     type
@@ -67,7 +76,6 @@ class PlaySuisseIE(InfoExtractor):
                 thumbnail2x3WithTitle {
                     ...ImageDetails
                 }
-            }
         }
         fragment ImageDetails on AssetImage {
             id

@pukkandan The remaining points where addressed. IMO this is good to merge, let me know if I should squash.


Some Emoji on iOS cannot be rendered correctly

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create A Text or TextField Widget
Find and enter 0⃣ in the input method emoji panel that comes with iOS, and let Text or TextField render it

Expected results
Text and TextField can be rendered correctly 0⃣
Actual results
0⃣ Can't be rendered correctly on iOS
Code sample
Code sample
import 'package:flutter/material.dart';

class Demo extends StatefulWidget {
  const Demo({super.key});

  @override
  State<Demo> createState() => _DemoState();
}

class _DemoState extends State<Demo> {
  String _content = "";

  final TextEditingController _controller = TextEditingController();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text("1⃣"),
        centerTitle: true,
      ),
      body: SafeArea(
          child: Padding(
        padding: const EdgeInsets.all(8.0),
        child: Column(
          crossAxisAlignment: CrossAxisAlignment.center,
          children: [
            Text(
              _content,
              style: const TextStyle(fontSize: 32, color: Colors.black),
            ),
            const SizedBox(height: 30),
            TextField(
              decoration: const InputDecoration(border: OutlineInputBorder()),
              controller: _controller,
              onChanged: (value) {
                setState(() {
                  _content = value;
                });
              },
            ),
          ],
        ),
      )),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration

https://github.com/flutter/flutter/assets/12570868/c20c44d5-892f-4f9e-9424-14832964ffc1

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.5, on macOS 13.4 22F66 darwin-arm64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.3)
[✓] VS Code (version 1.79.2)
[!] Proxy Configuration
    ! NO_PROXY is not set
[✓] Connected device (3 available)
[✓] Network resources

See https://github.com/flutter/flutter/issues/115517

@jiangkang
Based on above comment, let's track this in linked issue which has more details and root-cause.
Closing this in favor of the linked issue. If you disagree, write in comments and I'll reopen it.


docs: Add CMakeLists example

I created this example since it was a multi day struggle for me to get a simple example up and running.  I hope this might help other people in the future who just want to get started and make something.
Edit: I do not mean to imply that the docs are unclear, I am just a CMake noob helping out my fellow noobs. I honestly have very little bad to say about the rest of the documentation, it is very clear and complete!

Thanks. I plan to create a Hello World CMake project with the next release of the library.

The version v0.8.0 of ReactPhysics3D has been released.
In this version, there is now a "Hello World" example here with an example CMakeLists.txt file and a simple cpp file that shows on to create a simple executable using the ReactPhysics3D library.
Thanks a lot for your feedback.


Manage secrets with GitHub secrets in this repo

@Abhi94N This may be related to setting up integration tests with Kind but we no longer need this setup since we are using AWS Lambda and the environment variables provided with AWS Lambda to manage secrets with AWS KMS.

We can close this since the Terraform project in illumidesk/infra will handle these secrets. If any secrets are required for integration tests with Kind then we can add any environment variables to GH secrets for that chore issue.


Axial Expansion for CRAs

Description
This PR introduces axial expansion to pin-type control rod assemblies (CRAs).
Assumptions

Moveable inner control bundle that is inserted/withdrawn from the top.
The moveable control bundle must be surrounded by at least 1 expandable duct block above and below.
Control rods (consisting of clad, wire wrap, control pins, and plenum) within the bundle are pinned at both the top and bottom.
The top of the bundle remains fixed at its prescribed location.
Within the bundle, the guide tube, clad, and wire wrap expand downwards.
Control pins expand upward within downward expanding clad.
Driveline axial expansion is not accounted for.
Core vessel axial expansion is not accounted for.
Like the current axial expansion changer, multiple component axial linkage is not allowed.

User Considerations:

A new blueprints attribute, axially expands downwards is included for components. This attribute indicates that a given component expands downwards. If a component does not have this attribute, it retains its default behavior (false) of upwards expansion.
The expandable duct blocks must be tagged with the expandable flag in the blueprints.

Testing

Unit tests are included to account for prescribed and thermal expansion.

Note to reviewers:

This specific/cleaned up feature branch needs to be run through the gamut of downstream projects.

AxialExpansion_CRA_Algorithm_Simple.pdf
Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

This is a medium sized PR (as opposed to small).  I will take a little time and look at it in detail.

Do we know how this will affect popular downstream repos?

@john-science I figured it would take some time and thankfully I don't think there are any major priorities awaiting this.
As for popular downstream repos -- it does pass several of the big ones but a few repos will need to have unit tests updated. Those will be incoming.

I have not yet done a thorough review of this PR, but first I have a general request...
Can we have some documentation added to the User Docs that details all that one needs to know related to thermal expansion in ARMI? I'm thinking an aggregation of all of:

relevant case settings
relevant blueprints attributes
relevant flags
how to use it
how to turn it off
what to expect when it is on/off
what it can/can't handle
assumptions
others...

To me, this would be incredibly valuable and would save many users lots of time.
I don't think such a thing should be part of the current PR, but reading through this PR left me craving exactly such a compilation because it is difficult (for me) to keep track of all of the many pieces.

@keckler that's a great idea! I have a feature branch that has attempted to start this. As of now, it's just a single jupyter notebook without a home. Further fleshing this out is a great idea. I'll make an issue to kick start it.

It seems that there is no reason that the new axiallyExpandControlAssembly() method could not perform the same duties as the existing axiallyExpandAssembly() method. Absent the various checks like if c.hasFlag(Flags.CONTROL), it seems like I should be able to pass any other assembly into the axiallyExpandControlAssembly() method and have the thermal expansion be performed properly. This makes me think that the axiallyExpandControlAssembly() method is a generalized version of axiallyExpandAssembly(), and that we ultimately do not need both. Please correct me if I'm wrong there.

It might be able to. It has not yet been tested, but very well could work. I think an issue and follow-on PR to formally combine the two methods into one generalizable method is reasonable. I chose to separate them (and admittedly re-use a decent amount of code) simply to keep the existing (and decently vetted) methodology well separated from the new. After this PR gets merged, I'd be happy to work on combining the two methods into one.

It would be nice to get rid of the requirement that only control assemblies can have downward axial expansion. I don't see any specific reason why a non-control assembly could not have a component with the axial expand downwards attribute (except for that the assembly would also need to define a block with the EXPANDABLE flag, which it could do).

This is fair and I think would go hand-in-hand with the first. As of now, the new method that manages downwards expansion can only get called on assemblies with Flags.CONTROL. If we generalized the two methods as in your first point, we could remove this check and let the axial expansion changer handle it generally.

For control assemblies that are inserted from the bottom (as in EBR-II or any BWR), it appears that the new logic will work, I guess. Because it is a control assembly, it will be treated by axiallyExpandControlAssembly(), but then if you don't assign the axially expand downards attribute to any components, then I guess everything will expand upwards? And I guess that's probably the way it should be? I can't quite tell... If that's true, this lends credence to my supposition that axiallyExpandControlAssembly() is just a generalized version of axiallyExpandAssembly() and that we can get rid of the latter.

I suppose it might/should(?) work for CRAs that go bottom up. But that context has not yet been accounted for. That would be worthy of a second issue/feature request and follow-on PR.

@john-science This new "final" feature branch is failing one a key downstream tests and is not ready to merge. Just a heads up.
Before we merge, I will need to resolve it.

Add a check to ensure the validity of axially expands downwards and axially linked components. If one component within a series of axially linked components (who are all expected to expand downwards) does not have the axially expands downwards flag, then there will be competing/unphysical forces of upwards/downwards expansion between the series of axially linked components. This will likely leave to unexpected behavior. To prevent it there should be a check.

Note, need #942 merged in before this can open back up.


Multiple lines in graph

This is not supporting multiple lines in a single chart.

Did you find any solution ? i also require multiple lime graph with sort of same implementation.

This is not supported at the moment. Unfortunately, i don't think we plan to implement this feature anytime soon.
If you or somebody could open a PR for this, that would be great. What do you think @mrousavy ?

I think this requires a few structural changes and is a little bit of work. We don't plan to implement that anytime soon, but if you need this feature developed by us, contact us at<EMAIL_ADDRESS>:)

@mrousavy, would a PR be considered?

I have creates multiple line graphs with SVG, soon I will make package and make open source.

@sidferreira

@mrousavy, would a PR be considered?

Yes! If you shoot me a PR, we can review it :)

@sidferreira a PR would be much appreciated 🙏🏽

@youssdevx although I had some local work, my main need was cancelled, so I don't know when I'll be able to

Could you maybe push your work? I'll try to work on it

I'll try

https://github.com/sidferreira/react-native-graph-tests
https://github.com/sidferreira/react-native-graph/tree/multiple-graphs
What I tried to do is to create a shared const panGesture = usePanGesture({holdDuration: 100}); that is an argument for the graph, and then you can have a main graph and all others (using pointerEvents="none") will follow it
@youssdevx @mrousavy

I also tried to make the graph generic type

I'll look into it, many thanks 🙏🏽

@youssdevx https://github.com/margelo/react-native-graph/pull/66 too

I still did have the chance to work on this... @mrousavy do you have plans for this feature?

FYI, the new version of Victory has multiple lines, area charts...  => https://github.com/FormidableLabs/victory-native-xl

Any updates on this feature request?

https://github.com/FormidableLabs/victory-native-xl 👀

@mrousavy do you have plans for this feature?

 But if you submit a PR we can review it and merge it :)

Does anybody have a PR for this? with some draft ?

we opened a PR now. Would love feedback on it to see how we can improve it tto fit the quality of this library.
https://github.com/margelo/react-native-graph/pull/116


pyhandle 1.1.1 fails to install on Centos 7.x using pip2

When trying to install pyhandle 1.1.1 with pip2 it fails with the following error:
Yue are using pip version 8.1.2, however version 22.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting pyhandle
  Downloading https://files.pythonhosted.org/packages/c6/c1/f787154f5f9f2ae242c40875f12bc39b9bd98161f286252e77c80982ccbb/pyhandle-1.1.1.tar.gz (76kB)
    Complete output from command python setup.py egg_info:
    /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'python_requires'
      warnings.warn(msg)
    /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'long_description_content_type'
      warnings.warn(msg)
    error in pyhandle setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-kpCUCs/pyhandle/
You are using pip version 8.1.2, however version 22.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
The command '/bin/sh -c pip3 install -r /app/B2SAFE-core/scripts/tests/requirements.txt &&     pip2 install PyMySQL==0.10.1 &&     pip2 install pyhandle' returned a non-zero code: 1

The previous version of pyhandle installed fine. This was version: 1.0.4
$ pip2 list | grep handle
...
pyhandle (1.0.4)
...

Installing 1.0.4 using pip2
ollecting pyhandle==1.0.4
  Downloading https://files.pythonhosted.org/packages/a4/df/d500ba0a738e337b1c202919aec27050837e9f87eff81303c9f0e9a713a1/pyhandle-1.0.4.tar.gz (71kB)
Requirement already satisfied (use --upgrade to upgrade): requests in /usr/lib/python2.7/site-packages (from pyhandle==1.0.4)
Collecting datetime (from pyhandle==1.0.4)
  Downloading https://files.pythonhosted.org/packages/1d/bb/8e43c08cf8520816abe7afc5b5bff2a83807f371af90e7067d348b6a29ef/DateTime-4.5-py2.py3-none-any.whl (52kB)
Collecting future (from pyhandle==1.0.4)
  Downloading https://files.pythonhosted.org/packages/45/0b/38b06fd9b92dc2b68d58b75f900e97884c45bedd2ff83203d933cf5851c9/future-0.18.2.tar.gz (829kB)
Requirement already satisfied (use --upgrade to upgrade): six in /usr/lib/python2.7/site-packages (from pyhandle==1.0.4)
Requirement already satisfied (use --upgrade to upgrade): pymysql in /usr/lib/python2.7/site-packages (from pyhandle==1.0.4)
Collecting pytz (from datetime->pyhandle==1.0.4)
  Downloading https://files.pythonhosted.org/packages/60/2e/dec1cc18c51b8df33c7c4d0a321b084cf38e1733b98f9d15018880fb4970/pytz-2022.1-py2.py3-none-any.whl (503kB)
Collecting zope.interface (from datetime->pyhandle==1.0.4)
  Downloading https://files.pythonhosted.org/packages/47/55/20205df173d5c544a0002ee4b8f3aa862e3f1e2a0994a76ceed1587017f2/zope.interface-5.4.0-cp27-cp27mu-manylinux1_x86_64.whl (247kB)
Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/lib/python2.7/site-packages (from zope.interface->datetime->pyhandle==1.0.4)
Installing collected packages: pytz, zope.interface, datetime, future, pyhandle
  Running setup.py install for future: started
    Running setup.py install for future: finished with status 'done'
  Running setup.py install for pyhandle: started
    Running setup.py install for pyhandle: finished with status 'done'
Successfully installed datetime-4.5 future-0.18.2 pyhandle-1.0.4 pytz-2022.1 zope.interface-5.4.0
You are using pip version 8.1.2, however version 22.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Hi! I could not reproduce this. I used a CentOS 7 docker image, installed pip on it and tried to install pyhandle, which all worked perfectly. Have you tried updating pip?
My steps in trying to reproduce:
# Running a CentOS 7 test docker:
[me@localhost ~]$ docker run --name test -it centos:centos7.9.2009 /bin/bash
[root@9e6effe0556d /]# python --version
Python 2.7.5

# Installing pip:
[root@9e6effe0556d /]# curl -o get-pip.py https://bootstrap.pypa.io/pip/2.7/get-pip.py
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1863k  100 1863k    0     0   314k      0  0:00:05  0:00:05 --:--:--  424k
[root@9e6effe0556d /]# python get-pip.py
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Collecting pip<21.0
  Downloading pip-20.3.4-py2.py3-none-any.whl (1.5 MB)
     |################################| 1.5 MB 6.2 MB/s
Collecting setuptools<45
  Downloading setuptools-44.1.1-py2.py3-none-any.whl (583 kB)
     |################################| 583 kB 4.3 MB/s
Collecting wheel
  Downloading wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Installing collected packages: pip, setuptools, wheel
Successfully installed pip-20.3.4 setuptools-44.1.1 wheel-0.37.1

# Installing pyhandle using pip:
[root@9e6effe0556d /]# pip install pyhandle
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Collecting pyhandle
  Downloading pyhandle-1.0.4.tar.gz (71 kB)
     |################################| 71 kB 119 kB/s
Collecting requests
  Downloading requests-2.27.1-py2.py3-none-any.whl (63 kB)
     |################################| 63 kB 316 kB/s
Collecting datetime
  Downloading DateTime-4.5-py2.py3-none-any.whl (52 kB)
     |################################| 52 kB 201 kB/s
Collecting future
  Downloading future-0.18.2.tar.gz (829 kB)
     |################################| 829 kB 4.6 MB/s
Collecting six
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pymysql
  Downloading PyMySQL-0.10.1-py2.py3-none-any.whl (47 kB)
     |################################| 47 kB 1.3 MB/s
Collecting certifi>=2017.4.17
  Downloading certifi-2021.10.8-py2.py3-none-any.whl (149 kB)
     |################################| 149 kB 15.6 MB/s
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.11-py2.py3-none-any.whl (139 kB)
     |################################| 139 kB 25.8 MB/s
Collecting idna<3,>=2.5; python_version < "3"
  Downloading idna-2.10-py2.py3-none-any.whl (58 kB)
     |################################| 58 kB 1.6 MB/s
Collecting chardet<5,>=3.0.2; python_version < "3"
  Downloading chardet-4.0.0-py2.py3-none-any.whl (178 kB)
     |################################| 178 kB 21.6 MB/s
Collecting pytz
  Downloading pytz-2022.1-py2.py3-none-any.whl (503 kB)
     |################################| 503 kB 5.5 MB/s
Collecting zope.interface
  Downloading zope.interface-5.4.0-cp27-cp27mu-manylinux2010_x86_64.whl (247 kB)
     |################################| 247 kB 5.4 MB/s
Requirement already satisfied: setuptools in /usr/lib/python2.7/site-packages (from zope.interface->datetime->pyhandle) (44.1.1)
Building wheels for collected packages: pyhandle, future
  Building wheel for pyhandle (setup.py) ... done
  Created wheel for pyhandle: filename=pyhandle-1.0.4-py2.py3-none-any.whl size=93608 sha256=5de55ee53495e3491b1d2e8fcd9e80b96e4d2464dc16135314e8d060b191cfd2
  Stored in directory: /root/.cache/pip/wheels/ff/30/34/9ef4e0391a8e7438f37dc5bba62f9257474347759c9b3a7211
  Building wheel for future (setup.py) ... done
  Created wheel for future: filename=future-0.18.2-py2-none-any.whl size=502566 sha256=83c0e3994adfefd64a03013891be36ad2ce2771afbfb980d969fd665b5ed79d0
  Stored in directory: /root/.cache/pip/wheels/5f/11/0c/aad680baf5ef4fbcbab992c9f03e1130357e0c173a4fdabfff
Successfully built pyhandle future
Installing collected packages: certifi, urllib3, idna, chardet, requests, pytz, zope.interface, datetime, future, six, pymysql, pyhandle
  Attempting uninstall: chardet
    Found existing installation: chardet 2.2.1
    Uninstalling chardet-2.2.1:
      Successfully uninstalled chardet-2.2.1
Successfully installed certifi-2021.10.8 chardet-4.0.0 datetime-4.5 future-0.18.2 idna-2.10 pyhandle-1.0.4 pymysql-0.10.1 pytz-2022.1 requests-2.27.1 six-1.16.0 urllib3-1.26.11 zope.interface-5.4.0

# Importing it works fine:
[root@9e6effe0556d /]# python
Python 2.7.5 (default, Oct 14 2020, 14:45:30)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-44)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyhandle
>>>

Hi,
We install pip in a more regular way in our docker image:
yum install python2-pip

And you test and get version 1.0.4. While we try it and get version 1.1.1.
And that fails to install.
It can be seen in the following raw data of our docker image installation:
Step 11/14 : RUN pip3 install -r /app/B2SAFE-core/scripts/tests/requirements.txt &&     pip2 install PyMySQL==0.10.1 &&     pip2 install pyhandle
 ---> Running in 6177feb9ee33
WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3 install --user` instead.
Collecting defusedxml==0.4.1 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 1))
  Downloading https://files.pythonhosted.org/packages/09/3b/b1afa9649f48517d027e99413fec54f387f648c90156b3cf6451c8cd45f9/defusedxml-0.4.1.tar.gz (48kB)
Collecting funcsigs==0.4 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 2))
  Downloading https://files.pythonhosted.org/packages/5e/9f/025d4c92c6a1a94313cdf0813cd76f5700f8e5434fa15165090a6446ae22/funcsigs-0.4-py2.py3-none-any.whl
Collecting httplib2==0.9.2 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 3))
  Downloading https://files.pythonhosted.org/packages/ff/a9/5751cdf17a70ea89f6dde23ceb1705bfb638fd8cee00f845308bf8d26397/httplib2-0.9.2.tar.gz (205kB)
Collecting lxml (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 4))
  Downloading https://files.pythonhosted.org/packages/0f/4e/e139648475c0eb42cdb813461ae11f567e1888a20d7dfd5256f47e32909d/lxml-4.9.1-cp36-cp36m-manylinux_2_5_x86_64.manylinux1_x86_64.whl (5.6MB)
Collecting mock==1.0.1 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 5))
  Downloading https://files.pythonhosted.org/packages/a2/52/7edcd94f0afb721a2d559a5b9aae8af4f8f2c79bc63fdbe8a8a6c9b23bbe/mock-1.0.1.tar.gz (818kB)
Collecting pbr==1.8.1 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 6))
  Downloading https://files.pythonhosted.org/packages/fc/37/94af8387babb09796d306b18cf94ee5c70388c875a16d8a88e471500452c/pbr-1.8.1-py2.py3-none-any.whl (89kB)
Collecting queuelib==1.4.2 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 7))
  Downloading https://files.pythonhosted.org/packages/16/4f/b307fc978a21bfbb138e8e01a9f4953191d439e30578f5e4fd5befa77de1/queuelib-1.4.2-py2.py3-none-any.whl
Collecting simplejson==3.8.1 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 8))
  Downloading https://files.pythonhosted.org/packages/70/b0/c8169f6c2b7927614bea25636485992248ae0b1d7bc83858a9185461f57b/simplejson-3.8.1.tar.gz (76kB)
Collecting six==1.10.0 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 9))
  Downloading https://files.pythonhosted.org/packages/c8/0a/b6723e1bc4c516cb687841499455a8505b44607ab535be01091c0f24f079/six-1.10.0-py2.py3-none-any.whl
Collecting wheel==0.24.0 (from -r /app/B2SAFE-core/scripts/tests/requirements.txt (line 10))
  Downloading https://files.pythonhosted.org/packages/e8/14/eaaac12b0432c984a27ad0050a5a0bedc6135df35a0f5f1f35228faf12d4/wheel-0.24.0-py2.py3-none-any.whl (63kB)
Installing collected packages: defusedxml, funcsigs, httplib2, lxml, mock, pbr, queuelib, simplejson, six, wheel
  Found existing installation: defusedxml 0.7.1
    Uninstalling defusedxml-0.7.1:
      Successfully uninstalled defusedxml-0.7.1
  Running setup.py install for defusedxml: started
    Running setup.py install for defusedxml: finished with status 'done'
  Running setup.py install for httplib2: started
    Running setup.py install for httplib2: finished with status 'done'
  Running setup.py install for mock: started
    Running setup.py install for mock: finished with status 'done'
  Running setup.py install for simplejson: started
    Running setup.py install for simplejson: finished with status 'done'
  Found existing installation: six 1.16.0
    Uninstalling six-1.16.0:
      Successfully uninstalled six-1.16.0
Successfully installed defusedxml-0.4.1 funcsigs-0.4 httplib2-0.9.2 lxml-4.9.1 mock-1.0.1 pbr-1.8.1 queuelib-1.4.2 simplejson-3.8.1 six-1.10.0 wheel-0.24.0
Collecting PyMySQL==0.10.1
  Downloading https://files.pythonhosted.org/packages/1a/ea/dd9c81e2d85efd03cfbf808736dd055bd9ea1a78aea9968888b1055c3263/PyMySQL-0.10.1-py2.py3-none-any.whl (47kB)
Installing collected packages: PyMySQL
Successfully installed PyMySQL-0.10.1
You are using pip version 8.1.2, however version 22.2.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting pyhandle
  Downloading https://files.pythonhosted.org/packages/c6/c1/f787154f5f9f2ae242c40875f12bc39b9bd98161f286252e77c80982ccbb/pyhandle-1.1.1.tar.gz (76kB)
    Complete output from command python setup.py egg_info:
    /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'python_requires'
      warnings.warn(msg)
    /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'long_description_content_type'
      warnings.warn(msg)
    error in pyhandle setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-8kIetg/pyhandle/
You are using pip version 8.1.2, however version 22.2.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
The command '/bin/sh -c pip3 install -r /app/B2SAFE-core/scripts/tests/requirements.txt &&     pip2 install PyMySQL==0.10.1 &&     pip2 install pyhandle' returned a non-zero code: 1

Was it fixed in #85 ?


Please provide better RBAC guidance

This article states "You must be an admin for a business subscription to use these support methods.".  Please define what an "admin for a business subscription" is.  No such role exists, as far as I can tell, in Azure AD or O365 roles and permissions.  In AAD it looks like I might need "Billing Admin" or "Service Support Admin" to manage our support requests, but I'm not sure if that is the same list as I can see in the MS Services Hub or in the Azure "Help & Support" portal.
Frankly, all of these support requests should be centralized and visible through a single portal.

Please tell me specifically what role I need to assign to my director so that he can see the list of all of our open support tickets - especially for his monthly meeting with our CSAM!
Thanks.

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

ID: 1ed50e50-a3c1-1f3b-1ea5-40beec8ab6cd
Version Independent ID: 1ed50e50-a3c1-1f3b-1ea5-40beec8ab6cd
Content: Get support - Microsoft 365 admin
Content Source: microsoft-365/admin/get-help-support.md
Service: microsoft-365-business
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@cmcatee-MSFT Please help us in resolving this issue. Thanks

@HoCGeek You can assign someone the Service Support admin role so that they can open and manage support requests. There's a list of the admin roles available in the Microsoft 365 admin center here: Commonly used Microsoft 365 admin center roles. I'll update the article to include a link to that list.


Quartz ore handling

I've never done this, I don't understand what I'm doing, but if copypasta serves right, there is a chance that this is correct.
I'm not putting CLAY in at the same time because, see above, I don't know what I'm doing. ;)

Does quartz ore give one quartz or more?

Nether quartz ore http://minecraft.gamepedia.com/Nether_quartz_ore mined
using a pickaxe http://minecraft.gamepedia.com/Pickaxe will drop one unit
of nether quartz. If the pickaxe is enchanted with fortune, it may drop an
extra unit per level of fortune, up to a maximum of 4 with Fortune III. If
the pickaxe is enchanted with silk touch, the ore will be dropped.
On Wed, Apr 22, 2015 at 9:55 AM, NiLSPACE<EMAIL_ADDRESS>wrote:

Does quartz ore give one quartz or more?
—
Reply to this email directly or view it on GitHub
https://github.com/mc-server/MCServer/pull/1888#issuecomment-95067058.

About the brace, want me to try this again?
On Wed, Apr 22, 2015 at 12:34 PM<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Nether quartz ore http://minecraft.gamepedia.com/Nether_quartz_ore mined
using a pickaxe http://minecraft.gamepedia.com/Pickaxe will drop one
unit of nether quartz. If the pickaxe is enchanted with fortune, it may
drop an extra unit per level of fortune, up to a maximum of 4 with Fortune
III. If the pickaxe is enchanted with silk touch, the ore will be dropped.
On Wed, Apr 22, 2015 at 9:55 AM, NiLSPACE<EMAIL_ADDRESS>wrote:

Does quartz ore give one quartz or more?
—
Reply to this email directly or view it on GitHub
https://github.com/mc-server/MCServer/pull/1888#issuecomment-95067058.

You can just add it in this pull request.

Not sure if I need to click another different pull request button, but I made the change.

Like so?

Any chance you could do all these commits into a single commit?

Should I create a whole new one? I don't know how to otherwise "combine"
these.
On Wed, Apr 22, 2015 at 3:09 PM, NiLSPACE<EMAIL_ADDRESS>wrote:

Any chance you could do all these commits into a single commit?
—
Reply to this email directly or view it on GitHub
https://github.com/mc-server/MCServer/pull/1888#issuecomment-95171301.

I think @madmaxoft knows how to do that.
(Don't forget to rename E_ITEM_QUARTZ to E_ITEM_NETHER_QUARTZ btw)

Yes, I did rename it... or at least I think I did.
Sorry, in the end, you had a lot of time wasted just because I tried doing this.
Probably should stick to just pointing things out.
I'll wait for MadMaxoft.

Normally you'd need to use an advanced git technique called "interactive rebasing", which is a bit involved. I'll see if I can do it for you (tomorrow).

Thank you! :)

I managed to keep you as the author of the commit :)

O, the blood I shed, fighting for it to see the day ;).
Thanks! :)
On Thu, Apr 23, 2015 at 3:23 PM, Mattes D<EMAIL_ADDRESS>wrote:

I managed to keep you as the author of the commit :)
—
Reply to this email directly or view it on GitHub
https://github.com/mc-server/MCServer/pull/1888#issuecomment-95581336.


[Console-IoT] Add id to connection module

Type of change

Refactoring

Description
 Add meaningful ID to connections component
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

Can one of the admins verify this patch?


Improve error handling in OnSendDailyTelemetry

Summary
There are blocks in the OnSendDailyTelemetry function that check for an error, and log the error, but doesn't actually handle the error afterwards. This PR makes it so we don't attempt to access the invalid return value used in the error'd function calls.
https://github.com/mattermost/mattermost-plugin-jira/blob/e4f60983998d0f474172df79f76b5d9b087e3838/server/plugin.go#L519-L531
Ticket Link

Codecov Report
Base: 30.14% // Head: 30.12% // Decreases project coverage by -0.02% :warning:

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

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #913      +/-   ##
==========================================
- Coverage   30.14%   30.12%   -0.02%
==========================================
  Files          49       49
  Lines        7468     7466       -2
==========================================
- Hits         2251     2249       -2
  Misses       5028     5028
  Partials      189      189

Impacted Files
Coverage Δ

server/plugin.go
9.50% <0.00%> (+0.05%)
:arrow_up:

server/subscribe.go
65.71% <0.00%> (-0.30%)
:arrow_down:

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

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

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 7a5c6162b49c36cffd33d61cf8ad38152c17b1ae


Add compiled_with_cxx11_abi API

Description
Added a build option for specifying cxx1_abi, and a function to retrieve what ABI was used during compilation.
@leezu FYI
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@szha @eric-haibin-lin we shouldn't add a D_GLIBCXX_USE_CXX11_ABI option as this is a hidden feature of the gcc compiler and MXNet supports any C++17 compatible compiler (ie. this feature breaks non-gcc compiler support). Instead, we can add a more general ABI selector or verify that the option is only added when compiling with gcc.