on_message_complete callback doesn't invoke after an answer from squid proxy server

Hello.
After the CONNECT request the squid proxy server response
"HTTP/1.1 200 Connection established\r\n\r\n".
After parsing this string the "on_message_complete" callback doesn't invoke.
I use code below:
http_parser _parser = {0};
http_parser_settings _parserSettings = {0};
_parserSettings.on_message_complete = onMessageComplete; // callback
.........
http_parser_init(&_parser, HTTP_BOTH);
size_t offset = http_parser_execute(&_parser, &_parserSettings,.........

That's because "Content-Lenght" is not part of the response. In this case, you should perform one more recv call on the socket, obtain zero bytes and call:
http_parser_execute(&parser, &settings, your_empty_buf, 0);
and http_parser will call on_message_complete this time.

I just wanted to say, thank you for this. It made my day.

That's because "Content-Lenght" is not part of the response. In this case, you should perform one more recv call on the socket (you should do it anyway, because there is no any evidence that squid is not going to send some message body), obtain zero bytes and call:
http_parser_execute(&parser, &settings, your_empty_buf, 0);
and http_parser will call on_message_complete this time.

But how can one know that another rcv call on the socket is required?


[CPI] Option to ignore OpenStack Cinder availability zone, bsc#1095572

Ignore OpenStack Cinder avability zone when attaching volumes.
When Nova and Cinder have different availability zones,
this should be set to true. Default is false.

 Bug 1095572 - [ CPI ] Scheduling pods with automatic PersistentVolumenClaim doesn't work


Documentation improvements.

Fix some linking, some grammar, some typos, etc.

Codecov Report

Merging #1524 (1634cb1) into main (1a2ba70) will increase coverage by 0.00%.
The diff coverage is 66.66%.

@@           Coverage Diff           @@
##             main    #1524   +/-   ##
=======================================
  Coverage   93.81%   93.81%
=======================================
  Files         247      247
  Lines       45839    45839
=======================================
+ Hits        43002    43004    +2
+ Misses       2837     2835    -2

Impacted Files
Coverage Δ

common/src/lib.rs
89.33% <ø> (ø)

common/src/writer.rs
94.11% <ø> (ø)

query-grammar/src/query_grammar.rs
99.67% <ø> (ø)

src/collector/facet_collector.rs
98.00% <ø> (ø)

src/collector/mod.rs
48.21% <ø> (ø)

src/core/searcher.rs
77.93% <ø> (ø)

src/directory/directory.rs
90.14% <ø> (ø)

src/directory/directory_lock.rs
88.88% <ø> (ø)

src/directory/mmap_directory.rs
91.08% <ø> (ø)

src/directory/ram_directory.rs
88.81% <ø> (ø)

... and 12 more

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

Force updated to fix the formatting check failure.


What is the scope of the task?

Hey @ginobili ,
I have a question about the scope of the task. Is the infrastructure subject of the task (e.g. CI/CD pipeline), or only the code itself (or things that can be written in code)?
Thank you in advance.

@tuskajozsef
Good question. Only things written in the code itself. Infrastructure like servers or CI/CD are not part of the scope.


⚠ SolarQuery has degraded performance

In f8a2005, SolarQuery ($SOLARQUERY_URL) experienced degraded performance:

HTTP code: 200
Response time: 3812 ms

Resolved: SolarQuery performance has improved in 718f7fd after 13 minutes.


Update README

re-format
add RTD link
fix some typos

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

Comparison is base (7c71053) 60.61% compared to head (ce0e06a) 60.72%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #69      +/-   ##
===========================================
+ Coverage    60.61%   60.72%   +0.10%
===========================================
  Files           14       14
  Lines         1521     1515       -6
===========================================
- Hits           922      920       -2
+ Misses         599      595       -4

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

Nice, thanks! Was the formatting automatic or manual?

Mostly auto :sweat_smile:

Nice, thanks! Was the formatting automatic or manual?

 I can try to integrate it into CI or pre-commit.

Nice, thanks! Was the formatting automatic or manual?

 I can try to integrate it into CI or pre-commit.

IDE. Required some intervention. For non-code, I'd only do that in a supervised manner.


Read packets from resources instead of hard code

Deca updated packet ids again. Maybe it would be a good idea to read packets externally through an xml file :)
After I update my own packets I'll work on a pull request.

Packets are already updated in the repos

And i wanted to use an xml for the packet id's for the longest time now, the problem with C++ is that enum's (which is what the packet types are right now) are defined at compile time. So there is no way to set the value of an enum after compiling.
I havent quite figured out how best to handle defining packet id's at run-time yet.

Mm, looks like krelay just makes a few dictionaries. (unordered maps)
http://prntscr.com/ekvtxk

Yup. That is the basic idea outside of using an enum. The problem is comparing a string value (from the xml) to an enum. Otherwise i have to create a giant if/else statement going "if(stringvalue == "FAILURE") return PacketType::FAILURE;" etc etc etc.
But i think i almost have something almost similar working. Still trying to get the logic correct on it though.

cool i got it working. Im surprised it worked first try, thats extremely rare for me lol
anyways the way i did it is pretty different from k-relay. I had to change the macros i was using for creating the PacketType enums. You can see how the PacketTypes are defined in the file "packets/PacketTypes.h", and then you can see the macros that are being used in "utilites/EnumToString.h". I had to change the macros a bit, but the nice thing is i already had it so the enums got created as both an enum value and a string value. So i created an unordered_map<string, int> and filled that will the values from packets.xml. Then all the packet classes i had to change the packet->id to packet->type and had that variable be a PacketType. In the sendPacket function i simply call my function that gets the string version of the PacketType enum and then i can get the actual id value from the map. Working the other way was a bit tricky though. Having to convert an int into a string, and then a string into a PacketType was a bit weird, but luckily the idea i had worked.
So yeah, havent pushed this to the master branch yet (its pushed to the "packet-handler-test" branch). Im most-likely going to be merging the "packet-handler-test" branch with the "master" branch soon. I like the change from an if/else statement into a function handler. As well as a few other things i added to the packet-handler-test branch. So look/pull from that branch if you want to use the updated code. Ill probably do the merge later tonight after i verify that theres nothing i left out from the original master branch.


The throughput of phantun is only half that of udp2raw

wireguard over phantun with faketcp

wireguard over udp2raw with faketcp

native tcp

openvpn over udp2raw with faketcp

Please provide more information such as your config and setup, otherwise this won't be reproducible.

 With single core the multi core capability of Phantun becomes a disadvantage because of additional synchronization overhead to support it.


remove private maven & make gradlew executable

Just 3 tiny changes to allow other people to build and contribute to geckolib:

I replaced the private cloudsmith maven repository that apparently contains parchmentmc data with their public maven.
I made the gradlew files executable. This allows linux and macos users to easily run it.
Include the gradle wrapper files for Fabric (they were gitignored previously)

As per comment in Discord.

Sorry about the maven thing. I guess it just was a gradle hiccup of some sort. I Reverted that change.
It's not showing up here, probably because you closed the PR? I also can't seem to reopen it.


Specify a version

Hi, I've got this issue
Warning: Must specify version Use --force to continue.

Aborted due to warnings.

While my gruntfile is something like this (in coffee) :
    electron:
      build:
        options:{
          name:'Project',
          version:'0.32.0',
          dir:'app',
          out:'dist',
          plateform:'all',
          arch:'all'
        }

From the top of the readme:

Issues should be reported on the electron-packager issue tracker.


Workflow based tutorial for Tensorflow CNN training on MNIST data

This PR adds an example for training a Tensorflow CNN to recongnise handwritten digits using an MNIST dataset.

Hi @snehal-das , could you address the DCO job failure, by signing your commits?
git commit -s -m "..."

@snehal-das, could you try rebasing in an attempt to fix the GaNDLF test failure in the CI?


Function naming for C and language API's

there are a set of functions in the C shared library named like
helicsPublicationPublishXXX(pubid, value) or similar
I am wondering if it would be inconsistent to drop the Publication so they are
helicsPublishXXX(... ) instead.
likewise
helicsInputGetXXX  or helicsInputSetDefualt(...)
to helicsGetXXX or helicsSetDefault(...)
Basically dropping the Publication or Input for some functions that will be commonly used and have some redundancy in the name.
My reluctance is that it isn't totally consistent with the function names being helics  but on the other hand it is simpler and I don't think changes the information in the name, and might be a little more obvious for the transition to 2.0 as many functions will go from helicsSubscriptionGetXXX to helicsInputGetXXX which might be non obvious if you generated with the subscription convenience function.
Thoughts?

It sounded like the consensus was to leave the functions names as is to maintain consistency in the naming conventions.


Accelerate and Metal integration

Boost performance and reduce usage of unnecessary math libs on iOS and macOS

This needs to happen in the JavaCPP Presets:
https://github.com/bytedeco/javacpp-presets/issues/436
https://github.com/bytedeco/javacpp-presets/pull/444

Metal should be like CUDA for macos.
So kernels, loops etc are to be considered...
вт, 10 окт. 2017 г. в 0:20, Samuel Audet<EMAIL_ADDRESS>
Closed #501 https://github.com/deeplearning4j/libnd4j/issues/501.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deeplearning4j/libnd4j/issues/501#event-1284931863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALru_98yUCF0T97nK6NmFkndzXaiwEbSks5sqo4RgaJpZM4PxyPD
.


Stabilize test setup with toolchains

This commits makes sure that samples are never tested with toolchains
auto detection or download enabled. This will prevent flakiness on CI.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


Error: ListView is deprecated and removed from React Native

On app launching, this error is shown on my Emulator:
**

ListView has been removed from React NAtive

.**
ListView is used in KeyboardAwareListView. It is now depreacated.
Kindly fix this issue.
Thanks.

I am having the same issue - can't run any applications.

@SaimAhmedSheikh Are you sure it is because react-native-vector-icons do not relate to the list view. ListView is a different component and deprecated in the RN0.60 and after.


ARROW-103: Add files to gitignore

Patches ARROW-103, though perhaps it would make sense to leave that issue open to cover any future .gitignore-related pull requests.

+1, looking good.

Can you change it to exclude all *-build directories? We can encourage that pattern in out-of-source builds, then (I've been using test-build, release-build, etc.)

Thank you. +1


New Feature: Swerve tweaks

Current problem
Need to look over the drive subsystem and make any necessary tweaks for the test bot.
Solution should be like
Change of necessary constants so that the swerve runs smoothly and change gyro to pigeon
Considered alternatives
Do whatever will improve the functioning of the subsystem, if need be do more than what is stated in the solution.
Acceptance Criteria

identify necessary swerve tweaks
Change all affected consts.
Pigeon implemented with no errors
Driver controller must be responsive but not sensitive (drive team must confirm)

List of identified things

Wheel Base (done)
Wheel Diameter (done)
Controller deadband

All work for implementing field relative drive should be done on #6 . Changing gyro to pidgeon is required for completion of this issue, but field relative implementation is not required for completion of this issue.

2024/11/21 18:00 -- Testing Results:
Expectations:
A. During this test, the robot should drive relative to itself as a measure of simplicity to test the swerve modules and drive subsystem.
	- When moving forward, the robot should move towards its front (opposite the battery).
	- When moving left, the robot should move to the left relative to its front
	- When moving right, robot should move right
	- When moving backwards, the robot should move opposite to its front.
	- When turning the robot, these reference points should remain the same.
B. Driver controller should be responsive yet not overly sensitive
C. Speed of robot should be relative to joystick position; ie. moving slightly forward should not max out speed

Observations:
- Test A passed successfully; robot was able to drive relative to its own position and maintain relativity as expected.
- Test B failed; both thumbsticks are too sensitive.
- Test C passed successfully; robot speed is relative to joystick input.
- During an unrelated test, we attempted to test field oriented drive. Forward was defaulting to its front-left corner,
  and rotating the bot seemed to change its relative heading as well.
	(note: Field Relative testing should occur on issue #6, and should have separate test cases)

Testing Summary
Robot centric drive functions flawlessly indicating the swerve modules are configured properly. Need to update controller deadband to reduce sensitivity.
As a sidenote, all testing should relate to one single issue, and all testing results should be documented. Testing expectations can be formulated from the acceptance criteria of the issue being tested. Tests pass when the observations match expectations set by cross-team collaboration
If you have any questions about documenting test results or coming up with test cases, please reach out to me.

Have the controller sensitivities been adjusted according to our testing results? We may close this issue after this has been resolved. If issues come up from something broken later, we can create bug reports.

Branch should be assigned to #8 but we have some things we should do first:

gyro should currently have all working code committed to it. However, it's outdated because the fix for #6 was committed to swerve-tweaks.

Revert 9940c27dbeeac175985eadf16eb7e945e15bde59 from swerve-tweaks
Apply those reverted changes manually to gyro.
This will clean up swerve-tweaks and properly update gyro with fixes for #6 .

Let's also create a new branch called swerve to represent our working swerve subsystem code. swerve-tweaks was a branch we used to fix #4 , and when #4 is tested and approved, we can merge swerve-tweaks to swerve.
Now, gyro and swerve can be considered "working branches" where we ensure these subsystems contain only working code. I will look into protecting these branches from developmental commits.
Create a new branch for this issue

Name example: 8-swerve-drift-fix
Target repository should be set to Auth-Xero/9430-offseasonSwerve
Click "Change Branch Source" and select swerve as the branch source.

This is because we want to create a new branch based on only working changes. Other branches working on fixes for other issues related to our drivetrain may be in progress, so branching our fixes from working code will allow others to merge their fixes into swerve without affecting our work.

Click "Create Branch" and checkout the branch locally to VScode. This can be done by running git checkout origin/8-swerve-drift-fix.

This will automatically create a new local branch called 8-swerve-drift-fix and set its upstream to the origin branch of the same name. (git push will push changes to origin/8-swerve-drift-fix)

Do code and practice properly committing changes.

Since we are fixing a bug related to the swerve drivetrain, we will want to eventually merge #8 into swerve (our "working swerve" branch) using a pull request to coordinate this effort.


Should this distribution offer generic type implementations?

The text proposed in 1e8a758a38429078d40ef04741aeae0cdc7f3dd0 (#5) suggests that just about all implementation should eventually be removed from this distribution, leaving only the role itself.
However, the Point type already exists as what is basically a self-contained type, thanks to the existence of the new() constructor. So, with 1e8a758a38429078d40ef04741aeae0cdc7f3dd0 removing the documentation of the data structure itself, we already have achieved encapsulation – as far as you can get with old-style Perl, anyway.
We could decide to give Node, Relationship, and Path the same treatment: Offer a new() constructor for them, so that drivers can choose to use Neo4j::Types’ implementation after all without needing to know any internals.
Question is: Would they make that choice?
The generic type might well make sense for Point, which can be constructed by users and passed on to Neo4j as a parameter. (In theory, anyway – as of right now, no Perl module actually supports this.)
But for Node, Relationship, and Path I’m not sure I really see this use case. And even consistency is a weak argument because these types are different from Point.
So I’d tend towards maybe offering a generic implementation for Point, but not for the others.

There’s nothing wrong with a generic Node / Relationship / Path implementation as such, but there is no reason the role itself should provide one. If such a generic implementation exists, better to have additional modules for that. In fact, those should probably be in another distribution entirely, so that users who don’t need them don’t even need to install them.
However, for Point and other Cypher property types, there has to be a way to create them locally. Given that, offering a generic implementation would actually be useful: It might free drivers authors from having to implement and document a new() constructor; users could just use "new" in Neo4j::Types::Point. Additionally, it would give driver authors an incentive to accept Neo4j::Types::Point values created elsewhere; e.g. "run_query" in Neo4j::Bolt::Cxn should eventually accept Neo4j::Driver::Type::Point values.
Bottom line: No change required here.


support --insecure-registry for nerdctl build

What is the problem you're trying to solve
The problem is that if I use it directly in the pod, I can pull the image directly, but not in the Dockerfile
nerdctl pull --insecure-registry xxxx:30003/zikayou/serverjre:v1
time="2022-09-06T11:00:27Z" level=warning msg="skipping verifying HTTPS certs for "xxxx:30003""
xxxx:30003/zikayou/serverjre:v1: resolving |�[32m�[0m--------------------------------------|
elapsed: 0.1 s total: 0.0 B (0.0 B/s)
xxxx:30003/zikayou/serverjre:v1: resolved |�[32m++++++++++++++++++++++++++++++++++++++�[0m|
manifest-sha256:735c9e6406bc633a27735f93ae23b61b5a801d66010a3cce570938ca2331cc88: waiting |�[32m�[0m--------------------------------------|
elapsed: 0.2 s total: 0.0 B (0.0 B/s)

nerdctl build --insecure-registry -t xxxx:30003/zikayou/springboot-demo:v0.0.4 .
Dockerfile:1

1 | >>> FROM xxxx:30003/zikayou/serverjre:v1
2 | RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone
3 | ADD target/springboot-demo-0.0.1-SNAPSHOT.jar /springboot-demo-0.0.1-SNAPSHOT.jar

error: failed to solve: xxxx:30003/zikayou/serverjre:v1: failed to do request: Head "https://xxxx:30003/v2/zikayou/serverjre/manifests/v1": x509: cannot validate certificate for xxxx because it doesn't contain any IP SANs
time="2022-09-06T11:00:36Z" level=fatal msg="unrecognized image format"

Source  https://github.com/containerd/nerdctl/discussions/1362
Describe the solution you'd like
nerdctl build --insecure-registry -t xxxx:30003/zikayou/springboot-demo:v0.0.4 .    => should work
Additional context
No response

nerdctl build --insecure-registry -t xxxx:30003/zikayou/springboot-demo:v0.0.4 . => should work
He is not a good way to solve my problem

nerdctl build --insecure-registry -t xxxx:30003/zikayou/springboot-demo:v0.0.4 . => should work
He is not a good way to solve my problem

So what is the good way ?

I don't have any other good solutions. The question is why can't nerdctl use build in the pod to pull up the image specified by "from" in the dockerfile?

nerdctl build --insecure-registry -t xxxx:30003/zikayou/springboot-demo:v0.0.4 . => should work
He is not a good way to solve my problem

@l1douhua So what is the good way ?

I don't have any other good solutions. The question is why can't nerdctl use build in the pod to pull up the image specified by "from" in the dockerfile?


[Question] HipGraph & support for device graph launch

Hello everyone,
I'm working on some implementations requiring an great level of determinism. A very interesting feature of cudaGraph since CUDA 12.0 allows to launch graph within the GPU. Is there an ambition to propose the same feature on HIP? I think it would be very interesting for professional applications.
Thank you.

@Kawaboongawa Can you please check with latest ROCm 6.0.2 (HIP 6.0.32831)? Thanks!

@Kawaboongawa Sorry for the lack of response.  Will check internally and let you know. Thanks!

Hi @Kawaboongawa,
Good question! We currently have support for launching graphs through hipGraphLaunch, which is similar to the cudaGraph feature cudaGraphLaunch: Cuda Graph Launch. You can find the documentation for hipGraphLaunch, as well as other hipGraph features here: HIP Graph Management.


Examples needed

This looks like a very useful library, but it's hard to pick it up easily without some examples in the documentation. The tests are somewhat helpful, but it would be great to have some straightforward examples of common usage in the README.

That's fair feedback. I left some super high-level notes in the docs, but nothing really complete. I'll leave this open to remind me to write something better.
@lewisd32 any chance you want to take a crack at this? It might take me a while to put something together, whereas I seem to recall you're using this on a regular basis right now.

Example will be very helpful

I've been meaning to get to this for a while, but I've been pretty slammed. I've finally cobbled these together from a codebase that is using this. If someone else wants to put these in a pull request to add to the documentation, that would be awesome. I don't know when I'll be able to get to that.
Your configuration needs to implement CrossOriginFilterFactoryHolder:
import io.dropwizard.Configuration;
import ca.grimoire.dropwizard.cors.config.CrossOriginFilterFactory;
import ca.grimoire.dropwizard.cors.config.CrossOriginFilterFactoryHolder;

public class MyConfiguration extends Configuration implements CrossOriginFilterFactoryHolder {
    private CrossOriginFilterFactory cors = new CrossOriginFilterFactory();

    public void setCors(final CrossOriginFilterFactory cors) {
        this.cors = cors;
    }

    @Override
    public CrossOriginFilterFactory getCors() {
        return cors;
    }
}

And then in your Application class, you need to add the CorsBundle:
import ca.grimoire.dropwizard.cors.CorsBundle;

import io.dropwizard.Application;
import io.dropwizard.setup.Bootstrap;

public class MyApplication extends Application<MyConfiguration> {

    @Override
    public void initialize(final Bootstrap<MyConfiguration> bootstrap) {
        bootstrap.addBundle(new CorsBundle<MyConfiguration>());
    }

}

In your application's config file, you can do this if you simply want to allow everything:
cors:
  origins: "*"

I make no statements about the advisability of configuring CORS that way. Your needs may differ.

I found time after all. :smile:

I've been out of town - so I didn't have a chance to look at this until now. Thanks for submitting a patch!


migrate favicons from app.decenterai.com

Related Issue(s)
Fixes #46

For #
Proposed Changes

[x]

Checklist

[x] I have followed the repository's contribution guidelines.
[x] I have added necessary documentation or updated existing documentation.
[x] My code follows the established code style and formatting of the project.
[x] I have tested my changes and they function as expected.
[ ] I have added suitable unit tests (if applicable).

Screenshots

To-Do

[ ]

Additional Information

@utkarsh-1602 it seems like something has gone wrong: https://realfavicongenerator.net/favicon_checker?protocol=https&site=decenterai-92nb29cz6-decenter-ai.vercel.app

fix it:

fix it:

Overrided by #48


Vite 4 uses Rollup 3

Vite 4 uses Rollup 3. Pretty sure this package should depend on
"rollup": "^3.0.0"

and devDependancies:
"vite": "^4.0.0"

I think rollup should be in devDependencies, since it is only used for type imports..?

@gxmari007 Can we move rollup to devDependencies?


Utillize webdriverio + chrome options for metamask interactions (SPIKE)

https://www.guru99.com/chrome-options-desiredcapabilities.html
WebdriverIO framework supports chromedriver , chromedriver has various options with one of them being able to interact / install a  chrome extension. In this case we should look to utilize  this for metamask interactions

Looks like this is not possible to run on github CI, as chromedriver does not support extensions.
Next step is to try out a HTTP provider :+1: to avoid MM all together


Feature Request: Update/New Only

This feature would only consider importing rows that either create new entries or update existing ones (or both) depending on the setting selected. There could be a 'Filter' drop-down that lets users say 'Import All,' 'Update Only,' or 'New Only.'
I will try to take a stab at this when I'm able.

This would solve so much for me. i frequently clean an import file to avoid making new entries.

I vote for reopening this one.


Refactoring needed

Stuff to change:

[x] Pull out parsing of HAElements from the multiple places it's implemented and put it into one function
[x] Same thing with reminders
[x] Documentation
[x] Extract getDateDiff out of HomeworkUpdater
[ ] Use the new HAElement class instead of a preference for done items

Last point might not be possible currently as the list of HAElements is completely destroyed and rebuilt when the homework is downloaded again.


proxy.golang.org: i/o timeout frequently get i/o timeout when using bazel/gazelle

What is the URL of the page with the issue?
https://proxy.golang.org/
What is your user agent?
bazel 5.4.1 + bazel gazelle 0.33.0
Screenshot
Error looks like this:
(16:45:36) ERROR: /app/WORKSPACE:133:16: fetching go_repository rule //external:com_github_google_s2a_go: Traceback (most recent call last):
--
  | File "/root/.cache/bazel/_bazel_root/8c069df52082beee3c95ca17836fb8e2/external/bazel_gazelle/internal/go_repository.bzl", line 256, column 17, in _go_repository_impl
  | fail("failed to fetch %s: %s" % (ctx.name, result.stderr))
  | Error in fail: failed to fetch com_github_google_s2a_go: fetch_repo<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: i/o timeout
  | (16:45:36) ERROR: /root/.cache/bazel/_bazel_root/8c069df52082beee3c95ca17836fb8e2/external/org_golang_google_api/internal/BUILD.bazel:3:11: @org_golang_google_api//internal:internal depends on @com_github_google_s2a_go//:s2a-go in repository @com_github_google_s2a_go which failed to fetch. no such package '@com_github_google_s2a_go//': failed to fetch com_github_google_s2a_go: fetch_repo<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: i/o timeout
  | (16:45:36) ERROR: /root/.cache/bazel/_bazel_root/8c069df52082beee3c95ca17836fb8e2/external/org_golang_google_api/internal/BUILD.bazel:3:11: @org_golang_google_api//internal:internal depends on @com_github_google_s2a_go//fallback:fallback in repository @com_github_google_s2a_go which failed to fetch. no such package '@com_github_google_s2a_go//fallback': failed to fetch com_github_google_s2a_go: fetch_repo<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: i/o timeout

What did you do?
Uses bazel to build our internal repository on AWS ec2 machines. We do have a lot of these build machines. They are not behind a NAT though.
What did you expect to see?
proxy.golang.org responds
What did you see instead?
proxy.golang.org timesout
it is very flaky, maybe around 1% failure (eyeballed), though when it fails, retrying does not work. it is not frequent enough to break individual workflows, but frequent enough to 100% break CI/CD pipelines with a lot of parallelism.
this issue started around Friday last week, but did not go away during the weekend.
as a mitigation, we have changed go proxy to an unofficial one + direct for now.

not 100% sure if this is the right place to file this bug.. seems to us more like Google's load balancer might have some issue (or we got rate limited due to some new policy?)

cc @golang/tools-team

Hi @aslonnie, can you confirm that this is still happening?
The error rate you report is inconsistent with what we see on the backend, suggesting some sort of load balancing / throttling as you suggest. I think we'd hear more loudly if this were affecting all users in this way.

seems much better now. closing. thanks.

we are getting the same type of issue resulting in flakiness in our unit tests
 ERROR: /mnt/jenkins/home/jenkins/workspace/SUT-Base-Snowflake/GlobalServices/BUILD.bazel:159:19: //GlobalServices:update_build_files depends on @com_github_bazelbuild_buildtools//buildozer:buildozer in repository @com_github_bazelbuild_buildtools which failed to fetch. no such package '@com_github_bazelbuild_buildtools//buildozer': failed to fetch com_github_bazelbuild_buildtools: fetch_repo<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: i/o timeout


Add .rubocop.yml and apply fixes

@raskchanky That look better? 😄

I had the wrong name and email in there. Wanted to take care of it before merge.

@iamthemuffinman Looks better to me 😁


Upgrade to Go 1.19 on main

Partially addresses #174.
The SDK uses Go 1.19 from their release that integrates with v0.37, so this should be backported to v0.37.x too.

PR checklist

[x] Tests written/updated, or no tests needed
[x] CHANGELOG_PENDING.md updated, or no changelog entry needed
[x] Updated relevant documentation (docs/) and code comments, or no
documentation updates needed

We probably want to update these occurrences as well:
% find . -type f | grep -v '\.svg$' | xargs grep -n '[^\.]1\.18[^\.0-9]'
./README.md:63:| v0.34.x          | Go version  | Go 1.18 or higher |
./.github/workflows/e2e-nightly-34x.yml:24:          go-version: '1.18'
%

find . -type f | grep -v '.svg$' | xargs grep -n '[^.]1.18[^.0-9]'

These pertain to the 0.34 branch. They should be fixed on v0.34.x and forward ported to main and 0.37.

find . -type f | grep -v '.svg$' | xargs grep -n '[^.]1.18[^.0-9]'

These pertain to the 0.34 branch. They should be fixed on v0.34.x and forward ported to main and 0.37.

Ah! You're right... didn't notice in which context they were!


Check if the sourceSetDir is null. Use empty set instead.

Fixes https://github.com/gradle/gradle/issues/18134
AntlrSpecFactory would crash on an NPE whenever sourceSetDirectoriesFiles is null.
It appears that AntrExecutor.AntlrTool handles empty sourceInputDirectories properly.
=> converted sourceSetDirectoriesFiles from null to empty set.
Context
https://github.com/gradle/gradle/issues/18134
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


fix node used resource calc

Special notes for your reviewer:
fix two func SetNode/AddTask, because they are called in many places, so i think add limit in func better.
Release note:
if some tasks are Succeeded/Failed , resources for this pods are not used, used resource in node can't be add.

There should not terminated Pod on the node :)


Change README to test GitHub badges

Changes Unknown when pulling 1d49b2dedca4b0fe0854fca9c6a2f71987ef3b69 on badges into ** on master**.

Coverage remained the same at 100.0% when pulling bfd722e69b0c5ac96a1c7b4bf5521e678649ba4a on badges into fbf1c16462e8d035676b194905a27cbf772451e6 on master.

Coverage remained the same at 100.0% when pulling 2471b26491dbad28efcc08c6a4824926da60c970 on badges into fbf1c16462e8d035676b194905a27cbf772451e6 on master.


windows version missing on conda-forge

In the past version I disabled windows build but the 0.7.1 is capable to build on windows, tried that on one of our machines.
@jakirkham:  What is missing to get it done on conda-forge?

Have you re-rendered the feedstock after removing the skip?

thx, done by @dougalsutherland
I missed that completly :)


ClusterWithReadReplicasConnectionPool with read_from_replicas causes dump.

We are using redis-cluster py and have set up connection pool with class ClusterWithReadReplicasConnectionPool. One of the arguments that is passed is read_from_replicas.  An object gets created. But when a get is performed and the required node is not found in the pool, a make_connection is called. This internally calls SSLConnection class from redis/connection.py which does not recognise read_from_replicas.
"Traceback (most recent call last):",
"File "/opt/directory/venv/lib/python3.6/site-packages/rediscluster/connection.py", line 364, in get_connection_by_node
connection = self._available_connections.get(node["name"], []).pop()",
"IndexError: pop from empty list",
"During handling of the above exception, another exception occurred:",
"Traceback (most recent call last):",
"  File "/opt/directory/venv/lib/python3.6/site-packages/rediscluster/client.py", line 615, in _execute_command
connection = self.connection_pool.get_connection_by_node(node)",
"  File "/opt/directory/venv/lib/python3.6/site-packages/rediscluster/connection.py", line 366, in get_connection_by_node
connection = self.make_connection(node)",
"  File "/opt/directory/venv/lib/python3.6/site-packages/rediscluster/connection.py", line 273, in make_connection
connection = self.connection_class(host=node["host"], port=node["port"], **self.connection_kwargs)",
"  File "/opt/directory/venv/lib/python3.6/site-packages/rediscluster/connection.py", line 89, in init
super(SSLClusterConnection, self).init(**kwargs)",
"  File "/opt/directory/venv/lib/python3.6/site-packages/redis/connection.py", line 828, in init
super(SSLConnection, self).init( ** kwargs)",
"TypeError: init() got an unexpected keyword argument 'read_from_replicas'
Is read_from_replicas a valid argument for ClusterWithReadReplicasConnectionPool?
Many thanks in advance.

@prabhakarjuzgar In the latest code at least, all i can see is that read_from_replicas keyword do not follow down into the connection class anywhere and  i am assuming you are using older code that might been broken. The read_from_replicas feature is mostly used and supported in a ClusterPipeline object when i try to trace where the argument is used today.
In general i suggest you migrate over to redis-py where all future cluster code will be written. They have must better support for all of the features that you want/need


Bug: Select with default occasionally not in frame

Are you in the right place?

For issues or feature requests file a GitHub issue in this repository
For general questions or discussion post in Discussions

Describe the problem
It seems like the default value is sometime out of frame with the select prompt.
Steps to reproduce the problem

Note that when the 20th position is the default value it is in frame but when the 18th position is the default value it is 2 lines above the visible content.
Actual behaviour
The default value was correct because clicking enter immediately provides the expected value but it is out of frame.
Expected behaviour
The default value should always start in frame and the cursor should always be in frame.
Describe your environment

OS version: macOS 10.15.7
Ruby version: 3.2.2
TTY::Prompt version: 0.23.1
Console: iTerm2, Terminal (default on macOS)

irb(main):038> TTY::Prompt::Paginator.new.paginate((1..25).map(&:to_s), 12, 6).to_a
=> [["18", 17], ["19", 18], ["20", 19], ["21", 20], ["22", 21], ["23", 22]]
irb(main):039> TTY::Prompt::Paginator.new.paginate((1..25).map(&:to_s), 18, 6).to_a
=> [["20", 19], ["21", 20], ["22", 21], ["23", 22], ["24", 23], ["25", 24]]

I think that the problem might be here in the TTY::Prompt::Paginator#paginate method.
diff --git a/lib/tty/prompt/paginator.rb b/lib/tty/prompt/paginator.rb
index d69d03d..bd8b327 100644
--- a/lib/tty/prompt/paginator.rb
+++ b/lib/tty/prompt/paginator.rb
@@ -77,7 +77,7 @@ module TTY

         step = (current_index - @last_index).abs
         if current_index > @last_index # going up
-          if current_index >= @end_index && current_index < list.size - 1
+          if current_index > @end_index && current_index < list.size - 1
             last_page = list.size - @per_page
             @start_index = [@start_index + step, last_page].min
           end


fix: remove jobs from charts schema

We do not configure platform jobs and the '#/definitions/jobs' does not match the keycloak go template.

Why do we need to remove jobs from the charts schema?

There are two types of jobs: platform and team.
The platform jobs are not configurable. The team jobs are configurable but int the team context


⚠ Bofrost.lu has degraded performance

In 336ef9d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2542 ms

Resolved: Bofrost.lu performance has improved in c6bceff after 33 minutes.


[BugFix] Optional append_default need levels otherwise result is wrong

Fixes #issue
When Optional Column need return levels and with page skipped, only append_default values but not levels when skip page,
which will lead to error result in release version and be crash in debug version(num rows of values is not equal to level's, can't not pass DCHECK)
a case:
I have a struct which is null when values % 50 == 0, but with error levels, we will get the error result:

the right result should be:

What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0


Introduce DecodedType typealias

Introducing this typealias helps when trying to conform a non-final class to
JSONDecodable.
If we just use Self, we run into an issue where the compiler can't ensure
that return type is correct, because the class might be subclassed. By letting
classes explicitly define their decoded type, we can make the compiler happy
while maintaining the ability to subclass if that's what we want.
As an added benefit, we can default DecodedType to Self, which means that
structs and final classes don't need to worry about changing anything from
the way they are doing it now.
Note that I'm adding a JSONDecodable version of NSURL for the tests.
This might be something that's common enough to warrant pulling into the
actual source in the future.

This looks good to me, I think it's worth adding a note for the record here that this is ultimately due to the problem described and answered here: http://stackoverflow.com/questions/25645090/protocol-func-returning-self.

:+1: Make sure to bump the version to v0.2.2 and update the podspec file


Build State Maven Extension

Add a new module that provides an extension allowing for fast-resuming builds without changes

In the lifecycle listener where you save the state, it seems like it would be a good idea to avoid saving if nothing has changed.

In the lifecycle listener where you save the state, it seems like it would be a good idea to avoid saving if nothing has changed.

Even if the project files remain unchanged, the recorded executions might be different and need to be saved.


Expose setting to embedders to limit max rasterizations per frame

In raster_cache.h we hard-code a maximum of 3 picture raster caches per frame in order to reduce jank. Given that different hardware and software stacks have different tolerances for caching, we should expose a mechanism for tuning this parameter that can be used by power-users.

The raster cache is a legacy feature at this point (no plans on adding it to impeller) so I'm going to close this.


Rebuild DNS Managed Record

Versions
NetBox Version: 4.1.6
NetBox DNS Version: branch main
Python Version: 3.11.2
Describe the bug
Well, i think it's still related to #472.
Yesterday i was investigatin why my webhook didn't fire on updating an ip-dns address. I noticed netbox-dns didn't update records, so i made a cleanup_rrset, a setup_dnssync and a rebuild_dnssync.
Well, these commands deleted all my managed Records. So i came here to gh to lokk for an open bug and i found #472.
I manually upgraded netbox-plugin-dns from gh branch main, made again a rebuild_dnssync but i still have no managed records.
If i try to create a new record, these won't appear in managed record list.
I tried even to reinstall whole netbox and netbox-plugin-dns making all migrations, but even this didn't work.
Any hint ans suggestion would be very appreciated.
And yes, i've got custom fields both in ip addresses and on dns names.
Thanks again for your great work and tell me how i can provide some more detailed logs.
Screenshots

This is the log from rebuild_dnssync
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None

Hi @shakin89, thanks for your report. Let's try to tackle your issue systematically. There is some information that's missing.
I assume you are using NetBox DNS to synchronise IPAM IP addresses to DNS A records, and the managed records that are missing are the records created for IP addresses, correct? In this case, let's rule out some of the possible causes:

It's definiteny not linked to #472. That issue dealt with custom fields for zones and records, not IP addresses.
cleanup_rrset is not linked to this either, it just deals with TTLs across RRsets.

So the problem is probably in IPAM DNSsync, and I have the strong suspicion (from your focus to custom fields) that you upgraded from NetBox DNS 1.0.x to NetBox DNS 1.1.x when the error occurred. Is that correct?
NetBox DNS 1.0.x had an experimental feature named "IPAM Coupling" that linked DNS records to IP addresses by means of setting custom fields on the IP addresses to assign a host name and a zone per IP address. This feature was removed in NetBox DNS 1.1.0 and replaced by the more flexible "IPAM DNSsync", which works in a very different way.
If I'm correct in that assumption, please have a look at https://github.com/peteeckel/netbox-plugin-dns/blob/main/docs/using_netbox_dns.md#migration-from-ipam-coupling (and generally at the documentation regarding IPAM integration). If I'm not, please update what exactly you're doing to get DNS managed records that are missing.

Well, firt of all thanks for your support.
Your assumption are correct, I use netbox to manage ip address of devices and to synchronize them with A record. After every update of a record, an ansible script is launched with a webhook to update bind zone and kea dhcp persistent lease. So the missing managed records are those created for ip address.
Migrating from netbox 3.x to 4.0.x i followed your guide, launching every command to migrate from ipam coupling to dnssync.
I've associated my view with ipam prefixes (i've got only 4x256 ip address so the migration has been very quick).
Now, digging a little bit deeper, my eyes has fallen on zone registry

As you can see yesterday i've updated an ip address and the related A record was updated.
I've done the same thing now and no modification is reported.
Just yesterday evening, after 6pm i've upgraded to netbox 4.1.6.
Trying to downgrade to 4.1.3 (the working version) to see if that was the problem.

Let's try it systematically.

Go to one of the IP addresses, select (preferably the closest) IP prefix of that address and check whether a view is associated with that IP address
Check that the zone you expect the record to be created in actually is present in that view (you can navigate to the view's detail page and look at the 'Zones' tab.
If it is, look at the managed records to make sure the record isn't there.
Then, go back to the IP address, edit and save it immediately after. Just as an experiment, you can change the DNS name field to a different host name within the zone.
Check the zone for managed records again. If the record appears now, we have a better idea where to look.

Generally, there are tons of automated tests that validate the record generation, so it's improbably that there is a general problem with the record generation. It can, however, be the case that some optimisation takes place when you enter data in the GUI that might inhibit updating (or, in this case, creating) a new address record.

Let's try it systematically.

Go to one of the IP addresses, select (preferably the closest) IP prefix of that address and check whether a view is associated with that IP address
Done

Check that the zone you expect the record to be created in actually is present in that view (you can navigate to the view's detail page and look at the 'Zones' tab.

If it is, look at the managed records to make sure the record isn't there.
i've no more managed records in here, has been deleted when i've done rebuild_dnssync yesterday

Then, go back to the IP address, edit and save it immediately after. Just as an experiment, you can change the DNS name field to a different host name within the zone.

Check the zone for managed records again. If the record appears now, we have a better idea where to look.

No records are showing. Seems like it doesnt catch the save signal from ipam
this is the log from netbox in INFO level. The DEBUG level generates a ton of message regarding uncatched variables in templates (about >10k lines for this simple operation)
2024-11-20 14:03:50,628 netbox.views.ObjectDeleteView INFO object_views 2720<PHONE_NUMBER>31520 Deleted indirizzo IP <IP_ADDRESS>/32
2024-11-20 14:04:50,125 netbox.views.ObjectEditView INFO object_views 2720<PHONE_NUMBER>31520 Modified Visualizza internal (PK: 1)
2024-11-20 14:05:04,680 netbox.views.ObjectEditView INFO object_views 2721<PHONE_NUMBER>31520 Modified Visualizza internal (PK: 1)
2024-11-20 14:07:24,448 netbox.views.ObjectEditView INFO object_views 2721<PHONE_NUMBER>31520 Modified Zone [internal] mgmt.shakxxx(PK: 2)
2024-11-20 14:08:17,661 netbox.views.ObjectEditView INFO object_views 2723<PHONE_NUMBER>31520 Created indirizzo IP <IP_ADDRESS>/32 (PK: 229)
2024-11-20 14:14:15,362 netbox.views.BulkDeleteView INFO bulk_views 2723<PHONE_NUMBER>31520 Eliminato 1 Indirizzi IP
2024-11-20 14:17:11,605 netbox.views.ObjectEditView INFO object_views 2720<PHONE_NUMBER>31520 Created indirizzo IP <IP_ADDRESS>/32 (PK: 230)
2024-11-20 14:17:31,510 netbox.views.ObjectEditView INFO object_views 2722<PHONE_NUMBER>31520 Modified Zone [internal] mgmt.shakxxx (PK: 2)

Generally, there are tons of automated tests that validate the record generation, so it's improbable that there is a general problem with the record generation. It can, however, be the case that some optimisation takes place when you enter data in the GUI that might inhibit updating (or, in this case, creating) a new address record.

Well, again thanks for your patience to help me trying to understand where's the problem.

I just pushed a new version of the rebuild_dnssync command that will give you the list of matching zones when running rebuild_dnssync. Please try it out to see if any zones are selected at all for your IP addresses. There should be something like
(netbox) [root@dns netbox]# /opt/netbox/netbox/manage.py rebuild_dnssync -v3
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: [<Zone: zone1.example.com>, <Zone: [external] zone1.example.com>, <Zone: [test2] zone1.example.com>]
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: [<Zone: zone1.example.com>, <Zone: [external] zone1.example.com>, <Zone: [test2] zone1.example.com>]
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: [<Zone: zone1.example.com>, <Zone: [external] zone1.example.com>, <Zone: [test2] zone1.example.com>]

when you run it, as opposed to
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: []
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: []
Updating DNS records for IP Address <IP_ADDRESS>/24, VRF None
  Zones: []

if there are no matching zones. That will help us to narrow down the issue.

hi pete, sorry for late reply and thank you for helping in debugging this.
I've pulled the new branch and this is the output of rebuild_dnssync
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
  Zones: []
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
  Zones: []
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
  Zones: []
Updating DNS records for IP Address <IP_ADDRESS>/32, VRF None
  Zones: []

this is my plugin config
PLUGINS = ["netbox_dns"]
PLUGINS_CONFIG = {
    "netbox_dns": {
        "tolerate_underscores_in_hostnames": true,
        "tolerate_non_rfc1035_types": ["X25"],
        "enforce_unique_records": true,
        "zone_active_status": [
            "ZoneStatusChoices.STATUS_ACTIVE",
            "ZoneStatusChoices.STATUS_DYNAMIC",
        ],
        "record_active_status": ["RecordStatusChoices.STATUS_ACTIVE"],
        "dnssync_ipaddress_active_status": [
            "IPAddressStatusChoices.STATUS_ACTIVE",
            "IPAddressStatusChoices.STATUS_RESERVED",
            "IPAddressStatusChoices.STATUS_DHCP",
        ],
    }
}

Thanks. That narrows it down quite a bit. Apparently NetBox DNS can't match a zone name to your DNS names.
Can you confirm that the setting in 'DNS Name' is ending in the zone name? E.g. 'zone.example.com' (without a trailing dot)? The names must match exactly for the zone to be found.
If this is not the issue we'll ned to run some checks in nb_shell.

I confirm the zone name is mgmt.shak.xxx as you can see from the second screenshot here.
The zone name doesn't include a trailing dot.
The DNS name associated with the IP Addres does not include the trailing dot and is in the format name.mgmt.shak.xx
I'm trying to remember what i've done before everything broke down, but it seems i didn't do anything so dangerous.
As i told you before, i use a webhook to fire an ansible playbook to update the dns zone managed by bind (fired from a create/update/delete of a netbox dns record) and to update the dhcp leases managed by KEA (fired from ip address create/update/delete). I saw the dns playbook didn't play, so i started investigating and arrived here.

I confirm the zone name is mgmt.shak.xxx as you can see from the second screenshot here.
The zone name doesn't include a trailing dot.
The DNS name associated with the IP Addres does not include the trailing dot and is in the format name.mgmt.shak.xx
I'm trying to remember what i've done before everything broke down, but it seems i didn't do anything so dangerous.
As i told you before, i use a webhook to fire an ansible playbook to update the dns zone managed by bind (fired from a create/update/delete of a netbox dns record) and to update the dhcp leases managed by KEA (fired from ip address create/update/delete). I saw the dns playbook didn't play, so i started investigating and arrived here.

I don't think it's anything you've done but rather some weird circumstances. So far I can't find anything that you might have done wrong. I'm still trying to figure out what actually happens.
Let's try nbshell.
Please open an nbshell session:
[root@dns ~]# . /opt/netbox/venv/bin/activate
(netbox) [root@dns ~]# /opt/netbox/netbox/manage.py nbshell
### NetBox interactive shell (dns.dev.hindenburgring.com)
### Python 3.11.5 | Django 5.0.9 | NetBox NetBox Community v4.1.6
### lsmodels() will show available models. Use help(<model>) for more info.
>>>

Now we can look at the process in detail.
from netbox_dns.utilities.ipam_dnssync import _get_assigned_views

address = IPAddress.objects.get(address="<IP_ADDRESS>/32")
_get_assigned_views(address)

This should give you a list of views assigned to the prefix the address is located in. I assume that the list is empty (which is wrong, it should consist of the view "internal"), but that's only an assumption, so please run the test anyway.
Now I would like to drill down on the view assignment process a bit further:
Prefix.objects.filter(
    vrf=address.vrf,
    prefix__net_contains_or_equals=str(address.address.ip),
    netbox_dns_views__isnull=False,
)

This should give you the list of all prefixes the address is located in and that have an assigned DNS view. If it is empty there's something wrong with the DNS view assignment.

An additional check you can run is (still in nbshell):
from netbox_dns.utilities import get_parent_zone_names

get_parent_zone_names(address.dns_name)

This gives you a list of all parent zones that could contain the record (excluding the top level zone, which is normally not in scope).
If this works we can try to find the actual zone (it may return more than the zone we need, but that's fine):
Zone.objects.filter(
    name__in=get_parent_zone_names(address.dns_name),
    active=True,
)

Holy sh33t!!!
When i updated netbox i also updated the configuration and i couldn't remember cause i was focusing on the version upgrade!
Well, i knew it wasn't a bug, i was the bug! :)
I really don't know how to thank you!
I confirm you the configuration was the problem.
I've done a rebuild_dnssync and know everything is in the correct place!

Glad I could help - thanks for raising this, it definitely was a good issue that led to an improvement in the docs.


E2E tests don't respect mTLS config

/area runtime
/area operator
/area placement
/area docs

/area test-and-release
What version of Dapr?

v0.3.0-rc.0-80-g2d55351-dirty

Expected Behavior
The E2E tests deploy a default config (https://github.com/dapr/dapr/blob/master/tests/config/dapr_mtls_off_config.yaml) which should be picked up by the sidecar injector webhook and not enable mTLS on the E2E test apps.
Actual Behavior
Regardless of the config, the sidecar injector is starting the test apps with mTLS enabled.
Steps to Reproduce the Problem
Deploy the E2E test config using make setup-test-config and deploy an E2E app using make test-e2e-all. Use kubectl describe po <pod-name> on one of the test apps and check the dapr container arguments. It'll have --enable-mtls and have the trust-anchors set.

As per IRL discussion with @yaron2 this can be fixed by manually editing the default config kubectl edit configurations default -n dapr-system and setting spec.mtls.enabled: false instead of spec.mtls.enabled: "false". cc: @youngbupark

This is now fixed and being back ported with Dapr 0.4.1.


Add for the ComponentInterface the optional EReference to the original node that instantiates it

Added the anotation "FromRosNode" to the ComponentInterface, also to those ComponentInterfaces included within a RosSystem. The annotation was declared as optional, for ComponentInterfaces coming from the combination/composition of several ros nodes this annotation hasn't to be defined.
The idea is to use this reference to update automatically the ComponentInterface within a RosSystem model when the original .ros model is updated.
The PR includes also:

Update of the auto-generator of .componentinterfaces form .ros models (including the tests)
Upgrade of the Sirius .rossystem plugin that eases the addition of new components to a system
Upgrade of the RosSystem creation Wizard

Missed: new wizard for .componentinterface and .rossystem models to trigger a "re-load" of the  models which should:

check if the ComponentInterface instance has the annotation "FromRosNode"
Find the node pointed with "FromRosNode" and parse its interfaces
Compare the interfaces found in .ros with the ones within the ComponentInterface, if a discrepancy is found the ComponentInterface has to be updated accordingly (delete or add the interface)

[ ] The launch file generator should be updated to consider the annotation "FromRosNode" to add new nodes includes


[Question] Deprecated Status?

Dear all,
We are looking into the moving our current usage of Adyen payment flow that make use of the Adyen IOS and Android SQK with the quick flow to the API flow so we can have the full control of what we do.
With the API Flow we need to encrypt the payment method information using the CSE libraries.
We saw thoss libraries are today marked as deprecated. Can you tell us then what should be done today to encrypt the payment information when using the API flow?
Regards,
Alex.

Hi @AlexandreRoba,
The replacement for AdyenCSE is the CardEncryptor class inside our iOS SDK. You don't have to implement the full SDK, you can use the CardEncryptor standalone.
With kind regards,
Joost

Hello @joostvandijk thanks for the answer will use this one then. It is a little bit ennoying that we have to "import" the full SDK to support only the API integration... :(
If you have the answer what is the similar class for encrypting on android? Otherwise I will look into it myself :p

Hi @AlexandreRoba,
I understand. When you use CocoaPods, you can use the Adyen/Card subspec. If you use Carthage, you have to link Adyen, AdyenInternal, AdyenCard and Adyen3DS2. This will save some weight.
As for Android, the class is named the same: https://github.com/Adyen/adyen-android/blob/master/checkout-core-card/src/main/java/com/adyen/checkout/core/card/CardEncryptor.java
Joost

@joostvandijk is this still the recommended approach? We're looking to integrate the Adyen SDK into our React Native app and want full control over the flow so we're not looking to use the Card Components. If we use the CardEncryptor classes to encrypt our payment methods will we be able to follow the rest of the 'API only' integration for Online Payments? (https://docs.adyen.com/checkout)

@tomtargosz Hi Tom, yes, it is. Please use CardEncryptor. It will work with the direct API integration as described in the docs.
Best,
Joost


Unable to change colours

Unable to change colour by editing config.h.
No change by editing selbordercolor[].

After making changes to the config.h you have to recompile it.
Run sudo make clean install in the repo's folder. and after it reload dwm to see the changes.


Fix image path in Benchmark document

Replace "space char" with "%20" in image path to fix image display problem

Codecov Report

Merging #34 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   84.45%   84.45%
=======================================
  Files           5        5
  Lines         444      444
  Branches       59       59
=======================================
  Hits          375      375
  Misses         69       69

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 58e3589...9c0cd01. Read the comment docs.


Branding.ApplyBranding not displaying console

Just downloaded this and made the changes to the settings.xml. Runing the code does not popup the console i just get the following in my Output.
The thread 0x1f7c has exited with code 259 (0x103).
The thread 0x2e10 has exited with code 259 (0x103).
'Contoso.Branding.ApplyBranding.Console.vshost.exe' (CLR v4.0.30319: Contoso.Branding.ApplyBranding.Console.vshost.exe): Loaded 'C:\Users\xxxx.xxxx\Source\Repos\PnP\Samples\Branding.ApplyBranding\Branding.ApplyBranding.Console\bin\Debug\Contoso.Branding.ApplyBranding.Console.exe'. Symbols loaded.
The thread 0xa74 has exited with code 259 (0x103).
The thread 0x3318 has exited with code 259 (0x103).
The program '[11392] Contoso.Branding.ApplyBranding.Console.vshost.exe' has exited with code 0 (0x0).

In fact it does appear...just to quickly, running in CRTL F5 sorts it out.


Update log-query-overview.md

Per info from @yossi-y below and confirmed by Joshua Miller in support Teams, Get-AzOperationalInsightsSearchResults is obsolete.
https://github.com/Azure/azure-powershell/issues/8993

@dcbrown16 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Because of substantial changes made to the article since this pull request was opened, when I resolved merge conflicts, the diff disappeared (the change moved from line 93 to line 22). It looks like the revision suggested in the PR is not reflected in master. @dcbrown16 Sorry for the delay. If you want to against submit the update, could you open a new pull request? Thanks. We'll close this PR.


Update z_manpath.sh

It is run in every shell instance, not only for login shells, avoid executing manpath when already set.
manpath: warning: $MANPATH set, ignoring /etc/manpath.config

manpath should already do this internally
From man manpath:

If  $MANPATH  is  set,  manpath displays its value rather than determining it on the fly.

That would work too, but you can avoid executing mapath altogether.

@daurnimator Not quite equivalent: -q might silence other warnings

manpath does a few other interesting things, e.g. if MANPATH starts or ends with a colon then the default paths are prepended/appended.
But I don't mind either way..... I've never had the need for manpath or MANPATH before

@daurnimator Yes, but we don't use those aspects in profile.d, which is sourced before user customizations IIRC


Python3 compatibility fixes

It looks like this was written with python3 in mind, but only tested against python 2. This PR should fix the python3 implementation while not affecting the py2. The big things are the explicit calls to list() to exhaust the map() iterators, a consistent usage of text_type versus unicode (text_type had existed previously, but was inconsistently utilized), and a condtional import for urlparse(). Beyond this, there is one removal of some print statements that aren't currently reachable (these should have, imo, been click.echo calls anyway) and some style fixes that are strictly opinions on m part (you're using map much too heavily in this, even in places where a for-loop is much more readable.)
Feel free to merge the py3 compat fixes without merging the style fixes. I can also move those commits to another branch and open a new PR if you want to talk about them separately.

This is great, thanks. I'm fine with merging everything, although a couple notes before I do:

Should we use six, which provides text_type among other things, like the moves module?
I'd like to rewrite anything not using list comprehensions rather than cast map iterators to list, if you think that makes sense.

With regard to six, I'd advocate for it. I thought about adding it in this PR, but I thought I'd start out with the smallest thing that could possibly fix the bug.
The use of list comprehensions over map calls is an improvement, imo, but I'd like to see most of them rewritten to use explicit for-loops. Particularly if they're nested._


Fix undefined behavior in black_box

The previous implementation allowed the output to alias the input. This would cause undefined behavior when passed &mut references.
MaybeUninit::as_ptr was introduced in 1.59, so this does not affect the 1.60 MSRV.

Thanks for contributing!
I'm sorry but I haven't fully understood the point about aliasing. Maybe you could give an example for an incorrect usage of the old black_box function? Would it be possible to provide an unit test which fails with the old implementation and succeeds with your implementation?
I also thought about updating the MSRV to 1.66, so we could use the std::hint::black_box from the stdlib. 1.66 was released about 1 year ago and maybe it's time to update it. There are also some other new language features I would like to make use of.
I compared the assembly of our black_box with the one from rust library on my computer and it looks like the produced assembly when using std::hint::black_box is more efficient:
pub fn our_black_box() {
    let a = 1;
    let b = 2;
    for _ in 0..1024 {
        black_box(black_box(a) + black_box(b));
    }
}

produces
iai_callgrind::use_black_box:
 mov     eax, 1024
.LBB62_1:
 mov     dword, ptr, [rsp, -, 12], 1
 mov     ecx, dword, ptr, [rsp, -, 12]
 mov     dword, ptr, [rsp, -, 8], 2
 add     ecx, dword, ptr, [rsp, -, 8]
 mov     dword, ptr, [rsp, -, 4], ecx
 mov     ecx, dword, ptr, [rsp, -, 4]
 mov     dword, ptr, [rsp, -, 12], 1
 mov     ecx, dword, ptr, [rsp, -, 12]
 mov     dword, ptr, [rsp, -, 8], 2
 add     ecx, dword, ptr, [rsp, -, 8]
 mov     dword, ptr, [rsp, -, 4], ecx
 mov     ecx, dword, ptr, [rsp, -, 4]
 add     eax, -2
 jne     .LBB62_1
 ret

Compared to the std::hint::black_box:
pub fn std_hint_black_box() {
    let a = 1;
    let b = 2;
    for _ in 0..1024 {
        std::hint::black_box(std::hint::black_box(a) + std::hint::black_box(b));
    }
}

which produces
iai_callgrind::use_black_box:
 mov     eax, 1024
 lea     rcx, [rsp, -, 12]
 lea     rdx, [rsp, -, 8]
 lea     rsi, [rsp, -, 4]
.LBB62_1:
 mov     dword, ptr, [rsp, -, 12], 1
 #APP
 #NO_APP
 mov     edi, dword, ptr, [rsp, -, 12]
 mov     dword, ptr, [rsp, -, 8], 2
 #APP
 #NO_APP
 add     edi, dword, ptr, [rsp, -, 8]
 mov     dword, ptr, [rsp, -, 4], edi
 #APP
 #NO_APP
 dec     eax
 jne     .LBB62_1
 ret

Note, that I also compared the assembly (for this specific function) of this pr with the one from the main branch and I haven't found a difference. What would be a good point for the safer version of this pr.

This code fails under Miri for black_box_new. This is because two &mut references that alias each other are being used simultaneously. You can try it yourself by selecting Tools -> Miri.
error: Undefined Behavior: trying to retag from <1801> for Unique permission at alloc897[0x0], but that tag does not exist in the borrow stack for this location
  --> src/main.rs:6:9
   |
6  |         ret
   |         ^^^
   |         |
   |         trying to retag from <1801> for Unique permission at alloc897[0x0], but that tag does not exist in the borrow stack for this location
   |         this error occurs as part of retag at alloc897[0x0..0x4]
   |
   = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
   = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <1801> was created by a Unique retag at offsets [0x0..0x4]
  --> src/main.rs:4:19
   |
4  |         let ret = std::ptr::read_volatile(&dummy);
   |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: <1801> was later invalidated at offsets [0x0..0x4] by a Unique retag
  --> src/main.rs:5:26
   |
5  |         std::mem::forget(dummy);
   |                          ^^^^^
   = note: BACKTRACE (of the first span):
   = note: inside `black_box_old::<&mut i32>` at src/main.rs:6:9: 6:12
note: inside `main`
  --> src/main.rs:17:9
   |
17 |     _ = black_box_old(&mut 1);
   |         ^^^^^^^^^^^^^^^^^^^^^

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to 1 previous error

Looks like rust playground is down (again). I'll retry your link later. I haven't seen the code but we would have a failing test for the old version, if we would setup a ci job running miri?
Could you please fix the spelling checks and add Uninit to the .dicts/custom.txt dictionary?

I haven't seen the code but we would have a failing test for the old version, if we would setup a ci job running miri?

Yup. The code I linked simply passes &mut 1 to both implementations, demonstrating it failing on the old one.

Great! I'm going to push a ci job running miri test. I'm doing this on a separate branch, so you can merge it into your pr and setup a simple test case. You can setup a ci job too if you like to, but it's maybe a little bit tedious since you're a first time contributor and every change needs to be approved before the ci runs.

You can take the latest commit from the cicd branch.

I would have liked to merge it and put it in a patch release, but in favour of #48 and using std::hint::black_box I am closing this pr. In the long run, bumping the MSRV is the better choice. Nonetheless, thanks for pointing out this issue and the work you've put into it.


SinonSpy.getCalls

The getCalls method is missing. I think it should be getCalls():SinonSpyCall[] and I'm not sure whether it belongs to SinonSpyCallApi or SinonSpy

Feel free to add it to SinonSpy. I'll accept a PR, and if either you or @asvetliakov are interested I can add you as collaborators.


Add possibility to set custom annotations in Elasticsearch topology

Hi,
It would be so cool, if a user could specify custom annotations in Elasticsearch object for master, client and data.
I mean something like this:
apiVersion: kubedb.com/v1alpha1
kind: Elasticsearch
metadata:
  name: ops-elasticsearch
spec:
  version: 6.5.3
  storageType: Durable
  topology:
    master:
      prefix: master
      replicas: 1
      annotations:
        key1: value1
        key2: value2

Then the stateful set would create pods with all specified annotations.

I know, that it's possible to use spec.podTemplate but it is applied to all pods. Sometimes there is a case, where custom annotations are useful only for specific components of Elasticsearch cluster (e.g. only for master).


Next.js 15 (after 15.0.0-canary.13) support

[!NOTE]
Disclaimer: although I recognize it might be too early to think about Next.js 15 support, but it might be beneficial. I suggest at least to consider it.

Although OpenNext works fine with next@rc, it doesn't work with latest Next.js 15 canary (which eventually be a new RC). Issue is related to incremenatal cache changes. Specifically: kind values before were FETCH, IMAGE, REDIRECT, ROUTE, PAGE, but now values are FETCH, IMAGE, REDIRECT, APP_PAGE, APP_ROUTE, PAGES.
Next.js 14.2.8 implementation: https://github.com/vercel/next.js/blob/v14.2.8/packages/next/src/server/response-cache/types.ts#L92-L97
Next.js 15.0.0-rc.0 implementation (same as 14.2.8): https://github.com/vercel/next.js/blob/v15.0.0-rc.0/packages/next/src/server/response-cache/types.ts#L92-L97
Next.js 15.0.0-canary.145 implementation: https://github.com/vercel/next.js/blob/v15.0.0-canary.145/packages/next/src/server/response-cache/types.ts#L141-L147
Note: new APP_PAGE kind also has different object structure: https://github.com/vercel/next.js/blob/v15.0.0-canary.145/packages/next/src/server/response-cache/types.ts#L110-L119
I tracked down these changes to this commit: https://github.com/vercel/next.js/commit/e456acd85462bcf1807f6662f21ee16cedb2409d. It was released in 15.0.0-canary.13.
My understanding is that changes should be done here: https://github.com/sst/open-next/blob/main/packages/open-next/src/adapters/cache.ts
I confirmed that latest OpenNext (3.1.1) doesn't work with Next.js 15.0.0-canary.145. While it can be successfully deployed, when you try to open deployed application server function will fail with the following stack trace:
⨯ TypeError: result.toUnchunkedString is not a function
    at sendRenderResult (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/send-payload.js:64:54)
    at NextNodeServer.sendRenderResult (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/next-server.js:573:50)
    at NextNodeServer.pipeImpl (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/base-server.js:972:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async NextNodeServer.handleCatchallRenderRequest (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/next-server.js:283:17)
    at async NextNodeServer.runImpl (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/base-server.js:942:9)
    at async NextNodeServer.handleRequestImpl (/var/task/node_modules/.pnpm/next@15.0.0-canary.145_@opentelemetry+api@1.9.0_react-dom@19.0.0-rc-a03254bc-20240905_react@1_675uctallwwvzvgc2kh2q6726i/node_modules/next/dist/server/base-server.js:876:20)
    at async jX (file:///var/task/modules/frontend/index.mjs:58:239839)
    at async file:///var/task/modules/frontend/index.mjs:58:239536
    at async Wk (file:///var/task/modules/frontend/index.mjs:58:239430)

Yeah we can add support for this, we already fixed an issue with the middleware that only affected next 15 https://github.com/sst/open-next/pull/473

Faced the exact issue today is there any fix found yet, @conico974 ?

@Sreenivas1323 Yeah update OpenNext. It's fixed since 3.1.3

Upgrading the SST package to the latest version resolved this error.


Links don't load past first screen on emulator using API 32 and under

I've been building using an API 33 emulator for a while which works fine. I started to test older versions and on API 32 and under, the first screen loads but clicking a link shows an infinite spinning wheel. Rails gives a 200 OK but on the Android app it doesn't proceed past visitLocation, never executing visitStarted. I've built the app using the basic setup in the docs guide, so nothing out of the ordinary. I also tested using the Demo app plugging in <IP_ADDRESS> and the same thing. So I assume it is a bug when using <IP_ADDRESS> not receiving the response properly. Or maybe something with my Rails app is causing it but seems unlikely. The issue may even be a bug within the latest macOS.
I bought a cheap physical device that uses API 30 and everything works there. So no worries and maybe others are having this issue. Would be nice to emulate and test the other versions though.
System
macOS ARM 13.0.1
Android Studio 2022.2.1 Patch 1
ruby 3.2.0
rails <IP_ADDRESS>
turbo-rails 1.3.3

I'm not aware of others broadly having issues on older platform versions, so it could be due to a couple things:

Please make sure that the Android System WebView app installed on the device/emulator is updated to a recent Chromium version.
To point to your local machine, you may need to set the android:usesCleartextTraffic="true" flag in the application manifest.

@jayohms you mentioned Please make sure that the Android System WebView app installed on the device/emulator is updated to a recent Chromium version. How/where to do that in the emulator?
I've also encountered the web view infinite spinning wheel  when testing in Android Studio on Pixel 6 Pro simulators with lower API levels (24-27). But the emulators I managed to run don't have Play Store available and I don't find any app called "Chromium" in their lists of apps. (There is just an app called "WebView Shell" which has version 1.0.)
In Android Studio's Device Manager, when selecting Create Device, only some devices such as the Pixel 4 or Nexus 5X have an indicator that they support Play Store, which might offer a way to ensure the WebView app is the most recent. But when selecting such an emulator device, then in the next screen titled System Image I found no API 24-27 system image supporting Google Play and which can run on my Macbook M2. Only the x86 images have Google Play available, but they don't start at all on my machine (for example I tried Release Name: Nougat - API level: 24 - ABI: x86 - Target: Android 7.0 (Google Play)).
NB:

in the "Recommended" tab there is no way to select an API level below 28
in the "ARM Images" tab the API 24-27 system images don't have Google Play / Google APIs

And how to locate the emulator's "WebView app" to begin with, in order to check its version? How to upgrade it without Play Store?
So I haven't yet had success in seeing a working Turbo WebView in API 24-27. I need this to confirm that it works fine for our users, and also to be able to troubleshoot various other issues (not related to Turbo) they may be having with our app. I'd be grateful for any suggestions 🙏.


[bug] In the invoke method, if the options.headers contain English, request.body() will return Json(Object {"0": Number()}) instead of Raw([]).

In the writeFile function, when the path is a string that contains Chinese characters or spaces, and options.baseDir is not provided, it can lead to errors. It uses request.body() to obtain the data. Normally, it should return Raw([]), but when there are Chinese characters or spaces, it returns Json(Object {"0": Number()}). This problem also exists in the invoke method.

I think this has been fixed in the latest release of tauri-plugin-fs, please re-test and let us know if you still have issues.


Create Tor Onion Location blog post

Announce #706

I don't think this is necessary.  If people use Tor browser, they'll be notified.  If not, we already have a post announcing the existence of the hidden service, https://bitcoincore.org/en/2020/03/27/hidden-service/

I also don't really see why adding a HTTP header would need an announcement
post. End users have to do exactly nothing with it.
On Thu, Oct 1, 2020, 08:55 David A. Harding<EMAIL_ADDRESS>wrote:

I don't think this is necessary. If people use Tor browser, they'll be
notified. If not, we already have a post announcing the existence of the
hidden service, https://bitcoincore.org/en/2020/03/27/hidden-service/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-core/bitcoincore.org/pull/723#issuecomment-701929135,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA65NXEPPQJI4M3G4SN5HTSIQRVBANCNFSM4R5TX7BA
.


[Table]: Need unique IDs on overflow menu trigger so that automation can reliably target the overflow menu

For automation there isn't a reliable way to target to the overflow menu per row.  IDs should be added to the overflow trigger so that automation can easily trigger the overflow to get access to the overflow actions.

Closed in the above PR


exec_time built-in plugin keeps on being displayed

The exec_time built-in plugin shows a strange behavior after being displayed once. It may keep being show whether a command is executed or not.
Steps to reproduce:

Launch terminal
Wait at least 5 seconds
Press Enter key

Expected behavior:

No exec_time plugin is shown

Shown behavior:

exec_time is shown (8s, 9s, etc)

I think the cause of this is that there's no conditional check to see if a proper command was actually executed.
Every time I press enter with blank input in my terminal, prompt_geometry_set_command_timestamp() runs and a timestamp is saved.
Then, prompt_getometry_check_command_exec_time() runs, and if the elapsed time > the max time, it ouputs the elapsed seconds.


Add ability to mock VMService's WebSocket connection

@johnmccutchan

@cbracken

@johnmccutchan FYI, I had to make some substantive updates to deal with a test failure in the first rev.  Would you mind taking another look?

Still LGTM


cache/redis: add configurable expiration time

I see that RedisCache has Expiration field: https://github.com/go-spatial/tegola/blob/master/cache/redis/redis.go#L90
It would be nice to add ability to configure expiration time. I will try to implement it.
func (c *Client) Set(key string, value interface{}, expiration time.Duration) *StatusCmd

This has been merged into the v0.10.x branch


Update 20-documentation-issue.md

Minor update to the template to have better clarity over the content.

We will not be encouraging one liner grammatical changes as this is expensive process, thank you for your interest.
CC @mihaimaruseac

We will not be encouraging one liner grammatical changes as this is expensive process, thank you for your interest.
CC @mihaimaruseac


Build new schemes

@RRethy I just ran the script from the repo. Catppuccin was split into multiple subthemes. So if we want to restore this one we'll have to maintain it manually as it's not there in the main repo anymore.

Hi, I think this can be closed. This PR covers these changes already: https://github.com/RRethy/nvim-base16/pull/75


Role of unit tests

Hi! I'm the maintainer of ROCm community packages for Arch Linux  (rocm-arch). Currently, we're adding unit tests to our package build scripts.
Running the HIP unit test (with HIP_CATCH_TEST=1) many tests fail on my Vega 56 and some, in particular stream- and graph-related tests, even cause the GPU driver to crash. I've encountered similar problems with KFD unit tests (see https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/issues/76). In contrast to the linked problem which required to blacklist only three tests, filtering all bad HIP tests would be much harder.
Therefore, I would like to know if the unit tests are designed to be compiled and run by an end user? If not, what would be the best way to validate a (basic) HIP installation? I'm only aware of the HIP examples repository that includes checks for parts of the HIP functionalities.

I expect some tests to fail, vega 56 is quite old and some new tests might not be written with that in mind.
can you share some failed tests names.
Also to verify that HIP is installed correctly, you can run this example. It is very primitive and does not do a thorough check on any major HIP features, it just checks 3 things:

can host allocate device memory
can host copy memory to and from GPU
can host launch kernels on gpu.

#include <iostream>
#include <cassert>

#include <hip/hip_runtime.h>

#define HIP_CHECK(call_)                                                                           \
  {                                                                                \
    auto res_ = call_;                                                                             \
    if (res_ != hipSuccess) {                                                                      \
      std::cout << "Failed in: " << #call_ << " with error: " << res_ << std::endl;                \
      return -1;                                                                                \
    }                                                                                \
  }

__global__ void kernel(int* set) {
  if (*set == 20) {
    *set = 10;
  }
}

int main() {
  int* ptr{nullptr};
  HIP_CHECK(hipMalloc(&ptr, sizeof(int)));
  int val = 20;
  HIP_CHECK(hipMemcpy(ptr, &val, sizeof(int), hipMemcpyHostToDevice));
  kernel<<<1, 1>>>(ptr);
  int res = 0;
  HIP_CHECK(hipMemcpy(&res, ptr, sizeof(int), hipMemcpyDeviceToHost));
  if (res == 10) {
    std::cout << "HIP is working fine!" << std::endl;
  } else {
    std::cout << "HIP is NOT working fine!" << std::endl;
  }
}

@tpkessler Hi, is your issue resolved on the latest HIP? If so can we close this ticket?


Master Details my own design

Hi, Guys
I need your help as I am new with FreshMvvm
How do I create my own design for the master page something like this?

Take a look at this comment: https://github.com/rid00z/FreshMvvm/issues/37#issuecomment-194536483 this is pretty much what you want to do.
In the CreateMenuPage method you can initialize your custom menu page and assign that as the Master. For that youl need make your own class that extends FreshMasterDetailNavigationContainer and use that as the Container on App.cs


nslcd: restart when nslcd.conf changes and let pwdutils tools use libnss_ldap.so

Motivation for this change
Restart nslcd service when its configuration is modified by Nix. And set a global LD_LIBRARY_PATH to libnss_ldap.so so that getent and passwd can contact nslcd. Not sure what is missing to have passwd actually change the password as ldappasswd can. I was able to do it on Debian, but unable to find what config is missing to have passwd fully work on Nix.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

@ju1m I wanted to say changing the hardcoded values to the different settings is ok, in case the configuration then resembles more how it's done in other distros - see my configuration change in account management group.
About the ldap case,
password    sufficient    pam_unix.so […]
[…]
password sufficient pam_ldap.so  use_first_pass
[…]
password    required      pam_deny.so

seems to be what distros normally configure, that's pretty much what we have in NixOS (except flipping password requisite to password sufficient as suggested)
Personally, I fear adding hooks to configure the pam configuration line outside of the pam module itself as suggested in pam.nix since 2013 might become a huge mess of configuration lines with priorities outside the pam module itself and complicate things a lot, so I kinda prefer to just change this in-place, documenting in the release notes as done in #52488.
Still, having some tests ensuring things work as expected (and making sure they don't break in the future) should be the goal, too.
For this PR, you probably only need to do the changes in the pam configuration, extend the ldap server permission configuration, and extend the testScript by running passwd on both clients, verifying the password was changed on the other one, or something similar.


Can't auto-disable in TelescopePrompt

OS: Manjaro
What vim?: Neovim 0.5
Autopairs config:
let g:AutoPairsFiletypeBlacklist = ['TelescopePrompt']

Describe the bug
Adding 'TelescopePrompt' to the blacklist doesn't work. auto-pairs continues to close parentheses in Telescope.
Steps to reproduce

Install Telescope
Set up auto-pairs config with let g:AutoPairsFiletypeBlacklist = ['TelescopePrompt']
Open Neovim
Open Telescope (with :Telescope, for example)
Type ( in the prompt.

auto-pairs will insert ). I expect auto-pairs to be disabled with that setting.

Writing autocmd FileType TelescopePrompt let b:autopairs_enabled works but I would have expected let g:AutoPairsFiletypeBlacklist = ['TelescopePrompt'] to work as well.

Is TelescopePrompt the echo &ft of that buffer?

Is TelescopePrompt the echo &ft of that buffer?

Yes. I've opened telescope, pressed ESC, and typed :echo &ft and saw TelescopePrompt. Another proof is that autocmd FileType TelescopePrompt let b:autopairs_enabled = 0 works as expected.

Just nothing that I'm seeing this as well - I can use the autocmd for now though, thanks for the workaround

I can't reproduce with
set nocompatible

filetype off

call plug#begin()
Plug 'nvim-lua/popup.nvim'
Plug 'nvim-lua/plenary.nvim'
Plug 'nvim-telescope/telescope.nvim'

Plug 'LunarWatcher/auto-pairs'
call plug#end()

"let g:AutoPairsFiletypeBlacklist = ['TelescopePrompt']

filetype on
filetype plugin indent on
filetype plugin on

Note that the blacklist is intentionally commented out - doesn't autocomplete. Doesn't run with g:AutoPairsExperimentalAutocmd = 1 either, running NVIM v0.5.0-dev+1127-g667e3bfb6

I've used the your config on NVIM v0.5.0-dev+1385-g93f15db5d and it reproduced the issue for me. Here are more complete repro steps from me. Could you try them out on the newest nvim version?
Here's a more standalone minimal init.vim:
" init.vim
set nocompatible

filetype off

" Plugin configuration follows

" Ensure the Plug is installed
let s:target_plug_file = '~/.config/nvim/autoload/plug.vim'
if empty(glob(s:target_plug_file))
  silent !curl -fLo s:target_plug_file --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall --sync | source $MYVIMRC
endif

" Automatically install missing plugins on startup
function! InstallMissingPlugins()
  if !empty(filter(copy(g:plugs), '!isdirectory(v:val.dir)'))
    PlugInstall
  endif
endfunction
autocmd VimEnter * :call InstallMissingPlugins()

call plug#begin()
  Plug 'nvim-lua/popup.nvim'
  Plug 'nvim-lua/plenary.nvim'
  Plug 'nvim-telescope/telescope.nvim'

  Plug 'LunarWatcher/auto-pairs'
call plug#end()

filetype on
filetype plugin indent on
filetype plugin on

Run nvim -u init.vim foo.py
If run for the first time, quit and run nvim -u init.vim foo.py again to make sure the plugins are loaded.
To verify that auto-pairs works, type (.
Run :Telescope.
Type ( in telescope's prompt.

Step number 5 should reproduce the unwanted match. What do you see when you say that you can't reproduce?

Note that the blacklist is intentionally commented out - doesn't autocomplete.

I don't understand why lack of autocompletion on that matters. Could you elaborate?
It's in auto-pairs' documentation and doesn't behave as expected. The fact that some tooling doesn't help autocomplete a global variable seems irrelevant to the matter.

I don't understand why lack of autocompletion on that matters. Could you elaborate?

I meant that pairs don't autocomplete in the telescope prompt, regardless of the option. I see how that sentence is ambiguous though - My bad ^^"
I'll need a little while to re-excavate my build tooling (and probably docker) to test a newer version.

Reproduced in latest nvim nightly - mildly sus this borders a bug in neovim, however, when it's this inconsistent with other versions. Gonna have to investigate further, but first impressions: none of this makes any sense what so ever :')
My first assumption is that neovim now triggers the autocmd when a buffer is made for the popup, which also explains why it bypasses the filetype blacklist. I was right, but also wrong.
It's not just called once - it's called four times without a filetype. The only component that varies between my old install and my dockerized nightly build is neovim, which means that it's either a neovim bug, or a neovim "feature". Either way, I have no idea how to fix it.
autocmd FileType * echom "Filetype set"
autocmd BufEnter * echom "BufEnter"
autocmd BufWinEnter * echom "BufWinEnter"

BufWinEnter is naturally triggered after BufEnter. Those autocmds are triggered four times with telescope. Here's the order:
BufEnter
BufWinEnter
# Filetype:
BufEnter
BufWinEnter
# Filetype:
BufEnter
BufWinEnter
# Filetype:
BufEnter
BufWinEnter
# Filetype:
Filetype set

The lines starting with # are auto-pairs output. Observe how the filetype is set after BufWinEnter is called.
using the autocmds above, on a rando file :e test.py, here's the output in Vim:
Filetype set
BufEnter
BufWinEnter
# auto-pairs doesn't output anything, because this is tested against my proper install that I haven't modified

Neovim?
BufEnter
BufWinEnter
# filetype: python

If I set ft=cpp, Filetype set. What this means is that whatever neovim did between the version I last built and now, they've completely broken basic autocmd and filetype setting, making this either a wontfix or requiring some neovim-specific hack that I don't know about and won't have a chance of finding on my own.
Interestingly, though, the version I have compiled doesn't trigger filetype on :e test.py either. I'm not sure why, but telescope doesn't trigger four separate autocmds in the version I have (also updated all plugins today for good measure). In fact, it only triggers the filetype autocmd. Doesn't make any sense what so ever :')
I'm going to report an upstream issue (assuming I can't find one or find something in the changelog indicating that this is intentional) either asking for this to be fixed, or asking for a workaround. If it's not a bug and there's no workarounds by design, I'll be closing this as wontfix, because I don't feel like adding code for dealing with new versions of neovim while remaining compatible with 0.4.x (which, mind you, is still the stable version).
Completely unrelated to this, I'm considering reworking some of the blacklist mechanics to not load anything auto-pairs related at all, which would exclude using autocmd FileType. Using that also introduces huge coordination issues in terms of loading anyway. I also can't unload all the keybinds without potentially losing information if the filetype later indicates that it's meant to be using different filetypes or not load at all. Some of this is gonna have to wait 'til tomorrow, because I don't feel like dealing with neovim making awful decisions and/or poor deployment systems when I'm this sleepy.

I've bisected Neovim and found the commit where this bug started happenig: https://github.com/neovim/neovim/commit/1def3d1542d6a65f057e743faea39a760b50db87. Up until https://github.com/neovim/neovim/commit/03b3ff861082ff09f2903565d928187489225306, there's no auto matching in Telescope.
I haven't looked into your comment or the neovim commit deeply yet. I intend to do so some time later.

Initial report done: Neovim/neovim#14798
Probably gonna need to revisit later ^^'

https://github.com/neovim/neovim/commit/1def3d1542d6a65f057e743faea39a760b50db87 was reverted in https://github.com/neovim/neovim/pull/14531, which makes no sense at all. I managed to reproduce it on my end until I updated Telescope and its dependencies, and it started working somehow. Not sure what that says about the blame, but it looks like everything is fine now?

Just verified with a couple checkouts, https://github.com/nvim-telescope/telescope.nvim/pull/1102 somehow fixes the problem. I have no idea how. Closing this for the time being.

I still have this problem on nvim v0.10.1, telescope v1.8.0, and auto-pairs v4.0.2.

@jackroi:
I can reproduce. Either https://github.com/nvim-telescope/telescope.nvim/pull/1102 or https://github.com/neovim/neovim/issues/14798 has regressed; this isn't auto-pairs' fault.
Using the same debugging approach as last time shows that when auto-pairs is invoked (at BufWinEnter or BufEnter[^1]), the filetype is once again wrong:

(Note that the autocmds have had &ft appended to the output)
That means the bug from last time, not caused by auto-pairs, has regressed. I will not be writing a workaround for this recurring nvim and/or telescope bug.
Open an issue in nvim's repo. It's either their fault, or telescope's fault, or both (again). You can also try not using nvim, which seems to break vim compatibility on a regular basis. This fork of auto-pairs is first and foremost a vim plugin. Nvim only has support as long as it doesn't sufficiently break core and standard vimscript functionality, which nvim happens to be notorious for doing on a regular basis. I don't mind adding minor things to get nvim to work, but breaking standard and established functionality is not something I want to work around.
Failing that, there are nvim-specific auto-pair plugins that work with nvim's non-standard behaviour. Seeing as nvim is drifting towards a full vim/nvim separation, that switch might be inevitable anyway.
[^1]:  It's supposed to be BufWinEnter by default. There's actually a minor bug around how this is set up caused by the variables not being loaded before the autocmd is declared. It does not matter though, because the filetype is wrong in both autocmds, because nvim.


Support terragrunt configurations the same as terraform modules

Terragrunt is a wrapper around terraform and uses the same syntax for module source. But the specification is in a terraform.tfvars file rather than .tf file, and it's in a terragrunt.terraform dictionary instead of module.
Something like this:
terragrunt = {
  terraform {
    source = "<repo_url>//<path/to/module>?ref=<semver>"

Ah, interesting. Any open-source repos you can point me to that use it, so I've got some fixtures to work with?

Here's one of mine, https://github.com/plus3it/wrangler-watchmaker/blob/master/release/salt-yum-defs/terraform.tfvars
Here's one from the gruntwork team, https://github.com/gruntwork-io/terragrunt-infrastructure-live-example

👍, this looks pretty easy. Working on a PR for it here.

This is done (I just forgot to close this issue!)