[BUG] Circuit Board Crafting Broken

[Please fill out the form below and delete the sections in square brackets after reading them]
Version of Advanced Rocketry

1.12.2-2.0.0-13

Have you verified this is an issue in the latest unstable build

[x] N

Version of LibVulpes

1.12.2-0.4.2-25-universal

Version of Minecraft

1.12.2 Forge

Does this occur without other mods installed

[x] N/A

Description of the problem

When crafting a circuit board on Advanced Rocketry, I put all the correct ingredients into the correct spot, but no circuit board is created. To be specific, nothing shows up in the slot on the right when all ingredients are put in. This applies to the Control Circuit Board, Item IO Circuit Board, etc... This is on a server and I have tried restarting it to fix the issue with no success. All other players on the server have the same issue. Everything else has been craftable so far.

Solved, the issue is that most recipes for advanced rocketry ask for a diamond in the top middle slot, but for this version quarts is used instead.


Fix CSP issue in ReMo.

Please add a comment pointing to the inline script that has that specific hash (inline definition of ga).


Additional vehicle endpoints

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I use some additional vehicle end points in my integrations.
Describe the solution you'd like
It would be good if these could be added:
charger_phases 2
charge_current_request 2
charge_current_request_max 16
charger_actual_current 0
conn_charge_cable IEC
fast_charger_present false
fast_charger_type ACSingleWireCAN
Additional context
No response

charge_current_request and charge_current_request_max are the charge current number entity.
Curious what the usecase is for the rest, but I have no problems adding them as disabled by default entities.

current_request, current_max and current_actual have different values at different times.  Would be good as attributes of the main current sensor, but you said we aren't supporting attributes in HA core (although I note location does have kat/ long as attributes)
I use charger_phases to determine the optimal charge power to schedule;
    - name: p_nom_ev
      unique_id: 4e531d66-eaff-4de6-b670-e9ab3d0ed793
#      state: "{{states('sensor.ev_extremely_low_charge_rate')}}"
      state:    >-
        {% if is_state_attr('sensor.m3p_charger_power','charger_phases',2) %}
          {{240*16*3}}
        {% else -%}
          {{240*32*1}}
        {% endif %}

Also to determine how many hours I should schedule charging for based on a range of variables:

#    - name: def_total_hours_ev
#      unique_id: 7663c831-7d49-4d62-a358-d743ddd25284
#      state: "{{is_state('automation.p_deferable2_automation','on')|abs
#             * (is_state('device_tracker.m3p_location_tracker','home')|abs)
#             * (is_state('binary_sensor.m3p_charger', 'on') | abs)
#             * (min(state_attr('sensor.m3p_time_charge_complete','minutes_to_full_charge')/60|int(0)+1,
#                    (states('number.m3p_charge_limit')|int(0) - states('sensor.m3p_battery')|int(0))
#                    /5/state_attr('sensor.m3p_charger_power','charger_phases')|int(0)+0.9))|float(0)|round(1)}}"
#

current_max is an attribute, this isnt hardcoded, its the API value. I'll add the actual and such as sensors.
min: 0
max: 32 <<<<<<
step: 1
mode: box
unit_of_measurement: A
device_class: current

I don't have any attributes on my number entity.

I think that page might only show custom attributes? Using developer-tools/state it shows them, so it will be avaliable for automations.
{{ state_attr("number.sonic_charge_current_2","max") }}

Oh right, you have setup as the limits for the number entity.
Learnt something new today :-)

charger_amps_actual & charger_amps_request can be and are often different.

Charger current is already a entity in the sensor platform.

@purcell-lab is there anything still outstanding from this issue?

All working well, thanks.


Infinite loop of retries for RetryFailed listener

I have a test run set up in GCP where in options I included RetryFailed listener and skips for tags "skip":
substitutions
...
_ROBOT_OPTIONS: --listener RetryFailed --exclude skip
_HEADLESS: 'True'
...

Inside the test case I use tag:
[Tags]    test:retry(1)

I faced an issue that test run is stuck in an infinite loop. In the logs I can see messages:

...and again, and again: PASS skip FAIL skip. And it retries like this for hours until the job stops by timeout. I have a scheduled run.
I ran the same exact configuration tests run in Docker container locally and RetryFailed listener works as expected, without this infinite loop of retries.
I don't know if anyone stumbled upon this issue, but I found no similar information as to why it might happen.
I'm not sure, but I think the issue might happen because of the thing that in this block of code it sets up the result.status = "SKIP", sets the retry count back to 0, and on the next retry, which shouldn't happen, it loops back again:
def end_test(self, test, result):
        if self.retries and self._original_log_level is not None:
            BuiltIn()._context.output.set_log_level(self._original_log_level)
        if not self.max_retries:
            self.retries = 0
            return
        if result.status == "FAIL":
            if self.retries < self.max_retries:
                index = test.parent.tests.index(test)
                test.parent.tests.insert(index + 1, test)
                result.status = "SKIP"
                result.message += "\nSkipped for Retry"
                self.retried_tests.append(test.longname)
                self.retries += 1
                return
            else:
                result.message += (
                    f"{linebreak * bool(result.message)}[RETRY] FAIL on {self.retries}. retry."
                )
        else:
            if self.retries:
                result.message += (
                    f"{linebreak * bool(result.message)}[RETRY] PASS on {self.retries}. retry."
                )
        self.retries = 0
        return

The expected behavior is that it should mark test as FAIL after defined number of retries, and then skip to the next test run

Hi,
I'm encountering the same problem where our Jenkins pipeline experiences prolonged delays whenever a test fails during execution.
Any assistance you can provide would be greatly appreciated.

I'm not sure, but I might have solved this issue:
The issue was that I configured tests run the way the --listener RetryFailed was in 2 different places:

in .sh test run script

xvfb-run \
    ...
    --listener RetryFailed \
    ...

in substitutions in cloudbuild.yaml

substitutions:
    ...
    ROBOT_OPTIONS: --listener RetryFailed --exclude skip
    ....

I removed --listener RetryFailed from cloudbuild.yaml and now it runs as expected, without the infinite loop of retries for the same failed test


Create automation for "finished running"

In Homekit "Faucets" cannot have automations.
To be able to run automations upon "program finished" for washingmachines etc. it would be nice to add a plain switch-device.
Also I noticed a typo, in homekit I found a nice new device with name "Masmachine". Edit: The typo was mine hahha
Hope you are able to add the switch though! It would give us great feature-possibilities  :)

Hi, your statement is incorrect. Maybe the Apple Home app doesn't support creating automations that include a faucet. But HomeKit certainly does. Also once created, it shows up correctly in Apple's Home App. See below for an example.

I would suggest to use the Eve app.

Great info, thanks, I didn't know that.
There is an issue though.. When the washing-program is finished, the device keeps displaying the loading symbol in the Home-app.
It goes to status Off after I manually switch the machine off (or when it switches to standby after some idle time)
Is this something you are able to change?

Hi, it is something I intentionally designed as such.
I figured this was the best of worst solutions available to indicate the washing machine is switched on but finished. You can have a look at the wiki of this GitHub to see the mapping. Then it is easier to understand why I did it.

I understand. The side-effect though,
The automation triggers 2 times. Once on "finished", and once on "off". Have you got an idea to go 'round this?

Hello, in Eve, in the triggers for a rule, in case of the Wash Machine, you can act upon the Faucet and the "In use" value; That is the way to only have one execution: for instance: faucet active AND "In use"= 0 will react on the ending of the program, not again when switching off the machine (or something like that, I am not in front of my systems).

Probably @MichelRabozee's answer is the easiest solution.
Myself I made a Home automation shortcut using the Home app in which I check the "in use" state and only then react. Alternatively you could also check the remaining duration or another state.

For the sake of completeness I’ll mention my solution,
I made a plain automation through the Eve app.
The Miele device now switches a virtual Domoticz switch.
In Domoticz a script runs on “Off”, only when the last status update was longer than 30 minutes ago.
Still I would prefer to see 2 switches in Homekit: 1 Powered on/off, 1 running/completed. It seems more logical to me instead of trying to run all events into 1 single switch.

I sort of understand, but also not. Since what you have is two switches:

In use
Active

You can put event triggers on them natively in HomeKit via Eve or one of the others. Only apple's own Home app doesn't allow it.

Ah yes of course, just now I get the “in use” part of it. Okay cool.
Just wondering, what does your Homepod play when your laundry is clean? ;)

To bother you once again on this topic,
Would you mind implementing mosquitto_pub MQTT messages on status updates?
Your plugin already does everything it needs to and I see everything is already in place to add this feature.
I'm interested in hearing your thoughts on this.

hey,
i have the same issue and iam not able to create the rule in EVE to trigger just on finishing. Can somebody support me here?
Attached is the rule in eve ;) Sorry it is in German.

@QuickSander or @superjunky  an you help with the eve rule?

This is what my rule looks like:

@superjunky if i do it like this the automation always gets triggered when turning on the machine and when it is finishing.


Feature request: Show a notification for SafetyNet requests

Show something in the notification area (something like the root icon when root access is used on Lineage OS) when an app use SafetyNet that disappears automatically when the request ended.

sounds like a good idea

I'd love to see this!


Fix: non authored card titles come with appendix

Before: https://stage--dme-partners--adobecom.hlx.live/channelpartners/drafts/automation/regression/announcements?georouting=off
After: https://default-card-title-test-fix--dme-partners--adobecom.hlx.live/channelpartners/drafts/automation/regression/announcements?georouting=off

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

Project coverage is 83.36%. Comparing base (0629150) to head (beb82f0).
Report is 3 commits behind head on stage.

Additional details and impacted files
@@           Coverage Diff           @@
##            stage      #91   +/-   ##
=======================================
  Coverage   83.36%   83.36%
=======================================
  Files          10       10
  Lines        3180     3180
=======================================
  Hits         2651     2651
  Misses        529      529

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


bugreport: use tar.gz archive and expand help text

Description:
Uses tar.gz as the archive format and adds to the existing
help text regarding sensitive information in the bug report.

Affected area:

Functional Area

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3885 (a25a3db) into main (7afe0cb) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3885      +/-   ##
==========================================
+ Coverage   67.45%   67.57%   +0.11%
==========================================
  Files         201      201
  Lines       11173    11173
==========================================
+ Hits         7537     7550      +13
+ Misses       3586     3573      -13
  Partials       50       50

Flag
Coverage Δ

unittests
67.57% <100.00%> (+0.11%)
:arrow_up:

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

Impacted Files
Coverage Δ

cmd/cli/support_bugreport.go
31.91% <100.00%> (ø)

pkg/k8s/announcement_handlers.go
72.97% <0.00%> (-5.41%)
:arrow_down:

...icate/providers/certmanager/certificate_manager.go
86.61% <0.00%> (+0.70%)
:arrow_up:

pkg/crdconversion/crdconversion.go
75.00% <0.00%> (+15.21%)
:arrow_up:

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 7afe0cb...a25a3db. Read the comment docs.


basic request streaming support with flow control

basic request streaming support, could be useful in cases like large file upload.

Anyone take a look ?

@yunstanford can review tomorrow

@abuckenheimer agree in general, but httptools doesn't provide the transport that we can control how many bytes to read from the socket. We can build another layer in StreamBuffer for read_n(bytes), but the data has been feed in memory already at that time.
This is a simple fix for https://github.com/huge-success/sanic/issues/546, providing basic data flow control.
We can look into httptools later and see if we can do more around that, and vender it if needed.

Gotcha, I still think REQUEST_BUFFER_QUEUE_SIZE is kind of meaningless though, we need to restrict based on amounts of bytes in the queue somehow. Making an actual async buffer is kinda complicated, I'm fine with moving forward on this as long as there is some sort of "alpha/beta" marker on streaming incoming requests because I have to imagine the API will change.

yeah, the API doesn't need change as we can set default value for .read(bytes=100), but we need to document that in the future.

Each item could potentially be any size in bytes, how do you plan on rechunking the bytes across items in the queue?
Also ideally the default would be return all bytes like a real buffer. I realize this is kind of an anti pattern because your really no longer streaming the request but, I'd expect body = stream.read() to return the whole body. I think n=100 would be easier to misuse than the alternative.

We'll need introduce another layer in StreamBuffer for rechunking, but didn't think deep into this. and introduce another API like .read_any(bytes=some) or some similar if you think it's less confusing.
Also in reality, the common use case, like uploading large file, usually is in a loop, users might be not very interested in the exact bytes in each single read.
We can definitely look into improving this in the future as mentioned before (not small amount of work). and we can provide the functionality/support first.

@yunstanford @ahopkins Can we get this feature in next release ?

@pypycoder Unfortunately not. We put a freeze on features a few weeks back for the 18.12 release (which is ready to ship). It should be added to 19.03

@yunstanford @ahopkins this PR broke the graceful shutdown of streaming responses in 19.03.1
(Perhaps I'll create an issue or PR later)


Clicking on Home should refresh it

This button?

Yes!
... so I guess it really is "HOME" :smile:


remember entry._type

Required for better duck-type usage

_type is deprecated in the BlobEntry type.  It's a leftover of when we had an AbstractBlobEntry

@Affie  please keep _type in, do not deprecate


TextField Warning: value prop on input should not be null

TextField is throwing error when value prop of controlled component is null.
warning.js:44 Warning: `value` prop on `input` should not be null. Consider using the empty string to clear the component or `undefined` for uncontrolled components.
    in input (created by TextField)
    in div (created by TextField)

This seems to have been caused by upgrading React to 15.3.0. Currently using material-ui 0.15.3

Shit, wrong repo. Sorry.


Decide on how to deal with exceptions

I feel that this app is throwing way too many types of exceptions. I need to take a thorough look at whether I could reduce the number of exceptions thrown and how they should be caught.
Also, decide how to deal with error responses and the error codes that exist. I feel like I should make error responses more structured.

I've decided to wait with the error response part of this issue. See #33 for follow-up on that.

I've decided to wait with the error response part of this issue. See #33 for follow-up on that.

Done.

Done.


Class Illuminate\Http\Request has a method named "method".

Laravel Version
11.16.0
PHP Version
8.3.10
Database Driver & Version
N/A
Description
Class Illuminate\Http\Request has a method named "method". Doubling classes that have a method named "method" is deprecated. Support for this will be removed in PHPUnit 12.
Looks like PHPUnit is deprecating mocking classes with a method called "method." I am not sure what the work around here is. Mockery has its own set of issues with PHPStan when setting up expectations. Call to an undefined method Mockery\ExpectationInterface|Mockery\ExpectsHigherOrderMessage::with().
I would prefer to use PHPUnit's built in mocking but I am wondering how that is going to work with Laravel moving forward as you've implemented Illuminate\Http\Request::method(). If I need to move to PSR-7 or something else to avoid this, I would rather do that sooner than later.
Steps To Reproduce
class MyControllerTest extends Illuminate\Foundation\Testing\TestCase
{
    public function testMyEndpoint(): void
    {
        // Class Illuminate\Http\Request has a method named "method". Doubling classes that have a method named "method" is deprecated. Support for this will be removed in PHPUnit 12.
        $this->createMock(Request::class)
            ->expects($this->once())
            ->method('input')
            ->with('param')
            ->willReturn('data');

       /* OR */

        // phpstan: Call to an undefined method Mockery\ExpectationInterface|Mockery\HigherOrderMessage::with().
        Mockery::mock(Request::class)
            ->shouldReceive('input')
           ->with('param')
           ->andReturn('data');
    }
}

It would be a difficult decision to make. The method() function is just a wrapper for getMethod() from Symfony/PSR-7 with no extra functionality so removing it to appease PHPUnit wouldn't be a loss of functionality... But it's still a massive BC break because method() has been the documented function to use for many, many years.
To a certain extent I don't like the idea of removing or changing the interface of a very commonly used class because an external library made a decision like this, and I suspect that the answer will be "we're leaving method() where it is. Just don't use PHPUnit's doubling feature for HTTP requests."
Laravel tests internally use Mockery, not PHPUnit's doubling features. I've never seen PHPStan complain about mocked classes - are you using Larastan? I suspect that it might be an issue with Mockery's documentation, so maybe it's worth going there to update doc blocks, or you might just be able to stub it out or add a rule to ignore that specific complaint.

It's not a common practise to actually mock a Request, since you can easily create an object instance using.
$request = Request::create(/* ... */);

https://github.com/symfony/http-foundation/blob/f602d5c17d1fa02f8019ace2687d9d136b7f4a1a/Request.php#L280

@crynobone I've spent a few hours trying to get $request = Request::create(/* ... */); working but unfortunately I still haven't figured out how to use Request::create(/* ... */)->validate() because it's macro is expecting $this->isPrecognitive() and it doesn't get set by FoundationServiceProvider.


Add APIs for configuring fair sharing

What type of PR is this?
/kind feature
What this PR does / why we need it:
Add APIs for fair sharing:

In KueueConfiguration, a new FairSharing struct to enable the feature and configure strategies.
In ClusterQueueSpec, a new FairSharing struct containing the weight.

Which issue(s) this PR fixes:

Fixes #1714
Special notes for your reviewer:
At this point, I'm looking for feedback on the types and field documentation.
Does this PR introduce a user-facing change?

Add fair sharing in a cohort when borrowing unused resources from other ClusterQueues in a cohort.

Fair sharing is based on DRF for usage above nominal quotas.
When fair sharing is enabled, Kueue prefers to admit workloads from ClusterQueues with the lowest share first.
Administrators can enable and configure fair sharing preemption using a combination of two policies: `LessThanOrEqualtoFinalShare`, `LessThanInitialShare`.

You can define a fair sharing `weight` for ClusterQueues. The weight determines how much of the unused resources each ClusterQueue can take in comparison to others.

cc @mwielgus @tenzen-y

This is now ready for review 😄
/assign @tenzen-y @mwielgus

By the way, it seems that the fairSharing feature overlaps borrowWithinCohort at some points. So, in the v1 API, we might be able to consolidate both APIs into a single one or provide a comprehensive feature somehow.

Did you mean that borrowWithinCohort can be replaced by using weight: 0?
If so, I agree. I would like to completely remove borrowWithinCohort once we go to v1, unless we hear some opposing feedback.

Did you mean that borrowWithinCohort can be replaced by using weight: 0?

Yes, exactly.

If so, I agree. I would like to completely remove borrowWithinCohort once we go to v1, unless we hear some opposing feedback.

SGTM

We should relax the threshold more on the perf-test, right?

We should relax the threshold more on the perf-test, right?

I think so, I opened https://github.com/kubernetes-sigs/kueue/issues/2140 to keep track, I should open a PR later today.

borrowWithinCohort once we go to v1, unless we

But why, do we have similar capacity covered this?

borrowWithinCohort once we go to v1, unless we

But why, do we have similar capacity covered this?

Yes, the biggest motivation to have borrowWithinCohort was to allow certain ClusterQueues to always be preempted whenever some other CQ needs the resources.
And this can be easily achieved when enabling fair sharing, by setting the weight on these "preemptible" CQs to zero.

@tenzen-y anything to add?


Clone ores utilizing Enrichment Chamber and Redstone Furnace from TE

I was using this setup here on a server and noticed some strange results: http://puu.sh/i4qhG/4448c42fa4.jpg
I placed a full stack of sand in the Redstone Furnace and while it was operating, placed iron ore into the Enrichment Chamber.
When the Enrichment Chamber finished, it immediately pushed its iron dust into the ORANGE slot of the Redstone Furnace (which if of course output, nothing should go in there) and when the Redstone Furnace finished its operation, I found myself with 3 iron dust instead of 2.

This should be fixed as of a recent change.


improve cmake (portable on all OSes), add appveyor and travis CI

Plus other minor fixes

@cenit Thanks!
Yes, it seems it's better to make uniform short paths for both Win/Linux.
Travis and appveyor are good things too.
I will try to test it when I will have a time.

sure, no hurry. I just wanted to share what I had to do on this project to adapt to my workflow. If there's anything interesting for you, please feel free to pick it :)

Thank you so much for all your work!


flyteidl 1.2.8

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

This is merged into the v1.2_release branch, as flytekit appears to be maintaining a 1.2 release series

https://github.com/flyteorg/flytekit/releases/tag/v1.3.0


mindreader gets stuck uploading blocks to s3 after network communication issue

There are multiple reasons why s3 could be unreachable.  Server overloaded, network fail, s3 unavailable etc.
With the latest dfuse / sf binaries, there is a problem where if s3 cluster becomes unavailable for some reason, mindreader will no longer upload one-block files.  This was also seen on new jungle binary compiled back in November.
I managed to catch another case of the problem just now.  Logs are available for your investigation (not attached here)
This was discussed a few months back.  But the problem has occurred a few times now, so I'm pretty confident with the analysis. Binaries built before May 28 2021 do not have this problem. The problem was definitely there by November 26.

@matthewdarwin please try tag v0.10.0-rc.5 (build incoming) and see if the issue is still there.
This bug could also be the cause of https://github.com/streamingfast/sf-ethereum/issues/7

Yes, I'm pretty sure they are related.  I have been paying attention. I had no shutdown issues when s3 is happy.

This issue seems to be resolved. I am closing it. If I run into more problems, I will open a new issue.


[Feature] Dummy Express Server that could be used for sniffing

Feature Request

name: Dummy Express Server that could be used for sniffing
about: "This is to start a dummy server for testing."

Please Describe The Problem To Be Solved
Creating a dummy server as part of the code base to test and validating the sniffing
Suggest A Solution:
Building a simple server with basic RESTful APIs.

@idodav: Can i pick this up?


Don't use unaligned access on ARM

On ARM, unaligned memory access is not guaranteed to succeed; depending on
the CPU and the kernel configuration, it may raise SIGBUS instead.
memcached defaults to using unaligned access, which caused the package to
fail to build on Ubuntu infrastructure where SIGBUS is raised.
All credits to: Nishanth Aravamudan<EMAIL_ADDRESS>Original bug report: https://bugs.debian.org/879797

Hey,
Well I found out about this a month ago in https://github.com/memcached/memcached/issues/312

managed to get a repro after compiling things on my rpi3 for six hours.

Unfortunately this patch just forces aligned access for all platforms all the time forever, so I can't accept it :) I'll leave this open until I get time to fix the detector for ARM. It shouldn't be too hard since I do have a repro, but that code is tricky.

figured this out. GCC O2 was eliding the alignment test in configure.
fixing it fixes the binprot test, but apparently I have some fairly bad unaligned accesses in the logging code. leaving a note here so I don't forget what I was doing and finish fixing it tomorrow.

should be fixed properly in the next branch if you want to give it a try

released in 1.5.7


Type forking causes service timeout

Environment

OS:  Ubuntu 16.04
Redis version:  4:4.0.8-1chl1~xenial1

Using the default ppa

Puppet module:  the add_redis_4_support branch
Puppet version:  4.10.10

Summary
When the service file is setup w/ Type=forking, I get timeouts, and the service continually restarts in a loop.
Job for redis-server.service failed because a timeout was exceeded.

When I remove that setting (therefore using the default:  Type=simple), then it works as expected.
Why is that?  I assume it's because redis doesn't call fork() as part of its setup.

Taken from http://manpages.ubuntu.com/manpages/xenial/en/man5/systemd.service.5.html#contenttoc4

For now, I'll have to workaround this by creating my own service file and the service.

Passing manage_service_file: false

Actually, the manage_service_file isn't a public class param.

It's set by default to false in params
It's set to true when default_install: true.

So, I'd have to set default_install: false, then repeat everything in https://github.com/arioch/puppet-redis/blob/add_redis_4_support/manifests/instance.pp just so I can change the content of the service file.

In fce8da9c7b977db9f87e236cf63c2cb97abe8f93 daemonize behavior was improved to match the OS defaults. I believe with that this issue can be closed.

Hilarious, I was just updating my Puppet stack and got bit by this again on v5.0.0.
Looks like it's fixed in https://github.com/voxpupuli/puppet-redis/commit/d779b75a937dd846323481e72eb604f5829e4c0e#diff-8845f76d702128044df189e2b992901e
I'll try that now.

I just confirmed that the above commit fixed this.
This time, here are my environment details:

OS: Ubuntu 18.04
Redis server version: 5:5.0.7-1chl1~bionic1 (from http://ppa.launchpad.net/chris-lea/redis-server/ubuntu bionic/main)
Puppet module: https://github.com/voxpupuli/puppet-redis/commit/d779b75a937dd846323481e72eb604f5829e4c0e
Puppet version: 6.13.0

Thanks to everyone involved in making the updates to the service file!


Fixing small typo

Thanks, but I actually meant 'notation' – 'notation' of rotation value is data-rotation="90". :)


Mission control bug in contextTimeGraphQL

Describe the bug
The Context Time GraphQL in settings section does not show the value of  contextTimeGraphQL since the field in config is contextTimeGraphQL. However, mission control assumes the field to be contextTime.

If this bug restricts your use of space-cloud, give it a thumbs up reaction, so that we can determine which bugs need to be fixed immediately.
👍

Done.Coming in v0.18.1


[SPARK-35192][SQL][TESTS] Port minimal TPC-DS datagen code from databricks/spark-sql-perf

What changes were proposed in this pull request?

This PR proposes to port minimal code to generate TPC-DS data from databricks/spark-sql-perf. The classes in a new class file tpcdsDatagen.scala are basically copied from the databricks/spark-sql-perf codebase.
Note that I've modified them a bit to follow the Spark code style and removed unnecessary parts from them.
The code authors of these classes are:
@juliuszsompolski
@npoggi
@wangyum
Why are the changes needed?

We frequently use TPCDS data now for benchmarks/tests, but the classes for the TPCDS schemas of datagen and benchmarks/tests are managed separately, e.g.,

https://github.com/apache/spark/blob/master/sql/core/src/test/scala/org/apache/spark/sql/TPCDSBase.scala
https://github.com/databricks/spark-sql-perf/blob/master/src/main/scala/com/databricks/spark/sql/perf/tpcds/TPCDSTables.scala

I think this causes some inconveniences, e.g., we need to update both files in the separate repositories if we update the TPCDS schema #32037. So, it would be useful for the Spark codebase to generate them by referring to the same schema definition.
Does this PR introduce any user-facing change?

dev only.
How was this patch tested?

Manually checked and GA passed.

Test build #137658 has started for PR 32243 at commit 7b6949d.

Great work, @maropu and thanks for making this happen

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42187/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42187/

Test build #137658 has finished for PR 32243 at commit 7b6949d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait TPCDSBase extends SharedSparkSession with TPCDSSchema
trait TPCDSSchema
class Dsdgen(dsdgenDir: String) extends Serializable
class TPCDSTables(sqlContext: SQLContext, dsdgenDir: String, scaleFactor: Int)
class GenTPCDSDataConfig(args: Array[String])

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137658/

Glad to see this update happening.  Ideally, if we can store the [compressed] sf1 scale factor in a public server, there shouldn't be much of a need for compiling dsdgen and the generation.  I see in the PR that there is some caching already.
With @HyukjinKwon we need to update spark-sql-perf to the latest TPC-DS spec and query templates. @gatorsmile let's coordinate that effort.

I think it's okay. As you pointed out, GitHub Actions already caches the generated SF1 data one, and it doesn't seem adding much codes for that.

we need to update spark-sql-perf to the latest TPC-DS spec and query templates
@maropu would you mind porting the TPC-DS spec and query update to spark-sql-perf when you find some time?

Ur..., I noticed that generated data are different between the GA env(Ubuntu) and my env(MacOS) by following the same workflow. Probably, the generator behaviour seems to depend on the implementation of random functions. I'm currently not sure that we can generate the same data between different linux distro, so I need more work (e.g., adding a script to generate data on docker env) for making it easy for developers to generate data/golden files....

@maropu would you mind porting the TPC-DS spec and query update to spark-sql-perf when you find some time?

Of course not. Probably, I have time to work on it tomorrow.

Test build #138095 has started for PR 32243 at commit ef68b61.

Test build #138095 has finished for PR 32243 at commit ef68b61.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138095/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42615/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42615/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42615/

Test build #138110 has started for PR 32243 at commit 5ee9c1a.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42631/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42631/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42638/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42638/

Test build #138117 has finished for PR 32243 at commit a88fe32.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138117/

Test build #138119 has started for PR 32243 at commit 5f4d022.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42640/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42640/

Test build #138119 has finished for PR 32243 at commit 5f4d022.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138119/

okay, ready to review. cc: @juliuszsompolski @npoggi @wangyum

Thank you, @HyukjinKwon @dongjoon-hyun ~ Merged to master.

Arriving a big late.  Looks good. We should move the DDL for the tables as resource files at some point.  Thanks for the update.


SSL support

Lets get the SSL support we built internally to this project

Sorry, I think I misspoke in our conversation—the SSL support is for finagle-postgres, and is now available in the Finagle org fork.


Client on Windows

Set up pivpn and created a couple users. What client would you recommend under windows 10? I've tried the OpenVPN Connect Client from http://help.unotelly.com/support/solutions/articles/184301-openvpn-desktop-client-setup-windows- and OpenVPN Portable from https://sourceforge.net/projects/ovpnp/. In either case I get an error similar to this:
Options error: Unrecognized option or missing parameter(s) in stdin:11: tls-version-min (2.1.1oOAS) Use --help for more information.
That happens to be from trying to use the Connect Client. When I try to use OpenVPN Portable I get:
Options error: Unrecognized option or missing parameter(s) in Jeff.ovpn:11: tls-version-min (2.2.2) Use --help for more information.
In both cases it is complaining about the tls-version-min line in the ovpn file. Perhaps the OpenVPN packaged with this is too old to work with the options you're using. I'd install the OpenVPN package but I don't need a server and it wasn't clear which options to select to install just the client.

Found the answer https://github.com/pivpn/pivpn/blob/8f09ee9afd9c936af97daddb3c538c56a0a991b0/README.md
Thanks for the great script.


Add support for GKE

What does this PR do?
Add support for GKE
Which scenarios this will impact?
None for now
Motivation
Better GCP support
Additional Notes

/merge


Add samples about how to copy files using PowerShell cmdlets

Add samples about how to copy files using PowerShell cmdlets

Hi @gangsir, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@gangsir Thank you for this contribution.  I'll have the author review.
@tamram Would you please review this change and let me know if I should merge it?  Thank you.


Is there a way to create a custom editor with 'vue component'?

Hi @huangdaodai,
Here you can find a simple example: http://jsfiddle.net/k5cqjz8t/


try the ci mechanism for testing crucible and rickshaw updates

This is very old and very stale...and it was never intended to be merged anyway as I recall.


abapdoc check: local classes and interfaces

Remove check for local classes and interfaces? Create a setting that regulates its requirement?
(Currently abapdoc is required for local classes and interfaces)

create a setting that regulates it, default to not require abapdoc for local classes

class_definition.ts have methods:   public isLocal(): public isGlobal():
Suggest we add similar methods in interface_definition.ts, the heuristic can be added in the method, note the filename was added yesterday, which can be used to determine if it is global

actually interfaces work the same way as classes, "INTERFACE zif_test PUBLIC."


feat: test targets

Motivation
Add feature flag to be able to lower coinbase and proof targets for testing purposes. This feature flag will lower the proof and coinbase targets to 8 and 32 respectively.
The feature flag needed to be cascaded to all dependencies of snarkVM to be sure everything uses same constants.
To use, compile with --features test_targets
e.g.
cargo install --locked --features test_targets --path .

Test Plan
tested by using tx-cannon and adding println to verify correct targets.
Related PRs
Must first merge https://github.com/AleoNet/snarkVM/pull/2529 and the snarkVM revision must be updated in snarkOS in 2 places before merging this.

Does this apply to compiled snarkOS binaries via cargo install --path .? What does that process look like? Additional documentation in the PR description/in the code would be helpful to know the implications.

@raychu86 I've updated the description. Let me know if still not clear.

So if cargo install --locked --features test_targets --path . is used. The snarkOS binary will always have the test_targets version of the coinbase targets? We should have some failsafes where the node fails to boot-up in production mode if that is the case.
We need some sort of enforcement that the test_targets is being used only for devnets via --dev

Superseded by https://github.com/AleoNet/snarkOS/pull/3424 to resolve merge conflict


Catalog event tags

Catalog event tags as EventTag.* enums.
Standardize tag names for role events.
Record missing role events.
Update journal entries (cherry-picked from #11779).
Closes #7119.

This pull request should be reviewed and merged first.


[Google Workspace] Search and Reval Google Drive Files/Folders in Finder

Extension
https://www.raycast.com/raycast/google-workspace
Description
It would be awesome if there was a command that searched Google Drive and upon selection would reveal the file/folder in Finder.
Because of the way Google Drive mounts the drive locally, the files don't get indexed in MacOS. Additionally, the Google Drive application search only returns limited results.
The results of the Raycast Google Workspace extension are much better, but instead of opening in the browser, most often my workflow requires dealing with the files in Finder.
Opening the file locally in the associated application would be another great addition.
Who will benefit from this feature?
Anyone that works with Google Drive files locally.
Anything else?
No response

Unfortunately, Google Drive's API provides info about the files on Google Drive and doesn't have access to their location on the macOS file system, so I'm not sure this feature would be easily feasible.
That being said, there are still things that can be done to enable this feature. Here are some ideas:

Get the path of where Google Drive mounts locally (through a preference maybe?) and then construct the Finder path in the extension
Open the File Search Raycast command from the extension (Google files were properly indexed on this one)

That being said, things can still be done:

Using a preference to construct the path would work brilliantly!
The default File Search Raycast command doesn't return files on the local Google Drive for me. There's another Google Drive extension with a File Search command, but that seems to have problems with just the sheer amount of files on my Google Drive. It attempts to index and errors out. Also, by the nature of the indexing, it would mean whether a file/folder shows up depends on how long ago it was created and when the last index was built.


Logic for additional properties: dictionary type with object type value

We found many swagger examples (e.g. swagger, example) set value with primary type like string or integer for the dictionary type with object type value. The latest codegen will set such dictionary type with map[string][string]interface{} as m4 model it with any-object. It will cause marshal/unmarshall failure. The root cause is the wrong swagger definition. But other language's SDK use special logic for such type's code generation. We should decide how we can handle such issues in GO SDK: 1. change codegen logic or 2. use directive to rewrite all the wrong definition and then fix swagger one by one.

The current thinking is that we'll require the service teams to fix their affected swagger.  Will update as more info is available.

Fixed in upcoming preview.36 release.


UI - View a live delivery tasks list on the dashboard

As a driver supervisor, I would like to view the incomplete delivery tasks on the dashboard so that it acts as a alert for me to take action.

done


i18n path error

As of the current main this error will be displayed in the terminal when running the command npm run test from the frontend dir. After it runs it would return this error for i18n translations, It seems the issue has to do with the strings not being set correctly for the path.

Error: Command failed: npm run i18n
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:405:5)
    at validateString (node:internal/validators:162:11)
    at Object.join (node:path:1175:7)
    at file:///home/vtaylor/headlamp/frontend/src/i18n/i18next-parser.config.js:5:28
    at ModuleJob.run (node:internal/modules/esm/module_job:192:25)
    at async DefaultModuleLoader.import (node:internal/modules/esm/loader:228:24) {
  code: 'ERR_INVALID_ARG_TYPE'
}```

Issue is fixed with node update


Windows Crash v1.10.12

Happened till now once.
 [Mon Oct 30 11:03:04.010865 2017] [mpm_winnt:notice] [pid 1516:tid 448] AH00428: Parent: child process 2060 exited with status<PHONE_NUMBER> -- Restarting.
h2_bucket_beam.c

204 {
205    h2_bucket_beam *beam = ctx;
206    pbl->mutex = beam->lock; Unhandled exception thrown: read access violation.**beam** was nullptr. occurred <===
207    pbl->leave = mutex_leave;
208    return apr_thread_mutex_lock(pbl->mutex);
209 }

Call Stack
>	[Inline Frame] mod_http2.so!mutex_enter(void *) Line 206	C	Symbols loaded.
 	[Inline Frame] mod_http2.so!enter_yellow(h2_bucket_beam *) Line 213	C	Symbols loaded.
 	mod_http2.so!h2_beam_get_buffered(h2_bucket_beam * beam) Line 1168	C	Symbols loaded.
 	mod_http2.so!report_stream_iter(void * ctx, void * val) Line 380	C	Symbols loaded.
 	mod_http2.so!ihash_iter(void * ctx, const void * key, int klen, const void * val) Line 270	C	Symbols loaded.
 	libapr-1.dll!74cf6ed1()	Unknown	No symbols loaded.
 	[Frames below may be incorrect and/or missing, no symbols loaded for libapr-1.dll]		Annotated Frame
 	mod_http2.so!h2_ihash_iter(h2_ihash_t * ih, int(*)(void *, void *) fn, void * ctx) Line 279	C	Symbols loaded.
 	mod_http2.so!h2_mplx_release_and_join(h2_mplx * m, apr_thread_cond_t * wait) Line 465	C	Symbols loaded.
 	mod_http2.so!session_cleanup(h2_session * session, const char * trigger) Line 697	C	Symbols loaded.
 	mod_http2.so!h2_session_pre_close(h2_session * session, int async) Line 2279	C	Symbols loaded.
 	mod_http2.so!h2_conn_pre_close(h2_ctx * ctx, conn_rec * c) Line 265	C	Symbols loaded.
 	mod_http2.so!h2_h2_pre_close_conn(conn_rec * c) Line 680	C	Symbols loaded.
 	libhttpd.dll!74d5e9f5()	Unknown	No symbols loaded.
 	mod_http2.so!update_child_status(h2_session * session, int status, const char * msg) Line 1596	C	Symbols loaded.
 	[Inline Frame] mod_http2.so!transit(h2_session *) Line 1621	C	Symbols loaded.
 	[Inline Frame] mod_http2.so!h2_session_ev_local_goaway(h2_session *) Line 1648	C	Symbols loaded.
 	mod_http2.so!dispatch_event(h2_session * session, h2_session_event_t ev, int arg, const char * msg) Line 1927	C	Symbols loaded.
 	mod_http2.so!h2_session_shutdown(h2_session * session, int error, const char * msg, int force_close) Line 671	C	Symbols loaded.
 	[Inline Frame] mod_http2.so!h2_session_ev_conn_error(h2_session *) Line 1676	C	Symbols loaded.
 	mod_http2.so!dispatch_event(h2_session * session, h2_session_event_t ev, int arg, const char * msg) Line 1933	C	Symbols loaded.
 	[External Code]		Annotated Frame

Thanks for the nice stacktrace!
Please try v1.10.13.

Fixed in v1.10.13


Issue setting up surveyjs

Are you requesting a feature, reporting a bug or ask a question?
Asking a question/reporting a bug
What is the current behavior?
Receive "Uncaught Error: Element type is invalid"
Full console log:
Uncaught Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in. Check the render method of SurveyClass.
at invariant (bundle.js:752)
at instantiateReactComponent (bundle.js:39999)
at instantiateChild (bundle.js:61979)
at bundle.js:62006
at traverseAllChildrenImpl (bundle.js:40292)
at traverseAllChildrenImpl (bundle.js:40308)
at traverseAllChildren (bundle.js:40387)
at Object.instantiateChildren (bundle.js:62005)
at ReactDOMComponent._reconcilerInstantiateChildren (bundle.js:61668)
at ReactDOMComponent.mountChildren (bundle.js:61707)
What is the expected behavior?
Survey displaying on page
How would you reproduce the current behavior (if this is a bug)?
The line <Survey.Survey json={surveyJSON} /> seems to cause the issue.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
import React from 'react';
import ReactDOM from 'react-dom';
import { Survey, Model} from 'survey-react';
class SurveyClass extends React.Component {
render() {
const surveyJSON = { pages: [{ elements: [{ type: 'dropdown',
choices: [{ value: 'item1', text: 'Hospira' }, { value: 'item2',text: 'Drager' },
{ value: 'item3', text: 'Medtronic' }],
choicesOrder: 'desc', name: 'Manufacturer',
title: 'What is the manufacturer of the device?' }], name: 'page1' }]};
return (

<Survey.Survey json={surveyJSON} />

);
}
}
export default SurveyClass;
Specify your

browser: Chrome
browser version: 59.0.3071.104
surveyjs platform (angular or react or jquery or knockout or vue): react
surveyjs version: 0.12.17

Bug with azureedge script, used require in my jsx file and got it working


the wisdom of Wu or Cash Rules Everything Around Me (C.R.E.A.M.)  or how will we pay for this?

Hi all, so now that we've been accepted we'll need to figure out how to handle the publishing fee.  I think we have 3 options as I recall.

Ask for a waiver
Ask the SWC powers that be for the money
@jhollist at one point suggested he might be able to get the EPA to pay.  Not sure where we still stand on this.

I am willing to make the ask, but we would have to subject the manuscript to internal EPA review.  That wouldn't be too bad and quite frankly could happen in parallel to review for the journal.  Even then I am not guaranteed to get a yes on this one.
I think 1 or 2 (or a combination) would be the best tact.  We can save the EPA route as a last option.

Fourth is ask anyone w/ a budget for publication fees to pony up.
How much?
On Thu, Apr 28, 2016 at 11:54 AM Edmund Hart<EMAIL_ADDRESS>wrote:

Hi all, so now that we've been accepted we'll need to figure out how to
handle the publishing fee. I think we have 3 options as I recall.

Ask for a waiver
Ask the SWC powers that be for the money
@jhollist https://github.com/jhollist at one point suggested he
might be able to get the EPA to pay. Not sure where we still stand on this.

[image: giphy 11]
https://cloud.githubusercontent.com/assets/1039395/14894162/3718ce66-0d27-11e6-947e-83ded53a2f28.gif
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/130

It is a bit pricey. $2250
More at http://journals.plos.org/ploscompbiol/s/publication-fees

The fee is  $2,250. I'm happy to go to Greg and Jonah if no one has any publication budget.  So I think the current order of preference is:

Anyone with budget steps forward to cover it
We ask Jonah / Greg
We ask for a waiver
Consider the EPA

I concur!

So...ahem...anyone have $2250?  Or should I go right to Greg?

I have 99 problems but being able to spend 2250 ain't one.
I can pay part of it and would be happy to, though.
Unless we have a secret editorial board discount I don't know of...

I can also pay part.
On Thu, Apr 28, 2016 at 4:48 PM Timothée Poisot<EMAIL_ADDRESS>wrote:

I have 99 problems but being able to spend 2250 ain't one.
I can pay part of it and would be happy to, though.
Unless we have a secret editorial board discount I don't know of...
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/130#issuecomment-215573056

I don't have any funds to contribute, unfortunately.

I need a few days to check
On Sat, Apr 30, 2016 at 1:12 PM Kara Woo<EMAIL_ADDRESS>wrote:

I don't have any funds to contribute, unfortunately.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/130#issuecomment-215984651

Software Carpentry can kick in $500 toward this. cc @jduckles

Great!  Thanks @gvwilson, looks like we should have no worries coming up with the fees.  Thanks everyone.

Just let me know at<EMAIL_ADDRESS>when you need me to disburse the partial payment.

Finally got the provisional acceptance.  a few typos and then all that's left is to pay the bills.  @dlebauer @tpoisot and @jduckles I'll be in touch over e-mail to figure out how best to pay the bills.  It's been a long time coming, but it should be out soon.

w00t! 🎉

This has been sorted out, and paper is production, closing.


Change KafkaBackOffException Log Level to Debug

Resolves #2009
Currently KafkaBackOffException is being logged at WARN level, which is verbose and creates confusion.
This PR leverages the existing KafkaException.Level structure to change the logging level to DEBUG and remove the coupling between the KafkaMessageListenerContainer and KafkaBackOffException.

This seems to be a proper solution without any meaningful side effects, WDYT?
While looking into this, I noticed that it seems the original exception's message (the one being thrown by the listener in the first place) is not being logged.
Looks like since the recoverer kicks in and has a successful execution (sending to the next topic), the error message never gets logged.
Would it make sense to log every Listener execution failure? The problem is if I understood correctly the original exception never gets logged.
LMKWYT
Thanks!

Changed the solution because the previous one would interfere with other exceptions.
My intention here is to remove BackOff related code from the KafkaMessageListenerContainer. This solution duplicates logic, albeit a very small one, from the DefaultErrorHandler, so maybe there's room for improvement there.
But maybe it'd be simpler to just change the logging level directly in the KMLC as it was before 😄

I agree the decoupling makes sense; but I don't think we need a new subclass, we could just add

I'm not sure I follow; you mean checking the exception type in the DefaultErrorHandler? This would add the same coupling there. Maybe that's ok, since it's coupling an exception to an error handler, and is a simpler solution.
Another way I see around this would be if KafkaException could, maybe optionally, look into its causes to figure out the root logging level, in case there's a deeper KafkaException. Then we could set the debug logging level into the backoff exception itself. Since KE is responsible for its own logging, maybe that's not a bad complexity for it to have.

I mean doing this in the DEH....
SeekUtils.seekOrRecover(thrownException, records, consumer, container, isCommitRecovered(), // NOSONAR
		getRecoveryStrategy(records, thrownException), this.logger, getLogLevel(thrownException.getClass)); // <<<<< pass type

and then, maybe a more general API in KafkaExceptionLogLevelAware
public abstract class KafkaExceptionLogLevelAware {

	private KafkaException.Level logLevel = KafkaException.Level.ERROR;

	private final Map<Class<? extends Throwable>, KafkaException.Level> levels = new HashMap<>();

	{
		this.levels.put(KafkaBackoffException.class, KafkaException.Level.DEBUG);
	}

	/**
	 * Set the level at which the exception thrown by this handler is logged.
	 * @param logLevel the level (default ERROR).
	 */
	public void setLogLevel(KafkaException.Level logLevel) {
		Assert.notNull(logLevel, "'logLevel' cannot be null");
		this.logLevel = logLevel;
	}

	/**
	 * Set the level at which the exception thrown by this handler is logged.
	 * @return the level.
	 */
	protected KafkaException.Level getLogLevel() {
		return this.logLevel;
	}

	protected KafkaException.Level getLogLevel(Class<? extends Throwable> throwable) {
		return this.levels.containsKey(throwable) ? this.levels.get(throwable) : this.logLevel;
	}

	public void configureLogLevel(Class<? extends Throwable> throwable, KafkaException.Level level) {
		this.levels.put(throwable, level);
	}

}

I didn't answer your other point.

Would it make sense to log every Listener execution failure? The problem is if I understood correctly the original exception never gets logged.

The reason we added the KafkaExceptionLogLevelAware was because a lot of people complained about the log noise with it being logged on every retry.
But I see your point; since we always recover these failures, they are never logged. Maybe the DLPR needs an option to log the exception after successfully recovering a record (but that doesn't need to be part of this fix).

Actually; maybe we don't need any of this additional complexity; with just your change to the KMLC, the retryable topic code could simply set the DEH's log level to DEBUG for all exceptions?

Actually; maybe we don't need any of this additional complexity; with just your change to the KMLC, the retryable topic code could simply set the DEH's log level to DEBUG for all exceptions?

That was my previous attempt, but wouldn't that log every exception the recovery code might throw to DEBUG? Since they're all wrapped into a KE.

Yeah - need to take a step back and rethink; recovery exceptions should always log at ERROR, maybe in the FailedRecordTracker directly, regardless of the log level for KEs. I'd rather see such errors logged twice rather than not at all.

and then, maybe a more general API in KafkaExceptionLogLevelAware

The thing with this one is that the KafkaBackOffException comes wrapped in a ListenerExecutionException, so we'd have to either unwrap it or look into nested exceptions for this to work. But I agree since this is a class responsible for log levels it might be a good place to add the coupling, if we were going this way.

Yeah - need to take a step back and rethink; recovery exceptions should always log at ERROR, maybe in the FailedRecordTracker directly, regardless of the log level for KEs. I'd rather see such errors logged twice rather than not at all.

Actually, I stand corrected. There is logic in the SeekUtils class that logs the error regardless of it being a KE or not.
						logger.error(ex, () -> "Failed to determine if this record (" 								+ ListenerUtils.recordToString(record) 								+ ") should be recovererd, including in seeks");
So for the task at hand I think setting the DHR log level to DEBUG in the retry topic logic seems to be the right call.

I opened a new PR with the DHE solution - that worked well in my tests. If that's ok, we can close this one.

The reason we added the KafkaExceptionLogLevelAware was because a lot of people complained about the log noise with it being logged on every retry.
But I see your point; since we always recover these failures, they are never logged. Maybe the DLPR needs an option to log the exception after successfully recovering a record (but that doesn't need to be part of this fix).

We could log the error message just before we either send the record to the DLT or give up processing - that way nothing gets logged if any of the retrials work, and gets logged only once if none.

Replaced by https://github.com/spring-projects/spring-kafka/pull/2065


What is the easiest way to use deep-cache using the OneDiff's SDK?

I was trying to update stable-diffusion-benchmarks repository we have to include a test for OneFlow, but even when using the latest cu121 binaries (v=794a56cc787217f46b21f5cbc84f65295664b82c/oneflow-0.9.1) and the tip of this repo, all I can get is ~12it/s (which is great, but obviously far from the deepcache comfy version of 23it/s).

I was trying to update stable-diffusion-benchmarks repository we have to include a test for OneFlow, but even when using the latest cu121 binaries (v=794a56cc787217f46b21f5cbc84f65295664b82c/oneflow-0.9.1) and the tip of this repo, all I can get is ~12it/s (which is great, but obviously far from the deepcache comfy version of 23it/s).

We only provided deepcache for comfyui for now.  Later we will provide the pipeline.
You can try deepcache pipeline without onediff in https://github.com/horseee/DeepCache

stable-diffusion-benchmarks is a very good project. But I found that the speed tested by stable-diffusion-benchmarks is calculated by the end-to-end time and the number of iterations, which is not consistent with the real UNet iteration speed, because the VAE of oneflow has not been compiled. You can try to add the following code to make VAE to be compiled,
pipe.vae = oneflow_compile(pipe.vae)

Thanks @hjchen2, and yes, that's something we are aware of (and mention in the readme) and want to potnetially fix:

All the timings here are end to end, and reflects the time it takes to go from a single prompt to a decoded image. We are planning to make the benchmarking more granular and provide details and comparisons between each components (text encoder, VAE, and most importantly UNET) in the future, but for now, some of the results might not linearly scale with the number of inference steps since cost of certain components are one-time only.

We only provided deepcache for comfyui for now. Later we will provide the pipeline.

@isidentical  The deepcache pipeline merged: https://github.com/siliconflow/onediff/pull/450

@isidentical has successfully run deepcache pipeline.


Add Support Adding Extending TimeStamp Fields

Basic zip file support only have a 2 second resolution with its timestamps.
We should be able to easily add the Extra Fields which includes the enhanced timestamps which will give us better timestamps resolution.

Fixed via https://github.com/xamarin/LibZipSharp/pull/48


when import libraries, already registered error is occurred.

First of all, thank you for sharing your works.
I try to evaluate the model for testing my environment and model with following code
python3 train_net.py --eval-only --num-gpus 1 --config-file configs/coco/panoptic-segmentation/maskdino_R50_bs16_50ep_3s_dowsample1_2048.yaml MODEL.WEIGHTS ckpts/maskdino_r50_50ep_300q_hid2048_3sd1_panoptic_pq53.0.pth
But, error with AssertionError: An object named 'MaskDINOEncoder' was already registered in 'SEM_SEG_HEADS' registry! message.
Did anyone face the same case and have a solution?
Full Error message is below. Thank you.
Traceback (most recent call last):   File "train_net.py", line 46, in <module>     from maskdino import (   File "/workspace/MaskDINO/maskdino/__init__.py", line 23, in <module>     from .maskdino import MaskDINO   File "/workspace/MaskDINO/maskdino/maskdino/__init__.py", line 3, in <module>     from . import modeling   File "/workspace/MaskDINO/maskdino/maskdino/modeling/__init__.py", line 3, in <module>     from .pixel_decoder.maskdino_encoder import MaskDINOEncoder   File "/workspace/MaskDINO/maskdino/maskdino/modeling/pixel_decoder/maskdino_encoder.py", line 189, in <module>     class MaskDINOEncoder(nn.Module):   File "/usr/local/lib/python3.8/dist-packages/fvcore/common/registry.py", line 59, in deco     self._do_register(name, func_or_class)   File "/usr/local/lib/python3.8/dist-packages/fvcore/common/registry.py", line 43, in _do_register     assert ( AssertionError: An object named 'MaskDINOEncoder' was already registered in 'SEM_SEG_HEADS' registry!

No sure why this is happening. You can try cloning a clean copy of our code and rerun it.

I did get new clone repository before, and same result was appeared.
BUT after your reply, It works good. I don't know why.
Thank you for answering :)


Switch to PostgreSQL (Engine)

Is your feature request related to a problem? Please describe.
Currently our DEV and TEST engine runs on PostgreSQL and all other environments still on Oracle.
Describe the solution you'd like.

Provide separate PostgreSQL for each environment

No sharing of DBs across environments

Migration of data

IBS hat hier eventuell ein Tool (nachfragen)
Problematisch:

Oracle-Typen
Constrains

Configuration on Test, Demo, Processes-* and Prod

DB access from Engine, Engine-Rest & Cockpit

Remove custom PostgreSQL NoToast Dialect?

Describe alternatives you've considered
Continue to use Oracle -> Open Source strategy & better ext. usability of DigiWF through PostgreSQL
Acceptance Criteria

PostgreSQL databases are available for each environment and contain all data of the old DBs
All engine services are migrated to PostgreSQL

Wird nicht mehr benötigt


Rule34 xxx ripper

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[X] a new Ripper

Description
I added a unit test and ripper for rule34.xxx
Testing
Required verification:

[ ] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[ ] I've verified that this change works as intended.

[ ] Downloads all relevant content.
[ ] Downloads content from multiple pages (as necessary or appropriate).
[ ] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[ ] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

The failed tests unrelated to this ripper


Add command to add client to clients list by name (not requiring search).

Would it be possible to add a command to and a client name to to a vault item (even if that client doesn't exist yet). This would allow me to add the credentials of a user I want services to run as before bootstrapping the node, and get these services setup on bootstrap.
The alternative I have is just to store these in a node attribute, which is insecure.

Not sure you still have that issue but I think the only way to proceed with this is to add the vault attributes to your bootsrap command =>

knife bootstrap Options¶
Use the following options with a validatorless bootstrap to specify items that are stored in chef-vault:
--bootstrap-vault-file VAULT_FILE
The path to a JSON file that contains a list of vaults and items to be updated.
--bootstrap-vault-item VAULT_ITEM
A single vault and item to update as vault:item.
--bootstrap-vault-json VAULT_JSON
A JSON string that contains a list of vaults and items to be updated.

For example:

--bootstrap-vault-json '{ "vault1": ["item1", "item2"], "vault2": "item2" }'

source : https://docs.chef.io/install_bootstrap.html

Hi,
Sorry just got round to trying this. I have having problems making this work in Client mode (the vault item), and can't see any flags in bootstrap to specify the mode.
Thanks for your help,
Tim

I think using this in the bootstrap command is automatically done on the chef server, there is no distinction between client or local mode.
Maybe post your commands/logs if you still have issues ?

I have a vault called credentials that has an item for each chef node, that in turn contains user, password and domain.
I think my previous problem was that I wasn't specifying the vault name and item name (just supplying the JSON I would pass to:
knife vault create credentials  -f JSON
When trying to set this using the '--bootstrap-vault-json' option I get
knife vault create credentials "%CHEF_NODENAME%" '{"user": "%CHEF_USER%", "password": "%CHEF_USER_PASS%", "domain":"%CHEF_USER_DOMAIN%"}' -M client -F JSON -S "role:*" -u "********"
Now when specifing the vault and item, as below:
--bootstrap-vault-json '{"credentials": {"%CHEF_NODENAME%": {"user": "%CHEF_USER%", "password": "%CHEF_USER_PASS%", "domain":"%CHEF_USER_DOMAIN%"}}}'
I get:
ERROR: URI::InvalidURIError: bad URI(is not URI?): https://pdgt-chef-server/organizations/snsystems/data/credentials/{""=>{"user"=>"", "password"=>"*******", "domain"=>"domain"}}_keys
Which looks like it's not parsing the JSON correctly (just seeing the item as a string).
Note: I am using Windows bootstrap and chef SDK v0.18.26.

Not sure if it helps but here is the debug log:
DEBUG: Initiating POST to https://########/nodes
DEBUG: ---- HTTP Request Header Data: ----
DEBUG: Content-Type: application/json
DEBUG: Accept: application/json
DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
DEBUG: X-Ops-Server-API-Version: 1
DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.1;
DEBUG: X-OPS-USERID: ########
DEBUG: X-OPS-TIMESTAMP: 2016-09-23T13:02:00Z
DEBUG: X-OPS-CONTENT-HASH: ############################################################
DEBUG: X-OPS-AUTHORIZATION-1: ############################################################
DEBUG: X-OPS-AUTHORIZATION-2: ############################################################
DEBUG: X-OPS-AUTHORIZATION-3: ############################################################
DEBUG: X-OPS-AUTHORIZATION-4: ############################################################
DEBUG: X-OPS-AUTHORIZATION-5: ############################################################
DEBUG: X-OPS-AUTHORIZATION-6: ############################################################
DEBUG: HOST: ########:443
DEBUG: X-REMOTE-REQUEST-ID: ########
DEBUG: Content-Length: 352
DEBUG: ---- End HTTP Request Header Data ----
DEBUG: ---- HTTP Status and Header Data: ----
DEBUG: HTTP 1.1 201 Created
DEBUG: server: openresty/<IP_ADDRESS>
DEBUG: date: Fri, 23 Sep 2016 13:02:27 GMT
DEBUG: content-type: application/json
DEBUG: content-length: 78
DEBUG: connection: close
DEBUG: x-ops-server-api-version: {"min_version":"0","max_version":"1","request_version":"1","response_version":"1"}
DEBUG: x-ops-api-info: ########
DEBUG: location: https://########/nodes/########
DEBUG: ---- End HTTP Status/Header Data ----
DEBUG: Chef::HTTP calling Chef::HTTP::ValidateContentLength#handle_response
DEBUG: Content-Length validated correctly.
DEBUG: Chef::HTTP calling Chef::HTTP::RemoteRequestID#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Authenticator#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONOutput#handle_response
DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_response
C:/opscode/chefdk/embedded/lib/ruby/2.3.0/uri/rfc3986_parser.rb:67:in `split': bad URI(is not URI?): https://########/data/credentials/{"########"=>{"user"=>"########", "password"=>"########", "domain"=>"########"}}_keys (URI::InvalidURIError)

This looks like a powershell quoting problem, and is definitely not an issue with the chef-vault cookbook. If you're still having problems, I'd recommend posting about the problem to https://discourse.chef.io or to stack overflow, or asking on slack via https://community-slack.chef.io .


Build error under io.js 1.1.0

My setup is io.js 1.1.0 installed with nvm on OS X 10.10 using the version of node-gyp that ships with io.js. Looks like a v8 compatibility issue. Here is the error output:
><EMAIL_ADDRESS>install /code/node_modules/sharp
> node-gyp rebuild

child_process: customFds option is deprecated, use stdio instead.
  CXX(target) Release/obj.target/sharp/src/common.o
  CXX(target) Release/obj.target/sharp/src/utilities.o
In file included from ../src/utilities.cc:4:
../node_modules/nan/nan.h:1848:10: error: no matching function for call to
      'Encode'
  return node::Encode(
         ^~~~~~~~~~~~
/Users/ide/.node-gyp/1.1.0/src/node.h:257:34: note: candidate function not
      viable: cannot convert argument of incomplete type 'const void *' to
      'const char *'
NODE_EXTERN v8::Local<v8::Value> Encode(v8::Isolate* isolate,
                                 ^
/Users/ide/.node-gyp/1.1.0/src/node.h:263:34: note: candidate function not
      viable: requires 3 arguments, but 4 were provided
NODE_EXTERN v8::Local<v8::Value> Encode(v8::Isolate* isolate,
                                 ^
/Users/ide/.node-gyp/1.1.0/src/node.h:268:45: note: candidate function not
      viable: requires at most 3 arguments, but 4 were provided
                inline v8::Local<v8::Value> Encode(
                                            ^
/Users/ide/.node-gyp/1.1.0/src/node.h:43:53: note: expanded from macro
      'NODE_DEPRECATED'
#define NODE_DEPRECATED(msg, fn) V8_DEPRECATED(msg, fn)
                                                    ^
/Users/ide/.node-gyp/1.1.0/deps/v8/include/v8config.h:332:45: note: expanded from
      macro 'V8_DEPRECATED'
# define V8_DEPRECATED(message, declarator) declarator
                                            ^
1 error generated.
make: *** [Release/obj.target/sharp/src/utilities.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/ide/.nvm/versions/io.js/v1.1.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:100:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1040:12)
gyp ERR! System Darwin 14.1.0
gyp ERR! command "node" "/Users/ide/.nvm/versions/io.js/v1.1.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /code/node_modules/sharp
gyp ERR! node -v v1.1.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Darwin 14.1.0
npm ERR! argv "/Users/ide/.nvm/versions/io.js/v1.1.0/bin/iojs" "/Users/ide/.nvm/versions/io.js/v1.1.0/bin/npm" "install" "sharp"
npm ERR! node v1.1.0
npm ERR! npm  v2.4.1
npm ERR! code ELIFECYCLE

This looks like a problem with nan instead of sharp I guess...

Hi James, is this with nan 1.5.x? sharp v0.9.1 contains @jonathanong's rewind of nan from 1.6.x to 1.5.x to temporarily remove this problem.
https://github.com/rvagg/nan/pull/265 will fix this.
Travis CI adds support for iojs in <5 hour's time according to http://docs.travis-ci.com/user/build-environment-updates/2015-02-03/ so I will add it to the build/test matrix soon after.

I was using 1.6.1 because npm pulled it in automatically. I tested locally with 1.5.3 and it builds without issue. I'll close this out. You're really on top of things!


Ask for username or password on connect if absent.

Ask for username or password on connect if absent. This is useful for connecting to databases with different username and passwords with single connection.

DBeaver will ask for password unless you check option "Save password in connection properties.

The same:


Chx/storage plugin

Add storage plugin

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


[tool_crash] FileSystemException: Failed to decode data using encoding 'utf-8', null

Command
flutter --no-color run --machine --verbose --track-widget-creation --device-id=chrome --start-paused --dart-define=flutter.inspector.structuredErrors=true --devtools-server-address=http://<IP_ADDRESS>:9100 lib\main.dart

Steps to Reproduce

...
...
...

Logs
FileSystemException: Failed to decode data using encoding 'utf-8', null
#0      _File._tryDecode (dart:io/file_impl.dart:564:7)
#1      _File.readAsStringSync (dart:io/file_impl.dart:584:7)
#2      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:96:16)
#3      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:221:22)
#4      _runSync (package:flutter_tools/src/base/error_handling_io.dart:573:14)
#5      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:220:12)
#6      isAppUsingAndroidX (package:flutter_tools/src/android/gradle.dart:898:21)
#7      _writeAndroidPluginRegistrant (package:flutter_tools/src/plugins.dart:626:17)
#8      injectPlugins (package:flutter_tools/src/plugins.dart:1202:11)
<asynchronous suspension>
#9      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:322:5)
<asynchronous suspension>
#10     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1175:7)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1043:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:196:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:284:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#16     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:232:5)

[✓] Flutter (Channel stable, 2.2.1, on Microsoft Windows [Version 10.0.18363.1556], locale zh-TW)
    • Flutter version 2.2.1 at F:\12\flutter
    • Framework revision 02c026b03c (8 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\zx60216\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe
    • Java version Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[✓] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 91.0.4472.77
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 91.0.864.37

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 02c026b03cd31dd3f867e5faeb7e104cce174c5f

Closing this as duplicate of https://github.com/flutter/flutter/issues/65021


continuous deployment

I'd like to set up continuous deployment for bridgy, granary, oauth-dropins, etc. background:
https://circleci.com/docs/introduction-to-continuous-deployment/
https://circleci.com/docs/deploy-google-app-engine/
the catch is all the silo app ids and secrets in local files. circle lets us set environment variables that are available during test/deploy, but we need to get them into app engine. needs more thought.

straw man: add all the app ids and secrets as circle environment variables, then write them to files in deploy.sh (if they don't already exist) before deploying.
another straw man: put them in the datastore. way more invasive, and would need new design and code to keep granary and o-d working for other users.


Electrum invalid fee.

Context
Hello i have a little problem my wallet electrum have the invalid fee message error when i want make a transaction. i have passed 10 hours on this problem and i can not to solve the problem. (sorry if i have a bad english)
Prerequisites

I run on electrum 2.4.1, windows 10 (64 bits), AMD FX 8350 OC (4,6 Ghz)

User Story:

it's literally 20 -25 days that i am not touching my wallet i comback recenlty on and i finds this problem, i have try to pass my xvg coins on the Electrum TOR wallet but the problem i'ts again here. i have try too the download the QT wallet for try a transaction on this but nothing too do. i have try to sweep my address on the menu wallet > private keys > sweep but nothing.. when i try this i have the message "TX rejected" and i cant finish the operation.

Screenshots

Your Environment

Verge Release: Electrum 2.4.1
CPU: AMD FX 8350 OC (4,6 Ghz)
GPU: GTX 1080 + GTX 1060
RAM: 16 Go DDR3 1800 Mhz
OS: Windows 10 (64 bits)

The manual fee doesn't work either.  Have to use default.

you too ?

i have test with all payement verified by removing the file blockchain_headers on C:\Users\AppData\Roaming\Electrum-XVG but nothing again..

I had this issue and resolved it by increasing the fee. the issue stems from the fact that your balance is split across many keys in your wallet, in order to generate the output, electrum has to combine the inputs of multiple keys to a single output. this is a larger sized (in KB) transaction and unfortunately XVG's electrum doesn't auto calculate the fee correctly. for me i had to test the transaction out multiple times and ultimately a fees of 5 verge led to a successful transaction. but this is unique to you and the number of input address you are using to generate the output of 540 xvg... good luck

I use 1 address for receive my xvg but i have a another address not used, i have tried a lot amount fee manual on "transaction fee per kb:" but even with 100 xvg in fee the transaction cant want send. you have enter the fee by checking "set transaction fees manually" or on "transaction fee per kb" ?

ok i have resolve this bug !!!! my god.. for info i have pass the "transaction fee per kb" at 2 on the preférence menu, i have then create an address for sweep the principal private key we need to go on the wallet menu > private keys > sweep and enter the private key of your address primary (address containing your XVG bugued) and you select the address where you want to send. (sorry i have not a good english but i hope this will help you.)


Integration preferences - blanking spectrum?

Integration of a 1D proton and going through preferences of these integrals in right panel: When I clicked on “save preferences” the whole page reloads and I had again blank window (no spectrum or anything I did before), not reproducible – 1/3 times

@nes-cgn
i try to re-simulate again what happens with you by save preferences for 20 times but the bugs not appear.


show parent node as selected using minus icon if any child node selected

I have request if this feature added then it will be very very great and helpful

In example 4, I demonstrated how to template. It's very easy: https://github.com/leovo2708/ngx-treeview/blob/master/src/lib/treeview.component.ts#L56

Sorry, I will apply this feature next time. Thank for your idea.

+1 Any progress on getting this added?

Yes, it is in my plan.

+1 Any progress on getting this added?

Any updates on this feature?

I will try to do this, already have a pull request here: https://github.com/leovo2708/ngx-treeview/pulls

I hope this will be added shortly. Good luck and thanks :)

Supported in new version 1.2.0


Crazy for a "collapse"

Hi Olton!
Help, I'm going crazy with a "collapse"! See the example:
https://codepen.io/TorakikiSan/pen/EeyWmp?editors=1111
If I activate the checkbox, the "collapse" should close and the button that opens / closes it should be disabled, but the JS returns error on the "collapse" component.
Where is the problem?
Thank's

Check your code. element with id DIV-MACHINE hasn't role collapse

https://codepen.io/olton/pen/OJbzXma?editors=1010

OMG!

Thank's!


Specifying build target

I'm building an OS kernel and use rust-script for some build tasks. However, cargo's config.toml file is still used for the script, and that TOML file contains actions for building parts of the rust standard library (core, alloc, ...). (This is a known issue for cargo.) Is there a way of getting around this? I'm using cargo-make, and I'd explicitly like the build script I use to not be influenced by anything in .cargo/config.toml.

@ethindp Have you found any way around this?
Does anyone know of a workaround (either to apply manually, or that can be added to rust-script)?

I ran into this problem recently, I have a project setup which targets an embedded device with a specific platform.
But also a subdirectory inside that with a rust based script I'd like to run
unfortunately it looks like cargo search up the directory tree for .config/config.toml in any of the parent directories which then influences how the script is built (which typically in my case is for the wrong target)
Under windows I had to use the -o option to see the compile fail message
I suspect it might be related to
https://github.com/rust-lang/cargo/issues/8643

I also stumbled on this problem. You can solve it by using unstable package.forced-target option (added in https://github.com/rust-lang/cargo/pull/9030) in Cargo.toml instead of setting target in .cargo/config.toml. It's nightly only, but it works.

But also a subdirectory inside that with a rust based script I'd like to run
unfortunately it looks like cargo searches up the directory tree for .config/config.toml in any of the parent directories which then influences how the script is built (which typically in my case is for the wrong target)

The just released version 0.23.0 avoids building the project in the current working directory (instead standing inside of the generated package), so should fix this. Let me know if any problem remains!


Controlling multiple charts with one subchart?

Hi i'm new to c3 and absolutely loving it so far.
The project i'm working on involves having multiple charts display data from the same time points. I'd really like to be able to control all 3 charts from the same subchart.
Zooming works kinda though when panning the x axis become mis-aligned
zoom: {         		enabled: true,             onzoomend: function(d){             		chart2.zoom(d);                 chart3.zoom(d);                 drugchart.zoom(d);             }           },
Just wondering what the syntax would be in order to have a subchart control more then one graph? I'm sure i've seen it done with d3

Doh! worked this out almost immediately after posting it though it had been eluding me for a week now.
For other peoples reference:
subchart: {
            show: true,
            onbrush: function (d) {
              chart2.zoom(d);
              chart3.zoom(d);
            },
          },

controls as many charts as you'd like very nicely. C3 continues to rock.


Feature:Update Compile SDK version to 33

Hi @sourav-xarterian ,
Can you check this why Merging is blocked.


python310Packages.azure-servicebus: 7.8.2 -> 7.10.0

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

2 packages failed to build:

python311Packages.dvclive
python311Packages.dvclive.dist

55 packages built:

baserow
baserow.dist
dvc
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist
paperless-ngx
python310Packages.azure-servicebus
python310Packages.azure-servicebus.dist
python310Packages.celery
python310Packages.celery-redbeat
python310Packages.celery-redbeat.dist
python310Packages.celery.dist
python310Packages.django-celery-beat
python310Packages.django-celery-beat.dist
python310Packages.django-celery-email
python310Packages.django-celery-email.dist
python310Packages.django-celery-results
python310Packages.django-celery-results.dist
python310Packages.django-health-check
python310Packages.django-health-check.dist
python310Packages.django-raster
python310Packages.django-raster.dist
python310Packages.djmail
python310Packages.djmail.dist
python310Packages.dvc-task
python310Packages.dvc-task.dist
python310Packages.dvclive
python310Packages.dvclive.dist
python310Packages.flower
python310Packages.flower.dist
python310Packages.kombu
python310Packages.kombu.dist
python311Packages.azure-servicebus
python311Packages.azure-servicebus.dist
sourcehut.buildsrht
sourcehut.buildsrht.dist
sourcehut.coresrht
sourcehut.coresrht.dist
sourcehut.gitsrht
sourcehut.gitsrht.dist
sourcehut.hgsrht
sourcehut.hgsrht.dist
sourcehut.hubsrht
sourcehut.hubsrht.dist
sourcehut.listssrht
sourcehut.listssrht.dist
sourcehut.mansrht
sourcehut.mansrht.dist
sourcehut.metasrht
sourcehut.metasrht.dist
sourcehut.pastesrht
sourcehut.pastesrht.dist
sourcehut.todosrht
sourcehut.todosrht.dist


[stable/prometheus-operator] fix coreDNS chart to have a dynamic datasource #22024

What this PR does / why we need it:
Fixes CoreDNS chart to work without having to name the datsource Prometheus
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #22024

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test
/lgtm


MRG, DOC: Inverse math

Working on making eLORETA have units nAm.
Along the way Writing out some of the inverse derivations and adding equation links so that they are hopefully easier to follow.
This does not work, mostly opening PR so that @agramfort can look at where I've messed up the math :)

Rendered doc:
https://17326-1301584-gh.circle-artifacts.com/0/dev/overview/implementation.html#the-minimum-norm-current-estimates

@agramfort only https://github.com/mne-tools/mne-python/pull/7160/commits/bf467a20af5d9725e0612104ba69f1847a38afac is new but I rebased + force-pushed, should have addressed all your comments:
https://18038-1301584-gh.circle-artifacts.com/0/dev/overview/implementation.html#the-minimum-norm-current-estimates

FYI I killed Travis because it's going to fail due to failures in master (and was passing last time master was green)

@hichamjanati I pushed a commit to hopefully address your comments with the exception of the C^{-^1/_2} changes, as I think those will require a bit more work to sort out (as a bit of a departure from the existing notation). For example we might want to adopt the "whitener" naming/nomenclature, or we might just want to use the standard definition of C^{-^1/_2}, or we might want to show why it doesn't matter which one you use for our purposes. Which is best will take some thinking and math to sort out...

I'll go ahead and merge this once CIs are happy.
BTW @hichamjanati feel free to take a shot at the whitener changes if you want (after merge) :)


Example fails

The example given at https://docs.rs/countme/3.0.1/countme fails at runtime, with both Rust 1.61.0 and 1.63-nightly. My guess is non-lexical lifetimes make the local variables disappear early?
(The following is from https://github.com/peter-kehl/countme_test, which has the aforementioned example pasted in.)
thread 'tests::countme_orig_example' panicked at 'assertion failed: `(left == right)`
  left: `0`,
 right: `2`', src/lib.rs:23:9

Works fine if you use the feature "enable". Don't know why that feature isn't on by default.


LRM lacks a method to remove a lockable resource from the list

What feature do you want to see added?
I've recently got a stuck ephemeral resource which was not removed from the list of lockable resources, even across several Jenkins restarts (which should involve clean-up). This resource is no longer occupied by any job that it was temporarily made for, just sits stuck there (it may be a contributing factor that the Jenkins instance in question has no persistent resources - could the auto-cleanup leave one resource in the list? it did auto-clean some other resources during restarts...)
Anyway that is a separate problem. As for this one -- as I was trying to gracefully clean the list, using the scripting console, I found that LRM offers many methods about adding, reserving, recycling, etc. but none to remove/destroy/delete a resource. The best I could come up with was using the reference to its internal resources list which is not too nice of a programming pattern in general (no synchronized wraps etc. here):
org.jenkins.plugins.lockableresources.LockableResourcesManager lrm = org.jenkins.plugins.lockableresources.LockableResourcesManager.get()
lrm.getResources().removeIf({r -> r.getName() == 'dynamatrix-stash:nut-ci-src:jenkins-nut-nut-PR-2220-1'})

So the proposal is to add a method (or two) that can delete a resource from the list, by LockableResource type directly or by its String name, so this is done "properly".
Upstream changes
No response
Are you interested in contributing this feature?
Yes, if others agree this is useful :)

I like it. Something like ?
LRM.removeResource(String resourceName)
LRM.removeResource(LocakbleResource resource)
LRM.removeResourceByLabel(String label)
LRM.removeResourceByLabel(String label, int quantity)

@jimklimov  is this enough?
https://github.com/jenkinsci/lockable-resources-plugin/blob/765becf53c59d3f88b67178f42e89e35b2b051cc/src/main/java/org/jenkins/plugins/lockableresources/LockableResourcesManager.java#L1080C4-L1080C70

Method LRM.removeResources() has been added, therefore it might be closed.


[CT-634] Node configs: tech debt

Context

Previous version of similar proposal: https://github.com/dbt-labs/dbt-core/issues/3557
Prompted most recently by https://github.com/dbt-labs/dbt-core/pull/5230, which adds grants as a config under NodeConfig, where it gets inherited by node types that won't actually use it.

Problem
We need to better organize our tightly bundled NodeConfig. Many of these configs are only relevant to "executable" nodes (models, snapshots, seeds, and tests IFF store_failures is enabled). Some of them are only relevant to incremental models in particular. Analyses have no business with database/schema/alias.
Existing proposals
Incremental models. Many many configs are really just relevant to the incremental model materialization. As discussed in #5089: It feels a little icky that configs like unique_key and on_schema_change appear in the config for every node, when they're really just relevant to incremental models in particular. Could we isolate these to appear on incremental models only? This could be:

an IncrementalModelConfig subclass, which would supply unique_key, on_schema_change, incremental_strategy, and (new) incremental_predicates if and only if materialized == 'incremental'
a dictionary named incremental  that contains strategy + predicates, and the old names can be passthroughs to that dictionary for backwards compatibility

Metadata interface. Every time we add a new attribute to NodeConfig, it changes the manifest.json artifact schema. As discussed in https://github.com/dbt-labs/dbt-core/issues/4617: Given that users can supply whatever configs they want, to any node type that accepts config, should we even consider this a contracted metadata interface? I think the external contract for node.config should really be Dict[str, Any], and we should always be in the habit of "promoting" configs that are relevant and reliable to downstream metadata consumers as top-level node keys. Similar to what we did with node_info on logging events, which "promotes" config.materialized into node_info.materialized.
Adapter-specific configs (sort of discussed in https://github.com/dbt-labs/dbt-core/issues/4622): I'm actually not sure if AdapterConfig works at all today. My sense is that their keys don't show up in the manifest unless set, their types aren't really validated until used (at runtime), and their default values don't get passed through. The code here is kinda jank, to put it nicely.

@emmyoop @jtcohen6 could you work together to flesh this out some more? It can be a spike if we need some digging in and designing on what we want to do here


Create Civiform header

Description
Please explain the changes you made here.
Release notes
The title of the pull request will be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section.
Checklist
General
Read the full guidelines for PRs here

[ ] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[ ] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[ ] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
[ ] Created unit and/or browser tests which fail without the change (if possible)
[ ] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

Database evolutions
Read the guidelines here

[ ] Assigned two reviewers
[ ] Guarded against already existing resources using IF NOT EXISTS and IF EXISTS
[ ] Downs created to undo changes in Ups

User visible changes

[ ] Followed steps to internationalize new strings

[ ] Added context strings to new messages
[ ] Didn't use a message in applicant facing code that isn't translated yet (unless behind a flag)
[ ] Follow the workflow here

[ ] Wrote browser tests using the validateAccessibility method
[ ] Tested on mobile view. See mobile device mode
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/helper/feature-flags.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Instructions for manual testing
If instructions are needed for manual testing by reviewers, include them here.
Issue(s) this completes
Fixes #<issue_number>; Fixes #<issue_number>...

#7478  👈
main

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

Join @greg-hyde and the rest of your teammates on  Graphite

Do we maybe want to only take a screenshot of the question itself for most of these, rather then the whole page?
We can have one test that makes sure the question page in general is has the header but otherwise I don't think screenshotting the header on every question permutation is necessary.

Yeah agreed. I just filed https://github.com/civiform/civiform/issues/7533 to cover that work