[opencv4] Fix build failure when dnn feature is not enabled

Given the following manifest (when dnn feature is not included):
"dependencies": [
  {
    "name": "opencv4",
    "version>=": "4.8.0#18",
    "default-features": false,
    "features": [
      "png"
    ]
  }
]

it failed and here is what vcpkg/buildtrees/opencv4/config-x64-linux-out.log said:
...
CMake Error at /home/peter/open-source/git/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
  Could not find a package configuration file provided by "flatbuffers" with
  any of the following names:

    flatbuffersConfig.cmake
    flatbuffers-config.cmake

  Add the installation prefix of "flatbuffers" to CMAKE_PREFIX_PATH or set
  "flatbuffers_DIR" to a directory containing one of the above files.  If
  "flatbuffers" provides a separate development package or SDK, be sure it
  has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:759 (find_package)
...

This problem is introduced by commit 6d2c9714 contributed by @jimwang118
In the patch vcpkg/ports/opencv4/0023-fix-no-flatbuffers.patch, Jim disabled the procedure of Flatbuffers detection introduced by the previous patch 0017-fix-flatbuffers.patch, which has correctly fixed the flatbuffers-related issues.
...
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -756,7 +756,7 @@ include(cmake/OpenCVFindLibsVideo.cmake)
 include(cmake/OpenCVFindLibsPerf.cmake)
 include(cmake/OpenCVFindLAPACK.cmake)
 include(cmake/OpenCVFindProtobuf.cmake)
-include(cmake/OpenCVDetectFlatbuffers.cmake)
+find_package(flatbuffers CONFIG REQUIRED)
...

In vcpkg/ports/opencv4/vcpkg.json we can see, flatbuffers is only the dependency of feature dnn:
  "dependencies": [
...
    "dnn": {
      "description": "Enable dnn module",
      "dependencies": [
        "flatbuffers",
        {
          "name": "flatbuffers",
          "host": true,
          "default-features": false
        },
        "protobuf"
      ]
    },
...

and when dnn is not enabled, it broke down at the line find_package(flatbuffers CONFIG REQUIRED)
And this change is unnecessary either:
-  list(APPEND libs ocv.3rdparty.flatbuffers)
+  list(APPEND libs flatbuffers::flatbuffers)

Thus, we'd better to revert those changes.

I tested it locally without installing the dnn feature, and the error you mentioned did not occur.
Installation command:
vcpkg install opencv4[core,png]
result:

I tested it locally without installing the dnn feature, and the error you mentioned did not occur. Installation command: vcpkg install opencv4[core,png] result:

port version 15 is no problem. Bug is introduced since port version 16 you committed

I suggest adding constraints to the patch that determine when using dnn to find flatbuffers through the patch. Removing the patch may trigger the original CI error.
...
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -756,7 +756,7 @@ include(cmake/OpenCVFindLibsVideo.cmake)
include(cmake/OpenCVFindLibsPerf.cmake)
include(cmake/OpenCVFindLAPACK.cmake)
include(cmake/OpenCVFindProtobuf.cmake)
-include(cmake/OpenCVDetectFlatbuffers.cmake)
if(BUILD_opencv_dnn)
+find_package(flatbuffers CONFIG REQUIRED)
endif()
...

But I don't think that it's a good way to use find_package(flatbuffers) instead of include(cmake/OpenCVDetectFlatbuffers.cmake) because their script is better to handle with some corner cases.
Eg.
if(BUILD_opencv_dnn)

We shouldn't assume that dnn feature depends on flatbuffers or there is ONLY dnn feature depends on flatbuffers (i.e. if in the future, dnn is not depend on flatbuffers anymore or there is an another feature depends on flatbuffers), it will trigger errors again.

May I have ask why CI failed if we remove the patch? Does it related to something like caches?

I' ve seen that there are some commits removed the patches. It doesn't seem that vcpkg project disallow to remove port's patches

And your patches is the last one applied, remove it will not cause other patches applied failed

And your patches is the last one applied, remove it will not cause other patches applied failed

Ok, I will test it locally and if there are no problems, I will mark it as reviewed.

Compile test pass with following triplets:
x64-windows
x64-windows-static


Make default payload creator ignores synthetic events.

When combining this library with react-redux I noticed a whole bunch of errors in my console when firing lots of events:

The component causing the errors is written as such:
const Counter = ({ increment, decrement, counter }) => (

Counter: {counter}

    <button onClick={increment}>+1</button>
    <button onClick={decrement}>-1</button>

);

One solution is to rewrite the component so the synthetic event from React is not passed to the action creator:
const Counter = ({ increment, decrement, counter }) => (

Counter: {counter}

    <button onClick={() => increment()}>+1</button>
    <button onClick={() => decrement()}>-1</button>

);

This has the potential to violate some linting rules. That's where using something like withHandlers from recompose comes in:
const Counter = ({ increment, decrement, counter }) => (

Counter: {counter}

    <button onClick={increment}>+1</button>
    <button onClick={decrement}>-1</button>

);

// ...

export default compose(
  pure,
  withHandlers({
    increment: props => () => props.increment(),
    decrement: props => () => props.decrement(),
  }),
)(Counter);

But this feels like overkill for what the component is and what it does. This change simply makes the default payload creator return a null payload if it is passed a synthetic event, thus enabling the very first example to be valid.
Thoughts?

@knpwrs While this would make my life easier, I don't like the idea of putting code in checking specifically for the react event system.
My approach lately has been to use the function type of mapDispatchToProps to prevent this issue.
function mapDispatchToProps(dispatch) {
  return {
    increment: () => incement(),
    decrement: () => decrement()
  };
}

Yeah, I understand that you don't want to add react-specific code. Thinking I might just export argumentless actions with a little Ramda magic:
import R from 'ramda';
export const increment = R.nAry(0, createAction('INCREMENT'));
export const decrement = R.nAry(0, createAction('DECREMENT'));
export const add = createAction('ADD');

Then when it comes time to map I can import all actions and map them together:
import * as actions from '../actions/counter';

const mapDispatchToProps = () => actions;

Only the simple (argumentless) actions need to be wrapped in R.nAry(0).

@BerkeleyTrue another idea just came to mind. Another function, e.g., createSimpleAction which just ignores any arguments passed to the payload creator. What do you think of that idea?
While I'm on it, no need for Ramda on the previous example:
export const increment = createSimpleAction('INCREMENT');
export const decrement = createSimpleAction('DECREMENT');
export const add = createAction('ADD');

@knpwrs love your tagline, thanks for the PR

My tagline is pretty awesome isn't it? 😏
If any of the maintainers are interested in a PR for createSimpleAction I can go ahead and make one.

This looks like a userland issue more than a library issue.
There are already several examples of how to go about solving this in this thread, but even more the library itself provides a way to do this without the need of additional API.
const click = createAction('CLICK', () => {});

With Ramda:
const noop = R.always(undefined);
const click = createAction('CLICK', noop);

with Lodash:
const click = createAction('CLICK', _.noop);

Surprised to see Ramda doesn't have a noop. I see that they have a few issues tracked about it. I was going to suggest R.T as well which works as long as a payload of true is acceptable.
const click = createAction('CLICK', R.T);


Added main script to package.json

This allows the module to be required in projects.
I hit my head on the wall on cleaning up my project when I stumbled upon this, I took one hour to realize this simple thing. I hope this could help someone else using this module.

@sunyatasattva thanks for PR, I published new release


Notes for running with Python 3.11

I've been working to get this running with Python 3.11, mostly to check if EsiPy is still functional after recent ESI changes.
I'm creating this issue to leave some notes on what I ran into, to possibly fix with a PR later (if I get it fully working).

PySwagger is incompatible with Python>=3.10 due to an issue with collections.MutableMapping. This small change will resolve that issue: https://github.com/fboerman/pyswagger/commit/52019f41678d3f91f7f8dfc06387e0afd328ae38
as described here: https://github.com/Kyria/EsiPy/issues/64

The database file, app.db, seems to be created in the top level project directory when running flask db upgrade. However, the Flask app is looking for the db in instance/app.db, leading to the following error:
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: user
Moving the created app.db file to the instance directory fixes this.

The login button image link is broken, and can be updated to: https://web.ccpgamescdn.com/eveonlineassets/developers/eve-sso-login-white-small.png

At this point, I'm able to successfully authenticate with the SSO and retrieve my wallet balance, but I get the below error. That's the correct wallet balance, so I'm stopping at this point for now.
esipy.exceptions.APIException: HTTP Error 200: b'2113860735.69'

I got it to work today, you have to drill down to pyswagger/io.py and add the same .abc to both instances of collections on line 391


Express server for the application REST API

Installed express server
Created an endpoint to list users
Added settings file to implement environment's paths on the Front-end side

@rod6214, thank you very much for your contribution and and helping to grow the project. 💪


Fixtypo for BloomfilterTest

Coverage decreased (-0.03%) to 89.957% when pulling 00408690a26587b45f6efc819553c02126b21c25 on dota17:fixtypoForBloomfilterTest into 2cbac58f7e3b51a4f2f3a6672bb4380e18469c50 on apache:master.


Comparison sort (for GPUs)

This adds comparison sort,  sort-by-key, stable sort, stable sort-by-key algorithms. They're all based on counting merge sort. Additionally, for non-stable sorts there is block sort (i.e. sorting subarrays of elements) based on bitonic sorter which uses local memory.
Tests included.
Later this week I'll test stable block sort.
Performance
I couldn't make a working perf_bolt_comparison_sort. I think there's something wrong with Bolt or my installation of Bolt. However, I've manged to make a change inside Bolt library that forces it to use comparison sort in sort().
=== comparison_sort with compute (it's not stable) ===
size,time (ms)
2,0.090120
4,0.100572
8,0.095840
16,0.124584
32,0.253873
64,0.154097
128,0.135110
256,0.161665
512,0.328393
1024,0.421878
2048,0.562983
4096,0.666007
8192,0.826941
16384,0.943715
32768,1.160150
65536,1.135010
131072,1.387090
262144,1.277340
524288,2.092640
1048576,3.362030
2097152,6.242780
4194304,12.996700
8388608,28.479800
16777216,61.555000
33554432,134.799000

=== sort with bolt (forced to use comparison sort, stable) ===
size,time (ms)
2,0.062625
4,0.049883
8,0.053240
16,0.063964
32,0.064557
64,0.059619
128,0.998828
256,1.116950
512,1.208020
1024,1.242320
2048,1.148320
4096,1.205540
8192,1.148740
16384,1.215990
32768,1.295780
65536,1.522320
131072,2.452030
262144,1.685660
524288,2.143900
1048576,3.853150
2097152,8.349480
4194304,17.739800
8388608,38.839500
16777216,83.740300
33554432,182.363000

=== comparison_sort with compute (stable) ===
size,time (ms)
2,0.078412
4,0.093083
8,0.113689
16,0.132868
32,0.625694
64,0.739580
128,0.875305
256,0.968895
512,1.103770
1024,1.185820
2048,1.333790
4096,1.417630
8192,1.587050
16384,1.886840
32768,1.879140
65536,1.955670
131072,2.141840
262144,2.393540
524288,3.265350
1048576,4.328050
2097152,7.674590
4194304,15.662900
8388608,33.965800
16777216,73.278500
33554432,159.330000

Coverage decreased (-0.3%) to 80.579% when pulling 5d31bd0f0797c0fb66b55d12079c6a1ededff7d2 on haahh:pr_comp_sort into 04e7dde2204fb30eb223679ddefe437757a6feb9 on boostorg:develop.

Thanks for implementing this, it's been sorely missing for a long time! And the performance looks great! Awesome work!


Calling destroy method with empty array of ids removes all documents

I have a web server built with sails 0.10.5 + waterline 0.10.26 + sails-mongo 0.10.6.
The case is:
    async.series([
      function (done) {
          Notification.create({
            name: 'test'
          }, done);
      },
      function (done) {
          Notification.destroy({id: []}, done);
      }], _.noop):

I assume the destroy call will do nothing, but it removed the documents created in the first step.
Not sure if this issue happens on the latest release.

Which adapter are you using?

Okay, step one will be to look at the original and parsed criteria used to destroy the records here: https://github.com/balderdashy/sails-mongo/blob/master/lib/collection.js#L268
Does the done callback correctly receive an array of all the records that were destroyed?

Yes, the done callback received all the documents, and the collection is cleared.
And, at https://github.com/balderdashy/sails-mongo/blob/master/lib/collection.js#L254
The criteria argument is {}.

We should cove this in our API tests, somewhere in: waterline-adapter-tests - destroy.js.

A criteria of {} will match all records. We need to add something so that if it comes across an empty IN criteria as the only item to exit the query with no results rather than try and mangle the query.

Added https://github.com/balderdashy/waterline-adapter-tests/commit/00278fcefce0cbbbf07564f178009f03462cd201 to the test suite. I couldn't recreate this in any of the adapters. I'll give it another run through though.

Tested in mongo with the code block above and it kept the records. Calling this one closed.


CERxx renamed into R1SNyyy

As agreed, this big PR changes robot names from CERxx to R1SNyyy, where xx was in {01, 02, 03, 04}, whereas the SN yyy is now in {000, 001, 002, 003}.
To update the robot setup, just follow the main instructions in the README.
@randaz81, I didn't find the GitHub handle of our customer in Rome; you may want to proceed with advertising this on your own then.
cc @vtikha @maggia80 @Fabrizio69 @violadelbono

I am not sure if you want to update https://github.com/robotology/robots-configuration/blob/master/all_robots.xml or not.

Sure @traversaro 👍🏻
I simply forgot about it. Done in the latest push.


CSS class .ReactModal__Body--open isn't added to body

The CSS class .ReactModal__Body--open isn't added to body, so I can't add overflow: hidden to the body in order to prevent scrolling behind the modal.
I'm using version 0.5.0.

+1
In my case
renderPortal: function(props) {
    if (props.isOpen) {
      elementClass(document.body).add('ReactModal__Body--open');
    } else {
      elementClass(document.body).remove('ReactModal__Body--open');
    }

...

props.isOpen switch to false just after it was set to true, so the class is added then removed.

I think it was the second modal issue.

+1 Having this same issue when there is more than modal on the page.

See my comments here: https://github.com/reactjs/react-modal/pull/101#issuecomment-208891959
Two modals at once doesn't really make sense to me.  I could be missing something though.

https://github.com/reactjs/react-modal/issues/173 related issue.

@claydiffrient My usecase for multiple modals on one page is a number of similar components which each have a detail view which should be opened within a modal.  Think of something similar to how the Pinterest interface gives you a detail modal for each item.  Is there an implementation detail that makes supporting this extra difficult?
@goldensunliu pointed out a good work-around in #173 , simply choosing to only render the Modal component when it should be open and otherwise having it be null.  This works, but is less elegant than actually using the isOpen property everywhere.  Any ideas?

@john-osullivan I see the issue now.  It's not multiple modals opened at once, but rather multiple modal components rendered (with only one open at a time).  I think I see the issue with that now.
What I've done in the past in situations like this is to render one modal component and let state (or props) control what is displayed in it.  I'll look into a way we could possibly make this more efficient by sharing a modal portal for each rendered modal.

Until this bug is fixed the easiest workaround I found is to use onAfterOpen callback.
afterOpenModal() {
    document.body.classList.add('ReactModal__Body--open')
  }

<Modal onAfterOpen={this.afterOpenModal}></Modal>

+1

I solved this by adding the following CSS:
.ReactModalPortal {
  position: fixed;
  top: 0;
  left: 0;
  z-index: 1;
}

I got around this issue by setting and unsetting another class on body. This has the property that it'll work for multiple opened modals as long as you're using different class names for each modal.
afterOpenModal() {
  document.body.classList.add('ReactModal-open')
}
onRequestCancel() {
  document.body.classList.remove('ReactModal-open')
}
<Modal onAfterOpen={this.afterOpenModal} onRequestCancel={this.onRequestCancel}></Modal>

.ReactModal-open {
  overflow: hidden;
}

1.6.5+ should have a fix for this issue. Please, reopen this issue if necessary.

@diasbruno Does this mean that > 1.6.5 will have the fix, or that currently 1.6.5 and above has the fix? I updated the package and doesn't seem to have any effect. Perhaps there is a specific implementation required?

@boonier 1.6.5 and above.

Thanks @diasbruno. I can't however seem to get it to work how I need it to, so I'm doing a workaround for now. The closing modal needs to consider if there are other modals already in the DOM, and only remove the class if it is the last.

@boonier oh yeah, see #326. it will fix the case where many modals were opened.


Ign-delays referenced before assignment

This model works with the Burcat ChemKED files, however does not work for other ChemKED files I try to use individually such as data from Davidson, Hartmann, Mittal and Sung, and Shen.  All of them are validated with ChemKED 0.4.1. The error says " 'ign-delays' referenced before assignment".
test_performance_toluene_onefile.zip

When running PyTeCK v0.2.5a5 with a ChemKED file that has an ignition delay definition of "d/dt max extrapolated" I get this error message: "pint.errors.DimensionalityError: Cannot convert from 'second' to 'dimensionless' ". This would be with the Davidson files and Shen files. @kyleniemeyer

Got it. I will work on fixing this.

@morganmayer can you let me know which line(s) it says this error occurred at?

Getting this error message, even after the recent fixes:
.../site-packages/pyteck/eval_model.py:169: RuntimeWarning: Warning: multiple changing variables. Using temperature.
  RuntimeWarning
Traceback (most recent call last):
  File "test_performance.py", line 40, in <module>
    skip_validation=True
  File ".../site-packages/pyteck/eval_model.py", line 375, in evaluate_model
    sim.process_results()
  File ".../site-packages/pyteck/simulation.py", line 502, in process_results
    if len(ign_delays) > 0:
UnboundLocalError: local variable 'ign_delays' referenced before assignment

Correction, it seems this was actually fixed with the recent changes.


[Proposal] Exclude certain phrases from being processed

Screenshot:

It will be great if we can exclude words/phrases (like roman numbers, the word and, or, of etc.)

I fixed this issue in my custom fork.


AudixFix updates

Description
Checking in results of npm audit fix for release/20.10
Microsoft Reviewers: Open in CodeFlow

@almedina-ms and @dclaux ran into errors while running these commands. Did you also see them @shalinijoshi19 ?
Screenshot from David:

No. No such errors - What was the version of npm and Node he was running again? I've pasted mine (including the updated version that I was prompted to get as I ran npm install)

Interestingly my local npm builds are succeeding but build server ones failing -- requeued to see if it's a quirk


What environment was this developed under?

Can you briefly describe the NVIDIA toolkit version, GPU card model, etc. that was used during initial development?
I'm trying to stand-up a development system to compile and compare half a dozen published GPU-based 3SAT approaches.
My two hardware contexts are  GT 710 and  GTX 1070, running within Fedora with NVidia Driver 410.xx and Toolkit 10.x
This code compiles with minor warnings, but upon running the following occurs (paraphrased):
cudaCheckError() failed at ./solver_cuda.cu:1029 invalid configuration argument

Hi! Thanks for your interest in my work.
The latest version of CUDA that was used during Ringsat development was 8.0. However, this problem you have with cudaCheckError() is really a problem of an old error checking script copy-pasted since CUDA 2.0 or even earlier times. You could just comment out the offending line: https://github.com/ichorid/ringsat/blob/b0ffbcc112d0213c746e44c0a2023965af3e2c5c/solver_cuda.cu#L1029
and it should work fine then (except you lose the error handling).
If you're doing a survey of GPU-based SAT solvers, you could be also interested in my paper
describing the reasons why DPLL-based solvers can't run efficiently on modern GPUs. It is written in Russian, but the abstract is in English, and if you don't want to mess around with Google translator, I can tell you the most important points.
If you want to cite Ringsat, you could use the abovementioned paper, or the original conference paper.
There is one important thing about SAT-solvers that run BCP procedure on GPU. Their performance really suffers from irregularity of SAT problem, because SIMD architecture is bad at dealing with execution process irregularities, and GPU memory controllers are optimized for coalesced, not random reads. Thus, GPU-based solvers always lose to CPU-based ones in solving generic problems, but really shine in some synthetic tests. One example of these synthetic tests that Ringsat solve really fast is the DUBOIS suite from SATLIB benchmark collection.


Capability to configure timeouts

Before first using HttpClientManager.getHttpAsyncClient() there is capability to set operation timeouts.
The timeout in milliseconds used when requesting a connection from the connection manager.
HttpClientManager.setConnectionRequestTimeout()
The timeout in milliseconds until a connection is established.
HttpClientManager.setConnectTimeout()
The socket timeout in milliseconds, which is the timeout for waiting for data or,
put differently, a maximum period inactivity between two consecutive data packets.
HttpClientManager.setSocketTimeout()

There are two approaches.
One way is to force user to do a lot of additional steps via setHttpAsyncClient.
Second way is to allow user to do some small changes via setting timeouts.
I prefer second way.

There are two approaches.
One way is to force user to do a lot of additional steps via setHttpAsyncClient.
Second way is to allow user to do some small changes via setting timeouts.
I prefer second way.

Yes, let's do that and there is no need to make them do any additional steps via setHttpAsyncClient.


[Helios] Clear current frame after stop is called

Currently when you use a Helios device, after you call the stop() method on it, the last sent frame will still be visible on the laser. Instead, it should clear this frame.

Not sure if related, but when using the Python API, when I send empty frames it also keeps the previous ones
Can't find a way to clear it either

Thanks, that's interesting! At the moment I don't clear the frames at all when calling stop, so I'm curious if I'm going to be having the same issue.

Calling HeliosLib.SetShutter(dacNum, false) when closing seems to work (fixed this a while ago already).


Update Rust to 1.76.0

Release notes.

Adding run-extra-build-macos label as per https://github.com/neondatabase/neon/pull/6285#issuecomment-1882422122

CI job to update the tag as per https://github.com/neondatabase/neon/pull/6222#issuecomment-1866674925: https://github.com/neondatabase/neon/actions/runs/7901922918


Titan doesn't seem to work on Centos

When I install Titan and try to start it: titan-edge daemon start --init --url https://test-locator.titannet.io:5000/rpc/v0
output：
2024-03-14T20:12:37.876+0800	INFO	main	titan-edge/main.go:156	Starting titan edge node
2024-03-14T20:12:42.967+0800	ERROR	main	titan-edge/main.go:106	RPC client error: sendRequest failed: Post "https://test-locator.titannet.io:5000/rpc/v0": INTERNAL_ERROR (local): write udp [::]:38048-><IP_ADDRESS>:5000: sendmsg: invalid argument

I tested that this phenomenon does not appear on Ubuntu, but only on Centos (mine is 7.9).

50% of the time it's a network issue.
50% chance it is a bug in the code, we will try to fix it in the next update.

export QUIC_GO_DISABLE_ECN=true

Setting the environment variable QUIC_GO_DISABLE_ECN=true will solve this problem on linux:
export QUIC_GO_DISABLE_ECN=true

Setting the environment variable QUIC_GO_DISABLE_ECN=true will solve this problem.
on linux:
export QUIC_GO_DISABLE_ECN=true

Setting the environment variable QUIC_GO_DISABLE_ECN=true will solve this problem. on linux: export QUIC_GO_DISABLE_ECN=true

Thanks sir, it solved my problem!

have you fix this bug now? it also appear at my machine.

have you fix this bug now? it also appear at my machine.

You can follow this:

have you fix this bug now? it also appear at my machine.

https://github.com/Titannet-dao/titan-node/issues/21#issuecomment-2003281047


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


10.0 pos ms renamings

@KolushovAlexandr did you run external tests after renaming? Could  you make a PR with renamings only?

@yelizariev external tests passed, PR with renamings only https://github.com/it-projects-llc/pos-addons/pull/720

merged in #720


feat: firecracker-host-config

This adds the host firecracker config which has been migrated from https://github.com/systeminit/si-firecracker-config which was used during development. As it turned out we should version these files alongside the codebase as they are directly used and are compatible with the rust of the same version. It's very likely that versions of these files will be compatible on multiple versions of the rust, but keeping these things together makes things easier to track/change in one single PR.
All of this code is "dead" i.e. no functional changes to anything existing in the codebase & can safely be assumed to not cause any regressions or otherwise. Sister PR to https://github.com/systeminit/si/pull/2969 but has no direct dependency on it.
Explanation of the files below:

component/firecracker-base/machine-userdata.sh: The userdata wrapper script which clones from git used to provision a new machine to be "firecracker execution" compatible.
component/firecracker-base/orchestrate-install.sh: The script that's called from the userdata above to then pull in the relevant artifacts from S3 and make other dependent changes on the host.
component/firecracker-base/default-variables.txt: A variables file that can be used to drive the install orchestration. Set to defaults for now but can be leveraged in the future for custom installs/OS dependent changes.
component/firecracker-base/start.sh: The "start" file which is called directly in deadpool cylcone to create a new executor
component/firecracker-base/start.sh: The "stop" file which is called directly in deadpool cylcone to stop an existing executor and tidy up the filesystem

bors merge


pwwMap is better than leveldb

http://sourceforge.net/projects/pwwhashmap/?source=navbar

no software is ever better than another software. if you want to be helpful you could highlight in which way pwwhashmap is superior and spark a healthy discussion. however i'm quite confident leveldb's architecture is here to stay for a long time.

Mark :)

think your advise


redpanda: don't set cluster config values in redpanda.yaml

Prior to this commit, cluster config values were being set in redpanda.yaml. This was being done as a historical artifact of redpanda <= 22.1 1.
While doing so is largely benign it clutters the, already quite busy, redpanda.yaml and can result in unnecessary restarts when only changing cluster configurations.
This commit:

Removes cluster configurations from redpanda.yaml
Updates the config hash on the StatefulSet to only be computed from redpanda.yaml. This allows users to update cluster configurations from the chart without initiating a rolling restart.

Fixes #1345

The error in test case 99
helm install redpanda-fi5sxqqswg charts/redpanda --namespace redpanda-fi5sxqqswg --wait --values charts/redpanda/ci/99-none-existent-config-options-with-empty-values.yaml --timeout 600s --set=image.tag=

comes from s3 accessibility in new version of Redpanda.
2024-09-13T21:15:50.5543062Z ERROR 2024-09-13 21:13:10,462 [shard 0:main] s3 - s3_client.cc:618 - Couldn't reach S3 storage with either path style or virtual_host style requests.
2024-09-13T21:15:50.5544601Z ERROR 2024-09-13 21:13:10,462 [shard 0:main] client_pool - client_pool.cc:79 - Self configuration of the cloud storage client failed. This indicates a misconfiguration of Redpanda. Aborting start-up ...
2024-09-13T21:15:50.5545826Z INFO  2024-09-13 21:13:10,462 [shard 0:main] main - application.cc:466 - Stopping...

https://github.com/redpanda-data/helm-charts/actions/runs/10855662859/job/30128727897?pr=1524#step:16:38828

In values.go I see TieredStorageConfig.CloudStorageCacheDirectory, but wasn't sure where it's used. It's node config, along with cloud_storage_inventory_hash_path_directory. Most of the rest of TieredStorageConfig is cluster config, from what I can see.

I would drop tests with tiered storage. If we need that validation we could resurrect buildkite tests. Maybe not with chart testing.

I think a test case with minio might be the best bet as that'll have fewer moving parts and should provide the same degree of coverage. WDYT?

In values.go I see TieredStorageConfig.CloudStorageCacheDirectory, but wasn't sure where it's used. It's node config, along with cloud_storage_inventory_hash_path_directory. Most of the rest of TieredStorageConfig is cluster config, from what I can see.

Ah, that's interesting. A quick search didn't show anything in the docs. Are those settings publicly documented anywhere? The tiered.config struct is certainly going to be the most attractive to end users to set those settings given that it follows the naming of cloud_storage_*. It might be worth explicitly rejecting those from tiered.config via JSON schema.

I think a test case with minio might be the best bet as that'll have fewer moving parts and should provide the same degree of coverage. WDYT?

That would be great. But I would think it is additional work that might take you some time.

That would be great. But I would think it is additional work that might take you some time.

I was going to file an issue to do that later on and remove the current test 😅


protobuf: introduce new upstream versioning scheme

Description of changes

python310Packages.protobuf3: use dedicated package definition
python310Packages.protobuf3 is a legacy package with original versioning scheme. It's easier to mantain such a legacy dedicated package definition.
protobuf_{21,23,24}: init at 21.12, 23.4, 24.3
protobuf3_{21,23,24} will be kept as-is for compatibility. There will no new packages with protobuf3_ prefix. When they become outdated we can remove them.
To avoid massive rebuilds, protobuf is kept to pointing to protobuf3_24 right now.  A follow-up PR will use protobuf_24.
Future versions of protobuf will use the protobuf_<majar version> pattern.
python310Packages.protobuf: use pkgs.protobuf_24

Refactor pkgs/development/python-modules/protobuf/default.nix to use new versioning scheme.
Pin protobuf to new protobuf_24 package
protobuf still points to protobuf3_24. A follow-up PR will undo this action with protobuf pointing to protobuf_24.

On master for testing, will go to staging when ready.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

At least one alias was not converted: https://github.com/NixOS/nixpkgs/pull/262227

There's a eval failure
pkgsCross.aarch64-multiplatform.protobuf_24`

error: attribute 'protobuf24_4' missing

       at /home/artturin/nixgits/my-nixpkgs/pkgs/development/libraries/protobuf/generic.nix:60:7:

           59|       # re-use the executable generated as part of the build
           60|       buildPackages."protobuf${protobufVersion}"
             |       ^
           61|     ];

Fixed in https://github.com/NixOS/nixpkgs/pull/263264.


Fix removal of selected options if available options has zero length.

When this commit is applied, it is possible to remove all selected options and options from a multiselect and all labels will be removed from the mutliselect. This fixes the problem, that the labels are still being shown, if options and selected options are empty. This would fix #70

Thanks for this!


problem with main package class

i have this issue when i type pub get commend run the debug
The plugin google_gemini doesn't have a main class defined in /home/raghdkun/.pub-cache/hosted/pub.dev/google_gemini-0.0.3/android/src/main/java/com/wexende/google_gemini/GoogleGeminiPlugin.java or /home/raghdkun/.pub-cache/hosted/pub.dev/google_gemini-0.0.3/android/src/main/kotlin/com/wexende/google_gemini/GoogleGeminiPlugin.kt. This is likely to due to an incorrect androidPackage: com.wexende.google_gemini or mainClass entry in the plugin's pubspec.yaml.
If you are the author of this plugin, fix the androidPackage entry or move the main class to any of locations used above. Otherwise, please contact the author of this plugin and consider using a different plugin in the meanwhile.

I've got the same issue. Have you found a fix yet?

Hi, I just fixed the issue on version 0.0.6.
checkout  👈🏼

hello guys i fix it by running a vpn with good internet connection


Add yabai & hyprland rice

Very consistent rices @command-z-z !
Do the arrows in the bar collapse and expand? Was always wondering if waybar had such a feature.

Very consistent rices @command-z-z ! Do the arrows in the bar collapse and expand? Was always wondering if waybar had such a feature.

In fact, this is just an icon, it may be possible to customize it：）


Improve Materialiser cache and its GC mechanism

Current Implementation:
The are two per-key caches:
an operation cache where the most recent operations are stored, and
a snapshot cache which stores the latest materialised views (snapshots) of a  CRDT.
When the materialiser receives an operation, it stores in its operation cache. When it receives a read request, it checks whether there are suitable materialized views available in the snapshot cache and whether there are operations to be applied in the operation cache. If so, it materializes a new version of the CRDT that satisfies the request by applying the potentially missing operations to the corresponding snapshot, thus creating a new snapshot. In the event that cached snapshots or operations exist for a requested key, but none satisfying the read request parameters (i.e. snapshot time), the materialiser replies with an {error, no_snapshot} message.
GC
As there are object views (snapshots) and operations, the growing number of any of them needs to trigger the GC mechanism.

Snapshot (or read-triggered) GC:
In case the number of snapshots stored for a key grows up to a value “snapshot_threshold”, keep just the latest “snapshot_min” snapshots. Proposed initial values (for no particular reason) are 10 and 2 respectively. Note that the snapshot generation is done on reads, that’s why this mechanism is triggered only on reads.
Operation (or write triggered) GC:
In case the number of update operations stored for a key grows up to a number “ops_threshold”, keep just the latest “ops_min” operations by creating a snapshot of the object applying and then removing the oldest ops_threshold-ops_min ops. Proposed an initial values (for no particular reason are 50 and 5 respectively). Note that the snapshot generation could possibly trigger the Snapshot GC mechanism.

Please contribute to the following with your ideas:
Future
Caching
The idea is to generate some policies to define how each key will be cached, depending on its type or maybe its size. It might be even possible to change policy dynamically, e.g., according to an element’s size. The goal is to achieve a more efficient handling of the cache, in both terms of size and speed on handling requests.
There should be an implementation of the materialiser read and update functions for each policy.
NoOps: for an object cached respecting this policy, there will be no operations stored, only snapshots. This policy could be particularly handy for CRDTs which state is small compared to the size of an operation: e.g. counters, where the cost in terms of size of storing the value (a snapshot) is similar to storing the operation. In this case, for each update, a snapshot should be created. On read, the snapshots would be ready to serve requests. This would improve both size and read time for counter/like CRDTs.
DeltaCheckpoints: in the snapshot cache, there will be full snapshots and deltas (from those snapshots). There have to be parameters like how many full snapshots and how many “delta snapshots” are stored. This could be useful for big sets.
Ops&Snaps: the current implementation.
GC
Also, the idea here is to implement GC policies. The following are possible ideas:
NumberLimit: the current implementation. If the number of snapshots or operations in the cache for a given key grows to a certain threshold, perform GC.
CacheSize: when the overall cache reaches a memory limit, trigger GC.
TimeBased: perform GC every certain period of time.
ActiveSnapshot: all partitions should periodically exchange the latest snapshot time an active tx took and exchange it. That way, a partition can GC all state which is older than the ActiveSnapshot. In order to implement this, we should have an efficient broadcast mechanism. Could this possibly be piggybacked with group membership information in riak_core?

For information I did some tests on antidote to see the impact of the materialiser, all experiments are done using counter CRDT types, 2000 keys, single operation transactions either performing a read or an update:

This first benchmark is single DC, eight antidote machines, and two workload generation machines each running 80 client threads.  Average latencies for reads are around 1 - 2 ms, updates around 3 - 4 ms

This second benchmark is the same as the previous, except without the materialiser.  By "without the materialiser" I mean that no list of versioned snapshots are created and no lists of updates are calculated and kept in memory.  So it is more like a single version database.  Everything else is the same, all updates are still logged, all messages sent, locks, etc...  What we see here is just a small increase in performance, so it seems like the materialiser is doing a good job, and since it is single DC, likely most the time we are just dealing with the most recent snapshot (i.e. we are not really using the multi-versioning anyway).

This graph show what happens when we increase the number of DCs to 3.  So each update is replicated 3 times, there is a total of 24 antidote machines (8 per DC) and 6 workload generation machines (2 per DC).  What we see here is a huge performance drop as soon as we increase the update rate.  Average read latencies go up to around 5 - 10 ms, updates between 10 - 100.  In the 99% update workload we see around 5000 ops/sec.

This is the same 3 DC test as above except without the materialiser.  Again we are still doing the same amount of logging, network traffic, locks, etc.. We are just avoiding the multi versioning and materialisation.  Maybe the first thing to notice is that Antidote scales more as expected, we get 3x increased read throughput vs the single DC and around 2x write throughput (since each update is replicated 3x we are actually performing 6x more work, but most of it asynchronous).  Average latencies for reads are around 1 - 2 ms, updates around 3 - 4 ms.
So then the question is, is why does the materialiser work well for 1 DC and so poorly for 3 DCs?  Well it appears to be the tradeoff of multi versioning and staleness. In the 1 DC case, we are pretty much always operating on the latest version of the object, as our snapshot is based on our local physical clock.  With multiple DCs we are accessing older versions based on the stable time which can vary from node to node and are using a vector clock to find and calculate the version (i.e. there could be a large number of versions).  This still shouldn't account for a 20x difference in performance, so I plan to look deeper into the issue (how many snapshots we are creating, do we go to the log etc..), but I see two possible issues, first we risk over-engenieering trying to choose the proper cache size for the number of DCs/update rate, and second that there isn't really much support in Erlang for these kind of shared data structures that these multi-version objects really want to be.

Tyler, thanks for the extensive testing, I know how hard it is, and how essential.
See comment below.

Le 2 déc. 2015 à 15h42, tcrain<EMAIL_ADDRESS>a écrit :
[…]
So then the question is, is why does the materialiser work well for 1 DC and so poorly for 3 DCs? Well it appears to be the tradeoff of multi versioning and staleness. In the 1 DC case, we are pretty much always operating on the latest version of the object, as our snapshot is based on our local physical clock. With multiple DCs we are accessing older versions based on the stable time which can vary from node to node and are using a vector clock to find and calculate the version (i.e. there could be a large number of versions). This still shouldn't account for a 20x difference in performance, so I plan to look deeper into the issue (how many snapshots we are creating, do we go to the log etc..), but I see two possible issues, first we risk over-engenieering trying to choose the proper cache size for the number of DCs/update rate, and second that there isn't really much support in Erlang for these kind of shared data structures that these multi-version objects really wa!  nt to be.

If I follow you correctly, the materialiser is trying to compute eagerly lots of versions without knowing whether they will be ever useful.
The concept of materialiser is to serve as a cache.  It is always possible to compute any value from the log.  So for me the materialiser should be lazy and compute a materialised version only when necessary, i.e., when a client requests it.
If it turns out that this approach adds too much latency, it is always possible to add some kind of more pro-active daemon, but it should not be wired into the materialiser.
Isn’t this what Santiago is working on?
				Marc

I guess at this point I haven't investigated closely enough to tell exactly what is taking the most time, so the eagerness/laziness of generating snapshot it definitely something we need to look at.
The way it is implemented now is that within a local DC we always read before performing an update (to generate the downstream [but of course this is not necessary for all CRDT types]).  So local updates do generate a snapshot.
Differently when updates arrive that are propagated from other DCs, no snapshot is generated.  These are only used in a snapshot when a new update or read is performed locally.  So I guess it is working in the way you imagine, i.e. only snapshots that are needed are generated (but this could be optimised for certain objects).
I guess I was more eluding to the point that even if we are only creating useful snapshots, we still have to create lots of them and do a lot of work to do it.  So the first thing I was trying to say is that this is a problem and that we have to solve it, and it is an overhead that we have to pay compared to a database that uses simpler versioning.  And the second part is that in my mind the solution to this problem is much more adapted to be solved using shared memory.  I don't think this is a fault of erlang, but more that what we are doing is sandwiching the functional/message passing part of erlang between two shared memory abstractions.  On the bottom we have the shared memory abstraction provided by the hardware and on the top we have this multi-versioned CRDT key-value store which seems to have a lot of likeness with the hardware below [this is only for the materialiser and parts surrounding it, I think erlang works great for the rest of the protocol].
So it would seem nice to perform all this logging and object generation and multi versioning together closer to the hardware, especially if we end up using something like leveldb where we have to pay the price of going back and fourth from the erlang vm anyway.  Santiago is sort of working on this, but he was more looking at the structures on disk, but yes since the disk and memory will be somehow projections of each other we should solve these problems together.

Tyler, you are doing indeed an awesome and difficult job here - thank you very much!

Differently when updates arrive that are propagated from other DCs, no snapshot is generated. These are only used in a snapshot when a new update or read is performed locally. So I guess it is working in the way you imagine, i.e. only snapshots that are needed are generated (but this could be optimised for certain objects).

We had discussed this issue previously (in May):
The snapshot generation and update caching should be done type-specific, i.e. sets should not generate snapshots with every add since this uses a lot of space (and time), or counters should be able to apply blind updates.

I guess I was more eluding to the point that even if we are only creating useful snapshots, we still have to create lots of them and do a lot of work to do it. So the first thing I was trying to say is that this is a problem and that we have to solve it, and it is an overhead that we have to pay compared to a database that uses simpler versioning. And the second part is that in my mind the solution to this problem is much more adapted to be solved using shared memory. I don't think this is a fault of erlang, but more that what we are doing is sandwiching the functional/message passing part of erlang between two shared memory abstractions. On the bottom we have the shared memory abstraction provided by the hardware and on the top we have this multi-versioned CRDT key-value store which seems to have a lot of likeness with the hardware below [this is only for the materialiser and parts surrounding it, I think erlang works great for the rest of the protocol].

I tend to not agree.
Referential transparency is not expensive per se. Usually the overhead stems from the garbage collection that it requires.
I don’t know specifically for Erlang, but Haskell uses under the hood in the performance critical libraries several optimizations such as in place updates, sharing of values etc.
I wouldn’t be surprised if this is also true for Erlang’s core parts (which are implemented in C…).

So it would seem nice to perform all this logging and object generation and multi versioning together closer to the hardware, especially if we end up using something like leveldb where we have to pay the price of going back and fourth from the erlang vm anyway. Santiago is sort of working on this, but he was more looking at the structures on disk, but yes since the disk and memory will be somehow projections of each other we should solve these problems together.

I would strongly advise against coupling the materializer and the logging too closely.
We will end up with an unmaintainable chunk of code that will have bugs that would be very hard to locate, introduce bottlenecks and issues due to synchronization etc.
Any other opinions?
Annette

I agree with Annette on the importance of separating mechanism and policy.
I just had a conversation with Tyler.  My advice: (1) make sure to identify the source of the bottleneck before trying to fix it -- currently we have a hypothesis but not enough evidence.  (2) Rewriting the materialiser in C and interfacing it properly with Erlang is likely to be a manpower sink, so some kind of a cost/benefit thinking is appropriate.  (3) Consider some simple fixes first: will a per-client or per-server Zipfian distribution help (likely yes, since the materialiser will not need to incorporate as many foreign updates)?  How about batching and centralising the computation of the foreign part of the stable snapshot, i.e. separating read-my-writes (high priority) from foreign ones (tunable priority)?
								Marc

Le 3 déc. 2015 à 10:28, Annette Bieniusa<EMAIL_ADDRESS>a écrit :
Tyler, you are doing indeed an awesome and difficult job here - thank you very much!

Differently when updates arrive that are propagated from other DCs, no snapshot is generated. These are only used in a snapshot when a new update or read is performed locally. So I guess it is working in the way you imagine, i.e. only snapshots that are needed are generated (but this could be optimised for certain objects).

We had discussed this issue previously (in May):
The snapshot generation and update caching should be done type-specific, i.e. sets should not generate snapshots with every add since this uses a lot of space (and time), or counters should be able to apply blind updates.

I guess I was more eluding to the point that even if we are only creating useful snapshots, we still have to create lots of them and do a lot of work to do it. So the first thing I was trying to say is that this is a problem and that we have to solve it, and it is an overhead that we have to pay compared to a database that uses simpler versioning. And the second part is that in my mind the solution to this problem is much more adapted to be solved using shared memory. I don't think this is a fault of erlang, but more that what we are doing is sandwiching the functional/message passing part of erlang between two shared memory abstractions. On the bottom we have the shared memory abstraction provided by the hardware and on the top we have this multi-versioned CRDT key-value store which seems to have a lot of likeness with the hardware below [this is only for the materialiser and parts surrounding it, I think erlang works great for the rest of the protocol].

I tend to not agree.
Referential transparency is not expensive per se. Usually the overhead stems from the garbage collection that it requires.
I don’t know specifically for Erlang, but Haskell uses under the hood in the performance critical libraries several optimizations such as in place updates, sharing of values etc.
I wouldn’t be surprised if this is also true for Erlang’s core parts (which are implemented in C…).

So it would seem nice to perform all this logging and object generation and multi versioning together closer to the hardware, especially if we end up using something like leveldb where we have to pay the price of going back and fourth from the erlang vm anyway. Santiago is sort of working on this, but he was more looking at the structures on disk, but yes since the disk and memory will be somehow projections of each other we should solve these problems together.

I would strongly advise against coupling the materializer and the logging too closely.
We will end up with an unmaintainable chunk of code that will have bugs that would be very hard to locate, introduce bottlenecks and issues due to synchronization etc.
Any other opinions?
Annette
—
Reply to this email directly or view it on GitHub https://github.com/SyncFree/antidote/issues/83#issuecomment-161565420.

As anyone who has worked with native functions in Erlang knows, re-writing in C could cause more harm than good if you don't know how to do it properly.  NIFs are incredibly difficult to get right: you must call into the scheduler and record reduction counts properly, otherwise the preemptive scheduler will unfairly balance your native code vs. your Erlang code.

@tcrain did these measurements take place before your changes to the materializer?
I believe PhysiCS might be the "antidote" to this problem.


Made changes in Turkish local for Comments, Ghost and Portal

Dear Ghost team,
Hope you're well.
While developing our website https://fayn.press (we just launched it), we came across a few English-Turkish translations that needed correction.
Following the guide you shared with me, I made the corrections & changes using Github and am now submitting it.
I changed "Sign in": "Kayıt ol", to "Sign in": "Giriş Yap", as the current translation is wrong. Kayit ol means Sign up, as opposed to sign in. It's been confusing for our paying members to receive an email that says "sign up" in Turkish (Kayit ol) right after they sign up for the site by paying. We'd greatly appreciate it if this could be fixed as soon as possible.
Other suggestions are mostly improvements in translations that sound more natural in Turkish.
I went through all translations and other than these, they are all good.
Thank you,
Oktay

@soktaykilic Thanks for the contribution! 🙂


okhttp supports custom protocols. gh-809

hello @OlgaMaciaszek , Complete the OkHttpClient custom protocol, but Client.Default and ApacheHttp5Client do not support http2.

@galaxy-sea I see there are some test failures that I would not expect as a result of your PR. Can you first merge changes from origin/main into your PR to get the updated artifact versions? If it still fails then, will take a closer look.

@galaxy-sea I see there are some test failures that I would not expect as a result of your PR. Can you first merge changes from origin/main into your PR to get the updated artifact versions? If it still fails then, will take a closer look.

I submit

Ok, @galaxy-sea - I'll take a look at it on Monday.

Hi, @galaxy-sea, this is happening because the Protocol class has been compiled without - parameters, which is necessary for AOT processing of the properties file. I have modified it to use Strings instead. Merged within gh-825. Thanks for your work on this issue @galaxy-sea.


Improve alby fee reserve calculation

Related to https://github.com/getAlby/nostr-wallet-connect-next/pull/130 which uses a hardcoded 1000 sat amount.
This might not be enough to open a larger channel? the max outgoing payment of 1M sats * 0.8% + routing fees could be over 8000 sats.

fixed by now doing multiple withdrawals to migrate all shared funds to alby hub


PWA-2915: Added Tailwind CSS configuration and theming documentation

Description
This PR adds documentation for configuring and customizing Tailwind and Venia themes.
Staged Preview
https://developer-stage.adobe.com/commerce/pwa-studio/guides/theming
Related Issue
PWA-2915
Motivation and Context
Provide docs for existing Tailwind CSS theming in PWA Studio.
How Has This Been Tested?
Created a PWA Studio app from the create-pwa CLI and applied the examples to it to see the expected results.
Screenshots (if appropriate):
Types of changes

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

I think it's premature to change the theme.

I agree. This was a test that I should have mentioned in the PR description. Until this, I've never tried applying an npm dependency on the commerce-theme outside the project's internal example project. This was part of that testing (via the GitHub staging build workflow) to see the results. And the results proved that the existing setup (for version 0.0.2) needs some adjustments. I'll make sure it's set back to normal.

@keharper They look good to me. Thanks.


Add viewBox to all SVGs

Hello,
This is an attempt to get viewBox added to the legacy SVG icons which did not have them (such as color/btc.svg).
Followup to https://github.com/spothq/cryptocurrency-icons/pull/275
Without modifying any attribute order. It was done using the tool suggested in the above PR (https://github.com/guylando/svgo-addViewBox/blob/master/addViewBox.js)

I have a follow-up to this that I'd like to ask.
I am looking to hopefully use the white icons and override their path fill color. I have this working using the following library: https://github.com/kristerkari/react-native-svg-transformer
However, for this to work I have to also remove the following prop from the "white" SVGs: fill-rule="evenodd"
By doing this, I am able to change the WHITE BTC Svg to look coral as seen here:

I am not super well versed in SVG so do not know the implications of having this fill-rule vs not having it.

@jack-fin hello. Removing evenodd reverts the SVG fill rule to the default nonzero. This can lead to a misconception of what is inside or outside the shape during drawing. evenodd always alternates between inside and outside, whereas nonzero (as it name stands) will fill if the paths intersection winding order is non-zero.
The majority of the icons were made using Sketch set operations, and I do not know whether or not it alternates between clockwise/counter-clockwise paths. If yes, it would mean the fill mode can either be evenodd or nonzero without altering the render, and we could proceed.
Why did you need to remove evenodd? What happens when you try to draw with viewBox and evenodd mode? Is the issue react-native-svg is not compatible with evenodd? If yes I think we should check with the corresponding development team why it is the case, as fill-rule is not something exotic but exists in the W3C recommendations (see https://www.w3.org/TR/SVG11/painting.html from 2011).
Thank you for your efforts — waiting for your input on this.

@tommdn Thanks for the explanation of evenodd that makes sense!
I can look into why the color override was not working for me in react-native, its very possible its a user error on my end. I think outside of that though, I was hoping to merge this PR to add the viewBox to the older .svg files.
Thank you!

@jack-fin You're welcome. Please keep me informed.
Of course regarding adding viewBox to older icons. I'll take a look at it.

Appreciate it, I believe that is all this PR should do,

@tommdn - even I have been using this icons and saw viewBox missing in several icons. Let me know if there is anything I can help you with.

@jack-fin Hello. This should now be present on all icons. Please let me know if there are any issues.


toggle-sort does not seem to do anything

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
I am not sure if the toggle-sort action is broken.  I am launching fzf like this, and CTRL-R does not sort the finder:
FZF_DEFAULT_COMMAND="echo -e 'c\na\nb'" fzf --height=5 --bind=ctrl-r:toggle-sort

$ fzf --version
0.29.0 (dc975e8)

It's working as expected, try this:
seq 1000 | fzf --height=5 --bind=ctrl-r:toggle-sort --query 5

I had completely misunderstood this option.  I thought this option sorted the entries in the finder, whereas, in reality, it sorts the filtered list.
Thank you for clarifying.

Yes,  toggle-sort only works under the condition query string is not empty and match some item

Yes, toggle-sort only works [if the] query string is not empty

Is there a way to sort the original list with a keybind? Wouldn't it make sense for toggle-sort to live-sort the currently shown list in all circumstances?

Is there a way to sort the original list with a keybind?

One idea would be using the {+f} placeholder, which is a temporary filename of the currently selected lines. These lines are then sorted, and the entire list is reloaded.
fzf --multi --bind 'ctrl-t:select-all+reload:sort --ignore-case {+f}'

If you want this sorting to occur every time you start fzf, consider using a start EVENT instead of a KEYBINDING. The fzf manpage explains it well.
man fzf | less --pattern 'AVAILABLE EVENTS'
# AVAILABLE EVENTS:
#       start
#             Triggered only once when fzf finder starts. Since  fzf  consumes
#             the input stream asynchronously, the input list is not available
#             unless you use --sync.

fzf  --multi --sync --bind 'start:select-all+reload:sort --ignore-case {+f}'

But if you do use an event, you could simply assign your FZF_DEFAULT_COMMAND to find your items
and sort them before they are ever seen by fzf. However, this might slow you down on large lists.
export FZF_DEFAULT_COMMAND='fd -tf -HL | sort --ignore-case'


⚠ ClamAV has degraded performance

In 3be9de8, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 171 ms

Resolved: ClamAV performance has improved in ce69721.


Clarification on stopBehaviour.REAL_BOARDING_ALIGHTING enum value

Hello,
I just have a question on the field mentioned in the title. I'm currently implementing intermediate stops on TimedLegs and was wondering if this was the intended parameter choice over the field TripContentFiller.IncludeIntermediateStops available on the OJP spec.
https://github.com/UnionInternationalCheminsdeFer/OSDM/blob/27f9e64b518bb5c0d469e3d37d3c51728a39eaf1/specification/v3.2/OSDM-online-api-v3.2.0.yml#L408
Thanks,
Harry

Note: rail / bus border points to indicate border crossing are not virtual points. Virtual points are used for international fares.
Yes, it maps to TripContentFiller.IncludeIntermediateStops.

No reaction to proposed answer. Please reach out to us in case more clarification is needed.

Sorry for the late response, this answers my question, many thanks.


Unable to sign up users due to PKCE  error - developing locally using Sveltekit.

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Unable to sign users up - get the error "PKCE flow is not supported on signups with autoconfirm enabled". I'm developing locally using Sveltekit and https://github.com/supabase/auth-ui.
Looks like the issue has been resolved for Next https://github.com/supabase/auth-helpers/issues/569 but it's difficult to discern from all the comments what the actual status of the issue is and the action required.
Screenshots

System information

Version of supabase-js: 2.26.0
Version of Node.js: 18.17.0

I've left a comment about which comment has the fix in the second to last comment in that issue. I'm leaving it here again and will be closing this issue too https://github.com/supabase/auth-helpers/issues/569#issuecomment-1703159422.

@silentworks Can confirm it's working now after following your instructions, many thanks.


Add operators for ByteSize and int & double (e.g. *, /, etc)

Support operators like the following:
ByteSize size = ByteSize.FromBytes(1000);
double pi = Math.PI;

ByteSize sizeTimesThree = size * 3;
ByteSize sizeDividedByPi = size / pi;

Just hit a case right after referencing the library for the first time, where I wanted to divide the total memory by "the number of threads" and noticed there is no division overload.
Would make my code simpler if it had it.
Having said that, I don't agree with having an overloaded ^ operator @AdamCoulterOz , since that's normally used for bitwise XOR. It would be extremely misleading to overload it to do something completely different.

Ha, I didn't realise c# didn't use ^ as an exponent operator. I completely agree in that case.

Added in 2.1.0

@Omar this hasn't actually been implemented. I would expect to be able to divide or multiply ByteSize with a primitive number (i.e. int or double, etc).

I've just realised as well that the division operator should return a double, not a ByteSize, as it's now a ratio, not in units of bytes.


Revert "NEW: DockerMonitor No-Kill option (#205)"

This reverts commit b1b19550de4b18ecec8ed8ac96c5a1a22a5e6260.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #208   +/-   ##
=======================================
  Coverage   48.77%   48.77%
=======================================
  Files          33       33
  Lines        4230     4230
=======================================
  Hits         2063     2063
  Misses       1974     1974
  Partials      193      193

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 b1b1955...1deb0a1. Read the comment docs.


SVG support

What are the requirements in order to enable SVG support? RGL depends on react-resizable and draggable which are involved in the GridItem implementation which decides if the item is either resizable and draggable. Ideally the grid algorithms should be abstract from the rendering surface such as svg, canvas or within div containers. In the past hours we have experimented with the code, especially with the placeholder and gridItem processing methods in the ReactGridLayout class, modifying an items properties once an interaction occurs. What we have in mind is to delegate calculated properties to group and rect components (placeholder and gridItem processing methods in the ReactGridLayout class) positioned within an svg element defined in the render method of the ReactGridLayout class.
Thanks,

I don't quite understand your message. I render SVG's dynamically in RGL items out of the box without any issues at all.


General myths api endpt cm 300

General myths listed out with some short information about them (myth id, myth, what science says) only as response to the /myths endpoint.
example use:
http://localhost:5000/myths?session-id=8fd436c1-d15a-4237-9b43-55bd5655c429

Example local testing showing endpoint works.
@NickCallaghan I'd like to keep the session-id as part of the required parameter so that the backend can over time change the code to return the myths in a special order that's personalized to the user. Having the session-id is all that is needed to do that at a later time (so no future frontend changes would be needed).
If you'd like any of the content formatting changes, just let me know and I'll talk with Elle to get it done.
If you'd like any of the dictionary names changed in the JSON response, just let me know too!


After a while the currently playing song & volume controls disappear.

I don't know what triggers it, but after some time the controls disappear and i can no longer mute/unmute/change volume.

This looks to be an error stemming from the fix to chrome autoplay. The "playing" flag is not being set correctly, and its causing this. It happens seemingly randomly, and goes away on refresh, so this will be a hard one to track down.

Fixed in commit 4924f11886c6c51d8048257d384d812d6589a972


Allow copy download link from item

I posted an upstream issue for this, but it might be better fixed here. Either place is fine, as long as it gets fixed.
https://github.com/girder/girder_web_components/issues/225

since this will be related to a url for an item, should we figure out where the link should sit?
the ideal link would be something like:
dandiarchive.org/asset/{id}/  this could return the metadata about the asset
dandiarchive.org/asset/{id}/download could redirect to the actual download location.
where should we implement this?

related: #274 (that we had url with selected items reflected; no more) and #275 (guide user to dandi client)

I've asked @dchiquit to help with this because he got some cycles freed up.

I've asked @dchiquit to help with this because he got some cycles freed up.


[Issue report] Cant connect Raspberry Camera Pi

Describe the bug or issue
Cant connect module raspberry camera, when i open camera said "You camera is currently unavaliable"
Describe your setup

Raspberry Pi 3 Model
Chromium OS r83
Original Camera Raspberry

To Reproduce
Steps to reproduce the behavior:

Open Camera

Expected behaviour
when i open camera said "You camera is currently unavaliable", i already put my camera

Is there a way to use a pi camera module with Chromium OS?
If not, are there any near future plans to add it?
Thanks.

@rizdam I am not sure if they will implement it, but for now, you could use a USB camera, which will work perfectly.

Thanks for the reply.
I need to use the pi camera for my robots.   When a USB camera was properly recognized, it was quick.  Older USB cameras I tried were choppy.
I also found the sound/mic inputs were problematic without a GUI ability to change input volume or gain.

Okay, so maybe you could use another OS for it, as the camera works great on Raspbian, and it has all of the settings you need.
Unless you need NaCl support, for now, I think Raspbian is more stable and usable.
I am sure the devolopers will add it, but they have said that they will fix the performance issues first, so it might be a while before there is support for the Pi Camera.

The basic release only supports the USB camera. There is a lot of work to do to support the MIPI camera. We can't afford it without financial support.


lint fixes for pilot

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1439
Special notes for your reviewer:
Release note:

none

/assign @kyessenov


changed the name of the package

Changed the name of the package to the proper name,

I added the files that were not there

Oh nah, it's still there @Tezekiel

Already done on main branch.
Can we close PR and delete branch @aleksanderjessitm


Installers for 6.0.0 release come with 6.0.0rc2

Problem Description
Tried installing Spyder from the generated Windows installer from the 6.0.0 release but seems like when building it the Spyder version that ends up as part of the spyder-runtime env is 6.0.0rc2
Checking the action that generated the installers I see that the env ends up solving 6.0.0rc2 although spyder=6.0.0 is being requested:

Windows:

https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592842459#step:14:136
https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592842459#step:14:429

Linux:

https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592842226#step:14:147
https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592842226#step:14:522

macOS:

https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592841911#step:14:137
https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592841911#step:14:445

Maybe is related with having still having conda-forge/label/spyder_dev and conda-forge/label/spyder_kernels_rc as channels (https://github.com/spyder-ide/spyder/actions/runs/10677525658/job/29592842459#step:7:7)? 🤔
What is the expected output? What do you see instead?
See over the about dialog that spyder 6.0.0 was installed instead I see 6.0.0rc2

This is really serious and I was afraid something like that could happen because we haven't run the installer workflows with a stable version.
@mrclary, could you take a look at this asap?

I'll replace release assets asap with those from a patch on my fork. Then I'll submit a PR for a permanent fix.

Great! Thanks a lot @mrclary!

Then I'll submit a PR for a permanent fix.

Ok, please remember to submit that PR against master and not 6.x (from now on we'll do backports and not forward-ports between branches).


Link movie-review.js to movie-review.html

WE NEED the movie-review.js file linked to the movie-review.html file so that the interactive elements will work on that page.

Kyle K working on.


Drop Track 1 Azure SDK support

As Track 1 Azure SDK has been deprecated and out of maintenance (public announcement?), azure-cli-core needs to drop Track 1 SDK support.
The extended Track 1 SDK support in MSAL-based Azure CLI adds tons of extra maintenance effort for

MSAL authentication for Track 1 SDK, including ADAL's resource for backward compatibility
Cross-tenant authentication for Track 1 SDK
Continuous Access Evaluation for Track 1 SDK

Drop Track 1

The supportability for deprecated Track 1 SDK adds extra difficulty during the migration to MSAL's managed identity implementation.

Track 1 SDKs are causing problems here and there:

azure-keyvault Track 1 data-plane SDK is not compatible with Python 3.11 because of its dependency on deprecated function inspect.getargspec: https://github.com/Azure/azure-cli/pull/26923#issuecomment-1667329012
Installing azure-mgmt-consumption and azure-mgmt-relay Track 1 mgmt-plane SDKs from source code fails with latest wheel because of its dependency on deprecated module wheel.pep425tags: https://github.com/Azure/azure-cli/issues/27047

Track 1 SDKs are causing problems here and there:

azure-keyvault Track 1 data-plane SDK is not compatible with Python 3.11 because of its dependency on deprecated function inspect.getargspec: [Packaging] Support Python 3.11 #26923 (comment)
Installing azure-mgmt-consumption and azure-mgmt-relay Track 1 mgmt-plane SDKs from source code fails with latest wheel because of its dependency on deprecated module wheel.pep425tags: Azure CLI 2.51.0 cannot be released to Homebrew #27047

azure-mgmt-consumption and azure-mgmt-relay are already migrated to codegen and are not track 1 any longer.


SubViews of camera view disappear

I have added an IBOutlet named cameraView which as you would expect is the view that the camera gets added to. I have a button within that view that I want to use to take the photo, but when the camera gets added to the view, the button shows up for a second and then disappears. Any suggestions on how to fix this or is this an issue with the framework. Honestly not sure. Currently trying:
override func viewDidAppear(_ animated: Bool) {
        self.addCameraToView()
        cameraView.bringSubview(toFront: takePhoto) //Not Working
    }

    private func addCameraToView(){
        cameraManager.addPreviewLayerToView(cameraView)

        cameraManager.showErrorBlock = { [weak self] (erTitle: String, erMessage: String) -> Void in

            //Handle Issues
        }
    }

I thought the bringSubview() function might be a solution but it isn't working. Any help would be greatly appreciated.

@geoherna Did you end up finding a solution to this? I am running into a similar issue right now.

Don't add subviews to previewView, use previewView just for camera, add another view above previewView in superview and add those subviews to that view. This will will always stay above previewView based on position of view hierarchy.


Dataset Organization

Updated datasets retrieval to use the group name as organization when the dataset doesn't have an organization field
Closes #552

validated


Implement this in Node.js ?

Hi, epic project you got here.
I was wondering if this is possivle to make in nodejs?
I was planning to use this on a puppeteer but dunno how.

If there is a way to contact you, i would apreciate


Number of articles and open/close toggle misaligned

As you can see in the screenshot below, the number of articles and the open/close toggle are displayed above the folder names:

I have this issue with all theme variants provided by tt-rss-feedly-theme.

Which version of tt-rss do you use (open the preferences and look at the bottom of the screen)? And what's your browser and its version?

The displayed version is: Tiny Tiny RSS vr10820.4e81233ac (Unsupported)
I don't know why it is indicated "unsupported"?
My Web browser is Firefox 89.0.2 (64-bit) freshly installed. I used v89.0.1 before and had the same issue.

The versions of tt-rss and the theme don't match. You should either update tt-rss or, if you can't do that, switch back to the theme version 2.7.4.

Thank you for your answer. I'm going to try version 2.7.4.


chore: bump to v0.8.1

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
#4053
What's changed and what's your intention?
bump to v0.8.1
Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

🚀


How to silent undefined method errors?

Listing appears to be working correctly, however it lights up every method in a file as undefined if it has not been defined in the same file.
The example below highlights protect_from_forgery as undefined:
class ApplicationController < ActionController::Base
  protect_from_forgery with: :exception
end

This is a support question really and we don’t seem to have maintainers who use ruby a lot. Look for parameters or config options for the linter program itself, and otherwise SL has some filtering options built in.


Update issue templates

Change mmdet to mmdet3d in issue templates

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


How to get the 4h candles as 9:30-11:00-15:00 instead of 13:30 and 16:00?

When I download 4h candles, I get only 2 candles per trading session (I don't want extended hours).
Is there a way I can get those 3 candles: 9:30-11:00-15:00?

I don't think so. A simple, or maybe complicated way would be to get the 2h candles and then convert these to what you want.

Can we get hourly bars?
we I call this:
bar_data = wb.get_bars('QQQ', interval='h2', count=1000, extendTrading=0, timeStamp=None)
I get this output, only one bar...


Fix: for multiple header in parameter support

Hi,
We, a team from SAP working on API Hub and YaaS, started using this converter to convert our RAML definitions into Swagger. We found that some of our RAML files were failing to convert so we had to make some changes, and we wanted to share these changes with you. We collected the list of changes we made in this CHANGELOG and will provide each fix as a different pull request for you so that you can pick the ones that you want to support.
The issue to fix
Header with "collectionFormat: 'multi'" is not supported
The fix
Change the 'multi' to 'csv' so it accepts comma separated lists.
Best regards,
Daniel Roth - SAP Hybris

@tehcyx I apply this fix in https://github.com/APIs-guru/raml-to-swagger/commit/4c095b40bd48ea36402325828a6b4a954cf5e129
Thank you 👍


Hide or customize "Node-RED Map All The Things" Header

This is most likely more for a GitHub "discussion" vs an Issue, but is there a way to add an option to remove the "map all the things" and node-red logo? Option to hide and option to add your own logo and text would be awesome.
I have not contributed to any open source in the past but I use Node-RED a lot so if there's a way for me to help code/contribute on this let me know.

Hi, If you just want to change the name - set the node Name to whatever you want....

If you want t remove the bar completely the easiest way is to embed the map into your own webpage as an iframe and it will not be shown.

or in 2.22.2
msg.payload = {command:{"toptitle":"text you want"}}
return msg;

@smallf00t  - Happy to consider a Pull request like that if you like...

@dceejay how can i "pull request" i m not familiar with github :(

OK - slightly invloved...  but this is a good overview
https://opensource.com/article/19/7/create-pull-request-github
As it's a "small" change I'm happy to do it - but likewise if you want to use it as a learning exercise please go ahead, just let me know.

@dceejay thanks for this one please do it, promise il will learn

Thanks for PR - closing this issue now

Published as v2.23.0


Fixes #5866 -- Implement Support for Median Metric

Describe your changes :
This PR fixes #5866 and implement support for Median. It also implements the concept of window metrics as these types of metrics may require to run within a special context (i.e. executed by themselves for ease of implementation)

Type of change :

[ ] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
Ingestion: @open-metadata/ingestion

Hi @TeddyCr could you please expand on the definition of a WindowMetric? What is the difference functionally from a static metric?

Hey @pmbrull it will be all the metrics such as OVER() or WITHIN GROUP. Often needs to ran a specific way (i.e. group a specific field, etc.). As static metrics are ran all together, iterating over window metrics and executing them individually seems easier.

Hi @TeddyCr could you please expand on the definition of a WindowMetric? What is the difference functionally from a static metric?

Hey @pmbrull it will be all the metrics computed using window functions such as OVER() or WITHIN GROUP. Often needs to ran a specific way (i.e. group a specific field, etc.). As static metrics are ran all together, iterating over window metrics and executing them individually seems easier.

Is there any limitation on running them together with the static metrics? I was imagining Window Metrics as our own abstraction that could check the evolution of any given metric over any number of days (by checking our results history).
Not that we need to use Window Metrics for that, but just thinking if there is any real benefit of splitting these things out or if we can just use SQA syntax to handle whatever it is needed. If the issue is related to isolation (as the ticket you linked), maybe we can just call this "isolatedMetrics" to help us understand our technical approach on this

Hi @TeddyCr could you please expand on the definition of a WindowMetric? What is the difference functionally from a static metric?

Hey @pmbrull it will be all the metrics computed using window functions such as OVER() or WITHIN GROUP. Often needs to ran a specific way (i.e. group a specific field, etc.). As static metrics are ran all together, iterating over window metrics and executing them individually seems easier.

Is there any limitation on running them together with the static metrics? I was imagining Window Metrics as our own abstraction that could check the evolution of any given metric over any number of days (by checking our results history).
Not that we need to use Window Metrics for that, but just thinking if there is any real benefit of splitting these things out or if we can just use SQA syntax to handle whatever it is needed. If the issue is related to isolation (as the ticket you linked), maybe we can just call this "isolatedMetrics" to help us understand our technical approach on this

We can definitely execute them with the static metric, though it would add additional complexity. There is also, more specifically the Redshift (most likely Postgres) where percentil_cont() is throwing an error if ran with additional metrics.

Thanks @TeddyCr for the clarification. Not a direct drawback, just wanted to understand the grouping :) My counter-offer here would be to add these into queryMetrics, such as the histogram. Those are planned to be metrics that require a full query (Select ... from ... etcetc) or a series of queries. The main difference with static metrics is that static metrics can potentially be run all together in a single query. Query metrics are run one after each other.
Do you think that this would already handle the case of the median? Otherwise, we can keep it as is.

Yes, that was my hesitation. My rational was that window function don't necessarily require full custom query, they are supported by sqlalchemy. Something like this func.row_number().over(order_by='x') is a window function and is natively supported by SQA, wdyt?

oki let's leave it with window naming 👌 Should we then move the median.py into window instead of static module?

oki let's leave it with window naming 👌 Should we then move the median.py into window instead of static module?

Good point, let me do that. 🙂

amazing thanks for the explanations @TeddyCr


[Question] Can I have multiple schemas?

Like below
swagger_parser:
  - schema_path: assets/openapis/app_api.json
     output_directory: lib/data/sources/app_api
     client_postfix: AppApi

  - schema_path: assets/openapis/common_api.json
     output_directory: lib/data/sources/common_api
     client_postfix: CommonApi

No, but you can run the generation twice.


Make every flag configurable via ENV vars

Be twelve-factor. Also allows to transparently inject env vars into pods and have them picked up in the future, e.g. with PodInjectionPolicies.
drone does a good job here
$ docker run drone/drone:0.5 server --help
OPTIONS:
   --debug							start the server in debug mode [$DRONE_DEBUG]
   --broker-debug						start the broker in debug mode [$DRONE_BROKER_DEBUG]
   --server-addr ":8000"					server address [$DRONE_SERVER_ADDR]
   --server-cert 						server ssl cert [$DRONE_SERVER_CERT]

This would seem to already be implemented (https://github.com/kubernetes-incubator/external-dns/blob/master/pkg/apis/externaldns/types.go#L83) via kingpin (https://github.com/alecthomas/kingpin/blob/d2d8a9115b36a531781f0ed3c57bcba202976150/app.go#L109); a flag foo can be set via the env var EXTERNAL_DNS_FOO (note the value of config.TXTOwnerId changing from default to someval):
⌂65% [ismith] master ± $GOPATH/bin/external-dns --provider google --source service --once --dry-run 2>&1  | grep config
time="2017-05-12T14:31:36-07:00" level=info msg="config: &{Master: KubeConfig: Sources:[service] Namespace: FqdnTemplate: Compatibility: Provider:google GoogleProject: DomainFilter: Policy:sync Registry:txt TXTOwnerID:default TXTPrefix: Interval:1m0s Once:true DryRun:true LogFormat:text MetricsAddress::7979 Debug:false}"
⌂68% [ismith] master ± EXTERNAL_DNS_TXT_OWNER_ID=someval $GOPATH/bin/external-dns --provider google --source service --once --dry-run 2>&1  | grep config
time="2017-05-12T14:31:43-07:00" level=info msg="config: &{Master: KubeConfig: Sources:[service] Namespace: FqdnTemplate: Compatibility: Provider:google GoogleProject: DomainFilter: Policy:sync Registry:txt TXTOwnerID:someval TXTPrefix: Interval:1m0s Once:true DryRun:true LogFormat:text MetricsAddress::7979 Debug:false}"

So, just a documentation fix?


NoRegionError: You must specify a region.

Hi,
I get this error when I try to run your sample code specifying my cluser_arn and secret_arn:
NoRegionError: You must specify a region.
The connect function -
with aurora_data_api.connect(
aurora_cluster_arn=cluster_arn,
secret_arn=secret_arn,
database=database) as conn:
does not allow specifying a region_name parameter like boto3.client does.

You can use the rds_data_client keyword argument to pass a custom client to the connection constructor.

Oh thank you! I knew there was that parameter, just didn't know how it was worded!
Worked a treat, much obliged :)

@morgan-young this is how I got it to work.. left [your_parameter] where you'd need to feed in your information
rds_client = boto3.client(
'rds-data',
aws_access_key_id = [your_parameter],
aws_secret_access_key = [your_parameter],
region_name = [your_parameter]
)
with aurora_data_api.connect(
aurora_cluster_arn = [your_parameter],
secret_arn = [your_parameter],
rds_data_client = rds_client,
database = [your_parameter]
) as connection:
with connection.cursor() as cursor:

    cursor.execute(sql_query)


Bingo_Game finished

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes # 424
Creating a Bingo Game.

This is a multi-player game.
Including background-sound will keep user more attentive towards the game.
Adding hover effect and animation and images while crossing any number in the game.
Also adding sound while clicking on the any number.
Also providing sound controls to the users to control the background sound.
Also adding loading-page animation and error sound to make it more impressive.

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Avdhesh-Varshney ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Sirs @kunjgit @Arun9739 @raju-kumar21 , please revier my PR and merge it into main branch.


python3Packages.ffmpeg-python: 0.2.0 -> 0.2.0-unstable-2022-07-11; patch out future dependency; add patches for FFmpeg 7

Description of changes
I think it’s cool when the number of things that depend on FFmpeg 4 goes down.
Things done

Built on platform(s)

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

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

[x] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 332111 run on x86_64-linux 1

18 packages built:

backgroundremover
backgroundremover.dist
ffsubsync
ffsubsync.dist
miniplayer
miniplayer.dist
python311Packages.ffmpeg-python
python311Packages.ffmpeg-python.dist
python311Packages.reolink
python311Packages.reolink.dist
python312Packages.ffmpeg-python
python312Packages.ffmpeg-python.dist
python312Packages.reolink
python312Packages.reolink.dist
r128gain
r128gain.dist
ytmdl
ytmdl.dist

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

ffsubsync.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

ffsubsync:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

r128gain.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

r128gain:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 332111 run on aarch64-darwin 1

18 packages built:

backgroundremover
backgroundremover.dist
ffsubsync
ffsubsync.dist
miniplayer
miniplayer.dist
python311Packages.ffmpeg-python
python311Packages.ffmpeg-python.dist
python311Packages.reolink
python311Packages.reolink.dist
python312Packages.ffmpeg-python
python312Packages.ffmpeg-python.dist
python312Packages.reolink
python312Packages.reolink.dist
r128gain
r128gain.dist
ytmdl
ytmdl.dist

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

ffsubsync.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

ffsubsync:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

r128gain.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

r128gain:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.


how to fix bug thead?

Hi @mkoryak ! You try go to link:
http://mkoryak.github.io/floatThead/examples/hidden-columns/
and:
I use middle mouse/ scroll wheel for scroll table, I feel thead of table which it convulse, it not smoothness like I use mouse move scrollbar of browser (I'm not sure the word used to exact, I not good English :) ).
How to fix it? Please, help me! Thank you very much!

useAbsolutePositioning:false

Hi @mkoryak!  I also use useAbsolutePositioning:false, but It have a problem. I hover menu:

Help me! Thank you!

Your menu div needs to have a z index that is higher. Try setting it to 10000000

Thank you for answering, @mkoryak ! I fixed!

@mkoryak , How to fix position of Thead. I want to fix plan in red rectangle, Thead(screen rectangle) don't change position, when I move scrollbar.

sorry, if I cant see your code, I cant help you. jsfiddle please.

Hi @mkoryak ! My Demo:
http://jsfiddle.net/TaNoBi/t4jvqpvc/9/


Fixup following bug introduced in #148

Need to egg my face, I introduced a bug in https://github.com/ariovistus/pyd/pull/148/ - forgot to pass arguments down from the script to the main function. I made untested edits in that PR ("what's the worst that could happen?"); this time I tested this carefully.
Took the opportunity to make a few improvements that make the script more robust:

the shebang line avoids inadvertently running the script in a separate shell, otherwise it would appear to run successfully but have no effect
main has a random suffix so as to avoid clashing with some other main in the current environment
replaced the test -z $1 with $# -eq 0 because if the calling environment has set -u, it would fail on account of unset variable
quoted strings as https://www.shellcheck.net indicated, on the off chance somebody has spaces in dir names

Apologies for the mess!

Thanks for reminding me why I hate BASH

@ariovistus can you please get a chance to take a look?