Feat: add method field to exporter spec

Addresses #195.
Adds a new enum to kepler exporter spec that allows choosing which method/image to use: bcc or libbpf.
Needs to be changed once kepler 0.7.0 is released and default will be libbpf.
Testing was a little challenging and I am not super happy with the solution and open for suggestions.
As of now, the RELATED_IMAGE_KEPLER var gets set for Config.Image and determines the image used.
This is done in main.go lines 78 & 79. As this was needed for the test, I added lines 111-113 in exporter.go to set a default in case Config.Image is empty.
However, because of this and the test, now the image & its version is hardcoded in 3 different locations which is not good.
I am open to any help here :)
Was tested manually on an OpenShift 4.11 cluster.
@sthaha: any thoughts?

@BGrasnick , thank you for the PR. @vimalk78 is already working on enabling something similar but using an (undocumented) annotation since we know this (hack) is  going to be short lived.
The reason I call it a hack is because after 0.7, we will have to deprecate the method unless bcc is going to be supported for the foreseeable future.

Ah ok nevermind then! I wasn't sure if bcc will be deprecated or still be used in the future and thought it might be helpful also in the future because of your answer in #195.
When will this workaround come? We want to roll out kepler but need this or a release of 0.7.0 for kepler to work as we depend on libbpf...

@BGrasnick , it's good to validate our assumptions :)
@marceloamaral @rootfs, Could you please confirm if bcc will be deprecated? In this  PR  @BGrasnick adds a field in exporter spec to allow choosing between bcc and libbpf, depending on which, operator will deploy appropriate image.
We (@vimalk78 ) are currently working on a solution to allow this through a hack. We intent to add the ability to honour an annotation instead of a field in the spec, so that we don't have to delete the field later on  when bcc won't be used anymore -  which is causes API breakage.
But, this is all made under the assumption that there will only be libbpf image in future (from 0.7). Is that the right assumption to make? or would continue to use bcc, or some other mechanism later?

@sthaha yeah definitely sounds good to check again what is planned for the future.
My team and organization want to deploy kepler to our cloud/VM-based OpenShift clusters ASAP because we love the integrated dashboards and how easy use to use the operator is. We want to make this available for all teams on our clusters but cannot do it right now because we need to use libbpf instead of bcc. And there is neither a release date for kepler 0.7.0 when libbpf will become default nor a preview for it as far as I know. Do you know of any other way how we could use the libbpf version of kepler with the operator right now?

My team and organization want to deploy kepler to our cloud/VM-based OpenShift clusters ASAP because we love the integrated dashboards and how easy use to use the operator is. We want to make this available for all teams on our clusters but cannot do it right now because we need to use libbpf instead of bcc.

@BGrasnick , do note there always exists the possibility of creating your own bundle with any kepler image and use operator-sdk to deploy the bundle.
E.g. here is how I create my bundle that uses kepler libbpf bundle that gets pushed to quay as -  quay.io/sthaha/kepler-operator-bundle:0.0.0-dev
make operator-build bundle bundle-build operator-push bundle-push IMG_BASE=quay.io/sthaha VERSION=0.0.0-dev KEPLER_IMG=quay.io/sustainable_computing_io/kepler:release-0.6.1-libbpf

There exists a HACK as well  (but use it as your own risk)

Use community catalog to deploy operator
Deploy Kepler
Release all kepler - pod images as follows

for x in $(kubectl get pods -n openshift-kepler-operator -l app.kubernetes.io/component=exporter -l app.kubernetes.io/managed-by=kepler-operator -o name); do
 oc set image -n openshift-kepler-operator $x kepler-exporter=quay.io/sustainable_computing_io/kepler:release-0.6.1-libbpf ;
done

We have observed that daemonset controllers do not revert back the image.

We might have only libbpf in the future, there is no reason, as far as I know, for maintaining duplicated code.
However, I am not sure when we will remove the bcc. In the upcoming release, we plan to set libbpf as the default, and perhaps in the subsequent release, we may consider removing bcc.
Are there any use cases that I might not be aware of that require bcc?
If not, it's probably unnecessary to enable it in the operator.

@marceloamaral , thank you for taking time to answer.

Are there any use cases that I might not be aware of that require bcc?

Not that I am aware of but definitely there are more use-cases for libbpf than bcc. This also makes me wonder if it would be possible for us to make a release of kepler 0.7.0 that only switches to libbpf provided libbpf transition is mature enough.
This would allow us to make another operator release which deploys libbpf based kepler allows users of openshift 4.11+ to try out kepler and provide feedback.

If not, it's probably unnecessary to enable it in the operator.

@BGrasnick, I agree with Marcelo's comment. Since this issue is short lived, the hack @vimalk78 is working on should suffice.

@marceloamaral thanks for your answer!
@sthaha yeah of course that makes sense! If kepler doesn't need/support bcc in the future then there is no meaning in implementing this functionality of method choosing. However, as you outlined it would be great to fast track a release of kepler and kepler-operator with libbpf. I don't know if other people already use kepler on OpenShift + AWS with bcc but for us it does not work...

@BGrasnick I have started a discussion about switching to libbpf - https://github.com/sustainable-computing-io/kepler/discussions/1027

@sthaha That's a great idea! Alternatively, if it does not match up with the release plan for kepler, how about releasing a new kepler-operator 0.10.0 or 0.9.1 where we use release-0.6.1-libbpf of kepler?

how about releasing a new kepler-operator 0.10.0 or 0.9.1 where we use release-0.6.1-libbpf of kepler?

I am happy with that proposal if we can validate in kepler CI that both images produce the same / comparable values for all metrics.

@BGrasnick , I am closing this in favour of https://github.com/sustainable-computing-io/kepler-operator/pull/293


Cannot find "Storage" service tag

I just can't choose "Storage" as a service tag. I only see the following tags when trying to add outbound rule to my NSG:

Internet
VirtualNetwork
AzureLoadBalancer
AzurePlatformDNS
AzurePlatformIMDS
AzurePlatformLKM

what am i doing wrong?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cfd9533e-c174-cd48-0f72-a58457efa958
Version Independent ID: b7a77b77-61c2-5e89-cb4b-0b9a502fce71
Content: Restrict access to PaaS resources - tutorial - Azure portal
Content Source: articles/virtual-network/tutorial-restrict-network-access-to-resources.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

@dedalusmax , thank you for your query. We'll investigate and update as appropriate!

sure, here it is:

@dedalusmax , thank you for the update. May I know in which region you have created this NSG? Are you facing this issue in other regions as well? I would request you to create a new NSG and test again.

everything has been provisioned in the West Europe region.
btw, the problem appears for all NSGs that I have on that vnet.

@dedalusmax , you mentioned that the problem appears for all NSGs that you have on a particular Vnet. Could you confirm if it is same for other Vnets as well?
I would like to take a look at your Vnet, if possible. Could you send an email to<EMAIL_ADDRESS>referencing this thread and your subscription id? Please mention "ATTN gishar" in the subject field.

i don't have other Vnets, just this one.
i'm not the owner of the sub, so i don't have an authority to give you an access, i'm afraid.

@dedalusmax , I'm able to see/add "Storage" service tag in the destination when trying to create an outbound rule in my NSG deployed in West Europe region. So, the issue you are facing needs to be investigated on your subscription level.
I would request you to check with the subscription owner to confirm if there are any access restrictions applied on your Vnet. If not, create a support ticket for further investigation.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

okay, i will provide feedback about what we've investigated.
thank you for your support, Gitarani Sharma.

Same problem on East US 2. Have Owner permissions at Resource Group level.


[Hub Generated] Publish private branch 'IoTOperationsMQ'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/15027

For the PR reviewer -
We are only getting LintDiff warnings and most of them are coming from following -

Use common type v5 instead of v3. But I don't have that control from typeSpec and i am using latest TypeSpec file.
EnumInsteadOfBoolean (We don't want to use Enum for some of these fields and practically can't. Since our RP is K8S Bridge + RPaas enabled RP) and all these Azure resources are mapped to a Kubernetes CRD owned by us.

We already informed the Private branch reviewers too and they were aware.

/pr RequestMerge

@rkmanda: This PR should not have been merged with these changes to custom-words.txt.  These changes need to be reverted.  Can you please create a PR, or work with the spec author to create a PR, to fix this?
CC: @weshaggard, @konrad-jamrozik


Update Error signature - Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)

Please update the page about the below error signature from Azure Automation service.
Azure automation update failed for one server with error: Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)).

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c53fae91-9d02-f626-dd03-7c532bcffe38
Version Independent ID: 10756920-a188-fd6f-c9c9-910d6ce27673
Content: Troubleshoot Azure Automation Update Management issues
Content Source: articles/automation/troubleshoot/update-management.md
Service: automation
Sub-service: update-management
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

@dinu99
Thanks for your feedback! We will investigate and update as appropriate.

@dinu99 Thanks for your feedback.
Assigning to content author @SnehaSudhirG   for review.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Time!

Hello Adapter-hub team,
I'm working with the T5-small model for text summarization. I fine-tuned it and also trained the adapter for the same dataset on the same machine and with the same configuration.
I was expecting lesser time for adapter training as it is not changing all the parameters of the model. But surprisingly, It took same time as fine-tuning the model. I used that run_summarization for adapter training.
Can you help why it took the same time! or am I missing something?
Looking for a solution!
Thanks
Darshan Tank

Hi @Darshan2104, I am new to Adapters as well and experienced the same thing. As far as I can remember, a speed-up of training time by around x3 should be possible. I have no idea why this is not the case


Same here. codecov scores don't make much sense!
I did fix ArithmaticError -> ArithmeticError, but why would that change the diff? The rest of the changes is literally whitespace.

@Lnaden, @jaimergp if you can figure out why the Codecov tests are failing and and address that, I think this good to merge.
@jaimergp I think the todo from this is to make sure you have a list of name changes, and propose a PR to add to 3.0.x that deprecates the old names and tells people the new names for 4.0.

I don't fully understand the difference between both scores in codecov. We have only applied black? So the code is virtually the same (they compare ASTs before and after execution to guarantee they are equivalent!).
Anyway, maybe this should the last thing we merge to pymbar4. Otherwise there is going to be a lot of conflicting files. I would also suggest using something like https://github.com/cclauss/autoblack to apply it  automatically on every PR.

I would not worry about the codecov failures right now, we're doing so much adjustment that we can circle back to it. So long as the CI tests pass, I think its okay for now

I think that we are at a reasonable "not changing too much code this week" place, so I would go ahead and make formatting changes sooner rathe than later

The problem we have now is that we applied to black before some more changes were merged to pymbar4, so now we have these conflicting files. This will happen again as we change more things, so I'd rather run black only once (or have everybody involved run black automatically on file save in their IDE?).

I mean: we can close this PR and open a new one after we are finished with all changes.

I mean: we can close this PR and open a new one after we are finished with all changes.

How about we fix the lint issues, and then apply black after that?  The other PRs will be easy to refactor on top of reformatted code.

Closing this one - black will be applied on a new PR once we merge the ongoing work. Otherwise it's going to be a conflict nightmare.


Swift package identity is case-insensitive

This PR fixes the bug of some dependency (eg. Yams) not being recognized due to case-sensitive identity comparison.

@adam-fowler I added some assertions — and that’s what we can test now with a dedicated test suite for UI testing. Making getDependencyGraph public seems unnecessary for the case, because asserting on the UI (with getChildren()) is enough.


WSL will not launch after hibernation

Version
Microsoft Windows [Version 10.0.19045.2364]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
No response
Other Software
No response
Repro Steps
I believe this may be related to #9387 and #9301
I initially updated wsl using wsl --upgrade but then ran into the SSH issue ( #9231) so I uninstalled WSL completely and reinstalled from the control panel plus the kernel upgrade.
After hibernation, wsl will refuse to launch at all. Even commands such as wsl --status will simply hang.
I cannot use the taskkill workaround as there is no wslservice to kill. Only a reboot clears the problem
Expected Behavior
wsl should work, even after hibernation
Actual Behavior
The attached logs were taken from Windows Terminal Version: 1.15.3465.0 when trying to launch a new tab set to launch wsl with the following command C:\WINDOWS\system32\wsl.exe -d fedora36
WslLogs-2022-12-23_01-09-46.zip
Diagnostic Logs
No response

Additional information: I've discovered the LxssManager service gets stuck in "Stopping" status and cannot be killed without shutting down Windows.
Please let me know if additional information or logging would be helpful

/dupe #9301


Update to use opencv version 4.9

Good evening, I'm begging you to update this repo and npm package to include opencv v.4.9
It includes all the good functionalities like imdecode(jsbuffer)/ material.getDataAsArray() / Vector struct and so much more.
Without it - currently, we can't use this package in production.

Already bumped opencv version to 4.10.0 in my repo ( also removed deno and properly generated dockerfile along with bash files and script to build package consistently)
https://github.com/studentutu/opencv-wasm-node


Throttles calls to ES0 endpoint

not using the cluster work throttler? this allows the number of instances to be taken into account so the aggregate rate of all instances does not exceed the desired limit.


ARROW-14658: [C++] Add basic support for nested field refs in scanning

This implements the following:

Being able to project and filter on nested fields in the scanner/query engine.

Parquet, ORC, and Feather are supported/tested. For ORC and Feather, we will read the entire top-level column. (CSV does not support reading any nested types, though if it does in the future, it should behave the same as Feather/ORC.) For Parquet, we could materialize only the leaf nodes necessary for the projection, but without ARROW-1888 this will fail later on in the scanning pipeline, so we behave the same as Feather/ORC.
The following are not implemented:

Normally, the scanner can fill in a column of nulls if a requested column does not exist in a file. This is not supported for nested field refs because we need ARROW-1888 to be implemented.

A nested field ref cannot be used as a key/target of an aggregation or join. However, you can first project the nested fields into their own fields, then aggregate/join on them as usual.
This limitation is because the aggregate/join nodes currently compute a FieldPath to resolve a FieldRef, but then throw away the path, keeping only the first index. To implement this, we would need to store the FieldPath and use the struct_field kernel to resolve the actual array, however, this will have more overhead and we should be careful about regressions here, especially in the common case of no nested field refs.

Only FieldRefs consisting of field names are supported. For FieldRefs consisting of FieldPath (= a sequence of indices), the semantics are unclear. So far, the scanner is robust to individual files having fields in a different order than the overall dataset, but this won't work for FieldPath, so either we must require that the schema is consistent across files, or come up with some way to map file schemas onto the dataset schema so that indices have a consistent meaning.

A nested field ref cannot be used as a key/target of an aggregation or join.

If I project a = struct_col.some_nested_field in one step, can I then aggregate it?

A nested field ref cannot be used as a key/target of an aggregation or join.

If I project a = struct_col.some_nested_field in one step, can I then aggregate a?

Yes, you can (I just pushed a test to confirm that).

A nested field ref cannot be used as a key/target of an aggregation or join.

If I project a = struct_col.some_nested_field in one step, can I then aggregate a?

Yes, you can (I just pushed a test to confirm that).

Excellent. Can you note that on the PR description then? (i.e. you can't directly use a nested field ref there but you can project and then use what you projected)

Done (also clarified the comment about CSV)

CC @westonpace if you have any final comments

I'll try to rebase by EOD today, thanks for the ping.

Rebased, cc @westonpace if you have any final comments

I was thinking about the same thing in regards to indices. The current design, for better or worse, is "robust" to fields being reordered, but I don't think that was intentional and we may not want (or need) to have that property. If so I agree resolving fields to indices ASAP Is best.


support for symbolic link in some file functions

Codecov Report

Merging #5 (082e155) into main (b352f75) will decrease coverage by 0.50%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##              main       #5      +/-   ##
===========================================
- Coverage   100.00%   99.49%   -0.51%
===========================================
  Files           12       12
  Lines          599      599
===========================================
- Hits           599      596       -3
- Misses           0        3       +3

Flag
Coverage Δ

unittests
99.49% <100.00%> (-0.51%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pygemstones/__init__.py
100.00% <100.00%> (ø)

pygemstones/io/file.py
99.02% <100.00%> (-0.98%)
:arrow_down:

Continue to review full report at Codecov.

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


C++ distribtest improvements

cleanup the dockerfile (only use stuff that's documented in BUILDING.md)
switch some C++ distribtests to debian stretch with simplifies the way we can install libssl-dev (jessie has a version that's too old, and grabbing the backport version is a mess)
still keep some jessie distrib tests for ensuring grpc stays buildable on jessie

@veblush  this is now ready for review.

Known failures:
https://github.com/grpc/grpc/issues/20624


🎉 release: v8.0.0

Description
This is a release PR.

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


->each returns DOMElement instead of DomQuery

is that on purpose?
e.g. I cannot do
$dq->find('select[name="myname"]')->each(function ($el, $i){
            /** @var \DOMElement $el */
            $linktag = $el->parent(); //meeep parent doesn't exist on DOMElement

});

Yeh it is, see also: https://api.jquery.com/each/
If you want the result as an DomQuery instance you can just use a foreach loop.

@Rct567 ahh thanks
well in jquery you can do
->each(function(el){
var jel = $(el);
jel.parent();
});

is there something equivalent?

The constructor also accepts DOMNode/DOMElement, so just use new DomQuery (or DomQuery::create)  instead of $ 😁


Is the .idea directory intentionally published in npm

I have installed 1.7.6 and found that the .idea directory is also present in the library under node_modules. Is this intentional? If not I guess it could be removed. I find it a bit error prone to have .gitignore and .npmignore in the same time because it's not immediately obvious what will be effectively published in the registry.

Great. Thanks.


VM revert error when pranking an address that receives ether from contract

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (8b0af47 2022-11-06T00:06:24.552295Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
minimal reproduction repo: https://github.com/hexcowboy/foundry-bug-repro
It appears that when pranking an address, the VM will revert randomly if a contract method transfers ETH using payable(prankAddress).transfer(). This bug is reproducible using the repo above and running forge test -vvvv.
Here's the test:
    function testFuzzPayable(address[10] memory senders, uint256[10] memory amounts) public {
        for (uint256 i = 0; i < amounts.length; i++) {
            amounts[i] = bound(amounts[i], 0, 500);
        }

        // add funds to contract
        vm.deal(address(counter), 1 ether);

        for (uint256 i = 0; i < senders.length; i++) {
            vm.startPrank(senders[i]);
            counter.hello(amounts[i]);
            vm.stopPrank();
        }
    }

Here's the contract:
contract Counter {
    function hello(uint256 amount) public {
        payable(msg.sender).transfer(amount);
    }
}

Some examples of the error logs:
    ├─ [32103] Counter::hello(126)
    │   ├─ [0] console::fallback{value: 126}()
    │   │   └─ ← "Invalid data"
    │   └─ ← "Invalid data"
    └─ ← "Invalid data"

    ├─ [34394] Counter::hello(143)
    │   ├─ [0] PRECOMPILE::ecrecover{value: 143}()
    │   │   └─ ←
    │   └─ ← "EvmError: Revert"
    └─ ← "EvmError: Revert"

The problem is the addresses being used:

The first revert is using the console address. This is a special address to make console.log work, any calls to this address are intercepted and handled differently, so you should use vm.assume to exclude this address (and maybe it should be excluded from the fuzzer dict)
The second is a precompile address. You can use assumeNoPrecompiles to  remove these

Related: https://github.com/foundry-rs/forge-std/issues/211

The problem is the addresses being used:

There are still a few addresses causing trouble after ignoring the log address and the precompile addresses. Here are a few I could find:
    ├─ [0] VM::startPrank(Create2Deployer: [0x4e59b44847b379578588920cA78FbF26c0B4956C])
    │   └─ ← ()
    ├─ [9394] Counter::hello(408)
    │   ├─ [34] Create2Deployer::fallback{value: 408}()
    │   │   └─ ← "EvmError: OutOfGas"
    │   └─ ← "EvmError: Revert"
    └─ ← "EvmError: Revert"

    ├─ [0] VM::startPrank(VM: [0x7109709ECfa91a80626fF3989D68f67F5b1DD12D])
    │   └─ ← ()
    ├─ [7103] Counter::hello(433)
    │   ├─ [0] VM::fallback{value: 433}()
    │   │   └─ ← "Invalid data"
    │   └─ ← "Invalid data"
    └─ ← "Invalid data"

    ├─ [0] VM::startPrank(CounterTest: [0xb4c79daB8f259C7Aee6E5b2Aa729821864227e84])
    │   └─ ← ()
    ├─ [7139] Counter::hello(64)
    │   ├─ [45] CounterTest::fallback{value: 64}()
    │   │   └─ ← "EvmError: Revert"
    │   └─ ← "EvmError: Revert"
    └─ ← "EvmError: Revert"

What are these addresses?

Here's my workaround for now
// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.13;

import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import "../src/Counter.sol";

contract CounterTest is Test {
    Counter public counter;

    function setUp() public {
        counter = new Counter();
    }

    uint256 constant LOAD = 10;

    function testFuzzPayable(
        address[LOAD] memory senders,
        uint256[LOAD] memory amounts
    ) public {
        for (uint256 i = 0; i < LOAD; i++) {
            amounts[i] = bound(amounts[i], 0, 500);
            vm.assume(senders[i] != 0x000000000000000000636F6e736F6c652e6c6f67);
            vm.assume(senders[i] != 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D);
            vm.assume(senders[i] != 0x4e59b44847b379578588920cA78FbF26c0B4956C);
            vm.assume(senders[i] != 0xCe71065D4017F316EC606Fe4422e11eB2c47c246);
            vm.assume(senders[i] != address(this));
            StdCheatsSafe.assumeNoPrecompiles(senders[i]);
        }

        // add funds to contract
        vm.deal(address(counter), 1 ether);

        for (uint256 i = 0; i < senders.length; i++) {
            vm.startPrank(senders[i]);
            counter.hello(amounts[i]);
            vm.stopPrank();
        }
    }
}

Could I propose a cheat that provides safe payable addresses when fuzzing?

VM is the cheatcode address (e.g. vm.assume) and Create2Deployer is a deterministic create2 deployer used on many chains with forge script. For now you'll need to filter out those addresses which can be a bit tedious, since there's currently no way for the fuzzer to only generate addresses that can receive ETH.
Two possible foundry-level solutions if you want to create separate issues for each:
Exclude Special Addresses
We can consider excluding special foundry addresses from the fuzz dictionary. This would be all addresses that behave differently in foundry than they do on live chains, which includes:

VM address
Console address
Are there others?

Create2Deployer and precompiles are valid inputs an attacker can pass in real life, so we wouldn't want to exclude those.
Flag to only fuzz payable addresses
Foundry could check the ABI of a fuzzer generated address and discard it if it has code but there's no fallback/receive method. This would probably need to be a config flag as opposed to a cheatcode just based on the fuzzer architecture.

closing for https://github.com/foundry-rs/foundry/issues/3630 and https://github.com/foundry-rs/foundry/issues/3631

Thank you!


Added example and improved existing example

This simplifies creating an example

Thanks for the improvement.

Thanks for this ;)


@method tag's function arguments do not accept the use of default parameters

As mentioned here: https://github.com/phpDocumentor/phpDocumentor2/issues/379
The accepted signatures should be improved in /src/phpDocumentor/Plugin/Core/Parser/DocBlock/Tag/Definition/Method.php and documented in the @method tag's specific documentation

Needs specification update first.

This functions partially; for some odd reason the default value is only shown when a typehint is added to the magic method's parameter

Specs mention that no support is needed and noone commented on this issue since; I am closing it as a won't fix


Problem when trying to tag-release a new repo of of version 1.0

If the package.json is already at 1.0.0 and the repo has never been tagged before, tag-release will try to bump the version higher than 1.0.0.

I will update the readme for now in the FAQ with a workaround


Readme links are broken

Table of contents links do not work- github removes emojis and punctuation from anchor tags rather than encoding them 💢 :octocat: 😬
Fixing it now.

Seems to be an issue with my vscode plugin: https://github.com/AlanWalk/markdown-toc/issues/31
Should be solved now though after I upgraded :)


fix(cli): fix typegraphql template generation

:tada: This PR is included in version 3.20.13 :tada:
The release is available on:

v3.20.13
GitHub release

Your semantic-release bot :package::rocket:


fix: setting path pattern in opentelemetry traces

In the OpenTelemetry Tracing middleware, the path pattern is not set as an attribute. I think that's because the PathPattern is initialized when the request is "called". Similar to this PR, I have moved the setting of the attribute to after the request is called.
As a second change (which might be considered breaking), I am renaming the span to :method :pattern instead of :method :uri. This is recommended by OpenTelemetry: https://opentelemetry.io/docs/specs/otel/trace/api/#span.

thanks 🙂


What type of GPU was used when testing FPS in the experiment?

Excellent work! But I have a question as the title, in TABLE III, what type of GPU was used when testing FPS in the experiment?
In addition, the paper claims that RadOcc's inference speed is obtained from the RadOcc paper, but the RadOcc paper also does not mention the type of GPU used for inference.

I use a single A6000 to test FPS in the experiment. Since RadOcc does not open its code and does not mention its GPU used. I obtain the inference speed from the supplementary material of RadOcc.


Fix php-cs-fixer for PHP, make github credentials not required for --dry-run

LGTM, will leave approval to Ethan


Update abc.py

Allow for downloading of 1080p streams
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
1080p streams are beginning to be introduced to ABC iView (https://tvtonight.com.au/2021/07/iview-adds-news-clips-in-1080hd.html) I have made a small modification to the code so that youtube-dl will recognise any 1080p streams that are present.
Tests:
BEFORE
youtube-dl https://iview.abc.net.au/video/NEWS202113466544 -F
[abc.net.au:iview] NEWS202113466544: Downloading JSON metadata
[abc.net.au:iview] NEWS202113466544: Downloading webpage
[abc.net.au:iview] NEWS202113466544: Downloading m3u8 information
[info] Available formats for NEWS202113466544:
format code  extension  resolution note
hls-372      mp4        320x180     372k , avc1.4D401E, mp4a.40.2
hls-568      mp4        512x288     568k , avc1.4D401E, mp4a.40.2
hls-690      mp4        640x360     690k , avc1.4D401E, mp4a.40.2
hls-982      mp4        800x450     982k , avc1.640028, mp4a.40.2
hls-1371     mp4        1024x576   1371k , avc1.640028, mp4a.40.2
hls-2090     mp4        1280x720   2090k , avc1.640028, mp4a.40.2
hls-2283     mp4        1280x720   2283k , avc1.640028, mp4a.40.2 (best)
AFTER
youtube-dl https://iview.abc.net.au/video/NEWS202113466544 -F
[abc.net.au:iview] NEWS202113466544: Downloading JSON metadata
[abc.net.au:iview] NEWS202113466544: Downloading webpage
[abc.net.au:iview] NEWS202113466544: Downloading m3u8 information
[info] Available formats for NEWS202113466544:
format code  extension  resolution note
hls-372      mp4        320x180     372k , avc1.4D401E, mp4a.40.2
hls-568      mp4        512x288     568k , avc1.4D401E, mp4a.40.2
hls-690      mp4        640x360     690k , avc1.4D401E, mp4a.40.2
hls-982      mp4        800x450     982k , avc1.640028, mp4a.40.2
hls-1371     mp4        1024x576   1371k , avc1.640028, mp4a.40.2
hls-2090     mp4        1280x720   2090k , avc1.640028, mp4a.40.2
hls-2283     mp4        1280x720   2283k , avc1.640028, mp4a.40.2
hls-3758     mp4        1920x1080  3758k , avc1.640028, mp4a.40.2 (best)

For anyone wondering, this was added to (yt-dlp)[https://github.com/yt-dlp/yt-dlp] in this commit https://github.com/yt-dlp/yt-dlp/commit/c15c316b2147f9621818df41f585f6900ef85bd4

NOTE: please don't close this issue, even if using yt-dlp solves your problem, because it might not solve some people's


Wider stylesheets for built websites

Please select if your request is either something new or an enhancement

[ ] Enhancement of an existing Feature.
[ x] Request of a new feature.

Please select the area your request applies to. (Multiple selections are possible)

[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ x] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
Websites built using Dendron default to a narrow view. This is fine for most monitors, side by side viewing, and mobile view, but looks very awkward on wider monitors.
More complicated content such as long lines of code, or long equations can look quite janky.
Describe the solution you'd like
An option during to customize the width of built websites.
The most comprehensive solution would be to allow a built in widget so that users can toggle how wide the content is on the built website itself.
Describe alternatives you've considered
There are websites that allow you to customize how wide the content is. E.g. wikiwand extension for wikipedia.
Additional context

Thanks @zeyuz35  for the suggestion. It would be a good feature to have stylesheets for wider monitors


Running if-check in if root directory results in package name change

Description of the Error

Running if-check in if framework root directory results in the package name change.
Expected Behaviour

package.json to stay the same
Actual Behaviour

package.json -> name is changed to "if-environment"
Steps to Reproduce

run if-check in if framework root directory

@manushak please link the PR 🙏


🐛 Bug Report: Database does not return the correct count of announcements when using max or offset filter

📜 Description
I did not get the expected behavior when unit testing the announcements database.  The following unit test adds two entries to the database and then queries with the max set to 1. I would expect the count to come back as 1, but it comes back as 2.
it('max', async () => {
  await store.insertAnnouncement({
    id: 'id',
    publisher: 'publisher',
    title: 'title',
    excerpt: 'excerpt',
    body: 'body',
    created_at: DateTime.fromISO('2023-10-26T15:28:08.539Z'),
  });

  await store.insertAnnouncement({
    id: 'id2',
    publisher: 'publisher2',
    title: 'title2',
    excerpt: 'excerpt2',
    body: 'body2',
    created_at: DateTime.fromISO('2023-10-26T15:28:08.539Z'),
  });

  const announcements = await store.announcements({
    max: 1,
  });

  expect(announcements).toEqual({
    count: 1,
    results: [
      {
        id: 'id2',
        publisher: 'publisher2',
        title: 'title2',
        excerpt: 'excerpt2',
        body: 'body2',
        category: undefined,
        created_at: timestampToDateTime('2023-10-26T15:28:08.539Z'),
      },
    ],
  });

👍 Expected behavior
Using store.announcements({ max: 1 }) should return the correct count. This is likely affecting the offset parameter as well.
👎 Actual Behavior with Screenshots
I received 1 announcement back, but the count is set to 2

👟 Reproduction steps

Remove skip option on unit tests in AnnouncementsDatabase.test.ts found here.
Run the test suite (yarn test AnnouncementsDatabase.test.ts)
Observe the behavior. It may be helpful to add a console statement to print the count in AnnouncementsDatabase.ts and to print the returned announcements within the test.

📃 Provide the context for the Bug.
I do not have experience using this feature, but it may affect others
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

@kurtaking I can't reproduce the test failure.  Removing the skips makes the tests pass on a freshly cloned repo:


Implement RIPEMD algorithm series

ISO/IEC 10118-3:2018 => https://www.iso.org/standard/67116.html
https://webstore.iec.ch/preview/info_isoiec10118-3{ed4.0}en.pdf

https://homes.esat.kuleuven.be/~bosselae/ripemd/rmd128.txt
https://homes.esat.kuleuven.be/~bosselae/ripemd/rmd160.txt
https://homes.esat.kuleuven.be/~bosselae/ripemd/rmd320.txt

https://github.com/bcgit/bc-java/blob/master/core/src/main/java/org/bouncycastle/crypto/digests/RIPEMD128Digest.java
https://github.com/bcgit/bc-java/blob/master/core/src/main/java/org/bouncycastle/crypto/digests/RIPEMD160Digest.java
https://github.com/bcgit/bc-java/blob/master/core/src/main/java/org/bouncycastle/crypto/digests/RIPEMD256Digest.java
https://github.com/bcgit/bc-java/blob/master/core/src/main/java/org/bouncycastle/crypto/digests/RIPEMD360Digest.java


Code simplification ideas

In an ideal world, I'd have gotten every aspect of the design right first time. In this world ....
Switch to crypto to hide tx data
In server-assisted mode the server hides pledge transaction data from the client unless it authenticates. The client then crafts the claim and broadcasts it when the user hits the claim button (because it needs a fee and the server doesn't want to have a hot wallet, not even a small one, nor pay for claiming other people's projects).
This has turned out to be a source of bugs, complexity and inflexibility. Clients want to be able to see which pledge in the status report is theirs to render it properly in the GUI, so server statuses include the original hash of the pledge data for comparison purposes.
Additionally, it makes claiming more complicated when the wallet is encrypted. If the wallet is encrypted, and we fetch the status, we cannot authenticate because the user hasn't entered their password yet. So we don't have tx data even though we own the project. Then when the user presses claim, we have to ask for the password and then requery the server and wait for the response before starting to craft the claim. This is excessively fiddly.
Also, it means the server has more brains than it really needs to have, which increases the disparity between serverless and server assisted mode. In serverless mode, transactions are public so anyone can trigger the claim. That's not intuitive.
We can fix all this by encrypting the tx data to the owner, using ECIES. The server needs to be able to see tx data so it can check which pledges are active and which are revoked, so it must have a copy of the relevant private key, but this would still unify some code paths between serverless and server assisted mode. To keep project files fully self contained the private data key could be encrypted to the server pubkey as used in the SSL cert.
Pledge syncing
The LighthouseBackend.syncPledges function is horrible. It tries to update two observable collections to reflect pledges being open, revoked or claimed with minimal changes to the collections (so animations flow nicely), and it's used for serverless and server assisted projects in both client and server contexts. This is a recipe for confusion and buggy edge cases!

Split the function in four, one for each context, even if that results in a bit more code duplication.
Abstract out the process of syncing an observable set with a base set to result in minimal events being fired, so all we're doing in LighthouseBackend is figuring out what the current state is in the simplest way possible.
Why do we need a separate collection for claimed pledges again? This appears to be an artefact of the first collection being called openPledges rather than any obviously good reason. It could probably become activePledges or something like that, where "active" means open or claimed, and then the second collection can just be junked - it appears that the only places the second is being used, it's mostly being merged with the first before processing anyway.
ObservableSets are, well, sets, so that's the academically correct type to use, but they are less powerful than ObservableLists in terms of control over which events are triggered, and in the end we didn't exploit all the animation potential anyway. So it's not clear all the effort to minimise touching is actually useful. Perhaps if we animated the pledge list and made the pie chart more prominent it'd have more value.

Disk management
The original vision was that the app would be a super light thing with hardly any UI, oriented around watching disk folders and the server would really just be a quick directory syncer kind of thing. Then serverless mode could be done using a shared folder on dropbox/google drive/etc and both modes would be very similar. It didn't quite work out like that. The "leave the app running whilst it observes a shared folder" use case ends up being not very compelling, other apps don't work that way and the UI never really explained this feature properly.
 Gah. Also the UI doesn't actually surface the fact that in some cases directories are being watched, and there were bugs found during alpha like "I renamed the directory I downloaded my project to and Lighthouse crashed".
It also means that on platforms like Windows and Linux where the DirectoryWatcher is using the proper OS support for it, the code has a habit of spotting project/pledge files that are half copied and trying to load them.
And finally, to try and keep data flows consistent, importing a project ended up being implemented as "copy it into the apps private watched directory and let the rest happen asynchronously" which means if the project is bad/incompatible in some way, the app just ignores it and does nothing instead of showing you an error message! Also, on a Mac it takes several seconds to import the project, just because the app is waiting to notice what it did itself. That's dumb.
We should just rip directory watching out of the app entirely. It was a bad idea and isn't worth the cost. There can be an explicit action to import pledges for serverless projects.
Pledges being stored in the wallet
The PledgingWallet class stores pledges in a wallet extension. This means you only need to back up your wallet file, to keep all info about pledges. But the app doesn't encourage people to back up wallet files  in the UI, in the end. It encourages people to write down their wallet words instead. Restoring from wallet words will make the wallet forget about its pledges!
So what exactly is the point of having this data in the wallet? I put it there because, well, in the beginning it felt weird to not have it there and I figured people would back up entire files, so better have a copy of it there just in case! But now I think about it more I can't quite quantify exactly why the data must be in this file. A pledge file, once created, can just be stored alongside the wallet itself, like all the other pledges will be. If you lose the pledge file, no big deal, you can always just revoke it by emptying the wallet out, or re-pledge. The person who cares most about the pledge is the project owner, and they won't be storing the pledge in their wallet at all.
The fact that pledge data comes from multiple sources including the wallet adds complexity in a bunch of places, because we can end up seeing the same pledge multiple times. E.g. in serverless mode, it can be on disk in some random folder, and also in the wallet. So we have to make sure to deduplicate and stuff. This adds complexity.
All the pledging wallet really needs to store is which outputs have been pledged. The pledge itself, is less important.

Allow multiple getutxo queries to be queued up on the wire simultaneously
The code tries hard to avoid putting more than one getutxo query in flight simultaneously. I don't remember why - you can easily send lots after each other and you're guaranteed to get the answers back in the same order. There's really no need to do this at all.
If we fix this, then the process of checking a project or pledge can be done in a dedicated thread in parallel to other pledge checks in a fully blocking/synchronous style. This in turn means there's no longer any particular benefit to serialising it all onto the backend thread. Originally putting everything onto the backend thread was meant to simplify things but it hasn't quite worked out like that, due to the need to avoid blocking things like project imports during network lookups.
 It's absurdly difficult to keep track of how errors propagate through async computations and absurdly easy to lose error states along the way. Some of the methods unexpectedly block the executor thread when there's no apparent need to. Plus the code it results in is ugly. Even the pre-lambda ListenableFuture API is better than this. I don't know how they managed to stuff it up so badly but they did.
The new "reactive programming" stuff looks like it'd be a great fit for Lighthouse. Some stuff is already a bit like that, such as the mirrored observable collections. We should explore how using Rx/ReactFX can simplify the code and make it easier to read.


requirements for training the model

Hi, Yohei, it is a fantastic work. Can I ask some questions about the requirements for training the model.

What is the least requirements for a pc? My pc has a memory of 8G, and 1050Ti (4G GPU memory). Even though I changed the batch_size to 1, it still ran out of memory. From my experience, my pc could train the model with only 267k parameters.
My pc can not run the model according to the 'requirements.txt'. I did the following changes then it works. I have no idea whether it is common or only for me. I hope this will help.
Keras-Preprocessing==1.1.0
gast==0.3.3 (It always reminds me that gast==0.3.3 is imcompatible with tensorflow==1.15.)

Thank you very much!

Minimum requirements for a PC
I am sorry. I have not checked it exactly.
We will confirm it at the beginning of the week.

About "requirements.txt"
We will also check it at the beginning of the week.
As soon as we get information, we will report you.

Thank you very much.
I want to know your environment.

OS version
Python version

For answering the second question, I changed versions to

Keras-Preprocessing == 1.1.0
gast == 0.3.3
and ran the baseline.
The same results were obtained.

@nakamura419
Thanks for your reply.
I run the code in
Windows10 Home (version 1903),
Pycharm 2019.2.4(Community),
Python 3.6.10.

Answer questions 1.
As a result of training only with the largest amount of data, Toy Car, the maximum memory usage was 7578MB.
Even if batch_size was changed, this usage did not change much, so I think it is better not to use all dev_data with 8GB memory.

We have found that the memory usage can be reduced to 4136MB if the parameter of "n_mels" is changed from 128 to 64.
Please try it.

@Yuki-Nikaido
Thank you. I changed the 'n_mels' from 128 to 64, and 'batch_size' from 512 to 1, it still does not work. However, I reduced half of the training data, then it works. For example, there are 3291 files in valve. The training process works when only 1496 files are used.

Because train_data = list_to_vector_array() read all data in to train_data, it is very memory-consuming. It could save memory consumption by reading data in batch_size.

If only one model (ToyCar, valve ... etc) is trained, it can be executed with 8GB memory, so if you use all data, how about training only one model in one execution?
When using n_mels = 64 and using all dev_data, it was confirmed that a maximum of 8527 MB of memory was used, so in an 8 GB memory environment, training using all dev_data would be difficult.
(Maximum memory usage depends on garbage collection)

@20050710212 Thank you very much!
We understand that loading data little by little will save memory consumption.
However, processing speed will be slower. So, we will not revise this repository in such a direction.
At this time, it is recommended to train one machine-type model at a time as @Yuki-Nikaido said.
We hope you understand.

@y-kawagu @Yuki-Nikaido @nakamura419
Thank you for the reply. I have already add a memory chip in my pc.


Error in parseDataPacket

Hello there.
There's an error in parseDataPacket in this line:
double laser_relative_time = LASER_PER_FIRING * time_between_firings + time_half_idle* (laser_index / max_num_lasers);
It should be like this:
double laser_relative_time = laser_index * time_between_firings + time_half_idle* (laser_index / max_num_lasers);
Hope it helps.

@lasdasdas What do you think?

I have not been around for quite a while, sorry for that. It seems that this is an issue. I'll check it out later.

Fixed in 80970c8. Good find @AJMena .


getting base64 assets in the Texture Cache

Hiya I am trying to get base64 data from a jsonp file into the textureCache,
atm I am doing a sprite =  PIXI.Sprite.fromImage(data.under, true)
where data is the jsop file and data.under is the part where the base64 string is at.
this works wonderfully, but I'd like a way of putting that texture in the cache, preferablu under a name like JSONPURL+'under',
because I have the feeling these base64 strings are slowing me down when I want to draw that asset multiple times
how does that work?

how do we get the base64 out of a texture?

Please open a new issue with your question.


Add addons-related Fireplace views to routes.

r? @ngokevin @jasonthomas

r-, this only affects local zamboni and isn't worth doing in this case.
you want to update nginx configs at https://github.com/mozilla-services/svcops-puppet/

We need this eventually, right?

not really, i already added the routes at https://github.com/mozilla-services/svcops-puppet/commit/d0dfc42982c20022f2ab986b5b0c4d68b432add4
we'd only need specific routes if we wanted route reversal (e.g., link to app detail page in a commbadge email)


Cannot set ContentKeyPolicyFairPlayRentalAndLeaseKeyType for Fairplay

First of all, thank you for maintaining the SDK.
Issue Description:
In the Java SDK version 0.9.8, there is no way to set    RentalAndLeaseKeyType property while creating the OptionConfig

method name FairPlayConfiguration.createSerializedFairPlayOptionConfiguration.

The .net code has the option:-
FairPlayConfiguration = Microsoft.WindowsAzure.MediaServices.Client.FairPlay.FairPlayConfiguration.CreateSerializedFairPlayOptionConfiguration(
            objX509Certificate2,
            pfxPassword,
            pfxPasswordId,
            askId,
            iv,
            RentalAndLeaseKeyType.PersistentUnlimited,
            0x9999);

but the java SDK method has no such signature:-
public static String createSerializedFairPlayOptionConfiguration(
          KeyStore keyStore, String pfxPassword, String pfxPasswordKeyId, String askId,
          String contentIv)

Thanks in advance.

Hello @m-kumaran
I am sorry about you didn't get a sooner answer on this
Do you still need help? Let me know and I would be happy to assist.
Note: As part of repository cleaning effort, this issue will be closed by Sep 20 if no response is received from submitter and/or not further action is required.

Hello @vhvb1989
Thank you for the response.  Please close this issue, as I solved that issue by upgrading to V3.
Regards,
Kumaran


refactor(connector): remove JsonParser from production code

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Following up #16996, this PR removes JsonParser from production code. Close #16968.

Refactor all unit tests in json_parser.rs to use ByteStreamSourceParserImpl to create a (plain) parser to cover the real path.
Move JsonParser to the benchmark of json_vs_plain_parser.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#17016  👈
#16996
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BugenZhao and the rest of your teammates on  Graphite


Implement Graph API search for contacts in new registry front end

Describe the issue
The new registry should use the Microsoft Graph API to look up contacts for project owners and technical leads. A user should only be able to add a contact that they can look up through the microsoft graph API.
Rational/Why
. This way a user cannot add a 'random' person as a contact on a project. Only gov. contacts will be added to projects
Additional Context
This has been implemented in the current registry. The same will need to be implemented in the new registry
Here is the file that fetches the user from the API: https://github.com/bcgov/platform-services-registry-web/blob/main/src/components/forms/UserInput.js
It corresponds to this component in the frontend:

This is the component that you will need to implement the graphapi search. The intended flow is that when creating a user, the graph API will fetch the email of the user such that they can only enter in an email that exists in the graph API.
The graph api will fill out the email field and possibly any of the other fields in the UserInput form. These are email, ministry, firstName, lastName, githubId. I am not sure what information the graph API has, but lets automatically fill out the fields that it provides, the rest will need to filled out manually by the user.
Note Since I am not around to clarify things and you have not worked in this repo before, don't worry if you are not able to get the intended functionality down 100%. Just setting up the graph API will be extremely helpful. I can always take if from there to get the component working all the way.

Would be nice to also have some documentation in the readme about using the Graph API, if this has already been done in the Registry 1.0 readme, then it can be copied over

Dependencies
Alex C has already implemented this once, so there should not be a need to pull in any additional people into this.

This is done, and ready to be merged into the main branch.


Peek does not work here on Win10

Microsoft PowerToys version
0.70.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Peek
Steps to reproduce
Select file in explorer
use cntl/space key combo
nothing happens
check to be sure Peek is enabled
it is
select file on Desktop
click key combo
a brief flash of something shows, perhaps a half-second in duration.
turn off preview feature of QTTabbar
turn off preview window in explorer
repeat tests above.
no change
✔ Expected Behavior
Peek to work as advertised
❌ Actual Behavior
As above
Other Software
Think it's possible that the preview feature of QTTabbar is interfering, but turning it off didn't solve anything, and I have found no other way to test, short of uninstalling, and -- QTTabbar is too valuable to dispense with.
QTTabbar v 104.3
Am also running gadgets, by way of 8GadgetPack v 34.0 and have in the past found some incompatibility on that front.
PowerToysReport_2023-06-01-20-08-24.zip

I am not familiar with QTTabbar but, if it changes the structure of the windows inside the File Explorer window, it is possible that it breaks the IShellView, IShellFolder and IShellItemArray APIs.

Update.  Discovered Helmut has issued v 36 of 8gadgetpack, and so updated to v 36.  Peek now works on the desktop, though I think that it's annoyingly large, but still does not in explorer as enhanced by QTTabbar

Little we can do if an application interferes with public APIs.


make channel names on discover page links

Thanks @daovist! Sean can you review this to make sure it is up to your UI standards? also, the @stealthishow is now green because it is a link, do you think we should keep it that way or change it back to gray?

Thanks for the contribution @daovist!
@liamcardenas I think the green color is good, it looks the same as on the file page.

@daovist - also be sure to check out https://lbry.io/faq/tips
Thanks again for your contribution!

Actually I am seeing that nested links are illegal in HTML5. I just tested and my idea works, but I see an ugly error.
<a> cannot appear as a descendant of <a>

@kauffj thoughts?

@seanyesmunt Not sure of another solution to the nested anchor issue other than just attaching an onClick to a non-anchor element like a <div>. I believe we ran into this on <FileTile> and that's what it does.

I think that would be fine for now. @daovist could you try replacing the wrapper <Link /> to a div and moving the onClick to that? Then you would be able to add the link to the channel no problem. (you would still need to add the e.stopPropagation

I'm trying. The URI it gives me is for the video and I haven't figured out how to get the channel link the way the UriIndicator component does. I'm messing around with lbryuri.js but not having any luck so far.

You should still use the UriIndicator component. Just change the highest level wrapper <Link to a div.
If you still the the navigate action being fired twice you can change the <Link component to use event.stopPropagation()
Maybe something like this
// in UriIndicator/view.jsx

<Link noPropagation />

// inside link/view.jsx
const onClick = (e) => {
  e.stopPropagation();
  props.onClick();
}

You can message me on discord if that doesn't work, a little easier to chat there.

Nested nchors work but are not legit HTML. When I replace  with a  or  it messes up a lot of things throughout LBRY, such as FAQ and TOS links, not to mention navigation. So I added a span value to props which if true returns a  instead of an  which I am using to link to the channel pages of videos on the Discover page.

Could you also squash these commits into one commit?


Favicon

When the tab is pinned, along with many other tabs, it makes it difficult to go there without favicon.

resolved with #36


JEI Auto place crafting (the + button)

The plus (+) in JEI doesnt display when in the crafting terminal unlike AE2 or enderIO if you remember that relic.
Quilt client/server 1.19.2 (newest)
1.19-1.4.6

Update the mod, JEI on fabric/quilt was not supported in that version.

Ah thank you!


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing ad895de...f074878:
  > f074878 :fire: Remove k8s 1.20 APIs (# 6068)
bumping knative.dev/hack da09733...9b2ed84:
bumping knative.dev/serving bd2a436...e648a2f:
  > e648a2f Update net-contour nightly (# 12534)
  > 02417c6 bump ggcr again which includes azure credential timing fixes (# 12539)
  > a4f8b72 Update net-kourier nightly (# 12531)
  > cec1a47 Update net-gateway-api nightly (# 12529)
  > 7826030 Update net-certmanager nightly (# 12530)
  > 30f5c96 Move our CI to GKE 1.21 (# 12509)

/test pull-knative-operator-integration-tests

/lgtm
/approve


ci: Update workflow triggers

Codecov Report

Merging #57 (0d992a3) into main (5cbc6ea) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #57   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           99        99
=========================================
  Hits            99        99


Work on POC for X,Y,Velocity Sensor

hardware POC for photo sensor complete, next task POC for Kinect


Signum

I'm working on some feature enhancements for the atmos package, in which it is useful for various reasons to use indicator functions derived from Num's signum and subtraction instead of using the comparison operators from Ord.
Can we add signum :: (Num a) => Quantity d a -> Dimensionless a (with the obvious implementation) or is there some reason in principle why that is a bad idea?
We would still be respecting the (dimensionally-typed flavor of the) x == signum x * abs x identity.

Works for me. I think I didn't include it from day one because I wasn't certain what would be the desireable return type (Dimensionless a or maybe just a??). But I agree with satisfying the identity so please go ahead!


Support for running with the -m option

When I run docstrfmt with the -m option:
./venv/bin/python -m docstrfmt

I get the error:
No module named docstrfmt.__main__; 'docstrfmt' is a package and cannot be directly executed`

To solve this problem, I have added __main__.py in the same way as other libraries.
Reference:

https://stackoverflow.com/questions/22241420/execution-of-python-code-with-m-option-or-not
https://github.com/PyCQA/isort/blob/main/isort/__main__.py

Feel free to close this PR if you feel it is unnecessary.

Nope, I love the idea. I've just been on a FEMA deployment and I haven't had a chance to handle this.

OK, I'm sorry for rushing you to reply.
I haven't found the best way to test __main__.py. It might be better to exclude __main__.py from the coverage calculation.

OK, I'm sorry for rushing you to reply.
I haven't found the best way to test main.py. It might be better to exclude main.py from the coverage calculation.

No worries! I would include #  pragma: nocover to the top of the file.

Thank you for your suggestion. Will this work well?


Support request by Mingwei He: asking to bypass failed pipeline

As reported in email with subject Can someone help me bypass a failed pipeline for my PR to the 2023-04-01-preview private branch
Currently I did not engage; waiting for somebody from Swagger and Tools Team mailing list to reply.

Closing, as the relevant PR has been merged:

https://github.com/Azure/azure-rest-api-specs/pull/23118


Error running meta init (Ubuntu 16.04 LTS)

Getting the following error when running meta init:
[SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode]
Is this related to the node vs. nodejs version issues noted here:
https://stackoverflow.com/questions/21168141/cannot-install-packages-using-node-package-manager-in-ubuntu/38325376#38325376

Is that the full stack trace of the error you're seeing?

What version of node are you using? node -v

Yep, that is all that is emitted.
v4.2.6

Problem solved. Thanks for the pointer.
Linux novice here so I did not realize that apt-get would not install the latest.  I installed from source it it appears to be working.

No problem. Most people use n or nvm for version management. Cheers.


Kubefactory improvements and auth support

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area cmd
/area pkg

/area docs

/area tests

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #55
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

update(cmd): add support for Kubernetes auth plugins

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

Needs approval from an approver in each of these files:

OWNERS

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

@leogr: PR needs rebase.

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.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten


added methods to handle optional numbers, strings, etc

Love the idea of typesafe json parsing.
There are scenarios where some json fields are optionals.
My pr adds methods to JSONDecoder to allow the developer to declare fields as optionals (Int? as opposed to Int).

sweetness! Thanks


Feature request: Support classic fw

A write command on the ble "wire" to turn the device on looks like:
0200 43A2 9600 0203 0254 FF

The first 3 bytes contain the magic (the first bits seem to be constant 02 and the last 00) so 2 magic/unknown bytes.
Byte 4 starts with a counter, then probably opcode (or unit id) and length followed by the arguments, 54 FF which are the brightness and the temperature.
Other examples:
02D4 1712 FF00 0303 0200 FF # off, same connection as above

02BC 2754 2E00 0203 0254 FF #on (brigtness = 54), another connection
02B6 4C70 6C00 0303 0200 FF #off

The first message from the luminaire looks like this:
25AA 335E 507E AD73 03A2 4D05 00

or
5E62 CE74 5AFC 8793 03A2 4D05 00

4 unknown bytes followed by the state of the luminaire, I would guess.
Any ideas on how to continue, figure out how to compute the magic?

Did you already look at https://github.com/lkempf/casambi-bt-hass/issues/6#issuecomment-1368019222? That's my current state but I'm too busy to continue this until probably august due to my master thesis.
But that seems to confirm that there is no encryption (but still some kind of signature I think) which would make analysis a lot easier.

No, I did not :) Email is out.

0200 43A2 9600 0203 0254 FF

First byte is the auth level (02 for visitor)
The following 4 bytes are the first 4 bytes of the cmac with the network visitor key based on the connection hash + payload including the counter (<8 bytes connection hash> 00 0203 0254 FF)

I am not sure in how far the opcodes match to the evolution firmware, looks different to me..

Based on my analysis of the write commands I can conclude:
0215db43c40004040200b3

First byte is also 02 when using admin credentials
Following 4 bytes 15db43c4: I have no idea how this is calculated
Byte 6 00 is always 00
Byte 7 04 is the counter
Byte 8 04 is the unit id (no opcode in my eyes)
Byte 9 02 is the length of parameters
Byte 10 00 is the dimmer value
Byte 11 b3 can be the temperature value (e.g. Mito soffito) or the vertical value (e.g. Sento with up/down fading)

@lkempf I sent you some frida and bluetooth hci logs that have been recorded at the same time.

Highly appreciate your efforts here! I have 40+ classic devices and cannot afford to upgrade.
Tried to mitm the API/Gateway but it seems to be blocked when SSL certificate is exchanged so I was fearing some encryption...
Would it be another approach to mimic the Casambi Gateway into a (Rest)Api controllable from HA and have the gateway's casambi traffic routed to the API?
I'm not a programmer but let me know if I can contribute in any way. I have the gateway running on a rooted S3 with Lineage 14 and tried to use mitm so far...

Hi guys! Any progress on this and anyway I could help?


timeout

Sorry if this is a bit amateur but does anyone know how to set the timeout in version 0.9? The documentation stated that LocationRequest also specify a timeoutTimer property you can set to abort the request itself if no valid data is received in a certain amount of time. By default it's disabled.
But XCode tells me that LocationRequest has no member timeoutTimer

Property is timeout not timeoutTimer. Sorry about that, I'll fix docs.

Is there a way to handle the timeout? Like is there a callback when a timeout occured? So I can handle appropriately.


Permission check ignores further relationships when a relationship with caveat does not match

What platforms are affected?
linux
What architectures are affected?
amd64
What SpiceDB version are you using?
v1.35.2
Steps to Reproduce
docker-compose.yaml
services:
  spicedb:
    image: "authzed/spicedb"
    command: "serve"
    restart: "always"
    ports:
      - "50051:50051"
    environment:
      - "SPICEDB_GRPC_PRESHARED_KEY=123456"
      - "SPICEDB_DATASTORE_ENGINE=postgres"
      - "SPICEDB_DATASTORE_CONN_URI=postgres://postgres:postgres@database:5432/spicedb?sslmode=disable"
    depends_on:
      - "migrate"

  migrate:
    image: "authzed/spicedb"
    command: "datastore migrate head"
    restart: "on-failure"
    environment:
      - "SPICEDB_DATASTORE_ENGINE=postgres"
      - "SPICEDB_DATASTORE_CONN_URI=postgres://postgres:postgres@database:5432/spicedb?sslmode=disable"
    depends_on:
      - "database"

  database:
    image: "postgres"
    command: -c track_commit_timestamp=on
    ports:
      - "5432:5432"
    environment:
      - "POSTGRES_DB=spicedb"
      - "POSTGRES_PASSWORD=postgres"

schema.yaml
schema: >-
  definition user {}

  /**
   * The count of current entries in the database must be lower than the limit.
   */
  caveat write_limit(limit uint, count uint) {
    count < limit
  }

  definition role {
    relation member: user
  }

  definition database {
      relation writer: role#member with write_limit

      permission write = writer
  }
relationships: |-
  database:listings#writer@role:default#member[write_limit:{"limit":2}]
  database:listings#writer@role:premium#member[write_limit:{"limit":4}]
  role:default#member@user:bob
  role:premium#member@user:bob
assertions:
  assertTrue:
    - 'database:listings#write@user:bob with {"count":3}'
validation: {}

Run

docker compose -f ./docker-compose.yaml up
zed import ./schema.yaml
zed permission check database:listings write user:bob --caveat-context '{"count":3}' --consistency-full

Expected Result
I expected the permission check to succeed, which is the case when running Spicedb with the in-memory database or using zed validate ./schema.yaml.
Actual Result
The permission check fails when using Postgres, MySql or the zed terminal on the Authzed playground.
However, if I switch the values for the limit parameter and have relationships like
 database:listings#writer@role:default#member[write_limit:{"limit":4}]
 database:listings#writer@role:premium#member[write_limit:{"limit":2}]

instead of
database:listings#writer@role:default#member[write_limit:{"limit":2}]
database:listings#writer@role:premium#member[write_limit:{"limit":4}]

the permission check succeeds.
For me, it looks like Spicedb stops evaluation after encountering the first caveat relationship and ignores any further relationships.

@tim-mod Its not a datastore issue but rather something in the redispatcher logic. I've identified the issue and we'll issue a fix (and a point release) over the next few days

@tim-mod PR issued for a fix; once its reviewed and merged we'll issue a release

@josephschorr That's great! Thank you for the quick fix and reply.


Emit STAT table

Should fontmake emit a STAT table for all fonts?
https://www.microsoft.com/typography/otspec/stat.htm

I wonder if this should be the job of ufo2ft instead.

Way low on my priority list of things to do.
On Sun, Dec 4, 2016 at 10:04 AM, Cosimo Lupo<EMAIL_ADDRESS>wrote:

I wonder if this should be the job of ufo2ft instead.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/fontmake/issues/202#issuecomment-264719584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIuK1VE-vIq8EM4_gxRPOyqjdzScTaKks5rEwCZgaJpZM4LDoLH
.

--
behdad
http://behdad.org/

Belongs to varLib.  We are discussing it at https://github.com/LettError/designSpaceDocument/issues/8


Manage M_CONSENT_NOT_GIVEN Matrix error

Add a generic simple webview Activity
Display a dialog to propose the user to give its consent. 'Review now' action opens a webview with a Form to give consent.
Managed requests:

Join/Create/Leave room
Invite/Ban user
Change user name and user avatar
All requests done with the '/' command in a Room

https://github.com/matrix-org/matrix-android-sdk/pull/270 is needed
Fix #2287

Fix #2287


XCFramework support

Now that arm64 Macs exist, iOS binaries now need two arm64 slices (one for arm64 iOS devices, one for arm64 Macs running the iOS simulator) and a fat binary can't contain two slices of the same architecture. The current Cocoapods integration relies on .a fat binaries. Apple's solution to this problem is XCFramework, which separates the binaries for different platforms in different folder in a framework package.
Otherwise, we can't compile for the iOS simulator on the new Macs with arm64 processors:
building for iOS Simulator, but linking in object file built for iOS, file '~/myrepo/Pods/agg/lib/ios/libagg.a' for architecture arm64

@lapfelix I have updated the packages, now those contain xcframework instead of fat library. I haven't tested it though.
Could you update your packages and try?

There seems to be an issue with papki, because the xcframework doesn't get added to my test xcodeproj so I get Undefined symbol papki::xxxxxx errors. However if I manually download the pre-built papki SVGFramework (from here) and drag it into Xcode it does work!
In our case though, we can't really use pre-built binaries because I realized yesterday that papki requires iOS 13 (and we still support iOS 12) because it uses new std::filesystem methods in a function. I fixed it in my fork, but maybe there's a way to make it compatible with iOS 12 by using preprocessor directives to check if the new APIs are available. I can open a story in the papki repo about this specifically (and I could probably fix it myself).
But this is going to be great for iOS 13+ support.

Thanks for testing! I found that in papki I forgot to change library to framework in the podspec. I will fix it shortly.
As for iOS 13... before sdt::filesystem I had implementation via dirent API. I think I could revert it back. I'll make a new papki release today/tomorrow.

It actually appeared easier than I thought. I reverted back dirent implementation for iOS and now it supports iOS 11.0. I don't know, what is the minimum iOS version it is reasonable to support nowadays. Maybe even earlier iOS version could be enough, but I set 11.0 for now, as it is minimum one which does not produce i386 binaries for simulator.
The new papki package of version 1.0.112 is release. Please update your packages and try. Let me know if it works or not. I'm aiming to provide smooth experience when using the libs, there should be no need to hack anything, just install the package.

Actually, I have updated iOS version to 9.0 in all packages

Hi, thank you so much! It works very well. We don't use Cocoapods but I just set up an empty project with the svgren pod, grabbed the xcframeworks and the headers from it and now we have svgren binaries that work with iOS devices and the iOS simulator on the new Macs.


Improve automated functions (like "or specify other") to be translated into other languages.

Edwin is working around this by not using any of the shortcuts. It seems to be working alright for him. I think we should implement shortcuts when people request them. And when we implement shortcuts we should be careful to make them internationalizable.


set the right image for the release

At the moment in case of a release the image gets set to a default value of image: op-skr-registry.localhost:8888/unsigned/manager-images/nats-manager:<version> in the nats-manager.yaml due to an unset IMG var. This commit changes that by setting the var IMG. Also, the script was made more generic by removing references to nats and instead, pass the string "nats" as a var from the ghaw.

Description
Changes proposed in this pull request:

set the right value for the image in the nats-manager.yaml in a release.

Related issue(s)

/cla-recheck

/cla-recheck


Metrics: metrics script accept an yaml as configuration instead os specify all the arguments

https://github.com/ilausuch/project_management_statistics/pull/59


Kismatic Continuing?

Hey, I just saw the news about Apprenda. I'm very sorry.
I wanted to inquire about the state of the project now. Is this project going to be abandoned?

would it make sense to move this repo under kismatic/kismatic instead of apprenda/kismatic, giving the most active committers ownership?

Oh no!

@asultan001 and/or @eriklg - I would be willing to either take over this project and/or create a hard fork. Please let me know if either of you are willing to work with me on this!

@cvega @mjschmidt @burnettk @WillPlatnick  - I am currently reviewing the source code and looking at how difficult it would be to upgrade to 1.13.x. Hopefully @asultan001 or @eriklg get's back to me on how to formally take over this project. Worst case I will fork it and get it back online.

awesome!

Hi @Kralor-Guldan, we are trying to see what are the options with the repo and hope to have an answer very soon. We would love to continue working on it and would welcome your contributions as well so hopefully we can sort this out soon.

@asultan001 - will there be any work done in the meantime? I would like to use this for one of my customers, but can't in good conscience if it's not supported. I don't mind contributing either, just need to know this isn't abandoned.

Our plan is to either try to get the repo transferred to a new home where
we will continue to evolve it or fork the project and evolve it
independently as we were doing prior to the disruption. As for actual
support for the tool, we do provide paid support through a new company
called Nuvalence.io and you are more than welcomed to reach our sales
department directly<EMAIL_ADDRESS>to find out about support rates.
On Thu, Oct 4, 2018 at 6:45 PM Kralor-Guldan<EMAIL_ADDRESS>wrote:

@asultan001 https://github.com/asultan001 - will there be any work done
in the meantime? I would like to use this for one of my customers, but
can't in good conscience if it's not supported. I don't mind contributing
either, just need to know this isn't abandoned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apprenda/kismatic/issues/1273#issuecomment-427193430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGe2GJraQ0XhA1FSZUBXKd1BMuoUBSZ4ks5uho-OgaJpZM4VqTbL
.

@Kralor-Guldan I used to work on this project under @asultan001 back at Apprenda. I'd be interested in continuing to work on this in spare time. It's a tool I believe is valuable (and actually wished was up-to-date just yesterday). If you want to hard fork it, just shoot me a message where it is and I'll cook up some PRs in my spare time.

@based64god @asultan001 Also interested in working this, only allowed if the product is open source due to laws (:

@TimMeade and @mjschmidt  - I've abandoned this effort and moved onto Rancher 2.x. Couldn't wait for the old team to figure things out.

@mjschmidt KET is Apache-2.0 licensed. You can fork it and modify/distribute it however you want. You just can't use any of the trademarks (IE, you'd probably have to change the name and logos wherever they appear).

@Kralor-Guldan agreed. heading the same way.

@Kralor-Guldan If you all have questions around Rancher 2.x or RKE, feel free to reach out (jvb on the Rancher-Users and Kubernetes slack channels) .  I'm with Rancher Labs now (formerly Apprenda)


Multiple code cells connected to the same sandbox

Hi there, is it possible to have multiple code cells connected to the same sandbox. E.g.  the second sandbox below currently doesn't work.

Realize this probably won't work now because of statefulness. A potential alternative would be to allow for hidden code to be pre-executed before the cell is run...
Here is the use case I'm trying to solve: I'm building an iterative interactive tutorial, and I don't want to keep repeating the code from the last cell every time.

I also just tried this example, but it didn't work for me (at least in Docusaurus).


Non http links are not clickable (cbthunderlink)

Description
Using the main intance https://gitea.com I am unable to insert non-http emails. In particular I am interested to add links to my emails (I use the tool only internally) provided by the https://camiel.bouchier.be/en/cb_thunderlink extension. Unfortunately links like cbthunderlink://somebase64string are not clickable, even if I explicitely use the longer url notation:
See you can't click me [cbthunderlink://somebase64string](cbthunderlink://somebase64string)

Gitea Version
1.18.0+dev-333-g9e0c43777
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots

Git Version
No response
Operating System
No response
How are you running Gitea?
Using the instance from https://gitea.com
Database
No response

There is an config option. markdown.CUSTOM_URL_SCHEMES

Hum good to know… but I guess it will not work if I do not own the server (which is my case)… Is there any security reason for this limitation?

I believe security is the main concern (although it's not designed by me).
Some schemes/protocols could lead to security problem.

I would agree with you if there is no more security concern. The code is as old as year 2014 and 2016
https://github.com/go-gitea/gitea/commit/3a9fd81f5946cbd70390b9c061bdcd1842f29735
https://github.com/go-gitea/gitea/commit/a4cbe79567072befd96cf1b7eb319de1e2809ca3

Ok perfect then!


[directx12-agility] New port for using Microsoft.Direct3D.D3D12

The directx-headers port already provides the latest DirectX 12 headers from the GitHub project that hosts them, as well as the "GUIDS" library.
This new port adds VCPKG support for using the DirectX 12 Agility SDK redistributable binaries in a project.

I had originally considered adding this as a feature to directx-headers, but since it has its own license that seemed problematic (the directx-headers content is MIT). Therefore, this new port lists directx-headers as a dependency.
For an example of how one would consume this, see:
https://github.com/walbourn/directx-vs-templates/pull/74/files

Verified supported triplets locally:
.\vcpkg install directx12-agility:x86-windows
.\vcpkg install directx12-agility:x86-windows-static
.\vcpkg install directx12-agility:x86-windows-static-md

.\vcpkg install directx12-agility:x64-windows
.\vcpkg install directx12-agility:x64-windows-static
.\vcpkg install directx12-agility:x64-windows-static-md

.\vcpkg install directx12-agility:arm64-windows
.\vcpkg install directx12-agility:arm64-windows-static
.\vcpkg install directx12-agility:arm64-windows-static-md

.\vcpkg install directx12-agility:x64-mingw-static
.\vcpkg install directx12-agility:x86-mingw-static

Thanks!


Updating to "4.15.0-0.okd-2024-03-10-010116" from "4.14.0-0.okd-2024-01-26-175629"

Describe the bug

Unable to apply 4.15.0-0.okd-2024-03-10-010116: wait has exceeded 40 minutes for these operators: machine-config
Version

UPI install method
4.14.0-0.okd-2024-01-26-175629
How reproducible

The upgrade is stuck since 2 days... ..All Cluster Operator have been updated, exceptmachine-config (of course)
NAME                                       VERSION                          AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication                             4.15.0-0.okd-2024-03-10-010116   True        False         False      11m
baremetal                                  4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
cloud-controller-manager                   4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
cloud-credential                           4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
cluster-autoscaler                         4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
config-operator                            4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
console                                    4.15.0-0.okd-2024-03-10-010116   True        False         False      37m
control-plane-machine-set                  4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
csi-snapshot-controller                    4.15.0-0.okd-2024-03-10-010116   True        False         False      40d
dns                                        4.15.0-0.okd-2024-03-10-010116   True        False         False      40d
etcd                                       4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
image-registry                             4.15.0-0.okd-2024-03-10-010116   True        False         False      2d11h
ingress                                    4.15.0-0.okd-2024-03-10-010116   True        False         False      2d11h
insights                                   4.15.0-0.okd-2024-03-10-010116   True        False         False      40d
kube-apiserver                             4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
kube-controller-manager                    4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
kube-scheduler                             4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
kube-storage-version-migrator              4.15.0-0.okd-2024-03-10-010116   True        False         False      27h
machine-api                                4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
machine-approver                           4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
machine-config                             4.14.0-0.okd-2024-01-26-175629   True        True          True       27h     Unable to apply 4.15.0-0.okd-2024-03-10-010116: error during syncRequiredMachineConfigPools: [context deadline exceeded, failed to update clusteroperator: [client rate limiter Wait returned an error: context deadline exceeded, error MachineConfigPool infra is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 0)]]
marketplace                                4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
monitoring                                 4.15.0-0.okd-2024-03-10-010116   True        False         False      27h
network                                    4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
node-tuning                                4.15.0-0.okd-2024-03-10-010116   True        False         False      27h
openshift-apiserver                        4.15.0-0.okd-2024-03-10-010116   True        False         False      37m
openshift-controller-manager               4.15.0-0.okd-2024-03-10-010116   True        False         False      2d11h
openshift-samples                          4.15.0-0.okd-2024-03-10-010116   True        False         False      2d11h
operator-lifecycle-manager                 4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
operator-lifecycle-manager-catalog         4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
operator-lifecycle-manager-packageserver   4.15.0-0.okd-2024-03-10-010116   True        False         False      40d
service-ca                                 4.15.0-0.okd-2024-03-10-010116   True        False         False      47d
storage                                    4.15.0-0.okd-2024-03-10-010116   True        False         False      47d

Name:         machine-config
Namespace:
Labels:       <none>
Annotations:  exclude.release.openshift.io/internal-openshift-hosted: true
              include.release.openshift.io/self-managed-high-availability: true
              include.release.openshift.io/single-node-developer: true
API Version:  config.openshift.io/v1
Kind:         ClusterOperator
Metadata:
  Creation Timestamp:  2024-07-01T00:12:11Z
  Generation:          1
  Owner References:
    API Version:     config.openshift.io/v1
    Controller:      true
    Kind:            ClusterVersion
    Name:            version
    UID:             0d23cbeb-28af-4e38-aae2-bb62d5a52858
  Resource Version:  27496717
  UID:               05ae4ecf-092c-43de-919d-66a13ab07d6f
Spec:
Status:
  Conditions:
    Last Transition Time:  2024-08-16T18:00:18Z
    Message:               Working towards 4.15.0-0.okd-2024-03-10-010116
    Status:                True
    Type:                  Progressing
    Last Transition Time:  2024-08-16T18:33:49Z
    Message:               Unable to apply 4.15.0-0.okd-2024-03-10-010116: error during syncRequiredMachineConfigPools: [context deadline exceeded, failed to update clusteroperator: [client rate limiter Wait returned an error: context deadline exceeded, error MachineConfigPool infra is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 0)]]
    Reason:                RequiredPoolsFailed
    Status:                True
    Type:                  Degraded
    Last Transition Time:  2024-08-16T17:32:11Z
    Message:               Cluster has deployed [{operator 4.14.0-0.okd-2024-01-26-175629}]
    Reason:                AsExpected
    Status:                True
    Type:                  Available
    Last Transition Time:  2024-08-16T18:03:50Z
    Message:               One or more machine config pools are degraded, please see `oc get mcp` for further details and resolve before upgrading
    Reason:                DegradedPool
    Status:                False
    Type:                  Upgradeable
  Extension:
    Infra:   pool is degraded because nodes fail with "1 nodes are reporting degraded status on sync": "Node worker0.bomar.bme.lab is reporting: \"command \\\"/usr/bin/rpm -qf /etc/audit/rules.d/mco-audit-quiet-containers.rules\\\" returned with unexpected error: error: file /etc/audit/rules.d/mco-audit-quiet-containers.rules: Permission denied\\n: exit status 1\""
    Master:  pool is degraded because nodes fail with "1 nodes are reporting degraded status on sync": "Node master0.bomar.bme.lab is reporting: \"command \\\"/usr/bin/rpm -qf /etc/audit/rules.d/mco-audit-quiet-containers.rules\\\" returned with unexpected error: error: file /etc/audit/rules.d/mco-audit-quiet-containers.rules: Permission denied\\n: exit status 1\""
    Worker:  pool is degraded because nodes fail with "1 nodes are reporting degraded status on sync": "Node worker3.bomar.bme.lab is reporting: \"command \\\"/usr/bin/rpm -qf /etc/audit/rules.d/mco-audit-quiet-containers.rules\\\" returned with unexpected error: error: file /etc/audit/rules.d/mco-audit-quiet-containers.rules: Permission denied\\n: exit status 1\""
  Related Objects:
    Group:
    Name:      openshift-machine-config-operator
    Resource:  namespaces
    Group:     machineconfiguration.openshift.io
    Name:
    Resource:  machineconfigpools
    Group:     machineconfiguration.openshift.io
    Name:
    Resource:  controllerconfigs
    Group:     machineconfiguration.openshift.io
    Name:
    Resource:  kubeletconfigs
    Group:     machineconfiguration.openshift.io
    Name:
    Resource:  containerruntimeconfigs
    Group:     machineconfiguration.openshift.io
    Name:
    Resource:  machineconfigs
    Group:
    Name:
    Resource:  nodes
    Group:
    Name:      openshift-kni-infra
    Resource:  namespaces
    Group:
    Name:      openshift-openstack-infra
    Resource:  namespaces
    Group:
    Name:      openshift-ovirt-infra
    Resource:  namespaces
    Group:
    Name:      openshift-vsphere-infra
    Resource:  namespaces
    Group:
    Name:      openshift-nutanix-infra
    Resource:  namespaces
    Group:
    Name:      openshift-cloud-platform-infra
    Resource:  namespaces
  Versions:
    Name:     operator
    Version:  4.14.0-0.okd-2024-01-26-175629
Events:       <none>

All MC have Degraded status.
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
infra    rendered-infra-8461b7c208fd913262052c7193981d72    False     True       True       3              0                   0                     1                      28d
master   rendered-master-f43c37629059b8c27126b806bffb01cd   False     True       True       3              0                   0                     1                      47d
worker   rendered-worker-8461b7c208fd913262052c7193981d72   False     True       True       1              0                   0                     1                      47d

NAME                    STATUS   ROLES                  AGE   VERSION
master0.bomar.bme.lab   Ready    control-plane,master   47d   v1.27.9+e36e183
master1.bomar.bme.lab   Ready    control-plane,master   47d   v1.27.9+e36e183
master2.bomar.bme.lab   Ready    control-plane,master   47d   v1.27.9+e36e183
worker0.bomar.bme.lab   Ready    infra                  40d   v1.27.9+e36e183
worker1.bomar.bme.lab   Ready    infra                  40d   v1.27.9+e36e183
worker2.bomar.bme.lab   Ready    infra                  40d   v1.27.9+e36e183
worker3.bomar.bme.lab   Ready    worker                 40d   v1.27.9+e36e183

Log bundle

The must-gather is too big, ~40MB.

Can you check #1928? This seems to be a duplicate of that discussion.

Great, I've applied the workaround, and MCO doesn't complain anymore. Thanks :)