event calendar editing is funky

@xdamman Wordpress Foundation announced they'll be scaling up their Open Collective use to create events for their community. Net Squared just announced it too.
Can you please look into fixes  we have pending?
(search old issues)
the admins not being translated to the events
the thank you email being hard coded and not editable by event users.
Also, the calendar is looking weird see screenshot.
Tagging this issue bug fix Friday - Does using that tag work for you? Seems easy since you'll be doing Fridays with the team.

Fixed by https://github.com/opencollective/opencollective-frontend/pull/1649/

I think @Betree made a PR to fix the calendar issue.
There's another issue too with the way time is displayed


Add ConcurrencyLimit and its default implementation

Motivation:
As a preparatory step for resolving #12842, we need a construct that limits concurrency asynchronously.
Modifications:

Add ConcurrencyLimit and ConcurrencyLimitHandler
Add the default implementation SimpleConcurrencyLimit

Result:

In our future work, we can allow a user to specify a ConcurrencyLimit when building a DnsNameResolver and use it for limiting the concurrency of DNS queries in DnsQueryContext.writeQuery()

@trustin welcome back buddy :)

I renamed ConcurrencyLimit to Limiter and SimpleConcurrencyLimiter to ConcurrencyLimiter, and then added RateLimiter. I didn't address the comments yet and there are still some rough edges in the implementation, so I converted this PR to draft. I'll ping you once it's ready for reviews.

Had a chat with @normanmaurer a few days ago and we concluded that at the moment we don't really need any pluggability for rate-limiting DNS queries - just simple rate limiting implemented directly in our resolver implementation will do. Once we find similar use cases in other places in Netty, we may resurrect this PR, but for now, let me close it.


Support (R, G, B, 1) swizzle in Metal

This is useful for DXVK support to cover DXGI_FORMAT_B8G8R8X8_* format. See https://github.com/doitsujin/dxvk/issues/634#issuecomment-419977051

In the worst case, we could do this by brutally forcing 1 into the alpha channel (using a render pass) whenever the resource transitions into a SAMPLED state. I don't expect these kinds of resources to be used a lot dynamically,


Add tests for callback client to connect-web conformance tests

This adds logic to connect-web for testing Connect's callback client when running client conformance tests.
The basic approach is that a command-line arg is passed to each runnable client.ts file to specify which type of client to use. The client is then created based on this arg. What this also means is that each run of npm run conformance:client for these packages will run the conformance tests twice -- once with a promise client and once with a callback client.
Also, as part of this PR, the known-failures have been moved to files just for ease of discovery. As a result, there are two known failing files in connect-web now:

known-failing-callback-client.txt - all failing tests when using the callback client across all browsers.
known-failing-promise-client-firefox.txt - all failing tests when using the promise client in Firefox only.

@timostamm incorporated your feedback re: file names. Lmk what you think.


Python CompassApp run_from_file method supports CSV, newline JSON with batching

in order to run very large batches of queries, we want a method on a CompassApp which

takes a filename and chunksize argument (with reasonable default)
by testing the filename suffix, chooses pandas from_csv or from_json with lines=True
chunks the input, passes it to CompassApp.run

question: is it possible to do this without 1) converting each dataframe to a python List[Dict], 2) stringifying the List?

The CLI has been updated with this feature and the logic of writes should have the correct append output behavior to support batching from Python.
It would seem like this should just be a simple wrapper function in Python that creates the matches, such as the pandas chunking API.

This is directly related to #209


brace-bracket-paren doesn't dedent

This causes rest of user code to be indented even though we're at the end of statement
angular.module('flapperNews', []).controller('MainCtrl', [
    '$scope',
    function ($scope) {
        $scope.test = 'Hello world';
    }]);

hit enter. notice we are indented
[copied from codeplex https://nodejstools.codeplex.com/workitem/1504]

Fixed in ES6 Preview Intellisense in NTVS 1.2 Alpha


Add support for musl?

I'd love to use this on a minimal alpine linux VM but apparently I can't build this project so that it'll run on musl :( Maybe I just don't know how to do so, but sadly it doesn't seem like it...

@tulilirockz thanks for opening this. Have you looked into dotnet on alpine? Some relevant bits I see are:

https://learn.microsoft.com/en-us/dotnet/core/install/linux-alpine
https://github.com/dotnet/sdk/issues/24448

In any case, if someone figures out how to make dotnet link against musl and wrap it into a CI job, I'd be happy to accept a patch.

Looks like dotnet has musl target out of the box now https://learn.microsoft.com/en-us/dotnet/core/rid-catalog#linux-rids


[Private Domain Onboarding Check] Create new privateDomainOnboardingCheck beta

See design doc section here: https://docs.google.com/document/d/1JlM9G3jZpaHDlcILWL9170ancMLtOnI2a73dQgX6ENo/edit?tab=t.0#heading=h.bkqzqoni8k57

Create Beta privateDomainOnboardingCheck
We will put the work behind a beta so that we can build the frontend parts in parallel with the backend parts. The backend might take longer to build out than the frontend so having the work put behind a beta will allow us to merge frontend code without giving users an incomplete feature.

PR is up an in review

@allgandalf should be sometime today. Not sure exactly when but today.

Beta was deployed to production, should be available now @allgandalf


fly execute doesn't like hard links

when forgetting to use -x fly tries to tar up the entire git repo which prints confusing output:
 2015-09-25 11:41:27 ☆ ruby 2.2.2p95 (system) clementina in ~/workspace/concourse
± |develop ✓| → fly e -c ./ci/baggageclaim.yml
executing build 7
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 95.6M    0 95.6M    0     0  3963k      0 --:--:--  0:00:24 --:--:-- 4445ktar: can't create hardlink from ./.git/modules/src/github.com/concourse/gate/objects/pack/pack-5e7625078c21d7505391d37335d947c6a7b7c912.idx to ././@LongHardLink: No such file or directory
tar: can't create hardlink from ./.git/modules/src/github.com/concourse/gate/objects/pack/pack-5e7625078c21d7505391d37335d947c6a7b7c912.pack to ././@LongHardLink: No such file or directory
100 1752M    0 1752M    0     0  14.9M      0 --:--:--  0:01:57 --:--:-- 16.5M
initializing with docker:///concourse/baggageclaim-ci

This looks like a quirk of OS X <-> Linux tar interaction or something similarly cryptic. I'm finding it hard to care until it becomes an actual issue (it looks like it kept going, from your snippet). There are similar problems you'll find on Windows with path names being too long (which node_modules quickly reveals); there's not a whole lot we can do about it.
If it keeps happening all the time and starts impeding your progress, feel free to reopen.


Drag from outside is missing placeholder

Run /examples/15-drag-from-outside.html using version 0.18.x and note that the placeholder doesn't show up at all like it does in v0.17: https://strml.github.io/react-grid-layout/examples/15-drag-from-outside.html

I'm also experiencing this problem.

me too

me too

I have the same issue. This also means that the rest of the layout doesn't shift in response to dragging it over items.

Also running into this, it seems to me that this line should triggering a update to state (probably activeDrag or something like it) but instead, it just modifies a local variable, which doesn't trigger any render. I might dig in later to try to understand what the appropriate response should be, if i get some time.

I would assume these changes are due to the performance improvements in 0.18, so I'd like to figure out a way to maintain performance but also get the placeholder working.

I've submitted a PR to fix this. @STRML let me know if there are any changes, I know this issue is blocking me from using this library entirely.

@STRML any idea when this might be released? Just want to know if I should fall back to 0.7 or wait for the newest 0.8.

Good call. Released 0.18.3


Possibly improve std::variant readability

std::variant is kind of ugly to use without true pattern matching (hopefully in C++23), but get_if at least allows the type name to not be specified twice, which might be a little nicer to read.
There's some extra dereferencing involved with the coefficients, but #252 should clean that up.

LGTM

LGTM

LGTM

LGTM


add documentation about the document types & format in Mongodb

@surli, I saw you put this issue as minor priority, but I plan to check the types of info (e.g. runId) in each file we generate, to see if something important is missing, etc. In the middle of this task, it would be nice that I already document it, otherwise a duplicate effort will be put on it in the future. So I would like to ask you if you already have something in mind for this issue, so that way I could start by what you already think. If you don't have anything in mind, I will just start by myself, and then we can polish it in a PR.

if you already have something in mind for this issue

For me this documentation should be on the form of JSON schema for each collection we have in the database. And to add a README to document the purpose of each collection and how they can be related to each other.
I put a minor priority but I'll certainly do it before the end of my contract to complete our documentation.

Ok, I remember now the thing I wanted to talk to you: it's about this issue.

For me this documentation should be on the form of JSON schema for each collection we have in the database. And to add a README to document the purpose of each collection and how they can be related to each other.

WDYT if I take just one collection, build the JSON schema for it, write a README to document the purpose of it, and then you review it for me in the next two days? Because then, you validating one, I do the other ones in the same style, and when you come back, it will be ready for all collections, only missing the part of the relation of them, which we can discuss later.

if I take just one collection, build the JSON schema for it, write a README to document the purpose of it, and then you review it for me in the next two days?

I'll only be able to validate it tomorrow, and you know that's my job to do that: I'm sure you have plenty of other things to do. Here I'm afraid you loose time for nothing.


Support emmet-style tags?

Hi @lukejacksonn!
Thank you for this project! I am hoping to experiment with it as a way to write views in a virtual-Dom library independent way, so I hope you continue to support being able to specify the node structure and not just preact and hyperapp.
I have done an experiment with JSX here: https://meiosis.js.org/examples/setup
But I think an ijk/hyperscript version would be even cooler! I will give it a try.
Now, I was thinking, would it make sense to support emmet style tags such as ["button#save.btn.btn-primary", ...]? I suppose you would also have to have a way to specify whether to use class or className, not sure...
What do you think?
Thank you!

Hey 👋 thanks for getting involved! I do intend to keep the schema configurable (for now at least) perhaps at some point I might export a few framework ready functions that are already configured but I haven't found a super nice way to do it yet.
I actually have a version somewhere that does what you have requested.. but I can't find it right now. It might have been a bad implementation but I don't remember it being too big of a change (~5LOC)! I'd like to see how you would go about it if you have any bright ideas.

I ended up getting a little bit carried away, perhaps :-) and wrote seview. Thanks for the inspiration @lukejacksonn !

Wow. So you did! Looks great 🎉


BUG: Proportion before opening NeoTree is not kept

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
0.10.1
Operating System / Version
WSL2 + Ubuntu 22.04 LTS
Describe the Bug
When there are more than one window, then open neo-tree, the original proportion will not be kept.
Screenshots, Traceback
No response
Steps to Reproduce

Open two windows, their sizes are equal:

3. Open neo-tree, after this, window 1 and window 2 have different sizes:

Expected Behavior
An option for keeping the original proportion
Your Configuration
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}

local neotree_config = {
  "nvim-neo-tree/neo-tree.nvim",
  dependencies = { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim" },
  cmd = { "Neotree" },
  keys = {
    { "<Leader>e", "<Cmd>Neotree<CR>" }, -- change or remove this line if relevant.
  },
  opts = {
    -- Your config here
    -- ...
-- Use default
  },
}

table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")

This is what I have did to solve this:
                {
                    event = 'neo_tree_window_after_open',
                    handler = function(_)
                        vim.cmd('wincmd =')
                    end
                },


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 211 ms

Resolved: ClamAV performance has improved in 32e128f.


Put in place updated versioning scheme.

TOC agreed on an update versioning scheme: https://docs.google.com/document/d/1ilwz-HGSeiRDCFwP5rm-5d_UY6OOYL_nflx7bNggek0/edit#heading=h.7zgnj8bwqfld

dupe of https://github.com/istio/istio/issues/14770


Added Crop Rotation Recommendation system

Description

Added the Crop Rotation Recommendation system, which suggests the optimal next crop based on previous crop, soil type, moisture level, and nutrient content (Nitrogen, Phosphorus, Potassium). This feature uses a machine learning model to assist in sustainable farming practices by predicting the best crop rotation.
Issue Resolved
Resolves #106
Changes Made

Integrated the crop recommendation model.
Added a new section with input fields for Previous Crop, Soil Type, Moisture Level, Nitrogen (N), Phosphorus (P), and Potassium (K).
Implemented mappings for crop and soil types.
Added prediction logic that returns the recommended crop.
Added model's documentation and explanation for the new feature.

Screenshots or Videos

Additional Details
The dataset is not already existing one in the internet! Rather, it was synthesized specifically for this purpose from various internet sources.

Checklist

[x] My code follows the current project structure
[x] I have thoroughly reviewed and updated the requirements.txt file to include any new packages
[x] The predict.py file includes a properly implemented model_details() function, or the notebook contains this function to print a detailed model report. The model will not be accepted without this function, as it is essential for generating the necessary model details.
[x] I have added relevant tests (if necessary).
[x] I have added comments in the code where needed.
[x] This PR is submitted under Hacktoberfest.
[x] This PR is submitted under GirlScript Summer of Code (GSSoC-Extd).

I'm closing this PR for now. Please improve the model and submit a new PR once ready.

First, try to find a relevant dataset. If that's not feasible, dedicate time to researching the topic. Your dataset was highly unbalanced, with some crops appearing 10K times while others only in the thousands. Once the synthetic dataset is generated, analyze it using visualizations and other methods to ensure it accurately reflects real-world conditions.


fix: Export Mode enum as value

Previously it was only exported as a type, causing it to be undefined in release.

Fixes https://github.com/mrousavy/react-native-mmkv/issues/691

@mrousavy  when the issue will be released?
Currently using
"react-native-mmkv": "3.0.0-beta.5",
"react-native": "0.74.2",
"react": "18.2.0",
and getting error like
Invariant Violation: "MyAppName" has not been registered. This can happen if:

Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
A module failed to load due to an error and AppRegistry.registerComponent wasn't called.

working fine if I use new MMKV()
if I use like ->  new MMKV({ mode: 1 }) then getting above error.
@mrousavy  can you please help me ?

Dude I told you before in the other issue you created - please stop pinging me


Segmentation faults since interpret 0.1.11

Hi, thank you for your great work.
I just tried updating from 0.1.10 to 0.1.11 using pip and I am getting segmentation faults.
The issue does not seem to originate from a memory resource limitation (I have a 10 GB free memory margin when using 0.1.10) .
I was not able to diagnose further.
Platform : x86_64, Linux, ubuntu 16
Code extract: (works fine with 0.1.10)
_ebm = ExplainableBoostingRegressor(
    n_estimators=16,
    learning_rate=0.1,
    early_stopping_run_length=10,
    data_n_episodes=200,
    n_jobs=1, # same error with n_jobs=-2
    feature_names=_categorical_features + _numerical_features,
    feature_types= ['categorical'] * len(_categorical_features) + ['continuous'] * len(_numerical_features))

_ebm.fit(X, y)  # X: 108,728 x 39 numpy array

GDB trace:
# Segmentation fault (core dumped):

Thread 1 "python" received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x2) at malloc.c:2951
2951    malloc.c: No such file or directory.
(gdb) bt
#0  __GI___libc_free (mem=0x2) at malloc.c:2951
#1  0x00007ffed376128c in DataSetAttributeCombination::~DataSetAttributeCombination() ()
   from /home/ubuntu/miniconda3/envs/env/lib/python3.7/site-packages/interpret/glassbox/ebm/../../lib/lib_ebmcore_linux_x64.so
#2  0x00007ffed377508d in FreeTraining ()
   from /home/ubuntu/miniconda3/envs/env/lib/python3.7/site-packages/interpret/glassbox/ebm/../../lib/lib_ebmcore_linux_x64.so

Python logs tail: (lots of INFO and ERROR messages since this release !).
[...]
INFO: Entered GetBestModel: ebmTraining=0x555e1f55ad90, indexAttributeCombination=38
INFO: Exited GetBestModel 0x555e24b7e6f0
INFO: Deallocation start
INFO: Entered FreeTraining: ebmTraining=0x555e1f55ad90
INFO: Entered ~EbmTrainingState
INFO: ~EbmTrainingState identified as regression type
INFO: Entered ~CachedTrainingThreadResources
INFO: Exited ~CachedTrainingThreadResources
INFO: Entered SamplingWithReplacement::FreeSamplingSets
INFO: Entered ~SamplingWithReplacement
INFO: Exited ~SamplingWithReplacement
INFO: Exited SamplingWithReplacement::FreeSamplingSets
INFO: Entered ~DataSetAttributeCombination

Segmentation fault (core dumped)

(Full log here: ebm_error_log.txt ).

Hi @martinsotir -
Thank you for reporting this!  We believe we've found and fixed the issue, and are in the process of putting out a new release to address this.  This problem only manifests itself if you have features that contain a single value.

InterpretML Team

Hi @martinsotir -
The fix is released now as version 0.1.12.  Please try it out and let us know if everything is working for you now!
-InterpretML Team

Thanks for the quick answer, dropping single-valued features did the trick.
I can confirm that the 0.1.12 release also fix this issue!


[Issue][Windows] support output file path

issues:

cannot rename in the last step

this reference:


[iOS] Other shapes than squares

Describe the bug
Hello, when I try to use other shapes than squares on iOS generated library than the QR code is not visible at all. I tried to change parameters like color and sizes but the result is always the same. It works perfectly on Android (with same parameters).
To Reproduce
Steps to reproduce:

Add .ofCircles() to QRCode builder
Observe

Screenshots or other QRCodes rendered with other tools

Additional context
Xcode 15.2
Result is same on physical device and Simulator

Heya, I'll take a look on this! I found something similar on other platforms a while ago and I thought it has been solved for all the others as well.
Thanks for bringing it forth <3

Hello again ^^
Sorry for this taking longer than expected, I had some issues with my MacOS environment and had to pretty much rebuild it from scratch. This is the next fix I'll add to #131 :)


adding instructions for new forked repos

i might be dum but ok
im not sure about this, need more testing
so i forked this repo and then tried to run and realized node_modules is not present. then i tried cd ./src (package.json is in ./src) and npm install to download and add the modules.
the thing added a package-lock.json in ./ and edited a lot of things in ./src/package-lock.json. i ultimately deleted the generated ./package-lock.json and reverted changes of the one in ./src for this commit (ran again and everything worked fine).
idk but i suggest moving package.json and the lock one to ./ because its quite inconvenient i think (not sure).

Sorry for late respond, but I believe that README.md have been modified and you don't have the latest version of master branch on your local machine, please check and fetch the branch because I have changed the README on that particular section. Instructions relate to running and building the app are a lot more clear in those new commits.
Secondly, about node_module, it is not practical to commit node_module along with your repo, because it will be a waste of resource while others can just download and install packages using npm i. About the location of package.json, by putting it into src folder, developers would save more time not having to move the working directory to parent directory (./) just to use node_module.
Regard the problem with package-lock.json, it was meant to be modify during the installation of packages using npm i (according to npm documentation).

The difference is that package-lock.json cannot be published, and it will be ignored if found in any place other than the root project

But thanks to your request, I will add into .gitignore to ignore that file because this Stack Overflow question.
Thank you for interested in this project.


Moving to cmake based build changed shared library versioning semantics

Comment:
In #16 we moved to using CMake to build things, but it turns out the CMake build doesn't version the produced shared libraries the same way that autotools did. See https://github.com/davea42/libdwarf-code/issues/241 for more info.
This is technically a breaking change and if someone built against an earlier libdwarf they can now run into issues where it will look for libdwarf.so.0 which no longer exists in the package.
Any opinions on if we should address this in some kind of way?

Fixed by #20


Disabled codacy checks for library files

Fixes #1299
Changes: Added exclude files in .codacy.yml

@Princu7 @geekyd please review.


Efficient cloning of taskgraphs on top of new input partitions?

Hi!
I'm a high energy particle physicist using dask, dask-awkward, and dask-histogram to compute complex analyses over billions of rows with many variations of systematic uncertainties to create rich statistical models of our collider data.
The task graphs that we generate are often rather complex and can easily reach thousands of nodes before optimization for a single dataset, and we then construct the task graph for multiple datasets. This can be time consuming (tens of minutes for a ~200 datasets!), resulting in sluggish user experience that is largely because of repeated work. The structure of the task graph likely only needs to be calculated 2-3 times at most, depending on if the dataset is signal simulation, background simulation, or experiment data.
Would it be possible to instead calculate the structure, which is the expensive part, once and then re-key the graph for new input partitions (and rekeying all dependents of the inputs)? This should be much faster since it's essentially walking through the taskgraph, calculating some hashes, and creating the appropriate number of new partitions. This approach may even work for tree-reduction or repartitioning layers (in modes where you don't need to know the partition structure a priori), since these are often calculated only when the low level graph is finally materialized.
Has this operation already been implemented somewhere (I couldn't find anything)?
Is this a reasonable thing to do?
Are there any missing necessary components in dask to implementing a strategy like this?
Thanks in advance!

My first suggestion would be to profile graph construction.  That might
give you a better understanding of what's slowing things down and give you
ideas on where to focus effort.  It could be that what you suggest is the
best course of action, but if you haven't yet gone through a round of
profiling and optimization I wouldn't be surprised if there was a 10x cost
reduction in there somewhere.
On Wed, Oct 16, 2024, 12:23 PM Lindsey Gray @.***>
wrote:

Hi!
I'm a high energy particle physicist using dask, dask-awkward
https://github.com/dask-contrib/dask-awkward, and dask-histogram
https://github.com/dask-contrib/dask-histogram to compute complex
analyses over billions of rows with many variations of systematic
uncertainties to create rich statistical models of our collider data.
The task graphs that we generate are often rather complex and can easily
reach thousands of nodes before optimization for a single dataset, and we
then construct the task graph for multiple datasets. This can be time
consuming (tens of minutes for a ~200 datasets!), resulting in sluggish
user experience that is largely because of repeated work. The structure of
the task graph likely only needs to be calculated 2-3 times at most,
depending on if the dataset is signal simulation, background simulation, or
experiment data.
Would it be possible to instead calculate the structure, which is the
expensive part, once and then re-key the graph for new input partitions
(and rekeying all dependents of the inputs)? This should be much faster
since it's essentially walking through the taskgraph, calculating some
hashes, and creating the appropriate number of new partitions. This
approach may even work for tree-reduction or repartitioning layers (in
modes where you don't need to know the partition structure a priori), since
these are often calculated only when the low level graph is finally
materialized.
Has this operation already been implemented somewhere? Is this a
reasonable thing to do? Are there any missing necessary components in dask
to implementing a strategy like this?
Thanks in advance!
—
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/11435, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTCUKHDLNN2VTFFHL53Z32OKNAVCNFSM6AAAAABQB6VTB6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4TENJWGM3DSNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@mrocklin Thanks for the reply - we have already done one pass of extensive profile guided optimization, which got this process from taking > 1 hour to the ~10 minutes quoted above.

I can pull up the profiles in a bit for you to see (not at the right computer) but generally it boils down to that we are doing a very large number of small operations resulting in building that dictionary and predicting the output types (a la dask-array) takes quite some time. More succinctly: our task graphs are just big and it's kinda awkward to deal with.
Largely - it's the output type prediction that takes a significant amount of time, which is what gave me the idea for the proposal above and interest in corresponding tools. We've already optimized the type tracing/prediction to point of selectively removing correctness guarantees when we know they are met for other reasons. However, since we don't necessarily need to build the task graph again for the same data flow, it seemed prudent to instead rekey a graph that we know will be the same for a given dataset.
Joining all the datasets that share the same dataflow together creates other problems since it's easy to end up in a situation where you have a few billion individual tasks even after graph optimization. This creates other problems.
Revisiting the joining just now brings up another possible idea - if we only did the joining as a "logical" step and then "unjoined" the task graph at the end for actual submission it could be a way around. Though I can imagine it being a bit clunky for users, but that's also an engineering problem more than fundamental usage.

Does this issue/discussion fit under the umbrella of dask-expr and/or array-expr? I haven't carefully digested this discussion, but it seems like it could be solved by generating/caching a graph template at the expression level.

Hi! Sorry for the delay, I was on a quite needed vacation for a bit.

Does this issue/discussion fit under the umbrella of dask-expr and/or array-expr? I haven't carefully digested this discussion, but it seems like it could be solved by generating/caching a graph template at the expression level.

I'm not sure if dask(-array)-expr and dask-awkward are miscible with each other (or if they could be made to be). However, if it can cache a task graph and apply it to some other input dataset this is definitely a thread to pull on, even if we can only use some part of it. Perhaps there's an interface to the caching mechanism we can extract and work out generally?

I think the next question would then be "what is the slow part?"

Yes we've profiled this to a reasonable degree at this point and even after that a lot of time is spent in the "typetracing" mechanism to predict output types of various array transformations in awkward-array.
It's been a while since I made the profiles I'll regenerate those and post them to this thread and we can continue the discussion.
@martindurant @jpivarski


deps(dsr): DSR update for "[Warnings/Errors] Design and accessibility improvements" if you need it

Here's just the DSR updates in case ya need them @meissadia 👍 You can git cherry-pick this into your branch.

This has been integrated into 568__design-review__warnings


M24H-43 case number copy change

Has M24H-47 merged in, review that first please.

@KaitCrawford & @bruskiza ready for review. Has the earlier copy change merged in (which already landed) but somehow that's not reflecting here, not sure why. The only new commit is the last one.

:+1:

@smn I added some html that went missing

@KaitCrawford great catch, thank you!


Expand documentation on sp_stop_job and sp_update_job

Please add what is the difference between EXEC dbo.sp_stop_job and EXEC dbo.sp_update_job @enabled = 0.
How the db engine handles both operations?
What happens to specifc job when manipulated by either of above?
Does disabling allows currently running job to finish?
Does stopping rollsback entire data?
thx!

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

ID: 9f5362cd-2e52-0022-0953-4803f3c6ab9f
Version Independent ID: 8b73adfa-aab5-06a8-db1b-cc18d00abad6
Content: Disable or Enable a Job - SQL Server Agent
Content Source: docs/ssms/agent/disable-or-enable-a-job.md
Product: sql
Technology: ssms
GitHub Login: @markingmyname
Microsoft Alias: maghan

@marcin2x4 -- Marcin, thank you for your feedback and questions.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@markingmyname -- Mark, please look into this issue.

#reassign:@markingmyname I don't own this content

Hi, @marcin2x4.
First, apologizes for the extremely delayed response.
Let me try and give some reference and context to both sprocs.
sp_stop_job:
sp_stop_job sends a stop signal to the database. Some processes can be stopped immediately and some must reach a stable point (or an entry point to the code path) before they can stop. Some long-running Transact-SQL statements such as BACKUP, RESTORE, and some DBCC commands can take a long time to finish. When these are running, it may take a while before the job is canceled. Stopping a job causes a "Job Canceled" entry to be recorded in the job history.
If a job is currently executing a step of type CmdExec or PowerShell, the process being run (for example, MyProgram.exe) is forced to end prematurely. The premature ending can result in unpredictable behavior such as files in use by the process being held open. Consequently, sp_stop_job should be used only in extreme circumstances if the job contains steps of type CmdExec or PowerShell.
sp_update_job @enabled = 0:
sp_update_job must be run from the msdb database.
sp_update_job changes only those settings for which parameter values are supplied. If a parameter is omitted, the current setting is retained.

Please let me know if this better explains the differences.
If not, feel free to reach out again.
Thank you.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue. To see what the community is wanting, please visit the SQL Server User Feedback site.


Changing the readiness probe did not recreate the pod

Describe the bug
While bumping the cf-deployment version on KubeCF, it was required to change one of the readiness probes for doppler. Switching from a exec.command to a tcpSocket.port didn't trigger a pod recreation, and I can assert that not even the QuarksStatefulSet got updated.
To Reproduce
Change the doppler readiness probe from:
      healthcheck:
        doppler:
          readiness:
            exec:
              command: [curl, --fail, --head, --silent, http://localhost:14825/health]

to
      healthcheck:
        doppler:
          readiness:
            tcpSocket:
              port: 3459

Expected behavior
I expected the readiness probe to be updated.
Environment

CF-Operator Version: v3.3.0-0.gf32b521e.
KubeCF v1.0.1-ish.

I beleieve this is a duplicate of https://github.com/cloudfoundry-incubator/cf-operator/issues/812
Should be fixed by https://github.com/cloudfoundry-incubator/cf-operator/pull/841/files

@manno Thanks!


Connect event only on worldmap in node

When setting the worldmap in node to "connection event only" it does not only trigger on the connection event. it accually triggers on all events

Refactored recently in 2.7.0


migrate to use tembo-telemetry

Migrate project to use tembo-telemetry

I believe we will need to add this feature/option to the tembo-telemetry crate before we can do this https://github.com/tembo-io/tembo-telemetry/issues/2


how do I filter the data when some fields is null

select * from TEST where id = null
some query like above,the id may by tag or be field,but the result is empty
what's the correct sql?

This question is more appropriate for our community website.


Refactor writeAndFlushResponseToClient

Motivation
https://github.com/streamnative/kop/pull/429 introduced a request timeout to avoid some requests being blocked by the previous requests. However, it changes the behavior of writeAndFlushResponseToClient.
Before #429, writeAndFlushResponseToClient removed all completed response futures in the head of responseQueue and then sent the completed response to client.
After #429, writeAndFlushResponseToClient removed all response futures, and use CompletableFuture#get(long timeout, TimeUnit unit) to wait until all futures are completed or expired.
We shouldn't wait any CompletableFuture in a CompletableFuture's callback.
Modifications
In writeAndFlushResponseToClient, only remove completed or expired response futures. Here we combine peek and boolean remove(Object o) for thread safety.
For responses that are expired or completed exceptionally, just skip them and don't send any response to client because Kafka client has a retry mechanism. When Kafka processes an expired request, it also doesn't send any response to client.
For responses that are completed normally, send the response and release the internal Netty buffers if necessary.

@dockerzhang @wuzhanpeng PTAL

LGTM 👍


haddock3 tutorial review

This fixes a lot of typos, many inconsistent CSS styling and some wrong html tags
by the way there are a lot of spell-checkers for code :)

here you can see the live preview of this PR: https://www.rvhonorato.me/haddocking.github.io/education/HADDOCK3/HADDOCK3-antibody-antigen/


Revert "chore: import repository https://github.com/ajishasb/io.git"

Reverts ajishasb/jenkins#6

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

Needs approval from an approver in each of these files:

OWNERS

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


ES6: spread element for function argument.

Refs #1169

:+1:. LGTM! I wrote a simple range visualizer to check the range https://gist.github.com/ikarienator/a18b30b7186ac2edd464.


python312Packages.broadlink: 0.18.3 -> 0.19.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.broadlink is: Python API for controlling Broadlink IR controllers
meta.homepage for python312Packages.broadlink is: https://github.com/mjg59/python-broadlink
meta.changelog for python312Packages.broadlink is: https://github.com/mjg59/python-broadlink/releases/tag/0.19.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.19.0 with grep in /nix/store/f0g9riikzaly3mmdh9fvgg1ayvqkhv76-python3.12-broadlink-0.19.0
found 0.19.0 in filename of file in /nix/store/f0g9riikzaly3mmdh9fvgg1ayvqkhv76-python3.12-broadlink-0.19.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
broadlink-cli
home-assistant-component-tests.broadlink
python311Packages.broadlink
python312Packages.broadlink

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f0g9riikzaly3mmdh9fvgg1ayvqkhv76-python3.12-broadlink-0.19.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.broadlink https://github.com/r-ryantm/nixpkgs/archive/5c639817f69684e629274df1f3faae4708956e19.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5c639817f69684e629274df1f3faae4708956e19#python312Packages.broadlink

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f0g9riikzaly3mmdh9fvgg1ayvqkhv76-python3.12-broadlink-0.19.0
ls -la /nix/store/f0g9riikzaly3mmdh9fvgg1ayvqkhv76-python3.12-broadlink-0.19.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

6 packages built:

broadlink-cli
home-assistant-component-tests.broadlink
python311Packages.broadlink
python311Packages.broadlink.dist
python312Packages.broadlink
python312Packages.broadlink.dist

Maintainer pings
cc @fabaff for testing.

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

6 packages built:

broadlink-cli
home-assistant-component-tests.broadlink
python311Packages.broadlink
python311Packages.broadlink.dist
python312Packages.broadlink
python312Packages.broadlink.dist


Publish an estimated time before changes are active

Can you please include an estimate on the time it takes for changes to become active. For example, if I make a change to a Safe Links policy by adding an affected group of users, how long before the policy starts to affect the new group/users?

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

ID: 3a27041e-26ec-eaf9-83e3-a7a926a50d33
Version Independent ID: 3a27041e-26ec-eaf9-83e3-a7a926a50d33
Content: Set up Safe Links policies in Microsoft Defender for Office 365
Content Source: microsoft-365/security/office-365-security/safe-links-policies-configure.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@Jono007, according to the "What do you need to know before you begin?" section of the article you referenced:

Allow up to 6 hours for a new or updated policy to be applied.

Thank you Chris. Sorry I missed that!

@Jono007, no problem.
Thanks for the feedback.
Closing.


Use protocol version from the requested block in reward request

We should request the SeigniorageRecipientsRequest with protocol version from the same block as the state root hash, because the underlying logic will issue a legacy contract request only when major version is 1. Right now this causes an issue when requesting a V1 block from V2 node. Note: we still don't support V1 rewards but this returns the correct error message.

bors r+


Open in Spotify not working

Upon clicking the "Open in Spotify" button, Spotify should open via deep link.
It is currently not.

Fixed in 184d08cb77066218bf51c456ff40ce1132391b96
Merge to master in #34


[Enhancement] Set enable_new_load_on_memory_limit_exceeded default to true

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

This configuration is mainly to prevent high-concurrency imports, the memory has exceeded the limit, and new tasks are still initiated, resulting in the problem of memory overrun. However, in most actual scenarios of users, the import concurrency is not high, and the import itself has a back pressure mechanism, which can alleviate this problem. However, due to the high level of disk IO, the backlog of memory will lead to an import error. When the user sees the error, the load_mem_limit will be adjusted, which will cause the import memory to occupy too much and trigger a stability problem.
Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3
[x] 2.2

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


rolling_update: exclude clients from node-exporter

Since b105549 we don't install node-exporter on client nodes so we should
also exclude the client node from the node-exporter upgrade.
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

jenkins test centos-non_container-update

jenkins test centos-container-update

jenkins test centos-non_container-update

jenkins test centos-container-update


when no search params is receiver, it should behave like if it was not used

Hi,
Thank you for your amazing gem, I think it would be good to have
UsersSearch.new(User).search(permitted_filters)

be equivalent to
User.all

when permitted_filters is empty
what do you think?

Hi @pywebdesign,
I don't like the idea of adding logic to handle an specific type of class and a particular case, since Lupa tries to be ORM agnostic, meaning that your User class could be any kind of object.
Anyway, thanks for the suggestion.


run to fixed certainty

I think fixed iteration and fixed time benchmarks will both be affected by hard to predict platform level performance fluctuations. e.g. if you run the same file in a comparison against itself the second instance will be faster 9 times in 10. I guess the hardware warms up or something. A way around this would be to take multiple samples until the sample error falls below a certain level. statistics theory required though!

Not as such but it's not likely I'll do it  anytime soon
On Sun, May 31, 2015 at 9:09 AM, David Halls<EMAIL_ADDRESS>wrote:

Hey @jkroso did you decide not to do this?
Reply to this email directly or view it on GitHub:
https://github.com/vesln/b/issues/4#issuecomment-107085800

:( No time to do it either. This could have been the best Node benchmark module.
Anyway, all the best.


[Maoni-Sample-TEST] New Feedback

Device language : English (United States)
Device : Nexus 5X
Screen size : 1080 x 1794
Device Type : Phone
Manufacturer : LGE
Native platform : [arm64-v8a, ]
Screen density : 420 dpi
Version code : 240
Application ID : org.rm3l.maoni.sample
Version name : 2.4.0
Android version : Android 7.1.2 (SDK 25)

/!\ This is just a test, using maoni-github from the sample app


Doc refactoring and update hello-world sample

update doc for better reading.
update hello-world sample, as it fails with CUDA 10.

Coverage increased (+0.01%) to 52.947% when pulling b8ef2c75a0a2158307859734dfdf83fd94396327 on squirrelsc:doc_fix into a7525dc9c5c5ad11e9a5a4f182951c5e2dd07711 on Microsoft:master.


Potential Misconfiguration

We are a group of researchers from Yale University building a tool to finding bugs in configurations files. To evaluate the effectiveness of our tool, we randomly selected 1000 open source configuration files to verify and are requesting feedback on our error report. Your file https://raw.githubusercontent.com/mozilla/marketplace-env/55dab6510c373dd9011b9c554627fe346ecc23bc/docker/images/mysql-service/my.cnf was among those files. When we ran our tool your file, it reported the following potential errors.
[FINE GRAINED ERROR: Expected thread-cache-size[mysqld] * tmp-table-size[mysqld] >= max-heap-table-size[mysqld]
Found values: ["thread-cache-size[mysqld]=0","max-heap-table-size[mysqld]=16k","tmp-table-size[mysqld]=1k"]
In the training set we saw: ">=" 70 times, "<=" 1 times, "==" 0 times
FINE GRAINED ERROR: Expected thread-cache-size[mysqld] * thread-stack[mysqld] >= query-cache-size[mysqld]
Found values: ["query-cache-size[mysqld]=0","thread-cache-size[mysqld]=0","thread-stack[mysqld]=131072"]
In the training set we saw: ">=" 63 times, "<=" 0 times, "==" 0 times
FINE GRAINED ERROR: Expected innodb-buffer-pool-size[mysqld] * thread-cache-size[mysqld] >= innodb-log-buffer-size[mysqld]
Found values: ["innodb-buffer-pool-size[mysqld]=5m","innodb-log-buffer-size[mysqld]=256k","thread-cache-size[mysqld]=0"]
In the training set we saw: ">=" 74 times, "<=" 5 times, "==" 0 times
]
The training set referenced in the report is taken from the industrial configuration files at https://github.com/tianyin/configuration_datasets. Note that even if your system is currently working, these bug may manifest itself only under large traffic loads or different system environments.
If you feel the any of above errors may indeed cause problems either on your system, or a different system, please comment on this issue report in the space below. This will help use to improve our tool. If you do not believe this is a potential bug, please feel free to close this issue. If possible we would appreciate your feedback before July 27.
If you would like find out more about how we detected these bug, you can find the open source tool at https://github.com/santolucito/ConfigV. For a quick overview of this tool, you can watch this video at https://youtu.be/plliEh-5MpM. If you have further questions, or would like to get involved with this project, feel free to reach out over email at<EMAIL_ADDRESS>Thank you for your time!

This repo is dormant, and has not been touched in several years. Thanks, though!


Corrected a typo

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey @sambhujimmi
Could you go through checklist and make sure everything is in order?
Thank you and happy coding.

Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


Parse nanoseconds for intervals

Which issue does this PR close?

Closes #3204.
Rationale for this change

Change parsing granularity of intervals from milliseconds to nanoseconds, to support passing fractions of milliseconds/seconds (down to nanoseconds) as IntervalMonthDayNano supports granularity down to nanoseconds.
What changes are included in this PR?

Accumulating with nanoseconds instead of milliseconds, changing to f64/i128 where necessary to account for shift in range of values.
Are these changes tested?

Added some unit tests, and fixed others as there is now more precision for seconds fractions.
Are there any user-facing changes?

thank you @Jefffrey
there's a bug while displaying IntervalMonthDayNano
❯ select interval '0.0001 second';
+----------------------------------------------------+
| IntervalMonthDayNano("100000")                     |
+----------------------------------------------------+
| 0 years 0 mons 0 days 0 hours 0 mins 0.100000 secs |
+----------------------------------------------------+
1 row in set. Query took 0.002 seconds.

i checked the underline value it's correct (month: 0, day: 0, nanos: 100000) i think this is the display issue

Issue with arrow-rs, has already been addressed: https://github.com/apache/arrow-rs/pull/3093

while we have leading zeros after decimal, it displays incorrectly
❯ select interval '0.01 second';
+------------------------------------------------+
| IntervalDayTime("10")                          |
+------------------------------------------------+
| 0 years 0 mons 0 days 0 hours 0 mins 0.10 secs |
+------------------------------------------------+
1 row in set. Query took 0.000 seconds.

❯ select interval '0.001 second';
+------------------------------------------------+
| IntervalDayTime("1")                           |
+------------------------------------------------+
| 0 years 0 mons 0 days 0 hours 0 mins 0.01 secs |
+------------------------------------------------+
1 row in set. Query took 0.000 seconds.

Thanks @Jefffrey  for the fix and @waitingkuo and @waynexia for the reviews!


Set types for two arguments

Currently, the 'host_groups' and 'link_templates' args are
interpreted as 'str' types, at least with python v2.7.5, thus
resulting in failure during playbooks execution:
fatal: [localhost -> localhost]: FAILED! =>
{"changed": false, "failed": true, "msg": "Template not found: ["}
To prevent this, we need to set a proper type - the list - for
these arguments.

oh my.
Why there's library/zabbix_host ?
when the very same module available from upstream since 2.0?

Its a good question. Ok so I can propose here to remove the library/ directory for good.

PR updated to remove these py scripts as there are in upstream equivalent modules and having them may cause the Ansible to not use the upstreams ones.

Thanks!