HTTP: WebSocket Binary Messages Checks

At the moment there is no way to add checks to WebSocket binary messages, the messages are ignored.

Is anyone working on this? I would be happy to do the work but I won't start if someone is already working on it.

@jbank Please go ahead, contributions welcome :)

Would be awesome to see support for binary messages as it would make testing for example Vertx and their websocket bridge much much easier!

I have implemented this based on how the ResponseBody is done. The only issue is I am not sure that web sockets are functioning since the upgrade to the latest AHC. Is anyone able to verify this for me?

I have done a bit more digging. Looks like the issue is the NettyWebSocket don't support using a LazyResponseBodyPartFactory as it tries to call getBodyPartBytes which is not supported by the LazyResponseBodyPart.
byte[] fragment = NettyResponseBodyPart.class.cast(part).getBodyPartBytes();
I tried to change the factory to the EagerResponseBodyPartFactory but gatling currently makes some assumptions that we are using the LazyResponseBodyPartFactory. Looks like we could change the code to call getBuf on the LazyResponseBodyPart.
As I am very new to the code base it is hard for me to know which direction you would recommend.

@jbank Thanks for reporting. I got this fixed in AHC, but I'm working on another issue atm. I'll push everything by the end of the week.

@slandelle Can you please provide an updated timeline for the AHC fix?

@jbank done

@slandelle I haven't had a lot of time to debug this but it looks like if the within times out the socket gets into a bad state and never recovers. Hopefully I will have more time to debug this by the end of the week but I just wanted to see if it was on your radar?

@jbank The AHC issue should be fixed in master. Did you give it a try?

Yea the AHC issue is fixed now. But when the websocket times out the websocket actor gets into a weird state.

@jbank There's a chance you're referring to #2601. No, I really don't have the cycles for this atm.

Yea looks like it. Ok I will have a crack at it. I just didn't want to duplicate work.

Great, thanks!

Hi, Is there any progress on this issue? Is there any way to check the binary message now?

@jbank has done some initial work in #2882, looking forward to the update.

@yuekang0629 I will see if I can get to this today. Otherwise it will be in the next few weeks. This isn't my main priority. I am just doing it in spare cycles.

Thanks @jbank !

Checking in to see if you made any progress on this @jbank.

I see https://github.com/gatling/gatling/pull/2882 was rejected and that there won't be any real support for bytes until gatling 3, which isn't exactly around the corner...
How about at least unblocking folks who need to do byte testing by mapping the byte array to a string? https://github.com/gatling/gatling/blob/master/gatling-http/src/main/scala/io/gatling/http/action/async/ws/WsActor.scala?utf8=✓#L176 would then just call OnTextMessage which takes care of the rest.

@fabienrenaud I understand how this would help for counting expected messages, but anything else is wrong:

equals is not a valid check method, it's the plain old equals one
binary payloads can't be arbitrarily converted to String (note you don't specify a Charset in the constructor, so you're using the default one for your JVM, hence platform dependent) as unmappable characters get replaced. People using binary frames do so because they use a binary encoding, typically protobuf, and you definitively expect to use the String bytes as the bytes -> String -> bytes would be destructive

In order to have the binary frames support move forward, we would need:

a user who's really involved and provides real world use cases, test cases, and feedback
time to implement

Ideally, this would be a sponsoring contract so we can dedicate some effort on this.

equals is not a valid check method, it's the plain old equals one
Yeah I just found that out. regex and jsonpath checks are a bit limited.

binary payloads can't be arbitrarily converted to String

Correct, unless the encoding of the binary payload to string is communicated and known by the tester. A binary payload converted to string could be matched against the expected binary payload converted with the same algorithm.
In my example, I just did a simple new String() on the byte array because i know i could match it exactly to the expected binary payload i would construct in a similar fashion in my scenario. Alternatively, the byte array could be base64 encoded and testers who'd like to use gatling with ws and bytes would know what to code against.
I tested this in the context of a protobuf app. It works and unblocks the usage of bytes in gatling2 for ws testing.
Again, I think this is better than just simply dropping messages on such an important feature and waiting 6-12 months for gatling 3 isn't an option for everyone.

@fabienrenaud I would have used your fork :)

closed as of 36ebc9416fe73605bbdb55845435a3e43df9c1b4


Using Xrm addCustomFilter with control

Thanks for your excellent work with this control! It's so much more flexible and functional than the alternatives. Any thoughts about how one would go about referring to the control from the Xrm client API? I know the actual values are placed in a secondary text field, but is there a way to refer to the control itself with Xrm? I am experimenting with it now and I'll be sure to update here if I find a solution. Thanks again!

Hi, What are you trying to achieve? You have the control on a field, so you can get the value of that field and you can perform anything you want.
What are you trying to show/get/achieve so I can help out a little bit more on this.

Sorry Victor for the low-information post! There seems to be an issue with the control where it fails on create form when used with a filter. I believe my issue is a duplicate of an existing issue about that. Thank you..


restore nami wallet after reset

by accident, I reset my nami wallet with several accounts. how can I restore it again?

Talk to Cardano Dev on the Live support page so that your issue can be looked into.

It's a scamm @gaadrana he's a scammer @Devjohn12


bug(database): confd log error

Using deis/database:v1.5.0 I see this error:
Apr 08 22:28:51 nodo-3 sh[13633]: 2015-04-08T22:28:51Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928281/298901368]) [298929280]
Apr 08 22:28:53 nodo-3 sh[13633]: 2015-04-08T22:28:53Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928362/298904039]) [298929361]
Apr 08 22:28:53 nodo-3 sh[13633]: 2015-04-08T22:28:53Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928362/298901368]) [298929361]
Apr 08 22:28:55 nodo-3 sh[13633]: 2015-04-08T22:28:55Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928451/298904039]) [298929450]
Apr 08 22:28:55 nodo-3 sh[13633]: 2015-04-08T22:28:55Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928451/298901368]) [298929450]
Apr 08 22:28:57 nodo-3 sh[13633]: 2015-04-08T22:28:57Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928547/298904039]) [298929546]
Apr 08 22:28:57 nodo-3 sh[13633]: 2015-04-08T22:28:57Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928547/298901368]) [298929546]
Apr 08 22:28:59 nodo-3 sh[13633]: 2015-04-08T22:28:59Z 55b2af686f67 confd[152]: ERROR 401: The event in requested index is outdated and cleared (the requested history has been cleared [298928631/298904039]) [298929630]

From the etcd (docs)[https://github.com/coreos/etcd/blob/master/Documentation/api.md] this could be a confd error using watch?

ping @bacongobbler

@alebdf this looks like https://github.com/kelseyhightower/confd/issues/205 which is resolved in https://github.com/kelseyhightower/confd/pull/254.

This should be fixed in the next release of confd v0.9.0.


Issue 549: Add objectStatus

This Pull Request resolves all requirements of Issue #549 .
Coordination

[x] Pull Request is against correct branch
[x] Pull Request is in, or reverted to, Draft status before Solutions Approval vote has passed
[x] CI passes in UCO feature branch against develop
[x] CI passes in UCO current unstable branch (71dab8f)
[x] CI passes in CASE current unstable branch tracking UCO's unstable as submodule (ae08b73)
[x] Impact on SHACL validation reviewed for CASE-Corpora
[x] Impact on SHACL validation remediated for CASE-Corpora (N/A)
[x] Impact on SHACL validation reviewed for CASE-Examples
[x] Impact on SHACL validation remediated for CASE-Examples (N/A)
[x] Impact on SHACL validation reviewed for casework.github.io
[x] Impact on SHACL validation remediated for casework.github.io (N/A)
[x] Milestone linked
[x] Solutions Approval vote logged on corresponding Issue (once logged, can be taken out of Draft PR status)

This PR is ready for review and merge.


Refuler Pylon throws error on adding materials

When attempting to fill either smelter or kiln the following error appears in the log
"[Warning: Unity Log] 05/14/2024 20:30:55: Failed to find rpc method 44531401"
LogOutput.log

Fixed in 4.10.1, thank you for your report


Revert "python3: don't patch out -Wl,-stack_size,1000000"

Description of changes
This reverts commit c7c3187d9897b304c85542130ece7bacc44906a9, which had the following comment:

The original motivation behind removing that was to appease a consumer
of python-config's output. That issue was probably resolved by now, so
let's bring the build in sync with what python is doing by default.

There is at least one package (kitty) that is failing to build as a result of this change (see #165387).
I don't know much about this area, so reverting this commit is my naive way or resolving the issue.
Closes #165387.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I don't think that this is a good way. The straightforward revert will break python310 again and move us away from what the vanilla python does. It would seem like the kitty just should not use this flag to link the shared libraries. Someone could check if Apple's python-config reports the -stack_size flag, and if some other python on macOS does that.

FWIW, python310 does build for me on aarch64-darwin with the commit reverted:
~/C/nixpkgs on revert-c7c3187
❯ nix run .#python310 -- --version
Python 3.10.3

I'll check on the config for python for various distributions on macOS now.

Version packaged with macOS:
❯ /usr/bin/python3 -c "import sysconfig; print(sysconfig.get_config_var('LINKFORSHARED'))"
-Wl,-stack_size,1000000  -framework CoreFoundation Python3.framework/Versions/3.8/Python3

Version installed by Homebrew:
❯ /opt/homebrew/bin/python3 -c "import sysconfig; print(sysconfig.get_config_var('LINKFORSHARED'))"
-Wl,-stack_size,1000000  -framework CoreFoundation<EMAIL_ADDRESS>
I was surprised by the latter since, I remember the maintainer of kitty saying folks should use Homebrew's Python to build kitty to get around the -stack_size issue.
I'll investigate a little more.

FWIW, python310 does build for me on aarch64-darwin with the commit reverted:
~/C/nixpkgs on revert-c7c3187
❯ nix run .#python310 -- --version
Python 3.10.3

I'll check on the config for python for various distributions on macOS now.

Okay, I misremembered, you need to also revert the 49a0059a59a950c9261325fad14a2f905f53036d to trigger the bug.


a little reorg :-p

Reorganized source code to consolidate copied functions and structures:

common stuff is now in train_common.c and train_common.h
cuda version needs to define TRAIN_CUDA before including the header or the .c file.
using the checkFopen(), mallocCheck() etc. functions in train_gpt2.c also.

It may be possible to consolidate the reading of the model a bit more by using ifdefs with the TRAIN_CUDA and TRAIN_CPU macros.
Enjoy.

So I want to do this, I'm just not sure when :)

I certainly don't want to go down the IFDEF switching hell.

Yes, it would be great if we can reduce / eliminate the use of #ifdef's in the source.

What's hell for some is just a cozy summer vacation to others ;-)

Question is, really, what is the future of this project - how far can it go and how complex can it really get. Maybe split it out when it gets to the 4th target, 3 targets/flavors in one file doesn't mess with the elegant simplicity too much, does it? And exceptions for compilers wouldn't have any reason to blow up, would it?
It is C after all...

Having most of a file covered in ifdefs sure messes with the elegant simplicity. Compiler quirks should be few, so its the targets that are the real concern, isn't it? But it is C after all, maybe the pragmatic approach would be to refactor/split things out to separate files if and when a 4th platform is added? 2 seems managable, 3 might even be. Four could become too much to keep track of. I am here to learn though.

Closing (has hard to fix merge conflicts now, new version with different approach is https://github.com/karpathy/llm.c/pull/177).


Deploy v4 to prod

Motivation
Deploy v4 to Prod 🎉
Changes

Changes CI to deploy to prod
Will deploy to prod on merge!

Testing Instructions
Hit Merge!

LGTM


The mobile phone can't be rotated in full screen

中文用户请注意：请尽量用英文描述你的 issue，这样能够让尽可能多的人帮到你。
Dplay:  1.23.0

The mobile phone is full screen and can not be displayed horizontally. Cannot rotate 90 degrees display

Same  in Android chrome.


Formalise Django 3.2 support

Django 3.2 has just been released!
Although Wagtail seems to support it (I've seen tests are run against Django master) it is excluded in setup.py ("Django>=2.2,<3.2").
It is an issue because the Poetry package manager cannot install packages declared as being incompatible (source). That means that people currently using Wagtail and Poetry (me for example :D) cannot upgrade to Django 3.2 (not easily at least).

hi, is it planned to include this in wagtail 2.11(.8) LTS?

@kelvan No, the LTS branch only receives stability / security fixes, and support for new Django versions wouldn't fall in that category.

@gasman thanks for the info


[Good First Issues]: Add description to feature flag API

Description
We use feature flags to manage features in any software. After creation a feature flag, it happens that we may forget the purpose and scope of the it, then a block of text to describe the flag could helpful. The present task is to add a description field to feature flag.
Scope
Tech stack:

dotnet

Service： API
Component： feature flags
Files to modify: modules\back-end\src\Api\Controllers\FeatureFlagController.cs : UpdateSettingAsync
How to implement

Fork the FeatBit repository.
Create a branch issues-{issues number}
Implement the task based on Description and Scope mentioned above.
Submit your PR

Contribution points
Each contribution counts a certain number of points, depending on its difficulty. Contributors earn the appropriate points when the work is merged. Contribution points are used to describe the contributions that contributors have made. They can also be used to receive rewards for community events. You can view the current community submissions on a public google sheet.
Points: 4
How to claim to solve the issue
If you want to implement this function, please leave a comment in this issue like:
| I'd like to implement this function, please assign this issue to me.
FeatBit community will assign the issue to you on time.

Hey I'd like to take the issue. Can you assign me?

Hey I'd like to take the issue. Can you assign me?

Hi, @DaveFz . Thanks for contacting us. When @cosmos-explorer is available, he will do the assignment and guide you on how to contribute.
While you wait for the assignment, you can join our Slack community. https://join.slack.com/t/featbit/shared_invite/zt-1ew5e2vbb-x6Apan1xZOaYMnFzqZkGNQ

Thank you @DaveFz, just assigned the issue to you. If you have any questions, please join our slack channel. We usually have two weeks for a typical good firsts issue, please let us know if you have any difficulty.

closed by #258


Feature Request: expose separate API interfaces for each cipher

Currently, we have a unified cipher interface (Cipher) that encapsulates all cryptography operations on each supported cipher. While the existing API interface is simple enough to use, the users have little control over details. For those applications that only use certain selected ciphers, the cost of cipher matching can be considered as overhead. Therefore, I would like to know if exposing cipher details as public interfaces is acceptable, and hopefully help to work on it.

Why not use the underlying crypto interfaces directly?

@zonyitoo Correct me if I am wrong, AFAIK the underlying crypto interfaces are not publicly visible.

I mean you can use thouse libraries directly.

Shadowsocks-specific ciphers and encryption schemes implemented in this repo may be useful in various scenarios. All we need is presumably just adding a couple of pub keywords.
@zonyitoo Before making final decisions, may I know the reason not to make underlying cipher implementations public?

Making these ciphers public means that we have to maintain the stable public APIs for those underlying ciphers, which will make it harder to switch the underlying ciphers' implementations.

Making these ciphers public means that we have to maintain the stable public APIs for those underlying ciphers, which will make it harder to switch the underlying ciphers' implementations.

Makes sense! So I will just close this issue in light of the consideration above.


Modified RAMI SAP image

I have update the image and moved the SAP CCLA pdf document into the doc folder.

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


Fix conditional attribute comparison with Float

Currently node greater/less than comparison compares only integers and this PR changes this to work with both integers and Floats like jmespath.js does.

The file is outdated, but when I looked the master, then I still think the code does not work with Floats, as  COMPARABLE_TYPES = [Integer, String].freeze. I think the specs provided here as still useful.

I used the specs in my pr. This can be closed as it is stale

Can you please close in favor of https://github.com/jmespath/jmespath.rb/pull/57

Yes, it's fine to close in favor of #57, but this was not understandable for the first comment.


Clicks are not working in 4.26

I am using the 4.26 release out of the box and then binding a key to creating the widget. The widget and web page load but when I click into the widget it fails to fire a mouse click.

just kidding... <3

Great stuff


Launchpad "Masterclass" Curriculum Request

Problem Description
With the move to a 4 week curriculum, we want to be still able to educate folks about some of projects that are not in our core curriculum but people have a lot of interest in. We've previously been setting up Q&A sessions on an ad-hoc basis with the following teams:

Cryptoecon
Saturn
FVM
Compute Over Data
Filecoin Green
Marketing
Network Goods (they've been folded into the PLN section of the curriculum with their network funding Q&A session)

The goal here would be two things:

Cohort team to implement a rotation and cadence for live Q&A sessions
Curriculum team to build some supplemental curriculum and workshops around these teams.

What we could start with
-Crytpoecon: we already have a section for it in the curriculum we could just add workshop or a section on tokenomics
-Filecoin Green: we could add a section to the curriculum about filecoin green and add co.2storage to the dev tools section
Additional context
This is more of a broad issue ticket to get it on paper somewhere but I'm sure this will end up being multiple tickets and discussions. This will for sure need some discussion ideals/what to first/timeline etc with both teams.

@kt-wawro would be great to work with you to spec/ create an issue for each of the individual ones (e.g. one for CryptoEcon, one for COD, etc) and then plan which should be tackled in which order -- e.g. if you are going to ask COD to present next colo, we would prioritize making a page for that!

Info from Niki G FVM -
Best to check which dev tools should be featured here with respective dev advocates:
@truckerfling
@hammertoe
(also Zondax team maybe, for the solidity library they have built)
Filecoin. -
@Jenks
@Longfei
IPFS -
@Discordian
@Daniel Norman
Anything hackathon related -
@dawnkelly09
Bacalhau -
@Iryna
@AlisonWonderland (Ally)
Web.storage and NFT.storage -
@Aysun Demircan
Community tools:
Lighthouse -
@Nandit Mehra
Tableland - shared channel on Discord is fastest way to reach them, can add you
Livepeer - can check
Fleek/Ceramic/Pinata/Spheron/Moralis - are very low touch ways of using IPFS and we are recommending other ways listed above before any of these.
You should chat about how we are thinking about devtools with
@dawnkelly09
in maybe 1-2 weeks. They are changing very frequently.
1:09
All these chats can be done in the #devrel channel


fontawesome:0.4.0 broken in typst v0.12.0

I tested the package via the local environment and typed the web app. I received the same message.
warning: unknown font family: font awesome 6 sharp duotone
   ┌─ @preview/fontawesome:0.4.0/lib-impl.typ:20:10
   │
20 │       font: (
   │ ╭───────────^
21 │ │       "Font Awesome 6 Free" + if solid { " Solid" },
22 │ │       "Font Awesome 6 Brands",
23 │ │       // TODO: Help needed to test following fonts
   · │
27 │ │       "Font Awesome 6 Sharp Duotone" + if solid { " Solid" },
28 │ │     ),
   │ ╰─────^

Typst v0.11.1 works fine.
From Typst changelog, they mentioned that:

Setting the font to an unavailable family will now result in a warning

This package doesn't provide the font file, so a warning would be great if the Free set is not found. However, I currently have no idea how to handle Pro sets.

Some possibilities could be:

Splitting the fontawesome package in a pro and free version, both providing the #fa-icon function
Appending a pro option (#let fa-icon(name, solid: false, pro: false, [...])[[...] if pro { include pro fonts in #text))
Adding a new function #fa-icon-pro containing the pro fonts
(my preffered one, but requires documentation): Adding a state, something like:

#let _useProFonts = state("pro-fonts", false);
#let use-pro-fonts = { _useProFronts.update(true) }

#let fa-icon(
  name,
  solid: false,
  fa-icon-map: (:),
  ..args,
) = {
  context {
    let fonts = (
      "Font Awesome 6 Free" + if solid { " Solid" },
      "Font Awesome 6 Brands",
      )
    if (_useProFonts.get()) {
      fonts.join((
         "Font Awesome 6 Pro" + if solid { " Solid" },
        "Font Awesome 6 Duotone",
        "Font Awesome 6 Sharp" + if solid { " Solid" },
        "Font Awesome 6 Sharp Duotone" + if solid { " Solid" },
      ))
    }
  text(
    font: fonts,
    // TODO: We might need to check whether this is needed
    weight: if solid { 900 } else { 400 },
    // If the name is in the map, use the unicode from the map
    // If not, pass the name and let the ligature feature handle it
    fa-icon-map.at(name, default: name),
    ..args,
  )
  }
}

I'm still new to typst, so there may be better ways to built the fonts array (shorthand if or something like that).

(my preffered one, but requires documentation): Adding a state, something like: main...noboevbo:typst-fontawesome:main

Considering all the generated methods are affected by the default fonts, I agree with you. I will fix this ASAP

(my preffered one, but requires documentation): Adding a state, something like: main...noboevbo:typst-fontawesome:main

Considering all the generated methods are affected by the default fonts, I agree with you. I will fix this ASAP

Thanks! I created a pull request, as I already implemented it to continue work without those warning messages.

Oh, sorry. I just pushed the commit with a similar implementation and updated documents. (Though I add a co-author line) 😢

Oh, sorry. I just pushed the commit with a similar implementation and updated documents. (Though I add a co-author line) 😢

No problem :) Thanks for the quick fix and the quick pr to the typst packages repo.


CMake does not generate "toFloat.h" with Ninja

On Windows. Can someone check that?
ninja: error: 'C:/Users/Constantine/Desktop/openexr/IlmBase/Half/toFloat.h', needed
by 'Half/CMakeFiles/Half.dir/half.cpp.obj', missing and no known rule to make it

Anyone managed to get this working?

@ZeroCrunch ,
In openexr/IlmBase/Half/CMakeLists.txt, I updated the code to the followin:g:
...
SET_SOURCE_FILES_PROPERTIES(
half.cpp
PROPERTIES
OBJECT_DEPENDS
toFloat
OBJECT_DEPENDS
eLut
)
IF(BUILD_SHARED_LIBS)
ADD_DEFINITIONS(-DHALF_EXPORTS)
ENDIF()
ADD_LIBRARY ( Half ${LIB_TYPE}
half.cpp
)
INSTALL ( TARGETS
Half
DESTINATION
lib
)
...
It worked on my side.
Cheers,
Francis

This looks like the correct fix to me - it would be a good PR.

@francis-brissette,
What worked for me in the end was:
PROPERTIES
OBJECT_DEPENDS
"${CMAKE_CURRENT_BINARY_DIR}/toFloat.h;${CMAKE_CURRENT_BINARY_DIR}/eLut.h"

@meshula, will you take care of this bug & fix?

@ZeroCrunch @francis-brissette This fix is on the develop branch, thanks Jamie!

Looking into the backlog of open OpenEXR issues. This seems to have been resolved in the v2.3.0 release.
Closing the issue for now, feel free to re-open or file a new issue if you need further help.


OKD & Proxmox : 4.11.0 console and authentication not working after bootstrap

Describe the bug
Hi ! I have a problem when boostrap complete : Console and authentication not Ready. I have 503 call :
"APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request..."
I have six server proxmox with one "okd-services" contains : DNS server, haproxy, pxe server. And 3 master / 3 worker. Domains calls between nodes / master works (ping test). When i try to access to console : I access on cluster but with the not available screen (same as route not exist in cluster).
Note : I have a home lab proxmox with one server (with 6 VM : 3 master / 3 worker) and it works.
Install configuration :
apiVersion: v1
baseDomain: {{ dns.domain }}
metadata:
  name: {{ dns.clusterid }}
compute:
- hyperthreading: Enabled
  name: worker
  replicas: 3
controlPlane:
  hyperthreading: Enabled
  name: master
  replicas: 3
networking:
  clusterNetwork:
  - cidr: <IP_ADDRESS>/14
    hostPrefix: 23
  networkType: OpenShiftSDN
  serviceNetwork:
  - <IP_ADDRESS>/16
platform:
  none: {}
fips: false
pullSecret: '{{ pull_secret }}'
sshKey: "{{ ssh_pub_key }}"

[root@okd-services ~]# oc get nodes
NAME           STATUS   ROLES    AGE   VERSION
okd-master-1   Ready    master   52m   v1.24.6+5658434
okd-master-2   Ready    master   52m   v1.24.6+5658434
okd-master-3   Ready    master   52m   v1.24.6+5658434
okd-worker-1   Ready    worker   39m   v1.24.6+5658434
okd-worker-2   Ready    worker   39m   v1.24.6+5658434
okd-worker-3   Ready    worker   39m   v1.24.6+5658434

Version
4.11.0-0.okd-2022-12-02-145640
UPI / Platform none
How reproducible
100%
Log bundle
[root@okd-services ~]# oc get clusteroperators
NAME                                       VERSION                          AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication                             4.11.0-0.okd-2022-12-02-145640   False       False         True       45m     APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request...
baremetal                                  4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
cloud-controller-manager                   4.11.0-0.okd-2022-12-02-145640   True        False         False      46m
cloud-credential                           4.11.0-0.okd-2022-12-02-145640   True        False         False      46m
cluster-autoscaler                         4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
config-operator                            4.11.0-0.okd-2022-12-02-145640   True        False         False      45m
console                                    4.11.0-0.okd-2022-12-02-145640   False       False         True       37m     RouteHealthAvailable: console route is not admitted
csi-snapshot-controller                    4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
dns                                        4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
etcd                                       4.11.0-0.okd-2022-12-02-145640   True        False         False      42m
image-registry                             4.11.0-0.okd-2022-12-02-145640   False       True          True       30m     NodeCADaemonAvailable: The daemon set node-ca has available replicas...
ingress                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      4m11s
insights                                   4.11.0-0.okd-2022-12-02-145640   True        False         False      38m
kube-apiserver                             4.11.0-0.okd-2022-12-02-145640   True        True          False      40m     NodeInstallerProgressing: 2 nodes are at revision 8; 1 nodes are at revision 9
kube-controller-manager                    4.11.0-0.okd-2022-12-02-145640   True        False         True       42m     GarbageCollectorDegraded: error fetching rules: Get "https://thanos-querier.openshift-monitoring.svc:9091/api/v1/rules": dial tcp <IP_ADDRESS>:9091: connect: connection refused
kube-scheduler                             4.11.0-0.okd-2022-12-02-145640   True        True          False      41m     NodeInstallerProgressing: 1 nodes are at revision 7; 2 nodes are at revision 8
kube-storage-version-migrator              4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-api                                4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-approver                           4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-config                             4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
marketplace                                4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
monitoring                                                                  False       True          True       31m     Rollout of the monitoring stack failed and is degraded. Please investigate the degraded status error.
network                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
node-tuning                                4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
openshift-apiserver                        4.11.0-0.okd-2022-12-02-145640   False       False         False      29m     APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request...
openshift-controller-manager               4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
openshift-samples                          4.11.0-0.okd-2022-12-02-145640   True        False         False      34m
operator-lifecycle-manager                 4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
operator-lifecycle-manager-catalog         4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
operator-lifecycle-manager-packageserver   4.11.0-0.okd-2022-12-02-145640   True        False         False      6m7s
service-ca                                 4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
storage                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      45m

must-gather-okd-20221212.txt

We're gonna need an archive produced by must-gather tool, not its output

@titou10titou10 Thanks.
Yes i check many times. After each bootstrap complete, comment bootstrap on haproxy and stop bootstrap VM. My home lab works fine with one proxmox server.
I have 6 proxmox servers with private mesh VPN (Wireguard). Each server on 192.168.1X.1/24 network.
Server 1 : <IP_ADDRESS>
Server 2 : <IP_ADDRESS>
Server X : 192.168.1X.1
Each server have dnsmasq (config pxe server & attribute VM IP by mac address & configure DNS server).
Example dnsmasq config :
dhcp-range=<IP_ADDRESS>,<IP_ADDRESS>,12h
dhcp-lease-max=25
dhcp-host=D2:8E:FF:B3:01:73,<IP_ADDRESS>,okd-master-1
dhcp-host=12:8E:DE:B3:01:60,<IP_ADDRESS>,okd-services
dhcp-option=option:dns-server,<IP_ADDRESS>,<IP_ADDRESS>
dhcp-boot=pxelinux.0,,<IP_ADDRESS>

okd-services (bastion) :
public (enp6s18) : PUBLIC_IP
private (enp6s19) : <IP_ADDRESS>

haproxy
pxe server
dns server (bind)

okd-master-1 : <IP_ADDRESS>
okd-master-2 : <IP_ADDRESS>
okd-master-3 : <IP_ADDRESS>
okd-worker-1 : <IP_ADDRESS>
okd-worker-2 : <IP_ADDRESS>
okd-worker-3 : <IP_ADDRESS>

I have a problem on authentication operators (503) and console not contact oauth (timeout). Very similar : https://github.com/okd-project/okd/issues/430
My bad. The archive :
must-gather.local.1194632374733407674.tar.gz

Try with networkType: OVNKubernetes. Same result.
must-gather archive :
must-gather.local.7911081472470111102.tar.gz

Get \"https://oauth-openshift.apps.cloud.soyouweb.fr/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\nOAuthServerServiceEndpointAccessibleControllerDegraded: Get \"https://<IP_ADDRESS>:443/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

and
"WellKnownReadyControllerProgressing: kube-apiserver oauth endpoint https://<IP_ADDRESS>:6443/.well-known/oauth-authorization-server is not yet served and authentication operator keeps waiting (check kube-apiserver operator, and check that instances roll out successfully, which can take several minutes per instance)"

in authentication operator, as kube-apiserver never rolled out:
"NodeInstallerProgressing: 1 nodes are at revision 0; 1 nodes are at revision 3; 1 nodes are at revision 8"

installer pods cannot be created:
"Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_installer-8-okd-master-1_openshift-kube-apiserver_62b703a9-0b89-4801-92dc-a6af80a6b611_0(c09814543ff0b731abf40775238958a55b55b10d5c1059d5b47b070163b5d453): error adding pod openshift-kube-apiserver_installer-8-okd-master-1 to CNI network \"multus-cni-network\": plugin type=\"multus\" name=\"multus-cni-network\" failed (add): [openshift-kube-apiserver/installer-8-okd-master-1/62b703a9-0b89-4801-92dc-a6af80a6b611:openshift-sdn]: error adding container to network \"openshift-sdn\": CNI request failed with status 400: 'the server was unable to return a response in the time allotted, but may still be processing the request (get pods installer-8-okd-master-1)\n'"

That looks like a weird networking issue.
Also, must-gather is incomplete, seems its using some user cert and didn't fetch a lot of data from openshift-* namespaces. Could you check if that works using installer-generated kubeconfig? Also try via export KUBECONFIG=/etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig on masters

Thanks. I think too but i found not the problem.
The must-gather could be complete : https://drive.google.com/file/d/1LMTX6oV4Mz7n5h1rQ5RSIog8G4ccNP_Q/view?usp=share_link

I have 6 proxmox servers with private mesh VPN (Wireguard). Each server on 192.168.1X.1/24 network.

Are you sure the private mesh VPN between the hypervisors isn't interfering here? I'm not 100% sure, but the must-gather does indicate to me some kind of peculiar networking issue outside of the cluster.

I installed new cluster in single proxmox server and it works. I abandon installation on multiple proxmox with private mesh networks. Thanks for your help.


Externals not mounted in DIND from Runner

I am running into a complication where the mount of /home/runner/externals yields an empty folder in my jobs.
runner@runner-pool2-pod-4cj8m:~$ ls -la externals/total 16
drwxr-xr-x 4 runner 121 4096 Aug 30 17:28 .
drwxr-xr-x 1 runner 121 4096 Sep  1 12:01 ..
drwxr-xr-x 6 runner 121 4096 Aug 30 17:28 node12
drwxr-xr-x 3 runner 121 4096 Aug 30 17:28 node12_alpine
runner@runner-pool2-pod-4cj8m:~$ docker run --rm -it -v /home/runner/externals:/_externals --entrypoint bash centos:7
[root@b2aec0c0ed67 /]# ls -la /_externals/
total 8
drwxr-xr-x 2 root root 4096 Sep  1 12:25 .
drwxr-xr-x 1 root root 4096 Sep  1 12:25 ..

I have traced the issue down to DIND taking in that mount from its own container rather than mounting remotely from the runner as is apparently the expected function. I believe one could share a mount between runner and docker container to make it available on the DIND side of things, but out of the box, I do not see how any users are able to perform actions/checkout@v2 due to the missing /__e/node12/bin/node as the mount is empty.
Is anyone else's experience that the runner container can remotely mount its externals folder to DIND? Or is there some of other sync activity I am missing? Currently searching around for a clever way to expose the existing runner folder onto DIND, but I am starting to think I will rather need to copy the node12 folder to DIND to make it available when the mount is performed.

hmmmm gonna try an init container to copy the externals to an emptydir mount...

So using an init container totally worked. I created an emptyDir, mounted to an init container as /_externals, rsync'd /home/runner/externals, then mounted that volume in the runner and DIND and its now available. I am still not sure how anyone else is using this successfully given the above limitation. Am I missing something?

I believe I am hitting this same issue on checkout.
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/__e/node12/bin/node\": stat /__e/node12/bin/node: no such file or directory": unknown

@developerdino yep that is the exact error. You can see if you hop into the container that the externals folder has the node bin on the runner, but that DIND attempts the mount on its side instead mounting an empty folder.


php 7.1 ts in window  const error

in php 7.1 ts
zephir const can not use string
for example
class A
{
        const A = 1;
        const B = "test";
}

this example can complie,but can not execute.
if I delete const B="test", it can execute.

Hi, I checked 10minutes ago and with latest version everything works great.
PHP 7.1.3 (cli) (built: Mar 31 2017 22:05:21) ( ZTS DEBUG )
Zephir 0.9.6a-dev-3ea0e94d8e
Please checked again and I will be waiting for feedback.
my test case
<?php
var_dump(new \Utils\Test());

var_dump(\Utils\Test::A);
var_dump(\Utils\Test::B);

Can't reproduce

PHP 7.1.3-3+deb.sury.org~xenial+1 (cli) (built: Mar 25 2017 14:00:03) ( NTS )
Zephir 0.9.6a-dev-ec52b83e7f


feat: create endpoint for changing user password

Description
This pull request introduces an endpoint for changing the password of authenticated users.
The changes include:

Endpoint Addition: Added PATCH /api/v1/users/me/password  for changing user passwords.
Authentication: Ensured the endpoint is secured and only accessible to authenticated users.
Validation: Implemented checks for validating old passwords and ensuring new passwords meet security criteria.
Error Handling: Added appropriate error messages for invalid requests and authentication failures.
Testing: Added unit and integration tests to ensure functionality and edge cases are covered.

Related Issue (Link to issue ticket)
ticket

Motivation and Context

This feature is essential to allow users to securely change their passwords.
How Has This Been Tested?

Unit Tests: Added tests to validate the endpoint responsible for changing user passwords.
Integration Tests: Included end-to-end tests to ensure proper functionality and security.
Tests Include:

Changing a password with valid old and new passwords.
Ensuring the old password is correctly validated.
Handling validation errors and authentication failures.

Screenshots (if appropriate - Postman, etc):

SUCCESSFULLY CHANGED PASSWORD

WITHOUT AUTHENTICATION HEADER

MISSING BODY ARGUMENTS

WRONG OLD PASSWORD

Docs

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@zxenonx done

@Goketech i've removed it

@bolexs

resolve conflicts

@bolexs done

@bolexs

@zxenonx i am done


import maps module in colab

Habitat-Sim version
v0.2.1
I wonder that in colab maps module has been used in top-down view, I just download habitat-sim versionv0.2.1. But I can not fond maps.py file in the whole habitat-sim file, however it is in the habitat-lab file,  which I mean if I want to use maps module do I have to
install the habitat-lab file?

Hey @yaofeng11,
Yeah, the Colab imports maps from Habitat-lab: from habitat.utils.visualizations import maps to draw the map. You'll need to install lab in your conda environment to import that feature.
However, as noted by the tutorial, you can get the map data array from sim without lab:

You can get the topdown map directly from the Habitat-sim API with PathFinder.get_topdown_view.
This map is a 2D boolean array
sim_topdown_map = sim.pathfinder.get_topdown_view(meters_per_pixel, height)


Check-log added features and refactor

From the change log:
Added

Added option to ignore matched files based on given Regex - check-log.rb
Added option to set line limit on the return message for each file matched - check-log.rb
Added inode tracking for log files - check-log.rb

Changed

Returned lines now include the file name - check-log.rb
Refactored code into methods - check-log.rb (Increases modularity, improves code climate checks)
Fixed rubocop errors - check-log.rb
Now opens state files as read/write so new files have write access

Would you be able to write a couple of tests covering your changes?

@brandonr1007 can you rebase against master

Apologies for the delay. I'm having difficulty finding time to get back to this and write unit tests. Will close for now until I can make the changes.


What do you think to create stable branch by version?

Hi,
what do you think to create stable branch by version?
Best regards,
Stéphane

I see that http://lists.ceph.com/pipermail/ceph-ansible-ceph.com/2017-January/000025.html

This is not part of our current strategy I'm afraid. We release ceph-ansible version every ~3 months. Each stable version will be able to support the current LTS and potentially another release.
For example, we currently support and test Jewel, the current LTS but soon we will have stable-2.2 with both Jewel and Kraken support.


Example parameter files updates in content and path

Overview/Summary
-- Created parameters folder for each module
-- Moved example parameters files into the parameters folder
-- Created a minimum parameters version of the parameter example files
-- Updated test definition file with the new path to the parameter files (added /parameters/ folder to the path)
This PR fixes/adds/changes/removes

Created parameters folder for each module
Moved example parameters files into the parameters folder
Created a minimum parameters version of the parameter example files
Updated test definition file with the new path to the parameter files (added /parameters/ folder to the path)

Breaking Changes
None
Testing Evidence
Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
As part of this Pull Request I have

[ ] Checked for duplicate Pull Requests
[X] Associated it with relevant [ADO items](https://dev.azure.com/unifiedactiontracker/Solution%20Engineering/_backlogs/backlog/Azure%20Landing%20Zone%20Bicep/Backlog%20Bugs%20Feedback)
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Performed testing and provided evidence.
[ ] Updated relevant and associated documentation.

/azp E2E

/azp run e2e

@msftbot require at least 2 approvals for this PR

forget everything I just told you

@msftbot forget everything I just told you

@msftbot require at least 2 approvals from maintainers for this PR
also @jtracey93 must review

@msftbot forget everything I just told you

@msftbot require approvals from both @jtracey93 & @jfaurskov on this PR

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

Not stale. Under review still 👍

not stale @danycontre is busy on another project launch ATM

@jtracey93 I'd like to propose the following file names for parameters:
Keep for min parameter files:

Rename min from <module>.minimum.parameters.example.json to <module>.min.parameters.json for all modules

Consider one of the following for the complete parameter files:

Rename max all from <module>.parameters.example.json to <module>.all.parameters.json
Rename max complete from <module>.parameters.example.json to <module>.complete.parameters.json
Rename max full from <module>.parameters.example.json to <module>.full.parameters.json

Agreed on min and I like all for the complete option.
@jfaurskov thoughts?

@jtracey93 @jfaurskov I edited my comment regarding a completely different convention as I worked my way into the policy and role modules. Please see updated comment. I'm onboard with "complete" for all parameters.

I like. Do we want min or all at the front to help quickly chose the correct one ?

This goes back to the personal preference piece. I personally would prefer having the files grouped by like functionality vs complete vs min parameter files, but to each their own.
It's the difference between this:

roleAssignmentManagementGroup.managedIdentity.parameters.complete.json
roleAssignmentManagementGroup.managedIdentity.parameters.min.json
roleAssignmentManagementGroup.securityGroup.parameters.complete.json
roleAssignmentManagementGroup.securityGroup.parameters.min.json
roleAssignmentManagementGroup.servicePrincipal.parameters.complete.json
roleAssignmentManagementGroup.servicePrincipal.parameters.min.json

And this:

roleAssignmentManagementGroup.complete.managedIdentity.parameters.json
roleAssignmentManagementGroup.complete.securityGroup.parameters.json
roleAssignmentManagementGroup.complete.servicePrincipal.parameters.json
roleAssignmentManagementGroup.min.managedIdentity.parameters.json
roleAssignmentManagementGroup.min.securityGroup.parameters.json
roleAssignmentManagementGroup.min.servicePrincipal.parameters.json

Additionally, for modules that only contain a single set of complete & min parameter files, having the min complete designation at the end of the file name is more user-friendly if you want to test between the two... cursor only needs to move a few characters. 😜 #LazyDev

Agreed on min and I like all for the complete option.
@jfaurskov thoughts?

Sounds good to me :-)

Closing as #227 supersedes this


Showing wrong in Bluestacks

it shows false in Bluestacks. I have tried by the adding and removing the package.

Not work on BlueStacks 3

I've found the solution for Bluestacks 3
private EmulatorDetector(Context pContext) {     mContext = pContext;     mListPackageName.add("com.google.android.launcher.layouts.genymotion");     mListPackageName.add("com.bluestacks");     mListPackageName.add("com.bluestacks.appmart");     mListPackageName.add("com.bignox.app");     mListPackageName.add("com.vphone.launcher");// it's nox launcher }

What app is  "com.vphone.launcher"?

What app is "com.vphone.launcher"?

It's for nox emulator.


vue-router cant get query value without '#/'

Version
2.7.0
Reproduction link
http://jsfiddle.net/nbwsc/vav8yg63/
Steps to reproduce
make your url as http://ip:port/path/page/#/?query=value and you can get the query value using $route.query but if you remove the #/(like http://ip:port/path/page?query=value )and refresh the page . It will get undefined .
I meet some trouble with this using nginx static file server to deploy my Vue app.
So I get the query value using my own parser
is that a bug?
What is expected?
it should work I hope
What is actually happening?
but it gives me undefined

You have to change the mode option when creating the router. See https://router.vuejs.org/en/essentials/history-mode.html


macOS: winit emits a MouseInput event after resizing

repro example:
extern crate winit;

fn main() {
    let mut events_loop = winit::EventsLoop::new();

    let _window = winit::WindowBuilder::new()
        .with_title("A fantastic window!")
        .build(&events_loop)
        .unwrap();

    events_loop.run_forever(|event| {
        match event {
            winit::Event::WindowEvent { event: winit::WindowEvent::Resized(x, y), .. } => {
                println!("resized: {},{}", x, y);
                winit::ControlFlow::Continue
            }
            winit::Event::WindowEvent { event: winit::WindowEvent::MouseInput { state, .. }, .. } => {
                println!("mouse input: {:?}", state);
                winit::ControlFlow::Continue
            }
            winit::Event::WindowEvent { event: winit::WindowEvent::Closed, .. } => {
                winit::ControlFlow::Break
            },
            _ => winit::ControlFlow::Continue,
        }
    });
}

For some reason, after resizing, on mouse up, appkit::NSLeftMouseUp fires, and appkit::NSLeftMouseDown never fires. Seems like it might have something to do with resize blocking the event loop.

So, with the printlns added here: https://github.com/tomaka/winit/compare/master...sodiumjoe:463-resize?expand=1
the output looks like this on resize:
WindowEvent { window_id: WindowId(Id(140514968137152)), event: CursorEntered { device_id: DeviceId(DeviceId) } }
resizing
WindowEvent { window_id: WindowId(Id(140514968137152)), event: Resized(2040, 1526) }
resizing
WindowEvent { window_id: WindowId(Id(140514968137152)), event: Resized(2040, 1524) }
resizing
WindowEvent { window_id: WindowId(Id(140514968137152)), event: Resized(2040, 1522) }
WindowEvent { window_id: WindowId(Id(140514968137152)), event: MouseInput { device_id: DeviceId(DeviceId), state: Pressed, button: Left, modifiers: ModifiersState { shift: false, ctrl: false, alt: false, logo: false } } }
WindowEvent { window_id: WindowId(Id(140514968137152)), event: TouchpadPressure { device_id: DeviceId(DeviceId), pressure: 0.0, stage: 1 } }
WindowEvent { window_id: WindowId(Id(140514968137152)), event: TouchpadPressure { device_id: DeviceId(DeviceId), pressure: 0.000030517578, stage: 1 } }
WindowEvent { window_id: WindowId(Id(140514968137152)), event: TouchpadPressure { device_id: DeviceId(DeviceId), pressure: 0.002029419, stage: 1 } }
WindowEvent { window_id: WindowId(Id(140514968137152)), event: TouchpadPressure { device_id: DeviceId(DeviceId), pressure: 0.0050354004, stage: 1 } }

It looks like the event loop blocks when the resize starts. So while resizing all the event_loop events queue up inside the nextEventMatchingMask_untilDate_inMode_dequeue_. Then once the resizing finishes, the event loop runs again and emits all the events that were queued.
So it looks like the initial MouseInput { state: Pressed } is there, but for some reason the MouseInput { state: Released } isn't in the queue. I have no idea why.
One way to address this might be to discard all the queued events during resize with this. I guess the window would have to notify the event loop when a resize happens.

@Osspial @paulrouget @francesca64 @mitchmindtree @swiftcoder @robsaunders (pinging y'all because you're either well represented in git blame on src/platform/macos/{events_loop,window}.rs or I've interacted with you in the past on macos issues, apologies if this is inappropriate)
I'd be willing to take a stab at this, but would appreciate any guidance. Discarding all events queued during resize seems reasonable to me, since presumably those events would only originate from the window as opposed to other application events, but I'm new to objective-c and rust. I also don't want to sink too much time into this if the approach is just wrong.
Alternatively, if anyone has ideas about a better approach, I'm all ears. Thanks!

I'm actually a little surprised that this is happening, because winit is looking for events in NSDefaultRunLoopMode and window resize should be happening running in NSEventTrackingRunLoopMode.
That said, a simple hack would be to eat a single MouseUp event in WindowDelegate.window_did_resize(...), which might do the trick. Or we could potentially rework the whole event loop to work with live window resize, and get smooth rendering during resize working as well.

@swiftcoder

I'm actually a little surprised that this is happening, because winit is looking for events in NSDefaultRunLoopMode and window resize should be happening running in NSEventTrackingRunLoopMode.

I think the issue is that the resize event doesn't come from that event loop, it comes from the WindowDelegate.window_did_resize, which is out of band of the event loop (they eventually both called user_callback.call_with_event directly).
I think this is why the hack wouldn't work either, because the events are sourced from different places. I can try keeping a has_unhandled_resize_event boolean in UserCallback in order to eat the next MouseUp event in call_with_event, but that seems like a significantly nastier hack than what you suggested. I'll try it out and report back.
I also have tried googling around for why the event is emitted, and why the MouseDown isn't, but my google-fu is failing me there (and my unfamiliarity with cocoa is not helping).
Live window resize looks like it would involve a pretty significant refactor, and possibly an api change?

Ok, there's something a little more subtle going on here. If I take your example, and press and hold on the resize affordance (without moving the mouse), I see both the press and the release event one after another, but neither appears until I let go of the button.
If I drag, I get the resize events, then the Press, but the Release never shows up.

I see what's happening. We do actually receive the mouse down event, but then we call NSApp.sendEvent(...) with it, which dispatches to NSWindow.sendEvent(...), which if you are over a resize handle, enters a modal tracking loop... the tracking loop blocks until the user releases the mouse.
If the mouse wasn't moved, we'll deliver the mouse down when we are unblocked, and immediately receive the mouse up, and all is well.
However, if the mouse was dragged, NSWindow's tracking loop discards to mouse up event (along with all the mouse moved events). We are unblocked, we deliver the original mouse up event, and there's no mouse down in the queue any more, so things are not good.
We can solve this by marking the event for discarding in windowDidResize. See #466 for a working fix.

@swiftcoder awesome, thanks! I wouldn't have been able to figure this out for a while, if at all.

Oh wow, I wasn't expecting this to resolve so painlessly. Great work, @swiftcoder!
In regard to changing the API to make live window resize possible, there's been more discussion lately about changing the way the event loop works (#459) which is a fairly recurring area of concern (#231). Therefore, if you have any case to make for why the current API should change, then I encourage being vocal, since that will help lead us to a decisive stance on what's needed.
@sodiumjoe I certainly don't mind being pinged (though that's not saying much, since I get notified either way), but I'd like to take this opportunity to ask if you mind being pinged. I can see that you've been putting care into winit and the macOS backend, and it would be a big help if you could review PRs and generally represent the interests of Mac users.

@francesca64 I've found my way into contributing to winit by way of alacritty, mostly trying to scratch my own itches and also trying to learn rust. Out of necessity, I've had to learn a little bit of obj-c and c along the way 😅 . All that to say, I'm very inexperienced at basically everything in winit.
That said, I'm happy to contribute what time I can find (I have a full time job and young children), and I don't mind being pinged at all. If nothing else, I can help test/verify issues and fixes.

A prettier fix somewhere down the road might be to pull mouse down events off the Window, instead of the global event queue. If we overrode mouseDown: and mouseUp: on the window's container view, that would give us mouse events after the window has handled resizing, instead of before.
It would limit us to only handling those events within the window bounds, so we'd need to return to the existing method when capturing the mouse... maybe not prettier after all. Hmm.

what is the release process for winit/glutin?

@sodiumjoe You can ask to publish a new versi9j by submitting a PR that bumps the changelog and the version in Cargo.toml.

Re-opening as per #470

seems like at this point we should consider this blocked on https://github.com/tomaka/winit/issues/459 and https://github.com/tomaka/winit/issues/231

#561 appears to fix this.


Adds "storageclass" configuration parameter for S3 driver.

Defaults to STANDARD, also supports REDUCED_REDUNDANCY.
Addresses #753

Current coverage is 52.95%

Merging #1401 into master will decrease coverage by -4.23% as of 981f613

@@            master   #1401   diff @@
======================================
  Files          123     123
  Stmts        11327   11344    +17
  Branches       798     727    -71
  Methods          0       0
======================================
- Hit           6477    6007   -470
+ Partial        798     727    -71
- Missed        4052    4610   +558

Review entire Coverage Diff as of 981f613

Uncovered Suggestions

+0.28% via ...ge/driver/gcs/gcs.go#182...213
+0.24% via ...ge/driver/gcs/gcs.go#85...111
+0.21% via ...ge/driver/gcs/gcs.go#471...494
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Is it possible to test this by checking the storage class in the response header?

@RichardScothern Test added :+1:

LGTM

LGTM


Predicate-based removal of elements [HPPC-8]

Currently, Lists have the removeAll(type e) method that removes all elements that are equal to e. It would be good to generalize this method to become removeAll([type]Predicate) and have it remove all elements for which the predicate returns true.
Would it make sense to have this method in all Lists, Sets and Deques?

Issue: HPPC-8 (migrated from JIRA), created by Stanisław Osiński (@stanislawosinski), resolved Mar 10 2010
Attachments: HPPC-8.patch

Comment by Dawid Weiss (@dweiss) (migrated from JIRA)
A work-in-progress patch. I don't know how to implement removeAll using this predicate in an efficient way. It is quite awkward at the moment – I believe it could be done if we had a higher-level set of interfaces (at least a Collection-like with contains and iterators).
Will think of it, for now, postponing.

Comment by Dawid Weiss (@dweiss) (migrated from JIRA)
In trunk for all ObjectCollections and ObjectObjectAssociativeContainers.


Make a UI for series

There isn't a UI for series yet. We need to have a way to browse through the content we have (we can reuse the JSON file generated for the facet filtering page) and create series from content. We can currently only create series of a single category (limitation of Hakyll right now).

WIP is available at http://haskanything.com/ui/submit/series.html.

Nearly done, need a field for the body


Task - Type specimen - lectotype and neotype citation

Lectotype and Neotype designation require a citation of the source where the type was designated. Please add a citation field to the form.

I think it is fixed.


[Deps] Bump scale-info to match cumulus and polkadot

This makes sure we have the same scale-info version for all the libraries across cumulus/substrate/polkadot the repositories.
Cumulus is already on 2.5.0, polkadot is about to be.
Polkadot companion: https://github.com/paritytech/polkadot/pull/7049

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate-macos
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664563

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664561

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664562

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664550

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664735

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2664986

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2665940

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2667989

bot merge

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2671698


Update RESOURCES.md to add more up-to-date learning resources

The current recommended learning resources are outdated and don't reflect the improvements that the language has known in recent years.

Thanks for the PR 👍


[Confused] About DisplayObject.prototype.updateTransform

In current  PIXI.js :
    updateTransform()
    {
        this.transform.updateTransform(this.parent.transform);
        // ......
    }

the  DisplayObject.prototype.updateTransform not check the parent , So this code can't run :
var myContainer = new PIXI.Container();
// ......
myContainer.updateTransform();

If I want to run it , I have create an abstract  parent container , like this
var uselessAndAbstractContainer = new PIXI.Container();
var myContainer = new PIXI.Container();
uselessAndAbstractContainer.addChild(myContainer);
// ......
myContainer.updateTransform();

related issues : #3370

I think the updateTransform  of DisplayObject/Container/Sprite need to think about 3 important questions :

which transform matrix should be update ? localTransform?  worldTransform?  or both?
whether  with parent's  transform？ if with ,  with which one ？parent.localTransform?  parent.worldTransform?  or both?
whether  call children's  updateTransform ?

In the real game ,
Sometimes we use  containers & child nodes as a pure rendering tree ， in this case container.updateTransform() or  renderer.render(container) is good enough.
But Sometimes ,  We have to consider  updateTransform/render  of sprites separately.  in this case Container is like an abstract  group.
I know Container is an subclass of DisplayObject , it shouldn't be used as a abstract group.
But in PIXI , there is no an other way to manage some sprites which have same parent transform.

Share my solution now ：
the first step， add a new function named updateWorldTransform  to  Transform & TransformStatic, like this  (sure, there is a little difference)  :
    /**
     * Updates world matrix(include local matrix) without parent
     */
    updateWorldTransform()
    {
        const lt = this.localTransform;

        lt.a = this._cx * this.scale._x;
        lt.b = this._sx * this.scale._x;
        lt.c = this._cy * this.scale._y;
        lt.d = this._sy * this.scale._y;

        lt.tx = this.position._x - ((this.pivot._x * lt.a) + (this.pivot._y * lt.c));
        lt.ty = this.position._y - ((this.pivot._x * lt.b) + (this.pivot._y * lt.d));

        const wt = this.worldTransform;

        wt.a = lt.a;
        wt.b = lt.b;
        wt.c = lt.c;
        wt.d = lt.d;
        wt.tx = lt.tx;
        wt.ty = lt.ty;

        this._worldID ++;
    }

the 2nd step, add a function named updateTransformLite to DisplayObject & Container like this  (sure, there is a little difference) :
    /**
     * Updates the transform of this object self
     */
    updateTransformLite()
    {
        if (this.parent)
        {
            this.transform.updateTransform(this.parent.transform);
            this.worldAlpha = this.alpha * this.parent.worldAlpha;
        }
        else
        {
            this.transform.updateWorldTransform();
            this.worldAlpha = this.alpha;
        }

        this._bounds.updateID++;
    }

Doing a check for parent takes a significant performance hit.
Seems like the other issue you opened (#3415) talked more about this problem.


Remove merge-utils, make renderOptions immutable

Hi @emarukyan it looks like Object.assign doesn't exist in Node.js 0.10, so we need some kind of polyfill for it's behavior. Does the utils-merge not make a suitable polyfill? Is there something better to use?

Well, I just tried to remove mutability of variables along the way.
cos it's not a good practice to mutate variable in place.
so me think a bit, and come back with better offer.

What was being mutated? As far as I can tell yhe changes here mutate the exact same things just with Object.assign

Two things that I always try to avoid!
mutate input variables of functions., and do this several times in a raw.
so it would just be great, if we return new variable each time we want to add property on an object.
it's not a big trouble, but anyway.. I thought we might change this.hm?
  // merge app.locals
  merge(renderOptions, this.locals);
  // merge options._locals
  if (opts._locals) {
    merge(renderOptions, opts._locals);
  }

  // merge options
  merge(renderOptions, opts);

mutate input variables of functions

I agree that this is bad, but I don't think that this was actually done? The renderOptions variable was local inside the function, and created in the beginning of it. I'm not sure I see the exact problem?


wrong chest drop

Description (Required)

The destroyed chest will not drop properly.
Steps to reproduce the Issue (Required)

Place emerald chest
Destroy it (as player)
it drop a cs-corelib's head

Expected behavior (Required)

The chest will drop normally
Server Log / Error Report

Error: https://pastebin.com/VawhaPPk
Full log: https://pastebin.com/MUCK0rSL
Environment (Required)

Description (Required)

The destroyed chest will not drop properly.
Steps to reproduce the Issue (Required)

Place emerald chest
Destroy it (as player)
it drop a cs-corelib's head

Expected behavior (Required)

The chest will drop normally
Server Log / Error Report

Error: https://pastebin.com/VawhaPPk
Full log: https://pastebin.com/MUCK0rSL
Environment (Required)

Does this happen with or without PrivateStorage.bypass permission? Or both?

If I give player this permission, it will drop right.

Righto

So should I just give this permissi to the players?

Of course not this is a bug that I will fix soon


Dots in table names

Deserializing this toml:
[a]
c = ""

#[derive(Deserialize)]
struct Data {
    c: String
}

This works:
#[derive(Deserialize)]
pub struct MyToml {
    #[serde(rename = "a")]
    data = Data
}

Deserializing this toml:
[a.b]
c = ""

This does not:
[derive(Deserialize)]
pub struct MyToml {
    #[serde(rename = "a.b")]
     data = Data
}

I'm suspicious dots are handled in a special way, but I can't find this in the docs or examples.

Thank you - that fixed it. Added layers of dummy-structs.


Allow official document type to be null

https://trello.com/c/3E2vqBkS/1507-support-official-documents-for-featured-file-attachments
Previously we defaulted the official document type to 'unofficial',
but this is inconsistent with the design/intention to force users to
make an explicit selection. If the user aborts the upload workflow
for an attachment, it's also unclear if a selection was made or not.
This changes the column to default the official doc type to null.

Thanks for spotting - should by fixed now 🌤


template dump to console

It'd be useful to be able to dump the template out to the console.

fixed by #28


Issues parsing a column named user

First off thank you - I love this library!
 My simplified example looks like:
res, _ := pg_query.Parse(query)
stmt := res.Stmts[0].Stmt.GetSelectStmt()
for _, f := range stmt.GetTargetList() {
    sp := f.GetResTarget().GetVal().GetColumnRef().GetFields()[0]
    fmt.Println(sp.GetString_().Sval)
}

The following query of course, works: select username, password from foo where user = 'somehuman'
target_list:{res_target:{val:{column_ref:{fields:{string:{sval:\"username\"}}  location:7}}  location:7}}  target_list:{res_target:{val:{column_ref:{fields:{string:{sval:\"password\"}}  location:17}}  location:17}}  from_clause:{range_var:{relname:\"foo\"  inh:true  relpersistence:\"p\"  location:31}}  where_clause:{a_expr:{kind:AEXPR_OP  name:{string:{sval:\">\"}}  lexpr:{column_ref:{fields:{string:{sval:\"x\"}}  location:41}}  rexpr:{a_const:{ival:{ival:17}  location:45}}  location:43}}  limit_option:LIMIT_OPTION_DEFAULT  op:SETOP_NONE" time="2023-07-05T11:55:54+03:00" level=debug msg="column_ref:{fields:{string:{sval:\"username\"}}  location:7
The second, I change username to user, when attempting to call f.GetResTarget().GetVal().GetColumnRef().GetFields()[0] as clearly there's an indexing issue, do the the following parsed version of the object.
target_list:{res_target:{val:{sqlvalue_function:{op:SVFOP_USER typmod:-1 location:7}} location:7}} target_list:{res_target:{val:{column_ref:{fields:{string:{sval:\"password\"}} location:13}} location:13}} from_clause:{range_var:{relname:\"foo\" inh:true relpersistence:\"p\" location:27}} where_clause:{a_expr:{kind:AEXPR_OP name:{string:{sval:\">\"}} lexpr:{column_ref:{fields:{string:{sval:\"x\"}} location:37}} rexpr:{a_const:{ival:{ival:17} location:41}} location:39}} limit_option:LIMIT_OPTION_DEFAULT op:SETOP_NONE"
Is this an underlying libpq issue? I would have assumed my query would parse, and I'd just have a column named user

I think the problem here is that "user" is a keyword, and so you need to escape it like this: "user" (in Postgres syntax," is used to escape identifiers, ' is used for values).

Interesting, thank you. So I looked at 3 options that work with the postgres cli:

I wrapped user in backticks `user`. That fails to parse
As you mentioned, single quotes fail in the exact same way as mentioned above.
Double quotes work


AzureKeyVault@1 is printing the secret as a plain text in DevOps log

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Question/Bug
Enter Task Name: Azure Key Vault
Environment

Server - Azure Pipelines

Agent - Hosted or Private: Hosted, ubuntu-latest

Issue Description
As a part of a pipeline, we want to download all our secrets saved on Azure Key Vault and use it in the next Stages Tasks.
Somehow some of the new secrets created on Key Vault are actually printed as plain text whereas by default it should be ***.
The older secrets however are printed as ***.
     steps:
        -   task: AzureKeyVault@1
            displayName: Download secrets from KeyVault
            inputs:
                azureSubscription: azure_sub
                KeyVaultName: key_vault
                SecretsFilter: keyvault_variable
                RunAsPreJob: true

        -   task: PipAuthenticate@1
            displayName: Authenticate Pip to private package feed
            inputs:
                artifactFeeds: organization
                onlyAddExtraIndex: true

        -   script: |
                echo "##vso[task.setvariable variable=keyvault_variable;isOutput=true]$(keyvault_variable)"
            displayName: Set environment variables
            name: SetVariables

-   stage: Stage2
    jobs:
    -   job: check_if_encrypted
        steps:
        -   task: CmdLine@2
            displayName: Write secrets
            inputs:
                script: |
                    echo keyvault_variable

Task logs
The download happens successfully :
Starting: Download secrets from KeyVault
==============================================================================
Task         : Azure Key Vault
Description  : Download Azure Key Vault secrets
Version      : 1.200.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-key-vault
==============================================================================
SubscriptionId: .
Key vault name: kv5
Downloading secrets using:
Number of secrets found in kv5: 3
Number of enabled and unexpired secrets found in kv5: 3

Downloading secret value for: keyvault_variable.
Downloading secret value for: KVtest.
Downloading secret value for: KVuser.

Finishing: Download secrets from KeyVault

It is literally writing out the secrets :
Starting: Write secrets
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.201.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
========================== Starting Command Output ===========================
/bin/bash --noprofile --norc /__w/_temp/751c3161-4860-4d82-88cc-22223673922.sh

632!3YzHhnFm

Finishing: Write secrets

It should not be printing the secret, instead it should be ***
Need help, thanks

It seems we have to explicitly mention : issecret=true in the script:
echo "##vso[task.setvariable variable=keyvault_variable;isOutput=true]$(keyvault_variable)" . Only then it masks.
What is not clear is why this has to be set for certain for certain sercrets whereas for others it worked without explicitly mentioning. The newly secrets i have to set issecret additionally, however the older ones, it is not required.


Add ductbank

I update the python code to calculate the cable current capacity, including all the inputs and calculation functions/processes.

@xwang78su, the merge from develop is broken. Closing this branch/pr in favor of develop-add-ductbank-2. See new PR #1274 that replaces this one.


allow createMessageHandler to return a promise

...or modify argsAdjuster to allow this. Without this functionality it's difficult to look for an async value that we want to pass into every message handler.

This sounds sensible!


BUG: MetaMaskConnector.connect() throws error

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
v1.4.7
Current Behavior
When trying to connect using the MetamaskConnect an error is thrown and not prompting the connect dialog.

This seems to be reproducing only in Chrome
Expected Behavior
Should connect to wallet
Steps To Reproduce
Create a function that uses a MetamaskConnector.connect and is called upon button press.
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

It was actually an issue due to a company managed google profile being used


Add Hindi translation

Initial Hindi hi language translation.

thanks

thanks

Thanks for accepting my translation. Cheers Mate.


Update documentation for "Press Keys" keyword.

Updated the link to Playwright documentation for "press" that was linked under "Press Keys" keyword. I accidentally pull requested my own fork so that is why this is two commits. First time contributor. Hope that doesn't mess anything up.

Fixes #2202


Add versioning for database

The database should contain the version of the ConceptNet, and the conceptnet-lite.
The downloader should download the right version of the database.

ConceptNet upstream is no longer updated, this ConceptNet Lite wrapper won't be updated anymore either.


Rails 4 0

Rename redis' lock so it doesn't conflict with active record's lock.
https://github.com/nateware/redis-objects/issues/191

👍


[Bug]: Superset Error: (duckdb.IOException) IO Error: Could not set lock on file.

What happened?
(this might be the wrong repo - it looks like an issue with SQL Alchemy BUT this might also be an issue elsewhere)
When creating a dashboard with two charts on a single duckDB database, refreshing the dashboard gives the following error:
Error: (duckdb.IOException) IO Error: Could not set lock on file "/tmp/mdsbox.db": Resource temporarily unavailable. This looks like two reads on the same table at the same time.
As a workaround, refreshing each dashboard element one at a time (manually) does not reproduce the error.
DuckDB Engine Version
duckdb-engine 0.6.4
DuckDB Version
duckdb 0.5.1
Relevant log output
n/a

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, can you link where you've raised this in the superset repository? And also the full stack trace?

Hi @Mause - this was a config issue within superset, the default mode is an exclusive lock. So by adding {"connect_args":{"read_only":1}}, I was able to allow multiple queries at once against a single duckdb database.

Closing as resolved - config issue.


vite preivew failed , browser auto launch https:

Describe the bug
Click on the preview link, https://xxx,
However, the browser is redirected to the https:// address, resulting in failure to open the browser

Reproduction
http://<IP_ADDRESS>:4173/
Steps to reproduce
No response
System Info
System:
    OS: macOS 13.5.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 91.58 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.20.2 - ~/.volta/tools/image/node/16.20.2/bin/node
    Yarn: 1.22.19 - ~/.volta/bin/yarn
    npm: 8.19.4 - ~/.volta/tools/image/node/16.20.2/bin/npm
    pnpm: 8.5.1 - ~/.volta/bin/pnpm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 118.0.5993.117
    Safari: 16.6
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    vite: ^4.2.1 => 4.2.1

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.


pc: init at 0.4

Description of changes
pc(1) is a bc(1)-like from 9front.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1030

The commit message still reads
pc: init at 2022-05-20
while it should be
pc: init at 0.4
(the PR title does it right).
Looks good otherwise!


added TypeScript DefinitelyTyped badge

Note that the link is to the DefinitelyTyped site, and not the definition file for pino.
I think this is fine, because users of DefinitelyTyped need to install a type management tool,
described at DefinitelyTyped.

Thanks!


Alexa not showing up

Description
Even with the right cookie, obtained through alexa.amazon.co.uk, I still get the error [30/08/2023, 17:57:31] [AlexaPlayer] Error: Unknown Device or Serial number
Expected Behavior
The Alexa device would show up as an accessory to pair in Home app.
Logs
[30/08/2023, 17:57:31] [AlexaPlayer] Error: Unknown Device or Serial number
    at AlexaRemote.getMedia (/var/lib/homebridge/node_modules/homebridge-alexa-player/node_modules/alexa-remote2/alexa-remote.js:941:47)
    at /var/lib/homebridge/node_modules/homebridge-alexa-player/src/accessoryFactory.ts:61:24
    at new Promise (<anonymous>)
    at AccessoryFactory.getMedia (/var/lib/homebridge/node_modules/homebridge-alexa-player/src/accessoryFactory.ts:60:16)
    at AccessoryFactory.<anonymous> (/var/lib/homebridge/node_modules/homebridge-alexa-player/src/accessoryFactory.ts:28:34)
    at Generator.next (<anonymous>)
    at /var/lib/homebridge/node_modules/homebridge-alexa-player/lib/accessoryFactory.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/var/lib/homebridge/node_modules/homebridge-alexa-player/lib/accessoryFactory.js:4:12)
    at AccessoryFactory.createAccessory (/var/lib/homebridge/node_modules/homebridge-alexa-player/lib/accessoryFactory.js:30:16)
    at /var/lib/homebridge/node_modules/homebridge-alexa-player/src/accessoryFactory.ts:23:37
    at Array.map (<anonymous>)
    at AccessoryFactory.<anonymous> (/var/lib/homebridge/node_modules/homebridge-alexa-player/src/accessoryFactory.ts:23:18)
    at Generator.next (<anonymous>)
    at fulfilled (/var/lib/homebridge/node_modules/homebridge-alexa-player/lib/accessoryFactory.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Additional Context
ONCE I got it to pair in Home app, but the device said Not Supported (device not supported with Apple Home) and I couldn't use it at all.

Had a similar issue: Tried this plugin a few months ago, removed all the speakers then because of some housekeeping work, now wanting to retry this plugin but none of the speakers showed up except for the one Echo I got since. It seems like Homebridge doesn't unpair accessories cleanly after you remove them from the Home App.
After some digging around, I found the solution:
Even if devices do not show up in the Home App anymore, they're still marked as "paired" within Homebridge. To unpair devices that are no longer paired, in the Homebridge Config UI go to "Homebridge Settings" (three dots-menu on upper right corner), scroll down to "Unpair Bridges / Cameras / TVs / External Accessories" and click the button with an arrow in it on the right. Here, unpair all Echo devices and restart Homebridge. You should be able to see all devices in the "Add Accessory" dialogue in the Home App again.


Documentation Enhacement - Upgrade OXAR to latest APEX patchset

I propose  a new document/section on the github page of OXAR that has specific information about applying a patcheset to Oracle APEX.
Doesn't have to be complex, it's very simply actually:

Unzip the patchset in a directory owned by oracle:dba
Shutdown node4ords and tomcat:

# pm2 stop node4ords
# systemctl stop tomcat@oxar

Backup your database
You can use your preferred way to backup or clone your server for better protection.
Change directory to the patchset_folder/patch
Connect SYS as SYSDBA to the database and run apxpatch.sql
via:

SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password
SQL> @apxpatch.sql

As root copy new images files to /ords/apex_images

# cd /ords/apex_images
# cp -r /u01/app/oracle/PatchetFolder_Name/patch/images .

Reboot your server

I just upgraded my OXAR installation from 5.1.0 to 5.1.4 and everything worked flawless.
The script took 5 mins. on my VM
The Patchset Documentation is a bit too complex and because of OXAR way of installing we can do a target specific document on how to apply it.
thanks for your consideration

Unless things have changed, Oracle patch sets are only available through My Oracle Support. That requires a support contract and I do not anticipate that many people who use OXAR have that access. I personally would avoid giving the impression that one could easily obtain and apply these patches.
My two cents.


Limit GITHUB_TOKEN permissions

@jdolitsky @mattmoor why did this pr switch from using @main to a pinned chainguard-dev/actions commit, which is not upgraded by any automation?

I suspect @jedsalazar didn't realize that branches weren't supported by dependabot.  We can revert that aspect of this until we have a more serviceable solution.


KeyError: 'regularMarketPrice' not working for SPX

Hi, I'm using 0.1.55 version and get the above error on .info for SPX, others securities (spy, aapl,...) are ok.
Any hint to overcome the issue?
Thanks in advance

please use "^SPX" instead of "SPX" as the ticker

Thanks for your comment Lazaro, but I actually used ^SPX and wrote SPX in my query just for simplicity

So does that mean your issue is resolved?

Actually no, but I walked around using pandas datareader and pulling SPX
data from stooq. Wonder why can't do the same with yfinance.
Il mer 14 ott 2020, 15:59 Lazaro Hurtado<EMAIL_ADDRESS>ha
scritto:

So does that mean your issue is resolved?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ranaroussi/yfinance/issues/477#issuecomment-708422204,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABX6YBXT5TEQUAH5BYWGAJDSKWVDJANCNFSM4SPFNDLQ
.

What exactly are you doing to call .info on SPX and what are you trying to get?


arrow doesn't work on the first step on the flow

flow

go to https://staging.fightpandemics.work/
click on need help
click on the back arrow
back arrow doesn't work on the first step on the flow

Back button works while running on localhost, is https://staging.fightpandemics.work/ running latest code?

Staging
When a pull request is merged to master, it will automatically be deployed to the staging environment. You can view the build logs in GitHub Actions. After the build successfully completes, wait a few minutes for the changes to be reflected, and then access the staging app at http://staging.fightpandemics.work.

seems staging would always be automatically updated when merging a PR

Seems to work now, this was recently fixed, maybe it wasn't deployed that at the time of creating this issue...


feat(adshield): mitigate

https://listauthorschat.slack.com/archives/C010PK19W78/p1667827993654519

Merging immediately as crucial.


Add documentation for proxy pass through flag

@tomakehurst Added documentation for proxy pass-through flag feature. Needs a review.

Looks good, thanks!


migrate usages

Update of the font size ramp (2/3).
Divided the task into 3 parts to separate the changes:

Update font-size ramp.
Migrate usages in Dialtone.
Update Utilities page and migration guide.

This PR covers part 2.
Migrated usages in dialtone following the mapping described in the jira ticket https://dialpad.atlassian.net/browse/DT-641.
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[ ] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[ ] Ensure all gulp scripts successfully compile.
[ ] Update, remove, or extend all affected documentation.
[ ] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Boy, that was a doozy to review. All the search-and-replacing. Since this solely updated the size ramp, a step behind the Font Stack update, we'll get a more true visual impact of how everything renders. To that end I did pull this PR locally, temporarily changed the Font Stack to SF Pro and it's looking great.
The key to success of this task will be extending the Migration Guide, https://github.com/dialpad/dialtone/blob/dt-641-update-font-size-ramp-migration/migration_guide/MIGRATION_GUIDE.md, presumably in forthcoming PR 3 of 3.

Thanks for reviewing, it should be updated with the font stack change.
Yeah part 3 is here https://github.com/dialpad/dialtone/pull/674 and updates the utility page and adds the migration guide.
Will merge this PR into the dt-641-update-font-size-ramp main branch and once part 3 is good to go will merge that too.


WIP: DO NOT MERGE: Demo that some tests do not run

This is a demo for another pull request. Please do not merge.

Okay, the linter complains but rspec passes :smiley_cat:


Implement box around expanded operations

This PR implements rendering a box around expanded operations.

To do this, this PR:

Adds a new ConditionalRender.AsGroup enum type to have an operation be visualized as an expanded group of its children gates
Adds 2px of padding to nested groups
Fixes some tests for classically-controlled and implement tests for grouped operations
Rework how expanding and collapsing gates work in visualizer.ts that manages the logic for expanding/collapsing gates onclick

As this is my last few minutes before I sign off on my internship, please reach out to me on my personal email if there is any feedback and I can contribute further as an open-source contributor! :D

@theRoughCode Sorry for the delay in reviewing this! Looks good to me, though. I've tested it locally and things look good, so I'm happy to merge this. I'm going to retarget this PR to the feature/visualization-improvements branch, as that is where we'll continue the work on the overall visualization/debugging experience and get it ready to release.

Sounds good! Looking forward to the release ☺


Delete campaigns

Describe the Request
please, the three campaigns to be deleted and
make the table rows 20 per page.
To Reproduce

Which browser are you using? (if relevant)
No response

fixed with: https://github.com/podkrepi-bg/api/pull/417 and deployed on prod


Add Cahak George to Contributors list

Hi  @cahakgeorge, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Thanks. Will check it out


[FR] Introducing keyword shortcuts

Checklist / 检查清单

[X] No one has submitted a similar or identical feature request before. / 之前没有人提交过类似或相同的功能请求。
[X] This suggestion does not depart from the original intention of LibChecker. / 这个建议不会背离 LibChecker 的初衷。

Enhancement propose / 改进目的
When input some keywords to filter apps list, providing a banner area to make user able to create a shortcut that can easily reuse the keyword later.
Solution / 解决方案

Additional info / 额外信息
No response

Keyword shortcuts only for app list? or also for searching through the native libraries, Services, Activities, Permission, etc. ?

Keyword shortcuts only for app list? or also for searching through the native libraries, Services, Activities, Permission, etc. ?

I think both will be nice. But app list first.

⌘

This will be a new tab in home page. Users can create a bundle which contains some apps filtered by conditions users specify.
Such as searching keywords, target sdk version, abi type, etc.


images: install ccache in builder.

I'd like to cache bpf builds in development environments.

Aha, this needs to be a fork on the same repo. Closing.


[Feature]

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
my project originally used skywalking v8.2,now it upgraded to v9.3,when i query rest api like unsuccessfulservice,this problem occurred.
Elasticsearch exception [type=index_not_found_exception, reason=no such index [swnine_service_sla]]
(swnine is sw_namespace)
I wonder if switch to another index something changed
The existing indexes are as follows：swnine_records-all，swnine_zipkin_span，swnine_log，swnine_metrics-all，swnine_browser_error_log，swnine_ui_template，swnine_segment
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

hi, Have you solved the problem yet？


Add docs to describe the steps required to configure a vite build target for Custom UI projects

Refer to  https://github.com/toolsplus/nx-forge/issues/61#issuecomment-1907035176_ for details.

Working through this on the v17 branch worked well. There was a change that was needed to the vite.config.ts file. I had to add base: './' similar to the change that is needed in webpack config files.


Feature/BOAS 313 case details project information

Describe your changes
Case Details - Project Information page
BOAS-313 Case Details - Project Information
https://pins-ds.atlassian.net/browse/BOAS-313
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


optimize: remove variable deepest and reduce duplicate judgment

Ⅰ. Describe what this PR did
1.(null instanceof Object) always be false
2. Depth has been judged by RollbackRule.getDepth(ex)
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1946 into develop will increase coverage by 0.03%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #1946      +/-   ##
=============================================
+ Coverage      55.12%   55.15%   +0.03%
- Complexity      2402     2403       +1
=============================================
  Files            429      429
  Lines          14261    14259       -2
  Branches        1673     1673
=============================================
+ Hits            7861     7865       +4
+ Misses          5693     5691       -2
+ Partials         707      703       -4

Impacted Files
Coverage Δ
Complexity Δ

...a/io/seata/tm/api/transaction/TransactionInfo.java
100% <100%> (+4.76%)
12 <0> (-1)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
48.41% <0%> (+0.39%)
28% <0%> (+1%)
:arrow_up:

...in/java/io/seata/server/session/GlobalSession.java
85.02% <0%> (+0.48%)
68% <0%> (+1%)
:arrow_up:

...server/store/file/FileTransactionStoreManager.java
57.46% <0%> (+0.95%)
29% <0%> (ø)
:arrow_down:

sorry, just thought if roolbackrule and noroolnack has father and son exception, smallest win will useful

update test for showing smallest winner feature