How to produce individual embeddings for each face image ?

I wants to build the face clustering module, so i need to get the embedding's for each face?

I wants to build the face clustering module, so i need to get the embedding's for each face?

Hi, you may extract features for each face using our released model and the feature extraction APIs (.util/extract_feature_v1/v2.py).


logs from install phase don't show up

if you pass -a, they show up like this
{
  process: 'install',
  stream: 'stderr',
  timestamp: xxx,
  text: '...'
}

fixed in v2.15.0


Removing lodash

Lodash is great ultil library however this project is not heavily depend on it and some are supporting by ES6 so we will remove lodash soon to reduce the size of the bundle file.

We are not removing the lodash however adding the babel-plugin-lodash help to reduce the sign from ~104kb to ~34kb


[BUG] use onRecvOfflineNewMessage cant receive message

Describe the bug

How to reproduce

Steps to reproduce the behavior:

debug my app in my real phone
let my app run in background
use web ,send message to my app
4.no log and no notification

Expected behavior

Version information

Device: iPhone 12
OS: iOS 14.7.1
Package Version: 3.8
Flutter Version: v3.19.0

hi，On iOS, you need to use the PUSH function.


Changelog uses date from wrong tag for release message

When calling git-changelog for my project like this: git-changelog 0.9.0 0.8.0 --format slack it contains a line like the following: Version 0.9.0 (_03.09.2015_)
But 03.09.2015 is in fact the date of the tag 0.8.0. Instead, I would have expected it to pick up the date from the tag 0.9.0, which would be 17.09.2015.
I think the cause may be this line and this line (this should probably be DRYed up by abstracting the information retrieval to a new class for example), which should be str << " (_#{@commit_from.time.strftime("%d.%m.%Y")}_)" (from instead of to) instead.

The bug has been fixed in #5, but I agree that this should still be DRYed up.


When the request body has nested objects , ToJson() method is failing to deserialize the object .

Specs URI :
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/azsadmin/resource-manager/deployment/Microsoft.Deployment.Admin/
Please refer to this readme.md file for the changes required before generating the PS cmdlets :
https://github.com/kegangum/azurestack-powershell/blob/users/kegangum/autorest/src/Azs.Deployment.Admin/readme.md#autorest-configuration
To generate PS cmdlets , navigate into the 'azurestack-powershell\src\Azs.Deployment.Admin' folder and  run :
autorest
pwsh
.\build-module.ps1
The cmdlet which is causing the issue is :
Invoke-AzsProductDeployAction -Product 'microsoft.nullprovider' -Version '1.1' -Parameter @{}
This PS cmdlet is calling the DeployActionProduct method in the '\azurestack-powershell\src\Azs.Deployment.Admin\generated\api\DeploymentAdminClient.cs' . Please find this method in the attached screenshot.
DeployActionProduct method is formulating the request.Content :
request.Content = new global::System.Net.Http.StringContent(null != body ? body.ToJson(null).ToString() : @"{}", global::System.Text.Encoding.UTF8);
The object 'body' is of type 'DeployActionParameters' . This body has nested object 'Parameter' of type 'DeployActionParameters1' and a 'version' of type 'string'. Request.Content is obtained by deserialzing the body, with this expression body.ToJson() .
This expression , body.ToJson() is removing the nested object(DeployActionParameters1) and returning a Json which has only 'version' in it .
But , I'm able to read the nested object with this expression : body.Parameter.ToJson() .
Example :
body is {"Parameter" : {object of DeployActionParameters1 type } , "version" : "1.1"}
The output from the body.ToJson()
Actual :
{"version" : '1.1'}
Expected :
{"Parameter" : @{} , "version":"1.1"}
Please make ToJson() method to return the nested objects .

@dolauli I know you are busy with other work items, Are you aware of the issue here?

@kegangum
2 things that I do not understand:
Your actual response and expected response:
Example :
body is {"Parameter" : {object of DeployActionParameters1 type } , "version" : "1.1"}

The output from the body.ToJson()

Actual :
{"version" : '1.1'}

Expected :
{"Parameter" : @{} , "version":"1.1"}

Please ....

Because single qoute ' and is not JSON and @{} is not JSON:
Example :
body is {"Parameter" : {object of DeployActionParameters1 type } , "version" : "1.1"}

The output from the body.ToJson()

Actual :
{"version" : "1.1"}
or
{"version" : 1.1}

Expected :
{"Parameter" : "@{}" , "version":"1.1"}
or
{"Parameter" : {} , "version":"1.1"}
or
{"Parameter" : {} , "version": 1.1}

Please ....


Refactor HashMap Tests to use Matchers and Extend Tests

Overall, it's wonderful to see such an improvement in coverage.
Two minor concerns:

Using matchers is an improvement for when a test fails (since the output explains the intended property, and more human-readable stuff about what went wrong), but all of the independent suites are sharing a mutable HashMap in this instance.  It seems like they all just read from it (only), but there is nothing about matchers that actually enforces that.  Seems fine for now, but it's something that maybe warrants a comment explaining that invariant.

The prior test suite was very incomplete, but at least it used an initial hash table that was larger than only five elements.  Many of the operations here are using very tiny hash tables.  Is that a concern?  (Seems like we want to cover many size classes, from empty, to tiny, to those that have undergone growth, perhaps more than once?)

@matthewhammer Point taken. Will update the tests accordingly!

@crusso Okay tests updated to use Nat


package undefined does not exist import undefined.CustomerIOReactNativePackage;

SDK version: 3.9.0
Environment: Development
React Native version 0.68.5
Describe the bug

When building the project after upgrading the package from v2 to v3, I keep getting this error.
demoapp/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:41: error: package undefined does not exist
import undefined.CustomerIOReactNativePackage;
                ^
demoapp/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:162: error: cannot find symbol
      new CustomerIOReactNativePackage(),
          ^
  symbol:   class CustomerIOReactNativePackage
  location: class PackageList
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors

FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
To Reproduce

Migrating from v2 to v3.9
Expected behavior

Screenshots

Additional context

To debug, I have already added these on MainApplication.java file but I keep getting the above error of undefined import in generated PackageList file.
import io.customer.reactnative.sdk.CustomerIOReactNativePackage; // Add this import ---
        @Override
        protected List<ReactPackage> getPackages() {
          @SuppressWarnings("UnnecessaryLocalVariable")
          List<ReactPackage> packages = new PackageList(this).getPackages();

          packages.add(new RNAppsFlyerPackage());
          packages.add(new CustomerIOReactNativePackage()); // Add this to the list ----
          return packages;
        }

Hi @Birat77. Thanks for reaching out and sharing the details. Sorry to hear about the challenges you're facing while upgrading. To help you better, could you please answer the following questions:

Can you confirm if you've followed all the steps mentioned in the migration guide?
Are there any additional steps or details that you followed and think could be helpful for us to identify the root cause?
You shouldn't need to add CustomerIOReactNativePackage to your MainApplication as auto-linking should add for you. Can you try cleaning the project, removing node_modules folder, reinstalling dependencies, and then running the app to see if that fixes the problem for you?
Since you mentioned you're currently running the app on 0.68.5, which is quite an old version. Can you please try upgrading your React Native version to a newer one? Gradle support may be limited with such old versions. Our SDK now supports Gradle 8, which requires at least Gradle version 7.4.1 to work and may not function correctly with older versions.

The steps shared above should help troubleshoot the issue. Let us know if you have any more questions!

All the steps were followed from the migration guide.
There are lots of packages to upgrade for the react-native.
Currently I'm using gradle version 7.6.
I will try upgrading the react-native app to >0.70 and try again

Closing due to inactivity. Please feel free to reopen if needed or ask any further questions you may have.


Supporting references and further reads for better understanding of the NIfTI and DICOM functionality.

Gist of dicom data in python
https://towardsdatascience.com/dealing-with-dicom-using-imageio-python-package-117f1212ab82
Gist of NIfTI data in julia and python
https://brainder.org/2012/09/23/the-nifti-file-format/
https://peerherholz.github.io/workshop_weizmann/data/image_manipulation_nibabel.html#
^ above are some good starting points for newbies, who might want to consider reading more about the ecosystem and capabilities.
Feel free to include them in references as the documentation for the project grows!

The ITK implementation of loading nifti files, (consists up of stuff for loading and saving header and pixeldata from .nii)
--ITK c++ nifti file loading
--dicom to nifti python program which using numpy , pydicom and nibabel

Sample Reference Medical Imaging dataset links :
https://drive.google.com/drive/folders/1HqEgzS8BV2c7xYNrZdEAnrHk7osJJ--2
https://wiki.cancerimagingarchive.net/display/Public/RIDER+Lung+PET-CT
https://wiki.cancerimagingarchive.net/pages/viewpage.action?pageId=23691656
More comprehensive ones 👍🏻
https://github.com/icometrix/dicom2nifti/tree/main/tests/data

For Generative Adversarial Networks (GAN's) resources for medical imaging
check out
"Awesome GAN for medical imaging on github"

Currently making a reference "memo or mem" for loading nifti file data, u can find that here :
https://mem.ai/p/rWZ9et3sk1U5gkybJdNK

References (from SITK) for loading spatial metadata
https://simpleitk.org/SimpleITK-Notebooks/01_Image_Basics.html
https://simpleitk.org/SPIE2019_COURSE/02_images_and_resampling.html

Amazing data science in julia chapter based book under geospatial stuff, also include pixel array transforms information around orientation and spacing.
https://juliaearth.github.io/geospatial-data-science-with-julia/05-transforms.html


[Do not merge] Test workflow failure reporting with throw away PR

Summary
A concise description of the changes being introduced. If you are submitting a PR for a
new quickstart please review the pre merge checklist section to validate this PR is ready for review.

Pre merge checklist

[ ] Did you check you NRQL syntax? - Does it work?
[ ] Did you check your dashboard image quality? -  Do they look good?
[ ] Did you check that your alerts actually work?
[ ] Did you include an InstallPlan and Documentation reference?
[ ] Did you check your descriptive content for voice, tone, spelling and grammar errors?
[ ] Did you attach images of your dashboards to the PR so we can see them working?

Screenshots
Attach images of any visual changes, such as a dashboard here.

Notice this failure is not being reported back https://github.com/newrelic/newrelic-quickstarts/runs/5146603741?check_suite_focus=true


[7.67.x][Rhpam-4465] Add quarkus-file-vault-utils instructions and support

Thank you for submitting this pull request
JIRA:
RHPAM-4465
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

https://github.com/kiegroup/process-migration-service/pull/72

Jenkins retest this


M109 Wait for Extruder misconfigured? (And additional Feedback)

In the Start GCODE, the M109 is configured as "R[HotendTemp]"
My Ender 3 Is configured to run on Klipper, it seems that M109 R[HotendTemp] is not supported.
Perhaps changing it to M109 S[HotendTemp] solves this, im testing that now.

FYI: I am using an Ender 3, that is running on Klipper. I had to increase the Maximum Crosssection as well as the Maximum Extrude Only Move to 2.5 and 250mm respectively.

While Testing, it seems that the generated Gcode is also not keeping the Temperature.

I am updating this as I continue to test.
First edit: I thought the M109 was missing completely, but looking at the gcode, it is set at the beginning of each temperature setting. Weirdly enough, it doesnt keep the temperature.
Second edit: Klipper apparently does not support the R Prefix on M109, I changed it for S, and am running the test again

I can confirm: the " Malconfigured" M109 is the "Issue".
This is purely to the fact that I am not running Marlin, but Klipper. And Klipper does not support M109 R[HotendTemp]
As additional feedback: It would be lovely to be able to add ones own StartGcode from the GetGo. I store most of my Starting Parameters and Logic within a GcodeMacro in Klipper.

Klipper doesn't support the R parameter for the M109 command, only S. Search replace s/M109 R/M109 S/ is quick fix for the generated gcode.
Marlin has different behaviours for the R and S parameters:
[R] | Target temperature (wait for cooling or heating).
[S] | Target temperature (wait only when heating). Also AUTOTEMP: The min auto-temperature.
Klipper implements S behaviour only and it is equivalent to R on Marlin:
Set extruder temperature and wait: M109 [T] S
Note: M109 always waits for temperature to settle at requested value
So it needs to be M109 R on Marlin and M109 S on Klipper.

Ah that makes more sense, Thank you :D


Setting up the English file

Not sure what you wanted this PR to be. Would you mind adding a description for it? Closing this for now to clear the pending PRs.

I would not use technical terms like access token
The JSON is not correctly formatted
I would avoid putting trailing commas, if you need to we should adjust where the terms are located


Opencl working, ish.

I am training with Andrej Karpathy's char rnn, and whenever I use opencl to train, the integrated intel hd graphics gets used and not my amd radeon pro 560x

Have you tried using the -gpuid (i.e. -gpuid 2) option?

I figured this out a bit ago and I fee kinda dumb, especially because I forgot I posted this. You need to use -opencl option and -gpuid option. Thanks mturlo for the comment.


Operation not permitted [/opt/factorio/bin/x64/../../config/config.ini]

After a while my friend and me wanted to come back to factorio.
So i updated my server to 1.1.107 (stable) and got this:
0.000 Error Util.cpp:86: filesystem error: cannot make canonical path: Operation not permitted [/opt/factorio/bin/x64/../../config/config.ini]
I checked older versions and the server will run a container up to 1.1.100, updating to 1.1.101 or newer results in error stated above.
Any suggestions?

Can you share how you start the container?
So I may be able to reproduce it.

Sure. I have a systemd-service:
[Unit]
Description=Factorio Server
After=docker.service
Requires=docker.service

[Service]
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker stop factorio4
ExecStartPre=-/usr/bin/docker rm factorio4
ExecStartPre=/usr/bin/docker pull factoriotools/factorio:stable
ExecStart=docker run \
        -d \
        -p 34200:34197/udp \
        -v /home/factorio4:/factorio \
        --name factorio4 \
        -e LOAD_LATEST_SAVE=false \
        -e SAVE_NAME=archievement.zip \
        factoriotools/factorio:stable
ExecStop=/usr/bin/docker stop factorio4
User=factorio
Group=factorio
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

resulting in:
docker logs factorio4 -f
+ FACTORIO_VOL=/factorio
+ LOAD_LATEST_SAVE=false
+ GENERATE_NEW_SAVE=false
+ PRESET=
+ SAVE_NAME=archievement.zip
+ BIND=
+ CONSOLE_LOG_LOCATION=
+ mkdir -p /factorio
+ mkdir -p /factorio/saves
+ mkdir -p /factorio/config
+ mkdir -p /factorio/mods
+ mkdir -p /factorio/scenarios
+ mkdir -p /factorio/script-output
+ [[ ! -f /factorio/config/rconpw ]]
+ [[ ! -f /factorio/config/server-settings.json ]]
+ [[ ! -f /factorio/config/map-gen-settings.json ]]
+ [[ ! -f /factorio/config/map-settings.json ]]
++ find -L /factorio/saves -iname '*.tmp.zip' -mindepth 1
++ wc -l
+ NRTMPSAVES=0
+ [[ 0 -gt 0 ]]
+ [[ '' == \t\r\u\e ]]
+ EXEC=
++ id -u
+ [[ 0 = 0 ]]
+ usermod -o -u 845 factorio
usermod: no changes
+ groupmod -o -g 845 factorio
+ chown -R factorio:factorio /factorio
+ EXEC='runuser -u factorio -g factorio --'
+ [[ -f /bin/box64 ]]
+ sed -i '/write-data=/c\write-data=\/factorio/' /opt/factorio/config/config.ini
++ find -L /factorio/saves -iname '*.zip' -mindepth 1
++ wc -l
+ NRSAVES=1
+ [[ false != true ]]
+ [[ 1 == 0 ]]
+ [[ false == true ]]
+ FLAGS=(--port "$PORT" --server-settings "$CONFIG/server-settings.json" --server-banlist "$CONFIG/server-banlist.json" --rcon-port "$RCON_PORT" --server-whitelist "$CONFIG/server-whitelist.json" --use-server-whitelist --server-adminlist "$CONFIG/server-adminlist.json" --rcon-password "$(cat "$CONFIG/rconpw")" --server-id /factorio/config/server-id.json)
++ cat /factorio/config/rconpw
+ '[' -n '' ']'
+ '[' -n '' ']'
+ [[ false == true ]]
+ FLAGS+=(--start-server "$SAVE_NAME")
+ exec runuser -u factorio -g factorio -- /opt/factorio/bin/x64/factorio --port 34197 --server-settings /factorio/config/server-settings.json --server-banlist /factorio/config/server-banlist.json --rcon-port 27015 --server-whitelist /factorio/config/server-whitelist.json --use-server-whitelist --server-adminlist /factorio/config/server-adminlist.json --rcon-password SOMESECRETPW --server-id /factorio/config/server-id.json --start-server archievement.zip
   0.000 Error Util.cpp:86: filesystem error: cannot make canonical path: Operation not permitted [/opt/factorio/bin/x64/../../config/config.ini]

any update?

We had pretty much the same problem. Up to version 1.1.101 everything was fine. But every version tested from 102 to 110 had the same error message. Even when setting up a new container without any save game.
We tried many different things, but nothing worked. So our last option was a new host os, since we were still using Ubuntu 19. Now with Ubuntu 22 everything is working for us.

I got the same problem so I brushed my docker skills to understand what was happening.
The problem is this PR added a user to the dockerfile. In particular this line where the ownership of /opt is changed. This does not play well with the user you also created on your system because it most probably have a different gid and uid.
IMO it is a mistake to deal with the user in the DOCKERFILE. That being said, the quickest way to fix your poblem is to change the uid/gid on your system to the one expected by the DOCKERFILE.
usermod -u 845 factorio # this change the userid
groupmod -g 845 factorio # this change the groupid

and fix the owernship of the factorio folder.
something along the line of:
chown -R 845:845 /home/factorio4 # or whatever path your using with -v

It fixed my problem, I hope it will fix yours also!

But that PR you linked is from 2020. Why would that make problems when switching to version 1.1.100 (or 101)?
Also the Quick Start guide already mentions that they use

a 'factorio' user with user id 845

and that you have to permit that user. Which I double checked to do.
The file or path mentioned in the error message /opt/factorio/bin/x64/../../config/config.ini is not part of the host system, so that shouldn't even be relevant on my first glance?
Your statement might not be wrong, but I don't think it is related to this problem. Even though I can't test ist anymore myself, since we reinstalled our host server.

Also the Quick Start guide already mentions that they use

You are right. Unfortunately, I skipped that part also. Reading the quick start guide it is not super clear that is expected to create the user on the system with the given uid/gid. Personally, I missed that step.

Why would that make problems when switching to version 1.1.100 (or 101)?

That is a great question and unfortunately, we won't be able to know because we don't know what changed in the code of factorio. I took a peek and the changelog and didn't looks at anything released.

The file or path mentioned in the error message /opt/factorio/bin/x64/../../config/config.ini is not part of the host system

I /think/ you are confusing vm and containers. Docker/podman is using the user specified by the config/user when running the container. If the uid/gid does not match this is where you can enter in permission problems. One easy experiment you can do is if you run as root and you start writing file in the mounted volume, those file will be owned by root on the host system.

Even though I can't test ist anymore myself, since we reinstalled our host server.

If you feel you want to give it another try, happy to take a look if this solution does not solve the problem :)


Is there a way via the command pallette to move the currently checked out file to another changelist?

I am looking for a way to access the following menu via the command pallette;

You can access this by right clicking a file in the SCM window and selecting 'move changelist'. But when I try to use the command Perforce: Move to changelist, nothing happens. No error or anything. Is this meant to function?
Ideally I'd like to have the following workflow;

Try to save a file.
Warning about write only.
Ctrl+P select the P4 edit option from the pallette.
Ctrl+P select the 'move changelist' option.
Select changelist, if it exists.

Anyone have any ideas on this? Should that command pallet function be hooked up to something?


GeoJSON layer remove/replace data

The L.geoJson API seems to be missing an API that would make it symmetric:
var layer = L.geoJson();

// we have this
layer.addData(foo);

// we don't have this
layer.removeData(foo);

// or this
layer.getData(foo);
layer.replaceData(foo);

// and if we had this
layer.data(foo); // set the data to foo
layer.data(); // get all data

// we could implement the rest as sugar

layer.clearLayers() is not working for me on version 0.7.3. Is this feature only available on the master branch?

Ah, never mind. Figured out that it is working.

Here is the code to the solution I implemented. I made a dictionary of all the layers that I could look up and remove whenever necessary.
    var parcelDict = {};

    var queryParcel = Parcel.find();

    queryParcel.observe({
      added: function (item) {
            parcelDict[item._id._str] = L.geoJson(item, {
                style: {
                    fillColor: "FFF", //overlay color
                    weight: 2,
                    opacity: 1,
                    color: "FFF", // border color
                    fillOpacity: 0.65
                },
                onEachFeature: onEachFeature
            }).addTo(mymap);
        },
      changed: function (newItem) {
          parcelDict[newItem._id._str].clearLayers();
          L.geoJson(newItem, {
                style: {
                    fillColor: "FFF", //overlay color
                    weight: 2,
                    opacity: 1,
                    color: "FFF", // border color
                    fillOpacity: 0.65
                },
                onEachFeature: onEachFeature
            }).addTo(mymap);
        }
    });

I think leaflet-ajax


[FIX] Save ml image data when not in supervised mode

Hello @patrickcleeve2! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fibsem/detection/utils.py:

Line 113:1: E302 expected 2 blank lines, found 1
Line 114:1: W293 blank line contains whitespace
Line 118:5: E722 do not use bare 'except'
Line 124:25: E261 at least two spaces before inline comment
Line 124:40: W291 trailing whitespace
Line 129:80: E501 line too long (83 > 79 characters)
Line 132:34: W291 trailing whitespace
Line 136:1: W293 blank line contains whitespace
Line 140:80: E501 line too long (86 > 79 characters)
Line 141:80: E501 line too long (90 > 79 characters)
Line 142:80: E501 line too long (95 > 79 characters)
Line 143:80: E501 line too long (94 > 79 characters)
Line 144:80: E501 line too long (89 > 79 characters)
Line 145:80: E501 line too long (100 > 79 characters)
Line 145:101: W291 trailing whitespace
Line 146:80: E501 line too long (87 > 79 characters)
Line 146:88: W291 trailing whitespace
Line 147:80: E501 line too long (82 > 79 characters)
Line 148:80: E501 line too long (83 > 79 characters)
Line 149:9: E124 closing bracket does not match visual indentation
Line 164:1: W293 blank line contains whitespace
Line 172:1: W293 blank line contains whitespace
Line 174:1: W293 blank line contains whitespace
Line 181:80: E501 line too long (121 > 79 characters)
Line 181:122: W291 trailing whitespace
Line 191:25: E261 at least two spaces before inline comment
Line 191:40: W291 trailing whitespace


Can't add prefix when have same vlan id

I have same vlan id on production network and out-of-band network on same site, I can add these 2 vlan with different vlan name, but when I add a prefix to one vlan, netbox display an error if another vlan have signed a prefix.How to resolve it ? Thanks

It's not clear what you're doing. Please describe the exact steps you're taking that result in an error.

sorry, it was caused by my spelling error，please close this issue.


Automate Zenodo DOI renewal

Integrated with https://github.com/railtoolkit/tikz-trackschematic/commit/0b1a14fbc9cd7f8bdd8ca00ea9dfbd6d63736ff2


elasticsearch-env: line 71: 124 Aborted  (core dumped)

Ubuntu 18.04.4 LTS, 4.15.0-76-generic
JRE version:  (11.0.6+10
OpenJDK 64-Bit Server VM (11.0.6+10, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Client: Docker Engine - Community Version:           19.03.5
Server: Docker Engine - Community  Version:          18.09.9
root@K8C01-W02:~# docker run --name elasticsearch bitnami/elasticsearch:latest
13:30:58.85
13:30:58.87 Welcome to the Bitnami elasticsearch container
13:30:58.87 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-elasticsearch
13:30:58.87 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-elasticsearch/issues
13:30:58.88 Send us your feedback at<EMAIL_ADDRESS>13:30:58.88
13:30:58.88 INFO  ==> ** Starting Elasticsearch setup **
13:30:59.00 INFO  ==> Configuring/Initializing Elasticsearch...
13:30:59.04 INFO  ==> Setting default configuration
13:30:59.06 INFO  ==> Configuring Elasticsearch cluster settings...
13:30:59.18 INFO  ==> ** Elasticsearch setup finished! **
13:30:59.19 INFO  ==> ** Starting Elasticsearch **
A fatal error has been detected by the Java Runtime Environment:
SIGILL (0x4) at pc=0x00007efdd42be7f2, pid=124, tid=125
JRE version:  (11.0.6+10) (build )
Java VM: OpenJDK 64-Bit Server VM (11.0.6+10, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Problematic frame:
v  ~StubRoutines::call_stub
Core dump will be written. Default location: Core dumps may be processed with '/usr/share/apport/apport %p %s %c %d %P" (or dumping to //core.124)
An error report file with more information is saved as:
/tmp/hs_err_pid124.log
Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled
If you would like to submit a bug report, please visit:
https://github.com/AdoptOpenJDK/openjdk-support/issues
/opt/bitnami/elasticsearch/bin/elasticsearch-env: line 71:   124 Aborted                 (core dumped) "$JAVA" -cp "$ES_CLASSPATH" org.elasticsearch.tools.java_version_checker.JavaVersionChecker
can some help me, by explain what this error mean, and how can i solve this issue.
thank you

Please see https://github.com/AdoptOpenJDK/openjdk-build/issues/893. Should be fixed in 11.0.7+4 or better.


feat: allow disabling heuristics on annotations like @NotNull

Add a property forceUseRequired on @Schema annotations that allows disabling the heuristics on annotations like @NotNull which otherwise may force the required status to true even if @Schema(required = false)
Proposal for issue #4213

replaced by #4286


Metadata write is not atomic

The write_text function used to write config file is not atomic
https://stackoverflow.com/questions/73883435/is-python-3-path-write-text-from-pathlib-atomic

Thanks for pointing that out. I'm aware that some of the actions are non-atomic and they might cause trouble but since those actions are infrequent, I expect them to barely matter. Also, even if things go wrong, the corruption is not FATAL, and should be fairly easy to fix.
Those are the reasons I haven't spent time on fixing it yet. That said, PRs are welcome as long they keep it simple.


Use PlainTextResponse for handling validation errors.

Resolves #21

Codecov Report

Merging #23 (4ddb83a) into master (9b5ebcd) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          550       555    +5
=========================================
+ Hits           550       555    +5

Impacted Files
Coverage Δ

src/main.py
100.00% <100.00%> (ø)

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


Support UI resources in src/main/java in JavaFX JPA example.

Configured resource-handling in maven build so that we now pick-up UI resources from src/main/java.
Previously we required users to build parallel package hierarchies in src/main/resources in order to support UI resources. This can be a bit cumbersome to work with when packages are refactored etc.
This fixes #4.

Merged in to master.


Build a minimal PyPI based Docker image for MSRuleCleaner

Impact of the new feature
Overhaul the Dockerfile for reqmgr2ms, splitting out into separate containers for each microservice. Containers should be as small as possible. Container will use PyPI packages instead of the current RPM based deployment method.
Is your feature request related to a problem? Please describe.
reqmgr2ms container is currently very large and is used for multiple microservices, which is not ideal for k8s.
Describe the solution you'd like
Build a minimal Docker image using the MSRuleCleaner package from PyPI
Describe alternatives you've considered
NA
Additional context
NA

I provided initial Dockerfile to build docker image and it was successfully build, see details in https://github.com/dmwm/WMCore/issues/11310.

Basic functionality of these PyPi-based services have been tested with docker image label: 2.1.6rc3.
Workflows are getting their input rules evaluated and moving to staged status!
In addition to the changes already linked above, the following was required as well:
Mount rucio-secrets and rename the docker image name for microservices, global workqueue and t0_reqmon:
https://github.com/dmwm/CMSKubernetes/pull/1261
https://github.com/dmwm/CMSKubernetes/pull/1283
https://github.com/dmwm/CMSKubernetes/pull/1287
Fix to the run.sh script in the dmwm-base image:
https://github.com/dmwm/CMSKubernetes/pull/1288
A more in depth validation is still required and will be tracked through: https://github.com/dmwm/WMCore/issues/11354
Closing this one out.


ionic package command:  Add support for setting version and note

Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Note: for build related issues you can open up an issue on the ionic-app-scripts repo
https://github.com/driftyco/ionic-app-scripts
Please ensure that you are on the latest version of the CLI.
npm view ionic@latest version
What version of the CLI are you using? Output of ionic --version
2.2.1
Short description of the problem:
This is an enhancement request. It would be nice when creating a "package".  e.g. ionic package build ios --profile prod --release  to be able to attach a note or version via command line .  Currently all packages are uploaded with the message: "Ionic Package Upload"
What behavior are you expecting?
Right now we run the package command.  Go to the ionic.io cloud site.  We then go to the deploy tab and click edit.  On that modal they give you options to "add a note" which defaults to "Ionic Package Upload".  In our case we change the note to " ".  e.g. "Test 1.2.1" or  "Prod 1.2.1".  The next thing we do is then update the Version tab and set the version.  It would be nice for this to be pulled from the version in the cordova.xml file.  Our ideal state is to set the version based on cordova.xml and then we can set the note when we run the package command:
ionic package build ios --profile prod --release --note "Test 1.2.3
Steps to reproduce:

ionic package build ios --profile prod --release
go to your ionic.io site and look at what was uploaded

Where is the documentation for some of the api's that ionic-app-lib/package.js references?  I'm trying to find out what  the package/build api accepts in the post.
lib/package.js:sendToPackageServie(390)
url: settings.IONIC_DASH_API + 'apps/' + appId + '/package/builds/',

https://docs.ionic.io/services/package/#building

That does not show how to add a note @jthoms1 ?

Sorry that was in reference to not finding the documentation. @dwieeb Do you have any information on whether this could be intetegrated into the CLI?

I think I saw something similar in the upload command.  I can find the file
and line number.
On Tue, Feb 28, 2017, 8:17 AM Josh Thomas<EMAIL_ADDRESS>wrote:

Sorry that was in reference to not finding the documentation. @dwieeb
https://github.com/dwieeb Do you have any information on whether this
could be intetegrated into the CLI?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/driftyco/ionic-cli/issues/1942#issuecomment-283036086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkr39qpM4LFU9pzFz7k2y39z4lTktIvks5rhB57gaJpZM4MKpdr
.

"version": ""
add this leaving blank.

@kaszona  what does your comment mean?

leave this  blank. No need to add any version there.

Either you can write there like this "version": "1.0.0"

@ncapito @kaszona This functionality will be in the latest beta release of CLI v3 soon. Good idea!

@dwieeb  i just used this!  Thanks again.  Such a helpful change.

@ncapito You're welcome 😄 Thanks for following up. I'll close the issue.


test-requirements.txt: Sync

Reviewers Checklist

[ ] Appropriate logging is done.
[ ] Appropriate error responses.
[ ] Handle every possible exception.
[ ] Make sure there is a docstring in the command functions. Hint: Lookout for
botcmd and re_botcmd decorators.
[ ] See that 100% coverage is there.
[ ] See to it that mocking is not done where it is not necessary.

ack https://github.com/coala/corobo/pull/612/commits/6d074805e36831108e4d1b4d151269127370fa4f

@gitmate-bot ff


v3.3 Can't flash via fox magisk module manager

Hi, I would like to ask you that, this module can't be installed via magisk module manager, however it can be installed from magisk directly.
I am on magisk 25.1, app 26.2
magisk module manager v1.1.0
mindetach version3.3 and 2.4
Previously I had mindetach v2.4 installed via magisk module manager and there were no problem. While installing mindetach v3.3 via magisk module manager the terminal shows something similar to
- Do not clean the data of Play Store
- Open Play Store and reflash mindetach again!

I did as it asked by opening the play store, then reflash mindetach v3.3 via magisk module manager; results were the same with the error above.

@sarf2k4 installing mindetach latest v3.3 works fine incl. correct detaching via latest Fox's Mmm - Androidacy Module Manager, tested with v.2.1.1.

Thank you @LeeBinder for the info. I was avoiding v2.0.2 as they had the flashing bugs going on. I can confirm mindetach can be flash via fmmm v2.1.1 too


chproxy mistakenly detects remote client connection closing

We are currently using chproxy version 1.12.0.
When running heavier queries that take longer time, they are being killed after some time, despite having max_execution_time value set to 0 in both chproxy and clickhouse.
Here one example:
$ curl -v "benchmark@<IP_ADDRESS>:9090/?query=SELECT+toDate%28%60date_time%60%2C+%27UTC%27%29+as+%60ex_ch_date_time%60%2C+sumMerge%28%60invalid_impression%60%29+as+%60ex_ch_invalid_impression%60%2C+sumMerge%28%60advertiser_value_usd%60%29+as+%60ex_ch_advertiser_value_usd%60%2C+sumMerge%28%60impression%60%29+as+%60ex_ch_impression%60%2C+sumMerge%28%60invalid_click%60%29+as+%60ex_ch_invalid_click%60%2C+sumMerge%28%60advertiser_value_eur%60%29+as+%60ex_ch_advertiser_value_eur%60%2C+sumMerge%28%60margin_eur%60%29+as+%60ex_ch_margin_eur%60%2C+sumMerge%28%60click%60%29+as+%60ex_ch_click%60%2C+sumMerge%28%60publisher_value_eur%60%29+as+%60ex_ch_publisher_value_eur%60%2C+sumMerge%28%60margin_usd%60%29+as+%60ex_ch_margin_usd%60%2C+sumMerge%28%60publisher_value_usd%60%29+as+%60ex_ch_publisher_value_usd%60+FROM+%60dist_mv_agg_day_new%60+WHERE+%28%60date_time%60+%3E%3D+toDateTime%28%272018-09-04+00%3A00%3A00%27%2C+%27UTC%27%29+and+%60date_time%60+%3C%3D+toDateTime%28%272018-10-04+00%3A00%3A00%27%2C+%27UTC%27%29%29+GROUP+BY+date_time+FORMAT+JSONEachRow"
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 9090 (#0)
* Server auth using Basic with user 'benchmark'
> GET /?query=SELECT+toDate%28%60date_time%60%2C+%27UTC%27%29+as+%60ex_ch_date_time%60%2C+sumMerge%28%60invalid_impression%60%29+as+%60ex_ch_invalid_impression%60%2C+sumMerge%28%60advertiser_value_usd%60%29+as+%60ex_ch_advertiser_value_usd%60%2C+sumMerge%28%60impression%60%29+as+%60ex_ch_impression%60%2C+sumMerge%28%60invalid_click%60%29+as+%60ex_ch_invalid_click%60%2C+sumMerge%28%60advertiser_value_eur%60%29+as+%60ex_ch_advertiser_value_eur%60%2C+sumMerge%28%60margin_eur%60%29+as+%60ex_ch_margin_eur%60%2C+sumMerge%28%60click%60%29+as+%60ex_ch_click%60%2C+sumMerge%28%60publisher_value_eur%60%29+as+%60ex_ch_publisher_value_eur%60%2C+sumMerge%28%60margin_usd%60%29+as+%60ex_ch_margin_usd%60%2C+sumMerge%28%60publisher_value_usd%60%29+as+%60ex_ch_publisher_value_usd%60+FROM+%60dist_mv_agg_day_new%60+WHERE+%28%60date_time%60+%3E%3D+toDateTime%28%272018-09-04+00%3A00%3A00%27%2C+%27UTC%27%29+and+%60date_time%60+%3C%3D+toDateTime%28%272018-10-04+00%3A00%3A00%27%2C+%27UTC%27%29%29+GROUP+BY+date_time+FORMAT+JSONEachRow HTTP/1.1
> Host: <IP_ADDRESS>:9090
> Authorization: Basic YmVuY2htYXJrOg==
> User-Agent: curl/7.61.1
> Accept: */*
>
* Empty reply from server
* Connection #0 to host <IP_ADDRESS> left intact
curl: (52) Empty reply from server

As you can see, the connection is killed. Here are some relevant logs from chproxy:
Oct 04 11:34:41 gceuw1-chp01.c.lucky-eon-543.internal chproxy[13621]: DEBUG: 2018/10/04 11:34:41 proxy.go:74: [ Id: 155A63380D95D3C6; User "benchmark"(1) proxying as "readonly"(1) to "<IP_ADDRESS>:8123"(1); RemoteAddr: "<IP_ADDRESS>:49580"; LocalAddr: "<IP_ADDRESS>:9090"; Duration: 51.858µs ]: request start
Oct 04 11:37:20 gceuw1-chp01.c.lucky-eon-543.internal chproxy[13621]: DEBUG: 2018/10/04 11:37:20 proxy.go:199: [ Id: 155A63380D95D3C6; User "benchmark"(1) proxying as "readonly"(1) to "<IP_ADDRESS>:8123"(1); RemoteAddr: "<IP_ADDRESS>:49580"; LocalAddr: "<IP_ADDRESS>:9090"; Duration: 2m39.080545361s ]: remote client closed the connection in 2m39.080353788s; query: "SELECT toDate(`date_time`, 'UTC') as `ex_ch_date_time`, sumMerge(`invalid_impression`) as `ex_ch_invalid_impression`, sumMerge(`advertiser_value_usd`) as `ex_ch_advertiser_value_usd`, sumMerge(`impression`) as `ex_ch_impression`, sumMerge(`invalid_click`) as `ex_ch_invalid_click`, sumMerge(`advertiser_value_eur`) as `ex_ch_advertiser_value_eur`, sumMerge(`margin_eur`) as `ex_ch_margin_eur`, sumMerge(`click`) as `ex_ch_click`, sumMerge(`publisher_value_eur`) as `ex_ch_publisher_value_eur`, sumMerge(`margin_usd`) as `ex_ch_margin_usd`, sumMerge(`publisher_value_usd`) as `ex_ch_publisher_value_usd` FROM `dist_mv_agg_day_new` WHERE (`date_time` >= toDateTime('2018-09-04 00:00:00', 'UTC') and `date_time` <= toDateTime('2018-10-04 00:00:00', 'UTC')) GROUP BY date_time FORMAT JSONEachRow"
Oct 04 11:37:20 gceuw1-chp01.c.lucky-eon-543.internal chproxy[13621]: DEBUG: 2018/10/04 11:37:20 scope.go:243: killing the query with query_id=155A63380D95D3C6
Oct 04 11:37:20 gceuw1-chp01.c.lucky-eon-543.internal chproxy[13621]: DEBUG: 2018/10/04 11:37:20 scope.go:283: killed the query with query_id=155A63380D95D3C6; respBody: ""
Oct 04 11:37:20 gceuw1-chp01.c.lucky-eon-543.internal chproxy[13621]: DEBUG: 2018/10/04 11:37:20 proxy.go:115: [ Id: 155A63380D95D3C6; User "benchmark"(1) proxying as "readonly"(1) to "<IP_ADDRESS>:8123"(1); RemoteAddr: "<IP_ADDRESS>:49580"; LocalAddr: "<IP_ADDRESS>:9090"; Duration: 2m39.161807652s ]: request failure: non-200 status code 499; query: "SELECT toDate(`date_time`, 'UTC') as `ex_ch_date_time`, sumMerge(`invalid_impression`) as `ex_ch_invalid_impression`, sumMerge(`advertiser_value_usd`) as `ex_ch_advertiser_value_usd`, sumMerge(`impression`) as `ex_ch_impression`, sumMerge(`invalid_click`) as `ex_ch_invalid_click`, sumMerge(`advertiser_value_eur`) as `ex_ch_advertiser_value_eur`, sumMerge(`margin_eur`) as `ex_ch_margin_eur`, sumMerge(`click`) as `ex_ch_click`, sumMerge(`publisher_value_eur`) as `ex_ch_publisher_value_eur`, sumMerge(`margin_usd`) as `ex_ch_margin_usd`, sumMerge(`publisher_value_usd`) as `ex_ch_publisher_value_usd` FROM `dist_mv_agg_day_new` WHERE (`date_time` >= toDateTime('2018-09-04 00:00:00', 'UTC') and `date_time` <= toDateTime('2018-10-04 00:00:00', 'UTC')) GROUP BY date_time FORMAT JSONEachRow"; URL: "http://<IP_ADDRESS>:8123/?query=SELECT+toDate%28%60date_time%60%2C+%27UTC%27%29+as+%60ex_ch_date_time%60%2C+sumMerge%28%60invalid_impression%60%29+as+%60ex_ch_invalid_impression%60%2C+sumMerge%28%60advertiser_value_usd%60%29+as+%60ex_ch_advertiser_value_usd%60%2C+sumMerge%28%60impression%60%29+as+%60ex_ch_impression%60%2C+sumMerge%28%60invalid_click%60%29+as+%60ex_ch_invalid_click%60%2C+sumMerge%28%60advertiser_value_eur%60%29+as+%60ex_ch_advertiser_value_eur%60%2C+sumMerge%28%60margin_eur%60%29+as+%60ex_ch_margin_eur%60%2C+sumMerge%28%60click%60%29+as+%60ex_ch_click%60%2C+sumMerge%28%60publisher_value_eur%60%29+as+%60ex_ch_publisher_value_eur%60%2C+sumMerge%28%60margin_usd%60%29+as+%60ex_ch_margin_usd%60%2C+sumMerge%28%60publisher_value_usd%60%29+as+%60ex_ch_publisher_value_usd%60+FROM+%60dist_mv_agg_day_new%60+WHERE+%28%60date_time%60+%3E%3D+toDateTime%28%272018-09-04+00%3A00%3A00%27%2C+%27UTC%27%29+and+%60date_time%60+%3C%3D+toDateTime%28%272018-10-04+00%3A00%3A00%27%2C+%27UTC%27%29%29+GROUP+BY+date_time+FORMAT+JSONEachRow&query_id=155A63380D95D3C6"

And from clickhouse:
2018.10.04 11:34:41.713028 [ 11290 ] <Trace> HTTPHandler-factory: HTTP Request for HTTPHandler-factory. Method: GET, Address: [::ffff:<IP_ADDRESS>]:43198, User-Agent: RemoteAddr: <IP_ADDRESS>:49580; LocalAddr: <IP_ADDRESS>:9090; CHProxy-User: benchmark; CHProxy-ClusterUser: readonly; curl/7.61.1
2018.10.04 11:34:41.713126 [ 11290 ] <Trace> HTTPHandler: Request URI: /?query=SELECT+toDate%28%60date_time%60%2C+%27UTC%27%29+as+%60ex_ch_date_time%60%2C+sumMerge%28%60invalid_impression%60%29+as+%60ex_ch_invalid_impression%60%2C+sumMerge%28%60advertiser_value_usd%60%29+as+%60ex_ch_advertiser_value_usd%60%2C+sumMerge%28%60impression%60%29+as+%60ex_ch_impression%60%2C+sumMerge%28%60invalid_click%60%29+as+%60ex_ch_invalid_click%60%2C+sumMerge%28%60advertiser_value_eur%60%29+as+%60ex_ch_advertiser_value_eur%60%2C+sumMerge%28%60margin_eur%60%29+as+%60ex_ch_margin_eur%60%2C+sumMerge%28%60click%60%29+as+%60ex_ch_click%60%2C+sumMerge%28%60publisher_value_eur%60%29+as+%60ex_ch_publisher_value_eur%60%2C+sumMerge%28%60margin_usd%60%29+as+%60ex_ch_margin_usd%60%2C+sumMerge%28%60publisher_value_usd%60%29+as+%60ex_ch_publisher_value_usd%60+FROM+%60dist_mv_agg_day_new%60+WHERE+%28%60date_time%60+%3E%3D+toDateTime%28%272018-09-04+00%3A00%3A00%27%2C+%27UTC%27%29+and+%60date_time%60+%3C%3D+toDateTime%28%272018-10-04+00%3A00%3A00%27%2C+%27UTC%27%29%29+GROUP+BY+date_time+FORMAT+JSONEachRow&query_id=155A63380D95D3C6
2018.10.04 11:34:41.769439 [ 11290 ] <Debug> executeQuery: (from [::ffff:<IP_ADDRESS>]:43198, user: readonly, query_id: 155A63380D95D3C6) SELECT toDate(`date_time`, 'UTC') as `ex_ch_date_time`, sumMerge(`invalid_impression`) as `ex_ch_invalid_impression`, sumMerge(`advertiser_value_usd`) as `ex_ch_advertiser_value_usd`, sumMerge(`impression`) as `ex_ch_impression`, sumMerge(`invalid_click`) as `ex_ch_invalid_click`, sumMerge(`advertiser_value_eur`) as `ex_ch_advertiser_value_eur`, sumMerge(`margin_eur`) as `ex_ch_margin_eur`, sumMerge(`click`) as `ex_ch_click`, sumMerge(`publisher_value_eur`) as `ex_ch_publisher_value_eur`, sumMerge(`margin_usd`) as `ex_ch_margin_usd`, sumMerge(`publisher_value_usd`) as `ex_ch_publisher_value_usd` FROM `dist_mv_agg_day_new` WHERE (`date_time` >= toDateTime('2018-09-04 00:00:00', 'UTC') and `date_time` <= toDateTime('2018-10-04 00:00:00', 'UTC')) GROUP BY date_time FORMAT JSONEachRow
2018.10.04 11:34:41.975876 [ 11290 ] <Debug> default..inner.mv_agg_day_new (SelectExecutor): Key condition: (column 0 in [1536019200, +inf)), (column 0 in (-inf,<PHONE_NUMBER>]), and
2018.10.04 11:34:41.975914 [ 11290 ] <Debug> default..inner.mv_agg_day_new (SelectExecutor): MinMax index condition: (column 0 in [1536019200, +inf)), (column 0 in (-inf,<PHONE_NUMBER>]), and
2018.10.04 11:34:42.092220 [ 11290 ] <Debug> default..inner.mv_agg_day_new (SelectExecutor): Selected 21 parts by date, 21 parts by key, 432494 marks to read from 21 ranges
2018.10.04 11:34:42.096082 [ 11290 ] <Trace> default..inner.mv_agg_day_new (SelectExecutor): Reading approx.<PHONE_NUMBER> rows
2018.10.04 11:34:42.096146 [ 11290 ] <Trace> InterpreterSelectQuery: FetchColumns -> WithMergeableState
2018.10.04 11:34:42.097373 [ 11290 ] <Trace> InterpreterSelectQuery: WithMergeableState -> Complete
2018.10.04 11:34:42.172805 [ 11290 ] <Debug> executeQuery: Query pipeline:
2018.10.04 11:34:42.174612 [ 11290 ] <Trace> Aggregator: Reading blocks of partially aggregated data.
2018.10.04 11:37:20.693869 [ 11290 ] <Trace> Aggregator: Read 5 blocks of partially aggregated data, total 155 rows.
2018.10.04 11:37:20.693938 [ 11290 ] <Trace> Aggregator: Merging partially aggregated single-level data.
2018.10.04 11:37:20.721704 [ 11290 ] <Trace> Aggregator: Merged partially aggregated single-level data.
2018.10.04 11:37:20.739659 [ 11290 ] <Trace> Aggregator: Converting aggregated data to blocks
2018.10.04 11:37:20.739773 [ 11290 ] <Trace> Aggregator: Converted aggregated data to blocks. 31 rows, 0.002 MiB in 0.000 sec. (489777.862 rows/sec., 39.235 MiB/sec.)
2018.10.04 11:37:20.768479 [ 11290 ] <Trace> UnionBlockInputStream: Waiting for threads to finish
2018.10.04 11:37:20.768664 [ 11290 ] <Trace> UnionBlockInputStream: Waited for threads to finish
2018.10.04 11:37:20.768708 [ 11290 ] <Information> executeQuery: Read<PHONE_NUMBER>8 rows, 3.87 TiB in 158.999 sec., 111990246 rows/sec., 24.93 GiB/sec.
2018.10.04 11:37:20.786022 [ 11290 ] <Trace> UnionBlockInputStream: Waiting for threads to finish
2018.10.04 11:37:20.786042 [ 11290 ] <Trace> UnionBlockInputStream: Waited for threads to finish
2018.10.04 11:37:20.786088 [ 11290 ] <Trace> virtual DB::MergingAndConvertingBlockInputStream::~MergingAndConvertingBlockInputStream(): Waiting for threads to finish
2018.10.04 11:37:20.792317 [ 11290 ] <Debug> MemoryTracker: Peak memory usage (for query): 65.77 MiB.
2018.10.04 11:37:20.792482 [ 11290 ] <Information> HTTPHandler: Done processing query
2018.10.04 11:37:20.793398 [ 11290 ] <Trace> HTTPHandler-factory: HTTP Request for HTTPHandler-factory. Method: POST, Address: [::ffff:<IP_ADDRESS>]:43198, User-Agent: Go-http-client/1.1
2018.10.04 11:37:20.793451 [ 11290 ] <Trace> HTTPHandler: Request URI: /
2018.10.04 11:37:20.793667 [ 11290 ] <Debug> executeQuery: (from [::ffff:<IP_ADDRESS>]:43198, query_id: de0d107a-1617-4759-b275-96ff578c8d5e) KILL QUERY WHERE query_id = '155A63380D95D3C6'
2018.10.04 11:37:20.873350 [ 11290 ] <Trace> InterpreterSelectQuery: FetchColumns -> Complete
2018.10.04 11:37:20.873699 [ 11290 ] <Information> executeQuery: Read 2 rows, 1.45 KiB in 0.080 sec., 25 rows/sec., 18.17 KiB/sec.
2018.10.04 11:37:20.873732 [ 11290 ] <Debug> MemoryTracker: Peak memory usage (for query): 129.84 KiB.
2018.10.04 11:37:20.873843 [ 11290 ] <Information> HTTPHandler: Done processing query

Is there any reason for such behavior?

@lisuml , try using chproxy 1.13 and playing with read_timeout and write_timeout config params - see https://github.com/Vertamedia/chproxy/pull/36/files#diff-04c6e90faac2675aa89e2176d2eec7d8 .
Additionally, see default timeouts in curl - https://unix.stackexchange.com/questions/94604/does-curl-have-a-timeout/94612 .

Increasing write_timeout seems to do the trick. Thanks, @valyala!

I'm seeing this issue as well. However, we don't have a timeout set. After going through the configs, I think there should be no default limit on write_timeout. Could someone please help with this?


The specified network password is not correct

Hi,
I built the project with no errors also had LicenseSign.pfx in DemoActivationTool folder. When trying to generate the license having the following error "System.Security.Cryptography.CryptographicException: 'The specified network password is not correct".
Do I have to do any modifications to the certificate?
Thanks in advance!

was able to resolve it by exporting private key to Demo Activation folder with password generated and public key to Demo windowsformApp  with out password. And use the generated password key in your form as shown below. Good luck


Feature/admin notes - Fixes #205

This Admin Notes feature allows admin users to view, add, edit, and delete notes directly on a resource detail page. It also allows admin users to see all the notes of a given user on their user admin detail page.

If you click outside the modal window, it will create a new blank comment.  Or update the comment, but not actually update the text.

I had to run the e2e tests three times.  The third time they all passed.  I did a quick sanity check, and aside from clicking outside the window, things seem to work really well.


Fix token expiry date

As detailed in this issue, token was getting new date on every encode/decode, therefore never expiring.
This PR omits setting the expiresAt date and tries to only set it during first authentication and refresh.
After this, we might want to explore the option of a force refresh if 401 response is received.
That way expiry would never really need to be logged as we can always try with the old token and refresh if the bad response is received.

Oh wow, messed up the PR completely, I was sure I checked but it's not up to date at all. I will close it and re-do in the next few days 🙌

I just came back from the vacation, sry to have completely spaced this 😅, never got to correcting the PR.
Did you handle anything on this front or should I try to have at it again?

I think I fixed this in #34, feel free to verify in your project!

ohhh this looks nice, will check 🙌


draft: enable system auth for oracle based connections

Proposed solution for #202

Hi @wseaton , thanks so much for the PR! I will merge and make an alpha release for this feature to let users test it more conveniently.

What is the release to test it?

What is the release to test it?

Hi @cmartill , we will have our planned release (0.2.4) today first. Then I will merge this PR and release an alpha version.

Hi @cmartill , 0.2.4-alpha.1 is released. Please feel free to try out.


DEBUG versions for core ROS libraries would be VERY helpful (and static too)

It would be extremely helpful to include debug versions/builds of the core ROS libraries (not all of rosdeps) and, if possible, static library versions.  I have a lot of years working with ROS on windows (I worked a little with Brian et. al in the past and was responsible for the cygwin port of all of ROS that was out there for Indigo a few years back).   I am super excited to see what MSFT is doing here, saved me and others an enormous amount of work and will really help the community.  Thank you.
But back to debug...
Most of us developing ROS on windows will be using VS when authoring our own nodes.  We will still use catkin, but for debugging VS is king.  It is easy enough at present to use commandline cmake to generate VS projects for a package.  But DEBUG can not be used in the corresponding VS projects for a number of reasons (debug/release mismatch, class size/memory allocator differences, etc.).   No one needs to be debugging the ROS source code, but to debug one's own code, it is kind of important to important to be in DEBUG. (In fact, you can't even call ros::init without a "invalid size" exception being thrown immediately if you have DEBUG enabled...which makes sense as we're mixing Release libraries with Debug client code)
What I would suggest:

compile just the core ROS libraries in debug x64 and include in the chocolaty package. They can be anywhere, no one needs to make catkin do this.  They can be included just for those who know what they are doing with VS generally and require it...no need to make everything more complex.
you do NOT need to include debug versions of the boost libraries: it would be great, but most folks can build their own boost libraries.

In my experience with ROS on windows (having ported the core libs and TF2 et. al) they are very happy and stable in debug mode and only really require debug boost builds.  The tools like rviz and such have far more dependencies, but I am suggesting just the core ROS libraries like:
#pragma comment(lib, "roscpp.lib")
#pragma comment(lib, "rosconsole.lib")
#pragma comment(lib, "roscpp_serialization.lib")
#pragma comment(lib, "rostime.lib")
//and the TF libs
folks can do 99pct of what they need with just these.  So static and debug versions of these would be a dream and should not be tough to do.   I am not suggesting debug versions of all rosdeps.  Just a handful of core libraries so folks like me can write and debug our own code in ROS nodes.

Related issue and discussion: https://github.com/ms-iot/ROSOnWindows/issues/31 .

Yeah, I read the tinyXML thread...it is related.   I understand the perspective of not including the DEBUG as doing so could add a lot of complexity and maintenance for something only a few use,  but I would say again to powers that be: just include the debug versions in a special place/folder...don't go  and modify catkin or worry about the toolset and other dependencies.   Just a few core libraries.  It may be that to compile DEBUG for even a few libraries requires a lot of catkin/cmake headaches...but I found that simply importing the cmake files into CMAKE GUI, it was pretty trivial to generate VS projects and then compile them to debug (and also for static libs).  I did this for kinetic and indigo and I can do it for melodic if need be. Someone would just have a guide me a bit as to how to best collaborate.
On the subject of static libs, these can be more than nice to have.  When integrating ROS in complicated host systems (like game or simulation engines or embedded/mobile devices [like android NDK]) it can be really problematic to have a ton of DLLs hanging around.   In some cases, like for mobile, it can be impossible to handle.  I did a ROS port to android that required all static as there are restrictions on the .so loading for that platform that got in the way. And, anyway, there could be no .so versions of ROS without android-arm-compiled boost libraries...
So I would say: ROS for Windows really means ROS for VS and VS is really about cross-compilation and targeting everything these days and towards that end, we could really use the debug and static lib versions of ROS.

I totally agree that having libraries in Debug will be extremely convenient. With respect to that, I guess something is moving:

A GSoC student is working on adding vcpkg support to bloom ( https://summerofcode.withgoogle.com/projects/#5110132554334208 , https://www.openrobotics.org/blog/tag/GSoC )
According to a recent ROS2 TSC meeting minute, Microsoft is working on "a vcpkg feature to export chocolatey packages" ( https://discourse.ros.org/t/tsc-meeting-minutes-2019-04-18/8832 )

Thank you for the suggestion. we understand the desire and appreciate the time you took writing this up. At this time, we recommend that if you need the ability to debug an unoptimized distribution, it would be more beneficial to clone the source code and build a local ROS distribution. You can leverage the build scripts http://github.com/ms-iot/ros-windows-build.


Obsolete .new files are not removed

I just ran insta with some changes that caused the comparison to fail. I then reverted these changes and the test passed again. However, the .new files from the broken state were still there. I compared them with the approved snapshot until I noticed that the .new one did not represent my code anymore, since I had reverted it.
I did not expect the .new files to refer to previous runs. I expect them to refer to the latest run. If the comparison fails, then the .new files will be overwritten as expected. It is only when the test passes anew while having previously failed that this issue occurs.
I would suggest removing existing .new files when a test passes to prevent this mistake of assuming they represent the current state of the code.

Could you try running the latest master? This may have been solved in https://github.com/mitsuhiko/insta/pull/48

Yes, this is the behavior on the master! I looked through the issues, but I didn't sift through the PRs, so I missed it.
Awesome! Thanks for being a step ahead of me. insta is really, really nice to use!
Closing since it is fixed in #48 and already merged into master.


Figure out how workload identity work

I have an AKS cluster on Azure. I want to write a Go application that lists the VM on a subscription without using credentials.
Azure offers an authentication mechanism called workload identity that seems a good fit.
Let's see how it works.

After some reading and a few failed attempts, the document Deploy and configure workload identity on an Azure Kubernetes Service (AKS) cluster seems the best resource I was able to get.

Export environment variables
For this walkthrough, I'm using an existing cluster named mbranca-sdh-4160:
export RESOURCE_GROUP="mbranca-sdh-4160"
export CLUSTER_NAME="mbranca-sdh-4160"
export LOCATION="eastus2"
export SERVICE_ACCOUNT_NAMESPACE="default"
export SERVICE_ACCOUNT_NAME="workload-identity-sa"
export SUBSCRIPTION="$(az account show --query id --output tsv)"
export USER_ASSIGNED_IDENTITY_NAME="myIdentity"
export FEDERATED_IDENTITY_CREDENTIAL_NAME="myFedIdentity"

Update an existing AKS cluster
Since I already have a cluster, I'll set it up enabling OIDC and workload identity:
az aks update \
	-g "${RESOURCE_GROUP}" \
	-n "${CLUSTER_NAME}" \
	--enable-oidc-issuer \
	--enable-workload-identity

Retrieve the OIDC Issuer URL
Now that OIDC is enabled, we can collect the OIDC Issuer URL and store it as environment variable:
export AKS_OIDC_ISSUER="$(az aks show --resource-group "${RESOURCE_GROUP}" --name "${CLUSTER_NAME}" --query "oidcIssuerProfile.issuerUrl" -otsv)"

Create a managed identity
From the source document:

Use the Azure CLI az account set command to set a specific subscription to be the current active subscription. Then use the az identity create command to create a managed identity.

# set the default subscription
az account set --subscription "${SUBSCRIPTION}"

az identity create --name "${USER_ASSIGNED_IDENTITY_NAME}" --resource-group "${RESOURCE_GROUP}" --location "${LOCATION}" --subscription "${SUBSCRIPTION}"

# (optional) if you need to delete one
az identity delete --name "${USER_ASSIGNED_IDENTITY_NAME}" --resource-group "${RESOURCE_GROUP}" --subscription "${SUBSCRIPTION}"

Create Kubernetes service account

Create a Kubernetes service account and annotate it with the client ID of the managed identity created in the previous step. Use the az aks get-credentials command and replace the values for the cluster name and the resource group name.

az aks get-credentials -n "${CLUSTER_NAME}" -g "${RESOURCE_GROUP}"

Copy and paste the following multi-line input in the Azure CLI.

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    azure.workload.identity/client-id: "${USER_ASSIGNED_CLIENT_ID}"
  name: "${SERVICE_ACCOUNT_NAME}"
  namespace: "${SERVICE_ACCOUNT_NAMESPACE}"
EOF

Use the az identity federated-credential create command to create the federated identity credential between the managed identity, the service account issuer, and the subject.

az identity federated-credential create \
  --name ${FEDERATED_IDENTITY_CREDENTIAL_NAME} \
  --identity-name "${USER_ASSIGNED_IDENTITY_NAME}" \
  --resource-group "${RESOURCE_GROUP}" \
  --issuer "${AKS_OIDC_ISSUER}" \
  --subject system:serviceaccount:"${SERVICE_ACCOUNT_NAMESPACE}":"${SERVICE_ACCOUNT_NAME}" \
  --audience api://AzureADTokenExchange

Run your application
For this test, I created a trivial "application" that count the VMs available on a subscription.
Here's the source code:
package main

import (
	"context"
	"fmt"
	"net/http"
	"os"

	"github.com/Azure/azure-sdk-for-go/sdk/azidentity"
	"github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute"
	"k8s.io/klog/v2"
)

func main() {
	subscriptionId := os.Getenv("SUBSCRIPTION_ID")

	credential, err := azidentity.NewDefaultAzureCredential(nil)
	if err != nil {
		klog.Fatal(err)
	}

	client, err := armcompute.NewVirtualMachinesClient(subscriptionId, credential, nil)
	if err != nil {
		klog.Fatal(err)
	}

	pager := client.NewListAllPager(nil)

	for pager.More() {
		page, err := pager.NextPage(context.Background())
		if err != nil {
			klog.Fatal(err)
		}

		fmt.Printf("Found %d VMs\n", len(page.Value))
	}

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		fmt.Fprint(w, "Hello, Kubernetes!")
	})

	err = http.ListenAndServe(":8080", nil)
	if err != nil {
		klog.Fatal(err)
	}
}

Here is the Dockerfile to build an image:
FROM golang:1.21 as builder

WORKDIR /app
COPY . .

RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o myapp

FROM alpine:3.14

WORKDIR /app
COPY --from=builder /app/myapp /app/

EXPOSE 8080
CMD ["/app/myapp"]

And finally, the K8s deployment file:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      name: myapp
      namespace: default
      labels:
        azure.workload.identity/use: "true"
        app: myapp
    spec:
      serviceAccountName: workload-identity-sa
      containers:
        - name: myapp
          image: zmoog/myapp:latest
          env:
          - name: SUBSCRIPTION_ID
            value: "<put your subscription ID here>"

I build and pushed the image to Docker Hub:
docker build -t zmoog/myapp:latest .

docker push zmoog/myapp:latest

Give myIdentity the permission to list the VMs

Run your application
As a final step, I will deploy and run the app on k8s.
$ k apply -f deployment.yaml
deployment.apps/myapp-deployment created

$ k get pods
NAME                                READY   STATUS    RESTARTS   AGE
myapp-deployment-785ff98547-tmxn9   1/1     Running   0          14s

$ k logs myapp-deployment-785ff98547-tmxn9
Found 7 VMs


Blockchain repository

A repository of chains, or of blocks?

Both remarks are good points ; especially wrt BlockchainRepository.
I think I need to implement more here. I'm on it.


use transitionTo with external links

I have a willTransitionFrom handler on a component that checks to see if the form on the page has unsaved data. This works great when clicking on a link that navigates to a page within the app, but when clicking on an external link (like google.com) the page instantly loads the new page and willTransitionFrom never gets called.
I understand why this is the way it is, but I was wondering if there is a way one could trigger the transition with an external link with the transitionTo method or if any one else has run into this issue, how they handled it.

the history package that we're built on has the option to use onBeforeUnload for transition hooks too: https://github.com/rackt/history/blob/master/docs/ConfirmingNavigation.md#the-beforeunload-event
you can pass in your own history (that uses beforeunload) to <Router history={myHistory}/>


CI coveralls parallel fix

Closes #453
Update coveralls action to point a commit with a fix for dubious git ownership errors when running parallel coveralls step - e.g. https://github.com/AndreMiras/coveralls-python-action/commit/65c1672f0b8a201702d86c81b79187df74072505
This commit is merged into the develop branch on the coveralls-python-action repository, but not yet the main branch, and there hasn't been a tag released version update since 2020.
Another option is to use code-cov for this project which is used in other projects? https://github.com/ACCESS-NRI/dev-docs/wiki/Continuous-integration-and-deployment#uploading-code-coverage-reports-to-codecov

Yeah it shouldn't take too long to update to codecov. I logged into CodeCov and put in a request for payu-org organisation with only the payu repository. But I think it requires owner/admin of payu-org to approve it.

Ok I've created an issue to move to CodeCov when there's time, and will merge this PR now so there is some reporting on testing as part of CI


Support calculating gas cost of whole test execution

When running tests, we should be able to calculate its combined gas cost, that is: cost of all code in the test itself, probably extracted from the VM using https://github.com/starkware-libs/cairo/pull/4084 + the cost of blockifier calls which we are already calculating.
We should create some interface that makes the combined cost of the test available in the run_from_test_case https://github.com/foundry-rs/starknet-foundry/blob/894fedb266d30bfd633ae02a5d4c51d2119f846e/crates/forge/src/running.rs#L72 function, so it can be then collected and displayed by forge.

This is blocked by blockifier getting bumped to 2.3.0-rc0 or higher.

Please do create a follow-up to parse the result and display it (for forge-cli team)


fix(input): overflow-y scrollbar is displayed (IE)

y-scrollbar is displayed when placeholder text line-height is bigger than md-input-placeholder height (on IE browser)
fixes #3570

LGTM


Improve Actions Script

Changes:

Remove token from actions/checkout@v4 as by default it uses github action's token
Run the script in a separate task
Only Commit if changes are made
Show diff only if changes are made

so this pull can be closed

@Nusab19, not sure why you closed this pr. You cloud have resolved the issues than we could have merged this pr.
For better pr manage you should also try opening pull requests from a different branch than a main. This way your changes of a pr can be tracked separately.

@Nusab19, not sure why you closed this pr. You cloud have resolved the issues than we could have merged this pr.
For better pr manage you can also try opening pull requests from a different branch than a main. This way your changes of a pr can be tracked separately.

I tried to just comment it. Accidentally pressed close with comments.
:33

Ok, then I will resolve these issues myself.


facts: explicitly disable facter and ohai (bp #5486)

By default, ansible gathers facts from facter and ohai if installed on
the remote nodes, given we don't need them, let's exclude these facts
from our facts gathering
Backport: #5486
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>(cherry picked from commit c95adc564b8be6f9f9b1ba8568072daf39da7a2c)

jenkins test centos-container-all_daemons

jenkins test centos-container-update

jenkins test centos-container-purge

jenkins test centos-container-update

jenkins test centos-container-all_daemons

jenkins test centos-container-all_daemons

jenkins test centos-container-all_daemons


Support for the Windows Demo

This demo would enable people to try out my project without having to gain the actual Future Cop CD.
I would have to implement a way to read out of portable executable files from the ".exe".

As far as I remember, there are some differences between the Griffith Park level from the demo, compared with the RTM version.
The only one that comes to mind is that there is a small "in-game intro animation" showing X1-Alpha entering the park - probably to compensate for missing movies?
Not sure if this means that there are level format differences.

For the case with the Demo Windows version, I actually had managed to get them to run.
I think I did something like this a week ago. (Perhaps, I should of told people this, but I had managed to extract the maps from the demo and they work).
However, for this "issue" to be resolved I must get my project reading the Demo executable.
This way people do not need a special archive program to extract them.

I must get my project reading the Demo executable.

That would be the best scenario.


Make name issue specific for workshop

Signed-off-by: Francesco Murdaca<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign pacospace after the PR has been reviewed.
You can assign the PR to them by writing /assign @pacospace in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Pre-Commit Test failed! Click here
[INFO] Initializing environment for git://github.com/Lucas-C/pre-commit-hooks.
[INFO] Initializing environment for git://github.com/pre-commit/pre-commit-hooks.
[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Initializing environment for https://github.com/adrienverge/yamllint.git.
[INFO] Installing environment for git://github.com/Lucas-C/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for git://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/adrienverge/yamllint.git.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
Tabs remover.............................................................Passed
Trim Trailing Whitespace.................................................Passed
Check for merge conflicts................................................Passed
Fix End of Files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing .github/ISSUE_TEMPLATE/ml_prague_workshop.md

Check for added large files..............................................Passed
Check for case conflicts.................................................Passed
Check JSON...........................................(no files to check)Skipped
Check for broken symlinks............................(no files to check)Skipped
Detect Private Key.......................................................Passed
Fix End of Files.........................................................Passed
Trim Trailing Whitespace.................................................Passed
yamllint.................................................................Passed

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pacospace
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [pacospace]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Builds are broken

There are some Dockerfiles that reference the EPEL repo. It looks like the one for Centos 7 is no longer available with cent 7 EOL. We need to migrate these to EPEL 8 or 9.

Amazon Linux 2023 is no longer compatible with EPEL (here) and there is no tesseract package in their repository. There is a package request for AL2023 here from 2023 and there doesn't appear to be any movement. We need to rewrite these Dockerfiles. The official docs here point to some random person's GitHub and package repos. Unclear if we want to leverage these but the app image might be the best option going forward.


AvalancheGo Networking Refactor

Refactor both grpcClient and grpcServer classes for AvalancheGo communication

Refactor was finished, but we ultimately decided to redo the P2P to evpp, using TCP sockets instead of websockets, issue #20 was created for this reason, Documentation will be updated with issue #20

Moved to #26


Improve Caching Schema

Use Django async caching API

Note: This limits us to Django 4.0+, Python 3.8+.

Remove async_lru_cache.

Django's default cache engine is functionally equivalent.

Fix #46
Use aiofile for async file operations.
Protect against malicious file paths (ex ../../../etc/passwd)
Use cache versioning to invalidate old web module files stored in cache

This now uses aiofile as well, which means fetching IDOM web modules is fully async.
Should be performant enough to where we can put off #4 for a while.

I had a concept to use cache versioning to help invalidate old web module files stored in cache, but unfortunately this doesn't work since the temp directory names are randomized, thus we have no replicable cache key.

temp directory names are randomized

By default IDOM_WEB_MODULES_DIR is a temp dir, but that can be changed. For example you could set it using appdirs. That way it would be static.

A note on changing IDOM_WEB_MODULES_DIR: since there may already be files there at the time you change the directory you should copy over any existing files into the new location.

Is the default behavior within Core to not override existing files, if they have different contents?

The default behavior does not overwrite. The code there is a little messy, but I just put up a PR to clean that up: https://github.com/idom-team/idom/pull/586

Alright. I'll handle app directory stuff when idom-team/idom#586 is closed and made into a PyPI release.
In that case this PR is ready for merge. You need to make Python 3.7 tests non-required on your end for that to happen though.

IDOM core can continue supporting 3.7, you'll just need to constrain the supported versions in setup.py for this package.

@Archmonger the latest version of IDOM has been released with the changes from https://github.com/idom-team/idom/pull/586. Is there anything else to do here?

This PR should be feature complete, can't be merged without making 3.7 not required. I'm assuming that's in the project settings?
I'll make a separate PR to bump IDOM in here to the new version.

Feel free to merge


Alphabetize option description in help

Decided against a simple optimization, taking a cue from Git manpages (cause, why not?). Regrouped options a bit more semantically. Clarified --now and --timeZone.
Change 441fb0f


Show Tunnel Endpoint in details.

Would it be possible to show the endpoint IP's in tunnel details (netbird status -d) as currently it's a bit hard to troubleshoot how netbird is connecting, at the moment it just says direct/p2p/relayed.
Including information on any STUN/TURN mappings may also help with troubleshooting connection issues.

fixed in 0.25.5


Add an option to disable notifications popup at the end of Pomodoro interval

Describe the new feature
Add a toggle switch to the Pomodoro settings tab which would allow to opt out of the notifications popup which is shown at the end of each Pomodoro interval.
How does this help you?
Unfortunately the current notification window is very distracting. Having an option to disable it would greatly improve the user experience overall.
I'm using a tiling window manager, therefore when the sound is played, it opens a new browser window src/content/audio/index.html near the focused one, shifting all my other windows aside. Right at the moment I have two options to mitigate this: either make this window floating (and maybe hidden) in my window manager settings, or modify the source code of the extension itself. The latter is not very sustainable, given that the source code of the extension itself is "closed" from some time ago.
If we couldn't add this feature, is there a compromise you can think of?
You could utilize browser Notifications API instead. But still, having an option to opt out of it would be great either way.

In case this would be useful to anyone, my current solution is to add this line to my Sway config file:
for_window [instance="crx_oejgccbfbmkkpaidnkphaiaecficdnfn"] floating enable, move to scratchpad, focus disable

Should also work for i3, the config syntax is almost identical.
I didn't use [window_role="pop-up"] because for some reason Toggl extension sometimes creates multiple notification windows, one of them doesn't have this role in the propagated IPC data. So to hide them all, I need to filter it out by instance, which is actually the ID of the extension in the Chrome store:
https://chromewebstore.google.com/detail/toggl-track-productivity/oejgccbfbmkkpaidnkphaiaecficdnfn


Instantiate to bound doesn't produce correct types in some cases

Example of an incorrect type produced by the current implementation of instantiate to bound: https://github.com/dart-lang/sdk/issues/30724#issuecomment-355415956. The implementation should follow the spec.

I believe the issue is resolved by https://github.com/dart-lang/sdk/commit/8c82c3b5fe80f2870ad9780b06d84fa35f35257c.


Async bug for GPU backend

When running in async mode, if second request complete before get result of first one, the result of first one is overwritten by the second one. Only observed this in GPU target. Working fine in CPU and MYRIAD target. Openvino R5.
from openvino.inference_engine import IENetwork, IEPlugin
import numpy as np
from time import sleep

if __name__ == '__main__':
    device = 'GPU'
    num_requests = 2
    plugin = IEPlugin(device=device)
    net = IENetwork(model='/temp/f16_64/tf_model.xml', weights='/temp/f16_64/tf_model.bin')
    input_shape = (1, 6, 64, 64)
    net.batch_size = 1

    exec_net = plugin.load(network=net, num_requests=2)
    input_name = next(iter(net.inputs))
    output_name = next(iter(net.outputs))

    all0 = np.zeros(input_shape, np.float32)
    all1 = np.ones(input_shape, np.float32)*255

    exec_net.requests[0].async_infer(inputs={input_name: all0})
    exec_net.requests[1].async_infer(inputs={input_name: all1})
    exec_net.requests[0].wait(-1)
    sleep(2)
    results0 = exec_net.requests[0].outputs[output_name]
    exec_net.requests[1].wait(-1)
    results1 = exec_net.requests[1].outputs[output_name]
    print('Results are exactly same. Should be a bug. ' if (results0 == results1).all() else 'Results are different.')

I have the same problem. Does anyone fix it?

If you encounter issue in the open source version, you could add more details here.

Only the GPU Async of openvino inference would happen, CPU & Myriad work fine. The issue is that if the second request complete, the output of the second request will overwrite the output of the first request.


[TRACKING] Libs Release (0.13.0)

This issue tracks the libs+driver release (0.13.0). See the full release process here :point_down:
https://github.com/falcosecurity/libs/blob/master/release.md
Release Phases :cyclone:
Preparation :gift:

[x] Tag all necessary PR with milestones 0.13.0

Code freeze :cold_face:

[x] Test the libraries and drivers

Release branch :arrow_down:

[x] Craft release branch
- upstream: https://github.com/falcosecurity/libs/tree/release/0.13.x
- fork: https://github.com/Andreagit97/libs/tree/release/0.13.x
[x] Release candidate tags for testing purposes. (optional)
[ ] start the drivers build on driver-kit
[x] open in test-infra repository a PR to set the newly created branch as protected.

https://github.com/falcosecurity/test-infra/pull/1228

Thaw :sunrise_over_mountains:

[ ] thaw the repo allowing new PR to be merged in the master branch again.

Final tags :label:

[ ] craft them at the end of the release process

PR that should be cherry-picked into the release branch :cherries:

[x] https://github.com/falcosecurity/libs/pull/1321
[x] https://github.com/falcosecurity/libs/pull/1322
[x] https://github.com/falcosecurity/libs/pull/1323
[x] https://github.com/falcosecurity/libs/pull/1324
[x] https://github.com/falcosecurity/libs/pull/1329

Synced with: https://github.com/falcosecurity/libs/pull/1330

[x] https://github.com/falcosecurity/libs/pull/839
[x] https://github.com/falcosecurity/libs/pull/1332
[x] https://github.com/falcosecurity/libs/pull/1331
[x] https://github.com/falcosecurity/libs/pull/1334

Synced with: https://github.com/falcosecurity/libs/pull/1335

[x] https://github.com/falcosecurity/libs/pull/1341
[x] https://github.com/falcosecurity/libs/pull/1340

Synced with: https://github.com/falcosecurity/libs/pull/1344

[x] https://github.com/falcosecurity/libs/pull/1349
[x] https://github.com/falcosecurity/libs/pull/1350
[x] https://github.com/falcosecurity/libs/pull/1345
[x] https://github.com/falcosecurity/libs/pull/1339

Synced with: https://github.com/falcosecurity/libs/pull/1351

[x] https://github.com/falcosecurity/libs/pull/1352

Synced with: https://github.com/falcosecurity/libs/pull/1353

[x] https://github.com/falcosecurity/libs/pull/1354

Synced with: https://github.com/falcosecurity/libs/pull/1357

We are in code freeze phase :cold_face:

Libs 0.13.0-rc1 and drivers 6.0.0+driver released!

Due to https://github.com/falcosecurity/libs/pull/1341 we probably need to tag a 6.0.1+driver

We released our final tags :tada:

https://github.com/falcosecurity/libs/releases/tag/0.13.0
https://github.com/falcosecurity/libs/releases/tag/6.0.1%2Bdriver

We can declare the code thaw :) Thanks everyone for the precious help :pray:


Expose Web5PlatformAgent to Web5 instance

We need an easier way to access the keys of the connectedDid in the Web5.connect response object. This PR exposes the Web5PlatformAgent directly in the Web5 object. Example use case we have in our current app:
const { web5, did: aliceDid, recoveryPhrase } = await Web5.connect({ password });
const { did: aliceBearerDid } = await web5.platformAgent.identity.get({ didUri: aliceDid });
const signer = await aliceBearerDid.getSigner();
const signature = await signer.sign({ data: 'Hello world!' });

You should be able to immediately fix this in your downstream application by asserting that your agent is of type Web5PlatformAgent (agent as Web5PlatformAgent) without any upstream changes. But an upstream change that might immediately fix this is a type guard (or some sort of generic) to assert that an upstream agent is of type Web5PlatformAgent

@bnonni is the app you are including this in a client/user facing app?  or is it a backend service?

You should be able to immediately fix this in your downstream application by asserting that your agent is of type Web5PlatformAgent (agent as Web5PlatformAgent) without any upstream changes. But an upstream change that might work for this PR is either a type guard or a generic

@shamilovtim I don't know why I did not think of this 🤦🏼♂ I must be tired 😪 This works, thank you for the suggestion.

@bnonni Is the app you are developing a web browser client/user facing app? Or is it a backend service or mobile app?
If its a mobile app or backend service, then you probably don't need to use Web5.connect() since you're never going to be connecting to any remote agents.

@frankhinek both server and client. DCX will be using Web5.connect on the server side as a DCX issuer and on the client side as a DCX applicant. We have both a mobile and web app client side, so the web version would need Web5.connect. Each side needs access to their respective DWNs to perform their side of the DCX protocol.

Also, if this need to use the underlying agent is related to a lack of web5.vc.create() then we likely ought to tackle adding that in a PR rather than adding a second agent property to the Web5 instance.

Yes, that's accurate. Having an easy method to issue a vc from the server side is what I'm looking to do. To your point, I will close this PR and open one for the web5.vc.create() functionality instead.

@shamilovtim @frankhinek
I don't fully understand the nuances of the agent did vs. connected DID, and I'm concerned that when we scale DCX into the cloud and replicate it across multiple instances each running Web5.connect, they will each have the same agent DID with a different connected DID leading to issues with VC signatures and verification.

Are the connected DIDs published with their own DID docs?
Is there a way to resolve a connected DID back to its agent DID?
Which DID should we use to sign VCs on the server side?
If we use the connected DID, will the signatures on the VCs we issue to holders be valid against the agent DID somehow?
I'm aware of the long term plan to have delegation grants between agent DID and connected DIDs. Until that is complete, how should we go about signing and issuing VCs from the server? How do we let clients know a connected DID has a relationship to an agent DID such that the connected DID signature can be verified against the agent DID?

Thanks for the help!


routes of admin registration done

Fixes Issue
#1935
I have created routes in order to store data, it is working when tested from postman, integration with frontend is pending

Changes proposed

Screenshots

Note to reviewers

Summary by CodeRabbit

New Features

Introduced admin registration functionality, allowing admins to register through a new form.
Added a file upload capability for essential documents during admin registration.

User Interface Improvements

Streamlined user experience by removing unnecessary confirmation prompts when switching tabs in the admin form.

Bug Fixes

Improved logging for form submissions to enhance data visibility.

Dependencies

Added support for handling multipart/form-data with the inclusion of the multer library.

take a look of code rabbit code

done


make user scans less spammy

We recently discovered that if a significant portion of users.conf is lost, even after repairing it to a valid JSON, Izzy's attempt to recreate user data for all of the users in Manechat no longer in that file is extremely spammy in #modchat. That's because she logs a separate #modchat message for every single user, and each one involves a Discord request so it takes her a long time to work through hundreds of them. At the time I made a hotfix to disable those logs (and the corresponding New Pony removals), and Lunar reverted it after Izzy was done, but in the long run we certainly don't want to blanket disable catchup and role removal logs.
We should:

make the scan process only print separate messages per user when the number of users being synced is <10
for larger numbers, print only a single summary message to modchat and do the rest in silence (or log again when finished
don't do the whole New Pony thing if the user joined forever ago (this was noticed by active users)
think about whether we can improve the Discord requests made in this scenario; what are they and do we even need them?

After reading the code and performing some tests with a dev Izzy connected to Manechat, I am now convinced that much of this code can be deduplicated, the behavior made more uniform, and the total time to resync all users should go down to almost nothing once we properly batch the I/O steps.


Error: redefinition of module 'SwiftBridging'

Description
Build works fine with the default Xcode 15.0.1. However when we select Xcode 15.2, builds fail with Error: redefinition of module 'SwiftBridging'.
Possible useful link: https://forums.developer.apple.com/forums/thread/739510
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
macos-13-xlarge
Is it regression?
N/A
Expected behavior
Build should pass with Xcode 15.2
Actual behavior
Github Actions return build error: /Applications/Xcode_15.2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/swift/module.modulemap,line=13,col=8::redefinition of module 'SwiftBridging'
Repro steps

Select Xcode version by updating "sudo xcode-select -s /Applications/Xcode_15.2.app/Contents/Developer" in Github workflows
Build on macos-13-xlarge runner.

Hello @QiZhan.  Can you please provide simple repro step? Its can be sample xcode project with action yaml.

Hi sergei-pyshnoi, The only change we made was selecting Xcode 15.2 in the job compared with the working job with Xcode 15.0.1. We archive using bundle exec fastlane gym and our project is using React Native.

Hi sergei-pyshnoi, The only change we made was selecting Xcode 15.2 in the job compared with the working one with Xcode 15.0.1. Not sure if this info will help, we archive using bundle exec fastlane gym and our project is using React Native.

Unfortunately without any additional information we cannot start any investigation. I mean for example its error can be your project related. At least changing Xcode for building its kind of major changing and its It's not uncommon for this to cause errors during the build process.

Hey @QiZhan!
I'm going to close this item since no repro steps were provided. Feel free to reopen it in case you got some information to investigate.

Hey, @erik-bershel.
I have a project for you where this error occurs.
Failed job logs.zip
Let me know if there is anything else I can do to help resolve this issue.

Hi,

Hello @matbouil!
Unfortunately, we have not found the root cause yet.
It would be great for further investigation if you could also provide a link to the public repository where the issue occurred.

Hello @matbouil! Unfortunately, we have not found the root cause yet. It would be great for further investigation if you could also provide a link to the public repository where the issue occurred.

Hi Maksim,
Unfortunately, my project is not on a public repository and can't share it with you.
However, as @ruslanskorb said, the build works perfectly using Xcode 15.0.1.

Adding our observation here -
Last successful build with Xcode 15.2 was on Feb 12 and we noticed that it started failing from Feb 23.
In between, we noticed that the macOS 13 image got updated. We are thinking this could be a possible root cause.
Mac OS image on feb 12
Image: macos-13
Version: 20240114.1
Mac OS image we noticed on Feb 23
Image: macos-13
Version: 20240219.1
You may try to look into this direction and see if you can find any root cause.

Hello @nanduu058!
Thank you for providing additional information!
Could you please share the link to the latest successful build with Xcode 15.2?

@MaksimZhukov
Unfortunately, due to security concerns we cant share our project or logs. Is there any office hours for your clients to jump on a call to debug any of this kinds of issues? We can do a screen share

@MaksimZhukov Do you have any update on this?

Hello @MaksimZhukov
We would also be interested in an update on this subject too ;-)

Hello everyone!
The issue is caused by installing multiple versions of Xcode alongside and can be fixed by deleting Xcode.app:
- name: Delete Xcode.app
  run: sudo rm -rf /Applications/Xcode.app

Here is a link to the successful run and corresponding workflow file.
I'm closing the issue. Feel free to contact us if you have any questions or concerns.

https://github.com/actions/runner-images/issues/9542#issuecomment-2073287239
We were able to pass our build from the above mentioned link. However, we are curious if it can be fixed from GitHub side as this one stated happening with the recent update. It would be really difficult to triage this kind of issues that came up with the updates as it is difficult to reproduce locally.


Move this repo to CyPhyHouse-Dev

Move all contents in this repo to CyPhyHouse-Dev to use git subtree instead of git submodule

After further consideration, this may not be necessary. CyPhyHouse-Dev may not use git subtree but manually/automatically download pre-built packages or binaries from all components. A standalone repo for documenting all components is still necessary.


Fix a use-after-free with task tracing

We cannot access the executed job after it has finished executing:

If it's a non-task job, it is always invalidated; such jobs are self-owning, and they are expected to destroy themselves after execution.

If it's a task, and it completes during execution, it will invalidate itself synchronously, e.g. by releasing itself.  At this point, it must be assumed that the task memory has been releaed.

If it's a task, and it hasn't completed during execution, we are now racing with whatever event does complete the task.

Any information we want to log about the job must be recorded when it starts to run.
Fixes rdar://88817560

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Linux

Adding Mike who added the tracing stuff

@swift-ci Please smoke test macOS

@swift-ci Please test Linux

@swift-ci Please test

@swift-ci Please test macOS

@swift-ci Please test Linux

Unrelated LLDB failure.  This is getting tiring.

@swift-ci Please smoke test macOS


Move inserting ansible_managed header at the end of the tasks

Some sqlcmd commands remove the header from config. E.g.
/opt/mssql/bin/mssql-conf set sqlagent.enabled "True"
Inserting the header must be executed at the end of the role
https://bugzilla.redhat.com/show_bug.cgi?id=2057651

[citest]

Inspired by https://github.com/linux-system-roles/metrics/pull/109

[citest]