kinit fails authentication when gMSA password contains an embedded newline

Since the the credential-fetcher renews the gMSA Kerberos Ticket by piping the gMSA password to kinit, if the gMSA password contains an character with a value of 0x0A (i.e. an embedded newline character), then the input to kinit is prematurely aborted and the authentication fails.

Hi @ebekker ,
Could you contribute a PR ?
We could also have a hands-on session as well, if you like.

Hi,
I'm afraid it's been quite some time since I've done any C++ programming, so unlikely I could contribute a PR. :-)
However, the reason I stumbled upon this was that we has a very similar setup in our environment and we specifically ran into this very issue, so I was curious how others may have been addressing it.  I'm happy to say that we did solve it, and I'm happy to share our approach.
A little background on our setup which is a little bit different -- we're not trying to use gMSA accounts inside containers, but simply using them on AD-joined Linux hosts.  But the credential resolution and ticket renewal process is fundamentally the same as yours.  Also our solution is primarily based on PWSH.
Initially, we too were piping the retrieved and decoded gMSA password to kinit via its STDIN.  But just so happens the auto-managed password for one of our accounts recently got rotated and has an embedded 0x0A character value within.  Our initial approach quickly broke, and we were fortunate that it happened in a pre-PROD environment.
While we researched a few different approaches, including modifying and rebuilding some of the krb5-workstation tools packaged with AL2 to accommodate alternate input methods -- in the end a more simpler approach was just to adjust our invocation of kinit to use its built-in mechanism for taking in credentials via a keytab file instead of its STDIN.  And then the only challenge was to generate the keytab from within our scripts, but that was relatively easy thanks to this package which contains programmable support for creating, reading and writing keytab files.
If you would like more details or more discussion, happy to expound...

Hi ebekker,
we will like to know more about how you created gMSA account, we tried to mimic the behavior with almost 500 service account and didn't see any failure. We will be happy to help you to resolve this issue

@ebekker

If you would like more details or more discussion, happy to expound...

Yes,  we would love to discuss over a conference call, my email is samiull at amazon

So just to be perfectly clear, I want to make sure you're aware, we are not currently using your tools from this repository.  We have a similar tool we developed and it just so happens it works in very similar fashion.  And to clarify -- we no longer have "an issue" that needs resolving, we solved our problem by switching to the use of a keytab file.
I'm only continuing this discussion because I think that your tool has the potential for a similar problem.  It makes sense that you may not have run into the issue in your tests, as the range of possible characters in the Unicode alphabet is 2^16, so testing over 500 accounts could very well have still missed this one scenario.  And it is exactly 1 character in 2^16 that is the problem -- it's the newline character, any other will be fine.
But to clarify things and provide a sample of what we ran into, I created this repo  which contains a description of what I call the "bad password" scenario.  It also contains a sample of the LDIF result containing the msDS-ManagedPassword blob of the bad password that's caused the issue.
If you would like to setup a test with your tools, you can inject this encoded managed password blob into your find_password routine and exercise your tests to see if you run into this issue or not.
Let me know if you would still like to connect, I'll be happy to setup some time next week to discuss.

Thanks, I saw this late.
We will incorporate your repo  as a self-test.
Regarding implementation, we cannot add bundle dlls or binaries, but we will have to find another way.
I will keep this issue open until that time.
If you have time this week, we would love connect with you.


[BUG] o1-mini model not supported

Describe the bug
Attempting to use the Azure OpenAI o1-mini model results in the exception:
pf.flow.node_test failed with UserErrorException: Exception: OpenAI API hits BadRequestError: Error code: 400 - {'error': {'message': "Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.", 'type': 'invalid_request_error', 'param': 'max_tokens', 'code': 'unsupported_parameter'}} [Error reference: https://platform.openai.com/docs/guides/error-codes/api-errors]

How To Reproduce the bug
Configure a tool to use an instance of o1-mini. Execute it.
Expected behavior
The model responds.
Screenshots
pf.flow.node_test failed with UserErrorException: Exception: OpenAI API hits BadRequestError: Error code: 400 - {'error': {'message': "Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.", 'type': 'invalid_request_error', 'param': 'max_tokens', 'code': 'unsupported_parameter'}} [Error reference: https://platform.openai.com/docs/guides/error-codes/api-errors]

Running Information(please complete the following information):

Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
Operating System: [e.g. Ubuntu 20.04, Windows 11]
Python Version using python --version: [e.g. python==3.10.12]

{
  "promptflow": "1.16.0",
  "promptflow-azure": "1.16.0",
  "promptflow-core": "1.16.0",
  "promptflow-devkit": "1.16.0",
  "promptflow-tracing": "1.16.0"
}

OSX 14.4, python==3.10.13

Bump to prevent automatic closure

Bump to prevent closure again, I'm still interested in this


test framework: don't require UID 1 for echo container

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@dgn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
f0a50f904112e1afa7cadbf4e714d47d275e657d
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

doesn't this mean it will run as root by default? I think someone added this so it does not run as root

Or if you have a PSP to say run as UID X-Y it will automatically assign one? Not very familiar with PSP

Oh, that changes things. Yes, PSPs restrict to UID and will not allow pods with containers where runAsUser=0 - but on OpenShift, you'll usually be assigned a random one automatically, and if you specify one that isn't in the range, it fails.

I just checked: PSPs with runAsUser restrictions will reject illegal UIDs but also default to the first UID in the legal range: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#users-and-groups

Got it, we may have previously explicitly set to 0 before which prompted
the PR to change to 1. Sounds like this should work ok. Thanks
On Wed, Jun 24, 2020 at 8:12 AM Daniel Grimm<EMAIL_ADDRESS>wrote:

I just checked: PSPs with runAsUser restrictions will reject illegal UIDs
but also default to the first UID in the legal range:
https://kubernetes.io/docs/concepts/policy/pod-security-policy/#users-and-groups
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/24942#issuecomment-648882250, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPE2NGDKCHPKNIERPLRYIJXFANCNFSM4OGSIVLA
.

Thank you for checking!


Add Q_ID to Typecast

Please have two api calls.
The original api(args...), without the queue_id, that calls the one that requires the queue_id by setting queue_id to 0?
api(args...)
api(queue_id, args...)
This is better than having a default argument for queue_id.

In progress now

Implemented here
https://github.com/tenstorrent/tt-metal/pull/9146/files
Not merged yet, test found an issue with typecast itself

Completed here
https://github.com/tenstorrent/tt-metal/pull/9146


feat: add creating_txhash and spending_txhash to /transaction.get and /transaction.all txoutputs

Closes #1162
Overview
Add inputs.*.creating_txhash and outputs.*.spending_txhash to /transaction.get, /transaction.all and /transaction.create
Originally intended for /transaction.get but since the serializers are shared between endpoints, why not let them be consistent.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Add transaction_factory/0 and txoutput_factory/0 test data factories
Add :creating_txhash and :spending_txhash to Serializer.Base.to_utxo/1
Refactored /transaction.get away from complex fixtures setup and towards test data factories

Performance impact
Data is already there. This PR simply puts the data on to the API response so there should be minimal perf impact. Response size gets slightly larger.

Coverage decreased (-16.6%) to 70.935% when pulling cc44c8dd488df0d3054925d230d38271ceb1e4e6 on 1162-txoutputs-txhash into 40f899bc32797bc1ff3f286aef2b4c11f586af5c on master.

Have you missed update the swagger specs?

Addressed in https://github.com/omisego/elixir-omg/pull/1224/commits/c2c9ae36513b495d787860035ef01ae8dcdf3b09. I need to get better at this 🤦♂

Main thing though is, I hope we can avoid introducing random test data into tests as that often leads to flaky tests. Due to the randomness of tests using random data, an exact test failure or success is not repeatable. I don't see the random values in this PR directly causing problems, but who knows....and the random values don't seem to provide any specific benefits here, so I'd rather the test data be predictable and the test runs reproducible.

I have to disagree here. Random test data in the cases I use for this PR is to mimick closer to production value. E.g. the hashes. It should be beneficial if we see flaky tests arising from these random data.

(also got me wondering if ExMachina provided utilities for generating sequences, but omitted random value utilities on purpose)

Because that random function can be used/built easily from existing Elixir core library.

Does insert(:transaction) work ok in this PR given the DB key constraints, but the nil transaction block?

Interesting this does work per current code.
@pnowosie Seeing you're the original committer for<PHONE_NUMBER>1706_create_transaction_table.exs, do you have some context on the TODO there?

The UTXO being created in this factory gets its blknum from blknum: insert(:block).blknum. But will that be the same blknum as the transaction that created it? creating_transaction: insert(:transaction) is called, but the default transaction factory set its block to nil.

Correct sequencing of blknum, txindex, oindex. Eg: if we want to create a deposit then is_deposit(blknum, txindex, oindex)` should return true.

I'm supportive of finding a better middleground between business-valid vs primitive factories. Agreeing they're a little too primitive. But there's not enough test code using these factories to experiment I think. Happy to revisit this say after /deposit.all is merged though. 🎉

Main thing though is, I hope we can avoid introducing random test data into tests as that often leads to flaky tests. Due to the randomness of tests using random data, an exact test failure or success is not repeatable. I don't see the random values in this PR directly causing problems, but who knows....and the random values don't seem to provide any specific benefits here, so I'd rather the test data be predictable and the test runs reproducible.

I have to disagree here. Random test data in the cases I use for this PR is to mimick closer to production value. E.g. the hashes. It should be beneficial if we see flaky tests arising from these random data.

txbytes and metadata are not random data and have a specific encoded format, so I not sure how well random data mimics it.
Also if we want to make use random data are we drawing a clear line of when and where to use it? owner: owner.addr could also be random.

Summary here from my perspective...about using random data in these types of tests or not, I feel ok to agree to disagree for now. Definitely not a blocking.
The only blocker for me that I'd still like to see addressed are the comments about the factories... https://github.com/omisego/elixir-omg/pull/1224#discussion_r360647704
If get can align on that, then this PR is 👍 .

txbytes and metadata are not random data and have a specific encoded format, so I not sure how well random data mimics it.

In the context of WatcherInfo.DB and downstream usage, I think they're pretty random. E.g. we don't & shouldn't be deriving data from those fields. If needed, those derivations need to be done before it enters WatcherInfo.DB. So for these tests I think it's closer to random binary.
However, if we're intending these factories to be used out of WatcherInfo.DB, you have a good point which also defeats the use of both sequential and random data 😅 I don't think that's the plan though. If we do so then we'll need new factories independent of OMG.WatcherInfo.DB.* schemas so I think we can keep it the way it is.

The only blocker for me that I'd still like to see addressed are the comments about the factories... #1224 (comment)

Agreed on using build and avoid insert within factory implementations. 👍 Updating now.


Broader CI/Docker usage support

Is your feature request related to a particular use-case?
The usecase is running cargo-spellcheck in my CI system, which is based on Drone.
I'm using the official rust:latest Docker image to run the step in which I'm trying to get cargo-spellcheck to work.
A clean build attempt of cargo-spellcheck can take over 15 minutes (on hertzner cx21 = 2vCore 4GB RAM) and fail due to dynamic library linking errors which weren't as trivial as just apt-get installing hunspell.
Trying to just download the precompiled release binary also fails due to being linked against a newer GLIBC version I think.
Additionally means that using the slimmer rust:alpine docker image is also out of question because of the GLIBC requirement.
Describe the solution you'd like to implement/see implemented

Make prebuilt releases against x86_64-unknown-linux-musl.

Seemed to work on my system after doing a hacky workaround sudo ln -s /usr/bin/g++ /usr/bin/musl-g++, which was from rust-musl-builder which could be used too most likely for the building

Provide a Docker image for cargo-spellcheck.

While it'd be better for my use case, I think that just providing a musl binary would potentially be more applicable for other possible similar use cases. Though both would be even more awesome than just picking one :)
Describe alternatives you've considered

Build against an older GLIBC version
Look into if making cargo-spellcheck properly supported by cargo-quickinstall/cargo-binstall would solve the glibc issues
Document the solution to the compilation/linking issues in the official rust docker image, and accept waiting for the CI runs to compile cargo-spellcheck

Additional context
Relates to #241

I do have container build envs ready to produce musl artifacts and as a consequence alpine based containers.
Commonly, I'd create a CI pipeline for the base container of your projects CI pipeline. That's what I do.
I don't quite remember how drone CI works though, so that might not be applicable.
Regardless, I think it'd be a good addition and avoid needlessly burnt CPU time, so I'll take a stab at it soon™

I don't quite remember how drone CI works though, so that might not be applicable.

With the docker runner each step just runs commands in the specified docker container, so yes it'd be applicable 😄

Commonly, I'd create a CI pipeline for the base container of your projects CI pipeline.

Yeah, that could be one optimal solution in the end for my specific use case, which I've just not gotten around to.
Doing that would result in the same issues when building that base pipeline container regardless though.
And if that'd be accepted as the solution, it would mean that everyone who wants to use cargo-spellcheck in a Docker container would still need to do the same & re-discover the steps required for getting it to work.

This is non trivial, mostly due to the fact that the musl-gcc wrapper only suppers C but not C++ and some other shenengians, which brought me down the alpine container road, but the resulting build.rs of that crash with sigsegv 11 😵💫

Alright, it seems a series of patches is required to rustc, which the packaged alpine has. So it only needs some more CI love for the release pipeline.

@ljoonal please take a peek at 0.12.2 there are musl binaries now :) I didn't test them yet, so be warned

Yep, seems to run successfully on the rust:alpine image 😄
As an additional note, installation via cargo-binstall seemed to also work successfully on the rust:latest images somehow whilst manually downloading/compiling didn't.


zitadel: 2.37.2 -> 2.40.2

Description of changes
Update zitadel from 2.37.2 -> 2.40.2.
Changelog at Github Releases page
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 265143 run on x86_64-linux 1

1 package built:

zitadel

@ofborg build zitadel

Darwin build broken, mark it broken with a comment ECONNRESET Client network socket disconnected before secure TLS connection was established


Add a contract example for a bidding game

@VictorCMiraldo this is ready for a review. Let me know if you'd prefer to do this on a call.

@facundominguez, I think maybe it should be the rest of the team deciding what to do w.r.t. archiving older contracts to be honest. My main point for keeping them out of the repo is the maintenance cost when either we make a breaking change on cooked or there are breaking changes from plutus. Given that @carlhammann is now our in-house expert, his decision on this is important too.

Moving sounds good to me.

Closing this as this is outdated and examples are now in cooked-smart-contracts.


usage of deprecated hook

this hook got deprecated in prestashop 8.0
https://github.com/PayU-EMEA/plugin_prestashop/blob/1476d947babb3770f56835ae21d9fe4528de0095/payu/payu.php#L2031
it should be replaced with this one

Fixed in 3.2.11


Form Validation

Your framework is amazing but it would be better if it came bundled with a class based form validation library ie https://github.com/draganbabic/uni-form

Another option HTML5 form validation with polyfills

I may fork this and integrate uni-form during the coming week.


ionic tabs not work good!

Hi,
when I click the tab,it comes to be this!and errors in the chrome console!
thank you for help!

I've had a pull request to fix this for like a week.
https://github.com/Urigo/meteor-ionic/pull/47
The package's dependencies need to be updated.

@babakness thank you！

Addressed here:  https://github.com/Urigo/meteor-ionic/pull/47#issuecomment-113951360
@train860 if you just do
meteor update

for now, does it work?

@Urigo thank you for response!
I use "meteor update",but error happened.information is here：
While downloading<EMAIL_ADDRESS>error: socket hang up
so，I change to a new project，use “meteor add urigo:angular”。I works，but the version is a older one：urigo:angular    0.8.12*
cannot use “meteor add urigo:angular” to get the latest version？

@train860 very strange... looks like a network error no?

@babakness did meteor update worked for you?

@Urigo should be network error！but，why cannot get the latest version by meteor add

I guess that's happens when you add urigo:ionic before urigo:angular?
If that's the case the reason is that Meteor's version solver takes the lowest possible versions that is supported by the rest of the packages.
Can you try loading urigo:angular as the first package of the app and see if it is still takes an older version?

Yep!I get the last version of urigo:angular,but the same error happen……
Is it because of my angular:angular-animate  package version？

I have  resolved this problem by update angular:angular-animate and angular:angular-sanitize to the last version directly！
thank you very much！

Yes I can see why, When for the version solver, specifying a version means that's the highest version that that package was tested with.
I"ll merge the pull request and release a new version later today.
@train860 and @babakness , thank you

Released 1.0.0_1 with updated dependencies, can you check this out?

I works now! nice work!!!


optional no-cone support, adjust minimum version of git lower

Right now, we enforce the version 2.37.0. As I was working through ensuring git is present on our docker images, I realized that 2.37.0 is literally the latest version of git.
I am not comfortable with mandating that folks need to be on the very latest of ANY tool to run our tool. We should make the inclusion of --no-cone optional and based off a quick git --version check at Startup. This way we can require a version of git that has sparse-checkout, but relax on the no-cone side.

@scbedd versions < 2.37 still support both --cone and --no-cone flags, so our sparse checkout logic works in either case. The only change in 2.37.x is that cone mode is the default when no mode is specified (it used to be no cone). So the git commands will work exactly the same whether git 2.36 or 2.37 is installed as long as you manually specify --no-cone.

@benbp excellent! So we're future proofed by always specifying!  (cause that's what we do rn)
That means that we just need to relax the version check to one that supports sparse checkout.

@scbedd it may be worth investigating the perf of some of the 2.2 versions vs. 2.3. Sparse checkout has been around for a while, but they've been adding a lot more sparse index improvements and command support to git since then, so the differences may be big enough that it's worth setting a higher minimum bar.


Angular JS resources

#13

I think this one is good since its curated. Books are the acceptable once I will accept this since it will help others for further research 👍

Star the repo too :D

done!


MGDCTRS-512: UI component for DBZ connector edit flow

Jira issue https://issues.redhat.com/browse/MGDCTRS-512

tested locally. Looks good!


Stabilise the API

Once everything is stable, we should mark the API as being stable.
This will mean enabling mutation testing (#134) on all builds in CI, and also changing all API guardian @API annotations that are currently setting the status attribute as EXPERIMENTAL so that they are STABLE instead.
INTERNAL annotations should stay how they are.

Hi as #134 is done what about this issue? Can you guide on this one i want to contribute more

Hmm, you could pick this up, yeah. Think it is a good time to be doing it.
Go for it.

Hmm, you could pick this up, yeah. Think it is a good time to be doing it.
Go for it.
It is just a case of finding
@API(since = ..., status = Status.EXPERIMENTAL)

and replacing with
@API(since = ..., status = Status.STABLE)

...we want to keep anything marked as INTERNAL as it is though.


Remove repo.remove (or fix it, if it's still useful)

when I call the .remove() function, I keep getting these errors:
POST https://api.github.com/repos/Pomax/gh-blog/git/trees?1393981519258 422 (Unprocessable Entity) api.github.com/repos/Pomax/gh-blog/git/trees?1393981519258:1
POST https://api.github.com/repos/Pomax/gh-blog/git/commits?1393981519451 422 (Unprocessable Entity) api.github.com/repos/Pomax/gh-blog/git/commits?1393981519451:1
Uncaught TypeError: Cannot read property 'sha' of undefined

The network responses for the failed URLs are
{
  "message": "Must supply tree.sha or tree.content",
  "documentation_url": "http://developer.github.com/v3/git/trees/#create-a-tree"
}

and
{
  "message": "Validation Failed",
  "documentation_url": "http://developer.github.com/v3/git/commits/#create-a-commit",
  "errors": [
    {
      "value": null,
      "resource": "Commit",
      "field": "tree",
      "code": "missing"
    }
  ]
}

respectively.

Remove() or Delete() doesn't work for me. They actually behave the same and give me the same error "Uncaught SyntaxError: Unexpected number" in the browser when calling this method. Any update on this? Would really appreciated.

Huh. I just opened #175, given I ran into repo.remove and repo.delete while improving test coverage. Do we need both of these? Or will one working "remove a file or blob from a repo" function suffice? If so, which should it be called, and should the other be preserved in some capacity for backwards compatibility?

This thing generates so many issues and I want it fixed yesterday. Giving it P1 for next release.

This is fixed by c895f.

For future reference, I ended up removing repo.delete (did the exact same thing as repo.remove but was an uglier implementation) and aliased it to repo.remove.


VS19 CMake errors

Os: Windows 10 V10.0.18362 build 18362
Visual studio: 19 V16.5.0
Azure SDK for VS: 20.01
After creating a new project (example blink) or opening the sample, under the run menu (green arrow for running programs) I see no device
also I get a lot of CMake errors
Errore		CMake Error: Could not find cmake module file: C:/Users/Reloa/OneDrive/Reply/Azure Sphere - XCH20/AzSphere Reply Smart Valve V3/out/ARM-Debug-4/CMakeFiles/3.16.19112601-MSVC_2/CMakeReplyCompiler.cmake
Errore		CMake Error: CMAKE_Valve_COMPILER not set, after EnableLanguage
Errore		CMake Error: Could not find cmake module file: CMakeV3Information.cmake
Errore		CMake Error: Could not find cmake module file: CMakeDetermineReplyCompiler.cmake
Errore		CMake Error: CMAKE_Smart_COMPILER not set, after EnableLanguage
Errore		CMake Error: Could not find cmake module file: CMakeReplyInformation.cmake
Errore		CMake Error: Could not find cmake module file: C:/Users/Reloa/OneDrive/Reply/Azure Sphere - XCH20/AzSphere Reply Smart Valve V3/out/ARM-Debug-4/CMakeFiles/3.16.19112601-MSVC_2/CMakeValveCompiler.cmake
Errore		CMake Error: CMAKE_V3_COMPILER not set, after EnableLanguage
Errore		CMake Error: Could not find cmake module file: CMakeValveInformation.cmake
Errore		CMake Error: Could not find cmake module file: CMakeDetermineValveCompiler.cmake
Errore		CMake Error: CMAKE_Reply_COMPILER not set, after EnableLanguage
Errore		CMake Error: Could not find cmake module file: C:/Users/Reloa/OneDrive/Reply/Azure Sphere - XCH20/AzSphere Reply Smart Valve V3/out/ARM-Debug-4/CMakeFiles/3.16.19112601-MSVC_2/CMakeV3Compiler.cmake
Errore		CMake Error: Could not find cmake module file: CMakeSmartInformation.cmake
Errore		CMake Error: Could not find cmake module file: CMakeDetermineV3Compiler.cmake
Errore		CMake Error: Could not find cmake module file: C:/Users/Reloa/OneDrive/Reply/Azure Sphere - XCH20/AzSphere Reply Smart Valve V3/out/ARM-Debug-4/CMakeFiles/3.16.19112601-MSVC_2/CMakeSmartCompiler.cmake
Errore		CMake Error: Could not find cmake module file: CMakeDetermineSmartCompiler.cmake
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Smart_COMPILER		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Valve_COMPILER		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Reply_COMPILER		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_V3_COMPILER_ENV_VAR		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_V3_COMPILER		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Smart_COMPILER_ENV_VAR		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Valve_COMPILER_ENV_VAR		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_Reply_COMPILER_ENV_VAR		C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\Missing variable is
Errore		CMake Error at C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt:5 (project):
  No CMAKE_Reply_COMPILER could be found.

  Tell CMake where to find the compiler by setting the CMake cache entry
  CMAKE_Reply_COMPILER to the full path to the compiler, or to the compiler
  name if it is in the PATH.	AzSphere	C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt	5
Errore		CMake Error at C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt:5 (project):
  No CMAKE_V3_COMPILER could be found.

  Tell CMake where to find the compiler by setting the CMake cache entry
  CMAKE_V3_COMPILER to the full path to the compiler, or to the compiler name
  if it is in the PATH.	AzSphere	C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt	5
Errore		CMake Error at C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt:5 (project):
  No CMAKE_Valve_COMPILER could be found.

  Tell CMake where to find the compiler by setting the CMake cache entry
  CMAKE_Valve_COMPILER to the full path to the compiler, or to the compiler
  name if it is in the PATH.	AzSphere	C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt	5
Errore		CMake Error at C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt:5 (project):
  No CMAKE_Smart_COMPILER could be found.

  Tell CMake where to find the compiler by setting the CMake cache entry
  CMAKE_Smart_COMPILER to the full path to the compiler, or to the compiler
  name if it is in the PATH.	AzSphere	C:\Users\Reloa\OneDrive\Reply\Azure Sphere - XCH20\AzSphere Reply Smart Valve V3\CMakeLists.txt	5

PS: I had to set AzureSphereDefaultSDKDir because it was not setted by the installer, also there is something else missing?

@Raffa50, happy to help! Please share a link to the Azure documentation you are referencing and we can investigate futher.

@Raffa50 Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

@Raffa50 We have noticed that you also created an issue on the GitHub Sample repo and Product team is already helping you. Please continue your discussion there to avoid duplicate efforts.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Update: This issue is fixed by setting system variables:
AzureSphereDefaultSDKDir
AzureSphereTargetApiSet


Integration of MorphStore operators

In GitLab by @EricMier on Mar 21, 2022, 16:52
Goals
Enable the use of existing data processing operators of MorphStore, an in-memory columnar analytical query engine with a novel holistic compression-enabeld and highly-vectorized processing model.
Tasks

[ ] Add MorphStore as a new library
[ ] Create Daphne Kernels using MorphStore operators (wrapper + data format translation)
[ ] Create some test cases

More Information will follow.

Moved to #339.


Where do I put bowtie2-index files?

Bowtie2-build requests 16GB of memory which causes the run to crash. I can build the indexes myself, but where do I put the files so that the pipeline does not execute bowtie2-build? Alternatively, how can I customize how bowtie2-build is executed?
Thanks, Jon

Hi @jonbra! Hope you are well! Providing your own bowtie2 indices isn't possible with v1.1.0 but it will be in the next release! Sorry, it is taking much longer than anticipated to get it out because we have been adding some cool new functionality and simplifying things substantially. Come find us on the #viralrecon channel on the nf-core Slack workspace. Be easier to have a chat about these sorts of things and get updates.

I see, thanks! (I could also fix this by reducing the --max_memory btw).


[GHSA-6gcg-hp2x-q54h] Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

Updates

References

Comments
Adding the patch link for v2.1.15: https://github.com/argoproj/argo-cd/commit/7357cfdb58a560de70a0538c6e3bef6fe39505ea
Adding the patch link for v2.2.9: https://github.com/argoproj/argo-cd/commit/5e767a4b9e30983330c0fdec322192281a90eb84
Adding the patch link for v2.3.4: https://github.com/argoproj/argo-cd/commit/d36d95dc9f71ec61c1a93794f81ece6d61a0d943
The GHSA-ID is the in the commit patch message: "Merge pull request from GHSA-6gcg-hp2x-q54h"

Hi there @jannfis! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


UI Lag

Especially prevalent in Harrowhold and raids, the UI will lag and stutter while trying to update. For example debuffs on p4 won't update live when you get them along with boss HP, character MP, etc.
Also the buff bar doesn't disappear when you tab out and stays wherever you placed it permanently.

Regarding buff bar not hiding when tabbing out, it's going to be fixed in next release.
About the lag, I haven't found the cause which leads stuttering and freezes yet. Also I haven't tested buff bar in HH yet. Anyway, restarting TCC before starting the fight seems to help in some cases.

Mkay sounds good.
And yeah I found that it typically happens after having it running for a while, perhaps a memory issue too because my ShinraMeter will crash due to it freezing/stuttering. But yeah, the buff bar lagging is probably also directly due to the rest of the UI lagging alongside it.
I don't know if you've experienced it too but also using the tray icon to select click-through crashes TCC pretty often.

Buff bar not disappearing and crash on selecting click-thru fixed in v0.1.1.


summary_table_fields ignored when aggregation is used

Hi,
I need to have a report printed on my alert for the following rule:
name: 'not 200 ok'

type: frequency

num_events: 3

timeframe:
  minutes: 5

use_strftime_index: true
index: logstash-httpd-access-%Y.%m.%d

doc_type: httpd-access

filter:
- term:
    fields.ssl_client_verify.keyword: "SUCCESS"
- term:
    fields.method.keyword: "POST"
- terms:
    fields.url_path.keyword: ["/first/path", "/second/path"]
- terms:
    fields.host_canonical.keyword: ["first_host", "second_host"]
- query:
   query_string:
      query: "NOT fields.http_status:200"

raw_count_keys: False
summary_table_fields:
    - sys.id
    - fields.url_path
    - fields.http_status

alert:
    - email

email:
    -<EMAIL_ADDRESS>
alert_subject: "PROBLEM!!!"

This works. but if I modify it in the following way (notice the aggregation), the report is not printed on the alarm:
name: 'not 200 ok'

type: frequency

num_events: 3

timeframe:
    minutes: 5

use_strftime_index: true
index: logstash-httpd-access-%Y.%m.%d

doc_type: httpd-access

filter:
- term:
    fields.ssl_client_verify.keyword: "SUCCESS"
- term:
    fields.method.keyword: "POST"
- terms:
    fields.url_path.keyword: ["/first/path", "/second/path"]
- terms:
    fields.host_canonical.keyword: ["first_host", "second_host"]
- query:
   query_string:
      query: "NOT fields.http_status:200"

aggregation:
  minutes: 5

raw_count_keys: False
summary_table_fields:
    - sys.id
    - fields.url_path
    - fields.http_status

alert:
    - email

email:
    -<EMAIL_ADDRESS>
alert_subject: "PROBLEM!!!"

Any suggestions? Bug?

@amraam83
If you see any alerts less than five minutes it won't trigger, you have to wait for 5 minutes to get the alerts.
I see that you have set the time frame: and aggregation: to five minutes. Even if you get any alerts in less than five minutes you have to wait for the aggregation time to complete to get the consolidated alerts.
aggregation: This option allows you to aggregate multiple matches together into one alert. Every time a match is found, ElastAlert will wait for the aggregation period and send all of the matches that have occurred in that time for a particular rule together
You can monitor the alerts using below command. Hope this helps !!!
python -m elastalert.elastalert  --start NOW --verbose --rule rule_name.yaml

Add --verbose to the command if you have not already. You'll see lines like
"New aggregation for ... next alert at <5 minutes from now>"
and
"Adding alert for ... for aggregation ID: xxxx"
If you want until that "next alert time" passes, it will send them


Add wrk HTTP benchmarking tool to debug base image

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed


updated contact.md

Update to I'm a Developer! Section

Added a link to the new Discord channel, since Gitter is not being used.  This way newcomers won't have to join Gitter to read the message that we have moved to Discord.

 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.:x: DoctaCloak sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@DoctaCloak looks like you added your edits to the end of the file instead of updating the existing text

Made changes.  @riknoll  😃

Could you switch the link to https://aka.ms/makecodecommunity ? Otherwise looks good!

Done @riknoll  🙂 By the way, how do you generate a link like aka.ms?

It's Microsoft's internal URL shortening service. Sorta like Google's goo.gl


Download causes Timeout exception

Package
dio
Version
5.3.3
Operating-System
Android
Output of flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on macOS 13.5.2 22G91 darwin-arm64, locale de-DE)
    • Flutter version 3.13.6 on channel stable at /Users/patrick/development/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (8 weeks ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/patrick/development/sdks/android
    • Platform android-34, build-tools 33.0.2
    • ANDROID_SDK_ROOT = /Users/patrick/development/sdks/android
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 76.0.4
    • Dart plugin version 232.9559.10

[✓] VS Code (version 1.84.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)         • emulator-5554             • android-arm64  • Android 12 (API 32) (emulator)
    • iPhone von Patrick Schmidt (mobile) • 00008110-000449CE2699801E • ios            • iOS 17.1.1 21B91
    • macOS (desktop)                     • macos                     • darwin-arm64   • macOS 13.5.2 22G91 darwin-arm64
    • Chrome (web)                        • chrome                    • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources
    • All expected network resources are available.
• No issues found!

Dart Version
3.1.3
Steps to Reproduce

Create a Dio.download() request with a receiveTimeout set that will trigger (In my case the download takes 10s so I set it to 3s).
Start downloading the file.

Expected Result
As stated in the readme and the code itself, dio should only throw a TimeoutException based on the receiveTimeout defined "timeout during data transfer of each bytes and not the overall timing during the receiving.".
Therefore, the download should finish without any issue since bytes are constantly received.
Actual Result
The download is stopped due to a TimeoutException of the receiveTimeout. However, using the onReceiveProgress callback of the download method, I can see that progress and therefore bytes are received constantly.

As I stated in https://github.com/cfug/dio/pull/2029#issue-1989265472 (additional context).

As I stated in #2029 (comment) (additional context).

I don't understand how this is related to this problem. Do you mind explaining it to me?

We are currently trying to fix a couple things but it does not seem to be related directly.

As stated in the readme and the code itself, dio should only throw a TimeoutException based on the receiveTimeout defined "timeout during data transfer of each bytes and not the overall timing during the receiving.".

I was not aware of this and I have not seen any code which would support this.
AFAIK, the receiveTimeout is measured until the first frame/chunk is received.

Could you provide a reproducible URL or example?

Could you provide a reproducible URL or example?

Sure,
here is a somewhat minimal example, downloading one of the repos of cfug. You might need to adjust the timeout, for my connection 5 sec is enough to trigger the behavior.
void dummyDownload() async {
  final tmpDir = await getTemporaryDirectory();
  final File file = File('${tmpDir.path}/dummy.zip');

  var dio = Dio(BaseOptions(
    connectTimeout: Duration(seconds: 5),
    receiveTimeout: Duration(seconds: 5),
  ));

  // Some file that is rather "large" and takes longer to download
  var uri = "https://github.com/cfug/flutter.cn/archive/refs/heads/main.zip";

  var response = await dio.download(
    uri,
    file.path,
    onReceiveProgress: (received, total) {
      print('Received: $received, Total: $total');
    },
  );
  print('Download is done: ${response.statusCode}');
}

Sure, here is a somewhat minimal example, downloading one of the repos of cfug.

Thanks. I can easily reproduce the issue with your example.

This is caused by a duplicate timeout handler in the DioForNative.download implementation.
https://github.com/cfug/dio/blob/6e83a1181bc2afe2ff9b19736223d7e6a7ea6247/dio/lib/src/dio/dio_for_native.dart#L183-L190


Don't install lit 2 by default in context package

I missed this in this commit: https://github.com/lit/lit/pull/4287/commits/366e6b8525993d70a75154f5fa190ea2d8a5398d

Change description says "don't install" but this means "don't build"


Add a View > Targets menu item for non-proteomic UI modes.

Visible in Mixed and Small molecule modes only. Enabled only when the Targets window is not open.
Also, hide the View > Modifications menu item for small molecule UI mode.
This fixes:
Issue 791 Inconsistencies in Small Molecule UI mode make it difficult to reopen a closed Targets window
"From Brendan:
Bug found teaching Skyline Online. In small molecule mode, View > Proteins > etc. gets removed but not replaced with anything, which makes it confusing how to get the Targets window back if you close it. We should replace it with a View > Targets menu item that brings up the Targets view.
Also, we seem to leave View > Modifications > etc. in small molecule mode, when it doesn't apply to small molecules. It also brings up the Targets window. So, that was my easiest solution to getting the Targets window back after closing it, but the menu item should not be there. So we should be removing View > Proteins and Modifications and replacing them with View > Targets."

I figure the only likely design controversy here is the enable/disable of the menu item based on the Targets window visibility. I think it's good that users are made aware of its availability, but it would be confusing if it was left enabled when clicking on it would produce no action.
Some screen shots (note the UI modes)

Don't disable it when it is visible, just put a check next to it, and when you choose it and it is visible, it should still set the focus to the Targets view. It is an "Activate" command, and not a Show/Hide command, but we do put a check by it when it is visible to let the user know that Skyline thinks it is visible. So, if it is not immediately apparent, the user might want to search for it in a situation where there is a lot of screen real estate and the window may be floating and partially off screen.

So:

OK, I'll back out anything that directly messes with that settings value.

That sounds like more than I was suggesting. I just want you to put back 2 lines in your last commit. Using the View menu to show the Targets view changes the value today, and it should change the value for your View > Targets menu item. However, calls to SkylineWindow.ShowSequenceTreeForm(true) should not change the Settings.Default.ShowPeptides value, as it has not in the past. Your change to rely on visibility for the menu check mark was the right fix.

Agreed, I just meant to say no new manipulations. I think you'll find the current code meets your expectations, including having View>Targets available in all UI modes per our side conversation.


Projectors were not being applied

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

Project coverage is 77.80%. Comparing base (46a502f) to head (97146be).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #182      +/-   ##
==========================================
- Coverage   77.82%   77.80%   -0.02%
==========================================
  Files          37       37
  Lines        4076     4077       +1
==========================================
  Hits         3172     3172
- Misses        904      905       +1

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


ENH: integrate._tanhsinh: add array API support

Reference issue
Toward gh-20930
What does this implement/fix?
This adds support for CuPy arrays and PyTorch tensors to scipy.integrate._tanhsinh._tanhsinh. I think JAX can be added when we figure out how to handle assignment operations when a copy is OK.
Additional information
I went ahead and resolved the _tanhsinh part of gh-21071 here, too.
A follow-up will add support to the public function scipy.integrate.nsum.
For performance:

import numpy as np
# import cupy as cp
from scipy import stats
from scipy import special as sc
from scipy import integrate
from scipy.integrate._tanhsinh import _tanhsinh
from time import perf_counter
from mpmath import mp
mp.dps = 50

a, b, c, z = 1.5, 2.5, 2, 0

def _pdf(x):
    Cinv = sc.gamma(a) * sc.gamma(b) / sc.gamma(a + b)  # ignore hyp2f1 term for CuPy's sake
    return 1.0 / Cinv * x ** (a - 1.0) * (1.0 - x) ** (b - 1.0) / (1.0 + z * x) ** c

def _pdf_mpmath(x):
    a, b, c, z = 1.5, 2.5, 2, 0
    a, b, c, z = mp.mpf(a), mp.mpf(b), mp.mpf(c), mp.mpf(z)
    Cinv = mp.gamma(a) * mp.gamma(b) / mp.gamma(a + b)  # ignore hyp2f1 term for CuPy's sake
    return mp.one / Cinv * x ** (a - mp.one) * (mp.one - x) ** (b - mp.one) / (mp.one + z * x) ** c

x = np.linspace(0, 1, 1000)[1:]
tic = perf_counter()
cdf_vals = [integrate.quad(_pdf, 0, xi)[0] for xi in x]
toc = perf_counter()
t1 = toc-tic
print(f"Time for 1000 CDF values (quad): {t1}")

tic = perf_counter()
cdf_vals2 = _tanhsinh(_pdf, 0, x, minlevel=2).integral
toc = perf_counter()
t2 = toc-tic
print(f"Time for 1000 CDF values (_tanhsinh (NumPy)): {t2}")

# x_cp = cp.asarray(x)
# tic = perf_counter()
# cdf_vals2_cp = _tanhsinh(_pdf, cp.asarray(0.), x_cp, minlevel=2).integral
# toc = perf_counter()
# t2 = toc-tic
# print(f"Time for 1000 CDF values (_tanhsinh (CuPy)): {t2}")

cdf_vals3 = np.asarray([mp.quad(_pdf_mpmath, (mp.mpf(0), mp.mpf(xi))) for xi in x], dtype=np.float64)

rerr = abs((cdf_vals - cdf_vals3)/(cdf_vals3))
rerr2 = abs((np.asarray(cdf_vals2) - cdf_vals3)/(cdf_vals3))
rerr = rerr[rerr != 0]
rerr2 = rerr2[rerr2 != 0]

print(f"Speedup: {t1/t2}")
print(f"gmean of relative error (quad): {stats.gmean(rerr)}")
print(f"gmean of relative error (tanhsinh): {stats.gmean(rerr2)}")

print(f"max relative error (quad): {np.max(rerr)}")
print(f"max relative error (tanhsinh): {np.max(rerr2)}")

Time for 1000 CDF values (quad): 0.6513317999999799
Time for 1000 CDF values (_tanhsinh (NumPy)): 0.004911800000002131
Speedup:<PHONE_NUMBER>9738942
gmean of relative error (quad): 8.061987255729315e-16
gmean of relative error (tanhsinh): 4.46206718903016e-16
max relative error (quad): 1.1235272457145405e-07
max relative error (tanhsinh): 1.445515587446478e-13

In this example, which comes from gh-18799, we see a speedup on the CPU of 132x compared to quad, and the maximum relative error is several order of magnitude lower. CuPy has some overhead, so you don't get a GPU speedup for small arrays like this, but with 1,000,000 elements, CuPy was 5x~10x faster than NumPy. Torch is slower than NumPy here; maybe someday when everything else is done I'll profile to see why : )

Oops, I need to add this to the array API job.

Yeah, i need to fix those. They are new, of course.


fix: Revert master docker build until testing is finished

Currently master docker build is broken. It will be fixed soon after testing is finished. In the meanwhile, revert the changes if necessary.

Can you fix it today? If so, then lets fix rather than revert.

Can you fix it today? If so, then lets fix rather than revert.

Closing in favor of #4860

Closing in favor of #4860


Refactor more init functions to return Result

I've started working on the improved debug log described in #6 in commit 00a3ffc46c9ad8929ae10a56c78cbda1dc2f595e. However, for the debug log to be more meaningful, it would be nice if we actually had more of the init functions (i.e. memory::init_heap(), cpu::interrupts::initialize() return Results rather than panicking on failure and expecting that they don't panic.
That way, we can call each function, print [ OKAY ] if it returned Ok, or print [ FAIL ] and the error message if the initialisation function failed.  We get a much more meaningful boot log, and much better better debugging information if something goes wrong. It'd be easier to pinpoint where panics might occur, especially as the OS grows and our boot process eventually gets larger.

This is probably not a very difficult refactor, and it'd be great if someone wanted to take it on as their first contribution. I can give pointers if necessary.


pkg/client/monitoring: spelling mistake

small fix suggested from goreportcard.
cc @mxinden

lgtm on green


do not use serviceName when linking to trace results

38275c75229bf1941af09d5afacda8fe9ef72073 "really" made "Expand All"
the default way to view a span.  However, in practice search results
are a popular way to view a span, and they used the serviceName
query parameter to confusingly show only a single service.
ref #1046

Sorry about missing this.  It is an obvious test path in hindsight.

I think it was to focus on the service you searched for, right? Ex given 300 spans, you'd see the spans expanded that included your search term.

My understanding of #1046 was that showing partial spans was consistently confusing to users, so just show them the whole span was hoped to be a better default.  For reference this is how it all looks back in 122bb0193ccae30353fd9683d33031836b025871
I can search for spans by service name but not with any name (that I can tell, I wish I could!)

If I click on a span I get taken to traces/{{traceId}}?serviceName=foo which highlights spans with that service name, but hides all other spans

This is a different view from "Collapse All"

"Expand All"

And from navigating to the trace URL directly (no query parameter) and clicking on the service name

I think the best default view would be with up to 100 (or whatever limit) spans expanded. The service you searched for would be highlighted but other services dimmed, not hidden nor collapsed.  But that's not an option that exists today and I agree with #1046 (or at least what I thought the sentiment there was) that "Expand All" is the least confusing of the current options.  Maybe this is a subtle different in use cases between "I am trying to understand the emergent properties of my whole system" and "as service owner X, I wan to know how my thing is used and can be made faster?

appreciate the explanation, and I agree with your rationale. Thanks for taking time to make it easy to understand!


fix: run tests in sequential suite sequentially with sequence.concurrent

Description

Fixes #4473
Currently, when running Vitest with the --sequence.concurrent CLI option or with the sequence.concurrent config option set to true, describe.sequential has no effect and tests run concurrently.
This PR fixes the issue by correcting a typo causing the sequential option to not be passed to the task collector.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[x] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[x] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Merged with #4482


PreTag: [System - Palmetto Build -<PHONE_NUMBER>3832 ]  Test cases are failing in LED due to below error with post request

4 test case are failing in LED due to below error with post request
Documentation:	Fails if objects are unequal after converting them to strings.
Start / End / Elapsed:	20160623 17:22:39.777 / 20160623 17:22:39.778 / 00:00:00.001
17:22:39.777	INFO	Argument types are:
<type 'int'>
<type 'unicode'>
17:22:39.778	FAIL	404 != 200
Same issue is also seen with TC - deleting new log after obmc-phosphor-event.service restart - Failing
Documentation:	Fails if objects are unequal after converting them to strings.
Start / End / Elapsed:	20160623 17:17:06.415 / 20160623 17:17:06.415 / 00:00:00.000
17:17:06.415	INFO	Argument types are:
<type 'int'>
<type 'unicode'>
17:17:06.415	FAIL	404 != 200

This issue is now not seen to closing.

Test with below BMC level
To JSON using : content={
"data": {
"fault": "False",
"fru_type": "BMC",
"is_fru": 0,
"manufacturer": "ASPEED",
"present": "False",
"version": "v1.0-159-g212e8d6-dirty"
},
"message": "200 OK",
"status": "ok"


Ignore/Skip premium videos

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running yt-dlp version 2021.07.07
[x] I've searched the bugtracker for similar feature requests including closed ones

Description
Just wondering if we could add a feature to ignore/skip premium videos or instead have these be allowed errors when providing the  --ignore-errors flag
example youtube video id Q7bJ_HIf6XI
at the moment these result in making yt-dlp return an error exit code so i am forced to manually add them to the cache file to "skip them"

at the moment these result in making yt-dlp return an error exit code so i am forced to manually add them to the cache file to "skip them"

I don't see any issue here. If you are using --ignore-errors then ytdlp will still download the next item.

maybe this is more inline with my specific use case, but i loop over a list of channels in a bash script and use a trap on error codes as i do other processing aswell, when there is errors on a video i.e premium my trap is hit.
i guess its more of a should a premium video be regarded as an exit code error?

afaik, currently there is no way of distinguishing, since we just extract the error message YouTube gives and throw an ExtractorError.
This might be something in implementing https://github.com/yt-dlp/yt-dlp/issues/457 could possibly allow.

@colethedj ah i guess i didn't look hard enough.
i do agree if something like #457 was to be implemented then my request would be something along the lines of --ignore-error-category "premium"
i will close this as its basically a dupe at this point


windows-rs support for Microsoft DIA SDK (Debug Interface Access)

Hi !
I am willing to port existing code from C++ to Rust.
However, windows::Win32::System::Diagnostics::Debug exposes the dbghelp interfaces, I could not find the Microsoft DIA SDK (Debug Interface Access) interfaces.
Is there any plan to add these to windows-rs?
If so, how can I help?
If not, is #81 the only way to go?
Many thanks for windows-rs, it is precious to Windows developers switching to Rust.

@jeanga This should work today, if you drop in DIA SDK metadata. Let me write you a sample tomorrow, standby.

@jeanga Got most of a sample written today after overcoming some metadata challenges. Will share tomorrow, thanks for your patience.

Thanks for your patience @jeanga.
Check out this sample: https://github.com/microsoft/windows-samples-rs/pull/40
The high level overview is:

Microsoft.Windows.WinmdGenerator reads in raw DIA SDK idl/headers and outputs Windows Metadata
The windows crate takes in this metadata and generates the appropriate Rust code
The sample app then simply adds the appropriate use statements and uses DIA SDK APIs

What this sample doesn't show:

Use of DIA SDK's NoRegCreate path (to avoid having to register msdia*.dll)
Use of the pre-generated Windows APIs that come with the windows crate (currently blocked on #1338, will update asap)

Going to close this for now, but feel free to continue the discussion. Thanks!

Now uses pre-generated bindings. https://github.com/microsoft/windows-samples-rs/pull/40/commits/53ddb4fb052db1052db22c6c920ecc1f14042b92

Just checked the sample! Thank you sooo much for the quick answer!
You ROCK!


Generalized paths to MAPL utilities.

This allows ESMA_cmake to function with MAPL before and after the
upcoming reorg of MAPL subdirectories.

I assume I could remove all the HUH message() lines in this PR?

I really do not do well with details do I.  Yes - please fix.


Added HostHeader parameters to Web application examples

Added HostHeader parameters to Web application examples. This way multiple web applications can be created, without creating a blocker in IIS. Without this parameter, the website in IIS is created without host header and all other web applications won't be created due to an error.

[X] Change details added to Unreleased section of changelog.md?
[N/A] Added/updated documentation and descriptions in .schema.mof files where appropriate?
[X] Examples updated for both the single server and small farm templates in the examples folder?
[N/A] New/changed code adheres to [Style Guidelines]?(https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md)?
[N/A] Unit and Integration tests created/updated where possible?

This change is

Can I get some info on what the error is that you saw here? I feel like if HostHeader is going to stay optional we should make sure the error doesn't happen rather than just add it to the examples.

Review status: 0 of 5 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

In the current example, the created web application is created within IIS with a binding of ":80". The current example now only creates one web application, which works fine. But if you add another web application and don't use the HostHeader parameter, the second web application is also created with binding ":80" which is not possible so an error is thrown.
To illustrate the use of this parameter, I have added the parameter to the example.

Review status: 0 of 5 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Makes sense - I'll process this one in the morning but I think we need to handle this differently somehow to help steer customers away from doing this. Give it some thought and come back to me and we can have a chat about it

Review status: 0 of 5 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Field level policies don't apply to relations on read

ZenStack version: 1.2.0

It seems that https://github.com/zenstackhq/zenstack/blob/ac3206b42c2f4dfae25b5ed52df764d7256d8585/packages/runtime/src/enhancements/policy/policy-utils.ts#L1099 means that instead of calling this.hasFieldLevelPolicy(model) on the nested model it is using the hasFieldLevelPolicy of the parent, so no field level policies are applied.
We are using the pattern described in https://github.com/zenstackhq/zenstack/issues/809 to @deny all fields except one on our User model, and this appears to be leaking our entire user model when it is accessed via relation/include (edit - sorry I should emphasize that this is largely a non-issue since we are only selecting the field we need, I just noticed that in the default case the policies won't apply).
Happy to provide a reproduction if necessary.
Also - congrats on 1K stars! 🤩

Hi @tlancina , thanks for filing this issue and submitting the PR! It looks like a bug to me. It'll be great if you can provide a repro, and I'd like to include it as a regression test. I'll also add independent cases to cover it as well.
Since it's not blocking as far as I understand, I think we can merge it to "dev" branch and contain it in the next 1.3 release (around 11/15)?
I'm super happy with hitting 1K start too 😄. Thank you for the great support all along!

I've managed to get a repro and added a regression test to the PR. Will merge it when CI passes. Thanks!

Ah I'm sorry you had to do that, I was away from my computer until now. Thanks for cleaning it up!

Ah I'm sorry you had to do that, I was away from my computer until now. Thanks for cleaning it up!

No worries. Thanks for making the fix!


Add Travis

This was mostly copied over from PS, so please check over this and add/fix whatever,
crash emails will also have to be changed.

@Zarel

You have to run npm test and fix all the errors before Travis CI will be useful to you.

✖ 145373 problems (145324 errors, 49 warnings)
  141509 errors, 2 warnings potentially fixable with the `--fix` option.

At least they're nearly all fixable? Although it probably means that you need to set up .eslintignore correctly.

Oh when the Travis test didn’t fail so I thought it was fine, will fix

There won't be a Travis test until this pull request is merged. There definitely isn't a "passed Travis" message anywhere on this pull request.

In hindsight, I should probably be the one doing this...

I meant on the Travis website for my build when I merged these commits on my github... but yeah you probably should be as I’ve never worked with Travis before @Zarel

I did at least try to test this before merging, I probably should have done a console npm test though

So a lot the question here is stuff like, what do we want our standard to be? Right now, some files are tabs, some files are two spaces, some files are four spaces.
Also: switchcase indentation: Do we want to match Main? (Main doesn't indent case clauses; the damagecalc currently does)
Also: comma spacing: It's currently inconsistent; mostly, commas are spaced in most places except arrays. Should we keep this (eslint won't be able to check it if so) or just make them all spaced?
Don't worry about the amount of work of these changes; eslint can change them automatically.

Also: I understand now. The Travis build said "no errors" because you didn't set npm test to actually check the code, you set it to just open the eslint help, which it managed to do without any errors.

@Zarel how do you use eslint to change them automatically?

eslint --fix ... but you might as well just tell me and I'll do it myself.

@Zarel Ah well the code styling ultimately is your decision so I’m really fine with whatever. I think tabs would be better for the file style, switch case indentation should probably match main and we should just make all commas are spaced.

Okay, doing that.

I fixed all the style errors except for no-undef, and pushed.
https://github.com/Zarel/honko-damagecalc/commit/87992ed67805a9fbb1c4e8e553b09abf5432108a?w=1
Here's the non-whitespace changes, which you might want to review. You probably also want to restructure the indent pyramids eslint seems to prefer into switch statements or something: https://github.com/Zarel/honko-damagecalc/commit/87992ed67805a9fbb1c4e8e553b09abf5432108a?w=1#diff-178a90500caccbce7b63e50e6bed3037R533

Now all you need is to fix the 578 global accesses that you can see with npm test. A lot of those are actual bugs (forgetting to use var), and the remaining ones, well, the short way is to list all your globals in globals, but what I usually actually do is use namespaces (e.g. Data.SETDEX_RBY instead of SETDEX_RBY). You should generally have relatively few globals.

You still haven't actually fixed the global accesses...

@Zarel I know I finally spent some time on this again, we’re finally almost there!! Will fix your issues and start reversing a lot of the global declarations tonight

I actually think we might want to merge this now, and put those fixes in a separate commit.

For "reversing a lot of the global declarations" I'd probably do those in a separate pull request entirely.

👍👍👍 This is great!


Change inblorb and inrtps to generate HTML using per-platform CSS, for dark mode compatibility

Most of the HTML pages generated by Inform now include the per-plaforrm CSS file, so that on MacOS (and now Windows) the HTML looks good in dark mode as well as normal mode. Up until now, this hasn't been true of the results page that inblorb generates, or the Run-Time Problem and other failure case pages generated by inrtps.
This patch rectifies this problem. I have tried to keep changes to a minimum, so there is no rewriting of how inblorb generates its results page. Possibly that would be a good idea, but not right now. I have also borne in mind that inblorb can be run against blurb files generated by the old versions of the compiler supported by the front-end, so needs to keep compatibility with the template results page for those old versions.
The changes are:

Inblorb now looks for a per-platform CSS file (and then for a generic "platform.css") in the same directory as the template results file. If one is found it is read in, and is available as a replacement for the placeholder "PLATFORMCSS" in the results template.
There is now a lowercase version of the inblorb status placeholder. This is needed to align with the naming of the styles in the per-platform CSS. The original version of the inblorb status placeholder remains so that inblorb continues to work with the template results file from old versions of the compiler.
The template results file (in inform7/Internal/HTML) has been changed to use PLATFORMCSS and to use the appropriate CSS classes from the per-platform CSS.
Three images ("folder.png", "folder2.png" and "folder3.png") have been edited so that their background is transparent, rather than white, so that they look okay on a dark mode background.
Inrpts now looks for a per-platform CSS file (and then for a generic "platform.css") in "inform7/Internal/HTML". If one is found it is read in, and can be used to replace the token "*5" in the inrtps input files.
The pages generated by inrtps for releasing a game have been tidied: the failure case now refers to "inblorb", not "cblorb", and the success case is no longer present, as for the past decade cblorb (and then inblorb) have generated their own success report.

O dark dark dark, they all go into the dark...
Thanks! I'm happy for this to be merged.


add feature flags

I am not sure if  ffmpeg is a good name for the feature.
Also I am not sure, if we should fix warning, which appear when the program is complied without default features.


Update views to class based

I converted views to class based ones: FormView, RedirectView, TemplateView and View.
This will help developer to re-use the views and modifiy only part of them.
Function based views are still available through their path.

Hi @ZuluPro,
To be honest, I'm not a great fan of class-based view, but putting my feelings aside, have you been able to run the tests ? It seems like they aren't working here.
You can run them locally with python manage.py test appointment.tests --parallel=10 --shuffle --verbosity=1
Just to satisfy my curiosity, do you have use-cases of reusing the views ?
Thanks

Hi @adamspd
Sorry for my late reply
The tests work perfectly:
Ran 433 tests in 36.554s
OK

I've updated the branch to the latest version.
About the why I suggest class based-views, here's a clear example:
I'm not satisfied by how the user are created.
So I would to rewrite a part of appointment_client_information,
But just the user creation.
Thank you

Hi @ZuluPro,
Sorry for my late response as well, I just tried to run the test but one of them is failing.
I don't know why, but I'll try to see why before merging and also will try to keep the style of the code to maintain readability.
See below the output of the tests when I ran them:
pm test appointment.tests --parallel 10 --shuffle                                                                                ─╯
Using shuffle seed:<PHONE_NUMBER> (generated)
Found 433 test(s).
Creating test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
Cloning test database for alias 'default'...
System check identified no issues (0 silenced).
...............2024-07-15 00:01:02,789 - appointment.logger_config - INFO - New appointment created: {'id': 1, 'client_name': 'Georges', 'client_email'<EMAIL_ADDRESS>'start_time': '1900-01-01 09:00', 'end_time': '1900-01-01 10:00', 'service_name': 'Stargate Activation', 'address': '123, Stargate Command, Cheyenne Mountain, Colorado, USA', 'want_reminder': True, 'additional_info': 'Please bring a Zat gun.', 'paid': False, 'amount_to_pay': 100000, 'id_request': '17210016627886331b04a943dea074addbb50c3aacb5c7665'}
Missing conf: []
2024-07-15 00:01:02,816 - appointment.logger_config - INFO - Scheduling email reminder for appointment 1 at 2024-07-14 09:00:00+00:00
2024-07-15 00:01:02,825 - appointment.logger_config - INFO - Scheduling email reminder for appointment 1 at 2024-07-14 09:00:00+00:00
........................2024-07-15 00:01:03,489 - appointment.logger_config - INFO - Reminder for appointment 1 is not scheduled per user's preference or past datetime.
.2024-07-15 00:01:03,498 - appointment.logger_config - INFO - Reminder for appointment 1 is not scheduled per user's preference or past datetime.
response: b'{"message": "Appointment updated successfully.", "success": true, "appt": {"id": 1, "client": "georges.hammond", "start_time": "2024-07-15T15:00:26", "end_time": "2024-07-15T16:00:26", "client_name": "Vala Mal Doran", "url": "http://testserver/en/app-admin/display-appointment/1/", "background_color": "rgb(195, 22, 229)", "service_name": "Stargate Activation (Daniel)", "client_email"<EMAIL_ADDRESS>"client_phone": "+12392350345", "client_address": "456 Outer Rim, Free Jaffa Nation", "service_id": 1, "staff_id": 1, "additional_info": "", "want_reminder": false}}'
2024-07-15 00:01:03,504 - django.request - WARNING - Not Found: /en/ajax/update_appt_min_info/
........2024-07-15 00:01:03,508 - django.request - WARNING - Bad Request: /en/ajax/update_appt_min_info/
....2024-07-15 00:01:03,515 - appointment.logger_config - INFO - New appointment created: {'id': 2, 'client_name': 'Vala Doran', 'client_email'<EMAIL_ADDRESS>'start_time': '1900-01-01 15:00', 'end_time': '1900-01-01 16:00', 'service_name': 'Stargate Activation', 'address': '456 Outer Rim, Free Jaffa Nation', 'want_reminder': False, 'additional_info': '', 'paid': False, 'amount_to_pay': 100000, 'id_request': '17210016635150652ca6702a43fde4489a74162c09d2e1f01'}
....2024-07-15 00:01:03,520 - django.request - WARNING - Not Found: /en/ajax/update_appt_min_info/
.........response: b'{"message": "Not a working day for Daniel. Please select another date!", "success": false, "errorCode": 6, "date_chosen": "Mon, July 15, 2024", "staff_member": "Daniel", "available_slots": []}'
..2024-07-15 00:01:03,632 - appointment.logger_config - INFO - Email verified successfully for user daniel.jackson
..........F.......................................2024-07-15 00:01:04,607 - appointment.logger_config - INFO - Reminder for appointment 1 is not scheduled per user's preference or past datetime.
..................Missing conf: []
.........................2024-07-15 00:01:05,169 - appointment.logger_config - INFO - Rescheduling is allowed for service Stargate Activation -> Reschedule count: 0, Reschedule limit: 0
2024-07-15 00:01:05,169 - appointment.logger_config - ERROR - Appointment with id_request<PHONE_NUMBER>1455281c47719dfd89c4a5bbe0e4f99a1e5f7c8 cannot be rescheduled
2024-07-15 00:01:05,173 - django.request - WARNING - Forbidden: /en/appointment/17210016651455281c47719dfd89c4a5bbe0e4f99a1e5f7c8/reschedule/
2024-07-15 00:01:05,176 - appointment.logger_config - INFO - Rescheduling is allowed but no specific limit set for service Stargate Activation -> Reschedule count: 0, Reschedule limit: 3
2024-07-15 00:01:05,185 - appointment.logger_config - INFO - Rescheduling is allowed but no specific limit set for service Stargate Activation -> Reschedule count: 0, Reschedule limit: 3
.........Missing conf: []
00:01:05 [Q] INFO Enqueued [DjangORM] 1
Missing conf: []
00:01:05 [Q] INFO Enqueued [DjangORM] 2
Missing conf: []
00:01:05 [Q] INFO Enqueued [DjangORM] 1
Missing conf: []
00:01:05 [Q] INFO Enqueued [DjangORM] 2
Missing conf: []
00:01:05 [Q] INFO Enqueued [DjangORM] 3
2024-07-15 00:01:05,731 - django.request - WARNING - Not Found: /en/confirm-reschedule/unique_id_request/
2024-07-15 00:01:05,738 - django.request - WARNING - Not Found: /en/confirm-reschedule/unique_id_request/
.....2024-07-15 00:01:05,776 - appointment.logger_config - INFO - date_f 2024-07-15 start_time 09:00:00 end_time 10:00:00 service Stargate Activation staff Daniel
.........00:01:05 [Q] INFO Enqueued [DjangORM] 1
...................................................2024-07-15 00:01:07,194 - django.request - WARNING - Not Found: /en/app-admin/delete-day-off/99999/
..2024-07-15 00:01:07,203 - django.request - WARNING - Not Found: /en/app-admin/update-day-off/99999/
.2024-07-15 00:01:07,364 - django.request - WARNING - Forbidden: /en/app-admin/delete-day-off/1/
2024-07-15 00:01:07,491 - django.request - WARNING - Unauthorized: /en/app-admin/display-appointment/1/
2024-07-15 00:01:07,507 - django.request - WARNING - Forbidden: /en/app-admin/add-day-off/2/
2024-07-15 00:01:07,521 - django.request - WARNING - Not Found: /en/app-admin/display-appointment/99999/
2024-07-15 00:01:07,521 - django.request - WARNING - Unauthorized: /en/app-admin/add-day-off/1/
....2024-07-15 00:01:07,657 - django.request - WARNING - Forbidden: /en/app-admin/update-day-off/1/
..........2024-07-15 00:01:07,659 - django.request - WARNING - Forbidden: /en/app-admin/display-appointment/1/
...............................2024-07-15 00:01:07,966 - django.request - WARNING - Not Found: /en/appointment-reschedule-submit/
........2024-07-15 00:01:08,391 - django.request - WARNING - Forbidden: /en/ajax/delete_appointment/
2024-07-15 00:01:08,397 - django.request - WARNING - Forbidden: /en/app-admin/delete-appointment/2/
..........................................2024-07-15 00:01:09,054 - django.request - WARNING - Not Found: /en/ajax/fetch_service_list_for_staff/
2024-07-15 00:01:09,057 - django.request - WARNING - Forbidden: /en/app-admin/delete-service/1/
2024-07-15 00:01:09,061 - django.request - WARNING - Not Found: /en/app-admin/delete-service/99999/
.......................Missing conf: []
00:01:09 [Q] INFO Enqueued [DjangORM] 1
........2024-07-15 00:01:09,386 - appointment.logger_config - INFO - Sending reminder to<EMAIL_ADDRESS>for appointment 1
..........................2024-07-15 00:01:09,971 - appointment.logger_config - INFO - Email already in database, saving info in session and redirecting to enter verification code
.......Missing conf: []
00:01:10 [Q] INFO Enqueued [DjangORM] 1
2024-07-15 00:01:10,465 - django.request - WARNING - Forbidden: /en/app-admin/make-superuser-staff-member/
2024-07-15 00:01:10,469 - django.request - WARNING - Forbidden: /en/app-admin/remove-superuser-staff-member/
2024-07-15 00:01:10,474 - appointment.logger_config - INFO - Rescheduling is allowed but no specific limit set for service Stargate Activation -> Reschedule count: 0, Reschedule limit: 3
2024-07-15 00:01:10,478 - appointment.logger_config - INFO - Rescheduling is allowed but no specific limit set for service Stargate Activation -> Reschedule count: 2, Reschedule limit: 3
2024-07-15 00:01:10,479 - appointment.logger_config - INFO - Rescheduling is allowed but no specific limit set for service Stargate Activation -> Reschedule count: 3, Reschedule limit: 3
2024-07-15 00:01:10,482 - appointment.logger_config - INFO - Rescheduling is allowed for service Stargate Activation -> Reschedule count: 0, Reschedule limit: 0
2024-07-15 00:01:10,486 - appointment.logger_config - INFO - Rescheduling is allowed for service Stargate Activation -> Reschedule count: 4, Reschedule limit: 3
....................2024-07-15 00:01:10,721 - django.request - WARNING - Forbidden: /en/app-admin/add-staff-member-info/
.................
======================================================================
FAIL: test_exclude_with_pending_reschedules_within_last_5_minutes (appointment.tests.utils.test_db_helpers.ExcludePendingReschedulesTests)
Slots overlapping with pending rescheduling within the last 5 minutes should be excluded.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 591, in run
    self._callTestMethod(testMethod)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 549, in _callTestMethod
    method()
  File "/Users/adamspierredavid/developer/PycharmProjects/django-appointment/appointment/tests/utils/test_db_helpers.py", line 1063, in test_exclude_with_pending_reschedules_within_last_5_minutes
    self.assertEqual(len(filtered_slots), len(self.slots) - 1)  # Assuming only one slot overlaps
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 845, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual
    raise self.failureException(msg)
AssertionError: 2 != 1

----------------------------------------------------------------------
Ran 433 tests in 10.920s

FAILED (failures=1)
Used shuffle seed:<PHONE_NUMBER> (generated)
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...


easyinstall.sh assumes code is checked out in /home/pi/RASCSI

To support easy management of multiple RASCSI working directories on one system, improve easyinstall.sh to detect the directory it is in, and adjust paths dynamically in the script.
Current suggested workaround is to keep checkouts elsewhere, and symlink to /home/pi/RASCSI

Another alternative would be to 'install' the web service to a different location (like /usr/local or something) Then it will always be at a fixed location. (Similar to how the rascsi/rasctl tools are installed)

Wouldn't it make sense to make this even more flexible by using GNU autoconf or cmake?

I like the autoconf idea! In addition, it could take over some of the operations that the easyinstall.sh script does right now, such as compiling the protobuf library.

Alternatively, use Python's native package management. Some ideas:
https://packaging.python.org/tutorials/packaging-projects/
https://docs.python.org/3/distutils/setupscript.html#
Perhaps skip the step of publishing it on PyPI though. ;)

@rdmark autoconf only configures, but does not create parts of the final executables. That's still managed by the Makefile created by autoconf. I don't know how autoconf relates to python, I only know it as a tool for C/C++ based projects.

A quick test suggests that there is nothing hindering rascsi-web from running from a directory such as /usr/local/rascsi-web/
Let me pull together a PR with the install script updates needed..

Generally /opt/ is more accepted these days for this kind of thing. So /opt/rascsi-web

@karrots See my "fork" of your PR here: https://github.com/akuker/RASCSI/pull/305

@karrots I realized I could do it myself, so I made those tweaks and merged the PR.

Ok sounds good.

PR ready to address the portability of easyinstall and rascsi-web: https://github.com/akuker/RASCSI/pull/426


sketch of python object-store api

Maybe it's better to have methods on the classes instead of free functions, because it's easier to accidentally mix and match stores from multiple python packages with free functions, whereas you can't accidentally do that with class methods

This works!
from io import BytesIO

import arro3.io
import boto3
import object_store_rs

session = boto3.Session()

store = object_store_rs.store.S3Store.from_session(session, "ookla-open-data")
path = "parquet/performance/type=mobile/year=2019/quarter=1/2019-01-01_performance_mobile_tiles.parquet"
out = object_store_rs.get(store, path)

reader = arro3.io.read_parquet(BytesIO(out))
table = reader.read_all()

Maybe it's better to have methods on the classes instead of free functions, because it's easier to accidentally mix and match stores from multiple python packages with free functions, whereas you can't accidentally do that with class methods

This is true, but the issue is that in contrast to pyo3-arrow, in pyo3-object_store we're expecting the dependents to reexport the classes exported from pyo3-object_store. Therefore any Python APIs there become part of the public API, I want the public Python API of pyo3-object_store to only have constructors, because that makes the public API surface of pyo3-object_store much smaller.
So I think for now we'll have free functions from a python-facing object store package.

Todo:

[ ] Make a separation between put and put_file so that you can allow PutOptions on the former. This provides a nice PutMode enum that some people will probably want, but which PutMultipartOpts doesn't seem to have.


NO-ISSUE: Skip HAProxy multinode schedule conformance test

Which issue(s) this PR addresses:

Closes #

A failing example: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29074/pull-ci-openshift-origin-master-e2e-aws-ovn-microshift/1841472978387210240

/cc @copejon

/lgtm


Add nix-exec action to execute a new program in-place

Hi, Shea :-) What's the use case?

Wrapper scripts. The specific use case is a wrapper around nixops that passes in -I nixpkgs=${path-from-paths.json} since upstream nixops still doesn't have the ability to set nix path modularly.

very cool


feat: Adding new samples for the python callouts

Fixes #64 considering #65 PR comments
Use-cases

Validate client JWT for authorization
10. Validate client token using HMAC cookieless

Details
UC9 - Check the client request (query string) for a valid JWT token, validate (using RS256) log the authorization decision in Cloud Logging.
UC10 - Check the client request URL for a valid JWT token signed using HMAC. Log the authorization decision.

@pweiber we can close #65 in favor of #70 . Suggested some fixes

@rshriram let me know if I need to adjust something else.
Also for some reason in the pipeline the token is being invalid, locally it is working fine, also validated it in the jwt.io, is there any config I need to set for that?

The tests seem to be failing still. Are they passing locally?

@jstraceski I believe it should be fine now, I had to generate it on the fly and for the iat and exp just validate the pattern, the values were not matching by the time of the assert, let me know what you think


Fix revision numbers for NetworkPolicy watches

Description

Fixes revision numbers coming out of watch events, so that we can resume from where we left off if our watch gets cancelled (which happens periodically).
Fixes https://github.com/projectcalico/typha/issues/335
Todos

[x] Tests
[x] Documentation not required
[x] Release note

Release Note

Fixes an issue where Felix / Typha unnecessarily perform full resyncs of NetworkPolicies

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: spikecurtis:x: breunigsYou have signed the CLA already but the status is still pending? Let us recheck it.


Added an item check for the ElytraSwitch module (That was a really stupid mistake)

Type of change

[x] Bug fix
[ ] New feature

Description
When I added #63 I forgot to add a check that check if search has been successful or not.
that make it so:
            InteractionUtils.inputUse();

will be executed whenever the MixinClientPlayerEntity is called
Checklist:

[x] My code follows the style guidelines of ItziSpyder(ImproperIssues).
[x] I have added comments to my code in more complex areas.
[x] I have tested the code in both development and production environments.
[x] I have joined  the ClickCrystals Discord.

@ItziSpyder, it's important please accept the PR


Resolve merge conflicts for PR/84

Resolved merge conflicts for PR/84.

thanks! I already had it locally, and the branch was missing a few commits


Data source for databases

Is your feature request related to a problem? Please describe.
For some projects it's necessary to retrieve the databases in snowflake account. For example, to create service account for some kind of databases.
Describe the solution you'd like
A data source called "databases" that returns a list of databases (string[]).
Describe alternatives you've considered
N/A
Additional context
N/A

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


extra quote added when use Chinese Input Method

VSCode Version: 1.26.1
OS Version: macOS Sierra 10.12.1

Steps to Reproduce:

open a empty .js file
enter const str = ''
change the input method to Chinese Input Method
enter some words, but don't choose them, then press the backspace key to delete the input to empty
there is a extra quote left

here is a gif

Does this issue occur when all extensions are disabled?: Yes

I am sure the issue is not same with #26527 or #40344.

@rebornix Could this be a regression introduced via https://github.com/Microsoft/vscode/commit/2d0bbd3a926d9c42b15dc03c7d6e1d7a2b0dba6f#diff-f8aa0da950270e2d56baecaf5819a4c5

Since we don't know if users quit the composition mode, we should do auto close less aggressively for compositions. For this case, if the cursor is before a closing brace, we don't do auto close like what we usually do for non-composition mode.


No UI with 1.1.11-preview-160512

I've been pulling my hair out trying to figure out what kind of stupid thing I did to make my app only show a blank white screen after the splash screen disappears, but it appears to be a problem with the latest build..
gif..

Look at #956.

Thanks. Now if I could just stop watching that gif repeat over and over again...


fix docker -p flag for interop tests

Fixes https://github.com/grpc/grpc/issues/10374.
This undoes a change from https://github.com/grpc/grpc/commit/996a6734235ac21cb6a6222425fadc93706c93c3. The -p port:port flag tells Docker to map the container port to a specific host port. This constrains exactly one container to listen on the port, so when any server container runs after another server container has already started, it fails to bind.

Status update on this: Changes in the most recent h2 package on pip also broke the http2 test server and its health check mechanism. Setting the dockerfile to install h2 at version 2.6.1 gets the tests passing locally; still waiting for Jenkins to see if any other issues pop up. It's probably also a good idea to hardcode the versions of twisted and h2 that are installed to avoid this type of issue in the future, but will consider that in a separate PR.

Interop tests are passing. Will merge after the other tests complete.

@ericgribkoff Thanks for fixing this. How did you find this issue? My PR did not trigger anything that wasn't already failing.

@makdharma When the Go interop docker image was failing to build, the interop tests were all being aborted before anything ran. https://grpc-testing.appspot.com/job/gRPC_interop_master/ hasn't had a successful build in 6 days, with the first failure being the Go docker problem, but that allowed other issues to pop up in the meantime (including h2 releasing version 3.0.0 five days ago)

Known failures: https://github.com/grpc/grpc/issues/10199
Basic Tests Mac is heavily backlogged or stalled. Merging without waiting for it - nothing here should impact Mac tests, and want to get interop green again.


Replace named live-times with reference counting

For cases when Rust compiler cannot infer correct life-time the mechanism of
named life-times was introduced to let programmer manually state relations
between objects. This manual tinkering may however become tiresome or even lead
to issues like #3 so it should be avoided in APIs.
This commit aims to fix issue #3 by replacing named life-times with libudev
reference counting. Wrappers for raw libudev objects will now have Clone
trait implemented which increases reference count. Proper order of destruction
is ensured by adequate implementation of Drop trait as described in comments.
Example list_devices was successfully tested under Valgrind.

Both approaches are valid. To be honest, I'm a little put off by blanket statements like "[lifetimes] should be avoided in APIs," especially without justification. You mention issue #3, where I asked for anyone to reopen the ticket if they have a suggestion. Why didn't you bring this up for discussion there?
At any rate, using reference counting is a fine suggestion for addressing #3. The change needs to be thought through and would require careful review of the libudev source code to check for memory and thread safety issues. I'm not yet convinced that's the direction I want to go. I may consider this in a future release.

My justification for not using lifetimes is the rest of paragraph containing the sentence you quote. I mean, if you have structure with named lifetime it, or any structure containing it, will have to be local what in case of MonitorSocket means it will be useless in any practical case. (Note that I left lifetimes in e.g. Attribute, which should be local.)
Well, technically I brought up discussion there. This pull request is mentioned there. I could just propose solution there, but providing working example seemed to be better approach. Now we know exactly what we are talking about. (And I guess github doesn't allow strangers to reopen issues.)
Agree. I don't expect this will be merged right now. It's just a proposition. I changed memory management and public API so this PR should be deeply reviewed and widely opinionated. Any corrections and comments will be appreciated :)

@darkelement I really wanted to merge this, but unfortunately, when reviewing it for thread-safety issues, it became apparent that this approach is not going to work. From libudev(3):

However, a single context must not be accessed by multiple threads in parallel. The caller is responsible for providing suitable locking if they intend to use it from multiple threads.

Cloning a context would allow a program to send one of the contexts to a different thread, and thus they could be accessed simultaneously. Rust's type system is not aware that the two objects reference the same non-threadsafe data.

@darkelement I really wanted to merge this, but unfortunately, when reviewing it for thread-safety issues, it became apparent that this approach is not going to work. From libudev(3):

However, a single context must not be accessed by multiple threads in parallel. The caller is responsible for providing suitable locking if they intend to use it from multiple threads.

Cloning a context would allow a program to send one of the contexts to a different thread, and thus they could be accessed simultaneously. Rust's type system is not aware that the two objects reference the same non-threadsafe data.

Actually, I overlooked that we can impl !Send for Context. I'll take a closer look at this.

Actually, I overlooked that we can impl !Send for Context. I'll take a closer look at this.

I think this will work. Rust properly infers !Send for Context and the other types that reference a context internally, so the thread-safety issue from my earlier comment is nullified. I backed out the ability to clone Enumerator because of the memory-safety issue that I commented on earlier. I didn't find any other thread- or memory-safety issues, but it got difficult to remain focused toward the end, so I'll give it another review after I get some rest.

I think this will work. Rust properly infers !Send for Context and the other types that reference a context internally, so the thread-safety issue from my earlier comment is nullified. I backed out the ability to clone Enumerator because of the memory-safety issue that I commented on earlier. I didn't find any other thread- or memory-safety issues, but it got difficult to remain focused toward the end, so I'll give it another review after I get some rest.

This is now in master and released as v0.3.0. I commited this in 89a3261969ab7adc63d9699a583e5c4487c062a2 with the Enumerator changes backed out. I then took it a step further in 130f77035991b7c0a18866ac6e323283d6b681ff by doing the reference-counting manually with udev_unref(). This removes the need for the caller to manually clone Context, which has the benefit of retaining backwards-compatibility in the public API.
After looking over the changes a few times, I didn't find any more memory- or thread-safety issues.

This is now in master and released as v0.3.0. I commited this in 89a3261969ab7adc63d9699a583e5c4487c062a2 with the Enumerator changes backed out. I then took it a step further in 130f77035991b7c0a18866ac6e323283d6b681ff by doing the reference-counting manually with udev_unref(). This removes the need for the caller to manually clone Context, which has the benefit of retaining backwards-compatibility in the public API.
After looking over the changes a few times, I didn't find any more memory- or thread-safety issues.