configconnectorcontext.core.cnrm.cloud.google.com does not reconcile

I'm attempting to use the namespace pattern outlined here.
To set up namespace mode, I'm using the blueprint provided here.
After kpt live apply, kpt gets hung on:
configconnectorcontext.core.cnrm.cloud.google.com/configconnectorcontext.core.cnrm.cloud.google.com reconcile pending

A couple of things to note:

kubectl lists these resources as healthy (main reason I'm opening the bug in this repo)

~> kubectl get configconnectorcontext.core.cnrm.cloud.google.com -n ce-dev-auth
NAME                                                AGE   HEALTHY
configconnectorcontext.core.cnrm.cloud.google.com   17h   true
~> kubectl get configconnectorcontext.core.cnrm.cloud.google.com -n config-control
NAME                                                AGE   HEALTHY
configconnectorcontext.core.cnrm.cloud.google.com   17h   true

According to these docs, ConfigConnectorContext should create a service account (which it does):

~> kubectl get serviceaccount/cnrm-controller-manager-ce-dev-auth -n cnrm-system
NAME                                  SECRETS   AGE
cnrm-controller-manager-ce-dev-auth   1         22h

Pods are also successfully created:

~> kubectl get pod -n cnrm-system
NAME                                             READY   STATUS    RESTARTS   AGE
cnrm-controller-manager-c97fr14gkgt3le3gnbq0-0   2/2     Running   0          22h
cnrm-controller-manager-c97g09sgkgt3le3gnbqg-0   2/2     Running   0          22h
cnrm-deletiondefender-0                          1/1     Running   0          22h
cnrm-resource-stats-recorder-6c99fd7558-pjfz6    2/2     Running   0          22h
cnrm-webhook-manager-867ff75f95-74nhj            1/1     Running   0          22h
cnrm-webhook-manager-867ff75f95-lgkb5            1/1     Running   0          22h
~> kubectl wait -n cnrm-system --for=condition=Ready pod -l cnrm.cloud.google.com/component=cnrm-controller-manager -l cnrm.cloud.google.com/scoped-namespace=ce-dev-auth
pod/cnrm-controller-manager-c97g09sgkgt3le3gnbqg-0 condition met

So accoding to eveything above, I believe the ConfigConnectorContext should be fully reconciled, but it isn't.
Another interesting detail however, is that the cnrm-controller-manager pods created by ConfigConnectorContext are trying to reach project<PHONE_NUMBER>21.  Project<PHONE_NUMBER>21 is not owned by me - it is a special project internal to GCP.  See the following logs from pod/cnrm-controller-manager-c97g09sgkgt3le3gnbqg-0. They attempt to reach monitoring.googleapis.com on project<PHONE_NUMBER>21, but also say that reconcile is successful.  So regarless of the project<PHONE_NUMBER>21 error, I beleive kpt should see the ConfigConnectorContext as reconciled.
2022-04-08 09:53:38.881 EDTError while sending request to Stackdriver googleapi: Error 403: Cloud Monitoring API has not been used in project<PHONE_NUMBER>21 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/monitoring.googleapis.com/overview?project=538440108421 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
Info
2022-04-08 09:53:45.940 EDT{logger: iamserviceaccount-controller, msg: starting reconcile, resource: {…}, timestamp: 2022-04-08T13:53:45.940Z}
Info
2022-04-08 09:53:46.033 EDT{logger: iamserviceaccount-controller, msg: underlying resource already up to date, resource: {…}, timestamp: 2022-04-08T13:53:46.032Z}
Info
2022-04-08 09:53:46.033 EDT{logger: iamserviceaccount-controller, msg: successfully finished reconcile, resource: {…}, time to next reconciliation: 14m41.820099426s, timestamp: 2022-04-08T13:53:46.033Z}

Thanks!
P.S. I understand that this might be due to a bug in Config Connector or Config Controller, and if this is the case I can post this bug report somewhere else.

@cartyc beat me to it in https://github.com/GoogleContainerTools/kpt/issues/2982 !


Event registration page

EventBrite?

http://www.eventbrite.com/e/clojurebridge-durham-fall-2015-tickets-17849306757
The status is public, but it is actually a review stage. Comment please, if there's any.

Updated the issue to add Durham chapter on clojurebridge.org .
https://github.com/ClojureBridge/Workshops/issues/6

Closed the issue on Workshops repository. All done.


Format the dart output

Description
Hi, I'm using flutter_rust_bridge with the build.rs to automatically generate the dart output. I noticed that also if the rust APIs aren't changed and the dart output is already updated, it's re-genereated a new output "unformatted". If I commit those changes after few time it's re-generated formatted.
// build.rs

use std::process::{Command, Stdio};

use lib_flutter_rust_bridge_codegen::codegen;
use lib_flutter_rust_bridge_codegen::codegen::Config;

fn main() {
    println!("cargo:rerun-if-changed=src/api");

    if is_flutter_installed() {
        // Execute code generator with auto-detected config
        codegen::generate(
            Config::from_config_file("../flutter_rust_bridge.yaml")
                .unwrap()
                .unwrap(),
            Default::default(),
        )
        .unwrap();
    } else {
        eprintln!("Warning: flutter not installed.");
    }
}

fn is_flutter_installed() -> bool {
    let output = Command::new("flutter")
        .arg("--version")
        .stdout(Stdio::null())
        .stderr(Stdio::null())
        .status();
    matches!(output, Ok(status) if status.success())
}

The final output (formatted) that is re-generated with many whitespaces:
// This file is automatically generated, so please do not edit it.
// @generated by `flutter_rust_bridge`@ 2.6.0.

// ignore_for_file: invalid_use_of_internal_member, unused_import, unnecessary_import

import '../frb_generated.dart';
import 'package:flutter_rust_bridge/flutter_rust_bridge_for_generated.dart';
import 'protocol/event.dart';

// Rust type: RustOpaqueMoi<flutter_rust_bridge::for_generated::RustAutoOpaqueInner<_Client>>
abstract class Client implements RustOpaqueInterface {
  Future<bool> addRelay({required String url});

  Future<void> connect();

  static Client default_() =>
      RustLib.instance.api.crateApiClientClientDefault();

  Future<String> sendEvent({required Event event});
}

// This file is automatically generated, so please do not edit it.
// @generated by `flutter_rust_bridge`@ 2.6.0.

// ignore_for_file: invalid_use_of_internal_member, unused_import, unnecessary_import

import '../frb_generated.dart';
import 'package:flutter_rust_bridge/flutter_rust_bridge_for_generated.dart';
import 'protocol/event.dart';

                // Rust type: RustOpaqueMoi<flutter_rust_bridge::for_generated::RustAutoOpaqueInner<_Client>>
                abstract class Client implements RustOpaqueInterface {
                     Future<bool>  addRelay({required String url });

 Future<void>  connect();

static Client  default_()=>RustLib.instance.api.crateApiClientClientDefault();

 Future<String>  sendEvent({required Event event });

                }

Describe the solution you'd like
Always format the dart output or add an field in Config to choose if format the code.

2024-11-19.log

I guess this is related to how you setup the dart binary. i.e. sh seems to be confused and cannot find that binary when executed from build.rs.

Ah, thanks! Weird, dart is installed. I guess again an issue with RustRover, when it auto check the crates (the last time not found flutter binary). Thanks!

You are welcome and happy to see it is solved!


[ZEPPELIN-5782] Remove geode interpreter

What is this PR for?
Removing geode interpreters and related things unused by retirement
What type of PR is it?
Refactoring
What is the Jira issue?
ZEPPELIN-5782
How should this be tested?
CI
Questions:

Does the licenses files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? Yes

As you mentioned, could you please update license files as well if it's necessary?

I confused I updated license files even though I didn't. I changed the answer above. Sorry for bothering


Spot BUY fills with 0.0001 less

Problem:
All spot BUY trades fill with 0.0001 less than ordered. This happens on all pairs. BTC/USDC, ETH/USDC, etc.
Reproduction:

Go to https://devnet.mango.markets/market?name=BTC%2FUSDC
Place a spot limit buy on BTC for any quantity
Wait for fill
Go to Trade History
Notice you were filled for 0.0001 BTC less

I verified that this issue occurs both through this library and online on devnet. I have not tested mainnet.

This behavior has been fixed


Dev branch with latest network and mirror node images

Problem
In the .env file we have the latest version of the images on mainnet.
Solution
Create a develop branch where we have the newest images (alpha, pre-release) to be able to run against them.
Alternatives
No response

Closing this issue, dev branch created with latest versions for network node, mirror node and relay.


Timeout When Running npm start

Description
If I run npm start and then scan the qr code in the expo app, I always get a timeout error.
My phone and my laptop are on the same network.
Expected Behavior

create a new project with create-react-native-app
run npm start
scan shown qr code
expo app does not timeout.

Observed Behavior

expo app does timeout:

"Error while loading: The request timed out." (code -1001)

Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts<EMAIL_ADDRESS>npm ls react-native<EMAIL_ADDRESS>npm ls expo<EMAIL_ADDRESS>node -v: v6.9.5
npm -v: 3.10.10
yarn --version: not installed
watchman version: "version": "4.7.0"

Also specify:

Operating system: NixOS 17.09
Phone/emulator/simulator & version: iPhone 5s // iOS 10.2.1

Hi! Thanks for the report! Have you tried the network troubleshooting steps in the user guide?

Hi my phone and my laptop are on the same network but I tried to open, in my case http://<IP_ADDRESS>:19000/ on my phone and it doesn't reach the site.

Have you fixed this issue? I still got the same error, My phone and laptop connected in the same network, I tried to access it in my phone chrome browser as mentioned in network troubleshooting steps. It didn't work.

It might be a host issue. Inside of Expo XDE, I chose in config -> Host -> Tunnel with Protocol exp. The link to preview the app inside of XDS looks something like this  exp://4n-g26.username.project-name.exp.direct:80. When I run npm start finally I got something like this exp://<IP_ADDRESS>:19000. I don't know if this could be the problem. 😞

@kmiloarguello @sajankumar did you try the steps from the network troubleshooting guide, including using your phone's tethering/hotspot? https://github.com/react-community/create-react-native-app/blob/master/react-native-scripts/template/README.md#networking

I tried, but it didn't work.  Please see the attached screenshot

Thank you for the answer.
Actually the problem doesn't the network. I guess I could be a XDE host problem. For example I tried to run my project inside of Windows using Expo XDE software and it only works when I run from this button Open on Android (see attachment screenshot).

Any help would be highly appreciated :)

@kmiloarguello if you're using open on android, that doesn't hit the network the same way as scanning a QR code or typing in a URL. You'll need to be more specific about what steps you're taking from the network troubleshooting guide.
@sajankumar you didn't mention whether you tried this in your phone's web browser. If you can reach the URL in your phone's browser, but not in the Expo app, that's definitely something we need to investigate. Unfortunately I don't have time to help with networking issues that aren't directly a bug in the Expo app :(. If you still think this is a bug, please detail what steps you took from the network troubleshooting guide.

@dikaiosune Hey, I tried whatever the steps mentioned in this link https://github.com/react-community/create-react-native-app/blob/master/react-native-scripts/template/README.md#networking didn't work. Unfortunately I can't reach URL in my phone's browser.
So, I thought it maybe because of my network firewall so I deactivated the firewall and tried it but it didn't work.

I took all the steps from the network troubleshooting guide. Now it works for me, the problem was that my physical device wasn't be able to catch the same host url of XDE software. With the QR code scan was not possible to connect my device and XDE. The only way was send the url from XDE to the physical device.

@sajankumar if you can't reach the URL in your phone's browser, there's unfortunately not much I can do to help. I'd recommend trying XDE out instead of CRNA, because it handles a number of these networking issues for you.
I haven't heard back from the original reporter, and as far as I can tell all subsequent reports are just due to local network configuration issues, which are out of scope for help and bug reports on this repo (sorry, just not enough time to address every single one!). Giving this a close.
If you're coming to this issue when searching around, please please please try the network troubleshooting steps in the user guide. If you can reach the server URL in your phone's browser, but not in the Expo app, please open a new issue. Otherwise, I'd recommend looking around for resources to change your local network configuration to support connecting between devices, or installing XDE which will create network tunnels for you.

In my case, i solved this problem by changing IP react native to ip of pc in local network.
<IP_ADDRESS>:19000 (default) to my pc IP.
https://github.com/react-community/create-react-native-app/blob/master/react-native-scripts/template/README.md#configuring-packager-ip-address

I just ran yarn ios start and get this error, from a brand new project today with latest versions.

Note I am trying to use the simulator.
Previously the sim worked about 2-3 weeks ago.

@QuantumInformation - can you open your browser to http://localhost:19000 and see what the result is?

Maybe you could try to close windows(or other) firewall, it work for me.

when vpn used in phone  ,i came cross this problem. solved when vpn closed.

The problem is your OS firewall block access from your phone. Find your phone ip address in settings and allow on your PC/Laptop access (through firewall configuration) from phone ip to your PC ip address and ports 19000, 19001. On ubuntu with ufw firewall need to do something like:
sudo ufw allow from phone.ip.address.here to pc.ip.address.here port 19001

quick 1 liner: sudo ufw allow from <IP_ADDRESS>/24 to <IP_ADDRESS>/24 port 19000:19001 proto tcp

The address shown after running npm-start was exp://<IP_ADDRESS>:19000, which I could access on my host computer, but not on any other device, even with the firewall turned off (using http://<IP_ADDRESS>:19000).
However, changing the address to <IP_ADDRESS>:19000 worked. You'll need to figure out the IP of the host computer on your network.

@Onumis what does that do exactly?

@ToJen it opens the firewall ports 19000 and 19001 (used by the server and debugger to connect the phone to browser), on all IPs in your subnet. A bit more useful than https://github.com/react-community/create-react-native-app/issues/164#issuecomment-319034626 since you don't have to figure out your phone's ip address and it opens the 2 ports at once.
If you are working at a public wifi, like an airport, I don't recommend opening the firewall, just in case :)

Thanks @Onumis I eventually got it

I fixed this problem removing all my networks. In mi case I am connected by wifi, but Create-React-Native was selecting my Ethernet network, so, I am disabled from Windows Settings, and now its working

What you need to do is:
Go to cmd and type "ipconfig" and see which network is using the ip shown in your expo app. if it's not your router IP address then what you need to do is to go and disable the network which expo is using:
Control Panel -> Network and Internet -> Network Connections
and here disable the network that expo is using.
try to run "npm start" again, it should be working now.
If my solution is not clear feel free to ask me.

@raminghaderi, you saved the day!
Thank you so much!!!


[release-1.1] fix(vmclone): delete snapshot and restore after pvc bound

What this PR does / why we need it:
This is an manual cherry-pick of https://github.com/kubevirt/kubevirt/pull/10888
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

[Bugfix] Clone VM with WaitForFirstConsumer binding mode PVC now works.

/cc @acardace

/approve

/retest-required


Life cycle of devfile registry (start, stop, restart)

User Story
As a devfile registry admin, I want to start and stop the registry and restart the registry for the changes to take place.
Acceptance Criteria

[ ] It should provide the ability to start and stop a registry
[ ] It should provide ability to restart the registry in order to pick up changes on the registry
[ ] Handle gracefully and recover from registry abnormal exit, e.g. pod restart.

Links

Related issue:
This item is part of the epic #82

Design docs for start, stop, and container restart:
https://docs.google.com/document/d/1rQHCp4SWslWWJv5KK3A_iXHvgbqjsuDkSKDD72ifJio/edit?usp=sharing


explore/support Swoole

I recently came across a new event lib like ReactPHP called Swoole (https://www.swoole.com/) with very impressive benchmarks:
https://gist.github.com/nkt/e49289321c744155484c
Basically, ReactPHP was getting about 1/2 the performance of NodeJS and Swoole was about 10x greater than NodeJS (20x better than ReactPHP).
I would be great if it was possible for Ratchet to support Swoole where it's available.
Why would I not just use Swoole natively?  I would prefer to use Ratchet so I can have a common interface where Swoole is not installed.
There is a similar discussion in php-pm (https://github.com/php-pm/php-pm/issues/389) but I think with Ratchet the benefit is even greater because it's easier to reach a bottleneck with networking/concurrency (c10k).

"Hello World" benchmarks are to be taken with a grain of salt.

I personally haven't looked into Swoole at all though. To go about doing this, one would make a replacement for the IoServer class (and its IoConnection class that is bubbled through an app). I would prefer this to be a stand-alone library as, I mentioned above, I'm not familiar with Swoole, and would not want to have to officially support something I'm not familiar with.


Unchecking a checkbox with defaultValue 'checked' leaves it with checked value

Describe the bug
I am bit puzzled as to how the checkbox PARAMETER is supposed to be used. Per the manual,

checkbox: Must be “checked” to activate the checkbox

It is, therefore, what I am setting my parameter to, so that the checkbox is shown as checked by default. Everything works fine until I actually uncheck it. I can see the parameter is not passed via URL query anymore, which is expected, but the $this->getInput('uncheckedparameter') returns checked value.
So based on that, it is currently impossible to have a checkbox parameter set to 'checked' by default, as no matter what, its value is always resolved to exactly that.
Expected behavior
After unchecking a checkbox with a defaultValue set, $this->getInput('uncheckedparameter') should return NULL.

Can confirm this. It's not possible to have a default value of checked for a checkbox.

Has there been any progress on this?
There are multiple bridges that are affected by this, though I foresee no impact to already subscribed feeds since the checkbox is already selected by default.
Looking into the issue, the unchecked checkbox with 'defaultValue' => 'checked' would return 'checked', instead of NULL or false;
Input:

Output:
ON: 'checked';
OFF: true;

After some poking around, I think the issue may be with the BridgeAbstract::setInputs() function.


Using a implicitly defined constant as array length causes the application/editor to crash

Godot version
4.0 prerelease 2
System information
Fedora Linux 37, Nvidia 4090, Vulkan 1.3, nv 525.60.11
Issue description
When using a implicit constant as length in an array causes a crash to do failure to parse the shader syntax. This also crashes the editor when editing a shader. If the project is saved in that state this will cause the project to corrupt as it is impossible to open it without the editor crashing.
Steps to reproduce
Create a new Godot Project and create a new GD shader. Use the following example code or equivalent in the shader:
const int EXPLICIT = 1;
const int IMPLICIT = EXPLICIT + 1;
int[IMPLICIT];

Wait for the editor to realize what you just wrote and subsequently crash.
Minimal reproduction project
N/A

Can't reproduce in 4.0 stable. No crash with the given code.

Can't reproduce either in 4.0 RC 2, which I guess is what was referred to as "prerelease 2".

@RedNicStone Can you still reproduce it in 4.0 stable, and if so, can you give more detailed reproduction steps?

Issue is present for me in both version 4.0 stable and RC 2.
However I have found that the issue is inconsistent to reproduce. Sometimes the editor will crash immediately and other times it will only happen when the editor is restarted a few times.
Here is a crashlog I gathered when id did happen:
(base) [nic@ryzen9m Applications]$ ./Godot_v4.0-stable_linux.x86_64
Godot Engine v4.0.stable.official.92bee43ad - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 525.60.11 - Compatibility - Using Device: NVIDIA Corporation - NVIDIA GeForce RTX 3090

Editing project: /home/nic/GodotProjects/test_old
Godot Engine v4.0.stable.official.92bee43ad - https://godotengine.org
Vulkan API 1.3.224 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce RTX 4090
WARNING: Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
     at: _editor_init (modules/gltf/register_types.cpp:70)
--res://test.gdshader--
    1 | shader_type spatial;
    2 | render_mode unshaded;
    3 |
    4 | uniform sampler2D textureIn;
    5 | const int EXPLICIT = 1;
    6 | const int IMPLICIT = EXPLICIT + 1;
E   7-> int[IMPLICIT];
    8 |
SHADER ERROR: Expected a function name after type.
          at: (null) (res://test.gdshader:7)
ERROR: Shader compilation failed.
   at: set_code (servers/rendering/renderer_rd/forward_clustered/scene_shader_forward_clustered.cpp:137)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.stable.official (92bee43adba8d2401ef40e2480e53087bcb1eaf1)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
 Following shader reliably crashes in 4.2 whenever I try to open it in editor:
shader_type spatial;

const uint TEST = 1u;
const uint TEST_IMPLICIT = TEST + 1u;

float crash_array[TEST_IMPLICIT];

void fragment() {
	ALBEDO = vec3(1., .0, .0);
}

Dump:
--Main Shader--
    1 | shader_type spatial;
    2 |
    3 | const uint TEST = 1u;
    4 | const uint TEST_IMPLICIT = TEST + 1u;
    5 |
E   6-> float crash_array[TEST_IMPLICIT];
    7 |
    8 | void fragment() {
    9 |  ALBEDO = vec3(1., .0, .0);
   10 | }
   11 |
SHADER ERROR: Expected a positive integer constant.
          at: (null) (:6)
ERROR: Shader compilation failed.
   at: set_code (servers/rendering/renderer_rd/forward_clustered/scene_shader_forward_clustered.cpp:145)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.stable.arch_linux
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib/libc.so.6(+0x3e710) [0x7fcb9845c710] (??:0)
[2] /usr/bin/godot(+0x32dc06e) [0x55591f56006e] (??:?)
[3] /usr/bin/godot(+0x32f0342) [0x55591f574342] (??:?)
[4] /usr/bin/godot(+0x332dbd5) [0x55591f5b1bd5] (??:?)
[5] /usr/bin/godot(+0x3334773) [0x55591f5b8773] (??:?)
[6] /usr/bin/godot(+0x33007a8) [0x55591f5847a8] (??:?)
[7] /usr/bin/godot(+0x33c4c5c) [0x55591f648c5c] (??:?)
[8] /usr/bin/godot(+0x3420932) [0x55591f6a4932] (??:?)
[9] /usr/bin/godot(+0x2d3726a) [0x55591efbb26a] (??:?)
[10] /usr/bin/godot(+0x1a607be) [0x55591dce47be] (??:?)
[11] /usr/bin/godot(+0x3da562e) [0x55592002962e] (??:?)
[12] /usr/bin/godot(+0x1ab05cc) [0x55591dd345cc] (??:?)
[13] /usr/bin/godot(+0x1a6a7ea) [0x55591dcee7ea] (??:?)
[14] /usr/bin/godot(+0x1a323ec) [0x55591dcb63ec] (??:?)
[15] /usr/bin/godot(+0x126c084) [0x55591d4f0084] (??:?)
[16] /usr/bin/godot(+0x1280ea8) [0x55591d504ea8] (??:?)
[17] /usr/bin/godot(+0x14534fb) [0x55591d6d74fb] (??:?)
[18] /usr/bin/godot(+0x1267249) [0x55591d4eb249] (??:?)
[19] /usr/bin/godot(+0x14245bb) [0x55591d6a85bb] (??:?)
[20] /usr/bin/godot(+0x14249df) [0x55591d6a89df] (??:?)
[21] /usr/bin/godot(+0x3da562e) [0x55592002962e] (??:?)
[22] /usr/bin/godot(+0xb35057) [0x55591cdb9057] (??:?)
[23] /usr/bin/godot(+0x2572ac2) [0x55591e7f6ac2] (??:?)
[24] /usr/bin/godot(+0x219a2db) [0x55591e41e2db] (??:?)
[25] /usr/bin/godot(+0x21e7121) [0x55591e46b121] (??:?)
[26] /usr/bin/godot(+0x21e910d) [0x55591e46d10d] (??:?)
[27] /usr/bin/godot(+0x2202ff6) [0x55591e486ff6] (??:?)
[28] /usr/bin/godot(+0x426157b) [0x5559204e557b] (??:?)
[29] /usr/bin/godot(+0x5ff4e2) [0x55591c8834e2] (??:?)
[30] /usr/bin/godot(+0x3b374c1) [0x55591fdbb4c1] (??:?)
[31] /usr/bin/godot(+0x3b38e35) [0x55591fdbce35] (??:?)
[32] /usr/bin/godot(+0x603921) [0x55591c887921] (??:?)
[33] /usr/bin/godot(+0x5830bc) [0x55591c8070bc] (??:?)
[34] /usr/lib/libc.so.6(+0x27cd0) [0x7fcb98445cd0] (??:0)
[35] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7fcb98445d8a] (??:0)
[36] /usr/bin/godot(+0x58fd95) [0x55591c813d95] (??:?)
-- END OF BACKTRACE --
================================================================

Ok I can reproduce the crash in official build, but it does not happen in dev build 🤔

Can reproduce on v4.2.1.stable.flathub [b09f793f5] on linux mint, and on v4.2.1.stable.official [b09f793f5] on windows 10, with the following code:
shader_type spatial;

const int XD = 5*5;
uniform float[XD] lol;

I can reproduce this in godot 4.3
the problem seems to happen more consistently when vertex or fragment functions are defined. (even if empty)


Create command line flag to enable simultaneous multiple logins.

This is a response for https://github.com/yakyak/yakyak/issues/13 and https://github.com/yakyak/yakyak/issues/302.
It's a hack which will modify the path of userData depending on a command line argument user=<dir>. So now several instances of yakyak can run from different directories, with different accounts logged in.
Multiple windows must be used. I understand this isn't the clean solution (multiple accounts, single yakyak instance) wanted by users, but it works.. for me at least.
To streamline usage, the yakyak.desktop file can be copied, and each can then be modified to include this argument.
#!/usr/bin/env xdg-open

[Desktop Entry]
Name=YakYak

Add
GenericName=YakYak
Comment=Electron App from git
Path=/home/my-username/git/third-party/yakyak/
Exec=electron app user=my_first_account
Terminal=false
Type=Application
X-GNOME-Autostart-enabled=true
Icon=/home/my-username/git/third-party/yakyak/src/icons/atom.icns
Name[en_US]=YakYak [my_first_account]

cool initiative ^^
this seems to be javascript instead of coffeescript
see http://coffeescript.org/ for more information
it really really helps clean up the code, for instance the for cycle turns to:
regex = /^user=(.*)$/i;
for lineArg in cmdLineArgs
    match = regex.exec(lineArg)
    console.log("match: " + match)
    if match
        ...

Additionally, when creating the structure for "command line arguments", one should really include the help argument and the structure to easily add new arguments.
ps. I am just a fan of the project and a coder so take my comments lightly :)

Thanks for the tips, averissimo. I've never worked with coffeescript before, so they're appreciated.
If there's support/acknowledgement from the developers for this being the solution to the "multiple accounts logged in" request, I would be happy to learn some proper coffeescript and make a simple CLI argument handling system.
Right now the hack is certainly just a proof of concept, but I don't know how else to stage this conversation than to offer a pull request.

If you write this in a good way i will merge it. However, it's just a thing for developers who want to have fun with it. It does not solve any of the problems we need to solve in order to make this a user feature.

I close this to clean up things. If you want to just reopen it


Auto Snap when connected to dock

Description of the new feature / enhancement
When connecting my laptop to my dock with multiple screens. It would be awesome if I could save my window settings to my email, help desk and VS Code snap to the correct screens automatically.
Scenario when this would be used?
Any time I dock and undock my laptop I always have to move my windows around before getting started. Yes I know its not a difficult thing to do but every moment counts when time is money
Supporting information
No supporting documents, I just had this idea pop in to my head as I use the Fancy Zones feature all day every day. But I am always moving the same windows and applications around every time I dock and undock

This is a feature of Windows 11.


Add Transformation class and implement translation, rotation, scaling

create Transformation class with global variables translation, rotation, scale
add setters/getters
implement math function translation, rotation, scale


bad code1

PR Analysis

🎯 Main theme: The PR introduces a new function ddd in build.py.
📝 PR summary: The PR adds a new function ddd to build.py.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 3, because the PR is small and the code is well-structured.
🔒 Security concerns: No security concerns found

PR Feedback

General PR suggestions: The PR title and description are not descriptive enough. Please update them to reflect the changes made in the PR.

Preparing review...

PR Analysis

🎯 Main theme: The PR introduces a new function called 'ddd' in the 'build.py' file.
📝 PR summary: The PR adds a new function called 'ddd' to the 'build.py' file.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 3, because the PR is small and simple.
🔒 Security concerns: No security concerns found

PR Feedback

General PR suggestions: The PR title and description should be updated to reflect the changes made in the PR.

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

PR Analysis

🎯 Main theme: Addition of a new function in the cutlass build script.
📝 PR summary: This PR introduces a new function 'ddd' in the cutlass build script. The function currently prints a string "AAA" and an uninvoked print function.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 1, because the PR is small and the changes are straightforward.
🔒 Security concerns: No security concerns found

PR Feedback

💡 General suggestions: It would be beneficial to provide a more descriptive function name and also to include a brief comment explaining the purpose of the function. Additionally, the print statement seems to be incomplete.


Seed.Config.ts Changes

Hi Guys,
We need to incorporate the angular-seed project in another web application.
So we have decided to download angular-seed and place it at the root: /angular-seed-project/etc...
Now, in Seed.Config.ts there are the paths for the node_modules, which is in the angualr-seed-project folder. Now, since this is in our project root, we need that change that path to /angualr-seed-project/node_modules/etc...
Are there any practical solution on how I can do that instead of modifying the seed.config.ts itself?
Thank you in advance

All parameters defined in seed.config.ts can be overridden in project.config.ts.


Introduce delay start parameter

With this change StartWorkflowExecutionRequest will have the delay start
param so client can configure delay start

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


Network interfaces have trouble with video

Through testing, I can confirm that AWS spot instances network interfaces have trouble connecting properly to AWS to verify the drivers, and therefore not show any video, or the resolution is limited.
This could be an Open-stream based error in some cases but could also be due to the server's configuration.
If you are available for helping to fix this problem, please reply to this issue!

It seems that this is not due to spot instances and is due to the static IP addresses that are needed for Open-stream. This has no relation with Open-stream console errors.

The conclusion of this case seems like Open-stream was the underlying error and after changed Open-stream to Sunshine, everything works just as you would expect, even with network interfaces.


Bar chart with x time scale (tooltips) not correct

Expected behavior
See https://www.chartjs.org/docs/latest/samples/scales/time-combo.html, The tooltips should be correct
Current behavior
See https://www.chartjs.org/docs/latest/samples/scales/time-combo.html, The tooltips show the wrong date (17 instead of 18)

Reproducible sample
https://www.chartjs.org/docs/latest/samples/scales/time-combo.html
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
4.2.1
Browser name and version
No response
Link to your project
No response

Hi @stockiNail,
Are you suggesting that I add this to the following file: https://github.com/chartjs/Chart.js/blob/83ba8fd77689645d0f915a6c8b4881b882be5276/docs/samples/scales/time-combo.md?plain=1#L69
If so, I would be happy to contribute and create a PR. This seems like an excellent opportunity for me to make my first contribution. Thank you for your attention!

@mukham12 yes, I was suggesting that. Feel free to submit a PR!

Many thanks @stockiNail. I will try to submit a PR as soon as I am able to. I appreciate the support.

Hi @etimberg,
Now that the PR has been merged, can we consider closing this issue?
Also, it looks like issue #10889 shares similarities with this one, so it would be great if we could address that as well and close it if appropriate.
Thank you!


Add site title label to permissions dialog entries

The window.ipfs permissions manager is rad. The only thing that could make it better is if added a hint to what site a particular ipfs path was. I just accidentally hit deny on a site i was working in, jumped to the management page to fix it and then guessed that the only one currently set to Deny was probably the one i needed to edit, which won't scale well.

If we could add a label to the permissions entries it'd really help. In chrome, the url bar autocompletes with web addresses and the site title as muted secondary text, to help disambiguate opaque urls.

That kind of thing would really help here.

Marking this one as status/blocked until we bring back support for window.ipfs.

Closing due to https://github.com/ipfs-shipyard/ipfs-companion/issues/589#issuecomment-712356448


Auto-formatting in version 1.5 breaks undo history

The "Typescript Format On Key" action prevents undoing past the point at which the action was applied.
To replicate:

Ensure that you have the latest version of the TypeScript-Sublime-Plugin installed in Sublime Text
Create a new file and save as a file with a .ts extension so that the syntax gets set to TypeScript
Enter the following code: function log(entry: {message: string
Type }
Press Command + Z to undo
Nothing happens, because the action is re-applied as soon as it is undone.

I am running Sublime Text 3, Stable Channel, Build 3083.

confirmed. Windows machine


Make WCF interface async

And add number of cards drop remaining in "!status" response, which I think will be useful for users.

Last time I tested this it didn't work properly on Mono, let's see if it does now.

Still broken on Mono, I don't even know what is broken to be exact, server seems to be responding but client never gets response.


Zed stub navigation to gateway controller does not work for Spryker vendor classes

Tested on: PhpStorm 2022.2.4, Build #PS-222.4459.28
OS: Windows 10
Plugin version: 0.7.5

As for project level, the navigation to Gateway controller methods from Zed stub URL's works perfectly, it does seem to be glitchy for vendor classes. Example in AuthRestApi module in spryker:

Same issue I faced on other vendor modules as well. Would be helpful to have it working too, as sometimes code debugging leads to the vendor code as well.

Hi again @Lkopo, thanks for reporting! This is a bug, should be fixed with version 0.7.7.


Launch/open a region using the command line

Launches a game/region using the syntax:
(exe) open --game/-g (game name/number) --region/-r (region name/number) --play/-p
--region and --play are optional.
Without --region, the last is used.
Without --play, the region just changes.
It handles redirection if multiple instances are not enabled in settings.
#358

All looks good, thank you for your work!
Merging...


AMT_S

Hello, I encountered an error after updating today. How can I solve this problem?

I also get the same error.
I was able to temporarily avoid the error by commenting out lines 15 and 31 of init.py.
\ComfyUI\custom_nodes\ComfyUI-Frame-Interpolation_init_.py
15:#from models.amt import AMT_VFI
31:#    "AMT VFI": AMT_VFI,

I also get the same error. I was able to temporarily avoid the error by commenting out lines 15 and 31 of init.py.
\ComfyUI\custom_nodes\ComfyUI-Frame-Interpolation__init__.py
15:#from models.amt import AMT_VFI
31:#    "AMT VFI": AMT_VFI,
`

it's a good idea! thanks


#1273: updated grid page.

@joseegm - pls ignore inconsistent header styles on other pages. I have opened a new ticket to make these all consistent under #1282 and only focus on the girds page.

@saadmhybris
There are some conflicts probably because I merged #1281  before ....


shallowMount weird behaviour with repeating component stubs in snapshot

I haven't seen an issue like this and I'm not sure if this is an issue on my end but there's a weird behaviour when trying to shallow mount a component with multiple repeating components. ai-btn and ai-icon are added as global components in the mount.
This is the component:
<template lang="pug">
  .ai-simple-pagination
    ai-btn.ai-simple-pagination__arrow-button.left(
      variant="label",
      @click="goBack",
      :disabled="!hasPrev"
    )
      ai-icon.ai-simple-pagination__icon(
        icon="arrow-small-left",
        width="30",
        height="30"
      )
    ai-btn.ai-simple-pagination__arrow-button.right(
      variant="label",
      @click="goForward",
      :disabled="!hasNext"
    )
      ai-icon.ai-simple-pagination__icon(
        icon="arrow-small-right",
        width="30",
        height="30"
      )
</template>

<script lang="ts">
import {
  ref,
  PropType,
  defineComponent,
} from 'vue';

export default defineComponent({
  name: 'AiSimplePagination',
  props: {
    value: {
      type: Number,
      default: 1,
    },
    onChange: {
      type: Function as PropType<(val: number) => void>,
      required: true,
    },
    hasPrev: {
      type: Boolean,
      required: true,
    },
    hasNext: {
      type: Boolean,
      required: true,
    },
  },
  setup(props) {
    const model = ref<number>(props.value);

    const goForward = () => {
      model.value += 1;
      props.onChange(model.value);
    };

    const goBack = () => {
      model.value -= 1;
      props.onChange(model.value);
    };

    return {
      model,
      props,
      goForward,
      goBack,
    };
  },
});
</script>

When mounting it with shallowMount and expecting it to match the snapshot, the snapshot looks like this:
<div
  class="ai-simple-pagination"
>
  <ai-btn-stub
    class="ai-simple-pagination__arrow-button left"
    disabled="true"
    variant="label"
  >
    <ai-icon-stub
      class="ai-simple-pagination__icon"
      height="30"
      icon="arrow-small-left"
      width="30"
    />
  </ai-btn-stub>
  <ai-btn-stub
    class="ai-simple-pagination__arrow-button left ai-simple-pagination__arrow-button right"
    disabled="false"
    variant="label"
  >
    <ai-icon-stub
      class="ai-simple-pagination__icon"
      height="30"
      icon="arrow-small-left"
      width="30"
    />
  </ai-btn-stub>
</div>

As you can see the second ai-btn-stub has the classes of the first one also and the second ai-icon-stub has the icon from the left one instead of it's own.

Hello,
I forked this so I can write a test case which reproduces the above behavior when shallow mounting a component.

It seems the cause is this line on #453. Its seems to break the rendering of attributes in the html.
Here is an updated version of the test that shows it breaking: https://github.com/yakobe/vue-test-utils-next/commit/3283eeeabaa7fb6da81be6b611e18c44f0e4409b

So #453 introduced the regression?
We might just want to revert it. The rationale was to allow:
it('non-shallow mount', async () => {
        const wrapper = mount(OuterComponent, {
            shallow: false
        });

        const innerComponent = wrapper.getComponent(InnerComponent);
        await wrapper.find('button').trigger('click');
        expect(innerComponent.props()).toHaveProperty('text', 'new text');
    });

To work, but it looks like this might introduce problems by caching the stub. Instead we would just require users to re-run getComponent to get the updated values and whatnot. 🤔

The problem is either way, we have a breaking change from V1 - if we revert it, https://github.com/vuejs/vue-test-utils-next/issues/362 is going to a problem again.
In a real browser, if you do:
const foo = document.querySelector("#foo")
foo.textContent = "bar"
console.log(foo.textContent) // it's "bar"

So the code in https://github.com/vuejs/vue-test-utils-next/issues/362 makes Test Utils stubs closer to the generally expected behavior in a browser - reverting this seems like a step backwards, and a significant breaking change from VTU v1 -> VTU v2.
I am not sure on the best way to handle this - ideally we want to have both of these behaviors, we should not need to choose one breaking change over another.

The problem is that all snapshots that use the same component more than once break with that change too. It's not just when you query for prop values. That seems like a more serious break 😬. Literally half my test suites on multiple projects fails if I upgrade past RC3.
I would like to try to help solve the problem, but my knowledge how things work in this code base is very limited. Perhaps the problem is the caching you mentioned above? Maybe it's worth removing it and seeing if both features work again? If so we can add the test to ensure the features and work out how improve performance later (I'm assuming that the caching is only for performance).

The caching was adding in this PR for the specific reason to make it so you don't need call getComponent  again to get the updated version, removing it will definitely break the original bug it fixed.
While I understand snapshot + shallowMount is somewhat common in the Vue testing community, it breaks a lot of well established practices around testing. A snapshot of a shallowMount component is basically an assertion against the internal details of Vue Test Utils - it provides little to no validation that your component actually behaves how it should. Are you able to share the projects/test? Happy to provide some feedback/alternative testing strategies.
It would be great to fix this,  but we can't do so if it means reverting real bug fixes (like the one described in this issue because of a test depending on an implementation detail.
A potential fix that would allow us to support both behaviors might be to only use the cached stubs when using getComponent or findComponent. Even then, I'd still recommend against shallowMount + snapshots - they do not provide any validation outside of notifying you that an implementation detail changed, which is not something you should care about when testing.
Opinions aside, we can leave this open until we fix it. Let's explore some get/findComponent specific behavior - if we add the example reproduction but the OP, we have a solid test suite to guide us.

We ran into the same problem. We don't check against a snapshot but we check if attributes have specific values so something like
// (pseudo-code with example from above)
wrapper.findAll("ai-icon")[0].attributes("icon").toBe("left-icon");
wrapper.findAll("ai-icon")[1].attributes("icon").toBe("right-icon");

where the second assertion would fail due to the caching.
Shallowing makes sense in those cases where the ai-icon component has its own tests. If we use mount it might cause issues due to mocking or other stuff at any later point.
So do you have any ideas or plans if this can be fixed?

@mariusheine that's a similar situation to me. I'm rarely using snapshots anymore, but I have many scenarios where I use shallow mounts to reduce side effects and test for attributes/props on them.

So do you have any ideas or plans if this can be fixed

@mariusheine it's a bug so we should definitely fix it. I did not get to explore this deeply yet. Happy to either help out if someone has the time to, or do it when I have the time. I don't have an idea on how to fix it immediately, my approach is normally to add the test case I want to pass into this code base, then just run the tests in watch mode and modify code until everything passes.

Should shallow mount just not exist if it's not meant to be used? Or for what scenarios should we use it if attributes/props are not good to check against? (Honest question with absolutely no malicious intent 😬. I'm pretty new to the js/ts world).

@yakobe I generally don't like to use shallow mount for the reasons outlined above, especially with a snapshot - I don't think it's useful to know a specific DOM snapshot, I find more value in knowing the component behaves correctly (eg: if I click on this button, does the component update how I expect, etc). I find these tests fail a lot during refactoring, even if the code still works fine. I think good tests should be resilient to a major refactor.
Opinions aside, we should still make sure that everything behaves as you'd expect. Right now the shallow snapshot output is wrong, so we should fix it. I am guessing we just need some specific logic for findComponent and getComponent 🤔 we know that this was working before, so we should be able to come up with a combination of code that satisfies all use cases.

@lmiller1990 Sounds good! I would love to help.

my approach is normally to add the test case I want to pass into this code base, then just run the tests in watch mode and modify code until everything passes.

My change in https://github.com/yakobe/vue-test-utils-next/commit/3283eeeabaa7fb6da81be6b611e18c44f0e4409b extends the existing tests with an extra check for this bug. It obviously fails at the moment but I guess we can fiddle with the code until everything passes 😄.
Unfortunately I'm a noob at contributing to OSS. I have many years of non-OSS, but on long running projects so I dont have a "flow" yet for contributing quickly. With a bit of luck I will find some time to take a look soon. In the mean time, let me know if there's anything else i can do to help.

The flow is pretty much the same as non OSS.

identify problem (we did that here)
fork and clone this repo (you did that here
add a test to reproduce the current problem, a more minimal version of the test in the OP (also you did that here)
fix the problem
push to your repo
make a PR
🍻

I created PR #610 for this problem, and want to resolve this issue too ...!!
However it has a little problem, what do you think of it ??

@YutamaKotaro wow, great!
what is the "little problem" you are referring to?

@lmiller1990
As you already gave me comments, what I meant was the orders of attributes and props.
https://github.com/vuejs/vue-test-utils-next/pull/610#discussion_r637392308
So, there is no big problem. Thanks for your kindly comments !!

Hello everyone. @YutamaKotaro fixed this problem. I will do a release soon with the fix.


[Bug] Missing electron env variables in VS Code debug mode

When running the application through debugging via Visual Studio Code, the application lacks some environment variables associated with electron, for example process.env.INIT_CWD. If run the application through npm run dev, then this variable is present.


bucket location is not supported

Setting the location when creating a new bucket doesn't work:
#!/usr/bin/env python3
from gcloud import storage
client = storage.Client(project='foo')
bucket = Bucket(client=client, name="bar")
bucket.location = "EU"
bucket.create()

The bucket is always created with the default US location .
Patching the properties before creating the bucket doesn't work either:
bucket._patch_property('LocationConstraint', "EU")

Thanks for the report!  I checked, and none of the user-settable properties were being passed through to the 'bucket.create' API.  #1579 should address the issue.

D'oh! Nice find @tseaver

Thanks for filing @sebastiancodes too!


s/powerfull/powerful/g

I noticed the typo "powerfull" is used lots of places.  Is this typo intentional?  Should be "powerful".

I think it’s just me. English is not my first language.
My mother was an English teacher, so she will not be happy? 😉
Thanks.

Has been solved. So I closed this one.

Has been solved. So I closed this one.


cjxl_ng: Extensive clean-up

Greatly streamline flag-handling
Add support for --num_reps
Add --quality in addition to --depth
Many detail improvements

I left a bunch of comments, of course not all of them necessarily need to be addressed by this pull request but please keep track of them (maybe with a TODO).

I think this needs a rebase.


[c2][build] Fixed a compilation issue with Android version compatibility

Reference the corresponding include according to different versions
Tracked-On: OAM-113239

@TianmiChen @YuanjunHuang @Shao-Feng please help to review, thanks!

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has completed Engineering Build for this issue, build is FAILURE. Please check the linked Tracked-On issue/Android CI Web  for more details

Android CI has completed Engineering Build for this issue, build is SUCCESS.To merge the changes please click on APPROVE FOR MERGE button in Android CI WEB

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has completed Engineering Build for this issue, build is FAILURE. Please check the linked Tracked-On issue/Android CI Web  for more details


fix(core): Add missing Zookeeper exceptions codes

Sync'd up to Zookeeper 3.9.2 error codes.
Why is this needed?
Server errors with missing error codes are handled poorly and result in connection close.
Proposed Changes

Add definition for all know error codes as of Zookeeper 3.9.2

Does this PR introduce any breaking change?
No.

Nice! Does this relate to #727?

@StephenSorriaux  yes! It does resolve #727


Broken link in the readme

Does anyone know where https://galaxyproject.org/cloud/k8s/ was moved to?

The chart README is the closest/most up-to-date docs we have. There are a couple of tutorials on the GTN but those are 3 years old and likely not accurate any more.


Add code of conduct

This PR adds a code of conduct for Dask. The starting point is the Contributor Covenant, with modifications made based on discussion in #6 and further discussion to be had here. Closes #6.

How are we going to determine whether or not and when to merge this? Consensus or majority of "dask developers"? Some other process?

How are we going to determine whether or not and when to merge this? Consensus or majority of "dask developers"? Some other process?

Lets aim for consensus for a while.  For this topic in particular I think it's important that everyone's views be heard and integrated, and that everyone feel comfortable with what we come up with.  Given the conversation so far I think that this is pretty achievable.

Consensus is my preference as well.
Does anyone have objections to setting a (soft) deadline for comments on the proposal, and then some time to collect +/- 1s?

I think the text is fine, and I have nothing specific I'd like to change. The lists of specific things we wish not to discriminate on is all a bit weird for me, and I wish there could be an easier way to say "we hope that we shall treat each other as humans".
For the issue of anonymous complains, would a webform which sends an email to the conduct address, with appropriate capcha, work?

Ah, indeed!

We discussed the status of this CoC on the monthly Dask call today (ref the meeting notes at https://docs.google.com/document/d/1UqNAP87a56ERH_xkQsS5Q_0PKYybd5Lj2WANy_hRzI0/edit). I'll summarize the discussion here.
The last remaining issues here are to:

Figure out how to submit CoC concerns and
Determine who reads/checks these concerns

For the first point, I've set up a couple of ways for submitting concerns:

Concerns can be e-mailed to<EMAIL_ADDRESS>A Google form (https://goo.gl/forms/YHc1pc9POZRH7RDt2) can be used to submit concerns. Fields like name and e-mail are optional in the form to allow for submitting concerns anonymously.

As to who reads/checks these concerns, it was discussed in the meeting that we should try for a group of 3-5 people. I'm happy to be one of these people. It was also brought up that it would be nice to have someone on this who isn’t a 20s/30s-white-male.
Does anyone here want to either volunteer to help monitor CoC concerns, or know of someone not here who would be good for this?

Thanks for setting up the email and form.
I'm also willing to volunteer, but would happily give way to someone else.
On Thu, Mar 7, 2019 at 8:07 PM James Bourbeau<EMAIL_ADDRESS>wrote:

We discussed the status of this CoC on the monthly Dask call today (ref
the meeting notes at
https://docs.google.com/document/d/1UqNAP87a56ERH_xkQsS5Q_0PKYybd5Lj2WANy_hRzI0/edit).
I'll summarize the discussion here.
The last remaining issues here are to:

Figure out how to submit CoC concerns and
Determine who reads/checks these concerns

For the first point, I've set up a couple of ways for submitting concerns:

Concerns can be e-mailed to<EMAIL_ADDRESS>A Google form (https://goo.gl/forms/YHc1pc9POZRH7RDt2) can be used
to submit concerns. Fields like name and e-mail are optional in the form to
allow for submitting concerns anonymously.

As to who reads/checks these concerns, it was discussed in the meeting
that we should try for a group of 3-5 people. I'm happy to be one of these
people. It was also brought up that it would be nice to have someone on
this who isn’t a 20s/30s-white-male.
Does anyone here want to either volunteer to help monitor CoC concerns, or
know of someone not here who would be good for this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/governance/pull/10#issuecomment-470776304, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQHIhFKhrpwL8X5YrdIL0aId7AVbZwbks5vUcXhgaJpZM4Zc0Dk
.

Thanks @TomAugspurger!
If possible, I think having a minimum of 3 people handling CoC concerns would be ideal. That way we can have an additional point of view and also avoid a potential even 1-1 split on topics. Just to reiterate, would anyone here either like to help monitor CoC concerns, or know of someone not here who would be good for this?

I'd be happy to be on such a committee.  I reached out to a couple people to help improve diversity, but didn't get much response.

Thanks @mrocklin! I've specified you, @TomAugspurger, and myself as the relevant members who will receive and review reports

All lingering concerns should have been addressed in the current CoC draft.
At this point, I'd ask for us all to try to review this draft over the next few days and voice any final comments/questions/edits/etc we may have. In terms of a timeline, I propose, barring any large changes, that we start collecting +/- 1s starting this Friday (April 5).

Thanks for pushing this through @jrbourbeau !
I'll try to review this before the Thursday meeting as well.

I've read things over and things seem sensible to me.

+1

@pitrou if you have a moment can I ask you to look over this document?

@mrocklin Ok, I took a quick look. I hope I'm not rehashing previous questions.

If there are no further comments then I suggest that we merge this in 48 hours.  All current owners have been informed of this PR and the intent to merge.

Merging this in.  Thank you @jrbourbeau for starting and guiding this process.


Drafts REST API docs

The first REST API documentation pages for A3.
It might be easiest to pull this down and run npm run dev to view it at http://localhost:8080/reference/rest-api/pieces.html

@boutell There will undoubtedly be technical changes needed to this, at least in regards to available request parameters I'm sure. I'd welcome notes on those. Also on structure or anything I might be missing.

I think hammering home the relationship between the module name and the API
URL is important and worth doing. "But what is my piece type" is going to
be the new "where do I put my code" if we aren't careful. You can't be too
obvious about this stuff.
On Mon, Jan 4, 2021 at 12:38 PM Alex Bea<EMAIL_ADDRESS>wrote:

@abea https://github.com/abea requested your review on: #21
https://github.com/apostrophecms/a3-docs/pull/21 Drafts REST API docs.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/a3-docs/pull/21#event-4165986967, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27O27LKVYF3M7RY4OSLSYH4KLANCNFSM4VERQO5Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

I think hammering home the relationship between the module name and the API
URL is important and worth doing. "But what is my piece type" is going to
be the new "where do I put my code" if we aren't careful. You can't be too
obvious about this stuff.
On Mon, Jan 4, 2021 at 12:38 PM Alex Bea<EMAIL_ADDRESS>wrote:

@abea https://github.com/abea requested your review on: #21
https://github.com/apostrophecms/a3-docs/pull/21 Drafts REST API docs.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/a3-docs/pull/21#event-4165986967, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27O27LKVYF3M7RY4OSLSYH4KLANCNFSM4VERQO5Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

Okay. As long as we're going to be consistent about this everywhere.
"piece-name" needs to be laser-clear from previous context. If it's not,
say "piece-module-name".
On Tue, Jan 5, 2021 at 10:16 AM Alex Bea<EMAIL_ADDRESS>wrote:

@abea commented on this pull request.
In docs/reference/api/pieces.md
https://github.com/apostrophecms/a3-docs/pull/21#discussion_r551995635:

@@ -4,23 +4,23 @@ Every piece type has built in REST end points that share their overall s

Endpoints
-Note: :piece-name represents the name option for a piece type. For example, you would request all pieces of an article piece type with /api/v1/article.
+Note: :piece-type represents the name option for a piece type. For example, you would request all pieces of an article piece type with /api/v1/article.
If name is important in the placeholder, then :piece-name should work. We
could make the description more explicit, with ":piece-name represents
the name of a piece-type module." I'm trying to avoid the extra verbosity
and avoid beating people over the head with "module." This is something
we've discussed a few times and documented in our internal docs outline:
Acknowledge that everything is a module and what the types are. After
that, don't worry about saying "module" all the time (e.g., "create a
widget" vs "create a widget module"). Don't make it sound more complex than
it is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/a3-docs/pull/21#discussion_r551995635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27LEKOSYOZUQGWPXDCTSYMUNHANCNFSM4VERQO5Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

Okay. As long as we're going to be consistent about this everywhere.
"piece-name" needs to be laser-clear from previous context. If it's not,
say "piece-module-name".
On Tue, Jan 5, 2021 at 10:16 AM Alex Bea<EMAIL_ADDRESS>wrote:

@abea commented on this pull request.
In docs/reference/api/pieces.md
https://github.com/apostrophecms/a3-docs/pull/21#discussion_r551995635:

@@ -4,23 +4,23 @@ Every piece type has built in REST end points that share their overall s

Endpoints
-Note: :piece-name represents the name option for a piece type. For example, you would request all pieces of an article piece type with /api/v1/article.
+Note: :piece-type represents the name option for a piece type. For example, you would request all pieces of an article piece type with /api/v1/article.
If name is important in the placeholder, then :piece-name should work. We
could make the description more explicit, with ":piece-name represents
the name of a piece-type module." I'm trying to avoid the extra verbosity
and avoid beating people over the head with "module." This is something
we've discussed a few times and documented in our internal docs outline:
Acknowledge that everything is a module and what the types are. After
that, don't worry about saying "module" all the time (e.g., "create a
widget" vs "create a widget module"). Don't make it sound more complex than
it is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/a3-docs/pull/21#discussion_r551995635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27LEKOSYOZUQGWPXDCTSYMUNHANCNFSM4VERQO5Q
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his


kf ready test is failing - missing deployment istio-egressgateway

https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/kubeflow-gcp-blueprints-master-periodic/1280857598203006977
>           raise ApiException(http_resp=r)
E           kubernetes.client.rest.ApiException: (404)
E           Reason: Not Found
E           HTTP response headers: HTTPHeaderDict({'Audit-Id': 'b7c92170-04c6-4418-8aa3-dd0cff342cbe', 'Content-Type': 'application/json', 'Date': 'Wed, 08 Jul 2020 13:37:18 GMT', 'Content-Length': '240'})
E           HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"deployments.apps \"istio-egressgateway\" not found","reason":"NotFound","details":{"name":"istio-egressgateway","group":"apps","kind":"deployments"},"code":404}

Here's the test
https://github.com/kubeflow/kfctl/blob/12318dd5cf36f2d7e85c5ce9f2ee0da62f4a12ae/py/kubeflow/kfctl/testing/pytests/kf_is_ready_test.py#L170
The deployment doesn't exist.
Looking at our hydrated manifests it looks like the egressgateway component is disabled
.build/istio/Base/EgressGateway/EgressGateway.yaml
# EgressGateway component is disabled.

It looks like the egressgateway isn't required for out bound internet access; our notebook tests are passing. I also tried it manually.

Test has been refactored into a separate istio_test which is still failing
Looks like telemetry service might be missing.


Build fails on OpenBSD

OpenBSD is listed as a supported platforms, but it fails to build on it.
Here is error log. It seems that libc crate doesn't have these structs and functions on openbsd.
   Compiling thread-priority v0.8.0
error[E0412]: cannot find type `sched_param` in crate `libc`
  --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:63:34
   |
63 |     fn into_posix(self) -> libc::sched_param {
   |                                  ^^^^^^^^^^^ not found in `libc`

error[E0412]: cannot find type `sched_param` in crate `libc`
  --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:64:54
   |
64 |         let mut param = unsafe { MaybeUninit::<libc::sched_param>::zeroed().assume_init() };
   |                                                      ^^^^^^^^^^^ not found in `libc`

error[E0412]: cannot find type `sched_param` in crate `libc`
  --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:69:38
   |
69 |     fn from_posix(sched_param: libc::sched_param) -> Self {
   |                                      ^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find function `__errno_location` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:204:38
    |
204 |                 Err(Error::OS(*libc::__errno_location()))
    |                                      ^^^^^^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find function `__errno_location` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:222:38
    |
222 |                 Err(Error::OS(*libc::__errno_location()))
    |                                      ^^^^^^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find function `pthread_setschedparam` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:387:23
    |
387 |                 libc::pthread_setschedparam(
    |                       ^^^^^^^^^^^^^^^^^^^^^ not found in `libc`

error[E0412]: cannot find type `sched_param` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:390:45
    |
390 |                     &params as *const libc::sched_param,
    |                                             ^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find function `pthread_getschedparam` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:452:25
    |
452 |         let ret = libc::pthread_getschedparam(
    |                         ^^^^^^^^^^^^^^^^^^^^^ not found in `libc`

error[E0412]: cannot find type `sched_param` in crate `libc`
   --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/thread-priority-0.8.0/src/unix.rs:455:39
    |
455 |             &mut params as *mut libc::sched_param,
    |                                       ^^^^^^^^^^^ not found in `libc`

Some errors have detailed explanations: E0412, E0425.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `thread-priority` due to 9 previous errors

Thanks much for reporting this. Before writing down the list I carefully checked if the same mechanisms are available in BSD and they should be. I think this is a bug of libc that it doesn't expose these functions in the crate for openbsd, I'll have a look there.
OpenBSD itself should have the support.
Unfortunately, GitHub CI doesn't have *BSD building machines which I'd really like to use for this crate.

After the pull request in libc gets merged, I'll need to work around the absence of libc::__errno_location() in the thread-priority code.

Can you please try either with the master branch of version 0.8.1?

tested both, it builds now, yeah.
but when i ran cargo test --test unix there were 16 failed tests, is this okay?

This is odd, can you please tell what tests fail for you?

here's the output of test command:
    Finished test [unoptimized + debuginfo] target(s) in 0.03s
     Running tests/unix.rs (target/debug/deps/unix-7edcd13525f73f7c)

running 20 tests
test check_min_and_max_priority_values::case_4 ... FAILED
test check_min_and_max_priority_values::case_1 ... FAILED
test check_min_and_max_priority_values::case_2 ... FAILED
test check_min_and_max_priority_values::case_3 ... FAILED
test check_min_and_max_priority_values::case_5 ... ok
test check_min_and_max_priority_values::case_6 ... ok
test get_and_set_priority_with_normal_policies::policy_1::correct_priority_2::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_normal_policies::policy_2::correct_priority_2::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_normal_policies::policy_3::correct_priority_1::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_normal_policies::policy_1::correct_priority_1::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_normal_policies::policy_4::correct_priority_1::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_normal_policies::policy_4::correct_priority_2::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_realtime_policy_requires_capabilities::case_2_roundrobin ... ok
test get_and_set_priority_with_normal_policies::policy_2::correct_priority_1::incorrect_priority_1 ... FAILED
test get_and_set_priority_with_realtime_policy_requires_capabilities::case_1_fifo ... ok
test get_and_set_priority_with_normal_policies::policy_3::correct_priority_2::incorrect_priority_1 ... FAILED
test set_priority_with_normal_policy_but_with_invalid_value::case_1 ... FAILED
test set_priority_with_normal_policy_but_with_invalid_value::case_2 ... FAILED
test set_priority_with_normal_policy_but_with_invalid_value::case_3 ... FAILED
test set_priority_with_normal_policy_but_with_invalid_value::case_4 ...

Okay, I know what the problem is and know how to fix it. I'll post once I fix it.

It looks like it builds now. Can you please check it once more?

now all test are passing. thanks!

Glad to hear it works for you now! Well, you are author of this issue and you decide when to close it. I'd say if it works for you and the issue you opened this ticket for has been addressed, I'd close it :-)

ah, okay, i'm closing it then. thank you for your support!


FingerPrint Login

Hi
in my project i need to have both username/password login and Fingerprint Login and I do not know how to implement both authentication type in IdentityServer. can you help me?

Important update
This organization is not maintained anymore besides critical security bugfixes (if feasible). This organization will be archived when .NET Core 3.1 end of support is reached (3rd Dec 2022). All new development is happening in the new Duende Software organization.
The new Duende IdentityServer comes with a commercial license but is free for dev/testing/personal projects and companies or individuals making less than 1M USD gross annnual revenue. Please get in touch with us if you have any question.

Thank You


Async extension runners?

As in this example from the docs:
from strawberry.extensions import Extension

from mydb import get_db_session

class MyExtension(Extension):
    def on_request_start(self):
        self.execution_context.context["db"] = get_db_session()

    def on_request_end(self):
        self.execution_context.context["db"].close()

Is it an architectural decision that the extension runner doesn't support coroutines?

I think we should support that, similar to this https://github.com/strawberry-graphql/strawberry/issues/1085

I'll take a look


Unreal: fixes for custom integration plugin path

Changelog Description
Setting AYON_UNREAL_PLUGIN will override now inbuilt integration. Also fixing type issue with source plugin path.
Testing notes:

set AYON_UNREAL_PLUGIN to your local copy of https://github.com/ynput/ayon-unreal-plugin
OPTIONAL: delete existing plugin from Unreal Engine
run Unreal on AYON project

when https://github.com/ynput/ayon-core/pull/614 is merged, we need to reopen it in https://github.com/ynput/ayon-unreal

PR moved to https://github.com/ynput/ayon-unreal/pull/5


Fixes #30

Hmm... not sure what happened here...

There was an error with yarn and the very old referenced phantomJS. After merging in the cleaned up dependencies it seems to work fine.


Incompatible ratbagd API version (required: 1, provided: 2) when building libratbag manually

Information

ratbagd version: 0.17
Distribution: Artix
Kernel version: Linux 6.10.0-artix1-2 x86_64 GNU/Linux
extra/piper: 0.7-3

Describe the bug
See #1629 for more info.
I had to build libratbag manually to strip systemd:
yay -S swig # was missing build dep
meson setup -Dsystemd=false -Dlogind-provider=elogind build
ninja -C build
sudo ninja -C build install

yay -Sdd piper # install without libratbag dependency

Looked at the code and seems like piper 0.7 use api v2 https://github.com/libratbag/piper/blob/master/meson.build#L11 and https://github.com/libratbag/libratbag/blob/master/meson.build#L21, so I'm not sure what happening there.
To Reproduce

sudo ratbagd # Starting ratbagd version 0.17 (API version 2)
piper
See screenshot

Hi! You need to also build Piper from source.

Is there a reason why? If I get artix devs to add libratbag with elogind to artix repos would I still need to build piper? How do I explain this to them?


Make the variadic overloads AEIC

This marks all of the variadic builder overloads as @_alwaysEmitIntoClient so that these aren't permanently part of our ABI. However, in order to do so we have to expose DSLTree and friends as a public interface. This removes all of the @_spi(RegexBuilder) attributes and makes everything public but underscored.

@swift-ci please test

I support adding an underscored function (underscore can be on the namespace) to creating corresponding DSL tree nodes and removing the public and spi from anything we possibly can after that.

(assuming these creation methods let us de-public DSLTree nodes)


Abandoned: Add model_runs directory

This makes it easier to iterate over all the runs by calling dir_ls on model_runs and also makes it easier to locate collated  plots and other files that apply to all the model runs.

GitHub is confused about what is changed. Abandoning in favor of https://github.com/CDCgov/pyrenew-hew/pull/136


jsonrpc-types: add default unknown variants to various enums

It was recently reported in https://github.com/diem/diem/issues/8643
that a client built from the release-1.2 branch failed to deserialize a
response from a server built from the release-1.3 branch with the
following error:
"unknown variant `treasury_compliance`, expected one of `unknown`, `child_vasp`, `parent_vasp`, `designated_dealer`"

Looking at the difference between the code in
json-rpc/types/src/views.rs for the two difference releases it looks
like the TreasuryCompliance Role didn't exist in the 1.2 release but
does in the 1.3 release. So the old client wouldn't be able to properly
understand, parse and interpret that role since the old client doesn't
know about it. Despite this the older client should still be able to
properly deserialize a response from a newer server.
This patch addresses this issue by ensuring that all view enum's defined
have an Unknown varient marked with #[serde(other)] which will cause
deserialization to default to the Unknown variant in the event the
client doesn't know about a variant.
Fixes: #8643

This PR may have modified JSON-RPC server code.
Breaking changes policy:

Changing JSON-RPC method signatures or removing/modifying fields
in the response in /V1 will not be accepted.
Adding fields is ok.
Adding a new JSON-RPC method is ok.

Please ensure you have also done the following to update the docs:

Update json-rpc/API-CHANGELOG.md.
Add/update type/method documentation under json-rpc/docs.

/land

@bmwill :exclamation: This PR is still missing approvals, unable to queue for landing

/cherry-pick release-1.3

/cherry-pick release-1.2

@bmwill :exclamation: cherry-pick failed, possibly due to conflicts. You can perform the cherry-pick yourself by running the following commands:
git fetch https://github.com/diem/diem.git release-1.2 148da63b11c4159afa7175d30d29e4e6fa359020
git checkout release-1.2
git cherry-pick c247b098b9392286da8ff8c7cd6cf9880e9920c8..148da63b11c4159afa7175d30d29e4e6fa359020

/land

:broken_heart: Test Failed - ci-test

/land

https://www.mail-signatures.com/de/articles/tag/mailto-links/Von meinem/meiner Galaxy gesendet
-------- Ursprüngliche Nachricht --------Von: Brandon Williams @.> Datum: 30.06.21  01:13  (GMT+01:00) An: diem/diem @.> Cc: Subscribed @.***> Betreff: Re: [diem/diem] jsonrpc-types: add default unknown variants to various enums (#8646)
/land
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

@Ischgol: :key: Insufficient privileges: Not Collaborator

https://www.mail-signatures.com/de/articles/tag/mailto-links/Von meinem/meiner Galaxy gesendet
-------- Ursprüngliche Nachricht --------Von: bors-libra @.> Datum: 30.06.21  01:07  (GMT+01:00) An: diem/diem @.> Cc: Subscribed @.***> Betreff: Re: [diem/diem] jsonrpc-types: add default unknown variants to various enums (#8646)
💔 Test Failed - ci-test
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

https://www.mail-signatures.com/de/articles/tag/mailto-links/Von meinem/meiner Galaxy gesendet
-------- Ursprüngliche Nachricht --------Von: Xiao Li @.> Datum: 30.06.21  00:15  (GMT+01:00) An: diem/diem @.> Cc: Subscribed @.***> Betreff: Re: [diem/diem] jsonrpc-types: add default unknown variants to various enums (#8646)
@xli approved this pull request.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.


daos: investigate potential daos_mknod as open/close

The mfu_mknod is not critical to dcp, but it may be required on other tools.  This is lower priority, but if dfs has no mknod, I'm wondering if it can be emulated with a dfs_open/dfs_close.

@dsikich
I'm going to look into this, since I see minor errors cropping up when using dcp with a dfuse mounted path.
I.e. mfu_flist_copy -> mfu_create_file -> mfu_file_mknod
throws an error about the operation now being supported.

@daltonbohning can you share the error output here?

Setting up the pool/container
dmg pool create -s 1G -n 10G
export pool1=9dec0f4a-f5be-451d-9570-619641aeb37c
daos cont create --svc 0 --pool $pool1 --type POSIX --path /tmp/dbohninx/uns/p1cont1
export p1cont1=073e8a48-43ae-4732-ba94-5c520df1a878
dfuse --svc 0 --pool $pool1 --cont $p1cont1 -m /tmp/dbohninx/p1cont1
Contents of source directory
ls /tmp/dbohninx/s
dir1  file1
Copying
dcp /tmp/dbohninx/s /tmp/dbohninx/p1cont1
The error
[/home/dbohninx/mpifileutils_dev/mpifileutils/src/common/mfu_flist_copy.c:1140] ERROR: File `/tmp/dbohninx/p1cont1/s/file1' mknod() failed (errno=38 Function not implemented)
Corresponding code
https://github.com/daltonbohning/mpifileutils/blob/6f4a6d3252b720c770ed2bcb64c99dac3ae9f2bf/src/common/mfu_flist_copy.c#L1128-L1144
Result dfuse directory
ls /tmp/dbohninx/p1cont1/s
dir1  file1
The result appears to be fine, but the error is still thrown, presumably because dfuse doesn't have mknod implemented.
Of course, mfu_file_mknod switches between daos_ and mfu_ functions, BUT, this is a dfuse mounted path, so it appears to mpifileutils as a POSIX path, and therefore mfu_mknod is called and dfuse hasn't implemented it.
Another direct example (not using dcp)
mknod /tmp/dbohninx/p1cont1/some_file p
mknod: ‘/tmp/dbohninx/p1cont1/some_file’: Function not implemented

https://github.com/hpc/mpifileutils/pull/378
This adds daos_mknod, but dfs itself still does not have a mknod function, so the "errors" still appear for a dfuse mounted DAOS destination.

Moved the dfuse-specific discussion to #381


Do not test the GUI on Appveyor

while there is a problem with appveyor

See https://github.com/silx-kit/silx/issues/1039 and https://github.com/appveyor/ci/issues/1715


Staging a Git change ignores repo settings

I have a repo with specific autocrlf and whitespace settings. When I commit a one-line change in VSCode, it changes the entire file (in the patch). If I commit the exact same one-line change (made in VSCode) with Git Gui, everything works fine.

What if you use the command line: git add FILE && git commit -m message


TempFile "".suffix not replacing "" with random string as expected

What version of Go are you using (go version)?
1.10.3, but getting same result on go playground
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
darwin/amd64
What did you do?
Creating at temp file with a suffix after the random string does not seem to work.
Per the docs: "The filename is generated by taking pattern and adding a random string to the end. If pattern includes a " * ", the random string replaces the last " * ".
Here's example in the playground:
(I just added a Println to the example in the ioutil.TempFile GoDoc to show the file name)
https://play.golang.org/p/JAOZUSeNUBB
What did you expect to see?
/tmp/example.054003078.txt
What did you see instead?
/tmp/example.*.txt054003078

Thanks for the report.
The TempFile * thing was introduced in go1.11. The playground is still on 1.10.  Please try with 1.11 and comment here if it still doesn't work for you. Closing here, in the meantime, since I don't believe this is a bug


feat(dsp): support implicit Offer policy type

What this PR changes/adds
Set "Offer" as implicit policy type on JsonObjectToContractOfferMessageTransformer
Why it does that
because it's not mandatory in the dspace:offer type
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #4118
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.88%. Comparing base (7f20ba5) to head (5ff04f1).
Report is 231 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4143      +/-   ##
==========================================
+ Coverage   71.74%   74.88%   +3.13%
==========================================
  Files         919      986      +67
  Lines       18457    20262    +1805
  Branches     1037     1143     +106
==========================================
+ Hits        13242    15173    +1931
+ Misses       4756     4589     -167
- Partials      459      500      +41

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Backup of incoming SMS: "Date" header shows timestamp of local reception instead of sender's time

Using SMS Backup+ version 1.5.11 installed from F-Droid (on /e/OS 0.10-o-2020081968665), I can observe:

The RFC822-type messages created as backup of SMS messages carry a "Date" header which apparently represents the contents of the "date" column of table "sms" in "mmssms.db".
For incoming SMS messages, the remote side's timestamp is stored in the "date_sent" column of table "sms" in "mmssms.db".
An example:X-smssync-version: 1576
Date: Wed, 02 Sep 2020 20:30:56 +0200

sqlite> select type, date, date_sent from sms where _id=10;
type|date|date_sent
1|1599071456069|1599071455000

$ date<EMAIL_ADDRESS># incoming, date
Wed Sep  2 20:30:56 CEST 2020

$ date<EMAIL_ADDRESS># incoming, date_sent
Wed Sep  2 20:30:55 CEST 2020

In email messages, the "Date" header contains a timestamp representing the point in time a message was written (not the point in time it was received).
So to me this looks like unintended, wrong behaviour. I think the "Date" header in the backup messages should show the time the message was sent, i.e. for incoming SMS messages the value of the "date_sent" column.
In case the current behaviour is intended and/or won't get changed by default, could you make the suggested behaviour an option?

Agreed, but @jberkel will have to make the final call.
I would hope that both timestamps could be encoded in the RFC822 message headers, with the received timestamp for incoming messages and the network-acceptance timestamp for outgoing messages perhaps included in X-Received-Date: headers or even embedded in synthesised Received: headers.


Add TiKV's mission

Add a mission statement to TiKV. @winkyao and @siddontang were part of the editing and revising of this mission.

Closing. I am not longer involved with the project and have no stake in this merging. Feel free to create a new PR.


Force all tooltips to be displayed

How to make all tooltips for all points to be displayed? At the same time. No action like hover just let them be

Hello, I'm sorry this issue hasn't received much attention yet. It seems this is an implementation question, could you please post your question to StackOverflow with the Chart.js tag and include a link here. This will ensure your question reaches the largest audience.
https://stackoverflow.com/questions/tagged/chart.js

 myBarChart = new Chart(ctx1).Bar(buyerData,options);
 bars=myBarChart.datasets[0].bars;

     var options={
      ....
     onAnimationComplete: function(){
            myBarChart.showTooltip(bars,false);
            }
    .....
     }

  Chart.defaults = { global: { ... // Array - Array of string names to attach tooltip events //tooltipEvents: ["mousemove", "touchstart", "touchmove", "mouseout"], ...}

https://github.com/ryx725/chart.js/blob/master/tooltip.md

I've had asked this question on Stackoverflow. It was a bit open ended as we were in a phase of researching for a better option to plot charts. (I understand as the data points grow it might clutter the plotting of graph).
https://stackoverflow.com/questions/28581364/display-all-tooltips-in-chartjs
Had to go with highcharts solution :(. But I would still like to see this implemented as an improvement.
Thanks a lot.

If I understand correctly, the ability to show data values for bars is needed. Consolidating with #327

I believe #327 is close enough. :+1:
Thanks.

https://stackoverflow.com/questions/36953558/hide-disable-tooltips-chart-js


command-not-found: Update docs for Homebrew

Update documentation for Homebrew to indicate that a recent version of
Homebrew does not need to tap command-not-found Homebrew repository.
See: Homebrew/brew#11137

I'd actually omit any mention of how to install... this code is unlikely to get touched soon, and anyone looking at this within a few months will probably be running a newer version of homebrew as it auto-updates itself IIRC. Anyone who hits problems will almost certainly go look up the repo and find the install instructions, but I suspect the number of folks impacted will be very small.

Yes, I considered removing the how-to install part altogether. But then thought of keeping it around for a short while for that small subset of people who updated prezto (user environment) but didn't update homebrew (system environment) and then clean it up.

Don't forget to also remove the footnote [3] if you remove this.
Indeed :)


Ci/update ci

Adds a workflow triggered on release to update the changelog: It takes the notes under the unreleased section and adds them to the new release section. It also creates a PR to reflect the updates to the changelog after creating the release.
Adds a new workflow triggered on PRs to run tests and QA.
Updates the release workflow to use reusable actions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.32%. Comparing base (50a06d3) to head (d0f737f).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #17   +/-   ##
========================================
  Coverage    78.32%   78.32%
========================================
  Files            9        9
  Lines          706      706
========================================
  Hits           553      553
  Misses         153      153

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Write protect installed package files?

Thinking it might be good to chmod 444 package files during installation because it will give a clear signal that you've landed in code you shouldn't be modifying if M-. in LSP mode takes you there.

meh. maybe someday.


Prevent ObcQuotaObjectsAlert overlapping with ObcQuotaObjectsExhausedAlert

Since queries for both ObcQuotaObjectsAlert and
ObcQuotaObjectsExhausedAlert are same, we don't require both the alerts to be fired at the same time.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2257949

@aruniiird Can you pls fix a commit lint issue

@aruniiird Can you pls fix a commit lint issue

Done.

/cherry-pick release-4.16


About tabview tabs rebuild

I’m developing a desktop app using a tabView as the main widget. When the "reorder" event occurs within the tabView, I’m noticed that after reordering, all tab bodies between the oldIndex and newIndex are being build again. I think rebuilding process becomes problematic, for example, when dealing with large files within tab bodies, causing significant loading times. If I don't handle it asynchronously, the tab bar reorders fine, but the tab bodies still function in their previous order.(when I use futurebuilder, tabBody follow correct order but take quite some time.
I want if it is possible that when reorder function is called, the tab bodies' pointers are swapped, then I could potentially avoid the need for rebuilding. Because I’m not highly experienced in development, I acknowledge the possibility of misunderstandings on that.
Thank you for reading text.

You can use an AutomaticKeepAliveClientMixin.
Duplicate of #910


Requiring redirect-hack.html for redirects makes injecting into existing extensions break this functionality

Ideally this entire thing should be able to be injected into an existing extension with no issues. However currently the redirect-hack.html file is used to handle redirects (which will not exist when injected into another extension). Should find a way to remove the dependency on this file so it's more portable...

For the time, it should be enough to use any already existing file in that extension, no?

Ideally this entire thing should be able to be injected into an existing extension with no issues. However currently the redirect-hack.html file is used to handle redirects (which will not exist when injected into another extension). Should find a way to remove the dependency on this file so it's more portable...

hello brayan can you help me with this https://github.com/mandatoryprogrammer/CursedChrome/issues/67

@mandatoryprogrammer  the extension is not working in redirect url.
At the first, the proxy is getting the content of the redirected page but the assets is not loaded.

please check this image. the current content is for the redirected page.


Code lenses for tests do not update their positions on edit

Environment data

VS Code version: 1.28.2
Extension version (available under the Extensions sidebar): 2018.9.2 (29 Oct 2018)
OS and version: Linux Mint 19 Cinnamon (Cinnamon 3.8.9, Linux kernel 4.15.0-36-generic)
Python version (& distribution if applicable, e.g. Anaconda): 3.6.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: unittest

Actual behavior
Here are the correct code lens positions:

This happens if I add three empty lines inside the function:

The lenses keep their positions before 6th and 7th lines of code.
This happens even with default user settings and only Python extension enabled.
But everything is OK if I add empty lines just before the test class:

Expected  behavior
Code lenses should always follow the test class
Steps to reproduce:

Create new folder with file test.py:

import unittest

def func():
    pass

class Test(unittest.TestCase):
    def test(self):
        pass

Enable testing with unittest package in .vscode/settings.json:

{
    "python.unitTest.unittestArgs": [
        "-v",
        "-s",
        ".",
        "-p",
        "*test*.py"
    ],
    "python.unitTest.pyTestEnabled": false,
    "python.unitTest.nosetestsEnabled": false,
    "python.unitTest.unittestEnabled": true
}

Run command Python: Discover Unit Tests
Add some empty lines after line 3
Save the file

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Jedi Python language engine.
##########Linting Output - pylint##########

--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

##########Linting Output - pylint##########

--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
 INFO no standard startup: not a new window
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3297 [ms-python.python]Cannot read property 'replace' of undefined
e.$onExtensionRuntimeError @ /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3297
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3297 TypeError: Cannot read property 'replace' of undefined
	at Object.parseVersion (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/out/utils/version.js:7:15)
	at getos (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/out/utils/platform.js:108:29)
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/index.js:96:16
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:421:16
	at iteratorCallback (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:998:13)
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:906:16
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/index.js:91:18
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:3060:16
	at eachOfArrayLike (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:1003:9)
	at eachOf (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:1051:5)
	at Object.eachLimit (/home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/node_modules/async/dist/async.js:3122:5)
	at /home/maksim/.vscode/extensions/ms-python.python-2018.9.2/node_modules/getos/index.js:81:13
	at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3)
e.$onExtensionRuntimeError @ /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3297

I can't replicate it with the same setup, so I'm thinking it's either a VS Code thing on Linux or it's another extension (e.g. we have had gitlens break our code lenses before).

Try disabling all other extensions and see if that makes a difference.

This happens even if all other extensions are disabled:

This does not happen with CodeMetrics' code lenses:


Ensure that all rapids-cmake files have include guards

This brings all of rapids/export inline with rapids-cmake code requirement which requires that all modules to use include_guard(GLOBAL).

@gpucibot merge


Widths of 2nd and greater plots is smaller than width of the first plot

This is a layout issue that will need some research into how Chaco Containers work.

Cannot reproduce the same...

@buhii you may get some help understanding the layout from this example.


Show overall Cinder status in CLI

oc get cinder will now surface the status (following the pattern used by other operators)

Thanks for this!  :-)


Correction for raw affiliation Department of Epidemiology and Biostatistics, Faculty of Medicine, Western University, London, ON

Correction needed for raw affiliation Department of Epidemiology and Biostatistics, Faculty of Medicine, Western University, London, ON
raw_affiliation_name: Department of Epidemiology and Biostatistics, Faculty of Medicine, Western University, London, ON
new_rors: 02grkyz14
previous_rors: 02agqkc58
works_examples: W4386892179;W4386892103
contact: 9f55fa752bd95ea9120e0b00c3f5e882:4d3511b553c4c09a @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


standardization directory

code coverage be decided by test suite. this commit only change pom and directory

thanks！


Adding moderator commands

Summary
Adds more moderator commands. See #48.

Now I'm thinking about giving actions on user (like banning or ignoring) the same treatment as the chat modes.
I also kind of like the idea of having one single method for dealing with chat modes, since we basically have five of them and the method structures look very alike.
Maybe that is something I can change later.

Looks good to me! 👍 Feel free to merge the PR at your earliest convenience.
I'm excited for these changes. :)