video/fb: add xres and yres for fb overlay

xres and yres of video overlay buffer may not same as primay framebuffer. so add it to check the framebuffer count of overlay
Summary
Impact
Testing

Very nice @terry0012 ! Do you have some device or example where it could apply? Please include in the commit message why it is different from xres_virtual and yres_virtual. At first glance it appears you are adding redundant information.
Why planeinfo doesn´t have these xres and yres?

Very nice @terry0012 ! Do you have some device or example where it could apply?

this info will be used by nuttx lvgl fb driver, so lvgl could output the render result to the overlay buffer.

Please include in the commit message why it is different from xres_virtual and yres_virtual. At first glance it appears you are adding redundant information.
Why doesn´t planeinfo have these xres and yres?

planeinfo can get from fb_videoinfo_s:
https://github.com/apache/nuttx/pull/10458/files#diff-3a12aade3805409e568c9cf0fabe44cea93c6b841ec116a570abf8eb1ab84ba5R493-R494


Question: is this module aimed to create h&s on a multi account environment?

From the documentation it's not clear to me if I can leverage this module on different account in order to implement, for example, a centralized account with VPC endpoints shared among many spokes accounts...
Thanks in advance.

Hi! The idea for now is to keep the TGW and central VPCs in the same AWS Account. The Spoke VPC piece in the module only asks for VPC IDs and TGW attachments (it does not create them) as it supposes these VPCs are handled in other AWS Accounts - we suggest using our VPC module for that.


Error after install another plugin

after install and active plugin  above the fold optimization show this error:
Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
look this
https://github.com/optimalisatie/above-the-fold-optimization/issues/14
please update this plugin to work better

@szepeviktor please help me

@andyexeter please help me

@nigrosimone please help me

Hello @fredroo !
Thank you for opening this issue.
This is a community fork of W3TC.
Maybe it is not the best way to alert contributors.
Although I am not a using this plugin you may contact me it you need immediate help - see my profile page.


Renames incorrect, duplicate withIdleTimeout to withMaxTotalConnections

This fixes the name of a duplicate function withIdleTimeout that should actually be named withMaxTotalConnections. The implementation is already correct, and the real def withIdleTimeout(idleTimeout: Duration): BlazeClientBuilder[F] remains untouched.

Build failure looks unrelated.


ToggleButtonGroup example not working for me, export missing?

https://solid-libs.github.io/solid-bootstrap/components/buttons says to use import { ToggleButtonGroup } from 'solid-bootstrap' for managed ToggleButtons. But when importing that, I get an error in the browser:

Uncaught SyntaxError: ambiguous indirect export: ToggleButtonGroup

I also can't find the file in this repo. What am I missing? Or are the docs wrong?

Thanks for reporting that.  It looks like something that was copied over from the react-bootstrap docs but not implemented.
I'll have a look at whether it easy to port, or alternatively remove it from the docs.

Yeah I've decided to just remove that from the docs.  It did some nasty cloneElement stuff.


timeval: use libc types for tv_sec and tv_usec

Background: I was trying to build an application that depends on this crate for a 32-bit ARM platform (arm-unknown-linux-gnueabihf target in Rust). The library failed to build because it was expecting the tv_sec and tv_usec members of timeval to be of type i64 when they are in fact i32 on that target.
I see there are already some cfg conditionals in the code to work around different timeval types on different platforms. I think a more universal solution would be to use the types that the libc crate defines for the timeval struct members directly: https://docs.rs/libc/0.2.94/libc/struct.timeval.html. I tested this and it makes the library build correctly for my target; however, there may be some issue with this on another platform that I'm not aware of. Happy to modify if so.
Thanks!

Thanks for your contribution, sorry things have been crazy recently but I'll try and test this myself later today.

No worries, I understand! I appreciate you taking the time to look at it.


Search greyed out

I have a form that sets some grafana variables and then the data source refreshes based on those variables. I have also set a reset code to run in Reset to clear the form and clear the grafana variables which does seem to work, but then if i type in the same search parameters the search button is greyed out almost as if the local state remembers its fetched that data. Have i missed something here

@craftzneko Please check the latest video and blog post, which explains how to work and synchronize data manipulation panel with dashboard variables: https://www.youtube.com/watch?v=DW-yuSopejY
Blog post: https://volkovlabs.io/blog/form-panel-use-variables-20240301/


Google Analytics

Hi all:
I would like to setup google analytics in every page in production. Can we add this to each page.
<script>
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');

  ga('create', 'UA-70417662-2', 'auto');
  ga('send', 'pageview');

</script>

it already exists in every page

Great. I think we have a different token. @mindcrusher11 has the idea of adding it as a javascript dependency.

he already split it into seperate file

yes it is already added so I am closing this issue


Added pass in for admin url

Hey- Just adding on a bit to Craig's work. Magento supports custom urls for admins so I needed a way to pass these in. Do you guys have any changes you would make to this?

:+1: Thanks!

Looks slick to me!


Migrate fontawesome5

This is a migration to dependence on FA5, using the fontawesome5 package. This likely breaks some of the examples. Not sure if the style file is actually needed.
What do you think?
(only tested on macos, using texlive)

Thank you - I think many of us have made this or similar fixes over the years as posquit0's had other priorities. I have push access now to help maintain Awesome-CV; so I went with my old PR for this (#235/#344) for no reason other than my own familiarity, that I know it's been working for me.
Please do ping me/open another PR if something's still not right or I missed something though! Cheers.


Riding a ridable pokemon through a glass pane

you can throw your pokemon through other people's glass pane and get into other people's houses and bases

Not much we can really do about this, as it's an issue with pixelmon collisions. You could try reporting over at there tracker.


Reserve excess capacity in seed cluster

This PR allows reservation of excess capacity to deploy new shoot control planes on a seed cluster
Currently the shoot control plane size has been statically set to a requirement of 7CPU core and 14Gi of memory
The number of shoot control planes that can be supported is 3 or 5% of currently running shoots, whichever is greater

Resolves: https://github.com/gardener/gardener/issues/254
TBD: Enable cluster-autoscaler on seed clusters to enable the working on reserve excess capacity

Hello @mvladev,
Kindly have a look at this PR when you have time. This PR attempts to reserve excess capacity in the seed by adding a chart in the seed-bootstrap.
Thanks & Regards,
Prashanth

Also, since we use priority classes which are beta in 1.11. Should we enable only for seeds with versions above 1.11 or even enable it for shoots below 1.11 (as alpha) ?

Our seeds are 1.10 right now and I don't think we should go to 1.11 already (too early, not enough experience yet). If it also works with 1.10, why not?

I have currently enabled it for all supported versions of kubernetes that is 1.8 and above. But the feature is only beta in 1.11, so I was just wondering if it's okay to take support from an alpha version feature to support gardener. It does seem to work properly in 1.10 as a an alpha feature, I have tried it out.

I just tried with version 1.9.8 for Azure and seems to be working well. And yesterday I have already tried for 1.10.5 and 1.11.0.

Have you calculated the amount of requested resources, which are required for all control plane pods? For each control plane would be 7 replicas with each 1000m cpu and 2Gi memory allocated, means in sum 7000m cpu and 14Gi memory per control plane. This is plenty.
I think also when you calculate with the resource limits, which are probably higher then the requests, these values would be pretty much. Ok we have to consider that we need some additional resources to schedule Terraform pods.

I think the limits will never reached by the pause containers, therefore I would only rely on the request, because they express how many resources are required to run a control plane with minimum requirements. I would suggest to allocate request/limits based on formula like this:
requests = (<sum of control-plane pods request> + <sum of resource requests for Terraform pods>) * 1.1

In your pause-container deployment you have currently set the requests to the same value as the limits.

I have updated the requests to the summation of cpu and memory requests. Refer previous comment and this commit - https://github.com/gardener/gardener/pull/267/commits/af589677ee8fad572402d6401979d100afd5ae89.

Maximum resource usage observed for a single pod in control plane is - CPU: ~200m, Memory: ~1150Mi
Maximum resource requests for a single pod in control plane is - CPU: 200m, Memory: 1200Mi
Total resource usage observed for all pods in control plane is - CPU: ~500m, Memory: ~3000Mi
Total resource requests for all pods in control plane is - CPU: 1765m, Memory: 4166Mi

The total resource requests for all pods is observed to be much greater than the actual usage in current control planes, and hence I am considering the total resource requests for the calculations that is - CPU: 1765m, Memory: 4166Mi (1), as the required resources for running all control plane pods.

Keeping the above in mind, I am changing the reserve-excess-capacity deployment to have the following resource requirements per pod - CPU: 500m, Memory: 1200Mi
There would be 4 replicas of this pod to support each shoot cluster totalling to - CPU: 2000m, Memory: 4800Mi which is > (1)

Hope this sounds reasonable.

The provided values matching with the values, which I have calculated: 1665m cpu and 3966Mi memory per control plane plus additional resources for the Terraform pods.
Therefore I would agree having 4 replicas with each 500m cpu + 1200Mi memory seems to be sufficient.
Rest looks overall good to me.
Would nevertheless waiting for the feedback of @mvladev

@dkistner Thanks for the feedback.

@prashanth26 can you please resolve the conflicting files?
Is there anything else to be discussed yet before merging?

Thank you.


MedGui Reborn doesn't save my joypad configuration

I have configured a joypad but MedGui Reborn doesn't save my joypad configuration on close and also there is no save button and no menu.
How am I supposed to play the game with my joypad configuration?

I have configured a joypad but MedGui Reborn doesn't save my joypad configuration on close and also there is no save button and no menu.
How am I supposed to play the game with my joypad configuration?

Can you explain what step are you following to setup the pad?
Anyway you can always configure the pad by mednafen itself.
Launch a game, press CTRL SHIFT 1 on the left of your keyboard, and follow the instruction on the bottom of emulated game.

I have configured a joypad but MedGui Reborn doesn't save my joypad configuration on close and also there is no save button and no menu.
How am I supposed to play the game with my joypad configuration?

Can you explain what step are you following to setup the pad?
Anyway you can always configure the pad by mednafen itself. Launch a game, press CTRL SHIFT 1 on the left of your keyboard, and follow the instruction on the bottom of emulated game.

Right click the game that I want to play to show a context menu.
In the context menu left click "Configure Joypad"
"MedPad - Mednafen Pad Configurator" window appears without a menu and save button.
In this window I can choose "DualShock" in the "Device" drop down list and map my keyboard to DualShock buttons.
After I finished doing this I want to save the new pad configuration that I just made but as I said earlier there is no save button and not even File->Save menu because there is no a menu at all in the "MedPad - Mednafen Pad Configurator" window.
So I close the "MedPad - Mednafen Pad Configurator" window by left clicking the red cross button on the top right corner, a button that every window has in Microsoft Windows operarting systems.
I expected that the configuration that I made will be automatically save on close but it doesn't. When I play the game, all binds and maps that I made are gone.

You need to select first your device on the upper list, if no one pad is detected, you need to check direct input checkbox.
If your pad is detected, you can test it by the cross on the right side of medpad.
After, you need to select every input on the list, and press the relative input\direction to assign.
When you finished, close medpad and the input will be saved.
I have posted in the past a video on YouTube:
https://www.youtube.com/watch?v=hdc1PLYw0ho

You need to select first your device on the upper list, if no one pad is detected, you need to check direct input checkbox. If your pad is detected, you can test it by the cross on the right side of medpad. After, you need to select every input on the list, and press the relative input\direction to assign. When you finished, close medpad and the input will be saved.
I have posted in the past a video on YouTube:
https://www.youtube.com/watch?v=hdc1PLYw0ho

Only the Mouse appears in the "Available Pad" list. I ticked the DInput checkbox but my keyboard still does not appear in the "Available Pad" list.
Why only the Mouse appears in the "Available Pad" list?

then you want to set keyboard input, not a joypad?
If you want to set the keyboard you do not need to press anythings.
Select by mouse every single input to assign on the left list and press the key to assign.
I have tested now the procedure and it work fine.
Remember that mednafen for psx use as default controller the traditional digital gamepad, if you want to use the dualshock pad you need also to set it as default controller, you can do it by medguir on advanced emu setting, on the relative gamepad section or by mednafen itself, launching a game and swapping the available input by pressing the combo CTRL SHIFT 1.
In the previous post i have wrongly write the combo to assign input, the correct is ALT SHIFT 1.

then you want to set keyboard input, not a joypad? If you want to set the keyboard you do not need to press anythings. Select by mouse every single input to assign on the left list and press the key to assign. I have tested now the procedure and it work fine. Remember that mednafen for psx use as default controller the traditional digital gamepad, if you want to use the dualshock pad you need also to set it as default controller, you can do it by medguir on advanced emu setting, on the relative gamepad section or by mednafen itself, launching a game and swapping the available input by pressing the combo CTRL SHIFT 1. In the previous post i have wrongly write the combo to assign input, the correct is ALT SHIFT 1.

So to the play the game with my keyboard am I must use ALT SHIFT 1 while the game is running if I understood you correctly?

if you want to set the pad by mednafen you need firstly to launch the game.
Example to set dualshock on psx:
Launch a psx game
Swap the controller type by pressing CTRL SHIFT 1 (follow the bottom screen instructions)
Set the input by pressing ALT SHIFT 1 (follow the bottom screen instructions)
Done
When you close (not force close) the emulator, your setting will be saved by emulator

if you want to set the pad by mednafen you need firstly to launch the game. Example to set dualshock on psx: Launch a psx game Swap the controller type by pressing CTRL SHIFT 1 (follow the bottom screen instructions) Set the input by pressing ALT SHIFT 1 (follow the bottom screen instructions)
Done
When you close (not force close) the emulator, your setting will be saved by emulator

So I need to use the Mednafen itself and not MedGui Reborn? I will try and let you know if this works for me or not. Now I have time to try this method.

You can use what do you prefer, personally i use mednafen because is more speedly to set the input.
Now i close the the issue because it's not related to a bug, if you need help, use the discord channell, is more user friendly.


Don't use global pg connexion

Codecov Report

Merging #44 into master will decrease coverage by 3.16%.
The diff coverage is 70.96%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage     100%   96.83%   -3.17%
==========================================
  Files           6        7       +1
  Lines         541      568      +27
==========================================
+ Hits          541      550       +9
- Misses          0       18      +18

Impacted Files
Coverage Δ

ldap2pg/role.py
100% <ø> (ø)
:arrow_up:

ldap2pg/utils.py
100% <100%> (ø)
:arrow_up:

ldap2pg/manager.py
100% <100%> (ø)
:arrow_up:

ldap2pg/script.py
100% <100%> (ø)
:arrow_up:

ldap2pg/psql.py
43.75% <43.75%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca38c30...a6fa75b. Read the comment docs.


Global options not visible on sub-commands?

Hey there Armin, hope you're doing well :smile:
In many cases (as per your Git example), there is a need for certain options to be available across the entire CLI application.
e.g.

Enabling or disabling colour
Verbose switch
Help

Using the exact Git example code provided, the options registered against the global group do not appear in the help of sub-commands.
e.g.  when running python git.py --help, we get:
Usage: git.py [OPTIONS] COMMAND [ARGS]...

Options:
  --repo-home REPO_HOME
  --debug / --no-debug
  --help                Show this message and exit.

Commands:
  clone

and now when running python git.py clone --help, the repo-home and debug options are no longer shown:
Usage: git.py clone [OPTIONS] SRC [DEST]

Options:
  --help  Show this message and exit.

Any ideas?
Thanks heaps
Fotis

I'd be interested in this as well. Whilst this might be the intentional default behaviour, is there a way to work around this, and inherit group options on child commands? Or is the only way to repeat options on every command?

I have the same problem with likely every CLI program I write with subcommands. As a user I want to have the freedom to place an option "anywhere" (where it logically makes sense) in the command line. Examples:

Flags such as --debug, --verbose, --silent for global behavior
A --host or --uri option to specify, which main resource to connect to
--username, --password, --token options, whose values are the same for all subcommands

For what I know, it seems that with Click I only have two choices:

Expect the user to use the option of the lowest group (e.g. cli --debug foo; invalid would be e.g. cli foo --debug)
Repeat those options on each group in the source code (e.g. to allow both cli --debug foo and cli foo --debug)

Other CLI frameworks, such as Go's Cobra, have "global flags" for that. Is there absolutely now way to do this with Click?
Can we reopen this issue and discuss possible solutions?

We do not plan to change this. A third solution is to write a Command class or decorator that populates a default set of options.

https://stackoverflow.com/questions/32493912/is-it-possible-to-add-a-global-argument-for-all-subcommands-in-click-based-inter SO example that might fit your use case @bittner

Thanks Jay! Unfortunately, the example on SO is a bit hard to grasp.
We should come of with a simple, easy-to-understand solution and add that to the Click documentation. That would already help.

An interesting, related discussion is https://github.com/pallets/click/issues/108#issuecomment-280489786. Includes some usable solutions.


⚠ AZ-Launcher has degraded performance

In 0d32dde, AZ-Launcher (https://az-launcher.nz/) experienced degraded performance:

HTTP code: 200
Response time: 2312 ms

Resolved: AZ-Launcher performance has improved in ec6a185 after 14 minutes.


Dart ffi segmentation fault in linux after linking gstreamer

I was trying GStreamer with c for Linux audio and integrating it through dart:ffi in Linux. but after linking with GStreamer libraries dart crashes with error given below
===== CRASH =====
si_signo=Segmentation fault(11), si_code=1, si_addr=0x18
version=2.8.4 (stable) (Wed Jun 3 12:26:04 2020 +0200) on "linux_x64"
pid=46998, thread=47001, isolate=main(0x559665492900)
isolate_instructions=559663d1d500, vm_instructions=559663d1d500
Stack dump aborted because InitialRegisterCheck failed.
[2]    46998 abort (core dumped)  dart main.dart

My native C code is simple containing only two functions one is main which calls "int init_and_play()"
int init_and_play() is doing nothing but printing "hello world" and returning 1
This setup works fine(prints hello world) when Gstreamer not linked but after linking Gstreamer through target_link_libraries it fails with the above message
My C code
#include <stdio.h>
#include "sound.h"

int init_and_play()
{
  printf("hello world\n");

  return 1;
}

int main(int argc, char *argv[])
{

  init_and_play();

  return 0;
} //END main

My CmakeLists.txt which causes the crash
cmake_minimum_required(VERSION 3.10 FATAL_ERROR)
project(soundlib VERSION 1.0.0 LANGUAGES C)
add_library(soundlib   SHARED  sound.c)
add_executable(sound  sound.c)
find_package(PkgConfig) #finding pkg-config is a helper tool

#using pkg-config to getting Gstreamer
pkg_check_modules(GSTREAMER REQUIRED gstreamer-1.0)

target_link_libraries(soundlib PUBLIC  ${GSTREAMER_LIBRARIES})
target_link_libraries(sound PUBLIC ${GSTREAMER_LIBRARIES})

include_directories(
        ${GLIB_INCLUDE_DIRS}
        ${GSTREAMER_INCLUDE_DIRS}
)

link_directories(
        ${GLIB_LIBRARY_DIRS}
        ${GSTREAMER_LIBRARY_DIRS}
)

set_target_properties(soundlib PROPERTIES
    PUBLIC_HEADER sound.h
    VERSION ${PROJECT_VERSION}
    SOVERSION 1
    OUTPUT_NAME "sound"
    XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "Hex_Identity_ID_Goes_Here"
)

CMakeFile.txt which does not cause the crash(notice the linking is commented)
cmake_minimum_required(VERSION 3.10 FATAL_ERROR)
project(soundlib VERSION 1.0.0 LANGUAGES C)
add_library(soundlib   SHARED  sound.c)
add_executable(sound  sound.c)
find_package(PkgConfig) #finding pkg-config is a helper tool

#using pkg-config to getting Gstreamer
pkg_check_modules(GSTREAMER REQUIRED gstreamer-1.0)

#target_link_libraries(soundlib PUBLIC  ${GSTREAMER_LIBRARIES})
#target_link_libraries(sound PUBLIC ${GSTREAMER_LIBRARIES})

include_directories(
        ${GLIB_INCLUDE_DIRS}
        ${GSTREAMER_INCLUDE_DIRS}
)

link_directories(
        ${GLIB_LIBRARY_DIRS}
        ${GSTREAMER_LIBRARY_DIRS}
)

set_target_properties(soundlib PROPERTIES
    PUBLIC_HEADER sound.h
    VERSION ${PROJECT_VERSION}
    SOVERSION 1
    OUTPUT_NAME "sound"
    XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "Hex_Identity_ID_Goes_Here"
)

My main.dart file for both cases
import 'dart:ffi' as ffi;
// import 'dart:io' show Platform;

// FFI signature of the hello_world C function
typedef sound_func = ffi.Int32 Function();
// Dart type definition for calling the C foreign function
typedef Sound = int Function();

main() {
  var path = "./libsound.so";

  final dylib = ffi.DynamicLibrary.open(path);
  final Sound sound = dylib
      .lookup<ffi.NativeFunction<sound_func>>("init_and_play")
      .asFunction();
  // Call the function
  sound();
}

Since the only different thing, I am doing is linking GStreamer, so how to do it properly? Or is it purely a dart issue?

It was a strange c compiler issue, nothing to do with dart .


Release <IP_ADDRESS>

OpenSearch 1.3.13 has been released, see release notes.
Official OpenSearch release ticket: https://github.com/opensearch-project/opensearch-build/issues/3878
Checklist:

[x] Compatibility Matrix is updated (https://github.com/Aiven-Open/prometheus-exporter-plugin-for-opensearch/pull/228)
[x] Release <IP_ADDRESS> tag is present in the repo
[x] Release artifacts are available and downloadable
[x] Release notes published
[x] Forum announcement published

Forum announcement: https://forum.opensearch.org/t/prometheus-exporter-plugins-2-10-0-0-and-1-3-13-0-released/16072


turn shapefiles into geojson in browser

using https://github.com/calvinmetcalf/shapefile-js

:+1:

Should probably just use https://github.com/mapbox/leaflet-omnivore to cover all of our bases quickly

:+1:
Very few of my users have ever heard of geojson. Shapefiles are well-known though.

Yah, I think it's unlikely that people will have geoJson files lying around for them to edit. I'll make sure this becomes a priority during our sprint next week!

Cool. Looking forward to meeting you at the Spring Fling.

Likewise! :dancer:

Pssssssst: https://github.com/daguar/shapefile-to-webmap /cc @daguar

Oh snaps I should read comments before I post them... sorry to be repetitive :fearful:

Unless I'm missing something, leaflet-omnivore doesn't appear to handle shapefiles. Perhaps leaflet-shapefile would work.

@npeihl you are correct. I think the shapefile piece will have to be different but including omnivore is going to be part of the same process.
@aaronr what was your work-around for using modules without require()? Would it be worth adding browserify #8 so we can get these issues out of the way?

Thanks to @jczaplew for knocking this one out!


Cannot open Yaagl launcher

Describe the bug
When I try to open the launcher, it doesn't open and prints {"isTrusted":true} after a while.
Screenshots

System Information (please complete the following information):

macOS: Sonoma 14.6.1 (It started before updating MacOS)
Device: Macbook Air 13 inch 2020
CPU: Apple M1
RAM: 8G

are you using the latest version of yaagl? uninstall it completely and try again.

Same here, yesterday was working fine
macOS: sonoma 14.5
Device: macbook pro 14, 2021
CPU: m1
RAM: 16

I DONE these thing already what to do now

I can't open the game launcher what to do??


Verify a password against a SCRAM-SHA-256 hash

Hello,
I once had postgrest running with "SQL user management" as described in https://postgrest.org/en/stable/auth.html#sql-user-management .
In the MD5 hashing days I even went one step further, not having a password hash in the described basic_auth.users table, but I used the MD5 password hash rolpassword from the pg_catalog.pg_authid table. I thought this is a nice idea, having the same password for plain database connections and the postgrest API.
Now MD5 is considered as too insecure, and SCRAM-SHA-256 is standard in the pg_catalog.pg_authid table. How can I acheive my goal with SCRAM?
This means in particular, how can I verify a plaintext password against a SCRAM-SHA-256 password hash stored in pg_catalog.pg_authid.rolpassword, using the pgcrypto extension?

If you are interested to add that into the docs, please let me know.

@fjf2002 That would be great! Please go ahead.

Gladly I will try that. Before that, some questions:

Shall I edit/replace parts of the chapter "Storing users and passwords", or present a new chapter, as an alternative to the other chapter?
If the latter shall happen: Should a chapter be added there or in the "how-to" section?
The whole section depends on the idea of the email address being used in the authentication and the JWT. My whole issue is re-using the user's database password for postgrest authentication, which somehow would sound saner in conjunction with the sql user name (instead of the mail address) - what do you think?

Hmm, at first I was thinking we could have it as a tabbed snippet like we do for HTTP/CURL snippets on https://postgrest.org/en/stable/api.html.
But as you mention, since it differs from the "Storing users and passwords" I think it would be better as a new "how-to".

Solved on https://github.com/PostgREST/postgrest-docs/pull/581


Remove of parent resource fails if child resource is not deleted first

Description
Remove of parent resource fails if child resource is not deleted first
Steps to reproduce

Deploy a resource containing child resources. Tried with compute/gallery -> gallery/images
Run workflow with removal

Screenshots
[CannotDeleteResource : Can not delete resource before nested resources are deleted.]
See https://github.com/Azure/ResourceModules/runs/4137742516?check_suite_focus=true example

Duplicate


Two compatiable problem to fix

fix tilelayer loading problem on Leaflet.loading

The version of Leaflet.loading  in package.json was 0.1.18, which is not compatiable to leaflet.js rc1. I changed the version to 0.1.22, which is suitable to the new version leaflet.

fix test/index.html 'leaflet.label-src.js'=>'leaflet.label.js'

In the test/index.html, 'leaflet.label-src.js' is not existed, which can be replaced by 'leaflet.label.js'

Update Leaflet.loading version to v0.1.22 to be compatiable with Leaflet 1.0-rc2

Thanks! :)


PRISMA_QUERY_ENGINE_BINARY being ignored

I'm compiling my own binaries via Dockerfile, and setting the binaries on a custom path of /prisma-engine/binaries/<binary_name>.
However, when I run prisma lift or prisma generate commands, I get a node ENOENT error because it's trying to spawn the binary from /usr/local/lib/node_modules instead of the path I've provided to the explicit binary.
Just to be sure it wasn't a naming problem (see comment https://github.com/prisma/prisma2/issues/938#issuecomment-554780269), i named the binary with the same resolved name for my native platform.
$ echo $PRISMA_QUERY_ENGINE_BINARY
/prisma-engine/binaries/query-engine-linux-glibc-libssl1.1.0
$ prisma lift up --preview
Error: Get config Error: Command failed with exit code 2 (ENOENT): /usr/local/lib/node_modules/prisma2/query-engine-linux-glibc-libssl1.1.0 clie --get_config /tmp/d02f6653-7b90-478f-9cf4-98ce4d8b3ba8
spawn /usr/local/lib/node_modules/prisma2/query-engine-linux-glibc-libssl1.1.0 ENOENT

I also tried a build where I set a completely nonexistent path to the PRISMA_QUERY_ENGINE_BINARY and it did not throw the error for unkown platform that I believe is what you're expecting (error expected below)
https://github.com/prisma/photonjs/blob/5cb55281e0b4c41033ccce845c3aca1f09f86c1b/packages/engine-core/src/NodeEngine.ts#L105

Hi,
You will need to set the binary path in the platforms section in the schema as documented here: https://github.com/prisma/prisma2/blob/master/docs/prisma-schema-file.md#generators-optional
Can you please make sure that you have done that?

yes, I have done that, and it is still ignored entirely.

Running prisma2 generate with a non-existent path should throw as per the binaries spec, if that is not the case, then it is a bug.

I can confirm this as a bug now


Weird result returned

Weird result returned, only first record has the right display, and the other has the translations data
{
"status": "success",
"message": "success",
"data": {
"history": {
"total": 4,
"per_page": 10,
"page": 1,
"items": [
{
"id": 14,
"user_id": 2,
"transaction_id": 27,
"transaction_type_id": 1,
"net_proceeds_history_id": 2,
"value": 1.5,
"expiry_date": "2017-06-21 14:32:44",
"net_proceed_rate": 0.15,
"expired": 0,
"created_at": "2017-06-21 12:33:35",
"updated_at": "2017-06-21 14:32:44",
"transaction_type": {
"id": 1,
"code": "egood",
"show_in_filter": 1,
"with_net_proceed_rate": 1,
"title": "Egood"
}
},
{
"id": 46,
"user_id": 2,
"transaction_id": 70,
"transaction_type_id": 2,
"net_proceeds_history_id": null,
"value": 0.0015,
"expiry_date": "2017-06-29 17:26:08",
"net_proceed_rate": 0.15,
"expired": 0,
"created_at": "2017-06-29 17:26:08",
"updated_at": "2017-06-29 17:26:08",
"transaction_type": {
"id": 2,
"code": "cash_in",
"show_in_filter": 1,
"with_net_proceed_rate": 1,
"translations": [
{
"transaction_type_id": 2,
"locale": "en",
"title": "CashIn"
}
],
"title": "CashIn"
}
}
],
"last_page": 1,
"has_more": false
},
"balance": 1515.015
}
}

Hello, please provide enough information about the issue, otherwise nobody will be able to help you.

This is just the translations relationship. I would suggest to make it hidden makeHidden https://laravel.com/docs/5.6/eloquent-serialization#hiding-attributes-from-json - this will solve all your problems cause the title itself is also present.


Running from CLI?

So how do you run these from the CLI?

Any progress on this @ahalls? I've been looking into running XCTests from the CLI, but I haven't made much progress.

Swift 2.0 was just announced at WWDC and Xcode 7 around the corner. We should probably put this on hold until they go gold.

Im going to close this for now. We can revisit this when swift is stable in Linux.

In swift 2.2 we now have the option to use the pure swift implementation of swift.  https://github.com/apple/swift-corelibs-xctest
Some limitations: https://github.com/apple/swift-corelibs-xctest#additional-considerations-for-swift-on-linux
We need to manual add all the test to
    var allTests : [(String, () -> Void)] {}
We can handle this with a script
https://gist.github.com/briancroom/e2c22f162f8ba5211e31
Then all we would need to do is to call this with all the Test classes.
```XCTMain([BobTest(), Problem3Test(), ETCTest()])``
Live example with 2.2:
http://swiftlang.ng.bluemix.net/#/repl/b0d680996ae5506a06be941e7b1e642665ee35e51b0c216cb6d6f13957e18e41

we now support linux. There is updated documentation to run from the command line.


[aws-c-s3] update to 0.5.2

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Thanks for the update!


Transaction fails

I have gone through the three step process and after hitting the "claim" button in the final step, my MEW wallet asks me to confirm the transaction. I accept, however the transaction keeps failing (even though I do have loaded up some ETH to pay the gas):
https://etherscan.io/tx/0x371c22d0cb600fcd770c2a7ceabb57672b174f3a31755499f8aa1cd842683d80
https://etherscan.io/tx/0x8c0b802f036821f8578b361f4d488dc00a04421931234f39bc707b7f5a64feaf
https://etherscan.io/tx/0x243ecdc50da30f524ab8ab29eb6fd6574a52bd72dec5616bb2cb87818352aa37
Is there anything you can see on those links for debugging?
I noticed that my transaction has a "To:" section while others that went through have a "Interactec With (To):" section instead.
Does it matter which wallet I use? should MEW usually work for this?

Hmm, tried again with MetaMask and there it went through.


Archive this repo

As tutum no longer is a thing, the company has been bought by docker long time ago.

ping @geemus


Rethinking external assets

Closes #1558

Tests pass locally using the correct branch of event model in requirements.txt.


feat: [agoric] handle vesting accounts created out of genesis time

Description
Closes: #315

handle MsgCreatePeriodicVestingAccount

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

@huichiaotsou Is this currently only used by agoric chain? It would be better if we merge those changes onto v2/cosmos/v0.44.x branch so we can update the rest of branches with this PR

@huichiaotsou Is this currently only used by agoric chain? It would be better if we merge those changes onto v2/cosmos/v0.44.x branch so we can update the rest of branches with this PR

Hi @MonikaCat I think agoric changed a lot the v0.44.x sdk version because in v0.44.0 there is no MsgCreatePeriodicVestingAccount, but only in v0.46.x...

Hi @huichiaotsou , we are using v0.44.2-alpha.agoric.1 agoric version of cosmos-sdk that currently doesn’t support MsgCreatePeriodicVestingAccount message type, so you only need to handle MsgCreateVestingAccount type atm

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2/chains/agoric/mainnet@d8e74c1). Click here to learn what that means.
The diff coverage is n/a.

@@                     Coverage Diff                     @@
##             v2/chains/agoric/mainnet     #318   +/-   ##
===========================================================
  Coverage                            ?   49.61%
===========================================================
  Files                               ?       20
  Lines                               ?     1949
  Branches                            ?        0
===========================================================
  Hits                                ?      967
  Misses                              ?      849
  Partials                            ?      133

I tested it on my local, it works but the start_time value is always null. Since BaseVestingAccount type doesn't contain  StartTime value, can you try to pass the timestamp of this tx instead?


blockchain-carbon-accounting

CO2 emissions accounting calculations using Hyperledger Fabric
Thanks @C0rWin for looking through it.

Or is @C0rWin Artem Barger?

Yes, I'm :)

Merging as requested changes have been done.

Thanks @lehors!  We wrote about it on the wiki:
https://wiki.hyperledger.org/display/CASIG/Carbon+Accounting+and+Certification+Working+Group
If you'd like we can add it to the lab proposal as well.

Si Chen
Open Source Strategies, Inc.
Video: Fighting Climate Change with Blockchain and Open Source
https://youtu.be/NgxNWXa_IjE
On Fri, Nov 13, 2020 at 12:49 PM Arnaud J Le Hors<EMAIL_ADDRESS>wrote:

@lehors approved this pull request.
I think it'd be good to explain the motivation for organizations to
participate in such a system - is that to fulfill some legal obligations?
because it will help improve their public image? something else?
This is however not a requirement for this proposal to get approved
though. I'm fine with it.
In labs/blockchain-carbon-accounting.md
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/156#discussion_r523217678
:

@@ -0,0 +1,32 @@
+---
+layout: default
+title: Lab Proposal Document

I believe this should be set to the lab's name instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/156#pullrequestreview-530404062,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANAS4OTPJQQHQN44CM6PVDSPWLTZANCNFSM4TROMVFQ
.


[Improvement] Check missing properties when type is copied

Hello, it's me again. I was curious how issue #108 should happen. Is there a way how to use typescript to check if all properties are used?
I was looking at operation-node-transformer.ts source code mainly. There is used class like this:
export interface CreateSchemaNode extends OperationNode {
  readonly kind: 'CreateSchemaNode'
  readonly schema: IdentifierNode
  readonly ifNotExists?: boolean
}

and OperationNodeTransformer has copy method like this:
protected transformCreateSchema(node: CreateSchemaNode): CreateSchemaNode {
    return {
      kind: 'CreateSchemaNode',
      schema: this.transformNode(node.schema),
      ifNotExists: node.ifNotExists,
    }
  }

if I remove ifNotExists: node.ifNotExists, line no typescript error occurs because ifNotExists property is optional. I was looking for some utility type like build in Required. Sadly Required is not compatible with original T type, in this case it requires node.ifNotExists not to be possibly undefined. Long story short, after all I found out this utility type:
type AllProps<T> =  T & { [P in keyof T]-?: unknown; };

Now when I use the AllProps type like this
protected transformCreateSchema(node: CreateSchemaNode): AllProps<CreateSchemaNode> {
    return {
      kind: 'CreateSchemaNode',
      schema: this.transformNode(node.schema),
      // ifNotExists: node.ifNotExists,
    }
  }

Typescript shows error Property 'ifNotExists' is missing in type '{ kind: "CreateSchemaNode"; schema: IdentifierNode; }' but required in type '{ readonly kind: unknown; readonly schema: unknown; readonly ifNotExists: unknown; }' now. It's not very accurate, because type of all properties is unknown. In case of ifNotExists is initialised with string, Typescript shows Type 'string' is not assignable to type 'boolean | undefined'. error. Which is good enough because Typescript shows missing property and wrong property type errors. The only problem is, it changes OperationNodeTransformer interface, transform methods return type is AllProps<...Node> instead of ...Node, even types are compatible.
I can add it to the library if you agree.

Great idea! Feel free to implement and I'll merge. Thanks for looking into this 👍
By the way, I added a TEST_TRANSFORMER=1 npm test run to CI. But that only catches the forgotten stuff if there's a test for the feature.

PR merged. Thank you 👍


add python3-rhel image

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python3-rhel:<IP_ADDRESS>441
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python3-rhel/tags
Get started by pulling the image:
docker pull devdemisto/python3-rhel:<IP_ADDRESS>441

Docker Metadata

Image Size: 153.08 MB

Image ID: sha256:a075b79fe41f2737e4da679db57bd44e5565fd709edbe9a64a7d2facb2313628

Created: 2022-11-15T10:25:06.008098297Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=devdemisto/python3-rhel:<IP_ADDRESS>441

Labels:

architecture:x86_64
build-date:2022-10-26T11:06:57
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:9a4aa4fb4fd52b101ee78606161401e63695c688
org.opencontainers.image.version:<IP_ADDRESS>441
release:990
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.6-990
vcs-ref:f1ee6e37554363ec55e0035aba1a693d3627fdeb
vcs-type:git
vendor:Red Hat, Inc.
version:8.6

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python3-rhel:<IP_ADDRESS>446
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python3-rhel/tags
Get started by pulling the image:
docker pull devdemisto/python3-rhel:<IP_ADDRESS>446

Docker Metadata

Image Size: 156.07 MB

Image ID: sha256:8aeff0cc4d29bfc799f53fa244ddbf6f023c00d78b31f686937dc733a1913664

Created: 2022-11-15T11:07:53.873354553Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=devdemisto/python3-rhel:<IP_ADDRESS>446

Labels:

architecture:x86_64
build-date:2022-10-26T11:06:57
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:cba829e756f3a53055c952298d695b607ac3482a
org.opencontainers.image.version:<IP_ADDRESS>446
release:990
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.6-990
vcs-ref:f1ee6e37554363ec55e0035aba1a693d3627fdeb
vcs-type:git
vendor:Red Hat, Inc.
version:8.6

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python3-rhel:<IP_ADDRESS>455
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python3-rhel/tags
Get started by pulling the image:
docker pull devdemisto/python3-rhel:<IP_ADDRESS>455

Docker Metadata

Image Size: 156.10 MB

Image ID: sha256:12061dc608f0a858df88a6c2755032810a0c3626aaa44bf0d61e8b148bca9c84

Created: 2022-11-15T13:39:09.060155158Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=devdemisto/python3-rhel:<IP_ADDRESS>455

Labels:

architecture:x86_64
build-date:2022-10-26T11:06:57
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:c1dbbcd1e785d2fe16d42bcd4886ff16702e00ab
org.opencontainers.image.version:<IP_ADDRESS>455
release:990
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.6-990
vcs-ref:f1ee6e37554363ec55e0035aba1a693d3627fdeb
vcs-type:git
vendor:Red Hat, Inc.
version:8.6

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python3-ubi:<IP_ADDRESS>476
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python3-ubi/tags
Get started by pulling the image:
docker pull devdemisto/python3-ubi:<IP_ADDRESS>476

Docker Metadata

Image Size: 156.10 MB

Image ID: sha256:adeede3e72cc3a7e1a0a21ba3fdebcd5cba30df0e4ec37a6c3877f14491a002b

Created: 2022-11-15T15:32:05.684884246Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=devdemisto/python3-ubi:<IP_ADDRESS>476

Labels:

architecture:x86_64
build-date:2022-10-26T11:06:57
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:9915a05a3dab50cabd9d086433c55e3df3e6f4c2
org.opencontainers.image.version:<IP_ADDRESS>476
release:990
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.6-990
vcs-ref:f1ee6e37554363ec55e0035aba1a693d3627fdeb
vcs-type:git
vendor:Red Hat, Inc.
version:8.6

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/python3-ubi:<IP_ADDRESS>604
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/python3-ubi/tags
Get started by pulling the image:
docker pull devdemisto/python3-ubi:<IP_ADDRESS>604

Docker Metadata

Image Size: 106.16 MB

Image ID: sha256:1e5a4cacb298bfe20ca1b7a30cd9cb3fe9e1e80fa7100adba6c52e9fcde987bd

Created: 2022-11-20T10:17:34.718371022Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=devdemisto/python3-ubi:<IP_ADDRESS>604

Labels:

architecture:x86_64
build-date:2022-11-01T04:29:09
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:59f27ddbc2e5a358be445190b6cc6c995448f720
org.opencontainers.image.version:<IP_ADDRESS>604
release:929
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.7-929
vcs-ref:a995512a05037e3b60bbb1bf9fa6e394063131c3
vcs-type:git
vendor:Red Hat, Inc.
version:8.7

Docker Image Ready - Production
Docker automatic build at CircleCI has deployed your docker image: demisto/python3-ubi:<IP_ADDRESS>616
It is available now on docker hub at: https://hub.docker.com/r/demisto/python3-ubi/tags
Get started by pulling the image:
docker pull demisto/python3-ubi:<IP_ADDRESS>616

Docker Metadata

Image Size: 106.15 MB

Image ID: sha256:acb92b545102145433d375cd91bdad46f082c2a3bfd4b818375bd3d31c389fbc

Created: 2022-11-21T09:09:03.060090746Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/home/python/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
container=oci
DOCKER_IMAGE=demisto/python3-ubi:<IP_ADDRESS>616

Labels:

architecture:x86_64
build-date:2022-11-01T04:29:09
com.redhat.component:ubi8-container
com.redhat.license_terms:https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI
description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
distribution-scope:public
io.buildah.version:1.26.2
io.k8s.description:The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
io.k8s.display-name:Red Hat Universal Base Image 8
io.openshift.expose-services:
io.openshift.tags:base rhel8
maintainer:Red Hat, Inc.
name:ubi8
org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:e4013319acc613984ad8e9dc58d7de499fbcd631
org.opencontainers.image.version:<IP_ADDRESS>616
release:929
summary:Provides the latest release of Red Hat Universal Base Image 8.
url:https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/images/8.7-929
vcs-ref:a995512a05037e3b60bbb1bf9fa6e394063131c3
vcs-type:git
vendor:Red Hat, Inc.
version:8.7


Add service tree link when onboarding a product

When a team is onboarding, we should provide a link to the Service Tree instance so the user can verify which product they really want to onboard.
This is important when there are products with the same name but different type (offering vs sku).
An idea is to add the link like we do when creating a release plan:

Open to more ideas too :)

Updated the display name to show product type


Enable Portable format in Roaring64NavigableMap

SUMMARY

Implement the portable format as coded in CRoaring (https://github.com/RoaringBitmap/CRoaring/blob/master/cpp/roaring64map.hh#L991) (and Go ? (https://github.com/RoaringBitmap/roaring/tree/master/roaring64))
Unit-tests has been introduced, based on binary files existing in CRoaring repository

Automated Checks

[ ] I have run ./gradlew test and made sure that my PR does not break any unit test.
[ ] I have run ./gradlew checkstyleMain or the equivalent and corrected the formatting warnings reported.

org.roaringbitmap.longlong.Roaring64NavigableMap#SERIALIZATION_MODE is a static field enabling switching to portable mode by default.
One can migrate from legacy to portable by relying onRoaring64NavigableMap.deserializeLegacy() and Roaring64NavigableMap.serializeFuture()
I wonder if it would be useful/relevant to introduce a per/instance flag (e.g. in ctor or by setter, as suggested in https://github.com/RoaringBitmap/RoaringBitmap/pull/572/files#diff-5bb999cb0772cc6137e43d9fcd3218478da513af25783a038bd268950f0dea29R1463)

This would superseed https://github.com/RoaringBitmap/RoaringBitmap/pull/572

I may work into Roaring64Bitmap to Serialize in the portable format, but it is less trivial.

Looks like a very good initiative. I would favour merging this PR (or an extension of it) once people have had a chance of discussing it.
Someone ought to document the format independently at https://github.com/RoaringBitmap/RoaringFormatSpec

Someone ought to document the format independently at https://github.com/RoaringBitmap/RoaringFormatSpec

Let me make a draft proposal, but it is an exercise I'm less comfortable with.

Let me make a draft proposal, but it is an exercise I'm less comfortable with.

It was a request that you do it, but I think that we should be collectively concerned that there is not specification. There isn't even a bad specification.

Let me stress: "It was NOT a request that you do it"

Don't worry @lemire. I have more freetime and more energy than usual, hence I'm happy to contribute.

https://github.com/RoaringBitmap/RoaringFormatSpec/pull/12

[...] I think that we should be collectively concerned that there is not specification. There isn't even a bad specification..
I concur. It would be lovely if someone attacked this. My only concern is that a spec that generalises over the different implementations (ART vs Map) could end being highly inefficient for one or the other. But such is the nature of a "portable" format, I suppose.

My only concern is that a spec that generalises over the different implementations (ART vs Map) could end being highly inefficient for one or the other. But such is the nature of a "portable" format, I suppose.

By portable, I referred to the wording in the CRoaring implementation. Go implementation made the effort to be compatible with it: https://github.com/RoaringBitmap/roaring/blob/master/roaring64/roaring64.go#L84 . With this PR, it will be possible to reach compatibility through the Java implementation. Hence, I referred in the draft of the spec to a de-facto standard.
The C implementation has another serialization format (a.k.a the not-portable format). I did not looked at the details (as I did not expect natural compatibility with our ART implementation), but there is any room for various concurrent formats (if needed).
Also, if ART implementation would target The layout is designed so that random access to the data is possible without materializing the bitmap in memory while being storage efficient., I feel it could not be reachable through a format also naturally compatible for Map-based implementation (which may achieve (degraded ?) random access with the (so-called) portable format).

In CRoaring, there is another 32-bit format because people were concerned that you could sometimes have a more concise serialization if you just outputted a list of 32-bit values. So we allow it, but with the indication that it is not supported by Java/Go, etc.
There is also yet another format called 'frozen' that is supported by C and Go, and it is used for memory-file mapping. It is basically just the same format, but with padding so we align the words (to prevent undefined behaviour in C/C++). We don't need it in Java.

Just FYI: We also got our own 64-bit serialisation format in Delta: https://docs.google.com/document/d/1lv35ZPfioopBbzQ7zT82LOev7qV7x4YNLkMr2-L5E_M/edit#heading=h.yvlcj9hgj4tr
It's fairly similar to what @blacelle proposed in the spec doc, so that's nice :)

@blacelle Please add a reference to the specification : https://github.com/RoaringBitmap/RoaringFormatSpec#extention-for-64-bit-implementations

Done

I think we will be able to merge this. Great work.

@panda0120 Could you review this PR? It seems that it fixes a problem you were having?

I don't have any "skin in the game" in the 64 bit implementations so please don't wait for my review.

Fine @richardstartin . I understood you had specific interests in the default 64-bit serialization remaining constant.

I think as a general principle it's important not to make backward incompatible changes to formats of data structures users may have persisted.

I think as a general principle it's important not to make backward incompatible changes to formats of data structures users may have persisted.

I agree. Currently, I don't think we are breaking anything.
Still, it makes sense to migrate to the format used by C and Go given that we never had a format specification.
One solution might be to make it so that the deserialization routine is robust: we switch to the portable format for everyone, but when the deserialization routine recognizes the legacy format, it automagically switches to it for the duration of this deserialization. This might be possible (e.g., since the portable format will start with a sequence of 4 bytes, two of which are zero). Of course, this smart  behaviour could be disabled.

Given https://github.com/RoaringBitmap/RoaringBitmap/issues/351, @richardstartin I thought you would have more interests in this.

This might be possible (e.g., since the portable format will start with a sequence of 4 bytes, two of which are zero).

The legacy Roaring64NavigableMap serialization format starts with a boolean and an int: it also starts with 4 zero bytes if signedLongs is true (which is uncommon usage) and the number of buckets is lower than 0x000000FF = 255. We may also look ahead the consistency of first buckets to detect portable or legacy format.

The legacy Roaring64NavigableMap serialization format starts with a boolean and an int: it also starts with 4 zero bytes if signedLongs is true (which is uncommon usage) and the number of buckets is lower than 0x000000FF = 255. We may also look ahead the consistency of first buckets to detect portable or legacy format.

So maybe it makes sense to have a small 'format detection' routine. In fact, we could expose it right away. It is a reasonable concern for programmers: I have this data, what is the format it uses?

Thinking about it more, this will break stuff in Apache Pinot where this class is used for id sets (cc @kishoreg). So ideally this should be kept backward compatible. Without having to trawl through the code to find out, do either the new or the old format have a cookie or a version at the start? That's a good practice precisely because people generally end up wanting to evolve serialisation formats at some point, such as now. If these are present they can be used to maintain backward compatibility.

@richardstartin @blacelle
My current thought is that we should provide a best-effort format detection routine. However, we should not switch the format to portable... We should leave the programmers in control and not break things.
People who need portability (to C, to Go) will know what to do. People who don't need it will just be upset that we broke their systems.

Yes. A cookie is generally a good idea, but it is maybe too late to introduce it as a compulsory component. We could make it optional, however.

My current thought is that we should provide a best-effort format detection routine. However, we should not switch the format to portable... We should leave the programmers in control and not break things.

So maybe it makes sense to have a small 'format detection' routine. In fact, we could expose it right away. It is a reasonable concern for programmers: I have this data, what is the format it uses?

I advocate moving forward with this PR as it is backward compatible. I may work earlier or later on such a simple detection mechanism, but iI would need more thoughts to propose something with a good ROI.

People who need portability (to C, to Go) will know what to do. People who don't need it will just be upset that we broke their systems.

This PR keeps by default the current behavior. I understand we all agree on this, isn't it?

Yes. A cookie is generally a good idea, but it is maybe too late to introduce it as a compulsory component. We could make it optional, however.

It is not too late to introduce in a new format. Again, what I did here is to align Java with C++ ang Go. If we introduce such a Cookie i nthe first 4 bytes, C++ and Go would need to handle it specifically (as, with current/historical implementations, it would lead to weird behaviors).
A new future-proof format will need more considerations (memory-mapping ? Cookies ? Versioning ? etc), but it is out of the scope of this PR (which, again, implements the portable format, as defined de facto by C++ and Go).

@blacelle Yes. I agree. Can you just remove the following...

// RoaringBitmap 1.X shall switch to the portable format by default

This is not a firm decision.
If you want to keep the comment, what about something like "RoaringBitmap 1.X may switch to the portable format by default".
Otherwise, I agree, we should merge. You worked hard and it is great code.

Definitely.

Merging.

@panda0120 Could you review this PR? It seems that it fixes a problem you were having?

I am sorry that i can't finish my PR.#598 it fix my problem too.


Fix event hub auto config condition

Codecov Report

Merging #242 into master will decrease coverage by 0.25%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #242      +/-   ##
============================================
- Coverage     55.79%   55.53%   -0.26%
+ Complexity      267      265       -2
============================================
  Files            86       86
  Lines          1156     1156
  Branches         62       62
============================================
- Hits            645      642       -3
- Misses          477      480       +3
  Partials         34       34

Impacted Files
Coverage Δ
Complexity Δ

...eam/binder/config/EventHubBinderConfiguration.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../eventhub/AzureEventHubKafkaAutoConfiguration.java
0% <ø> (-18.75%)
0 <0> (-2)

...igure/eventhub/AzureEventHubAutoConfiguration.java
57.14% <0%> (ø)
3 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 463225b...bb37a9d. Read the comment docs.


Register Hanzi.jl

@JuliaRegistrator register()

Error while trying to register: "Pre-release version not allowed"

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/103604
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" d7c67a39b05546d91ce81154a5a2b124d5d43b3c
git push origin v1.0.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/103604
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 30ea7b176df9f834133eccecf276bef3150a1993
git push origin v1.0.0


Protractor - log type 'performance' not found error

webdriver-manager 12.1.5
protractor Version 5.4.2
Chrome version 75.0.3770.100
browser.manage().logs().get('performance');
This used to work fine before upgrading my webdriver-manager and protractor version.
(node:27715) UnhandledPromiseRejectionWarning: WebDriverError: invalid argument: log type 'performance' not found
 (Session info: chrome=75.0.3770.100)
 Build info: version: '3.141.59', revision: 'e82be7d358', time:    '2018-11-14T08:25:53'
System info:, os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.14.4', java.version: '1.8.0_191'
 Driver info: driver.version: unknown
at Object.checkLegacyResponse (node_modules/selenium-webdriver/lib/error.js:546:15)

If I comment the browser.manage().logs().get('performance'); and other performance related code, then the test runs fine.
webdriver-manager logs show:
Starting ChromeDriver 75.0.3770.90  on port 12268

This stack overflow thread has a work around for webdriver with java. Is there a way to recreate the same functionality for Protractor?

Could really use some help with this issue. Thank you.

Hi @sumxyz , the same capability works for chrome 74, it doesn't work with 75. It seems like an -issue not really an wwebdriver-manager issue.
For workaround you can uninstall<EMAIL_ADDRESS>and use<EMAIL_ADDRESS>to make your existing script to work.
Thanks.

@Harsha509 In that stack overflow thread I posted the poster suggests the change was made in chromedriver to comply with the w3c standards more strictly. If that is the case this is unlikely to change back so shouldn't this new functionality be handled  by Protractor?

@DublinDev , i have seen the post just now, thanks a lot for your research. Yes it should be handled by protractor and a user working with<EMAIL_ADDRESS>should install<EMAIL_ADDRESS>instead of 12.1.5.
It might work with<EMAIL_ADDRESS>as it has selenium4-alpha, which follows w3c protocol. For now, yes it is an issue for people working with<EMAIL_ADDRESS>and chrome version 75.

Hi - I am using chrome 76 and chromedriver 77, so your milage may vary, but adding the w3c flag (to false) in capabilities is required to access the performance log type.
Those log types are hidden behind that flag due to w3c compliance issues. It likely is the case in the slightly older driver version you are using.
capabilities: {
browserName: 'chrome',
loggingPrefs: {
browser: 'ALL',
driver: 'ALL',
performance: 'ALL',
},
'goog:chromeOptions': {
args: ['disable-infobars'],
perfLoggingPrefs: {
enableNetwork: true,
},
w3c: false,
},
elementScrollBehavior: 1,
};

@JosephBittman that seems to solve the issue for me anyway! thanks.
Also @Harsha509 I didn't actually mean to imply that that was my answer or research, I just found the thread on stackoverflow.

thank you<EMAIL_ADDRESS>with<EMAIL_ADDRESS>instead of 12.1.5. helped!

@JosephBittman  Hi - I am using chrome 79 ,how to reslove the problem!!! selenium.common.exceptions.InvalidArgumentException: Message: invalid argument: log type 'performance' not found


Paginate nested elements

Hi,
I am trying to paginate over items which have been purchased through a certain time period. My goal is to display the items annotated by the date they have been purchased.
Here is my code snippet,

JSON data source:
{
"28-06-2016":[{itemId: "11", itemName: "item_11"},{itemId: "22", itemName: "item_22"}],
"22-06-2016":[{itemId: "101", itemName: "item_101"},{itemId: "202", itemName: "item_202"},{itemId: "303", itemName: "item_303"}],
"20-06-2016":[{itemId: "1001", itemName: "item_1001"}]
}

However, I end up seeing just the list of dates and the following error on console, "the itemsPerPage id argument does not match a registered pagination-id".
Any help with this?

Hi,
Since you will be using multiple pagination instances on a single page, you'll need to explicitly set the pagination-id to some unique value for each instance. This could be as simple as something like:

You would then have to use the same pagination id on the corresponding controls.


ssh breaks when ctest is run

I have successfully built MIOpen-rocm-5.6.0 from source code.
I use ssh to connect to the remote developer, but whenever I run make check, the ssh connection breaks. I have no idea what the reason is.
Can someone help me solve this problem?If there is any information I need to provide, please let me know.

@JiaJiDuan could you please provide a reproduce procedure? If the remote node offline when you try to run "check" since it will run all unit tests? Or it could be the high CPU/GPU utilization is causing ssh connection to break? Hard to tell from others' side without a minimal reproducible example.

Sorry, I think this may be a system driven issue, not related to miopen, I will close this issue first.
If a new problem is encountered, I will describe the phenomenon in more detail and open a new issue.


Assertion sometimes fails at BOOST_ASSERT(! state.timeout)?

I have an HTTPS server built off beast. At seemingly random times, an assertion inside timeout_handler (within basic_stream.hpp) that asserts that state.timeout is false fails, and kills my server. My program is basically the example HTTPS server with POST handling added, and I'm really not sure what the source of the issue is. I provided some code that may be related.
Does anybody have any idea how it would be possible for state.timeout to sometimes fail to be reset to "false"? Looking through the code the timeout appears to only be set directly after this assertion, and in two other areas within basic_stream.hpp. I cannot seem to find anybody else experiencing this error. Could it have something to do with using a do_close() function? Or could it have something to do with using a thread pool?
I have been struggling with this all day and would appreciate any input!
beast code where assertion fails:
template<class Protocol, class Executor, class RatePolicy>
struct basic_stream<Protocol, Executor, RatePolicy>::
    timeout_handler
{
    op_state& state;
    boost::weak_ptr<impl_type> wp;
    tick_type tick;

    void
    operator()(error_code ec)
    {
        // timer canceled
        if(ec == net::error::operation_aborted)
            return;
        BOOST_ASSERT(! ec);

        auto sp = wp.lock();

        // stream destroyed
        if(! sp)
            return;

        // stale timer
        if(tick < state.tick)
            return;
        BOOST_ASSERT(tick == state.tick);

        // timeout
        BOOST_ASSERT(! state.timeout); // <---- ASSERTION FAILS HERE
        sp->close();
        state.timeout = true;
    }
};

Some server code
Used in the async_write callback:
if (sp->need_eof())
{
	return session_ptr->do_close();
	session_ptr->res_ = nullptr;
} else {
	session_ptr->res_ = nullptr;
	session_ptr->do_read();
}

async_read's callback includes these lines:
if (ec == boost::beast::http::error::end_of_stream || ec == boost::asio::error::connection_reset)
	return do_close();

And do_close looks like:
void http_server_session::do_close()
{
	boost::system::error_code ec;
	socket_.shutdown(tcp::socket::shutdown_send, ec);
}

And my thread pool initialization looks like:
for (auto i = thread_count - 1; i > 0; --i) {
		threads.emplace_back([&io_context] {
		io_context.run();
	});
}

Version of Beast
I'm using Boost 1.70.0
All relevant compiler information
Microsoft Visual Studio 2017

Hi there @nosamproductions. Is there any chance you can put together a minimal complete compilable example that causes the problem to exhibit itself?
I'm thinking a minimal client and server that chats to itself until the problem is realised.
I appreciate that this will involve a little work, but it would definitively establish:

Whether there is a problem in beast
A means to reproduce the problem in a controlled environment.

Does the problem go away when you make your io_context single-threaded?

This morning the error has occurred less frequently, making it harder to compare single-threaded to multi-threaded. Perhaps the error occurs because of a race condition that exists somewhere? I'm thinking the error might be occurring less frequently now because my computer has been restarted and is a bit faster. I'm struggling to trigger it.
The most consistent way to trigger an assertion so far has been to place a breakpoint on the line with this assertion described in my original post, and randomly sometimes pressing "continue" in the error dialogue leads immediately to the assertion failing, though the assertion that fails is in a different thread and the assertion itself is on a different line of code further down in basic_stream.hpp:
if(state().timer.expiry() != never())
	{
	++state().tick;

	// try cancelling timer
	auto const n =
		state().timer.cancel();
	if(n == 0)
	{
		// timeout handler invoked?
		if(state().timeout)
		{
	// yes, socket already closed
	ec = beast::error::timeout;
	state().timeout = false;
		}
	}
	else
	{
		BOOST_ASSERT(n == 1);
		BOOST_ASSERT(! state().timeout); // <---- ASSERTION FAILS HERE
	}
}

I think I when I first made this post I wasn't aware that the assertion was two assertions in different places checking the same condition. The assertion I described in the initial post on this thread seems to be something that I cannot trigger but that occurs randomly on connection timeouts (but currently doesn't trigger at all, even though I haven't been changing code).
Two important pieces of information I forgot to add is that this error is occurring in an environment where the server is receiving a client request every second (the client is making heartbeat requests) AND after either of the two assertions fails, until I hit Retry/Abort/Ignore on the error popup, the server appears to continue handling the heartbeats just fine, receiving client requests and providing a response. It doesn't appear to break the server's ability to communicate, at least for a short period of time.

Does the problem go away when you make your io_context single-threaded?

No matter what I try, so far I cannot trigger any kind of assertion failure with a single-threaded io_context. I'm not sure how this code is designed to work so I don't know what protections/locks there are in place to prevent simultaneous access to variables, but I think this is may be some kind of threading related issue, I'm wondering: is a thread changing state.timeout to "true" before it is evaluated in an assertion in a different thread? Or am I somehow doing something on my end to trigger this strange behavior? I know for a fact I am not directly accessing the state.timeout variable in my own code.

I think this is may be some kind of threading related issue
Are you using a strand?

 I seem to recall not using those when first writing this a long time ago thinking they were unneeded. Woops.

I/O objects (such as sockets) are not thread safe. You must ensure that the same instance of an I/O object is not accessed concurrently. Explicit strands are one way to do that. Only using one thread with the io_context is another. There are more ways.

Ok, I will implement strands into my server and see how it goes, thank you very much! Definitely wont be repeating this mistake.

Issue resolved


org_slug is ignored

Module
n.a.
Describe the bug
OCA is used as org_slug even if a different one is set.
To Reproduce
Affected versions:
tags >= 1.16.0
Steps to reproduce the behavior:

copy or update copier template
launch pre-commit run -a

Expected behavior
org_slug is used as defined in .copier-answers.yml
Additional info
python version 3.8.16
pydantic==1.10.8 (for https://github.com/geekan/MetaGPT/issues/282)
copier<8.1.0

Do you have an example? What commands should I run to reproduce the problem?

Fixed by #210


serve.prod.exp is failing

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

When I am running npm run serve.prod.exp, the script seems to be failing.
Minimal reproduction of the problem with instructions

Clone the latest changes and run npm run serve.prod.exp
Please tell us about your environment:

Mac OS, webstrom

Node: node --version = v6.9.1

@zaksyed , hello, thanks for this bug submitting, actually I'm working on experimental buld, sof for now it's now working.

Issue resolved, per: https://github.com/vyakymenko/angular2-seed-express/pull/28


added apeel sciences

Checklist

[ x] I reviewed 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
[x ] I read and followed the CONTRIBUTING guidelines.
[ x] This pull request has a title in the format Add Company Name. Or Add Company1, Company2 and Company3 if it adds multiple companies.

:x: Update README.md
:x: Added Orbital Systems
:white_check_mark: Add Orbital Systems
:white_check_mark: Add Orbital Systems and Bulb

[ x] I added entries in alphabetical order.
[ x] The description is simple and doesn't contain unnecessary buzzwords. It needs to say what the company does, it's not a sales pitch.

:x: Disruptive company developing cutting-edge AI-enabled solutions to provide farmers with a decision support system.
:white_check_mark: They use satellites to help farmers monitor crops and lower their emissions by reducing their nitrogen usage.

Thanks for contributing!
I would make one stylistic change: avoid repeating the name of the company in the description, e.g. "They develop plant-derived..."


[FRONTEND] Setup axios instances

set Axios instances for API integration so that we don't have write the whole config everytime when calling the api

@chirag3003 Go ahead

Pls reassign this issue to me

Ok I have reassigned @chirag3003

@chirag3003 When will you PR?

@chirag3003 What's the progress?

I want to work on this issue under JWOC


review fc2 site usage patterns

In order to decide on sharding strategy and shard key (#260) need to know how users are actually using the new system to choose shard key based on typical usage patterns instead of just a guess at what the patterns will be.  Of particular interest is whether most searches are done by specific census years or by "all years" as all years was not even an option in FC1.
Needs #504
E1 U6 S8 C6: P21

Search stats are available


[Question] Is there any way of building xml with ... field?

Hi.
I'm using pydantic-xml to build xml files from json.
I faced a problem. I need to add a ... value and I tried to do it manually, simply using f-strings.
But after xml_model.to_xml() my < and > is being replaced by < and >
How can I avoid it?

@DLogunoff Hi
right now CDATA is not supported by the library since it is not supported by xml.etree library. I am going to add it for lxml backend only in the next version.

@DLogunoff  as a temporary solution you could use custom serializer:
>>> from pydantic_xml import BaseXmlModel, xml_field_serializer
>>> from pydantic_xml.element import XmlElementWriter
>>>
>>> from lxml.etree import CDATA
>>>
>>> class Content(BaseXmlModel, tag='content'):
...     text: str
...
...     @xml_field_serializer('text')
...     def serialize_text(self, element: XmlElementWriter, value: str, field_name: str) -> None:
...         element.set_text(CDATA(value))
...
>>> content = Content(text='')
>>>
>>> print(content.to_xml())
b'<content><![CDATA[]]></content>'


Downsampling Strategy

Hi,
Thank you for the amazing work! May I ask what is the sampling strategy used in the paper when depicting Figure 2 E&F, where only 300K cells are used to pre-train the model.
Thanks!

Hi, thanks for the question. We simply did a ransom subsampling for that experiment. For example, each cell from the whole 33M collection will have the same around 1/100 probability to be selected, and then this makes the 300K training examples.

Thanks for the reply! That makes sense to me.


Unexpected % movement with square brackets and +

Steps to reproduce

vim -u NONE -N
Insert the following content: '%[' + ']'
'[' + ']%'

Move the cursor over [ at 1,3.
Press %.  Unexpected: Notice that the cursor jumps to 2,8 instead of 1,9.
Remove + and one space from each line leaving:'%[' ']'
'[' ']%'

Move the cursor over [ at 1,3.
Press %.  Expected: Notice that the cursor jumps to 1,7, as expected, and not to 2,6.

Expected behaviour
The cursor would always jump between square brackets on the same line (as the matchparen highlighting suggests, if loaded, and as vim does without the -N option).
Version of Vim
8.2.4324 (and 7.0)
Environment
Reproduced with

cmd in ConHost on Windows 10.0.19043.1466 with %TERM% unset.
bash in xfce4-terminal 0.8.10 on Debian GNU/Linux testing with kernel 5.16 and $TERM=xterm-256color
bash in foot 1.10.3 on Debian GNU/Linux testing with kernel 5.16 and $TERM=xterm-256color

Logs and stack traces
No response

The builti-in behavior of % is a bit simplistic, it doesn't notice the % starts inside quotes.
To do this better use the matchit plugin:
packad matchit

Since this can be done with a plugin, I don't think the builtin functionality needs to be improved.

Thanks @brammool.  Could you explain a bit more why the quotes are
relevant to the observed behavior?  I'm curious why % jumps between
square brackets on different lines when + is present and between
different lines when + is removed (but matchparen always
highlights brackets on the same line).

It is not the plus that matters, it's that there is one character
between single quotes, and that is recognized like 'x' is.
As mentioned, this string detection is a bit primitive.  That's why the
plugin was added.
--
hundred-and-one symptoms of being an internet addict:
31. You code your homework in HTML and give your instructor the URL.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Add scamlink (discord-nitre.xyz)

By the way as a general note I don't always mention because I didn't want to get in the way:
Typically when we add new scams found recently we add them to scams.txt. The scamlinks.txt file is mainly just a bulk imported list from other data sources, rather than something maintained manually.

Will merge anyway because it isn't a big deal, just keep in mind for future small additions. Cheers

Oh, ok, thank you for the heads up, I'll keep this in mind. It makes sense since most spambots will use the same three words either way.


Fix Build.cmd to stop building when Examples compiling failed

Currently, the build process cannot be stopped if Examples solution has compiling failure. The fix is to stop building process if Examples failed.

LGTM

Current coverage is 82.30%

Merging #404 into master will not affect coverage as of 65915e4

@@            master   #404   diff @@
=====================================
  Files           45     45
  Stmts         4645   4645
  Branches       416    416
  Methods
=====================================
  Hit           3823   3823
  Partial        191    191
  Missed         631    631

Review entire Coverage Diff as of 65915e4

Powered by Codecov. Updated on successful CI builds.

@hebinhuang - can you also add this to build.sh? Looks like Travis CI does not fail when Examples.sln fails to build.

I will do it.


Add archive fields to pipeline item patch endpoint

Description of change
This PR allows the fields 'archive', 'archived_on' and 'archived_reason' to be change through the PATCH /v4/pipeline-item endpoint.
These fields were added in #2897
They were added to the result of the GET endpoint in #2908
Checklist

[x] If this is a releasable change, has a news fragment been added?

Explanation
A news fragment is required for any releasable change (i.e. code that runs in or affects production) so that a corresponding changelog entry is added when releasing.
Check changelog/README.md for instructions.

[x] Has this branch been rebased on top of the current develop branch?

Explanation
The branch should not be stale or have conflicts at the time reviews are requested.

[ ] Is the CircleCI build passing?

General points

Other things to check

Make sure fixtures/test_data.yaml is maintained when updating models
Consider the admin site when making changes to models
Use select-/prefetch-related field lists in views and search apps, and update them when fields are added
Make sure the README is updated e.g. when adding new environment variables

See docs/CONTRIBUTING.md for more guidelines.

Why do we want user to set the date when the object was archived? I think we have a pattern where for this purpose a POST <entity>/<entity_id>/archive is created through ArchivableViewSetMixin.

Why do we want the user to set the date when the object was archived? I think we have a pattern where for this purpose we use ArchivableViewSetMixin.

@elcct you're right. Discussing it with @sekharpanja tomorrow.


DSND-2488: Update CERT22 Description

Describe the changes
This PR changes the CERT22 descriptions in the transfrom rules.
Related Jira tickets
DSND-2488
Developer check list
General

[ ] Is the PR as small as it can be?
[ ] Has the Jira ticket been updated with any relevant comments?
[ ] Is the README up to date?
[ ] Has the POM been updated for the latest versions of dependencies?
[ ] Has the code been double-checked against main?
[ ] Does the code adhere standards in this repository, including SonarQube checks?

Testing

[ ] Do the code changes have unit and integration tests with code coverage > 80%?
[ ] Has the code been tested locally and/or passed the API Karate tests on Tilt?
[ ] Have mandatory manual test cases been run?
[ ] Are extra Karate tests required?
[ ] Are all the test data resources up to date?

Release preparation
Where possible, add links to the respective Jira tickets when an item is checked

[ ] Have these changes been included in a release ticket?
[ ] Are changes required to the docker-chs-development deployment or test data?
[ ] Are any changes required to the environment added to chs-configs?

Notes to the tester
Add any testing hints or instructions here.

CI: No security warnings found

CI: Security warnings found!

CI: Security warnings found!


moving to target-based cmake

Codecov Report
Base: 76.94% // Head: 76.65% // Decreases project coverage by -0.28% :warning:

Coverage data is based on head (56fd5ce) compared to base (35bec48).
Patch coverage: 82.65% of modified lines in pull request are covered.

:exclamation: Current head 56fd5ce differs from pull request most recent head 448f576. Consider uploading reports for the commit 448f576 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #224      +/-   ##
==========================================
- Coverage   76.94%   76.65%   -0.29%
==========================================
  Files         104      105       +1
  Lines        7620     7939     +319
==========================================
+ Hits         5863     6086     +223
- Misses       1757     1853      +96

Impacted Files
Coverage Δ

src/radiative_transfer/radiator_warehouse.F90
62.50% <38.88%> (-22.73%)
:arrow_down:

src/core.F90
72.43% <48.48%> (-6.85%)
:arrow_down:

src/radiative_transfer/solvers/delta_eddington.F90
93.08% <50.00%> (-3.57%)
:arrow_down:

src/profiles/extraterrestrial_flux.F90
87.05% <66.66%> (-0.55%)
:arrow_down:

src/cross_section_warehouse.F90
84.81% <70.37%> (-6.57%)
:arrow_down:

src/radiative_transfer/radiative_transfer.F90
76.81% <73.68%> (-4.15%)
:arrow_down:

src/spectral_weights/gaussian.F90
92.30% <75.00%> (+0.30%)
:arrow_up:

src/spectral_weights/notch_filter.F90
93.33% <75.00%> (+0.22%)
:arrow_up:

src/radiative_transfer/radiators/from_host.F90
75.80% <75.80%> (ø)

src/grid_warehouse.F90
85.83% <78.57%> (-1.30%)
:arrow_down:

... and 78 more

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

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


Email generated after changing user role shows enum

Once a user has joined an org, the role of the user can be changed. When the role is changed, the email generated lists the new role as the enum value.
to recreate the steps-

Click on 'Your organization'
Select an org
Scroll down to view the members in the org
Change the role of any member and click on 'Save'

The following emails are generated

The template variable values in https://github.com/pypi/warehouse/blob/637435d22451494c83a5c404c409211b25df7c13/warehouse/manage/views.py#L2022-L2037 need to be updated to role.role_name.value.
Resolving this should also include checking for this in other places where role.role_name or similar is called.

Related https://github.com/pypi/warehouse/issues/6636

Fixed by #12231.


Add route/query info to $fetchState

Is your feature request related to a problem? Please describe.
I have keep-alived page (/characters) which uses query based filters. If apply the filter - /characters?species=Alien, then go to main page and then back to /characters - filtered (cached) results shown, not all.
Example: https://codesandbox.io/s/morning-sun-zh98i?file=/pages/characters/index.vue
And that is the expected behavior 👍 . To fix that I save route query on the last fetch call and compare it with current route query in activated hook, if not the same - call $fetch() (you can see commented block in pages/characters/index.vue):
data() {
  return {
    lastQuery: {},
  }
},
activated() {
  if (JSON.stringify(this.$route.query) !== JSON.stringify(this.lastQuery))
    this.$fetch();
},
async fetch() {
  // ...
  this.lastQuery = this.$route.query
},
watch: {
  '$route.query'() {
    if (!this._inactive) this.$fetch()
  }
},

Describe the solution you'd like
Wouldn't it be a good idea to have route/query info (active on last $fetch() call) in $fetchState alongside current pending, error, timestamp fields?
activated() {
  if (JSON.stringify(this.$route.query) !== JSON.stringify(this.$fetchState.query))
    this.$fetch();
},

On the other hand it's also not good to keep in memory a lot of route data for every cached component.
Describe alternatives you've considered
The other workaround what I see to make caching properly work with query filters is using :key="$route.fullPath" or something, but it feels like not the best solution. Maybe there is a better solution than a custom "lastQuery"?

any updates?

We are approaching the Nuxt 2 EOL date (June 30, 2024) - see this article for more information. I'm closing this issue as it's marked as a Nuxt 2 related enhancement and it's not a critical issue.
That doesn't mean it might not be relevant for Nuxt 3. If it is, please feel free to open a new issue (or just comment, and I can reopen it). 🙏
Thank you for your understanding and for your contribution to Nuxt! 🎉


Add CI via Github workflow

Epic. Thank you, @tuxuser! I'm going to follow your lead on this since I've actually never used GH Actions before.
How hard would it be to add golangci-lint?